From 6445fcc05bfc9e817b656bd736d1ab99d4861dd6 Mon Sep 17 00:00:00 2001 From: Antigravity Agent Date: Sat, 2 May 2026 09:18:34 +0900 Subject: [PATCH] docs: finalized wiki integrity maintenance (v3.0 standard) - pruned 1400+ stubs and fixed 11k+ ghost links --- 00_Raw/.gitkeep | 0 01_Archive/.gitkeep | 0 01_Archive/2026-04-20/.gitkeep | 0 .../01_WebWorker-performance-optimization.md | 20 - ..._StateManagement-single-source-of-truth.md | 19 - .../03_Architecture-design-principle.md | 22 - .../04_execution-environment-management.md | 22 - .../05_simulation-design-principles.md | 19 - 01_Archive/2026-04-20/2026-04-15.md | 6 +- .../2026-04-20/20k skinned instances demo.md | 10 +- .../3D Gaussian Splatting (3DGS).md | 10 +- 01_Archive/2026-04-20/3D Web-based HMI.md | 10 +- .../2026-04-20/3D_Gaussian_Splatting.md | 10 +- 01_Archive/2026-04-20/3D_Web_HMI.md | 10 +- .../ABA(Applied Behavior Analysis).md | 6 +- 01_Archive/2026-04-20/ABA.md | 10 +- .../ACL-Injury-Prevention-Protocols.md | 6 +- 01_Archive/2026-04-20/ACL_Prevention.md | 10 +- 01_Archive/2026-04-20/AI Connect LLM Tool.md | 10 +- 01_Archive/2026-04-20/AI Safety (AI 안전).md | 6 +- .../AI 거버넌스 정책(AI Usage Policy).md | 10 +- .../AI 생성 코드 검증(AI Code Assurance).md | 10 +- .../2026-04-20/AI 에이전트 (AI Agent).md | 6 +- ...드 리뷰 및 보안 취약점 점검(DevSecOps).md | 10 +- 01_Archive/2026-04-20/AI 코드 리뷰.md | 10 +- .../2026-04-20/AI-Driven Narrative Systems.md | 6 +- 01_Archive/2026-04-20/AI.md | 0 ...열 맡기기_ - 정적 분석 툴 (ESLint Prettier)).md | 10 +- ... 맡기기_ - 정적 분석 툴 (ESLint & Prettier)).md | 6 +- ...E (Almost Native Graphics Layer Engine).md | 10 +- 01_Archive/2026-04-20/ANGLE.md | 10 +- ...ity-for-Ontarians-with-Disabilities-Act.md | 6 +- ... 모델링 및 상태 머신(State Machine) 설계.md | 10 +- ... 모델링 (State Modeling and API Responses).md | 10 +- .../API 응답 및 에러 핸들링 아키텍처.md | 10 +- .../2026-04-20/API-Contract-Definition.md | 6 +- .../2026-04-20/API-First Architecture.md | 10 +- 01_Archive/2026-04-20/API-First-Design.md | 6 +- .../2026-04-20/ARG-Alternate-Reality-Games.md | 6 +- 01_Archive/2026-04-20/ASP.NET Core.md | 6 +- 01_Archive/2026-04-20/ASPNET Core.md | 10 +- 01_Archive/2026-04-20/AST (추상 구문 트리).md | 10 +- .../2026-04-20/AST(Abstract Syntax Tree).md | 10 +- .../2026-04-20/AST-Manipulation-Techniques.md | 6 +- .../2026-04-20/AST-based-Static-Analysis.md | 6 +- 01_Archive/2026-04-20/AST_Traversal.md | 10 +- .../2026-04-20/A_B-Testing-Platforms.md | 6 +- .../2026-04-20/Abstract Syntax Tree (AST).md | 10 +- .../Abstract-Syntax-Tree-Transformation.md | 6 +- .../Abstract-Syntax-Tree-Traversal.md | 6 +- 01_Archive/2026-04-20/Accessibility (A11y).md | 6 +- .../Accessibility-Compliance-Audit.md | 6 +- .../Accessibility-Compliance-WCAG.md | 6 +- 01_Archive/2026-04-20/Accessibility.md | 10 +- .../Adaptive Compute (적응형 계산량 조절).md | 6 +- .../2026-04-20/Adaptive-Learning-Systems.md | 6 +- 01_Archive/2026-04-20/Adaptive_Learning.md | 10 +- .../2026-04-20/Addiction Neuroscience.md | 6 +- .../2026-04-20/Addiction_Neuroscience.md | 10 +- 01_Archive/2026-04-20/Additive-Type-Logic.md | 6 +- .../Advanced-Design-Patterns-in-TypeScript.md | 6 +- .../2026-04-20/Advanced-Interface-Design.md | 6 +- .../Adversarial Attack (적대적 공격).md | 6 +- .../2026-04-20/Adversarial Code Stylometry.md | 10 +- .../2026-04-20/Aerospace Flight Simulation.md | 6 +- 01_Archive/2026-04-20/Affective Computing.md | 6 +- .../Affective User Interfaces (AUI).md | 6 +- .../2026-04-20/Agency and Player Autonomy.md | 6 +- .../Agency-Narrative Integration.md | 6 +- .../2026-04-20/Agency-in-Game-Design.md | 6 +- ...unication Protocol (에이전트 통신 규약).md | 6 +- .../2026-04-20/Agent-Based Modeling (ABM).md | 6 +- 01_Archive/2026-04-20/Agent-Based Modeling.md | 6 +- 01_Archive/2026-04-20/Agent-Based-Modeling.md | 6 +- .../Agile-Software-Development-Life-Cycle.md | 0 01_Archive/2026-04-20/Agile-UX-Integration.md | 6 +- ...ine (Full LootPlayer-Driven Production).md | 6 +- ...ne (Full Loot_Player-Driven Production).md | 6 +- .../Algebraic-Data-Types-in-TypeScript.md | 6 +- 01_Archive/2026-04-20/Algebraic-Data-Types.md | 6 +- .../2026-04-20/Algorithmic Bias in Art.md | 6 +- .../2026-04-20/Algorithmic Decision Making.md | 6 +- .../2026-04-20/Algorithmic Game Theory.md | 6 +- .../2026-04-20/Algorithmic Governance.md | 6 +- .../Algorithmic Mechanism Design.md | 6 +- 01_Archive/2026-04-20/Algorithmic Rhetoric.md | 6 +- 01_Archive/2026-04-20/Algorithmic-Biology.md | 6 +- .../2026-04-20/Algorithmic-Game-Theory.md | 6 +- .../2026-04-20/Algorithmic-Governance.md | 6 +- .../Allocation Timeline(할당 타임라인).md | 10 +- 01_Archive/2026-04-20/Allocation Timeline.md | 10 +- 01_Archive/2026-04-20/Alpha Blending.md | 8 +- ...iving Simulation] [Robotic Manipulation.md | 6 +- ...ving Simulation], [Robotic Manipulation.md | 6 +- 01_Archive/2026-04-20/AlphaZero Strategy.md | 6 +- .../Amazon-AWS-Formal-Verification.md | 6 +- 01_Archive/2026-04-20/Ambient Contexts.md | 6 +- 01_Archive/2026-04-20/Ambient Declarations.md | 6 +- 01_Archive/2026-04-20/Ambient-Declarations.md | 6 +- .../2026-04-20/Amdahl's Law (암달의 법칙).md | 6 +- .../2026-04-20/Amdahls Law (암달의 법칙).md | 6 +- .../Americans-with-Disabilities-Act-ADA.md | 6 +- .../2026-04-20/Amygdala Hyperactivity.md | 6 +- .../2026-04-20/Analyze runtime performance.md | 10 +- .../2026-04-20/AppSec (애플리케이션 보안).md | 10 +- .../Apple Human Interface Guidelines.md | 6 +- .../2026-04-20/Apple Vision Pro Ecosystem.md | 6 +- .../Apple-Human-Interface-Guidelines.md | 6 +- .../Architectural-Constraint-Enforcement.md | 6 +- 01_Archive/2026-04-20/Architecture.md | 10 +- 01_Archive/2026-04-20/Arkane Studios.md | 6 +- 01_Archive/2026-04-20/Arkane-Studios.md | 6 +- 01_Archive/2026-04-20/ArrayBuffer.md | 10 +- 01_Archive/2026-04-20/Arthrokinematics.md | 6 +- .../2026-04-20/Artificial Life (ALife).md | 6 +- .../Artificial-Intelligence-Explainability.md | 6 +- .../Artificial-Intelligence-in-Games.md | 6 +- .../2026-04-20/Artificial-Intelligence.md | 6 +- .../2026-04-20/Assignability-Relation.md | 6 +- 01_Archive/2026-04-20/Assignability-Rules.md | 6 +- .../Assistive-Technology-Interoperability.md | 6 +- .../2026-04-20/Athletic Peak Performance.md | 6 +- .../Athletic-Performance-Optimization.md | 6 +- .../2026-04-20/Atomic Design Pattern.md | 10 +- 01_Archive/2026-04-20/Auction Theory.md | 6 +- 01_Archive/2026-04-20/Auction-Theory.md | 6 +- .../Augmented Reality (AR) Interfaces.md | 6 +- .../2026-04-20/Augmented Reality (AR).md | 6 +- .../Augmented Reality Navigation Systems.md | 6 +- .../2026-04-20/Authorship Attribution.md | 10 +- ...sm Spectrum Disorder (ASD) Intervention.md | 6 +- .../2026-04-20/Automated-Client-Generation.md | 6 +- .../2026-04-20/Automated-Game-Testing.md | 6 +- .../2026-04-20/Automated-Map-Generation.md | 6 +- 01_Archive/2026-04-20/Automated-Reasoning.md | 6 +- .../2026-04-20/Automated-Refactoring-Tools.md | 6 +- .../2026-04-20/Automated-Theorem-Proving.md | 6 +- 01_Archive/2026-04-20/Automated_Mapping.md | 10 +- .../Autonomous Vehicle Path Planning.md | 6 +- .../Autonomous Vehicle Perception.md | 6 +- .../Autonomous-Polling-Wait-Automation.md | 10 +- .../Autonomous-Vehicle-Path-Planning.md | 6 +- .../2026-04-20/Autotelic Personality.md | 6 +- .../2026-04-20/Autotelic-Personality.md | 6 +- 01_Archive/2026-04-20/Axify.md | 10 +- 01_Archive/2026-04-20/Azure DevOps.md | 8 +- 01_Archive/2026-04-20/BIM 모델 렌더링.md | 10 +- 01_Archive/2026-04-20/BIM 모델 시뮬레이션.md | 10 +- .../BM25 알고리즘 (Best Match 25).md | 6 +- 01_Archive/2026-04-20/BVH.md | 10 +- 01_Archive/2026-04-20/Babylon.js.md | 6 +- 01_Archive/2026-04-20/Babylonjs.md | 10 +- 01_Archive/2026-04-20/Baseline Project.md | 10 +- ...chedMesh 및 InstancedMesh 성능 벤치마크.md | 10 +- 01_Archive/2026-04-20/BatchedMesh.md | 10 +- 01_Archive/2026-04-20/Batching.md | 10 +- 01_Archive/2026-04-20/Bay 12 Games.md | 6 +- 01_Archive/2026-04-20/Bayesian Inference.md | 6 +- 01_Archive/2026-04-20/Bazel.md | 6 +- ...서게임 연구(Beat Saber Exergaming Study).md | 10 +- 01_Archive/2026-04-20/Beat Saber.md | 10 +- ...게임 후유증 연구(VR Exergaming Aftereffects).md | 10 +- ...avioral Economics in Digital Ecosystems.md | 6 +- 01_Archive/2026-04-20/Behavioral Economics.md | 6 +- 01_Archive/2026-04-20/Behavioral Finance.md | 6 +- 01_Archive/2026-04-20/Behavioral-Economics.md | 6 +- 01_Archive/2026-04-20/Behavioral_Economics.md | 10 +- 01_Archive/2026-04-20/Bellman Equation.md | 6 +- .../2026-04-20/Best SAST Tools in 2026.md | 10 +- .../Best-of-N Sampling (최적 샘플링).md | 6 +- .../2026-04-20/Bio-mechanical-Modeling.md | 6 +- 01_Archive/2026-04-20/BioShock (2007).md | 6 +- ... Home (Domestic Narrative Architecture).md | 6 +- ... Home (Domestic Narrative Architecture).md | 6 +- 01_Archive/2026-04-20/BioShock-Critique.md | 6 +- 01_Archive/2026-04-20/Bioenergetics.md | 6 +- .../Bioinformatics-Structure-Prediction.md | 6 +- .../2026-04-20/Biomechanical-Analysis.md | 6 +- .../2026-04-20/Biomechanics-of-Injury.md | 6 +- 01_Archive/2026-04-20/Biomechanics.md | 6 +- .../2026-04-20/Biomedical-Engineering.md | 10 +- 01_Archive/2026-04-20/Biometrics.md | 6 +- 01_Archive/2026-04-20/Bioregionalism.md | 6 +- 01_Archive/2026-04-20/Black-box Testing.md | 10 +- 01_Archive/2026-04-20/Blink.md | 10 +- 01_Archive/2026-04-20/Blog_Content_Rules.md | 6 +- 01_Archive/2026-04-20/Blog_Title_Rules.md | 6 +- .../2026-04-20/Borderlands-Art-Direction.md | 6 +- .../2026-04-20/Boundary-Layer-Validation.md | 6 +- 01_Archive/2026-04-20/Bounded Contexts.md | 10 +- 01_Archive/2026-04-20/Bounded Rationality.md | 6 +- ...nded-Contexts-and-Interface-Segregation.md | 6 +- .../Bounding Volume Hierarchy (BVH).md | 10 +- ...rain-Derived Neurotrophic Factor (BDNF).md | 6 +- 01_Archive/2026-04-20/Branch Prediction.md | 10 +- .../2026-04-20/Branchless Security Checks.md | 10 +- .../2026-04-20/Brand-Identity-Management.md | 6 +- .../2026-04-20/Branded Types in TypeScript.md | 6 +- 01_Archive/2026-04-20/Branded Types.md | 10 +- .../Branded-Types-for-Nominal-Typing.md | 6 +- 01_Archive/2026-04-20/Branded-Types.md | 6 +- .../Browser Security Mitigations.md | 10 +- 01_Archive/2026-04-20/Buck2.md | 6 +- 01_Archive/2026-04-20/Buffer Allocation.md | 10 +- 01_Archive/2026-04-20/BufferAttribute.md | 10 +- 01_Archive/2026-04-20/BufferGeometry.md | 10 +- ...rnout Prevention in Professional Gaming.md | 6 +- 01_Archive/2026-04-20/CAD 렌더링 최적화.md | 10 +- ...택 반응 시간 과제(CANTAB 5-choice RTI).md | 10 +- 01_Archive/2026-04-20/CI_CD Pipeline.md | 10 +- .../CI_CD 및 Pull Request 자동화 리뷰.md | 10 +- .../CI_CD 파이프라인 (CI_CD Pipelines).md | 10 +- .../CI_CD 파이프라인 및 IDE 통합 보안.md | 10 +- .../2026-04-20/CI_CD 파이프라인 자동화.md | 10 +- .../CI_CD 파이프라인 통합 및 Git 훅(Hooks).md | 10 +- 01_Archive/2026-04-20/CI_CD 파이프라인.md | 10 +- 01_Archive/2026-04-20/CI_CD.md | 10 +- 01_Archive/2026-04-20/CPTED.md | 6 +- 01_Archive/2026-04-20/CPU Bottleneck.md | 10 +- 01_Archive/2026-04-20/CPU Overhead.md | 10 +- 01_Archive/2026-04-20/CST (구체 구문 트리).md | 10 +- 01_Archive/2026-04-20/CST.md | 10 +- 01_Archive/2026-04-20/CV_Synthesis.md | 10 +- .../2026-04-20/Cache Side-Channel Attack.md | 10 +- 01_Archive/2026-04-20/Cache miss rates.md | 10 +- ...등의 프로그램 바이너리 작성자 식별 연구.md | 10 +- 01_Archive/2026-04-20/Call Stack.md | 10 +- .../2026-04-20/Causal Loop Diagramming.md | 6 +- .../Causal Tracing (인과적 추적).md | 6 +- .../2026-04-20/Cel-Shading-Techniques.md | 6 +- 01_Archive/2026-04-20/Cellular Automata.md | 6 +- 01_Archive/2026-04-20/Cellular-Automata.md | 6 +- .../2026-04-20/Central-Pattern-Generators.md | 6 +- 01_Archive/2026-04-20/Cesium.md | 10 +- 01_Archive/2026-04-20/CesiumJS.md | 12 +- .../Chain-of-Thought (CoT 사고 사슬).md | 6 +- .../Chain-of-Thought (CoT, 사고 사슬).md | 6 +- 01_Archive/2026-04-20/Chaos Theory.md | 6 +- 01_Archive/2026-04-20/Chaos-Theory.md | 6 +- 01_Archive/2026-04-20/Cheney's Algorithm.md | 6 +- 01_Archive/2026-04-20/Cheneys Algorithm.md | 10 +- .../Choice Architecture in Digital UX.md | 6 +- 01_Archive/2026-04-20/Chrome (Blink_Dawn).md | 10 +- .../Chrome DevTools Memory Panel.md | 10 +- .../Chrome DevTools Memory Profiling.md | 10 +- ...ome DevTools 메모리 분석 및 성능 최적화.md | 10 +- ...ols 메모리 프로파일링 및 힙 스냅샷 분석.md | 10 +- .../Chrome DevTools 메모리 프로파일링.md | 10 +- .../Chrome DevTools(크롬 개발자 도구).md | 10 +- 01_Archive/2026-04-20/Chrome DevTools.md | 10 +- .../Chrome User Experience Report (CrUX).md | 10 +- .../2026-04-20/Chrome V8 Heap Analysis.md | 10 +- 01_Archive/2026-04-20/Chrome WebGPU 구현.md | 10 +- .../Chrome _ Blink WebGPU Implementation.md | 10 +- ...Chrome 렌더러 프로세스 V8 샌드박스 보안.md | 10 +- .../2026-04-20/Chrome 브라우저 렌더링 성능.md | 10 +- 01_Archive/2026-04-20/Chrome.md | 10 +- .../Chromium WebGPU Implementation.md | 10 +- 01_Archive/2026-04-20/Chromium.md | 10 +- .../Chronic-Pain-Management-Protocols.md | 6 +- .../Circuit Discovery (회로 발견).md | 6 +- .../Circular Economy Transitions.md | 6 +- 01_Archive/2026-04-20/Circular-Economy.md | 6 +- 01_Archive/2026-04-20/Clean as You Code.md | 10 +- .../Clean-Architecture-Implementation.md | 6 +- .../Clean-Architecture-TypeScript.md | 6 +- .../Climate Change Mitigation Frameworks.md | 6 +- .../Clinical-Kinesiology-Assessment.md | 6 +- 01_Archive/2026-04-20/Code Formatting.md | 10 +- 01_Archive/2026-04-20/Code Minification.md | 10 +- 01_Archive/2026-04-20/Code Obfuscation.md | 10 +- 01_Archive/2026-04-20/Code Review.md | 10 +- ... Lazy Loading (코드 분할 및 지연 로딩).md | 10 +- .../Code Splitting Lazy Loading.md | 6 +- ...& Lazy Loading (코드 분할 및 지연 로딩).md | 6 +- .../Code Splitting & Lazy Loading.md | 0 .../Code Stylometry (코드 문체론).md | 10 +- 01_Archive/2026-04-20/Codemod-Engineering.md | 6 +- .../2026-04-20/Cognitive Aging Research.md | 6 +- 01_Archive/2026-04-20/Cognitive Biases.md | 6 +- 01_Archive/2026-04-20/Cognitive Computing.md | 6 +- 01_Archive/2026-04-20/Cognitive Dissonance.md | 6 +- .../2026-04-20/Cognitive Load Theory.md | 6 +- .../Cognitive Neuroscience of Flow.md | 6 +- 01_Archive/2026-04-20/Cognitive Psychology.md | 6 +- .../2026-04-20/Cognitive Reserve Theory.md | 6 +- ...ining Software (e.g., Aim Lab_KovaaK's).md | 6 +- ... Training Software (eg Aim Lab_KovaaKs).md | 6 +- .../2026-04-20/Cognitive-Evaluation-Theory.md | 6 +- .../2026-04-20/Cognitive-Flexibility.md | 6 +- .../2026-04-20/Cognitive-Load-Theory.md | 6 +- 01_Archive/2026-04-20/Cognitive-Psychology.md | 6 +- .../2026-04-20/Cognitive-Therapy-in-CBT.md | 6 +- 01_Archive/2026-04-20/Cognitive_Load.md | 10 +- .../Collaborative Learning Environments.md | 6 +- .../2026-04-20/Combinatorial Game Theory.md | 6 +- .../2026-04-20/Combinatorial-Optimization.md | 6 +- 01_Archive/2026-04-20/CompCert-C-Compiler.md | 6 +- .../Competitive Esports Ecosystems.md | 6 +- .../2026-04-20/Complex Adaptive Systems.md | 6 +- .../2026-04-20/Complex-Adaptive-Systems.md | 6 +- .../Complexity Science in Economics.md | 6 +- 01_Archive/2026-04-20/Complexity Theory.md | 6 +- 01_Archive/2026-04-20/Complexity-Theory.md | 6 +- .../Computation-Caching-Strategies.md | 6 +- .../2026-04-20/Computational Creativity.md | 6 +- .../2026-04-20/Computational Ecology.md | 6 +- .../2026-04-20/Computational Geometry.md | 10 +- ... Neuroscience of Reinforcement Learning.md | 6 +- .../2026-04-20/Computational Thinking.md | 6 +- .../2026-04-20/Computational-Creativity.md | 6 +- .../Computational-Fluid-Dynamics.md | 6 +- 01_Archive/2026-04-20/Compute Shader.md | 8 +- 01_Archive/2026-04-20/Compute Shaders.md | 10 +- 01_Archive/2026-04-20/Computer Vision.md | 6 +- .../2026-04-20/Computer-Aided-Design (CAD).md | 6 +- .../2026-04-20/Computer-Vision-Synthesis.md | 6 +- 01_Archive/2026-04-20/Computer_Vision.md | 10 +- .../Concept Drift (개념 드리프트).md | 6 +- ...Drift (개념 드리프트, 모델 지식의 부패).md | 10 +- .../2026-04-20/Concrete Syntax Tree (CST).md | 8 +- 01_Archive/2026-04-20/Conditional-Types.md | 6 +- .../Connect AI 기술 문서 및 사용 설명서.md | 6 +- ... AI 시스템 아키텍처 및 데이터 흐름 분석.md | 6 +- 01_Archive/2026-04-20/Conscientiousness.md | 6 +- .../2026-04-20/Constitutional AI (헌법 AI).md | 6 +- .../Constraint Satisfaction Problems (CSP).md | 6 +- .../Constraint-Satisfaction-Problems.md | 6 +- 01_Archive/2026-04-20/Content-Strategy.md | 6 +- .../2026-04-20/Continuous Integration (CI).md | 10 +- 01_Archive/2026-04-20/Continuous-Discovery.md | 6 +- .../2026-04-20/Contract-Driven-Development.md | 6 +- .../2026-04-20/Contract-First-Development.md | 6 +- 01_Archive/2026-04-20/Contract-Testing.md | 6 +- .../Contravariance-and-Covariance.md | 6 +- .../2026-04-20/Control Systems Engineering.md | 6 +- .../2026-04-20/Control-Flow-Analysis.md | 6 +- 01_Archive/2026-04-20/Control-Theory.md | 6 +- .../Conway's On Numbers and Games.md | 6 +- .../Conways On Numbers and Games.md | 6 +- 01_Archive/2026-04-20/Core Web Vitals.md | 10 +- 01_Archive/2026-04-20/Corgea.md | 10 +- .../2026-04-20/Corporate-LMS-Training.md | 6 +- .../2026-04-20/Cosmos 플랫폼 (Netflix).md | 10 +- .../Covariance-and-Contravariance.md | 6 +- 01_Archive/2026-04-20/CrUX.md | 10 +- 01_Archive/2026-04-20/Creative Process.md | 6 +- 01_Archive/2026-04-20/Creativity Research.md | 6 +- .../Creativity-and-Cognitive-Complexity.md | 6 +- .../2026-04-20/Credit Assignment Problem.md | 6 +- 01_Archive/2026-04-20/Critical Design.md | 6 +- 01_Archive/2026-04-20/Critical-Play.md | 6 +- 01_Archive/2026-04-20/Cryptoeconomics.md | 6 +- .../Cultural-Heritage-Informatics.md | 6 +- .../Cumulative Layout Shift (CLS).md | 10 +- .../Custom-ESLint-Rules-Development.md | 6 +- .../2026-04-20/Customer-Journey-Mapping.md | 6 +- 01_Archive/2026-04-20/CyArk.md | 6 +- .../Cyber-Physical Systems (CPS).md | 6 +- 01_Archive/2026-04-20/Cybernetics.md | 6 +- 01_Archive/2026-04-20/Cybertext Theory.md | 6 +- 01_Archive/2026-04-20/Cybertext.md | 6 +- .../2026-04-20/Cypher 질의 언어 (Neo4j).md | 6 +- .../DAST (동적 애플리케이션 보안 테스트).md | 10 +- 01_Archive/2026-04-20/DBpedia.md | 6 +- .../DOM 요소 조작 및 타입 좁히기.md | 10 +- 01_Archive/2026-04-20/DOM 요소 조작.md | 10 +- .../DPO (Direct Preference Optimization).md | 6 +- ...Dark Souls (Environmental Storytelling).md | 6 +- 01_Archive/2026-04-20/Data Array Textures.md | 10 +- .../Data Distillation (데이터 증류).md | 6 +- .../Data-Augmentation-for-Medical-Imaging.md | 6 +- 01_Archive/2026-04-20/Data-Sanitization.md | 6 +- 01_Archive/2026-04-20/Data-Science-in-UX.md | 6 +- .../2026-04-20/Data-Transfer-Object-Design.md | 6 +- 01_Archive/2026-04-20/Dead Space (Series).md | 6 +- .../Deceptive Alignment (기만적 정렬).md | 6 +- 01_Archive/2026-04-20/Decision Theory.md | 6 +- .../2026-04-20/Declaration Files (.d.ts).md | 6 +- .../2026-04-20/Declaration Files (dts).md | 6 +- 01_Archive/2026-04-20/Declaration Merging.md | 6 +- 01_Archive/2026-04-20/Declaration-Files.md | 6 +- 01_Archive/2026-04-20/Declaration-Merging.md | 6 +- .../2026-04-20/Deep Q-Networks (DQN).md | 6 +- .../2026-04-20/Deep-Convolutional-GANs.md | 6 +- 01_Archive/2026-04-20/DeepCode AI.md | 10 +- 01_Archive/2026-04-20/DeepReadonly.md | 10 +- .../2026-04-20/Deepfake-Detection-Research.md | 6 +- .../2026-04-20/Default Mode Network (DMN).md | 6 +- ...efinitelyTyped and Ambient Declarations.md | 6 +- 01_Archive/2026-04-20/DefinitelyTyped.md | 6 +- 01_Archive/2026-04-20/Degrees-of-Freedom.md | 6 +- 01_Archive/2026-04-20/Deliberate-Practice.md | 6 +- .../Denavit-Hartenberg-Parameters.md | 6 +- .../2026-04-20/Dependency-Graph-Analysis.md | 6 +- 01_Archive/2026-04-20/Dependency-Injection.md | 6 +- .../Dependency-Inversion-Principle.md | 6 +- 01_Archive/2026-04-20/Depth Pre-Pass.md | 10 +- 01_Archive/2026-04-20/Depth-Subtyping.md | 6 +- .../Description Logic (기술 논리).md | 6 +- 01_Archive/2026-04-20/Description-Logics.md | 6 +- 01_Archive/2026-04-20/Design-Thinking.md | 6 +- 01_Archive/2026-04-20/Design-Tokens.md | 6 +- .../2026-04-20/Deterministic Algorithms.md | 6 +- .../Deterministic Lockstep Architecture.md | 6 +- .../2026-04-20/DevOps-and-UX-Convergence.md | 6 +- 01_Archive/2026-04-20/DevSecOps.md | 10 +- 01_Archive/2026-04-20/Diegetic UI.md | 6 +- 01_Archive/2026-04-20/Diegetic-Interface.md | 6 +- 01_Archive/2026-04-20/Diffusion-Models.md | 6 +- 01_Archive/2026-04-20/Digital Humanities.md | 6 +- .../Digital Intellectual Property Rights.md | 6 +- .../2026-04-20/Digital Sandbox Theory.md | 6 +- .../2026-04-20/Digital Thread Integration.md | 6 +- .../2026-04-20/Digital Twin Interfaces.md | 6 +- .../2026-04-20/Digital Twin Visualization.md | 6 +- 01_Archive/2026-04-20/Digital Twins.md | 10 +- .../Digital-Heritage-Preservation.md | 6 +- 01_Archive/2026-04-20/Digital-Humanities.md | 6 +- .../Digital-Transformation-Strategy.md | 6 +- .../2026-04-20/Digital-Twin-Technology.md | 6 +- 01_Archive/2026-04-20/Digital_Twin.md | 10 +- .../Diminishing Returns (한계 수익 체감).md | 6 +- 01_Archive/2026-04-20/Direct3D.md | 10 +- .../Directed-Acyclic-Graph-Build-Systems.md | 6 +- ...ted-Acyclic-Graph-Dependency-Management.md | 6 +- 01_Archive/2026-04-20/Discriminated Unions.md | 10 +- ...Discriminated-Unions-for-Error-Handling.md | 6 +- ...Discriminated-Unions-for-State-Modeling.md | 6 +- 01_Archive/2026-04-20/Discriminated-Unions.md | 6 +- .../2026-04-20/Disentanglement (개념 분리).md | 6 +- .../2026-04-20/Dissipative Structures.md | 6 +- .../Distributed-System-Type-Safety.md | 6 +- .../Distributed-Systems-Engineering.md | 10 +- 01_Archive/2026-04-20/Divergent-Thinking.md | 6 +- 01_Archive/2026-04-20/Domain Objects.md | 10 +- .../Domain-Driven Design (DDD) Type Safety.md | 6 +- ...omain-Driven Design (DDD) in TypeScript.md | 6 +- .../2026-04-20/Domain-Driven Design (DDD).md | 10 +- ...omain-Driven-Design (DDD) in TypeScript.md | 6 +- .../2026-04-20/Domain-Driven-Design (DDD).md | 6 +- ...omain-Driven-Design-(DDD)-in-TypeScript.md | 6 +- .../2026-04-20/Domain-Driven-Design-(DDD).md | 6 +- .../Domain-Driven-Design-Bounded-Context.md | 6 +- ...Domain-Driven-Design-Interface-Modeling.md | 6 +- .../Domain-Driven-Design-in-TypeScript.md | 6 +- .../Domain-Driven-Design-with-TypeScript.md | 6 +- 01_Archive/2026-04-20/Domain-Driven-Design.md | 6 +- 01_Archive/2026-04-20/Dopamine Signaling.md | 6 +- 01_Archive/2026-04-20/Dopamine.md | 10 +- .../2026-04-20/Dopaminergic Reward System.md | 6 +- .../2026-04-20/Dopaminergic Reward Systems.md | 6 +- .../2026-04-20/Drama Management Systems.md | 6 +- .../2026-04-20/Drama-Management-Systems.md | 6 +- .../2026-04-20/Draw Call Optimization.md | 10 +- 01_Archive/2026-04-20/Draw Call.md | 10 +- 01_Archive/2026-04-20/Dual-Track-Agile.md | 6 +- .../Dublin Core Metadata Initiative.md | 6 +- 01_Archive/2026-04-20/Duck-Typing.md | 6 +- ...ication] [FinTech Engagement Strategies.md | 6 +- ...cation], [FinTech Engagement Strategies.md | 6 +- .../Dwarf Fortress (Simulation-heavy PCG).md | 6 +- 01_Archive/2026-04-20/Dwarf Fortress.md | 6 +- 01_Archive/2026-04-20/Dwarf-Fortress.md | 6 +- 01_Archive/2026-04-20/Dynamic Assessment.md | 6 +- .../Dynamic Difficulty Adjustment (DDA).md | 6 +- .../Dynamic Few-Shot (동적 퓨샷 선택 전략).md | 6 +- .../2026-04-20/Dynamical Systems Theory.md | 6 +- .../E-commerce-Catalog-Management.md | 6 +- .../E-commerce-Conversion-Optimization.md | 6 +- .../2026-04-20/E-commerce-Optimization.md | 6 +- 01_Archive/2026-04-20/ESL Pro Tour.md | 6 +- .../2026-04-20/ESLint-Plugin-TypeScript.md | 6 +- .../2026-04-20/ESLint-Static-Analysis.md | 6 +- 01_Archive/2026-04-20/ESLint.md | 10 +- .../EU-Web-Accessibility-Directive.md | 6 +- .../EVE Online (Spreadsheet Economy).md | 6 +- .../2026-04-20/EXT_disjoint_timer_query.md | 10 +- 01_Archive/2026-04-20/Early-Z.md | 10 +- .../Ecology and Ecosystem Modeling.md | 6 +- 01_Archive/2026-04-20/Ecosystem-Modeling.md | 6 +- .../2026-04-20/EdTech (Gamified Learning).md | 6 +- 01_Archive/2026-04-20/Edge Bleeding.md | 10 +- 01_Archive/2026-04-20/Edge Computing.md | 10 +- .../2026-04-20/Edge-Detection-Algorithms.md | 6 +- ...Pedagogy (Zone of Proximal Development).md | 6 +- .../2026-04-20/Educational-Gamification.md | 6 +- .../2026-04-20/Educational-Psychology.md | 6 +- .../Effect TS 및 ts-brand 라이브러리 활용.md | 10 +- 01_Archive/2026-04-20/Effect TS.md | 10 +- 01_Archive/2026-04-20/Electromyography.md | 6 +- .../2026-04-20/Electron V8 Memory Cage.md | 10 +- 01_Archive/2026-04-20/Electron.md | 10 +- .../2026-04-20/Elite-Athletic-Development.md | 6 +- .../Elite-Sport-Science-Protocols.md | 6 +- .../Elite-Strength-and-Conditioning.md | 6 +- .../Embodied Cognition in Virtual Reality.md | 6 +- 01_Archive/2026-04-20/Embodied Cognition.md | 6 +- .../2026-04-20/Emergent Gameplay Theory.md | 6 +- 01_Archive/2026-04-20/Emergent Gameplay.md | 6 +- 01_Archive/2026-04-20/Emergent Systems.md | 6 +- 01_Archive/2026-04-20/Emergent-Gameplay.md | 6 +- ...lly Intelligent Tutoring Systems (EITS).md | 6 +- .../2026-04-20/Employee Engagement Systems.md | 6 +- .../Encapsulation-and-Information-Hiding.md | 6 +- .../Encapsulation-of-Domain-Invariants.md | 6 +- .../Encapsulation-via-Access-Modifiers.md | 6 +- .../Endurance-Athletics-Cognition.md | 6 +- .../2026-04-20/Enterprise-Design-Systems.md | 6 +- .../Enterprise-Resource-Planning-Systems.md | 6 +- .../Enterprise-Scale-Monorepo-Management.md | 6 +- .../Enterprise-Software-Architecture.md | 6 +- .../Enterprise-Software-Engineering.md | 6 +- .../Entity Component System (ECS).md | 6 +- .../2026-04-20/Environmental Storyability.md | 6 +- .../2026-04-20/Environmental Storytelling.md | 6 +- .../2026-04-20/Environmental-Storytelling.md | 6 +- .../2026-04-20/Epidemiological Forecasting.md | 6 +- .../2026-04-20/Epidemiological Modeling.md | 6 +- .../Epigenetics of Neuroplasticity.md | 6 +- 01_Archive/2026-04-20/Ergodic Literature.md | 6 +- 01_Archive/2026-04-20/Ergodic-Literature.md | 6 +- .../2026-04-20/Escape Hatch (탈출구).md | 10 +- 01_Archive/2026-04-20/Europeana.md | 6 +- 01_Archive/2026-04-20/Event Storming.md | 10 +- 01_Archive/2026-04-20/Evolutionary Biology.md | 6 +- .../2026-04-20/Evolutionary Computation.md | 6 +- 01_Archive/2026-04-20/Evolutionary-Biology.md | 6 +- .../2026-04-20/Evolutionary-Computation.md | 6 +- .../2026-04-20/Excess Property Checking.md | 10 +- .../2026-04-20/Excess-Property-Checking.md | 6 +- .../2026-04-20/Executive Dysfunction.md | 6 +- 01_Archive/2026-04-20/Executive Function.md | 6 +- .../2026-04-20/Executive-Function-Deficit.md | 6 +- 01_Archive/2026-04-20/Exercise-Physiology.md | 6 +- 01_Archive/2026-04-20/Exergaming.md | 10 +- .../Exhaustiveness-Checking-with-Never.md | 6 +- .../2026-04-20/Exhaustiveness-Checking.md | 6 +- .../2026-04-20/Expected Utility Theory.md | 6 +- 01_Archive/2026-04-20/Expo 2025 Osaka.md | 10 +- .../2026-04-20/Express.js-Type-Extensions.md | 6 +- .../2026-04-20/Expressjs-Type-Extensions.md | 6 +- .../2026-04-20/FSD (Feature-Sliced Design).md | 10 +- 01_Archive/2026-04-20/FXAA.md | 10 +- .../Facade Pattern (퍼사드 패턴).md | 10 +- .../2026-04-20/Fallout (Pip-Boy Mechanic).md | 6 +- .../Feature Ablation (피처 제거).md | 6 +- .../Feature Clamping (피처 고정).md | 6 +- .../2026-04-20/Feature-Sliced Design.md | 10 +- .../Federated SPARQL (연합 질의).md | 6 +- .../2026-04-20/Feedback-Control-Systems.md | 6 +- 01_Archive/2026-04-20/Figma.md | 10 +- 01_Archive/2026-04-20/Fill Rate.md | 10 +- .../2026-04-20/Finite-Element-Analysis.md | 6 +- .../Finite-State-Machines-in-TypeScript.md | 6 +- 01_Archive/2026-04-20/Firefox.md | 10 +- .../2026-04-20/First Input Delay (FID).md | 10 +- .../Fixed Time Step vs Variable Time Step.md | 6 +- 01_Archive/2026-04-20/Flame Chart.md | 10 +- 01_Archive/2026-04-20/Flow State Theory.md | 6 +- 01_Archive/2026-04-20/Flow State.md | 6 +- 01_Archive/2026-04-20/Flow Theory.md | 6 +- .../2026-04-20/Flow-Sensitive-Typing.md | 6 +- 01_Archive/2026-04-20/Flow-State.md | 6 +- 01_Archive/2026-04-20/Flow-Theory.md | 6 +- 01_Archive/2026-04-20/Formal-Grammar.md | 6 +- .../Formal-Methods-in-Software-Engineering.md | 6 +- .../2026-04-20/Formalism vs Structuralism.md | 6 +- .../2026-04-20/Formalism vs. Structuralism.md | 6 +- .../2026-04-20/Formalism-vs-Structuralism.md | 6 +- 01_Archive/2026-04-20/Formalist Criticism.md | 6 +- .../2026-04-20/Formalist Game Design.md | 6 +- 01_Archive/2026-04-20/Formatting.md | 10 +- 01_Archive/2026-04-20/Fractal-Geometry.md | 6 +- 01_Archive/2026-04-20/Fragment Shading.md | 10 +- 01_Archive/2026-04-20/Fragment-bound.md | 10 +- 01_Archive/2026-04-20/Frustum Culling.md | 10 +- 01_Archive/2026-04-20/Function-Overloading.md | 6 +- .../Function-Signature-Compatibility.md | 6 +- .../Functional Behavior Analysis (FBA).md | 10 +- .../Functional-Programming-in-TypeScript.md | 6 +- 01_Archive/2026-04-20/Fuzzing.md | 8 +- 01_Archive/2026-04-20/GC Root.md | 10 +- 01_Archive/2026-04-20/GPU Resources.md | 10 +- .../GPU for the Web Community Group.md | 10 +- 01_Archive/2026-04-20/GPU-driven Rendering.md | 10 +- 01_Archive/2026-04-20/GPU.md | 10 +- 01_Archive/2026-04-20/GPURenderBundles.md | 10 +- ...라인의 미세 지연(Micro-latency) 측정 사례.md | 10 +- .../GQL (Graph Query Language ISO 표준).md | 6 +- .../GQL (Graph Query Language, ISO 표준).md | 6 +- ...PO (Group Relative Policy Optimization).md | 6 +- .../2026-04-20/Gacha Mechanics Analysis.md | 6 +- .../2026-04-20/Gait-Analysis-Laboratory.md | 6 +- .../2026-04-20/Gait-Analysis-Methodologies.md | 6 +- 01_Archive/2026-04-20/Game Balance Theory.md | 6 +- 01_Archive/2026-04-20/Game Design Theory.md | 10 +- .../2026-04-20/Game Economy Modeling.md | 6 +- ...ame Engine Architecture (Jason Gregory).md | 6 +- .../2026-04-20/Game Engine Architecture.md | 6 +- .../Game Studies (Academic Discipline).md | 6 +- .../Game Studies (Digital Media Theory).md | 6 +- .../Game Studies (Game Studies Journal).md | 6 +- .../Game Studies (Ludology vs Narratology).md | 6 +- ...Game Studies (Ludology vs. Narratology).md | 6 +- 01_Archive/2026-04-20/Game Studies.md | 6 +- 01_Archive/2026-04-20/Game Systems Design.md | 6 +- .../2026-04-20/Game Theory (Economics).md | 6 +- .../Game Theory and Market Equilibrium.md | 6 +- 01_Archive/2026-04-20/Game Theory.md | 6 +- 01_Archive/2026-04-20/Game-Design-Ontology.md | 6 +- 01_Archive/2026-04-20/Game-Design-Theory.md | 6 +- 01_Archive/2026-04-20/Game-Level-Design.md | 6 +- .../2026-04-20/Game-Ontology-for-PCG.md | 6 +- .../Game-Studies-Academic-Discourse.md | 6 +- 01_Archive/2026-04-20/Game-Studies-Journal.md | 6 +- 01_Archive/2026-04-20/Gamification Theory.md | 6 +- .../2026-04-20/Gamification in Pedagogy.md | 6 +- 01_Archive/2026-04-20/Gamification-Design.md | 6 +- .../2026-04-20/Gamification-Mechanics.md | 6 +- .../Garbage Collection (GC) 최적화.md | 10 +- .../2026-04-20/Garbage Collection (GC).md | 10 +- .../Garbage Collection(가비지 컬렉션).md | 10 +- 01_Archive/2026-04-20/Garbage Collection.md | 10 +- .../2026-04-20/Generational Hypothesis.md | 10 +- ...dversarial Networks (GANs) in Fine Arts.md | 6 +- .../Generative-Adversarial-Networks.md | 6 +- .../2026-04-20/Generics-and-Polymorphism.md | 6 +- .../Geographic-Information-Systems (GIS).md | 6 +- 01_Archive/2026-04-20/Geometry Merging.md | 10 +- 01_Archive/2026-04-20/Geriatric-Medicine.md | 6 +- 01_Archive/2026-04-20/Git Hooks.md | 10 +- ...t Hook을 이용한 CI_CD 자동화 파이프라인.md | 10 +- ...mmit 훅을 활용한 개발 워크플로우 자동화.md | 10 +- 01_Archive/2026-04-20/GitHub Actions.md | 10 +- 01_Archive/2026-04-20/GitLab CI.md | 10 +- 01_Archive/2026-04-20/Global Augmentation.md | 6 +- .../Global Network Positioning (GNP).md | 10 +- .../Goal Misgeneralization (목표 오일반화).md | 6 +- 01_Archive/2026-04-20/Google Chrome.md | 10 +- .../2026-04-20/Google Code Jam Dataset.md | 10 +- 01_Archive/2026-04-20/Google Lighthouse.md | 10 +- .../2026-04-20/Grammar-based-Synthesis.md | 6 +- .../Graph Theory in Level Design.md | 6 +- 01_Archive/2026-04-20/Graph Theory.md | 10 +- .../2026-04-20/Graph-Coloring-Problem.md | 6 +- 01_Archive/2026-04-20/Graph-Grammars.md | 6 +- 01_Archive/2026-04-20/Graph-Theory.md | 6 +- .../2026-04-20/GraphQL-Code-Generator.md | 6 +- .../GraphRAG (그래프 기반 검색 증강 생성).md | 6 +- 01_Archive/2026-04-20/Grit.md | 6 +- .../Grokking (그로킹 지연 일반화).md | 6 +- .../Grokking (그로킹, 지연 일반화).md | 6 +- ...rowth Mindset Intervention in Education.md | 6 +- 01_Archive/2026-04-20/Growth-Mindset.md | 6 +- .../Guilty-Gear-Xrd-Rendering-Pipeline.md | 6 +- 01_Archive/2026-04-20/HANDOVER.md | 6 +- .../2026-04-20/HBO Prestige Television.md | 6 +- 01_Archive/2026-04-20/HCI.md | 10 +- .../HHH (Helpful Harmless Honest).md | 6 +- .../HHH (Helpful, Harmless, Honest).md | 6 +- ...ead-Mounted Display) 기반 엑서게임 환경.md | 10 +- ...리즘 (Hierarchical Navigable Small World).md | 6 +- 01_Archive/2026-04-20/HTC Vive Pro HMD.md | 10 +- 01_Archive/2026-04-20/HTML5 Canvas.md | 10 +- .../2026-04-20/HUD-less Design Paradigms.md | 6 +- .../2026-04-20/Haptic Feedback Technology.md | 6 +- .../2026-04-20/Hardware-Verification.md | 6 +- .../Health Informatics (mHealth).md | 6 +- .../2026-04-20/Heap Snapshot(힙 스냅샷).md | 10 +- 01_Archive/2026-04-20/Heap Snapshot.md | 10 +- 01_Archive/2026-04-20/Hebbian Theory.md | 6 +- .../Hello Games Development Lifecycle.md | 6 +- ...erarchical Reinforcement Learning (HRL).md | 6 +- 01_Archive/2026-04-20/High Resolution Time.md | 10 +- .../2026-04-20/High-Cohesion-Low-Coupling.md | 6 +- .../High-Frequency Trading Models.md | 6 +- ...ormance Training Programs (Tier 1 Orgs).md | 6 +- .../2026-04-20/High-Performance-Coaching.md | 6 +- .../High-Performance-Human-Factors.md | 6 +- .../High-Performance-Sports-Science.md | 6 +- 01_Archive/2026-04-20/Homeostasis.md | 6 +- .../2026-04-20/Human-Centered Design.md | 6 +- .../Human-Computer Interaction (HCI).md | 6 +- .../Human-Computer-Interaction (HCI).md | 6 +- .../Human-Computer-Interaction-HCI.md | 6 +- .../2026-04-20/Human-Computer-Interaction.md | 6 +- .../Human-Machine Interface (HMI) Design.md | 6 +- .../Human-Robot Interaction (HRI).md | 6 +- .../2026-04-20/Human-Robot-Interaction.md | 6 +- 01_Archive/2026-04-20/Husky lint-staged.md | 10 +- 01_Archive/2026-04-20/Husky & lint-staged.md | 6 +- 01_Archive/2026-04-20/Husky.md | 10 +- .../Hyperinflation in Closed-Loop Systems.md | 6 +- 01_Archive/2026-04-20/Hypertextuality.md | 6 +- 01_Archive/2026-04-20/IBM 가비지 컬렉션.md | 10 +- 01_Archive/2026-04-20/IEEE P3652.1.md | 6 +- 01_Archive/2026-04-20/IEEE P36521.md | 6 +- 01_Archive/2026-04-20/IFC.js (Fragment).md | 6 +- 01_Archive/2026-04-20/IFC.js.md | 6 +- 01_Archive/2026-04-20/IFCjs (Fragment).md | 10 +- 01_Archive/2026-04-20/IFCjs.md | 10 +- 01_Archive/2026-04-20/ISO 9241 Standards.md | 6 +- 01_Archive/2026-04-20/ISO 9241 표준.md | 6 +- 01_Archive/2026-04-20/Immersive Analytics.md | 6 +- .../Immersive Educational Simulations.md | 6 +- 01_Archive/2026-04-20/Immersive Sim Design.md | 6 +- 01_Archive/2026-04-20/Immersive Sim Genre.md | 6 +- ...ersive Sims (e.g., Deus Ex, Dishonored).md | 6 +- .../Immersive Sims (e.g., Deus Ex, Thief).md | 6 +- .../Immersive Sims (eg Deus Ex Dishonored).md | 6 +- .../Immersive Sims (eg Deus Ex Thief).md | 6 +- 01_Archive/2026-04-20/Immersive-Sim-Genre.md | 6 +- .../2026-04-20/Immutability-Patterns.md | 6 +- .../In-Context Learning (ICL 문맥 내 학습).md | 6 +- ...In-Context Learning (ICL, 문맥 내 학습).md | 6 +- 01_Archive/2026-04-20/Inclusive_Design.md | 10 +- 01_Archive/2026-04-20/Incremental Marking.md | 10 +- .../2026-04-20/Incremental-Compilation.md | 6 +- .../2026-04-20/Incremental-Computation.md | 6 +- 01_Archive/2026-04-20/Index Masking.md | 10 +- 01_Archive/2026-04-20/Index.md | 62 +- 01_Archive/2026-04-20/Indirect Draw.md | 10 +- .../Indoor Wayfinding for Smart Cities.md | 6 +- 01_Archive/2026-04-20/Industrial Metaverse.md | 6 +- .../2026-04-20/Industrial-Automation.md | 6 +- .../Industry 4.0_Smart Manufacturing.md | 6 +- .../Industry 40_Smart Manufacturing.md | 6 +- 01_Archive/2026-04-20/Information Theory.md | 10 +- .../2026-04-20/Information-Architecture.md | 6 +- .../2026-04-20/Injury-Prevention-Protocols.md | 6 +- .../2026-04-20/Inquiry-Based Learning.md | 6 +- .../InstancedMesh (드로우 콜 최적화).md | 10 +- .../InstancedMesh Performance Bottlenecks.md | 10 +- .../InstancedMesh 동적 버퍼 확장.md | 10 +- ... 시 드로우 콜 최적화의 한계점 사례 연구.md | 10 +- 01_Archive/2026-04-20/InstancedMesh 최적화.md | 16 +- 01_Archive/2026-04-20/InstancedMesh.md | 10 +- .../2026-04-20/InstancedMesh2 library.md | 10 +- 01_Archive/2026-04-20/InstancedMesh2.md | 10 +- 01_Archive/2026-04-20/Instancing.md | 10 +- .../Instructional Systems Design (ISD).md | 6 +- 01_Archive/2026-04-20/Instructional-Design.md | 6 +- .../Integrated Gradients (통합 그래디언트).md | 6 +- .../Interaction to Next Paint (INP).md | 10 +- .../2026-04-20/Interactive Fiction (IF).md | 6 +- .../2026-04-20/Interactive Narrative.md | 6 +- .../2026-04-20/Interactive Storytelling.md | 6 +- .../Interactive-Fiction-Tradition.md | 6 +- .../2026-04-20/Interactive-Storytelling.md | 6 +- .../Interface Segregation Principle (ISP).md | 10 +- .../Interface Segregation Principle.md | 6 +- .../Interface-Extension-vs-Augmentation.md | 6 +- 01_Archive/2026-04-20/Interface-Extension.md | 6 +- 01_Archive/2026-04-20/Interface-Merging.md | 6 +- .../Interface-Segregation-Principle-in-TS.md | 6 +- ...ace-Segregation-Principle-in-TypeScript.md | 6 +- .../Interface-Segregation-Principle.md | 6 +- .../Internet of Things (IoT) Telemetry.md | 6 +- 01_Archive/2026-04-20/Interop 2025.md | 10 +- 01_Archive/2026-04-20/Interop 2026.md | 10 +- .../2026-04-20/Interoperability Standards.md | 6 +- .../Interpolation and Extrapolation.md | 6 +- ...tersection-Types-vs-Interface-Extension.md | 6 +- 01_Archive/2026-04-20/Intrinsic Motivation.md | 6 +- 01_Archive/2026-04-20/Intrinsic-Motivation.md | 6 +- .../Inventory Management Example.md | 10 +- 01_Archive/2026-04-20/Inverse-Kinematics.md | 6 +- 01_Archive/2026-04-20/InversifyJS.md | 6 +- 01_Archive/2026-04-20/IoT.md | 10 +- 01_Archive/2026-04-20/Irrational Games.md | 6 +- 01_Archive/2026-04-20/Isovist-Analysis.md | 6 +- 01_Archive/2026-04-20/Itô Calculus.md | 6 +- .../J-curve S-curve (AI 발전의 동학).md | 6 +- .../J-curve & S-curve (AI 발전의 동학).md | 6 +- 01_Archive/2026-04-20/JPEG XL.md | 10 +- .../2026-04-20/JSON-Schema-Validation.md | 6 +- 01_Archive/2026-04-20/JSON-Schema.md | 6 +- .../2026-04-20/Jacobian-Matrix-Analysis.md | 6 +- 01_Archive/2026-04-20/Jailbreaking (탈옥).md | 6 +- ...모리 관리(JavaScript Memory Management).md | 10 +- 01_Archive/2026-04-20/JavaScript.md | 10 +- 01_Archive/2026-04-20/JavaScriptCore.md | 10 +- 01_Archive/2026-04-20/Jenkins.md | 10 +- 01_Archive/2026-04-20/Joern.md | 10 +- 01_Archive/2026-04-20/K-12-EdTech.md | 6 +- .../KTO (Kahneman-Tversky Optimization).md | 6 +- .../Ken Levine-Design-Philosophy.md | 6 +- 01_Archive/2026-04-20/Keyof-Operator.md | 6 +- 01_Archive/2026-04-20/Kinematic-Modeling.md | 6 +- 01_Archive/2026-04-20/Kinematics.md | 6 +- 01_Archive/2026-04-20/Kinetics.md | 6 +- .../Knowledge-Graph-Construction.md | 6 +- 01_Archive/2026-04-20/Knowledge-Graphs.md | 6 +- .../Knowledge-Representation-in-AI.md | 6 +- 01_Archive/2026-04-20/L-Systems.md | 6 +- 01_Archive/2026-04-20/L-systems in Biology.md | 6 +- ...(League of Legends Championship Series).md | 6 +- .../2026-04-20/LLM Alignment (LLM 정렬).md | 6 +- .../LLM Hallucination (언어 모델 환각).md | 6 +- 01_Archive/2026-04-20/LLM.md | 10 +- 01_Archive/2026-04-20/LOD.md | 10 +- ...abeled Property Graph (LPG 속성 그래프).md | 6 +- ...beled Property Graph (LPG, 속성 그래프).md | 6 +- .../2026-04-20/Language-Acquisition-Apps.md | 6 +- ...Scale-Enterprise-Frontend-Architectures.md | 6 +- .../Large-Scale-Knowledge-Integration.md | 6 +- .../Large-scale-Frontend-Architecture.md | 6 +- .../Large-scale-TypeScript-Monorepos.md | 6 +- .../Largest Contentful Paint (LCP).md | 10 +- 01_Archive/2026-04-20/Latio.tech Report.md | 6 +- 01_Archive/2026-04-20/Latiotech Report.md | 10 +- 01_Archive/2026-04-20/Lean-UX.md | 6 +- .../2026-04-20/Lerna-Legacy-Management.md | 6 +- .../2026-04-20/Level Design Architecture.md | 6 +- .../2026-04-20/Level Design Automation.md | 6 +- 01_Archive/2026-04-20/Level Design Theory.md | 6 +- .../2026-04-20/Level of Detail (LOD).md | 10 +- .../2026-04-20/Level-Design-Automation.md | 6 +- 01_Archive/2026-04-20/Level-Design-Theory.md | 6 +- 01_Archive/2026-04-20/Lighthouse.md | 10 +- ...resentation Hypothesis (선형 표현 가설).md | 6 +- 01_Archive/2026-04-20/Linguistics.md | 6 +- .../2026-04-20/Linked Open Data (LOD).md | 6 +- .../2026-04-20/Linked-Data-Principles.md | 6 +- .../Liskov-Substitution-Principle.md | 6 +- .../2026-04-20/Live Service Game Design.md | 6 +- .../2026-04-20/Live Streaming Monetization.md | 6 +- 01_Archive/2026-04-20/LiveOps Management.md | 6 +- .../2026-04-20/LoRA (Low-Rank Adaptation).md | 6 +- 01_Archive/2026-04-20/Locus of Control.md | 6 +- 01_Archive/2026-04-20/Locus-of-Control.md | 6 +- .../2026-04-20/Logit Lens (로짓 렌즈).md | 6 +- .../2026-04-20/Long Animation Frames API.md | 10 +- 01_Archive/2026-04-20/Long Tasks.md | 10 +- .../Long-Term Potentiation (LTP).md | 6 +- .../2026-04-20/Looking Glass Studios.md | 6 +- .../2026-04-20/Looking-Glass-Studios.md | 6 +- ...ot Box Regulation (EU_China Compliance).md | 6 +- .../2026-04-20/Ludo-Narrative-Dissonance.md | 6 +- .../2026-04-20/Ludo-narrative Dissonance.md | 6 +- .../Ludology vs Narratology Debate.md | 6 +- .../2026-04-20/Ludology vs Narratology.md | 6 +- .../2026-04-20/Ludology vs. Narratology.md | 6 +- .../2026-04-20/Ludology-vs-Narratology.md | 6 +- 01_Archive/2026-04-20/Ludology.md | 6 +- .../2026-04-20/Ludonarrative Dissonance.md | 6 +- .../2026-04-20/Ludonarrative Resonance.md | 6 +- .../2026-04-20/Ludonarrative-Dissonance.md | 6 +- 01_Archive/2026-04-20/MDA Framework.md | 6 +- 01_Archive/2026-04-20/MDA-Framework.md | 6 +- 01_Archive/2026-04-20/MDA-P-Framework.md | 6 +- .../2026-04-20/MMORPG Economic Management.md | 6 +- 01_Archive/2026-04-20/MMORPG Ecosystems.md | 6 +- .../2026-04-20/MVC (Model-View-Controller).md | 10 +- .../Machine Learning in Game Design.md | 6 +- .../2026-04-20/Machine-Learning-Animation.md | 6 +- 01_Archive/2026-04-20/Main Thread.md | 10 +- 01_Archive/2026-04-20/Major GC.md | 10 +- 01_Archive/2026-04-20/Mapped-Types.md | 6 +- .../2026-04-20/Mark-Sweep-Compact 알고리즘.md | 10 +- .../Mark-Sweep-Compact(메이저 GC).md | 10 +- 01_Archive/2026-04-20/Mark-Sweep-Compact.md | 10 +- 01_Archive/2026-04-20/Mark-Sweep.md | 12 +- 01_Archive/2026-04-20/Market Regulation.md | 6 +- .../Markov Decision Process (MDP).md | 6 +- .../2026-04-20/Markov Decision Processes.md | 6 +- 01_Archive/2026-04-20/Markov-Random-Fields.md | 6 +- .../2026-04-20/Material Design System.md | 6 +- 01_Archive/2026-04-20/Material Design.md | 6 +- 01_Archive/2026-04-20/Material-Design.md | 6 +- .../2026-04-20/Mathematical Game Theory.md | 6 +- 01_Archive/2026-04-20/Measure Theory.md | 6 +- .../Mechanism Design in Auctions.md | 6 +- 01_Archive/2026-04-20/Mechanism Design.md | 6 +- 01_Archive/2026-04-20/Mechanism-Design.md | 6 +- ...c Interpretability (기계적 해석 가능성).md | 6 +- 01_Archive/2026-04-20/Mechanobiology.md | 6 +- 01_Archive/2026-04-20/Meltdown.md | 10 +- ...Memory Leak Prevention 메모리 누수 방지.md | 10 +- .../2026-04-20/Memory Leak(메모리 누수).md | 10 +- 01_Archive/2026-04-20/Memory Leak.md | 10 +- 01_Archive/2026-04-20/Memory Leaks.md | 10 +- 01_Archive/2026-04-20/Memory Management.md | 10 +- .../Mesa-Optimization (메사 최적화).md | 6 +- .../MeshStandardMaterial 조명 연산.md | 10 +- 01_Archive/2026-04-20/Mesocortical Pathway.md | 6 +- .../2026-04-20/Meta Quest_Horizon OS.md | 6 +- 01_Archive/2026-04-20/Metabolic Efficiency.md | 6 +- .../2026-04-20/Metabolic-Flexibility.md | 6 +- .../Metabolic-Resource-Allocation.md | 6 +- 01_Archive/2026-04-20/Metal.md | 10 +- 01_Archive/2026-04-20/Metaverse Aesthetics.md | 6 +- .../2026-04-20/Metaverse Architecture.md | 6 +- 01_Archive/2026-04-20/Metro Exodus.md | 6 +- .../2026-04-20/Micro-Frontend-Architecture.md | 6 +- 01_Archive/2026-04-20/Micro-latency.md | 10 +- ...oservices-Architecture-Bounded-Contexts.md | 6 +- .../Microservices-Architecture-Type-Safety.md | 6 +- .../2026-04-20/Microservices-Architecture.md | 10 +- .../Microservices-Communication-Patterns.md | 6 +- .../2026-04-20/Microsoft Edge DevTools.md | 10 +- 01_Archive/2026-04-20/Minecraft.md | 6 +- .../Minecraft_ Education Edition.md | 6 +- 01_Archive/2026-04-20/Mipmap.md | 10 +- .../Mobile Gaming Monetization Strategies.md | 6 +- .../2026-04-20/Mobile-App-Development.md | 6 +- .../2026-04-20/Mobile-App-Onboarding.md | 6 +- .../Model Collapse (모델 붕괴 현상).md | 6 +- .../Model Context Protocol (MCP).md | 10 +- .../Model Predictive Control (MPC).md | 6 +- .../Model Spec (모델 스펙 AI 행동 명세서).md | 6 +- .../Model Spec (모델 스펙, AI 행동 명세서).md | 6 +- 01_Archive/2026-04-20/Model-Checking.md | 6 +- .../Model-Free RL vs Model-Based RL.md | 6 +- 01_Archive/2026-04-20/Module Augmentation.md | 6 +- .../2026-04-20/Module Resolution Algorithm.md | 6 +- .../Module-Augmentation-Patterns.md | 6 +- 01_Archive/2026-04-20/Module-Augmentation.md | 6 +- .../2026-04-20/Module-Boundary-Enforcement.md | 6 +- .../2026-04-20/Module-Resolution-Strategy.md | 6 +- .../Monetary Policy in Virtual Worlds.md | 6 +- 01_Archive/2026-04-20/Monetary Policy.md | 6 +- ...Monorepo(Turborepo 등) 환경의 린트 관리.md | 10 +- .../Monorepo-Architecture-Design.md | 6 +- .../2026-04-20/Monorepo-Architecture.md | 6 +- .../Monorepo-Dependency-Graph-Analysis.md | 6 +- 01_Archive/2026-04-20/Monorepo.md | 10 +- .../2026-04-20/Monosemanticity (일의성).md | 6 +- .../Monte Carlo Tree Search (MCTS).md | 6 +- .../2026-04-20/Motion-Capture-Retargeting.md | 6 +- .../2026-04-20/Motor-Learning-Theory.md | 6 +- 01_Archive/2026-04-20/Motor-Learning.md | 6 +- ...ti-Agent Debate (에이전트 간 토론 전략).md | 6 +- ...lti-Agent System (다중 에이전트 시스템).md | 6 +- 01_Archive/2026-04-20/Multi-Agent-Systems.md | 6 +- .../Multi-Hop Reasoning (다중 홉 추론).md | 6 +- .../2026-04-20/Multi-threaded Architecture.md | 10 +- .../Multimodal Sentiment Analysis.md | 6 +- 01_Archive/2026-04-20/Mycological Horror.md | 6 +- ...ropulsion-Laboratory-Software-Standards.md | 6 +- 01_Archive/2026-04-20/NPM Ecosystem.md | 6 +- 01_Archive/2026-04-20/NVIDIA Omniverse.md | 6 +- 01_Archive/2026-04-20/Narrative Design.md | 6 +- .../2026-04-20/Narrative Intelligence.md | 6 +- .../2026-04-20/Narrative-Branching-Models.md | 6 +- 01_Archive/2026-04-20/Narratology.md | 6 +- 01_Archive/2026-04-20/Nash Equilibrium.md | 6 +- 01_Archive/2026-04-20/Nash-Equilibrium.md | 6 +- ... Language Processing (NLP) in Narrative.md | 6 +- .../2026-04-20/Natural-Language-Processing.md | 6 +- .../2026-04-20/Naughty Dog Development.md | 6 +- 01_Archive/2026-04-20/Needle Engine.md | 10 +- 01_Archive/2026-04-20/NestJS-Architecture.md | 6 +- .../2026-04-20/Netflix 마이크로서비스 전환.md | 10 +- .../2026-04-20/Network Coordinate Systems.md | 10 +- 01_Archive/2026-04-20/Network Science.md | 6 +- ...rk Synchronization in Multiplayer Games.md | 6 +- .../2026-04-20/Neural-Symbolic-Integration.md | 6 +- 01_Archive/2026-04-20/Neuro-Symbolic-AI.md | 6 +- .../2026-04-20/Neurobiology-of-Reward.md | 6 +- .../Neurodevelopmental Disorders.md | 6 +- 01_Archive/2026-04-20/Neuroeconomics.md | 6 +- 01_Archive/2026-04-20/Neuroergonomics.md | 6 +- .../2026-04-20/Neuromuscular-Adaptation.md | 6 +- .../2026-04-20/Neuromuscular-Control.md | 6 +- ...pharmacology of Substance Use Disorders.md | 6 +- .../Neuroplasticity in Addiction.md | 6 +- .../Neuroplasticity in Motor Learning.md | 6 +- .../Neuroplasticity-in-Motor-Learning.md | 6 +- 01_Archive/2026-04-20/Neuroplasticity.md | 10 +- .../Neuroprosthetics-Development.md | 6 +- .../2026-04-20/Neuropsychiatric Disorders.md | 6 +- 01_Archive/2026-04-20/Neuropsychology.md | 6 +- .../Neurorehabilitation after Stroke.md | 6 +- .../Neurorehabilitation-Post-Stroke.md | 6 +- 01_Archive/2026-04-20/New Media Theory.md | 6 +- .../2026-04-20/New Space(Young Generation).md | 10 +- 01_Archive/2026-04-20/New Space.md | 10 +- 01_Archive/2026-04-20/Ninja-Build-System.md | 6 +- ... Sky (Large-scale planetary generation).md | 6 +- 01_Archive/2026-04-20/No Man's Sky.md | 6 +- ... Sky (Large-scale planetary generation).md | 6 +- 01_Archive/2026-04-20/No Mans Sky.md | 6 +- .../2026-04-20/Node.js Memory Management.md | 6 +- .../2026-04-20/Node.js Memory Tuning.md | 6 +- .../Node.js Production Monitoring.md | 6 +- .../2026-04-20/Node.js 메모리 누수 분석.md | 6 +- .../2026-04-20/Node.js 메모리 최적화.md | 6 +- 01_Archive/2026-04-20/Node.js 메모리 튜닝.md | 6 +- 01_Archive/2026-04-20/Node.js 성능 디버깅.md | 6 +- .../Node.js 성능 최적화 및 디버깅.md | 6 +- .../Node.js 프로덕션 메모리 누수 진단.md | 6 +- .../Node.js 프로덕션 메모리 문제 해결.md | 6 +- .../Node.js 프로덕션 메모리 병목 분석.md | 6 +- ...ode.js 프로세스 모니터링 및 메모리 분석.md | 6 +- .../Node.js-Backend-Architecture.md | 6 +- .../Node.js-Global-Namespace-Augmentation.md | 6 +- 01_Archive/2026-04-20/Node.js.md | 6 +- .../2026-04-20/Nodejs Memory Management.md | 10 +- 01_Archive/2026-04-20/Nodejs Memory Tuning.md | 10 +- .../Nodejs Production Monitoring.md | 10 +- .../2026-04-20/Nodejs 메모리 누수 분석.md | 10 +- 01_Archive/2026-04-20/Nodejs 메모리 최적화.md | 10 +- 01_Archive/2026-04-20/Nodejs 메모리 튜닝.md | 10 +- 01_Archive/2026-04-20/Nodejs 성능 디버깅.md | 10 +- .../Nodejs 성능 최적화 및 디버깅.md | 10 +- .../Nodejs 프로덕션 메모리 누수 진단.md | 10 +- .../Nodejs 프로덕션 메모리 문제 해결.md | 10 +- .../Nodejs 프로덕션 메모리 병목 분석.md | 10 +- ...Nodejs 프로세스 모니터링 및 메모리 분석.md | 10 +- .../2026-04-20/Nodejs-Backend-Architecture.md | 6 +- .../Nodejs-Global-Namespace-Augmentation.md | 6 +- 01_Archive/2026-04-20/Nodejs.md | 10 +- 01_Archive/2026-04-20/Nominal Typing.md | 6 +- 01_Archive/2026-04-20/Nominal-Subtyping.md | 6 +- .../Nominal-Typing-in-TypeScript.md | 6 +- .../Nominal-Typing-via-Branded-Types.md | 6 +- .../Nominal-Typing-vs-Structural-Typing.md | 6 +- 01_Archive/2026-04-20/Nominal-Typing.md | 6 +- .../Nominal-vs-Structural-Typing.md | 6 +- 01_Archive/2026-04-20/Non-Diegetic UI.md | 6 +- ...hotorealistic-Rendering-in-Level-Design.md | 6 +- .../2026-04-20/Non-null Assertion Operator.md | 8 +- ...NotebookLM-Automated-Authentication-CLI.md | 10 +- .../2026-04-20/Nuclear Deterrence Models.md | 6 +- 01_Archive/2026-04-20/Nudge Theory.md | 6 +- 01_Archive/2026-04-20/Nudge_Theory.md | 10 +- .../2026-04-20/Nutritional-Biochemistry.md | 6 +- 01_Archive/2026-04-20/Nx-Build-System.md | 6 +- ...WA vs CWA (개방 세계 vs 폐쇄 세계 가정).md | 6 +- 01_Archive/2026-04-20/OWASP Top 10.md | 10 +- .../Object Pooling (가비지 컬렉션 최적화).md | 6 +- .../Object Pooling (오브젝트 풀링).md | 10 +- 01_Archive/2026-04-20/Object Pooling.md | 10 +- .../2026-04-20/Object-Literal-Assignment.md | 6 +- .../Object-Oriented-Design-Patterns.md | 6 +- .../Object-Oriented-Interface-Design.md | 6 +- .../Objective Distillation (목표 증류).md | 6 +- 01_Archive/2026-04-20/Objectivism.md | 6 +- 01_Archive/2026-04-20/Occlusion Culling.md | 10 +- .../2026-04-20/Occupational-Ergonomics.md | 6 +- 01_Archive/2026-04-20/Occupational-Therapy.md | 6 +- .../OffscreenCanvas (멀티스레딩).md | 6 +- .../OffscreenCanvas Safari 제약 사항.md | 10 +- ...creenCanvas 기반 멀티스레드 렌더링 구현.md | 6 +- 01_Archive/2026-04-20/OffscreenCanvas.md | 10 +- ...eb Worker를 활용한 메인 스레드 병목 해결.md | 10 +- 01_Archive/2026-04-20/Oilpan.md | 10 +- .../2026-04-20/Okami-Ink-Wash-Aesthetics.md | 6 +- .../2026-04-20/Old Space (구 세대 공간).md | 10 +- .../2026-04-20/Old Space(Old Generation).md | 10 +- 01_Archive/2026-04-20/Old Space.md | 10 +- .../2026-04-20/Olympic-Training-Cycles.md | 6 +- .../2026-04-20/Olympic-Training-Models.md | 6 +- .../2026-04-20/Olympic-Training-Protocols.md | 6 +- .../Ontology-Driven-Relevancy-Filtering.md | 12 +- 01_Archive/2026-04-20/Ontology-Engineering.md | 6 +- .../Ontology-Guided Knowledge Extraction.md | 6 +- 01_Archive/2026-04-20/Opaque Types.md | 12 +- 01_Archive/2026-04-20/Opaque-Types.md | 6 +- .../2026-04-20/Open Metaverse Framework.md | 6 +- 01_Archive/2026-04-20/Open-Access-Movement.md | 6 +- .../2026-04-20/Open-World Design Paradigms.md | 6 +- .../2026-04-20/OpenAPI-Specification.md | 6 +- 01_Archive/2026-04-20/OpenGL ES 2.0.md | 6 +- 01_Archive/2026-04-20/OpenGL ES 20.md | 10 +- 01_Archive/2026-04-20/OpenGL ES.md | 10 +- 01_Archive/2026-04-20/Opera.md | 10 +- 01_Archive/2026-04-20/Operant Conditioning.md | 6 +- 01_Archive/2026-04-20/Operant_Conditioning.md | 10 +- .../2026-04-20/Operations-Management.md | 6 +- 01_Archive/2026-04-20/Operations-Research.md | 6 +- .../2026-04-20/Optimal-Experience-Research.md | 6 +- .../2026-04-20/Organizational Behavior.md | 6 +- .../Organizational Learning Culture.md | 6 +- .../2026-04-20/Organizational Psychology.md | 6 +- .../2026-04-20/Organizational-Behavior.md | 6 +- .../Organizational-Innovation-Management.md | 6 +- .../2026-04-20/Organizational-Psychology.md | 6 +- 01_Archive/2026-04-20/Orinoco GC.md | 10 +- .../2026-04-20/Orinoco 가비지 컬렉터.md | 10 +- 01_Archive/2026-04-20/Orinoco 프로젝트.md | 10 +- .../2026-04-20/Orinoco(V8 GC 프로젝트).md | 10 +- 01_Archive/2026-04-20/Orinoco.md | 10 +- .../Orthopedic-Implant-Validation.md | 6 +- .../Outer Alignment vs Inner Alignment.md | 6 +- 01_Archive/2026-04-20/Overdraw.md | 10 +- 01_Archive/2026-04-20/P-Reinforce_Skill.md | 14 +- 01_Archive/2026-04-20/PBR.md | 10 +- 01_Archive/2026-04-20/PCGML-Frameworks.md | 6 +- .../PEFT (Parameter-Efficient Fine-Tuning).md | 6 +- .../2026-04-20/PRM (Process Reward Model).md | 6 +- .../2026-04-20/Page Experience Algorithm.md | 10 +- .../PageRank (페이지랭크 알고리즘).md | 6 +- 01_Archive/2026-04-20/PageSpeed Insights.md | 10 +- ...Papers Please (Bureaucratic Simulation).md | 6 +- ...rs Please (Mechanics as Moral Argument).md | 6 +- ...apers, Please (Bureaucratic Simulation).md | 6 +- ...s, Please (Mechanics as Moral Argument).md | 6 +- 01_Archive/2026-04-20/Papers-Please.md | 6 +- 01_Archive/2026-04-20/Parse dont validate.md | 12 +- .../2026-04-20/Parse, don't validate.md | 8 +- 01_Archive/2026-04-20/Parser.md | 10 +- 01_Archive/2026-04-20/Pedestrian-Modeling.md | 6 +- .../2026-04-20/Perceptual-Motor-Skills.md | 6 +- .../Performance Management Systems.md | 6 +- 01_Archive/2026-04-20/Performance Panel.md | 10 +- .../2026-04-20/Performance Psychology.md | 6 +- 01_Archive/2026-04-20/Periodization-Theory.md | 6 +- 01_Archive/2026-04-20/Perlin Noise.md | 6 +- .../2026-04-20/Personalization-Engines.md | 6 +- 01_Archive/2026-04-20/Persuasive Games.md | 6 +- .../Phase Transition (위상 변이).md | 6 +- 01_Archive/2026-04-20/Phyllotaxis-Modeling.md | 6 +- .../2026-04-20/Physics Engine Integration.md | 6 +- .../2026-04-20/Physics-Based-Simulation.md | 6 +- 01_Archive/2026-04-20/Platform Economics.md | 6 +- .../Play-to-Earn (P2E) Economies.md | 6 +- 01_Archive/2026-04-20/Player Agency.md | 6 +- 01_Archive/2026-04-20/Player-Agency.md | 6 +- 01_Archive/2026-04-20/Player-Autonomy.md | 6 +- 01_Archive/2026-04-20/Pointer Compression.md | 10 +- 01_Archive/2026-04-20/Pointer Poisoning.md | 10 +- 01_Archive/2026-04-20/Policy.md | 3 - 01_Archive/2026-04-20/PolicyIQ.md | 10 +- .../Political-Philosophy-in-Games.md | 6 +- 01_Archive/2026-04-20/Positive Psychology.md | 6 +- 01_Archive/2026-04-20/Positive-Education.md | 6 +- 01_Archive/2026-04-20/Positive-Psychology.md | 6 +- .../2026-04-20/Post-Acute-Care-Models.md | 6 +- .../2026-04-20/Post-Apocalyptic Fiction.md | 6 +- .../Post-Modernist Literature in Gaming.md | 6 +- .../Post-Surgical-Orthopedic-Recovery.md | 6 +- 01_Archive/2026-04-20/Post-humanism.md | 6 +- 01_Archive/2026-04-20/Post-structuralism.md | 6 +- .../2026-04-20/Precision Medicine Training.md | 6 +- .../Predictive Maintenance (PdM).md | 6 +- 01_Archive/2026-04-20/Predictive-Modeling.md | 6 +- .../2026-04-20/Predictive-Urban-Modeling.md | 6 +- .../2026-04-20/Predictive_Maintenance.md | 10 +- .../Prefrontal Cortex Dysfunction.md | 6 +- .../Prefrontal-Cortex-Dysfunction.md | 6 +- 01_Archive/2026-04-20/Prettier.md | 10 +- .../Probabilistic-Graphical-Models.md | 6 +- ...obability Theory (Stochastic Processes).md | 6 +- 01_Archive/2026-04-20/Probability Theory.md | 6 +- .../2026-04-20/Problem-Solving-Theory.md | 6 +- ...ural Content Generation (PCG) Balancing.md | 6 +- .../Procedural Content Generation (PCG).md | 6 +- ...Generation via Machine Learning (PCGML).md | 6 +- .../Procedural Content Generation.md | 6 +- 01_Archive/2026-04-20/Procedural Rhetoric.md | 6 +- 01_Archive/2026-04-20/Procedural-Animation.md | 6 +- .../Procedural-Content-Generation (PCG).md | 6 +- ...Content-Generation-via-Machine-Learning.md | 6 +- .../Procedural-Content-Generation.md | 6 +- 01_Archive/2026-04-20/Procedural-Rhetoric.md | 6 +- .../Procedural-Texture-Generation.md | 6 +- .../Process Supervision (과정 감독).md | 6 +- .../Product-Analytics-Infrastructure.md | 6 +- 01_Archive/2026-04-20/Product-Types.md | 6 +- .../Prompt Injection (프롬프트 주입 공격).md | 6 +- 01_Archive/2026-04-20/Proprioception.md | 6 +- 01_Archive/2026-04-20/Prospect Theory.md | 6 +- .../Prosthetic-Design-Optimization.md | 6 +- .../2026-04-20/Protocol-Buffers-TypeScript.md | 6 +- 01_Archive/2026-04-20/Psychophysiology.md | 6 +- 01_Archive/2026-04-20/Public Policy Design.md | 6 +- .../Pull Request (PR) 워크플로우.md | 10 +- 01_Archive/2026-04-20/Pull Request (PR).md | 10 +- 01_Archive/2026-04-20/Quality Gates.md | 10 +- 01_Archive/2026-04-20/Quantitative Finance.md | 10 +- .../Quantitative-Usability-Testing.md | 6 +- .../Quantum-Computing-Simulations.md | 6 +- 01_Archive/2026-04-20/Quantum-Game-Theory.md | 6 +- .../R3F 3D 게임 환경의 메모리 관리.md | 6 +- 01_Archive/2026-04-20/RAG (검색 증강 생성).md | 6 +- .../2026-04-20/RDF-star (RDF 확장 사양).md | 6 +- 01_Archive/2026-04-20/RDF와 OWL.md | 6 +- 01_Archive/2026-04-20/README.md | 6 +- .../RLAIF (AI 피드백 기반 강화학습).md | 6 +- .../RLHF (인간 피드백 기반 강화학습).md | 6 +- 01_Archive/2026-04-20/RL_Neuroscience.md | 10 +- .../RRF (Reciprocal Rank Fusion).md | 6 +- 01_Archive/2026-04-20/Radix Sort.md | 10 +- ...리 엔진 스냅샷(Snapshot) 기반 상태 복원.md | 6 +- 01_Archive/2026-04-20/Raycaster.md | 10 +- 01_Archive/2026-04-20/Raycasting.md | 10 +- .../2026-04-20/ReAct (Reasoning Acting).md | 6 +- .../2026-04-20/ReAct (Reasoning + Acting).md | 6 +- .../2026-04-20/Reachability Analysis.md | 10 +- 01_Archive/2026-04-20/React 19 Compiler.md | 10 +- ...mpiler의 Three.js 런타임 성능 개선 원리.md | 4 +- ...ompiler의 Threejs 런타임 성능 개선 원리.md | 10 +- .../React Native 게임 최적화 (JSI Hermes).md | 6 +- .../React Native 게임 최적화 (JSI, Hermes).md | 6 +- .../React Performance Optimization.md | 10 +- .../2026-04-20/React Three Fiber (R3F).md | 10 +- ... Fiber 자산 최적화 (Asset Optimization).md | 10 +- ...e Fiber에서 Rapier 물리 엔진 최적화하기.md | 10 +- .../2026-04-20/React 게임 엔진 아키텍처.md | 6 +- .../React 기반 게임 엔진 아키텍처.md | 6 +- ...React 동시성 기능 (Concurrent Features).md | 6 +- .../2026-04-20/React 및 Next.js 개발 환경.md | 6 +- .../2026-04-20/React 및 Nextjs 개발 환경.md | 10 +- ...eact 상태 관리 (React State Management).md | 10 +- .../React 상태 관리 및 API 응답 처리.md | 10 +- .../React 재조정 (Reconciliation) 최적화.md | 10 +- .../2026-04-20/React 컴포넌트 Props 검증.md | 10 +- .../React 컴포넌트 Props 전달 및 상태 관리.md | 10 +- 01_Archive/2026-04-20/Readonly Type.md | 10 +- .../2026-04-20/Readonly 유틸리티 타입.md | 8 +- .../2026-04-20/Real User Monitoring (RUM).md | 10 +- .../2026-04-20/Real-Time-Game-Engines.md | 6 +- 01_Archive/2026-04-20/Redstone Engineering.md | 6 +- .../Redux 등 상태 관리 (State Management).md | 10 +- .../Redux 스타일 리듀서 및 액션 관리.md | 10 +- .../2026-04-20/Redux-Reducer-Pattern.md | 6 +- .../2026-04-20/Redux-Reducers-Design.md | 6 +- 01_Archive/2026-04-20/Redux-Reducers.md | 6 +- .../2026-04-20/Redux-State-Management.md | 6 +- .../2026-04-20/Redux-Toolkit-Architecture.md | 6 +- 01_Archive/2026-04-20/Regenerative Design.md | 6 +- 01_Archive/2026-04-20/Regenerative-Design.md | 6 +- .../2026-04-20/Rehabilitative-Medicine.md | 6 +- .../2026-04-20/Reinforcement Learning (RL).md | 6 +- .../Reinforcement Learning Reward Shaping.md | 6 +- ...ment Learning for Automated Playtesting.md | 6 +- .../Reinforcement Learning in Economics.md | 6 +- .../2026-04-20/Reinforcement Learning.md | 6 +- .../2026-04-20/Reinforcement Schedules.md | 6 +- 01_Archive/2026-04-20/Render State.md | 10 +- 01_Archive/2026-04-20/Resilience Science.md | 6 +- .../2026-04-20/Resilience-Engineering.md | 6 +- 01_Archive/2026-04-20/Result Type.md | 10 +- 01_Archive/2026-04-20/Retainers(유지 경로).md | 10 +- 01_Archive/2026-04-20/Retaining Path.md | 10 +- 01_Archive/2026-04-20/Retrograde-Games.md | 6 +- 01_Archive/2026-04-20/Revit glTF Export.md | 10 +- 01_Archive/2026-04-20/Revit 모델 렌더링.md | 10 +- .../2026-04-20/Reward Hacking (보상 해킹).md | 6 +- .../2026-04-20/Reward Prediction Error.md | 6 +- .../2026-04-20/Reward Shaping (보상 설계).md | 6 +- .../2026-04-20/Risk Management in Finance.md | 6 +- .../Robotic Manipulation Control.md | 6 +- .../Robotic-Manipulator-Dynamics.md | 6 +- .../Robotic-Prosthetics-Control-Systems.md | 6 +- .../2026-04-20/Robotics-Control-Systems.md | 6 +- .../2026-04-20/Robust-GitHub-Sync-Pipeline.md | 10 +- 01_Archive/2026-04-20/Robustness (강건성).md | 6 +- .../Roguelike Procedural Generation.md | 6 +- 01_Archive/2026-04-20/Roguelike Subgenre.md | 6 +- .../2026-04-20/Role-Playing-Games (RPGs).md | 6 +- 01_Archive/2026-04-20/Rowhammer attack.md | 10 +- 01_Archive/2026-04-20/Rowhammer.md | 10 +- .../2026-04-20/Runtime-Type-Validation.md | 6 +- ...T (Static Application Security Testing).md | 10 +- .../SAST (정적 애플리케이션 보안 테스트).md | 10 +- .../SAST (정적 애플리케이션 보안 테스팅).md | 10 +- 01_Archive/2026-04-20/SAST.md | 10 +- .../2026-04-20/SCA (소프트웨어 구성 분석).md | 10 +- 01_Archive/2026-04-20/SCADA.md | 10 +- .../SDLC (소프트웨어 개발 수명 주기).md | 10 +- .../SFT (Supervised Fine-Tuning).md | 6 +- .../SHACL (Shapes Constraint Language).md | 6 +- 01_Archive/2026-04-20/SLA-Definition.md | 6 +- .../SOLID 원칙 (SOLID Principles).md | 10 +- 01_Archive/2026-04-20/SOLID 원칙.md | 10 +- .../2026-04-20/SPA 라우트 전환 성능 최적화.md | 10 +- .../SPARQL (RDF 그래프 질의 언어).md | 6 +- .../STEM Laboratory Virtualization.md | 6 +- .../2026-04-20/SaaS-Product-Management.md | 6 +- .../2026-04-20/SaaS-Retention-Strategies.md | 6 +- ...tions (e.g., Minecraft, Dwarf Fortress).md | 6 +- ...mulations (eg Minecraft Dwarf Fortress).md | 6 +- 01_Archive/2026-04-20/Sandbox-Simulation.md | 6 +- 01_Archive/2026-04-20/Santa Fe Institute.md | 6 +- .../Satisfiability-Problem-(SAT).md | 6 +- 01_Archive/2026-04-20/Satisfies Operator.md | 10 +- .../Scaffolding (Instructional Technique).md | 6 +- 01_Archive/2026-04-20/Scavenge.md | 10 +- 01_Archive/2026-04-20/Scavenger 알고리즘.md | 10 +- 01_Archive/2026-04-20/Scavenger(Minor GC).md | 10 +- 01_Archive/2026-04-20/Scavenger(마이너 GC).md | 10 +- 01_Archive/2026-04-20/Scheduler API.md | 10 +- .../2026-04-20/Scheduling-and-Timetabling.md | 6 +- .../2026-04-20/Schema-Driven-Development.md | 6 +- 01_Archive/2026-04-20/Schema.org.md | 6 +- 01_Archive/2026-04-20/Schemaorg.md | 6 +- 01_Archive/2026-04-20/SeL4-Microkernel.md | 6 +- ...d Procedural Content Generation (SBPCG).md | 6 +- .../2026-04-20/Section-508-Compliance.md | 6 +- 01_Archive/2026-04-20/Segments.ai.md | 6 +- 01_Archive/2026-04-20/Segmentsai.md | 10 +- .../Self-Consistency (자기 일관성 디코딩).md | 6 +- .../2026-04-20/Self-Determination Theory.md | 6 +- .../2026-04-20/Self-Determination-Theory.md | 6 +- .../2026-04-20/Self-Organized Criticality.md | 6 +- .../Self-Play (자기 대결 기반 강화학습).md | 6 +- 01_Archive/2026-04-20/Self-Regulation.md | 6 +- .../Semantic Grounding Provenance.md | 6 +- .../Semantic Grounding & Provenance.md | 6 +- ...ntic Versioning (SemVer) in Type Safety.md | 6 +- .../2026-04-20/Semantic-Web-Technologies.md | 6 +- 01_Archive/2026-04-20/Semantic-Web.md | 6 +- 01_Archive/2026-04-20/Semgrep Assistant.md | 10 +- 01_Archive/2026-04-20/Semiotics in Media.md | 6 +- 01_Archive/2026-04-20/Sensor Fusion.md | 6 +- .../2026-04-20/Sensorimotor-Integration.md | 6 +- 01_Archive/2026-04-20/Serious Games.md | 6 +- 01_Archive/2026-04-20/Server Architecture.md | 6 +- .../2026-04-20/Service-Design-Blueprinting.md | 6 +- 01_Archive/2026-04-20/Service-Design.md | 6 +- .../2026-04-20/Service-Dominant-Logic.md | 6 +- 01_Archive/2026-04-20/Shannon-Entropy.md | 6 +- ...redArrayBuffer vs postMessage 성능 차이.md | 10 +- .../SharedArrayBuffer 동시성 문제 해결법.md | 10 +- ...안 이슈와 Cross-Origin Isolation 설정법.md | 10 +- ...ffer 보안 이슈와 Cross-Origin Isolation.md | 10 +- ...yBuffer 보안을 위한 COOP COEP 헤더 설정.md | 10 +- ...Buffer 보안을 위한 COOP, COEP 헤더 설정.md | 4 +- ...위한 Cross-Origin Isolation 서버 헤더 설정.md | 10 +- 01_Archive/2026-04-20/SharedArrayBuffer.md | 10 +- ...fer로 스레드 간 메모리 공유 효율 높이기.md | 6 +- ...aredArrayBuffer와 Atomics 구체적 활용법.md | 10 +- 01_Archive/2026-04-20/Side-channel Attack.md | 10 +- 01_Archive/2026-04-20/Side-channel attacks.md | 10 +- 01_Archive/2026-04-20/Signal Processing.md | 6 +- ...ty (as a model of systemic interaction).md | 6 +- 01_Archive/2026-04-20/SimCity-Series.md | 6 +- 01_Archive/2026-04-20/Simulated History.md | 6 +- 01_Archive/2026-04-20/Simulation Theory.md | 6 +- .../Simulations of Social Systems.md | 6 +- .../Simulator Sickness Questionnaire (SSQ).md | 10 +- ...taneous Localization and Mapping (SLAM).md | 6 +- .../Single Page Applications (SPA).md | 10 +- .../Single-Responsibility-Principle.md | 6 +- .../Single-Source-of-Truth-Principle.md | 6 +- .../2026-04-20/Single-Source-of-Truth.md | 6 +- .../2026-04-20/Singularity (기술적 특이점).md | 6 +- 01_Archive/2026-04-20/SkinnedMesh.md | 10 +- ...col 개발자 확장 가이드 및 아키텍처 리뷰.md | 6 +- ...조 및 의존성 분석 (Dependency Mapping).md | 6 +- ...d Protocol 기술 메뉴얼 및 개발자 가이드.md | 6 +- ...ocol 데이터 및 제어 흐름 (Control Flow).md | 6 +- ...col 시스템 아키텍처 및 데이터 흐름 분석.md | 6 +- .../2026-04-20/Skybound Protocol 코드리뷰.md | 10 +- .../2026-04-20/Smart City Digital Twins.md | 6 +- .../2026-04-20/Smart-City-Frameworks.md | 6 +- .../Smithsonian-Digital-Repository.md | 6 +- ...r Labs 등 종합 애플리케이션 보안 플랫폼.md | 10 +- 01_Archive/2026-04-20/Snyk Open Source.md | 10 +- ...r Labs 등 종합 애플리케이션 보안 플랫폼.md | 6 +- .../2026-04-20/Social Constructivism.md | 6 +- .../2026-04-20/Social Learning Theory.md | 6 +- .../2026-04-20/Social Systems Theory.md | 6 +- .../Socially Assistive Robotics (SAR).md | 6 +- 01_Archive/2026-04-20/Soft Navigation.md | 10 +- ...tware Architecture API Contract Design.md | 6 +- ...ware Architecture & API Contract Design.md | 6 +- .../Software-Contract-Enforcement.md | 6 +- .../2026-04-20/Software-Product-Management.md | 6 +- 01_Archive/2026-04-20/SonarQube.md | 10 +- 01_Archive/2026-04-20/Sorting.md | 10 +- .../2026-04-20/Sparse Autoencoder (SAE).md | 6 +- 01_Archive/2026-04-20/Spatial Cognition.md | 6 +- 01_Archive/2026-04-20/Spatial Computing.md | 6 +- 01_Archive/2026-04-20/Spatial Partitioning.md | 10 +- 01_Archive/2026-04-20/Spatial UI.md | 6 +- 01_Archive/2026-04-20/Spatial-Syntax.md | 6 +- 01_Archive/2026-04-20/Spatial_Computing.md | 10 +- .../Special Education Interventions.md | 6 +- .../Specification Gaming (명세 우회).md | 6 +- 01_Archive/2026-04-20/Spectre and Meltdown.md | 10 +- 01_Archive/2026-04-20/Spectre.md | 10 +- 01_Archive/2026-04-20/Speculative Biology.md | 6 +- .../2026-04-20/Speculative Execution.md | 10 +- .../2026-04-20/Sports Management Theory.md | 6 +- 01_Archive/2026-04-20/Sports Neuroscience.md | 6 +- .../Sports-Medicine-Rehabilitation.md | 6 +- .../Sports-Performance-Optimization.md | 6 +- 01_Archive/2026-04-20/Sports-Psychology.md | 6 +- .../2026-04-20/Sports-Science-Training.md | 6 +- .../2026-04-20/Sprague-Grundy Theorem.md | 6 +- 01_Archive/2026-04-20/Spring Framework.md | 10 +- .../State-Machine-Implementation.md | 6 +- ...tic Application Security Testing (SAST).md | 10 +- .../Static Type Checking Systems.md | 6 +- ...Static-Analysis-in-JavaScript-Ecosystem.md | 6 +- .../Static-Analysis-in-JavaScript.md | 6 +- ...Static-Analysis-in-Software-Engineering.md | 6 +- .../Static-Analysis-of-Interfaces.md | 6 +- .../2026-04-20/Static-Program-Analysis.md | 6 +- .../2026-04-20/Static-Type-Inference.md | 6 +- .../2026-04-20/Statistical Mechanics.md | 6 +- 01_Archive/2026-04-20/Stochastic Processes.md | 6 +- 01_Archive/2026-04-20/Stochastic-Games.md | 6 +- 01_Archive/2026-04-20/Stop-the-world.md | 10 +- .../2026-04-20/Structural Type System.md | 6 +- 01_Archive/2026-04-20/Structural Typing.md | 10 +- 01_Archive/2026-04-20/Structural-Subtyping.md | 6 +- .../2026-04-20/Structural-Type-System.md | 6 +- .../2026-04-20/Structural-Typing-Analysis.md | 6 +- .../Structural-Typing-Compatibility.md | 6 +- .../2026-04-20/Structural-Typing-Mechanics.md | 6 +- .../Structural-Typing-Mechanisms.md | 6 +- .../2026-04-20/Structural-Typing-System.md | 6 +- .../Structural-Typing-and-Compatibility.md | 6 +- .../Structural-Typing-vs-Nominal-Typing.md | 6 +- 01_Archive/2026-04-20/Structural-Typing.md | 6 +- .../Structural-vs-Nominal-Typing-in-TS.md | 6 +- .../Structural-vs-Nominal-Typing.md | 6 +- 01_Archive/2026-04-20/Structuralism.md | 6 +- 01_Archive/2026-04-20/StyleCounsel.md | 10 +- 01_Archive/2026-04-20/Submodules.md | 10 +- 01_Archive/2026-04-20/Subtyping-Relations.md | 6 +- 01_Archive/2026-04-20/Subtyping-Rules.md | 6 +- .../2026-04-20/Subtyping-and-Variance.md | 6 +- 01_Archive/2026-04-20/Sum-Types.md | 6 +- 01_Archive/2026-04-20/Superposition (중첩).md | 6 +- .../2026-04-20/Supply-Chain-Management.md | 6 +- 01_Archive/2026-04-20/Surgical-Robotics.md | 6 +- 01_Archive/2026-04-20/Surreal Numbers.md | 6 +- .../2026-04-20/Survival Horror Genre.md | 6 +- .../Sustainable Development Goals (SDGs).md | 6 +- .../Sustainable-Development-Goals (SDGs).md | 6 +- .../2026-04-20/Sycophancy (LLM 아첨 문제).md | 6 +- 01_Archive/2026-04-20/Symbolic-Logic.md | 6 +- 01_Archive/2026-04-20/Synaptic Plasticity.md | 6 +- .../2026-04-20/SynthID (구글 AI 식별 기술).md | 6 +- .../Synthetic Data (합성 데이터).md | 6 +- 01_Archive/2026-04-20/Synthetic Testing.md | 10 +- 01_Archive/2026-04-20/System Dynamics.md | 6 +- .../System Prompt (시스템 프롬프트).md | 6 +- 01_Archive/2026-04-20/Systemic Design.md | 6 +- 01_Archive/2026-04-20/Systemic Game Design.md | 6 +- 01_Archive/2026-04-20/Systemic-Cohesion.md | 6 +- .../2026-04-20/Systemic-Design-Frameworks.md | 6 +- 01_Archive/2026-04-20/Systemic-Design.md | 6 +- 01_Archive/2026-04-20/Systems Biology.md | 6 +- 01_Archive/2026-04-20/Systems Dynamics.md | 6 +- 01_Archive/2026-04-20/Systems Theory.md | 6 +- .../Systems Thinking in Management.md | 6 +- 01_Archive/2026-04-20/Systems Thinking.md | 6 +- 01_Archive/2026-04-20/Systems-Thinking.md | 6 +- 01_Archive/2026-04-20/TLB design.md | 10 +- .../2026-04-20/TSL (Three Shader Language).md | 10 +- .../2026-04-20/Taxonomy-and-Ontology.md | 6 +- 01_Archive/2026-04-20/TeamCity.md | 10 +- .../2026-04-20/Template-Literal-Types.md | 6 +- .../Temporal Difference Learning.md | 6 +- 01_Archive/2026-04-20/Temporal-Logic.md | 6 +- ...mpute Scaling (추론 시간 계산 스케일링).md | 6 +- 01_Archive/2026-04-20/Texture Atlas.md | 10 +- 01_Archive/2026-04-20/Texture Compression.md | 10 +- 01_Archive/2026-04-20/Texture-Synthesis.md | 6 +- .../The 'Immersive Sim' Taxonomy Debate.md | 6 +- .../The Emergence Theory in Game Design.md | 6 +- .../The Immersive Sim Taxonomy Debate.md | 6 +- ... (Resource Scarcity and Character Bond).md | 6 +- .../2026-04-20/The Last of Us Series.md | 6 +- .../The Overwatch League Case Study.md | 6 +- 01_Archive/2026-04-20/The Rapture Setting.md | 6 +- .../The Science of Well-Being (Yale).md | 6 +- .../The-Collapse-of-Utopian-Ideologies.md | 6 +- .../2026-04-20/The-Space-Syntax-Laboratory.md | 6 +- .../2026-04-20/Themework-Integration.md | 6 +- .../2026-04-20/Three Shader Language (TSL).md | 10 +- .../Three.js WebGL Rendering Optimization.md | 6 +- .../Three.js WebGL 렌더링 최적화.md | 6 +- .../2026-04-20/Three.js WebGPU 파티클 예제.md | 6 +- .../2026-04-20/Three.js WebGPURenderer.md | 6 +- ...hree.js 대규모 렌더링 최적화 파이프라인.md | 6 +- .../2026-04-20/Three.js 렌더링 성능 최적화.md | 6 +- .../2026-04-20/Three.js 렌더링 최적화.md | 10 +- .../Three.js 모바일 렌더링 최적화.md | 6 +- 01_Archive/2026-04-20/Three.js 성능 최적화.md | 6 +- 01_Archive/2026-04-20/Three.js.md | 6 +- .../Threejs WebGL Rendering Optimization.md | 10 +- .../2026-04-20/Threejs WebGL 렌더링 최적화.md | 10 +- .../2026-04-20/Threejs WebGPU 파티클 예제.md | 10 +- .../2026-04-20/Threejs WebGPURenderer.md | 10 +- ...Threejs 대규모 렌더링 최적화 파이프라인.md | 10 +- .../2026-04-20/Threejs 렌더링 성능 최적화.md | 10 +- .../2026-04-20/Threejs 렌더링 최적화.md | 10 +- .../Threejs 모바일 렌더링 최적화.md | 10 +- 01_Archive/2026-04-20/Threejs 성능 최적화.md | 10 +- .../2026-04-20/Threejs 자원 해제 (Dispose).md | 6 +- 01_Archive/2026-04-20/Threejs.md | 10 +- ...tling Debouncing (스로틀링과 디바운싱).md | 6 +- .../2026-04-20/Throttling Debouncing.md | 10 +- .../2026-04-20/Throttling & Debouncing.md | 6 +- 01_Archive/2026-04-20/Time Series Analysis.md | 6 +- .../2026-04-20/Time to Interactive (TTI).md | 10 +- .../2026-04-20/Timestamp Quantization.md | 10 +- .../Timestamp Queries Quantization.md | 10 +- 01_Archive/2026-04-20/Timestamp Queries.md | 10 +- 01_Archive/2026-04-20/Timing Attack.md | 10 +- .../Timing Attacks (Spectre_Meltdown).md | 10 +- 01_Archive/2026-04-20/Timing Attacks.md | 10 +- .../2026-04-20/To-Space와 From-Space.md | 10 +- 01_Archive/2026-04-20/Tokenomics.md | 6 +- 01_Archive/2026-04-20/Topological-Sorting.md | 6 +- .../2026-04-20/Topology-of-Strategy-Spaces.md | 6 +- ...반 외부 연동사 플러그인 개발 생태계 구축.md | 10 +- .../Toss Front SDK의 Facade 패턴 적용 사례.md | 10 +- ...사드(Facade) 패턴 설계와 인터페이스 전략.md | 10 +- 01_Archive/2026-04-20/Touchpoint-Analysis.md | 6 +- 01_Archive/2026-04-20/Trajectory-Planning.md | 6 +- 01_Archive/2026-04-20/Transhumanism.md | 6 +- .../2026-04-20/Transient Hypofrontality.md | 6 +- .../2026-04-20/Transient-Hypofrontality.md | 6 +- .../Transit-Oriented-Development (TOD).md | 6 +- .../Tree Shaking (번들 크기 최적화).md | 10 +- .../Tree-of-Thought (ToT 사고 트리).md | 6 +- .../Tree-of-Thought (ToT, 사고 트리).md | 6 +- .../Turborepo 기반 모노레포 워크플로우.md | 10 +- 01_Archive/2026-04-20/Turborepo 환경 구성.md | 10 +- .../2026-04-20/Turborepo-Orchestration.md | 6 +- 01_Archive/2026-04-20/Turborepo.md | 10 +- ... 다중 애플리케이션 및 라이브러리 통합 관리.md | 10 +- 01_Archive/2026-04-20/Turtle-Graphics.md | 6 +- 01_Archive/2026-04-20/Type Alias.md | 10 +- 01_Archive/2026-04-20/Type Branding.md | 6 +- 01_Archive/2026-04-20/Type Casting.md | 10 +- 01_Archive/2026-04-20/Type Declaration.md | 10 +- ...Type Definition Files (DefinitelyTyped).md | 6 +- 01_Archive/2026-04-20/Type Inference.md | 6 +- 01_Archive/2026-04-20/Type Narrowing.md | 8 +- 01_Archive/2026-04-20/Type Predicates.md | 6 +- 01_Archive/2026-04-20/Type Theory.md | 10 +- 01_Archive/2026-04-20/Type-Assertion.md | 6 +- 01_Archive/2026-04-20/Type-Aware-Linting.md | 6 +- .../2026-04-20/Type-Compatibility-Rules.md | 6 +- .../Type-Compatibility-and-Subtyping.md | 6 +- 01_Archive/2026-04-20/Type-Compatibility.md | 6 +- ...Type-Composition-via-Intersection-Types.md | 6 +- .../Type-Composition-via-Intersections.md | 6 +- .../2026-04-20/Type-Driven-Development.md | 6 +- .../Type-Erasure-and-Runtime-Behavior.md | 6 +- 01_Archive/2026-04-20/Type-Erasure.md | 6 +- .../2026-04-20/Type-Guards-and-Narrowing.md | 6 +- 01_Archive/2026-04-20/Type-Guards.md | 6 +- .../2026-04-20/Type-Inference-Algorithms.md | 6 +- 01_Archive/2026-04-20/Type-Inference.md | 6 +- 01_Archive/2026-04-20/Type-Intersection.md | 6 +- .../2026-04-20/Type-Narrowing-Mechanisms.md | 6 +- ...ype-Narrowing-and-Control-Flow-Analysis.md | 6 +- .../2026-04-20/Type-Narrowing-and-Guards.md | 6 +- 01_Archive/2026-04-20/Type-Narrowing.md | 6 +- 01_Archive/2026-04-20/Type-Predicates.md | 6 +- 01_Archive/2026-04-20/Type-Safe-API-Design.md | 6 +- ...Type-Safety-and-Exhaustiveness-Checking.md | 6 +- .../Type-Safety-in-Distributed-Systems.md | 6 +- .../Type-Safety-in-Domain-Driven-Design.md | 6 +- .../2026-04-20/Type-Safety-in-Generics.md | 6 +- 01_Archive/2026-04-20/Type-Safety.md | 6 +- 01_Archive/2026-04-20/Type-Soundness.md | 6 +- 01_Archive/2026-04-20/Type-Theory.md | 6 +- 01_Archive/2026-04-20/Type-Unification.md | 6 +- .../2026-04-20/Type-Variance-in-TypeScript.md | 6 +- ...Error Handling Exhaustiveness Checking.md | 10 +- ...rror Handling & Exhaustiveness Checking.md | 6 +- 01_Archive/2026-04-20/TypeScript 4.9.md | 6 +- 01_Archive/2026-04-20/TypeScript 49.md | 10 +- .../2026-04-20/TypeScript API Development.md | 10 +- .../TypeScript Advanced Type System.md | 10 +- .../2026-04-20/TypeScript Compiler (tsc).md | 6 +- .../2026-04-20/TypeScript Compiler API.md | 6 +- ...Script Declaration Files (.d.ts) Design.md | 6 +- ...peScript Declaration Files (dts) Design.md | 6 +- .../2026-04-20/TypeScript Interface Design.md | 6 +- ...peScript Type System (Interface Design).md | 6 +- .../TypeScript Type System Design.md | 6 +- ...eScript Utility Types (Record Readonly).md | 8 +- ...Script Utility Types (Record, Readonly).md | 4 +- .../TypeScript 라이브러리 타입 확장.md | 10 +- ...인터페이스 및 시스템 보호 아키텍처 설계.md | 10 +- .../TypeScript 컴파일러 캐싱 최적화.md | 10 +- ...pt 타입 시스템 (TypeScript Type System).md | 10 +- ...ypeScript 타입 시스템 (인터페이스 설계).md | 6 +- ...peScript 타입 시스템 및 인터페이스 설계.md | 10 +- ... 시스템 아키텍처 및 도메인 기반 설계(DDD).md | 10 +- ...템을 활용한 내부 로직 보호 및 데이터 검증.md | 10 +- .../TypeScript-Advanced-Type-System-Design.md | 6 +- .../TypeScript-Compiler-API-Design.md | 6 +- .../TypeScript-Compiler-API-Integration.md | 6 +- .../2026-04-20/TypeScript-Compiler-API.md | 6 +- .../TypeScript-Compiler-Architecture.md | 6 +- .../TypeScript-Domain-Driven-Design.md | 6 +- .../2026-04-20/TypeScript-Interface-Design.md | 6 +- .../TypeScript-Language-Service-API.md | 6 +- .../2026-04-20/TypeScript-Language-Service.md | 6 +- .../TypeScript-Project-References.md | 6 +- .../TypeScript-Type-System-Architecture.md | 6 +- .../TypeScript-Type-System-Design.md | 6 +- ...TypeScript-Type-System-Interface-Design.md | 6 +- .../2026-04-20/TypeScript-Type-System.md | 6 +- .../TypeScript의 안전한 인터페이스 설계.md | 10 +- ...peScript의 인터페이스 및 객체 타입 설계.md | 10 +- ...ript의 제어 흐름 분석 및 상태 관리 패턴.md | 10 +- 01_Archive/2026-04-20/TypedArray.md | 10 +- .../2026-04-20/UNESCO-Memory-of-the-World.md | 6 +- .../USD - Universal Scene Description.md | 6 +- 01_Archive/2026-04-20/UV Offset.md | 10 +- .../2026-04-20/UX Design Gamification.md | 6 +- .../2026-04-20/UX Design & Gamification.md | 6 +- .../2026-04-20/UX-Design-Architecture.md | 6 +- .../2026-04-20/UX-Design-and-Engagement.md | 6 +- 01_Archive/2026-04-20/UX-Gamification.md | 10 +- .../2026-04-20/UX-Research-Methodologies.md | 6 +- .../2026-04-20/UX_UI in Interactive Media.md | 6 +- .../Ubiquitous Computing Paradigm.md | 6 +- 01_Archive/2026-04-20/Ubiquitous Computing.md | 6 +- 01_Archive/2026-04-20/Ubiquitous-Computing.md | 6 +- .../Ubiquitous-Language-Encoding.md | 6 +- .../2026-04-20/Unified-User-Experience.md | 6 +- 01_Archive/2026-04-20/Union Types.md | 10 +- .../2026-04-20/Union-Types-vs-Overloading.md | 6 +- 01_Archive/2026-04-20/Union-Types.md | 6 +- 01_Archive/2026-04-20/Unity.md | 10 +- .../2026-04-20/Universal-Design-Principles.md | 6 +- .../2026-04-20/Urban Planning Simulation.md | 6 +- .../2026-04-20/Urban Resilience Strategies.md | 6 +- 01_Archive/2026-04-20/Urban-Morphology.md | 6 +- .../2026-04-20/Urban-Planning-Simulations.md | 6 +- 01_Archive/2026-04-20/Urban-Planning.md | 6 +- .../2026-04-20/Urban-Resilience-Planning.md | 6 +- .../2026-04-20/User Experience (UX) Design.md | 6 +- .../User Experience (UX) in Game Design.md | 6 +- .../2026-04-20/User-Experience-Design.md | 6 +- 01_Archive/2026-04-20/User-Story-Mapping.md | 6 +- 01_Archive/2026-04-20/Utility Theory.md | 6 +- 01_Archive/2026-04-20/Utsubo.md | 10 +- .../2026-04-20/V8 Engine Heap Management.md | 10 +- 01_Archive/2026-04-20/V8 Engine.md | 10 +- 01_Archive/2026-04-20/V8 Heap Architecture.md | 10 +- ...ipt Engine 메모리 관리 및 가비지 컬렉션.md | 10 +- 01_Archive/2026-04-20/V8 JavaScript Engine.md | 10 +- 01_Archive/2026-04-20/V8 JavaScript 엔진.md | 10 +- 01_Archive/2026-04-20/V8 Memory Cage.md | 10 +- .../V8 가비지 컬렉션(Garbage Collection).md | 10 +- .../V8 메모리 케이지(V8 Memory Cage).md | 10 +- 01_Archive/2026-04-20/V8 엔진 (V8 Engine).md | 10 +- 01_Archive/2026-04-20/V8 엔진 메모리 구조.md | 10 +- .../V8 엔진 힙 아키텍처 및 로그 분석.md | 10 +- ... 힙 아키텍처(V8 Engine Heap Architecture).md | 10 +- 01_Archive/2026-04-20/V8 엔진 힙 아키텍처.md | 10 +- 01_Archive/2026-04-20/V8 엔진(V8 Engine).md | 10 +- ... 메모리 관리 아키텍처 및 Orinoco 프로젝트.md | 10 +- 01_Archive/2026-04-20/V8 자바스크립트 엔진.md | 8 +- .../2026-04-20/V8 힙 공간(V8 Heap Spaces).md | 10 +- 01_Archive/2026-04-20/V8 힙(Heap).md | 10 +- .../2026-04-20/VIA Institute on Character.md | 6 +- 01_Archive/2026-04-20/VIA-Classification.md | 6 +- 01_Archive/2026-04-20/VPS_NeRF.md | 10 +- 01_Archive/2026-04-20/VR Sickness.md | 10 +- .../2026-04-20/VR 멀미 (VR Sickness).md | 10 +- 01_Archive/2026-04-20/VR 멀미(VR sickness).md | 10 +- .../2026-04-20/VR 엑서게임 (VR Exergaming).md | 10 +- 01_Archive/2026-04-20/Value Object Pattern.md | 6 +- 01_Archive/2026-04-20/Value-Objects.md | 6 +- .../Variable Ratio Reinforcement.md | 6 +- ... (Covariance Contravariance Invariance).md | 6 +- ...Covariance, Contravariance, Invariance).md | 6 +- ...-(Covariance-Contravariance-Invariance).md | 6 +- .../Variance-Covariance-Contravariance.md | 6 +- .../Variance-Covariance-and-Contravariance.md | 6 +- 01_Archive/2026-04-20/Variance-Rules.md | 6 +- .../2026-04-20/Variance-in-TypeScript.md | 6 +- .../2026-04-20/Variational-Autoencoders.md | 6 +- 01_Archive/2026-04-20/Varying Variables.md | 10 +- .../Vergence-Accommodation Conflicts.md | 10 +- 01_Archive/2026-04-20/Vertex Shader.md | 10 +- 01_Archive/2026-04-20/Video Game Design.md | 6 +- .../Virtual Reality (VR) Storytelling.md | 6 +- .../Visual Positioning Systems (VPS).md | 6 +- .../Visual-Hierarchy-in-Game-Design.md | 6 +- .../Von Neumann-Morgenstern Axioms.md | 6 +- .../2026-04-20/Voxel-based Rendering.md | 6 +- 01_Archive/2026-04-20/Vulkan.md | 10 +- .../2026-04-20/W3C-Semantic-Web-Standards.md | 6 +- ...A-Accessible-Rich-Internet-Applications.md | 6 +- 01_Archive/2026-04-20/WEBGL_multi_draw.md | 10 +- 01_Archive/2026-04-20/Wang-Tiles.md | 6 +- .../2026-04-20/Watermarking (AI 워터마킹).md | 6 +- .../Wavefunction-Collapse-Algorithm.md | 6 +- 01_Archive/2026-04-20/Waves of Connection.md | 10 +- 01_Archive/2026-04-20/Wayfinding-Design.md | 6 +- .../Web Performance Optimization.md | 10 +- 01_Archive/2026-04-20/Web Worker (웹 워커).md | 10 +- ...제 고부하 병렬 처리 구현체 (실패_성공 포함).md | 6 +- ...b-Content-Accessibility-Guidelines-WCAG.md | 6 +- 01_Archive/2026-04-20/Web3 Infrastructure.md | 6 +- 01_Archive/2026-04-20/WebAssembly.md | 10 +- 01_Archive/2026-04-20/WebGL 2.0.md | 6 +- 01_Archive/2026-04-20/WebGL 20.md | 10 +- 01_Archive/2026-04-20/WebGL API.md | 10 +- 01_Archive/2026-04-20/WebGL Optimization.md | 10 +- .../2026-04-20/WebGL 모바일 GPU 성능 관리.md | 10 +- 01_Archive/2026-04-20/WebGL.md | 10 +- 01_Archive/2026-04-20/WebGL2.md | 10 +- .../2026-04-20/WebGLRenderingContext.md | 10 +- .../2026-04-20/WebGPU Compute Shader.md | 10 +- .../2026-04-20/WebGPU Compute Shaders.md | 10 +- .../WebGPU Performance Profiling.md | 10 +- .../2026-04-20/WebGPU Timestamp Queries.md | 10 +- .../WebGPU _ WebGL Timing API Security.md | 10 +- .../2026-04-20/WebGPU 대규모 건설 뷰어.md | 10 +- 01_Archive/2026-04-20/WebGPU.md | 10 +- .../2026-04-20/WebKit Security Mitigations.md | 10 +- 01_Archive/2026-04-20/WebKit.md | 10 +- .../WebSplatter (3D Gaussian Splatting).md | 10 +- 01_Archive/2026-04-20/Wellbeing-Science.md | 6 +- 01_Archive/2026-04-20/Wicked-Problems.md | 6 +- 01_Archive/2026-04-20/Width-Subtyping.md | 6 +- .../2026-04-20/Width-and-Depth-Subtyping.md | 6 +- 01_Archive/2026-04-20/Wikidata.md | 6 +- ...inning Ways for your Mathematical Plays.md | 6 +- 01_Archive/2026-04-20/Wonderland Engine.md | 10 +- .../2026-04-20/Work-Engagement-Models.md | 6 +- ...World of Warcraft (Gold Sink Mechanics).md | 6 +- 01_Archive/2026-04-20/Write Barrier.md | 10 +- 01_Archive/2026-04-20/XState-Library.md | 6 +- .../2026-04-20/Zod 런타임 유효성 검사 통합.md | 10 +- ... 브랜디드 타입을 결합한 런타임 데이터 검증.md | 8 +- .../2026-04-20/Zod-Runtime-Validation.md | 6 +- .../2026-04-20/Zod-Schema-Validation.md | 6 +- 01_Archive/2026-04-20/Zod.md | 10 +- .../Zod를 활용한 런타임 데이터 파싱.md | 10 +- .../Zustand-Based-Mission-Persistence.md | 10 +- 01_Archive/2026-04-20/[[Cluster A | 0 01_Archive/2026-04-20/[[Cluster E | 0 ...리_ - 관심사의 분리 (Separation of Concerns).md | 10 +- .../agargaro의 오픈 소스 라이브러리.md | 10 +- 01_Archive/2026-04-20/as const Assertion.md | 10 +- 01_Archive/2026-04-20/as const.md | 10 +- ...ffer를 결합한 멀티스레드 고성능 아키텍처.md | 10 +- ...CS와 SharedArrayBuffer의 실제 코드 통합.md | 10 +- 01_Archive/2026-04-20/clinic.js.md | 6 +- 01_Archive/2026-04-20/clinicjs.md | 10 +- .../eSports Performance Psychology.md | 6 +- .../2026-04-20/eslint-config-prettier.md | 10 +- .../2026-04-20/eslint-plugin-prettier.md | 10 +- .../e스포츠 인지 상태 및 성과 위험 평가.md | 8 +- 01_Archive/2026-04-20/instancedArray.md | 10 +- 01_Archive/2026-04-20/lint-staged.md | 10 +- .../2026-04-20/never 타입(never type).md | 10 +- 01_Archive/2026-04-20/never 타입.md | 10 +- 01_Archive/2026-04-20/readonly 수식어.md | 10 +- 01_Archive/2026-04-20/readonly.md | 10 +- 01_Archive/2026-04-20/satisfies Keyword.md | 10 +- 01_Archive/2026-04-20/satisfies 연산자.md | 10 +- 01_Archive/2026-04-20/three-mesh-bvh.md | 10 +- .../2026-04-20/three.js Issue _30352.md | 6 +- 01_Archive/2026-04-20/threejs Issue _30352.md | 10 +- 01_Archive/2026-04-20/ts-brand.md | 10 +- 01_Archive/2026-04-20/ts-pattern.md | 10 +- .../2026-04-20/useEffect 클린업(Cleanup).md | 10 +- .../가비지 컬렉션 (Garbage Collection).md | 10 +- .../가비지 컬렉션(Garbage Collection).md | 10 +- .../가비지 컬렉터(Garbage Collector).md | 10 +- .../2026-04-20/가상 DOM (Virtual DOM).md | 10 +- .../2026-04-20/가상현실 멀미 (VR Sickness).md | 10 +- .../2026-04-20/가상현실 멀미(VR Sickness).md | 10 +- ...효과 연구(Virtual Reality Aftereffects Study).md | 10 +- ... 후유증 연구(VR Exergaming Aftereffects Study).md | 10 +- ...(Virtual reality exergaming aftereffects research).md | 10 +- ...상현실 엑서게임(Exergaming) 후유증 연구.md | 10 +- ...실 후유증 (Virtual Reality Aftereffects).md | 10 +- .../가상현실 후유증(VR Aftereffects).md | 10 +- ...게임 인지 사후 효과 분석(CANTAB 5-choice RTI).md | 10 +- .../가상현실(VR) 자전거 시뮬레이터.md | 10 +- 01_Archive/2026-04-20/가상현실(VR).md | 10 +- .../2026-04-20/가상화 (Virtualization).md | 6 +- .../감각 통합(Sensory integration).md | 10 +- 01_Archive/2026-04-20/강화 계획.md | 6 +- ...화 학습(Reinforcement Learning) 알고리즘.md | 6 +- .../강화학습 (Reinforcement Learning).md | 6 +- 01_Archive/2026-04-20/개발자 경험(DX).md | 10 +- .../객체 지향 소프트웨어 아키텍처 설계.md | 10 +- .../2026-04-20/객체 지향 프로그래밍 (OOP).md | 10 +- ... 프로그래밍 (Object-Oriented Programming).md | 10 +- .../2026-04-20/객체 지향 프로그래밍(OOP).md | 8 +- 01_Archive/2026-04-20/건강 심리학.md | 6 +- 01_Archive/2026-04-20/건강 행동 변화 모델.md | 6 +- .../2026-04-20/게임 디자인 이론 및 구조론.md | 6 +- ...임 디자인의 보상 루프(Reward Loop) 설계.md | 6 +- 01_Archive/2026-04-20/게임 루프 설계.md | 6 +- 01_Archive/2026-04-20/게임 행동 심리학.md | 6 +- ...학(Ludology) vs 서사학(Narratology) 논쟁.md | 6 +- .../견고한 도메인 모델 및 API 계약 설계.md | 10 +- .../2026-04-20/결정 속도(Decision Speed).md | 10 +- 01_Archive/2026-04-20/결합도 (Coupling).md | 10 +- .../2026-04-20/경고 피로 (Alert Fatigue).md | 10 +- .../계층형 아키텍처 (Layered Architecture).md | 10 +- .../계층화 아키텍처 (Layered Architecture).md | 10 +- .../고성능 3D WebGL 게임 렌더링 엔진.md | 6 +- .../고성능 멀티스레드 React 앱 아키텍처.md | 10 +- ...용 시스템을 위한 React 기반 게임 엔진 아키텍처.md | 6 +- 01_Archive/2026-04-20/고전적 조건 형성.md | 6 +- .../공급망 공격 (Supply Chain Attack).md | 10 +- .../2026-04-20/공존 질환 (Comorbidity).md | 6 +- ...잉 속성 체크 (Excess Property Checking).md | 10 +- 01_Archive/2026-04-20/과잉 속성 체크(EPC).md | 10 +- ...잉 속성 체크(Excess Property Checking).md | 10 +- ... 정당화 효과 (Overjustification Effect).md | 6 +- ...심사의 분리 (Separation of Concerns SoC).md | 10 +- .../관심사의 분리 (Separation of Concerns).md | 10 +- ...사의 분리 (Separation of Concerns, SoC).md | 6 +- 01_Archive/2026-04-20/관심사의 분리 (SoC).md | 10 +- .../관심사의 분리(Separation of Concerns).md | 10 +- 01_Archive/2026-04-20/관심사의 분리(SoC).md | 10 +- .../2026-04-20/관점 지향 프로그래밍 (AOP).md | 6 +- .../2026-04-20/관점 지향 프로그래밍(AOP).md | 10 +- .../광범위한 신경과학적 연합 기제.md | 6 +- .../2026-04-20/교육 심리학 및 교수법 설계.md | 6 +- .../2026-04-20/교육 심리학에서의 보상 설계.md | 6 +- .../교육 심리학에서의 학습 동기 유도.md | 6 +- .../교육 심리학에서의 학습 동기 유발.md | 6 +- 01_Archive/2026-04-20/교육학의 모델링 전략.md | 6 +- .../교집합 타입 (Intersection Types).md | 10 +- .../교집합 타입(Intersection Type).md | 10 +- .../구조적 타이핑 (Structural Typing).md | 10 +- .../구조적 타이핑(Structural Typing).md | 10 +- 01_Archive/2026-04-20/구조적 타이핑.md | 10 +- ...본 타입에의 집착 (Primitive Obsession).md | 10 +- ...기본 타입에의 집착(Primitive Obsession).md | 10 +- .../2026-04-20/기업 문화 진단 및 개선.md | 6 +- .../깊이 지각 (Depth Perception).md | 10 +- .../2026-04-20/깊이 지각(Depth perception).md | 10 +- .../내재적 동기 (Intrinsic Motivation).md | 6 +- .../2026-04-20/내재적 동기 vs 외재적 동기.md | 6 +- .../2026-04-20/네버 타입 (never type).md | 10 +- ...릭스 (Netflix) 마이크로서비스 도입 사례.md | 10 +- ...딩 파이프라인 (Netflix Video Encoding Pipeline).md | 10 +- ... 코스모스 플랫폼 (Netflix Cosmos Platform).md | 10 +- ...플릭스 코스모스 플랫폼 (Netflix Cosmos).md | 10 +- ...x)의 마이크로서비스 및 코스모스 플랫폼 전환.md | 10 +- ...의 코스모스 플랫폼 및 마이크로서비스 전환.md | 10 +- .../2026-04-20/뇌 가소성 (Neuroplasticity).md | 6 +- .../뇌과학 기반 중독 재활 프로그램.md | 6 +- ...절 충돌(Vergence-accommodation conflicts).md | 10 +- .../느슨한 결합 (Loose Coupling).md | 10 +- 01_Archive/2026-04-20/단일 책임 원칙 (SRP).md | 10 +- ...임 원칙 (Single Responsibility Principle).md | 10 +- 01_Archive/2026-04-20/단일 책임 원칙(SRP).md | 10 +- .../대규모 3D 건축 모델(BIM) 시각화.md | 10 +- .../대규모 React 프론트엔드 최적화.md | 6 +- ...모 TypeScript 애플리케이션 아키텍처 설계.md | 10 +- ... TypeScript 프로젝트의 컴파일 성능 최적화.md | 10 +- .../대규모 건설 뷰어(Construction Viewers).md | 10 +- .../대규모 건축물 및 지형 뷰어(BIM).md | 10 +- .../대규모 데이터 렌더링 및 가상화 최적화.md | 10 +- .../대규모 로그 뷰어 및 데이터 테이블 구현.md | 6 +- ...포(Turborepo) 환경에서의 린트 오케스트레이션.md | 10 +- .../2026-04-20/대규모 애플리케이션 개발.md | 10 +- .../2026-04-20/대규모 웹 그래픽스 프로젝트.md | 10 +- ... 애플리케이션의 조직 및 기술적 확장성 확보.md | 10 +- .../대규모 인스턴스 렌더링 및 투명도 처리.md | 10 +- .../2026-04-20/대규모 파티클 시스템 최적화.md | 10 +- ...규모 프론트엔드 웹 프로젝트 폴더 구조화.md | 10 +- .../2026-04-20/덕 타이핑 (Duck Typing).md | 10 +- .../2026-04-20/덕 타이핑(Duck Typing).md | 10 +- ... (DevSecOps) 환경에서의 지속적인 보안 검사.md | 10 +- .../데이터 거버넌스 (Data Governance).md | 10 +- ...데이터 지향 설계 (Data-Oriented Design).md | 6 +- ...달 가능성 분석 (Reachability Analysis).md | 10 +- ...메인 기반 설계 (DDD) 및 데이터 오염 방지.md | 10 +- .../2026-04-20/도메인 기반 설계 (DDD).md | 10 +- .../2026-04-20/도메인 기반 설계(DDD).md | 8 +- .../도메인 기반 설계(DDD)의 데이터 검증.md | 10 +- .../도메인 기반 설계(DDD)의 식별자 분리.md | 10 +- .../2026-04-20/도메인 주도 설계 (DDD).md | 10 +- ...인 주도 설계 (Domain-Driven Design DDD).md | 10 +- ...인 주도 설계 (Domain-Driven Design, DDD).md | 6 +- .../2026-04-20/도메인 주도 설계(DDD).md | 10 +- ...민 보상 체계 (Dopaminergic Reward System).md | 6 +- 01_Archive/2026-04-20/도파민 보상 체계.md | 6 +- ...기강화 상담(Motivational Interviewing).md | 6 +- ...진적 마킹(Concurrent Incremental Marking).md | 10 +- ...진적 마킹(Concurrent & Incremental Marking).md | 6 +- .../2026-04-20/동작 속도(Movement Speed).md | 10 +- .../동적 애플리케이션 보안 테스트(DAST).md | 10 +- .../디자인 시스템 (Design Systems).md | 6 +- .../디지털 미학(Digital Aesthetics).md | 6 +- .../라이브러리 및 확장 가능한 코드베이스.md | 10 +- .../라이브러리 타입 선언 (d.ts) 확장.md | 6 +- .../라이브러리 타입 선언 (dts) 확장.md | 10 +- .../런타임 상태 검증(Runtime Validation).md | 8 +- ...내러티브 부조화(Ludonarrative Dissonance).md | 6 +- 01_Archive/2026-04-20/리로디드(Reloaded).md | 10 +- .../2026-04-20/리터럴 타입 (Literal Types).md | 10 +- 01_Archive/2026-04-20/린터 (Linter).md | 10 +- .../마이너 가비지 컬렉션(Minor GC).md | 10 +- .../마이크로 프론트엔드 (Micro Frontends).md | 10 +- 01_Archive/2026-04-20/마이크로 프론트엔드.md | 10 +- .../마이크로서비스 아키텍처 (MSA).md | 10 +- ...비스 아키텍처 (Microservices Architecture).md | 10 +- .../2026-04-20/마이크로서비스 아키텍처.md | 10 +- .../2026-04-20/마크-스위프(Mark-Sweep).md | 10 +- .../마크-스위프-컴팩트(Mark-Sweep-Compact).md | 10 +- .../2026-04-20/마크-스윕(Mark-Sweep).md | 10 +- .../2026-04-20/마크-컴팩트(Mark-Compact).md | 10 +- .../2026-04-20/만성 질환 행동 수정 개입.md | 6 +- .../2026-04-20/맞춤형 개별화 학습 설계.md | 6 +- ... 디스플레이(HMD) 환경의 시각적 후유증 연구.md | 10 +- .../머리 착용 디스플레이(HMD) 시각 연구.md | 10 +- .../2026-04-20/메모리 누수(Memory Leak).md | 10 +- .../2026-04-20/메모리 누수(Memory Leaks).md | 10 +- .../메모리 단편화(Fragmentation).md | 10 +- ... 파편화 방지 및 객체 풀링 (Object Pooling).md | 6 +- ...령형 직접 조작 (Imperative Manipulation).md | 6 +- .../명목적 타이핑 (Nominal Typing).md | 10 +- .../명목적 타이핑(Nominal Typing).md | 10 +- .../모노레포(Monorepo) 기반 구성 중앙화.md | 10 +- .../모노레포(Monorepo) 설정 중앙화.md | 10 +- .../모노레포(Monorepo) 아키텍처 설정.md | 10 +- ...리식 아키텍처 (Monolithic Architecture).md | 10 +- .../2026-04-20/모듈러 통합 건설 (MiC).md | 10 +- .../모듈화 및 아키텍처 경계 설정.md | 10 +- .../모바일 기반 WebGL 애플리케이션 개발.md | 10 +- .../모바일 앱 및 웹 인터페이스 설계.md | 6 +- 01_Archive/2026-04-20/몰입 (Flow Theory).md | 6 +- 01_Archive/2026-04-20/몰입감 (Presence).md | 10 +- 01_Archive/2026-04-20/무제.md | 6 +- .../2026-04-20/미디어 폭력과 공격성 연구.md | 6 +- .../바운디드 컨텍스트 (Bounded Context).md | 8 +- .../2026-04-20/반응 시간(Reaction Time).md | 10 +- ...응형 윈도우 리사이즈(Resize) 이벤트 처리.md | 10 +- ...(Data Transformation between Backend and Frontend).md | 10 +- .../2026-04-20/번아웃 및 직무 스트레스.md | 6 +- .../범이론적 모델(Transtheoretical Model).md | 6 +- .../벡터 데이터베이스 (Vector Database).md | 6 +- ...상 예측 오류 (Reward Prediction Error).md | 6 +- ...상의 역효과 (Overjustification Effect).md | 6 +- .../보조 공학 (Assistive Technology).md | 6 +- .../2026-04-20/보존 경로(Retaining Path).md | 10 +- .../보편적 언어 (Ubiquitous Language).md | 10 +- ...즈니스 도메인 (금융 헬스케어 이커머스 등).md | 10 +- ...즈니스 도메인 (금융, 헬스케어, 이커머스 등).md | 6 +- .../2026-04-20/불변성 (Immutability).md | 10 +- 01_Archive/2026-04-20/불변성(Immutability).md | 10 +- .../2026-04-20/불필요한 리렌더링 방지.md | 10 +- ...브라우저 DOM 누수 탐지 및 렌더링 최적화.md | 10 +- .../브라우저 그래픽 렌더링 백엔드.md | 10 +- .../브라우저 메모리 관리 및 최적화.md | 10 +- ...리 누수 탐지(Browser Memory Leak Detection).md | 10 +- ... 메모리 할당 시점별 힙(Heap) 동작 상세 로그.md | 10 +- .../브라우저 및 Node.js 메모리 튜닝.md | 6 +- .../브라우저 및 Nodejs 메모리 튜닝.md | 10 +- .../브랜디드 타입 (Branded Types).md | 10 +- .../브랜디드 타입(Branded Types).md | 10 +- 01_Archive/2026-04-20/브랜디드 타입.md | 10 +- ...기 데이터 패칭 (Async Operations Pattern).md | 10 +- ... 도메인 모델링 (Business Domain Modeling).md | 10 +- ... 후유증 평가(Beat Saber Exergaming Aftereffects).md | 10 +- ...트 세이버(Beat Saber) VR 엑서게임 연구.md | 10 +- .../비트 세이버(Beat Saber) 실험.md | 10 +- .../비트 세이버(Beat Saber) 엑서게임 연구.md | 10 +- .../2026-04-20/비트 세이버(Beat Saber).md | 10 +- ...Beat Saber_ An Investigation of Virtual Reality Aftereffects).md | 10 +- .../빌보드 임포스터(Billboard Impostors).md | 10 +- .../사용성 공학 (Usability Engineering).md | 6 +- .../2026-04-20/사용자 경험 (UX) 디자인.md | 6 +- 01_Archive/2026-04-20/사용자 경험 (UX).md | 6 +- .../사용자 경험 디자인 (UX Design).md | 6 +- ...사회 인지 이론(Social Cognitive Theory).md | 6 +- 01_Archive/2026-04-20/사회 학습 이론.md | 6 +- 01_Archive/2026-04-20/사회학습이론.md | 6 +- ...링(State Management and API Response Modeling).md | 10 +- ...상태 관리 최적화 (Zustand Jotai Valtio).md | 10 +- .../상태 관리 최적화 (Zustand Valtio).md | 6 +- ...태 관리 최적화 (Zustand, Jotai, Valtio).md | 6 +- .../상태 관리 최적화 (Zustand, Valtio).md | 6 +- .../2026-04-20/상태 관리(State Management).md | 10 +- ...e Machine) 모델링 및 Redux 액션_리듀서 설계.md | 10 +- .../상태 머신(State Machine) 설계.md | 10 +- .../상태 모델링 (State Modeling).md | 10 +- .../2026-04-20/새로운 공간(New Space).md | 10 +- 01_Archive/2026-04-20/생물학적 학습 이론.md | 6 +- .../서드파티 라이브러리 및 API 연동.md | 10 +- .../서버리스 컴퓨팅(Serverless Computing).md | 10 +- .../서비스 디자인 (Service Design).md | 6 +- ...플라이 체인 보안 (Supply Chain Security).md | 10 +- .../선언 병합 (Declaration Merging).md | 10 +- .../선언 병합(Declaration Merging).md | 10 +- 01_Archive/2026-04-20/선언 파일(.d.ts).md | 4 +- 01_Archive/2026-04-20/선언 파일(dts).md | 8 +- ...블 설계(Configuration Objects and Lookup Tables).md | 10 +- .../성장 마인드셋 (Growth Mindset).md | 6 +- .../성장 마인드셋(Growth Mindset).md | 6 +- .../세대 가설(Generational Hypothesis).md | 10 +- .../세대별 가설(Generational Hypothesis).md | 10 +- .../셰이더 정밀도 (Mediump_Highp).md | 10 +- .../소프트웨어 개발 수명 주기 (SDLC).md | 10 +- .../2026-04-20/소프트웨어 구성 분석(SCA).md | 10 +- ...소프트웨어 시스템 설계 및 아키텍처 구축.md | 10 +- .../소프트웨어 아키텍처 베스트 프랙티스.md | 10 +- .../2026-04-20/소프트웨어 아키텍처 설계.md | 10 +- .../수동 코드 리뷰 (Manual Code Review).md | 10 +- 01_Archive/2026-04-20/수동 코드 리뷰.md | 10 +- ...절 불일치(Vergence-Accommodation Conflict).md | 10 +- .../2026-04-20/순차적 게이트 아키텍처.md | 6 +- .../스캐빈저(Scavenger) _ 마이너 GC.md | 10 +- 01_Archive/2026-04-20/스캐빈저(Scavenger).md | 10 +- .../2026-04-20/스택 트레이스(Stack trace).md | 10 +- .../스토리지 텍스처(Storage Textures).md | 10 +- ...랭글러 피그 패턴(Strangler Fig Pattern).md | 10 +- .../스파게티 코드 (Spaghetti Code).md | 8 +- ...티파이 자율적 분대 모델 (Spotify Squad).md | 8 +- ...크로 프론트엔드 (Spotify Squads and Micro Frontends).md | 10 +- .../2026-04-20/스포티파이 자율적 분대 모델.md | 10 +- ...y)의 스쿼드 모델 및 마이크로 프론트엔드 도입.md | 10 +- 01_Archive/2026-04-20/습관 교정 프로그램.md | 6 +- .../2026-04-20/시각 및 인지적 후유증 연구.md | 10 +- ...-전정 갈등 (Visual-Vestibular Conflict).md | 10 +- ...정 감각 충돌(Visual-Vestibular Conflict).md | 10 +- ...각-전정 충돌(Visual-vestibular conflict).md | 10 +- .../2026-04-20/시맨틱 웹 (Semantic Web).md | 6 +- .../2026-04-20/시뮬레이터 멀미 설문지(SSQ).md | 10 +- ...미 설문지(Simulator Sickness Questionnaire).md | 10 +- .../시스템 다이내믹스 (System Dynamics).md | 6 +- .../2026-04-20/시프트 레프트 (Shift-Left).md | 10 +- .../2026-04-20/시프트 레프트(Shift-Left).md | 8 +- ...별 가능한 유니온 (Discriminated Unions).md | 10 +- ...별 가능한 유니온(Discriminated Unions).md | 10 +- 01_Archive/2026-04-20/식별 가능한 유니온.md | 10 +- .../신경 가소성 (Neuroplasticity).md | 6 +- ...간 데이터 대시보드 레이아웃 조절 시스템.md | 10 +- .../2026-04-20/실시간 렌더링 파이프라인.md | 10 +- .../실시간 물리 및 유체 시뮬레이션.md | 10 +- .../실시간 물리 시뮬레이션 동기화.md | 6 +- 01_Archive/2026-04-20/실재감(Presence).md | 10 +- .../심리적 계약 (Psychological Contract).md | 6 +- .../심리적 안전감 (Psychological Safety).md | 6 +- .../2026-04-20/쓰기 장벽(Write Barrier).md | 10 +- 01_Archive/2026-04-20/아보(Bobo) 인형 실험.md | 6 +- .../안구 운동 기능 (Oculomotor Functions).md | 10 +- .../안구 운동 기능(Oculomotor functions).md | 10 +- .../안구 운동 증상(Oculomotor Symptoms).md | 10 +- ...TypeScript 데이터 모델링 및 설정 관리 구축.md | 10 +- .../안전한 소프트웨어 개발 수명주기(SSDLC).md | 10 +- ...수 없는 외부 데이터 검증 (unknown types).md | 8 +- .../2026-04-20/애그리거트 (Aggregates).md | 10 +- .../애자일 방법론 (Agile Methodology).md | 6 +- .../약한 타입 검사(Weak Type Detection).md | 10 +- .../약한 타입 탐지 (Weak Type Detection).md | 10 +- .../2026-04-20/양가감정(Ambivalence).md | 6 +- .../2026-04-20/양자화 (Quantization).md | 6 +- .../에듀테크 기반 게이미피케이션 전략.md | 6 +- .../에르고딕 문학(Ergodic Literature).md | 6 +- .../2026-04-20/에일리어싱 (Aliasing).md | 10 +- 01_Archive/2026-04-20/엑서게임(Exergaming).md | 10 +- .../엔터프라이즈 소프트웨어 개발.md | 10 +- .../엔터프라이즈 소프트웨어 시스템 설계.md | 10 +- ...프라이즈 애플리케이션 및 점진적 리팩토링.md | 10 +- .../엔터프라이즈 애플리케이션 설계.md | 10 +- 01_Archive/2026-04-20/엔티티 (Entities).md | 10 +- .../연합 학습 (Associative Learning).md | 6 +- .../2026-04-20/오래된 공간(Old Space).md | 10 +- 01_Archive/2026-04-20/오리노코(Orinoco GC).md | 10 +- .../2026-04-20/오리노코(Orinoco) 프로젝트.md | 10 +- 01_Archive/2026-04-20/오버드로우(Overdraw).md | 10 +- ...5 호쿠사이 인스톨레이션(Hokusai installation).md | 10 +- .../2026-04-20/오탐 (False Positive).md | 10 +- ...픈소스 컴포넌트 (Open Source Components).md | 10 +- 01_Archive/2026-04-20/온톨로지 (Ontology).md | 6 +- 01_Archive/2026-04-20/온톨로지 지식 베이스.md | 6 +- .../완전성 검사 (Exhaustiveness Checking).md | 10 +- .../완전성 검사(Exhaustiveness Checking).md | 10 +- .../외부 API 데이터 및 설정 파일 처리.md | 10 +- .../외부 API 데이터의 런타임 검증 후 처리.md | 10 +- .../2026-04-20/외부 라이브러리 API 설계.md | 10 +- .../웹 브라우저 그래픽 API 호환성.md | 10 +- .../웹 애플리케이션의 3계층 구조.md | 10 +- .../웹 워커 이벤트 포워딩 Event Forwarding.md | 10 +- ...워커 이벤트 포워딩 통신 지연 최소화 방법.md | 10 +- .../2026-04-20/웹 프론트엔드 성능 최적화.md | 10 +- ... 통합 이론 (Organismic Integration Theory).md | 6 +- .../2026-04-20/유능감 및 자율성 욕구.md | 6 +- .../유니언 타입 식별 및 상태 분기 처리.md | 10 +- .../2026-04-20/유니온 타입 (Union Types).md | 10 +- .../2026-04-20/유니온 타입(Union Types).md | 10 +- .../유비쿼터스 언어 (Ubiquitous Language).md | 12 +- .../2026-04-20/유스케이스 (Use Cases).md | 10 +- ...)] [행동 경제학] [교육 심리학의 행동주의 모델.md | 6 +- ..., [행동 경제학], [교육 심리학의 행동주의 모델.md | 6 +- 01_Archive/2026-04-20/응집도 (Cohesion).md | 10 +- ...응집도와 결합도 (Cohesion and Coupling).md | 10 +- 01_Archive/2026-04-20/응집도와 결합도.md | 10 +- .../의사결정 속도(Decision Speed).md | 10 +- .../의존성 규칙 (Dependency Rule).md | 10 +- .../의존성 역전 (Dependency Inversion).md | 10 +- .../2026-04-20/의존성 역전 원칙 (DIP).md | 10 +- ... 원칙 (Dependency Inversion Principle DIP).md | 10 +- ...역전 원칙 (Dependency Inversion Principle).md | 12 +- ... 원칙 (Dependency Inversion Principle, DIP).md | 6 +- 01_Archive/2026-04-20/의존성 주입 (DI).md | 10 +- .../의존성 주입 (Dependency Injection).md | 10 +- 01_Archive/2026-04-20/의존성 주입(DI).md | 10 +- .../2026-04-20/이동 속도(Movement Speed).md | 10 +- ... 기반 아키텍처 (Event-Driven Architecture).md | 10 +- .../이벤트 포워딩(Event Forwarding).md | 6 +- .../이전 세대(Old Generation_Space).md | 10 +- .../2026-04-20/이커머스의 실시간 재고 관리.md | 8 +- ...간 요인 공학 (Human Factors Engineering).md | 6 +- .../2026-04-20/인간-컴퓨터 상호작용 (HCI).md | 6 +- .../2026-04-20/인공지능 상호작용 (HAI).md | 6 +- .../인문학적 게임 비평 및 서사학.md | 6 +- .../인문학적 게임 비평 및 서사학12.md | 6 +- .../인적 자원 관리(HRM) 전략 수립.md | 6 +- 01_Archive/2026-04-20/인지 부조화 이론.md | 6 +- .../인지 부하 이론(Cognitive Load Theory).md | 6 +- .../인지 심리학 (Cognitive Psychology).md | 6 +- ... 평가 이론 (Cognitive Evaluation Theory).md | 6 +- 01_Archive/2026-04-20/인지 행동 치료 (CBT).md | 6 +- 01_Archive/2026-04-20/인지행동치료(CBT).md | 6 +- .../2026-04-20/인터랙티브 스토리텔링 연구.md | 6 +- .../2026-04-20/인터페이스 (Interface).md | 10 +- ... 분리 원칙 (Interface Segregation Principle).md | 10 +- 01_Archive/2026-04-20/임베딩 (Embedding).md | 6 +- .../임상 심리학의 변화 동기 치료.md | 6 +- .../입자 시스템(Particle Systems).md | 10 +- .../2026-04-20/자기 효능감 (Self-Efficacy).md | 6 +- .../2026-04-20/자기 효능감(Self-Efficacy).md | 6 +- .../2026-04-20/자기결정성 이론 (SDT).md | 6 +- ...결정성 이론 (Self-Determination Theory).md | 6 +- .../자기조절학습(Self-Regulated Learning).md | 6 +- 01_Archive/2026-04-20/자동화된 코드 리뷰.md | 10 +- 01_Archive/2026-04-20/자바 가상 머신(JVM).md | 10 +- .../자율성 지지 (Autonomy Support).md | 6 +- .../자폐 스펙트럼 장애(ASD) 중재.md | 6 +- ... 실행되는 실시간 데이터 대시보드 최적화.md | 6 +- .../재귀적 불변성 (DeepReadonly).md | 10 +- .../2026-04-20/재조정 (Reconciliation).md | 10 +- .../전두엽 기능 저하 (Hypofrontality).md | 6 +- .../절차적 수사학(Procedural Rhetoric).md | 6 +- .../점진적 마킹(Incremental marking).md | 10 +- ... 조건 형성 (Emotional Classical Conditioning).md | 6 +- .../정신 의학적 진단 체계 (DSM-5_ICD-11).md | 6 +- .../2026-04-20/정적 분석(Static Analysis).md | 10 +- .../정적 애플리케이션 보안 테스트 (SAST).md | 10 +- .../정적 애플리케이션 보안 테스트(SAST).md | 10 +- .../제어 흐름 분석 (Control Flow Analysis).md | 10 +- ...조작적 조건 형성 (Operant Conditioning).md | 6 +- 01_Archive/2026-04-20/조작적 조건 형성.md | 6 +- 01_Archive/2026-04-20/조작적 조건형성.md | 6 +- ... 불일치 (Vergence-Accommodation Conflict).md | 10 +- ...주 불일치(Vergence-Accommodation Conflict).md | 10 +- .../2026-04-20/조직 개발(OD) 프로그램 설계.md | 6 +- 01_Archive/2026-04-20/조직 시민 행동 (OCB).md | 6 +- 01_Archive/2026-04-20/조직 행동 관리(OBM).md | 6 +- .../조직 행동론 및 직무 만족도 연구.md | 6 +- .../조직 행동론의 성과급 체계 분석.md | 6 +- .../조직 행동론의 직무 몰입 연구.md | 6 +- .../중뇌-변연계 경로 (Mesolimbic Pathway).md | 6 +- .../2026-04-20/중독 의학 및 정신 병리학.md | 6 +- 01_Archive/2026-04-20/중독 재활 프로그램.md | 6 +- .../지식 그래프 (Knowledge Graph).md | 6 +- .../지식 베이스 (Knowledge Base).md | 6 +- .../직렬화(Serialization) 및 병목 현상.md | 6 +- ...무 특성 모델 (Job Characteristics Model).md | 6 +- 01_Archive/2026-04-20/집합론 (Set Theory).md | 10 +- 01_Archive/2026-04-20/집합론(Set Theory).md | 10 +- .../창발 능력 (Emergent Abilities).md | 6 +- .../철벽 수비대 인터페이스 설계 전략.md | 10 +- ..._ - TypeScript 타입 시스템 (인터페이스 설계).md | 10 +- ... 타입 시스템과 견고한 인터페이스 설계의 정수.md | 10 +- ...과 속성 검사 (Excess Property Checking).md | 10 +- ...초과 속성 검사 (Excess Property Checks).md | 10 +- .../추론 엔진 (Semantic Reasoner).md | 6 +- 01_Archive/2026-04-20/추상 구문 트리(AST).md | 10 +- 01_Archive/2026-04-20/추상화(Abstraction).md | 10 +- 01_Archive/2026-04-20/추상화.md | 10 +- .../2026-04-20/치타 사람 이미지 프롬프트.md | 10 +- 01_Archive/2026-04-20/카산드라(Cassandra).md | 10 +- .../2026-04-20/카오스 몽키(Chaos Monkey).md | 10 +- .../커뮤니티 탐지 (Community Detection).md | 6 +- ...포넌트 기반 웹 프레임워크 아키텍처 설계.md | 10 +- .../컴퓨트 셰이더(Compute Shaders).md | 10 +- .../2026-04-20/코드 리뷰 (Code Review).md | 10 +- .../2026-04-20/코드 리뷰(Code Review).md | 10 +- ...자 인식)에 미치는 영향을 평가하는 기계 학습 모델 분류 연구.md | 10 +- .../코드 스타일로메트리 (Code Stylometry).md | 10 +- .../코드 축소 (Code minification).md | 10 +- .../코드 포매팅 (Code formatting).md | 10 +- ...동화 (Code Quality Management and Automation).md | 8 +- 01_Archive/2026-04-20/코스모스(Cosmos).md | 10 +- 01_Archive/2026-04-20/클로저(Closures).md | 10 +- .../클린 아키텍처 (Clean Architecture).md | 10 +- .../클린 아키텍처(Clean Architecture).md | 10 +- 01_Archive/2026-04-20/클린 아키텍처.md | 10 +- ... 계측(Allocation instrumentation on timeline).md | 10 +- .../2026-04-20/타입 가드 (Type Guards).md | 10 +- .../2026-04-20/타입 가드 (Type Predicates).md | 10 +- .../2026-04-20/타입 가드(Type Guards).md | 10 +- .../2026-04-20/타입 단언 (Type Assertions).md | 10 +- .../2026-04-20/타입 단언(Type Assertion).md | 10 +- .../2026-04-20/타입 단언(Type Assertions).md | 10 +- .../2026-04-20/타입 별칭 (Type Alias).md | 10 +- .../타입 서술어 (Type Predicates).md | 8 +- .../타입 서술어(Type Predicates).md | 10 +- .../2026-04-20/타입 안전성 (Type Safety).md | 10 +- ... 정의가 부족한 서드파티 라이브러리 연동.md | 10 +- .../타입 조건자(Type Predicates).md | 10 +- .../타입 좁히기 (Type Narrowing).md | 10 +- .../2026-04-20/타입 좁히기(Type Narrowing).md | 10 +- .../2026-04-20/타입 캐스팅 (Type Casting).md | 8 +- ...입스크립트 상태 관리 및 분기 처리 설계.md | 10 +- 01_Archive/2026-04-20/타파스(Tapas).md | 10 +- .../2026-04-20/테스트 용이성 (Testability).md | 10 +- .../토스(Toss) Front SDK 퍼사드 패턴 적용.md | 10 +- 01_Archive/2026-04-20/토스(Toss) SDK 설계.md | 10 +- ...플레이스 결제 단말기 외부 연동 SDK 개발.md | 10 +- .../팀 단위 코드 품질 및 컨벤션 유지.md | 10 +- .../포인터 압축(Pointer Compression).md | 10 +- ...절 갈등 (Vergence-Accommodation Conflict).md | 10 +- ... 불일치(Vergence-Accommodation Conflicts).md | 10 +- ...절 불일치(Vergence-accommodation conflict).md | 10 +- ...절 충돌(Vergence-accommodation conflict).md | 10 +- .../2026-04-20/풀 리퀘스트 워크플로우.md | 10 +- .../풀 리퀘스트(PR) 기반 보안 검토.md | 10 +- .../프래그먼트 바운드(Fragment-bound).md | 10 +- .../프래그먼트 셰이딩(Fragment Shading).md | 10 +- .../프론트엔드 및 Node.js 개발 워크플로우.md | 6 +- .../프론트엔드 및 Nodejs 개발 워크플로우.md | 10 +- ...엔드 및 모노레포(Monorepo) 개발 환경 설정.md | 10 +- .../2026-04-20/프론트엔드 컴포넌트 구조화.md | 10 +- .../2026-04-20/프론트엔드 컴포넌트 설계.md | 10 +- ...어 경험 디자인 (Player Experience Design).md | 6 +- .../2026-04-20/핀테크의 실시간 사기 탐지.md | 10 +- .../하이브리드 검색 (Hybrid Search).md | 6 +- ...이브리드 코드 리뷰 (Hybrid Code Review).md | 10 +- 01_Archive/2026-04-20/하이브리드 코드 리뷰.md | 10 +- .../할당 실패(Allocation Failure).md | 10 +- .../할당 타임라인(Allocation Timeline).md | 10 +- .../함수 호출 (Function Calling).md | 6 +- .../행동 경제학의 인센티브 구조 설계.md | 6 +- .../2026-04-20/행동 경제학의 학습 이론.md | 6 +- 01_Archive/2026-04-20/행동 수정 기법.md | 6 +- .../행동 치료 및 인지 행동 치료 (CBT).md | 6 +- .../행동주의 심리학 (Behaviorism).md | 6 +- 01_Archive/2026-04-20/행동주의 심리학.md | 6 +- .../2026-04-20/헤드 마운트 디스플레이(HMD).md | 10 +- .../2026-04-20/헤드마운트 디스플레이 (HMD).md | 10 +- ...어의 민감 데이터(PII_PCI) 보안 규제 준수.md | 10 +- .../2026-04-20/현대 웹 애플리케이션 설계.md | 10 +- 01_Archive/2026-04-20/환영합니다!.md | 5 - 01_Archive/2026-04-20/환영합니다.md | 6 +- .../2026-04-20/회복탄력성 (Resilience).md | 6 +- .../2026-04-20/힙 메모리(Heap Memory).md | 10 +- .../2026-04-20/힙 스냅샷 (Heap Snapshots).md | 10 +- .../2026-04-20/힙 스냅샷(Heap Snapshot).md | 10 +- 01_Archive/Old_2nd_Structure/2026-04-20.md | 0 01_Archive/Old_2nd_Structure/환영합니다!.md | 5 - 10_Wiki/Decisions/Index.md | 2 +- .../Decisions/Skybound/Combat_Balance_Buff.md | 10 +- .../Skybound/Frame_Type_Restoration.md | 10 +- .../Decisions/Skybound/IDE_Stability_Fix.md | 10 +- 10_Wiki/Decisions/Skybound/Index.md | 6 +- 10_Wiki/Development/Code Splitting.md | 14 +- 10_Wiki/Development/Concurrent Features.md | 12 +- .../Concurrent Rendering in React 18+.md | 12 +- 10_Wiki/Development/Context API.md | 12 +- .../Debugging Frontend Applications.md | 14 +- .../Engineering Scalable Frontend Systems.md | 18 +- .../Folder Structure Best Practices.md | 12 +- .../Frontend Performance Debugging.md | 16 +- 10_Wiki/Development/Index.md | 4 +- .../Large-scale Application Refactoring.md | 14 +- 10_Wiki/Development/Lazy Loading.md | 14 +- 10_Wiki/Development/Next.js App Router.md | 12 +- 10_Wiki/Development/Prop Drilling.md | 10 +- .../Development/Re-renders Optimization.md | 12 +- .../React 18 Concurrent Features.md | 12 +- .../Development/React Application Scaling.md | 4 +- .../Development/React Codebase Refactoring.md | 16 +- .../Development/React DevTools Profiler.md | 12 +- .../React Frontend Architecture.md | 14 +- 10_Wiki/Development/React Scalability.md | 18 +- 10_Wiki/Development/React.lazy().md | 18 +- .../Development/Real User Monitoring (RUM).md | 16 +- 10_Wiki/Development/Redux.md | 14 +- 10_Wiki/Development/Rollup.md | 14 +- .../Development/Scalable Frontend Systems.md | 18 +- 10_Wiki/Development/Storybook.md | 14 +- 10_Wiki/Development/UI_Components/Index.md | 2 +- .../Development/Visual Regression Testing.md | 14 +- .../Development/Vite + React 성능 최적화.md | 16 +- 10_Wiki/Development/Vite Build System.md | 14 +- 10_Wiki/Development/Vite Build Tool.md | 14 +- .../대규모 프론트엔드 애플리케이션.md | 16 +- 10_Wiki/Development/비동기 데이터 관리.md | 14 +- ...론트엔드 애플리케이션 렌더링 병목 개선.md | 16 +- 10_Wiki/Index.md | 26 +- 10_Wiki/Management/Agile Environments.md | 12 +- 10_Wiki/Management/Branching Strategies.md | 16 +- 10_Wiki/Management/Code Review.md | 10 +- 10_Wiki/Management/Git Workflow.md | 16 +- 10_Wiki/Management/GitHub Flow.md | 14 +- 10_Wiki/Management/Index.md | 2 +- .../System/Antigravity_Agent_System_v1.md | 10 +- 10_Wiki/Management/System/Index.md | 2 +- 10_Wiki/Management/Team Collaboration.md | 18 +- 10_Wiki/Management/Version Control.md | 16 +- .../ConnectAI/Core_Optimization_Plan.md | 10 +- 10_Wiki/Projects/Index.md | 2 +- .../Skybound/Architecture_Refactor.md | 10 +- .../Projects/Skybound/HUD_UI_Refinement.md | 10 +- 10_Wiki/Projects/Skybound/Index.md | 4 +- .../Skills/BuildSystem/Incremental_Build.md | 10 +- 10_Wiki/Skills/BuildSystem/Index.md | 2 +- 10_Wiki/Skills/Connect-AI-Architecture.md | 4 +- 10_Wiki/Skills/Index.md | 4 +- 10_Wiki/Skills/P-Reinforce_Skill.md | 14 +- 10_Wiki/Skills/knowledge_inventory_1535.json | 0 10_Wiki/Technical_Reports/Index.md | 4 +- 10_Wiki/Topics/.obsidian/graph.json | 2 +- 10_Wiki/Topics/.obsidian/workspace.json | 7 +- .../Topics/00_Raw/conversations/2026-04-30.md | 12 +- 10_Wiki/Topics/01_Frontend_Mastery/Index.md | 16 +- .../React_Clean_Code_Best_Practices.md | 10 +- .../React_Hooks_Deep_Dive.md | 10 +- .../01_Frontend_Mastery/React_Mental_Model.md | 14 +- .../React_Performance_Optimization.md | 12 +- .../React_State_Management_Strategy.md | 14 +- .../React_Testing_Strategy.md | 10 +- .../TypeScript_Type_Safety.md | 8 +- .../WebWorker_Performance.md | 8 +- ...SDLC & SSDLC (소프트웨어 개발 생명주기).md | 14 +- ...ulture & Onboarding (팀 문화 및 온보딩).md | 14 +- .../API_Communication_Patterns.md | 8 +- .../Clean Architecture & Patterns.md | 12 +- .../Clean Architecture.md | 12 +- .../Component_Design_Patterns.md | 14 +- .../Dependency Injection (DI).md | 12 +- .../Dependency Management (DI & DIP).md | 16 +- .../02_Architecture_Principles/Index.md | 10 +- .../MVC (Model-View-Controller).md | 12 +- .../SOLID Principles.md | 16 +- .../Separation_of_Concerns.md | 12 +- .../Single Responsibility Principle (SRP).md | 12 +- .../Single_Source_of_Truth.md | 12 +- .../Systemic_Simulation_Principles.md | 8 +- ... Practices (현대적 엔지니어링 프랙티스).md | 14 +- ...iples (소프트웨어 엔지니어링 핵심 원칙).md | 14 +- .../Testing Methodologies (테스트 방법론).md | 14 +- .../CI-CD Pipeline (지속적 통합 및 배포).md | 14 +- .../03_DevOps_Environment/CI-CD Pipeline.md | 12 +- .../Deployment_Final_Gate.md | 10 +- .../DevOps_Environment_Setup.md | 4 +- .../Engineering Metrics (DORA).md | 12 +- .../Git_Operation_Protocol.md | 8 +- 10_Wiki/Topics/03_DevOps_Environment/Index.md | 10 +- .../Modern_Environment_Ecosystem.md | 12 +- .../Tetris_Project_Retrospective.md | 10 +- ...ated Code Assurance (AI 생성 코드 검증).md | 48 +- .../Accessibility_Inclusivity.md | 12 +- ...tion Security Posture Management (ASPM).md | 14 +- ...itecture Review (아키텍처 및 설계 리뷰).md | 14 +- ...ated Code Analysis (자동화된 코드 분석).md | 14 +- ...peline Security (CI-CD 파이프라인 보안).md | 14 +- .../Code Quality & Health.md | 12 +- ...on & Metrics (코드 리뷰 자동화 및 지표).md | 14 +- ...tion (코드 리뷰 에티켓 및 커뮤니케이션).md | 14 +- ...ode Review Foundations (코드 리뷰 기초).md | 14 +- ...onal Excellence (코드 리뷰 운영 우수성).md | 14 +- .../Collaboration_Governance.md | 12 +- ...ORA Metrics (소프트웨어 전달 성과 지표).md | 14 +- ... Chain Security (의존성 및 공급망 보안).md | 14 +- .../Engineering Metrics (DORA).md | 12 +- .../Topics/04_Governance_Reliability/Index.md | 12 +- ...est Best Practices (PR 베스트 프랙티스).md | 14 +- .../Reliability_Safety_First.md | 10 +- .../Review Performance & Flow.md | 14 +- ...ecure Code Review (보안 중심 코드 리뷰).md | 14 +- ...ity Core Practices (보안 핵심 프랙티스).md | 14 +- ...lities (소프트웨어 보안 표준 및 취약점).md | 14 +- ... Analysis & Linting (정적 분석 및 린팅).md | 18 +- .../Styling_Governance.md | 16 +- .../System_Debugging_Protocol.md | 6 +- .../System_Protocol_Standard.md | 8 +- .../Testing Strategy.md | 14 +- 10_Wiki/Topics/10_Wiki/Index.md | 2 +- 10_Wiki/Topics/10v10 대규모 멀티플레이어.md | 24 - 10_Wiki/Topics/2026-05-02.md | 0 ...어 생성 패러다임 전환 및 연속적 창작 워크플로우.md | 16 +- 10_Wiki/Topics/20k skinned instances demo.md | 39 - .../Topics/A-B-Testing-and-Data-Driven-UX.md | 29 - 10_Wiki/Topics/ABA.md | 29 - 10_Wiki/Topics/ADA-Website-Compliance.md | 31 - 10_Wiki/Topics/AGI.md | 29 - 10_Wiki/Topics/AI & Data Sovereignty.md | 31 - .../AI & Games/10v10 대규모 멀티플레이어.md | 8 +- .../Topics/AI & Games/AlphaZero Strategy.md | 6 +- .../Combined Arms (제병협동) 전술.md | 8 +- .../AI & Games/Eugen Systems 모딩 매뉴얼.md | 10 +- ...stems의 Iriszoom 엔진 및 전략 게임 개발.md | 12 +- .../Eugen Systems의 WARNO 시뮬레이션 개발.md | 12 +- ...냉전기 가상 시나리오 및 모딩 생태계 구축.md | 12 +- 10_Wiki/Topics/AI & Games/Index.md | 2 +- .../AI & Games/Steel Division 시리즈.md | 10 +- .../WARNO 그래픽 엔진 업그레이드 프로젝트.md | 12 +- .../AI & Games/WARNO 데이터 기반 밸런싱.md | 12 +- .../AI & Games/WARNO 데이터 기반 설계.md | 14 +- ...멀티플레이어 및 경쟁 플레이 밸런스 패치.md | 10 +- .../Topics/AI & Games/WARNO 모딩(Modding).md | 12 +- 10_Wiki/Topics/AI & Games/WARNO 모딩.md | 12 +- .../AI & Games/WARNO 밸런싱 및 사단 시스템.md | 12 +- ...ARNO 사후 관리 (Post-Launch Management).md | 10 +- ...(Real-time Tactics) 및 Army General 캠페인.md | 10 +- .../WARNO 전술 시뮬레이션 시스템.md | 14 +- .../WARNO 전투 메커니즘 (Combat Mechanics).md | 10 +- .../WARNO 커뮤니티 데이터 도구 생태계.md | 18 +- .../AI & Games/WARNO 커뮤니티 모딩 생태계.md | 16 +- 10_Wiki/Topics/AI & Games/WARNO-DATA Wiki.md | 14 +- .../Topics/AI & Games/WARNO-DATA 프로젝트.md | 12 +- 10_Wiki/Topics/AI & Games/WARNO.md | 10 +- .../AI & Games/WME (Warno Mod Editor).md | 10 +- ...arno-Armory (커뮤니티 데이터 분석 도구).md | 10 +- .../War-Yes 및 Warno-Armory 도구.md | 10 +- 10_Wiki/Topics/AI & Games/Wargame 시리즈.md | 8 +- .../AI & Games/Warno 데이터 기반 설계.md | 12 +- 10_Wiki/Topics/AI & Games/Warno-Armory.md | 10 +- .../AI & Games/가용성 (Availability).md | 10 +- ...위보 상성 (Rock-paper-scissors principle).md | 10 +- ...딩 커뮤니티 도구 (War-Yes, Warno-Armory).md | 12 +- .../사단 시스템 (Division System).md | 10 +- .../Topics/AI & Games/사단 편제표 (TO&E).md | 8 +- .../AI & Games/사단(Division) 시스템.md | 8 +- .../AI & Games/소음 역학 (Noise Dynamics).md | 12 +- ...신과 시야 매커니즘 (Stealth and Optics).md | 8 +- ... 관통 모델링(Armor Penetration Modeling).md | 8 +- ... 및 사거리 데이터 (Armor and Range Stats).md | 8 +- .../AI & Games/제병협동 (Combined Arms).md | 8 +- .../제병협동 전술 (Combined Arms).md | 10 +- ... 알고리즘 (Ballistics and Accuracy Algorithms).md | 8 +- ...Drift (개념 드리프트, 모델 지식의 부패).md | 10 +- 10_Wiki/Topics/AI & ML MLOps/Index.md | 2 +- .../AI-Driven Narrative Systems.md | 6 +- 10_Wiki/Topics/AI & Narrative/Index.md | 2 +- .../AI & Psychology/Affective Computing.md | 6 +- 10_Wiki/Topics/AI & Psychology/Index.md | 2 +- .../Topics/AI & Tools/AI Connect LLM Tool.md | 4 +- 10_Wiki/Topics/AI & Tools/Index.md | 2 +- 10_Wiki/Topics/AI Accountability.md | 32 - 10_Wiki/Topics/AI Connect LLM Tool.md | 39 - 10_Wiki/Topics/AI Governance.md | 32 - 10_Wiki/Topics/AI Humanism.md | 31 - 10_Wiki/Topics/AI Literacy.md | 32 - 10_Wiki/Topics/AI and Narrative.md | 34 - 10_Wiki/Topics/AI for Social Good.md | 33 - .../AI 거버넌스 정책(AI Usage Policy).md | 27 - 10_Wiki/Topics/AI 안전 (AI Safety).md | 4 +- 10_Wiki/Topics/AI 에이전트 (AI Agents).md | 4 +- ... 디버깅 (Image Quality Optimization & Debugging).md | 18 +- ...드 리뷰 및 보안 취약점 점검(DevSecOps).md | 40 - 10_Wiki/Topics/AI 코드 리뷰.md | 33 - 10_Wiki/Topics/AI-Alignment.md | 28 - .../Topics/AI-Answer-Engine-Optimization.md | 29 - 10_Wiki/Topics/AI-Overviews-and-SGE.md | 29 - .../AI-Personalization-and-Adaptive-UX.md | 28 - 10_Wiki/Topics/AI-Search-Optimization.md | 28 - .../Topics/AI/20k skinned instances demo.md | 14 +- .../AI/A-B-Testing-and-Data-Driven-UX.md | 8 +- .../AI/A2A (Agent-to-Agent Protocol).md | 14 +- 10_Wiki/Topics/AI/A2A.md | 10 +- 10_Wiki/Topics/AI/ABA.md | 8 +- 10_Wiki/Topics/AI/ACI.md | 10 +- .../AI/ACP (Agent Communication Protocol).md | 10 +- 10_Wiki/Topics/AI/ADA-Website-Compliance.md | 2 +- 10_Wiki/Topics/AI/AGI.md | 8 +- 10_Wiki/Topics/AI/AI & Data Sovereignty.md | 6 +- 10_Wiki/Topics/AI/AI Accountability.md | 8 +- 10_Wiki/Topics/AI/AI Agents.md | 8 +- 10_Wiki/Topics/AI/AI Governance.md | 12 +- 10_Wiki/Topics/AI/AI Humanism.md | 8 +- 10_Wiki/Topics/AI/AI Literacy.md | 10 +- 10_Wiki/Topics/AI/AI Safety (AI 안전).md | 12 +- 10_Wiki/Topics/AI/AI Safety.md | 10 +- 10_Wiki/Topics/AI/AI and Narrative.md | 10 +- 10_Wiki/Topics/AI/AI for Social Good.md | 8 +- .../AI/AI 거버넌스 정책(AI Usage Policy).md | 8 +- .../AI 생성 코드 검증(AI Code Assurance).md | 12 +- 10_Wiki/Topics/AI/AI 에이전트 (AI Agent).md | 14 +- ...드 리뷰 및 보안 취약점 점검(DevSecOps).md | 16 +- 10_Wiki/Topics/AI/AI 코드 리뷰.md | 14 +- 10_Wiki/Topics/AI/AI-Alignment.md | 4 +- .../AI/AI-Answer-Engine-Optimization.md | 10 +- 10_Wiki/Topics/AI/AI-Overviews-and-SGE.md | 10 +- .../AI/AI-Personalization-and-Adaptive-UX.md | 6 +- 10_Wiki/Topics/AI/AI-Search-Optimization.md | 6 +- ...열 맡기기_ - 정적 분석 툴 (ESLint Prettier)).md | 18 +- ... 모델링 및 상태 머신(State Machine) 설계.md | 10 +- .../Topics/AI/API-Design for AI Services.md | 6 +- 10_Wiki/Topics/AI/API-Key-Management.md | 8 +- 10_Wiki/Topics/AI/A_B-Testing-Platforms.md | 10 +- 10_Wiki/Topics/AI/Abundance.md | 10 +- 10_Wiki/Topics/AI/Academic-Integrity.md | 8 +- .../AI/Accessibility-Compliance-Audit.md | 10 +- 10_Wiki/Topics/AI/Active Learning.md | 10 +- 10_Wiki/Topics/AI/Active-Reasoning.md | 10 +- 10_Wiki/Topics/AI/Activism.md | 12 +- 10_Wiki/Topics/AI/Actor-Critic-Models.md | 10 +- 10_Wiki/Topics/AI/Ad-hoc-Hypotheses.md | 12 +- 10_Wiki/Topics/AI/Ad-hoc-Optimization.md | 12 +- 10_Wiki/Topics/AI/Adaptability.md | 12 +- .../Adaptive Compute (적응형 계산량 조절).md | 12 +- .../Topics/AI/Adaptive Context Compaction.md | 8 +- 10_Wiki/Topics/AI/Adaptive-Curation.md | 6 +- .../Topics/AI/Advanced-Interface-Design.md | 8 +- .../Topics/AI/Adversarial Code Stylometry.md | 10 +- 10_Wiki/Topics/AI/Aesthetic-Value.md | 12 +- 10_Wiki/Topics/AI/Affordance.md | 10 +- 10_Wiki/Topics/AI/Agent Architecture.md | 12 +- .../Topics/AI/Agent Identity Management.md | 8 +- 10_Wiki/Topics/AI/Agent Memory System.md | 8 +- 10_Wiki/Topics/AI/Agent Personality.md | 12 +- 10_Wiki/Topics/AI/Agent_Harness.md | 10 +- 10_Wiki/Topics/AI/Agent_State_Store.md | 10 +- 10_Wiki/Topics/AI/Agentic Coding.md | 12 +- 10_Wiki/Topics/AI/Agentic Orchestration.md | 12 +- 10_Wiki/Topics/AI/Agile-Philosophy.md | 12 +- 10_Wiki/Topics/AI/Alcoholism.md | 10 +- .../Topics/AI/Algorithm-Complexity-Big-O.md | 6 +- 10_Wiki/Topics/AI/Algorithmic Fairness.md | 10 +- 10_Wiki/Topics/AI/Algorithmic Transparency.md | 6 +- 10_Wiki/Topics/AI/Algorithmic-Biology.md | 10 +- 10_Wiki/Topics/AI/Algorithmic-Game-Theory.md | 6 +- 10_Wiki/Topics/AI/Alignment.md | 8 +- 10_Wiki/Topics/AI/Alternative Realities.md | 12 +- 10_Wiki/Topics/AI/Altruism.md | 12 +- 10_Wiki/Topics/AI/Ambient-Declarations.md | 10 +- 10_Wiki/Topics/AI/Ambition.md | 14 +- .../Topics/AI/Amdahls Law (암달의 법칙).md | 6 +- 10_Wiki/Topics/AI/Analogical-Reasoning.md | 12 +- 10_Wiki/Topics/AI/Analogy.md | 8 +- 10_Wiki/Topics/AI/Analysis.md | 8 +- 10_Wiki/Topics/AI/Anarchism.md | 10 +- 10_Wiki/Topics/AI/Anarcho-Capitalism.md | 8 +- 10_Wiki/Topics/AI/Anarcho-Primitivism.md | 6 +- 10_Wiki/Topics/AI/Anisomorphism.md | 12 +- 10_Wiki/Topics/AI/Anomaly-Detection.md | 8 +- 10_Wiki/Topics/AI/Anthropic-Principle.md | 4 +- 10_Wiki/Topics/AI/Anthropomorphism.md | 10 +- 10_Wiki/Topics/AI/Anticipation.md | 12 +- 10_Wiki/Topics/AI/Antifragility.md | 10 +- 10_Wiki/Topics/AI/Antinomianism.md | 10 +- 10_Wiki/Topics/AI/Anxiety.md | 8 +- .../Topics/AI/Arguing-by-Counterexample.md | 10 +- .../Topics/AI/Arrangement-and-Composition.md | 12 +- 10_Wiki/Topics/AI/Articulateness.md | 8 +- .../Artificial General Intelligence (AGI).md | 12 +- .../Topics/AI/Artificial Intelligence (AI).md | 16 +- .../AI/Artificial-Intelligence-in-Games.md | 12 +- 10_Wiki/Topics/AI/Artificial-Intelligence.md | 10 +- 10_Wiki/Topics/AI/Artificial-Life.md | 6 +- 10_Wiki/Topics/AI/Arts.md | 8 +- 10_Wiki/Topics/AI/Assertiveness.md | 10 +- 10_Wiki/Topics/AI/Assessment.md | 14 +- 10_Wiki/Topics/AI/Asset-Specific-Knowledge.md | 8 +- 10_Wiki/Topics/AI/Assumptions-vs-Facts.md | 12 +- 10_Wiki/Topics/AI/Atheism.md | 12 +- 10_Wiki/Topics/AI/Atlantic.md | 8 +- 10_Wiki/Topics/AI/Atmospheric-Intelligence.md | 10 +- .../AI/Atomic-Design-System-Architecture.md | 10 +- .../AI/Atomic-Styling-and-Design-Systems.md | 12 +- 10_Wiki/Topics/AI/Atomism.md | 12 +- 10_Wiki/Topics/AI/Attention Mechanisms.md | 10 +- .../Topics/AI/Attention is All You Need.md | 6 +- 10_Wiki/Topics/AI/Authenticity.md | 8 +- ...sm Spectrum Disorder (ASD) Intervention.md | 4 +- 10_Wiki/Topics/AI/Auto-Encoding.md | 10 +- .../AI/Auto-GPT and Autonomous Agents.md | 8 +- 10_Wiki/Topics/AI/Autobiography.md | 10 +- 10_Wiki/Topics/AI/Autoethnography.md | 12 +- .../Topics/AI/Automated-Decision-Making.md | 12 +- 10_Wiki/Topics/AI/Automated-Game-Testing.md | 8 +- 10_Wiki/Topics/AI/Automated-Map-Generation.md | 12 +- 10_Wiki/Topics/AI/Automated-Reasoning.md | 10 +- .../Topics/AI/Automated-Refactoring-Tools.md | 12 +- .../Topics/AI/Automated-Security-Audits.md | 10 +- .../Topics/AI/Automated-Theorem-Proving.md | 10 +- 10_Wiki/Topics/AI/Automated_Mapping.md | 8 +- 10_Wiki/Topics/AI/Automation-Paradox.md | 8 +- 10_Wiki/Topics/AI/Autonomous Vehicles.md | 14 +- 10_Wiki/Topics/AI/Autonomous-Agents.md | 12 +- .../AI/Autonomous-Polling-Wait-Automation.md | 16 +- .../AI/Autonomous-Vehicle-Path-Planning.md | 12 +- .../Topics/AI/Availability-and-Persistence.md | 12 +- 10_Wiki/Topics/AI/Awards.md | 8 +- 10_Wiki/Topics/AI/Axify.md | 6 +- 10_Wiki/Topics/AI/Axiology.md | 12 +- 10_Wiki/Topics/AI/Axiomatic-Systems.md | 12 +- 10_Wiki/Topics/AI/Axioms.md | 10 +- 10_Wiki/Topics/AI/Azure DevOps.md | 10 +- 10_Wiki/Topics/AI/B-Tree.md | 10 +- 10_Wiki/Topics/AI/BERT.md | 8 +- 10_Wiki/Topics/AI/BFS vs DFS.md | 10 +- 10_Wiki/Topics/AI/Backend.md | 14 +- .../Topics/AI/Backpropagation Through Time.md | 6 +- 10_Wiki/Topics/AI/Backpropagation.md | 8 +- 10_Wiki/Topics/AI/Backups.md | 8 +- 10_Wiki/Topics/AI/Backward-Reasoning.md | 10 +- 10_Wiki/Topics/AI/Bag of Words (BoW).md | 8 +- 10_Wiki/Topics/AI/Baseline Project.md | 8 +- 10_Wiki/Topics/AI/Batch-Inference.md | 8 +- 10_Wiki/Topics/AI/Bayes-Theorem.md | 8 +- 10_Wiki/Topics/AI/Bayesian Inference.md | 6 +- 10_Wiki/Topics/AI/Bayesian Statistics.md | 12 +- .../Topics/AI/Bayesian-Brain-Hypothesis.md | 4 +- 10_Wiki/Topics/AI/Bayesian-Updating.md | 12 +- 10_Wiki/Topics/AI/Be-Detailed.md | 10 +- 10_Wiki/Topics/AI/Beckett.md | 10 +- 10_Wiki/Topics/AI/Behavior.md | 12 +- 10_Wiki/Topics/AI/Behavioral Finance.md | 8 +- 10_Wiki/Topics/AI/Behavioral-Economics.md | 10 +- 10_Wiki/Topics/AI/Behavioral-Incentives.md | 12 +- 10_Wiki/Topics/AI/Belief-Revision.md | 12 +- 10_Wiki/Topics/AI/Belief-System.md | 16 +- 10_Wiki/Topics/AI/Beliefs.md | 12 +- 10_Wiki/Topics/AI/Bellman Equation.md | 8 +- 10_Wiki/Topics/AI/Bellman-Equation.md | 12 +- 10_Wiki/Topics/AI/Benchmarks.md | 8 +- 10_Wiki/Topics/AI/Bert-Language-Model.md | 12 +- 10_Wiki/Topics/AI/Best SAST Tools in 2026.md | 10 +- 10_Wiki/Topics/AI/Best-of-N Sampling ( ø).md | 10 +- .../AI/Best-of-N Sampling (최적 샘플링).md | 6 +- 10_Wiki/Topics/AI/Best-of-N Sampling.md | 8 +- 10_Wiki/Topics/AI/Best-of-N-Sampling.md | 14 +- 10_Wiki/Topics/AI/Bias vs Variance.md | 10 +- .../Topics/AI/Bias-Correction-Algorithm.md | 12 +- 10_Wiki/Topics/AI/Bias-Variance-Tradeoff.md | 10 +- 10_Wiki/Topics/AI/Bible.md | 10 +- 10_Wiki/Topics/AI/Bibliometrics.md | 8 +- 10_Wiki/Topics/AI/Big-Data.md | 6 +- 10_Wiki/Topics/AI/Big-Picture.md | 20 +- .../Topics/AI/Binary-Author-Identification.md | 16 +- 10_Wiki/Topics/AI/Binary-Search.md | 8 +- 10_Wiki/Topics/AI/BioShock (2007).md | 8 +- 10_Wiki/Topics/AI/BioShock-Critique.md | 10 +- 10_Wiki/Topics/AI/Bioenergetics.md | 8 +- .../AI/Bioinformatics-Structure-Prediction.md | 8 +- .../AI/Biological-Inspired-Algorithms.md | 12 +- 10_Wiki/Topics/AI/Biological-Intelligence.md | 14 +- 10_Wiki/Topics/AI/Biomechanics-of-Injury.md | 10 +- 10_Wiki/Topics/AI/Biometrics.md | 10 +- 10_Wiki/Topics/AI/Black-Box-Optimization.md | 6 +- 10_Wiki/Topics/AI/Black-Hole.md | 8 +- 10_Wiki/Topics/AI/Black-Swan.md | 12 +- 10_Wiki/Topics/AI/Blockchain.md | 10 +- 10_Wiki/Topics/AI/Blocking.md | 10 +- 10_Wiki/Topics/AI/Blog-Post.md | 8 +- 10_Wiki/Topics/AI/Bloom-Filters in Search.md | 6 +- 10_Wiki/Topics/AI/Bloom-Filters.md | 12 +- 10_Wiki/Topics/AI/Boltzmann-Machines.md | 4 +- .../Boosting-Algorithms-XGBoost-LightGBM.md | 10 +- 10_Wiki/Topics/AI/Bottlenecks.md | 14 +- 10_Wiki/Topics/AI/Bottom-Up-Approach.md | 14 +- 10_Wiki/Topics/AI/Boundaries.md | 12 +- 10_Wiki/Topics/AI/Boundary-Setting.md | 12 +- 10_Wiki/Topics/AI/Bounded Contexts.md | 10 +- 10_Wiki/Topics/AI/Bounded Rationality.md | 12 +- ...nded-Contexts-and-Interface-Segregation.md | 12 +- 10_Wiki/Topics/AI/Bounded-Rationality.md | 12 +- 10_Wiki/Topics/AI/Bounding-Box-Regression.md | 8 +- 10_Wiki/Topics/AI/Bourgeoisie.md | 10 +- .../AI/Brain-Computer Interface (BCI).md | 4 +- .../AI/Brain-Computer-Interface (BCI).md | 8 +- ...rain-Derived Neurotrophic Factor (BDNF).md | 8 +- .../AI/Branded-Types-for-Nominal-Typing.md | 10 +- 10_Wiki/Topics/AI/Branded-Types.md | 12 +- 10_Wiki/Topics/AI/Branding.md | 12 +- 10_Wiki/Topics/AI/Browser.md | 12 +- 10_Wiki/Topics/AI/Brute-force.md | 10 +- 10_Wiki/Topics/AI/Bubble-Sort.md | 10 +- 10_Wiki/Topics/AI/Budget.md | 14 +- 10_Wiki/Topics/AI/Bureaucracy.md | 10 +- ...rnout Prevention in Professional Gaming.md | 8 +- 10_Wiki/Topics/AI/Burnout.md | 10 +- .../Topics/AI/Business Intelligence (BI).md | 10 +- 10_Wiki/Topics/AI/CAP-Theorem.md | 4 +- .../Topics/AI/CI-CD-Pipeline-Foundations.md | 8 +- .../AI/CI_CD 및 Pull Request 자동화 리뷰.md | 16 +- .../AI/CI_CD 파이프라인 및 IDE 통합 보안.md | 16 +- 10_Wiki/Topics/AI/CI_CD.md | 14 +- 10_Wiki/Topics/AI/CLIP.md | 6 +- 10_Wiki/Topics/AI/CPTED.md | 12 +- 10_Wiki/Topics/AI/CV_Synthesis.md | 14 +- 10_Wiki/Topics/AI/Call Stack.md | 14 +- .../AI/Case-Study-Allbirds-PWA-Redesign.md | 8 +- .../Case-Study-Kiwi-com-Frontend-Migration.md | 10 +- ...Case-Study-Skybound-Asset-Cache-Busting.md | 4 +- ...ybound-Red-Striker-Jitter-Stabilization.md | 6 +- 10_Wiki/Topics/AI/Catastrophic-Forgetting.md | 8 +- 10_Wiki/Topics/AI/Causal-Inference.md | 4 +- .../Topics/AI/Central-Pattern-Generators.md | 10 +- 10_Wiki/Topics/AI/CesiumJS.md | 16 +- .../Topics/AI/Chain-of-Thought (CoT 罽).md | 10 +- .../AI/Chain-of-Thought (CoT 사고 사슬).md | 12 +- 10_Wiki/Topics/AI/Chaos-Theory in Systems.md | 6 +- .../AI/Chrome DevTools Memory Profiling.md | 8 +- ...ols 메모리 프로파일링 및 힙 스냅샷 분석.md | 18 +- .../AI/Chrome DevTools 메모리 프로파일링.md | 14 +- 10_Wiki/Topics/AI/Chrome DevTools.md | 16 +- .../Topics/AI/Chrome-Rendering-Performance.md | 14 +- .../AI/Chronic-Pain-Management-Protocols.md | 10 +- .../AI/Circuit Discovery (회로 발견).md | 10 +- 10_Wiki/Topics/AI/Circuit Discovery.md | 6 +- .../Topics/AI/Circular-Economy-Transitions.md | 14 +- 10_Wiki/Topics/AI/Circular-Economy.md | 8 +- .../AI/Clean-Architecture-Implementation.md | 12 +- .../AI/Clean-Architecture-TypeScript.md | 10 +- 10_Wiki/Topics/AI/Clean-Code-Principles.md | 6 +- .../Climate Change Mitigation Frameworks.md | 12 +- .../AI/Clinical-Kinesiology-Assessment.md | 12 +- 10_Wiki/Topics/AI/Code Review.md | 12 +- ...g-and-Frontend-Performance-Optimization.md | 6 +- 10_Wiki/Topics/AI/Cognitive Biases.md | 14 +- 10_Wiki/Topics/AI/Cognitive Computing.md | 6 +- .../AI/Cognitive Neuroscience of Flow.md | 10 +- 10_Wiki/Topics/AI/Cognitive Psychology.md | 10 +- 10_Wiki/Topics/AI/Cognitive Reserve Theory.md | 4 +- ... Training Software (eg Aim Lab_KovaaKs).md | 6 +- 10_Wiki/Topics/AI/Cognitive-Architecture.md | 4 +- .../Topics/AI/Cognitive-Evaluation-Theory.md | 8 +- 10_Wiki/Topics/AI/Cognitive-Therapy-in-CBT.md | 12 +- 10_Wiki/Topics/AI/Collaborative-Filtering.md | 4 +- 10_Wiki/Topics/AI/Collective-Intelligence.md | 10 +- .../Topics/AI/Combinatorial Game Theory.md | 8 +- .../Topics/AI/Combinatorial-Optimization.md | 4 +- 10_Wiki/Topics/AI/CompCert-C-Compiler.md | 10 +- 10_Wiki/Topics/AI/Complexity Theory.md | 12 +- 10_Wiki/Topics/AI/Complexity-Theory.md | 6 +- 10_Wiki/Topics/AI/Component-Composition.md | 8 +- 10_Wiki/Topics/AI/Computational Creativity.md | 8 +- ... Neuroscience of Reinforcement Learning.md | 6 +- 10_Wiki/Topics/AI/Computational-Creativity.md | 12 +- .../Topics/AI/Computational-Linguistics.md | 4 +- .../AI/Computational-Neuroscience-RL.md | 14 +- 10_Wiki/Topics/AI/Computer Vision.md | 10 +- 10_Wiki/Topics/AI/Computer-Aided-Design.md | 16 +- 10_Wiki/Topics/AI/Computer-Vision.md | 8 +- 10_Wiki/Topics/AI/Computer_Vision.md | 10 +- .../AI/Concept Drift (개념 드리프트).md | 10 +- 10_Wiki/Topics/AI/Concept Mapping.md | 10 +- 10_Wiki/Topics/AI/Concept-Drift.md | 6 +- 10_Wiki/Topics/AI/Concreteness-Principle.md | 4 +- 10_Wiki/Topics/AI/Concurrent Programming.md | 8 +- .../AI/Conditioning and Learning ( ).md | 8 +- 10_Wiki/Topics/AI/Connect-AI-Documentation.md | 16 +- .../Topics/AI/Constitutional AI (헌법 AI).md | 10 +- 10_Wiki/Topics/AI/Constitutional-AI.md | 4 +- .../Constraint Satisfaction Problems (CSP).md | 14 +- .../AI/Constraint-Satisfaction Problems.md | 4 +- .../AI/Constraint-Satisfaction-Problems.md | 12 +- 10_Wiki/Topics/AI/Context Engineering.md | 10 +- 10_Wiki/Topics/AI/Context Rot.md | 8 +- 10_Wiki/Topics/AI/Context-Aware-Computing.md | 4 +- 10_Wiki/Topics/AI/Context_Engineering.md | 10 +- 10_Wiki/Topics/AI/Continuous-Discovery.md | 12 +- 10_Wiki/Topics/AI/Contrastive-Learning.md | 6 +- .../Topics/AI/Control Systems Engineering.md | 12 +- .../Topics/AI/Control-Systems-Engineering.md | 10 +- 10_Wiki/Topics/AI/Control-Theory.md | 6 +- .../AI/Convolutional-Neural-Networks.md | 6 +- 10_Wiki/Topics/AI/Core-Web-Vitals-Metrics.md | 12 +- 10_Wiki/Topics/AI/Core-Web-Vitals.md | 10 +- 10_Wiki/Topics/AI/Corgea.md | 14 +- 10_Wiki/Topics/AI/Corporate-LMS-Training.md | 18 +- .../Topics/AI/Cost-Benefit Analysis in AI.md | 6 +- 10_Wiki/Topics/AI/Creativity Research.md | 14 +- .../Topics/AI/Credit Assignment Problem.md | 8 +- 10_Wiki/Topics/AI/Cross-Entropy Loss.md | 4 +- .../Topics/AI/Cumulative-Layout-Shift-CLS.md | 8 +- 10_Wiki/Topics/AI/Curriculum-Learning.md | 4 +- .../AI/Custom-ESLint-Rules-Development.md | 6 +- 10_Wiki/Topics/AI/Custom-ESLint-Rules.md | 16 +- 10_Wiki/Topics/AI/Custom-Hooks-Patterns.md | 10 +- 10_Wiki/Topics/AI/Customer-Journey-Mapping.md | 16 +- 10_Wiki/Topics/AI/Cybernetics Foundations.md | 8 +- 10_Wiki/Topics/AI/Cybernetics.md | 12 +- .../Topics/AI/DAG-Dependency-Management.md | 14 +- 10_Wiki/Topics/AI/DDD-Type-Safety.md | 18 +- 10_Wiki/Topics/AI/DDD-in-TypeScript.md | 14 +- 10_Wiki/Topics/AI/DORA-Metrics.md | 12 +- .../DPO (Direct Preference Optimization).md | 8 +- 10_Wiki/Topics/AI/DQN.md | 8 +- 10_Wiki/Topics/AI/Data Cleaning Algorithms.md | 10 +- .../AI/Data Distillation (데이터 증류).md | 12 +- .../Topics/AI/Data-Augmentation Strategies.md | 10 +- 10_Wiki/Topics/AI/Data-Ethics and Privacy.md | 6 +- 10_Wiki/Topics/AI/Data-Flywheel-Effect.md | 6 +- .../Topics/AI/Data-Pipeline Orchestration.md | 6 +- 10_Wiki/Topics/AI/Data-Science-in-UX.md | 12 +- .../Topics/AI/Data-Transfer-Object-Design.md | 8 +- 10_Wiki/Topics/AI/Dead-Space-Series.md | 6 +- .../AI/Deceptive Alignment (기만적 정렬).md | 10 +- 10_Wiki/Topics/AI/Decision Theory.md | 16 +- .../AI/Decision-Trees and Random Forests.md | 4 +- 10_Wiki/Topics/AI/Declaration-Files.md | 14 +- 10_Wiki/Topics/AI/Deep Q-Networks (DQN).md | 8 +- 10_Wiki/Topics/AI/Deep-Convolutional-GANs.md | 14 +- 10_Wiki/Topics/AI/Deep-Grammar.md | 10 +- 10_Wiki/Topics/AI/Deep-Learning.md | 6 +- 10_Wiki/Topics/AI/Deep-Q-Networks-DQN.md | 8 +- 10_Wiki/Topics/AI/DeepCode AI.md | 10 +- 10_Wiki/Topics/AI/Deepfake-Detection.md | 12 +- 10_Wiki/Topics/AI/Deepfake-Technology.md | 4 +- .../Topics/AI/Default Mode Network (DMN).md | 8 +- 10_Wiki/Topics/AI/DefinitelyTyped.md | 12 +- 10_Wiki/Topics/AI/Definitions_of_Game.md | 8 +- 10_Wiki/Topics/AI/Degrees-of-Freedom.md | 12 +- 10_Wiki/Topics/AI/Deliberate-Practice.md | 10 +- .../AI/Denavit-Hartenberg-Parameters.md | 10 +- .../AI/Dense vs Sparse Neural Networks.md | 8 +- .../Topics/AI/Dependency-Graph-Analysis.md | 10 +- 10_Wiki/Topics/AI/Dependency-Injection.md | 8 +- .../AI/Dependency-Inversion-Principle.md | 8 +- 10_Wiki/Topics/AI/Deployment-Strategy.md | 14 +- 10_Wiki/Topics/AI/Design-System.md | 16 +- 10_Wiki/Topics/AI/Determinism-in-Computing.md | 6 +- .../Topics/AI/DevOps-and-UX-Convergence.md | 10 +- 10_Wiki/Topics/AI/DevOps-for-AI-MLOps.md | 4 +- 10_Wiki/Topics/AI/DevSecOps.md | 12 +- .../Topics/AI/Differentiable Programming.md | 8 +- 10_Wiki/Topics/AI/Diffusion-Models.md | 8 +- .../Digital Intellectual Property Rights.md | 6 +- .../Topics/AI/Digital Thread Integration.md | 12 +- 10_Wiki/Topics/AI/Digital-Twin-Technology.md | 16 +- 10_Wiki/Topics/AI/Dijkstra's Algorithm.md | 8 +- 10_Wiki/Topics/AI/Dimensionality-Reduction.md | 6 +- .../Diminishing Returns (한계 수익 체감).md | 8 +- .../Directed-Acyclic-Graph-Build-Systems.md | 12 +- ...ted-Acyclic-Graph-Dependency-Management.md | 8 +- ...Discriminated-Unions-for-Error-Handling.md | 8 +- ...Discriminated-Unions-for-State-Modeling.md | 10 +- 10_Wiki/Topics/AI/Discriminated-Unions.md | 12 +- 10_Wiki/Topics/AI/Dissipative-Structures.md | 12 +- 10_Wiki/Topics/AI/Distillation.md | 10 +- .../AI/Distributed Reinforcement Learning.md | 12 +- 10_Wiki/Topics/AI/Distributed-Computing.md | 4 +- .../AI/Distributed-System-Type-Safety.md | 12 +- 10_Wiki/Topics/AI/Distributed-Systems.md | 8 +- 10_Wiki/Topics/AI/Documentation-Strategy.md | 14 +- 10_Wiki/Topics/AI/Domain Objects.md | 8 +- 10_Wiki/Topics/AI/Domain-Driven-Design-DDD.md | 6 +- .../Topics/AI/Domain-Specific-Languages.md | 10 +- 10_Wiki/Topics/AI/Dopamine-Modeling.md | 10 +- .../Topics/AI/Dopaminergic Reward System.md | 12 +- .../Topics/AI/Dopaminergic Reward Systems.md | 12 +- 10_Wiki/Topics/AI/Drama Management Systems.md | 12 +- 10_Wiki/Topics/AI/Dramaturgy-Theory.md | 12 +- 10_Wiki/Topics/AI/Dry-Principle.md | 10 +- .../AI/Dynamic Difficulty Adjustment (DDA).md | 8 +- .../Dynamic Few-Shot (동적 퓨샷 선택 전략).md | 12 +- 10_Wiki/Topics/AI/Dynamic-Capabilities.md | 14 +- .../AI/Dynamic-Creative-Optimization.md | 10 +- .../Topics/AI/Dynamic-Environment-Handling.md | 6 +- 10_Wiki/Topics/AI/Dynamic-Programming.md | 12 +- 10_Wiki/Topics/AI/E-Learning-Gamification.md | 12 +- .../AI/E-commerce-Catalog-Management.md | 12 +- 10_Wiki/Topics/AI/E-commerce-Optimization.md | 12 +- .../Topics/AI/ESLint-Plugin-Development.md | 14 +- 10_Wiki/Topics/AI/ESLint-Static-Analysis.md | 14 +- .../AI/EU-Web-Accessibility-Directive.md | 12 +- .../AI/Ecology and Ecosystem Modeling.md | 10 +- 10_Wiki/Topics/AI/Economic-Analysis.md | 14 +- .../Topics/AI/Economic-Complexity-Index.md | 10 +- 10_Wiki/Topics/AI/Economic-Mobility.md | 12 +- 10_Wiki/Topics/AI/Economics-of-Information.md | 12 +- 10_Wiki/Topics/AI/Edge-AI-and-Computing.md | 8 +- .../Topics/AI/Edge-Artificial-Intelligence.md | 20 +- 10_Wiki/Topics/AI/Edge-Computing.md | 12 +- 10_Wiki/Topics/AI/Edtech-Industry-Trends.md | 10 +- 10_Wiki/Topics/AI/Effective-Altruism-in-AI.md | 14 +- 10_Wiki/Topics/AI/Efficiency.md | 16 +- .../Topics/AI/Eigenvalues-and-Eigenvectors.md | 4 +- 10_Wiki/Topics/AI/Eligibility-Traces.md | 4 +- .../AI/Elite-Sport-Science-Protocols.md | 10 +- .../AI/Elite-Strength-and-Conditioning.md | 8 +- 10_Wiki/Topics/AI/Elite-Theory.md | 12 +- 10_Wiki/Topics/AI/Embodied Cognition.md | 6 +- 10_Wiki/Topics/AI/Embodied-AI.md | 4 +- .../Topics/AI/Emergence-in-Complex-Systems.md | 12 +- 10_Wiki/Topics/AI/Emergence-in-Systems.md | 8 +- 10_Wiki/Topics/AI/Emergence.md | 10 +- .../AI/Emotional-AI (Affective Computing).md | 6 +- ...lly Intelligent Tutoring Systems (EITS).md | 8 +- 10_Wiki/Topics/AI/Empathy-in-AI.md | 10 +- .../Encapsulation-and-Information-Hiding.md | 6 +- .../AI/Encapsulation-of-Domain-Invariants.md | 10 +- .../AI/Encapsulation-via-Access-Modifiers.md | 8 +- 10_Wiki/Topics/AI/End-to-End-Learning.md | 4 +- .../AI/End-to-End-Testing-Strategies.md | 12 +- .../AI/Endurance-Athletics-Cognition.md | 10 +- 10_Wiki/Topics/AI/Ensemble-Learning.md | 12 +- 10_Wiki/Topics/AI/Ensemble-Methods.md | 2 +- 10_Wiki/Topics/AI/Ensuring-Data-Privacy.md | 12 +- .../Topics/AI/Enterprise-Design-Systems.md | 12 +- .../Enterprise-Resource-Planning-Systems.md | 12 +- .../Enterprise-Scale-Monorepo-Management.md | 10 +- 10_Wiki/Topics/AI/Enterprise-Service-Bus.md | 14 +- .../AI/Enterprise-Software-Architecture.md | 8 +- .../AI/Enterprise-Software-Engineering.md | 10 +- .../Topics/AI/Entity-Relationship-Modeling.md | 16 +- .../AI/Entropy in Information Theory.md | 8 +- 10_Wiki/Topics/AI/Environment-Design-in-RL.md | 6 +- .../Topics/AI/Enzyme-Inhibition-Kinetics.md | 8 +- 10_Wiki/Topics/AI/Epidemiological-Modeling.md | 10 +- 10_Wiki/Topics/AI/Epistemic-Uncertainty.md | 6 +- 10_Wiki/Topics/AI/Epistemology.md | 8 +- 10_Wiki/Topics/AI/Equality.md | 12 +- 10_Wiki/Topics/AI/Ergodic-Theory.md | 14 +- .../AI/Ergonomics-in-Workspace-Design.md | 8 +- 10_Wiki/Topics/AI/Error-Boundary-Pattern.md | 8 +- 10_Wiki/Topics/AI/Es-Lint-Configuration.md | 14 +- 10_Wiki/Topics/AI/Escalation-of-Commitment.md | 14 +- 10_Wiki/Topics/AI/Ethical-Decision-Making.md | 12 +- 10_Wiki/Topics/AI/Ethics & AI.md | 14 +- .../Topics/AI/Ethics of Autonomous Systems.md | 6 +- .../AI/Ethics-in-Artificial-Intelligence.md | 8 +- 10_Wiki/Topics/AI/Ethnographic-Research.md | 16 +- 10_Wiki/Topics/AI/Etiology-of-Disease.md | 12 +- .../Topics/AI/Eudaimonia-and-Well-being.md | 12 +- .../Topics/AI/Event-Driven-Architecture.md | 10 +- 10_Wiki/Topics/AI/Evolutionary Biology.md | 6 +- 10_Wiki/Topics/AI/Evolutionary Computation.md | 12 +- .../AI/Evolutionary-Algorithm-Design.md | 14 +- 10_Wiki/Topics/AI/Evolutionary-Algorithms.md | 14 +- 10_Wiki/Topics/AI/Evolutionary-Computation.md | 8 +- 10_Wiki/Topics/AI/Excess-Property-Checking.md | 6 +- 10_Wiki/Topics/AI/Executive Dysfunction.md | 10 +- .../Topics/AI/Executive-Function-Deficit.md | 8 +- 10_Wiki/Topics/AI/Exhaustiveness-Checking.md | 8 +- 10_Wiki/Topics/AI/Expectation-Maximization.md | 8 +- 10_Wiki/Topics/AI/Expected Utility Theory.md | 6 +- 10_Wiki/Topics/AI/Experience-Replay.md | 8 +- .../Topics/AI/Experience-Sampling-Method.md | 14 +- 10_Wiki/Topics/AI/Explainable-AI (XAI).md | 10 +- 10_Wiki/Topics/AI/Explainable-AI-XAI.md | 6 +- .../Topics/AI/Exploding-Gradient Problem.md | 10 +- .../Topics/AI/Exploration vs Exploitation.md | 12 +- .../Topics/AI/Exploration-vs-Exploitation.md | 6 +- .../Topics/AI/Exploratory-Data-Analysis.md | 6 +- 10_Wiki/Topics/AI/Expo 2025 Osaka.md | 12 +- 10_Wiki/Topics/AI/Exponential-Growth.md | 12 +- 10_Wiki/Topics/AI/Extended-Reality-XR.md | 6 +- 10_Wiki/Topics/AI/Externalities.md | 10 +- 10_Wiki/Topics/AI/Extreme-Programming-XP.md | 4 +- .../Topics/AI/Eye-Tracking-in-UX-Research.md | 12 +- 10_Wiki/Topics/AI/Eye-Tracking.md | 14 +- 10_Wiki/Topics/AI/Factor-Analysis.md | 4 +- 10_Wiki/Topics/AI/Factory-Pattern.md | 6 +- 10_Wiki/Topics/AI/Failable-Task-Handling.md | 10 +- 10_Wiki/Topics/AI/Fault-Tolerance.md | 8 +- .../Topics/AI/Feature Clamping (피처 고정).md | 2 +- 10_Wiki/Topics/AI/Feature-Engineering.md | 6 +- 10_Wiki/Topics/AI/Feature-Flags.md | 12 +- 10_Wiki/Topics/AI/Federated-Learning.md | 4 +- 10_Wiki/Topics/AI/Feedback-Control-Systems.md | 6 +- .../Topics/AI/Feedback-Loops in Systems.md | 8 +- 10_Wiki/Topics/AI/Feedback-Loops-in-Design.md | 10 +- 10_Wiki/Topics/AI/Feedback-Loops.md | 12 +- 10_Wiki/Topics/AI/Few-Shot-Learning.md | 6 +- 10_Wiki/Topics/AI/Figma-to-Code-Workflow.md | 12 +- 10_Wiki/Topics/AI/Figurative-Language.md | 6 +- 10_Wiki/Topics/AI/Fine-tuning.md | 8 +- 10_Wiki/Topics/AI/Finished Goods.md | 16 +- 10_Wiki/Topics/AI/Finite-Element-Analysis.md | 4 +- .../Topics/AI/Finite-State-Machines-FSM.md | 8 +- 10_Wiki/Topics/AI/Finite-State-Machines.md | 10 +- 10_Wiki/Topics/AI/First Input Delay (FID).md | 14 +- 10_Wiki/Topics/AI/Fitness-Landscape.md | 4 +- .../Fixed Time Step vs Variable Time Step.md | 2 +- 10_Wiki/Topics/AI/Flow State.md | 6 +- 10_Wiki/Topics/AI/Flow-State.md | 14 +- 10_Wiki/Topics/AI/Fluent-Interface-Design.md | 8 +- 10_Wiki/Topics/AI/Fluid-Dynamics for Games.md | 4 +- 10_Wiki/Topics/AI/Focal-Loss.md | 4 +- 10_Wiki/Topics/AI/Formal Methods.md | 12 +- .../AI/Formal-Verification-of-Software.md | 12 +- 10_Wiki/Topics/AI/Foundation-Models.md | 12 +- .../Topics/AI/Foundational LLM Concepts.md | 8 +- 10_Wiki/Topics/AI/Fragility.md | 18 +- 10_Wiki/Topics/AI/Free-Energy-Principle.md | 8 +- ...ntend-Architecture-and-Folder-Structure.md | 4 +- 10_Wiki/Topics/AI/Frontend-Architecture.md | 6 +- .../AI/Frontend-Debugging-and-Testing.md | 6 +- ...Frontend-Performance-Optimization-Guide.md | 14 +- ...ntend-Team-Collaboration-and-Governance.md | 8 +- 10_Wiki/Topics/AI/Frontend.md | 14 +- 10_Wiki/Topics/AI/Functional Programming.md | 10 +- .../Functional-Programming-in-TypeScript.md | 8 +- 10_Wiki/Topics/AI/Functional-Programming.md | 4 +- 10_Wiki/Topics/AI/Fuzzy-Logic.md | 8 +- 10_Wiki/Topics/AI/G-Stack Principles.md | 2 +- .../Topics/AI/G-Stack-Integration-Guide.md | 6 +- 10_Wiki/Topics/AI/GAN.md | 2 +- 10_Wiki/Topics/AI/GNN.md | 4 +- .../Topics/AI/GPT-Architecture-Foundations.md | 12 +- 10_Wiki/Topics/AI/GPU-Architecture.md | 10 +- .../Topics/AI/GPU-Programming-with-CUDA.md | 8 +- 10_Wiki/Topics/AI/GPU.md | 14 +- 10_Wiki/Topics/AI/GRPO.md | 14 +- 10_Wiki/Topics/AI/GRU.md | 8 +- 10_Wiki/Topics/AI/Gacha Mechanics Analysis.md | 12 +- 10_Wiki/Topics/AI/Gait-Analysis-Laboratory.md | 4 +- .../Topics/AI/Game Analytics (게임 분석).md | 4 +- 10_Wiki/Topics/AI/Game-Balance-Design.md | 6 +- 10_Wiki/Topics/AI/Game-Balance-Modeling.md | 2 +- 10_Wiki/Topics/AI/Game-Design-Ontology.md | 16 +- 10_Wiki/Topics/AI/Game-Design-Theory.md | 10 +- 10_Wiki/Topics/AI/Game-Economy-Design.md | 4 +- 10_Wiki/Topics/AI/Game-Feel-and-Juiciness.md | 6 +- 10_Wiki/Topics/AI/Game-Loop-Architecture.md | 8 +- 10_Wiki/Topics/AI/Game-Mechanics.md | 8 +- 10_Wiki/Topics/AI/Game-Ontology-for-PCG.md | 16 +- 10_Wiki/Topics/AI/Game-Theory-in-AI.md | 8 +- 10_Wiki/Topics/AI/Game-Theory.md | 2 +- 10_Wiki/Topics/AI/Gamification-Strategies.md | 6 +- 10_Wiki/Topics/AI/Gamification-Theory.md | 12 +- 10_Wiki/Topics/AI/Gates.md | 12 +- 10_Wiki/Topics/AI/Gaussian-Processes.md | 10 +- 10_Wiki/Topics/AI/Gen-AI.md | 12 +- 10_Wiki/Topics/AI/Generalization-in-AI.md | 6 +- ...dversarial Networks (GANs) in Fine Arts.md | 6 +- 10_Wiki/Topics/AI/Generative-AI-Impact.md | 6 +- 10_Wiki/Topics/AI/Generative-AI.md | 10 +- .../AI/Generative-Adversarial-Networks.md | 4 +- .../Topics/AI/Generics-and-Polymorphism.md | 14 +- 10_Wiki/Topics/AI/Genetic-Algorithms.md | 6 +- .../AI/Geographic-Information-Systems.md | 14 +- 10_Wiki/Topics/AI/Geometric-Deep-Learning.md | 4 +- 10_Wiki/Topics/AI/Geriatric-Medicine.md | 16 +- 10_Wiki/Topics/AI/Gestalt Psychology.md | 16 +- 10_Wiki/Topics/AI/Gestalt-Principles in UX.md | 4 +- .../Topics/AI/Gestalt-Principles-of-Design.md | 8 +- 10_Wiki/Topics/AI/Gimbals-and-Orientation.md | 6 +- .../Git-Branching-Strategies-and-Workflows.md | 6 +- 10_Wiki/Topics/AI/Git-Version-Control.md | 6 +- 10_Wiki/Topics/AI/GitHub-Actions-CI-CD.md | 4 +- 10_Wiki/Topics/AI/GitLab CI.md | 10 +- 10_Wiki/Topics/AI/GloVe (Word Embeddings).md | 6 +- 10_Wiki/Topics/AI/Global-Standard.md | 12 +- 10_Wiki/Topics/AI/Global-vs-Local-Optima.md | 4 +- 10_Wiki/Topics/AI/Goal-Misgeneralization.md | 16 +- .../AI/Goal-Oriented-Action-Planning.md | 6 +- 10_Wiki/Topics/AI/God-Object-Antipattern.md | 6 +- .../AI/Godel's Incompleteness Theorems.md | 10 +- .../AI/Google-Page-Experience-2025-Update.md | 6 +- .../Topics/AI/Gradient-Boosting-Machines.md | 4 +- 10_Wiki/Topics/AI/Gradient-Descent.md | 8 +- 10_Wiki/Topics/AI/Graph Theory.md | 8 +- 10_Wiki/Topics/AI/Graph-Coloring-Problem.md | 14 +- 10_Wiki/Topics/AI/Graph-Database.md | 4 +- 10_Wiki/Topics/AI/Graph-Theory.md | 6 +- 10_Wiki/Topics/AI/GraphQL-Code-Generator.md | 16 +- .../AI/GraphRAG & Knowledge Graph Memory.md | 8 +- .../GraphRAG (그래프 기반 검색 증강 생성).md | 10 +- 10_Wiki/Topics/AI/Greedy-Algorithms.md | 8 +- 10_Wiki/Topics/AI/Grit.md | 14 +- 10_Wiki/Topics/AI/Grounded Theory Method.md | 10 +- .../Topics/AI/Growth-Mindset-Intervention.md | 14 +- 10_Wiki/Topics/AI/Growth-Mindset.md | 16 +- .../AI/Guilty-Gear-Xrd-Rendering-Pipeline.md | 10 +- 10_Wiki/Topics/AI/HANDOVER.md | 16 +- 10_Wiki/Topics/AI/HBO-Prestige-Television.md | 12 +- .../AI/HCI (Human-Computer Interaction).md | 12 +- 10_Wiki/Topics/AI/HHH.md | 16 +- 10_Wiki/Topics/AI/HMM.md | 8 +- 10_Wiki/Topics/AI/Habit-Formation.md | 6 +- 10_Wiki/Topics/AI/Hallucination (환각).md | 16 +- 10_Wiki/Topics/AI/Hallucination-in-LLM.md | 12 +- 10_Wiki/Topics/AI/Hallucination-in-LLMs.md | 8 +- .../Topics/AI/Hardware-Acceleration-for-AI.md | 10 +- 10_Wiki/Topics/AI/Hardware-Verification.md | 16 +- 10_Wiki/Topics/AI/Hardware.md | 14 +- 10_Wiki/Topics/AI/Hash-Functions-and-Maps.md | 6 +- 10_Wiki/Topics/AI/Health-Informatics.md | 16 +- 10_Wiki/Topics/AI/Hebbian-Learning.md | 4 +- 10_Wiki/Topics/AI/Hebbian-Theory.md | 12 +- 10_Wiki/Topics/AI/Heuristic-Search.md | 4 +- 10_Wiki/Topics/AI/Heuristics.md | 14 +- .../AI/Hierarchical-Task-Network (HTN).md | 6 +- .../Topics/AI/High-Availability-Systems.md | 8 +- .../Topics/AI/High-Cohesion-Low-Coupling.md | 14 +- .../AI/High-Frequency-Trading-Models.md | 12 +- .../AI/High-Performance Computing (HPC).md | 14 +- .../Topics/AI/High-Performance-Coaching.md | 16 +- .../AI/High-Performance-Organizations.md | 20 +- .../AI/High-Performance-Sports-Science.md | 16 +- 10_Wiki/Topics/AI/Homeostasis (항상성).md | 14 +- 10_Wiki/Topics/AI/Homeostasis.md | 14 +- 10_Wiki/Topics/AI/Homomorphic-Encryption.md | 4 +- 10_Wiki/Topics/AI/Human Centered AI (HCAI).md | 12 +- 10_Wiki/Topics/AI/Human-AI-Collaboration.md | 2 +- .../AI/Human-Computer-Interaction-HCI.md | 8 +- .../Topics/AI/Human-Computer-Interaction.md | 12 +- 10_Wiki/Topics/AI/Human-in-the-loop (HITL).md | 8 +- 10_Wiki/Topics/AI/Human-in-the-loop-AI.md | 4 +- .../Topics/AI/Hybrid-Cloud-Architectures.md | 6 +- .../Hydration-Mismatch-and-SSR-Debugging.md | 10 +- .../Hyperinflation-in-Closed-Loop-Systems.md | 12 +- .../Topics/AI/Hyperparameter-Optimization.md | 6 +- 10_Wiki/Topics/AI/Hyperparameters.md | 16 +- 10_Wiki/Topics/AI/Hypostatic-Abstraction.md | 10 +- 10_Wiki/Topics/AI/Hypothesis-Testing.md | 4 +- 10_Wiki/Topics/AI/ICRE-Framework.md | 12 +- ...DE (Integrated Development Environment).md | 8 +- 10_Wiki/Topics/AI/IEEE-P36521.md | 14 +- 10_Wiki/Topics/AI/ISO-Standard.md | 10 +- 10_Wiki/Topics/AI/Ikigai (이키가이).md | 12 +- .../Topics/AI/Image-Classification-Mastery.md | 10 +- .../Image-Optimization-for-Web-Performance.md | 4 +- .../AI/Image-Segmentation-Techniques.md | 4 +- 10_Wiki/Topics/AI/Image-Segmentation.md | 6 +- 10_Wiki/Topics/AI/Imbalanced-Data-Handling.md | 6 +- 10_Wiki/Topics/AI/Imitation-Learning.md | 10 +- 10_Wiki/Topics/AI/Immersive-Sim-Design.md | 16 +- 10_Wiki/Topics/AI/Immersive-Sim-Genre.md | 12 +- .../AI/Immersive-Sims-Deus-Ex-Dishonored.md | 16 +- .../Topics/AI/Immersive-Sims-Deus-Ex-Thief.md | 10 +- 10_Wiki/Topics/AI/Immutability-Patterns.md | 14 +- 10_Wiki/Topics/AI/Impedance-Matching.md | 10 +- 10_Wiki/Topics/AI/In-Context-Learning.md | 6 +- 10_Wiki/Topics/AI/Inclusive-Design-and-UX.md | 6 +- 10_Wiki/Topics/AI/Incremental-Computation.md | 14 +- 10_Wiki/Topics/AI/Incremental-Learning.md | 6 +- .../AI/Incremental-Static-Regeneration-ISR.md | 4 +- 10_Wiki/Topics/AI/Incrementalism.md | 12 +- .../Independent Component Analysis (ICA).md | 10 +- .../AI/Independent-Component-Analysis.md | 6 +- .../Topics/AI/Index-Fragmentation-Analysis.md | 16 +- 10_Wiki/Topics/AI/Index.md | 2942 ++++++++--------- 10_Wiki/Topics/AI/Indexing-Strategies.md | 6 +- 10_Wiki/Topics/AI/Indian-Innovation-Models.md | 14 +- 10_Wiki/Topics/AI/Inductive-Bias.md | 2 +- 10_Wiki/Topics/AI/Inductive-Reasoning.md | 16 +- 10_Wiki/Topics/AI/Inexact-Science.md | 14 +- .../AI/Inference-Coupled Persistence.md | 8 +- 10_Wiki/Topics/AI/Inference-Optimization.md | 10 +- 10_Wiki/Topics/AI/Inferential-Statistics.md | 14 +- 10_Wiki/Topics/AI/Information-Entropy.md | 14 +- 10_Wiki/Topics/AI/Information-Retrieval-IR.md | 4 +- 10_Wiki/Topics/AI/Information-Society.md | 14 +- 10_Wiki/Topics/AI/Information-Theory.md | 2 +- 10_Wiki/Topics/AI/Infraspace.md | 16 +- .../Topics/AI/Infrastructure-as-Code-IaC.md | 6 +- .../Topics/AI/Inheritance-and-Polymorphism.md | 2 +- 10_Wiki/Topics/AI/Inner-Product-Spaces.md | 4 +- 10_Wiki/Topics/AI/Innovation.md | 14 +- .../Topics/AI/Input-Validation-Strategies.md | 4 +- 10_Wiki/Topics/AI/Inquiry-Based Learning.md | 10 +- 10_Wiki/Topics/AI/Instance-based-Learning.md | 6 +- 10_Wiki/Topics/AI/InstancedMesh2 library.md | 14 +- 10_Wiki/Topics/AI/Instinct.md | 10 +- 10_Wiki/Topics/AI/Instruction-Tuning.md | 10 +- 10_Wiki/Topics/AI/Intangible-Capital.md | 10 +- .../AI/Integrated-Development-Environment.md | 4 +- .../Topics/AI/Integration-Testing-for-AI.md | 4 +- .../Topics/AI/Intellectual-Property-in-AI.md | 4 +- .../AI/Interaction to Next Paint (INP).md | 22 +- .../AI/Interaction-to-Next-Paint-INP.md | 14 +- .../Topics/AI/Interdisciplinary-Research.md | 16 +- .../AI/Interface-Segregation-Principle.md | 8 +- 10_Wiki/Topics/AI/Internet of Things (IoT).md | 8 +- 10_Wiki/Topics/AI/Interop 2026.md | 12 +- 10_Wiki/Topics/AI/Interoperability.md | 16 +- .../AI/Interpretability-vs-Explainability.md | 4 +- .../Topics/AI/Introduction-to-Programming.md | 14 +- 10_Wiki/Topics/AI/Introspection (자기성찰).md | 14 +- 10_Wiki/Topics/AI/Inverse-Kinematics.md | 8 +- .../AI/Inverse-Reinforcement-Learning.md | 8 +- 10_Wiki/Topics/AI/Inversion.md | 18 +- 10_Wiki/Topics/AI/IoT-and-AI-Integration.md | 8 +- .../AI/Isaac-Asimovs-Laws-of-Robotics.md | 4 +- .../AI/Item-Item-Collaborative-Filtering.md | 4 +- 10_Wiki/Topics/AI/Iteration.md | 14 +- .../Topics/AI/Iterative-Development-Models.md | 10 +- 10_Wiki/Topics/AI/Iterative-Development.md | 12 +- .../AI/JIT-Compilation-in-AI-Engines.md | 4 +- 10_Wiki/Topics/AI/JSON-LD-Structured-Data.md | 6 +- .../Topics/AI/JSON-and-Data-Serialization.md | 4 +- .../Topics/AI/JUnit-and-Testing-Frameworks.md | 4 +- .../AI/JavaScript-Async-and-Event-Loop.md | 8 +- .../AI/JavaScript-Optimization-Patterns.md | 10 +- 10_Wiki/Topics/AI/Joint-Optimization.md | 12 +- 10_Wiki/Topics/AI/Journaling.md | 12 +- 10_Wiki/Topics/AI/Judgment.md | 14 +- 10_Wiki/Topics/AI/Just-In-Time (JIT).md | 12 +- 10_Wiki/Topics/AI/Just-in-Case.md | 16 +- .../Topics/AI/Just-in-time-Data-Loading.md | 6 +- .../AI/K-Means-Clustering-Foundations.md | 8 +- 10_Wiki/Topics/AI/K-Nearest-Neighbors-K-NN.md | 10 +- .../AI/KISS (Keep It Simple, Stupid).md | 10 +- .../AI/KISS-Principle-in-Software-Design.md | 4 +- .../AI/KPI (Key Performance Indicator).md | 12 +- .../AI/Kalman-Filter-and-State-Tracking.md | 6 +- .../AI/Kernel-Density-Estimation-KDE.md | 6 +- 10_Wiki/Topics/AI/Kernel-Methods-and-SVMs.md | 6 +- 10_Wiki/Topics/AI/Knowledge synthesis.md | 16 +- 10_Wiki/Topics/AI/Knowledge-Distillation.md | 8 +- .../Topics/AI/Knowledge-Graph-Foundations.md | 6 +- 10_Wiki/Topics/AI/Knowledge-Graph.md | 8 +- .../AI/Knowledge-Representation-in-AI.md | 16 +- 10_Wiki/Topics/AI/Knowledge-Structure.md | 16 +- 10_Wiki/Topics/AI/Kolmogorov-Complexity.md | 4 +- .../AI/Kubernetes-for-AI-Orchestration.md | 4 +- .../Topics/AI/Kullback-Leibler-Divergence.md | 12 +- 10_Wiki/Topics/AI/L1-and-L2-Regularization.md | 6 +- 10_Wiki/Topics/AI/L2-Regularization.md | 12 +- 10_Wiki/Topics/AI/LLM-Security-and-Safety.md | 6 +- 10_Wiki/Topics/AI/LLM.md | 14 +- 10_Wiki/Topics/AI/LOD.md | 12 +- .../AI/LSTM (Long Short-Term Memory).md | 10 +- 10_Wiki/Topics/AI/LSTM.md | 6 +- .../Topics/AI/Label-Noise-and-Robustness.md | 6 +- 10_Wiki/Topics/AI/Lagrange-Multipliers.md | 6 +- 10_Wiki/Topics/AI/Language-Models.md | 14 +- .../Topics/AI/Large Language Models (LLM).md | 14 +- ...scale-Application-Architecture-Patterns.md | 10 +- .../AI/Largest Contentful Paint (LCP).md | 18 +- .../Topics/AI/Largest-Contentful-Paint-LCP.md | 12 +- .../Topics/AI/Latent-Dirichlet-Allocation.md | 6 +- .../Topics/AI/Latent-Semantic-Analysis-LSA.md | 8 +- 10_Wiki/Topics/AI/Layer-Normalization.md | 10 +- .../AI/Layered-Architecture-in-Frontend.md | 10 +- 10_Wiki/Topics/AI/Lazy-Loading-Strategies.md | 6 +- 10_Wiki/Topics/AI/Leadership.md | 16 +- .../Topics/AI/Leaky-ReLU-and-Activations.md | 4 +- 10_Wiki/Topics/AI/Lean-Operations.md | 14 +- 10_Wiki/Topics/AI/Lean-Project-Management.md | 6 +- 10_Wiki/Topics/AI/Learning-Paths.md | 14 +- 10_Wiki/Topics/AI/Learning-Rate-Schedules.md | 4 +- 10_Wiki/Topics/AI/Learning-Rate-Scheduling.md | 4 +- 10_Wiki/Topics/AI/Least-Squares-Methods.md | 4 +- 10_Wiki/Topics/AI/Legacy-Systems.md | 14 +- 10_Wiki/Topics/AI/Lessons Learned.md | 14 +- 10_Wiki/Topics/AI/Level of Detail (LOD).md | 14 +- 10_Wiki/Topics/AI/Levels of Understanding.md | 16 +- .../Topics/AI/Linear-Algebra-Foundations.md | 4 +- 10_Wiki/Topics/AI/Linear-Algebra-for-ML.md | 4 +- 10_Wiki/Topics/AI/Linear-Algebra.md | 10 +- .../Topics/AI/Linear-Discriminant-Analysis.md | 6 +- 10_Wiki/Topics/AI/Linear-Programming.md | 10 +- .../Topics/AI/Linear-Regression-Mastery.md | 6 +- .../Topics/AI/Linguistic-Analysis-in-AI.md | 8 +- 10_Wiki/Topics/AI/Linked-Lists-and-Trees.md | 10 +- 10_Wiki/Topics/AI/Linux-Performance-Tuning.md | 8 +- 10_Wiki/Topics/AI/Liquid-Democracy.md | 2 +- .../AI/Liskov-Substitution-Principle.md | 10 +- 10_Wiki/Topics/AI/LlamaIndex.md | 2 +- .../Topics/AI/LoRA (Low-Rank Adaptation).md | 10 +- .../Topics/AI/Load-Balancing-Strategies.md | 4 +- 10_Wiki/Topics/AI/Local-Brain-Management.md | 8 +- 10_Wiki/Topics/AI/Local-Search.md | 14 +- .../AI/Locality-Sensitive-Hashing (LSH).md | 12 +- .../Topics/AI/Locality-Sensitive-Hashing.md | 4 +- 10_Wiki/Topics/AI/Logic.md | 10 +- .../AI/Logistic-Regression-Foundations.md | 6 +- 10_Wiki/Topics/AI/Logistic-Regression.md | 12 +- .../Topics/AI/Long Animation Frames API.md | 14 +- 10_Wiki/Topics/AI/Long Tasks.md | 14 +- .../AI/Long-Short-Term-Memory (LSTM).md | 12 +- 10_Wiki/Topics/AI/Long-Short-Term-Memory.md | 12 +- 10_Wiki/Topics/AI/Long-Tail.md | 10 +- 10_Wiki/Topics/AI/Loose-Coupling.md | 12 +- 10_Wiki/Topics/AI/Loss Functions.md | 16 +- .../Topics/AI/Loss-Functions-Foundations.md | 8 +- 10_Wiki/Topics/AI/Low-Rank-Adaptation-LoRA.md | 6 +- 10_Wiki/Topics/AI/Lubrication.md | 20 +- 10_Wiki/Topics/AI/Lucas-Kanade-Method.md | 4 +- 10_Wiki/Topics/AI/MAP-Estimation.md | 14 +- ...MBA (Master of Business Administration).md | 16 +- .../Topics/AI/MCP (Model Context Protocol).md | 10 +- 10_Wiki/Topics/AI/MCP.md | 10 +- 10_Wiki/Topics/AI/MLA-Format.md | 12 +- 10_Wiki/Topics/AI/MLOps.md | 8 +- 10_Wiki/Topics/AI/Machine Learning (ML).md | 8 +- .../Topics/AI/Machine-Learning-Foundations.md | 6 +- .../Topics/AI/Machine-Learning-Lifecycle.md | 4 +- 10_Wiki/Topics/AI/Macros (매크로).md | 10 +- 10_Wiki/Topics/AI/Magic-Circle.md | 6 +- 10_Wiki/Topics/AI/Main Thread.md | 16 +- 10_Wiki/Topics/AI/Malware-Analysis.md | 10 +- 10_Wiki/Topics/AI/Management.md | 16 +- 10_Wiki/Topics/AI/Manhattan-Distance.md | 4 +- 10_Wiki/Topics/AI/MapReduce.md | 16 +- 10_Wiki/Topics/AI/Markov-Chain-Monte-Carlo.md | 4 +- 10_Wiki/Topics/AI/Markov-Chains.md | 16 +- .../AI/Markov-Decision-Process (MDP).md | 10 +- .../Topics/AI/Markov-Decision-Process-MDP.md | 8 +- .../Topics/AI/Markov-Decision-Processes.md | 16 +- .../AI/Master-of-Information-Management.md | 20 +- 10_Wiki/Topics/AI/Mastery.md | 14 +- 10_Wiki/Topics/AI/Matrix-Factorization.md | 4 +- 10_Wiki/Topics/AI/Matrix-Operations-and-AI.md | 6 +- 10_Wiki/Topics/AI/Mean-Absolute-Error-MAE.md | 8 +- 10_Wiki/Topics/AI/Mean-Squared-Error-MSE.md | 4 +- ...c Interpretability (기계적 해석 가능성).md | 12 +- 10_Wiki/Topics/AI/Media-Literacy.md | 14 +- .../AI/Medical-Imaging-Data-Augmentation.md | 16 +- 10_Wiki/Topics/AI/Memetics.md | 10 +- 10_Wiki/Topics/AI/Memory-Hierarchy.md | 14 +- .../AI/Memory-Leak-Debugging-in-JavaScript.md | 10 +- 10_Wiki/Topics/AI/Mental-Models.md | 16 +- .../AI/Mental-Operations-Synthesized.md | 18 +- .../AI/Message-Queues-and-Event-Streams.md | 4 +- 10_Wiki/Topics/AI/Meta-Learning-in-AI.md | 4 +- .../Micro-interactions-and-Feedback-Loops.md | 4 +- 10_Wiki/Topics/AI/Micro-interactions.md | 8 +- .../Topics/AI/Microservices-Architecture.md | 6 +- 10_Wiki/Topics/AI/Middle-Out-Thinking.md | 18 +- 10_Wiki/Topics/AI/Minimal-Viable-Product.md | 14 +- .../Topics/AI/Minimum-Viable-Product-MVP.md | 6 +- 10_Wiki/Topics/AI/Mipmap.md | 10 +- 10_Wiki/Topics/AI/Mobile-AI-Optimization.md | 8 +- 10_Wiki/Topics/AI/Mobile-Augmented-Reality.md | 14 +- ...bile-First-Responsive-Design-Principles.md | 10 +- .../Topics/AI/Model Context Protocol (MCP).md | 8 +- .../Topics/AI/Model-Agnostic-Meta-Learning.md | 4 +- .../Topics/AI/Model-Compression-Strategies.md | 8 +- 10_Wiki/Topics/AI/Model-Compression.md | 14 +- .../Topics/AI/Model-Deployment-Patterns.md | 8 +- .../Topics/AI/Model-Drift-and-Monitoring.md | 8 +- 10_Wiki/Topics/AI/Model-Ensemble-Methods.md | 6 +- .../Topics/AI/Model-Interpretability-Tools.md | 4 +- .../AI/Model-Predictive-Control (MPC).md | 8 +- ...odern-Frontend-Engineering-Architecture.md | 12 +- ...React-Application-Architecture-Patterns.md | 12 +- .../Modern-Web-Design-Best-Practices-2025.md | 8 +- .../Topics/AI/Modern-Website-Architecture.md | 12 +- 10_Wiki/Topics/AI/Modular-Design.md | 12 +- 10_Wiki/Topics/AI/Modular-Programming.md | 12 +- 10_Wiki/Topics/AI/Modularity.md | 12 +- .../Topics/AI/Momentum-and-Optimization.md | 4 +- .../Topics/AI/Monolithic-vs-Microservices.md | 8 +- 10_Wiki/Topics/AI/Monte-Carlo-Integration.md | 4 +- 10_Wiki/Topics/AI/Monte-Carlo-Methods.md | 14 +- .../Topics/AI/Monte-Carlo-Tree-Search-MCTS.md | 6 +- .../AI/Multi-Agent-Reinforcement-Learning.md | 6 +- 10_Wiki/Topics/AI/Multi-Agent-Systems-MAS.md | 12 +- .../AI/Multi-Head-Attention-Mechanism.md | 4 +- 10_Wiki/Topics/AI/Multi-Modal-Learning.md | 6 +- 10_Wiki/Topics/AI/Multi-agent-System.md | 14 +- .../Topics/AI/Multi-armed-Bandit-Problem.md | 4 +- .../Topics/AI/Multilayer-Perceptron-MLP.md | 2 +- 10_Wiki/Topics/AI/Multimodal-Learning.md | 14 +- 10_Wiki/Topics/AI/Multinomial-Naive-Bayes.md | 8 +- 10_Wiki/Topics/AI/Multivariate-Analysis.md | 4 +- 10_Wiki/Topics/AI/Mutual-Information.md | 4 +- .../AI/NLP (Natural Language Processing).md | 20 +- 10_Wiki/Topics/AI/NLP-Attention-Mechanisms.md | 8 +- 10_Wiki/Topics/AI/NVIDIA-CUDA-and-AI.md | 8 +- 10_Wiki/Topics/AI/Naive-Bayes-Classifiers.md | 2 +- .../Topics/AI/Named-Entity-Recognition-NER.md | 6 +- .../Topics/AI/National-Language-Processing.md | 6 +- .../AI/Natural-Language-Generation-NLG.md | 6 +- .../AI/Natural-Language-Processing-NLP.md | 8 +- .../Topics/AI/Natural-Language-Processing.md | 8 +- 10_Wiki/Topics/AI/Nearest-Neighbor-Search.md | 8 +- .../Topics/AI/Network-Latency-Optimization.md | 8 +- .../AI/Neural-Architecture-Search-NAS.md | 10 +- .../Topics/AI/Neural-Architecture-Search.md | 10 +- 10_Wiki/Topics/AI/Neural-Darwinism.md | 2 +- .../AI/Neural-Networks (신경망 기초).md | 6 +- .../AI/Neural-Networks-for-Beginners.md | 6 +- 10_Wiki/Topics/AI/Neural-Style-Transfer.md | 8 +- .../Topics/AI/Neural-Symbolic-Integration.md | 10 +- 10_Wiki/Topics/AI/Neuro-Symbolic AI.md | 12 +- 10_Wiki/Topics/AI/Neuro-Symbolic-AI.md | 8 +- 10_Wiki/Topics/AI/Neurobiology-of-Reward.md | 12 +- .../Topics/AI/Neurodevelopmental Disorders.md | 8 +- 10_Wiki/Topics/AI/Neuroeconomics.md | 10 +- 10_Wiki/Topics/AI/Neuroergonomics.md | 8 +- 10_Wiki/Topics/AI/Neuroevolution.md | 4 +- 10_Wiki/Topics/AI/Neuromuscular-Adaptation.md | 6 +- 10_Wiki/Topics/AI/Neuromuscular-Control.md | 10 +- ...pharmacology of Substance Use Disorders.md | 6 +- .../Topics/AI/Neuroplasticity in Addiction.md | 8 +- .../AI/Neuroplasticity in Motor Learning.md | 8 +- .../AI/Neuroplasticity-in-Motor-Learning.md | 6 +- .../Topics/AI/Neuroprosthetics-Development.md | 8 +- .../Topics/AI/Neuropsychiatric Disorders.md | 10 +- 10_Wiki/Topics/AI/Neuropsychology.md | 10 +- .../AI/Neurorehabilitation after Stroke.md | 8 +- .../AI/Neurorehabilitation-Post-Stroke.md | 8 +- 10_Wiki/Topics/AI/Next-js-and-Modern-Web.md | 10 +- .../AI/Nextjs-App-Router-Architecture.md | 12 +- ... Sky (Large-scale planetary generation).md | 12 +- 10_Wiki/Topics/AI/No Mans Sky.md | 8 +- 10_Wiki/Topics/AI/NoSQL-Databases-in-AI.md | 6 +- 10_Wiki/Topics/AI/Nodejs 메모리 누수 분석.md | 22 +- .../AI/Nodejs 프로덕션 메모리 누수 진단.md | 16 +- .../AI/Nodejs 프로덕션 메모리 병목 분석.md | 20 +- .../Nodejs-Global-Namespace-Augmentation.md | 8 +- 10_Wiki/Topics/AI/Noise-Reduction-in-AI.md | 10 +- 10_Wiki/Topics/AI/Noise.md | 16 +- .../Topics/AI/Nominal-Typing-in-TypeScript.md | 12 +- ...hotorealistic-Rendering-in-Level-Design.md | 10 +- .../AI/Non-linear-Activation-Functions.md | 4 +- 10_Wiki/Topics/AI/Non-parametric-Models.md | 8 +- 10_Wiki/Topics/AI/Normalization-Strategies.md | 6 +- 10_Wiki/Topics/AI/Normalization.md | 10 +- .../Topics/AI/Nuclear Deterrence Models.md | 10 +- 10_Wiki/Topics/AI/Numbers-and-Games.md | 12 +- 10_Wiki/Topics/AI/Nutritional-Biochemistry.md | 8 +- 10_Wiki/Topics/AI/OKR.md | 16 +- ...WA vs CWA (개방 세계 vs 폐쇄 세계 가설).md | 8 +- .../AI/Object Pooling (오브젝트 풀링).md | 12 +- .../Topics/AI/Object-Detection-Foundations.md | 4 +- .../AI/Object-Oriented-Design-Patterns.md | 10 +- .../Topics/AI/Object-Oriented-Programming.md | 2 +- 10_Wiki/Topics/AI/Objective-Functions.md | 6 +- 10_Wiki/Topics/AI/Objectivism.md | 10 +- 10_Wiki/Topics/AI/Observation.md | 16 +- 10_Wiki/Topics/AI/Occupational-Therapy.md | 6 +- .../AI/Off-policy-vs-On-policy-Learning.md | 6 +- .../Topics/AI/Okami-Ink-Wash-Aesthetics.md | 8 +- 10_Wiki/Topics/AI/Olympic-Training-Cycles.md | 6 +- 10_Wiki/Topics/AI/Olympic-Training-Models.md | 6 +- .../Topics/AI/Olympic-Training-Protocols.md | 10 +- 10_Wiki/Topics/AI/One-Hot-Encoding.md | 6 +- 10_Wiki/Topics/AI/One-Shot-Learning.md | 6 +- .../AI/Online-Learning-and-Streaming.md | 8 +- 10_Wiki/Topics/AI/Ontological-Engineering.md | 10 +- .../AI/Ontology-Driven-Relevancy-Filtering.md | 10 +- 10_Wiki/Topics/AI/Ontology-Engineering.md | 10 +- .../Ontology-Guided Knowledge Extraction.md | 12 +- .../Ontology-and-Knowledge-Representation.md | 6 +- 10_Wiki/Topics/AI/Ontology.md | 12 +- 10_Wiki/Topics/AI/Opaque-Types.md | 10 +- 10_Wiki/Topics/AI/Open-Access-Movement.md | 6 +- 10_Wiki/Topics/AI/Open-Source-AI-Ecosystem.md | 6 +- 10_Wiki/Topics/AI/OpenAI-API-Integration.md | 6 +- 10_Wiki/Topics/AI/Operations-Management.md | 8 +- 10_Wiki/Topics/AI/Operations-Research.md | 10 +- 10_Wiki/Topics/AI/Operator-Theory.md | 10 +- 10_Wiki/Topics/AI/Opportunity-Cost.md | 14 +- .../AI/Optical-Character-Recognition.md | 8 +- 10_Wiki/Topics/AI/Optimal-Control-Theory.md | 6 +- 10_Wiki/Topics/AI/Optimization-Algorithms.md | 10 +- 10_Wiki/Topics/AI/Optimization-in-AI.md | 6 +- 10_Wiki/Topics/AI/Optimization.md | 14 +- 10_Wiki/Topics/AI/Ordinal-Data-Analysis.md | 4 +- .../Topics/AI/Organizational Psychology.md | 10 +- .../AI/Out-of-distribution-Detection.md | 4 +- .../AI/Outer Alignment vs Inner Alignment.md | 12 +- .../Topics/AI/Outlier-Detection-Techniques.md | 6 +- 10_Wiki/Topics/AI/Outside-Thinking.md | 14 +- .../Topics/AI/Overfitting-and-Underfitting.md | 4 +- 10_Wiki/Topics/AI/Overfitting.md | 14 +- .../Topics/AI/P-Reinforce-Template-Guide.md | 4 +- 10_Wiki/Topics/AI/P-Reinforce.md | 18 +- .../Topics/AI/PCA-and-Dimension-Reduction.md | 4 +- 10_Wiki/Topics/AI/PCGML-Frameworks.md | 12 +- 10_Wiki/Topics/AI/PDF-Format.md | 12 +- .../PEFT (Parameter-Efficient Fine-Tuning).md | 12 +- 10_Wiki/Topics/AI/PEV_Loop.md | 10 +- 10_Wiki/Topics/AI/PID-Controllers-in-AI.md | 4 +- 10_Wiki/Topics/AI/PMI-Technique.md | 12 +- 10_Wiki/Topics/AI/POMDP.md | 14 +- 10_Wiki/Topics/AI/PageSpeed Insights.md | 12 +- ...Papers Please (Bureaucratic Simulation).md | 8 +- 10_Wiki/Topics/AI/Papers-Please.md | 10 +- 10_Wiki/Topics/AI/Parallel-Computing-in-AI.md | 4 +- 10_Wiki/Topics/AI/Parallel-Computing.md | 6 +- 10_Wiki/Topics/AI/Parallel-Processing.md | 10 +- .../Topics/AI/Parameter-Efficiency-in-LLMs.md | 8 +- .../Parameter-Efficient Fine-Tuning (PEFT).md | 10 +- 10_Wiki/Topics/AI/Parameter-Sharing.md | 6 +- 10_Wiki/Topics/AI/Pareto-Principle.md | 12 +- .../AI/Partial-Differential-Equations.md | 4 +- .../Topics/AI/Particle-Filter-Algorithms.md | 4 +- 10_Wiki/Topics/AI/Pattern-Recognition.md | 4 +- 10_Wiki/Topics/AI/Pedestrian-Modeling.md | 8 +- 10_Wiki/Topics/AI/Perceptrons-Foundations.md | 6 +- 10_Wiki/Topics/AI/Perceptual-Learning.md | 6 +- 10_Wiki/Topics/AI/Perceptual-Motor-Skills.md | 8 +- .../AI/Performance Management Systems.md | 12 +- 10_Wiki/Topics/AI/Performance Psychology.md | 10 +- .../Topics/AI/Performance-Metrics-in-AI.md | 4 +- 10_Wiki/Topics/AI/Periodization-Theory.md | 8 +- .../Topics/AI/Personal-Brain-Management.md | 4 +- .../AI/Personal-Information-Security.md | 2 +- 10_Wiki/Topics/AI/Personalization-Engines.md | 6 +- .../AI/Phase-Transitions-in-Learning.md | 6 +- 10_Wiki/Topics/AI/Philosophy.md | 12 +- 10_Wiki/Topics/AI/Physical-Intelligence.md | 16 +- ...hysics-Informed Neural Networks (PINNs).md | 8 +- .../AI/Physics-informed-Neural-Networks.md | 8 +- 10_Wiki/Topics/AI/Physics.md | 12 +- 10_Wiki/Topics/AI/Pipeline-Parallelism.md | 6 +- 10_Wiki/Topics/AI/Pivot-Table-Analysis.md | 4 +- 10_Wiki/Topics/AI/Platform-Engineering.md | 8 +- .../Topics/AI/Player-Experience-Modeling.md | 18 +- .../AI/Player-Psyche-Profiling-Framework.md | 8 +- .../Topics/AI/Plutchiks-Wheel-of-Emotions.md | 14 +- 10_Wiki/Topics/AI/Poetic-Computation.md | 8 +- 10_Wiki/Topics/AI/Point-Cloud-Processing.md | 8 +- 10_Wiki/Topics/AI/Point-of-Sale.md | 14 +- 10_Wiki/Topics/AI/Policy-Gradient-Methods.md | 8 +- 10_Wiki/Topics/AI/Policy-Optimization.md | 10 +- 10_Wiki/Topics/AI/Policy-Surveillance.md | 6 +- 10_Wiki/Topics/AI/PolicyIQ.md | 8 +- .../AI/Polymorphism-in-Engine-Architecture.md | 16 +- 10_Wiki/Topics/AI/Pooling.md | 12 +- 10_Wiki/Topics/AI/Pose-Estimation.md | 4 +- 10_Wiki/Topics/AI/Positive-Reinforcement.md | 4 +- .../AI/Posterior-and-Prior-Probability.md | 4 +- 10_Wiki/Topics/AI/Poverty-Cycle-Dynamics.md | 8 +- 10_Wiki/Topics/AI/Poverty-Simulation.md | 8 +- 10_Wiki/Topics/AI/Practical-Cryptography.md | 12 +- 10_Wiki/Topics/AI/Pre-Mortem-Analysis.md | 10 +- .../Topics/AI/Pre-processing-Data-for-AI.md | 6 +- .../Topics/AI/Precision-Recall-Tradeoff.md | 2 +- 10_Wiki/Topics/AI/Precision-Recursion.md | 14 +- 10_Wiki/Topics/AI/Predictive-Analytics.md | 6 +- 10_Wiki/Topics/AI/Predictive-Coding.md | 6 +- 10_Wiki/Topics/AI/Prenatal-Neurology.md | 6 +- .../Preserving-State-in-Procedural-Worlds.md | 16 +- .../Topics/AI/Principal-Component-Analysis.md | 4 +- .../Topics/AI/Principle-Component-Analysis.md | 16 +- .../Topics/AI/Principle-of-Least-Action.md | 4 +- ...rinciples of Structuralism (Linguistic).md | 8 +- .../Topics/AI/Principles-of-Architecture.md | 16 +- .../Topics/AI/Principles-of-Data-Connect.md | 8 +- .../Topics/AI/Principles-of-Structuralism.md | 10 +- 10_Wiki/Topics/AI/Principles.md | 12 +- .../AI/Prioritized-Experience-Replay.md | 4 +- 10_Wiki/Topics/AI/Prisoners-Dilemma-Models.md | 10 +- .../Topics/AI/Prisons-and-Self-Correction.md | 14 +- 10_Wiki/Topics/AI/Privacy-Preserving-AI.md | 4 +- .../AI/Probabilistic-Graphical-Models.md | 4 +- 10_Wiki/Topics/AI/Probabilistic-Reasoning.md | 12 +- 10_Wiki/Topics/AI/Probability Theory.md | 8 +- .../Topics/AI/Probability and Logic Fusion.md | 10 +- .../AI/Probability-Theory-Foundations.md | 10 +- 10_Wiki/Topics/AI/Problem-Solving.md | 20 +- ...Generation via Machine Learning (PCGML).md | 10 +- .../AI/Procedural Narrative Generation.md | 6 +- .../AI/Procedural Rhetoric (In Gaming).md | 8 +- .../AI/Procedural-Architecture-Systems.md | 10 +- 10_Wiki/Topics/AI/Procedural-Knowledge.md | 14 +- .../Topics/AI/Procedural-Level-Geometry.md | 10 +- 10_Wiki/Topics/AI/Procedural-Rhetoric.md | 8 +- .../Topics/AI/Process-Automation-with-AI.md | 4 +- 10_Wiki/Topics/AI/Processing.md | 12 +- 10_Wiki/Topics/AI/Product-Led-Growth.md | 12 +- 10_Wiki/Topics/AI/Product-Management.md | 14 +- 10_Wiki/Topics/AI/Product-Marketing.md | 10 +- 10_Wiki/Topics/AI/Product-Thinking-in-AI.md | 6 +- .../Topics/AI/Productivity-Hacks-for-Devs.md | 8 +- .../Topics/AI/Profiling-and-Optimization.md | 6 +- 10_Wiki/Topics/AI/Progressive-Disclosure.md | 6 +- .../AI/Project-Management-Best-Practices.md | 8 +- 10_Wiki/Topics/AI/Project-Management.md | 16 +- 10_Wiki/Topics/AI/Prompt Engineering.md | 10 +- .../AI/Prompt-Engineering-Foundations.md | 8 +- 10_Wiki/Topics/AI/Prompt-Engineering.md | 10 +- 10_Wiki/Topics/AI/Proprioception.md | 10 +- 10_Wiki/Topics/AI/Pros-Cons-Table.md | 12 +- 10_Wiki/Topics/AI/Protocols.md | 12 +- 10_Wiki/Topics/AI/Prototyping.md | 12 +- .../AI/Proximal Policy Optimization (PPO).md | 10 +- .../Topics/AI/Proximal-Policy-Optimization.md | 8 +- 10_Wiki/Topics/AI/Pruning-Techniques.md | 6 +- .../AI/Ps-Reinforce Policy Framework.md | 8 +- 10_Wiki/Topics/AI/Ps-Reinforce.md | 6 +- 10_Wiki/Topics/AI/Psychology & Behavior.md | 12 +- 10_Wiki/Topics/AI/Psychology-of-Learning.md | 6 +- 10_Wiki/Topics/AI/Psychology.md | 14 +- .../Topics/AI/Pull Request (PR) 워크플로우.md | 12 +- 10_Wiki/Topics/AI/Pull Request (PR).md | 14 +- 10_Wiki/Topics/AI/Pull-Request.md | 10 +- 10_Wiki/Topics/AI/Purpose.md | 18 +- 10_Wiki/Topics/AI/PyTorch-Foundations.md | 6 +- 10_Wiki/Topics/AI/PyTorch-Lightning.md | 8 +- 10_Wiki/Topics/AI/Python-for-Data-Science.md | 4 +- 10_Wiki/Topics/AI/Q-Learning Foundations.md | 10 +- 10_Wiki/Topics/AI/Quality Gates.md | 12 +- 10_Wiki/Topics/AI/Quality-Control.md | 12 +- .../AI/Quantitative Economics (수량경제학).md | 10 +- 10_Wiki/Topics/AI/Quantization-Foundations.md | 4 +- 10_Wiki/Topics/AI/Quantization.md | 14 +- .../Topics/AI/Quantum Computing (Intro).md | 10 +- 10_Wiki/Topics/AI/Quantum-Computing-for-AI.md | 8 +- 10_Wiki/Topics/AI/Quantum-Computing.md | 10 +- 10_Wiki/Topics/AI/Quantum-Machine-Learning.md | 4 +- 10_Wiki/Topics/AI/Query-Optimization.md | 10 +- 10_Wiki/Topics/AI/Queue-Management-Systems.md | 6 +- 10_Wiki/Topics/AI/Quick-Wins.md | 14 +- 10_Wiki/Topics/AI/RAG (검색 증강 생성).md | 10 +- .../Topics/AI/RAG-and-Document-Retrieval.md | 6 +- 10_Wiki/Topics/AI/RAG.md | 10 +- .../AI/RLAIF (AI 피드백 기반 강화학습).md | 8 +- .../AI/RLHF (인간 피드백 기반 강화 학습).md | 16 +- 10_Wiki/Topics/AI/RL_Neuroscience.md | 8 +- 10_Wiki/Topics/AI/RMSProp-Optimizer.md | 6 +- 10_Wiki/Topics/AI/RNN.md | 14 +- 10_Wiki/Topics/AI/ROC-AUC-Curves.md | 4 +- 10_Wiki/Topics/AI/ROUGE-Metrics.md | 6 +- .../Topics/AI/Random-Forest-Classifiers.md | 8 +- 10_Wiki/Topics/AI/Randomized-Algorithms.md | 8 +- 10_Wiki/Topics/AI/Ranking-Algorithms.md | 4 +- 10_Wiki/Topics/AI/Rapid-Prototyping.md | 16 +- .../Topics/AI/ReLU-Activation-Functions.md | 12 +- 10_Wiki/Topics/AI/React-Context-API.md | 10 +- .../AI/React-Error-Boundaries-and-Handling.md | 6 +- 10_Wiki/Topics/AI/React-Hooks.md | 12 +- 10_Wiki/Topics/AI/Reactive-Programming.md | 12 +- 10_Wiki/Topics/AI/Real-time-Data-Streaming.md | 10 +- 10_Wiki/Topics/AI/Real-time-Operation.md | 12 +- 10_Wiki/Topics/AI/Reasoning & Planning.md | 12 +- 10_Wiki/Topics/AI/Reasoning.md | 14 +- 10_Wiki/Topics/AI/Recommendation-Systems.md | 8 +- .../AI/Recording Academy (The Grammys).md | 10 +- .../Topics/AI/Recurrent-Neural-Networks.md | 10 +- .../AI/Refactoring-Legacy-React-Codebases.md | 8 +- 10_Wiki/Topics/AI/Reference-Management.md | 14 +- 10_Wiki/Topics/AI/Reference.md | 12 +- 10_Wiki/Topics/AI/Refinement.md | 16 +- 10_Wiki/Topics/AI/Reflection.md | 12 +- .../AI/Regression-Analysis-Foundations.md | 8 +- .../Topics/AI/Regularization-Strategies.md | 6 +- .../Topics/AI/Regularization-Techniques.md | 4 +- 10_Wiki/Topics/AI/Regularization.md | 12 +- .../Topics/AI/Reinforcement Learning (RL).md | 12 +- ...ment Learning for Automated Playtesting.md | 12 +- ...ement-Learning-from-Human-Feedback-RLHF.md | 6 +- 10_Wiki/Topics/AI/Reinforcement-Learning.md | 10 +- 10_Wiki/Topics/AI/Related-Work.md | 14 +- .../AI/Relational Algebra in Databases.md | 10 +- 10_Wiki/Topics/AI/Relational-Database.md | 12 +- 10_Wiki/Topics/AI/Relational-Databases.md | 8 +- 10_Wiki/Topics/AI/Relative-Positioning.md | 8 +- 10_Wiki/Topics/AI/Relevance-Feedback.md | 6 +- 10_Wiki/Topics/AI/Reliability.md | 14 +- 10_Wiki/Topics/AI/Remote-Rehabilitation.md | 6 +- 10_Wiki/Topics/AI/Replenishment.md | 14 +- 10_Wiki/Topics/AI/Reports.md | 14 +- 10_Wiki/Topics/AI/Repository.md | 12 +- 10_Wiki/Topics/AI/Representation Theory.md | 4 +- 10_Wiki/Topics/AI/Representation-Learning.md | 6 +- 10_Wiki/Topics/AI/Requirements.md | 12 +- 10_Wiki/Topics/AI/ResNet-Architectures.md | 6 +- 10_Wiki/Topics/AI/Research-Framework.md | 18 +- 10_Wiki/Topics/AI/Research-Methodology.md | 14 +- 10_Wiki/Topics/AI/Research.md | 14 +- 10_Wiki/Topics/AI/Residual-Networks.md | 6 +- 10_Wiki/Topics/AI/Resilience.md | 18 +- 10_Wiki/Topics/AI/Resource-Allocation.md | 14 +- 10_Wiki/Topics/AI/Resource-Management.md | 8 +- 10_Wiki/Topics/AI/Restorative Justice.md | 8 +- 10_Wiki/Topics/AI/Retainers(유지 경로).md | 16 +- 10_Wiki/Topics/AI/Retaining Path.md | 12 +- .../Retrieval-Augmented Generation (RAG).md | 10 +- .../AI/Retrieval-Augmented-Generation-RAG.md | 6 +- 10_Wiki/Topics/AI/Revenge-Cycle-Dynamics.md | 10 +- .../Topics/AI/Reward Hacking (보상 해킹).md | 8 +- 10_Wiki/Topics/AI/Reward Prediciton Error.md | 11 - ...eward Prediction Error (상태 예측 오류).md | 11 - 10_Wiki/Topics/AI/Reward Prediction Error.md | 10 +- 10_Wiki/Topics/AI/Reward-Shaping-in-RL.md | 6 +- 10_Wiki/Topics/AI/Ridge-Regression.md | 8 +- 10_Wiki/Topics/AI/Risk Management.md | 12 +- 10_Wiki/Topics/AI/Risk-Assessment-with-AI.md | 8 +- 10_Wiki/Topics/AI/Risk-Management.md | 14 +- 10_Wiki/Topics/AI/Risk-Orchestration.md | 14 +- 10_Wiki/Topics/AI/Roadmap.md | 12 +- 10_Wiki/Topics/AI/Robotics-Foundations.md | 8 +- 10_Wiki/Topics/AI/Robotics.md | 10 +- 10_Wiki/Topics/AI/Robust-Machine-Learning.md | 6 +- 10_Wiki/Topics/AI/Robustness.md | 10 +- .../AI/Role of Conflict in Narrative.md | 10 +- 10_Wiki/Topics/AI/Root-Cause-Analysis-RCA.md | 6 +- 10_Wiki/Topics/AI/Root-Mean-Square-Error.md | 6 +- .../Topics/AI/Roughness (그래픽 및 물리).md | 14 +- 10_Wiki/Topics/AI/Rule-based-Systems.md | 8 +- 10_Wiki/Topics/AI/SAR.md | 18 +- ...T (Static Application Security Testing).md | 27 - .../SAST (정적 애플리케이션 보안 테스트).md | 40 - .../SAST (정적 애플리케이션 보안 테스팅).md | 37 - 10_Wiki/Topics/AI/SAST.md | 12 +- .../AI/SCM (Supply Chain Management).md | 14 +- .../AI/SDLC (소프트웨어 개발 수명 주기).md | 12 +- 10_Wiki/Topics/AI/SEO.md | 12 +- .../Topics/AI/SFT (Supervised Fine-Tuning).md | 10 +- 10_Wiki/Topics/AI/SME.md | 12 +- 10_Wiki/Topics/AI/SOTA.md | 16 +- 10_Wiki/Topics/AI/SOW.md | 16 +- 10_Wiki/Topics/AI/SPOF.md | 12 +- 10_Wiki/Topics/AI/SQL-Performance-Tuning.md | 8 +- 10_Wiki/Topics/AI/SRE.md | 12 +- .../Topics/AI/SaaS (Software as a Service).md | 12 +- 10_Wiki/Topics/AI/SaaS.md | 14 +- 10_Wiki/Topics/AI/Safety & Reliability.md | 10 +- 10_Wiki/Topics/AI/Sales-Strategy.md | 14 +- 10_Wiki/Topics/AI/Sampling-Techniques.md | 4 +- .../Topics/AI/Scalability-in-AI-Systems.md | 8 +- 10_Wiki/Topics/AI/Scalability.md | 14 +- .../AI/Scalable-Design-System-Governance.md | 14 +- 10_Wiki/Topics/AI/Scaling-Laws-for-LLMs.md | 4 +- 10_Wiki/Topics/AI/Scheduler-Design-in-ML.md | 4 +- 10_Wiki/Topics/AI/Schema-Design-for-NoSQL.md | 6 +- 10_Wiki/Topics/AI/Schema.md | 10 +- 10_Wiki/Topics/AI/Science of Failure.md | 14 +- 10_Wiki/Topics/AI/Scientific Communication.md | 6 +- .../AI/Scientific-Computing-with-Python.md | 2 +- 10_Wiki/Topics/AI/Scientific-Method.md | 18 +- 10_Wiki/Topics/AI/Scripts.md | 14 +- .../Topics/AI/Search-Engine-Optimization.md | 6 +- 10_Wiki/Topics/AI/Search-Methodology.md | 18 +- 10_Wiki/Topics/AI/Search-Optimization.md | 16 +- 10_Wiki/Topics/AI/Search-Space.md | 18 +- 10_Wiki/Topics/AI/Search-Strategy.md | 14 +- 10_Wiki/Topics/AI/Search.md | 8 +- 10_Wiki/Topics/AI/Secondary-Research.md | 12 +- .../AI/Secure-Multi-party-Computation.md | 4 +- 10_Wiki/Topics/AI/Security-Best-Practices.md | 4 +- 10_Wiki/Topics/AI/Security-Governance.md | 14 +- 10_Wiki/Topics/AI/Seed.md | 10 +- 10_Wiki/Topics/AI/Segmentsai.md | 12 +- .../Topics/AI/Self-Attention-Mechanisms.md | 6 +- .../Topics/AI/Self-Correction Mechanisms.md | 11 - 10_Wiki/Topics/AI/Self-Correction.md | 11 - .../Topics/AI/Self-Driving-Car-Foundations.md | 4 +- .../AI/Self-Play (자기 대결 기반 강화학습).md | 8 +- .../AI/Self-Supervised Learning (SSL).md | 10 +- 10_Wiki/Topics/AI/Self-Supervised-Learning.md | 8 +- .../AI/Semantic Grounding & Provenance.md | 8 +- .../Topics/AI/Semantic-HTML-Foundations.md | 4 +- 10_Wiki/Topics/AI/Semantic-Search-with-AI.md | 8 +- 10_Wiki/Topics/AI/Semantic-Search.md | 6 +- 10_Wiki/Topics/AI/Semantics & Ontology.md | 8 +- 10_Wiki/Topics/AI/Semgrep Assistant.md | 10 +- 10_Wiki/Topics/AI/Sensitivity-Analysis.md | 18 +- 10_Wiki/Topics/AI/Sensor-Fusion.md | 4 +- .../Topics/AI/Sentiment-Analysis-Models.md | 8 +- 10_Wiki/Topics/AI/Sentiment-Analysis.md | 10 +- 10_Wiki/Topics/AI/Sequence-Modeling.md | 12 +- .../Topics/AI/Sequence-to-Sequence-Models.md | 6 +- .../Topics/AI/Serverless-Computing-for-AI.md | 8 +- .../AI/Service-oriented-Architecture.md | 4 +- .../Topics/AI/Shadowing-and-Observability.md | 4 +- 10_Wiki/Topics/AI/Shape-Feature-Extraction.md | 4 +- .../Topics/AI/Sharding-and-Partitioning.md | 4 +- 10_Wiki/Topics/AI/Shift.md | 14 +- 10_Wiki/Topics/AI/Signal in Noise.md | 10 +- .../AI/Signal-Processing-Foundations.md | 4 +- 10_Wiki/Topics/AI/Similarity-Metrics-in-AI.md | 4 +- 10_Wiki/Topics/AI/Similarity-Metrics.md | 12 +- 10_Wiki/Topics/AI/Simulated-Annealing.md | 6 +- 10_Wiki/Topics/AI/Simulation-Environments.md | 8 +- .../Simulator Sickness Questionnaire (SSQ).md | 6 +- .../Topics/AI/Singular-Value-Decomposition.md | 4 +- 10_Wiki/Topics/AI/Six-Sigma-Methodologies.md | 4 +- .../Topics/AI/Skybound Protocol 코드리뷰.md | 8 +- 10_Wiki/Topics/AI/Slack-Bot-Development.md | 4 +- 10_Wiki/Topics/AI/Smart-Contract-Auditing.md | 10 +- .../Topics/AI/Snowflake-Data-Warehousing.md | 8 +- ...r Labs 등 종합 애플리케이션 보안 플랫폼.md | 12 +- 10_Wiki/Topics/AI/Social Systems Theory.md | 10 +- 10_Wiki/Topics/AI/Social-Network-Analysis.md | 4 +- 10_Wiki/Topics/AI/Sociology of Knowledge.md | 10 +- 10_Wiki/Topics/AI/Soft Navigation.md | 8 +- 10_Wiki/Topics/AI/Soft-Skills-Development.md | 10 +- .../AI/Software-Architecture-Patterns.md | 8 +- .../Topics/AI/Software-Design-Principles.md | 12 +- 10_Wiki/Topics/AI/Solitude-Optimization.md | 12 +- 10_Wiki/Topics/AI/Solow Growth Model.md | 10 +- 10_Wiki/Topics/AI/Solution.md | 12 +- 10_Wiki/Topics/AI/SonarQube.md | 16 +- 10_Wiki/Topics/AI/Sorting.md | 16 +- 10_Wiki/Topics/AI/Sound Design Principles.md | 10 +- 10_Wiki/Topics/AI/Source-Control.md | 12 +- 10_Wiki/Topics/AI/Space-based-Architecture.md | 6 +- 10_Wiki/Topics/AI/Sparse-Data-Handling.md | 4 +- 10_Wiki/Topics/AI/Spatial-Data-Analysis.md | 6 +- 10_Wiki/Topics/AI/Specification.md | 14 +- 10_Wiki/Topics/AI/Spectral-Clustering.md | 4 +- 10_Wiki/Topics/AI/Speculative-Design.md | 8 +- .../AI/Speech-Recognition-Foundations.md | 4 +- 10_Wiki/Topics/AI/Speech-Synthesis.md | 8 +- .../Topics/AI/Spiking-Neural-Networks-SNNs.md | 6 +- 10_Wiki/Topics/AI/Stability vs Flexibility.md | 14 +- 10_Wiki/Topics/AI/Stability.md | 11 - 10_Wiki/Topics/AI/Stacked-Generalization.md | 2 +- 10_Wiki/Topics/AI/Stages-of-Grief.md | 10 +- 10_Wiki/Topics/AI/Stakeholder.md | 10 +- .../AI/Standard-Deviation-and-Variance.md | 6 +- .../Topics/AI/Standard-Operating-Procedure.md | 16 +- .../AI/Standardization vs Innovation.md | 8 +- 10_Wiki/Topics/AI/Startup.md | 14 +- 10_Wiki/Topics/AI/State Space Model (SSM).md | 12 +- ...e-Management-Architecture-and-Ownership.md | 10 +- .../Topics/AI/State-Management-Patterns.md | 10 +- 10_Wiki/Topics/AI/State-Space-Models.md | 10 +- 10_Wiki/Topics/AI/State-Space.md | 14 +- 10_Wiki/Topics/AI/State.md | 12 +- ...tic Application Security Testing (SAST).md | 34 - .../AI/Static-Site-Generation-with-Gatsby.md | 2 +- 10_Wiki/Topics/AI/Statistical-Analysis.md | 16 +- .../AI/Statistical-Hypothesis-Testing.md | 6 +- .../Topics/AI/Statistical-Learning-Theory.md | 4 +- 10_Wiki/Topics/AI/Statistical-Power.md | 6 +- .../Topics/AI/Statistics & Data Analysis.md | 8 +- 10_Wiki/Topics/AI/Statistics.md | 10 +- 10_Wiki/Topics/AI/Stem-Analysis.md | 14 +- .../AI/Stochastic-Gradient-Descent-SGD.md | 10 +- .../Topics/AI/Stochastic-Gradient-Descent.md | 12 +- 10_Wiki/Topics/AI/Storage-Area-Networks.md | 6 +- 10_Wiki/Topics/AI/Storage.md | 14 +- 10_Wiki/Topics/AI/Straightening.md | 8 +- 10_Wiki/Topics/AI/Strategic-Alignment.md | 10 +- 10_Wiki/Topics/AI/Strategic-Ambiguity.md | 8 +- .../Topics/AI/Strategic-Planning-for-AI.md | 6 +- 10_Wiki/Topics/AI/Strategic-Planning.md | 18 +- 10_Wiki/Topics/AI/Strategic-Thinking.md | 12 +- 10_Wiki/Topics/AI/Strategy.md | 16 +- .../AI/Stream-Processing-Architectures.md | 6 +- 10_Wiki/Topics/AI/Structural Principles.md | 12 +- .../Topics/AI/Structural-Equation-Modeling.md | 4 +- 10_Wiki/Topics/AI/Structuralism.md | 10 +- 10_Wiki/Topics/AI/Style-Transfer-in-AI.md | 6 +- 10_Wiki/Topics/AI/Style-Transfer.md | 12 +- 10_Wiki/Topics/AI/Superficiality-Metrics.md | 10 +- .../Topics/AI/Supervised Fine-Tuning (SFT).md | 11 - .../Supervised-Learning (지도 학습 기초).md | 4 +- .../AI/Supervised-Learning-Foundations.md | 8 +- 10_Wiki/Topics/AI/Supervised-Learning.md | 14 +- 10_Wiki/Topics/AI/Supply-Chain.md | 12 +- 10_Wiki/Topics/AI/Support-Vector-Machines.md | 4 +- 10_Wiki/Topics/AI/Support.md | 12 +- 10_Wiki/Topics/AI/Sustainability.md | 14 +- 10_Wiki/Topics/AI/Swarm Intelligence.md | 16 +- 10_Wiki/Topics/AI/Swarm-Intelligence.md | 12 +- .../Topics/AI/Symbolic-AI vs Connectionism.md | 6 +- 10_Wiki/Topics/AI/Symbols.md | 14 +- 10_Wiki/Topics/AI/Symmetric-Encryption.md | 4 +- 10_Wiki/Topics/AI/Symmetry-and-Invariance.md | 10 +- 10_Wiki/Topics/AI/Synergy.md | 14 +- 10_Wiki/Topics/AI/Synthesized Intelligence.md | 8 +- .../Topics/AI/Synthetic-Data-Generation.md | 6 +- 10_Wiki/Topics/AI/Synthetic-Data.md | 12 +- .../AI/System Prompt (시스템 프롬프트).md | 10 +- .../Topics/AI/System-Architecture-Design.md | 6 +- .../Topics/AI/System-Design for AI Scale.md | 10 +- .../Topics/AI/System-Design-Interview-Prep.md | 6 +- 10_Wiki/Topics/AI/System-Dynamics-Modeling.md | 6 +- 10_Wiki/Topics/AI/System-Theory.md | 14 +- 10_Wiki/Topics/AI/Systems Thinking.md | 10 +- 10_Wiki/Topics/AI/Systems-Thinking.md | 16 +- 10_Wiki/Topics/AI/TDD.md | 12 +- 10_Wiki/Topics/AI/TS-Declaration-Files.md | 14 +- .../Topics/AI/Tableau-Data-Visualization.md | 4 +- .../Topics/AI/Target-Function-Profiling.md | 12 +- 10_Wiki/Topics/AI/Task-Management.md | 10 +- 10_Wiki/Topics/AI/Technical-Architecture.md | 14 +- 10_Wiki/Topics/AI/Technical-Debt.md | 16 +- .../Topics/AI/Temporal-Difference-Learning.md | 4 +- 10_Wiki/Topics/AI/TensorFlow-Foundations.md | 4 +- ...rm-Frequency-Inverse-Document-Frequency.md | 6 +- 10_Wiki/Topics/AI/Terminology.md | 16 +- .../AI/Terraform-Infrastructure-as-Code.md | 6 +- ...mpute Scaling (추론 시간 계산 스케일링).md | 10 +- 10_Wiki/Topics/AI/Testing.md | 12 +- 10_Wiki/Topics/AI/Text-Mining.md | 16 +- 10_Wiki/Topics/AI/Text-to-Speech-Synthesis.md | 6 +- .../AI/The Evolution of Music Distribution.md | 10 +- 10_Wiki/Topics/AI/The Grammys.md | 11 - .../Topics/AI/Theoretical-Computer-Science.md | 8 +- .../Topics/AI/Theory of Constraints (TOC).md | 8 +- .../Topics/AI/Theory-of-Mind (ToM) in AI.md | 8 +- 10_Wiki/Topics/AI/Thought-Architecture.md | 18 +- .../Topics/AI/Threejs WebGL 렌더링 최적화.md | 22 +- 10_Wiki/Topics/AI/Threejs WebGPURenderer.md | 14 +- 10_Wiki/Topics/AI/Threejs 성능 최적화.md | 24 +- 10_Wiki/Topics/AI/Time-Series-Analysis.md | 12 +- 10_Wiki/Topics/AI/Time-Step-Logic-in-Games.md | 6 +- 10_Wiki/Topics/AI/Tokenization-Strategies.md | 4 +- 10_Wiki/Topics/AI/Tool-Usage-Optimization.md | 12 +- .../Topics/AI/Toxicity-and-Bias-Mitigation.md | 10 +- 10_Wiki/Topics/AI/Transfer Learning.md | 14 +- .../AI/Transfer-Learning (전이 학습 기초).md | 8 +- 10_Wiki/Topics/AI/Transformer-Architecture.md | 8 +- 10_Wiki/Topics/AI/Transformers.md | 14 +- 10_Wiki/Topics/AI/Trustworthy-AI.md | 4 +- 10_Wiki/Topics/AI/Turing Test.md | 10 +- .../Topics/AI/Turing-Machine Foundations.md | 6 +- 10_Wiki/Topics/AI/Type 1 vs Type 2 Errors.md | 8 +- 10_Wiki/Topics/AI/UX-Design-Principles.md | 8 +- .../Topics/AI/Uber-Base-Web-Design-System.md | 10 +- 10_Wiki/Topics/AI/Ultra-Efficiency.md | 8 +- .../Topics/AI/Uncertainty-Quantification.md | 4 +- .../Topics/AI/Unconscious Structuralism.md | 10 +- .../AI/Understanding Complex Systems.md | 18 +- .../Topics/AI/Universal Basic Income (UBI).md | 6 +- .../AI/Universal-Approximation-Theorem.md | 4 +- 10_Wiki/Topics/AI/Universal-Grammar.md | 10 +- ...nsupervised-Learning (비지도 학습 기초).md | 4 +- .../AI/Variational Autoencoders (VAE).md | 10 +- .../Topics/AI/Variational-Autoencoders-VAE.md | 8 +- .../Topics/AI/Vector-Database Selection.md | 8 +- 10_Wiki/Topics/AI/Victimhood-Narratives.md | 10 +- .../AI/Viral-Dynamics-and-Network-Effects.md | 12 +- .../Topics/AI/Visual-Effects-VFX-in-Games.md | 10 +- 10_Wiki/Topics/AI/Visual-Effects-VFX.md | 6 +- 10_Wiki/Topics/AI/Vocabulary-Expansion.md | 8 +- .../Topics/AI/Voice-Assistant-Architecture.md | 8 +- .../Topics/AI/Web Performance Optimization.md | 32 +- .../AI/Web-Rendering-Strategies-CSR-vs-SSR.md | 10 +- 10_Wiki/Topics/AI/Web3-and-AI-Integration.md | 6 +- .../AI/WebSplatter (3D Gaussian Splatting).md | 16 +- 10_Wiki/Topics/AI/What-is-AI.md | 12 +- 10_Wiki/Topics/AI/Wicked-Problems.md | 14 +- 10_Wiki/Topics/AI/Word-Representation.md | 10 +- 10_Wiki/Topics/AI/Work-Displacement.md | 8 +- 10_Wiki/Topics/AI/Workflow-Integrity.md | 10 +- 10_Wiki/Topics/AI/Working-Backwards.md | 12 +- .../AI/Zero Shot and Few Shot Learning.md | 12 +- .../Topics/AI/Zero-Shot-Chain-of-Thought.md | 8 +- 10_Wiki/Topics/AI/Zero-Shot-Learning.md | 6 +- ...리_ - 관심사의 분리 (Separation of Concerns).md | 6 +- .../AI/agargaro의 오픈 소스 라이브러리.md | 10 +- 10_Wiki/Topics/AI/clinicjs.md | 10 +- .../Topics/AI/stochastic gradient descent.md | 8 +- .../AI/공급망 공격 (Supply Chain Attack).md | 10 +- ...비스 아키텍처 (Microservices Architecture).md | 12 +- .../AI/벡터 데이터베이스 (Vector Database).md | 10 +- .../Topics/AI/보존 경로(Retaining Path).md | 14 +- .../AI/보편적 언어 (Ubiquitous Language).md | 10 +- ...리 누수 탐지(Browser Memory Leak Detection).md | 12 +- ... 도메인 모델링 (Business Domain Modeling).md | 18 +- .../빌보드 임포스터(Billboard Impostors).md | 6 +- ...상태 관리 최적화 (Zustand Jotai Valtio).md | 18 +- ...플라이 체인 보안 (Supply Chain Security).md | 10 +- .../AI/소프트웨어 개발 수명 주기 (SDLC).md | 33 - .../Topics/AI/시뮬레이터 멀미 설문지(SSQ).md | 8 +- ...미 설문지(Simulator Sickness Questionnaire).md | 8 +- 10_Wiki/Topics/AI/애그리거트 (Aggregates).md | 12 +- ...5 호쿠사이 인스톨레이션(Hokusai installation).md | 10 +- .../유비쿼터스 언어 (Ubiquitous Language).md | 12 +- 10_Wiki/Topics/AI/인지 행동 치료 (CBT).md | 10 +- .../정적 애플리케이션 보안 테스트 (SAST).md | 18 +- .../AI/정적 애플리케이션 보안 테스트(SAST).md | 14 +- 10_Wiki/Topics/AI/카산드라(Cassandra).md | 6 +- 10_Wiki/Topics/AI/코드 리뷰(Code Review).md | 14 +- 10_Wiki/Topics/AI/풀 리퀘스트 워크플로우.md | 14 +- .../AI/풀 리퀘스트(PR) 기반 보안 검토.md | 14 +- .../프론트엔드 및 Nodejs 개발 워크플로우.md | 20 +- ...이브리드 코드 리뷰 (Hybrid Code Review).md | 14 +- 10_Wiki/Topics/AI/하이브리드 코드 리뷰.md | 12 +- .../AI/할당 실패(Allocation Failure).md | 10 +- .../Topics/AI/함수 호출 (Function Calling).md | 10 +- ...열 맡기기_ - 정적 분석 툴 (ESLint Prettier)).md | 44 - ... 모델링 및 상태 머신(State Machine) 설계.md | 40 - 10_Wiki/Topics/API-Design for AI Services.md | 29 - 10_Wiki/Topics/API-Key-Management.md | 31 - 10_Wiki/Topics/API_Communication_Patterns.md | 26 - 10_Wiki/Topics/A_B-Testing-Platforms.md | 27 - 10_Wiki/Topics/Abundance.md | 34 - 10_Wiki/Topics/Academic-Integrity.md | 35 - .../Topics/Accessibility-Compliance-Audit.md | 27 - 10_Wiki/Topics/Accessibility_Inclusivity.md | 26 - 10_Wiki/Topics/Active Learning.md | 33 - 10_Wiki/Topics/Active-Reasoning.md | 33 - 10_Wiki/Topics/Activism.md | 36 - 10_Wiki/Topics/Actor-Critic-Models.md | 32 - 10_Wiki/Topics/Ad-hoc-Hypotheses.md | 33 - 10_Wiki/Topics/Ad-hoc-Optimization.md | 34 - 10_Wiki/Topics/Adaptability.md | 34 - .../Adaptive Compute (적응형 계산량 조절).md | 25 - 10_Wiki/Topics/Adaptive-Curation.md | 33 - 10_Wiki/Topics/Advanced-Interface-Design.md | 27 - 10_Wiki/Topics/Adversarial Code Stylometry.md | 34 - 10_Wiki/Topics/Aesthetic-Value.md | 32 - 10_Wiki/Topics/Affordance.md | 33 - .../Agent & AI/ConnectAI_Dev_Log_20260429.md | 26 +- 10_Wiki/Topics/Agent & AI/Index.md | 4 +- 10_Wiki/Topics/Agent & AI/P-Reinforce.md | 4 +- 10_Wiki/Topics/Agent & AI/Zen-Pop.md | 4 +- 10_Wiki/Topics/Agent Architecture.md | 36 - 10_Wiki/Topics/Agent Personality.md | 34 - 10_Wiki/Topics/Agentic Coding.md | 34 - 10_Wiki/Topics/Agentic Creative Era.md | 10 +- 10_Wiki/Topics/Agile-Philosophy.md | 36 - 10_Wiki/Topics/Alcoholism.md | 33 - 10_Wiki/Topics/Algorithm-Complexity-Big-O.md | 31 - 10_Wiki/Topics/Algorithmic Fairness.md | 35 - 10_Wiki/Topics/Algorithmic Transparency.md | 31 - 10_Wiki/Topics/Algorithmic-Biology.md | 27 - 10_Wiki/Topics/Algorithmic-Game-Theory.md | 27 - 10_Wiki/Topics/Alignment.md | 33 - 10_Wiki/Topics/AlphaZero Strategy.md | 25 - 10_Wiki/Topics/Alternative Realities.md | 34 - 10_Wiki/Topics/Altruism.md | 33 - 10_Wiki/Topics/Ambient-Declarations.md | 27 - 10_Wiki/Topics/Ambition.md | 33 - 10_Wiki/Topics/Amdahls Law (암달의 법칙).md | 28 - 10_Wiki/Topics/Analogical-Reasoning.md | 32 - 10_Wiki/Topics/Analogy.md | 31 - 10_Wiki/Topics/Analysis.md | 32 - 10_Wiki/Topics/Anarchism.md | 34 - 10_Wiki/Topics/Anarcho-Capitalism.md | 32 - 10_Wiki/Topics/Anarcho-Primitivism.md | 31 - 10_Wiki/Topics/Anisomorphism.md | 31 - 10_Wiki/Topics/Anomaly-Detection.md | 34 - 10_Wiki/Topics/Anthropic-Principle.md | 27 - 10_Wiki/Topics/Anthropomorphism.md | 33 - 10_Wiki/Topics/Anticipation.md | 31 - 10_Wiki/Topics/Antifragility.md | 32 - 10_Wiki/Topics/Antinomianism.md | 31 - 10_Wiki/Topics/Anxiety.md | 31 - 10_Wiki/Topics/Arguing-by-Counterexample.md | 32 - 10_Wiki/Topics/Arrangement-and-Composition.md | 34 - 10_Wiki/Topics/Articulateness.md | 33 - .../Artificial General Intelligence (AGI).md | 32 - .../Topics/Artificial Intelligence (AI).md | 34 - .../Artificial-Intelligence-in-Games.md | 27 - 10_Wiki/Topics/Artificial-Intelligence.md | 27 - 10_Wiki/Topics/Artificial-Life.md | 29 - 10_Wiki/Topics/Arts.md | 32 - 10_Wiki/Topics/Assertiveness.md | 32 - 10_Wiki/Topics/Assessment.md | 33 - 10_Wiki/Topics/Asset-Specific-Knowledge.md | 32 - 10_Wiki/Topics/Assumptions-vs-Facts.md | 34 - 10_Wiki/Topics/Atheism.md | 32 - 10_Wiki/Topics/Atlantic.md | 31 - 10_Wiki/Topics/Atmospheric-Intelligence.md | 31 - .../Atomic-Design-System-Architecture.md | 30 - .../Atomic-Styling-and-Design-Systems.md | 29 - 10_Wiki/Topics/Atomism.md | 31 - 10_Wiki/Topics/Attention Mechanisms.md | 34 - 10_Wiki/Topics/Attention is All You Need.md | 29 - 10_Wiki/Topics/Authenticity.md | 33 - ...sm Spectrum Disorder (ASD) Intervention.md | 27 - 10_Wiki/Topics/Auto-Encoding.md | 34 - .../Topics/Auto-GPT and Autonomous Agents.md | 29 - 10_Wiki/Topics/Autobiography.md | 32 - 10_Wiki/Topics/Autoethnography.md | 31 - 10_Wiki/Topics/Automated-Decision-Making.md | 34 - 10_Wiki/Topics/Automated-Game-Testing.md | 27 - 10_Wiki/Topics/Automated-Map-Generation.md | 28 - 10_Wiki/Topics/Automated-Reasoning.md | 34 - 10_Wiki/Topics/Automated-Refactoring-Tools.md | 27 - 10_Wiki/Topics/Automated-Security-Audits.md | 27 - 10_Wiki/Topics/Automated-Theorem-Proving.md | 27 - 10_Wiki/Topics/Automated_Mapping.md | 29 - 10_Wiki/Topics/Automation-Paradox.md | 31 - .../Automation/Automated Quality & Review.md | 14 +- 10_Wiki/Topics/Automation/Index.md | 4 +- 10_Wiki/Topics/Automation/IoT.md | 10 +- 10_Wiki/Topics/Automation/SCADA.md | 6 +- 10_Wiki/Topics/Autonomous Vehicles.md | 35 - 10_Wiki/Topics/Autonomous-Agents.md | 33 - .../Autonomous-Polling-Wait-Automation.md | 35 - .../Autonomous-Vehicle-Path-Planning.md | 27 - .../Topics/Availability-and-Persistence.md | 33 - 10_Wiki/Topics/Awards.md | 32 - 10_Wiki/Topics/Axify.md | 33 - 10_Wiki/Topics/Axiology.md | 30 - 10_Wiki/Topics/Axiomatic-Systems.md | 31 - 10_Wiki/Topics/Axioms.md | 32 - 10_Wiki/Topics/Azure DevOps.md | 35 - 10_Wiki/Topics/B-Tree.md | 27 - ...oder Representations from Transformers).md | 4 +- 10_Wiki/Topics/BFS vs DFS.md | 33 - 10_Wiki/Topics/Backend.md | 33 - .../Topics/Backpropagation Through Time.md | 28 - 10_Wiki/Topics/Backpropagation.md | 32 - 10_Wiki/Topics/Backups.md | 35 - 10_Wiki/Topics/Backward-Reasoning.md | 33 - 10_Wiki/Topics/Bag of Words (BoW).md | 33 - 10_Wiki/Topics/Baseline Project.md | 35 - 10_Wiki/Topics/Batch-Inference.md | 33 - 10_Wiki/Topics/Bayesian-Brain-Hypothesis.md | 29 - 10_Wiki/Topics/Be-Detailed.md | 31 - 10_Wiki/Topics/Beckett.md | 31 - 10_Wiki/Topics/Behavior.md | 33 - 10_Wiki/Topics/Behavioral Finance.md | 27 - 10_Wiki/Topics/Behavioral-Economics.md | 29 - 10_Wiki/Topics/Behavioral-Incentives.md | 32 - 10_Wiki/Topics/Belief-Revision.md | 31 - 10_Wiki/Topics/Belief-System.md | 32 - 10_Wiki/Topics/Beliefs.md | 32 - 10_Wiki/Topics/Bellman Equation.md | 27 - 10_Wiki/Topics/Bellman-Equation.md | 27 - 10_Wiki/Topics/Benchmarks.md | 33 - 10_Wiki/Topics/Best SAST Tools in 2026.md | 29 - 10_Wiki/Topics/Best-of-N Sampling ( ø).md | 27 - .../Best-of-N Sampling (최적 샘플링).md | 29 - 10_Wiki/Topics/Best-of-N Sampling.md | 27 - 10_Wiki/Topics/Best-of-N-Sampling.md | 31 - 10_Wiki/Topics/Bias vs Variance.md | 32 - 10_Wiki/Topics/Bias-Correction-Algorithm.md | 27 - 10_Wiki/Topics/Bias-Variance-Tradeoff.md | 27 - 10_Wiki/Topics/Bible.md | 32 - 10_Wiki/Topics/Bibliometrics.md | 32 - 10_Wiki/Topics/Big-Data.md | 33 - 10_Wiki/Topics/Big-Picture.md | 31 - .../Topics/Binary-Author-Identification.md | 31 - 10_Wiki/Topics/Binary-Search.md | 35 - 10_Wiki/Topics/BioShock (2007).md | 27 - 10_Wiki/Topics/BioShock-Critique.md | 27 - 10_Wiki/Topics/Bioenergetics.md | 27 - .../Bioinformatics-Structure-Prediction.md | 27 - .../Topics/Biological-Inspired-Algorithms.md | 27 - 10_Wiki/Topics/Biological-Intelligence.md | 31 - 10_Wiki/Topics/Biomechanics-of-Injury.md | 27 - 10_Wiki/Topics/Biometrics.md | 30 - 10_Wiki/Topics/Black-Box-Optimization.md | 29 - 10_Wiki/Topics/Black-Hole.md | 31 - 10_Wiki/Topics/Black-Swan.md | 31 - 10_Wiki/Topics/Blockchain.md | 31 - 10_Wiki/Topics/Blocking.md | 33 - 10_Wiki/Topics/Blog-Post.md | 31 - 10_Wiki/Topics/Bloom-Filters in Search.md | 28 - 10_Wiki/Topics/Bloom-Filters.md | 27 - 10_Wiki/Topics/Boltzmann-Machines.md | 27 - .../Boosting-Algorithms-XGBoost-LightGBM.md | 27 - 10_Wiki/Topics/Bottlenecks.md | 31 - 10_Wiki/Topics/Bottom-Up-Approach.md | 32 - 10_Wiki/Topics/Boundaries.md | 31 - 10_Wiki/Topics/Boundary-Setting.md | 31 - 10_Wiki/Topics/Bounded Contexts.md | 27 - 10_Wiki/Topics/Bounded Rationality.md | 27 - ...nded-Contexts-and-Interface-Segregation.md | 27 - 10_Wiki/Topics/Bounded-Rationality.md | 31 - 10_Wiki/Topics/Bounding-Box-Regression.md | 27 - 10_Wiki/Topics/Bourgeoisie.md | 31 - .../Topics/Brain-Computer Interface (BCI).md | 27 - .../Topics/Brain-Computer-Interface (BCI).md | 31 - ...rain-Derived Neurotrophic Factor (BDNF).md | 27 - .../Topics/Brand Consistency Maintenance.md | 10 +- .../Branded-Types-for-Nominal-Typing.md | 29 - 10_Wiki/Topics/Branded-Types.md | 27 - 10_Wiki/Topics/Branding.md | 31 - 10_Wiki/Topics/Browser.md | 31 - 10_Wiki/Topics/Brute-force.md | 33 - 10_Wiki/Topics/Bubble-Sort.md | 34 - 10_Wiki/Topics/Budget.md | 31 - 10_Wiki/Topics/Bureaucracy.md | 32 - ...rnout Prevention in Professional Gaming.md | 27 - 10_Wiki/Topics/Burnout.md | 34 - 10_Wiki/Topics/Business Intelligence (BI).md | 31 - .../Business_Strategy/E-commerce Platforms.md | 10 +- .../Himart_UIUX_Direction_20260428.md | 20 +- .../Himart_Webstore_Meeting_20260429.md | 22 +- 10_Wiki/Topics/Business_Strategy/Index.md | 16 +- .../Business_Strategy/Meta Quest Store.md | 10 +- .../SaaS 대시보드 및 이커머스 UI 개발.md | 16 +- ...SaaS 대시보드 및 이커머스 레이아웃 구축.md | 8 +- ...SaaS 플랫폼 및 인터랙티브 대시보드 개발.md | 16 +- ...심의 SaaS 어드민 패널 및 CRM 대시보드 구축.md | 10 +- ...스 모바일 최적화 및 상품 탐색 UX-UI 설계.md | 6 +- ...자상거래 플랫폼 (E-commerce Platforms).md | 8 +- 10_Wiki/Topics/CAP-Theorem.md | 30 - .../CI-CD 파이프라인 (CI-CD Pipeline).md | 4 +- 10_Wiki/Topics/CLIP.md | 28 - 10_Wiki/Topics/CPTED.md | 33 - 10_Wiki/Topics/CV_Synthesis.md | 31 - 10_Wiki/Topics/Call Stack.md | 31 - .../Case-Study-Allbirds-PWA-Redesign.md | 31 - .../Case-Study-Kiwi-com-Frontend-Migration.md | 30 - ...Case-Study-Skybound-Asset-Cache-Busting.md | 28 - ...ybound-Red-Striker-Jitter-Stabilization.md | 28 - 10_Wiki/Topics/Catastrophic-Forgetting.md | 28 - 10_Wiki/Topics/Causal-Inference.md | 28 - 10_Wiki/Topics/Central-Pattern-Generators.md | 30 - 10_Wiki/Topics/CesiumJS.md | 31 - 10_Wiki/Topics/Chain-of-Thought (CoT 罽).md | 27 - .../Chain-of-Thought (CoT 사고 사슬).md | 30 - 10_Wiki/Topics/Chaos-Theory in Systems.md | 29 - 10_Wiki/Topics/Character Consistency.md | 14 +- 10_Wiki/Topics/Character Reference.md | 12 +- ...기반 텍스트 투 이미지(Text-to-Image) 생성.md | 14 +- .../Chrome DevTools 및 메모리 프로파일링.md | 4 +- .../Topics/Chrome-Rendering-Performance.md | 35 - .../Chronic-Pain-Management-Protocols.md | 27 - .../Topics/Circuit Discovery (회로 발견).md | 28 - 10_Wiki/Topics/Circuit Discovery.md | 29 - .../Topics/Circular-Economy-Transitions.md | 32 - 10_Wiki/Topics/Circular-Economy.md | 31 - .../Clean-Architecture-Implementation.md | 30 - .../Topics/Clean-Architecture-TypeScript.md | 32 - 10_Wiki/Topics/Clean-Code-Principles.md | 29 - .../Climate Change Mitigation Frameworks.md | 27 - .../Topics/Clinical-Kinesiology-Assessment.md | 27 - 10_Wiki/Topics/Code Review.md | 40 - ...g-and-Frontend-Performance-Optimization.md | 29 - 10_Wiki/Topics/Coding/AST_Traversal.md | 6 +- 10_Wiki/Topics/Coding/CST.md | 8 +- 10_Wiki/Topics/Coding/Formatting.md | 8 +- 10_Wiki/Topics/Coding/Index.md | 8 +- 10_Wiki/Topics/Coding/Parser.md | 4 +- 10_Wiki/Topics/Cognitive Biases.md | 32 - 10_Wiki/Topics/Cognitive Computing.md | 27 - .../Topics/Cognitive Neuroscience of Flow.md | 27 - 10_Wiki/Topics/Cognitive Psychology.md | 27 - 10_Wiki/Topics/Cognitive Reserve Theory.md | 27 - ... Training Software (eg Aim Lab_KovaaKs).md | 28 - 10_Wiki/Topics/Cognitive-Architecture.md | 30 - 10_Wiki/Topics/Cognitive-Evaluation-Theory.md | 27 - 10_Wiki/Topics/Cognitive-Therapy-in-CBT.md | 27 - 10_Wiki/Topics/Collaboration_Governance.md | 26 - 10_Wiki/Topics/Collaborative-Filtering.md | 28 - 10_Wiki/Topics/Collective-Intelligence.md | 32 - 10_Wiki/Topics/Combinatorial Game Theory.md | 27 - 10_Wiki/Topics/Combinatorial-Optimization.md | 29 - .../Topics/Combined Arms (제병협동) 전술.md | 27 - .../Topics/Commercial AI Art Production.md | 12 +- .../BLUF (Bottom Line Up Front).md | 12 +- .../Business Presentation.md | 10 +- .../Communication & Tech/Business Writing.md | 12 +- .../Data-Driven Personalization.md | 12 +- .../Effective Code Review Feedback.md | 14 +- .../Executive Briefings.md | 4 +- .../Executive Communication.md | 10 +- .../Executive Presentation.md | 10 +- 10_Wiki/Topics/Communication & Tech/Index.md | 30 +- .../Knowledge Management in Engineering.md | 12 +- .../Persuasive Business Writing.md | 10 +- .../Real-Time Translation.md | 8 +- .../Storytelling in Business.md | 12 +- .../Strategic Communication.md | 16 +- .../Communication & Tech/Tripledot Studios.md | 10 +- .../User Acquisition (UA).md | 12 +- .../사용자 확보 (User Acquisition).md | 10 +- 10_Wiki/Topics/CompCert-C-Compiler.md | 31 - 10_Wiki/Topics/Complexity Theory.md | 32 - 10_Wiki/Topics/Complexity-Theory.md | 29 - 10_Wiki/Topics/Component-Composition.md | 28 - 10_Wiki/Topics/Component_Design_Patterns.md | 28 - 10_Wiki/Topics/Computational Creativity.md | 31 - ... Neuroscience of Reinforcement Learning.md | 28 - .../Graph Theory.md | 8 +- .../Computational Theory & Math/Index.md | 4 +- .../Information Theory.md | 6 +- 10_Wiki/Topics/Computational-Creativity.md | 31 - 10_Wiki/Topics/Computational-Linguistics.md | 29 - .../Topics/Computational-Neuroscience-RL.md | 30 - 10_Wiki/Topics/Computer Vision.md | 32 - 10_Wiki/Topics/Computer-Aided-Design.md | 31 - 10_Wiki/Topics/Computer-Vision.md | 30 - 10_Wiki/Topics/Computer_Vision.md | 29 - .../Topics/Concept Drift (개념 드리프트).md | 29 - ...Drift (개념 드리프트, 모델 지식의 부패).md | 32 - 10_Wiki/Topics/Concept Mapping.md | 31 - 10_Wiki/Topics/Concept-Drift.md | 29 - 10_Wiki/Topics/Concreteness-Principle.md | 28 - 10_Wiki/Topics/Concurrent Programming.md | 31 - .../Topics/Conditioning and Learning ( ).md | 27 - 10_Wiki/Topics/Connect-AI-Documentation.md | 31 - 10_Wiki/Topics/ConnectAI_Dev_Log_20260429.md | 36 - 10_Wiki/Topics/Constitutional AI (헌법 AI).md | 30 - 10_Wiki/Topics/Constitutional-AI.md | 27 - .../Constraint Satisfaction Problems (CSP).md | 29 - .../Constraint-Satisfaction Problems.md | 32 - .../Constraint-Satisfaction-Problems.md | 33 - 10_Wiki/Topics/Context-Aware-Computing.md | 29 - 10_Wiki/Topics/Continuous-Discovery.md | 31 - 10_Wiki/Topics/Contrastive-Learning.md | 29 - 10_Wiki/Topics/Control Systems Engineering.md | 29 - 10_Wiki/Topics/Control-Systems-Engineering.md | 32 - 10_Wiki/Topics/Control-Theory.md | 29 - 10_Wiki/Topics/ControlNet.md | 10 +- .../Topics/Convolutional-Neural-Networks.md | 28 - 10_Wiki/Topics/Core-Web-Vitals-Metrics.md | 31 - 10_Wiki/Topics/Core-Web-Vitals.md | 31 - 10_Wiki/Topics/Corgea.md | 34 - 10_Wiki/Topics/Corporate-LMS-Training.md | 31 - 10_Wiki/Topics/Cost-Benefit Analysis in AI.md | 28 - 10_Wiki/Topics/Creativity Research.md | 33 - 10_Wiki/Topics/Credit Assignment Problem.md | 31 - 10_Wiki/Topics/Cross-Entropy Loss.md | 28 - 10_Wiki/Topics/Cumulative-Layout-Shift-CLS.md | 33 - 10_Wiki/Topics/Curriculum-Learning.md | 28 - .../Topics/Custom-ESLint-Rules-Development.md | 29 - 10_Wiki/Topics/Custom-ESLint-Rules.md | 31 - 10_Wiki/Topics/Custom-Hooks-Patterns.md | 31 - 10_Wiki/Topics/Customer-Journey-Mapping.md | 33 - 10_Wiki/Topics/Cybernetics Foundations.md | 29 - 10_Wiki/Topics/Cybernetics.md | 30 - 10_Wiki/Topics/DAG-Dependency-Management.md | 33 - 10_Wiki/Topics/DALL-E 3 Natural Language.md | 10 +- 10_Wiki/Topics/DALL-E 3 Negation Handling.md | 10 +- .../Topics/DALL-E 3 Synthetic Captioning.md | 12 +- .../DALL-E 3와 GPT-4의 상호작용적 생성.md | 14 +- .../Topics/DALL-E 3의 자연어 기반 최적화.md | 12 +- 10_Wiki/Topics/DDD-Type-Safety.md | 31 - 10_Wiki/Topics/DDD-in-TypeScript.md | 32 - 10_Wiki/Topics/DORA-Metrics.md | 32 - .../DPO (Direct Preference Optimization).md | 32 - 10_Wiki/Topics/DQN.md | 31 - 10_Wiki/Topics/Data Cleaning Algorithms.md | 32 - .../Topics/Data Distillation (데이터 증류).md | 32 - .../Topics/Data-Augmentation Strategies.md | 29 - 10_Wiki/Topics/Data-Ethics and Privacy.md | 29 - 10_Wiki/Topics/Data-Flywheel-Effect.md | 30 - 10_Wiki/Topics/Data-Pipeline Orchestration.md | 29 - 10_Wiki/Topics/Data-Science-in-UX.md | 31 - 10_Wiki/Topics/Data-Transfer-Object-Design.md | 28 - ...ridge_Connection_Refused_Run_Script_Fix.md | 6 +- ...ture_Review_and_Initial_Risk_Assessment.md | 14 +- ...lector_Local_Wiki_Save_Only_Output_Mode.md | 6 +- ...acollector_Mac_Windows_Launcher_Scripts.md | 6 +- ...M_Auth_Browser_and_Stale_Env_Cookie_Fix.md | 4 +- ...ctor_NotebookLM_Automatic_Auth_Recovery.md | 8 +- ..._Automatic_Reauth_Verification_and_Lock.md | 4 +- ...LM_Connection_Guard_and_MCP_Restart_Fix.md | 6 +- ..._Progress_Visibility_and_Auth_Diagnosis.md | 10 +- .../Datacollector-Knowledge-Hub.md | 42 +- 10_Wiki/Topics/Datacollector/Index.md | 24 +- 10_Wiki/Topics/Dead-Space-Series.md | 32 - .../Deceptive Alignment (기만적 정렬).md | 27 - 10_Wiki/Topics/Decision Theory.md | 32 - .../Decision-Trees and Random Forests.md | 28 - 10_Wiki/Topics/Declaration-Files.md | 27 - 10_Wiki/Topics/Deep Q-Networks (DQN).md | 26 - 10_Wiki/Topics/Deep-Convolutional-GANs.md | 31 - 10_Wiki/Topics/Deep-Grammar.md | 30 - 10_Wiki/Topics/Deep-Learning.md | 28 - 10_Wiki/Topics/Deep-Q-Networks-DQN.md | 28 - 10_Wiki/Topics/DeepCode AI.md | 37 - 10_Wiki/Topics/Deepfake-Detection.md | 31 - 10_Wiki/Topics/Deepfake-Technology.md | 28 - 10_Wiki/Topics/Default Mode Network (DMN).md | 29 - 10_Wiki/Topics/DefinitelyTyped.md | 28 - 10_Wiki/Topics/Definitions_of_Game.md | 26 - 10_Wiki/Topics/Degrees-of-Freedom.md | 27 - 10_Wiki/Topics/Deliberate-Practice.md | 27 - .../Topics/Denavit-Hartenberg-Parameters.md | 28 - .../Topics/Dense vs Sparse Neural Networks.md | 27 - 10_Wiki/Topics/Dependency-Graph-Analysis.md | 27 - 10_Wiki/Topics/Dependency-Injection.md | 29 - .../Topics/Dependency-Inversion-Principle.md | 27 - 10_Wiki/Topics/Deployment-Strategy.md | 32 - 10_Wiki/Topics/Deployment_Final_Gate.md | 26 - ...ity-for-Ontarians-with-Disabilities-Act.md | 6 +- ... 모델링 (State Modeling and API Responses).md | 12 +- .../Abstract-Syntax-Tree-Transformation.md | 8 +- .../Abstract-Syntax-Tree-Traversal.md | 12 +- .../Accessibility-Compliance-WCAG.md | 6 +- .../Additive-Type-Logic.md | 10 +- .../Affective User Interfaces (AUI).md | 4 +- .../Agency-in-Game-Design.md | 8 +- ...unication Protocol (에이전트 통신 규약).md | 14 +- .../Agile-UX-Integration.md | 4 +- .../Americans-with-Disabilities-Act-ADA.md | 4 +- .../Apple Human Interface Guidelines.md | 4 +- .../Atomic Design Pattern.md | 6 +- .../Behavior-Driven-Development (BDD).md | 6 +- .../Design & Experience/Business-Strategy.md | 10 +- .../Design & Experience/Code Formatting.md | 14 +- .../FSD (Feature-Sliced Design).md | 8 +- .../Feature-Sliced Design.md | 8 +- .../Design & Experience/GitHub Actions.md | 8 +- 10_Wiki/Topics/Design & Experience/Index.md | 134 +- .../Interface Segregation Principle (ISP).md | 8 +- .../React Performance Optimization.md | 20 +- ...eact 상태 관리 (React State Management).md | 18 +- .../React 상태 관리 및 API 응답 처리.md | 12 +- .../React 컴포넌트 Props 검증.md | 10 +- .../Redux 등 상태 관리 (State Management).md | 12 +- .../Redux 스타일 리듀서 및 액션 관리.md | 8 +- .../Design & Experience/Snyk Open Source.md | 8 +- .../Tree Shaking (번들 크기 최적화).md | 8 +- .../Topics/Design & Experience/Type Alias.md | 8 +- .../Design & Experience/Type Declaration.md | 12 +- ...인터페이스 및 시스템 보호 아키텍처 설계.md | 14 +- .../TypeScript 컴파일러 캐싱 최적화.md | 4 +- .../TypeScript의 안전한 인터페이스 설계.md | 14 +- ...peScript의 인터페이스 및 객체 타입 설계.md | 10 +- .../Design & Experience/UX-Gamification.md | 8 +- .../가상 DOM (Virtual DOM).md | 10 +- .../계층형 아키텍처 (Layered Architecture).md | 16 +- ...규모 프론트엔드 웹 프로젝트 폴더 구조화.md | 10 +- .../도메인 주도 설계 (DDD).md | 12 +- .../도메인 주도 설계(DDD).md | 12 +- .../라이브러리 타입 선언 (dts) 확장.md | 10 +- .../Design & Experience/몰입감 (Presence).md | 12 +- .../바운디드 컨텍스트 (Bounded Context).md | 10 +- ...응형 윈도우 리사이즈(Resize) 이벤트 처리.md | 12 +- ...기 데이터 패칭 (Async Operations Pattern).md | 12 +- .../상태 관리(State Management).md | 12 +- ...e Machine) 모델링 및 Redux 액션_리듀서 설계.md | 12 +- .../상태 모델링 (State Modeling).md | 8 +- .../선언 병합(Declaration Merging).md | 8 +- ...소프트웨어 시스템 설계 및 아키텍처 구축.md | 14 +- ...간 데이터 대시보드 레이아웃 조절 시스템.md | 10 +- .../Design & Experience/엔티티 (Entities).md | 8 +- .../의존성 규칙 (Dependency Rule).md | 12 +- ... 분리 원칙 (Interface Segregation Principle).md | 12 +- .../재조정 (Reconciliation).md | 16 +- ..._ - TypeScript 타입 시스템 (인터페이스 설계).md | 16 +- .../치타 사람 이미지 프롬프트.md | 4 +- ...포넌트 기반 웹 프레임워크 아키텍처 설계.md | 16 +- .../클린 아키텍처 (Clean Architecture).md | 12 +- .../클린 아키텍처(Clean Architecture).md | 14 +- .../Design & Experience/클린 아키텍처.md | 10 +- .../타입 가드 (Type Guards).md | 10 +- .../타입 별칭 (Type Alias).md | 10 +- .../테스트 용이성 (Testability).md | 10 +- .../프론트엔드 컴포넌트 구조화.md | 12 +- .../프론트엔드 컴포넌트 설계.md | 16 +- .../현대 웹 애플리케이션 설계.md | 10 +- .../Core Web Vitals.md | 14 +- .../Topics/Design & Web Performance/Index.md | 2 +- 10_Wiki/Topics/Design-System.md | 33 - 10_Wiki/Topics/Design/Accessibility.md | 6 +- 10_Wiki/Topics/Design/Cognitive_Load.md | 10 +- 10_Wiki/Topics/Design/CrUX.md | 10 +- 10_Wiki/Topics/Design/HCI.md | 8 +- 10_Wiki/Topics/Design/Inclusive_Design.md | 12 +- 10_Wiki/Topics/Design/Index.md | 10 +- 10_Wiki/Topics/Determinism-in-Computing.md | 29 - 10_Wiki/Topics/DevOps-and-UX-Convergence.md | 26 - 10_Wiki/Topics/DevOps-for-AI-MLOps.md | 30 - 10_Wiki/Topics/DevOps_Environment_Setup.md | 24 - 10_Wiki/Topics/DevSecOps.md | 32 - .../Agentic_Software_Engineering.md | 10 +- .../Agile_and_Team_Collaboration.md | 10 +- .../Development/Automated Quality & Review.md | 14 +- 10_Wiki/Topics/Development/CI-CD Pipeline.md | 12 +- .../Topics/Development/Code Refactoring.md | 12 +- .../Development/Code Review Checklist.md | 16 +- .../Collaborative Programming (Pair & Mob).md | 16 +- .../Development Communication Standards.md | 16 +- .../Development/Engineering_Principles.md | 10 +- .../Error_Handling_and_Stability.md | 10 +- .../Frontend_Governance_and_Observability.md | 10 +- 10_Wiki/Topics/Development/Git_Workflows.md | 10 +- .../Development/Legacy_React_Migration.md | 10 +- .../Development/Modern Review Workflow.md | 16 +- .../Modern_React_Engineering_2025.md | 10 +- .../Nextjs_and_Modern_React_Patterns.md | 10 +- .../Performance_and_Memory_Management.md | 10 +- .../Scalable_Frontend_Architecture.md | 10 +- .../Software Engineering Agents (SWE).md | 8 +- .../State_Management_and_Concurrent_React.md | 10 +- .../Topics/Development/Testing Strategy.md | 14 +- 10_Wiki/Topics/Differentiable Programming.md | 27 - 10_Wiki/Topics/Diffusion-Models.md | 28 - .../Digital Intellectual Property Rights.md | 29 - 10_Wiki/Topics/Digital Thread Integration.md | 29 - 10_Wiki/Topics/Digital-Twin-Technology.md | 29 - 10_Wiki/Topics/Dijkstra's Algorithm.md | 27 - 10_Wiki/Topics/Dimensionality-Reduction.md | 28 - .../Diminishing Returns (한계 수익 체감).md | 29 - .../Directed-Acyclic-Graph-Build-Systems.md | 29 - ...ted-Acyclic-Graph-Dependency-Management.md | 29 - ...Discriminated-Unions-for-Error-Handling.md | 29 - ...Discriminated-Unions-for-State-Modeling.md | 28 - 10_Wiki/Topics/Discriminated-Unions.md | 31 - 10_Wiki/Topics/Dissipative-Structures.md | 31 - 10_Wiki/Topics/Distillation.md | 31 - .../Distributed Reinforcement Learning.md | 27 - 10_Wiki/Topics/Distributed-Computing.md | 29 - .../Topics/Distributed-System-Type-Safety.md | 31 - 10_Wiki/Topics/Distributed-Systems.md | 31 - 10_Wiki/Topics/Documentation-Strategy.md | 32 - 10_Wiki/Topics/Domain Objects.md | 35 - 10_Wiki/Topics/Domain-Driven-Design-DDD.md | 29 - 10_Wiki/Topics/Domain-Specific-Languages.md | 30 - 10_Wiki/Topics/Dopamine-Modeling.md | 32 - 10_Wiki/Topics/Dopaminergic Reward System.md | 26 - 10_Wiki/Topics/Dopaminergic Reward Systems.md | 29 - 10_Wiki/Topics/Drama Management Systems.md | 27 - 10_Wiki/Topics/Dramaturgy-Theory.md | 31 - 10_Wiki/Topics/Dry-Principle.md | 24 - .../Dynamic Difficulty Adjustment (DDA).md | 28 - .../Dynamic Few-Shot (동적 퓨샷 선택 전략).md | 29 - 10_Wiki/Topics/Dynamic-Capabilities.md | 31 - .../Topics/Dynamic-Creative-Optimization.md | 32 - .../Topics/Dynamic-Environment-Handling.md | 27 - 10_Wiki/Topics/Dynamic-Programming.md | 33 - 10_Wiki/Topics/E-Learning-Gamification.md | 32 - .../Topics/E-commerce-Catalog-Management.md | 27 - 10_Wiki/Topics/E-commerce-Optimization.md | 28 - 10_Wiki/Topics/ESLint-Plugin-Development.md | 31 - 10_Wiki/Topics/ESLint-Static-Analysis.md | 26 - .../Topics/EU-Web-Accessibility-Directive.md | 28 - .../Topics/Ecology and Ecosystem Modeling.md | 27 - 10_Wiki/Topics/Economic-Analysis.md | 31 - 10_Wiki/Topics/Economic-Complexity-Index.md | 30 - 10_Wiki/Topics/Economic-Mobility.md | 34 - .../2025 Casual Gaming Apps Report.md | 10 +- .../2026년 BCG 글로벌 게이밍 설문조사.md | 8 +- .../AI 기반 보상 및 난이도 스케일링.md | 6 +- .../Economics & Algorithms/ARPU-ARPPU.md | 8 +- .../Base 플랫폼(Chef Universe).md | 10 +- .../Economics & Algorithms/Beresnev Studio.md | 8 +- .../CPI (Cost Per Install).md | 8 +- .../Economics & Algorithms/Capybara GO!.md | 8 +- .../Economics & Algorithms/Chef Universe.md | 8 +- .../Continuous Obsolescence.md | 8 +- .../Economics & Algorithms/Dynamic Offers.md | 14 +- .../Dynamic Pricing & Offers.md | 12 +- .../Economics & Algorithms/Dynamic Pricing.md | 10 +- .../EVE 온라인(EVE Online).md | 8 +- .../Economics & Algorithms/EVE 온라인.md | 8 +- .../Topics/Economics & Algorithms/Fortnite.md | 10 +- .../Game of War- Fire Age BM 구조.md | 10 +- ...e of War- Fire Age BM 및 게임 구조 분석.md | 20 +- .../Game of War- Fire Age BM.md | 12 +- .../Hedera(HCS 및 Fauxkens).md | 8 +- .../Topics/Economics & Algorithms/Index.md | 54 +- .../Kick-back System.md | 8 +- .../LTV (Lifetime Value).md | 10 +- .../Lifetime Value (LTV).md | 10 +- .../Love and Deepspace.md | 8 +- .../MMORPG 영속적 세계와 자원 관리.md | 8 +- .../Machinations 라이브옵스 데이터 연동.md | 14 +- .../Machinations(토크노믹스 시뮬레이션).md | 12 +- .../Economics & Algorithms/Machinations.md | 10 +- .../Market Entry Strategy.md | 10 +- .../Monetization (BM).md | 14 +- .../Monetization Strategy.md | 20 +- .../Monetization at the Point of Friction.md | 14 +- ...GO! 및 Royal Match의 라이브 이벤트 구조.md | 10 +- .../Economics & Algorithms/Monopoly GO!.md | 10 +- .../Economics & Algorithms/Play-and-Earn.md | 8 +- .../Profitability Framework.md | 8 +- .../Project Awakening(CCP Games).md | 8 +- .../Topics/Economics & Algorithms/Roblox.md | 12 +- .../Supercell의 모바일 게임 개발.md | 8 +- .../Economics & Algorithms/Triple Match 3D.md | 8 +- .../Economics & Algorithms/Whale Hunting.md | 8 +- .../Willingness to Pay (WTP).md | 10 +- ...버-그레인저 방법 (Gabor-Granger Method).md | 8 +- ...이션 및 사전 검증(Virtual Economy Simulation).md | 10 +- ...상 경제 시스템(Virtual Economy System).md | 8 +- .../가상 경제 시스템.md | 12 +- .../가상 경제 시스템의 구조적 무결성 분석.md | 10 +- ... 경제 인플레이션(Game Economy Inflation).md | 10 +- ...제 인플레이션(Virtual Economy Inflation).md | 8 +- .../가상 경제 인플레이션.md | 8 +- .../가상 경제(Virtual Economy).md | 12 +- .../Economics & Algorithms/가상 경제.md | 6 +- .../가차(Gacha) 시스템.md | 6 +- .../Economics & Algorithms/가차(Gacha).md | 8 +- .../가챠(Gacha) 시스템.md | 8 +- .../게임 경제 균형(Game Economy Balance).md | 10 +- .../게임 경제 밸런스(Game Balance).md | 12 +- .../게임 경제 설계(Game Economy Design).md | 10 +- .../Economics & Algorithms/게임 경제 설계.md | 10 +- ... 경제 인플레이션(Game Economy Inflation).md | 12 +- .../게임 내 광고(IAA).md | 6 +- .../게임 데이터 분석(Game Analytics).md | 10 +- .../Economics & Algorithms/게임 밸런싱.md | 14 +- ...게임 수익화 전략(Monetization Strategy).md | 12 +- .../게임 수익화 전략.md | 14 +- .../게임파이(GameFi).md | 10 +- .../결제 사용자당 평균 매출(ARPPU).md | 8 +- .../경제 밸런싱(Economic Balancing).md | 10 +- .../고객 유지율(Retention).md | 8 +- .../고객 평생 가치(LTV).md | 8 +- .../과금 의향 (Willingness to Pay).md | 10 +- .../관리자 상점(Admin Shop).md | 8 +- .../기간 한정 제안(Limited-time offers).md | 8 +- .../뉴 월드(New World).md | 8 +- .../다중 게임 경제(Multi-Game Economies).md | 10 +- ... 게임 구독 모델(Multigame Subscriptions).md | 12 +- ...다중 통화 시스템(Multi-Currency System).md | 8 +- ...화 전략 분석 및 가상 경제 시스템 검증 프로젝트.md | 14 +- .../동적 가격 책정(Dynamic Pricing).md | 10 +- .../디아블로 2(Diablo II).md | 8 +- .../디지털 트윈 및 데이터 시뮬레이션.md | 14 +- .../라이브옵스(Live-ops).md | 12 +- .../리더보드(Leaderboards).md | 8 +- .../리텐션(Retention).md | 8 +- .../마키네이션(Machinations.io) 시뮬레이션.md | 12 +- ...춤형 IAP 번들(Customizable IAP bundles).md | 10 +- ... 수익화 (Dynamic Offers & Staircase Monetization).md | 8 +- .../멀티 게임 경제(Multi-Game Economy).md | 12 +- .../메타 레이어 (Meta Layers).md | 14 +- ...개발 핵심 지표(Mobile Game Development KPIs).md | 8 +- .../모바일 게임 수익화 모델.md | 10 +- ...일 게임 수익화(Mobile Game Monetization).md | 10 +- ... 게임(Mobile PvP Game) 환경에서의 경제 밸런싱.md | 8 +- ...주얼 게임 시장(Mobile Casual Game Market).md | 10 +- .../몬테카를로 시뮬레이션.md | 10 +- .../무료 플레이(Free-to-Play) 모델.md | 10 +- ... 확장성 경제 (Infinitely Scalable Economy).md | 12 +- .../물리 기반 렌더링(PBR).md | 10 +- .../미세결제(Microtransactions).md | 10 +- .../Economics & Algorithms/미호요(miHoYo).md | 8 +- .../Economics & Algorithms/배수구(Sinks).md | 10 +- .../베레스네프(Beresnev).md | 8 +- .../Economics & Algorithms/보상 시스템.md | 12 +- ... 유료화 메타게임(Free-to-play metagame).md | 10 +- .../부분 유료화(Free-to-Play).md | 12 +- .../부분 유료화(Freemium) 게임 경제 모델링.md | 10 +- .../사용자 생성 콘텐츠(UGC).md | 12 +- .../사용자 참여도(Player Engagement).md | 14 +- ...공적인 게임 경제 설계와 핵심 지표 분석.md | 8 +- .../소액 결제 (Microtransactions).md | 14 +- .../Economics & Algorithms/소유 효과.md | 10 +- .../소프트 싱크(Soft Sinks).md | 8 +- .../수도꼭지(Faucets).md | 8 +- .../수도꼭지와 배수구(Faucets and Sinks).md | 6 +- .../수도꼭지와 배수구(Taps and Sinks).md | 6 +- .../수요와 공급(Supply and Demand).md | 10 +- .../Economics & Algorithms/수익화 전략.md | 10 +- .../수익화(Monetization).md | 12 +- .../시뮬레이션(Simulation).md | 14 +- ... 척도 연구(In-Game Purchase Motivation Scale Study).md | 8 +- ...비온 온라인(Albion Online)의 경제 시스템.md | 8 +- .../어포던스(Affordances).md | 8 +- .../에셋 재사용(Asset Reuse).md | 10 +- .../연속 승리 이벤트(Streak events).md | 10 +- .../Economics & Algorithms/오디오 광고.md | 10 +- .../원신(Genshin Impact)의 레진 시스템.md | 8 +- ...Genshin Impact)의 진행 제한과 가차 시스템.md | 6 +- ...월드 오브 워크래프트(World of Warcraft).md | 8 +- ...중 게임 경제(Web3 & Multi-Game Economies).md | 14 +- ...보상 구조(Structures of Risks and Rewards).md | 8 +- .../위험과 보상(Risks and Rewards).md | 10 +- .../유니버스 LTV(Universe LTV).md | 10 +- .../유닛 이코노믹스(LTV와 CAC).md | 8 +- .../유저 평균 매출(ARPU).md | 8 +- .../유지율(Retention Rate).md | 10 +- .../이브 온라인(EVE Online).md | 8 +- .../Economics & Algorithms/이커머스 플랫폼.md | 10 +- .../이탈률(Churn Rate).md | 8 +- ...임 결제 동기(In-Game Purchase Motivation).md | 14 +- .../인게임 수익화(In-Game Monetization).md | 10 +- .../Economics & Algorithms/인앱 결제(IAP).md | 8 +- .../Economics & Algorithms/인앱 광고 (IAA).md | 10 +- .../Economics & Algorithms/인앱 광고(IAA).md | 10 +- .../Economics & Algorithms/인앱 구매 (IAP).md | 12 +- .../Economics & Algorithms/인앱 구매(IAP).md | 10 +- .../인플레이션 관리(Inflation Management).md | 10 +- .../Economics & Algorithms/인플레이션 관리.md | 12 +- .../인플레이션(Inflation).md | 10 +- .../자원 로지스틱스(Resource Logistics).md | 14 +- ...관 및 압축(Resource Storage & Compression).md | 6 +- .../자원 소모처(Sinks).md | 8 +- .../잔존율(Retention).md | 10 +- .../장기 운영 게임(Long-running Games).md | 10 +- .../전리품 상자(Loot Box).md | 8 +- ...상거래 소비자 참여 및 보상 시스템 최적화.md | 8 +- .../지불 용의 (Willingness to Pay).md | 6 +- .../초인플레이션(Hyperinflation).md | 10 +- .../콘텐츠 로테이션(Content Rotation).md | 8 +- ...스 플랫폼 기술(Cross-Platform Technology).md | 8 +- .../크로스 플랫폼(Cross-Platform) 아키텍처.md | 12 +- .../클라우드 게이밍(Cloud Gaming).md | 10 +- .../클래시 로얄 라틴 아메리카 챔피언십.md | 10 +- .../클래시 로얄(Clash Royale)의 엘릭서.md | 12 +- .../탭과 싱크(Taps and Sinks).md | 8 +- ...통제된 인플레이션(Controlled Inflation).md | 8 +- .../페이 투 윈 (Pay to Win).md | 67 + .../페이 투 윈(Pay to Win).md | 22 - .../포켓랜드(Pocket Land).md | 10 +- .../포켓몬 마스터즈 EX(Pokemon Masters EX).md | 8 +- ...tnite) 및 로블록스(Roblox)의 UGC 창작자 경제.md | 10 +- .../프리미엄 모델 (Freemium Model).md | 10 +- ...미엄 통화 브릿지(Premium Currency Bridge).md | 8 +- .../프리미엄 통화(Premium Currency).md | 8 +- .../플랫폼 컨버전스(Platform Convergence).md | 12 +- .../플레이어 기반 경제.md | 8 +- .../플레이어 잔존율(Player Retention).md | 8 +- .../핀치 포인트(Pinch Point).md | 8 +- .../하드 싱크(Hard Sinks).md | 6 +- ...하이브리드 수익화 (Hybrid Monetization).md | 6 +- .../하이브리드 수익화 모델.md | 8 +- ... 수익화 전략(Hybrid Monetization Strategy).md | 8 +- .../하이브리드 수익화(Hybrid Monetization).md | 8 +- .../하이브리드 수익화.md | 6 +- ...브리드 캐주얼 게임(Hybrid-casual Games).md | 8 +- ...리드 캐주얼 퍼즐 게임(Hybrid Puzzle Games).md | 10 +- .../하이브리드 캐주얼(Hybrid-Casual).md | 12 +- ...주얼(Hybrid-casual)의 하이브리드 수익화 모델.md | 6 +- .../핵심 루프(Core Loop).md | 10 +- .../핵심 성과 지표(KPI).md | 8 +- .../행동 경제학(Behavioral Economics).md | 10 +- .../Economics & Algorithms/행동 경제학.md | 8 +- .../행동 유도성(Affordances).md | 8 +- .../Economics & Algorithms/행동경제학.md | 8 +- 10_Wiki/Topics/Economics-of-Information.md | 32 - 10_Wiki/Topics/Edge-AI-and-Computing.md | 28 - .../Topics/Edge-Artificial-Intelligence.md | 33 - 10_Wiki/Topics/Edge-Computing.md | 31 - 10_Wiki/Topics/Edtech-Industry-Trends.md | 31 - 10_Wiki/Topics/Education/Adaptive_Learning.md | 4 +- .../Behavioral Interview Questions.md | 10 +- 10_Wiki/Topics/Education/Case Interviews.md | 8 +- .../Education/Consulting Case Interviews.md | 12 +- 10_Wiki/Topics/Education/Index.md | 20 +- .../Management Consulting (경영 컨설팅).md | 12 +- .../Management Consulting Case Interviews.md | 10 +- .../Management Consulting Reports.md | 8 +- .../Topics/Education/Management Consulting.md | 12 +- .../Topics/Education/McKinsey & Company.md | 12 +- .../Education/McKinsey Case Interview.md | 10 +- 10_Wiki/Topics/Effective-Altruism-in-AI.md | 31 - 10_Wiki/Topics/Efficiency.md | 31 - .../Topics/Eigenvalues-and-Eigenvectors.md | 31 - 10_Wiki/Topics/Eligibility-Traces.md | 29 - .../Topics/Elite-Sport-Science-Protocols.md | 27 - .../Topics/Elite-Strength-and-Conditioning.md | 24 - 10_Wiki/Topics/Elite-Theory.md | 31 - 10_Wiki/Topics/Embodied Cognition.md | 24 - 10_Wiki/Topics/Embodied-AI.md | 29 - .../Topics/Emergence-in-Complex-Systems.md | 31 - 10_Wiki/Topics/Emergence-in-Systems.md | 28 - 10_Wiki/Topics/Emergence.md | 31 - .../Emotional-AI (Affective Computing).md | 29 - ...lly Intelligent Tutoring Systems (EITS).md | 24 - 10_Wiki/Topics/Empathy-in-AI.md | 31 - .../Encapsulation-and-Information-Hiding.md | 26 - .../Encapsulation-of-Domain-Invariants.md | 28 - .../Encapsulation-via-Access-Modifiers.md | 27 - 10_Wiki/Topics/End-to-End-Learning.md | 29 - .../Topics/End-to-End-Testing-Strategies.md | 32 - .../Topics/Endurance-Athletics-Cognition.md | 24 - 10_Wiki/Topics/Ensemble-Learning.md | 31 - 10_Wiki/Topics/Ensemble-Methods.md | 28 - 10_Wiki/Topics/Ensuring-Data-Privacy.md | 31 - 10_Wiki/Topics/Enterprise-Design-Systems.md | 25 - .../Enterprise-Resource-Planning-Systems.md | 25 - .../Enterprise-Scale-Monorepo-Management.md | 25 - 10_Wiki/Topics/Enterprise-Service-Bus.md | 32 - .../Enterprise-Software-Architecture.md | 25 - .../Topics/Enterprise-Software-Engineering.md | 25 - .../Topics/Entity-Relationship-Modeling.md | 33 - .../Topics/Entropy in Information Theory.md | 28 - 10_Wiki/Topics/Environment-Design-in-RL.md | 29 - 10_Wiki/Topics/Enzyme-Inhibition-Kinetics.md | 31 - 10_Wiki/Topics/Epidemiological-Modeling.md | 32 - 10_Wiki/Topics/Epistemic-Uncertainty.md | 28 - 10_Wiki/Topics/Epistemology.md | 32 - 10_Wiki/Topics/Equality.md | 31 - 10_Wiki/Topics/Ergodic-Theory.md | 30 - .../Topics/Ergonomics-in-Workspace-Design.md | 29 - 10_Wiki/Topics/Error-Boundary-Pattern.md | 26 - 10_Wiki/Topics/Es-Lint-Configuration.md | 27 - 10_Wiki/Topics/Escalation-of-Commitment.md | 32 - 10_Wiki/Topics/Ethical-Decision-Making.md | 33 - 10_Wiki/Topics/Ethics & AI.md | 32 - .../Topics/Ethics of Autonomous Systems.md | 29 - .../Ethics-in-Artificial-Intelligence.md | 27 - 10_Wiki/Topics/Ethnographic-Research.md | 31 - 10_Wiki/Topics/Etiology-of-Disease.md | 31 - 10_Wiki/Topics/Eudaimonia-and-Well-being.md | 30 - 10_Wiki/Topics/Eugen Systems 모딩 매뉴얼.md | 28 - ...stems의 Iriszoom 엔진 및 전략 게임 개발.md | 32 - .../Eugen Systems의 WARNO 시뮬레이션 개발.md | 31 - ...냉전기 가상 시나리오 및 모딩 생태계 구축.md | 34 - 10_Wiki/Topics/Event-Driven-Architecture.md | 29 - 10_Wiki/Topics/Evolutionary Biology.md | 25 - 10_Wiki/Topics/Evolutionary Computation.md | 25 - .../Topics/Evolutionary-Algorithm-Design.md | 32 - 10_Wiki/Topics/Evolutionary-Algorithms.md | 33 - 10_Wiki/Topics/Evolutionary-Computation.md | 29 - 10_Wiki/Topics/Excess-Property-Checking.md | 27 - 10_Wiki/Topics/Executive Dysfunction.md | 27 - 10_Wiki/Topics/Executive-Function-Deficit.md | 26 - 10_Wiki/Topics/Exhaustiveness-Checking.md | 27 - 10_Wiki/Topics/Expectation-Maximization.md | 30 - 10_Wiki/Topics/Expected Utility Theory.md | 29 - 10_Wiki/Topics/Experience-Replay.md | 29 - 10_Wiki/Topics/Experience-Sampling-Method.md | 31 - 10_Wiki/Topics/Explainable-AI (XAI).md | 32 - 10_Wiki/Topics/Explainable-AI-XAI.md | 29 - 10_Wiki/Topics/Exploding-Gradient Problem.md | 28 - 10_Wiki/Topics/Exploration vs Exploitation.md | 32 - 10_Wiki/Topics/Exploration-vs-Exploitation.md | 29 - 10_Wiki/Topics/Exploratory-Data-Analysis.md | 29 - 10_Wiki/Topics/Expo 2025 Osaka.md | 33 - 10_Wiki/Topics/Exponential-Growth.md | 31 - 10_Wiki/Topics/Extended-Reality-XR.md | 29 - 10_Wiki/Topics/Externalities.md | 30 - 10_Wiki/Topics/Extreme-Programming-XP.md | 30 - 10_Wiki/Topics/Eye-Tracking-in-UX-Research.md | 29 - 10_Wiki/Topics/Eye-Tracking.md | 33 - 10_Wiki/Topics/Factor-Analysis.md | 28 - 10_Wiki/Topics/Factory-Pattern.md | 25 - 10_Wiki/Topics/Failable-Task-Handling.md | 27 - 10_Wiki/Topics/Fault-Tolerance.md | 31 - .../Topics/Feature Clamping (피처 고정).md | 29 - 10_Wiki/Topics/Feature-Engineering.md | 30 - 10_Wiki/Topics/Feature-Flags.md | 26 - 10_Wiki/Topics/Federated-Learning.md | 30 - 10_Wiki/Topics/Feedback-Control-Systems.md | 29 - 10_Wiki/Topics/Feedback-Loops in Systems.md | 27 - 10_Wiki/Topics/Feedback-Loops-in-Design.md | 30 - 10_Wiki/Topics/Feedback-Loops.md | 30 - 10_Wiki/Topics/Few-Shot-Learning.md | 28 - 10_Wiki/Topics/Figma-to-Code-Workflow.md | 27 - 10_Wiki/Topics/Figurative-Language.md | 32 - .../Topics/Financial Modeling & Math/Index.md | 2 +- .../Quantitative Finance.md | 14 +- 10_Wiki/Topics/Fine-tuning.md | 31 - 10_Wiki/Topics/Finished Goods.md | 31 - 10_Wiki/Topics/Finite-Element-Analysis.md | 29 - 10_Wiki/Topics/Finite-State-Machines-FSM.md | 29 - 10_Wiki/Topics/Finite-State-Machines.md | 32 - 10_Wiki/Topics/First Input Delay (FID).md | 33 - 10_Wiki/Topics/Fitness-Landscape.md | 28 - .../Fixed Time Step vs Variable Time Step.md | 31 - 10_Wiki/Topics/Flow State.md | 29 - 10_Wiki/Topics/Flow-State.md | 31 - 10_Wiki/Topics/Fluent-Interface-Design.md | 27 - 10_Wiki/Topics/Fluid-Dynamics for Games.md | 28 - 10_Wiki/Topics/Focal-Loss.md | 27 - 10_Wiki/Topics/Formal Methods.md | 31 - .../Topics/Formal-Verification-of-Software.md | 26 - 10_Wiki/Topics/Foundation-Models.md | 32 - 10_Wiki/Topics/Fragility.md | 32 - 10_Wiki/Topics/Free-Energy-Principle.md | 30 - .../Topics/Frontend & Concurrency/Index.md | 2 +- .../Web Worker (웹 워커).md | 16 +- ...ntend-Architecture-and-Folder-Structure.md | 30 - 10_Wiki/Topics/Frontend-Architecture.md | 30 - .../Topics/Frontend-Debugging-and-Testing.md | 32 - ...Frontend-Performance-Optimization-Guide.md | 29 - ...ntend-Team-Collaboration-and-Governance.md | 29 - 10_Wiki/Topics/Frontend.md | 31 - ..._Structure_Audit_and_Stabilization_Plan.md | 36 +- ...al_Stylized_Casual_Magitech_Redirection.md | 12 +- ...AC_LevelUp_Stylized_Casual_Magitech_Fix.md | 8 +- ...Skybound_Nova_Burst_Icon_and_Effect_Fix.md | 6 +- ...und_Particle_and_Supply_Readability_Fix.md | 6 +- ...irealistic_Magitech_Fantasy_Redirection.md | 6 +- ...bound_Stylized_Casual_Magitech_Art_Pack.md | 14 +- ...ylized_Casual_Magitech_Ingame_Asset_Fix.md | 6 +- ...ybound_Survivor_Like_Balance_Curve_Pass.md | 10 +- ...ridge_Connection_Refused_Run_Script_Fix.md | 6 +- ...ture_Review_and_Initial_Risk_Assessment.md | 14 +- ...lector_Local_Wiki_Save_Only_Output_Mode.md | 6 +- ...acollector_Mac_Windows_Launcher_Scripts.md | 6 +- ...M_Auth_Browser_and_Stale_Env_Cookie_Fix.md | 4 +- ...ctor_NotebookLM_Automatic_Auth_Recovery.md | 8 +- ..._Automatic_Reauth_Verification_and_Lock.md | 4 +- ...LM_Connection_Guard_and_MCP_Restart_Fix.md | 6 +- ..._Progress_Visibility_and_Auth_Diagnosis.md | 10 +- ...re_Gameplay_Rebalance_and_Purpose_Reset.md | 14 +- ...frame_and_8Stage_Boss_Continuity_Rework.md | 2 +- ...l_Concept_and_Hangar_Layout_Overlap_Fix.md | 6 +- ...p_DirectKill_and_UI_Productization_Pass.md | 4 +- ...vivors_Loop_and_Stage_Curve_Preparation.md | 2 +- ...age_Pressure_and_Projectile_Visual_Pass.md | 2 +- ...nd_HP_Scarcity_and_Module_Cache_Rewards.md | 2 +- ...nvasion_Response_Stage_Difficulty_Curve.md | 2 +- ...und_Miniboss_Treasure_Cache_Reward_Loop.md | 2 +- ...Skybound_Player_Sprite_Path_Warning_Fix.md | 2 +- ...eward_Card_Clarity_and_Command_Cache_UI.md | 2 +- ...de_and_Weapon_Transform_Reconfiguration.md | 2 +- ..._Balance_Bomb_and_Visual_Diversity_Pass.md | 2 +- ..._Stage_Miniboss_Pattern_Differentiation.md | 6 +- .../Frontend_Mastery/Accessibility (A11y).md | 18 +- .../Topics/Frontend_Mastery/Accessibility.md | 16 +- .../Accessible UI Libraries.md | 18 +- .../Topics/Frontend_Mastery/Atomic Design.md | 14 +- .../Frontend_Mastery/Automatic Batching.md | 12 +- ...ic Batching을 통한 React 18 성능 최적화.md | 10 +- .../BEM (Block Element Modifier).md | 12 +- 10_Wiki/Topics/Frontend_Mastery/BEM.md | 12 +- .../Building Reusable UI Components.md | 20 +- .../Frontend_Mastery/CSR vs SSR vs SSG.md | 14 +- .../Topics/Frontend_Mastery/CSS Animations.md | 12 +- .../Frontend_Mastery/CSS Architecture.md | 16 +- .../Frontend_Mastery/CSS Container Queries.md | 16 +- .../Frontend_Mastery/CSS Grid 및 Flexbox.md | 10 +- 10_Wiki/Topics/Frontend_Mastery/CSS Grid.md | 8 +- .../Frontend_Mastery/CSS Media Queries.md | 14 +- .../Topics/Frontend_Mastery/CSS Modules.md | 18 +- .../CSS Performance Optimization.md | 14 +- .../Topics/Frontend_Mastery/CSS Variables.md | 20 +- .../Frontend_Mastery/CSS 구조 설계 방식.md | 16 +- ...능 최적화(CSS Performance Optimization).md | 16 +- ...니메이션 성능(CSS Animation Performance).md | 14 +- ...이션 최적화(CSS Animations Optimization).md | 12 +- ...메이션 최적화(Optimizing CSS Animations).md | 10 +- 10_Wiki/Topics/Frontend_Mastery/CSS-in-JS.md | 20 +- .../CSSOM(CSS Object Model).md | 12 +- 10_Wiki/Topics/Frontend_Mastery/CSSOM.md | 10 +- .../Frontend_Mastery/Client Components.md | 16 +- .../Client-Side Rendering (CSR).md | 14 +- .../Frontend_Mastery/Component API Design.md | 16 +- .../Component Library Architecture.md | 24 +- .../Component-Based Architecture (CBA).md | 12 +- .../Component-Based Architecture.md | 12 +- .../Component-Based Design.md | 26 +- .../Compound Components Pattern.md | 14 +- .../Frontend_Mastery/Compound Components.md | 14 +- .../Frontend_Mastery/Concurrent Rendering.md | 18 +- .../Frontend_Mastery/Container Queries.md | 10 +- .../Topics/Frontend_Mastery/Context API.md | 12 +- ...Web Vitals Optimization (INP, LCP 개선).md | 22 +- .../Frontend_Mastery/Core Web Vitals.md | 10 +- .../Critical Rendering Path (CRP).md | 16 +- .../Critical Rendering Path.md | 16 +- .../DOM (Document Object Model).md | 14 +- .../Frontend_Mastery/DOM vs Virtual DOM.md | 14 +- .../Topics/Frontend_Mastery/DOM 및 CSSOM.md | 14 +- .../DOM(Document Object Model).md | 18 +- 10_Wiki/Topics/Frontend_Mastery/DOM.md | 20 +- .../Design System Architecture.md | 32 +- .../Topics/Frontend_Mastery/Design Systems.md | 22 +- .../Topics/Frontend_Mastery/Design Tokens.md | 14 +- .../Frontend_Mastery/Diffing Algorithm.md | 14 +- 10_Wiki/Topics/Frontend_Mastery/Downshift.md | 10 +- .../Frontend_Mastery/Dynamic Theming.md | 18 +- .../Frontend_Mastery/E-commerce Platforms.md | 10 +- .../Feature-Driven Architecture.md | 16 +- .../Feature-Sliced Design (FSD).md | 16 +- .../Frontend_Mastery/Feature-Sliced Design.md | 12 +- .../Frontend_Mastery/Fiber Architecture.md | 14 +- .../Fiber 아키텍처 (Fiber Architecture).md | 16 +- ...키텍처와 동시성 (Concurrent Rendering).md | 18 +- .../Figma Design System Integration.md | 12 +- .../Frontend_Mastery/Figma Integration.md | 14 +- .../Frontend_Mastery/Figma Tokens Studio.md | 14 +- .../First Contentful Paint (FCP).md | 14 +- 10_Wiki/Topics/Frontend_Mastery/Flexbox.md | 8 +- .../Frontend_Mastery/Fluid Typography.md | 10 +- .../GPU Acceleration (Compositing).md | 10 +- .../GPU 가속 및 Compositing.md | 6 +- .../Frontend_Mastery/GPU 가속 및 컴포지팅.md | 6 +- .../GPU 가속(GPU Acceleration).md | 8 +- .../Frontend_Mastery/Headless Components.md | 20 +- .../Topics/Frontend_Mastery/Headless UI.md | 14 +- .../Frontend_Mastery/Hydration 성능 최적화.md | 20 +- 10_Wiki/Topics/Frontend_Mastery/Hydration.md | 14 +- 10_Wiki/Topics/Frontend_Mastery/Index.md | 782 ++--- .../Interaction to Next Paint (INP).md | 16 +- .../Frontend_Mastery/Island Architecture.md | 10 +- 10_Wiki/Topics/Frontend_Mastery/Lane Model.md | 18 +- .../Topics/Frontend_Mastery/Lanes Model.md | 10 +- .../Large Frontend Projects.md | 20 +- .../Frontend_Mastery/Layout Thrashing.md | 10 +- 10_Wiki/Topics/Frontend_Mastery/Lighthouse.md | 12 +- 10_Wiki/Topics/Frontend_Mastery/MUI.md | 16 +- .../Frontend_Mastery/Meta Quest Store.md | 10 +- .../Frontend_Mastery/Mobile-First Approach.md | 10 +- .../Frontend_Mastery/Mobile-First Design.md | 8 +- .../Modern Scalable Frontend Architecture.md | 32 +- .../Frontend_Mastery/Monorepo Architecture.md | 18 +- .../Frontend_Mastery/Next.js 15 App Router.md | 16 +- 10_Wiki/Topics/Frontend_Mastery/Next.js 15.md | 16 +- .../Next.js App Router Migration.md | 20 +- .../Next.js App Router Styling Strategies.md | 16 +- .../Next.js App Router 프로젝트.md | 14 +- ....js App Router 환경의 컴포넌트 스타일링.md | 14 +- .../Frontend_Mastery/Next.js App Router.md | 18 +- ... Modular and Scalable Project Structure.md | 20 +- .../Next.js 기반 대규모 웹 애플리케이션.md | 16 +- ... Hybrid Rendering (SSR-CSR-RSC 혼합 적용).md | 14 +- .../Frontend_Mastery/Next.js 렌더링 최적화.md | 14 +- ...서의 UI 컴포넌트 스타일링 및 렌더링 최적화.md | 22 +- 10_Wiki/Topics/Frontend_Mastery/Next.js.md | 10 +- ... 성능 최적화 하이브리드 렌더링 아키텍처 설계.md | 12 +- ...브리드 렌더링 및 React Server Components 도입.md | 16 +- ... 활용한 하이브리드 렌더링 및 SEO 최적화.md | 14 +- .../Frontend_Mastery/Overrides Pattern.md | 8 +- .../Performance Optimization.md | 20 +- .../Topics/Frontend_Mastery/Prop Drilling.md | 10 +- .../Topics/Frontend_Mastery/Public APIs.md | 12 +- 10_Wiki/Topics/Frontend_Mastery/Radix UI.md | 12 +- .../Frontend_Mastery/React 16+ Core Engine.md | 10 +- .../React 18 & 19 Performance Optimization.md | 20 +- .../React 18 Concurrent Features.md | 26 +- ...18 동시성 렌더링 (Concurrent Rendering).md | 16 +- ...괄 처리 및 React 19 컴파일러 최적화 적용.md | 18 +- 10_Wiki/Topics/Frontend_Mastery/React 18.md | 16 +- 10_Wiki/Topics/Frontend_Mastery/React 19.md | 16 +- .../Frontend_Mastery/React Applications.md | 26 +- .../Topics/Frontend_Mastery/React Compiler.md | 16 +- .../React Component Architecture.md | 22 +- .../React Component Library Architecture.md | 22 +- .../React Component Patterns.md | 24 +- .../Frontend_Mastery/React Context API.md | 14 +- .../Topics/Frontend_Mastery/React Context.md | 14 +- .../Frontend_Mastery/React Design Systems.md | 24 +- .../Frontend_Mastery/React Design Tokens.md | 20 +- .../React Fiber Architecture.md | 12 +- .../React Fiber 및 동시성 렌더링.md | 18 +- .../Frontend_Mastery/React Fiber 아키텍처.md | 14 +- .../Topics/Frontend_Mastery/React Fiber.md | 16 +- .../Frontend_Mastery/React Flight Protocol.md | 12 +- .../React Frontend Architecture.md | 28 +- .../React Performance Optimization.md | 24 +- .../React Server Components (RSC).md | 14 +- ... Components(RSC) 환경의 스타일링 최적화.md | 14 +- ...eact 기반 대규모 웹 애플리케이션 최적화.md | 20 +- ... 페이지 애플리케이션(SPA)의 렌더링 최적화.md | 24 +- .../React 기반 프론트엔드 성능 최적화.md | 28 +- ...성 훅 (useTransition, useDeferredValue).md | 10 +- .../Frontend_Mastery/React 렌더링 최적화.md | 20 +- ...act 서버 컴포넌트 (RSC) 및 Next.js 환경.md | 16 +- ... 최적화 (React Performance Optimization).md | 20 +- .../Frontend_Mastery/React 성능 최적화.md | 16 +- .../React 컴파일러 (React Compiler).md | 12 +- .../React 컴포넌트 기반 아키텍처.md | 20 +- .../React-Vue-Angular 프레임워크.md | 12 +- .../Frontend_Mastery/React가 빠른 이유.md | 16 +- .../Topics/Frontend_Mastery/Reconciliation.md | 14 +- .../Frontend_Mastery/Reflow & Repaint.md | 16 +- .../Reflow - Repaint 최소화 방법.md | 14 +- .../Frontend_Mastery/Reflow - Repaint.md | 14 +- .../Frontend_Mastery/Reflow and Repaint.md | 10 +- .../Reflow 및 Repaint 최적화.md | 6 +- .../Frontend_Mastery/Reflow 및 Repaint.md | 14 +- .../Reflow와 Repaint(리플로우와 리페인트).md | 10 +- .../Frontend_Mastery/Reflow와 Repaint.md | 10 +- .../Topics/Frontend_Mastery/Render Props.md | 14 +- .../Topics/Frontend_Mastery/Render Tree.md | 10 +- .../Frontend_Mastery/Responsive Web Design.md | 20 +- .../Reusable UI Component Libraries.md | 36 +- .../Topics/Frontend_Mastery/SCSS (Sass).md | 14 +- 10_Wiki/Topics/Frontend_Mastery/SCSS.md | 10 +- ...SEO 중심의 마케팅 및 블로그 사이트 구축.md | 8 +- .../SPA (Single Page Application).md | 10 +- .../SaaS 대시보드 및 이커머스 UI 개발.md | 16 +- ...SaaS 대시보드 및 이커머스 레이아웃 구축.md | 8 +- ...SaaS 플랫폼 및 인터랙티브 대시보드 개발.md | 16 +- .../Topics/Frontend_Mastery/Sanity Studio.md | 10 +- .../Scalable Design Systems.md | 30 +- .../Scalable Frontend Design Systems.md | 24 +- .../Scalable Frontend Systems.md | 30 +- .../Search Engine Optimization (SEO).md | 12 +- .../Frontend_Mastery/Server Components.md | 20 +- .../Server-Side Rendering (SSR).md | 12 +- .../Frontend_Mastery/Shopify Polaris.md | 8 +- .../Static Site Generation (SSG).md | 8 +- .../Style Dictionary Pipelines.md | 14 +- .../Frontend_Mastery/Style Dictionary.md | 16 +- .../Style Registry Pattern.md | 18 +- .../Topics/Frontend_Mastery/Style Registry.md | 16 +- .../Frontend_Mastery/Styled Components v6.md | 16 +- .../Frontend_Mastery/Styled Components.md | 18 +- 10_Wiki/Topics/Frontend_Mastery/Styletron.md | 10 +- .../Tailwind CSS v4 CSS-first Architecture.md | 16 +- .../Frontend_Mastery/Tailwind CSS v4.md | 16 +- .../Topics/Frontend_Mastery/Tailwind CSS.md | 20 +- .../Tailwind vs 일반 CSS 비교.md | 12 +- .../Topics/Frontend_Mastery/Time Slicing.md | 8 +- .../Time to Interactive (TTI).md | 14 +- .../Topics/Frontend_Mastery/Time-Slicing.md | 8 +- .../Total Blocking Time (TBT).md | 16 +- ...레이션 도구를 활용하는 대규모 조직의 React 시스템.md | 8 +- .../Topics/Frontend_Mastery/UXPin Merge.md | 10 +- .../Uber Base Web Design System.md | 14 +- .../Topics/Frontend_Mastery/Uber Base Web.md | 16 +- .../Frontend_Mastery/Utility-first CSS.md | 14 +- .../Topics/Frontend_Mastery/Virtual DOM.md | 12 +- .../Virtual DOM과 Reconciliation.md | 18 +- ...Content Accessibility Guidelines (WCAG).md | 10 +- .../Zero-Runtime CSS-in-JS.md | 18 +- ...ructure UI components scalable frontend.md | 30 +- 10_Wiki/Topics/Frontend_Mastery/flushSync.md | 12 +- 10_Wiki/Topics/Frontend_Mastery/shadcn-ui.md | 12 +- .../Frontend_Mastery/startTransition.md | 16 +- .../styled-components v6.3+.md | 18 +- .../Frontend_Mastery/styled-components.md | 14 +- .../Frontend_Mastery/useDeferredValue.md | 14 +- .../useTransition 및 useDeferredValue.md | 12 +- .../Topics/Frontend_Mastery/useTransition.md | 14 +- .../Frontend_Mastery/vanilla-extract.md | 16 +- ...React가 빠른 이유” 및 렌더링 최적화 개념.md | 24 +- .../Frontend_Mastery/“React가 빠른 이유”.md | 28 +- .../가변 타이포그래피 (Fluid Typography).md | 10 +- .../가상 DOM (Virtual DOM) 및 Fiber.md | 10 +- ...M (Virtual DOM) 및 재조정(Reconciliation).md | 12 +- .../가상 DOM과 재조정 (Reconciliation).md | 16 +- ... 재조정 (Virtual DOM and Reconciliation).md | 16 +- .../검색 엔진 최적화 (SEO).md | 8 +- ... 엔진 최적화(SEO) 대응 렌더링 전략 수립.md | 14 +- ...심 아키텍처(Feature-Driven Architecture).md | 12 +- .../Frontend_Mastery/다수 팀 협업 환경.md | 14 +- ...브러리를 보유한 엔터프라이즈 규모의 프론트엔드 환경.md | 22 +- ...모드 및 다중 브랜드 테마 동적 전환 시스템.md | 16 +- ... 진실 공급원(Single Source of Truth) 구축.md | 12 +- ...일 진실 공급원(Single Source of Truth).md | 14 +- ...멀티 디바이스(모바일-데스크톱) 웹 인터페이스 구축.md | 18 +- .../단일 페이지 애플리케이션 (SPA).md | 10 +- ...일 페이지 애플리케이션(SPA) UI 성능 관리.md | 16 +- ...일 페이지 애플리케이션(SPA) 렌더링 설계.md | 12 +- ... 페이지 애플리케이션(SPA) 아키텍처 설계.md | 34 +- ...규모 엔지니어링 프론트엔드 아키텍처 구축.md | 24 +- .../대규모 엔터프라이즈 테마 시스템.md | 18 +- .../대규모 엔터프라이즈 프론트엔드.md | 22 +- .../대규모 이커머스 플랫폼 렌더링 설계.md | 10 +- ... 기반 애플리케이션 및 전자상거래 플랫폼 구축.md | 6 +- ...드 아키텍처(Large-Scale Frontend Architecture).md | 24 +- ...엔드 아키텍처(Scalable Frontend Architecture).md | 24 +- .../대규모 프론트엔드 프로젝트 아키텍처.md | 16 +- ...론트엔드 프로젝트(Large Frontend Projects).md | 18 +- .../대규모 프론트엔드 프로젝트.md | 22 +- ...젝트의 확장성 있는 구조 및 스타일링 시스템 설계.md | 22 +- ...보수성이 요구되는 프런트엔드 모노레포 프로젝트.md | 12 +- ...심의 SaaS 어드민 패널 및 CRM 대시보드 구축.md | 10 +- .../동시성 렌더링 (Concurrent Rendering).md | 18 +- .../디자인 시스템 (Design System).md | 10 +- .../디자인 시스템 (Design Systems).md | 18 +- .../Frontend_Mastery/디자인 시스템 개념.md | 12 +- .../Frontend_Mastery/디자인 시스템 구축.md | 18 +- .../디자인 시스템 기반 컴포넌트 개발.md | 16 +- .../디자인 시스템(Design System).md | 18 +- .../디자인 시스템(Design Systems).md | 16 +- .../Topics/Frontend_Mastery/디자인 시스템.md | 18 +- ... 시스템의 타이포그래피 토큰 확장 및 최적화.md | 10 +- .../디자인 토큰 (Design Tokens).md | 14 +- .../디자인 토큰(Design Tokens).md | 12 +- ...-개발 워크플로우(Design-to-Code Workflow).md | 18 +- .../레이아웃 Flexbox - Grid 완전 이해.md | 12 +- .../레이아웃 스래싱(Layout Thrashing).md | 12 +- ...블로킹 방지를 위한 CSS 분할 및 로딩 최적화.md | 10 +- ...링 차단 리소스(Render-blocking resources).md | 18 +- .../렌더링 최적화 개념 설명 자료.md | 18 +- .../렌더링 파이프라인(Rendering Pipeline).md | 16 +- .../Frontend_Mastery/리페인트(Repaint).md | 6 +- ...리플로우 및 리페인트 (Reflow & Repaint).md | 8 +- .../리플로우 및 리페인트(Reflow & Repaint).md | 10 +- ...플로우 및 리페인트(Reflow and Repaint).md | 12 +- .../Frontend_Mastery/리플로우(Reflow).md | 10 +- .../마이크로 인터랙션(Micro-interactions).md | 6 +- ...비스 아키텍처 (Microservices Architecture).md | 8 +- .../메인 스레드 (Main Thread).md | 16 +- ...er 엔진 교체 및 React 18, 19의 동시성 렌더링 적용 사례.md | 18 +- ...리식 아키텍처 (Monolithic Architecture).md | 10 +- .../모던 웹 성능 최적화(Core Web Vitals).md | 12 +- .../모듈식 CSS(Modular CSS).md | 16 +- .../모듈식 컴포넌트 (Modular Components).md | 18 +- .../모바일 우선 설계(Mobile-First Design).md | 8 +- .../모바일 우선주의 (Mobile-First) 디자인.md | 8 +- ...양한 디바이스 환경을 위한 반응형 레이아웃 구축.md | 16 +- ...일 퍼스트 인덱싱(Mobile-First Indexing).md | 10 +- .../모바일 퍼스트(Mobile-First).md | 8 +- .../무거운 데이터 리스트 필터링 구현.md | 12 +- .../미디어 쿼리 (Media Queries).md | 12 +- .../미디어 쿼리(Media Queries).md | 14 +- ... 인터랙티브 UI(Responsive and Interactive UI).md | 18 +- .../반응형 디자인(Responsive Design).md | 16 +- .../Topics/Frontend_Mastery/반응형 디자인.md | 18 +- .../Frontend_Mastery/반응형 웹 UI 구현.md | 14 +- ...응형 웹 디자인 (Responsive Web Design).md | 20 +- ...저 렌더링 과정 (Critical Rendering Path).md | 16 +- ... 렌더링 과정 (HTML → CSSOM → Render Tree).md | 18 +- ...우저 렌더링 과정 최적화 및 UI 반응성 개선.md | 26 +- .../Frontend_Mastery/브라우저 렌더링 과정.md | 18 +- ... 렌더링 파이프라인(Critical Rendering Path).md | 18 +- .../브라우저 렌더링 프로세스 (CRP).md | 14 +- ...우저 메인 스레드 최적화 및 타임 슬라이싱.md | 14 +- ...이드 렌더링(SSR)과 하이드레이션(Hydration).md | 16 +- .../성능 및 SEO 최적화 프로젝트.md | 22 +- ...능 중심의 웹 애니메이션 및 인터랙션 구현.md | 14 +- .../성능 최적화(Performance Optimization).md | 16 +- .../성능 최적화(Reflow & Repaint).md | 12 +- ...최적화가 필수적인 대규모 다중 테마 플랫폼.md | 20 +- .../실무에서 CSS 관리하는 방법.md | 16 +- .../실무에서의 프론트엔드 성능 최적화.md | 18 +- ...이션 (transition - keyframes) 성능 최적화.md | 8 +- .../애니메이션 (transition - keyframes).md | 10 +- .../엔터프라이즈 프론트엔드 아키텍처.md | 24 +- .../엔터프라이즈급 플랫폼 개발.md | 18 +- .../웹 렌더링 전략 (CSR, SSR, SSG, ISR).md | 14 +- .../웹 성능 가이드(Web Performance).md | 18 +- ...능 최적화(Web Performance Optimization).md | 18 +- .../웹 접근성 및 prefers-reduced-motion.md | 6 +- .../웹 접근성 및 성능 최적화.md | 14 +- .../웹 접근성(Web Accessibility).md | 8 +- .../웹 프론트엔드 아키텍처 설계.md | 28 +- .../유동적 타이포그래피 (Fluid Typography).md | 10 +- .../유동적 타이포그래피(Fluid Typography).md | 10 +- ...수 가능하고 확장 가능한 CSS 아키텍처 설계.md | 22 +- ...가능한 CSS 아키텍처(CSS Modules & Tailwind).md | 12 +- ...지보수 가능한 대규모 프론트엔드 CSS 설계.md | 24 +- .../유지보수성(Maintainability).md | 16 +- .../유틸리티 퍼스트(Utility-first).md | 12 +- ...스 모바일 최적화 및 상품 탐색 UX-UI 설계.md | 6 +- ...자상거래 플랫폼 (E-commerce Platforms).md | 8 +- .../점진적 정적 재생성 (ISR).md | 8 +- ...요 렌더링 경로 (Critical Rendering Path).md | 16 +- ...과 작업 우선순위 (Lane Model & Priorities).md | 14 +- .../초기 로드 시간 (Initial Load Time).md | 16 +- .../컨테이너 쿼리 (Container Queries).md | 10 +- .../컨테이너 쿼리(Container Queries).md | 10 +- .../컴포넌트 기반 아키텍처 (CBA).md | 16 +- .../컴포넌트 기반 아키텍처 (React, Vue 등).md | 14 +- ...컴포넌트 기반 아키텍처 개념 수집 포인트.md | 14 +- ...기반 아키텍처(Component-Based Architecture).md | 20 +- .../컴포넌트 기반 아키텍처.md | 14 +- ...기반의 이커머스 및 뉴스 웹사이트 성능 튜닝.md | 12 +- ...랫폼 UI 개발(Cross-Platform UI Development).md | 18 +- .../크로스 플랫폼 디자인 시스템 연동.md | 14 +- ...Web, iOS, Android) UI 개발 및 배포 파이프라인.md | 12 +- ...컬 렌더링 패스 (Critical Rendering Path).md | 18 +- .../클라이언트 사이드 렌더링 (CSR).md | 8 +- ...각 반응해야 하는 검색창 (Search-as-you-type).md | 12 +- .../프론트엔드 기초 구조 이해 핵심 목적.md | 18 +- .../프론트엔드 기초 구조 이해.md | 28 +- ...엔드 렌더링 최적화(Rendering Optimization).md | 30 +- ...트엔드 성능 최적화 및 SEO 개선 프로젝트.md | 22 +- .../프론트엔드 성능 최적화 전략.md | 24 +- ...능 최적화(Frontend Performance Optimization).md | 24 +- .../프론트엔드 성능 최적화.md | 24 +- .../Frontend_Mastery/프론트엔드 아키텍처.md | 22 +- ...트엔드 프레임워크 (React, Angular, Vue).md | 20 +- ... 슬라이스 디자인 (Feature-Sliced Design).md | 8 +- .../하이드레이션 (Hydration).md | 16 +- .../확장 가능한 스타일 시스템.md | 24 +- .../확장 가능한 프론트엔드 아키텍처 구축.md | 24 +- ...엔드 아키텍처(Scalable Frontend Architecture).md | 22 +- 10_Wiki/Topics/Functional Programming.md | 31 - .../Functional-Programming-in-TypeScript.md | 30 - 10_Wiki/Topics/Functional-Programming.md | 29 - 10_Wiki/Topics/Fuzzy-Logic.md | 28 - 10_Wiki/Topics/G-Stack Principles.md | 28 - 10_Wiki/Topics/G-Stack-Integration-Guide.md | 31 - 10_Wiki/Topics/GAN.md | 28 - 10_Wiki/Topics/GNN.md | 29 - .../Topics/GPT-Architecture-Foundations.md | 28 - 10_Wiki/Topics/GPU-Architecture.md | 29 - 10_Wiki/Topics/GPU-Programming-with-CUDA.md | 29 - 10_Wiki/Topics/GPU.md | 33 - 10_Wiki/Topics/GRPO.md | 30 - 10_Wiki/Topics/GRU.md | 28 - 10_Wiki/Topics/Gacha Mechanics Analysis.md | 28 - 10_Wiki/Topics/Gait-Analysis-Laboratory.md | 28 - 10_Wiki/Topics/Game Analytics (게임 분석).md | 31 - .../2014 Combat Controls Update.md | 14 +- .../Game Design/4X 시스템 (4X System).md | 14 +- .../Game Design/4X 전략 게임 수익화 모델.md | 10 +- 10_Wiki/Topics/Game Design/4X 전략.md | 14 +- 10_Wiki/Topics/Game Design/AI Exploitation.md | 12 +- .../AI 추적 논리(AI Pursuit Logic).md | 12 +- .../Game Design/Agency and Player Autonomy.md | 4 +- 10_Wiki/Topics/Game Design/Alliance (동맹).md | 10 +- .../Alliances-and-Sector-Hegemony.md | 10 +- .../Anti-Air-and-Anti-Ground-Combat.md | 14 +- .../Topics/Game Design/Arc-2-Technology.md | 6 +- .../Area-of-Effect (AoE) Damage.md | 14 +- .../Topics/Game Design/Assault-Platoons.md | 8 +- 10_Wiki/Topics/Game Design/Baiting Tactics.md | 10 +- .../Baiting-and-Combat-Controls.md | 18 +- 10_Wiki/Topics/Game Design/Baiting.md | 12 +- 10_Wiki/Topics/Game Design/Base Layouts.md | 12 +- .../Base-Layouts-and-Kill-Zones.md | 12 +- 10_Wiki/Topics/Game Design/Base-Layouts.md | 10 +- .../Combat Controls Update (Feb 2014).md | 16 +- 10_Wiki/Topics/Game Design/Combat Controls.md | 14 +- 10_Wiki/Topics/Game Design/Combined-Arms.md | 6 +- 10_Wiki/Topics/Game Design/Command Center.md | 12 +- .../Command and Control (C2) Interface.md | 18 +- .../Game Design/Command and Control (C2).md | 18 +- 10_Wiki/Topics/Game Design/Control-Points.md | 6 +- .../Damage-Resistance-Platforms.md | 14 +- 10_Wiki/Topics/Game Design/Damage-Types.md | 12 +- .../Topics/Game Design/Defense-Buildings.md | 10 +- .../Topics/Game Design/Defensive Stances.md | 16 +- .../Game Design/Defensive-Architecture.md | 10 +- .../Game Design/Descendants-Sector-Control.md | 12 +- 10_Wiki/Topics/Game Design/Eugen Systems.md | 12 +- 10_Wiki/Topics/Game Design/Events.md | 16 +- ...n-of-the-War-Commander-Combat-Ecosystem.md | 16 +- 10_Wiki/Topics/Game Design/Fate War.md | 12 +- .../Final Fantasy XV- A New Empire.md | 12 +- .../Game Design/Free-Repair-Strategy.md | 10 +- .../Topics/Game Design/Free-Repair-Tactics.md | 6 +- .../Game Design/GAME_SYSTEM_DESIGN_PROMPT.md | 2 +- .../Game of War BM과 구조 조사.md | 20 +- .../Game Design/Game of War BM과 구조 조사.md | 22 +- .../Game of War- Fire Age BM 및 구조 설계.md | 14 +- .../Game Design/Game of War- Fire Age.md | 18 +- .../Genre & Mechanics/4X Strategy.md | 14 +- .../Game Design/Genre & Mechanics/Index.md | 2 +- 10_Wiki/Topics/Game Design/Index.md | 330 +- .../Topics/Game Design/Industry/AppLovin.md | 14 +- 10_Wiki/Topics/Game Design/Industry/Index.md | 4 +- .../Game Design/Industry/Machine Zone.md | 14 +- 10_Wiki/Topics/Game Design/Iridium.md | 10 +- 10_Wiki/Topics/Game Design/Jailing.md | 4 +- .../Game Design/Kingdom vs. Kingdom (KvK).md | 8 +- .../Kingdom vs. Kingdom Events (KvK).md | 10 +- .../Game Design/Live Operations (LiveOps).md | 12 +- 10_Wiki/Topics/Game Design/LiveOps.md | 12 +- ...폴리오 확장 및 라이브 서비스 모델 고도화.md | 22 +- .../Game Design/Metronomos-Heavy-Turret.md | 10 +- .../Topics/Game Design/Micro-management.md | 14 +- 10_Wiki/Topics/Game Design/Mixed-Platoons.md | 6 +- 10_Wiki/Topics/Game Design/Mobile Strike.md | 10 +- .../Topics/Game Design/Monetization/Index.md | 6 +- .../Game Design/Monetization/Power Creep.md | 12 +- .../Monetization/Staircase Monetization.md | 8 +- .../Game Design/Monetization/VIP System.md | 10 +- .../Topics/Game Design/Nightwatch-Bunker.md | 8 +- 10_Wiki/Topics/Game Design/Pay-to-win.md | 18 - 10_Wiki/Topics/Game Design/Permanent Loss.md | 12 +- ...Resistance-and-Defensive-Specialization.md | 12 +- .../Topics/Game Design/Platform-Resistance.md | 14 +- .../Game Design/Platform-Specialization.md | 12 +- .../Power Creep (Content Treadmills).md | 12 +- .../Topics/Game Design/Puzzles & Survival.md | 10 +- .../Topics/Game Design/Rise of Kingdoms.md | 12 +- .../Rock-Paper-Scissors-Dynamic.md | 4 +- .../Topics/Game Design/Rogue-Player-Bases.md | 6 +- .../Game Design/Sarkis-Cloning-Technology.md | 6 +- .../Topics/Game Design/Sector-Breach-Store.md | 4 +- .../Topics/Game Design/Sector-Breach-XP.md | 6 +- 10_Wiki/Topics/Game Design/Sector.md | 8 +- .../Social & Psychology/Alliances.md | 18 +- .../Game Design/Social & Psychology/Index.md | 4 +- .../Social & Psychology/Social Engineering.md | 10 +- 10_Wiki/Topics/Game Design/Splash Damage.md | 8 +- .../Staircase Monetization Model.md | 10 +- 10_Wiki/Topics/Game Design/Status-Effects.md | 8 +- .../Topics/Game Design/Street Duel Fighter.md | 8 +- ...tical-Evolution-of-the-Combat-Ecosystem.md | 14 +- ...Structural-Dynamics-of-Combat-Ecosystem.md | 16 +- .../Topics/Game Design/Support Insulated.md | 12 +- .../Topics/Game Design/Support-Platforms.md | 12 +- ...n-of-the-War-Commander-Combat-Ecosystem.md | 20 +- 10_Wiki/Topics/Game Design/Thorium.md | 6 +- 10_Wiki/Topics/Game Design/Unit Stances.md | 12 +- .../Game Design/VIP 시스템 (VIP System).md | 12 +- 10_Wiki/Topics/Game Design/VIP 시스템.md | 12 +- 10_Wiki/Topics/Game Design/VIP.md | 10 +- ...진화(Tactical Evolution of the Combat Ecosystem).md | 18 +- .../War-Commander-Combat-Ecosystem.md | 16 +- .../War-Commander-Event-Operations.md | 8 +- .../War-Commander-Strategic-Hub.md | 24 - ...-Commander-전투-생태계-및-지정학적-구조.md | 12 +- .../Game Design/War-Commander-전투-시스템.md | 22 +- 10_Wiki/Topics/Game Design/Wonder.md | 4 +- .../Topics/Game Design/World War Rising.md | 8 +- .../가상 화폐 (Virtual Currency).md | 8 +- .../거점(Control Points) 점령전.md | 10 +- .../계단식 수익화 (Staircase Monetization).md | 10 +- ...식 수익화 모델 (Staircase Monetization).md | 6 +- .../Game Design/고과금 유저 (Whales).md | 14 +- .../Game Design/고래 유저 (Whale Players).md | 10 +- .../Game Design/과금 모델 (Monetization).md | 20 +- ... 동맹 전쟁(Sector Control and Alliance Wars).md | 12 +- .../기지 레이아웃 메타(Base Layout Meta).md | 8 +- .../기지 방어 레이아웃(Base Layouts).md | 10 +- ...방어 설계 및 공략(Base Defense and Siege).md | 14 +- .../기지 방어 설계(Defensive Architecture).md | 14 +- .../Game Design/기지 방어(Base Defense).md | 18 +- .../Game Design/다크 패턴 (Dark Patterns).md | 10 +- 10_Wiki/Topics/Game Design/동맹(Alliances).md | 10 +- .../동적 가격 책정 (Dynamic Pricing).md | 12 +- .../라이브 서비스 (Live Service).md | 12 +- .../맞춤형 팩 (Personalized Packs).md | 12 +- .../매몰 비용의 오류 (Sunk Cost Fallacy).md | 10 +- ...임의 진화 및 Game of War BM 구조 분석 프로젝트.md | 12 +- .../Topics/Game Design/미끼 전술(Baiting).md | 8 +- ...이아웃(Defensive Architecture and Base Layouts).md | 10 +- .../방어 구조(Defensive Architecture).md | 18 +- ...하학 및 구조 설계(Defensive Architecture).md | 8 +- .../방어 아키텍처(Defensive Architecture).md | 16 +- .../방어 태세(Defensive Stance).md | 12 +- .../방어 플랫폼(Defense Platforms).md | 14 +- 10_Wiki/Topics/Game Design/병원 (Hospital).md | 12 +- ... 방어 전략(Combined Arms Defensive Grid).md | 10 +- ...적 권력 피라미드 (Feudal Power Pyramid).md | 8 +- .../부대 편성(Platoon Formations).md | 8 +- .../블리츠 기지 설계(Blitz Base Design).md | 10 +- ...미지 유형(Unit Counters & Damage Profiles).md | 10 +- .../Game Design/세계 지도(World Map).md | 12 +- 10_Wiki/Topics/Game Design/섹터.md | 10 +- 10_Wiki/Topics/Game Design/소대.md | 10 +- ... 수익화 모델 (Staircase Monetization Model).md | 10 +- .../시간 제한 메커니즘 (Time-gating).md | 8 +- ...간 제한 활성화 (Time-limited Activation).md | 6 +- .../Game Design/실시간 번역 엔진 (RTE).md | 10 +- .../실시간 번역 엔진 (Real-Time Engine).md | 10 +- .../Topics/Game Design/실시간 엔진 (RTE).md | 10 +- .../실시간 엔진 (Real-Time Engine).md | 10 +- .../약탈적 수익화 (Predatory Monetization).md | 12 +- .../Game Design/얼라이언스 (Alliance).md | 8 +- .../Game Design/영구 손실 (Permanent loss).md | 10 +- .../영구적 손실 (Permanent Loss).md | 12 +- .../Game Design/왕국 대 왕국 (KvK) 이벤트.md | 10 +- .../Topics/Game Design/월드 맵(World Map).md | 8 +- .../Game Design/유닛 미끼 전술(Baiting).md | 10 +- .../Game Design/유닛 상성(Unit Counters).md | 10 +- .../Game Design/유닛 상성(Unit Matchups).md | 10 +- .../Game Design/유인 전술(Baiting Tactics).md | 10 +- .../Topics/Game Design/유인 전술(Baiting).md | 8 +- .../이중 VIP 시스템 (Dual-layer VIP).md | 12 +- ... 계층 과금 모델 (Two-layer Monetization).md | 10 +- .../적자 경제 (Deficit economy).md | 6 +- .../Game Design/전력 시스템(Power Systems).md | 6 +- .../전투 전술(Battle Strategies).md | 12 +- .../Game Design/전투 제어(Combat Controls).md | 14 +- .../전투 컨트롤(Combat Controls).md | 14 +- .../Game Design/전투 통제(Combat Controls).md | 14 +- .../Game Design/제로잉 (Getting Zero-ed).md | 8 +- .../Topics/Game Design/제로잉 (Zeroing).md | 12 +- .../Game Design/파워 크립 (Power Creep).md | 6 +- .../포탑 시스템(Turret Systems).md | 14 +- .../Game Design/피해 유형(Damage Types).md | 14 +- .../혼합 소대 전술(Mixed Platoon Tactics).md | 10 +- .../Game Design/혼합 소대(Mixed Platoons).md | 14 +- 10_Wiki/Topics/Game-Balance-Design.md | 28 - 10_Wiki/Topics/Game-Balance-Modeling.md | 29 - 10_Wiki/Topics/Game-Design-Ontology.md | 32 - 10_Wiki/Topics/Game-Design-Theory.md | 31 - 10_Wiki/Topics/Game-Economy-Design.md | 28 - 10_Wiki/Topics/Game-Feel-and-Juiciness.md | 27 - 10_Wiki/Topics/Game-Loop-Architecture.md | 28 - 10_Wiki/Topics/Game-Mechanics.md | 29 - 10_Wiki/Topics/Game-Ontology-for-PCG.md | 31 - 10_Wiki/Topics/Game-Theory-in-AI.md | 29 - 10_Wiki/Topics/Game-Theory.md | 28 - 10_Wiki/Topics/Gamification-Strategies.md | 28 - 10_Wiki/Topics/Gamification-Theory.md | 31 - 10_Wiki/Topics/Gates.md | 32 - 10_Wiki/Topics/Gaussian-Processes.md | 28 - 10_Wiki/Topics/General Knowledge/Index.md | 2 +- .../Topics/General Knowledge/Iriszoom 엔진.md | 10 +- .../Iriszoom 엔진의 물리적 가시화.md | 10 +- ...의 몬테카를로 시뮬레이션 및 데이터 예측.md | 12 +- .../Topics/General Knowledge/Magic Sort!.md | 10 +- ...Mobile Game Development Financial Model.md | 8 +- .../General Knowledge/Nexus Gaming Labs.md | 6 +- .../Topics/General Knowledge/Pocket Land.md | 6 +- .../General Knowledge/Reb's FRAGO 모드.md | 8 +- .../General Knowledge/RebsFRAGO 모드.md | 8 +- .../Resource Deposits(자원 매장지).md | 10 +- .../SARD 안티치트 솔루션(SARD Anti-Cheat).md | 8 +- ...안 이슈와 Cross-Origin Isolation 설정법.md | 10 +- 10_Wiki/Topics/General Knowledge/WARPLAN.md | 12 +- .../General Knowledge/WoW 토큰 및 PLEX.md | 6 +- ...이터 기반 밸런싱 (Data-Driven Balancing).md | 10 +- ...이터 기반 밸런싱(Data-Driven Balancing).md | 8 +- .../General Knowledge/데이터 기반 밸런싱.md | 10 +- .../데이터 기반 설계 (Data-Driven Design).md | 12 +- .../데이터 기반 설계(Data-Driven Design).md | 10 +- .../General Knowledge/데이터 기반 설계.md | 14 +- .../덱 빌딩 (Deck building).md | 8 +- .../덱 빌딩 시스템 (Deck Building System).md | 10 +- .../디아블로 2(Diablo II) 조던링 사태.md | 6 +- .../디지털 트윈(Digital Twin).md | 10 +- .../General Knowledge/라이브옵스(LiveOps).md | 10 +- .../리그 오브 레전드(League of Legends).md | 6 +- .../마키네이션(Machinations).md | 14 +- .../마키네이션(Machinations.io).md | 14 +- .../Topics/General Knowledge/모딩 생태계.md | 10 +- ... 모델 (Mobile Game Development Financial Model).md | 8 +- ...카를로 시뮬레이션(Monte Carlo Simulation).md | 8 +- .../부분 유료화(Free-to-Play) 게임.md | 10 +- ...임 산업의 플랫폼 융합(Platform Convergence).md | 8 +- .../사용자 제작 콘텐츠(UGC).md | 10 +- .../숨겨진 스탯(Hidden Stats).md | 12 +- ...측 모델링(Simulation and Predictive Modeling).md | 12 +- ...시간 전략 및 부분유료화(F2P) 밸런싱 맥락.md | 8 +- ...비온 온라인(Albion Online) 암시장 시스템.md | 6 +- .../알비온 온라인(Albion Online).md | 6 +- .../General Knowledge/원신(Genshin Impact).md | 6 +- ...노믹스 모델링(Web3 and Tokenomics Modeling).md | 12 +- .../자원 관리(Resource Management).md | 8 +- .../General Knowledge/전자상거래 플랫폼.md | 6 +- .../진행 제한(Progression Limitation).md | 6 +- .../총이익률 (Gross Margin).md | 8 +- .../크리에이터 이코노미(Creator Economy).md | 10 +- .../클래시 로얄 모바일 게임 프로덕션.md | 8 +- .../클래시 로얄(Clash Royale).md | 6 +- ...시 로얄(Clash Royale)의 대칭성과 밸런싱.md | 6 +- ... 로얄(Clash Royale)의 비용-엘릭서 밸런싱.md | 6 +- .../하이브리드 캐주얼 (Hybrid Casual).md | 8 +- .../하이브리드 캐주얼 게임.md | 8 +- ...발 주자 불이익(Latecomer Disadvantage).md | 6 +- ...dversarial Networks (GANs) in Fine Arts.md | 26 - .../Topics/Generative-Adversarial-Networks.md | 28 - 10_Wiki/Topics/Generics-and-Polymorphism.md | 32 - 10_Wiki/Topics/Genetic-Algorithms.md | 30 - .../Topics/Geographic-Information-Systems.md | 32 - 10_Wiki/Topics/Geometric-Deep-Learning.md | 31 - 10_Wiki/Topics/Geriatric-Medicine.md | 30 - 10_Wiki/Topics/Gestalt Psychology.md | 32 - 10_Wiki/Topics/Gestalt-Principles in UX.md | 30 - .../Topics/Gestalt-Principles-of-Design.md | 26 - 10_Wiki/Topics/Gimbals-and-Orientation.md | 29 - .../Git-Branching-Strategies-and-Workflows.md | 32 - 10_Wiki/Topics/Git-Version-Control.md | 29 - 10_Wiki/Topics/Git_Operation_Protocol.md | 50 - 10_Wiki/Topics/GloVe (Word Embeddings).md | 28 - 10_Wiki/Topics/Global-Standard.md | 31 - 10_Wiki/Topics/Global-vs-Local-Optima.md | 31 - 10_Wiki/Topics/Goal-Misgeneralization.md | 30 - .../Topics/Goal-Oriented-Action-Planning.md | 28 - 10_Wiki/Topics/God-Object-Antipattern.md | 27 - .../Topics/Godel's Incompleteness Theorems.md | 29 - .../Google-Page-Experience-2025-Update.md | 29 - .../Agentic Governance.md | 8 +- .../Autonomous Logging.md | 8 +- .../Distributed Systems & Reliability.md | 8 +- .../Topics/Governance & Reliability/Index.md | 4 +- .../Self-verification.md | 8 +- .../Session Lifecycle.md | 8 +- 10_Wiki/Topics/Gradient-Boosting-Machines.md | 30 - 10_Wiki/Topics/Gradient-Descent.md | 31 - 10_Wiki/Topics/Graph Theory.md | 31 - 10_Wiki/Topics/Graph-Coloring-Problem.md | 32 - 10_Wiki/Topics/Graph-Database.md | 28 - 10_Wiki/Topics/Graph-Theory.md | 30 - 10_Wiki/Topics/GraphQL-Code-Generator.md | 31 - .../GraphRAG (그래프 기반 검색 증강 생성).md | 27 - ...E (Almost Native Graphics Layer Engine).md | 12 +- .../Topics/Graphics & Performance/ANGLE.md | 12 +- .../Graphics & Performance/Alpha Blending.md | 10 +- .../Graphics & Performance/BIM 모델 렌더링.md | 16 +- .../BIM 모델 시뮬레이션.md | 14 +- 10_Wiki/Topics/Graphics & Performance/BVH.md | 16 +- .../Graphics & Performance/Babylonjs.md | 12 +- ...chedMesh 및 InstancedMesh 성능 벤치마크.md | 18 +- .../Topics/Graphics & Performance/Batching.md | 16 +- .../Buffer Allocation.md | 16 +- .../Graphics & Performance/BufferAttribute.md | 10 +- .../Graphics & Performance/BufferGeometry.md | 10 +- .../Graphics & Performance/CPU Bottleneck.md | 20 +- .../Graphics & Performance/CPU Overhead.md | 14 +- .../Topics/Graphics & Performance/Cesium.md | 6 +- .../Chrome (Blink_Dawn).md | 18 +- .../Chrome WebGPU 구현.md | 16 +- .../Chrome _ Blink WebGPU Implementation.md | 20 +- .../Topics/Graphics & Performance/Chrome.md | 16 +- .../Chromium WebGPU Implementation.md | 16 +- .../Computational Geometry.md | 10 +- .../Graphics & Performance/Compute Shader.md | 14 +- .../Graphics & Performance/Compute Shaders.md | 14 +- .../Data Array Textures.md | 14 +- .../Topics/Graphics & Performance/Direct3D.md | 14 +- .../Graphics & Performance/Draw Call.md | 18 +- .../Graphics & Performance/Fill Rate.md | 10 +- .../Fragment Shading.md | 16 +- .../Graphics & Performance/Fragment-bound.md | 12 +- .../Graphics & Performance/Frustum Culling.md | 16 +- .../Graphics & Performance/GPU Resources.md | 16 +- .../GPU for the Web Community Group.md | 16 +- .../GPU-driven Rendering.md | 14 +- .../GPURenderBundles.md | 8 +- ...라인의 미세 지연(Micro-latency) 측정 사례.md | 26 +- .../Garbage Collection.md | 12 +- .../Geometry Merging.md | 16 +- ...ead-Mounted Display) 기반 엑서게임 환경.md | 12 +- .../High Resolution Time.md | 12 +- .../IFCjs (Fragment).md | 14 +- .../Topics/Graphics & Performance/Index.md | 268 +- .../Graphics & Performance/Indirect Draw.md | 12 +- .../InstancedMesh (드로우 콜 최적화).md | 12 +- .../Graphics & Performance/InstancedMesh2.md | 18 +- .../Graphics & Performance/Instancing.md | 14 +- .../Graphics & Performance/JavaScript.md | 16 +- ...Memory Leak Prevention 메모리 누수 방지.md | 12 +- .../Graphics & Performance/Memory Leaks.md | 14 +- .../Memory Management.md | 18 +- .../MeshStandardMaterial 조명 연산.md | 10 +- .../Topics/Graphics & Performance/Metal.md | 12 +- .../Multi-threaded Architecture.md | 18 +- .../Graphics & Performance/Needle Engine.md | 10 +- .../Graphics & Performance/Object Pooling.md | 12 +- .../OffscreenCanvas Safari 제약 사항.md | 14 +- .../Graphics & Performance/OffscreenCanvas.md | 14 +- .../Graphics & Performance/OpenGL ES 20.md | 10 +- .../Graphics & Performance/OpenGL ES.md | 16 +- .../Topics/Graphics & Performance/Opera.md | 14 +- 10_Wiki/Topics/Graphics & Performance/PBR.md | 6 +- .../Graphics & Performance/Radix Sort.md | 10 +- .../Graphics & Performance/Raycaster.md | 16 +- .../Graphics & Performance/Raycasting.md | 14 +- ...ompiler의 Threejs 런타임 성능 개선 원리.md | 16 +- .../React Three Fiber (R3F).md | 10 +- ... Fiber 자산 최적화 (Asset Optimization).md | 12 +- ...e Fiber에서 Rapier 물리 엔진 최적화하기.md | 12 +- .../Revit glTF Export.md | 8 +- .../Revit 모델 렌더링.md | 8 +- .../Rowhammer attack.md | 14 +- .../Graphics & Performance/Rowhammer.md | 12 +- .../Graphics & Performance/SkinnedMesh.md | 10 +- .../Topics/Graphics & Performance/Sorting.md | 20 +- .../Spatial Partitioning.md | 14 +- .../Spectre and Meltdown.md | 20 +- .../Spring Framework.md | 8 +- .../Graphics & Performance/TLB design.md | 10 +- .../TSL (Three Shader Language).md | 10 +- .../Texture Compression.md | 6 +- .../Three Shader Language (TSL).md | 12 +- .../Three.js 렌더링 최적화.md | 16 +- .../Threejs WebGL Rendering Optimization.md | 30 +- .../Threejs WebGPU 파티클 예제.md | 16 +- ...Threejs 대규모 렌더링 최적화 파이프라인.md | 18 +- .../Threejs 렌더링 성능 최적화.md | 24 +- .../Threejs 렌더링 최적화.md | 20 +- .../Threejs 모바일 렌더링 최적화.md | 20 +- .../Topics/Graphics & Performance/Threejs.md | 26 +- .../Timestamp Quantization.md | 18 +- .../Timestamp Queries Quantization.md | 16 +- .../Timestamp Queries.md | 12 +- .../Graphics & Performance/TypedArray.md | 10 +- .../Graphics & Performance/UV Offset.md | 14 +- .../Topics/Graphics & Performance/Unity.md | 16 +- .../Topics/Graphics & Performance/Utsubo.md | 14 +- .../VR 엑서게임 (VR Exergaming).md | 14 +- .../Varying Variables.md | 10 +- .../Graphics & Performance/Vertex Shader.md | 8 +- .../Topics/Graphics & Performance/Vulkan.md | 8 +- .../WEBGL_multi_draw.md | 18 +- .../Graphics & Performance/WebAssembly.md | 16 +- .../Topics/Graphics & Performance/WebGL 20.md | 16 +- .../Graphics & Performance/WebGL API.md | 18 +- .../WebGL Optimization.md | 20 +- .../WebGL 모바일 GPU 성능 관리.md | 18 +- .../Topics/Graphics & Performance/WebGL.md | 16 +- .../Topics/Graphics & Performance/WebGL2.md | 16 +- .../WebGLRenderingContext.md | 8 +- .../WebGPU Compute Shader.md | 18 +- .../WebGPU Compute Shaders.md | 20 +- .../WebGPU Performance Profiling.md | 20 +- .../WebGPU _ WebGL Timing API Security.md | 18 +- .../WebGPU 대규모 건설 뷰어.md | 16 +- .../Topics/Graphics & Performance/WebGPU.md | 18 +- .../Wonderland Engine.md | 16 +- .../Graphics & Performance/instancedArray.md | 10 +- .../Graphics & Performance/three-mesh-bvh.md | 14 +- .../Graphics & Performance/가상현실(VR).md | 12 +- .../고성능 멀티스레드 React 앱 아키텍처.md | 14 +- .../대규모 3D 건축 모델(BIM) 시각화.md | 18 +- .../대규모 건설 뷰어(Construction Viewers).md | 12 +- .../대규모 건축물 및 지형 뷰어(BIM).md | 18 +- .../대규모 파티클 시스템 최적화.md | 20 +- .../마이크로 프론트엔드.md | 6 +- .../모바일 기반 WebGL 애플리케이션 개발.md | 12 +- .../셰이더 정밀도 (Mediump_Highp).md | 4 +- .../스토리지 텍스처(Storage Textures).md | 12 +- .../실시간 물리 및 유체 시뮬레이션.md | 14 +- .../웹 브라우저 그래픽 API 호환성.md | 18 +- .../입자 시스템(Particle Systems).md | 18 +- .../컴퓨트 셰이더(Compute Shaders).md | 18 +- .../프래그먼트 바운드(Fragment-bound).md | 18 +- .../프래그먼트 셰이딩(Fragment Shading).md | 18 +- .../헤드 마운트 디스플레이(HMD).md | 14 +- .../헤드마운트 디스플레이 (HMD).md | 12 +- .../Topics/Graphics/3D_Gaussian_Splatting.md | 4 +- 10_Wiki/Topics/Graphics/3D_Web_HMI.md | 6 +- 10_Wiki/Topics/Graphics/Digital_Twin.md | 8 +- 10_Wiki/Topics/Graphics/Index.md | 10 +- .../Topics/Graphics/Predictive_Maintenance.md | 8 +- 10_Wiki/Topics/Graphics/VPS_NeRF.md | 6 +- 10_Wiki/Topics/Greedy-Algorithms.md | 29 - 10_Wiki/Topics/Grit.md | 32 - 10_Wiki/Topics/Grounded Theory Method.md | 31 - 10_Wiki/Topics/Growth-Mindset-Intervention.md | 31 - 10_Wiki/Topics/Growth-Mindset.md | 30 - .../Guilty-Gear-Xrd-Rendering-Pipeline.md | 31 - 10_Wiki/Topics/HANDOVER.md | 32 - 10_Wiki/Topics/HBO-Prestige-Television.md | 31 - .../HCI (Human-Computer Interaction).md | 31 - 10_Wiki/Topics/HHH.md | 31 - 10_Wiki/Topics/HMM.md | 28 - 10_Wiki/Topics/Habit-Formation.md | 28 - 10_Wiki/Topics/Hallucination (환각).md | 32 - 10_Wiki/Topics/Hallucination-in-LLM.md | 31 - 10_Wiki/Topics/Hallucination-in-LLMs.md | 32 - .../Topics/Hardware-Acceleration-for-AI.md | 32 - 10_Wiki/Topics/Hardware-Verification.md | 31 - 10_Wiki/Topics/Hardware.md | 31 - 10_Wiki/Topics/Hash-Functions-and-Maps.md | 28 - .../Biomedical-Engineering.md | 10 +- 10_Wiki/Topics/Health & Science/Index.md | 2 +- 10_Wiki/Topics/Health-Informatics.md | 31 - 10_Wiki/Topics/Health/ACL_Prevention.md | 8 +- 10_Wiki/Topics/Health/Index.md | 2 +- 10_Wiki/Topics/Hebbian-Learning.md | 28 - 10_Wiki/Topics/Hebbian-Theory.md | 30 - 10_Wiki/Topics/Heuristic-Search.md | 28 - 10_Wiki/Topics/Heuristics.md | 32 - .../Topics/Hierarchical-Task-Network (HTN).md | 28 - 10_Wiki/Topics/High-Availability-Systems.md | 29 - 10_Wiki/Topics/High-Cohesion-Low-Coupling.md | 33 - .../Topics/High-Frequency-Trading-Models.md | 32 - .../High-Performance Computing (HPC).md | 31 - 10_Wiki/Topics/High-Performance-Coaching.md | 31 - .../Topics/High-Performance-Organizations.md | 31 - .../Topics/High-Performance-Sports-Science.md | 31 - 10_Wiki/Topics/Homeostasis (항상성).md | 32 - 10_Wiki/Topics/Homeostasis.md | 32 - 10_Wiki/Topics/Homomorphic-Encryption.md | 28 - 10_Wiki/Topics/Human Centered AI (HCAI).md | 32 - 10_Wiki/Topics/Human-AI-Collaboration.md | 28 - .../Topics/Human-Computer-Interaction-HCI.md | 29 - 10_Wiki/Topics/Human-Computer-Interaction.md | 31 - 10_Wiki/Topics/Human-in-the-loop (HITL).md | 28 - 10_Wiki/Topics/Human-in-the-loop-AI.md | 28 - 10_Wiki/Topics/Hybrid-Cloud-Architectures.md | 29 - .../Hydration-Mismatch-and-SSR-Debugging.md | 32 - .../Hyperinflation-in-Closed-Loop-Systems.md | 31 - 10_Wiki/Topics/Hyperparameter-Optimization.md | 29 - 10_Wiki/Topics/Hyperparameters.md | 32 - 10_Wiki/Topics/Hypostatic-Abstraction.md | 30 - 10_Wiki/Topics/Hypothesis-Testing.md | 29 - 10_Wiki/Topics/ICRE-Framework.md | 29 - ...DE (Integrated Development Environment).md | 31 - 10_Wiki/Topics/IEEE-P36521.md | 31 - 10_Wiki/Topics/ISO-Standard.md | 31 - 10_Wiki/Topics/Ikigai (이키가이).md | 32 - .../Topics/Image Inpainting (Vary Region).md | 14 +- 10_Wiki/Topics/Image Parameters.md | 14 +- .../Topics/Image-Classification-Mastery.md | 28 - .../Image-Optimization-for-Web-Performance.md | 30 - .../Topics/Image-Segmentation-Techniques.md | 29 - 10_Wiki/Topics/Image-Segmentation.md | 28 - 10_Wiki/Topics/Imbalanced-Data-Handling.md | 32 - 10_Wiki/Topics/Imitation-Learning.md | 27 - 10_Wiki/Topics/Immersive-Sim-Design.md | 31 - 10_Wiki/Topics/Immersive-Sim-Genre.md | 31 - .../Immersive-Sims-Deus-Ex-Dishonored.md | 33 - .../Topics/Immersive-Sims-Deus-Ex-Thief.md | 33 - 10_Wiki/Topics/Immutability-Patterns.md | 32 - 10_Wiki/Topics/Impedance-Matching.md | 28 - 10_Wiki/Topics/In-Context-Learning.md | 28 - 10_Wiki/Topics/Inclusive-Design-and-UX.md | 29 - 10_Wiki/Topics/Incremental-Computation.md | 33 - 10_Wiki/Topics/Incremental-Learning.md | 28 - .../Incremental-Static-Regeneration-ISR.md | 28 - 10_Wiki/Topics/Incrementalism.md | 31 - .../Independent Component Analysis (ICA).md | 31 - .../Topics/Independent-Component-Analysis.md | 31 - .../Topics/Index-Fragmentation-Analysis.md | 33 - 10_Wiki/Topics/Index.md | 72 - 10_Wiki/Topics/Index_692.md | 2942 ++++++++--------- 10_Wiki/Topics/Indexing-Strategies.md | 29 - 10_Wiki/Topics/Indian-Innovation-Models.md | 33 - 10_Wiki/Topics/Inductive-Bias.md | 29 - 10_Wiki/Topics/Inductive-Reasoning.md | 30 - 10_Wiki/Topics/Inexact-Science.md | 31 - 10_Wiki/Topics/Inference-Optimization.md | 30 - 10_Wiki/Topics/Inferential-Statistics.md | 30 - 10_Wiki/Topics/Information-Entropy.md | 30 - 10_Wiki/Topics/Information-Retrieval-IR.md | 29 - 10_Wiki/Topics/Information-Society.md | 31 - 10_Wiki/Topics/Information-Theory.md | 28 - 10_Wiki/Topics/Infraspace.md | 32 - .../Artifacts & Infrastructure.md | 8 +- .../Edge Computing.md | 8 +- .../Execution Environment (Sandbox).md | 8 +- .../Infrastructure & Automation/Index.md | 8 +- .../Real-Time Engine (RTE).md | 14 +- .../플랫폼 저항성(Platform Resistance).md | 14 +- .../플랫폼 저항성(Platform Resistances).md | 14 +- 10_Wiki/Topics/Infrastructure-as-Code-IaC.md | 31 - .../Topics/Inheritance-and-Polymorphism.md | 27 - 10_Wiki/Topics/Inner-Product-Spaces.md | 32 - 10_Wiki/Topics/Innovation.md | 31 - 10_Wiki/Topics/Inpainting & Outpainting.md | 10 +- 10_Wiki/Topics/Input-Validation-Strategies.md | 29 - 10_Wiki/Topics/Inquiry-Based Learning.md | 33 - 10_Wiki/Topics/Instance-based-Learning.md | 30 - 10_Wiki/Topics/InstancedMesh2 library.md | 37 - 10_Wiki/Topics/Instinct.md | 32 - 10_Wiki/Topics/Instruction-Tuning.md | 26 - 10_Wiki/Topics/Intangible-Capital.md | 32 - .../Integrated-Development-Environment.md | 28 - 10_Wiki/Topics/Integration-Testing-for-AI.md | 28 - 10_Wiki/Topics/Intellectual-Property-in-AI.md | 28 - .../Topics/Interaction to Next Paint (INP).md | 48 - .../Topics/Interaction-to-Next-Paint-INP.md | 33 - 10_Wiki/Topics/Interdisciplinary-Research.md | 30 - .../Topics/Interface-Segregation-Principle.md | 24 - 10_Wiki/Topics/Internet of Things (IoT).md | 31 - 10_Wiki/Topics/Interop 2026.md | 32 - 10_Wiki/Topics/Interoperability.md | 31 - .../Interpretability-vs-Explainability.md | 27 - 10_Wiki/Topics/Interpretability.md | 28 - 10_Wiki/Topics/Introduction-to-Programming.md | 31 - 10_Wiki/Topics/Introspection (자기성찰).md | 31 - 10_Wiki/Topics/Inverse-Kinematics.md | 28 - .../Topics/Inverse-Reinforcement-Learning.md | 27 - 10_Wiki/Topics/Inversion.md | 32 - 10_Wiki/Topics/IoT-and-AI-Integration.md | 28 - .../Topics/Isaac-Asimovs-Laws-of-Robotics.md | 29 - .../Item-Item-Collaborative-Filtering.md | 28 - 10_Wiki/Topics/Iteration.md | 31 - 10_Wiki/Topics/Iterative Prompting.md | 12 +- .../Topics/Iterative-Development-Models.md | 29 - 10_Wiki/Topics/Iterative-Development.md | 32 - .../Topics/JIT-Compilation-in-AI-Engines.md | 28 - 10_Wiki/Topics/JSON-LD-Structured-Data.md | 29 - 10_Wiki/Topics/JSON-and-Data-Serialization.md | 28 - .../Topics/JUnit-and-Testing-Frameworks.md | 31 - .../Topics/JavaScript-Async-and-Event-Loop.md | 30 - .../JavaScript-Optimization-Patterns.md | 30 - 10_Wiki/Topics/Joint-Optimization.md | 30 - 10_Wiki/Topics/Journaling.md | 31 - 10_Wiki/Topics/Judgment.md | 30 - 10_Wiki/Topics/Just-In-Time (JIT).md | 30 - 10_Wiki/Topics/Just-in-Case.md | 31 - 10_Wiki/Topics/Just-in-time-Data-Loading.md | 28 - .../Topics/K-Means-Clustering-Foundations.md | 29 - 10_Wiki/Topics/K-Nearest-Neighbors-K-NN.md | 28 - .../Topics/KISS (Keep It Simple, Stupid).md | 31 - .../KISS-Principle-in-Software-Design.md | 29 - .../Topics/KPI (Key Performance Indicator).md | 33 - .../Kalman-Filter-and-State-Tracking.md | 28 - .../Topics/Kernel-Density-Estimation-KDE.md | 27 - 10_Wiki/Topics/Kernel-Methods-and-SVMs.md | 28 - 10_Wiki/Topics/Knowledge synthesis.md | 31 - 10_Wiki/Topics/Knowledge-Distillation.md | 28 - 10_Wiki/Topics/Knowledge-Graph-Foundations.md | 28 - 10_Wiki/Topics/Knowledge-Graph.md | 28 - .../Topics/Knowledge-Representation-in-AI.md | 28 - 10_Wiki/Topics/Knowledge-Structure.md | 31 - 10_Wiki/Topics/Kolmogorov-Complexity.md | 27 - .../Topics/Kubernetes-for-AI-Orchestration.md | 28 - 10_Wiki/Topics/Kullback-Leibler-Divergence.md | 31 - 10_Wiki/Topics/L1-and-L2-Regularization.md | 27 - 10_Wiki/Topics/L2-Regularization.md | 30 - 10_Wiki/Topics/LLM-Security-and-Safety.md | 28 - 10_Wiki/Topics/LLM.md | 37 - 10_Wiki/Topics/LOD.md | 33 - 10_Wiki/Topics/Label-Noise-and-Robustness.md | 28 - 10_Wiki/Topics/Lagrange-Multipliers.md | 27 - 10_Wiki/Topics/Language-Models.md | 32 - 10_Wiki/Topics/Large Language Models (LLM).md | 31 - ...scale-Application-Architecture-Patterns.md | 29 - .../Topics/Largest Contentful Paint (LCP).md | 38 - .../Topics/Largest-Contentful-Paint-LCP.md | 34 - 10_Wiki/Topics/Latent-Dirichlet-Allocation.md | 27 - .../Topics/Latent-Semantic-Analysis-LSA.md | 28 - 10_Wiki/Topics/Layer-Normalization.md | 28 - .../Layered-Architecture-in-Frontend.md | 30 - 10_Wiki/Topics/Lazy-Loading-Strategies.md | 29 - 10_Wiki/Topics/Leadership.md | 32 - 10_Wiki/Topics/Leaky-ReLU-and-Activations.md | 29 - 10_Wiki/Topics/Lean-Operations.md | 33 - 10_Wiki/Topics/Lean-Project-Management.md | 30 - 10_Wiki/Topics/Learning-Paths.md | 31 - 10_Wiki/Topics/Learning-Rate-Schedules.md | 29 - 10_Wiki/Topics/Learning-Rate-Scheduling.md | 29 - 10_Wiki/Topics/Least-Squares-Methods.md | 28 - 10_Wiki/Topics/Legacy-Systems.md | 31 - 10_Wiki/Topics/Lessons Learned.md | 32 - 10_Wiki/Topics/Level of Detail (LOD).md | 35 - 10_Wiki/Topics/Levels of Understanding.md | 34 - 10_Wiki/Topics/Lighting and Composition.md | 12 +- 10_Wiki/Topics/Linear-Algebra-Foundations.md | 29 - 10_Wiki/Topics/Linear-Algebra-for-ML.md | 28 - 10_Wiki/Topics/Linear-Algebra.md | 32 - .../Topics/Linear-Discriminant-Analysis.md | 27 - 10_Wiki/Topics/Linear-Programming.md | 31 - 10_Wiki/Topics/Linear-Regression-Mastery.md | 28 - 10_Wiki/Topics/Linguistic-Analysis-in-AI.md | 29 - 10_Wiki/Topics/Linked-Lists-and-Trees.md | 28 - 10_Wiki/Topics/Linux-Performance-Tuning.md | 29 - 10_Wiki/Topics/Liquid-Democracy.md | 28 - .../Topics/Liskov-Substitution-Principle.md | 25 - 10_Wiki/Topics/LlamaIndex.md | 28 - 10_Wiki/Topics/LoRA (Low-Rank Adaptation).md | 28 - 10_Wiki/Topics/Load-Balancing-Strategies.md | 31 - 10_Wiki/Topics/Local-Brain-Management.md | 28 - 10_Wiki/Topics/Local-Search.md | 31 - .../Locality-Sensitive-Hashing (LSH).md | 31 - 10_Wiki/Topics/Locality-Sensitive-Hashing.md | 28 - .../Topics/Logic & Reasoning/5R Structure.md | 6 +- .../BCG Corporate Restructuring.md | 12 +- .../Logic & Reasoning/Bottom-Up Thinking.md | 12 +- .../Business Problem Solving.md | 14 +- .../Logic & Reasoning/Complex Systems.md | 16 +- .../Consulting Problem Solving.md | 12 +- .../Topics/Logic & Reasoning/Decision Tree.md | 10 +- .../Deductive & Inductive Reasoning.md | 18 +- .../Logic & Reasoning/Deductive Reasoning.md | 12 +- .../Deductive and Inductive Reasoning.md | 14 +- .../Deductive vs. Inductive Reasoning.md | 10 +- .../Logic & Reasoning/Horizontal Logic.md | 10 +- .../Horizontal and Vertical Logic.md | 14 +- .../Logic & Reasoning/Hypothesis Tree.md | 12 +- 10_Wiki/Topics/Logic & Reasoning/Index.md | 86 +- .../Logic & Reasoning/Inductive Reasoning.md | 8 +- .../Inductive and Deductive Reasoning.md | 14 +- .../Inductive vs. Deductive Reasoning.md | 16 +- .../Topics/Logic & Reasoning/Issue Tree.md | 10 +- .../Logic & Reasoning/Linear Thinking.md | 10 +- .../Topics/Logic & Reasoning/Logic Trees.md | 20 +- ...Logical Reasoning (Deductive-Inductive).md | 12 +- .../MECE + Pyramid Principle--.md | 12 +- .../Logic & Reasoning/MECE Framework.md | 14 +- .../Logic & Reasoning/MECE Principle.md | 16 +- 10_Wiki/Topics/Logic & Reasoning/MECE.md | 12 +- .../Management Consulting Problem Solving.md | 16 +- .../McKinsey Problem Solving Game.md | 6 +- .../McKinsey Problem Solving Test (PST).md | 8 +- .../McKinsey Problem Solving.md | 10 +- .../Topics/Logic & Reasoning/Mental Models.md | 14 +- .../Minto Pyramid Principle.md | 10 +- ...sive and Collectively Exhaustive (MECE).md | 8 +- .../Logic & Reasoning/Problem Solving Game.md | 8 +- .../Problem Solving Process.md | 8 +- .../Problem Solving Skills.md | 8 +- .../Problem Solving Test (PST).md | 6 +- .../Logic & Reasoning/Problem Solving.md | 12 +- .../Logic & Reasoning/Pyramid Principle.md | 14 +- .../Topics/Logic & Reasoning/Rule of Three.md | 6 +- .../Logic & Reasoning/SCQA Framework.md | 6 +- .../Logic & Reasoning/Strategic Thinking.md | 20 +- .../Logic & Reasoning/Structural Reasoning.md | 18 +- .../매몰 비용 오류 (Sunk Cost Fallacy).md | 10 +- 10_Wiki/Topics/Logic.md | 31 - .../Topics/Logistic-Regression-Foundations.md | 28 - 10_Wiki/Topics/Logistic-Regression.md | 30 - 10_Wiki/Topics/Long Animation Frames API.md | 32 - 10_Wiki/Topics/Long Tasks.md | 39 - 10_Wiki/Topics/Long-Tail.md | 31 - 10_Wiki/Topics/Loose-Coupling.md | 27 - 10_Wiki/Topics/Loss Functions.md | 30 - 10_Wiki/Topics/Loss-Functions-Foundations.md | 28 - 10_Wiki/Topics/Low-Rank-Adaptation-LoRA.md | 28 - 10_Wiki/Topics/Lubrication.md | 32 - 10_Wiki/Topics/Lucas-Kanade-Method.md | 28 - 10_Wiki/Topics/MAP-Estimation.md | 31 - ...MBA (Master of Business Administration).md | 32 - 10_Wiki/Topics/MLA-Format.md | 31 - 10_Wiki/Topics/MLOps.md | 28 - 10_Wiki/Topics/Machine Learning (ML).md | 31 - .../Topics/Machine-Learning-Foundations.md | 29 - 10_Wiki/Topics/Machine-Learning-Lifecycle.md | 29 - 10_Wiki/Topics/Macros (매크로).md | 31 - 10_Wiki/Topics/Magic-Circle.md | 26 - 10_Wiki/Topics/Main Thread.md | 32 - 10_Wiki/Topics/Malware-Analysis.md | 30 - 10_Wiki/Topics/Management.md | 32 - 10_Wiki/Topics/Manhattan-Distance.md | 29 - 10_Wiki/Topics/MapReduce.md | 31 - 10_Wiki/Topics/Marketing/MrBeast_Algorithm.md | 10 +- 10_Wiki/Topics/Markov-Chain-Monte-Carlo.md | 27 - 10_Wiki/Topics/Markov-Chains.md | 30 - .../Topics/Markov-Decision-Process (MDP).md | 29 - 10_Wiki/Topics/Markov-Decision-Process-MDP.md | 30 - 10_Wiki/Topics/Markov-Decision-Processes.md | 33 - .../Master-of-Information-Management.md | 32 - 10_Wiki/Topics/Mastery.md | 34 - 10_Wiki/Topics/Matrix-Factorization.md | 27 - 10_Wiki/Topics/Matrix-Operations-and-AI.md | 28 - 10_Wiki/Topics/Mean-Absolute-Error-MAE.md | 28 - 10_Wiki/Topics/Mean-Squared-Error-MSE.md | 28 - ...c Interpretability (기계적 해석 가능성).md | 27 - 10_Wiki/Topics/Media-Literacy.md | 31 - .../Medical-Imaging-Data-Augmentation.md | 31 - 10_Wiki/Topics/Memetics.md | 31 - .../Memory & Systems/Allocation Timeline.md | 12 +- 10_Wiki/Topics/Memory & Systems/Index.md | 2 +- 10_Wiki/Topics/Memory-Hierarchy.md | 35 - .../Memory-Leak-Debugging-in-JavaScript.md | 33 - 10_Wiki/Topics/Mental-Models.md | 32 - .../Topics/Mental-Operations-Synthesized.md | 31 - .../Message-Queues-and-Event-Streams.md | 27 - 10_Wiki/Topics/Meta-Learning-in-AI.md | 28 - .../Apple Vision Pro Ecosystem.md | 4 +- 10_Wiki/Topics/Metaverse & Devices/Index.md | 2 +- 10_Wiki/Topics/Metaverse/Architecture.md | 4 +- 10_Wiki/Topics/Metaverse/Index.md | 4 +- 10_Wiki/Topics/Metaverse/Spatial_Computing.md | 6 +- .../Micro-interactions-and-Feedback-Loops.md | 30 - 10_Wiki/Topics/Micro-interactions.md | 30 - 10_Wiki/Topics/Microservices-Architecture.md | 29 - 10_Wiki/Topics/Middle-Out-Thinking.md | 31 - 10_Wiki/Topics/Midjourney Parameter.md | 14 +- 10_Wiki/Topics/Midjourney Parameters.md | 22 +- 10_Wiki/Topics/Midjourney V7 Draft Mode.md | 12 +- .../Topics/Midjourney V7 및 V6 워크플로우.md | 12 +- .../Midjourney V7의 Draft Mode 워크플로우.md | 12 +- ...djourney 브랜드 캠페인 및 무드보드 제작.md | 10 +- 10_Wiki/Topics/Minimal-Viable-Product.md | 31 - 10_Wiki/Topics/Minimum-Viable-Product-MVP.md | 29 - 10_Wiki/Topics/Mipmap.md | 33 - 10_Wiki/Topics/Mobile-AI-Optimization.md | 29 - 10_Wiki/Topics/Mobile-Augmented-Reality.md | 31 - ...bile-First-Responsive-Design-Principles.md | 29 - .../Topics/Model Context Protocol (MCP).md | 32 - .../Topics/Model-Agnostic-Meta-Learning.md | 27 - .../Topics/Model-Compression-Strategies.md | 29 - 10_Wiki/Topics/Model-Compression.md | 27 - 10_Wiki/Topics/Model-Deployment-Patterns.md | 29 - 10_Wiki/Topics/Model-Drift-and-Monitoring.md | 28 - 10_Wiki/Topics/Model-Ensemble-Methods.md | 28 - .../Topics/Model-Interpretability-Tools.md | 29 - .../Topics/Model-Predictive-Control (MPC).md | 28 - ...odern-Frontend-Engineering-Architecture.md | 29 - ...React-Application-Architecture-Patterns.md | 29 - .../Modern-Web-Design-Best-Practices-2025.md | 30 - 10_Wiki/Topics/Modern-Website-Architecture.md | 29 - .../Topics/Modern_Environment_Ecosystem.md | 26 - 10_Wiki/Topics/Modular-Design.md | 31 - 10_Wiki/Topics/Modular-Programming.md | 29 - 10_Wiki/Topics/Modularity.md | 31 - 10_Wiki/Topics/Momentum-and-Optimization.md | 28 - 10_Wiki/Topics/Monolithic-vs-Microservices.md | 28 - 10_Wiki/Topics/Monte-Carlo-Integration.md | 28 - 10_Wiki/Topics/Monte-Carlo-Methods.md | 31 - .../Topics/Monte-Carlo-Tree-Search-MCTS.md | 29 - 10_Wiki/Topics/Moodboard Creation.md | 12 +- .../Multi-Agent-Reinforcement-Learning.md | 27 - 10_Wiki/Topics/Multi-Agent-Systems-MAS.md | 28 - .../Topics/Multi-Head-Attention-Mechanism.md | 28 - 10_Wiki/Topics/Multi-Modal-Learning.md | 28 - 10_Wiki/Topics/Multi-agent-System.md | 31 - 10_Wiki/Topics/Multi-armed-Bandit-Problem.md | 28 - 10_Wiki/Topics/Multilayer-Perceptron-MLP.md | 29 - 10_Wiki/Topics/Multimodal-Learning.md | 31 - 10_Wiki/Topics/Multinomial-Naive-Bayes.md | 28 - 10_Wiki/Topics/Multivariate-Analysis.md | 29 - 10_Wiki/Topics/Mutual-Information.md | 29 - .../NLP (Natural Language Processing).md | 32 - 10_Wiki/Topics/NLP-Attention-Mechanisms.md | 28 - 10_Wiki/Topics/NVIDIA-CUDA-and-AI.md | 29 - 10_Wiki/Topics/Naive-Bayes-Classifiers.md | 28 - .../Topics/Named-Entity-Recognition-NER.md | 28 - .../Topics/National-Language-Processing.md | 28 - .../Topics/Natural-Language-Generation-NLG.md | 28 - .../Topics/Natural-Language-Processing-NLP.md | 28 - 10_Wiki/Topics/Natural-Language-Processing.md | 28 - 10_Wiki/Topics/Nearest-Neighbor-Search.md | 28 - .../Topics/Network-Latency-Optimization.md | 29 - .../Topics/Neural-Architecture-Search-NAS.md | 28 - 10_Wiki/Topics/Neural-Architecture-Search.md | 28 - 10_Wiki/Topics/Neural-Darwinism.md | 28 - 10_Wiki/Topics/Neural-Style-Transfer.md | 28 - 10_Wiki/Topics/Neural-Symbolic-Integration.md | 34 - 10_Wiki/Topics/Neuro-Symbolic AI.md | 30 - 10_Wiki/Topics/Neuro-Symbolic-AI.md | 28 - 10_Wiki/Topics/Neurobiology-of-Reward.md | 33 - .../Topics/Neurodevelopmental Disorders.md | 35 - 10_Wiki/Topics/Neuroeconomics.md | 33 - 10_Wiki/Topics/Neuroergonomics.md | 33 - 10_Wiki/Topics/Neuroevolution.md | 27 - 10_Wiki/Topics/Neuromuscular-Adaptation.md | 33 - 10_Wiki/Topics/Neuromuscular-Control.md | 33 - ...pharmacology of Substance Use Disorders.md | 32 - .../Topics/Neuroplasticity in Addiction.md | 32 - .../Neuroplasticity in Motor Learning.md | 32 - .../Neuroplasticity-in-Motor-Learning.md | 32 - .../Topics/Neuroprosthetics-Development.md | 33 - 10_Wiki/Topics/Neuropsychiatric Disorders.md | 33 - 10_Wiki/Topics/Neuropsychology.md | 32 - .../Neurorehabilitation after Stroke.md | 33 - .../Topics/Neurorehabilitation-Post-Stroke.md | 31 - 10_Wiki/Topics/Next-js-and-Modern-Web.md | 29 - .../Topics/Nextjs-App-Router-Architecture.md | 29 - ... Sky (Large-scale planetary generation).md | 33 - 10_Wiki/Topics/No Mans Sky.md | 33 - 10_Wiki/Topics/NoSQL-Databases-in-AI.md | 29 - 10_Wiki/Topics/Nodejs 메모리 누수 분석.md | 41 - .../Nodejs 프로덕션 메모리 누수 진단.md | 50 - .../Nodejs 프로덕션 메모리 병목 분석.md | 53 - .../Nodejs-Global-Namespace-Augmentation.md | 41 - 10_Wiki/Topics/Noise-Reduction-in-AI.md | 28 - 10_Wiki/Topics/Noise.md | 31 - .../Topics/Nominal-Typing-in-TypeScript.md | 40 - ...hotorealistic-Rendering-in-Level-Design.md | 34 - .../Topics/Non-linear-Activation-Functions.md | 29 - 10_Wiki/Topics/Non-parametric-Models.md | 28 - 10_Wiki/Topics/Normalization-Strategies.md | 29 - 10_Wiki/Topics/Normalization.md | 30 - 10_Wiki/Topics/Nuclear Deterrence Models.md | 32 - 10_Wiki/Topics/Numbers-and-Games.md | 31 - 10_Wiki/Topics/Nutritional-Biochemistry.md | 33 - 10_Wiki/Topics/OKR.md | 32 - ...WA vs CWA (개방 세계 vs 폐쇄 세계 가설).md | 36 - .../Topics/Object Pooling (오브젝트 풀링).md | 34 - .../Topics/Object-Detection-Foundations.md | 30 - .../Topics/Object-Oriented-Design-Patterns.md | 33 - 10_Wiki/Topics/Object-Oriented-Programming.md | 29 - 10_Wiki/Topics/Objective-Functions.md | 28 - 10_Wiki/Topics/Objectivism.md | 32 - 10_Wiki/Topics/Observation.md | 31 - 10_Wiki/Topics/Occupational-Therapy.md | 34 - .../Off-policy-vs-On-policy-Learning.md | 27 - 10_Wiki/Topics/Okami-Ink-Wash-Aesthetics.md | 33 - 10_Wiki/Topics/Olympic-Training-Cycles.md | 33 - 10_Wiki/Topics/Olympic-Training-Models.md | 33 - 10_Wiki/Topics/Olympic-Training-Protocols.md | 32 - 10_Wiki/Topics/Omni Reference (--oref).md | 16 +- 10_Wiki/Topics/Omni Reference.md | 12 +- 10_Wiki/Topics/One-Hot-Encoding.md | 27 - 10_Wiki/Topics/One-Shot-Learning.md | 28 - .../Topics/Online-Learning-and-Streaming.md | 28 - 10_Wiki/Topics/Ontological-Engineering.md | 28 - .../Ontology-Driven-Relevancy-Filtering.md | 35 - 10_Wiki/Topics/Ontology-Engineering.md | 34 - .../Ontology-Guided Knowledge Extraction.md | 34 - .../Ontology-and-Knowledge-Representation.md | 29 - 10_Wiki/Topics/Ontology.md | 31 - 10_Wiki/Topics/Opaque-Types.md | 36 - 10_Wiki/Topics/Open-Access-Movement.md | 34 - 10_Wiki/Topics/Open-Source-AI-Ecosystem.md | 29 - 10_Wiki/Topics/OpenAI-API-Integration.md | 29 - 10_Wiki/Topics/Operations-Management.md | 29 - 10_Wiki/Topics/Operations-Research.md | 35 - 10_Wiki/Topics/Operator-Theory.md | 31 - 10_Wiki/Topics/Opportunity-Cost.md | 28 - .../Topics/Optical-Character-Recognition.md | 28 - 10_Wiki/Topics/Optimal-Control-Theory.md | 28 - 10_Wiki/Topics/Optimization-Algorithms.md | 30 - 10_Wiki/Topics/Optimization-in-AI.md | 28 - 10_Wiki/Topics/Optimization.md | 31 - 10_Wiki/Topics/Ordinal-Data-Analysis.md | 27 - 10_Wiki/Topics/Organizational Psychology.md | 35 - .../Topics/Out-of-distribution-Detection.md | 28 - .../Outer Alignment vs Inner Alignment.md | 33 - .../Topics/Outlier-Detection-Techniques.md | 29 - 10_Wiki/Topics/Outside-Thinking.md | 31 - .../Topics/Overfitting-and-Underfitting.md | 27 - 10_Wiki/Topics/Overfitting.md | 34 - 10_Wiki/Topics/P-Reinforce-Template-Guide.md | 31 - 10_Wiki/Topics/P-Reinforce.md | 29 - 10_Wiki/Topics/P-Reinforce_1011.md | 20 +- 10_Wiki/Topics/PCA-and-Dimension-Reduction.md | 29 - 10_Wiki/Topics/PCGML-Frameworks.md | 34 - 10_Wiki/Topics/PDF-Format.md | 31 - .../PEFT (Parameter-Efficient Fine-Tuning).md | 33 - 10_Wiki/Topics/PID-Controllers-in-AI.md | 28 - 10_Wiki/Topics/PMI-Technique.md | 31 - 10_Wiki/Topics/POMDP.md | 30 - 10_Wiki/Topics/PageSpeed Insights.md | 32 - ...Papers Please (Bureaucratic Simulation).md | 33 - 10_Wiki/Topics/Papers-Please.md | 31 - 10_Wiki/Topics/Parallel-Computing-in-AI.md | 28 - 10_Wiki/Topics/Parallel-Computing.md | 28 - 10_Wiki/Topics/Parallel-Processing.md | 32 - 10_Wiki/Topics/Parameter Control.md | 16 +- .../Topics/Parameter-Efficiency-in-LLMs.md | 28 - .../Parameter-Efficient Fine-Tuning (PEFT).md | 29 - 10_Wiki/Topics/Parameter-Sharing.md | 28 - 10_Wiki/Topics/Parameter.md | 12 +- 10_Wiki/Topics/Pareto-Principle.md | 31 - .../Topics/Partial-Differential-Equations.md | 27 - 10_Wiki/Topics/Particle-Filter-Algorithms.md | 27 - 10_Wiki/Topics/Pattern-Recognition.md | 28 - 10_Wiki/Topics/Pedestrian-Modeling.md | 35 - 10_Wiki/Topics/Perceptrons-Foundations.md | 28 - 10_Wiki/Topics/Perceptual-Learning.md | 28 - 10_Wiki/Topics/Perceptual-Motor-Skills.md | 35 - .../Topics/Performance Management Systems.md | 35 - 10_Wiki/Topics/Performance Psychology.md | 33 - 10_Wiki/Topics/Performance-Metrics-in-AI.md | 29 - 10_Wiki/Topics/Periodization-Theory.md | 31 - 10_Wiki/Topics/Personal-Brain-Management.md | 29 - .../Topics/Personal-Information-Security.md | 29 - 10_Wiki/Topics/Personalization-Engines.md | 34 - .../Topics/Phase-Transitions-in-Learning.md | 28 - 10_Wiki/Topics/Philosophy.md | 31 - 10_Wiki/Topics/Physical-Intelligence.md | 31 - .../Aerospace Flight Simulation.md | 6 +- 10_Wiki/Topics/Physics & Simulation/Index.md | 2 +- ...hysics-Informed Neural Networks (PINNs).md | 28 - .../Physics-informed-Neural-Networks.md | 28 - 10_Wiki/Topics/Physics.md | 31 - 10_Wiki/Topics/Pipeline-Parallelism.md | 27 - 10_Wiki/Topics/Pivot-Table-Analysis.md | 29 - 10_Wiki/Topics/Platform-Engineering.md | 28 - 10_Wiki/Topics/Player-Experience-Modeling.md | 35 - .../Player-Psyche-Profiling-Framework.md | 35 - 10_Wiki/Topics/Plutchiks-Wheel-of-Emotions.md | 37 - 10_Wiki/Topics/Poetic-Computation.md | 35 - 10_Wiki/Topics/Point-Cloud-Processing.md | 28 - 10_Wiki/Topics/Point-of-Sale.md | 31 - 10_Wiki/Topics/Policy-Gradient-Methods.md | 28 - 10_Wiki/Topics/Policy-Optimization.md | 35 - 10_Wiki/Topics/Policy-Surveillance.md | 35 - 10_Wiki/Topics/PolicyIQ.md | 32 - .../Polymorphism-in-Engine-Architecture.md | 32 - 10_Wiki/Topics/Pooling.md | 32 - 10_Wiki/Topics/Pose-Estimation.md | 29 - 10_Wiki/Topics/Positive Prompts.md | 12 +- 10_Wiki/Topics/Positive-Reinforcement.md | 28 - .../Topics/Posterior-and-Prior-Probability.md | 28 - 10_Wiki/Topics/Poverty-Cycle-Dynamics.md | 33 - 10_Wiki/Topics/Poverty-Simulation.md | 35 - 10_Wiki/Topics/Practical-Cryptography.md | 36 - 10_Wiki/Topics/Pre-Mortem-Analysis.md | 31 - 10_Wiki/Topics/Pre-processing-Data-for-AI.md | 29 - 10_Wiki/Topics/Precision-Recall-Tradeoff.md | 28 - 10_Wiki/Topics/Precision-Recursion.md | 31 - 10_Wiki/Topics/Predictive-Analytics.md | 29 - 10_Wiki/Topics/Predictive-Coding.md | 28 - 10_Wiki/Topics/Prenatal-Neurology.md | 34 - .../Preserving-State-in-Procedural-Worlds.md | 32 - .../Topics/Principal-Component-Analysis.md | 28 - .../Topics/Principle-Component-Analysis.md | 32 - 10_Wiki/Topics/Principle-of-Least-Action.md | 28 - ...rinciples of Structuralism (Linguistic).md | 33 - 10_Wiki/Topics/Principles-of-Architecture.md | 36 - 10_Wiki/Topics/Principles-of-Data-Connect.md | 33 - 10_Wiki/Topics/Principles-of-Structuralism.md | 35 - 10_Wiki/Topics/Principles.md | 31 - .../Topics/Prioritized-Experience-Replay.md | 28 - 10_Wiki/Topics/Prisoners-Dilemma-Models.md | 38 - 10_Wiki/Topics/Prisons-and-Self-Correction.md | 33 - 10_Wiki/Topics/Privacy-Preserving-AI.md | 29 - .../Topics/Probabilistic-Graphical-Models.md | 28 - 10_Wiki/Topics/Probabilistic-Reasoning.md | 31 - 10_Wiki/Topics/Probability Theory.md | 35 - .../Topics/Probability and Logic Fusion.md | 32 - .../Topics/Probability-Theory-Foundations.md | 29 - 10_Wiki/Topics/Problem-Solving.md | 32 - ...Generation via Machine Learning (PCGML).md | 35 - .../Topics/Procedural Narrative Generation.md | 34 - .../Topics/Procedural Rhetoric (In Gaming).md | 33 - .../Topics/Procedural-Architecture-Systems.md | 35 - 10_Wiki/Topics/Procedural-Knowledge.md | 31 - 10_Wiki/Topics/Procedural-Level-Geometry.md | 35 - 10_Wiki/Topics/Procedural-Rhetoric.md | 34 - 10_Wiki/Topics/Process-Automation-with-AI.md | 27 - 10_Wiki/Topics/Processing.md | 31 - 10_Wiki/Topics/Product-Led-Growth.md | 32 - 10_Wiki/Topics/Product-Management.md | 32 - 10_Wiki/Topics/Product-Marketing.md | 31 - 10_Wiki/Topics/Product-Thinking-in-AI.md | 29 - 10_Wiki/Topics/Productivity-Hacks-for-Devs.md | 29 - 10_Wiki/Topics/Profiling-and-Optimization.md | 29 - .../Programming & Formal Methods/Index.md | 2 +- .../Type Theory.md | 8 +- .../API 응답 및 에러 핸들링 아키텍처.md | 10 +- .../AST (추상 구문 트리).md | 12 +- .../AST(Abstract Syntax Tree).md | 12 +- .../Advanced-Design-Patterns-in-TypeScript.md | 4 +- .../Ambient Contexts.md | 4 +- .../Ambient Declarations.md | 4 +- .../AppSec (애플리케이션 보안).md | 14 +- ...서게임 연구(Beat Saber Exergaming Study).md | 10 +- .../Programming & Language/Beat Saber.md | 10 +- ...게임 후유증 연구(VR Exergaming Aftereffects).md | 14 +- .../Topics/Programming & Language/Blink.md | 14 +- .../Branch Prediction.md | 14 +- .../Branchless Security Checks.md | 16 +- .../Browser Security Mitigations.md | 24 +- .../CAD 렌더링 최적화.md | 18 +- ...택 반응 시간 과제(CANTAB 5-choice RTI).md | 10 +- .../Programming & Language/CI_CD Pipeline.md | 18 +- .../CI_CD 파이프라인 자동화.md | 18 +- .../CI_CD 파이프라인 통합 및 Git 훅(Hooks).md | 16 +- .../CI_CD 파이프라인.md | 20 +- .../CST (구체 구문 트리).md | 8 +- .../Cache Side-Channel Attack.md | 18 +- .../Cache miss rates.md | 14 +- .../Cheneys Algorithm.md | 10 +- .../Chrome DevTools Memory Panel.md | 14 +- .../Chrome DevTools(크롬 개발자 도구).md | 16 +- .../Chrome V8 Heap Analysis.md | 24 +- .../Topics/Programming & Language/Chromium.md | 14 +- .../Code Minification.md | 8 +- .../Code Obfuscation.md | 6 +- ... Lazy Loading (코드 분할 및 지연 로딩).md | 6 +- .../Code Stylometry (코드 문체론).md | 12 +- .../Concrete Syntax Tree (CST).md | 6 +- .../Continuous Integration (CI).md | 14 +- .../Cosmos 플랫폼 (Netflix).md | 10 +- .../Cumulative Layout Shift (CLS).md | 16 +- .../DAST (동적 애플리케이션 보안 테스트).md | 12 +- .../DOM 요소 조작 및 타입 좁히기.md | 8 +- .../Programming & Language/DOM 요소 조작.md | 6 +- .../Programming & Language/DeepReadonly.md | 10 +- .../Programming & Language/Depth Pre-Pass.md | 10 +- .../Discriminated Unions.md | 10 +- .../Draw Call Optimization.md | 22 +- .../Topics/Programming & Language/ESLint.md | 16 +- .../Topics/Programming & Language/Early-Z.md | 12 +- .../Programming & Language/Edge Bleeding.md | 14 +- .../Effect TS 및 ts-brand 라이브러리 활용.md | 12 +- .../Programming & Language/Effect TS.md | 4 +- .../Electron V8 Memory Cage.md | 16 +- .../Topics/Programming & Language/Electron.md | 8 +- .../Escape Hatch (탈출구).md | 6 +- .../Excess Property Checking.md | 10 +- .../Programming & Language/Exergaming.md | 14 +- .../Facade Pattern (퍼사드 패턴).md | 6 +- .../Topics/Programming & Language/Figma.md | 8 +- .../Programming & Language/Flame Chart.md | 12 +- .../Topics/Programming & Language/Fuzzing.md | 4 +- .../Topics/Programming & Language/GC Root.md | 14 +- .../Garbage Collection(가비지 컬렉션).md | 24 +- .../Generational Hypothesis.md | 14 +- .../Programming & Language/Git Hooks.md | 14 +- ...t Hook을 이용한 CI_CD 자동화 파이프라인.md | 10 +- ...mmit 훅을 활용한 개발 워크플로우 자동화.md | 12 +- .../Global Network Positioning (GNP).md | 6 +- .../Programming & Language/Google Chrome.md | 16 +- .../Google Code Jam Dataset.md | 6 +- .../Google Lighthouse.md | 14 +- .../Programming & Language/Heap Snapshot.md | 16 +- .../Topics/Programming & Language/Husky.md | 14 +- .../IBM 가비지 컬렉션.md | 16 +- .../Topics/Programming & Language/IFCjs.md | 12 +- .../Incremental Marking.md | 16 +- .../Programming & Language/Index Masking.md | 14 +- .../Topics/Programming & Language/Index.md | 864 ++--- .../InstancedMesh 동적 버퍼 확장.md | 14 +- ... 시 드로우 콜 최적화의 한계점 사례 연구.md | 20 +- .../InstancedMesh 최적화.md | 22 +- .../Programming & Language/InstancedMesh.md | 20 +- .../Programming & Language/Interop 2025.md | 12 +- .../Inventory Management Example.md | 10 +- .../Topics/Programming & Language/JPEG XL.md | 8 +- .../Programming & Language/JavaScriptCore.md | 16 +- .../Topics/Programming & Language/Joern.md | 6 +- .../MVC (Model-View-Controller).md | 8 +- .../Topics/Programming & Language/Major GC.md | 14 +- .../Mark-Sweep-Compact 알고리즘.md | 12 +- .../Mark-Sweep-Compact(메이저 GC).md | 16 +- .../Programming & Language/Mark-Sweep.md | 20 +- ...Monorepo(Turborepo 등) 환경의 린트 관리.md | 18 +- .../Topics/Programming & Language/Monorepo.md | 16 +- .../Netflix 마이크로서비스 전환.md | 10 +- .../Network Coordinate Systems.md | 12 +- .../New Space(Young Generation).md | 10 +- .../Nodejs Memory Tuning.md | 14 +- .../Nodejs Production Monitoring.md | 14 +- .../Nodejs 메모리 최적화.md | 18 +- .../Nodejs 메모리 튜닝.md | 20 +- .../Nodejs 성능 디버깅.md | 22 +- .../Nodejs 성능 최적화 및 디버깅.md | 16 +- ...Nodejs 프로세스 모니터링 및 메모리 분석.md | 18 +- .../Topics/Programming & Language/Nodejs.md | 18 +- ...NotebookLM-Automated-Authentication-CLI.md | 6 +- .../Object Pooling (오브젝트 풀링).md | 12 +- ...eb Worker를 활용한 메인 스레드 병목 해결.md | 10 +- .../Topics/Programming & Language/Oilpan.md | 10 +- .../Old Space (구 세대 공간).md | 14 +- .../Old Space(Old Generation).md | 18 +- .../Programming & Language/Old Space.md | 16 +- .../Orinoco 가비지 컬렉터.md | 16 +- .../Orinoco 프로젝트.md | 14 +- .../Topics/Programming & Language/Orinoco.md | 14 +- .../Topics/Programming & Language/Overdraw.md | 10 +- .../Page Experience Algorithm.md | 12 +- .../Parse dont validate.md | 8 +- .../Performance Panel.md | 16 +- .../Pointer Compression.md | 12 +- .../Pointer Poisoning.md | 12 +- .../Topics/Programming & Language/Prettier.md | 12 +- .../Reachability Analysis.md | 14 +- .../React 19 Compiler.md | 14 +- .../React 및 Nextjs 개발 환경.md | 16 +- .../React 재조정 (Reconciliation) 최적화.md | 18 +- .../React 컴포넌트 Props 전달 및 상태 관리.md | 10 +- .../Programming & Language/Readonly Type.md | 12 +- .../Readonly 유틸리티 타입.md | 10 +- .../Real User Monitoring (RUM).md | 10 +- .../Programming & Language/Render State.md | 12 +- .../Programming & Language/Result Type.md | 10 +- .../Robust-GitHub-Sync-Pipeline.md | 10 +- .../SCA (소프트웨어 구성 분석).md | 12 +- .../Programming & Language/SOLID 원칙.md | 12 +- .../SPA 라우트 전환 성능 최적화.md | 12 +- .../Satisfies Operator.md | 14 +- .../Topics/Programming & Language/Scavenge.md | 12 +- .../Scavenger 알고리즘.md | 16 +- .../Programming & Language/Scheduler API.md | 10 +- .../Server Architecture.md | 6 +- ...redArrayBuffer vs postMessage 성능 차이.md | 6 +- .../SharedArrayBuffer 동시성 문제 해결법.md | 10 +- ...ffer 보안 이슈와 Cross-Origin Isolation.md | 8 +- ...yBuffer 보안을 위한 COOP COEP 헤더 설정.md | 8 +- ...위한 Cross-Origin Isolation 서버 헤더 설정.md | 10 +- ...fer로 스레드 간 메모리 공유 효율 높이기.md | 10 +- ...aredArrayBuffer와 Atomics 구체적 활용법.md | 8 +- .../Side-channel Attack.md | 18 +- .../Single Page Applications (SPA).md | 10 +- .../Topics/Programming & Language/Spectre.md | 16 +- .../Speculative Execution.md | 16 +- .../Programming & Language/Stop-the-world.md | 14 +- .../Structural Typing.md | 10 +- .../Programming & Language/StyleCounsel.md | 8 +- .../Programming & Language/Submodules.md | 8 +- .../Synthetic Testing.md | 16 +- .../Topics/Programming & Language/TeamCity.md | 4 +- .../Programming & Language/Texture Atlas.md | 18 +- .../Throttling Debouncing.md | 8 +- .../Programming & Language/Timing Attack.md | 16 +- .../Programming & Language/Timing Attacks.md | 18 +- .../To-Space와 From-Space.md | 14 +- ...반 외부 연동사 플러그인 개발 생태계 구축.md | 8 +- .../Toss Front SDK의 Facade 패턴 적용 사례.md | 8 +- .../Turborepo 기반 모노레포 워크플로우.md | 16 +- .../Turborepo 환경 구성.md | 14 +- .../Programming & Language/Turborepo.md | 14 +- ... 다중 애플리케이션 및 라이브러리 통합 관리.md | 14 +- .../Programming & Language/Type Casting.md | 8 +- ...Error Handling Exhaustiveness Checking.md | 8 +- .../Programming & Language/TypeScript 49.md | 10 +- .../TypeScript API Development.md | 8 +- .../TypeScript Advanced Type System.md | 22 +- ...eScript Utility Types (Record Readonly).md | 10 +- ...pt 타입 시스템 (TypeScript Type System).md | 16 +- ...peScript 타입 시스템 및 인터페이스 설계.md | 12 +- ...템을 활용한 내부 로직 보호 및 데이터 검증.md | 14 +- ...ript의 제어 흐름 분석 및 상태 관리 패턴.md | 10 +- .../Programming & Language/Union Types.md | 10 +- .../V8 Engine Heap Management.md | 24 +- .../Programming & Language/V8 Engine.md | 22 +- .../V8 Heap Architecture.md | 20 +- .../V8 JavaScript Engine.md | 24 +- .../V8 가비지 컬렉션(Garbage Collection).md | 22 +- .../V8 메모리 케이지(V8 Memory Cage).md | 14 +- .../V8 엔진 힙 아키텍처 및 로그 분석.md | 24 +- .../V8 엔진 힙 아키텍처.md | 18 +- ... 메모리 관리 아키텍처 및 Orinoco 프로젝트.md | 24 +- .../V8 힙 공간(V8 Heap Spaces).md | 14 +- .../Programming & Language/V8 힙(Heap).md | 18 +- .../Programming & Language/VR Sickness.md | 8 +- .../VR 멀미 (VR Sickness).md | 12 +- .../VR 멀미(VR sickness).md | 12 +- .../Vergence-Accommodation Conflicts.md | 10 +- ...제 고부하 병렬 처리 구현체 (실패_성공 포함).md | 4 +- .../WebKit Security Mitigations.md | 20 +- .../Topics/Programming & Language/WebKit.md | 16 +- .../Programming & Language/Write Barrier.md | 10 +- .../Zod 런타임 유효성 검사 통합.md | 6 +- ... 브랜디드 타입을 결합한 런타임 데이터 검증.md | 8 +- 10_Wiki/Topics/Programming & Language/Zod.md | 12 +- .../Zustand-Based-Mission-Persistence.md | 10 +- .../as const Assertion.md | 10 +- .../Topics/Programming & Language/as const.md | 8 +- ...ffer를 결합한 멀티스레드 고성능 아키텍처.md | 10 +- ...CS와 SharedArrayBuffer의 실제 코드 통합.md | 6 +- .../eslint-config-prettier.md | 12 +- .../eslint-plugin-prettier.md | 10 +- .../Programming & Language/lint-staged.md | 16 +- .../never 타입(never type).md | 8 +- .../Programming & Language/never 타입.md | 10 +- .../Topics/Programming & Language/readonly.md | 12 +- .../satisfies Keyword.md | 12 +- .../satisfies 연산자.md | 14 +- .../Topics/Programming & Language/ts-brand.md | 12 +- .../useEffect 클린업(Cleanup).md | 12 +- .../가비지 컬렉션 (Garbage Collection).md | 20 +- .../가비지 컬렉터(Garbage Collector).md | 22 +- .../가상현실 멀미 (VR Sickness).md | 10 +- ...효과 연구(Virtual Reality Aftereffects Study).md | 12 +- ... 후유증 연구(VR Exergaming Aftereffects Study).md | 14 +- ...(Virtual reality exergaming aftereffects research).md | 12 +- ...실 후유증 (Virtual Reality Aftereffects).md | 8 +- .../가상현실 후유증(VR Aftereffects).md | 10 +- ...게임 인지 사후 효과 분석(CANTAB 5-choice RTI).md | 8 +- .../가상현실(VR) 자전거 시뮬레이터.md | 4 +- .../감각 통합(Sensory integration).md | 8 +- .../Programming & Language/개발자 경험(DX).md | 8 +- .../객체 지향 소프트웨어 아키텍처 설계.md | 10 +- .../객체 지향 프로그래밍 (OOP).md | 12 +- ... 프로그래밍 (Object-Oriented Programming).md | 8 +- .../객체 지향 프로그래밍(OOP).md | 8 +- .../견고한 도메인 모델 및 API 계약 설계.md | 12 +- .../결합도 (Coupling).md | 8 +- .../경고 피로 (Alert Fatigue).md | 8 +- .../계층화 아키텍처 (Layered Architecture).md | 12 +- ...잉 속성 체크 (Excess Property Checking).md | 14 +- .../과잉 속성 체크(EPC).md | 12 +- ...잉 속성 체크(Excess Property Checking).md | 12 +- ...심사의 분리 (Separation of Concerns SoC).md | 18 +- .../관심사의 분리 (Separation of Concerns).md | 14 +- .../관심사의 분리 (SoC).md | 12 +- .../관심사의 분리(Separation of Concerns).md | 14 +- .../관심사의 분리(SoC).md | 12 +- .../관점 지향 프로그래밍 (AOP).md | 4 +- .../관점 지향 프로그래밍(AOP).md | 6 +- .../교집합 타입(Intersection Type).md | 6 +- .../구조적 타이핑(Structural Typing).md | 10 +- .../Programming & Language/구조적 타이핑.md | 10 +- ...본 타입에의 집착 (Primitive Obsession).md | 12 +- ...기본 타입에의 집착(Primitive Obsession).md | 8 +- .../깊이 지각 (Depth Perception).md | 10 +- .../깊이 지각(Depth perception).md | 12 +- ...딩 파이프라인 (Netflix Video Encoding Pipeline).md | 8 +- ...플릭스 코스모스 플랫폼 (Netflix Cosmos).md | 12 +- ...x)의 마이크로서비스 및 코스모스 플랫폼 전환.md | 12 +- ...의 코스모스 플랫폼 및 마이크로서비스 전환.md | 14 +- ...절 충돌(Vergence-accommodation conflicts).md | 12 +- .../느슨한 결합 (Loose Coupling).md | 12 +- .../단일 책임 원칙 (SRP).md | 8 +- ...임 원칙 (Single Responsibility Principle).md | 8 +- .../단일 책임 원칙(SRP).md | 4 +- ...모 TypeScript 애플리케이션 아키텍처 설계.md | 12 +- ... TypeScript 프로젝트의 컴파일 성능 최적화.md | 6 +- .../대규모 데이터 렌더링 및 가상화 최적화.md | 10 +- ...포(Turborepo) 환경에서의 린트 오케스트레이션.md | 18 +- .../대규모 웹 그래픽스 프로젝트.md | 16 +- ... 애플리케이션의 조직 및 기술적 확장성 확보.md | 12 +- .../덕 타이핑(Duck Typing).md | 8 +- ... (DevSecOps) 환경에서의 지속적인 보안 검사.md | 14 +- .../데이터 거버넌스 (Data Governance).md | 6 +- ...달 가능성 분석 (Reachability Analysis).md | 14 +- ...메인 기반 설계 (DDD) 및 데이터 오염 방지.md | 6 +- .../도메인 기반 설계 (DDD).md | 12 +- .../도메인 기반 설계(DDD).md | 4 +- .../도메인 기반 설계(DDD)의 데이터 검증.md | 4 +- ...진적 마킹(Concurrent Incremental Marking).md | 18 +- .../동작 속도(Movement Speed).md | 10 +- .../동적 애플리케이션 보안 테스트(DAST).md | 10 +- .../라이브러리 및 확장 가능한 코드베이스.md | 8 +- .../런타임 상태 검증(Runtime Validation).md | 6 +- .../리로디드(Reloaded).md | 8 +- .../리터럴 타입 (Literal Types).md | 10 +- .../마이크로서비스 아키텍처 (MSA).md | 14 +- .../마크-스윕(Mark-Sweep).md | 16 +- ... 디스플레이(HMD) 환경의 시각적 후유증 연구.md | 8 +- .../메모리 누수(Memory Leaks).md | 18 +- .../명목적 타이핑 (Nominal Typing).md | 10 +- .../명목적 타이핑(Nominal Typing).md | 12 +- .../모노레포(Monorepo) 기반 구성 중앙화.md | 16 +- .../모노레포(Monorepo) 설정 중앙화.md | 14 +- .../모노레포(Monorepo) 아키텍처 설정.md | 14 +- ...리식 아키텍처 (Monolithic Architecture).md | 8 +- .../모듈러 통합 건설 (MiC).md | 6 +- .../모듈화 및 아키텍처 경계 설정.md | 16 +- .../반응 시간(Reaction Time).md | 10 +- ...(Data Transformation between Backend and Frontend).md | 14 +- ...즈니스 도메인 (금융 헬스케어 이커머스 등).md | 12 +- .../불변성 (Immutability).md | 14 +- .../불변성(Immutability).md | 14 +- .../불필요한 리렌더링 방지.md | 14 +- .../브라우저 메모리 관리 및 최적화.md | 18 +- .../브라우저 및 Nodejs 메모리 튜닝.md | 20 +- .../브랜디드 타입 (Branded Types).md | 10 +- ... 후유증 평가(Beat Saber Exergaming Aftereffects).md | 12 +- .../비트 세이버(Beat Saber) 실험.md | 10 +- .../비트 세이버(Beat Saber) 엑서게임 연구.md | 10 +- .../비트 세이버(Beat Saber).md | 12 +- ...Beat Saber_ An Investigation of Virtual Reality Aftereffects).md | 12 +- ...링(State Management and API Response Modeling).md | 10 +- .../상태 머신(State Machine) 설계.md | 10 +- .../서드파티 라이브러리 및 API 연동.md | 8 +- .../Programming & Language/선언 파일(dts).md | 10 +- ...블 설계(Configuration Objects and Lookup Tables).md | 12 +- .../세대 가설(Generational Hypothesis).md | 18 +- .../소프트웨어 구성 분석(SCA).md | 12 +- .../소프트웨어 아키텍처 베스트 프랙티스.md | 14 +- .../소프트웨어 아키텍처 설계.md | 14 +- .../수동 코드 리뷰 (Manual Code Review).md | 10 +- .../Programming & Language/수동 코드 리뷰.md | 6 +- ...절 불일치(Vergence-Accommodation Conflict).md | 10 +- .../순차적 게이트 아키텍처.md | 4 +- .../스캐빈저(Scavenger) _ 마이너 GC.md | 16 +- .../스택 트레이스(Stack trace).md | 12 +- ...랭글러 피그 패턴(Strangler Fig Pattern).md | 6 +- .../스파게티 코드 (Spaghetti Code).md | 8 +- ...티파이 자율적 분대 모델 (Spotify Squad).md | 8 +- ...크로 프론트엔드 (Spotify Squads and Micro Frontends).md | 10 +- .../스포티파이 자율적 분대 모델.md | 6 +- ...y)의 스쿼드 모델 및 마이크로 프론트엔드 도입.md | 8 +- .../시각 및 인지적 후유증 연구.md | 12 +- ...-전정 갈등 (Visual-Vestibular Conflict).md | 8 +- ...정 감각 충돌(Visual-Vestibular Conflict).md | 8 +- ...각-전정 충돌(Visual-vestibular conflict).md | 10 +- .../시프트 레프트 (Shift-Left).md | 12 +- .../시프트 레프트(Shift-Left).md | 12 +- .../식별 가능한 유니온.md | 8 +- .../실재감(Presence).md | 8 +- .../쓰기 장벽(Write Barrier).md | 16 +- .../안구 운동 기능 (Oculomotor Functions).md | 8 +- .../안구 운동 기능(Oculomotor functions).md | 10 +- .../안구 운동 증상(Oculomotor Symptoms).md | 12 +- ...TypeScript 데이터 모델링 및 설정 관리 구축.md | 16 +- .../안전한 소프트웨어 개발 수명주기(SSDLC).md | 10 +- ...수 없는 외부 데이터 검증 (unknown types).md | 8 +- .../약한 타입 검사(Weak Type Detection).md | 8 +- .../약한 타입 탐지 (Weak Type Detection).md | 6 +- .../에일리어싱 (Aliasing).md | 10 +- .../엑서게임(Exergaming).md | 14 +- .../엔터프라이즈 소프트웨어 개발.md | 8 +- .../엔터프라이즈 소프트웨어 시스템 설계.md | 12 +- ...프라이즈 애플리케이션 및 점진적 리팩토링.md | 12 +- .../엔터프라이즈 애플리케이션 설계.md | 16 +- .../오래된 공간(Old Space).md | 18 +- .../오리노코(Orinoco GC).md | 18 +- .../오리노코(Orinoco) 프로젝트.md | 18 +- .../오버드로우(Overdraw).md | 16 +- ...픈소스 컴포넌트 (Open Source Components).md | 12 +- .../완전성 검사(Exhaustiveness Checking).md | 8 +- .../외부 API 데이터 및 설정 파일 처리.md | 14 +- .../외부 API 데이터의 런타임 검증 후 처리.md | 8 +- .../외부 라이브러리 API 설계.md | 6 +- .../웹 애플리케이션의 3계층 구조.md | 14 +- .../웹 워커 이벤트 포워딩 Event Forwarding.md | 12 +- ...워커 이벤트 포워딩 통신 지연 최소화 방법.md | 6 +- .../웹 프론트엔드 성능 최적화.md | 18 +- .../유니온 타입(Union Types).md | 12 +- .../유스케이스 (Use Cases).md | 6 +- .../응집도 (Cohesion).md | 12 +- ...응집도와 결합도 (Cohesion and Coupling).md | 8 +- .../Programming & Language/응집도와 결합도.md | 6 +- .../의존성 역전 (Dependency Inversion).md | 10 +- .../의존성 역전 원칙 (DIP).md | 12 +- ... 원칙 (Dependency Inversion Principle DIP).md | 12 +- ...역전 원칙 (Dependency Inversion Principle).md | 12 +- .../의존성 주입 (DI).md | 8 +- .../의존성 주입 (Dependency Injection).md | 14 +- .../Programming & Language/의존성 주입(DI).md | 8 +- .../이동 속도(Movement Speed).md | 8 +- ... 기반 아키텍처 (Event-Driven Architecture).md | 10 +- .../이전 세대(Old Generation_Space).md | 20 +- .../이커머스의 실시간 재고 관리.md | 6 +- .../자동화된 코드 리뷰.md | 14 +- .../자바 가상 머신(JVM).md | 10 +- ... 실행되는 실시간 데이터 대시보드 최적화.md | 12 +- .../재귀적 불변성 (DeepReadonly).md | 10 +- .../점진적 마킹(Incremental marking).md | 16 +- .../정적 분석(Static Analysis).md | 14 +- .../제어 흐름 분석 (Control Flow Analysis).md | 12 +- ... 불일치 (Vergence-Accommodation Conflict).md | 8 +- ...주 불일치(Vergence-Accommodation Conflict).md | 10 +- .../집합론 (Set Theory).md | 8 +- .../집합론(Set Theory).md | 8 +- .../철벽 수비대 인터페이스 설계 전략.md | 14 +- ... 타입 시스템과 견고한 인터페이스 설계의 정수.md | 18 +- ...과 속성 검사 (Excess Property Checking).md | 14 +- ...초과 속성 검사 (Excess Property Checks).md | 10 +- .../추상 구문 트리(AST).md | 12 +- .../추상화(Abstraction).md | 10 +- .../Topics/Programming & Language/추상화.md | 10 +- .../카오스 몽키(Chaos Monkey).md | 8 +- .../코드 리뷰 (Code Review).md | 14 +- ...자 인식)에 미치는 영향을 평가하는 기계 학습 모델 분류 연구.md | 8 +- .../코드 축소 (Code minification).md | 10 +- .../코드 포매팅 (Code formatting).md | 14 +- ...동화 (Code Quality Management and Automation).md | 16 +- .../클로저(Closures).md | 10 +- ... 계측(Allocation instrumentation on timeline).md | 10 +- .../타입 가드 (Type Predicates).md | 8 +- .../타입 가드(Type Guards).md | 8 +- .../타입 단언 (Type Assertions).md | 12 +- .../타입 단언(Type Assertion).md | 10 +- .../타입 단언(Type Assertions).md | 12 +- .../타입 서술어 (Type Predicates).md | 4 +- .../타입 서술어(Type Predicates).md | 8 +- .../타입 안전성 (Type Safety).md | 12 +- ... 정의가 부족한 서드파티 라이브러리 연동.md | 8 +- .../타입 조건자(Type Predicates).md | 6 +- .../타입 좁히기 (Type Narrowing).md | 14 +- .../타입 좁히기(Type Narrowing).md | 16 +- .../타입 캐스팅 (Type Casting).md | 10 +- ...입스크립트 상태 관리 및 분기 처리 설계.md | 10 +- .../Programming & Language/타파스(Tapas).md | 4 +- .../토스(Toss) Front SDK 퍼사드 패턴 적용.md | 10 +- .../토스(Toss) SDK 설계.md | 6 +- ...플레이스 결제 단말기 외부 연동 SDK 개발.md | 8 +- .../팀 단위 코드 품질 및 컨벤션 유지.md | 16 +- .../포인터 압축(Pointer Compression).md | 14 +- ...절 갈등 (Vergence-Accommodation Conflict).md | 8 +- ... 불일치(Vergence-Accommodation Conflicts).md | 10 +- ...절 불일치(Vergence-accommodation conflict).md | 8 +- ...엔드 및 모노레포(Monorepo) 개발 환경 설정.md | 16 +- .../핀테크의 실시간 사기 탐지.md | 6 +- .../할당 타임라인(Allocation Timeline).md | 16 +- .../힙 메모리(Heap Memory).md | 22 +- .../힙 스냅샷 (Heap Snapshots).md | 14 +- .../NDF (Neutral Data Format).md | 12 +- 10_Wiki/Topics/Programming & Tools/War-Yes.md | 8 +- .../Programming & Tools/ndf-parse 패키지.md | 10 +- .../Topics/Programming & Tools/ndf-parse.md | 8 +- .../가변적 LOD(Level of Detail) 시스템.md | 8 +- .../데이터 파싱 (Data Parsing).md | 12 +- .../데이터 파싱(Data Parsing).md | 14 +- .../지연 렌더링(Deferred Rendering).md | 12 +- .../텔레메트리 (Telemetry) 밸런싱.md | 8 +- .../텔레메트리 (Telemetry).md | 8 +- .../텔레메트리 데이터 (Telemetry Data).md | 8 +- ...텔레메트리 밸런싱 (Telemetry Balancing).md | 8 +- .../텔레메트리 밸런싱(Telemetry Balancing).md | 8 +- .../텔레메트리(Telemetry) 데이터 분석.md | 10 +- .../Topics/Programming & Web/ASPNET Core.md | 6 +- 10_Wiki/Topics/Programming & Web/Index.md | 2 +- 10_Wiki/Topics/Progressive-Disclosure.md | 28 - .../Project-Management-Best-Practices.md | 29 - 10_Wiki/Topics/Project-Management.md | 32 - 10_Wiki/Topics/Prompt Structure.md | 16 +- .../Topics/Prompt-Engineering-Foundations.md | 29 - 10_Wiki/Topics/Prompt-Engineering.md | 29 - 10_Wiki/Topics/Proprioception.md | 34 - 10_Wiki/Topics/Pros-Cons-Table.md | 30 - 10_Wiki/Topics/Protocols.md | 31 - 10_Wiki/Topics/Prototyping.md | 31 - .../Proximal Policy Optimization (PPO).md | 35 - .../Topics/Proximal-Policy-Optimization.md | 28 - 10_Wiki/Topics/Pruning-Techniques.md | 28 - .../Topics/Ps-Reinforce Policy Framework.md | 36 - 10_Wiki/Topics/Ps-Reinforce.md | 35 - 10_Wiki/Topics/Psychology & Behavior.md | 36 - .../Amygdala Hyperactivity.md | 8 +- .../Behavioral Segmentation.md | 14 +- .../FOMO (Fear of Missing Out).md | 6 +- 10_Wiki/Topics/Psychology & Behavior/Index.md | 10 +- .../Psychology & Behavior/게이미피케이션.md | 10 +- .../대수의 법칙(Law of Large Numbers).md | 8 +- .../소셜 엔지니어링 (Social Engineering).md | 10 +- .../Topics/Psychology & Behavior/손실 회피.md | 12 +- .../악명(Infamy) 시스템.md | 4 +- .../Functional Behavior Analysis (FBA).md | 10 +- .../Topics/Psychology & Education/Index.md | 2 +- 10_Wiki/Topics/Psychology-of-Learning.md | 28 - 10_Wiki/Topics/Psychology.md | 31 - 10_Wiki/Topics/Psychology/ABA.md | 12 +- .../Psychology/Addiction_Neuroscience.md | 14 +- .../Topics/Psychology/Behavioral_Economics.md | 14 +- 10_Wiki/Topics/Psychology/Dopamine.md | 12 +- 10_Wiki/Topics/Psychology/Index.md | 14 +- 10_Wiki/Topics/Psychology/Neuroplasticity.md | 10 +- 10_Wiki/Topics/Psychology/Nudge_Theory.md | 12 +- .../Topics/Psychology/Operant_Conditioning.md | 14 +- 10_Wiki/Topics/Purpose.md | 31 - 10_Wiki/Topics/PyTorch-Foundations.md | 29 - 10_Wiki/Topics/PyTorch-Lightning.md | 28 - 10_Wiki/Topics/Python-for-Data-Science.md | 29 - 10_Wiki/Topics/Q-Learning Foundations.md | 28 - 10_Wiki/Topics/Quality Gates.md | 33 - 10_Wiki/Topics/Quality-Control.md | 31 - .../Quantitative Economics (수량경제학).md | 33 - 10_Wiki/Topics/Quantization-Foundations.md | 28 - 10_Wiki/Topics/Quantization.md | 34 - 10_Wiki/Topics/Quantum Computing (Intro).md | 33 - 10_Wiki/Topics/Quantum-Computing-for-AI.md | 28 - 10_Wiki/Topics/Quantum-Computing.md | 31 - 10_Wiki/Topics/Quantum-Machine-Learning.md | 28 - 10_Wiki/Topics/Query-Optimization.md | 34 - 10_Wiki/Topics/Queue-Management-Systems.md | 29 - 10_Wiki/Topics/Quick-Wins.md | 31 - 10_Wiki/Topics/RAG (검색 증강 생성).md | 35 - 10_Wiki/Topics/RAG-and-Document-Retrieval.md | 28 - 10_Wiki/Topics/RAG.md | 31 - .../Topics/RLAIF (AI 피드백 기반 강화학습).md | 27 - .../RLHF (인간 피드백 기반 강화 학습).md | 35 - 10_Wiki/Topics/RL_Neuroscience.md | 29 - 10_Wiki/Topics/RMSProp-Optimizer.md | 27 - 10_Wiki/Topics/ROC-AUC-Curves.md | 27 - 10_Wiki/Topics/ROUGE-Metrics.md | 28 - 10_Wiki/Topics/Random-Forest-Classifiers.md | 28 - 10_Wiki/Topics/Randomized-Algorithms.md | 27 - 10_Wiki/Topics/Ranking-Algorithms.md | 28 - 10_Wiki/Topics/Rapid-Prototyping.md | 31 - 10_Wiki/Topics/ReLU-Activation-Functions.md | 28 - 10_Wiki/Topics/React-Context-API.md | 31 - .../React-Error-Boundaries-and-Handling.md | 29 - 10_Wiki/Topics/React-Hooks.md | 29 - .../Topics/React_Clean_Code_Best_Practices.md | 28 - 10_Wiki/Topics/React_Hooks_Deep_Dive.md | 26 - 10_Wiki/Topics/React_Mental_Model.md | 26 - .../Topics/React_Performance_Optimization.md | 28 - .../Topics/React_State_Management_Strategy.md | 28 - 10_Wiki/Topics/React_Testing_Strategy.md | 26 - 10_Wiki/Topics/Reactive-Programming.md | 36 - 10_Wiki/Topics/Real-time-Data-Streaming.md | 28 - 10_Wiki/Topics/Real-time-Operation.md | 32 - 10_Wiki/Topics/Reasoning.md | 31 - 10_Wiki/Topics/Recommendation-Systems.md | 29 - .../Topics/Recording Academy (The Grammys).md | 34 - .../Refactoring-Legacy-React-Codebases.md | 30 - 10_Wiki/Topics/Reference-Management.md | 31 - 10_Wiki/Topics/Reference.md | 31 - 10_Wiki/Topics/Refinement.md | 31 - 10_Wiki/Topics/Reflection.md | 31 - .../Topics/Regression-Analysis-Foundations.md | 29 - 10_Wiki/Topics/Regularization-Strategies.md | 29 - 10_Wiki/Topics/Regularization-Techniques.md | 28 - 10_Wiki/Topics/Regularization.md | 32 - 10_Wiki/Topics/Reinforcement Learning (RL).md | 36 - ...ment Learning for Automated Playtesting.md | 35 - ...ement-Learning-from-Human-Feedback-RLHF.md | 28 - 10_Wiki/Topics/Reinforcement-Learning.md | 33 - 10_Wiki/Topics/Related-Work.md | 31 - .../Topics/Relational Algebra in Databases.md | 38 - 10_Wiki/Topics/Relational-Database.md | 31 - 10_Wiki/Topics/Relational-Databases.md | 29 - 10_Wiki/Topics/Relative-Positioning.md | 29 - 10_Wiki/Topics/Relevance-Feedback.md | 28 - 10_Wiki/Topics/Reliability.md | 31 - 10_Wiki/Topics/Reliability_Safety_First.md | 28 - 10_Wiki/Topics/Remote-Rehabilitation.md | 35 - 10_Wiki/Topics/Replenishment.md | 31 - 10_Wiki/Topics/Reports.md | 31 - 10_Wiki/Topics/Repository.md | 31 - 10_Wiki/Topics/Representation Theory.md | 34 - 10_Wiki/Topics/Representation-Learning.md | 28 - 10_Wiki/Topics/Requirements.md | 32 - 10_Wiki/Topics/ResNet-Architectures.md | 29 - 10_Wiki/Topics/Research-Framework.md | 32 - 10_Wiki/Topics/Research-Methodology.md | 32 - 10_Wiki/Topics/Research.md | 31 - 10_Wiki/Topics/Residual-Networks.md | 28 - 10_Wiki/Topics/Resilience.md | 31 - 10_Wiki/Topics/Resource-Allocation.md | 31 - 10_Wiki/Topics/Resource-Management.md | 35 - 10_Wiki/Topics/Restorative Justice.md | 35 - 10_Wiki/Topics/Retainers(유지 경로).md | 40 - 10_Wiki/Topics/Retaining Path.md | 39 - .../Retrieval-Augmented-Generation-RAG.md | 28 - 10_Wiki/Topics/Revenge-Cycle-Dynamics.md | 35 - 10_Wiki/Topics/Reward Hacking (보상 해킹).md | 26 - 10_Wiki/Topics/Reward Prediction Error.md | 34 - 10_Wiki/Topics/Reward-Shaping-in-RL.md | 28 - 10_Wiki/Topics/Ridge-Regression.md | 28 - 10_Wiki/Topics/Risk Management.md | 38 - 10_Wiki/Topics/Risk-Assessment-with-AI.md | 29 - 10_Wiki/Topics/Risk-Management.md | 32 - 10_Wiki/Topics/Risk-Orchestration.md | 31 - 10_Wiki/Topics/Roadmap.md | 31 - 10_Wiki/Topics/Robotics-Foundations.md | 29 - 10_Wiki/Topics/Robotics.md | 36 - 10_Wiki/Topics/Robust-Machine-Learning.md | 28 - 10_Wiki/Topics/Robustness.md | 33 - .../Topics/Role of Conflict in Narrative.md | 36 - 10_Wiki/Topics/Root-Cause-Analysis-RCA.md | 28 - 10_Wiki/Topics/Root-Mean-Square-Error.md | 27 - 10_Wiki/Topics/Roughness (그래픽 및 물리).md | 34 - 10_Wiki/Topics/Rule-based-Systems.md | 29 - 10_Wiki/Topics/SAR.md | 31 - .../Topics/SCM (Supply Chain Management).md | 36 - .../SDLC (소프트웨어 개발 수명 주기).md | 32 - 10_Wiki/Topics/SEO.md | 28 - .../Topics/SFT (Supervised Fine-Tuning).md | 34 - 10_Wiki/Topics/SME.md | 31 - 10_Wiki/Topics/SOTA.md | 31 - 10_Wiki/Topics/SOW.md | 31 - 10_Wiki/Topics/SPOF.md | 31 - 10_Wiki/Topics/SQL-Performance-Tuning.md | 29 - 10_Wiki/Topics/SRE.md | 31 - .../Topics/SaaS (Software as a Service).md | 36 - 10_Wiki/Topics/SaaS.md | 31 - 10_Wiki/Topics/Safety & Reliability.md | 35 - 10_Wiki/Topics/Sales-Strategy.md | 32 - 10_Wiki/Topics/Sampling-Techniques.md | 30 - 10_Wiki/Topics/Scalability-in-AI-Systems.md | 29 - 10_Wiki/Topics/Scalability.md | 33 - .../Scalable-Design-System-Governance.md | 29 - 10_Wiki/Topics/Scaling-Laws-for-LLMs.md | 27 - 10_Wiki/Topics/Scheduler-Design-in-ML.md | 29 - 10_Wiki/Topics/Schema-Design-for-NoSQL.md | 28 - 10_Wiki/Topics/Schema.md | 31 - 10_Wiki/Topics/Science of Failure.md | 35 - 10_Wiki/Topics/Scientific Communication.md | 35 - .../Scientific-Computing-with-Python.md | 28 - 10_Wiki/Topics/Scientific-Method.md | 33 - 10_Wiki/Topics/Scripts.md | 33 - 10_Wiki/Topics/Search-Engine-Optimization.md | 28 - 10_Wiki/Topics/Search-Methodology.md | 31 - 10_Wiki/Topics/Search-Optimization.md | 31 - 10_Wiki/Topics/Search-Space.md | 31 - 10_Wiki/Topics/Search-Strategy.md | 33 - 10_Wiki/Topics/Search.md | 31 - 10_Wiki/Topics/Secondary-Research.md | 31 - .../Topics/Secure-Multi-party-Computation.md | 28 - .../Agentic AI Security.md | 14 +- ... (Dynamic Application Security Testing).md | 12 +- .../Excessive Agency.md | 8 +- ...teractive Application Security Testing).md | 10 +- .../Topics/Security & Reliability/Index.md | 2 +- .../Indirect Prompt Injection.md | 8 +- .../Security & Reliability/OWASP Top 10.md | 12 +- ...T (Static Application Security Testing).md | 12 +- .../Security-focused Code Review.md | 12 +- .../Shift-Left & Supply Chain Security.md | 16 +- .../Software Composition Analysis (SCA).md | 12 +- 10_Wiki/Topics/Security-Best-Practices.md | 30 - 10_Wiki/Topics/Security-Governance.md | 27 - 10_Wiki/Topics/Seed.md | 30 - 10_Wiki/Topics/Segmentsai.md | 33 - 10_Wiki/Topics/Self-Attention-Mechanisms.md | 28 - .../Topics/Self-Driving-Car-Foundations.md | 29 - .../Self-Play (자기 대결 기반 강화학습).md | 28 - .../Topics/Self-Supervised Learning (SSL).md | 35 - 10_Wiki/Topics/Self-Supervised-Learning.md | 28 - .../Topics/Semantic Grounding & Provenance.md | 33 - 10_Wiki/Topics/Semantic-HTML-Foundations.md | 33 - 10_Wiki/Topics/Semantic-Search-with-AI.md | 28 - 10_Wiki/Topics/Semantic-Search.md | 28 - 10_Wiki/Topics/Semantics & Ontology.md | 34 - 10_Wiki/Topics/Semgrep Assistant.md | 41 - 10_Wiki/Topics/Sensitivity-Analysis.md | 31 - 10_Wiki/Topics/Sensor-Fusion.md | 28 - 10_Wiki/Topics/Sentiment-Analysis-Models.md | 29 - 10_Wiki/Topics/Sentiment-Analysis.md | 36 - 10_Wiki/Topics/Separation_of_Concerns.md | 25 - 10_Wiki/Topics/Sequence-Modeling.md | 32 - 10_Wiki/Topics/Sequence-to-Sequence-Models.md | 28 - 10_Wiki/Topics/Serverless-Computing-for-AI.md | 31 - .../Topics/Service-oriented-Architecture.md | 29 - 10_Wiki/Topics/Shadowing-and-Observability.md | 30 - 10_Wiki/Topics/Shape-Feature-Extraction.md | 28 - 10_Wiki/Topics/Sharding-and-Partitioning.md | 28 - 10_Wiki/Topics/Shift.md | 31 - 10_Wiki/Topics/Signal in Noise.md | 35 - .../Topics/Signal-Processing-Foundations.md | 29 - 10_Wiki/Topics/Signature Style Design.md | 12 +- 10_Wiki/Topics/Similarity-Metrics-in-AI.md | 29 - 10_Wiki/Topics/Similarity-Metrics.md | 36 - 10_Wiki/Topics/Simulated-Annealing.md | 28 - 10_Wiki/Topics/Simulation-Environments.md | 28 - .../Simulator Sickness Questionnaire (SSQ).md | 36 - 10_Wiki/Topics/Single_Source_of_Truth.md | 24 - .../Topics/Singular-Value-Decomposition.md | 28 - 10_Wiki/Topics/Six-Sigma-Methodologies.md | 30 - 10_Wiki/Topics/Skybound Protocol 코드리뷰.md | 37 - .../2026-04-23_Engine_Stabilization_Report.md | 4 +- ...ombat_System_Reference_Error_Resolution.md | 6 +- ...me-Engine-Loop-and-System-Orchestration.md | 8 +- .../Git_Synchronization_Protocol.md | 6 +- .../Topics/Skybound/01_Core_Engine/Index.md | 12 +- .../Skybound-Modular-Game-Architecture.md | 12 +- .../Skybound_Implementation_Report_V10_5.md | 8 +- ...-Injection-and-Visual-Renderer-Pipeline.md | 4 +- ...ate-Machine-and-Phase-Transition-Events.md | 12 +- .../Visual_Feedback_Signal_Pattern.md | 4 +- ...-System-and-Bullet-Interaction-Pipeline.md | 14 +- 10_Wiki/Topics/Skybound/02_Combat_AI/Index.md | 6 +- ...tage-Director-and-World-Tension-Scaling.md | 10 +- ...Staggered-Firing-Logic-and-Phase-Offset.md | 12 +- .../Boss-AI-Contextual-Decision-Engine.md | 10 +- ...ss-Orchestration-and-Gimmick-Management.md | 8 +- .../Boss_Battle_Design_System.md | 8 +- .../Boss_Combat_Stability_Fix_Log.md | 10 +- .../Boss_Encounter_and_Timeline_Design.md | 6 +- .../Topics/Skybound/03_Boss_Systems/Index.md | 6 +- .../Campaign_and_Dual_Loop_System.md | 16 +- .../Combat_Timeline_Difficulty_Scaling.md | 6 +- ...Equipment-Crafting-and-Synthesis-Engine.md | 4 +- .../Equipment_Crafting_and_Synthesis_Full.md | 8 +- .../InGame_Progression_System.md | 6 +- .../04_Mechanics_Progression/Index.md | 18 +- .../Meta-Progression-and-Economy-Systems.md | 4 +- ...odular-Weapon-Evolution-and-Skill-Trees.md | 6 +- .../Tactical-Air-Drop-and-Supply-Logistics.md | 4 +- .../UX_Gameplay_Protocol_V10_0.md | 8 +- ...04-21-Engine-Stability-and-Optimization.md | 2 +- ...-Implementation-and-Architecture-Report.md | 4 +- ...ect-Report-V11.5-Combat-and-UI-Recovery.md | 8 +- ...2026-04-21-UX-Dopamine-Feedback-Upgrade.md | 2 +- ...04-21_Stability_and_Optimization_Report.md | 10 +- ...-04-22_Engine_Logic_Optimization_Report.md | 8 +- .../2026-04-22_Engine_Stability_Audit.md | 12 +- .../2026-04-23_Post-Mortem_Loot_Rebalance.md | 2 +- .../Skybound/05_Project_Issues/Index.md | 14 +- ...-Combat-Reference-Error-Troubleshooting.md | 8 +- ..._Structure_Audit_and_Stabilization_Plan.md | 36 +- ...al_Stylized_Casual_Magitech_Redirection.md | 12 +- ...AC_LevelUp_Stylized_Casual_Magitech_Fix.md | 8 +- ...Skybound_Nova_Burst_Icon_and_Effect_Fix.md | 6 +- ...und_Particle_and_Supply_Readability_Fix.md | 6 +- ...irealistic_Magitech_Fantasy_Redirection.md | 6 +- ...bound_Stylized_Casual_Magitech_Art_Pack.md | 14 +- ...ylized_Casual_Magitech_Ingame_Asset_Fix.md | 6 +- ...ybound_Survivor_Like_Balance_Curve_Pass.md | 10 +- ...re_Gameplay_Rebalance_and_Purpose_Reset.md | 14 +- ...frame_and_8Stage_Boss_Continuity_Rework.md | 2 +- ...l_Concept_and_Hangar_Layout_Overlap_Fix.md | 6 +- ...p_DirectKill_and_UI_Productization_Pass.md | 4 +- ...vivors_Loop_and_Stage_Curve_Preparation.md | 2 +- ...age_Pressure_and_Projectile_Visual_Pass.md | 2 +- ...nd_HP_Scarcity_and_Module_Cache_Rewards.md | 2 +- ...nvasion_Response_Stage_Difficulty_Curve.md | 2 +- ...und_Miniboss_Treasure_Cache_Reward_Loop.md | 2 +- ...Skybound_Player_Sprite_Path_Warning_Fix.md | 2 +- ...eward_Card_Clarity_and_Command_Cache_UI.md | 2 +- ...de_and_Weapon_Transform_Reconfiguration.md | 2 +- ..._Balance_Bomb_and_Visual_Diversity_Pass.md | 2 +- ..._Stage_Miniboss_Pattern_Differentiation.md | 6 +- ... 3월 연구 드롭(March 2026 Research Drop).md | 16 +- ... 연구 업데이트(March 2026 Research Drop).md | 14 +- ...년 연구 업데이트(March 2026 Research Drop).md | 18 +- .../Skybound/Boss_Battle_Design_System.md | 4 +- 10_Wiki/Topics/Skybound/Flak Tank.md | 8 +- 10_Wiki/Topics/Skybound/Index.md | 114 +- .../Skybound/March 2026 Research Drop.md | 12 +- ...연구 업데이트(March 2026 Research Drop).md | 14 +- .../Topics/Skybound/Operation- Western Sun.md | 10 +- .../Skybound/Sector Breach August 2025.md | 12 +- .../Topics/Skybound/Sector Breach 이벤트.md | 8 +- .../Topics/Skybound/Skybound-Knowledge-Hub.md | 182 +- .../Skybound_Asset_Generation_Roadmap.md | 4 +- .../Skybound/Skybound_Asset_Purity_Sync.md | 2 +- .../Skybound_Defensive_Architecture_Reboot.md | 12 +- .../Skybound_Enemy_Orientation_Fix.md | 4 +- .../Skybound_Firepower_Overclock_v1.5.md | 2 +- .../Skybound_Skill_Asset_Integration.md | 4 +- .../Skybound_Skill_Image_Integration.md | 6 +- ...ybound_Weapon_Behavior_Engine_Migration.md | 4 +- .../War Commander AI and UI Enhancements.md | 16 +- .../Skybound/War Commander → 전투 시스템.md | 12 +- ... 전투 시스템 진화 (2014년 2월 업데이트).md | 12 +- .../War Commander 전투 전술 및 방어 메타.md | 20 +- ... 전투(Sector Warfare and Elite Event Operations).md | 12 +- ...놀로지 및 유닛(Arc 2 Technology and Units).md | 12 +- ... 및 토륨 경제(Iridium and Thorium Economy).md | 16 +- .../Skybound/토륨 경제(Thorium Economy).md | 8 +- 10_Wiki/Topics/Slack-Bot-Development.md | 29 - 10_Wiki/Topics/Smart-Contract-Auditing.md | 29 - 10_Wiki/Topics/Snowflake-Data-Warehousing.md | 28 - ...r Labs 등 종합 애플리케이션 보안 플랫폼.md | 33 - 10_Wiki/Topics/Social Systems Theory.md | 34 - 10_Wiki/Topics/Social-Network-Analysis.md | 29 - 10_Wiki/Topics/Sociology of Knowledge.md | 33 - 10_Wiki/Topics/Soft Navigation.md | 32 - 10_Wiki/Topics/Soft-Skills-Development.md | 34 - .../API-Contract-Definition.md | 6 +- .../API-First Architecture.md | 8 +- ...iving Simulation] [Robotic Manipulation.md | 12 +- .../Architectural-Constraint-Enforcement.md | 6 +- .../Domain-Driven Design (DDD).md | 6 +- 10_Wiki/Topics/Software Architecture/Index.md | 12 +- .../Microservices-Architecture.md | 14 +- .../Amazon-AWS-Formal-Verification.md | 6 +- 10_Wiki/Topics/Software Reliability/Index.md | 2 +- .../Topics/Software-Architecture-Patterns.md | 30 - 10_Wiki/Topics/Software-Design-Principles.md | 38 - 10_Wiki/Topics/Solitude-Optimization.md | 35 - 10_Wiki/Topics/Solow Growth Model.md | 33 - 10_Wiki/Topics/Solution.md | 31 - 10_Wiki/Topics/SonarQube.md | 33 - 10_Wiki/Topics/Sorting.md | 30 - 10_Wiki/Topics/Sound Design Principles.md | 36 - 10_Wiki/Topics/Source-Control.md | 31 - 10_Wiki/Topics/Space-based-Architecture.md | 28 - 10_Wiki/Topics/Sparse-Data-Handling.md | 29 - 10_Wiki/Topics/Spatial-Data-Analysis.md | 29 - 10_Wiki/Topics/Specification.md | 31 - 10_Wiki/Topics/Spectral-Clustering.md | 32 - 10_Wiki/Topics/Speculative-Design.md | 33 - .../Topics/Speech-Recognition-Foundations.md | 28 - 10_Wiki/Topics/Speech-Synthesis.md | 35 - .../Topics/Spiking-Neural-Networks-SNNs.md | 28 - 10_Wiki/Topics/Stability vs Flexibility.md | 36 - .../Stable Diffusion Image Optimization.md | 12 +- 10_Wiki/Topics/Stable Diffusion Weights.md | 12 +- .../Topics/Stable Diffusion 오픈소스 제어.md | 14 +- .../Stable Diffusion의 가중치 제어 문법.md | 12 +- 10_Wiki/Topics/Stacked-Generalization.md | 28 - 10_Wiki/Topics/Stages-of-Grief.md | 33 - 10_Wiki/Topics/Stakeholder.md | 31 - .../Topics/Standard-Deviation-and-Variance.md | 28 - .../Topics/Standard-Operating-Procedure.md | 31 - .../Topics/Standardization vs Innovation.md | 33 - 10_Wiki/Topics/Startup.md | 31 - 10_Wiki/Topics/State Space Model (SSM).md | 35 - ...e-Management-Architecture-and-Ownership.md | 29 - 10_Wiki/Topics/State-Management-Patterns.md | 29 - 10_Wiki/Topics/State-Space-Models.md | 28 - 10_Wiki/Topics/State-Space.md | 30 - 10_Wiki/Topics/State.md | 31 - .../Static-Site-Generation-with-Gatsby.md | 29 - 10_Wiki/Topics/Statistical-Analysis.md | 31 - .../Topics/Statistical-Hypothesis-Testing.md | 29 - 10_Wiki/Topics/Statistical-Learning-Theory.md | 28 - 10_Wiki/Topics/Statistical-Power.md | 29 - 10_Wiki/Topics/Statistics & Data Analysis.md | 33 - 10_Wiki/Topics/Statistics.md | 31 - 10_Wiki/Topics/Steel Division 시리즈.md | 34 - 10_Wiki/Topics/Stem-Analysis.md | 32 - .../Topics/Stochastic-Gradient-Descent-SGD.md | 28 - 10_Wiki/Topics/Stochastic-Gradient-Descent.md | 28 - 10_Wiki/Topics/Storage-Area-Networks.md | 28 - 10_Wiki/Topics/Storage.md | 31 - 10_Wiki/Topics/Straightening.md | 34 - 10_Wiki/Topics/Strategic-Alignment.md | 29 - 10_Wiki/Topics/Strategic-Ambiguity.md | 35 - 10_Wiki/Topics/Strategic-Planning-for-AI.md | 29 - 10_Wiki/Topics/Strategic-Planning.md | 31 - 10_Wiki/Topics/Strategic-Thinking.md | 28 - 10_Wiki/Topics/Strategy.md | 31 - .../Topics/Stream-Processing-Architectures.md | 28 - 10_Wiki/Topics/Structural Principles.md | 35 - .../Topics/Structural-Equation-Modeling.md | 27 - 10_Wiki/Topics/Structuralism.md | 32 - 10_Wiki/Topics/Style Reference (--sref).md | 12 +- 10_Wiki/Topics/Style-Transfer-in-AI.md | 29 - 10_Wiki/Topics/Style-Transfer.md | 35 - 10_Wiki/Topics/Styling_Governance.md | 27 - 10_Wiki/Topics/Superficiality-Metrics.md | 34 - 10_Wiki/Topics/Supervised-Learning.md | 32 - 10_Wiki/Topics/Supply-Chain.md | 31 - 10_Wiki/Topics/Support-Vector-Machines.md | 28 - 10_Wiki/Topics/Support.md | 31 - 10_Wiki/Topics/Sustainability.md | 31 - 10_Wiki/Topics/Swarm Intelligence.md | 35 - 10_Wiki/Topics/Swarm-Intelligence.md | 31 - .../Topics/Symbolic-AI vs Connectionism.md | 28 - 10_Wiki/Topics/Symbols.md | 31 - 10_Wiki/Topics/Symmetric-Encryption.md | 28 - 10_Wiki/Topics/Symmetry-and-Invariance.md | 34 - 10_Wiki/Topics/Synergy.md | 31 - 10_Wiki/Topics/Synthesized Intelligence.md | 35 - 10_Wiki/Topics/Synthetic-Data-Generation.md | 28 - 10_Wiki/Topics/Synthetic-Data.md | 31 - .../Distributed-Systems-Engineering.md | 14 +- .../Index.md | 2 +- .../Digital Twins.md | 18 +- .../System Architecture & Simulation/Index.md | 2 +- .../System Design & Modeling/Agent Harness.md | 20 +- .../C-component (Context Manager).md | 8 +- .../E-component (Execution Loop).md | 8 +- .../Event Storming.md | 14 +- .../Topics/System Design & Modeling/Index.md | 2 +- .../L-component (Lifecycle Hooks).md | 8 +- .../S-component (State Store).md | 8 +- .../T-component (Tool Registry).md | 8 +- .../V-component (Evaluation Interface).md | 8 +- .../Topics/System Prompt (시스템 프롬프트).md | 26 - 10_Wiki/Topics/System-Architecture-Design.md | 29 - 10_Wiki/Topics/System-Design for AI Scale.md | 28 - .../Topics/System-Design-Interview-Prep.md | 29 - 10_Wiki/Topics/System-Dynamics-Modeling.md | 29 - 10_Wiki/Topics/System-Theory.md | 31 - 10_Wiki/Topics/System_Debugging_Protocol.md | 27 - 10_Wiki/Topics/System_Protocol_Standard.md | 26 - .../Game Design Theory.md | 14 +- .../Topics/Systemic Modeling & Fun/Index.md | 2 +- .../Topics/Systemic_Simulation_Principles.md | 24 - 10_Wiki/Topics/Systems Thinking.md | 37 - 10_Wiki/Topics/Systems-Thinking.md | 32 - 10_Wiki/Topics/TDD.md | 31 - 10_Wiki/Topics/TS-Declaration-Files.md | 31 - 10_Wiki/Topics/Tableau-Data-Visualization.md | 29 - 10_Wiki/Topics/Target-Function-Profiling.md | 35 - 10_Wiki/Topics/Task-Management.md | 31 - 10_Wiki/Topics/Technical-Architecture.md | 31 - 10_Wiki/Topics/Technical-Debt.md | 34 - .../Topics/Temporal-Difference-Learning.md | 28 - 10_Wiki/Topics/TensorFlow-Foundations.md | 30 - ...rm-Frequency-Inverse-Document-Frequency.md | 27 - 10_Wiki/Topics/Terminology.md | 31 - .../Terraform-Infrastructure-as-Code.md | 29 - ...mpute Scaling (추론 시간 계산 스케일링).md | 28 - 10_Wiki/Topics/Testing.md | 31 - .../Topics/Tetris_Project_Retrospective.md | 30 - 10_Wiki/Topics/Text-Mining.md | 31 - 10_Wiki/Topics/Text-to-Speech-Synthesis.md | 29 - .../The Evolution of Music Distribution.md | 34 - .../Topics/Theoretical-Computer-Science.md | 29 - 10_Wiki/Topics/Theory of Constraints (TOC).md | 37 - 10_Wiki/Topics/Theory-of-Mind (ToM) in AI.md | 29 - 10_Wiki/Topics/Thought-Architecture.md | 35 - 10_Wiki/Topics/Threejs WebGL 렌더링 최적화.md | 47 - 10_Wiki/Topics/Threejs WebGPURenderer.md | 37 - 10_Wiki/Topics/Threejs 성능 최적화.md | 49 - 10_Wiki/Topics/Time-Series-Analysis.md | 36 - 10_Wiki/Topics/Time-Step-Logic-in-Games.md | 28 - 10_Wiki/Topics/Tokenization-Strategies.md | 28 - 10_Wiki/Topics/Tool-Usage-Optimization.md | 34 - .../Topics/Toxicity-and-Bias-Mitigation.md | 34 - 10_Wiki/Topics/Transfer Learning.md | 34 - .../Transfer-Learning (전이 학습 기초).md | 28 - 10_Wiki/Topics/Transformer-Architecture.md | 28 - 10_Wiki/Topics/Transformers.md | 34 - 10_Wiki/Topics/Trustworthy-AI.md | 31 - 10_Wiki/Topics/Turing Test.md | 32 - 10_Wiki/Topics/Turing-Machine Foundations.md | 29 - 10_Wiki/Topics/Type 1 vs Type 2 Errors.md | 33 - 10_Wiki/Topics/TypeScript_Type_Safety.md | 26 - 10_Wiki/Topics/UX-Design-Principles.md | 30 - 10_Wiki/Topics/Uber-Base-Web-Design-System.md | 29 - 10_Wiki/Topics/Ultra-Efficiency.md | 32 - 10_Wiki/Topics/Uncertainty-Quantification.md | 30 - 10_Wiki/Topics/Unconscious Structuralism.md | 31 - .../Topics/Understanding Complex Systems.md | 33 - .../Topics/Universal Basic Income (UBI).md | 35 - .../Topics/Universal-Approximation-Theorem.md | 27 - 10_Wiki/Topics/Universal-Grammar.md | 33 - ...nsupervised-Learning (비지도 학습 기초).md | 29 - 10_Wiki/Topics/V7 Draft Mode Workflow.md | 14 +- .../Topics/Variational Autoencoders (VAE).md | 33 - .../Topics/Variational-Autoencoders-VAE.md | 28 - 10_Wiki/Topics/Vary Region (인페인팅).md | 12 +- 10_Wiki/Topics/Vector-Database Selection.md | 32 - 10_Wiki/Topics/Victimhood-Narratives.md | 32 - .../Viral-Dynamics-and-Network-Effects.md | 33 - 10_Wiki/Topics/Visual-Effects-VFX-in-Games.md | 28 - 10_Wiki/Topics/Visual-Effects-VFX.md | 34 - 10_Wiki/Topics/Vocabulary-Expansion.md | 33 - .../Topics/Voice-Assistant-Architecture.md | 29 - .../WARNO 그래픽 엔진 업그레이드 프로젝트.md | 25 - 10_Wiki/Topics/WARNO 데이터 기반 밸런싱.md | 24 - 10_Wiki/Topics/WARNO 데이터 기반 설계.md | 32 - ...멀티플레이어 및 경쟁 플레이 밸런스 패치.md | 31 - 10_Wiki/Topics/WARNO 모딩(Modding).md | 34 - 10_Wiki/Topics/WARNO 모딩.md | 24 - 10_Wiki/Topics/WARNO 밸런싱 및 사단 시스템.md | 24 - ...ARNO 사후 관리 (Post-Launch Management).md | 24 - ...(Real-time Tactics) 및 Army General 캠페인.md | 31 - .../Topics/WARNO 전술 시뮬레이션 시스템.md | 34 - .../WARNO 전투 메커니즘 (Combat Mechanics).md | 28 - .../WARNO 커뮤니티 데이터 도구 생태계.md | 24 - 10_Wiki/Topics/WARNO 커뮤니티 모딩 생태계.md | 25 - 10_Wiki/Topics/WARNO-DATA Wiki.md | 23 - 10_Wiki/Topics/WARNO-DATA 프로젝트.md | 24 - 10_Wiki/Topics/WARNO.md | 27 - 10_Wiki/Topics/WME (Warno Mod Editor).md | 23 - ...arno-Armory (커뮤니티 데이터 분석 도구).md | 31 - .../Topics/War-Yes 및 Warno-Armory 도구.md | 24 - 10_Wiki/Topics/Wargame 시리즈.md | 23 - 10_Wiki/Topics/Warno 데이터 기반 설계.md | 31 - 10_Wiki/Topics/Warno-Armory.md | 24 - .../Analyze runtime performance.md | 16 +- 10_Wiki/Topics/Web & Performance/Index.md | 2 +- .../Topics/Web Performance Optimization.md | 47 - .../Web-Rendering-Strategies-CSR-vs-SSR.md | 29 - 10_Wiki/Topics/Web3-and-AI-Integration.md | 28 - .../WebSplatter (3D Gaussian Splatting).md | 40 - 10_Wiki/Topics/WebWorker_Performance.md | 24 - 10_Wiki/Topics/What-is-AI.md | 34 - 10_Wiki/Topics/Wicked-Problems.md | 36 - 10_Wiki/Topics/Word-Representation.md | 34 - 10_Wiki/Topics/Work-Displacement.md | 33 - 10_Wiki/Topics/Workflow-Integrity.md | 32 - 10_Wiki/Topics/Working-Backwards.md | 34 - 10_Wiki/Topics/Zen-Pop.md | 28 - .../Topics/Zero Shot and Few Shot Learning.md | 34 - 10_Wiki/Topics/Zero-Shot-Chain-of-Thought.md | 33 - 10_Wiki/Topics/Zero-Shot-Learning.md | 28 - 10_Wiki/Topics/_agents/business/goal.md | 15 - 10_Wiki/Topics/_agents/business/memory.md | 4 +- 10_Wiki/Topics/_agents/business/prompt.md | 5 - 10_Wiki/Topics/_agents/ceo/prompt.md | 5 - 10_Wiki/Topics/_agents/designer/goal.md | 15 - 10_Wiki/Topics/_agents/designer/memory.md | 5 - 10_Wiki/Topics/_agents/designer/prompt.md | 5 - 10_Wiki/Topics/_agents/developer/goal.md | 16 - 10_Wiki/Topics/_agents/developer/prompt.md | 5 - 10_Wiki/Topics/_agents/editor/goal.md | 15 - 10_Wiki/Topics/_agents/editor/memory.md | 5 - 10_Wiki/Topics/_agents/editor/prompt.md | 5 - 10_Wiki/Topics/_agents/instagram/goal.md | 15 - 10_Wiki/Topics/_agents/instagram/memory.md | 5 - 10_Wiki/Topics/_agents/instagram/prompt.md | 5 - 10_Wiki/Topics/_agents/researcher/goal.md | 15 - 10_Wiki/Topics/_agents/researcher/memory.md | 6 +- 10_Wiki/Topics/_agents/researcher/prompt.md | 5 - 10_Wiki/Topics/_agents/secretary/goal.md | 15 - 10_Wiki/Topics/_agents/secretary/memory.md | 8 - 10_Wiki/Topics/_agents/secretary/prompt.md | 5 - 10_Wiki/Topics/_agents/writer/goal.md | 15 - 10_Wiki/Topics/_agents/writer/memory.md | 5 - 10_Wiki/Topics/_agents/writer/prompt.md | 5 - 10_Wiki/Topics/_agents/youtube/goal.md | 14 +- 10_Wiki/Topics/_agents/youtube/memory.md | 5 - 10_Wiki/Topics/_agents/youtube/prompt.md | 5 - .../_agents/youtube/tools/auto_planner.md | 2 +- .../youtube/tools/comment_harvester.md | 4 +- .../_agents/youtube/tools/competitor_brief.md | 20 - .../_agents/youtube/tools/my_videos_check.md | 2 +- .../_agents/youtube/tools/telegram_notify.md | 2 +- .../_agents/youtube/tools/trend_sniper.md | 21 - 10_Wiki/Topics/_shared/_system.md | 16 +- 10_Wiki/Topics/_shared/goals.md | 12 - 10_Wiki/Topics/_shared/identity.md | 10 - ...리_ - 관심사의 분리 (Separation of Concerns).md | 28 - .../Topics/agargaro의 오픈 소스 라이브러리.md | 44 - 10_Wiki/Topics/clinicjs.md | 33 - .../sessions/2026-04-30T07-07/_brief.md | 8 +- .../sessions/2026-04-30T07-07/business.md | 3 - .../sessions/2026-04-30T07-07/researcher.md | 3 - .../sessions/2026-04-30T07-07/secretary.md | 3 - .../sessions/2026-05-01T08-07/_brief.md | 11 - .../sessions/2026-05-01T08-07/_report.md | 14 - .../sessions/2026-05-01T08-07/secretary.md | 3 - .../sessions/2026-05-01T08-57/_brief.md | 10 - .../sessions/2026-05-01T10-17/_brief.md | 10 - .../sessions/2026-05-01T11-39/_brief.md | 10 - .../sessions/2026-05-01T11-39/_report.md | 13 - 10_Wiki/Topics/stochastic gradient descent.md | 35 - 10_Wiki/Topics/가용성 (Availability).md | 24 - ...위보 상성 (Rock-paper-scissors principle).md | 23 - .../공급망 공격 (Supply Chain Attack).md | 40 - ...비스 아키텍처 (Microservices Architecture).md | 46 - ...딩 커뮤니티 도구 (War-Yes, Warno-Armory).md | 24 - 10_Wiki/Topics/무제 1.canvas | 1 + ... V7 드래프트 모드 및 옴니 참조 워크플로우.md | 14 +- ... V7 및 V8 알파 (Midjourney V7 & V8.1 Alpha).md | 12 +- .../미드저니 V7 및 V8.1 Alpha 워크플로우.md | 18 +- ...미드저니 V7 및 드래프트 모드 워크플로우.md | 12 +- ...프트 일관성 유지 (Midjourney V7 Consistency).md | 16 +- ...저니 및 스테이블 디퓨전의 부분 편집 기법.md | 14 +- .../미드저니(Midjourney) 에디터 기능.md | 12 +- .../버전 및 모델 (Versions and Models).md | 14 +- .../베이지안 추론 (Bayesian Inference).md | 4 +- .../벡터 데이터베이스 (Vector Database).md | 29 - 10_Wiki/Topics/보존 경로(Retaining Path).md | 33 - ... 활용한 시각적 아티팩트(Artifact) 디버깅 및 제어.md | 12 +- .../Topics/사단 시스템 (Division System).md | 24 - 10_Wiki/Topics/사단 편제표 (TO&E).md | 24 - 10_Wiki/Topics/사단(Division) 시스템.md | 24 - 10_Wiki/Topics/사후 편집 (Post-editing).md | 10 +- ...Commercial Marketing Campaign and Product Mockup Creation).md | 10 +- ...업용 브랜드 이미지 및 디자인 시스템 구축.md | 10 +- .../상업용 제품 사진 및 브랜드 로고 디자인.md | 10 +- .../Topics/상호작용적 프롬프트 엔지니어링.md | 14 +- .../Topics/샘플링 스텝 (Sampling Steps).md | 14 +- ...셜 미디어 그래픽 및 마케팅 캠페인 제작.md | 10 +- 10_Wiki/Topics/소음 역학 (Noise Dynamics).md | 24 - .../순환 신경망 및 LSTM (RNN & LSTM).md | 4 +- ...릭터 참조 (Style and Character References).md | 4 +- 10_Wiki/Topics/스타일 코드.md | 10 +- ...테이블 디퓨전 CFG Scale 및 가중치 제어.md | 16 +- ...스테이블 디퓨전의 가중치 및 제어 시스템.md | 14 +- ...샷 워크플로우 (Series and Multi-shot Workflow).md | 12 +- .../Topics/신경망 기초 (Neural Networks).md | 4 +- ...지 최적화 (Stable Diffusion Image Optimization).md | 14 +- 10_Wiki/Topics/에이전틱 AI (Agentic AI).md | 10 +- .../오픈소스 이미지 모델 미세 조정 및 배포.md | 12 +- ...신과 시야 매커니즘 (Stealth and Optics).md | 30 - .../Topics/인-이미지 텍스트(In-Image Text).md | 14 +- ... 및 사후 편집 (Inpainting & Post-Editing).md | 4 +- ...연어 프롬프트(Natural Language Prompt).md | 10 +- ... 관통 모델링(Armor Penetration Modeling).md | 28 - ... 및 사거리 데이터 (Armor and Range Stats).md | 24 - .../정적 애플리케이션 보안 테스트 (SAST).md | 29 - .../Topics/제병협동 전술 (Combined Arms).md | 29 - ... 사양 지시(Lighting and Camera Specification).md | 14 +- .../Topics/지도 학습 (Supervised Learning).md | 4 +- .../초상화 및 애니메이션 스타일 제어.md | 12 +- 10_Wiki/Topics/컨트롤넷 (ControlNet).md | 4 +- ... 알고리즘 (Ballistics and Accuracy Algorithms).md | 33 - .../Topics/텍스트 렌더링(Text Rendering).md | 10 +- .../파라미터 튜닝 (Parameter Tuning).md | 12 +- 10_Wiki/Topics/풀 리퀘스트 (Pull Request).md | 4 +- .../프롬프트 가중치 (Prompt Weighting).md | 4 +- .../Topics/프롬프트 구문 (Prompt Syntax).md | 12 +- ... 구조 및 문법 (Prompt Structure & Syntax).md | 4 +- ...롬프트 엔지니어링 (Prompt Engineering).md | 4 +- .../프롬프트 정밀도 (Prompt Precision).md | 10 +- ... 파라미터 제어 (Prompt Parameter Control).md | 12 +- .../Topics/프롬프트 확장(Prompt Expansion).md | 10 +- .../Topics/해부학적 오류 디버깅 워크플로우.md | 12 +- .../Topics/확산 모델 (Diffusion Models).md | 4 +- ...어 생성 패러다임 전환 및 연속적 창작 워크플로우.md | 6 +- .../A-B-Testing-and-Data-Driven-UX.md | 2 +- .../A2A (Agent-to-Agent Protocol).md | 14 +- 10_Wiki/Topics_Art/A2A.md | 10 +- .../ACP (Agent Communication Protocol).md | 10 +- 10_Wiki/Topics_Art/AGI.md | 2 +- 10_Wiki/Topics_Art/AI Connect LLM Tool.md | 2 +- .../AI Image Generation Workflow.md | 6 +- 10_Wiki/Topics_Art/AI Safety.md | 4 +- ...델 사후 편집 도구 (Post-editing Tools).md | 6 +- .../AI 이미지 생성 (AI Image Generation).md | 6 +- .../AI 이미지 생성 도구 및 매개변수.md | 4 +- ...플로우 (AI Image Generation & Editing Workflow).md | 6 +- ... 워크플로우 (AI Image Generation Workflow).md | 6 +- .../Topics_Art/AI 이미지 생성 파이프라인.md | 6 +- ... 디버깅 (Image Quality Optimization & Debugging).md | 6 +- 10_Wiki/Topics_Art/AI-Overviews-and-SGE.md | 2 +- .../AI-Personalization-and-Adaptive-UX.md | 2 +- ... 모델링 및 상태 머신(State Machine) 설계.md | 4 +- .../Topics_Art/API-Design for AI Services.md | 2 +- .../API-backed Image Generation Workflow.md | 6 +- .../Topics_Art/API_Communication_Patterns.md | 6 +- .../Accessibility-Compliance-Audit.md | 4 +- .../Topics_Art/Accessibility_Inclusivity.md | 6 +- 10_Wiki/Topics_Art/Ad-hoc-Optimization.md | 4 +- .../Adaptive Compute (적응형 계산량 조절).md | 12 +- .../Topics_Art/Adaptive Context Compaction.md | 8 +- 10_Wiki/Topics_Art/Adaptive-Curation.md | 6 +- .../Topics_Art/Advanced-Interface-Design.md | 4 +- 10_Wiki/Topics_Art/Aesthetic-Value.md | 4 +- 10_Wiki/Topics_Art/Aesthetics/.gitkeep | 0 10_Wiki/Topics_Art/Affordance.md | 4 +- 10_Wiki/Topics_Art/Agent Architecture.md | 4 +- 10_Wiki/Topics_Art/Agent Harness.md | 20 +- 10_Wiki/Topics_Art/Agent Memory System.md | 8 +- 10_Wiki/Topics_Art/Agentic AI Security.md | 14 +- 10_Wiki/Topics_Art/Agentic Creative Era.md | 6 +- 10_Wiki/Topics_Art/Agentic Creative.md | 6 +- 10_Wiki/Topics_Art/Agentic Orchestration.md | 12 +- 10_Wiki/Topics_Art/Agile-Philosophy.md | 4 +- .../Topics_Art/Algorithm-Complexity-Big-O.md | 2 +- 10_Wiki/Topics_Art/Algorithmic Fairness.md | 4 +- 10_Wiki/Topics_Art/Algorithmic-Game-Theory.md | 4 +- 10_Wiki/Topics_Art/Altruism.md | 4 +- 10_Wiki/Topics_Art/Ambient-Declarations.md | 6 +- 10_Wiki/Topics_Art/Analogy.md | 4 +- 10_Wiki/Topics_Art/Anarchism.md | 4 +- 10_Wiki/Topics_Art/Anisomorphism.md | 4 +- 10_Wiki/Topics_Art/Anthropomorphism.md | 4 +- 10_Wiki/Topics_Art/Antifragility.md | 4 +- .../Topics_Art/Arguing-by-Counterexample.md | 4 +- .../Topics_Art/Arrangement-and-Composition.md | 4 +- 10_Wiki/Topics_Art/Articulateness.md | 4 +- .../Topics_Art/Artifacts & Infrastructure.md | 8 +- .../Artificial General Intelligence (AGI).md | 4 +- .../Artificial Intelligence (AI).md | 4 +- .../Artificial-Intelligence-in-Games.md | 6 +- 10_Wiki/Topics_Art/Artificial-Intelligence.md | 2 +- 10_Wiki/Topics_Art/Artificial-Life.md | 2 +- 10_Wiki/Topics_Art/Arts.md | 4 +- .../Topics_Art/Asset-Specific-Knowledge.md | 4 +- 10_Wiki/Topics_Art/Atheism.md | 4 +- .../Topics_Art/Atmospheric-Intelligence.md | 4 +- .../Atomic-Design-System-Architecture.md | 2 +- .../Atomic-Styling-and-Design-Systems.md | 2 +- ...sm Spectrum Disorder (ASD) Intervention.md | 2 +- .../Topics_Art/Automated-Map-Generation.md | 6 +- 10_Wiki/Topics_Art/Backend.md | 4 +- 10_Wiki/Topics_Art/Behavioral Finance.md | 4 +- 10_Wiki/Topics_Art/Behavioral-Incentives.md | 4 +- 10_Wiki/Topics_Art/Benchmarks.md | 4 +- 10_Wiki/Topics_Art/Best SAST Tools in 2026.md | 4 +- 10_Wiki/Topics_Art/Bible.md | 4 +- 10_Wiki/Topics_Art/BioShock (2007).md | 4 +- 10_Wiki/Topics_Art/BioShock-Critique.md | 6 +- 10_Wiki/Topics_Art/Blocking.md | 4 +- 10_Wiki/Topics_Art/Bottom-Up-Approach.md | 4 +- 10_Wiki/Topics_Art/Bounded Contexts.md | 4 +- 10_Wiki/Topics_Art/Bourgeoisie.md | 4 +- .../Brand Consistency Maintenance.md | 6 +- 10_Wiki/Topics_Art/Browser.md | 4 +- .../Topics_Art/Business Intelligence (BI).md | 4 +- .../C-component (Context Manager).md | 8 +- 10_Wiki/Topics_Art/CAP-Theorem.md | 2 +- 10_Wiki/Topics_Art/CFG Scale.md | 6 +- 10_Wiki/Topics_Art/CFG 스케일 (CFG Scale).md | 6 +- ... 스케일(Classifier-Free Guidance Scale).md | 6 +- .../CI_CD 파이프라인 및 IDE 통합 보안.md | 4 +- 10_Wiki/Topics_Art/CLIP.md | 2 +- 10_Wiki/Topics_Art/CPTED.md | 4 +- 10_Wiki/Topics_Art/CV_Synthesis.md | 4 +- .../Case-Study-Allbirds-PWA-Redesign.md | 2 +- .../Case-Study-Kiwi-com-Frontend-Migration.md | 2 +- ...Case-Study-Skybound-Asset-Cache-Busting.md | 2 +- 10_Wiki/Topics_Art/CesiumJS.md | 4 +- 10_Wiki/Topics_Art/Chaos-Theory in Systems.md | 2 +- 10_Wiki/Topics_Art/Character Consistency.md | 6 +- 10_Wiki/Topics_Art/Character Reference.md | 6 +- .../ChatGPT 통합 (ChatGPT Integration).md | 6 +- ...기반 텍스트 투 이미지(Text-to-Image) 생성.md | 6 +- .../Chrome-Rendering-Performance.md | 4 +- .../Circuit Discovery (회로 발견).md | 4 +- 10_Wiki/Topics_Art/Circuit Discovery.md | 2 +- .../Circular-Economy-Transitions.md | 4 +- 10_Wiki/Topics_Art/Circular-Economy.md | 4 +- .../Clean-Architecture-Implementation.md | 6 +- .../Clean-Architecture-TypeScript.md | 4 +- ...g-and-Frontend-Performance-Optimization.md | 2 +- .../Topics_Art/Cognitive-Evaluation-Theory.md | 4 +- 10_Wiki/Topics_Art/Collaborative-Filtering.md | 2 +- .../Commercial AI Art Production.md | 6 +- 10_Wiki/Topics_Art/Component-Composition.md | 2 +- .../Topics_Art/Component_Design_Patterns.md | 6 +- .../Topics_Art/Computational Creativity.md | 4 +- .../Topics_Art/Computational-Creativity.md | 4 +- .../Topics_Art/Computational-Linguistics.md | 2 +- 10_Wiki/Topics_Art/Computer-Aided-Design.md | 4 +- 10_Wiki/Topics_Art/Concept Mapping.md | 4 +- .../Topics_Art/ConnectAI_Dev_Log_20260429.md | 20 +- 10_Wiki/Topics_Art/Context Engineering.md | 10 +- 10_Wiki/Topics_Art/Context Rot.md | 8 +- 10_Wiki/Topics_Art/Context-Aware-Computing.md | 4 +- 10_Wiki/Topics_Art/Context_Engineering.md | 10 +- 10_Wiki/Topics_Art/ControlNet.md | 6 +- .../Topics_Art/Cost-Benefit Analysis in AI.md | 2 +- .../Topics_Art/Cumulative-Layout-Shift-CLS.md | 2 +- 10_Wiki/Topics_Art/Custom-Hooks-Patterns.md | 2 +- .../Topics_Art/Customer-Journey-Mapping.md | 4 +- .../Topics_Art/DAG-Dependency-Management.md | 4 +- .../Topics_Art/DALL-E 3 Natural Language.md | 6 +- .../Topics_Art/DALL-E 3 Negation Handling.md | 6 +- .../DALL-E 3 Synthetic Captioning.md | 6 +- .../DALL-E 3 대화형 프롬프트 생성.md | 6 +- 10_Wiki/Topics_Art/DALL-E 3.md | 6 +- .../DALL-E 3와 GPT-4의 상호작용적 생성.md | 6 +- .../DALL-E 3의 자연어 기반 최적화.md | 6 +- 10_Wiki/Topics_Art/DDD-in-TypeScript.md | 4 +- 10_Wiki/Topics_Art/Data-Flywheel-Effect.md | 2 +- 10_Wiki/Topics_Art/Data-Science-in-UX.md | 4 +- .../Topics_Art/Data-Transfer-Object-Design.md | 2 +- 10_Wiki/Topics_Art/Dead-Space-Series.md | 4 +- 10_Wiki/Topics_Art/Deep-Grammar.md | 4 +- 10_Wiki/Topics_Art/Deepfake-Detection.md | 4 +- 10_Wiki/Topics_Art/Definitions_of_Game.md | 4 +- 10_Wiki/Topics_Art/Degrees-of-Freedom.md | 6 +- 10_Wiki/Topics_Art/Deliberate-Practice.md | 4 +- .../Denavit-Hartenberg-Parameters.md | 4 +- .../Topics_Art/Dependency-Graph-Analysis.md | 4 +- .../Dependency-Inversion-Principle.md | 4 +- 10_Wiki/Topics_Art/Deployment_Final_Gate.md | 6 +- 10_Wiki/Topics_Art/Design-System.md | 4 +- .../Topics_Art/DevOps-and-UX-Convergence.md | 6 +- 10_Wiki/Topics_Art/Diffusion Models.md | 6 +- .../Directed-Acyclic-Graph-Build-Systems.md | 4 +- 10_Wiki/Topics_Art/Dissipative-Structures.md | 4 +- .../Distributed Systems & Reliability.md | 8 +- .../Distributed-System-Type-Safety.md | 4 +- 10_Wiki/Topics_Art/Distributed-Systems.md | 4 +- 10_Wiki/Topics_Art/Documentation-Strategy.md | 4 +- 10_Wiki/Topics_Art/Domain Objects.md | 2 +- .../Topics_Art/Domain-Driven-Design-DDD.md | 2 +- .../Topics_Art/Drama Management Systems.md | 4 +- .../Dynamic Difficulty Adjustment (DDA).md | 4 +- .../Dynamic-Creative-Optimization.md | 4 +- 10_Wiki/Topics_Art/E-commerce-Optimization.md | 4 +- .../E-component (Execution Loop).md | 8 +- .../EU-Web-Accessibility-Directive.md | 2 +- .../Ecology and Ecosystem Modeling.md | 4 +- .../Topics_Art/Economic-Complexity-Index.md | 4 +- 10_Wiki/Topics_Art/Edge Computing.md | 8 +- .../Edge-Artificial-Intelligence.md | 4 +- 10_Wiki/Topics_Art/Edtech-Industry-Trends.md | 4 +- .../Topics_Art/Effective-Altruism-in-AI.md | 4 +- 10_Wiki/Topics_Art/Embodied-AI.md | 2 +- 10_Wiki/Topics_Art/Emergence-in-Systems.md | 2 +- ...lly Intelligent Tutoring Systems (EITS).md | 2 +- 10_Wiki/Topics_Art/Empathy-in-AI.md | 4 +- .../Encapsulation-and-Information-Hiding.md | 2 +- .../Encapsulation-of-Domain-Invariants.md | 2 +- 10_Wiki/Topics_Art/End-to-End-Learning.md | 2 +- .../Topics_Art/Enterprise-Design-Systems.md | 2 +- .../Enterprise-Scale-Monorepo-Management.md | 2 +- .../Enterprise-Software-Architecture.md | 4 +- .../Entity-Relationship-Modeling.md | 4 +- .../Topics_Art/Environment-Design-in-RL.md | 2 +- .../Topics_Art/Enzyme-Inhibition-Kinetics.md | 4 +- 10_Wiki/Topics_Art/Equality.md | 4 +- .../Ergonomics-in-Workspace-Design.md | 4 +- 10_Wiki/Topics_Art/Error-Boundary-Pattern.md | 2 +- .../Ethics-in-Artificial-Intelligence.md | 4 +- 10_Wiki/Topics_Art/Ethnographic-Research.md | 4 +- .../Topics_Art/Eugen Systems 모딩 매뉴얼.md | 4 +- ...stems의 Iriszoom 엔진 및 전략 게임 개발.md | 4 +- .../Eugen Systems의 WARNO 시뮬레이션 개발.md | 4 +- 10_Wiki/Topics_Art/Event Storming.md | 14 +- 10_Wiki/Topics_Art/Evolutionary Biology.md | 4 +- .../Evolutionary-Algorithm-Design.md | 4 +- .../Topics_Art/Excess-Property-Checking.md | 2 +- 10_Wiki/Topics_Art/Excessive Agency.md | 8 +- .../Execution Environment (Sandbox).md | 8 +- .../Topics_Art/Experience-Sampling-Method.md | 4 +- 10_Wiki/Topics_Art/Explainable-AI-XAI.md | 2 +- .../Topics_Art/Exploratory-Data-Analysis.md | 2 +- 10_Wiki/Topics_Art/Exponential-Growth.md | 4 +- .../Topics_Art/Eye-Tracking-in-UX-Research.md | 6 +- 10_Wiki/Topics_Art/Eye-Tracking.md | 4 +- 10_Wiki/Topics_Art/Factory-Pattern.md | 4 +- 10_Wiki/Topics_Art/Failable-Task-Handling.md | 4 +- 10_Wiki/Topics_Art/Feature-Flags.md | 4 +- .../Topics_Art/Feedback-Loops-in-Design.md | 4 +- 10_Wiki/Topics_Art/Figma-to-Code-Workflow.md | 2 +- 10_Wiki/Topics_Art/Figurative-Language.md | 4 +- 10_Wiki/Topics_Art/Finite-State-Machines.md | 4 +- 10_Wiki/Topics_Art/Fluent-Interface-Design.md | 4 +- .../Topics_Art/Fluid-Dynamics for Games.md | 2 +- ...ntend-Architecture-and-Folder-Structure.md | 2 +- 10_Wiki/Topics_Art/Frontend-Architecture.md | 2 +- .../Frontend-Debugging-and-Testing.md | 2 +- ...Frontend-Performance-Optimization-Guide.md | 2 +- ...ntend-Team-Collaboration-and-Governance.md | 2 +- 10_Wiki/Topics_Art/Frontend.md | 4 +- 10_Wiki/Topics_Art/GPU.md | 6 +- .../Topics_Art/Gacha Mechanics Analysis.md | 2 +- .../Topics_Art/Game Analytics (게임 분석).md | 2 +- 10_Wiki/Topics_Art/Game-Balance-Design.md | 2 +- 10_Wiki/Topics_Art/Game-Balance-Modeling.md | 2 +- 10_Wiki/Topics_Art/Game-Design-Ontology.md | 4 +- 10_Wiki/Topics_Art/Game-Design-Theory.md | 4 +- 10_Wiki/Topics_Art/Game-Economy-Design.md | 2 +- 10_Wiki/Topics_Art/Game-Feel-and-Juiciness.md | 4 +- 10_Wiki/Topics_Art/Game-Loop-Architecture.md | 4 +- 10_Wiki/Topics_Art/Game-Mechanics.md | 2 +- 10_Wiki/Topics_Art/Game-Ontology-for-PCG.md | 4 +- 10_Wiki/Topics_Art/Game-Theory-in-AI.md | 2 +- 10_Wiki/Topics_Art/Gamification-Strategies.md | 2 +- ...dversarial Networks (GANs) in Fine Arts.md | 4 +- .../Generative-Adversarial-Networks.md | 2 +- .../Geographic-Information-Systems.md | 4 +- 10_Wiki/Topics_Art/Geometric-Deep-Learning.md | 2 +- 10_Wiki/Topics_Art/Gestalt Psychology.md | 4 +- .../Topics_Art/Gestalt-Principles in UX.md | 2 +- .../Gestalt-Principles-of-Design.md | 2 +- 10_Wiki/Topics_Art/Goal-Misgeneralization.md | 4 +- 10_Wiki/Topics_Art/Gradient-Descent.md | 4 +- 10_Wiki/Topics_Art/Graph-Coloring-Problem.md | 4 +- .../GraphRAG & Knowledge Graph Memory.md | 8 +- .../GraphRAG (그래프 기반 검색 증강 생성).md | 10 +- .../Guilty-Gear-Xrd-Rendering-Pipeline.md | 4 +- 10_Wiki/Topics_Art/HBO-Prestige-Television.md | 4 +- .../HCI (Human-Computer Interaction).md | 4 +- .../Hardware-Acceleration-for-AI.md | 2 +- 10_Wiki/Topics_Art/Hardware-Verification.md | 4 +- 10_Wiki/Topics_Art/Hardware.md | 4 +- 10_Wiki/Topics_Art/Hedera(HCS 및 Fauxkens).md | 6 +- .../Hierarchical-Task-Network (HTN).md | 2 +- .../Topics_Art/High-Availability-Systems.md | 2 +- .../Topics_Art/High-Cohesion-Low-Coupling.md | 4 +- .../Topics_Art/High-Performance-Coaching.md | 4 +- 10_Wiki/Topics_Art/Homeostasis.md | 4 +- 10_Wiki/Topics_Art/Homomorphic-Encryption.md | 2 +- .../Human-Computer-Interaction-HCI.md | 2 +- .../Topics_Art/Human-Computer-Interaction.md | 4 +- .../Hydration-Mismatch-and-SSR-Debugging.md | 2 +- .../Hyperinflation-in-Closed-Loop-Systems.md | 4 +- ...DE (Integrated Development Environment).md | 4 +- .../Image Inpainting (Vary Region).md | 6 +- 10_Wiki/Topics_Art/Image Parameters.md | 6 +- 10_Wiki/Topics_Art/Immersive-Sim-Design.md | 4 +- 10_Wiki/Topics_Art/Immutability-Patterns.md | 4 +- 10_Wiki/Topics_Art/Impedance-Matching.md | 2 +- 10_Wiki/Topics_Art/Inclusive-Design-and-UX.md | 2 +- 10_Wiki/Topics_Art/Incremental-Computation.md | 4 +- .../Incremental-Static-Regeneration-ISR.md | 2 +- .../Independent-Component-Analysis.md | 2 +- .../Index-Fragmentation-Analysis.md | 4 +- 10_Wiki/Topics_Art/Index.md | 8 +- 10_Wiki/Topics_Art/Index_13.md | 10 +- 10_Wiki/Topics_Art/Index_2.md | 16 +- 10_Wiki/Topics_Art/Index_692.md | 2942 ++++++++--------- .../Topics_Art/Indirect Prompt Injection.md | 8 +- .../Inference-Coupled Persistence.md | 8 +- 10_Wiki/Topics_Art/Inference-Optimization.md | 10 +- 10_Wiki/Topics_Art/Information-Society.md | 4 +- .../Inheritance-and-Polymorphism.md | 2 +- .../Topics_Art/Inpainting & Outpainting.md | 6 +- 10_Wiki/Topics_Art/Inquiry-Based Learning.md | 4 +- 10_Wiki/Topics_Art/InstancedMesh2 library.md | 4 +- 10_Wiki/Topics_Art/Instinct.md | 4 +- 10_Wiki/Topics_Art/Intangible-Capital.md | 4 +- .../Topics_Art/Integration-Testing-for-AI.md | 2 +- .../Interaction-to-Next-Paint-INP.md | 2 +- .../Interface-Segregation-Principle.md | 2 +- .../Topics_Art/Internet of Things (IoT).md | 4 +- 10_Wiki/Topics_Art/IoT-and-AI-Integration.md | 2 +- 10_Wiki/Topics_Art/Iterative Prompting.md | 6 +- .../Iterative-Development-Models.md | 2 +- 10_Wiki/Topics_Art/Iterative-Development.md | 4 +- .../Topics_Art/JSON-and-Data-Serialization.md | 2 +- .../JavaScript-Async-and-Event-Loop.md | 2 +- 10_Wiki/Topics_Art/Joint-Optimization.md | 4 +- 10_Wiki/Topics_Art/Journaling.md | 4 +- 10_Wiki/Topics_Art/Just-in-Case.md | 4 +- .../K-Means-Clustering-Foundations.md | 2 +- .../KISS (Keep It Simple, Stupid).md | 4 +- .../KISS-Principle-in-Software-Design.md | 2 +- .../KPI (Key Performance Indicator).md | 4 +- .../Kernel-Density-Estimation-KDE.md | 2 +- .../L-component (Lifecycle Hooks).md | 8 +- 10_Wiki/Topics_Art/Language-Models.md | 4 +- ...scale-Application-Architecture-Patterns.md | 2 +- .../Largest Contentful Paint (LCP).md | 6 +- .../Largest-Contentful-Paint-LCP.md | 2 +- .../Layered-Architecture-in-Frontend.md | 2 +- 10_Wiki/Topics_Art/Lazy-Loading-Strategies.md | 2 +- 10_Wiki/Topics_Art/Learning-Paths.md | 4 +- .../Topics_Art/Lighting and Composition.md | 6 +- .../Topics_Art/Linguistic-Analysis-in-AI.md | 2 +- .../Topics_Art/Linux-Performance-Tuning.md | 2 +- 10_Wiki/Topics_Art/Liquid-Democracy.md | 2 +- 10_Wiki/Topics_Art/LoRA.md | 6 +- .../Topics_Art/Load-Balancing-Strategies.md | 2 +- .../MCP (Model Context Protocol).md | 10 +- 10_Wiki/Topics_Art/MCP.md | 10 +- 10_Wiki/Topics_Art/Magic-Circle.md | 4 +- 10_Wiki/Topics_Art/Main Thread.md | 6 +- .../Topics_Art/Markov-Chain-Monte-Carlo.md | 2 +- .../Markov-Decision-Process (MDP).md | 4 +- .../Master-of-Information-Management.md | 4 +- 10_Wiki/Topics_Art/Mastery.md | 4 +- .../Medical-Imaging-Data-Augmentation.md | 4 +- .../Memory-Leak-Debugging-in-JavaScript.md | 2 +- .../Mental-Operations-Synthesized.md | 4 +- 10_Wiki/Topics_Art/Metaverse Aesthetics.md | 6 +- .../Micro-interactions-and-Feedback-Loops.md | 2 +- 10_Wiki/Topics_Art/Micro-interactions.md | 4 +- 10_Wiki/Topics_Art/Middle-Out-Thinking.md | 4 +- 10_Wiki/Topics_Art/Midjourney Parameter.md | 6 +- 10_Wiki/Topics_Art/Midjourney Parameters.md | 6 +- ... V6 및 V7 기반의 이미지 생성 워크플로우.md | 6 +- .../Topics_Art/Midjourney V7 Draft Mode.md | 6 +- .../Midjourney V7 및 V6 워크플로우.md | 6 +- .../Midjourney V7의 Draft Mode 워크플로우.md | 6 +- ...djourney 브랜드 캠페인 및 무드보드 제작.md | 6 +- 10_Wiki/Topics_Art/Midjourney.md | 6 +- 10_Wiki/Topics_Art/Minimal-Viable-Product.md | 4 +- .../Topics_Art/Minimum-Viable-Product-MVP.md | 2 +- 10_Wiki/Topics_Art/Mipmap.md | 4 +- .../Topics_Art/Mobile-Augmented-Reality.md | 4 +- ...bile-First-Responsive-Design-Principles.md | 2 +- 10_Wiki/Topics_Art/Model Parameters.md | 6 +- .../Topics_Art/Model-Deployment-Patterns.md | 2 +- 10_Wiki/Topics_Art/Modeling/.gitkeep | 0 10_Wiki/Topics_Art/Modeling/Index.md | 6 +- .../Apple Vision Pro Ecosystem.md | 6 +- .../Modeling/Metaverse & Devices/Index.md | 2 +- .../Modeling/Metaverse/Architecture.md | 10 +- .../Topics_Art/Modeling/Metaverse/Index.md | 4 +- .../Modeling/Metaverse/Spatial_Computing.md | 10 +- ...odern-Frontend-Engineering-Architecture.md | 2 +- ...React-Application-Architecture-Patterns.md | 2 +- .../Modern-Web-Design-Best-Practices-2025.md | 2 +- .../Topics_Art/Modern-Website-Architecture.md | 2 +- .../Modern_Environment_Ecosystem.md | 6 +- 10_Wiki/Topics_Art/Modular-Design.md | 4 +- 10_Wiki/Topics_Art/Moodboard Creation.md | 6 +- .../Topics_Art/Motion-Capture-Retargeting.md | 6 +- .../Multi-Agent-Reinforcement-Learning.md | 2 +- 10_Wiki/Topics_Art/Multi-agent-System.md | 4 +- .../NLP (Natural Language Processing).md | 4 +- .../National-Language-Processing.md | 2 +- .../Topics_Art/Natural-Language-Processing.md | 2 +- 10_Wiki/Topics_Art/Nearest-Neighbor-Search.md | 2 +- 10_Wiki/Topics_Art/Negative Prompt.md | 6 +- 10_Wiki/Topics_Art/Negative Prompts.md | 6 +- .../Network-Latency-Optimization.md | 2 +- .../Neural-Networks-for-Beginners.md | 2 +- 10_Wiki/Topics_Art/Neural-Style-Transfer.md | 2 +- .../Topics_Art/Neuromuscular-Adaptation.md | 4 +- .../Neuroplasticity in Motor Learning.md | 4 +- 10_Wiki/Topics_Art/Next-js-and-Modern-Web.md | 2 +- .../Nextjs-App-Router-Architecture.md | 2 +- ... Sky (Large-scale planetary generation).md | 4 +- 10_Wiki/Topics_Art/No Mans Sky.md | 4 +- ...hotorealistic-Rendering-in-Level-Design.md | 4 +- 10_Wiki/Topics_Art/OKR.md | 4 +- 10_Wiki/Topics_Art/OWASP Top 10.md | 16 +- .../Object-Oriented-Design-Patterns.md | 4 +- .../Topics_Art/Object-Oriented-Programming.md | 2 +- 10_Wiki/Topics_Art/Observation.md | 4 +- .../Topics_Art/Okami-Ink-Wash-Aesthetics.md | 4 +- .../Topics_Art/Olympic-Training-Protocols.md | 4 +- 10_Wiki/Topics_Art/Omni Reference (--oref).md | 6 +- 10_Wiki/Topics_Art/Omni Reference.md | 6 +- 10_Wiki/Topics_Art/One-Hot-Encoding.md | 2 +- .../Ontology-Driven-Relevancy-Filtering.md | 2 +- .../Ontology-Guided Knowledge Extraction.md | 4 +- 10_Wiki/Topics_Art/Operations-Research.md | 4 +- .../Optical-Character-Recognition.md | 2 +- 10_Wiki/Topics_Art/Optimization-Algorithms.md | 2 +- .../Topics_Art/P-Reinforce-Template-Guide.md | 2 +- 10_Wiki/Topics_Art/PDF-Format.md | 4 +- ...Papers Please (Bureaucratic Simulation).md | 4 +- 10_Wiki/Topics_Art/Parameter Control.md | 6 +- 10_Wiki/Topics_Art/Parameter.md | 6 +- .../Partial-Differential-Equations.md | 2 +- .../Topics_Art/Particle-Filter-Algorithms.md | 2 +- .../Personal-Information-Security.md | 2 +- 10_Wiki/Topics_Art/Pipeline-Parallelism.md | 2 +- .../Topics_Art/Player-Experience-Modeling.md | 4 +- .../Player-Psyche-Profiling-Framework.md | 4 +- .../Topics_Art/Plutchiks-Wheel-of-Emotions.md | 4 +- 10_Wiki/Topics_Art/Poetic-Computation.md | 2 +- .../Polymorphism-in-Engine-Architecture.md | 4 +- 10_Wiki/Topics_Art/Pose-Estimation.md | 2 +- 10_Wiki/Topics_Art/Positive Prompt.md | 6 +- 10_Wiki/Topics_Art/Positive Prompts.md | 6 +- 10_Wiki/Topics_Art/Positive-Reinforcement.md | 2 +- 10_Wiki/Topics_Art/Poverty-Simulation.md | 4 +- .../Principle-Component-Analysis.md | 4 +- ...rinciples of Structuralism (Linguistic).md | 4 +- .../Topics_Art/Principles-of-Architecture.md | 4 +- .../Topics_Art/Prisoners-Dilemma-Models.md | 4 +- .../Topics_Art/Prisons-and-Self-Correction.md | 4 +- 10_Wiki/Topics_Art/Privacy-Preserving-AI.md | 2 +- .../Probabilistic-Graphical-Models.md | 2 +- .../Probability and Logic Fusion.md | 4 +- 10_Wiki/Topics_Art/Problem-Solving.md | 4 +- ...Generation via Machine Learning (PCGML).md | 4 +- .../Procedural Narrative Generation.md | 4 +- .../Procedural Rhetoric (In Gaming).md | 4 +- .../Procedural-Architecture-Systems.md | 4 +- 10_Wiki/Topics_Art/Procedural-Knowledge.md | 4 +- .../Topics_Art/Procedural-Level-Geometry.md | 4 +- 10_Wiki/Topics_Art/Product-Led-Growth.md | 4 +- 10_Wiki/Topics_Art/Product-Management.md | 4 +- 10_Wiki/Topics_Art/Product-Marketing.md | 4 +- 10_Wiki/Topics_Art/Product-Thinking-in-AI.md | 2 +- 10_Wiki/Topics_Art/Progressive-Disclosure.md | 2 +- 10_Wiki/Topics_Art/Project-Management.md | 4 +- 10_Wiki/Topics_Art/Prompt Engineering.md | 6 +- 10_Wiki/Topics_Art/Prompt Structure.md | 6 +- 10_Wiki/Topics_Art/Prompt Weight.md | 6 +- 10_Wiki/Topics_Art/Prompt Weighting.md | 6 +- 10_Wiki/Topics_Art/Prompt Weights.md | 6 +- .../Prompt-Engineering-Foundations.md | 2 +- 10_Wiki/Topics_Art/Prompt-Engineering.md | 2 +- 10_Wiki/Topics_Art/Prototyping.md | 4 +- 10_Wiki/Topics_Art/Psychology.md | 4 +- 10_Wiki/Topics_Art/Quick-Wins.md | 4 +- .../Topics_Art/Random-Forest-Classifiers.md | 2 +- 10_Wiki/Topics_Art/Randomized-Algorithms.md | 2 +- 10_Wiki/Topics_Art/Ranking-Algorithms.md | 2 +- 10_Wiki/Topics_Art/Rapid-Prototyping.md | 4 +- 10_Wiki/Topics_Art/React-Context-API.md | 2 +- .../React-Error-Boundaries-and-Handling.md | 2 +- 10_Wiki/Topics_Art/React-Hooks.md | 2 +- .../React_Clean_Code_Best_Practices.md | 6 +- 10_Wiki/Topics_Art/React_Hooks_Deep_Dive.md | 6 +- 10_Wiki/Topics_Art/React_Mental_Model.md | 6 +- .../React_Performance_Optimization.md | 6 +- .../React_State_Management_Strategy.md | 6 +- 10_Wiki/Topics_Art/React_Testing_Strategy.md | 6 +- 10_Wiki/Topics_Art/Reactive-Programming.md | 4 +- 10_Wiki/Topics_Art/Real-Time Engine (RTE).md | 14 +- 10_Wiki/Topics_Art/Recommendation-Systems.md | 2 +- .../Recording Academy (The Grammys).md | 2 +- .../Refactoring-Legacy-React-Codebases.md | 2 +- 10_Wiki/Topics_Art/Refinement.md | 4 +- 10_Wiki/Topics_Art/Related-Work.md | 4 +- .../Relational Algebra in Databases.md | 4 +- 10_Wiki/Topics_Art/Relative-Positioning.md | 2 +- .../Topics_Art/Reliability_Safety_First.md | 6 +- 10_Wiki/Topics_Art/Reports.md | 4 +- 10_Wiki/Topics_Art/Requirements.md | 4 +- 10_Wiki/Topics_Art/ResNet-Architectures.md | 2 +- .../Retrieval-Augmented Generation (RAG).md | 10 +- .../Retrieval-Augmented-Generation-RAG.md | 6 +- .../Topics_Art/Reward Hacking (보상 해킹).md | 4 +- 10_Wiki/Topics_Art/Reward-Shaping-in-RL.md | 2 +- 10_Wiki/Topics_Art/Roadmap.md | 4 +- .../Topics_Art/Roughness (그래픽 및 물리).md | 4 +- 10_Wiki/Topics_Art/Rule-based-Systems.md | 2 +- .../Topics_Art/S-component (State Store).md | 8 +- 10_Wiki/Topics_Art/SAST.md | 4 +- .../SDLC (소프트웨어 개발 수명 주기).md | 6 +- 10_Wiki/Topics_Art/SOTA.md | 4 +- 10_Wiki/Topics_Art/SOW.md | 4 +- 10_Wiki/Topics_Art/SaaS.md | 4 +- 10_Wiki/Topics_Art/Safety & Reliability.md | 4 +- 10_Wiki/Topics_Art/Sales-Strategy.md | 4 +- .../Scalable-Design-System-Governance.md | 2 +- 10_Wiki/Topics_Art/Scheduler-Design-in-ML.md | 2 +- 10_Wiki/Topics_Art/Schema-Design-for-NoSQL.md | 2 +- 10_Wiki/Topics_Art/Schema.md | 4 +- .../Topics_Art/Scientific Communication.md | 4 +- 10_Wiki/Topics_Art/Scientific-Method.md | 4 +- .../Secure-Multi-party-Computation.md | 2 +- 10_Wiki/Topics_Art/Security-Best-Practices.md | 2 +- .../Self-Play (자기 대결 기반 강화학습).md | 4 +- .../Topics_Art/Semantic-HTML-Foundations.md | 2 +- .../Topics_Art/Sentiment-Analysis-Models.md | 2 +- 10_Wiki/Topics_Art/Sentiment-Analysis.md | 4 +- 10_Wiki/Topics_Art/Separation_of_Concerns.md | 4 +- .../Topics_Art/Serverless-Computing-for-AI.md | 2 +- .../Topics_Art/Sharding-and-Partitioning.md | 2 +- .../Signal-Processing-Foundations.md | 2 +- 10_Wiki/Topics_Art/Signature Style Design.md | 6 +- 10_Wiki/Topics_Art/Single_Source_of_Truth.md | 4 +- .../Topics_Art/Skybound Protocol 코드리뷰.md | 2 +- .../Skybound_Asset_Generation_Roadmap.md | 4 +- .../Topics_Art/Skybound_Asset_Purity_Sync.md | 6 +- .../Skybound_Skill_Asset_Integration.md | 4 +- .../Skybound_Skill_Image_Integration.md | 6 +- 10_Wiki/Topics_Art/Smart-Contract-Auditing.md | 2 +- .../Software Engineering Agents (SWE).md | 8 +- .../Software-Architecture-Patterns.md | 2 +- .../Topics_Art/Software-Design-Principles.md | 4 +- 10_Wiki/Topics_Art/Solitude-Optimization.md | 4 +- 10_Wiki/Topics_Art/Solution.md | 4 +- 10_Wiki/Topics_Art/Sorting.md | 4 +- 10_Wiki/Topics_Art/Sound Design Principles.md | 4 +- 10_Wiki/Topics_Art/Spatial-Data-Analysis.md | 2 +- 10_Wiki/Topics_Art/Specification.md | 4 +- 10_Wiki/Topics_Art/Speculative-Design.md | 4 +- .../Stable Diffusion Image Optimization.md | 6 +- .../Topics_Art/Stable Diffusion Weights.md | 6 +- .../Stable Diffusion 오픈소스 제어.md | 6 +- 10_Wiki/Topics_Art/Stable Diffusion.md | 6 +- .../Stable Diffusion의 가중치 제어 문법.md | 6 +- 10_Wiki/Topics_Art/Startup.md | 4 +- ...e-Management-Architecture-and-Ownership.md | 2 +- .../Topics_Art/State-Management-Patterns.md | 2 +- 10_Wiki/Topics_Art/Steel Division 시리즈.md | 4 +- 10_Wiki/Topics_Art/Stem-Analysis.md | 4 +- 10_Wiki/Topics_Art/Strategic-Ambiguity.md | 4 +- .../Topics_Art/Strategic-Planning-for-AI.md | 2 +- 10_Wiki/Topics_Art/Strategy.md | 4 +- 10_Wiki/Topics_Art/Structuralism.md | 4 +- .../Topics_Art/Style Reference (--sref).md | 8 +- 10_Wiki/Topics_Art/Style Reference.md | 6 +- 10_Wiki/Topics_Art/Style-Transfer-in-AI.md | 2 +- 10_Wiki/Topics_Art/Style-Transfer.md | 4 +- 10_Wiki/Topics_Art/Styling_Governance.md | 6 +- 10_Wiki/Topics_Art/Support.md | 4 +- 10_Wiki/Topics_Art/Swarm Intelligence.md | 4 +- 10_Wiki/Topics_Art/Swarm-Intelligence.md | 2 +- 10_Wiki/Topics_Art/Symmetry-and-Invariance.md | 4 +- .../Topics_Art/Synthesized Intelligence.md | 4 +- .../Topics_Art/Synthetic-Data-Generation.md | 2 +- .../Topics_Art/System-Architecture-Design.md | 2 +- .../Topics_Art/System-Design for AI Scale.md | 2 +- .../System-Design-Interview-Prep.md | 2 +- .../Topics_Art/System-Dynamics-Modeling.md | 2 +- .../Topics_Art/System_Debugging_Protocol.md | 4 +- .../Topics_Art/System_Protocol_Standard.md | 2 +- .../Topics_Art/T-component (Tool Registry).md | 8 +- .../Topics_Art/Tableau-Data-Visualization.md | 2 +- 10_Wiki/Topics_Art/Task-Management.md | 4 +- 10_Wiki/Topics_Art/Technical-Architecture.md | 4 +- 10_Wiki/Topics_Art/Technical-Debt.md | 4 +- 10_Wiki/Topics_Art/Terminology.md | 4 +- .../Tetris_Project_Retrospective.md | 2 +- 10_Wiki/Topics_Art/Threejs WebGPURenderer.md | 6 +- 10_Wiki/Topics_Art/Threejs 성능 최적화.md | 4 +- 10_Wiki/Topics_Art/TypeScript_Type_Safety.md | 6 +- 10_Wiki/Topics_Art/UI_UX_Assets/.gitkeep | 0 .../Topics_Art/UI_UX_Assets/Atomic Design.md | 6 +- ...ic Batching을 통한 React 18 성능 최적화.md | 6 +- .../Building Reusable UI Components.md | 6 +- .../UI_UX_Assets/CSS Architecture.md | 6 +- .../UI_UX_Assets/CSS Container Queries.md | 6 +- .../UI_UX_Assets/CSS Grid 및 Flexbox.md | 6 +- 10_Wiki/Topics_Art/UI_UX_Assets/CSS Grid.md | 6 +- .../UI_UX_Assets/CSS Media Queries.md | 6 +- .../CSS Performance Optimization.md | 6 +- .../Topics_Art/UI_UX_Assets/CSS Variables.md | 6 +- .../UI_UX_Assets/CSS 구조 설계 방식.md | 6 +- ...능 최적화(CSS Performance Optimization).md | 6 +- ...니메이션 성능(CSS Animation Performance).md | 6 +- ...이션 최적화(CSS Animations Optimization).md | 6 +- ...메이션 최적화(Optimizing CSS Animations).md | 6 +- .../UI_UX_Assets/Client Components.md | 8 +- .../UI_UX_Assets/Component API Design.md | 6 +- .../Component Library Architecture.md | 6 +- .../UI_UX_Assets/Component-Based Design.md | 6 +- .../Compound Components Pattern.md | 6 +- .../UI_UX_Assets/Compound Components.md | 6 +- .../UI_UX_Assets/Concurrent Rendering.md | 6 +- ...Web Vitals Optimization (INP, LCP 개선).md | 6 +- .../UI_UX_Assets/Critical Rendering Path.md | 6 +- .../DOM (Document Object Model).md | 4 +- .../Topics_Art/UI_UX_Assets/DOM 및 CSSOM.md | 6 +- .../DOM(Document Object Model).md | 4 +- ...ity-for-Ontarians-with-Disabilities-Act.md | 6 +- ... 모델링 (State Modeling and API Responses).md | 10 +- .../AST-Manipulation-Techniques.md | 6 +- .../Abstract-Syntax-Tree-Transformation.md | 8 +- .../Abstract-Syntax-Tree-Traversal.md | 8 +- .../Accessibility (A11y).md | 6 +- .../Accessibility-Compliance-WCAG.md | 6 +- .../Additive-Type-Logic.md | 8 +- .../Affective User Interfaces (AUI).md | 6 +- .../Agency-in-Game-Design.md | 8 +- ...unication Protocol (에이전트 통신 규약).md | 8 +- .../Agile-UX-Integration.md | 6 +- .../Americans-with-Disabilities-Act-ADA.md | 6 +- .../Apple Human Interface Guidelines.md | 6 +- .../Design & Experience/Arkane-Studios.md | 6 +- .../Assignability-Rules.md | 6 +- .../Assistive-Technology-Interoperability.md | 6 +- .../Atomic Design Pattern.md | 10 +- .../Design & Experience/Auction-Theory.md | 6 +- .../Augmented Reality (AR) Interfaces.md | 6 +- .../Automated-Client-Generation.md | 6 +- .../Design & Experience/Bay 12 Games.md | 6 +- .../UI_UX_Assets/Design & Experience/Bazel.md | 6 +- .../Behavior-Driven-Development (BDD).md | 8 +- ... Home (Domestic Narrative Architecture).md | 6 +- .../Borderlands-Art-Direction.md | 6 +- .../Boundary-Layer-Validation.md | 6 +- .../Branded Types in TypeScript.md | 6 +- .../UI_UX_Assets/Design & Experience/Buck2.md | 6 +- .../Design & Experience/Business-Strategy.md | 8 +- .../Causal Loop Diagramming.md | 6 +- .../Choice Architecture in Digital UX.md | 6 +- .../Chrome User Experience Report (CrUX).md | 10 +- .../Design & Experience/Code Formatting.md | 10 +- .../Cognitive Aging Research.md | 6 +- .../Cognitive Dissonance.md | 6 +- .../Cognitive-Flexibility.md | 6 +- .../Cognitive-Psychology.md | 6 +- .../Complexity Science in Economics.md | 6 +- .../Computation-Caching-Strategies.md | 6 +- .../Computational Thinking.md | 6 +- .../Computational-Fluid-Dynamics.md | 6 +- .../Design & Experience/Conditional-Types.md | 6 +- .../Design & Experience/Content-Strategy.md | 6 +- .../Contract-Driven-Development.md | 6 +- .../Contract-First-Development.md | 6 +- .../Design & Experience/Contract-Testing.md | 6 +- .../Contravariance-and-Covariance.md | 6 +- .../Creativity-and-Cognitive-Complexity.md | 6 +- .../Design & Experience/Critical Design.md | 6 +- .../Design & Experience/Cryptoeconomics.md | 6 +- ...Dark Souls (Environmental Storytelling).md | 6 +- .../Design & Experience/Data-Sanitization.md | 6 +- .../Declaration Merging.md | 6 +- .../Declaration-Merging.md | 6 +- .../Design & Experience/Depth-Subtyping.md | 6 +- .../Design & Experience/Design-Thinking.md | 6 +- .../Design & Experience/Design-Tokens.md | 6 +- .../Design & Experience/Diegetic UI.md | 6 +- .../Design & Experience/Diegetic-Interface.md | 6 +- .../Design & Experience/Digital Humanities.md | 6 +- .../Digital Twin Interfaces.md | 6 +- .../Digital-Heritage-Preservation.md | 6 +- .../Design & Experience/Digital-Humanities.md | 6 +- .../Digital-Transformation-Strategy.md | 6 +- .../Design & Experience/Divergent-Thinking.md | 6 +- .../Design & Experience/Duck-Typing.md | 6 +- .../Design & Experience/Dwarf Fortress.md | 6 +- .../E-commerce-Conversion-Optimization.md | 6 +- .../Design & Experience/ESL Pro Tour.md | 6 +- .../ESLint-Plugin-TypeScript.md | 6 +- .../Edge-Detection-Algorithms.md | 6 +- ...Pedagogy (Zone of Proximal Development).md | 6 +- .../Educational-Psychology.md | 6 +- .../Design & Experience/Electromyography.md | 6 +- .../Environmental Storyability.md | 6 +- .../Environmental Storytelling.md | 6 +- .../Environmental-Storytelling.md | 6 +- .../Design & Experience/Ergodic Literature.md | 6 +- .../Design & Experience/Ergodic-Literature.md | 6 +- .../Design & Experience/Executive Function.md | 6 +- .../Exhaustiveness-Checking-with-Never.md | 6 +- .../FSD (Feature-Sliced Design).md | 10 +- .../Fallout (Pip-Boy Mechanic).md | 6 +- .../Feature-Sliced Design.md | 10 +- .../Flow-Sensitive-Typing.md | 6 +- .../Formalism vs Structuralism.md | 6 +- .../Formalist Criticism.md | 6 +- .../Game Studies (Game Studies Journal).md | 6 +- .../Game Systems Design.md | 6 +- .../Design & Experience/Game-Level-Design.md | 6 +- .../Game-Studies-Academic-Discourse.md | 6 +- .../Game-Studies-Journal.md | 6 +- .../Gamification in Pedagogy.md | 6 +- .../Gamification-Mechanics.md | 6 +- .../Design & Experience/GitHub Actions.md | 10 +- .../Global Augmentation.md | 6 +- .../Grammar-based-Synthesis.md | 6 +- .../HUD-less Design Paradigms.md | 6 +- .../Haptic Feedback Technology.md | 6 +- ...erarchical Reinforcement Learning (HRL).md | 6 +- .../High-Performance-Human-Factors.md | 6 +- .../Human-Computer Interaction (HCI).md | 6 +- .../Human-Computer-Interaction (HCI).md | 6 +- .../Human-Machine Interface (HMI) Design.md | 6 +- .../Human-Robot Interaction (HRI).md | 6 +- .../Human-Robot-Interaction.md | 6 +- .../Design & Experience/Hypertextuality.md | 6 +- .../Design & Experience/ISO 9241 표준.md | 6 +- .../Immersive Analytics.md | 6 +- .../Incremental-Compilation.md | 6 +- .../UI_UX_Assets/Design & Experience/Index.md | 708 ++-- .../Information-Architecture.md | 6 +- .../Inquiry-Based Learning.md | 6 +- .../Interface Segregation Principle (ISP).md | 10 +- .../Interface-Extension-vs-Augmentation.md | 6 +- .../Interface-Extension.md | 6 +- .../Design & Experience/Interface-Merging.md | 6 +- ...ace-Segregation-Principle-in-TypeScript.md | 6 +- .../Interface-Segregation-Principle.md | 6 +- .../Interoperability Standards.md | 6 +- ...tersection-Types-vs-Interface-Extension.md | 6 +- .../Design & Experience/Inverse-Kinematics.md | 6 +- .../JSON-Schema-Validation.md | 6 +- .../Design & Experience/K-12-EdTech.md | 6 +- .../Design & Experience/Kinetics.md | 6 +- .../Knowledge-Graph-Construction.md | 6 +- ...(League of Legends Championship Series).md | 6 +- .../Design & Experience/Lean-UX.md | 6 +- .../Level Design Theory.md | 6 +- .../Level-Design-Theory.md | 6 +- .../Design & Experience/Linguistics.md | 6 +- .../Linked-Data-Principles.md | 6 +- .../Liskov-Substitution-Principle.md | 6 +- .../Ludo-Narrative-Dissonance.md | 6 +- .../Ludo-narrative Dissonance.md | 6 +- .../Ludonarrative-Dissonance.md | 6 +- .../Design & Experience/Mapped-Types.md | 6 +- .../Material Design System.md | 6 +- .../Design & Experience/Material Design.md | 6 +- .../Design & Experience/Material-Design.md | 6 +- .../Mechanism Design in Auctions.md | 6 +- .../Design & Experience/Mechanism Design.md | 6 +- .../Design & Experience/Mechanism-Design.md | 6 +- .../Micro-Frontend-Architecture.md | 6 +- .../Mobile-App-Onboarding.md | 6 +- .../Module Resolution Algorithm.md | 6 +- .../Module-Augmentation-Patterns.md | 6 +- .../Module-Resolution-Strategy.md | 6 +- .../Monorepo-Architecture-Design.md | 6 +- .../Monorepo-Architecture.md | 6 +- .../Monorepo-Dependency-Graph-Analysis.md | 6 +- .../Monte Carlo Tree Search (MCTS).md | 6 +- .../Motor-Learning-Theory.md | 6 +- .../Design & Experience/Motor-Learning.md | 6 +- .../Design & Experience/Narrative Design.md | 6 +- .../Narrative Intelligence.md | 6 +- .../Design & Experience/Nash Equilibrium.md | 6 +- .../Design & Experience/Nash-Equilibrium.md | 6 +- .../Design & Experience/Ninja-Build-System.md | 6 +- .../Nodejs-Backend-Architecture.md | 6 +- .../Design & Experience/Nominal Typing.md | 6 +- .../Nominal-Typing-via-Branded-Types.md | 6 +- .../Nominal-Typing-vs-Structural-Typing.md | 6 +- .../Nominal-vs-Structural-Typing.md | 6 +- .../Design & Experience/Non-Diegetic UI.md | 6 +- .../Design & Experience/Nx-Build-System.md | 6 +- .../Object-Literal-Assignment.md | 6 +- .../Object-Oriented-Interface-Design.md | 6 +- .../Occupational-Ergonomics.md | 6 +- .../OpenAPI-Specification.md | 6 +- .../Optimal-Experience-Research.md | 6 +- .../Organizational Learning Culture.md | 6 +- .../Organizational-Innovation-Management.md | 6 +- .../Orthopedic-Implant-Validation.md | 6 +- .../Design & Experience/Player Agency.md | 6 +- .../Design & Experience/Player-Autonomy.md | 6 +- .../Political-Philosophy-in-Games.md | 6 +- .../Product-Analytics-Infrastructure.md | 6 +- .../Protocol-Buffers-TypeScript.md | 6 +- .../Public Policy Design.md | 6 +- .../Quantum-Computing-Simulations.md | 6 +- ...리 엔진 스냅샷(Snapshot) 기반 상태 복원.md | 6 +- .../React Native 게임 최적화 (JSI Hermes).md | 6 +- .../React Performance Optimization.md | 10 +- ...eact 상태 관리 (React State Management).md | 10 +- .../React 상태 관리 및 API 응답 처리.md | 10 +- .../React 컴포넌트 Props 검증.md | 10 +- .../Redstone Engineering.md | 6 +- .../Redux 등 상태 관리 (State Management).md | 10 +- .../Redux 스타일 리듀서 및 액션 관리.md | 10 +- .../Design & Experience/Redux-Reducers.md | 6 +- .../Redux-Toolkit-Architecture.md | 6 +- .../Reinforcement Learning Reward Shaping.md | 6 +- .../Design & Experience/Roguelike Subgenre.md | 6 +- .../Design & Experience/SeL4-Microkernel.md | 6 +- .../Self-Determination Theory.md | 6 +- .../Self-Determination-Theory.md | 6 +- .../Design & Experience/Service-Design.md | 6 +- .../Design & Experience/SimCity-Series.md | 6 +- .../Single-Responsibility-Principle.md | 6 +- .../Single-Source-of-Truth-Principle.md | 6 +- .../Smithsonian-Digital-Repository.md | 6 +- .../Design & Experience/Snyk Open Source.md | 10 +- .../Social Learning Theory.md | 6 +- .../Socially Assistive Robotics (SAR).md | 6 +- ...tware Architecture API Contract Design.md | 6 +- .../Software-Contract-Enforcement.md | 6 +- .../Software-Product-Management.md | 6 +- .../Design & Experience/Spatial Cognition.md | 6 +- .../Design & Experience/Spatial Computing.md | 6 +- .../State-Machine-Implementation.md | 6 +- .../Static Type Checking Systems.md | 6 +- .../Static-Program-Analysis.md | 6 +- .../Structural Type System.md | 6 +- .../Structural-Subtyping.md | 6 +- .../Structural-Type-System.md | 6 +- .../Structural-Typing-Analysis.md | 6 +- .../Structural-Typing-Compatibility.md | 6 +- .../Structural-Typing-Mechanics.md | 6 +- .../Structural-Typing-Mechanisms.md | 6 +- .../Structural-Typing-System.md | 6 +- .../Structural-Typing-and-Compatibility.md | 6 +- .../Structural-Typing-vs-Nominal-Typing.md | 6 +- .../Design & Experience/Structural-Typing.md | 6 +- .../Structural-vs-Nominal-Typing-in-TS.md | 6 +- .../Structural-vs-Nominal-Typing.md | 6 +- .../Subtyping-Relations.md | 6 +- .../Design & Experience/Subtyping-Rules.md | 6 +- .../Subtyping-and-Variance.md | 6 +- .../Design & Experience/Systemic Design.md | 6 +- .../Systemic Game Design.md | 6 +- .../Design & Experience/Systemic-Design.md | 6 +- .../Design & Experience/Systems-Thinking.md | 6 +- .../Template-Literal-Types.md | 6 +- .../The Emergence Theory in Game Design.md | 6 +- ... (Resource Scarcity and Character Bond).md | 6 +- .../Topological-Sorting.md | 6 +- .../Touchpoint-Analysis.md | 6 +- .../Tree Shaking (번들 크기 최적화).md | 10 +- .../Turborepo-Orchestration.md | 6 +- .../Design & Experience/Type Alias.md | 10 +- .../Design & Experience/Type Branding.md | 6 +- .../Design & Experience/Type Declaration.md | 10 +- .../Design & Experience/Type-Aware-Linting.md | 6 +- .../Type-Compatibility-Rules.md | 6 +- .../Type-Compatibility-and-Subtyping.md | 6 +- .../Design & Experience/Type-Compatibility.md | 6 +- .../Type-Composition-via-Intersections.md | 6 +- .../Type-Driven-Development.md | 6 +- .../Type-Erasure-and-Runtime-Behavior.md | 6 +- .../Type-Guards-and-Narrowing.md | 6 +- .../Design & Experience/Type-Narrowing.md | 6 +- .../Type-Safe-API-Design.md | 6 +- ...Type-Safety-and-Exhaustiveness-Checking.md | 6 +- .../Design & Experience/Type-Safety.md | 6 +- .../Type-Variance-in-TypeScript.md | 6 +- .../TypeScript Compiler API.md | 6 +- ...peScript Type System (Interface Design).md | 6 +- .../TypeScript 라이브러리 타입 확장.md | 10 +- ...인터페이스 및 시스템 보호 아키텍처 설계.md | 10 +- .../TypeScript 컴파일러 캐싱 최적화.md | 10 +- .../TypeScript-Compiler-API-Design.md | 6 +- .../TypeScript-Compiler-API.md | 6 +- .../TypeScript-Compiler-Architecture.md | 6 +- .../TypeScript-Language-Service-API.md | 6 +- .../TypeScript-Project-References.md | 6 +- .../TypeScript의 안전한 인터페이스 설계.md | 10 +- ...peScript의 인터페이스 및 객체 타입 설계.md | 10 +- .../Design & Experience/UX-Gamification.md | 10 +- .../UX_UI in Interactive Media.md | 6 +- .../Unified-User-Experience.md | 6 +- .../Design & Experience/Union-Types.md | 6 +- .../Design & Experience/Urban-Morphology.md | 6 +- .../Urban-Planning-Simulations.md | 6 +- .../User Experience (UX) Design.md | 6 +- .../User Experience (UX) in Game Design.md | 6 +- .../User-Experience-Design.md | 6 +- ... (Covariance Contravariance Invariance).md | 6 +- ...-(Covariance-Contravariance-Invariance).md | 6 +- .../Variance-Covariance-Contravariance.md | 6 +- .../Design & Experience/Video Game Design.md | 6 +- .../Visual-Hierarchy-in-Game-Design.md | 6 +- .../Von Neumann-Morgenstern Axioms.md | 6 +- .../W3C-Semantic-Web-Standards.md | 6 +- .../Design & Experience/Wayfinding-Design.md | 6 +- .../Design & Experience/Wicked-Problems.md | 6 +- .../Width-and-Depth-Subtyping.md | 6 +- .../Zod-Runtime-Validation.md | 6 +- .../Zod-Schema-Validation.md | 6 +- .../eSports Performance Psychology.md | 6 +- .../가상 DOM (Virtual DOM).md | 10 +- .../계층형 아키텍처 (Layered Architecture).md | 10 +- ...용 시스템을 위한 React 기반 게임 엔진 아키텍처.md | 6 +- .../교육 심리학에서의 보상 설계.md | 6 +- .../교육학의 모델링 전략.md | 6 +- .../뇌과학 기반 중독 재활 프로그램.md | 6 +- ...규모 프론트엔드 웹 프로젝트 폴더 구조화.md | 10 +- ...데이터 지향 설계 (Data-Oriented Design).md | 6 +- .../도메인 주도 설계 (DDD).md | 10 +- .../도메인 주도 설계(DDD).md | 10 +- .../Design & Experience/도파민 보상 체계.md | 6 +- .../라이브러리 타입 선언 (dts) 확장.md | 10 +- .../마이크로 프론트엔드 (Micro Frontends).md | 10 +- .../맞춤형 개별화 학습 설계.md | 6 +- .../모바일 앱 및 웹 인터페이스 설계.md | 6 +- .../Design & Experience/몰입감 (Presence).md | 10 +- .../바운디드 컨텍스트 (Bounded Context).md | 8 +- ...응형 윈도우 리사이즈(Resize) 이벤트 처리.md | 10 +- ...기 데이터 패칭 (Async Operations Pattern).md | 10 +- .../사용성 공학 (Usability Engineering).md | 6 +- .../사용자 경험 (UX) 디자인.md | 6 +- .../Design & Experience/사용자 경험 (UX).md | 6 +- .../사용자 경험 디자인 (UX Design).md | 6 +- ...사회 인지 이론(Social Cognitive Theory).md | 6 +- .../상태 관리 최적화 (Zustand Valtio).md | 6 +- .../상태 관리(State Management).md | 10 +- ...e Machine) 모델링 및 Redux 액션_리듀서 설계.md | 10 +- .../상태 모델링 (State Modeling).md | 10 +- .../선언 병합(Declaration Merging).md | 10 +- ...소프트웨어 시스템 설계 및 아키텍처 구축.md | 10 +- ...간 데이터 대시보드 레이아웃 조절 시스템.md | 10 +- .../아보(Bobo) 인형 실험.md | 6 +- .../Design & Experience/엔티티 (Entities).md | 10 +- ...)] [행동 경제학] [교육 심리학의 행동주의 모델.md | 6 +- .../의존성 규칙 (Dependency Rule).md | 10 +- ...간 요인 공학 (Human Factors Engineering).md | 6 +- .../Design & Experience/인지 부조화 이론.md | 6 +- .../인지 부하 이론(Cognitive Load Theory).md | 6 +- .../인지 심리학 (Cognitive Psychology).md | 6 +- ... 평가 이론 (Cognitive Evaluation Theory).md | 6 +- .../인터페이스 (Interface).md | 10 +- ... 분리 원칙 (Interface Segregation Principle).md | 10 +- .../자기 효능감 (Self-Efficacy).md | 6 +- .../자기 효능감(Self-Efficacy).md | 6 +- .../자기조절학습(Self-Regulated Learning).md | 6 +- .../재조정 (Reconciliation).md | 10 +- .../조직 시민 행동 (OCB).md | 6 +- .../조직 행동론의 성과급 체계 분석.md | 6 +- .../중독 의학 및 정신 병리학.md | 6 +- .../Design & Experience/중독 재활 프로그램.md | 6 +- ..._ - TypeScript 타입 시스템 (인터페이스 설계).md | 10 +- .../치타 사람 이미지 프롬프트.md | 10 +- ...포넌트 기반 웹 프레임워크 아키텍처 설계.md | 10 +- .../클린 아키텍처 (Clean Architecture).md | 10 +- .../클린 아키텍처(Clean Architecture).md | 10 +- .../Design & Experience/클린 아키텍처.md | 10 +- .../타입 가드 (Type Guards).md | 10 +- .../타입 별칭 (Type Alias).md | 10 +- .../테스트 용이성 (Testability).md | 10 +- .../프론트엔드 컴포넌트 구조화.md | 10 +- .../프론트엔드 컴포넌트 설계.md | 10 +- ...어 경험 디자인 (Player Experience Design).md | 6 +- .../행동 치료 및 인지 행동 치료 (CBT).md | 6 +- .../현대 웹 애플리케이션 설계.md | 10 +- .../Core Web Vitals.md | 10 +- .../Design & Web Performance/Index.md | 2 +- .../Design System Architecture.md | 6 +- .../Topics_Art/UI_UX_Assets/Design Systems.md | 6 +- .../Topics_Art/UI_UX_Assets/Design Tokens.md | 6 +- .../UI_UX_Assets/Design/Accessibility.md | 10 +- .../UI_UX_Assets/Design/Cognitive_Load.md | 10 +- .../Topics_Art/UI_UX_Assets/Design/CrUX.md | 10 +- 10_Wiki/Topics_Art/UI_UX_Assets/Design/HCI.md | 10 +- .../UI_UX_Assets/Design/Inclusive_Design.md | 10 +- .../Topics_Art/UI_UX_Assets/Design/Index.md | 10 +- .../Domain-Driven Design (DDD).md | 6 +- .../Feature-Sliced Design (FSD).md | 8 +- .../UI_UX_Assets/Feature-Sliced Design.md | 8 +- .../Figma Design System Integration.md | 6 +- .../UI_UX_Assets/Headless Components.md | 6 +- .../UI_UX_Assets/Hydration 성능 최적화.md | 6 +- 10_Wiki/Topics_Art/UI_UX_Assets/Index.md | 258 +- .../UI_UX_Assets/Layout Thrashing.md | 6 +- .../UI_UX_Assets/Mobile-First Design.md | 6 +- ....js App Router 환경의 컴포넌트 스타일링.md | 6 +- ... Hybrid Rendering (SSR-CSR-RSC 혼합 적용).md | 6 +- .../UI_UX_Assets/Performance Optimization.md | 8 +- .../React 18 & 19 Performance Optimization.md | 6 +- .../React 18 Concurrent Features.md | 6 +- ...18 동시성 렌더링 (Concurrent Rendering).md | 6 +- ...괄 처리 및 React 19 컴파일러 최적화 적용.md | 6 +- 10_Wiki/Topics_Art/UI_UX_Assets/React 19.md | 6 +- .../React Component Architecture.md | 6 +- .../React Component Library Architecture.md | 6 +- .../UI_UX_Assets/React Component Patterns.md | 6 +- .../UI_UX_Assets/React Design Systems.md | 6 +- .../UI_UX_Assets/React Design Tokens.md | 6 +- .../React Fiber 및 동시성 렌더링.md | 6 +- .../UI_UX_Assets/React Fiber 아키텍처.md | 6 +- .../UI_UX_Assets/React Flight Protocol.md | 6 +- .../React Frontend Development.md | 6 +- .../React Performance Optimization.md | 6 +- .../React Server Components (RSC).md | 6 +- ... Components(RSC) 환경의 스타일링 최적화.md | 6 +- .../UI_UX_Assets/React Server Components.md | 6 +- ...eact 기반 대규모 웹 애플리케이션 최적화.md | 6 +- ... 페이지 애플리케이션(SPA)의 렌더링 최적화.md | 6 +- .../React 기반 프론트엔드 성능 최적화.md | 6 +- ...성 훅 (useTransition, useDeferredValue).md | 6 +- .../UI_UX_Assets/React 렌더링 최적화.md | 6 +- ... 최적화 (React Performance Optimization).md | 6 +- .../React 컴파일러 (React Compiler).md | 6 +- .../UI_UX_Assets/Responsive Web Design.md | 4 +- .../Reusable UI Component Libraries.md | 6 +- .../Topics_Art/UI_UX_Assets/SCSS (Sass).md | 6 +- 10_Wiki/Topics_Art/UI_UX_Assets/SCSS.md | 4 +- .../UI_UX_Assets/Scalable Design Systems.md | 6 +- .../Scalable Frontend Design Systems.md | 6 +- .../UI_UX_Assets/Server Components.md | 6 +- .../Server-Side Rendering (SSR).md | 6 +- .../UI_UX_Assets/Styled Components v6.md | 6 +- .../UI_UX_Assets/Styled Components.md | 6 +- .../Tailwind CSS v4 CSS-first Architecture.md | 6 +- .../UI_UX_Assets/Tailwind CSS v4.md | 6 +- .../Topics_Art/UI_UX_Assets/Tailwind CSS.md | 6 +- .../UI_UX_Assets/Tailwind vs 일반 CSS 비교.md | 6 +- .../UI_UX_Assets/Time to Interactive (TTI).md | 6 +- .../UI_UX_Assets/Total Blocking Time (TBT).md | 6 +- .../Uber Base Web Design System.md | 6 +- .../UI_UX_Assets/Utility-first CSS.md | 6 +- .../Virtual DOM과 Reconciliation.md | 6 +- .../Analyze runtime performance.md | 10 +- .../UI_UX_Assets/Web & Performance/Index.md | 2 +- 10_Wiki/Topics_Art/UI_UX_Assets/shadcn-ui.md | 6 +- ...React가 빠른 이유” 및 렌더링 최적화 개념.md | 6 +- .../가상 DOM (Virtual DOM) 및 Fiber.md | 6 +- ... 재조정 (Virtual DOM and Reconciliation).md | 6 +- .../단일 페이지 애플리케이션 (SPA).md | 6 +- ...젝트의 확장성 있는 구조 및 스타일링 시스템 설계.md | 6 +- .../동시성 렌더링 (Concurrent Rendering).md | 6 +- .../디자인 시스템 (Design System).md | 6 +- .../디자인 시스템 (Design Systems).md | 6 +- .../디자인 시스템(Design System).md | 6 +- .../디자인 시스템(Design Systems).md | 6 +- .../디자인 토큰 (Design Tokens).md | 6 +- .../디자인 토큰(Design Tokens).md | 4 +- ...-개발 워크플로우(Design-to-Code Workflow).md | 6 +- ...블로킹 방지를 위한 CSS 분할 및 로딩 최적화.md | 6 +- ...링 차단 리소스(Render-blocking resources).md | 6 +- ...er 엔진 교체 및 React 18, 19의 동시성 렌더링 적용 사례.md | 6 +- .../UI_UX_Assets/모듈식 CSS(Modular CSS).md | 6 +- .../모바일 우선 설계(Mobile-First Design).md | 6 +- .../반응형 디자인(Responsive Design).md | 6 +- ...응형 웹 디자인 (Responsive Web Design).md | 6 +- ...저 렌더링 과정 (Critical Rendering Path).md | 6 +- ... 렌더링 파이프라인(Critical Rendering Path).md | 6 +- .../브라우저 렌더링 프로세스 (CRP).md | 6 +- ...우저 메인 스레드 최적화 및 타임 슬라이싱.md | 6 +- .../성능 및 SEO 최적화 프로젝트.md | 6 +- .../실무에서 CSS 관리하는 방법.md | 6 +- ...능 최적화(Web Performance Optimization).md | 6 +- ...수 가능하고 확장 가능한 CSS 아키텍처 설계.md | 6 +- ...가능한 CSS 아키텍처(CSS Modules & Tailwind).md | 6 +- ...지보수 가능한 대규모 프론트엔드 CSS 설계.md | 6 +- ...요 렌더링 경로 (Critical Rendering Path).md | 6 +- ...컬 렌더링 패스 (Critical Rendering Path).md | 4 +- ...엔드 렌더링 최적화(Rendering Optimization).md | 6 +- .../프론트엔드 성능 최적화 전략.md | 6 +- ...능 최적화(Frontend Performance Optimization).md | 6 +- ...트엔드 프레임워크 (React, Angular, Vue).md | 6 +- ... 슬라이스 디자인 (Feature-Sliced Design).md | 6 +- .../UI_UX_Assets/확장 가능한 스타일 시스템.md | 6 +- 10_Wiki/Topics_Art/UX-Design-Principles.md | 2 +- .../Topics_Art/Uber-Base-Web-Design-System.md | 2 +- 10_Wiki/Topics_Art/Universal-Grammar.md | 4 +- .../V-component (Evaluation Interface).md | 8 +- 10_Wiki/Topics_Art/V7 Draft Mode Workflow.md | 6 +- 10_Wiki/Topics_Art/Vary Region (인페인팅).md | 6 +- .../Topics_Art/Visual Regression Testing.md | 14 +- .../Topics_Art/Visual-Effects-VFX-in-Games.md | 2 +- 10_Wiki/Topics_Art/Visual-Effects-VFX.md | 4 +- 10_Wiki/Topics_Art/Visual_Effects/.gitkeep | 0 ...니메이션 성능(CSS Animation Performance).md | 6 +- ...이션 최적화(CSS Animations Optimization).md | 6 +- ...메이션 최적화(Optimizing CSS Animations).md | 6 +- .../3D Gaussian Splatting (3DGS).md | 10 +- ...E (Almost Native Graphics Layer Engine).md | 10 +- .../Graphics & Performance/ANGLE.md | 10 +- .../Agency-Narrative Integration.md | 6 +- .../Graphics & Performance/Alpha Blending.md | 8 +- .../Apple-Human-Interface-Guidelines.md | 6 +- .../Augmented Reality (AR).md | 6 +- .../Augmented Reality Navigation Systems.md | 6 +- .../Autonomous Vehicle Perception.md | 6 +- .../Graphics & Performance/BIM 모델 렌더링.md | 10 +- .../BIM 모델 시뮬레이션.md | 10 +- .../Graphics & Performance/BVH.md | 10 +- .../Graphics & Performance/Babylonjs.md | 10 +- ...chedMesh 및 InstancedMesh 성능 벤치마크.md | 10 +- .../Graphics & Performance/BatchedMesh.md | 10 +- .../Graphics & Performance/Batching.md | 10 +- ...avioral Economics in Digital Ecosystems.md | 6 +- .../Behavioral Economics.md | 6 +- .../Bio-mechanical-Modeling.md | 6 +- .../Graphics & Performance/Bioregionalism.md | 6 +- .../Bounding Volume Hierarchy (BVH).md | 10 +- .../Buffer Allocation.md | 10 +- .../Graphics & Performance/BufferAttribute.md | 10 +- .../Graphics & Performance/BufferGeometry.md | 10 +- .../Graphics & Performance/CPU Bottleneck.md | 10 +- .../Graphics & Performance/CPU Overhead.md | 10 +- .../Cel-Shading-Techniques.md | 6 +- .../Cellular Automata.md | 6 +- .../Graphics & Performance/Cesium.md | 10 +- .../Chrome (Blink_Dawn).md | 10 +- .../Chrome WebGPU 구현.md | 10 +- .../Chrome _ Blink WebGPU Implementation.md | 10 +- .../Graphics & Performance/Chrome.md | 10 +- .../Chromium WebGPU Implementation.md | 10 +- .../Cognitive Load Theory.md | 6 +- .../Cognitive-Load-Theory.md | 6 +- .../Collaborative Learning Environments.md | 6 +- .../Competitive Esports Ecosystems.md | 6 +- .../Complexity-Theory.md | 6 +- .../Computational Ecology.md | 6 +- .../Computational Geometry.md | 10 +- .../Graphics & Performance/Compute Shader.md | 8 +- .../Graphics & Performance/Compute Shaders.md | 10 +- .../Computer-Vision-Synthesis.md | 6 +- .../Creative Process.md | 6 +- .../Graphics & Performance/Critical-Play.md | 6 +- .../Cultural-Heritage-Informatics.md | 6 +- .../Graphics & Performance/CyArk.md | 6 +- .../Cybertext Theory.md | 6 +- .../Graphics & Performance/DBpedia.md | 6 +- .../Data Array Textures.md | 10 +- .../Digital Sandbox Theory.md | 6 +- .../Digital Twin Visualization.md | 6 +- .../Graphics & Performance/Direct3D.md | 10 +- .../Drama-Management-Systems.md | 6 +- .../Graphics & Performance/Draw Call.md | 10 +- .../Dual-Track-Agile.md | 6 +- ...ication] [FinTech Engagement Strategies.md | 6 +- .../Dynamic Assessment.md | 6 +- .../Dynamical Systems Theory.md | 6 +- .../EXT_disjoint_timer_query.md | 10 +- .../Ecosystem-Modeling.md | 6 +- .../EdTech (Gamified Learning).md | 6 +- .../Educational-Gamification.md | 6 +- .../Embodied Cognition in Virtual Reality.md | 6 +- .../Employee Engagement Systems.md | 6 +- .../Epidemiological Forecasting.md | 6 +- .../Epidemiological Modeling.md | 6 +- .../Expressjs-Type-Extensions.md | 6 +- .../Graphics & Performance/FXAA.md | 10 +- .../Graphics & Performance/Fill Rate.md | 10 +- .../Flow State Theory.md | 6 +- .../Graphics & Performance/Formal-Grammar.md | 6 +- .../Formalism-vs-Structuralism.md | 6 +- .../Formalist Game Design.md | 6 +- .../Fragment Shading.md | 10 +- .../Graphics & Performance/Fragment-bound.md | 10 +- .../Graphics & Performance/Frustum Culling.md | 10 +- .../Graphics & Performance/GPU Resources.md | 10 +- .../GPU for the Web Community Group.md | 10 +- .../GPU-driven Rendering.md | 10 +- .../GPURenderBundles.md | 10 +- ...라인의 미세 지연(Micro-latency) 측정 사례.md | 10 +- .../Game Studies (Academic Discipline).md | 6 +- .../Game Theory (Economics).md | 6 +- .../Game Theory and Market Equilibrium.md | 6 +- .../Graphics & Performance/Game Theory.md | 6 +- .../Gamification-Design.md | 6 +- .../Garbage Collection.md | 10 +- .../Geometry Merging.md | 10 +- .../Graph Theory in Level Design.md | 6 +- ...ead-Mounted Display) 기반 엑서게임 환경.md | 10 +- .../Graphics & Performance/HTML5 Canvas.md | 10 +- .../High Resolution Time.md | 10 +- .../Human-Centered Design.md | 6 +- .../Human-Computer-Interaction-HCI.md | 6 +- .../IFCjs (Fragment).md | 10 +- .../ISO 9241 Standards.md | 6 +- .../Immersive Educational Simulations.md | 6 +- .../Graphics & Performance/Index.md | 578 ++-- .../Graphics & Performance/Indirect Draw.md | 10 +- .../InstancedMesh (드로우 콜 최적화).md | 10 +- .../Graphics & Performance/InstancedMesh2.md | 10 +- .../Graphics & Performance/Instancing.md | 10 +- .../Instructional Systems Design (ISD).md | 6 +- .../Instructional-Design.md | 6 +- .../Interactive Storytelling.md | 6 +- .../Interactive-Storytelling.md | 6 +- .../Internet of Things (IoT) Telemetry.md | 6 +- .../Intrinsic Motivation.md | 6 +- .../Graphics & Performance/JavaScript.md | 10 +- .../Knowledge-Graphs.md | 6 +- .../Looking-Glass-Studios.md | 6 +- ...ot Box Regulation (EU_China Compliance).md | 6 +- .../Graphics & Performance/Ludology.md | 6 +- .../Graphics & Performance/MDA Framework.md | 6 +- .../Graphics & Performance/MDA-Framework.md | 6 +- .../Markov Decision Process (MDP).md | 6 +- .../Markov Decision Processes.md | 6 +- .../Mathematical Game Theory.md | 6 +- .../Graphics & Performance/Measure Theory.md | 6 +- ...Memory Leak Prevention 메모리 누수 방지.md | 10 +- .../Graphics & Performance/Memory Leaks.md | 10 +- .../Memory Management.md | 10 +- .../MeshStandardMaterial 조명 연산.md | 10 +- .../Meta Quest_Horizon OS.md | 6 +- .../Graphics & Performance/Metal.md | 10 +- .../Metaverse Architecture.md | 6 +- .../Graphics & Performance/Micro-latency.md | 10 +- .../Graphics & Performance/Minecraft.md | 6 +- .../Minecraft_ Education Edition.md | 6 +- .../Mobile Gaming Monetization Strategies.md | 6 +- .../Multi-threaded Architecture.md | 10 +- ...ropulsion-Laboratory-Software-Standards.md | 6 +- .../NVIDIA Omniverse.md | 6 +- .../Narrative-Branching-Models.md | 6 +- .../Graphics & Performance/Narratology.md | 6 +- .../Graphics & Performance/Needle Engine.md | 10 +- .../Graphics & Performance/Object Pooling.md | 10 +- .../OffscreenCanvas Safari 제약 사항.md | 10 +- ...creenCanvas 기반 멀티스레드 렌더링 구현.md | 6 +- .../Graphics & Performance/OffscreenCanvas.md | 10 +- .../Open Metaverse Framework.md | 6 +- .../Open-World Design Paradigms.md | 6 +- .../Graphics & Performance/OpenGL ES 20.md | 10 +- .../Graphics & Performance/OpenGL ES.md | 10 +- .../Graphics & Performance/Opera.md | 10 +- .../Operant Conditioning.md | 6 +- .../Graphics & Performance/PBR.md | 10 +- .../Graphics & Performance/Perlin Noise.md | 6 +- .../Physics Engine Integration.md | 6 +- .../Positive Psychology.md | 6 +- .../Positive-Psychology.md | 6 +- .../Post-Acute-Care-Models.md | 6 +- .../Graphics & Performance/Post-humanism.md | 6 +- .../Probabilistic-Graphical-Models.md | 6 +- .../Problem-Solving-Theory.md | 6 +- .../Procedural-Animation.md | 6 +- .../R3F 3D 게임 환경의 메모리 관리.md | 6 +- .../Graphics & Performance/RDF와 OWL.md | 6 +- .../Graphics & Performance/Radix Sort.md | 10 +- .../Graphics & Performance/Raycaster.md | 10 +- .../Graphics & Performance/Raycasting.md | 10 +- ...ompiler의 Threejs 런타임 성능 개선 원리.md | 10 +- .../React Three Fiber (R3F).md | 10 +- ... Fiber 자산 최적화 (Asset Optimization).md | 10 +- ...e Fiber에서 Rapier 물리 엔진 최적화하기.md | 10 +- .../React 기반 게임 엔진 아키텍처.md | 6 +- ...React 동시성 기능 (Concurrent Features).md | 6 +- .../Redux-Reducer-Pattern.md | 6 +- .../Revit glTF Export.md | 10 +- .../Revit 모델 렌더링.md | 10 +- .../Robotics-Control-Systems.md | 6 +- .../Role-Playing-Games (RPGs).md | 6 +- .../Rowhammer attack.md | 10 +- .../Graphics & Performance/Rowhammer.md | 10 +- .../Graphics & Performance/SLA-Definition.md | 6 +- .../SaaS-Retention-Strategies.md | 6 +- .../Sandbox-Simulation.md | 6 +- ...d Procedural Content Generation (SBPCG).md | 6 +- ...ntic Versioning (SemVer) in Type Safety.md | 6 +- .../Semantic-Web-Technologies.md | 6 +- .../Graphics & Performance/Semantic-Web.md | 6 +- .../Semiotics in Media.md | 6 +- .../Graphics & Performance/Sensor Fusion.md | 6 +- .../Service-Dominant-Logic.md | 6 +- .../SharedArrayBuffer.md | 10 +- .../Simulations of Social Systems.md | 6 +- ...taneous Localization and Mapping (SLAM).md | 6 +- .../Graphics & Performance/SkinnedMesh.md | 10 +- ...d Protocol 기술 메뉴얼 및 개발자 가이드.md | 6 +- .../Smart City Digital Twins.md | 6 +- .../Smart-City-Frameworks.md | 6 +- .../Graphics & Performance/Sorting.md | 10 +- .../Spatial Partitioning.md | 10 +- .../Special Education Interventions.md | 6 +- .../Spectre and Meltdown.md | 10 +- .../Speculative Biology.md | 6 +- .../Spring Framework.md | 10 +- .../Graphics & Performance/Structuralism.md | 6 +- .../Surgical-Robotics.md | 6 +- .../Systemic-Design-Frameworks.md | 6 +- .../Graphics & Performance/Systems Theory.md | 6 +- .../Graphics & Performance/TLB design.md | 10 +- .../TSL (Three Shader Language).md | 10 +- .../Graphics & Performance/Temporal-Logic.md | 6 +- .../Texture Compression.md | 10 +- .../The Rapture Setting.md | 6 +- .../The-Space-Syntax-Laboratory.md | 6 +- .../Three Shader Language (TSL).md | 10 +- .../Three.js 렌더링 최적화.md | 10 +- .../Threejs WebGL Rendering Optimization.md | 10 +- .../Threejs WebGPU 파티클 예제.md | 10 +- ...Threejs 대규모 렌더링 최적화 파이프라인.md | 10 +- .../Threejs 렌더링 성능 최적화.md | 10 +- .../Threejs 렌더링 최적화.md | 10 +- .../Threejs 모바일 렌더링 최적화.md | 10 +- .../Threejs 자원 해제 (Dispose).md | 6 +- .../Graphics & Performance/Threejs.md | 10 +- .../Timestamp Quantization.md | 10 +- .../Timestamp Queries Quantization.md | 10 +- .../Timestamp Queries.md | 10 +- .../Graphics & Performance/Turtle-Graphics.md | 6 +- .../Graphics & Performance/TypedArray.md | 10 +- .../USD - Universal Scene Description.md | 6 +- .../Graphics & Performance/UV Offset.md | 10 +- .../UX Design Gamification.md | 6 +- .../UX-Design-Architecture.md | 6 +- .../Graphics & Performance/Unity.md | 10 +- .../Urban-Resilience-Planning.md | 6 +- .../User-Story-Mapping.md | 6 +- .../Graphics & Performance/Utsubo.md | 10 +- .../VIA-Classification.md | 6 +- .../VR 엑서게임 (VR Exergaming).md | 10 +- .../Varying Variables.md | 10 +- .../Graphics & Performance/Vertex Shader.md | 10 +- .../Virtual Reality (VR) Storytelling.md | 6 +- .../Voxel-based Rendering.md | 6 +- .../Graphics & Performance/Vulkan.md | 10 +- .../WEBGL_multi_draw.md | 10 +- .../Waves of Connection.md | 10 +- .../Graphics & Performance/WebAssembly.md | 10 +- .../Graphics & Performance/WebGL 20.md | 10 +- .../Graphics & Performance/WebGL API.md | 10 +- .../WebGL Optimization.md | 10 +- .../WebGL 모바일 GPU 성능 관리.md | 10 +- .../Graphics & Performance/WebGL.md | 10 +- .../Graphics & Performance/WebGL2.md | 10 +- .../WebGLRenderingContext.md | 10 +- .../WebGPU Compute Shader.md | 10 +- .../WebGPU Compute Shaders.md | 10 +- .../WebGPU Performance Profiling.md | 10 +- .../WebGPU Timestamp Queries.md | 10 +- .../WebGPU _ WebGL Timing API Security.md | 10 +- .../WebGPU 대규모 건설 뷰어.md | 10 +- .../Graphics & Performance/WebGPU.md | 10 +- ...inning Ways for your Mathematical Plays.md | 6 +- .../Wonderland Engine.md | 10 +- .../Graphics & Performance/XState-Library.md | 6 +- .../Graphics & Performance/instancedArray.md | 10 +- .../Graphics & Performance/three-mesh-bvh.md | 10 +- .../threejs Issue _30352.md | 10 +- .../Graphics & Performance/가상현실(VR).md | 10 +- .../고성능 3D WebGL 게임 렌더링 엔진.md | 6 +- .../고성능 멀티스레드 React 앱 아키텍처.md | 10 +- .../교육 심리학 및 교수법 설계.md | 6 +- .../기업 문화 진단 및 개선.md | 6 +- .../대규모 3D 건축 모델(BIM) 시각화.md | 10 +- .../대규모 건설 뷰어(Construction Viewers).md | 10 +- .../대규모 건축물 및 지형 뷰어(BIM).md | 10 +- .../대규모 파티클 시스템 최적화.md | 10 +- .../마이크로 프론트엔드.md | 10 +- .../만성 질환 행동 수정 개입.md | 6 +- ...령형 직접 조작 (Imperative Manipulation).md | 6 +- .../모바일 기반 WebGL 애플리케이션 개발.md | 10 +- .../브라우저 그래픽 렌더링 백엔드.md | 10 +- .../서비스 디자인 (Service Design).md | 6 +- .../셰이더 정밀도 (Mediump_Highp).md | 10 +- .../스토리지 텍스처(Storage Textures).md | 10 +- .../실시간 렌더링 파이프라인.md | 10 +- .../실시간 물리 및 유체 시뮬레이션.md | 10 +- .../실시간 물리 시뮬레이션 동기화.md | 6 +- .../웹 브라우저 그래픽 API 호환성.md | 10 +- .../입자 시스템(Particle Systems).md | 10 +- .../조직 행동론의 직무 몰입 연구.md | 6 +- .../컴퓨트 셰이더(Compute Shaders).md | 10 +- .../프래그먼트 바운드(Fragment-bound).md | 10 +- .../프래그먼트 셰이딩(Fragment Shading).md | 10 +- .../헤드 마운트 디스플레이(HMD).md | 10 +- .../헤드마운트 디스플레이 (HMD).md | 10 +- .../Graphics/3D_Gaussian_Splatting.md | 10 +- .../Visual_Effects/Graphics/3D_Web_HMI.md | 10 +- .../Visual_Effects/Graphics/Digital_Twin.md | 10 +- .../Visual_Effects/Graphics/Index.md | 10 +- .../Graphics/Predictive_Maintenance.md | 10 +- .../Visual_Effects/Graphics/VPS_NeRF.md | 10 +- 10_Wiki/Topics_Art/Visual_Effects/Index.md | 24 +- ...능 중심의 웹 애니메이션 및 인터랙션 구현.md | 6 +- .../애니메이션 (transition - keyframes).md | 6 +- 10_Wiki/Topics_Art/Vocabulary-Expansion.md | 4 +- .../WARNO 그래픽 엔진 업그레이드 프로젝트.md | 4 +- 10_Wiki/Topics_Art/WARNO 데이터 기반 설계.md | 4 +- ...(Real-time Tactics) 및 Army General 캠페인.md | 4 +- .../WARNO 전술 시뮬레이션 시스템.md | 4 +- .../WARNO 커뮤니티 데이터 도구 생태계.md | 4 +- .../Topics_Art/WARNO 커뮤니티 모딩 생태계.md | 4 +- 10_Wiki/Topics_Art/WARNO.md | 4 +- 10_Wiki/Topics_Art/WME (Warno Mod Editor).md | 4 +- ...arno-Armory (커뮤니티 데이터 분석 도구).md | 4 +- .../War-Yes 및 Warno-Armory 도구.md | 4 +- 10_Wiki/Topics_Art/Warno-Armory.md | 4 +- .../Web-Rendering-Strategies-CSR-vs-SSR.md | 2 +- 10_Wiki/Topics_Art/Web3-and-AI-Integration.md | 2 +- 10_Wiki/Topics_Art/WebWorker_Performance.md | 4 +- 10_Wiki/Topics_Art/What-is-AI.md | 4 +- 10_Wiki/Topics_Art/Working-Backwards.md | 4 +- 10_Wiki/Topics_Art/Zen-Pop.md | 2 +- 10_Wiki/Topics_Art/clinicjs.md | 4 +- 10_Wiki/Topics_Art/image prompt 작성 방법.md | 6 +- ...위보 상성 (Rock-paper-scissors principle).md | 4 +- 10_Wiki/Topics_Art/가중치 (Prompt Weights).md | 4 +- .../가중치 부여(Prompt Weighting).md | 4 +- .../가중치 조절 (Prompt Weights).md | 6 +- .../긍정 프롬프트 (Positive Prompt).md | 6 +- .../네거티브 프롬프트 (Negative Prompt).md | 6 +- .../네거티브 프롬프트 (Negative Prompts).md | 6 +- .../네거티브 프롬프트(Negative Prompt).md | 6 +- .../Topics_Art/드래프트 모드 (Draft Mode).md | 6 +- .../디퓨전 모델 (Diffusion Models).md | 6 +- .../Topics_Art/리믹스 모드 (Remix Mode).md | 6 +- 10_Wiki/Topics_Art/매개변수 (Parameters).md | 6 +- 10_Wiki/Topics_Art/매개변수(Parameters).md | 6 +- ... 매개변수 제어 (Model Parameter Control).md | 6 +- ...딩 커뮤니티 도구 (War-Yes, Warno-Armory).md | 4 +- 10_Wiki/Topics_Art/미드저니 (Midjourney).md | 6 +- .../Topics_Art/미드저니 V7 (Midjourney V7).md | 6 +- ... V7 드래프트 모드 및 옴니 참조 워크플로우.md | 6 +- ...브랜드 이미지 및 텍스트 포함 콘텐츠 제작 워크플로우.md | 6 +- ... V7 및 V8 알파 (Midjourney V7 & V8.1 Alpha).md | 6 +- .../미드저니 V7 및 V8.1 Alpha 워크플로우.md | 6 +- ...미드저니 V7 및 드래프트 모드 워크플로우.md | 6 +- ...드저니 V7 업데이트 및 시각적 워크플로우.md | 6 +- ...프트 일관성 유지 (Midjourney V7 Consistency).md | 6 +- ...드저니 매개변수 (Midjourney Parameters).md | 6 +- ...개변수 제어 및 스타일 참조(Style Reference).md | 6 +- ...저니 및 스테이블 디퓨전의 부분 편집 기법.md | 6 +- ...화 (Midjourney Prompt Structuring and Optimization).md | 6 +- ...저니(Midjourney) V7 초안 기반 워크플로우.md | 6 +- .../미드저니(Midjourney) 에디터 기능.md | 6 +- .../반복적 정교화 (Iterative Refinement).md | 4 +- ... 워크플로우(Iterative Prompt Engineering Workflow).md | 6 +- .../버전 및 모델 (Versions and Models).md | 6 +- .../부정 프롬프트 (Negative Prompt).md | 6 +- .../부정 프롬프트 (Negative Prompts).md | 6 +- .../부정 프롬프트(Negative Prompt).md | 6 +- ... 활용한 시각적 아티팩트(Artifact) 디버깅 및 제어.md | 6 +- 10_Wiki/Topics_Art/사단(Division) 시스템.md | 4 +- 10_Wiki/Topics_Art/사용자 생성 콘텐츠(UGC).md | 6 +- .../Topics_Art/사후 편집 (Post-editing).md | 6 +- ... AI 이미지 품질 관리 및 워크플로우 최적화.md | 6 +- ...Commercial Marketing Campaign and Product Mockup Creation).md | 6 +- ...업용 브랜드 이미지 및 디자인 시스템 구축.md | 6 +- .../상업용 제품 사진 및 브랜드 로고 디자인.md | 4 +- .../상호작용적 프롬프트 엔지니어링.md | 6 +- .../샘플링 스텝 (Sampling Steps).md | 6 +- ...로세스 (Iterative Workflow of Generative AI Imaging).md | 6 +- .../Topics_Art/생성형 AI (Generative AI).md | 6 +- ...형 AI 워크플로우 (Generative AI Workflow).md | 6 +- ...셜 미디어 그래픽 및 마케팅 캠페인 제작.md | 6 +- ...릭터 참조 (Style and Character References).md | 6 +- .../스타일 및 캐릭터 참조(References).md | 6 +- ... 캐릭터 참조(Style and Character Reference).md | 6 +- .../스타일 참조 (Style Reference).md | 6 +- .../스타일 참조(Style Reference, --sref).md | 6 +- 10_Wiki/Topics_Art/스타일 코드.md | 6 +- .../스테이블 디퓨전 (Stable Diffusion).md | 6 +- ...테이블 디퓨전 CFG Scale 및 가중치 제어.md | 6 +- ... 디퓨전 아티팩트 디버깅(Artifact Debugging).md | 6 +- ...디퓨전(Stable Diffusion) 이미지 생성 최적화.md | 6 +- ...기반 정밀 이미지 합성 및 해부학적 오류 수정 파이프라인.md | 6 +- ...스테이블 디퓨전의 가중치 및 제어 시스템.md | 6 +- ...샷 워크플로우 (Series and Multi-shot Workflow).md | 6 +- ...지 최적화 (Stable Diffusion Image Optimization).md | 6 +- .../Topics_Art/에셋 재사용(Asset Reuse).md | 6 +- .../Topics_Art/에이전틱 AI (Agentic AI).md | 6 +- ...미지 생성 및 하드웨어 수준의 정밀 통제 워크플로우.md | 6 +- ...스 기반 맞춤형 이미지 생성 워크플로우 구축.md | 6 +- .../오픈소스 이미지 모델 미세 조정 및 배포.md | 6 +- .../Topics_Art/옴니 참조 (Omni Reference).md | 6 +- .../옴니 참조(Omni Reference, --oref).md | 6 +- .../이미지 생성 및 제어 파이프라인.md | 6 +- ...성 최적화 (Image Generation Optimization).md | 6 +- .../인-이미지 텍스트(In-Image Text).md | 6 +- ...각 언어 생성 (AI Visual Language Generation).md | 6 +- 10_Wiki/Topics_Art/인페인팅 (Inpainting).md | 6 +- .../인페인팅 (Inpainting-Vary Region).md | 6 +- ...및 드래프트 모드(Inpainting and Draft Mode).md | 6 +- ... 및 아웃페인팅 (Inpainting & Outpainting).md | 6 +- ... 및 아웃페인팅 (Inpainting and Outpainting).md | 6 +- .../일관된 캐릭터 및 스타일 구축.md | 6 +- ...연어 프롬프트 (Natural Language Prompt).md | 6 +- ...연어 프롬프트(Natural Language Prompt).md | 6 +- ... 사양 지시(Lighting and Camera Specification).md | 6 +- .../초상화 및 애니메이션 스타일 제어.md | 6 +- .../캐릭터 참조 (Character Reference).md | 6 +- .../캐릭터 참조(Character Reference).md | 6 +- 10_Wiki/Topics_Art/컨트롤넷 (ControlNet).md | 6 +- 10_Wiki/Topics_Art/컨트롤넷(ControlNet).md | 6 +- .../텍스트 렌더링(Text Rendering).md | 6 +- .../파라미터 튜닝 (Parameter Tuning).md | 4 +- .../프롬프트 가중치 (Prompt Weighting).md | 6 +- .../프롬프트 가중치 (Prompt Weights).md | 6 +- ... 프롬프트 (Prompt Weights and Negative Prompts).md | 6 +- .../프롬프트 가중치(Prompt Weighting).md | 6 +- .../프롬프트 구문 (Prompt Syntax).md | 6 +- .../프롬프트 구조 (Prompt Structure).md | 6 +- 10_Wiki/Topics_Art/프롬프트 구조 및 문법.md | 6 +- ...롬프트 엔지니어링 (Prompt Engineering).md | 6 +- .../프롬프트 엔지니어링 미세 조정.md | 6 +- ...프롬프트 엔지니어링(Prompt Engineering).md | 6 +- 10_Wiki/Topics_Art/프롬프트 엔지니어링.md | 6 +- .../Topics_Art/프롬프트 엔지니어링의 진화.md | 6 +- ...트 자동 확장 (Automatic Prompt Expansion).md | 6 +- .../프롬프트 정밀도 (Prompt Precision).md | 6 +- ... 파라미터 제어 (Prompt Parameter Control).md | 6 +- .../프롬프트 확장(Prompt Expansion).md | 6 +- .../플랫폼 저항성(Platform Resistance).md | 14 +- .../플랫폼 저항성(Platform Resistances).md | 14 +- ... 최적화 (Platform-Specific Prompt Optimization).md | 6 +- .../해부학적 오류 디버깅 워크플로우.md | 6 +- .../Topics_Art/확산 모델 (Diffusion Model).md | 6 +- .../확산 모델 (Diffusion Models).md | 6 +- .../2025 Casual Gaming Apps Report.md | 6 +- .../2026년 BCG 글로벌 게이밍 설문조사.md | 6 +- ...어 생성 패러다임 전환 및 연속적 창작 워크플로우.md | 6 +- 10_Wiki/Topics_Biz/5R Structure.md | 6 +- .../A-B-Testing-and-Data-Driven-UX.md | 2 +- 10_Wiki/Topics_Biz/A2A.md | 10 +- 10_Wiki/Topics_Biz/ACI.md | 10 +- 10_Wiki/Topics_Biz/AI & Data Sovereignty.md | 4 +- 10_Wiki/Topics_Biz/AI Accountability.md | 4 +- 10_Wiki/Topics_Biz/AI Connect LLM Tool.md | 2 +- 10_Wiki/Topics_Biz/AI Governance.md | 4 +- 10_Wiki/Topics_Biz/AI Safety (AI 안전).md | 4 +- .../AI 거버넌스 정책(AI Usage Policy).md | 4 +- 10_Wiki/Topics_Biz/AI 에이전트 (AI Agent).md | 2 +- 10_Wiki/Topics_Biz/API-Key-Management.md | 4 +- .../Topics_Biz/API_Communication_Patterns.md | 6 +- 10_Wiki/Topics_Biz/ARPU-ARPPU.md | 6 +- 10_Wiki/Topics_Biz/A_B-Testing-Platforms.md | 6 +- 10_Wiki/Topics_Biz/Abundance.md | 4 +- .../Accessibility-Compliance-Audit.md | 4 +- .../Topics_Biz/Accessibility_Inclusivity.md | 6 +- 10_Wiki/Topics_Biz/Active Learning.md | 4 +- 10_Wiki/Topics_Biz/Activism.md | 4 +- 10_Wiki/Topics_Biz/Ad-hoc-Optimization.md | 4 +- 10_Wiki/Topics_Biz/Adaptability.md | 4 +- 10_Wiki/Topics_Biz/Agent-Based Modeling.md | 6 +- 10_Wiki/Topics_Biz/Agent_Harness.md | 10 +- 10_Wiki/Topics_Biz/Agent_State_Store.md | 10 +- 10_Wiki/Topics_Biz/Agentic AI Security.md | 14 +- 10_Wiki/Topics_Biz/Agentic Coding.md | 4 +- 10_Wiki/Topics_Biz/Agentic Governance.md | 8 +- 10_Wiki/Topics_Biz/Agentic Orchestration.md | 12 +- .../Agentic_Software_Engineering.md | 10 +- 10_Wiki/Topics_Biz/Agile Environments.md | 12 +- 10_Wiki/Topics_Biz/Agile-Philosophy.md | 4 +- 10_Wiki/Topics_Biz/Algorithmic Fairness.md | 4 +- .../Algorithmic Mechanism Design.md | 6 +- 10_Wiki/Topics_Biz/Algorithmic Rhetoric.md | 6 +- 10_Wiki/Topics_Biz/AlphaZero Strategy.md | 2 +- 10_Wiki/Topics_Biz/Altruism.md | 4 +- 10_Wiki/Topics_Biz/Amygdala Hyperactivity.md | 6 +- 10_Wiki/Topics_Biz/Anarchism.md | 4 +- 10_Wiki/Topics_Biz/Anarcho-Capitalism.md | 4 +- 10_Wiki/Topics_Biz/Antifragility.md | 4 +- .../Topics_Biz/Asset-Specific-Knowledge.md | 4 +- 10_Wiki/Topics_Biz/Auction Theory.md | 6 +- ...sm Spectrum Disorder (ASD) Intervention.md | 2 +- .../Topics_Biz/Automated-Decision-Making.md | 4 +- .../Topics_Biz/Automated-Refactoring-Tools.md | 6 +- .../Topics_Biz/Automated-Security-Audits.md | 6 +- 10_Wiki/Topics_Biz/Autonomous Logging.md | 8 +- 10_Wiki/Topics_Biz/Autonomous-Agents.md | 4 +- .../Autonomous-Polling-Wait-Automation.md | 4 +- .../Topics_Biz/BCG Corporate Restructuring.md | 10 +- .../Topics_Biz/BLUF (Bottom Line Up Front).md | 10 +- 10_Wiki/Topics_Biz/Backend.md | 4 +- 10_Wiki/Topics_Biz/Behavioral Finance.md | 4 +- 10_Wiki/Topics_Biz/Behavioral Segmentation.md | 6 +- 10_Wiki/Topics_Biz/Best SAST Tools in 2026.md | 4 +- .../Best-of-N Sampling (최적 샘플링).md | 2 +- 10_Wiki/Topics_Biz/Best-of-N-Sampling.md | 4 +- .../Topics_Biz/Bias-Correction-Algorithm.md | 6 +- .../Binary-Author-Identification.md | 4 +- .../Bioinformatics-Structure-Prediction.md | 6 +- .../Biological-Inspired-Algorithms.md | 4 +- 10_Wiki/Topics_Biz/Black-Swan.md | 4 +- 10_Wiki/Topics_Biz/Blocking.md | 4 +- 10_Wiki/Topics_Biz/Blog-Post.md | 4 +- 10_Wiki/Topics_Biz/Bottom-Up Thinking.md | 10 +- 10_Wiki/Topics_Biz/Bottom-Up-Approach.md | 4 +- 10_Wiki/Topics_Biz/Boundary-Setting.md | 4 +- 10_Wiki/Topics_Biz/Branching Strategies.md | 16 +- .../Brand Consistency Maintenance.md | 6 +- 10_Wiki/Topics_Biz/Branding.md | 4 +- 10_Wiki/Topics_Biz/Budget.md | 4 +- .../Topics_Biz/Business Intelligence (BI).md | 4 +- 10_Wiki/Topics_Biz/Business Presentation.md | 10 +- .../Topics_Biz/Business Problem Solving.md | 10 +- 10_Wiki/Topics_Biz/Business Writing.md | 10 +- 10_Wiki/Topics_Biz/Business_Strategy/.gitkeep | 0 .../Business_Strategy/E-commerce Platforms.md | 4 +- .../Algorithmic Mechanism Design.md | 6 +- .../Economics & Algorithms/Auction Theory.md | 6 +- .../Economics & Algorithms/Index.md | 4 +- .../Financial Modeling & Math/Index.md | 2 +- .../Quantitative Finance.md | 10 +- 10_Wiki/Topics_Biz/Business_Strategy/Index.md | 20 +- .../Business_Strategy/Meta Quest Store.md | 6 +- .../SaaS 대시보드 및 이커머스 UI 개발.md | 6 +- ...SaaS 대시보드 및 이커머스 레이아웃 구축.md | 6 +- ...SaaS 플랫폼 및 인터랙티브 대시보드 개발.md | 6 +- ...심의 SaaS 어드민 패널 및 CRM 대시보드 구축.md | 6 +- ...스 모바일 최적화 및 상품 탐색 UX-UI 설계.md | 6 +- ...자상거래 플랫폼 (E-commerce Platforms).md | 6 +- 10_Wiki/Topics_Biz/CI_CD.md | 4 +- 10_Wiki/Topics_Biz/CPI (Cost Per Install).md | 6 +- 10_Wiki/Topics_Biz/Call Stack.md | 4 +- .../Case-Study-Allbirds-PWA-Redesign.md | 2 +- .../Case-Study-Kiwi-com-Frontend-Migration.md | 2 +- ...Case-Study-Skybound-Asset-Cache-Busting.md | 2 +- 10_Wiki/Topics_Biz/Character Consistency.md | 6 +- 10_Wiki/Topics_Biz/Character Reference.md | 6 +- 10_Wiki/Topics_Biz/Chrome DevTools.md | 4 +- .../Chronic-Pain-Management-Protocols.md | 6 +- .../Climate Change Mitigation Frameworks.md | 4 +- 10_Wiki/Topics_Biz/Code Review.md | 10 +- .../Topics_Biz/Collaboration_Governance.md | 6 +- .../Commercial AI Art Production.md | 6 +- 10_Wiki/Topics_Biz/Complex Systems.md | 6 +- 10_Wiki/Topics_Biz/Computer-Aided-Design.md | 4 +- ...Drift (개념 드리프트, 모델 지식의 부패).md | 4 +- 10_Wiki/Topics_Biz/Concept Mapping.md | 4 +- .../Topics_Biz/Connect-AI-Documentation.md | 4 +- .../ConnectAI_Core_Optimization_Plan.md | 10 +- .../Topics_Biz/ConnectAI_Dev_Log_20260429.md | 20 +- .../Constraint-Satisfaction-Problems.md | 4 +- .../Topics_Biz/Consulting Problem Solving.md | 6 +- 10_Wiki/Topics_Biz/Context_Engineering.md | 10 +- 10_Wiki/Topics_Biz/Continuous Obsolescence.md | 6 +- 10_Wiki/Topics_Biz/Corporate-LMS-Training.md | 4 +- .../Topics_Biz/Cost-Benefit Analysis in AI.md | 2 +- 10_Wiki/Topics_Biz/Curriculum-Learning.md | 2 +- 10_Wiki/Topics_Biz/Custom-Hooks-Patterns.md | 2 +- 10_Wiki/Topics_Biz/Cybernetics.md | 4 +- .../Topics_Biz/DAG-Dependency-Management.md | 4 +- 10_Wiki/Topics_Biz/DQN.md | 4 +- .../Topics_Biz/Data-Driven Personalization.md | 6 +- 10_Wiki/Topics_Biz/Data-Ethics and Privacy.md | 2 +- 10_Wiki/Topics_Biz/Data-Flywheel-Effect.md | 2 +- .../Topics_Biz/Data-Pipeline Orchestration.md | 2 +- 10_Wiki/Topics_Biz/Decision Tree.md | 6 +- 10_Wiki/Topics_Biz/Declaration-Files.md | 4 +- .../Deductive & Inductive Reasoning.md | 10 +- 10_Wiki/Topics_Biz/Deductive Reasoning.md | 6 +- .../Deductive and Inductive Reasoning.md | 6 +- .../Deductive vs. Inductive Reasoning.md | 6 +- 10_Wiki/Topics_Biz/Deep Q-Networks (DQN).md | 4 +- 10_Wiki/Topics_Biz/Deepfake-Detection.md | 4 +- 10_Wiki/Topics_Biz/DefinitelyTyped.md | 4 +- 10_Wiki/Topics_Biz/Deliberate-Practice.md | 4 +- 10_Wiki/Topics_Biz/Deployment-Strategy.md | 4 +- 10_Wiki/Topics_Biz/Deployment_Final_Gate.md | 6 +- .../Topics_Biz/DevOps_Environment_Setup.md | 2 +- .../Digital Intellectual Property Rights.md | 2 +- .../Topics_Biz/Digital Thread Integration.md | 4 +- .../Diminishing Returns (한계 수익 체감).md | 4 +- ...ted-Acyclic-Graph-Dependency-Management.md | 2 +- ...Discriminated-Unions-for-State-Modeling.md | 4 +- .../Distributed Systems & Reliability.md | 8 +- 10_Wiki/Topics_Biz/Documentation-Strategy.md | 4 +- .../Topics_Biz/Drama Management Systems.md | 4 +- 10_Wiki/Topics_Biz/Dramaturgy-Theory.md | 4 +- .../Dynamic Few-Shot (동적 퓨샷 선택 전략).md | 4 +- 10_Wiki/Topics_Biz/Dynamic Offers.md | 6 +- .../Topics_Biz/Dynamic Pricing & Offers.md | 6 +- 10_Wiki/Topics_Biz/Dynamic Pricing.md | 6 +- 10_Wiki/Topics_Biz/Dynamic-Capabilities.md | 4 +- .../E-commerce-Catalog-Management.md | 4 +- 10_Wiki/Topics_Biz/E-commerce-Optimization.md | 4 +- .../Topics_Biz/ESLint-Plugin-Development.md | 4 +- .../EU-Web-Accessibility-Directive.md | 2 +- 10_Wiki/Topics_Biz/Economic-Analysis.md | 4 +- .../Topics_Biz/Economic-Complexity-Index.md | 4 +- .../Topics_Biz/Economics-of-Information.md | 4 +- .../Topics_Biz/Effective-Altruism-in-AI.md | 4 +- 10_Wiki/Topics_Biz/Efficiency.md | 4 +- .../Elite-Strength-and-Conditioning.md | 2 +- 10_Wiki/Topics_Biz/Elite-Theory.md | 4 +- .../Encapsulation-of-Domain-Invariants.md | 2 +- .../End-to-End-Testing-Strategies.md | 4 +- 10_Wiki/Topics_Biz/Engineering_Principles.md | 10 +- 10_Wiki/Topics_Biz/Ensuring-Data-Privacy.md | 4 +- .../Topics_Biz/Enterprise-Design-Systems.md | 2 +- .../Enterprise-Resource-Planning-Systems.md | 2 +- .../Enterprise-Scale-Monorepo-Management.md | 2 +- .../Enterprise-Software-Architecture.md | 4 +- .../Enterprise-Software-Engineering.md | 4 +- .../Topics_Biz/Escalation-of-Commitment.md | 4 +- .../Ethics-in-Artificial-Intelligence.md | 4 +- .../Evolutionary-Algorithm-Design.md | 4 +- 10_Wiki/Topics_Biz/Excessive Agency.md | 8 +- 10_Wiki/Topics_Biz/Executive Briefings.md | 6 +- 10_Wiki/Topics_Biz/Executive Communication.md | 6 +- 10_Wiki/Topics_Biz/Executive Presentation.md | 6 +- .../Topics_Biz/Executive-Function-Deficit.md | 2 +- 10_Wiki/Topics_Biz/Explainable-AI (XAI).md | 4 +- .../Topics_Biz/Exploration vs Exploitation.md | 4 +- 10_Wiki/Topics_Biz/Exponential-Growth.md | 4 +- 10_Wiki/Topics_Biz/Extreme-Programming-XP.md | 2 +- .../Topics_Biz/FOMO (Fear of Missing Out).md | 6 +- .../Fact_Based_Meeting_Minutes_Prompt.md | 6 +- 10_Wiki/Topics_Biz/Failable-Task-Handling.md | 4 +- 10_Wiki/Topics_Biz/Feature-Flags.md | 4 +- .../Topics_Biz/Feedback-Loops in Systems.md | 2 +- 10_Wiki/Topics_Biz/Feedback-Loops.md | 4 +- 10_Wiki/Topics_Biz/Figma-to-Code-Workflow.md | 2 +- 10_Wiki/Topics_Biz/Finished Goods.md | 4 +- 10_Wiki/Topics_Biz/Fragility.md | 4 +- 10_Wiki/Topics_Biz/Frontend-Architecture.md | 2 +- ...ntend-Team-Collaboration-and-Governance.md | 2 +- 10_Wiki/Topics_Biz/Frontend.md | 4 +- .../Topics_Biz/Gacha Mechanics Analysis.md | 2 +- .../Game of War- Fire Age BM 구조.md | 6 +- ...e of War- Fire Age BM 및 게임 구조 분석.md | 6 +- .../Topics_Biz/Game of War- Fire Age BM.md | 6 +- 10_Wiki/Topics_Biz/Game-Balance-Design.md | 2 +- 10_Wiki/Topics_Biz/Game-Balance-Modeling.md | 2 +- 10_Wiki/Topics_Biz/Game-Loop-Architecture.md | 4 +- 10_Wiki/Topics_Biz/Game-Mechanics.md | 2 +- .../Geographic-Information-Systems.md | 4 +- 10_Wiki/Topics_Biz/Git Workflow.md | 16 +- .../Git-Branching-Strategies-and-Workflows.md | 2 +- 10_Wiki/Topics_Biz/GitHub Flow.md | 14 +- 10_Wiki/Topics_Biz/Git_Workflows.md | 10 +- 10_Wiki/Topics_Biz/Global-Standard.md | 4 +- 10_Wiki/Topics_Biz/GraphQL-Code-Generator.md | 4 +- .../Topics_Biz/Growth-Mindset-Intervention.md | 4 +- 10_Wiki/Topics_Biz/Growth-Mindset.md | 4 +- 10_Wiki/Topics_Biz/HANDOVER.md | 4 +- 10_Wiki/Topics_Biz/Hebbian-Theory.md | 4 +- 10_Wiki/Topics_Biz/Heuristics.md | 4 +- .../Topics_Biz/High-Availability-Systems.md | 2 +- .../High-Frequency-Trading-Models.md | 4 +- .../Topics_Biz/High-Performance-Coaching.md | 4 +- .../High-Performance-Organizations.md | 4 +- 10_Wiki/Topics_Biz/Horizontal Logic.md | 6 +- .../Horizontal and Vertical Logic.md | 6 +- .../Topics_Biz/Human-in-the-Loop (HITL).md | 8 +- 10_Wiki/Topics_Biz/Hypothesis Tree.md | 6 +- ...DE (Integrated Development Environment).md | 4 +- 10_Wiki/Topics_Biz/IEEE-P36521.md | 4 +- 10_Wiki/Topics_Biz/ISO-Standard.md | 4 +- .../Image Inpainting (Vary Region).md | 6 +- .../Immersive-Sims-Deus-Ex-Thief.md | 4 +- 10_Wiki/Topics_Biz/Incremental-Computation.md | 4 +- 10_Wiki/Topics_Biz/Incrementalism.md | 4 +- 10_Wiki/Topics_Biz/Index.md | 4 +- 10_Wiki/Topics_Biz/Index_1490.md | 2 +- 10_Wiki/Topics_Biz/Index_1528.md | 2 +- 10_Wiki/Topics_Biz/Index_1534.md | 2 +- 10_Wiki/Topics_Biz/Index_2.md | 16 +- 10_Wiki/Topics_Biz/Index_20.md | 10 +- 10_Wiki/Topics_Biz/Index_25.md | 12 +- 10_Wiki/Topics_Biz/Index_692.md | 2942 ++++++++--------- .../Topics_Biz/Indian-Innovation-Models.md | 4 +- .../Topics_Biz/Indirect Prompt Injection.md | 8 +- 10_Wiki/Topics_Biz/Inductive Reasoning.md | 6 +- .../Inductive and Deductive Reasoning.md | 6 +- .../Inductive vs. Deductive Reasoning.md | 6 +- .../Topics_Biz/Infrastructure-as-Code-IaC.md | 2 +- 10_Wiki/Topics_Biz/Innovation.md | 4 +- 10_Wiki/Topics_Biz/InstancedMesh2 library.md | 4 +- .../Topics_Biz/Introduction-to-Programming.md | 4 +- 10_Wiki/Topics_Biz/Inversion.md | 4 +- 10_Wiki/Topics_Biz/Issue Tree.md | 6 +- .../Iterative-Development-Models.md | 2 +- 10_Wiki/Topics_Biz/Iterative-Development.md | 4 +- .../JavaScript-Async-and-Event-Loop.md | 2 +- 10_Wiki/Topics_Biz/Just-in-Case.md | 4 +- .../KPI (Key Performance Indicator).md | 4 +- 10_Wiki/Topics_Biz/Kick-back System.md | 6 +- 10_Wiki/Topics_Biz/LTV (Lifetime Value).md | 6 +- ...scale-Application-Architecture-Patterns.md | 2 +- 10_Wiki/Topics_Biz/Leadership.md | 4 +- 10_Wiki/Topics_Biz/Lean-Operations.md | 4 +- 10_Wiki/Topics_Biz/Lean-Project-Management.md | 2 +- 10_Wiki/Topics_Biz/Learning-Paths.md | 4 +- .../Topics_Biz/Learning-Rate-Scheduling.md | 2 +- 10_Wiki/Topics_Biz/Legacy-Systems.md | 4 +- 10_Wiki/Topics_Biz/Legacy_React_Migration.md | 10 +- 10_Wiki/Topics_Biz/Lifetime Value (LTV).md | 6 +- 10_Wiki/Topics_Biz/Linear Thinking.md | 6 +- 10_Wiki/Topics_Biz/Linear-Programming.md | 4 +- 10_Wiki/Topics_Biz/Liquid-Democracy.md | 2 +- 10_Wiki/Topics_Biz/Local-Brain-Management.md | 2 +- 10_Wiki/Topics_Biz/Local-Search.md | 4 +- 10_Wiki/Topics_Biz/Logic Trees.md | 10 +- ...Logical Reasoning (Deductive-Inductive).md | 6 +- 10_Wiki/Topics_Biz/Long-Tail.md | 4 +- 10_Wiki/Topics_Biz/Loose-Coupling.md | 6 +- ...MBA (Master of Business Administration).md | 4 +- 10_Wiki/Topics_Biz/MCP.md | 10 +- .../Topics_Biz/MECE + Pyramid Principle--.md | 6 +- 10_Wiki/Topics_Biz/MECE Framework.md | 6 +- 10_Wiki/Topics_Biz/MECE Principle.md | 10 +- 10_Wiki/Topics_Biz/MECE.md | 6 +- .../Topics_Biz/Machine-Learning-Lifecycle.md | 2 +- .../Management Consulting Problem Solving.md | 6 +- 10_Wiki/Topics_Biz/Management.md | 4 +- 10_Wiki/Topics_Biz/Market Entry Strategy.md | 6 +- 10_Wiki/Topics_Biz/Market_Research/.gitkeep | 0 10_Wiki/Topics_Biz/Market_Research/Index.md | 2 +- .../Algorithmic Governance.md | 6 +- .../Algorithmic-Governance.md | 6 +- .../Market_Research/Sociology & Tech/Index.md | 4 +- .../Master-of-Information-Management.md | 4 +- .../Topics_Biz/Matrix-Operations-and-AI.md | 2 +- .../McKinsey Problem Solving Game.md | 6 +- .../McKinsey Problem Solving Test (PST).md | 6 +- .../Topics_Biz/McKinsey Problem Solving.md | 6 +- 10_Wiki/Topics_Biz/Mental Models.md | 6 +- .../Mental-Operations-Synthesized.md | 4 +- ... V6 및 V7 기반의 이미지 생성 워크플로우.md | 6 +- .../Topics_Biz/Midjourney V7 Draft Mode.md | 6 +- .../Midjourney V7 및 V6 워크플로우.md | 6 +- .../Midjourney V7의 Draft Mode 워크플로우.md | 6 +- ...djourney 브랜드 캠페인 및 무드보드 제작.md | 6 +- 10_Wiki/Topics_Biz/Minimal-Viable-Product.md | 4 +- .../Topics_Biz/Minimum-Viable-Product-MVP.md | 2 +- 10_Wiki/Topics_Biz/Minto Pyramid Principle.md | 6 +- 10_Wiki/Topics_Biz/Mipmap.md | 4 +- .../Modern_Environment_Ecosystem.md | 6 +- .../Modern_React_Engineering_2025.md | 10 +- 10_Wiki/Topics_Biz/Modular-Programming.md | 6 +- 10_Wiki/Topics_Biz/Modularity.md | 4 +- 10_Wiki/Topics_Biz/Monetization (BM).md | 6 +- 10_Wiki/Topics_Biz/Monetization Strategy.md | 6 +- .../Monetization at the Point of Friction.md | 6 +- 10_Wiki/Topics_Biz/Moodboard Creation.md | 6 +- .../Multi-Agent-Reinforcement-Learning.md | 2 +- ...sive and Collectively Exhaustive (MECE).md | 6 +- .../Neural-Architecture-Search-NAS.md | 2 +- .../Topics_Biz/Neural-Architecture-Search.md | 2 +- 10_Wiki/Topics_Biz/Neural-Darwinism.md | 2 +- .../Neurodevelopmental Disorders.md | 4 +- 10_Wiki/Topics_Biz/Neuroevolution.md | 2 +- .../Neuroplasticity in Motor Learning.md | 4 +- .../Neuroplasticity-in-Motor-Learning.md | 4 +- .../Neuroprosthetics-Development.md | 4 +- 10_Wiki/Topics_Biz/Next-js-and-Modern-Web.md | 2 +- .../Topics_Biz/Nuclear Deterrence Models.md | 4 +- 10_Wiki/Topics_Biz/OKR.md | 4 +- 10_Wiki/Topics_Biz/OWASP Top 10.md | 16 +- .../Object Pooling (오브젝트 풀링).md | 4 +- .../Object-Oriented-Design-Patterns.md | 4 +- 10_Wiki/Topics_Biz/Omni Reference (--oref).md | 6 +- 10_Wiki/Topics_Biz/Omni Reference.md | 6 +- 10_Wiki/Topics_Biz/Ontology-Engineering.md | 4 +- 10_Wiki/Topics_Biz/OpenAI-API-Integration.md | 2 +- 10_Wiki/Topics_Biz/Operations-Management.md | 2 +- 10_Wiki/Topics_Biz/Operations-Research.md | 4 +- 10_Wiki/Topics_Biz/Operations/.gitkeep | 0 .../Automation & Industry/3D Web-based HMI.md | 10 +- .../Operations/Automation & Industry/Index.md | 2 +- .../Autonomous Logging.md | 10 +- .../Governance & Reliability/Index.md | 4 +- .../Session Lifecycle.md | 10 +- 10_Wiki/Topics_Biz/Operations/Index.md | 6 +- .../Security & Reliability/Index.md | 2 +- .../Security & Reliability/OWASP Top 10.md | 10 +- .../Topics_Biz/Organizational Psychology.md | 4 +- 10_Wiki/Topics_Biz/P-Reinforce_1011.md | 4 +- 10_Wiki/Topics_Biz/PEV_Loop.md | 10 +- 10_Wiki/Topics_Biz/PMI-Technique.md | 4 +- 10_Wiki/Topics_Biz/Parallel-Processing.md | 4 +- 10_Wiki/Topics_Biz/Partnerships/.gitkeep | 0 10_Wiki/Topics_Biz/Perceptual-Learning.md | 2 +- 10_Wiki/Topics_Biz/Perceptual-Motor-Skills.md | 4 +- .../Performance Management Systems.md | 4 +- .../Topics_Biz/Personal-Brain-Management.md | 2 +- .../Topics_Biz/Persuasive Business Writing.md | 6 +- 10_Wiki/Topics_Biz/Pivot-Table-Analysis.md | 2 +- 10_Wiki/Topics_Biz/Point-of-Sale.md | 4 +- 10_Wiki/Topics_Biz/Policy-Surveillance.md | 4 +- 10_Wiki/Topics_Biz/Practical-Cryptography.md | 2 +- 10_Wiki/Topics_Biz/Pre-Mortem-Analysis.md | 4 +- 10_Wiki/Topics_Biz/Predictive-Analytics.md | 2 +- 10_Wiki/Topics_Biz/Prenatal-Neurology.md | 4 +- .../Preserving-State-in-Procedural-Worlds.md | 4 +- .../Topics_Biz/Principles-of-Data-Connect.md | 4 +- .../Topics_Biz/Prisoners-Dilemma-Models.md | 4 +- 10_Wiki/Topics_Biz/Problem Solving Game.md | 6 +- 10_Wiki/Topics_Biz/Problem Solving Process.md | 6 +- 10_Wiki/Topics_Biz/Problem Solving Skills.md | 6 +- .../Topics_Biz/Problem Solving Test (PST).md | 6 +- 10_Wiki/Topics_Biz/Problem Solving.md | 6 +- 10_Wiki/Topics_Biz/Problem-Solving.md | 4 +- .../Topics_Biz/Process-Automation-with-AI.md | 2 +- 10_Wiki/Topics_Biz/Product-Led-Growth.md | 4 +- 10_Wiki/Topics_Biz/Product-Management.md | 4 +- 10_Wiki/Topics_Biz/Product-Marketing.md | 4 +- 10_Wiki/Topics_Biz/Product-Thinking-in-AI.md | 2 +- .../Topics_Biz/Productivity-Hacks-for-Devs.md | 2 +- 10_Wiki/Topics_Biz/Profitability Framework.md | 6 +- .../Project-Management-Best-Practices.md | 2 +- 10_Wiki/Topics_Biz/Project-Management.md | 4 +- .../Ps-Reinforce Policy Framework.md | 4 +- 10_Wiki/Topics_Biz/Pull-Request.md | 4 +- 10_Wiki/Topics_Biz/PyTorch-Foundations.md | 2 +- 10_Wiki/Topics_Biz/Pyramid Principle.md | 6 +- .../Topics_Biz/Queue-Management-Systems.md | 2 +- 10_Wiki/Topics_Biz/Quick-Wins.md | 4 +- 10_Wiki/Topics_Biz/RAG.md | 10 +- 10_Wiki/Topics_Biz/Randomized-Algorithms.md | 2 +- 10_Wiki/Topics_Biz/Rapid-Prototyping.md | 4 +- 10_Wiki/Topics_Biz/React-Context-API.md | 2 +- .../React-Error-Boundaries-and-Handling.md | 2 +- 10_Wiki/Topics_Biz/React-Hooks.md | 2 +- 10_Wiki/Topics_Biz/React_Hooks_Deep_Dive.md | 6 +- .../React_State_Management_Strategy.md | 6 +- 10_Wiki/Topics_Biz/React_Testing_Strategy.md | 6 +- 10_Wiki/Topics_Biz/Real-Time Translation.md | 6 +- 10_Wiki/Topics_Biz/Real-time-Operation.md | 4 +- 10_Wiki/Topics_Biz/Reasoning & Planning.md | 12 +- 10_Wiki/Topics_Biz/Recommendation-Systems.md | 2 +- 10_Wiki/Topics_Biz/Reference-Management.md | 4 +- .../Relational Algebra in Databases.md | 4 +- .../Topics_Biz/Reliability_Safety_First.md | 6 +- 10_Wiki/Topics_Biz/Remote-Rehabilitation.md | 4 +- 10_Wiki/Topics_Biz/Replenishment.md | 4 +- 10_Wiki/Topics_Biz/Repository.md | 4 +- 10_Wiki/Topics_Biz/Research-Framework.md | 4 +- 10_Wiki/Topics_Biz/Resilience.md | 4 +- 10_Wiki/Topics_Biz/Resource-Allocation.md | 4 +- 10_Wiki/Topics_Biz/Resource-Management.md | 4 +- .../Retrieval-Augmented-Generation-RAG.md | 2 +- 10_Wiki/Topics_Biz/Risk Management.md | 4 +- 10_Wiki/Topics_Biz/Risk-Assessment-with-AI.md | 2 +- 10_Wiki/Topics_Biz/Risk-Management.md | 4 +- 10_Wiki/Topics_Biz/Risk-Orchestration.md | 4 +- 10_Wiki/Topics_Biz/Roadmap.md | 4 +- 10_Wiki/Topics_Biz/Rule of Three.md | 6 +- 10_Wiki/Topics_Biz/SAR.md | 4 +- .../SCM (Supply Chain Management).md | 4 +- 10_Wiki/Topics_Biz/SCQA Framework.md | 6 +- 10_Wiki/Topics_Biz/SEO.md | 2 +- 10_Wiki/Topics_Biz/SOW.md | 4 +- 10_Wiki/Topics_Biz/SPOF.md | 4 +- 10_Wiki/Topics_Biz/SaaS.md | 4 +- 10_Wiki/Topics_Biz/Sales-Strategy.md | 4 +- 10_Wiki/Topics_Biz/Scalability.md | 4 +- .../Scalable-Design-System-Governance.md | 2 +- 10_Wiki/Topics_Biz/Scaling-Laws-for-LLMs.md | 2 +- .../Topics_Biz/Search-Engine-Optimization.md | 2 +- 10_Wiki/Topics_Biz/Search-Methodology.md | 4 +- 10_Wiki/Topics_Biz/Search-Strategy.md | 4 +- 10_Wiki/Topics_Biz/Security-Best-Practices.md | 2 +- 10_Wiki/Topics_Biz/Security-Governance.md | 6 +- 10_Wiki/Topics_Biz/Self-verification.md | 8 +- .../Topics_Biz/Semantic-HTML-Foundations.md | 2 +- 10_Wiki/Topics_Biz/Sensitivity-Analysis.md | 4 +- .../Topics_Biz/Serverless-Computing-for-AI.md | 2 +- 10_Wiki/Topics_Biz/Session Lifecycle.md | 8 +- 10_Wiki/Topics_Biz/Shift.md | 4 +- 10_Wiki/Topics_Biz/Signature Style Design.md | 6 +- 10_Wiki/Topics_Biz/Single_Source_of_Truth.md | 4 +- 10_Wiki/Topics_Biz/Six-Sigma-Methodologies.md | 2 +- .../Topics_Biz/Skybound Protocol 코드리뷰.md | 2 +- 10_Wiki/Topics_Biz/Slack-Bot-Development.md | 2 +- 10_Wiki/Topics_Biz/Soft-Skills-Development.md | 4 +- .../Software Engineering Agents (SWE).md | 8 +- .../Software-Architecture-Patterns.md | 2 +- 10_Wiki/Topics_Biz/Solow Growth Model.md | 4 +- 10_Wiki/Topics_Biz/Specification.md | 4 +- 10_Wiki/Topics_Biz/Stages-of-Grief.md | 4 +- 10_Wiki/Topics_Biz/Stakeholder.md | 4 +- .../Standard-Operating-Procedure.md | 4 +- .../Standardization vs Innovation.md | 4 +- 10_Wiki/Topics_Biz/Startup.md | 4 +- ...e-Management-Architecture-and-Ownership.md | 2 +- .../Topics_Biz/State-Management-Patterns.md | 2 +- 10_Wiki/Topics_Biz/Storage.md | 4 +- .../Topics_Biz/Storytelling in Business.md | 10 +- 10_Wiki/Topics_Biz/Strategic Communication.md | 10 +- 10_Wiki/Topics_Biz/Strategic Thinking.md | 10 +- 10_Wiki/Topics_Biz/Strategic-Alignment.md | 2 +- 10_Wiki/Topics_Biz/Strategic-Ambiguity.md | 4 +- .../Topics_Biz/Strategic-Planning-for-AI.md | 2 +- 10_Wiki/Topics_Biz/Strategic-Planning.md | 4 +- 10_Wiki/Topics_Biz/Strategic-Thinking.md | 2 +- 10_Wiki/Topics_Biz/Strategy.md | 4 +- 10_Wiki/Topics_Biz/Structural Reasoning.md | 6 +- .../Topics_Biz/Style Reference (--sref).md | 8 +- 10_Wiki/Topics_Biz/Styling_Governance.md | 6 +- 10_Wiki/Topics_Biz/Sustainability.md | 4 +- 10_Wiki/Topics_Biz/Synthetic-Data.md | 4 +- 10_Wiki/Topics_Biz/System-Theory.md | 4 +- .../Topics_Biz/System_Debugging_Protocol.md | 4 +- .../Topics_Biz/System_Protocol_Standard.md | 2 +- 10_Wiki/Topics_Biz/TDD.md | 4 +- .../Topics_Biz/Tableau-Data-Visualization.md | 2 +- 10_Wiki/Topics_Biz/Task-Management.md | 4 +- 10_Wiki/Topics_Biz/Team Collaboration.md | 18 +- 10_Wiki/Topics_Biz/Technical-Debt.md | 4 +- .../Topics_Biz/Theory of Constraints (TOC).md | 4 +- .../Topics_Biz/Time-Step-Logic-in-Games.md | 2 +- 10_Wiki/Topics_Biz/Tripledot Studios.md | 6 +- 10_Wiki/Topics_Biz/Trustworthy-AI.md | 2 +- .../Topics_Biz/Uber-Base-Web-Design-System.md | 2 +- 10_Wiki/Topics_Biz/Ultra-Efficiency.md | 4 +- 10_Wiki/Topics_Biz/User Acquisition (UA).md | 6 +- 10_Wiki/Topics_Biz/V7 Draft Mode Workflow.md | 6 +- 10_Wiki/Topics_Biz/Vary Region (인페인팅).md | 6 +- 10_Wiki/Topics_Biz/Version Control.md | 16 +- .../Viral-Dynamics-and-Network-Effects.md | 4 +- .../Topics_Biz/Visual-Effects-VFX-in-Games.md | 2 +- .../Voice-Assistant-Architecture.md | 2 +- ...ARNO 사후 관리 (Post-Launch Management).md | 4 +- 10_Wiki/Topics_Biz/Whale Hunting.md | 6 +- .../Topics_Biz/Willingness to Pay (WTP).md | 6 +- 10_Wiki/Topics_Biz/Work-Displacement.md | 4 +- 10_Wiki/Topics_Biz/Workflow-Integrity.md | 4 +- ...버-그레인저 방법 (Gabor-Granger Method).md | 4 +- ...게임 수익화 전략(Monetization Strategy).md | 6 +- 10_Wiki/Topics_Biz/게임 수익화 전략.md | 6 +- .../결제 사용자당 평균 매출(ARPPU).md | 6 +- 10_Wiki/Topics_Biz/고객 평생 가치(LTV).md | 6 +- .../공급망 공격 (Supply Chain Attack).md | 4 +- .../과금 의향 (Willingness to Pay).md | 6 +- ...화 전략 분석 및 가상 경제 시스템 검증 프로젝트.md | 6 +- ...비스 아키텍처 (Microservices Architecture).md | 4 +- ...춤형 IAP 번들(Customizable IAP bundles).md | 6 +- ... 수익화 (Dynamic Offers & Staircase Monetization).md | 6 +- .../매몰 비용 오류 (Sunk Cost Fallacy).md | 6 +- ...일 게임 수익화(Mobile Game Monetization).md | 6 +- ...주얼 게임 시장(Mobile Casual Game Market).md | 6 +- ... 확장성 경제 (Infinitely Scalable Economy).md | 6 +- ... V7 드래프트 모드 및 옴니 참조 워크플로우.md | 6 +- ... V7 및 V8 알파 (Midjourney V7 & V8.1 Alpha).md | 6 +- .../미드저니 V7 및 V8.1 Alpha 워크플로우.md | 6 +- ...프트 일관성 유지 (Midjourney V7 Consistency).md | 6 +- .../Topics_Biz/미세결제(Microtransactions).md | 6 +- .../버전 및 모델 (Versions and Models).md | 6 +- ...상의 역효과 (Overjustification Effect).md | 6 +- .../사용자 확보 (User Acquisition).md | 6 +- ...Commercial Marketing Campaign and Product Mockup Creation).md | 6 +- ...업용 브랜드 이미지 및 디자인 시스템 구축.md | 6 +- .../상업용 제품 사진 및 브랜드 로고 디자인.md | 4 +- ...셜 미디어 그래픽 및 마케팅 캠페인 제작.md | 6 +- .../소셜 엔지니어링 (Social Engineering).md | 6 +- .../소액 결제 (Microtransactions).md | 6 +- 10_Wiki/Topics_Biz/수익화(Monetization).md | 6 +- ...릭터 참조 (Style and Character References).md | 6 +- .../스타일 및 캐릭터 참조(References).md | 6 +- ... 캐릭터 참조(Style and Character Reference).md | 6 +- .../스타일 참조(Style Reference, --sref).md | 6 +- ...샷 워크플로우 (Series and Multi-shot Workflow).md | 6 +- ... 척도 연구(In-Game Purchase Motivation Scale Study).md | 6 +- 10_Wiki/Topics_Biz/악명(Infamy) 시스템.md | 6 +- 10_Wiki/Topics_Biz/오디오 광고.md | 6 +- .../옴니 참조(Omni Reference, --oref).md | 6 +- .../Topics_Biz/유니버스 LTV(Universe LTV).md | 6 +- .../Topics_Biz/유닛 이코노믹스(LTV와 CAC).md | 6 +- 10_Wiki/Topics_Biz/유저 평균 매출(ARPU).md | 6 +- 10_Wiki/Topics_Biz/이커머스 플랫폼.md | 6 +- .../인-이미지 텍스트(In-Image Text).md | 6 +- ...임 결제 동기(In-Game Purchase Motivation).md | 10 +- .../인게임 수익화(In-Game Monetization).md | 6 +- 10_Wiki/Topics_Biz/인앱 광고 (IAA).md | 6 +- 10_Wiki/Topics_Biz/인앱 광고(IAA).md | 6 +- 10_Wiki/Topics_Biz/인앱 구매 (IAP).md | 6 +- 10_Wiki/Topics_Biz/인앱 구매(IAP).md | 6 +- .../인페인팅 (Inpainting-Vary Region).md | 6 +- .../자원 로지스틱스(Resource Logistics).md | 6 +- ...관 및 압축(Resource Storage & Compression).md | 6 +- ... 사양 지시(Lighting and Camera Specification).md | 6 +- .../지불 용의 (Willingness to Pay).md | 6 +- .../캐릭터 참조 (Character Reference).md | 6 +- .../파라미터 튜닝 (Parameter Tuning).md | 4 +- .../프리미엄 모델 (Freemium Model).md | 6 +- 10_Wiki/Topics_Biz/하이브리드 수익화 모델.md | 6 +- .../하이브리드 수익화(Hybrid Monetization).md | 6 +- .../Topics_Blog/10v10 대규모 멀티플레이어.md | 4 +- .../2025 Casual Gaming Apps Report.md | 6 +- .../2026년 BCG 글로벌 게이밍 설문조사.md | 6 +- ...어 생성 패러다임 전환 및 연속적 창작 워크플로우.md | 6 +- .../Topics_Blog/20k skinned instances demo.md | 4 +- .../A-B-Testing-and-Data-Driven-UX.md | 2 +- 10_Wiki/Topics_Blog/A2A.md | 10 +- 10_Wiki/Topics_Blog/ABA.md | 2 +- 10_Wiki/Topics_Blog/ACI.md | 10 +- 10_Wiki/Topics_Blog/AGI.md | 2 +- 10_Wiki/Topics_Blog/AI & Data Sovereignty.md | 4 +- 10_Wiki/Topics_Blog/AI Accountability.md | 4 +- 10_Wiki/Topics_Blog/AI Agents.md | 2 +- 10_Wiki/Topics_Blog/AI Connect LLM Tool.md | 2 +- 10_Wiki/Topics_Blog/AI Governance.md | 4 +- 10_Wiki/Topics_Blog/AI Humanism.md | 4 +- 10_Wiki/Topics_Blog/AI Literacy.md | 4 +- 10_Wiki/Topics_Blog/AI Safety (AI 안전).md | 4 +- 10_Wiki/Topics_Blog/AI Safety.md | 4 +- 10_Wiki/Topics_Blog/AI and Narrative.md | 4 +- 10_Wiki/Topics_Blog/AI for Social Good.md | 4 +- .../AI 거버넌스 정책(AI Usage Policy).md | 4 +- .../AI 생성 코드 검증(AI Code Assurance).md | 4 +- 10_Wiki/Topics_Blog/AI 에이전트 (AI Agent).md | 2 +- ... 워크플로우 (AI Image Generation Workflow).md | 6 +- ... 디버깅 (Image Quality Optimization & Debugging).md | 6 +- ...드 리뷰 및 보안 취약점 점검(DevSecOps).md | 4 +- 10_Wiki/Topics_Blog/AI 코드 리뷰.md | 6 +- 10_Wiki/Topics_Blog/AI-Alignment.md | 2 +- .../AI-Driven Narrative Systems.md | 2 +- 10_Wiki/Topics_Blog/AI-Overviews-and-SGE.md | 2 +- .../AI-Personalization-and-Adaptive-UX.md | 2 +- 10_Wiki/Topics_Blog/AI-Search-Optimization.md | 2 +- ...열 맡기기_ - 정적 분석 툴 (ESLint Prettier)).md | 4 +- ... 모델링 및 상태 머신(State Machine) 설계.md | 4 +- .../Topics_Blog/API-Design for AI Services.md | 2 +- 10_Wiki/Topics_Blog/API-Key-Management.md | 4 +- .../API-backed Image Generation Workflow.md | 6 +- .../Topics_Blog/API_Communication_Patterns.md | 6 +- 10_Wiki/Topics_Blog/A_B-Testing-Platforms.md | 6 +- 10_Wiki/Topics_Blog/Abundance.md | 4 +- 10_Wiki/Topics_Blog/Academic-Integrity.md | 4 +- .../Accessibility-Compliance-Audit.md | 4 +- .../Topics_Blog/Accessibility_Inclusivity.md | 6 +- 10_Wiki/Topics_Blog/Active Learning.md | 4 +- 10_Wiki/Topics_Blog/Active-Reasoning.md | 4 +- 10_Wiki/Topics_Blog/Activism.md | 4 +- 10_Wiki/Topics_Blog/Actor-Critic-Models.md | 4 +- 10_Wiki/Topics_Blog/Ad-hoc-Hypotheses.md | 4 +- 10_Wiki/Topics_Blog/Ad-hoc-Optimization.md | 4 +- 10_Wiki/Topics_Blog/Adaptability.md | 4 +- .../Adaptive Compute (적응형 계산량 조절).md | 12 +- .../Adaptive Context Compaction.md | 8 +- 10_Wiki/Topics_Blog/Adaptive-Curation.md | 6 +- .../Topics_Blog/Advanced-Interface-Design.md | 4 +- .../Adversarial Code Stylometry.md | 4 +- 10_Wiki/Topics_Blog/Aesthetic-Value.md | 4 +- 10_Wiki/Topics_Blog/Affective Computing.md | 2 +- 10_Wiki/Topics_Blog/Affordance.md | 4 +- 10_Wiki/Topics_Blog/Agent Architecture.md | 4 +- 10_Wiki/Topics_Blog/Agent Memory System.md | 8 +- 10_Wiki/Topics_Blog/Agent Personality.md | 4 +- 10_Wiki/Topics_Blog/Agent_Harness.md | 10 +- 10_Wiki/Topics_Blog/Agent_State_Store.md | 10 +- 10_Wiki/Topics_Blog/Agentic Coding.md | 4 +- 10_Wiki/Topics_Blog/Agentic Creative Era.md | 6 +- .../Agentic_Software_Engineering.md | 10 +- 10_Wiki/Topics_Blog/Agile-Philosophy.md | 4 +- 10_Wiki/Topics_Blog/Alcoholism.md | 4 +- .../Topics_Blog/Algorithm-Complexity-Big-O.md | 2 +- 10_Wiki/Topics_Blog/Algorithmic Fairness.md | 4 +- 10_Wiki/Topics_Blog/Algorithmic Rhetoric.md | 6 +- .../Topics_Blog/Algorithmic Transparency.md | 4 +- 10_Wiki/Topics_Blog/Algorithmic-Biology.md | 4 +- .../Topics_Blog/Algorithmic-Game-Theory.md | 4 +- 10_Wiki/Topics_Blog/Alignment.md | 4 +- 10_Wiki/Topics_Blog/AlphaZero Strategy.md | 2 +- 10_Wiki/Topics_Blog/Alternative Realities.md | 4 +- 10_Wiki/Topics_Blog/Altruism.md | 4 +- 10_Wiki/Topics_Blog/Ambient-Declarations.md | 6 +- 10_Wiki/Topics_Blog/Ambition.md | 4 +- .../Topics_Blog/Amdahls Law (암달의 법칙).md | 4 +- 10_Wiki/Topics_Blog/Analogical-Reasoning.md | 4 +- 10_Wiki/Topics_Blog/Analogy.md | 4 +- 10_Wiki/Topics_Blog/Analysis.md | 4 +- 10_Wiki/Topics_Blog/Anarchism.md | 4 +- 10_Wiki/Topics_Blog/Anarcho-Capitalism.md | 4 +- 10_Wiki/Topics_Blog/Anarcho-Primitivism.md | 4 +- 10_Wiki/Topics_Blog/Anisomorphism.md | 4 +- 10_Wiki/Topics_Blog/Anomaly-Detection.md | 4 +- 10_Wiki/Topics_Blog/Anthropic-Principle.md | 2 +- 10_Wiki/Topics_Blog/Anthropomorphism.md | 4 +- 10_Wiki/Topics_Blog/Anticipation.md | 4 +- 10_Wiki/Topics_Blog/Antifragility.md | 4 +- 10_Wiki/Topics_Blog/Antinomianism.md | 4 +- 10_Wiki/Topics_Blog/Anxiety.md | 4 +- .../Topics_Blog/Arguing-by-Counterexample.md | 4 +- .../Arrangement-and-Composition.md | 4 +- 10_Wiki/Topics_Blog/Articulateness.md | 4 +- .../Artificial General Intelligence (AGI).md | 4 +- .../Artificial Intelligence (AI).md | 4 +- .../Artificial-Intelligence-in-Games.md | 6 +- .../Topics_Blog/Artificial-Intelligence.md | 2 +- 10_Wiki/Topics_Blog/Artificial-Life.md | 2 +- 10_Wiki/Topics_Blog/Arts.md | 4 +- 10_Wiki/Topics_Blog/Assertiveness.md | 4 +- 10_Wiki/Topics_Blog/Assessment.md | 4 +- .../Topics_Blog/Asset-Specific-Knowledge.md | 4 +- 10_Wiki/Topics_Blog/Assumptions-vs-Facts.md | 4 +- 10_Wiki/Topics_Blog/Atheism.md | 4 +- 10_Wiki/Topics_Blog/Atlantic.md | 4 +- .../Topics_Blog/Atmospheric-Intelligence.md | 4 +- .../Atomic-Design-System-Architecture.md | 2 +- .../Atomic-Styling-and-Design-Systems.md | 2 +- 10_Wiki/Topics_Blog/Atomism.md | 4 +- 10_Wiki/Topics_Blog/Attention Mechanisms.md | 4 +- .../Topics_Blog/Attention is All You Need.md | 2 +- 10_Wiki/Topics_Blog/Authenticity.md | 4 +- ...sm Spectrum Disorder (ASD) Intervention.md | 2 +- 10_Wiki/Topics_Blog/Auto-Encoding.md | 4 +- .../Auto-GPT and Autonomous Agents.md | 2 +- 10_Wiki/Topics_Blog/Autobiography.md | 4 +- 10_Wiki/Topics_Blog/Autoethnography.md | 4 +- .../Topics_Blog/Automated-Decision-Making.md | 4 +- 10_Wiki/Topics_Blog/Automated-Game-Testing.md | 4 +- .../Topics_Blog/Automated-Map-Generation.md | 6 +- 10_Wiki/Topics_Blog/Automated-Reasoning.md | 4 +- .../Automated-Refactoring-Tools.md | 6 +- .../Topics_Blog/Automated-Security-Audits.md | 6 +- .../Topics_Blog/Automated-Theorem-Proving.md | 4 +- 10_Wiki/Topics_Blog/Automated_Mapping.md | 2 +- 10_Wiki/Topics_Blog/Automation-Paradox.md | 4 +- 10_Wiki/Topics_Blog/Autonomous Vehicles.md | 4 +- 10_Wiki/Topics_Blog/Autonomous-Agents.md | 4 +- .../Autonomous-Polling-Wait-Automation.md | 4 +- .../Autonomous-Vehicle-Path-Planning.md | 6 +- .../Availability-and-Persistence.md | 4 +- 10_Wiki/Topics_Blog/Awards.md | 4 +- 10_Wiki/Topics_Blog/Axify.md | 2 +- 10_Wiki/Topics_Blog/Axiology.md | 4 +- 10_Wiki/Topics_Blog/Axiomatic-Systems.md | 4 +- 10_Wiki/Topics_Blog/Axioms.md | 4 +- 10_Wiki/Topics_Blog/Azure DevOps.md | 4 +- 10_Wiki/Topics_Blog/B-Tree.md | 4 +- 10_Wiki/Topics_Blog/BERT.md | 2 +- 10_Wiki/Topics_Blog/BFS vs DFS.md | 4 +- .../BLUF (Bottom Line Up Front).md | 10 +- 10_Wiki/Topics_Blog/Backend.md | 4 +- .../Backpropagation Through Time.md | 2 +- 10_Wiki/Topics_Blog/Backpropagation.md | 4 +- 10_Wiki/Topics_Blog/Backups.md | 4 +- 10_Wiki/Topics_Blog/Backward-Reasoning.md | 4 +- 10_Wiki/Topics_Blog/Bag of Words (BoW).md | 4 +- 10_Wiki/Topics_Blog/Baseline Project.md | 2 +- 10_Wiki/Topics_Blog/Batch-Inference.md | 4 +- 10_Wiki/Topics_Blog/Bayes-Theorem.md | 4 +- 10_Wiki/Topics_Blog/Bayesian Inference.md | 4 +- 10_Wiki/Topics_Blog/Bayesian Statistics.md | 4 +- .../Topics_Blog/Bayesian-Brain-Hypothesis.md | 2 +- 10_Wiki/Topics_Blog/Bayesian-Updating.md | 4 +- 10_Wiki/Topics_Blog/Be-Detailed.md | 4 +- 10_Wiki/Topics_Blog/Beckett.md | 4 +- 10_Wiki/Topics_Blog/Behavior.md | 4 +- 10_Wiki/Topics_Blog/Behavioral Finance.md | 4 +- 10_Wiki/Topics_Blog/Behavioral-Economics.md | 2 +- 10_Wiki/Topics_Blog/Behavioral-Incentives.md | 4 +- 10_Wiki/Topics_Blog/Belief-Revision.md | 4 +- 10_Wiki/Topics_Blog/Belief-System.md | 4 +- 10_Wiki/Topics_Blog/Beliefs.md | 4 +- 10_Wiki/Topics_Blog/Bellman Equation.md | 4 +- 10_Wiki/Topics_Blog/Bellman-Equation.md | 6 +- 10_Wiki/Topics_Blog/Benchmarks.md | 4 +- 10_Wiki/Topics_Blog/Bert-Language-Model.md | 6 +- .../Topics_Blog/Best SAST Tools in 2026.md | 4 +- .../Topics_Blog/Best-of-N Sampling ( ø).md | 4 +- .../Best-of-N Sampling (최적 샘플링).md | 2 +- 10_Wiki/Topics_Blog/Best-of-N Sampling.md | 4 +- 10_Wiki/Topics_Blog/Best-of-N-Sampling.md | 4 +- 10_Wiki/Topics_Blog/Bias vs Variance.md | 4 +- .../Topics_Blog/Bias-Correction-Algorithm.md | 6 +- 10_Wiki/Topics_Blog/Bias-Variance-Tradeoff.md | 6 +- 10_Wiki/Topics_Blog/Bible.md | 4 +- 10_Wiki/Topics_Blog/Bibliometrics.md | 4 +- 10_Wiki/Topics_Blog/Big-Data.md | 4 +- 10_Wiki/Topics_Blog/Big-Picture.md | 4 +- .../Binary-Author-Identification.md | 4 +- 10_Wiki/Topics_Blog/Binary-Search.md | 4 +- 10_Wiki/Topics_Blog/BioShock (2007).md | 4 +- 10_Wiki/Topics_Blog/BioShock-Critique.md | 6 +- 10_Wiki/Topics_Blog/Bioenergetics.md | 6 +- .../Bioinformatics-Structure-Prediction.md | 6 +- .../Biological-Inspired-Algorithms.md | 4 +- .../Topics_Blog/Biological-Intelligence.md | 4 +- 10_Wiki/Topics_Blog/Biomechanics-of-Injury.md | 6 +- 10_Wiki/Topics_Blog/Biometrics.md | 6 +- 10_Wiki/Topics_Blog/Black-Box-Optimization.md | 2 +- 10_Wiki/Topics_Blog/Black-Hole.md | 4 +- 10_Wiki/Topics_Blog/Black-Swan.md | 4 +- 10_Wiki/Topics_Blog/Blockchain.md | 4 +- 10_Wiki/Topics_Blog/Blocking.md | 4 +- 10_Wiki/Topics_Blog/Blog-Post.md | 4 +- 10_Wiki/Topics_Blog/Blog_Content_Rules.md | 6 +- 10_Wiki/Topics_Blog/Blog_Title_Rules.md | 6 +- .../Topics_Blog/Bloom-Filters in Search.md | 2 +- 10_Wiki/Topics_Blog/Bloom-Filters.md | 4 +- 10_Wiki/Topics_Blog/Boltzmann-Machines.md | 2 +- .../Boosting-Algorithms-XGBoost-LightGBM.md | 4 +- 10_Wiki/Topics_Blog/Bottlenecks.md | 4 +- 10_Wiki/Topics_Blog/Bottom-Up-Approach.md | 4 +- 10_Wiki/Topics_Blog/Boundaries.md | 4 +- 10_Wiki/Topics_Blog/Boundary-Setting.md | 4 +- 10_Wiki/Topics_Blog/Bounded Contexts.md | 4 +- 10_Wiki/Topics_Blog/Bounded Rationality.md | 6 +- ...nded-Contexts-and-Interface-Segregation.md | 6 +- 10_Wiki/Topics_Blog/Bounded-Rationality.md | 4 +- .../Topics_Blog/Bounding-Box-Regression.md | 2 +- 10_Wiki/Topics_Blog/Bourgeoisie.md | 4 +- .../Brain-Computer Interface (BCI).md | 2 +- .../Brain-Computer-Interface (BCI).md | 4 +- ...rain-Derived Neurotrophic Factor (BDNF).md | 2 +- .../Brand Consistency Maintenance.md | 6 +- .../Branded-Types-for-Nominal-Typing.md | 2 +- 10_Wiki/Topics_Blog/Branded-Types.md | 6 +- 10_Wiki/Topics_Blog/Branding.md | 4 +- 10_Wiki/Topics_Blog/Browser.md | 4 +- 10_Wiki/Topics_Blog/Brute-force.md | 4 +- 10_Wiki/Topics_Blog/Bubble-Sort.md | 4 +- 10_Wiki/Topics_Blog/Budget.md | 4 +- 10_Wiki/Topics_Blog/Bureaucracy.md | 4 +- ...rnout Prevention in Professional Gaming.md | 4 +- 10_Wiki/Topics_Blog/Burnout.md | 4 +- .../Topics_Blog/Business Intelligence (BI).md | 4 +- 10_Wiki/Topics_Blog/Business Presentation.md | 10 +- 10_Wiki/Topics_Blog/Business Writing.md | 10 +- 10_Wiki/Topics_Blog/CAP-Theorem.md | 2 +- .../Topics_Blog/CI-CD-Pipeline-Foundations.md | 2 +- .../CI_CD 및 Pull Request 자동화 리뷰.md | 6 +- .../CI_CD 파이프라인 및 IDE 통합 보안.md | 4 +- 10_Wiki/Topics_Blog/CI_CD.md | 4 +- 10_Wiki/Topics_Blog/CLIP.md | 2 +- 10_Wiki/Topics_Blog/CPTED.md | 4 +- 10_Wiki/Topics_Blog/CV_Synthesis.md | 4 +- 10_Wiki/Topics_Blog/Call Stack.md | 4 +- .../Case-Study-Allbirds-PWA-Redesign.md | 2 +- .../Case-Study-Kiwi-com-Frontend-Migration.md | 2 +- ...Case-Study-Skybound-Asset-Cache-Busting.md | 2 +- ...ybound-Red-Striker-Jitter-Stabilization.md | 2 +- .../Topics_Blog/Catastrophic-Forgetting.md | 2 +- 10_Wiki/Topics_Blog/Causal-Inference.md | 2 +- .../Topics_Blog/Central-Pattern-Generators.md | 4 +- 10_Wiki/Topics_Blog/CesiumJS.md | 4 +- .../Topics_Blog/Chain-of-Thought (CoT 罽).md | 4 +- .../Chain-of-Thought (CoT 사고 사슬).md | 4 +- .../Topics_Blog/Chaos-Theory in Systems.md | 2 +- 10_Wiki/Topics_Blog/Character Consistency.md | 6 +- 10_Wiki/Topics_Blog/Character Reference.md | 6 +- ...기반 텍스트 투 이미지(Text-to-Image) 생성.md | 6 +- ...ols 메모리 프로파일링 및 힙 스냅샷 분석.md | 6 +- .../Chrome DevTools 메모리 프로파일링.md | 6 +- 10_Wiki/Topics_Blog/Chrome DevTools.md | 4 +- .../Chrome-Rendering-Performance.md | 4 +- .../Chronic-Pain-Management-Protocols.md | 6 +- .../Circuit Discovery (회로 발견).md | 4 +- 10_Wiki/Topics_Blog/Circuit Discovery.md | 2 +- .../Circular-Economy-Transitions.md | 4 +- 10_Wiki/Topics_Blog/Circular-Economy.md | 4 +- .../Clean-Architecture-Implementation.md | 6 +- .../Clean-Architecture-TypeScript.md | 4 +- 10_Wiki/Topics_Blog/Clean-Code-Principles.md | 2 +- .../Climate Change Mitigation Frameworks.md | 4 +- .../Clinical-Kinesiology-Assessment.md | 6 +- 10_Wiki/Topics_Blog/Code Review.md | 4 +- 10_Wiki/Topics_Blog/Code Splitting.md | 14 +- ...g-and-Frontend-Performance-Optimization.md | 2 +- 10_Wiki/Topics_Blog/Cognitive Biases.md | 4 +- 10_Wiki/Topics_Blog/Cognitive Computing.md | 4 +- .../Cognitive Neuroscience of Flow.md | 4 +- 10_Wiki/Topics_Blog/Cognitive Psychology.md | 4 +- ... Training Software (eg Aim Lab_KovaaKs).md | 4 +- .../Cognitive-Evaluation-Theory.md | 4 +- .../Topics_Blog/Cognitive-Therapy-in-CBT.md | 4 +- .../Topics_Blog/Collaboration_Governance.md | 6 +- .../Topics_Blog/Collaborative-Filtering.md | 2 +- .../Topics_Blog/Collective-Intelligence.md | 4 +- .../Topics_Blog/Combinatorial-Optimization.md | 2 +- .../Combined Arms (제병협동) 전술.md | 4 +- .../Commercial AI Art Production.md | 6 +- .../Algorithmic Rhetoric.md | 6 +- .../Topics_Blog/Communication & Tech/Index.md | 2 +- 10_Wiki/Topics_Blog/CompCert-C-Compiler.md | 4 +- 10_Wiki/Topics_Blog/Complexity Theory.md | 4 +- 10_Wiki/Topics_Blog/Complexity-Theory.md | 2 +- 10_Wiki/Topics_Blog/Component-Composition.md | 2 +- .../Topics_Blog/Component_Design_Patterns.md | 6 +- .../Topics_Blog/Computational Creativity.md | 4 +- .../Topics_Blog/Computational-Creativity.md | 4 +- .../Topics_Blog/Computational-Linguistics.md | 2 +- .../Computational-Neuroscience-RL.md | 4 +- 10_Wiki/Topics_Blog/Computer Vision.md | 4 +- 10_Wiki/Topics_Blog/Computer-Aided-Design.md | 4 +- 10_Wiki/Topics_Blog/Computer-Vision.md | 2 +- 10_Wiki/Topics_Blog/Computer_Vision.md | 4 +- .../Concept Drift (개념 드리프트).md | 6 +- ...Drift (개념 드리프트, 모델 지식의 부패).md | 4 +- 10_Wiki/Topics_Blog/Concept Mapping.md | 4 +- 10_Wiki/Topics_Blog/Concept-Drift.md | 4 +- 10_Wiki/Topics_Blog/Concurrent Features.md | 12 +- 10_Wiki/Topics_Blog/Concurrent Programming.md | 4 +- .../Concurrent Rendering in React 18+.md | 12 +- .../Conditioning and Learning ( ).md | 2 +- .../Topics_Blog/Connect-AI-Documentation.md | 4 +- .../Topics_Blog/ConnectAI_Dev_Log_20260429.md | 20 +- .../Constitutional AI (헌법 AI).md | 4 +- 10_Wiki/Topics_Blog/Constitutional-AI.md | 2 +- .../Constraint Satisfaction Problems (CSP).md | 6 +- .../Constraint-Satisfaction Problems.md | 2 +- .../Constraint-Satisfaction-Problems.md | 4 +- 10_Wiki/Topics_Blog/Content_Strategy/.gitkeep | 0 .../Content_Strategy/Accessibility (A11y).md | 6 +- .../Content_Strategy/Accessibility.md | 6 +- .../Accessible UI Libraries.md | 6 +- .../Building Reusable UI Components.md | 6 +- 10_Wiki/Topics_Blog/Content_Strategy/Index.md | 28 +- .../Content_Strategy/Mobile-First Approach.md | 6 +- .../Content_Strategy/Mobile-First Design.md | 6 +- .../Functional Behavior Analysis (FBA).md | 10 +- .../Psychology & Education/Index.md | 2 +- .../Reusable UI Component Libraries.md | 6 +- ...Content Accessibility Guidelines (WCAG).md | 6 +- .../모바일 우선 설계(Mobile-First Design).md | 6 +- .../모바일 우선주의 (Mobile-First) 디자인.md | 6 +- ...일 퍼스트 인덱싱(Mobile-First Indexing).md | 6 +- .../모바일 퍼스트(Mobile-First).md | 6 +- .../웹 접근성(Web Accessibility).md | 6 +- 10_Wiki/Topics_Blog/Context API.md | 12 +- 10_Wiki/Topics_Blog/Context Engineering.md | 10 +- 10_Wiki/Topics_Blog/Context Rot.md | 8 +- .../Topics_Blog/Context-Aware-Computing.md | 4 +- 10_Wiki/Topics_Blog/Context_Engineering.md | 10 +- 10_Wiki/Topics_Blog/Continuous-Discovery.md | 4 +- 10_Wiki/Topics_Blog/Contrastive-Learning.md | 2 +- .../Control Systems Engineering.md | 2 +- .../Control-Systems-Engineering.md | 4 +- 10_Wiki/Topics_Blog/Control-Theory.md | 2 +- .../Convolutional-Neural-Networks.md | 2 +- .../Topics_Blog/Core-Web-Vitals-Metrics.md | 2 +- 10_Wiki/Topics_Blog/Core-Web-Vitals.md | 4 +- 10_Wiki/Topics_Blog/Corgea.md | 6 +- 10_Wiki/Topics_Blog/Corporate-LMS-Training.md | 4 +- .../Cost-Benefit Analysis in AI.md | 2 +- 10_Wiki/Topics_Blog/Creativity Research.md | 4 +- .../Topics_Blog/Credit Assignment Problem.md | 4 +- 10_Wiki/Topics_Blog/Cross-Entropy Loss.md | 2 +- .../Cumulative-Layout-Shift-CLS.md | 2 +- 10_Wiki/Topics_Blog/Curriculum-Learning.md | 2 +- 10_Wiki/Topics_Blog/Custom-ESLint-Rules.md | 4 +- 10_Wiki/Topics_Blog/Custom-Hooks-Patterns.md | 2 +- .../Topics_Blog/Customer-Journey-Mapping.md | 4 +- .../Topics_Blog/Cybernetics Foundations.md | 2 +- 10_Wiki/Topics_Blog/Cybernetics.md | 4 +- .../Topics_Blog/DAG-Dependency-Management.md | 4 +- .../Topics_Blog/DALL-E 3 Natural Language.md | 6 +- .../Topics_Blog/DALL-E 3 Negation Handling.md | 6 +- .../DALL-E 3 Synthetic Captioning.md | 6 +- .../DALL-E 3와 GPT-4의 상호작용적 생성.md | 6 +- .../DALL-E 3의 자연어 기반 최적화.md | 6 +- 10_Wiki/Topics_Blog/DDD-Type-Safety.md | 4 +- 10_Wiki/Topics_Blog/DDD-in-TypeScript.md | 4 +- 10_Wiki/Topics_Blog/DORA-Metrics.md | 4 +- .../DPO (Direct Preference Optimization).md | 4 +- 10_Wiki/Topics_Blog/DQN.md | 4 +- .../Topics_Blog/Data Cleaning Algorithms.md | 4 +- .../Data Distillation (데이터 증류).md | 4 +- .../Data-Augmentation Strategies.md | 2 +- .../Data-Driven Personalization.md | 6 +- .../Topics_Blog/Data-Ethics and Privacy.md | 2 +- 10_Wiki/Topics_Blog/Data-Flywheel-Effect.md | 2 +- .../Data-Pipeline Orchestration.md | 2 +- 10_Wiki/Topics_Blog/Data-Science-in-UX.md | 4 +- .../Data-Transfer-Object-Design.md | 2 +- 10_Wiki/Topics_Blog/Dead-Space-Series.md | 4 +- .../Debugging Frontend Applications.md | 14 +- .../Deceptive Alignment (기만적 정렬).md | 4 +- 10_Wiki/Topics_Blog/Decision Theory.md | 4 +- .../Decision-Trees and Random Forests.md | 2 +- 10_Wiki/Topics_Blog/Declaration-Files.md | 4 +- 10_Wiki/Topics_Blog/Deep Q-Networks (DQN).md | 4 +- .../Topics_Blog/Deep-Convolutional-GANs.md | 4 +- 10_Wiki/Topics_Blog/Deep-Grammar.md | 4 +- 10_Wiki/Topics_Blog/Deep-Learning.md | 2 +- 10_Wiki/Topics_Blog/Deep-Q-Networks-DQN.md | 4 +- 10_Wiki/Topics_Blog/DeepCode AI.md | 4 +- 10_Wiki/Topics_Blog/Deepfake-Detection.md | 4 +- 10_Wiki/Topics_Blog/Deepfake-Technology.md | 2 +- .../Topics_Blog/Default Mode Network (DMN).md | 4 +- 10_Wiki/Topics_Blog/DefinitelyTyped.md | 4 +- 10_Wiki/Topics_Blog/Definitions_of_Game.md | 4 +- 10_Wiki/Topics_Blog/Degrees-of-Freedom.md | 6 +- 10_Wiki/Topics_Blog/Deliberate-Practice.md | 4 +- .../Denavit-Hartenberg-Parameters.md | 4 +- .../Dense vs Sparse Neural Networks.md | 2 +- .../Topics_Blog/Dependency-Graph-Analysis.md | 4 +- 10_Wiki/Topics_Blog/Dependency-Injection.md | 4 +- .../Dependency-Inversion-Principle.md | 4 +- 10_Wiki/Topics_Blog/Deployment-Strategy.md | 4 +- 10_Wiki/Topics_Blog/Deployment_Final_Gate.md | 6 +- 10_Wiki/Topics_Blog/Design-System.md | 4 +- .../Topics_Blog/Determinism-in-Computing.md | 2 +- .../Topics_Blog/DevOps-and-UX-Convergence.md | 6 +- 10_Wiki/Topics_Blog/DevOps-for-AI-MLOps.md | 2 +- 10_Wiki/Topics_Blog/DevSecOps.md | 6 +- .../Topics_Blog/Differentiable Programming.md | 4 +- 10_Wiki/Topics_Blog/Diffusion-Models.md | 2 +- .../Digital Intellectual Property Rights.md | 2 +- .../Topics_Blog/Digital Thread Integration.md | 4 +- .../Topics_Blog/Digital-Twin-Technology.md | 4 +- 10_Wiki/Topics_Blog/Dijkstra's Algorithm.md | 4 +- .../Topics_Blog/Dimensionality-Reduction.md | 2 +- .../Diminishing Returns (한계 수익 체감).md | 4 +- .../Directed-Acyclic-Graph-Build-Systems.md | 4 +- ...ted-Acyclic-Graph-Dependency-Management.md | 2 +- ...Discriminated-Unions-for-Error-Handling.md | 2 +- ...Discriminated-Unions-for-State-Modeling.md | 4 +- 10_Wiki/Topics_Blog/Discriminated-Unions.md | 4 +- 10_Wiki/Topics_Blog/Dissipative-Structures.md | 4 +- 10_Wiki/Topics_Blog/Distillation.md | 4 +- .../Distributed Reinforcement Learning.md | 4 +- 10_Wiki/Topics_Blog/Distributed-Computing.md | 2 +- .../Distributed-System-Type-Safety.md | 4 +- 10_Wiki/Topics_Blog/Distributed-Systems.md | 4 +- 10_Wiki/Topics_Blog/Documentation-Strategy.md | 4 +- 10_Wiki/Topics_Blog/Domain Objects.md | 2 +- .../Topics_Blog/Domain-Driven-Design-DDD.md | 2 +- .../Topics_Blog/Domain-Specific-Languages.md | 4 +- 10_Wiki/Topics_Blog/Dopamine-Modeling.md | 4 +- .../Topics_Blog/Dopaminergic Reward System.md | 6 +- .../Dopaminergic Reward Systems.md | 2 +- .../Topics_Blog/Drama Management Systems.md | 4 +- 10_Wiki/Topics_Blog/Dramaturgy-Theory.md | 4 +- 10_Wiki/Topics_Blog/Dry-Principle.md | 4 +- .../Dynamic Difficulty Adjustment (DDA).md | 4 +- .../Dynamic Few-Shot (동적 퓨샷 선택 전략).md | 4 +- 10_Wiki/Topics_Blog/Dynamic-Capabilities.md | 4 +- .../Dynamic-Creative-Optimization.md | 4 +- .../Dynamic-Environment-Handling.md | 4 +- 10_Wiki/Topics_Blog/Dynamic-Programming.md | 4 +- .../Topics_Blog/E-Learning-Gamification.md | 4 +- .../E-commerce-Catalog-Management.md | 4 +- .../Topics_Blog/E-commerce-Optimization.md | 4 +- .../Topics_Blog/ESLint-Plugin-Development.md | 4 +- 10_Wiki/Topics_Blog/ESLint-Static-Analysis.md | 6 +- .../EU-Web-Accessibility-Directive.md | 2 +- .../Ecology and Ecosystem Modeling.md | 4 +- 10_Wiki/Topics_Blog/Economic-Analysis.md | 4 +- .../Topics_Blog/Economic-Complexity-Index.md | 4 +- 10_Wiki/Topics_Blog/Economic-Mobility.md | 4 +- .../Topics_Blog/Economics-of-Information.md | 4 +- 10_Wiki/Topics_Blog/Edge-AI-and-Computing.md | 2 +- .../Edge-Artificial-Intelligence.md | 4 +- 10_Wiki/Topics_Blog/Edge-Computing.md | 4 +- 10_Wiki/Topics_Blog/Edtech-Industry-Trends.md | 4 +- .../Topics_Blog/Effective-Altruism-in-AI.md | 4 +- 10_Wiki/Topics_Blog/Efficiency.md | 4 +- .../Eigenvalues-and-Eigenvectors.md | 2 +- 10_Wiki/Topics_Blog/Eligibility-Traces.md | 2 +- .../Elite-Sport-Science-Protocols.md | 2 +- .../Elite-Strength-and-Conditioning.md | 2 +- 10_Wiki/Topics_Blog/Elite-Theory.md | 4 +- 10_Wiki/Topics_Blog/Embodied Cognition.md | 2 +- 10_Wiki/Topics_Blog/Embodied-AI.md | 2 +- .../Emergence-in-Complex-Systems.md | 4 +- 10_Wiki/Topics_Blog/Emergence-in-Systems.md | 2 +- 10_Wiki/Topics_Blog/Emergence.md | 4 +- .../Emotional-AI (Affective Computing).md | 2 +- ...lly Intelligent Tutoring Systems (EITS).md | 2 +- 10_Wiki/Topics_Blog/Empathy-in-AI.md | 4 +- .../Encapsulation-and-Information-Hiding.md | 2 +- .../Encapsulation-of-Domain-Invariants.md | 2 +- .../Encapsulation-via-Access-Modifiers.md | 4 +- 10_Wiki/Topics_Blog/End-to-End-Learning.md | 2 +- .../End-to-End-Testing-Strategies.md | 4 +- .../Endurance-Athletics-Cognition.md | 4 +- 10_Wiki/Topics_Blog/Engineering_Principles.md | 10 +- 10_Wiki/Topics_Blog/Ensemble-Learning.md | 4 +- 10_Wiki/Topics_Blog/Ensemble-Methods.md | 2 +- 10_Wiki/Topics_Blog/Ensuring-Data-Privacy.md | 4 +- .../Topics_Blog/Enterprise-Design-Systems.md | 2 +- .../Enterprise-Resource-Planning-Systems.md | 2 +- .../Enterprise-Scale-Monorepo-Management.md | 2 +- 10_Wiki/Topics_Blog/Enterprise-Service-Bus.md | 4 +- .../Enterprise-Software-Architecture.md | 4 +- .../Enterprise-Software-Engineering.md | 4 +- .../Entity-Relationship-Modeling.md | 4 +- .../Entropy in Information Theory.md | 2 +- .../Topics_Blog/Environment-Design-in-RL.md | 2 +- .../Topics_Blog/Enzyme-Inhibition-Kinetics.md | 4 +- .../Topics_Blog/Epidemiological-Modeling.md | 4 +- 10_Wiki/Topics_Blog/Epistemic-Uncertainty.md | 2 +- 10_Wiki/Topics_Blog/Epistemology.md | 4 +- 10_Wiki/Topics_Blog/Equality.md | 4 +- 10_Wiki/Topics_Blog/Ergodic-Theory.md | 4 +- .../Ergonomics-in-Workspace-Design.md | 4 +- 10_Wiki/Topics_Blog/Error-Boundary-Pattern.md | 2 +- 10_Wiki/Topics_Blog/Es-Lint-Configuration.md | 6 +- .../Topics_Blog/Escalation-of-Commitment.md | 4 +- .../Topics_Blog/Ethical-Decision-Making.md | 4 +- 10_Wiki/Topics_Blog/Ethics & AI.md | 4 +- .../Ethics of Autonomous Systems.md | 2 +- .../Ethics-in-Artificial-Intelligence.md | 4 +- 10_Wiki/Topics_Blog/Ethnographic-Research.md | 4 +- 10_Wiki/Topics_Blog/Etiology-of-Disease.md | 4 +- .../Topics_Blog/Eudaimonia-and-Well-being.md | 4 +- .../Topics_Blog/Eugen Systems 모딩 매뉴얼.md | 4 +- ...stems의 Iriszoom 엔진 및 전략 게임 개발.md | 4 +- .../Eugen Systems의 WARNO 시뮬레이션 개발.md | 4 +- ...냉전기 가상 시나리오 및 모딩 생태계 구축.md | 4 +- .../Topics_Blog/Event-Driven-Architecture.md | 4 +- 10_Wiki/Topics_Blog/Evolutionary Biology.md | 4 +- .../Topics_Blog/Evolutionary Computation.md | 4 +- .../Evolutionary-Algorithm-Design.md | 4 +- .../Topics_Blog/Evolutionary-Algorithms.md | 4 +- .../Topics_Blog/Evolutionary-Computation.md | 2 +- .../Topics_Blog/Excess-Property-Checking.md | 2 +- 10_Wiki/Topics_Blog/Executive Briefings.md | 6 +- .../Topics_Blog/Executive Communication.md | 6 +- 10_Wiki/Topics_Blog/Executive Dysfunction.md | 4 +- 10_Wiki/Topics_Blog/Executive Presentation.md | 6 +- .../Topics_Blog/Executive-Function-Deficit.md | 2 +- .../Topics_Blog/Exhaustiveness-Checking.md | 4 +- .../Topics_Blog/Expectation-Maximization.md | 4 +- .../Topics_Blog/Expected Utility Theory.md | 2 +- 10_Wiki/Topics_Blog/Experience-Replay.md | 2 +- .../Topics_Blog/Experience-Sampling-Method.md | 4 +- 10_Wiki/Topics_Blog/Explainable-AI (XAI).md | 4 +- 10_Wiki/Topics_Blog/Explainable-AI-XAI.md | 2 +- .../Topics_Blog/Exploding-Gradient Problem.md | 2 +- .../Exploration vs Exploitation.md | 4 +- .../Exploration-vs-Exploitation.md | 2 +- .../Topics_Blog/Exploratory-Data-Analysis.md | 2 +- 10_Wiki/Topics_Blog/Expo 2025 Osaka.md | 6 +- 10_Wiki/Topics_Blog/Exponential-Growth.md | 4 +- 10_Wiki/Topics_Blog/Extended-Reality-XR.md | 2 +- 10_Wiki/Topics_Blog/External_Media/.gitkeep | 0 10_Wiki/Topics_Blog/Externalities.md | 4 +- 10_Wiki/Topics_Blog/Extreme-Programming-XP.md | 2 +- .../Eye-Tracking-in-UX-Research.md | 6 +- 10_Wiki/Topics_Blog/Eye-Tracking.md | 4 +- .../Fact_Based_Meeting_Minutes_Prompt.md | 6 +- 10_Wiki/Topics_Blog/Factor-Analysis.md | 2 +- 10_Wiki/Topics_Blog/Factory-Pattern.md | 4 +- 10_Wiki/Topics_Blog/Failable-Task-Handling.md | 4 +- 10_Wiki/Topics_Blog/Fault-Tolerance.md | 4 +- 10_Wiki/Topics_Blog/Feature-Engineering.md | 2 +- 10_Wiki/Topics_Blog/Feature-Flags.md | 4 +- 10_Wiki/Topics_Blog/Federated-Learning.md | 2 +- .../Topics_Blog/Feedback-Control-Systems.md | 2 +- .../Topics_Blog/Feedback-Loops in Systems.md | 2 +- .../Topics_Blog/Feedback-Loops-in-Design.md | 4 +- 10_Wiki/Topics_Blog/Feedback-Loops.md | 4 +- 10_Wiki/Topics_Blog/Few-Shot-Learning.md | 2 +- 10_Wiki/Topics_Blog/Figma-to-Code-Workflow.md | 2 +- 10_Wiki/Topics_Blog/Figurative-Language.md | 4 +- 10_Wiki/Topics_Blog/Fine-tuning.md | 4 +- 10_Wiki/Topics_Blog/Finished Goods.md | 4 +- 10_Wiki/Topics_Blog/Finite-State-Machines.md | 4 +- .../Topics_Blog/First Input Delay (FID).md | 4 +- 10_Wiki/Topics_Blog/Fitness-Landscape.md | 2 +- 10_Wiki/Topics_Blog/Flow-State.md | 4 +- .../Topics_Blog/Fluent-Interface-Design.md | 4 +- .../Topics_Blog/Fluid-Dynamics for Games.md | 2 +- 10_Wiki/Topics_Blog/Formal Methods.md | 4 +- .../Formal-Verification-of-Software.md | 4 +- 10_Wiki/Topics_Blog/Foundation-Models.md | 4 +- .../Topics_Blog/Foundational LLM Concepts.md | 8 +- 10_Wiki/Topics_Blog/Fragility.md | 4 +- 10_Wiki/Topics_Blog/Free-Energy-Principle.md | 4 +- ...ntend-Architecture-and-Folder-Structure.md | 2 +- 10_Wiki/Topics_Blog/Frontend-Architecture.md | 2 +- .../Frontend-Debugging-and-Testing.md | 2 +- ...Frontend-Performance-Optimization-Guide.md | 2 +- ...ntend-Team-Collaboration-and-Governance.md | 2 +- 10_Wiki/Topics_Blog/Frontend.md | 4 +- 10_Wiki/Topics_Blog/Functional Programming.md | 4 +- .../Functional-Programming-in-TypeScript.md | 2 +- 10_Wiki/Topics_Blog/Functional-Programming.md | 2 +- 10_Wiki/Topics_Blog/Fuzzy-Logic.md | 2 +- 10_Wiki/Topics_Blog/GAN.md | 2 +- 10_Wiki/Topics_Blog/GNN.md | 2 +- .../GPT-Architecture-Foundations.md | 2 +- 10_Wiki/Topics_Blog/GPU-Architecture.md | 2 +- .../Topics_Blog/GPU-Programming-with-CUDA.md | 2 +- 10_Wiki/Topics_Blog/GPU.md | 6 +- 10_Wiki/Topics_Blog/GRPO.md | 4 +- 10_Wiki/Topics_Blog/GRU.md | 2 +- .../Topics_Blog/Gacha Mechanics Analysis.md | 2 +- .../Topics_Blog/Game Analytics (게임 분석).md | 2 +- 10_Wiki/Topics_Blog/Game-Balance-Design.md | 2 +- 10_Wiki/Topics_Blog/Game-Balance-Modeling.md | 2 +- 10_Wiki/Topics_Blog/Game-Design-Ontology.md | 4 +- 10_Wiki/Topics_Blog/Game-Design-Theory.md | 4 +- 10_Wiki/Topics_Blog/Game-Economy-Design.md | 2 +- .../Topics_Blog/Game-Feel-and-Juiciness.md | 4 +- 10_Wiki/Topics_Blog/Game-Loop-Architecture.md | 4 +- 10_Wiki/Topics_Blog/Game-Mechanics.md | 2 +- 10_Wiki/Topics_Blog/Game-Ontology-for-PCG.md | 4 +- 10_Wiki/Topics_Blog/Game-Theory-in-AI.md | 2 +- .../Topics_Blog/Gamification-Strategies.md | 2 +- 10_Wiki/Topics_Blog/Gamification-Theory.md | 4 +- 10_Wiki/Topics_Blog/Gates.md | 4 +- 10_Wiki/Topics_Blog/Gaussian-Processes.md | 4 +- 10_Wiki/Topics_Blog/Gen-AI.md | 4 +- .../General Knowledge/2026-04-15.md | 6 +- .../General Knowledge/Blog_Content_Rules.md | 6 +- .../General Knowledge/Blog_Title_Rules.md | 6 +- .../Brand-Identity-Management.md | 6 +- .../Code Splitting Lazy Loading.md | 6 +- .../General Knowledge/Description-Logics.md | 6 +- .../General Knowledge/Dopamine Signaling.md | 6 +- .../Topics_Blog/General Knowledge/Index.md | 40 +- .../General Knowledge/Markov-Random-Fields.md | 6 +- .../General Knowledge/Metaverse Aesthetics.md | 6 +- .../Model-Free RL vs Model-Based RL.md | 6 +- .../Motion-Capture-Retargeting.md | 6 +- .../General Knowledge/Mycological Horror.md | 6 +- .../OffscreenCanvas (멀티스레딩).md | 6 +- .../Topics_Blog/General Knowledge/README.md | 6 +- ...안 이슈와 Cross-Origin Isolation 설정법.md | 10 +- .../General Knowledge/Variance-Rules.md | 6 +- .../마크-스위프-컴팩트(Mark-Sweep-Compact).md | 10 +- 10_Wiki/Topics_Blog/General Knowledge/무제.md | 6 +- .../이벤트 포워딩(Event Forwarding).md | 6 +- .../General Knowledge/환영합니다.md | 6 +- 10_Wiki/Topics_Blog/Generalization-in-AI.md | 2 +- ...dversarial Networks (GANs) in Fine Arts.md | 4 +- 10_Wiki/Topics_Blog/Generative-AI-Impact.md | 2 +- 10_Wiki/Topics_Blog/Generative-AI.md | 2 +- .../Generative-Adversarial-Networks.md | 2 +- .../Topics_Blog/Generics-and-Polymorphism.md | 4 +- 10_Wiki/Topics_Blog/Genetic-Algorithms.md | 2 +- .../Geographic-Information-Systems.md | 4 +- .../Topics_Blog/Geometric-Deep-Learning.md | 2 +- 10_Wiki/Topics_Blog/Geriatric-Medicine.md | 4 +- 10_Wiki/Topics_Blog/Gestalt Psychology.md | 4 +- .../Topics_Blog/Gestalt-Principles in UX.md | 2 +- .../Gestalt-Principles-of-Design.md | 2 +- .../Topics_Blog/Gimbals-and-Orientation.md | 2 +- .../Git-Branching-Strategies-and-Workflows.md | 2 +- 10_Wiki/Topics_Blog/Git-Version-Control.md | 2 +- 10_Wiki/Topics_Blog/GitLab CI.md | 4 +- 10_Wiki/Topics_Blog/Git_Workflows.md | 10 +- 10_Wiki/Topics_Blog/Global-Standard.md | 4 +- 10_Wiki/Topics_Blog/Global-vs-Local-Optima.md | 2 +- 10_Wiki/Topics_Blog/Goal-Misgeneralization.md | 4 +- 10_Wiki/Topics_Blog/God-Object-Antipattern.md | 2 +- .../Godel's Incompleteness Theorems.md | 4 +- .../Google-Page-Experience-2025-Update.md | 2 +- .../Topics_Blog/Gradient-Boosting-Machines.md | 2 +- 10_Wiki/Topics_Blog/Gradient-Descent.md | 4 +- 10_Wiki/Topics_Blog/Graph Theory.md | 4 +- 10_Wiki/Topics_Blog/Graph-Coloring-Problem.md | 4 +- 10_Wiki/Topics_Blog/Graph-Database.md | 2 +- 10_Wiki/Topics_Blog/Graph-Theory.md | 2 +- 10_Wiki/Topics_Blog/GraphQL-Code-Generator.md | 4 +- .../GraphRAG & Knowledge Graph Memory.md | 8 +- .../GraphRAG (그래프 기반 검색 증강 생성).md | 6 +- 10_Wiki/Topics_Blog/Greedy-Algorithms.md | 2 +- 10_Wiki/Topics_Blog/Grit.md | 4 +- 10_Wiki/Topics_Blog/Grounded Theory Method.md | 4 +- .../Growth-Mindset-Intervention.md | 4 +- 10_Wiki/Topics_Blog/Growth-Mindset.md | 4 +- .../Guilty-Gear-Xrd-Rendering-Pipeline.md | 4 +- 10_Wiki/Topics_Blog/HANDOVER.md | 4 +- .../Topics_Blog/HBO-Prestige-Television.md | 4 +- .../HCI (Human-Computer Interaction).md | 4 +- 10_Wiki/Topics_Blog/HHH.md | 4 +- 10_Wiki/Topics_Blog/HMM.md | 2 +- 10_Wiki/Topics_Blog/Habit-Formation.md | 2 +- 10_Wiki/Topics_Blog/Hallucination (환각).md | 4 +- 10_Wiki/Topics_Blog/Hallucination-in-LLM.md | 2 +- 10_Wiki/Topics_Blog/Hallucination-in-LLMs.md | 2 +- .../Hardware-Acceleration-for-AI.md | 2 +- 10_Wiki/Topics_Blog/Hardware-Verification.md | 4 +- 10_Wiki/Topics_Blog/Hardware.md | 4 +- .../Topics_Blog/Hash-Functions-and-Maps.md | 2 +- 10_Wiki/Topics_Blog/Health-Informatics.md | 4 +- 10_Wiki/Topics_Blog/Hebbian-Theory.md | 4 +- 10_Wiki/Topics_Blog/Heuristic-Search.md | 2 +- 10_Wiki/Topics_Blog/Heuristics.md | 4 +- .../Hierarchical-Task-Network (HTN).md | 2 +- .../Topics_Blog/High-Availability-Systems.md | 2 +- .../Topics_Blog/High-Cohesion-Low-Coupling.md | 4 +- .../High-Frequency-Trading-Models.md | 4 +- .../High-Performance Computing (HPC).md | 4 +- .../Topics_Blog/High-Performance-Coaching.md | 4 +- .../High-Performance-Organizations.md | 4 +- .../High-Performance-Sports-Science.md | 4 +- 10_Wiki/Topics_Blog/Homeostasis (항상성).md | 4 +- 10_Wiki/Topics_Blog/Homeostasis.md | 4 +- 10_Wiki/Topics_Blog/Homomorphic-Encryption.md | 2 +- .../Topics_Blog/Human Centered AI (HCAI).md | 4 +- 10_Wiki/Topics_Blog/Human-AI-Collaboration.md | 2 +- .../Human-Computer-Interaction-HCI.md | 2 +- .../Topics_Blog/Human-Computer-Interaction.md | 4 +- .../Topics_Blog/Human-in-the-loop (HITL).md | 8 +- 10_Wiki/Topics_Blog/Human-in-the-loop-AI.md | 2 +- .../Topics_Blog/Hybrid-Cloud-Architectures.md | 2 +- .../Hydration-Mismatch-and-SSR-Debugging.md | 2 +- .../Hyperinflation-in-Closed-Loop-Systems.md | 4 +- .../Hyperparameter-Optimization.md | 2 +- 10_Wiki/Topics_Blog/Hyperparameters.md | 4 +- 10_Wiki/Topics_Blog/Hypostatic-Abstraction.md | 4 +- 10_Wiki/Topics_Blog/Hypothesis-Testing.md | 2 +- 10_Wiki/Topics_Blog/ICRE-Framework.md | 4 +- ...DE (Integrated Development Environment).md | 4 +- 10_Wiki/Topics_Blog/IEEE-P36521.md | 4 +- 10_Wiki/Topics_Blog/ISO-Standard.md | 4 +- 10_Wiki/Topics_Blog/Ikigai (이키가이).md | 4 +- .../Image Inpainting (Vary Region).md | 6 +- 10_Wiki/Topics_Blog/Image Parameters.md | 6 +- .../Image-Classification-Mastery.md | 2 +- .../Image-Optimization-for-Web-Performance.md | 2 +- .../Image-Segmentation-Techniques.md | 2 +- 10_Wiki/Topics_Blog/Image-Segmentation.md | 2 +- .../Topics_Blog/Imbalanced-Data-Handling.md | 4 +- 10_Wiki/Topics_Blog/Imitation-Learning.md | 4 +- 10_Wiki/Topics_Blog/Immersive-Sim-Design.md | 4 +- 10_Wiki/Topics_Blog/Immersive-Sim-Genre.md | 4 +- .../Immersive-Sims-Deus-Ex-Dishonored.md | 4 +- .../Immersive-Sims-Deus-Ex-Thief.md | 4 +- 10_Wiki/Topics_Blog/Immutability-Patterns.md | 4 +- 10_Wiki/Topics_Blog/Impedance-Matching.md | 2 +- 10_Wiki/Topics_Blog/In-Context-Learning.md | 2 +- .../Topics_Blog/Inclusive-Design-and-UX.md | 2 +- .../Topics_Blog/Incremental-Computation.md | 4 +- 10_Wiki/Topics_Blog/Incremental-Learning.md | 2 +- .../Incremental-Static-Regeneration-ISR.md | 2 +- 10_Wiki/Topics_Blog/Incrementalism.md | 4 +- .../Independent Component Analysis (ICA).md | 4 +- .../Independent-Component-Analysis.md | 2 +- .../Index-Fragmentation-Analysis.md | 4 +- 10_Wiki/Topics_Blog/Index.md | 48 +- 10_Wiki/Topics_Blog/Index_1530.md | 2 +- 10_Wiki/Topics_Blog/Index_1532.md | 2 +- 10_Wiki/Topics_Blog/Index_20.md | 10 +- 10_Wiki/Topics_Blog/Index_692.md | 2942 ++++++++--------- 10_Wiki/Topics_Blog/Indexing-Strategies.md | 2 +- .../Topics_Blog/Indian-Innovation-Models.md | 4 +- 10_Wiki/Topics_Blog/Inductive-Bias.md | 2 +- 10_Wiki/Topics_Blog/Inductive-Reasoning.md | 4 +- 10_Wiki/Topics_Blog/Inexact-Science.md | 4 +- .../Inference-Coupled Persistence.md | 8 +- 10_Wiki/Topics_Blog/Inference-Optimization.md | 10 +- 10_Wiki/Topics_Blog/Inferential-Statistics.md | 4 +- 10_Wiki/Topics_Blog/Information-Entropy.md | 4 +- .../Topics_Blog/Information-Retrieval-IR.md | 2 +- 10_Wiki/Topics_Blog/Information-Society.md | 4 +- 10_Wiki/Topics_Blog/Infraspace.md | 4 +- .../Topics_Blog/Infrastructure-as-Code-IaC.md | 2 +- .../Inheritance-and-Polymorphism.md | 2 +- 10_Wiki/Topics_Blog/Inner-Product-Spaces.md | 2 +- 10_Wiki/Topics_Blog/Innovation.md | 4 +- .../Topics_Blog/Inpainting & Outpainting.md | 6 +- .../Input-Validation-Strategies.md | 2 +- 10_Wiki/Topics_Blog/Inquiry-Based Learning.md | 4 +- .../Topics_Blog/Instance-based-Learning.md | 2 +- 10_Wiki/Topics_Blog/InstancedMesh2 library.md | 4 +- 10_Wiki/Topics_Blog/Instinct.md | 4 +- 10_Wiki/Topics_Blog/Instruction-Tuning.md | 2 +- 10_Wiki/Topics_Blog/Intangible-Capital.md | 4 +- .../Topics_Blog/Integration-Testing-for-AI.md | 2 +- .../Intellectual-Property-in-AI.md | 2 +- .../Interaction to Next Paint (INP).md | 6 +- .../Interaction-to-Next-Paint-INP.md | 2 +- .../Topics_Blog/Interdisciplinary-Research.md | 4 +- .../Interface-Segregation-Principle.md | 2 +- .../Topics_Blog/Internet of Things (IoT).md | 4 +- 10_Wiki/Topics_Blog/Interop 2026.md | 4 +- 10_Wiki/Topics_Blog/Interoperability.md | 4 +- .../Interpretability-vs-Explainability.md | 2 +- .../Introduction-to-Programming.md | 4 +- .../Topics_Blog/Introspection (자기성찰).md | 4 +- 10_Wiki/Topics_Blog/Inverse-Kinematics.md | 4 +- .../Inverse-Reinforcement-Learning.md | 2 +- 10_Wiki/Topics_Blog/Inversion.md | 4 +- 10_Wiki/Topics_Blog/IoT-and-AI-Integration.md | 2 +- .../Isaac-Asimovs-Laws-of-Robotics.md | 2 +- .../Item-Item-Collaborative-Filtering.md | 2 +- 10_Wiki/Topics_Blog/Iteration.md | 4 +- 10_Wiki/Topics_Blog/Iterative Prompting.md | 6 +- .../Iterative-Development-Models.md | 2 +- 10_Wiki/Topics_Blog/Iterative-Development.md | 4 +- .../JIT-Compilation-in-AI-Engines.md | 2 +- .../Topics_Blog/JSON-LD-Structured-Data.md | 2 +- .../JSON-and-Data-Serialization.md | 2 +- .../JUnit-and-Testing-Frameworks.md | 2 +- .../JavaScript-Async-and-Event-Loop.md | 2 +- .../JavaScript-Optimization-Patterns.md | 2 +- 10_Wiki/Topics_Blog/Joint-Optimization.md | 4 +- 10_Wiki/Topics_Blog/Journaling.md | 4 +- 10_Wiki/Topics_Blog/Judgment.md | 4 +- 10_Wiki/Topics_Blog/Just-In-Time (JIT).md | 4 +- 10_Wiki/Topics_Blog/Just-in-Case.md | 4 +- .../Topics_Blog/Just-in-time-Data-Loading.md | 2 +- .../K-Means-Clustering-Foundations.md | 2 +- .../Topics_Blog/K-Nearest-Neighbors-K-NN.md | 2 +- .../KISS (Keep It Simple, Stupid).md | 4 +- .../KISS-Principle-in-Software-Design.md | 2 +- .../KPI (Key Performance Indicator).md | 4 +- .../Kalman-Filter-and-State-Tracking.md | 2 +- .../Kernel-Density-Estimation-KDE.md | 2 +- .../Topics_Blog/Kernel-Methods-and-SVMs.md | 2 +- 10_Wiki/Topics_Blog/Knowledge synthesis.md | 4 +- 10_Wiki/Topics_Blog/Knowledge-Distillation.md | 2 +- .../Knowledge-Graph-Foundations.md | 2 +- 10_Wiki/Topics_Blog/Knowledge-Graph.md | 2 +- .../Knowledge-Representation-in-AI.md | 6 +- 10_Wiki/Topics_Blog/Knowledge-Structure.md | 4 +- 10_Wiki/Topics_Blog/Kolmogorov-Complexity.md | 2 +- .../Kubernetes-for-AI-Orchestration.md | 2 +- .../Kullback-Leibler-Divergence.md | 2 +- .../Topics_Blog/L1-and-L2-Regularization.md | 2 +- 10_Wiki/Topics_Blog/L2-Regularization.md | 4 +- .../Topics_Blog/LLM-Security-and-Safety.md | 2 +- 10_Wiki/Topics_Blog/LLM.md | 6 +- 10_Wiki/Topics_Blog/LOD.md | 6 +- .../LSTM (Long Short-Term Memory).md | 4 +- 10_Wiki/Topics_Blog/LSTM.md | 2 +- .../Topics_Blog/Label-Noise-and-Robustness.md | 2 +- 10_Wiki/Topics_Blog/Lagrange-Multipliers.md | 2 +- 10_Wiki/Topics_Blog/Language-Models.md | 4 +- .../Large Language Models (LLM).md | 4 +- .../Large-scale Application Refactoring.md | 14 +- ...scale-Application-Architecture-Patterns.md | 2 +- .../Largest Contentful Paint (LCP).md | 6 +- .../Largest-Contentful-Paint-LCP.md | 2 +- .../Latent-Dirichlet-Allocation.md | 2 +- .../Latent-Semantic-Analysis-LSA.md | 2 +- .../Layered-Architecture-in-Frontend.md | 2 +- 10_Wiki/Topics_Blog/Lazy Loading.md | 14 +- .../Topics_Blog/Lazy-Loading-Strategies.md | 2 +- 10_Wiki/Topics_Blog/Leadership.md | 4 +- 10_Wiki/Topics_Blog/Lean-Operations.md | 4 +- .../Topics_Blog/Lean-Project-Management.md | 2 +- 10_Wiki/Topics_Blog/Learning-Paths.md | 4 +- .../Topics_Blog/Learning-Rate-Schedules.md | 2 +- .../Topics_Blog/Learning-Rate-Scheduling.md | 2 +- 10_Wiki/Topics_Blog/Least-Squares-Methods.md | 2 +- 10_Wiki/Topics_Blog/Legacy-Systems.md | 4 +- 10_Wiki/Topics_Blog/Legacy_React_Migration.md | 10 +- 10_Wiki/Topics_Blog/Lessons Learned.md | 4 +- 10_Wiki/Topics_Blog/Level of Detail (LOD).md | 6 +- .../Topics_Blog/Levels of Understanding.md | 4 +- .../Topics_Blog/Lighting and Composition.md | 6 +- .../Topics_Blog/Linear-Algebra-Foundations.md | 2 +- 10_Wiki/Topics_Blog/Linear-Algebra.md | 4 +- .../Linear-Discriminant-Analysis.md | 2 +- 10_Wiki/Topics_Blog/Linear-Programming.md | 4 +- .../Topics_Blog/Linear-Regression-Mastery.md | 2 +- .../Topics_Blog/Linguistic-Analysis-in-AI.md | 2 +- 10_Wiki/Topics_Blog/Linked-Lists-and-Trees.md | 2 +- .../Topics_Blog/Linux-Performance-Tuning.md | 2 +- 10_Wiki/Topics_Blog/Liquid-Democracy.md | 2 +- .../Liskov-Substitution-Principle.md | 2 +- 10_Wiki/Topics_Blog/LlamaIndex.md | 2 +- .../Topics_Blog/LoRA (Low-Rank Adaptation).md | 4 +- .../Topics_Blog/Load-Balancing-Strategies.md | 2 +- 10_Wiki/Topics_Blog/Local-Brain-Management.md | 2 +- 10_Wiki/Topics_Blog/Local-Search.md | 4 +- .../Locality-Sensitive-Hashing (LSH).md | 4 +- .../Topics_Blog/Locality-Sensitive-Hashing.md | 2 +- 10_Wiki/Topics_Blog/Logic.md | 4 +- .../Logistic-Regression-Foundations.md | 2 +- 10_Wiki/Topics_Blog/Logistic-Regression.md | 4 +- .../Topics_Blog/Long Animation Frames API.md | 6 +- 10_Wiki/Topics_Blog/Long Tasks.md | 6 +- .../Long-Short-Term-Memory (LSTM).md | 4 +- 10_Wiki/Topics_Blog/Long-Short-Term-Memory.md | 2 +- 10_Wiki/Topics_Blog/Long-Tail.md | 4 +- 10_Wiki/Topics_Blog/Loose-Coupling.md | 6 +- 10_Wiki/Topics_Blog/Loss Functions.md | 4 +- .../Topics_Blog/Loss-Functions-Foundations.md | 2 +- .../Topics_Blog/Low-Rank-Adaptation-LoRA.md | 2 +- 10_Wiki/Topics_Blog/Lubrication.md | 4 +- 10_Wiki/Topics_Blog/Lucas-Kanade-Method.md | 2 +- 10_Wiki/Topics_Blog/MAP-Estimation.md | 4 +- ...MBA (Master of Business Administration).md | 4 +- 10_Wiki/Topics_Blog/MCP.md | 10 +- 10_Wiki/Topics_Blog/MLA-Format.md | 4 +- 10_Wiki/Topics_Blog/MLOps.md | 6 +- 10_Wiki/Topics_Blog/Machine Learning (ML).md | 4 +- .../Machine-Learning-Foundations.md | 2 +- .../Topics_Blog/Machine-Learning-Lifecycle.md | 2 +- 10_Wiki/Topics_Blog/Macros (매크로).md | 4 +- 10_Wiki/Topics_Blog/Magic-Circle.md | 4 +- 10_Wiki/Topics_Blog/Main Thread.md | 6 +- 10_Wiki/Topics_Blog/Malware-Analysis.md | 4 +- 10_Wiki/Topics_Blog/Management.md | 4 +- 10_Wiki/Topics_Blog/Manhattan-Distance.md | 2 +- 10_Wiki/Topics_Blog/MapReduce.md | 4 +- .../Topics_Blog/Markov-Chain-Monte-Carlo.md | 2 +- 10_Wiki/Topics_Blog/Markov-Chains.md | 4 +- .../Markov-Decision-Process (MDP).md | 4 +- .../Markov-Decision-Process-MDP.md | 2 +- .../Topics_Blog/Markov-Decision-Processes.md | 4 +- .../Master-of-Information-Management.md | 4 +- 10_Wiki/Topics_Blog/Mastery.md | 4 +- 10_Wiki/Topics_Blog/Matrix-Factorization.md | 2 +- .../Topics_Blog/Matrix-Operations-and-AI.md | 2 +- .../Topics_Blog/Mean-Absolute-Error-MAE.md | 2 +- 10_Wiki/Topics_Blog/Mean-Squared-Error-MSE.md | 2 +- ...c Interpretability (기계적 해석 가능성).md | 6 +- 10_Wiki/Topics_Blog/Media-Literacy.md | 4 +- .../Medical-Imaging-Data-Augmentation.md | 4 +- 10_Wiki/Topics_Blog/Memetics.md | 4 +- 10_Wiki/Topics_Blog/Memory-Hierarchy.md | 4 +- .../Memory-Leak-Debugging-in-JavaScript.md | 2 +- 10_Wiki/Topics_Blog/Mental-Models.md | 4 +- .../Mental-Operations-Synthesized.md | 4 +- .../Message-Queues-and-Event-Streams.md | 2 +- 10_Wiki/Topics_Blog/Meta-Learning-in-AI.md | 2 +- .../Micro-interactions-and-Feedback-Loops.md | 2 +- 10_Wiki/Topics_Blog/Micro-interactions.md | 4 +- .../Topics_Blog/Microservices-Architecture.md | 2 +- 10_Wiki/Topics_Blog/Middle-Out-Thinking.md | 4 +- 10_Wiki/Topics_Blog/Midjourney Parameter.md | 6 +- 10_Wiki/Topics_Blog/Midjourney Parameters.md | 6 +- ... V6 및 V7 기반의 이미지 생성 워크플로우.md | 6 +- .../Topics_Blog/Midjourney V7 Draft Mode.md | 6 +- .../Midjourney V7 및 V6 워크플로우.md | 6 +- .../Midjourney V7의 Draft Mode 워크플로우.md | 6 +- ...djourney 브랜드 캠페인 및 무드보드 제작.md | 6 +- 10_Wiki/Topics_Blog/Minimal-Viable-Product.md | 4 +- .../Topics_Blog/Minimum-Viable-Product-MVP.md | 2 +- 10_Wiki/Topics_Blog/Mipmap.md | 4 +- 10_Wiki/Topics_Blog/Mobile-AI-Optimization.md | 2 +- .../Topics_Blog/Mobile-Augmented-Reality.md | 4 +- ...bile-First-Responsive-Design-Principles.md | 2 +- .../Model Context Protocol (MCP).md | 4 +- .../Model-Agnostic-Meta-Learning.md | 2 +- .../Model-Compression-Strategies.md | 2 +- 10_Wiki/Topics_Blog/Model-Compression.md | 4 +- .../Topics_Blog/Model-Deployment-Patterns.md | 2 +- .../Topics_Blog/Model-Drift-and-Monitoring.md | 2 +- 10_Wiki/Topics_Blog/Model-Ensemble-Methods.md | 2 +- .../Model-Interpretability-Tools.md | 2 +- .../Model-Predictive-Control (MPC).md | 4 +- ...odern-Frontend-Engineering-Architecture.md | 2 +- ...React-Application-Architecture-Patterns.md | 2 +- .../Modern-Web-Design-Best-Practices-2025.md | 2 +- .../Modern-Website-Architecture.md | 2 +- .../Modern_Environment_Ecosystem.md | 6 +- .../Modern_React_Engineering_2025.md | 10 +- 10_Wiki/Topics_Blog/Modular-Design.md | 4 +- 10_Wiki/Topics_Blog/Modular-Programming.md | 6 +- 10_Wiki/Topics_Blog/Modularity.md | 4 +- .../Topics_Blog/Momentum-and-Optimization.md | 2 +- .../Monolithic-vs-Microservices.md | 4 +- .../Topics_Blog/Monte-Carlo-Integration.md | 2 +- 10_Wiki/Topics_Blog/Monte-Carlo-Methods.md | 4 +- .../Monte-Carlo-Tree-Search-MCTS.md | 2 +- 10_Wiki/Topics_Blog/Moodboard Creation.md | 6 +- .../Multi-Agent-Reinforcement-Learning.md | 2 +- .../Topics_Blog/Multi-Agent-Systems-MAS.md | 2 +- .../Multi-Head-Attention-Mechanism.md | 2 +- 10_Wiki/Topics_Blog/Multi-agent-System.md | 4 +- .../Topics_Blog/Multi-armed-Bandit-Problem.md | 2 +- 10_Wiki/Topics_Blog/Multimodal-Learning.md | 4 +- .../Topics_Blog/Multinomial-Naive-Bayes.md | 2 +- 10_Wiki/Topics_Blog/Multivariate-Analysis.md | 2 +- 10_Wiki/Topics_Blog/Mutual-Information.md | 2 +- .../NLP (Natural Language Processing).md | 4 +- .../Topics_Blog/NLP-Attention-Mechanisms.md | 2 +- 10_Wiki/Topics_Blog/NVIDIA-CUDA-and-AI.md | 2 +- .../Topics_Blog/Naive-Bayes-Classifiers.md | 2 +- .../Named-Entity-Recognition-NER.md | 2 +- .../National-Language-Processing.md | 2 +- .../Natural-Language-Generation-NLG.md | 2 +- .../Natural-Language-Processing-NLP.md | 2 +- .../Natural-Language-Processing.md | 2 +- .../Topics_Blog/Nearest-Neighbor-Search.md | 2 +- .../Network-Latency-Optimization.md | 2 +- .../Neural-Architecture-Search-NAS.md | 2 +- .../Topics_Blog/Neural-Architecture-Search.md | 2 +- 10_Wiki/Topics_Blog/Neural-Darwinism.md | 2 +- .../Neural-Networks (신경망 기초).md | 2 +- .../Neural-Networks-for-Beginners.md | 2 +- 10_Wiki/Topics_Blog/Neural-Style-Transfer.md | 2 +- .../Neural-Symbolic-Integration.md | 4 +- 10_Wiki/Topics_Blog/Neuro-Symbolic AI.md | 4 +- 10_Wiki/Topics_Blog/Neuro-Symbolic-AI.md | 2 +- 10_Wiki/Topics_Blog/Neurobiology-of-Reward.md | 4 +- .../Neurodevelopmental Disorders.md | 4 +- 10_Wiki/Topics_Blog/Neuroeconomics.md | 4 +- 10_Wiki/Topics_Blog/Neuroergonomics.md | 4 +- 10_Wiki/Topics_Blog/Neuroevolution.md | 2 +- .../Topics_Blog/Neuromuscular-Adaptation.md | 4 +- 10_Wiki/Topics_Blog/Neuromuscular-Control.md | 4 +- ...pharmacology of Substance Use Disorders.md | 4 +- .../Neuroplasticity in Addiction.md | 4 +- .../Neuroplasticity in Motor Learning.md | 4 +- .../Neuroplasticity-in-Motor-Learning.md | 4 +- .../Neuroprosthetics-Development.md | 4 +- .../Topics_Blog/Neuropsychiatric Disorders.md | 4 +- 10_Wiki/Topics_Blog/Neuropsychology.md | 4 +- .../Neurorehabilitation after Stroke.md | 4 +- .../Neurorehabilitation-Post-Stroke.md | 4 +- 10_Wiki/Topics_Blog/Next-js-and-Modern-Web.md | 2 +- 10_Wiki/Topics_Blog/Next.js App Router.md | 12 +- .../Nextjs-App-Router-Architecture.md | 2 +- ... Sky (Large-scale planetary generation).md | 4 +- 10_Wiki/Topics_Blog/No Mans Sky.md | 4 +- 10_Wiki/Topics_Blog/NoSQL-Databases-in-AI.md | 2 +- .../Topics_Blog/Nodejs 메모리 누수 분석.md | 6 +- .../Nodejs 프로덕션 메모리 누수 진단.md | 6 +- .../Nodejs 프로덕션 메모리 병목 분석.md | 2 +- .../Nodejs-Global-Namespace-Augmentation.md | 4 +- 10_Wiki/Topics_Blog/Noise-Reduction-in-AI.md | 2 +- 10_Wiki/Topics_Blog/Noise.md | 4 +- .../Nominal-Typing-in-TypeScript.md | 4 +- ...hotorealistic-Rendering-in-Level-Design.md | 4 +- .../Non-linear-Activation-Functions.md | 2 +- 10_Wiki/Topics_Blog/Non-parametric-Models.md | 2 +- .../Topics_Blog/Normalization-Strategies.md | 2 +- 10_Wiki/Topics_Blog/Normalization.md | 4 +- .../Topics_Blog/Nuclear Deterrence Models.md | 4 +- 10_Wiki/Topics_Blog/Numbers-and-Games.md | 4 +- .../Topics_Blog/Nutritional-Biochemistry.md | 4 +- 10_Wiki/Topics_Blog/OKR.md | 4 +- ...WA vs CWA (개방 세계 vs 폐쇄 세계 가설).md | 4 +- .../Object Pooling (오브젝트 풀링).md | 4 +- .../Object-Detection-Foundations.md | 2 +- .../Object-Oriented-Design-Patterns.md | 4 +- .../Object-Oriented-Programming.md | 2 +- 10_Wiki/Topics_Blog/Objective-Functions.md | 2 +- 10_Wiki/Topics_Blog/Objectivism.md | 2 +- 10_Wiki/Topics_Blog/Observation.md | 4 +- 10_Wiki/Topics_Blog/Occupational-Therapy.md | 4 +- .../Off-policy-vs-On-policy-Learning.md | 2 +- .../Topics_Blog/Okami-Ink-Wash-Aesthetics.md | 4 +- .../Topics_Blog/Olympic-Training-Cycles.md | 4 +- .../Topics_Blog/Olympic-Training-Models.md | 4 +- .../Topics_Blog/Olympic-Training-Protocols.md | 4 +- .../Topics_Blog/Omni Reference (--oref).md | 6 +- 10_Wiki/Topics_Blog/Omni Reference.md | 6 +- 10_Wiki/Topics_Blog/One-Hot-Encoding.md | 2 +- 10_Wiki/Topics_Blog/One-Shot-Learning.md | 2 +- .../Online-Learning-and-Streaming.md | 2 +- .../Topics_Blog/Ontological-Engineering.md | 2 +- .../Ontology-Driven-Relevancy-Filtering.md | 2 +- 10_Wiki/Topics_Blog/Ontology-Engineering.md | 4 +- .../Ontology-Guided Knowledge Extraction.md | 4 +- .../Ontology-and-Knowledge-Representation.md | 2 +- 10_Wiki/Topics_Blog/Ontology.md | 4 +- 10_Wiki/Topics_Blog/Opaque-Types.md | 4 +- 10_Wiki/Topics_Blog/Open-Access-Movement.md | 4 +- .../Topics_Blog/Open-Source-AI-Ecosystem.md | 2 +- 10_Wiki/Topics_Blog/OpenAI-API-Integration.md | 2 +- 10_Wiki/Topics_Blog/Operations-Management.md | 2 +- 10_Wiki/Topics_Blog/Operations-Research.md | 4 +- 10_Wiki/Topics_Blog/Operator-Theory.md | 4 +- 10_Wiki/Topics_Blog/Opportunity-Cost.md | 4 +- .../Optical-Character-Recognition.md | 2 +- 10_Wiki/Topics_Blog/Optimal-Control-Theory.md | 2 +- .../Topics_Blog/Optimization-Algorithms.md | 2 +- 10_Wiki/Topics_Blog/Optimization-in-AI.md | 2 +- 10_Wiki/Topics_Blog/Optimization.md | 4 +- 10_Wiki/Topics_Blog/Ordinal-Data-Analysis.md | 2 +- .../Topics_Blog/Organizational Psychology.md | 4 +- .../Out-of-distribution-Detection.md | 2 +- .../Outer Alignment vs Inner Alignment.md | 4 +- .../Outlier-Detection-Techniques.md | 2 +- 10_Wiki/Topics_Blog/Outside-Thinking.md | 4 +- .../Overfitting-and-Underfitting.md | 2 +- 10_Wiki/Topics_Blog/Overfitting.md | 4 +- .../Topics_Blog/P-Reinforce-Template-Guide.md | 2 +- 10_Wiki/Topics_Blog/P-Reinforce.md | 2 +- 10_Wiki/Topics_Blog/P-Reinforce_1011.md | 4 +- .../PCA-and-Dimension-Reduction.md | 2 +- 10_Wiki/Topics_Blog/PCGML-Frameworks.md | 4 +- 10_Wiki/Topics_Blog/PDF-Format.md | 4 +- .../PEFT (Parameter-Efficient Fine-Tuning).md | 4 +- 10_Wiki/Topics_Blog/PEV_Loop.md | 10 +- 10_Wiki/Topics_Blog/PID-Controllers-in-AI.md | 2 +- 10_Wiki/Topics_Blog/PMI-Technique.md | 4 +- 10_Wiki/Topics_Blog/POMDP.md | 4 +- 10_Wiki/Topics_Blog/PageSpeed Insights.md | 6 +- ...Papers Please (Bureaucratic Simulation).md | 4 +- 10_Wiki/Topics_Blog/Papers-Please.md | 4 +- .../Topics_Blog/Parallel-Computing-in-AI.md | 2 +- 10_Wiki/Topics_Blog/Parallel-Computing.md | 2 +- 10_Wiki/Topics_Blog/Parallel-Processing.md | 4 +- 10_Wiki/Topics_Blog/Parameter Control.md | 6 +- .../Parameter-Efficiency-in-LLMs.md | 2 +- .../Parameter-Efficient Fine-Tuning (PEFT).md | 2 +- 10_Wiki/Topics_Blog/Parameter-Sharing.md | 2 +- 10_Wiki/Topics_Blog/Parameter.md | 6 +- 10_Wiki/Topics_Blog/Pareto-Principle.md | 4 +- .../Partial-Differential-Equations.md | 2 +- .../Topics_Blog/Particle-Filter-Algorithms.md | 2 +- 10_Wiki/Topics_Blog/Pattern-Recognition.md | 2 +- 10_Wiki/Topics_Blog/Pedestrian-Modeling.md | 4 +- .../Topics_Blog/Perceptrons-Foundations.md | 2 +- 10_Wiki/Topics_Blog/Perceptual-Learning.md | 2 +- .../Topics_Blog/Perceptual-Motor-Skills.md | 4 +- .../Performance Management Systems.md | 4 +- 10_Wiki/Topics_Blog/Performance Psychology.md | 4 +- .../Topics_Blog/Performance-Metrics-in-AI.md | 2 +- 10_Wiki/Topics_Blog/Periodization-Theory.md | 4 +- .../Topics_Blog/Personal-Brain-Management.md | 2 +- .../Personal-Information-Security.md | 2 +- .../Topics_Blog/Personalization-Engines.md | 4 +- .../Persuasive Business Writing.md | 6 +- .../Phase-Transitions-in-Learning.md | 2 +- 10_Wiki/Topics_Blog/Philosophy.md | 4 +- 10_Wiki/Topics_Blog/Physical-Intelligence.md | 4 +- ...hysics-Informed Neural Networks (PINNs).md | 2 +- .../Physics-informed-Neural-Networks.md | 2 +- 10_Wiki/Topics_Blog/Physics.md | 4 +- 10_Wiki/Topics_Blog/Pipeline-Parallelism.md | 2 +- 10_Wiki/Topics_Blog/Pivot-Table-Analysis.md | 2 +- 10_Wiki/Topics_Blog/Platform-Engineering.md | 2 +- .../Topics_Blog/Player-Experience-Modeling.md | 4 +- .../Player-Psyche-Profiling-Framework.md | 4 +- .../Plutchiks-Wheel-of-Emotions.md | 4 +- 10_Wiki/Topics_Blog/Poetic-Computation.md | 2 +- 10_Wiki/Topics_Blog/Point-Cloud-Processing.md | 2 +- 10_Wiki/Topics_Blog/Point-of-Sale.md | 4 +- .../Topics_Blog/Policy-Gradient-Methods.md | 2 +- 10_Wiki/Topics_Blog/Policy-Optimization.md | 4 +- 10_Wiki/Topics_Blog/Policy-Surveillance.md | 4 +- 10_Wiki/Topics_Blog/PolicyIQ.md | 4 +- .../Polymorphism-in-Engine-Architecture.md | 4 +- 10_Wiki/Topics_Blog/Pooling.md | 4 +- 10_Wiki/Topics_Blog/Pose-Estimation.md | 2 +- 10_Wiki/Topics_Blog/Positive Prompts.md | 6 +- 10_Wiki/Topics_Blog/Positive-Reinforcement.md | 2 +- 10_Wiki/Topics_Blog/Post_Drafts/.gitkeep | 0 .../Posterior-and-Prior-Probability.md | 2 +- 10_Wiki/Topics_Blog/Poverty-Cycle-Dynamics.md | 4 +- 10_Wiki/Topics_Blog/Poverty-Simulation.md | 4 +- 10_Wiki/Topics_Blog/Practical-Cryptography.md | 2 +- 10_Wiki/Topics_Blog/Pre-Mortem-Analysis.md | 4 +- .../Topics_Blog/Pre-processing-Data-for-AI.md | 2 +- .../Topics_Blog/Precision-Recall-Tradeoff.md | 2 +- 10_Wiki/Topics_Blog/Precision-Recursion.md | 4 +- 10_Wiki/Topics_Blog/Predictive-Analytics.md | 2 +- 10_Wiki/Topics_Blog/Predictive-Coding.md | 2 +- 10_Wiki/Topics_Blog/Prenatal-Neurology.md | 4 +- .../Preserving-State-in-Procedural-Worlds.md | 4 +- .../Principal-Component-Analysis.md | 2 +- .../Principle-Component-Analysis.md | 4 +- .../Topics_Blog/Principle-of-Least-Action.md | 2 +- ...rinciples of Structuralism (Linguistic).md | 4 +- .../Topics_Blog/Principles-of-Architecture.md | 4 +- .../Topics_Blog/Principles-of-Data-Connect.md | 4 +- .../Principles-of-Structuralism.md | 4 +- 10_Wiki/Topics_Blog/Principles.md | 4 +- .../Prioritized-Experience-Replay.md | 2 +- .../Topics_Blog/Prisoners-Dilemma-Models.md | 4 +- .../Prisons-and-Self-Correction.md | 4 +- 10_Wiki/Topics_Blog/Privacy-Preserving-AI.md | 2 +- .../Probabilistic-Graphical-Models.md | 2 +- .../Topics_Blog/Probabilistic-Reasoning.md | 4 +- 10_Wiki/Topics_Blog/Probability Theory.md | 4 +- .../Probability and Logic Fusion.md | 4 +- .../Probability-Theory-Foundations.md | 2 +- 10_Wiki/Topics_Blog/Problem-Solving.md | 4 +- ...Generation via Machine Learning (PCGML).md | 4 +- .../Procedural Narrative Generation.md | 4 +- .../Procedural Rhetoric (In Gaming).md | 4 +- .../Procedural-Architecture-Systems.md | 4 +- 10_Wiki/Topics_Blog/Procedural-Knowledge.md | 4 +- .../Topics_Blog/Procedural-Level-Geometry.md | 4 +- 10_Wiki/Topics_Blog/Procedural-Rhetoric.md | 4 +- .../Topics_Blog/Process-Automation-with-AI.md | 2 +- 10_Wiki/Topics_Blog/Processing.md | 4 +- 10_Wiki/Topics_Blog/Product-Led-Growth.md | 4 +- 10_Wiki/Topics_Blog/Product-Management.md | 4 +- 10_Wiki/Topics_Blog/Product-Marketing.md | 4 +- 10_Wiki/Topics_Blog/Product-Thinking-in-AI.md | 2 +- .../Productivity-Hacks-for-Devs.md | 2 +- .../Topics_Blog/Profiling-and-Optimization.md | 2 +- 10_Wiki/Topics_Blog/Progressive-Disclosure.md | 2 +- .../Project-Management-Best-Practices.md | 2 +- 10_Wiki/Topics_Blog/Project-Management.md | 4 +- 10_Wiki/Topics_Blog/Prompt Engineering.md | 10 +- 10_Wiki/Topics_Blog/Prompt Structure.md | 6 +- .../Prompt-Engineering-Foundations.md | 2 +- 10_Wiki/Topics_Blog/Prompt-Engineering.md | 2 +- 10_Wiki/Topics_Blog/Prop Drilling.md | 10 +- 10_Wiki/Topics_Blog/Proprioception.md | 4 +- 10_Wiki/Topics_Blog/Pros-Cons-Table.md | 4 +- 10_Wiki/Topics_Blog/Protocols.md | 4 +- 10_Wiki/Topics_Blog/Prototyping.md | 4 +- .../Proximal Policy Optimization (PPO).md | 4 +- .../Proximal-Policy-Optimization.md | 2 +- 10_Wiki/Topics_Blog/Pruning-Techniques.md | 2 +- .../Ps-Reinforce Policy Framework.md | 4 +- 10_Wiki/Topics_Blog/Ps-Reinforce.md | 4 +- 10_Wiki/Topics_Blog/Psychology & Behavior.md | 4 +- 10_Wiki/Topics_Blog/Psychology-of-Learning.md | 2 +- 10_Wiki/Topics_Blog/Psychology.md | 4 +- .../Pull Request (PR) 워크플로우.md | 4 +- 10_Wiki/Topics_Blog/Pull Request (PR).md | 6 +- 10_Wiki/Topics_Blog/Pull-Request.md | 4 +- 10_Wiki/Topics_Blog/Purpose.md | 4 +- 10_Wiki/Topics_Blog/PyTorch-Foundations.md | 2 +- 10_Wiki/Topics_Blog/PyTorch-Lightning.md | 2 +- .../Topics_Blog/Python-for-Data-Science.md | 2 +- 10_Wiki/Topics_Blog/Q-Learning Foundations.md | 2 +- 10_Wiki/Topics_Blog/Quality Gates.md | 4 +- 10_Wiki/Topics_Blog/Quality-Control.md | 4 +- .../Quantitative Economics (수량경제학).md | 4 +- .../Topics_Blog/Quantization-Foundations.md | 2 +- 10_Wiki/Topics_Blog/Quantization.md | 4 +- .../Topics_Blog/Quantum Computing (Intro).md | 4 +- .../Topics_Blog/Quantum-Computing-for-AI.md | 2 +- 10_Wiki/Topics_Blog/Quantum-Computing.md | 4 +- .../Topics_Blog/Quantum-Machine-Learning.md | 2 +- 10_Wiki/Topics_Blog/Query-Optimization.md | 4 +- .../Topics_Blog/Queue-Management-Systems.md | 2 +- 10_Wiki/Topics_Blog/Quick-Wins.md | 4 +- 10_Wiki/Topics_Blog/RAG (검색 증강 생성).md | 4 +- .../Topics_Blog/RAG-and-Document-Retrieval.md | 2 +- 10_Wiki/Topics_Blog/RAG.md | 10 +- .../RLAIF (AI 피드백 기반 강화학습).md | 4 +- .../RLHF (인간 피드백 기반 강화 학습).md | 4 +- 10_Wiki/Topics_Blog/RL_Neuroscience.md | 2 +- 10_Wiki/Topics_Blog/RMSProp-Optimizer.md | 2 +- 10_Wiki/Topics_Blog/RNN.md | 4 +- 10_Wiki/Topics_Blog/ROC-AUC-Curves.md | 2 +- 10_Wiki/Topics_Blog/ROUGE-Metrics.md | 2 +- .../Topics_Blog/Random-Forest-Classifiers.md | 2 +- 10_Wiki/Topics_Blog/Randomized-Algorithms.md | 2 +- 10_Wiki/Topics_Blog/Ranking-Algorithms.md | 2 +- 10_Wiki/Topics_Blog/Rapid-Prototyping.md | 4 +- .../Topics_Blog/Re-renders Optimization.md | 12 +- .../Topics_Blog/ReLU-Activation-Functions.md | 2 +- .../React 18 Concurrent Features.md | 12 +- .../Topics_Blog/React Codebase Refactoring.md | 16 +- .../Topics_Blog/React DevTools Profiler.md | 12 +- 10_Wiki/Topics_Blog/React-Context-API.md | 2 +- .../React-Error-Boundaries-and-Handling.md | 2 +- 10_Wiki/Topics_Blog/React-Hooks.md | 2 +- 10_Wiki/Topics_Blog/React.lazy().md | 18 +- .../React_Clean_Code_Best_Practices.md | 6 +- 10_Wiki/Topics_Blog/React_Hooks_Deep_Dive.md | 6 +- 10_Wiki/Topics_Blog/React_Mental_Model.md | 6 +- .../React_Performance_Optimization.md | 6 +- .../React_State_Management_Strategy.md | 6 +- 10_Wiki/Topics_Blog/React_Testing_Strategy.md | 6 +- 10_Wiki/Topics_Blog/Reactive-Programming.md | 4 +- .../Topics_Blog/Real User Monitoring (RUM).md | 16 +- 10_Wiki/Topics_Blog/Real-Time Translation.md | 6 +- .../Topics_Blog/Real-time-Data-Streaming.md | 2 +- 10_Wiki/Topics_Blog/Real-time-Operation.md | 4 +- 10_Wiki/Topics_Blog/Reasoning & Planning.md | 12 +- 10_Wiki/Topics_Blog/Reasoning.md | 4 +- 10_Wiki/Topics_Blog/Recommendation-Systems.md | 2 +- .../Recording Academy (The Grammys).md | 2 +- .../Topics_Blog/Recurrent-Neural-Networks.md | 2 +- 10_Wiki/Topics_Blog/Redux.md | 14 +- .../Refactoring-Legacy-React-Codebases.md | 2 +- 10_Wiki/Topics_Blog/Reference-Management.md | 4 +- 10_Wiki/Topics_Blog/Reference.md | 4 +- 10_Wiki/Topics_Blog/Refinement.md | 4 +- 10_Wiki/Topics_Blog/Reflection.md | 4 +- .../Regression-Analysis-Foundations.md | 2 +- .../Topics_Blog/Regularization-Strategies.md | 2 +- .../Topics_Blog/Regularization-Techniques.md | 2 +- 10_Wiki/Topics_Blog/Regularization.md | 4 +- .../Reinforcement Learning (RL).md | 4 +- ...ment Learning for Automated Playtesting.md | 4 +- ...ement-Learning-from-Human-Feedback-RLHF.md | 2 +- 10_Wiki/Topics_Blog/Reinforcement-Learning.md | 4 +- 10_Wiki/Topics_Blog/Related-Work.md | 4 +- .../Relational Algebra in Databases.md | 4 +- 10_Wiki/Topics_Blog/Relational-Database.md | 4 +- 10_Wiki/Topics_Blog/Relational-Databases.md | 2 +- 10_Wiki/Topics_Blog/Relative-Positioning.md | 2 +- 10_Wiki/Topics_Blog/Relevance-Feedback.md | 2 +- 10_Wiki/Topics_Blog/Reliability.md | 4 +- .../Topics_Blog/Reliability_Safety_First.md | 6 +- 10_Wiki/Topics_Blog/Remote-Rehabilitation.md | 4 +- 10_Wiki/Topics_Blog/Replenishment.md | 4 +- 10_Wiki/Topics_Blog/Reports.md | 4 +- 10_Wiki/Topics_Blog/Repository.md | 4 +- 10_Wiki/Topics_Blog/Representation Theory.md | 2 +- 10_Wiki/Topics_Blog/Requirements.md | 4 +- 10_Wiki/Topics_Blog/ResNet-Architectures.md | 2 +- 10_Wiki/Topics_Blog/Research-Framework.md | 4 +- 10_Wiki/Topics_Blog/Research-Methodology.md | 4 +- 10_Wiki/Topics_Blog/Research.md | 4 +- 10_Wiki/Topics_Blog/Residual-Networks.md | 2 +- 10_Wiki/Topics_Blog/Resilience.md | 4 +- 10_Wiki/Topics_Blog/Resource-Allocation.md | 4 +- 10_Wiki/Topics_Blog/Resource-Management.md | 4 +- 10_Wiki/Topics_Blog/Restorative Justice.md | 4 +- 10_Wiki/Topics_Blog/Retainers(유지 경로).md | 6 +- 10_Wiki/Topics_Blog/Retaining Path.md | 6 +- .../Retrieval-Augmented Generation (RAG).md | 10 +- .../Retrieval-Augmented-Generation-RAG.md | 6 +- 10_Wiki/Topics_Blog/Revenge-Cycle-Dynamics.md | 4 +- .../Topics_Blog/Reward Hacking (보상 해킹).md | 4 +- .../Topics_Blog/Reward Prediction Error.md | 4 +- 10_Wiki/Topics_Blog/Reward-Shaping-in-RL.md | 2 +- 10_Wiki/Topics_Blog/Ridge-Regression.md | 2 +- 10_Wiki/Topics_Blog/Risk Management.md | 4 +- .../Topics_Blog/Risk-Assessment-with-AI.md | 2 +- 10_Wiki/Topics_Blog/Risk-Management.md | 4 +- 10_Wiki/Topics_Blog/Risk-Orchestration.md | 4 +- 10_Wiki/Topics_Blog/Roadmap.md | 4 +- 10_Wiki/Topics_Blog/Robotics-Foundations.md | 2 +- 10_Wiki/Topics_Blog/Robotics.md | 4 +- .../Topics_Blog/Robust-Machine-Learning.md | 2 +- 10_Wiki/Topics_Blog/Robustness.md | 4 +- .../Role of Conflict in Narrative.md | 4 +- 10_Wiki/Topics_Blog/Rollup.md | 14 +- .../Topics_Blog/Root-Cause-Analysis-RCA.md | 2 +- 10_Wiki/Topics_Blog/Root-Mean-Square-Error.md | 2 +- .../Topics_Blog/Roughness (그래픽 및 물리).md | 4 +- 10_Wiki/Topics_Blog/Rule-based-Systems.md | 2 +- 10_Wiki/Topics_Blog/SAR.md | 4 +- ...T (Static Application Security Testing).md | 4 +- .../SAST (정적 애플리케이션 보안 테스트).md | 6 +- .../SAST (정적 애플리케이션 보안 테스팅).md | 6 +- 10_Wiki/Topics_Blog/SAST.md | 4 +- .../SCM (Supply Chain Management).md | 4 +- .../SDLC (소프트웨어 개발 수명 주기).md | 6 +- 10_Wiki/Topics_Blog/SEO.md | 2 +- .../SFT (Supervised Fine-Tuning).md | 4 +- 10_Wiki/Topics_Blog/SME.md | 4 +- 10_Wiki/Topics_Blog/SOTA.md | 4 +- 10_Wiki/Topics_Blog/SOW.md | 4 +- 10_Wiki/Topics_Blog/SPOF.md | 4 +- 10_Wiki/Topics_Blog/SQL-Performance-Tuning.md | 2 +- 10_Wiki/Topics_Blog/SRE.md | 4 +- .../SaaS (Software as a Service).md | 4 +- 10_Wiki/Topics_Blog/SaaS.md | 4 +- 10_Wiki/Topics_Blog/Safety & Reliability.md | 4 +- 10_Wiki/Topics_Blog/Sales-Strategy.md | 4 +- 10_Wiki/Topics_Blog/Sampling-Techniques.md | 2 +- .../Topics_Blog/Scalability-in-AI-Systems.md | 2 +- 10_Wiki/Topics_Blog/Scalability.md | 4 +- .../Scalable-Design-System-Governance.md | 2 +- 10_Wiki/Topics_Blog/Scaling-Laws-for-LLMs.md | 2 +- 10_Wiki/Topics_Blog/Scheduler-Design-in-ML.md | 2 +- .../Topics_Blog/Schema-Design-for-NoSQL.md | 2 +- 10_Wiki/Topics_Blog/Schema.md | 4 +- 10_Wiki/Topics_Blog/Science of Failure.md | 4 +- .../Topics_Blog/Scientific Communication.md | 4 +- .../Scientific-Computing-with-Python.md | 2 +- 10_Wiki/Topics_Blog/Scientific-Method.md | 4 +- 10_Wiki/Topics_Blog/Scripts.md | 4 +- .../Topics_Blog/Search-Engine-Optimization.md | 2 +- 10_Wiki/Topics_Blog/Search-Methodology.md | 4 +- 10_Wiki/Topics_Blog/Search-Optimization.md | 4 +- 10_Wiki/Topics_Blog/Search-Space.md | 4 +- 10_Wiki/Topics_Blog/Search-Strategy.md | 4 +- 10_Wiki/Topics_Blog/Search.md | 4 +- 10_Wiki/Topics_Blog/Secondary-Research.md | 4 +- .../Secure-Multi-party-Computation.md | 2 +- .../Topics_Blog/Security-Best-Practices.md | 2 +- 10_Wiki/Topics_Blog/Security-Governance.md | 6 +- 10_Wiki/Topics_Blog/Seed.md | 4 +- 10_Wiki/Topics_Blog/Segmentsai.md | 6 +- .../Topics_Blog/Self-Attention-Mechanisms.md | 2 +- .../Self-Driving-Car-Foundations.md | 2 +- .../Self-Play (자기 대결 기반 강화학습).md | 4 +- .../Self-Supervised Learning (SSL).md | 4 +- .../Topics_Blog/Self-Supervised-Learning.md | 2 +- .../Semantic Grounding & Provenance.md | 4 +- .../Topics_Blog/Semantic-HTML-Foundations.md | 2 +- .../Topics_Blog/Semantic-Search-with-AI.md | 2 +- 10_Wiki/Topics_Blog/Semantic-Search.md | 2 +- 10_Wiki/Topics_Blog/Semantics & Ontology.md | 4 +- 10_Wiki/Topics_Blog/Semgrep Assistant.md | 4 +- 10_Wiki/Topics_Blog/Sensitivity-Analysis.md | 4 +- 10_Wiki/Topics_Blog/Sensor-Fusion.md | 2 +- .../Topics_Blog/Sentiment-Analysis-Models.md | 2 +- 10_Wiki/Topics_Blog/Sentiment-Analysis.md | 4 +- 10_Wiki/Topics_Blog/Separation_of_Concerns.md | 4 +- 10_Wiki/Topics_Blog/Sequence-Modeling.md | 4 +- .../Sequence-to-Sequence-Models.md | 2 +- .../Serverless-Computing-for-AI.md | 2 +- .../Service-oriented-Architecture.md | 2 +- .../Shadowing-and-Observability.md | 2 +- .../Topics_Blog/Shape-Feature-Extraction.md | 2 +- .../Topics_Blog/Sharding-and-Partitioning.md | 2 +- 10_Wiki/Topics_Blog/Shift.md | 4 +- 10_Wiki/Topics_Blog/Signal in Noise.md | 4 +- .../Signal-Processing-Foundations.md | 2 +- 10_Wiki/Topics_Blog/Signature Style Design.md | 6 +- .../Topics_Blog/Similarity-Metrics-in-AI.md | 2 +- 10_Wiki/Topics_Blog/Similarity-Metrics.md | 4 +- 10_Wiki/Topics_Blog/Simulated-Annealing.md | 2 +- .../Topics_Blog/Simulation-Environments.md | 2 +- .../Simulator Sickness Questionnaire (SSQ).md | 2 +- .../Singular-Value-Decomposition.md | 2 +- .../Topics_Blog/Six-Sigma-Methodologies.md | 2 +- .../Topics_Blog/Skybound Protocol 코드리뷰.md | 2 +- 10_Wiki/Topics_Blog/Slack-Bot-Development.md | 2 +- .../Topics_Blog/Smart-Contract-Auditing.md | 2 +- .../Topics_Blog/Snowflake-Data-Warehousing.md | 2 +- ...r Labs 등 종합 애플리케이션 보안 플랫폼.md | 6 +- 10_Wiki/Topics_Blog/Social Systems Theory.md | 4 +- .../Topics_Blog/Social-Network-Analysis.md | 2 +- 10_Wiki/Topics_Blog/Sociology of Knowledge.md | 4 +- 10_Wiki/Topics_Blog/Soft Navigation.md | 2 +- .../Topics_Blog/Soft-Skills-Development.md | 4 +- .../Software Engineering Agents (SWE).md | 8 +- .../Software-Architecture-Patterns.md | 2 +- .../Topics_Blog/Software-Design-Principles.md | 4 +- 10_Wiki/Topics_Blog/Solitude-Optimization.md | 4 +- 10_Wiki/Topics_Blog/Solow Growth Model.md | 4 +- 10_Wiki/Topics_Blog/Solution.md | 4 +- 10_Wiki/Topics_Blog/SonarQube.md | 6 +- 10_Wiki/Topics_Blog/Sorting.md | 4 +- .../Topics_Blog/Sound Design Principles.md | 4 +- 10_Wiki/Topics_Blog/Source-Control.md | 4 +- .../Topics_Blog/Space-based-Architecture.md | 2 +- 10_Wiki/Topics_Blog/Sparse-Data-Handling.md | 2 +- 10_Wiki/Topics_Blog/Spatial-Data-Analysis.md | 2 +- 10_Wiki/Topics_Blog/Specification.md | 4 +- 10_Wiki/Topics_Blog/Spectral-Clustering.md | 2 +- 10_Wiki/Topics_Blog/Speculative-Design.md | 4 +- .../Speech-Recognition-Foundations.md | 2 +- 10_Wiki/Topics_Blog/Speech-Synthesis.md | 4 +- .../Spiking-Neural-Networks-SNNs.md | 2 +- .../Topics_Blog/Stability vs Flexibility.md | 4 +- .../Stable Diffusion Image Optimization.md | 6 +- .../Topics_Blog/Stable Diffusion Weights.md | 6 +- .../Stable Diffusion 오픈소스 제어.md | 6 +- .../Stable Diffusion의 가중치 제어 문법.md | 6 +- 10_Wiki/Topics_Blog/Stacked-Generalization.md | 2 +- 10_Wiki/Topics_Blog/Stages-of-Grief.md | 4 +- 10_Wiki/Topics_Blog/Stakeholder.md | 4 +- .../Standard-Deviation-and-Variance.md | 2 +- .../Standard-Operating-Procedure.md | 4 +- .../Standardization vs Innovation.md | 4 +- 10_Wiki/Topics_Blog/Startup.md | 4 +- .../Topics_Blog/State Space Model (SSM).md | 4 +- ...e-Management-Architecture-and-Ownership.md | 2 +- .../Topics_Blog/State-Management-Patterns.md | 2 +- 10_Wiki/Topics_Blog/State-Space-Models.md | 2 +- 10_Wiki/Topics_Blog/State-Space.md | 4 +- 10_Wiki/Topics_Blog/State.md | 4 +- ...tic Application Security Testing (SAST).md | 4 +- .../Static-Site-Generation-with-Gatsby.md | 2 +- 10_Wiki/Topics_Blog/Statistical-Analysis.md | 4 +- .../Statistical-Hypothesis-Testing.md | 2 +- .../Statistical-Learning-Theory.md | 2 +- 10_Wiki/Topics_Blog/Statistical-Power.md | 2 +- .../Topics_Blog/Statistics & Data Analysis.md | 4 +- 10_Wiki/Topics_Blog/Statistics.md | 4 +- 10_Wiki/Topics_Blog/Steel Division 시리즈.md | 4 +- 10_Wiki/Topics_Blog/Stem-Analysis.md | 4 +- .../Stochastic-Gradient-Descent-SGD.md | 2 +- .../Stochastic-Gradient-Descent.md | 2 +- 10_Wiki/Topics_Blog/Storage-Area-Networks.md | 2 +- 10_Wiki/Topics_Blog/Storage.md | 4 +- .../Topics_Blog/Storytelling in Business.md | 10 +- 10_Wiki/Topics_Blog/Storytelling/.gitkeep | 0 .../AI-Driven Narrative Systems.md | 6 +- .../Storytelling/AI & Narrative/Index.md | 2 +- .../AI & Psychology/Affective Computing.md | 6 +- .../Storytelling/AI & Psychology/Index.md | 2 +- 10_Wiki/Topics_Blog/Storytelling/Index.md | 6 +- .../ABA(Applied Behavior Analysis).md | 6 +- .../Addiction Neuroscience.md | 6 +- .../Agent-Based Modeling.md | 6 +- .../Agent-Based-Modeling.md | 6 +- .../Amygdala Hyperactivity.md | 6 +- .../Psychology & Behavior/Index.md | 12 +- ...상의 역효과 (Overjustification Effect).md | 6 +- 10_Wiki/Topics_Blog/Straightening.md | 4 +- .../Topics_Blog/Strategic Communication.md | 10 +- 10_Wiki/Topics_Blog/Strategic-Alignment.md | 2 +- 10_Wiki/Topics_Blog/Strategic-Ambiguity.md | 4 +- .../Topics_Blog/Strategic-Planning-for-AI.md | 2 +- 10_Wiki/Topics_Blog/Strategic-Planning.md | 4 +- 10_Wiki/Topics_Blog/Strategic-Thinking.md | 2 +- 10_Wiki/Topics_Blog/Strategy.md | 4 +- .../Stream-Processing-Architectures.md | 2 +- 10_Wiki/Topics_Blog/Structural Principles.md | 4 +- .../Structural-Equation-Modeling.md | 2 +- 10_Wiki/Topics_Blog/Structuralism.md | 4 +- .../Topics_Blog/Style Reference (--sref).md | 8 +- 10_Wiki/Topics_Blog/Style-Transfer-in-AI.md | 2 +- 10_Wiki/Topics_Blog/Style-Transfer.md | 4 +- 10_Wiki/Topics_Blog/Styling_Governance.md | 6 +- .../Supercell의 모바일 게임 개발.md | 6 +- 10_Wiki/Topics_Blog/Superficiality-Metrics.md | 4 +- .../Supervised-Learning (지도 학습 기초).md | 2 +- .../Supervised-Learning-Foundations.md | 2 +- 10_Wiki/Topics_Blog/Supervised-Learning.md | 4 +- 10_Wiki/Topics_Blog/Supply-Chain.md | 4 +- .../Topics_Blog/Support-Vector-Machines.md | 2 +- 10_Wiki/Topics_Blog/Support.md | 4 +- 10_Wiki/Topics_Blog/Sustainability.md | 4 +- 10_Wiki/Topics_Blog/Swarm Intelligence.md | 4 +- 10_Wiki/Topics_Blog/Swarm-Intelligence.md | 2 +- .../Symbolic-AI vs Connectionism.md | 2 +- 10_Wiki/Topics_Blog/Symbols.md | 4 +- 10_Wiki/Topics_Blog/Symmetric-Encryption.md | 2 +- .../Topics_Blog/Symmetry-and-Invariance.md | 4 +- 10_Wiki/Topics_Blog/Synergy.md | 4 +- .../Topics_Blog/Synthesized Intelligence.md | 4 +- .../Topics_Blog/Synthetic-Data-Generation.md | 2 +- 10_Wiki/Topics_Blog/Synthetic-Data.md | 4 +- .../System Prompt (시스템 프롬프트).md | 4 +- .../Topics_Blog/System-Architecture-Design.md | 2 +- .../Topics_Blog/System-Design for AI Scale.md | 2 +- .../System-Design-Interview-Prep.md | 2 +- .../Topics_Blog/System-Dynamics-Modeling.md | 2 +- 10_Wiki/Topics_Blog/System-Theory.md | 4 +- .../Topics_Blog/System_Debugging_Protocol.md | 4 +- 10_Wiki/Topics_Blog/Systems Thinking.md | 4 +- 10_Wiki/Topics_Blog/Systems-Thinking.md | 4 +- 10_Wiki/Topics_Blog/TDD.md | 4 +- 10_Wiki/Topics_Blog/TS-Declaration-Files.md | 4 +- .../Topics_Blog/Tableau-Data-Visualization.md | 2 +- .../Topics_Blog/Target-Function-Profiling.md | 4 +- 10_Wiki/Topics_Blog/Task-Management.md | 4 +- 10_Wiki/Topics_Blog/Technical-Architecture.md | 4 +- 10_Wiki/Topics_Blog/Technical-Debt.md | 4 +- .../Temporal-Difference-Learning.md | 2 +- 10_Wiki/Topics_Blog/TensorFlow-Foundations.md | 2 +- ...rm-Frequency-Inverse-Document-Frequency.md | 2 +- 10_Wiki/Topics_Blog/Terminology.md | 4 +- .../Terraform-Infrastructure-as-Code.md | 2 +- ...mpute Scaling (추론 시간 계산 스케일링).md | 4 +- 10_Wiki/Topics_Blog/Testing.md | 4 +- .../Tetris_Project_Retrospective.md | 2 +- 10_Wiki/Topics_Blog/Text-Mining.md | 4 +- .../Topics_Blog/Text-to-Speech-Synthesis.md | 2 +- .../The Evolution of Music Distribution.md | 4 +- .../Theoretical-Computer-Science.md | 2 +- .../Theory of Constraints (TOC).md | 4 +- .../Topics_Blog/Theory-of-Mind (ToM) in AI.md | 2 +- 10_Wiki/Topics_Blog/Thought-Architecture.md | 4 +- .../Threejs WebGL 렌더링 최적화.md | 4 +- 10_Wiki/Topics_Blog/Threejs WebGPURenderer.md | 6 +- 10_Wiki/Topics_Blog/Threejs 성능 최적화.md | 4 +- 10_Wiki/Topics_Blog/Time-Series-Analysis.md | 4 +- .../Topics_Blog/Time-Step-Logic-in-Games.md | 2 +- .../Topics_Blog/Tokenization-Strategies.md | 2 +- .../Topics_Blog/Tool-Usage-Optimization.md | 4 +- .../Toxicity-and-Bias-Mitigation.md | 4 +- 10_Wiki/Topics_Blog/Transfer Learning.md | 4 +- .../Transfer-Learning (전이 학습 기초).md | 2 +- .../Topics_Blog/Transformer-Architecture.md | 2 +- 10_Wiki/Topics_Blog/Transformers.md | 4 +- 10_Wiki/Topics_Blog/Tripledot Studios.md | 6 +- 10_Wiki/Topics_Blog/Trustworthy-AI.md | 2 +- 10_Wiki/Topics_Blog/Turing Test.md | 4 +- .../Topics_Blog/Turing-Machine Foundations.md | 2 +- .../Topics_Blog/Type 1 vs Type 2 Errors.md | 4 +- 10_Wiki/Topics_Blog/TypeScript_Type_Safety.md | 6 +- 10_Wiki/Topics_Blog/UX-Design-Principles.md | 2 +- .../Uber-Base-Web-Design-System.md | 2 +- 10_Wiki/Topics_Blog/Ultra-Efficiency.md | 4 +- .../Topics_Blog/Uncertainty-Quantification.md | 2 +- .../Topics_Blog/Unconscious Structuralism.md | 4 +- .../Understanding Complex Systems.md | 4 +- .../Universal Basic Income (UBI).md | 4 +- .../Universal-Approximation-Theorem.md | 2 +- 10_Wiki/Topics_Blog/Universal-Grammar.md | 4 +- ...nsupervised-Learning (비지도 학습 기초).md | 2 +- 10_Wiki/Topics_Blog/User Acquisition (UA).md | 6 +- 10_Wiki/Topics_Blog/V7 Draft Mode Workflow.md | 6 +- .../Variational Autoencoders (VAE).md | 4 +- .../Variational-Autoencoders-VAE.md | 4 +- 10_Wiki/Topics_Blog/Vary Region (인페인팅).md | 6 +- .../Topics_Blog/Vector-Database Selection.md | 2 +- 10_Wiki/Topics_Blog/Victimhood-Narratives.md | 4 +- .../Viral-Dynamics-and-Network-Effects.md | 4 +- .../Visual-Effects-VFX-in-Games.md | 2 +- 10_Wiki/Topics_Blog/Visual-Effects-VFX.md | 4 +- .../Topics_Blog/Vite + React 성능 최적화.md | 16 +- 10_Wiki/Topics_Blog/Vite Build System.md | 14 +- 10_Wiki/Topics_Blog/Vite Build Tool.md | 14 +- 10_Wiki/Topics_Blog/Vocabulary-Expansion.md | 4 +- .../Voice-Assistant-Architecture.md | 2 +- .../WARNO 그래픽 엔진 업그레이드 프로젝트.md | 4 +- .../Topics_Blog/WARNO 데이터 기반 밸런싱.md | 4 +- 10_Wiki/Topics_Blog/WARNO 데이터 기반 설계.md | 4 +- ...멀티플레이어 및 경쟁 플레이 밸런스 패치.md | 4 +- 10_Wiki/Topics_Blog/WARNO 모딩(Modding).md | 4 +- 10_Wiki/Topics_Blog/WARNO 모딩.md | 4 +- .../WARNO 밸런싱 및 사단 시스템.md | 4 +- ...ARNO 사후 관리 (Post-Launch Management).md | 4 +- ...(Real-time Tactics) 및 Army General 캠페인.md | 4 +- .../WARNO 전술 시뮬레이션 시스템.md | 4 +- .../WARNO 전투 메커니즘 (Combat Mechanics).md | 4 +- .../WARNO 커뮤니티 데이터 도구 생태계.md | 4 +- .../Topics_Blog/WARNO 커뮤니티 모딩 생태계.md | 4 +- 10_Wiki/Topics_Blog/WARNO-DATA Wiki.md | 4 +- 10_Wiki/Topics_Blog/WARNO-DATA 프로젝트.md | 4 +- 10_Wiki/Topics_Blog/WARNO.md | 4 +- 10_Wiki/Topics_Blog/WME (Warno Mod Editor).md | 4 +- ...arno-Armory (커뮤니티 데이터 분석 도구).md | 4 +- .../War-Yes 및 Warno-Armory 도구.md | 4 +- 10_Wiki/Topics_Blog/Wargame 시리즈.md | 4 +- .../Topics_Blog/Warno 데이터 기반 설계.md | 4 +- 10_Wiki/Topics_Blog/Warno-Armory.md | 4 +- .../Web Performance Optimization.md | 6 +- .../Web-Rendering-Strategies-CSR-vs-SSR.md | 2 +- .../Topics_Blog/Web3-and-AI-Integration.md | 2 +- .../WebSplatter (3D Gaussian Splatting).md | 4 +- 10_Wiki/Topics_Blog/What-is-AI.md | 4 +- 10_Wiki/Topics_Blog/Wicked-Problems.md | 4 +- 10_Wiki/Topics_Blog/Word-Representation.md | 4 +- 10_Wiki/Topics_Blog/Work-Displacement.md | 4 +- 10_Wiki/Topics_Blog/Workflow-Integrity.md | 4 +- 10_Wiki/Topics_Blog/Working-Backwards.md | 4 +- 10_Wiki/Topics_Blog/Zen-Pop.md | 2 +- .../Zero Shot and Few Shot Learning.md | 4 +- .../Topics_Blog/Zero-Shot-Chain-of-Thought.md | 4 +- 10_Wiki/Topics_Blog/Zero-Shot-Learning.md | 2 +- .../agargaro의 오픈 소스 라이브러리.md | 4 +- 10_Wiki/Topics_Blog/clinicjs.md | 4 +- .../stochastic gradient descent.md | 2 +- 10_Wiki/Topics_Blog/가용성 (Availability).md | 4 +- ...위보 상성 (Rock-paper-scissors principle).md | 4 +- .../Topics_Blog/가중치 (Prompt Weights).md | 4 +- .../공급망 공격 (Supply Chain Attack).md | 4 +- .../네거티브 프롬프트(Negative Prompt).md | 6 +- .../Topics_Blog/드래프트 모드 (Draft Mode).md | 6 +- .../디퓨전 모델 (Diffusion Models).md | 6 +- .../Topics_Blog/리믹스 모드 (Remix Mode).md | 6 +- ...비스 아키텍처 (Microservices Architecture).md | 4 +- 10_Wiki/Topics_Blog/매개변수(Parameters).md | 6 +- ...딩 커뮤니티 도구 (War-Yes, Warno-Armory).md | 4 +- ... V7 드래프트 모드 및 옴니 참조 워크플로우.md | 6 +- ... V7 및 V8 알파 (Midjourney V7 & V8.1 Alpha).md | 6 +- .../미드저니 V7 및 V8.1 Alpha 워크플로우.md | 6 +- ...미드저니 V7 및 드래프트 모드 워크플로우.md | 6 +- ...프트 일관성 유지 (Midjourney V7 Consistency).md | 6 +- ...저니 및 스테이블 디퓨전의 부분 편집 기법.md | 6 +- .../미드저니(Midjourney) 에디터 기능.md | 6 +- 10_Wiki/Topics_Blog/미호요(miHoYo).md | 6 +- .../버전 및 모델 (Versions and Models).md | 6 +- .../벡터 데이터베이스 (Vector Database).md | 4 +- .../Topics_Blog/보존 경로(Retaining Path).md | 6 +- ... 활용한 시각적 아티팩트(Artifact) 디버깅 및 제어.md | 6 +- 10_Wiki/Topics_Blog/비동기 데이터 관리.md | 14 +- .../사단 시스템 (Division System).md | 4 +- 10_Wiki/Topics_Blog/사단 편제표 (TO&E).md | 4 +- 10_Wiki/Topics_Blog/사단(Division) 시스템.md | 4 +- .../사용자 확보 (User Acquisition).md | 6 +- .../Topics_Blog/사후 편집 (Post-editing).md | 6 +- ...Commercial Marketing Campaign and Product Mockup Creation).md | 6 +- ...업용 브랜드 이미지 및 디자인 시스템 구축.md | 6 +- .../상업용 제품 사진 및 브랜드 로고 디자인.md | 4 +- .../상호작용적 프롬프트 엔지니어링.md | 6 +- .../샘플링 스텝 (Sampling Steps).md | 6 +- ...로세스 (Iterative Workflow of Generative AI Imaging).md | 6 +- ...형 AI 워크플로우 (Generative AI Workflow).md | 6 +- ...셜 미디어 그래픽 및 마케팅 캠페인 제작.md | 6 +- .../Topics_Blog/소음 역학 (Noise Dynamics).md | 4 +- ...릭터 참조 (Style and Character References).md | 6 +- .../스타일 및 캐릭터 참조(References).md | 6 +- ... 캐릭터 참조(Style and Character Reference).md | 6 +- .../스타일 참조(Style Reference, --sref).md | 6 +- 10_Wiki/Topics_Blog/스타일 코드.md | 6 +- ...테이블 디퓨전 CFG Scale 및 가중치 제어.md | 6 +- ...스테이블 디퓨전의 가중치 및 제어 시스템.md | 6 +- ...샷 워크플로우 (Series and Multi-shot Workflow).md | 6 +- ...지 최적화 (Stable Diffusion Image Optimization).md | 6 +- .../Topics_Blog/에이전틱 AI (Agentic AI).md | 6 +- ...미지 생성 및 하드웨어 수준의 정밀 통제 워크플로우.md | 6 +- ...스 기반 맞춤형 이미지 생성 워크플로우 구축.md | 6 +- .../오픈소스 이미지 모델 미세 조정 및 배포.md | 6 +- .../옴니 참조(Omni Reference, --oref).md | 6 +- ...신과 시야 매커니즘 (Stealth and Optics).md | 4 +- .../인-이미지 텍스트(In-Image Text).md | 6 +- 10_Wiki/Topics_Blog/인페인팅 (Inpainting).md | 6 +- .../인페인팅 (Inpainting-Vary Region).md | 6 +- ...및 드래프트 모드(Inpainting and Draft Mode).md | 6 +- ... 및 아웃페인팅 (Inpainting and Outpainting).md | 6 +- ...연어 프롬프트(Natural Language Prompt).md | 6 +- ... 관통 모델링(Armor Penetration Modeling).md | 4 +- ... 및 사거리 데이터 (Armor and Range Stats).md | 4 +- .../Topics_Blog/제병협동 (Combined Arms).md | 4 +- .../제병협동 전술 (Combined Arms).md | 4 +- ... 사양 지시(Lighting and Camera Specification).md | 6 +- .../초상화 및 애니메이션 스타일 제어.md | 6 +- .../캐릭터 참조 (Character Reference).md | 6 +- 10_Wiki/Topics_Blog/컨트롤넷 (ControlNet).md | 6 +- 10_Wiki/Topics_Blog/컨트롤넷(ControlNet).md | 6 +- ... 알고리즘 (Ballistics and Accuracy Algorithms).md | 4 +- .../텍스트 렌더링(Text Rendering).md | 6 +- .../파라미터 튜닝 (Parameter Tuning).md | 4 +- .../프롬프트 가중치 (Prompt Weighting).md | 6 +- .../프롬프트 가중치(Prompt Weighting).md | 6 +- .../프롬프트 구문 (Prompt Syntax).md | 6 +- .../프롬프트 구조 (Prompt Structure).md | 6 +- 10_Wiki/Topics_Blog/프롬프트 구조 및 문법.md | 6 +- 10_Wiki/Topics_Blog/프롬프트 엔지니어링.md | 6 +- .../Topics_Blog/프롬프트 엔지니어링의 진화.md | 6 +- .../프롬프트 정밀도 (Prompt Precision).md | 6 +- ... 파라미터 제어 (Prompt Parameter Control).md | 6 +- .../프롬프트 확장(Prompt Expansion).md | 6 +- .../해부학적 오류 디버깅 워크플로우.md | 6 +- .../확산 모델 (Diffusion Model).md | 6 +- .../확산 모델 (Diffusion Models).md | 6 +- .../Topics_GD/10v10 대규모 멀티플레이어.md | 4 +- ... 3월 연구 드롭(March 2026 Research Drop).md | 8 +- ... 연구 업데이트(March 2026 Research Drop).md | 6 +- ...어 생성 패러다임 전환 및 연속적 창작 워크플로우.md | 6 +- .../Topics_GD/20k skinned instances demo.md | 14 +- 10_Wiki/Topics_GD/4X 전략.md | 6 +- .../A-B-Testing-and-Data-Driven-UX.md | 8 +- .../A2A (Agent-to-Agent Protocol).md | 14 +- 10_Wiki/Topics_GD/A2A.md | 10 +- 10_Wiki/Topics_GD/ABA.md | 8 +- 10_Wiki/Topics_GD/ACI.md | 10 +- .../ACP (Agent Communication Protocol).md | 10 +- 10_Wiki/Topics_GD/ADA-Website-Compliance.md | 2 +- 10_Wiki/Topics_GD/AGI.md | 8 +- 10_Wiki/Topics_GD/AI & Data Sovereignty.md | 6 +- 10_Wiki/Topics_GD/AI Accountability.md | 8 +- 10_Wiki/Topics_GD/AI Agents.md | 8 +- 10_Wiki/Topics_GD/AI Connect LLM Tool.md | 2 +- 10_Wiki/Topics_GD/AI Governance.md | 12 +- 10_Wiki/Topics_GD/AI Humanism.md | 8 +- 10_Wiki/Topics_GD/AI Literacy.md | 10 +- 10_Wiki/Topics_GD/AI Safety (AI 안전).md | 12 +- 10_Wiki/Topics_GD/AI Safety.md | 10 +- 10_Wiki/Topics_GD/AI and Narrative.md | 10 +- 10_Wiki/Topics_GD/AI for Social Good.md | 8 +- .../AI 거버넌스 정책(AI Usage Policy).md | 8 +- .../AI 생성 코드 검증(AI Code Assurance).md | 12 +- 10_Wiki/Topics_GD/AI 에이전트 (AI Agent).md | 14 +- ... 워크플로우 (AI Image Generation Workflow).md | 6 +- ... 디버깅 (Image Quality Optimization & Debugging).md | 6 +- ...드 리뷰 및 보안 취약점 점검(DevSecOps).md | 16 +- 10_Wiki/Topics_GD/AI 코드 리뷰.md | 14 +- 10_Wiki/Topics_GD/AI-Alignment.md | 4 +- .../AI-Answer-Engine-Optimization.md | 10 +- .../Topics_GD/AI-Driven Narrative Systems.md | 2 +- 10_Wiki/Topics_GD/AI-Overviews-and-SGE.md | 10 +- .../AI-Personalization-and-Adaptive-UX.md | 6 +- 10_Wiki/Topics_GD/AI-Search-Optimization.md | 6 +- ...열 맡기기_ - 정적 분석 툴 (ESLint Prettier)).md | 18 +- ... 모델링 및 상태 머신(State Machine) 설계.md | 10 +- .../Topics_GD/API-Design for AI Services.md | 6 +- 10_Wiki/Topics_GD/API-Key-Management.md | 8 +- .../API-backed Image Generation Workflow.md | 6 +- .../Topics_GD/ARG-Alternate-Reality-Games.md | 6 +- 10_Wiki/Topics_GD/A_B-Testing-Platforms.md | 10 +- 10_Wiki/Topics_GD/Abundance.md | 10 +- 10_Wiki/Topics_GD/Academic-Integrity.md | 8 +- .../Accessibility-Compliance-Audit.md | 10 +- 10_Wiki/Topics_GD/Active Learning.md | 10 +- 10_Wiki/Topics_GD/Active-Reasoning.md | 10 +- 10_Wiki/Topics_GD/Activism.md | 12 +- 10_Wiki/Topics_GD/Actor-Critic-Models.md | 10 +- 10_Wiki/Topics_GD/Ad-hoc-Hypotheses.md | 12 +- 10_Wiki/Topics_GD/Ad-hoc-Optimization.md | 12 +- 10_Wiki/Topics_GD/Adaptability.md | 12 +- .../Adaptive Compute (적응형 계산량 조절).md | 12 +- .../Topics_GD/Adaptive Context Compaction.md | 8 +- 10_Wiki/Topics_GD/Adaptive-Curation.md | 6 +- .../Topics_GD/Advanced-Interface-Design.md | 8 +- .../Topics_GD/Adversarial Code Stylometry.md | 10 +- 10_Wiki/Topics_GD/Aesthetic-Value.md | 12 +- 10_Wiki/Topics_GD/Affective Computing.md | 2 +- 10_Wiki/Topics_GD/Affordance.md | 10 +- 10_Wiki/Topics_GD/Agent Architecture.md | 12 +- 10_Wiki/Topics_GD/Agent Harness.md | 20 +- .../Topics_GD/Agent Identity Management.md | 8 +- 10_Wiki/Topics_GD/Agent Memory System.md | 8 +- 10_Wiki/Topics_GD/Agent Personality.md | 12 +- 10_Wiki/Topics_GD/Agent_Harness.md | 10 +- 10_Wiki/Topics_GD/Agent_State_Store.md | 10 +- 10_Wiki/Topics_GD/Agentic AI Security.md | 14 +- 10_Wiki/Topics_GD/Agentic Coding.md | 12 +- 10_Wiki/Topics_GD/Agentic Creative Era.md | 6 +- 10_Wiki/Topics_GD/Agentic Governance.md | 8 +- 10_Wiki/Topics_GD/Agentic Orchestration.md | 12 +- .../Topics_GD/Agentic_Software_Engineering.md | 10 +- 10_Wiki/Topics_GD/Agile-Philosophy.md | 12 +- .../Topics_GD/Agile_and_Team_Collaboration.md | 10 +- ...ine (Full LootPlayer-Driven Production).md | 6 +- 10_Wiki/Topics_GD/Alcoholism.md | 10 +- .../Topics_GD/Algorithm-Complexity-Big-O.md | 6 +- 10_Wiki/Topics_GD/Algorithmic Fairness.md | 10 +- 10_Wiki/Topics_GD/Algorithmic Transparency.md | 6 +- 10_Wiki/Topics_GD/Algorithmic-Biology.md | 10 +- 10_Wiki/Topics_GD/Algorithmic-Game-Theory.md | 6 +- 10_Wiki/Topics_GD/Alignment.md | 8 +- 10_Wiki/Topics_GD/Alliance (동맹).md | 6 +- 10_Wiki/Topics_GD/AlphaZero Strategy.md | 2 +- 10_Wiki/Topics_GD/Alternative Realities.md | 12 +- 10_Wiki/Topics_GD/Altruism.md | 12 +- 10_Wiki/Topics_GD/Ambient-Declarations.md | 10 +- 10_Wiki/Topics_GD/Ambition.md | 14 +- .../Topics_GD/Amdahls Law (암달의 법칙).md | 6 +- 10_Wiki/Topics_GD/Analogical-Reasoning.md | 12 +- 10_Wiki/Topics_GD/Analogy.md | 8 +- 10_Wiki/Topics_GD/Analysis.md | 8 +- 10_Wiki/Topics_GD/Anarchism.md | 10 +- 10_Wiki/Topics_GD/Anarcho-Capitalism.md | 8 +- 10_Wiki/Topics_GD/Anarcho-Primitivism.md | 6 +- 10_Wiki/Topics_GD/Anisomorphism.md | 12 +- 10_Wiki/Topics_GD/Anomaly-Detection.md | 8 +- 10_Wiki/Topics_GD/Anthropic-Principle.md | 4 +- 10_Wiki/Topics_GD/Anthropomorphism.md | 10 +- 10_Wiki/Topics_GD/Anticipation.md | 12 +- 10_Wiki/Topics_GD/Antifragility.md | 10 +- 10_Wiki/Topics_GD/Antinomianism.md | 10 +- 10_Wiki/Topics_GD/Anxiety.md | 8 +- ...년 연구 업데이트(March 2026 Research Drop).md | 6 +- .../Topics_GD/Arguing-by-Counterexample.md | 10 +- 10_Wiki/Topics_GD/Arkane Studios.md | 6 +- .../Topics_GD/Arrangement-and-Composition.md | 12 +- 10_Wiki/Topics_GD/Articulateness.md | 8 +- .../Topics_GD/Artifacts & Infrastructure.md | 8 +- .../Artificial General Intelligence (AGI).md | 12 +- .../Topics_GD/Artificial Intelligence (AI).md | 16 +- .../Artificial-Intelligence-in-Games.md | 12 +- 10_Wiki/Topics_GD/Artificial-Intelligence.md | 10 +- 10_Wiki/Topics_GD/Artificial-Life.md | 6 +- 10_Wiki/Topics_GD/Arts.md | 8 +- 10_Wiki/Topics_GD/Assertiveness.md | 10 +- 10_Wiki/Topics_GD/Assessment.md | 14 +- 10_Wiki/Topics_GD/Asset-Specific-Knowledge.md | 8 +- 10_Wiki/Topics_GD/Assumptions-vs-Facts.md | 12 +- 10_Wiki/Topics_GD/Atheism.md | 12 +- 10_Wiki/Topics_GD/Atlantic.md | 8 +- 10_Wiki/Topics_GD/Atmospheric-Intelligence.md | 10 +- .../Atomic-Design-System-Architecture.md | 10 +- .../Atomic-Styling-and-Design-Systems.md | 12 +- 10_Wiki/Topics_GD/Atomism.md | 12 +- 10_Wiki/Topics_GD/Attention Mechanisms.md | 10 +- .../Topics_GD/Attention is All You Need.md | 6 +- 10_Wiki/Topics_GD/Authenticity.md | 8 +- ...sm Spectrum Disorder (ASD) Intervention.md | 4 +- 10_Wiki/Topics_GD/Auto-Encoding.md | 10 +- .../Auto-GPT and Autonomous Agents.md | 8 +- 10_Wiki/Topics_GD/Autobiography.md | 10 +- 10_Wiki/Topics_GD/Autoethnography.md | 12 +- .../Topics_GD/Automated-Decision-Making.md | 12 +- 10_Wiki/Topics_GD/Automated-Game-Testing.md | 8 +- 10_Wiki/Topics_GD/Automated-Map-Generation.md | 12 +- 10_Wiki/Topics_GD/Automated-Reasoning.md | 10 +- .../Topics_GD/Automated-Refactoring-Tools.md | 12 +- .../Topics_GD/Automated-Security-Audits.md | 10 +- .../Topics_GD/Automated-Theorem-Proving.md | 10 +- 10_Wiki/Topics_GD/Automated_Mapping.md | 8 +- 10_Wiki/Topics_GD/Automation-Paradox.md | 8 +- 10_Wiki/Topics_GD/Autonomous Logging.md | 8 +- 10_Wiki/Topics_GD/Autonomous Vehicles.md | 14 +- 10_Wiki/Topics_GD/Autonomous-Agents.md | 12 +- .../Autonomous-Polling-Wait-Automation.md | 16 +- .../Autonomous-Vehicle-Path-Planning.md | 12 +- .../Topics_GD/Availability-and-Persistence.md | 12 +- 10_Wiki/Topics_GD/Awards.md | 8 +- 10_Wiki/Topics_GD/Axify.md | 6 +- 10_Wiki/Topics_GD/Axiology.md | 12 +- 10_Wiki/Topics_GD/Axiomatic-Systems.md | 12 +- 10_Wiki/Topics_GD/Axioms.md | 10 +- 10_Wiki/Topics_GD/Azure DevOps.md | 10 +- 10_Wiki/Topics_GD/B-Tree.md | 10 +- 10_Wiki/Topics_GD/BERT.md | 8 +- 10_Wiki/Topics_GD/BFS vs DFS.md | 10 +- 10_Wiki/Topics_GD/Backend.md | 14 +- .../Topics_GD/Backpropagation Through Time.md | 6 +- 10_Wiki/Topics_GD/Backpropagation.md | 8 +- 10_Wiki/Topics_GD/Backups.md | 8 +- 10_Wiki/Topics_GD/Backward-Reasoning.md | 10 +- 10_Wiki/Topics_GD/Bag of Words (BoW).md | 8 +- 10_Wiki/Topics_GD/Balancing/.gitkeep | 0 .../Algorithmic Game Theory.md | 6 +- .../Balancing/Game Design & Math/Index.md | 2 +- 10_Wiki/Topics_GD/Balancing/Index.md | 22 +- ...미지 유형(Unit Counters & Damage Profiles).md | 6 +- .../Balancing/유닛 상성(Unit Counters).md | 6 +- .../Balancing/유닛 상성(Unit Matchups).md | 6 +- 10_Wiki/Topics_GD/Baseline Project.md | 8 +- 10_Wiki/Topics_GD/Batch-Inference.md | 8 +- 10_Wiki/Topics_GD/Bayes-Theorem.md | 8 +- 10_Wiki/Topics_GD/Bayesian Inference.md | 6 +- 10_Wiki/Topics_GD/Bayesian Statistics.md | 12 +- .../Topics_GD/Bayesian-Brain-Hypothesis.md | 4 +- 10_Wiki/Topics_GD/Bayesian-Updating.md | 12 +- 10_Wiki/Topics_GD/Be-Detailed.md | 10 +- 10_Wiki/Topics_GD/Beckett.md | 10 +- 10_Wiki/Topics_GD/Behavior.md | 12 +- 10_Wiki/Topics_GD/Behavioral Finance.md | 8 +- 10_Wiki/Topics_GD/Behavioral-Economics.md | 10 +- 10_Wiki/Topics_GD/Behavioral-Incentives.md | 12 +- 10_Wiki/Topics_GD/Belief-Revision.md | 12 +- 10_Wiki/Topics_GD/Belief-System.md | 16 +- 10_Wiki/Topics_GD/Beliefs.md | 12 +- 10_Wiki/Topics_GD/Bellman Equation.md | 8 +- 10_Wiki/Topics_GD/Bellman-Equation.md | 12 +- 10_Wiki/Topics_GD/Benchmarks.md | 8 +- 10_Wiki/Topics_GD/Bert-Language-Model.md | 12 +- 10_Wiki/Topics_GD/Best SAST Tools in 2026.md | 10 +- 10_Wiki/Topics_GD/Best-of-N Sampling ( ø).md | 10 +- .../Best-of-N Sampling (최적 샘플링).md | 6 +- 10_Wiki/Topics_GD/Best-of-N Sampling.md | 8 +- 10_Wiki/Topics_GD/Best-of-N-Sampling.md | 14 +- 10_Wiki/Topics_GD/Bias vs Variance.md | 10 +- .../Topics_GD/Bias-Correction-Algorithm.md | 12 +- 10_Wiki/Topics_GD/Bias-Variance-Tradeoff.md | 10 +- 10_Wiki/Topics_GD/Bible.md | 10 +- 10_Wiki/Topics_GD/Bibliometrics.md | 8 +- 10_Wiki/Topics_GD/Big-Data.md | 6 +- 10_Wiki/Topics_GD/Big-Picture.md | 20 +- .../Topics_GD/Binary-Author-Identification.md | 16 +- 10_Wiki/Topics_GD/Binary-Search.md | 8 +- 10_Wiki/Topics_GD/BioShock (2007).md | 8 +- 10_Wiki/Topics_GD/BioShock-Critique.md | 10 +- 10_Wiki/Topics_GD/Bioenergetics.md | 8 +- .../Bioinformatics-Structure-Prediction.md | 8 +- .../Biological-Inspired-Algorithms.md | 12 +- 10_Wiki/Topics_GD/Biological-Intelligence.md | 14 +- 10_Wiki/Topics_GD/Biomechanics-of-Injury.md | 10 +- 10_Wiki/Topics_GD/Biometrics.md | 10 +- 10_Wiki/Topics_GD/Black-Box-Optimization.md | 6 +- 10_Wiki/Topics_GD/Black-Hole.md | 8 +- 10_Wiki/Topics_GD/Black-Swan.md | 12 +- 10_Wiki/Topics_GD/Blockchain.md | 10 +- 10_Wiki/Topics_GD/Blocking.md | 10 +- 10_Wiki/Topics_GD/Blog-Post.md | 8 +- 10_Wiki/Topics_GD/Bloom-Filters in Search.md | 6 +- 10_Wiki/Topics_GD/Bloom-Filters.md | 12 +- 10_Wiki/Topics_GD/Boltzmann-Machines.md | 4 +- .../Boosting-Algorithms-XGBoost-LightGBM.md | 10 +- 10_Wiki/Topics_GD/Bottlenecks.md | 14 +- 10_Wiki/Topics_GD/Bottom-Up-Approach.md | 14 +- 10_Wiki/Topics_GD/Boundaries.md | 12 +- 10_Wiki/Topics_GD/Boundary-Setting.md | 12 +- 10_Wiki/Topics_GD/Bounded Contexts.md | 10 +- 10_Wiki/Topics_GD/Bounded Rationality.md | 12 +- ...nded-Contexts-and-Interface-Segregation.md | 12 +- 10_Wiki/Topics_GD/Bounded-Rationality.md | 12 +- 10_Wiki/Topics_GD/Bounding-Box-Regression.md | 8 +- 10_Wiki/Topics_GD/Bourgeoisie.md | 10 +- .../Brain-Computer Interface (BCI).md | 4 +- .../Brain-Computer-Interface (BCI).md | 8 +- ...rain-Derived Neurotrophic Factor (BDNF).md | 8 +- .../Brand Consistency Maintenance.md | 6 +- .../Branded-Types-for-Nominal-Typing.md | 10 +- 10_Wiki/Topics_GD/Branded-Types.md | 12 +- 10_Wiki/Topics_GD/Branding.md | 12 +- 10_Wiki/Topics_GD/Browser.md | 12 +- 10_Wiki/Topics_GD/Brute-force.md | 10 +- 10_Wiki/Topics_GD/Bubble-Sort.md | 10 +- 10_Wiki/Topics_GD/Budget.md | 14 +- 10_Wiki/Topics_GD/Bureaucracy.md | 10 +- ...rnout Prevention in Professional Gaming.md | 8 +- 10_Wiki/Topics_GD/Burnout.md | 10 +- .../Topics_GD/Business Intelligence (BI).md | 10 +- .../C-component (Context Manager).md | 8 +- 10_Wiki/Topics_GD/CAP-Theorem.md | 4 +- .../Topics_GD/CI-CD-Pipeline-Foundations.md | 8 +- .../CI_CD 및 Pull Request 자동화 리뷰.md | 16 +- .../CI_CD 파이프라인 및 IDE 통합 보안.md | 16 +- 10_Wiki/Topics_GD/CI_CD.md | 14 +- 10_Wiki/Topics_GD/CLIP.md | 6 +- 10_Wiki/Topics_GD/CPTED.md | 12 +- 10_Wiki/Topics_GD/CV_Synthesis.md | 14 +- 10_Wiki/Topics_GD/Call Stack.md | 14 +- .../Case-Study-Allbirds-PWA-Redesign.md | 8 +- .../Case-Study-Kiwi-com-Frontend-Migration.md | 10 +- ...Case-Study-Skybound-Asset-Cache-Busting.md | 4 +- ...ybound-Red-Striker-Jitter-Stabilization.md | 6 +- 10_Wiki/Topics_GD/Catastrophic-Forgetting.md | 8 +- 10_Wiki/Topics_GD/Causal-Inference.md | 4 +- .../Topics_GD/Central-Pattern-Generators.md | 10 +- 10_Wiki/Topics_GD/CesiumJS.md | 16 +- .../Topics_GD/Chain-of-Thought (CoT 罽).md | 10 +- .../Chain-of-Thought (CoT 사고 사슬).md | 12 +- 10_Wiki/Topics_GD/Chaos-Theory in Systems.md | 6 +- 10_Wiki/Topics_GD/Character Consistency.md | 6 +- 10_Wiki/Topics_GD/Character Reference.md | 6 +- ...기반 텍스트 투 이미지(Text-to-Image) 생성.md | 6 +- .../Chrome DevTools Memory Profiling.md | 8 +- ...ols 메모리 프로파일링 및 힙 스냅샷 분석.md | 18 +- .../Chrome DevTools 메모리 프로파일링.md | 14 +- 10_Wiki/Topics_GD/Chrome DevTools.md | 16 +- .../Topics_GD/Chrome-Rendering-Performance.md | 14 +- .../Chronic-Pain-Management-Protocols.md | 10 +- .../Circuit Discovery (회로 발견).md | 10 +- 10_Wiki/Topics_GD/Circuit Discovery.md | 6 +- .../Topics_GD/Circular-Economy-Transitions.md | 14 +- 10_Wiki/Topics_GD/Circular-Economy.md | 8 +- .../Clean-Architecture-Implementation.md | 12 +- .../Clean-Architecture-TypeScript.md | 10 +- 10_Wiki/Topics_GD/Clean-Code-Principles.md | 6 +- .../Climate Change Mitigation Frameworks.md | 12 +- .../Clinical-Kinesiology-Assessment.md | 12 +- 10_Wiki/Topics_GD/Code Review.md | 12 +- ...g-and-Frontend-Performance-Optimization.md | 6 +- 10_Wiki/Topics_GD/Cognitive Biases.md | 14 +- 10_Wiki/Topics_GD/Cognitive Computing.md | 6 +- .../Cognitive Neuroscience of Flow.md | 10 +- 10_Wiki/Topics_GD/Cognitive Psychology.md | 10 +- 10_Wiki/Topics_GD/Cognitive Reserve Theory.md | 4 +- ... Training Software (eg Aim Lab_KovaaKs).md | 6 +- 10_Wiki/Topics_GD/Cognitive-Architecture.md | 4 +- .../Topics_GD/Cognitive-Evaluation-Theory.md | 8 +- 10_Wiki/Topics_GD/Cognitive-Therapy-in-CBT.md | 12 +- 10_Wiki/Topics_GD/Collaborative-Filtering.md | 4 +- 10_Wiki/Topics_GD/Collective-Intelligence.md | 10 +- .../Topics_GD/Combinatorial Game Theory.md | 8 +- .../Topics_GD/Combinatorial-Optimization.md | 4 +- .../Combined Arms (제병협동) 전술.md | 4 +- 10_Wiki/Topics_GD/Command Center.md | 6 +- 10_Wiki/Topics_GD/Command and Control (C2).md | 6 +- .../Topics_GD/Commercial AI Art Production.md | 6 +- 10_Wiki/Topics_GD/CompCert-C-Compiler.md | 10 +- 10_Wiki/Topics_GD/Complexity Theory.md | 12 +- 10_Wiki/Topics_GD/Complexity-Theory.md | 6 +- 10_Wiki/Topics_GD/Component-Composition.md | 8 +- 10_Wiki/Topics_GD/Computational Creativity.md | 8 +- ... Neuroscience of Reinforcement Learning.md | 6 +- 10_Wiki/Topics_GD/Computational-Creativity.md | 12 +- .../Topics_GD/Computational-Linguistics.md | 4 +- .../Computational-Neuroscience-RL.md | 14 +- 10_Wiki/Topics_GD/Computer Vision.md | 10 +- 10_Wiki/Topics_GD/Computer-Aided-Design.md | 16 +- 10_Wiki/Topics_GD/Computer-Vision.md | 8 +- 10_Wiki/Topics_GD/Computer_Vision.md | 10 +- .../Concept Drift (개념 드리프트).md | 10 +- 10_Wiki/Topics_GD/Concept Mapping.md | 10 +- 10_Wiki/Topics_GD/Concept-Drift.md | 6 +- 10_Wiki/Topics_GD/Concreteness-Principle.md | 4 +- 10_Wiki/Topics_GD/Concurrent Programming.md | 8 +- .../Conditioning and Learning ( ).md | 8 +- 10_Wiki/Topics_GD/Connect-AI-Documentation.md | 16 +- .../Topics_GD/ConnectAI_Dev_Log_20260429.md | 20 +- .../Topics_GD/Constitutional AI (헌법 AI).md | 10 +- 10_Wiki/Topics_GD/Constitutional-AI.md | 4 +- .../Constraint Satisfaction Problems (CSP).md | 14 +- .../Constraint-Satisfaction Problems.md | 4 +- .../Constraint-Satisfaction-Problems.md | 12 +- 10_Wiki/Topics_GD/Context Engineering.md | 10 +- 10_Wiki/Topics_GD/Context Rot.md | 8 +- 10_Wiki/Topics_GD/Context-Aware-Computing.md | 4 +- 10_Wiki/Topics_GD/Context_Engineering.md | 10 +- 10_Wiki/Topics_GD/Continuous-Discovery.md | 12 +- 10_Wiki/Topics_GD/Contrastive-Learning.md | 6 +- .../Topics_GD/Control Systems Engineering.md | 12 +- .../Topics_GD/Control-Systems-Engineering.md | 10 +- 10_Wiki/Topics_GD/Control-Theory.md | 6 +- 10_Wiki/Topics_GD/ControlNet.md | 6 +- .../Convolutional-Neural-Networks.md | 6 +- 10_Wiki/Topics_GD/Core-Web-Vitals-Metrics.md | 12 +- 10_Wiki/Topics_GD/Core-Web-Vitals.md | 10 +- 10_Wiki/Topics_GD/Core_Systems/.gitkeep | 0 .../2014 Combat Controls Update.md | 6 +- .../Core_Systems/4X 시스템 (4X System).md | 6 +- .../AI & Games/AlphaZero Strategy.md | 6 +- .../Core_Systems/AI & Games/Index.md | 2 +- .../Topics_GD/Core_Systems/AI Exploitation.md | 6 +- .../AI 추적 논리(AI Pursuit Logic).md | 6 +- .../Area-of-Effect (AoE) Damage.md | 6 +- .../Topics_GD/Core_Systems/Baiting Tactics.md | 6 +- 10_Wiki/Topics_GD/Core_Systems/Baiting.md | 6 +- .../Combat Controls Update (Feb 2014).md | 6 +- .../Topics_GD/Core_Systems/Combat Controls.md | 6 +- .../Cyber-Physical Systems (CPS).md | 6 +- .../Algorithmic Game Theory.md | 6 +- .../Core_Systems/Game Design & Math/Index.md | 2 +- .../ARG-Alternate-Reality-Games.md | 6 +- .../Game Design/Agency and Player Autonomy.md | 6 +- ...ine (Full LootPlayer-Driven Production).md | 6 +- .../Game Design/Arkane Studios.md | 6 +- .../Cyber-Physical Systems (CPS).md | 6 +- .../Game Design/Elite-Athletic-Development.md | 6 +- .../Core_Systems/Game Design/Index.md | 24 +- .../Post-Modernist Literature in Gaming.md | 6 +- .../Game Design/Quantum-Game-Theory.md | 6 +- .../Roguelike Procedural Generation.md | 6 +- .../Game Design/Street Duel Fighter.md | 10 +- .../Game Design/Systems Biology.md | 6 +- .../인문학적 게임 비평 및 서사학.md | 6 +- 10_Wiki/Topics_GD/Core_Systems/Index.md | 94 +- .../Aerospace Flight Simulation.md | 6 +- .../Physics & Simulation/Index.md | 2 +- .../Agent-Based Modeling (ABM).md | 6 +- .../Core_Systems/Simulation & Math/Index.md | 2 +- .../Topics_GD/Core_Systems/Splash Damage.md | 6 +- .../Digital Twins.md | 10 +- .../System Architecture & Simulation/Index.md | 2 +- .../Event Storming.md | 10 +- .../System Design & Modeling/Index.md | 2 +- .../Topics_GD/Core_Systems/Systems Biology.md | 6 +- .../Topics_GD/Core_Systems/Unit Stances.md | 6 +- .../War Commander AI and UI Enhancements.md | 6 +- .../War Commander → 전투 시스템.md | 6 +- ...진화(Tactical Evolution of the Combat Ecosystem).md | 6 +- ... 전투 시스템 진화 (2014년 2월 업데이트).md | 6 +- .../War Commander 전투 전술 및 방어 메타.md | 8 +- .../기지 방어 설계(Defensive Architecture).md | 6 +- .../Core_Systems/미끼 전술(Baiting).md | 6 +- .../방어 구조(Defensive Architecture).md | 6 +- ...하학 및 구조 설계(Defensive Architecture).md | 6 +- .../방어 아키텍처(Defensive Architecture).md | 6 +- ... 전투(Sector Warfare and Elite Event Operations).md | 6 +- ...놀로지 및 유닛(Arc 2 Technology and Units).md | 6 +- .../Core_Systems/유닛 미끼 전술(Baiting).md | 6 +- .../유인 전술(Baiting Tactics).md | 6 +- .../Core_Systems/유인 전술(Baiting).md | 6 +- .../전력 시스템(Power Systems).md | 6 +- .../전투 전술(Battle Strategies).md | 6 +- .../전투 제어(Combat Controls).md | 6 +- .../전투 컨트롤(Combat Controls).md | 6 +- .../전투 통제(Combat Controls).md | 6 +- .../포탑 시스템(Turret Systems).md | 6 +- .../Core_Systems/피해 유형(Damage Types).md | 6 +- 10_Wiki/Topics_GD/Corgea.md | 14 +- 10_Wiki/Topics_GD/Corporate-LMS-Training.md | 18 +- .../Topics_GD/Cost-Benefit Analysis in AI.md | 6 +- 10_Wiki/Topics_GD/Creativity Research.md | 14 +- .../Topics_GD/Credit Assignment Problem.md | 8 +- 10_Wiki/Topics_GD/Cross-Entropy Loss.md | 4 +- .../Topics_GD/Cumulative-Layout-Shift-CLS.md | 8 +- 10_Wiki/Topics_GD/Curriculum-Learning.md | 4 +- .../Custom-ESLint-Rules-Development.md | 6 +- 10_Wiki/Topics_GD/Custom-ESLint-Rules.md | 16 +- 10_Wiki/Topics_GD/Custom-Hooks-Patterns.md | 10 +- 10_Wiki/Topics_GD/Customer-Journey-Mapping.md | 16 +- 10_Wiki/Topics_GD/Cybernetics Foundations.md | 8 +- 10_Wiki/Topics_GD/Cybernetics.md | 12 +- .../Topics_GD/DAG-Dependency-Management.md | 14 +- .../Topics_GD/DALL-E 3 Natural Language.md | 6 +- .../Topics_GD/DALL-E 3 Negation Handling.md | 6 +- .../DALL-E 3 Synthetic Captioning.md | 6 +- .../DALL-E 3와 GPT-4의 상호작용적 생성.md | 6 +- .../DALL-E 3의 자연어 기반 최적화.md | 6 +- 10_Wiki/Topics_GD/DDD-Type-Safety.md | 18 +- 10_Wiki/Topics_GD/DDD-in-TypeScript.md | 14 +- 10_Wiki/Topics_GD/DORA-Metrics.md | 12 +- .../DPO (Direct Preference Optimization).md | 8 +- 10_Wiki/Topics_GD/DQN.md | 8 +- 10_Wiki/Topics_GD/Data Cleaning Algorithms.md | 10 +- .../Data Distillation (데이터 증류).md | 12 +- .../Topics_GD/Data-Augmentation Strategies.md | 10 +- 10_Wiki/Topics_GD/Data-Ethics and Privacy.md | 6 +- 10_Wiki/Topics_GD/Data-Flywheel-Effect.md | 6 +- .../Topics_GD/Data-Pipeline Orchestration.md | 6 +- 10_Wiki/Topics_GD/Data-Science-in-UX.md | 12 +- .../Topics_GD/Data-Transfer-Object-Design.md | 8 +- 10_Wiki/Topics_GD/Dead-Space-Series.md | 6 +- .../Deceptive Alignment (기만적 정렬).md | 10 +- 10_Wiki/Topics_GD/Decision Theory.md | 16 +- .../Decision-Trees and Random Forests.md | 4 +- 10_Wiki/Topics_GD/Declaration-Files.md | 14 +- 10_Wiki/Topics_GD/Deep Q-Networks (DQN).md | 8 +- 10_Wiki/Topics_GD/Deep-Convolutional-GANs.md | 14 +- 10_Wiki/Topics_GD/Deep-Grammar.md | 10 +- 10_Wiki/Topics_GD/Deep-Learning.md | 6 +- 10_Wiki/Topics_GD/Deep-Q-Networks-DQN.md | 8 +- 10_Wiki/Topics_GD/DeepCode AI.md | 10 +- 10_Wiki/Topics_GD/Deepfake-Detection.md | 12 +- 10_Wiki/Topics_GD/Deepfake-Technology.md | 4 +- .../Topics_GD/Default Mode Network (DMN).md | 8 +- 10_Wiki/Topics_GD/Defensive Stances.md | 6 +- 10_Wiki/Topics_GD/DefinitelyTyped.md | 12 +- 10_Wiki/Topics_GD/Definitions_of_Game.md | 8 +- 10_Wiki/Topics_GD/Degrees-of-Freedom.md | 12 +- 10_Wiki/Topics_GD/Deliberate-Practice.md | 10 +- .../Denavit-Hartenberg-Parameters.md | 10 +- .../Dense vs Sparse Neural Networks.md | 8 +- .../Topics_GD/Dependency-Graph-Analysis.md | 10 +- 10_Wiki/Topics_GD/Dependency-Injection.md | 8 +- .../Dependency-Inversion-Principle.md | 8 +- 10_Wiki/Topics_GD/Deployment-Strategy.md | 14 +- 10_Wiki/Topics_GD/Design-System.md | 16 +- 10_Wiki/Topics_GD/Determinism-in-Computing.md | 6 +- .../Topics_GD/DevOps-and-UX-Convergence.md | 10 +- 10_Wiki/Topics_GD/DevOps-for-AI-MLOps.md | 4 +- 10_Wiki/Topics_GD/DevSecOps.md | 12 +- .../Topics_GD/Differentiable Programming.md | 8 +- 10_Wiki/Topics_GD/Diffusion-Models.md | 8 +- .../Digital Intellectual Property Rights.md | 6 +- .../Topics_GD/Digital Thread Integration.md | 12 +- 10_Wiki/Topics_GD/Digital-Twin-Technology.md | 16 +- 10_Wiki/Topics_GD/Dijkstra's Algorithm.md | 8 +- 10_Wiki/Topics_GD/Dimensionality-Reduction.md | 6 +- .../Diminishing Returns (한계 수익 체감).md | 8 +- .../Directed-Acyclic-Graph-Build-Systems.md | 12 +- ...ted-Acyclic-Graph-Dependency-Management.md | 8 +- ...Discriminated-Unions-for-Error-Handling.md | 8 +- ...Discriminated-Unions-for-State-Modeling.md | 10 +- 10_Wiki/Topics_GD/Discriminated-Unions.md | 12 +- 10_Wiki/Topics_GD/Dissipative-Structures.md | 12 +- 10_Wiki/Topics_GD/Distillation.md | 10 +- .../Distributed Reinforcement Learning.md | 12 +- .../Distributed Systems & Reliability.md | 8 +- 10_Wiki/Topics_GD/Distributed-Computing.md | 4 +- .../Distributed-System-Type-Safety.md | 12 +- 10_Wiki/Topics_GD/Distributed-Systems.md | 8 +- 10_Wiki/Topics_GD/Documentation-Strategy.md | 14 +- 10_Wiki/Topics_GD/Domain Objects.md | 8 +- 10_Wiki/Topics_GD/Domain-Driven-Design-DDD.md | 6 +- .../Topics_GD/Domain-Specific-Languages.md | 10 +- 10_Wiki/Topics_GD/Dopamine-Modeling.md | 10 +- .../Topics_GD/Dopaminergic Reward System.md | 12 +- .../Topics_GD/Dopaminergic Reward Systems.md | 12 +- 10_Wiki/Topics_GD/Drama Management Systems.md | 12 +- 10_Wiki/Topics_GD/Dramaturgy-Theory.md | 12 +- 10_Wiki/Topics_GD/Dry-Principle.md | 10 +- .../Dynamic Difficulty Adjustment (DDA).md | 8 +- .../Dynamic Few-Shot (동적 퓨샷 선택 전략).md | 12 +- 10_Wiki/Topics_GD/Dynamic-Capabilities.md | 14 +- .../Dynamic-Creative-Optimization.md | 10 +- .../Topics_GD/Dynamic-Environment-Handling.md | 6 +- 10_Wiki/Topics_GD/Dynamic-Programming.md | 12 +- 10_Wiki/Topics_GD/E-Learning-Gamification.md | 12 +- .../E-commerce-Catalog-Management.md | 12 +- 10_Wiki/Topics_GD/E-commerce-Optimization.md | 12 +- .../Topics_GD/E-component (Execution Loop).md | 8 +- .../Topics_GD/ESLint-Plugin-Development.md | 14 +- 10_Wiki/Topics_GD/ESLint-Static-Analysis.md | 14 +- .../EU-Web-Accessibility-Directive.md | 12 +- .../Ecology and Ecosystem Modeling.md | 10 +- 10_Wiki/Topics_GD/Economic-Analysis.md | 14 +- .../Topics_GD/Economic-Complexity-Index.md | 10 +- 10_Wiki/Topics_GD/Economic-Mobility.md | 12 +- 10_Wiki/Topics_GD/Economics-of-Information.md | 12 +- .../Economy/4X 전략 게임 수익화 모델.md | 6 +- .../Economy/Game of War BM과 구조 조사.md | 6 +- .../Economy/Game of War BM과 구조 조사.md | 6 +- .../Game of War- Fire Age BM 및 구조 설계.md | 6 +- 10_Wiki/Topics_GD/Economy/Index.md | 42 +- .../Economy/Staircase Monetization Model.md | 6 +- .../Economy/VIP 시스템 (VIP System).md | 6 +- 10_Wiki/Topics_GD/Economy/VIP 시스템.md | 6 +- 10_Wiki/Topics_GD/Economy/VIP.md | 6 +- .../Economy/가상 화폐 (Virtual Currency).md | 6 +- .../계단식 수익화 (Staircase Monetization).md | 6 +- ...식 수익화 모델 (Staircase Monetization).md | 6 +- .../Topics_GD/Economy/고과금 유저 (Whales).md | 6 +- .../Economy/고래 유저 (Whale Players).md | 6 +- .../Economy/과금 모델 (Monetization).md | 6 +- .../Economy/맞춤형 팩 (Personalized Packs).md | 6 +- ...임의 진화 및 Game of War BM 구조 분석 프로젝트.md | 6 +- ... 수익화 모델 (Staircase Monetization Model).md | 6 +- .../약탈적 수익화 (Predatory Monetization).md | 6 +- .../이중 VIP 시스템 (Dual-layer VIP).md | 6 +- ... 계층 과금 모델 (Two-layer Monetization).md | 6 +- .../Economy/적자 경제 (Deficit economy).md | 6 +- 10_Wiki/Topics_GD/Edge Computing.md | 8 +- 10_Wiki/Topics_GD/Edge-AI-and-Computing.md | 8 +- .../Topics_GD/Edge-Artificial-Intelligence.md | 20 +- 10_Wiki/Topics_GD/Edge-Computing.md | 12 +- 10_Wiki/Topics_GD/Edtech-Industry-Trends.md | 10 +- 10_Wiki/Topics_GD/Effective-Altruism-in-AI.md | 14 +- 10_Wiki/Topics_GD/Efficiency.md | 16 +- .../Topics_GD/Eigenvalues-and-Eigenvectors.md | 4 +- 10_Wiki/Topics_GD/Eligibility-Traces.md | 4 +- .../Topics_GD/Elite-Athletic-Development.md | 6 +- .../Elite-Sport-Science-Protocols.md | 10 +- .../Elite-Strength-and-Conditioning.md | 8 +- 10_Wiki/Topics_GD/Elite-Theory.md | 12 +- 10_Wiki/Topics_GD/Embodied Cognition.md | 6 +- 10_Wiki/Topics_GD/Embodied-AI.md | 4 +- .../Topics_GD/Emergence-in-Complex-Systems.md | 12 +- 10_Wiki/Topics_GD/Emergence-in-Systems.md | 8 +- 10_Wiki/Topics_GD/Emergence.md | 10 +- .../Emotional-AI (Affective Computing).md | 6 +- ...lly Intelligent Tutoring Systems (EITS).md | 8 +- 10_Wiki/Topics_GD/Empathy-in-AI.md | 10 +- .../Encapsulation-and-Information-Hiding.md | 6 +- .../Encapsulation-of-Domain-Invariants.md | 10 +- .../Encapsulation-via-Access-Modifiers.md | 8 +- 10_Wiki/Topics_GD/End-to-End-Learning.md | 4 +- .../End-to-End-Testing-Strategies.md | 12 +- .../Endurance-Athletics-Cognition.md | 10 +- .../Engineering Scalable Frontend Systems.md | 18 +- 10_Wiki/Topics_GD/Engineering_Principles.md | 10 +- 10_Wiki/Topics_GD/Ensemble-Learning.md | 12 +- 10_Wiki/Topics_GD/Ensemble-Methods.md | 2 +- 10_Wiki/Topics_GD/Ensuring-Data-Privacy.md | 12 +- .../Topics_GD/Enterprise-Design-Systems.md | 12 +- .../Enterprise-Resource-Planning-Systems.md | 12 +- .../Enterprise-Scale-Monorepo-Management.md | 10 +- 10_Wiki/Topics_GD/Enterprise-Service-Bus.md | 14 +- .../Enterprise-Software-Architecture.md | 8 +- .../Enterprise-Software-Engineering.md | 10 +- .../Topics_GD/Entity-Relationship-Modeling.md | 16 +- .../Entropy in Information Theory.md | 8 +- 10_Wiki/Topics_GD/Environment-Design-in-RL.md | 6 +- .../Topics_GD/Enzyme-Inhibition-Kinetics.md | 8 +- 10_Wiki/Topics_GD/Epidemiological-Modeling.md | 10 +- 10_Wiki/Topics_GD/Epistemic-Uncertainty.md | 6 +- 10_Wiki/Topics_GD/Epistemology.md | 8 +- 10_Wiki/Topics_GD/Equality.md | 12 +- 10_Wiki/Topics_GD/Ergodic-Theory.md | 14 +- .../Ergonomics-in-Workspace-Design.md | 8 +- 10_Wiki/Topics_GD/Error-Boundary-Pattern.md | 8 +- .../Topics_GD/Error_Handling_and_Stability.md | 10 +- 10_Wiki/Topics_GD/Es-Lint-Configuration.md | 14 +- 10_Wiki/Topics_GD/Escalation-of-Commitment.md | 14 +- 10_Wiki/Topics_GD/Ethical-Decision-Making.md | 12 +- 10_Wiki/Topics_GD/Ethics & AI.md | 14 +- .../Topics_GD/Ethics of Autonomous Systems.md | 6 +- .../Ethics-in-Artificial-Intelligence.md | 8 +- 10_Wiki/Topics_GD/Ethnographic-Research.md | 16 +- 10_Wiki/Topics_GD/Etiology-of-Disease.md | 12 +- .../Topics_GD/Eudaimonia-and-Well-being.md | 12 +- .../Topics_GD/Eugen Systems 모딩 매뉴얼.md | 4 +- ...stems의 Iriszoom 엔진 및 전략 게임 개발.md | 4 +- .../Eugen Systems의 WARNO 시뮬레이션 개발.md | 4 +- ...냉전기 가상 시나리오 및 모딩 생태계 구축.md | 4 +- 10_Wiki/Topics_GD/Event Storming.md | 14 +- .../Topics_GD/Event-Driven-Architecture.md | 10 +- 10_Wiki/Topics_GD/Events.md | 6 +- 10_Wiki/Topics_GD/Evolutionary Biology.md | 6 +- 10_Wiki/Topics_GD/Evolutionary Computation.md | 12 +- .../Evolutionary-Algorithm-Design.md | 14 +- 10_Wiki/Topics_GD/Evolutionary-Algorithms.md | 14 +- 10_Wiki/Topics_GD/Evolutionary-Computation.md | 8 +- 10_Wiki/Topics_GD/Excess-Property-Checking.md | 6 +- 10_Wiki/Topics_GD/Excessive Agency.md | 8 +- .../Execution Environment (Sandbox).md | 8 +- 10_Wiki/Topics_GD/Executive Dysfunction.md | 10 +- .../Topics_GD/Executive-Function-Deficit.md | 8 +- 10_Wiki/Topics_GD/Exhaustiveness-Checking.md | 8 +- 10_Wiki/Topics_GD/Expectation-Maximization.md | 8 +- 10_Wiki/Topics_GD/Expected Utility Theory.md | 6 +- 10_Wiki/Topics_GD/Experience-Replay.md | 8 +- .../Topics_GD/Experience-Sampling-Method.md | 14 +- 10_Wiki/Topics_GD/Explainable-AI (XAI).md | 10 +- 10_Wiki/Topics_GD/Explainable-AI-XAI.md | 6 +- .../Topics_GD/Exploding-Gradient Problem.md | 10 +- .../Topics_GD/Exploration vs Exploitation.md | 12 +- .../Topics_GD/Exploration-vs-Exploitation.md | 6 +- .../Topics_GD/Exploratory-Data-Analysis.md | 6 +- 10_Wiki/Topics_GD/Expo 2025 Osaka.md | 12 +- 10_Wiki/Topics_GD/Exponential-Growth.md | 12 +- 10_Wiki/Topics_GD/Extended-Reality-XR.md | 6 +- 10_Wiki/Topics_GD/Externalities.md | 10 +- 10_Wiki/Topics_GD/Extreme-Programming-XP.md | 4 +- .../Topics_GD/Eye-Tracking-in-UX-Research.md | 12 +- 10_Wiki/Topics_GD/Eye-Tracking.md | 14 +- 10_Wiki/Topics_GD/Factor-Analysis.md | 4 +- 10_Wiki/Topics_GD/Factory-Pattern.md | 6 +- 10_Wiki/Topics_GD/Failable-Task-Handling.md | 10 +- 10_Wiki/Topics_GD/Fate War.md | 6 +- 10_Wiki/Topics_GD/Fault-Tolerance.md | 8 +- .../Topics_GD/Feature Clamping (피처 고정).md | 2 +- 10_Wiki/Topics_GD/Feature-Engineering.md | 6 +- 10_Wiki/Topics_GD/Feature-Flags.md | 12 +- 10_Wiki/Topics_GD/Federated-Learning.md | 4 +- 10_Wiki/Topics_GD/Feedback-Control-Systems.md | 6 +- .../Topics_GD/Feedback-Loops in Systems.md | 8 +- 10_Wiki/Topics_GD/Feedback-Loops-in-Design.md | 10 +- 10_Wiki/Topics_GD/Feedback-Loops.md | 12 +- 10_Wiki/Topics_GD/Few-Shot-Learning.md | 6 +- 10_Wiki/Topics_GD/Figma-to-Code-Workflow.md | 12 +- 10_Wiki/Topics_GD/Figurative-Language.md | 6 +- .../Final Fantasy XV- A New Empire.md | 6 +- 10_Wiki/Topics_GD/Fine-tuning.md | 8 +- 10_Wiki/Topics_GD/Finished Goods.md | 16 +- 10_Wiki/Topics_GD/Finite-Element-Analysis.md | 4 +- .../Topics_GD/Finite-State-Machines-FSM.md | 8 +- 10_Wiki/Topics_GD/Finite-State-Machines.md | 10 +- 10_Wiki/Topics_GD/First Input Delay (FID).md | 14 +- 10_Wiki/Topics_GD/Fitness-Landscape.md | 4 +- .../Fixed Time Step vs Variable Time Step.md | 2 +- 10_Wiki/Topics_GD/Flak Tank.md | 6 +- 10_Wiki/Topics_GD/Flow State.md | 6 +- 10_Wiki/Topics_GD/Flow-State.md | 14 +- 10_Wiki/Topics_GD/Fluent-Interface-Design.md | 8 +- 10_Wiki/Topics_GD/Fluid-Dynamics for Games.md | 4 +- 10_Wiki/Topics_GD/Focal-Loss.md | 4 +- .../Folder Structure Best Practices.md | 12 +- 10_Wiki/Topics_GD/Formal Methods.md | 12 +- .../Formal-Verification-of-Software.md | 12 +- 10_Wiki/Topics_GD/Foundation-Models.md | 12 +- .../Topics_GD/Foundational LLM Concepts.md | 8 +- 10_Wiki/Topics_GD/Fragility.md | 18 +- 10_Wiki/Topics_GD/Free-Energy-Principle.md | 8 +- .../Frontend Performance Debugging.md | 16 +- ...ntend-Architecture-and-Folder-Structure.md | 4 +- 10_Wiki/Topics_GD/Frontend-Architecture.md | 6 +- .../Frontend-Debugging-and-Testing.md | 6 +- ...Frontend-Performance-Optimization-Guide.md | 14 +- ...ntend-Team-Collaboration-and-Governance.md | 8 +- 10_Wiki/Topics_GD/Frontend.md | 14 +- .../Frontend_Governance_and_Observability.md | 10 +- 10_Wiki/Topics_GD/Functional Programming.md | 10 +- .../Functional-Programming-in-TypeScript.md | 8 +- 10_Wiki/Topics_GD/Functional-Programming.md | 4 +- 10_Wiki/Topics_GD/Fuzzy-Logic.md | 8 +- 10_Wiki/Topics_GD/G-Stack Principles.md | 2 +- .../Topics_GD/G-Stack-Integration-Guide.md | 6 +- 10_Wiki/Topics_GD/GAN.md | 2 +- 10_Wiki/Topics_GD/GNN.md | 4 +- .../Topics_GD/GPT-Architecture-Foundations.md | 12 +- 10_Wiki/Topics_GD/GPU-Architecture.md | 10 +- .../Topics_GD/GPU-Programming-with-CUDA.md | 8 +- 10_Wiki/Topics_GD/GPU.md | 14 +- 10_Wiki/Topics_GD/GRPO.md | 14 +- 10_Wiki/Topics_GD/GRU.md | 8 +- 10_Wiki/Topics_GD/Gacha Mechanics Analysis.md | 12 +- 10_Wiki/Topics_GD/Gait-Analysis-Laboratory.md | 4 +- .../Topics_GD/Game Analytics (게임 분석).md | 4 +- 10_Wiki/Topics_GD/Game of War- Fire Age.md | 6 +- 10_Wiki/Topics_GD/Game-Balance-Design.md | 6 +- 10_Wiki/Topics_GD/Game-Balance-Modeling.md | 2 +- 10_Wiki/Topics_GD/Game-Design-Ontology.md | 16 +- 10_Wiki/Topics_GD/Game-Design-Theory.md | 10 +- 10_Wiki/Topics_GD/Game-Economy-Design.md | 4 +- 10_Wiki/Topics_GD/Game-Feel-and-Juiciness.md | 6 +- 10_Wiki/Topics_GD/Game-Loop-Architecture.md | 8 +- 10_Wiki/Topics_GD/Game-Mechanics.md | 8 +- 10_Wiki/Topics_GD/Game-Ontology-for-PCG.md | 16 +- 10_Wiki/Topics_GD/Game-Theory-in-AI.md | 8 +- 10_Wiki/Topics_GD/Game-Theory.md | 2 +- 10_Wiki/Topics_GD/Gamification-Strategies.md | 6 +- 10_Wiki/Topics_GD/Gamification-Theory.md | 12 +- 10_Wiki/Topics_GD/Gates.md | 12 +- 10_Wiki/Topics_GD/Gaussian-Processes.md | 10 +- 10_Wiki/Topics_GD/Gen-AI.md | 12 +- 10_Wiki/Topics_GD/Generalization-in-AI.md | 6 +- ...dversarial Networks (GANs) in Fine Arts.md | 6 +- 10_Wiki/Topics_GD/Generative-AI-Impact.md | 6 +- 10_Wiki/Topics_GD/Generative-AI.md | 10 +- .../Generative-Adversarial-Networks.md | 4 +- .../Topics_GD/Generics-and-Polymorphism.md | 14 +- 10_Wiki/Topics_GD/Genetic-Algorithms.md | 6 +- .../Geographic-Information-Systems.md | 14 +- 10_Wiki/Topics_GD/Geometric-Deep-Learning.md | 4 +- 10_Wiki/Topics_GD/Geriatric-Medicine.md | 16 +- 10_Wiki/Topics_GD/Gestalt Psychology.md | 16 +- 10_Wiki/Topics_GD/Gestalt-Principles in UX.md | 4 +- .../Topics_GD/Gestalt-Principles-of-Design.md | 8 +- 10_Wiki/Topics_GD/Gimbals-and-Orientation.md | 6 +- .../Git-Branching-Strategies-and-Workflows.md | 6 +- 10_Wiki/Topics_GD/Git-Version-Control.md | 6 +- 10_Wiki/Topics_GD/GitHub-Actions-CI-CD.md | 4 +- 10_Wiki/Topics_GD/GitLab CI.md | 10 +- 10_Wiki/Topics_GD/Git_Workflows.md | 10 +- 10_Wiki/Topics_GD/GloVe (Word Embeddings).md | 6 +- 10_Wiki/Topics_GD/Global-Standard.md | 12 +- 10_Wiki/Topics_GD/Global-vs-Local-Optima.md | 4 +- 10_Wiki/Topics_GD/Goal-Misgeneralization.md | 16 +- .../Goal-Oriented-Action-Planning.md | 6 +- 10_Wiki/Topics_GD/God-Object-Antipattern.md | 6 +- .../Godel's Incompleteness Theorems.md | 10 +- .../Google-Page-Experience-2025-Update.md | 6 +- .../Topics_GD/Gradient-Boosting-Machines.md | 4 +- 10_Wiki/Topics_GD/Gradient-Descent.md | 8 +- 10_Wiki/Topics_GD/Graph Theory.md | 8 +- 10_Wiki/Topics_GD/Graph-Coloring-Problem.md | 14 +- 10_Wiki/Topics_GD/Graph-Database.md | 4 +- 10_Wiki/Topics_GD/Graph-Theory.md | 6 +- 10_Wiki/Topics_GD/GraphQL-Code-Generator.md | 16 +- .../GraphRAG & Knowledge Graph Memory.md | 8 +- .../GraphRAG (그래프 기반 검색 증강 생성).md | 10 +- 10_Wiki/Topics_GD/Greedy-Algorithms.md | 8 +- 10_Wiki/Topics_GD/Grit.md | 14 +- 10_Wiki/Topics_GD/Grounded Theory Method.md | 10 +- .../Topics_GD/Growth-Mindset-Intervention.md | 14 +- 10_Wiki/Topics_GD/Growth-Mindset.md | 16 +- .../Guilty-Gear-Xrd-Rendering-Pipeline.md | 10 +- 10_Wiki/Topics_GD/HANDOVER.md | 16 +- 10_Wiki/Topics_GD/HBO-Prestige-Television.md | 12 +- .../HCI (Human-Computer Interaction).md | 12 +- 10_Wiki/Topics_GD/HHH.md | 16 +- 10_Wiki/Topics_GD/HMM.md | 8 +- 10_Wiki/Topics_GD/Habit-Formation.md | 6 +- 10_Wiki/Topics_GD/Hallucination (환각).md | 16 +- 10_Wiki/Topics_GD/Hallucination-in-LLM.md | 12 +- 10_Wiki/Topics_GD/Hallucination-in-LLMs.md | 8 +- .../Topics_GD/Hardware-Acceleration-for-AI.md | 10 +- 10_Wiki/Topics_GD/Hardware-Verification.md | 16 +- 10_Wiki/Topics_GD/Hardware.md | 14 +- 10_Wiki/Topics_GD/Hash-Functions-and-Maps.md | 6 +- 10_Wiki/Topics_GD/Health-Informatics.md | 16 +- 10_Wiki/Topics_GD/Hebbian-Learning.md | 4 +- 10_Wiki/Topics_GD/Hebbian-Theory.md | 12 +- 10_Wiki/Topics_GD/Heuristic-Search.md | 4 +- 10_Wiki/Topics_GD/Heuristics.md | 14 +- .../Hierarchical-Task-Network (HTN).md | 6 +- .../Topics_GD/High-Availability-Systems.md | 8 +- .../Topics_GD/High-Cohesion-Low-Coupling.md | 14 +- .../High-Frequency-Trading-Models.md | 12 +- .../High-Performance Computing (HPC).md | 14 +- .../Topics_GD/High-Performance-Coaching.md | 16 +- .../High-Performance-Organizations.md | 20 +- .../High-Performance-Sports-Science.md | 16 +- 10_Wiki/Topics_GD/Homeostasis (항상성).md | 14 +- 10_Wiki/Topics_GD/Homeostasis.md | 14 +- 10_Wiki/Topics_GD/Homomorphic-Encryption.md | 4 +- 10_Wiki/Topics_GD/Human Centered AI (HCAI).md | 12 +- 10_Wiki/Topics_GD/Human-AI-Collaboration.md | 2 +- .../Human-Computer-Interaction-HCI.md | 8 +- .../Topics_GD/Human-Computer-Interaction.md | 12 +- 10_Wiki/Topics_GD/Human-in-the-Loop (HITL).md | 8 +- 10_Wiki/Topics_GD/Human-in-the-loop-AI.md | 4 +- .../Topics_GD/Hybrid-Cloud-Architectures.md | 6 +- .../Hydration-Mismatch-and-SSR-Debugging.md | 10 +- .../Hyperinflation-in-Closed-Loop-Systems.md | 12 +- .../Topics_GD/Hyperparameter-Optimization.md | 6 +- 10_Wiki/Topics_GD/Hyperparameters.md | 16 +- 10_Wiki/Topics_GD/Hypostatic-Abstraction.md | 10 +- 10_Wiki/Topics_GD/Hypothesis-Testing.md | 4 +- 10_Wiki/Topics_GD/ICRE-Framework.md | 12 +- ...DE (Integrated Development Environment).md | 8 +- 10_Wiki/Topics_GD/IEEE-P36521.md | 14 +- 10_Wiki/Topics_GD/ISO-Standard.md | 10 +- 10_Wiki/Topics_GD/Ikigai (이키가이).md | 12 +- .../Image Inpainting (Vary Region).md | 6 +- 10_Wiki/Topics_GD/Image Parameters.md | 6 +- .../Topics_GD/Image-Classification-Mastery.md | 10 +- .../Image-Optimization-for-Web-Performance.md | 4 +- .../Image-Segmentation-Techniques.md | 4 +- 10_Wiki/Topics_GD/Image-Segmentation.md | 6 +- 10_Wiki/Topics_GD/Imbalanced-Data-Handling.md | 6 +- 10_Wiki/Topics_GD/Imitation-Learning.md | 10 +- 10_Wiki/Topics_GD/Immersive-Sim-Design.md | 16 +- 10_Wiki/Topics_GD/Immersive-Sim-Genre.md | 12 +- .../Immersive-Sims-Deus-Ex-Dishonored.md | 16 +- .../Topics_GD/Immersive-Sims-Deus-Ex-Thief.md | 10 +- 10_Wiki/Topics_GD/Immutability-Patterns.md | 14 +- 10_Wiki/Topics_GD/Impedance-Matching.md | 10 +- 10_Wiki/Topics_GD/In-Context-Learning.md | 6 +- 10_Wiki/Topics_GD/Inclusive-Design-and-UX.md | 6 +- 10_Wiki/Topics_GD/Incremental-Computation.md | 14 +- 10_Wiki/Topics_GD/Incremental-Learning.md | 6 +- .../Incremental-Static-Regeneration-ISR.md | 4 +- 10_Wiki/Topics_GD/Incrementalism.md | 12 +- .../Independent Component Analysis (ICA).md | 10 +- .../Independent-Component-Analysis.md | 6 +- .../Topics_GD/Index-Fragmentation-Analysis.md | 16 +- 10_Wiki/Topics_GD/Index.md | 8 +- 10_Wiki/Topics_GD/Index_1490.md | 2 +- 10_Wiki/Topics_GD/Index_1530.md | 2 +- 10_Wiki/Topics_GD/Index_1532.md | 2 +- 10_Wiki/Topics_GD/Index_1534.md | 2 +- 10_Wiki/Topics_GD/Indexing-Strategies.md | 6 +- 10_Wiki/Topics_GD/Indian-Innovation-Models.md | 14 +- .../Topics_GD/Indirect Prompt Injection.md | 8 +- 10_Wiki/Topics_GD/Inductive-Bias.md | 2 +- 10_Wiki/Topics_GD/Inductive-Reasoning.md | 16 +- 10_Wiki/Topics_GD/Inexact-Science.md | 14 +- .../Inference-Coupled Persistence.md | 8 +- 10_Wiki/Topics_GD/Inference-Optimization.md | 10 +- 10_Wiki/Topics_GD/Inferential-Statistics.md | 14 +- 10_Wiki/Topics_GD/Information-Entropy.md | 14 +- 10_Wiki/Topics_GD/Information-Retrieval-IR.md | 4 +- 10_Wiki/Topics_GD/Information-Society.md | 14 +- 10_Wiki/Topics_GD/Information-Theory.md | 2 +- 10_Wiki/Topics_GD/Infraspace.md | 16 +- .../Topics_GD/Infrastructure-as-Code-IaC.md | 6 +- .../Topics_GD/Inheritance-and-Polymorphism.md | 2 +- 10_Wiki/Topics_GD/Inner-Product-Spaces.md | 4 +- 10_Wiki/Topics_GD/Innovation.md | 14 +- 10_Wiki/Topics_GD/Inpainting & Outpainting.md | 6 +- .../Topics_GD/Input-Validation-Strategies.md | 4 +- 10_Wiki/Topics_GD/Inquiry-Based Learning.md | 10 +- 10_Wiki/Topics_GD/Instance-based-Learning.md | 6 +- 10_Wiki/Topics_GD/InstancedMesh2 library.md | 14 +- 10_Wiki/Topics_GD/Instinct.md | 10 +- 10_Wiki/Topics_GD/Instruction-Tuning.md | 10 +- 10_Wiki/Topics_GD/Intangible-Capital.md | 10 +- .../Integrated-Development-Environment.md | 4 +- .../Topics_GD/Integration-Testing-for-AI.md | 4 +- .../Topics_GD/Intellectual-Property-in-AI.md | 4 +- .../Interaction to Next Paint (INP).md | 22 +- .../Interaction-to-Next-Paint-INP.md | 14 +- .../Topics_GD/Interdisciplinary-Research.md | 16 +- .../Interface-Segregation-Principle.md | 8 +- 10_Wiki/Topics_GD/Internet of Things (IoT).md | 8 +- 10_Wiki/Topics_GD/Interop 2026.md | 12 +- 10_Wiki/Topics_GD/Interoperability.md | 16 +- .../Interpretability-vs-Explainability.md | 4 +- .../Topics_GD/Introduction-to-Programming.md | 14 +- 10_Wiki/Topics_GD/Introspection (자기성찰).md | 14 +- 10_Wiki/Topics_GD/Inverse-Kinematics.md | 8 +- .../Inverse-Reinforcement-Learning.md | 8 +- 10_Wiki/Topics_GD/Inversion.md | 18 +- 10_Wiki/Topics_GD/IoT-and-AI-Integration.md | 8 +- .../Isaac-Asimovs-Laws-of-Robotics.md | 4 +- .../Item-Item-Collaborative-Filtering.md | 4 +- 10_Wiki/Topics_GD/Iteration.md | 14 +- 10_Wiki/Topics_GD/Iterative Prompting.md | 6 +- .../Topics_GD/Iterative-Development-Models.md | 10 +- 10_Wiki/Topics_GD/Iterative-Development.md | 12 +- .../JIT-Compilation-in-AI-Engines.md | 4 +- 10_Wiki/Topics_GD/JSON-LD-Structured-Data.md | 6 +- .../Topics_GD/JSON-and-Data-Serialization.md | 4 +- .../Topics_GD/JUnit-and-Testing-Frameworks.md | 4 +- .../JavaScript-Async-and-Event-Loop.md | 8 +- .../JavaScript-Optimization-Patterns.md | 10 +- 10_Wiki/Topics_GD/Joint-Optimization.md | 12 +- 10_Wiki/Topics_GD/Journaling.md | 12 +- 10_Wiki/Topics_GD/Judgment.md | 14 +- 10_Wiki/Topics_GD/Just-In-Time (JIT).md | 12 +- 10_Wiki/Topics_GD/Just-in-Case.md | 16 +- .../Topics_GD/Just-in-time-Data-Loading.md | 6 +- .../K-Means-Clustering-Foundations.md | 8 +- 10_Wiki/Topics_GD/K-Nearest-Neighbors-K-NN.md | 10 +- .../KISS (Keep It Simple, Stupid).md | 10 +- .../KISS-Principle-in-Software-Design.md | 4 +- .../KPI (Key Performance Indicator).md | 12 +- .../Kalman-Filter-and-State-Tracking.md | 6 +- .../Kernel-Density-Estimation-KDE.md | 6 +- 10_Wiki/Topics_GD/Kernel-Methods-and-SVMs.md | 6 +- .../Topics_GD/Kingdom vs. Kingdom (KvK).md | 6 +- .../Kingdom vs. Kingdom Events (KvK).md | 6 +- 10_Wiki/Topics_GD/Knowledge synthesis.md | 16 +- 10_Wiki/Topics_GD/Knowledge-Distillation.md | 8 +- .../Topics_GD/Knowledge-Graph-Foundations.md | 6 +- 10_Wiki/Topics_GD/Knowledge-Graph.md | 8 +- .../Knowledge-Representation-in-AI.md | 16 +- 10_Wiki/Topics_GD/Knowledge-Structure.md | 16 +- 10_Wiki/Topics_GD/Kolmogorov-Complexity.md | 4 +- .../Kubernetes-for-AI-Orchestration.md | 4 +- .../Topics_GD/Kullback-Leibler-Divergence.md | 12 +- .../L-component (Lifecycle Hooks).md | 8 +- 10_Wiki/Topics_GD/L1-and-L2-Regularization.md | 6 +- 10_Wiki/Topics_GD/L2-Regularization.md | 12 +- 10_Wiki/Topics_GD/LLM-Security-and-Safety.md | 6 +- 10_Wiki/Topics_GD/LLM.md | 14 +- 10_Wiki/Topics_GD/LOD.md | 12 +- .../LSTM (Long Short-Term Memory).md | 10 +- 10_Wiki/Topics_GD/LSTM.md | 6 +- .../Topics_GD/Label-Noise-and-Robustness.md | 6 +- 10_Wiki/Topics_GD/Lagrange-Multipliers.md | 6 +- 10_Wiki/Topics_GD/Language-Models.md | 14 +- .../Topics_GD/Large Language Models (LLM).md | 14 +- ...scale-Application-Architecture-Patterns.md | 10 +- .../Largest Contentful Paint (LCP).md | 18 +- .../Topics_GD/Largest-Contentful-Paint-LCP.md | 12 +- .../Topics_GD/Latent-Dirichlet-Allocation.md | 6 +- .../Topics_GD/Latent-Semantic-Analysis-LSA.md | 8 +- 10_Wiki/Topics_GD/Layer-Normalization.md | 10 +- .../Layered-Architecture-in-Frontend.md | 10 +- 10_Wiki/Topics_GD/Lazy-Loading-Strategies.md | 6 +- 10_Wiki/Topics_GD/Leadership.md | 16 +- .../Topics_GD/Leaky-ReLU-and-Activations.md | 4 +- 10_Wiki/Topics_GD/Lean-Operations.md | 14 +- 10_Wiki/Topics_GD/Lean-Project-Management.md | 6 +- 10_Wiki/Topics_GD/Learning-Paths.md | 14 +- 10_Wiki/Topics_GD/Learning-Rate-Schedules.md | 4 +- 10_Wiki/Topics_GD/Learning-Rate-Scheduling.md | 4 +- 10_Wiki/Topics_GD/Least-Squares-Methods.md | 4 +- 10_Wiki/Topics_GD/Legacy-Systems.md | 14 +- 10_Wiki/Topics_GD/Legacy_React_Migration.md | 10 +- 10_Wiki/Topics_GD/Lessons Learned.md | 14 +- 10_Wiki/Topics_GD/Level of Detail (LOD).md | 14 +- 10_Wiki/Topics_GD/Level_Design/.gitkeep | 0 .../Topics_GD/Level_Design/Base Layouts.md | 6 +- 10_Wiki/Topics_GD/Level_Design/Index.md | 28 +- ...폴리오 확장 및 라이브 서비스 모델 고도화.md | 6 +- .../Level_Design/World War Rising.md | 6 +- .../거점(Control Points) 점령전.md | 6 +- .../기지 레이아웃 메타(Base Layout Meta).md | 6 +- .../기지 방어 레이아웃(Base Layouts).md | 6 +- ...방어 설계 및 공략(Base Defense and Siege).md | 6 +- .../Level_Design/기지 방어(Base Defense).md | 6 +- ...이아웃(Defensive Architecture and Base Layouts).md | 6 +- .../블리츠 기지 설계(Blitz Base Design).md | 6 +- .../Level_Design/세계 지도(World Map).md | 8 +- .../Level_Design/월드 맵(World Map).md | 6 +- 10_Wiki/Topics_GD/Levels of Understanding.md | 16 +- 10_Wiki/Topics_GD/Lighting and Composition.md | 6 +- .../Topics_GD/Linear-Algebra-Foundations.md | 4 +- 10_Wiki/Topics_GD/Linear-Algebra-for-ML.md | 4 +- 10_Wiki/Topics_GD/Linear-Algebra.md | 10 +- .../Topics_GD/Linear-Discriminant-Analysis.md | 6 +- 10_Wiki/Topics_GD/Linear-Programming.md | 10 +- .../Topics_GD/Linear-Regression-Mastery.md | 6 +- .../Topics_GD/Linguistic-Analysis-in-AI.md | 8 +- 10_Wiki/Topics_GD/Linked-Lists-and-Trees.md | 10 +- 10_Wiki/Topics_GD/Linux-Performance-Tuning.md | 8 +- 10_Wiki/Topics_GD/Liquid-Democracy.md | 2 +- .../Liskov-Substitution-Principle.md | 10 +- .../Topics_GD/Live Operations (LiveOps).md | 6 +- 10_Wiki/Topics_GD/LiveOps.md | 6 +- 10_Wiki/Topics_GD/LlamaIndex.md | 2 +- .../Topics_GD/LoRA (Low-Rank Adaptation).md | 10 +- .../Topics_GD/Load-Balancing-Strategies.md | 4 +- 10_Wiki/Topics_GD/Local-Brain-Management.md | 8 +- 10_Wiki/Topics_GD/Local-Search.md | 14 +- .../Locality-Sensitive-Hashing (LSH).md | 12 +- .../Topics_GD/Locality-Sensitive-Hashing.md | 4 +- 10_Wiki/Topics_GD/Logic.md | 10 +- .../Logistic-Regression-Foundations.md | 6 +- 10_Wiki/Topics_GD/Logistic-Regression.md | 12 +- .../Topics_GD/Long Animation Frames API.md | 14 +- 10_Wiki/Topics_GD/Long Tasks.md | 14 +- .../Long-Short-Term-Memory (LSTM).md | 12 +- 10_Wiki/Topics_GD/Long-Short-Term-Memory.md | 12 +- 10_Wiki/Topics_GD/Long-Tail.md | 10 +- 10_Wiki/Topics_GD/Loose-Coupling.md | 12 +- 10_Wiki/Topics_GD/Loss Functions.md | 16 +- .../Topics_GD/Loss-Functions-Foundations.md | 8 +- 10_Wiki/Topics_GD/Low-Rank-Adaptation-LoRA.md | 6 +- 10_Wiki/Topics_GD/Lubrication.md | 20 +- 10_Wiki/Topics_GD/Lucas-Kanade-Method.md | 4 +- 10_Wiki/Topics_GD/MAP-Estimation.md | 14 +- ...MBA (Master of Business Administration).md | 16 +- .../Topics_GD/MCP (Model Context Protocol).md | 10 +- 10_Wiki/Topics_GD/MCP.md | 10 +- 10_Wiki/Topics_GD/MLA-Format.md | 12 +- 10_Wiki/Topics_GD/MLOps.md | 8 +- .../Machinations 라이브옵스 데이터 연동.md | 6 +- .../Machinations(토크노믹스 시뮬레이션).md | 6 +- 10_Wiki/Topics_GD/Machinations.md | 6 +- 10_Wiki/Topics_GD/Machine Learning (ML).md | 8 +- .../Topics_GD/Machine-Learning-Foundations.md | 6 +- .../Topics_GD/Machine-Learning-Lifecycle.md | 4 +- 10_Wiki/Topics_GD/Macros (매크로).md | 10 +- 10_Wiki/Topics_GD/Magic-Circle.md | 6 +- 10_Wiki/Topics_GD/Main Thread.md | 16 +- 10_Wiki/Topics_GD/Malware-Analysis.md | 10 +- 10_Wiki/Topics_GD/Management.md | 16 +- 10_Wiki/Topics_GD/Manhattan-Distance.md | 4 +- 10_Wiki/Topics_GD/MapReduce.md | 16 +- 10_Wiki/Topics_GD/March 2026 Research Drop.md | 6 +- ...연구 업데이트(March 2026 Research Drop).md | 6 +- 10_Wiki/Topics_GD/Markov-Chain-Monte-Carlo.md | 4 +- 10_Wiki/Topics_GD/Markov-Chains.md | 16 +- .../Markov-Decision-Process (MDP).md | 10 +- .../Topics_GD/Markov-Decision-Process-MDP.md | 8 +- .../Topics_GD/Markov-Decision-Processes.md | 16 +- .../Master-of-Information-Management.md | 20 +- 10_Wiki/Topics_GD/Mastery.md | 14 +- 10_Wiki/Topics_GD/Matrix-Factorization.md | 4 +- 10_Wiki/Topics_GD/Matrix-Operations-and-AI.md | 6 +- 10_Wiki/Topics_GD/Mean-Absolute-Error-MAE.md | 8 +- 10_Wiki/Topics_GD/Mean-Squared-Error-MSE.md | 4 +- ...c Interpretability (기계적 해석 가능성).md | 12 +- 10_Wiki/Topics_GD/Media-Literacy.md | 14 +- .../Medical-Imaging-Data-Augmentation.md | 16 +- 10_Wiki/Topics_GD/Memetics.md | 10 +- 10_Wiki/Topics_GD/Memory-Hierarchy.md | 14 +- .../Memory-Leak-Debugging-in-JavaScript.md | 10 +- 10_Wiki/Topics_GD/Mental-Models.md | 16 +- .../Mental-Operations-Synthesized.md | 18 +- .../Message-Queues-and-Event-Streams.md | 4 +- 10_Wiki/Topics_GD/Meta-Learning-in-AI.md | 4 +- .../Micro-interactions-and-Feedback-Loops.md | 4 +- 10_Wiki/Topics_GD/Micro-interactions.md | 8 +- 10_Wiki/Topics_GD/Micro-management.md | 6 +- .../Topics_GD/Microservices-Architecture.md | 6 +- 10_Wiki/Topics_GD/Middle-Out-Thinking.md | 18 +- 10_Wiki/Topics_GD/Midjourney Parameter.md | 6 +- 10_Wiki/Topics_GD/Midjourney Parameters.md | 6 +- ... V6 및 V7 기반의 이미지 생성 워크플로우.md | 6 +- 10_Wiki/Topics_GD/Midjourney V7 Draft Mode.md | 6 +- .../Midjourney V7 및 V6 워크플로우.md | 6 +- .../Midjourney V7의 Draft Mode 워크플로우.md | 6 +- ...djourney 브랜드 캠페인 및 무드보드 제작.md | 6 +- 10_Wiki/Topics_GD/Minimal-Viable-Product.md | 14 +- .../Topics_GD/Minimum-Viable-Product-MVP.md | 6 +- 10_Wiki/Topics_GD/Mipmap.md | 10 +- 10_Wiki/Topics_GD/Mobile Strike.md | 6 +- 10_Wiki/Topics_GD/Mobile-AI-Optimization.md | 8 +- 10_Wiki/Topics_GD/Mobile-Augmented-Reality.md | 14 +- ...bile-First-Responsive-Design-Principles.md | 10 +- .../Topics_GD/Model Context Protocol (MCP).md | 8 +- .../Topics_GD/Model-Agnostic-Meta-Learning.md | 4 +- .../Topics_GD/Model-Compression-Strategies.md | 8 +- 10_Wiki/Topics_GD/Model-Compression.md | 14 +- .../Topics_GD/Model-Deployment-Patterns.md | 8 +- .../Topics_GD/Model-Drift-and-Monitoring.md | 8 +- 10_Wiki/Topics_GD/Model-Ensemble-Methods.md | 6 +- .../Topics_GD/Model-Interpretability-Tools.md | 4 +- .../Model-Predictive-Control (MPC).md | 8 +- ...odern-Frontend-Engineering-Architecture.md | 12 +- ...React-Application-Architecture-Patterns.md | 12 +- .../Modern-Web-Design-Best-Practices-2025.md | 8 +- .../Topics_GD/Modern-Website-Architecture.md | 12 +- .../Modern_React_Engineering_2025.md | 10 +- 10_Wiki/Topics_GD/Modular-Design.md | 12 +- 10_Wiki/Topics_GD/Modular-Programming.md | 12 +- 10_Wiki/Topics_GD/Modularity.md | 12 +- .../Topics_GD/Momentum-and-Optimization.md | 4 +- .../Topics_GD/Monolithic-vs-Microservices.md | 8 +- 10_Wiki/Topics_GD/Monte-Carlo-Integration.md | 4 +- 10_Wiki/Topics_GD/Monte-Carlo-Methods.md | 14 +- .../Topics_GD/Monte-Carlo-Tree-Search-MCTS.md | 6 +- 10_Wiki/Topics_GD/Moodboard Creation.md | 6 +- .../Multi-Agent-Reinforcement-Learning.md | 6 +- 10_Wiki/Topics_GD/Multi-Agent-Systems-MAS.md | 12 +- .../Multi-Head-Attention-Mechanism.md | 4 +- 10_Wiki/Topics_GD/Multi-Modal-Learning.md | 6 +- 10_Wiki/Topics_GD/Multi-agent-System.md | 14 +- .../Topics_GD/Multi-armed-Bandit-Problem.md | 4 +- .../Topics_GD/Multilayer-Perceptron-MLP.md | 2 +- 10_Wiki/Topics_GD/Multimodal-Learning.md | 14 +- 10_Wiki/Topics_GD/Multinomial-Naive-Bayes.md | 8 +- 10_Wiki/Topics_GD/Multivariate-Analysis.md | 4 +- 10_Wiki/Topics_GD/Mutual-Information.md | 4 +- .../NLP (Natural Language Processing).md | 20 +- 10_Wiki/Topics_GD/NLP-Attention-Mechanisms.md | 8 +- 10_Wiki/Topics_GD/NVIDIA-CUDA-and-AI.md | 8 +- 10_Wiki/Topics_GD/Naive-Bayes-Classifiers.md | 2 +- .../Topics_GD/Named-Entity-Recognition-NER.md | 6 +- .../Topics_GD/National-Language-Processing.md | 6 +- .../Natural-Language-Generation-NLG.md | 6 +- .../Natural-Language-Processing-NLP.md | 8 +- .../Topics_GD/Natural-Language-Processing.md | 8 +- 10_Wiki/Topics_GD/Nearest-Neighbor-Search.md | 8 +- .../Topics_GD/Network-Latency-Optimization.md | 8 +- .../Neural-Architecture-Search-NAS.md | 10 +- .../Topics_GD/Neural-Architecture-Search.md | 10 +- 10_Wiki/Topics_GD/Neural-Darwinism.md | 2 +- .../Neural-Networks (신경망 기초).md | 6 +- .../Neural-Networks-for-Beginners.md | 6 +- 10_Wiki/Topics_GD/Neural-Style-Transfer.md | 8 +- .../Topics_GD/Neural-Symbolic-Integration.md | 10 +- 10_Wiki/Topics_GD/Neuro-Symbolic AI.md | 12 +- 10_Wiki/Topics_GD/Neuro-Symbolic-AI.md | 8 +- 10_Wiki/Topics_GD/Neurobiology-of-Reward.md | 12 +- .../Topics_GD/Neurodevelopmental Disorders.md | 8 +- 10_Wiki/Topics_GD/Neuroeconomics.md | 10 +- 10_Wiki/Topics_GD/Neuroergonomics.md | 8 +- 10_Wiki/Topics_GD/Neuroevolution.md | 4 +- 10_Wiki/Topics_GD/Neuromuscular-Adaptation.md | 6 +- 10_Wiki/Topics_GD/Neuromuscular-Control.md | 10 +- ...pharmacology of Substance Use Disorders.md | 6 +- .../Topics_GD/Neuroplasticity in Addiction.md | 8 +- .../Neuroplasticity in Motor Learning.md | 8 +- .../Neuroplasticity-in-Motor-Learning.md | 6 +- .../Topics_GD/Neuroprosthetics-Development.md | 8 +- .../Topics_GD/Neuropsychiatric Disorders.md | 10 +- 10_Wiki/Topics_GD/Neuropsychology.md | 10 +- .../Neurorehabilitation after Stroke.md | 8 +- .../Neurorehabilitation-Post-Stroke.md | 8 +- 10_Wiki/Topics_GD/Next-js-and-Modern-Web.md | 10 +- .../Nextjs-App-Router-Architecture.md | 12 +- .../Nextjs_and_Modern_React_Patterns.md | 10 +- ... Sky (Large-scale planetary generation).md | 12 +- 10_Wiki/Topics_GD/No Mans Sky.md | 8 +- 10_Wiki/Topics_GD/NoSQL-Databases-in-AI.md | 6 +- 10_Wiki/Topics_GD/Nodejs 메모리 누수 분석.md | 22 +- .../Nodejs 프로덕션 메모리 누수 진단.md | 16 +- .../Nodejs 프로덕션 메모리 병목 분석.md | 20 +- .../Nodejs-Global-Namespace-Augmentation.md | 8 +- 10_Wiki/Topics_GD/Noise-Reduction-in-AI.md | 10 +- 10_Wiki/Topics_GD/Noise.md | 16 +- .../Topics_GD/Nominal-Typing-in-TypeScript.md | 12 +- ...hotorealistic-Rendering-in-Level-Design.md | 10 +- .../Non-linear-Activation-Functions.md | 4 +- 10_Wiki/Topics_GD/Non-parametric-Models.md | 8 +- 10_Wiki/Topics_GD/Normalization-Strategies.md | 6 +- 10_Wiki/Topics_GD/Normalization.md | 10 +- .../Topics_GD/Nuclear Deterrence Models.md | 10 +- 10_Wiki/Topics_GD/Numbers-and-Games.md | 12 +- 10_Wiki/Topics_GD/Nutritional-Biochemistry.md | 8 +- 10_Wiki/Topics_GD/OKR.md | 16 +- ...WA vs CWA (개방 세계 vs 폐쇄 세계 가설).md | 8 +- 10_Wiki/Topics_GD/OWASP Top 10.md | 16 +- .../Object Pooling (오브젝트 풀링).md | 12 +- .../Topics_GD/Object-Detection-Foundations.md | 4 +- .../Object-Oriented-Design-Patterns.md | 10 +- .../Topics_GD/Object-Oriented-Programming.md | 2 +- 10_Wiki/Topics_GD/Objective-Functions.md | 6 +- 10_Wiki/Topics_GD/Objectivism.md | 10 +- 10_Wiki/Topics_GD/Observation.md | 16 +- 10_Wiki/Topics_GD/Occupational-Therapy.md | 6 +- .../Off-policy-vs-On-policy-Learning.md | 6 +- .../Topics_GD/Okami-Ink-Wash-Aesthetics.md | 8 +- 10_Wiki/Topics_GD/Olympic-Training-Cycles.md | 6 +- 10_Wiki/Topics_GD/Olympic-Training-Models.md | 6 +- .../Topics_GD/Olympic-Training-Protocols.md | 10 +- 10_Wiki/Topics_GD/Omni Reference (--oref).md | 6 +- 10_Wiki/Topics_GD/Omni Reference.md | 6 +- 10_Wiki/Topics_GD/One-Hot-Encoding.md | 6 +- 10_Wiki/Topics_GD/One-Shot-Learning.md | 6 +- .../Online-Learning-and-Streaming.md | 8 +- 10_Wiki/Topics_GD/Ontological-Engineering.md | 10 +- .../Ontology-Driven-Relevancy-Filtering.md | 10 +- 10_Wiki/Topics_GD/Ontology-Engineering.md | 10 +- .../Ontology-Guided Knowledge Extraction.md | 12 +- .../Ontology-and-Knowledge-Representation.md | 6 +- 10_Wiki/Topics_GD/Ontology.md | 12 +- 10_Wiki/Topics_GD/Opaque-Types.md | 10 +- 10_Wiki/Topics_GD/Open-Access-Movement.md | 6 +- 10_Wiki/Topics_GD/Open-Source-AI-Ecosystem.md | 6 +- 10_Wiki/Topics_GD/OpenAI-API-Integration.md | 6 +- 10_Wiki/Topics_GD/Operation- Western Sun.md | 6 +- 10_Wiki/Topics_GD/Operations-Management.md | 8 +- 10_Wiki/Topics_GD/Operations-Research.md | 10 +- 10_Wiki/Topics_GD/Operator-Theory.md | 10 +- 10_Wiki/Topics_GD/Opportunity-Cost.md | 14 +- .../Optical-Character-Recognition.md | 8 +- 10_Wiki/Topics_GD/Optimal-Control-Theory.md | 6 +- 10_Wiki/Topics_GD/Optimization-Algorithms.md | 10 +- 10_Wiki/Topics_GD/Optimization-in-AI.md | 6 +- 10_Wiki/Topics_GD/Optimization.md | 14 +- 10_Wiki/Topics_GD/Ordinal-Data-Analysis.md | 4 +- .../Topics_GD/Organizational Psychology.md | 10 +- .../Out-of-distribution-Detection.md | 4 +- .../Outer Alignment vs Inner Alignment.md | 12 +- .../Topics_GD/Outlier-Detection-Techniques.md | 6 +- 10_Wiki/Topics_GD/Outside-Thinking.md | 14 +- .../Topics_GD/Overfitting-and-Underfitting.md | 4 +- 10_Wiki/Topics_GD/Overfitting.md | 14 +- .../Topics_GD/P-Reinforce-Template-Guide.md | 4 +- 10_Wiki/Topics_GD/P-Reinforce.md | 18 +- .../Topics_GD/PCA-and-Dimension-Reduction.md | 4 +- 10_Wiki/Topics_GD/PCGML-Frameworks.md | 12 +- 10_Wiki/Topics_GD/PDF-Format.md | 12 +- .../PEFT (Parameter-Efficient Fine-Tuning).md | 12 +- 10_Wiki/Topics_GD/PEV_Loop.md | 10 +- 10_Wiki/Topics_GD/PID-Controllers-in-AI.md | 4 +- 10_Wiki/Topics_GD/PMI-Technique.md | 12 +- 10_Wiki/Topics_GD/POMDP.md | 14 +- 10_Wiki/Topics_GD/PageSpeed Insights.md | 12 +- ...Papers Please (Bureaucratic Simulation).md | 8 +- 10_Wiki/Topics_GD/Papers-Please.md | 10 +- 10_Wiki/Topics_GD/Parallel-Computing-in-AI.md | 4 +- 10_Wiki/Topics_GD/Parallel-Computing.md | 6 +- 10_Wiki/Topics_GD/Parallel-Processing.md | 10 +- 10_Wiki/Topics_GD/Parameter Control.md | 6 +- .../Topics_GD/Parameter-Efficiency-in-LLMs.md | 8 +- .../Parameter-Efficient Fine-Tuning (PEFT).md | 10 +- 10_Wiki/Topics_GD/Parameter-Sharing.md | 6 +- 10_Wiki/Topics_GD/Parameter.md | 6 +- 10_Wiki/Topics_GD/Pareto-Principle.md | 12 +- .../Partial-Differential-Equations.md | 4 +- .../Topics_GD/Particle-Filter-Algorithms.md | 4 +- 10_Wiki/Topics_GD/Pattern-Recognition.md | 4 +- 10_Wiki/Topics_GD/Pay-to-win.md | 18 - 10_Wiki/Topics_GD/Pedestrian-Modeling.md | 8 +- 10_Wiki/Topics_GD/Perceptrons-Foundations.md | 6 +- 10_Wiki/Topics_GD/Perceptual-Learning.md | 6 +- 10_Wiki/Topics_GD/Perceptual-Motor-Skills.md | 8 +- .../Performance Management Systems.md | 12 +- 10_Wiki/Topics_GD/Performance Psychology.md | 10 +- .../Topics_GD/Performance-Metrics-in-AI.md | 4 +- .../Performance_and_Memory_Management.md | 10 +- 10_Wiki/Topics_GD/Periodization-Theory.md | 8 +- 10_Wiki/Topics_GD/Permanent Loss.md | 6 +- .../Topics_GD/Personal-Brain-Management.md | 4 +- .../Personal-Information-Security.md | 2 +- 10_Wiki/Topics_GD/Personalization-Engines.md | 6 +- .../Phase-Transitions-in-Learning.md | 6 +- 10_Wiki/Topics_GD/Philosophy.md | 12 +- 10_Wiki/Topics_GD/Physical-Intelligence.md | 16 +- ...hysics-Informed Neural Networks (PINNs).md | 8 +- .../Physics-informed-Neural-Networks.md | 8 +- 10_Wiki/Topics_GD/Physics.md | 12 +- 10_Wiki/Topics_GD/Pipeline-Parallelism.md | 6 +- 10_Wiki/Topics_GD/Pivot-Table-Analysis.md | 4 +- 10_Wiki/Topics_GD/Platform-Engineering.md | 8 +- .../Topics_GD/Player-Experience-Modeling.md | 18 +- .../Player-Psyche-Profiling-Framework.md | 8 +- .../Topics_GD/Plutchiks-Wheel-of-Emotions.md | 14 +- 10_Wiki/Topics_GD/Poetic-Computation.md | 8 +- 10_Wiki/Topics_GD/Point-Cloud-Processing.md | 8 +- 10_Wiki/Topics_GD/Point-of-Sale.md | 14 +- 10_Wiki/Topics_GD/Policy-Gradient-Methods.md | 8 +- 10_Wiki/Topics_GD/Policy-Optimization.md | 10 +- 10_Wiki/Topics_GD/Policy-Surveillance.md | 6 +- 10_Wiki/Topics_GD/PolicyIQ.md | 8 +- .../Polymorphism-in-Engine-Architecture.md | 16 +- 10_Wiki/Topics_GD/Pooling.md | 12 +- 10_Wiki/Topics_GD/Pose-Estimation.md | 4 +- 10_Wiki/Topics_GD/Positive Prompts.md | 6 +- 10_Wiki/Topics_GD/Positive-Reinforcement.md | 4 +- .../Posterior-and-Prior-Probability.md | 4 +- 10_Wiki/Topics_GD/Poverty-Cycle-Dynamics.md | 8 +- 10_Wiki/Topics_GD/Poverty-Simulation.md | 8 +- .../Power Creep (Content Treadmills).md | 6 +- 10_Wiki/Topics_GD/Practical-Cryptography.md | 12 +- 10_Wiki/Topics_GD/Pre-Mortem-Analysis.md | 10 +- .../Topics_GD/Pre-processing-Data-for-AI.md | 6 +- .../Topics_GD/Precision-Recall-Tradeoff.md | 2 +- 10_Wiki/Topics_GD/Precision-Recursion.md | 14 +- 10_Wiki/Topics_GD/Predictive-Analytics.md | 6 +- 10_Wiki/Topics_GD/Predictive-Coding.md | 6 +- 10_Wiki/Topics_GD/Prenatal-Neurology.md | 6 +- .../Preserving-State-in-Procedural-Worlds.md | 16 +- .../Topics_GD/Principal-Component-Analysis.md | 4 +- .../Topics_GD/Principle-Component-Analysis.md | 16 +- .../Topics_GD/Principle-of-Least-Action.md | 4 +- ...rinciples of Structuralism (Linguistic).md | 8 +- .../Topics_GD/Principles-of-Architecture.md | 16 +- .../Topics_GD/Principles-of-Data-Connect.md | 8 +- .../Topics_GD/Principles-of-Structuralism.md | 10 +- 10_Wiki/Topics_GD/Principles.md | 12 +- .../Prioritized-Experience-Replay.md | 4 +- 10_Wiki/Topics_GD/Prisoners-Dilemma-Models.md | 10 +- .../Topics_GD/Prisons-and-Self-Correction.md | 14 +- 10_Wiki/Topics_GD/Privacy-Preserving-AI.md | 4 +- .../Probabilistic-Graphical-Models.md | 4 +- 10_Wiki/Topics_GD/Probabilistic-Reasoning.md | 12 +- 10_Wiki/Topics_GD/Probability Theory.md | 8 +- .../Topics_GD/Probability and Logic Fusion.md | 10 +- .../Probability-Theory-Foundations.md | 10 +- 10_Wiki/Topics_GD/Problem-Solving.md | 20 +- ...Generation via Machine Learning (PCGML).md | 10 +- .../Procedural Narrative Generation.md | 6 +- .../Procedural Rhetoric (In Gaming).md | 8 +- .../Procedural-Architecture-Systems.md | 10 +- 10_Wiki/Topics_GD/Procedural-Knowledge.md | 14 +- .../Topics_GD/Procedural-Level-Geometry.md | 10 +- 10_Wiki/Topics_GD/Procedural-Rhetoric.md | 8 +- .../Topics_GD/Process-Automation-with-AI.md | 4 +- 10_Wiki/Topics_GD/Processing.md | 12 +- 10_Wiki/Topics_GD/Product-Led-Growth.md | 12 +- 10_Wiki/Topics_GD/Product-Management.md | 14 +- 10_Wiki/Topics_GD/Product-Marketing.md | 10 +- 10_Wiki/Topics_GD/Product-Thinking-in-AI.md | 6 +- .../Topics_GD/Productivity-Hacks-for-Devs.md | 8 +- .../Topics_GD/Profiling-and-Optimization.md | 6 +- 10_Wiki/Topics_GD/Progressive-Disclosure.md | 6 +- .../Project-Management-Best-Practices.md | 8 +- 10_Wiki/Topics_GD/Project-Management.md | 16 +- 10_Wiki/Topics_GD/Prompt Engineering.md | 10 +- 10_Wiki/Topics_GD/Prompt Structure.md | 6 +- .../Prompt-Engineering-Foundations.md | 8 +- 10_Wiki/Topics_GD/Prompt-Engineering.md | 10 +- 10_Wiki/Topics_GD/Proprioception.md | 10 +- 10_Wiki/Topics_GD/Pros-Cons-Table.md | 12 +- 10_Wiki/Topics_GD/Protocols.md | 12 +- 10_Wiki/Topics_GD/Prototyping.md | 12 +- .../Proximal Policy Optimization (PPO).md | 10 +- .../Topics_GD/Proximal-Policy-Optimization.md | 8 +- 10_Wiki/Topics_GD/Pruning-Techniques.md | 6 +- .../Ps-Reinforce Policy Framework.md | 8 +- 10_Wiki/Topics_GD/Ps-Reinforce.md | 6 +- 10_Wiki/Topics_GD/Psychology & Behavior.md | 12 +- 10_Wiki/Topics_GD/Psychology-of-Learning.md | 6 +- 10_Wiki/Topics_GD/Psychology.md | 14 +- .../Topics_GD/Pull Request (PR) 워크플로우.md | 12 +- 10_Wiki/Topics_GD/Pull Request (PR).md | 14 +- 10_Wiki/Topics_GD/Pull-Request.md | 10 +- 10_Wiki/Topics_GD/Purpose.md | 18 +- 10_Wiki/Topics_GD/Puzzles & Survival.md | 6 +- 10_Wiki/Topics_GD/PyTorch-Foundations.md | 6 +- 10_Wiki/Topics_GD/PyTorch-Lightning.md | 8 +- 10_Wiki/Topics_GD/Python-for-Data-Science.md | 4 +- 10_Wiki/Topics_GD/Q-Learning Foundations.md | 10 +- 10_Wiki/Topics_GD/Quality Gates.md | 12 +- 10_Wiki/Topics_GD/Quality-Control.md | 12 +- .../Quantitative Economics (수량경제학).md | 10 +- 10_Wiki/Topics_GD/Quantization-Foundations.md | 4 +- 10_Wiki/Topics_GD/Quantization.md | 14 +- .../Topics_GD/Quantum Computing (Intro).md | 10 +- 10_Wiki/Topics_GD/Quantum-Computing-for-AI.md | 8 +- 10_Wiki/Topics_GD/Quantum-Computing.md | 10 +- 10_Wiki/Topics_GD/Quantum-Machine-Learning.md | 4 +- 10_Wiki/Topics_GD/Query-Optimization.md | 10 +- 10_Wiki/Topics_GD/Queue-Management-Systems.md | 6 +- 10_Wiki/Topics_GD/Quick-Wins.md | 14 +- 10_Wiki/Topics_GD/RAG (검색 증강 생성).md | 10 +- .../Topics_GD/RAG-and-Document-Retrieval.md | 6 +- 10_Wiki/Topics_GD/RAG.md | 10 +- .../RLAIF (AI 피드백 기반 강화학습).md | 8 +- .../RLHF (인간 피드백 기반 강화 학습).md | 16 +- 10_Wiki/Topics_GD/RL_Neuroscience.md | 8 +- 10_Wiki/Topics_GD/RMSProp-Optimizer.md | 6 +- 10_Wiki/Topics_GD/RNN.md | 14 +- 10_Wiki/Topics_GD/ROC-AUC-Curves.md | 4 +- 10_Wiki/Topics_GD/ROUGE-Metrics.md | 6 +- .../Topics_GD/Random-Forest-Classifiers.md | 8 +- 10_Wiki/Topics_GD/Randomized-Algorithms.md | 8 +- 10_Wiki/Topics_GD/Ranking-Algorithms.md | 4 +- 10_Wiki/Topics_GD/Rapid-Prototyping.md | 16 +- .../Topics_GD/ReLU-Activation-Functions.md | 12 +- .../Topics_GD/React Application Scaling.md | 4 +- .../Topics_GD/React Frontend Architecture.md | 14 +- 10_Wiki/Topics_GD/React Scalability.md | 18 +- 10_Wiki/Topics_GD/React-Context-API.md | 10 +- .../React-Error-Boundaries-and-Handling.md | 6 +- 10_Wiki/Topics_GD/React-Hooks.md | 12 +- 10_Wiki/Topics_GD/Reactive-Programming.md | 12 +- 10_Wiki/Topics_GD/Real-Time Engine (RTE).md | 14 +- 10_Wiki/Topics_GD/Real-time-Data-Streaming.md | 10 +- 10_Wiki/Topics_GD/Real-time-Operation.md | 12 +- 10_Wiki/Topics_GD/Reasoning & Planning.md | 12 +- 10_Wiki/Topics_GD/Reasoning.md | 14 +- 10_Wiki/Topics_GD/Recommendation-Systems.md | 8 +- .../Recording Academy (The Grammys).md | 10 +- .../Topics_GD/Recurrent-Neural-Networks.md | 10 +- .../Refactoring-Legacy-React-Codebases.md | 8 +- 10_Wiki/Topics_GD/Reference-Management.md | 14 +- 10_Wiki/Topics_GD/Reference.md | 12 +- 10_Wiki/Topics_GD/Refinement.md | 16 +- 10_Wiki/Topics_GD/Reflection.md | 12 +- .../Regression-Analysis-Foundations.md | 8 +- .../Topics_GD/Regularization-Strategies.md | 6 +- .../Topics_GD/Regularization-Techniques.md | 4 +- 10_Wiki/Topics_GD/Regularization.md | 12 +- .../Topics_GD/Reinforcement Learning (RL).md | 12 +- ...ment Learning for Automated Playtesting.md | 12 +- ...ement-Learning-from-Human-Feedback-RLHF.md | 6 +- 10_Wiki/Topics_GD/Reinforcement-Learning.md | 10 +- 10_Wiki/Topics_GD/Related-Work.md | 14 +- .../Relational Algebra in Databases.md | 10 +- 10_Wiki/Topics_GD/Relational-Database.md | 12 +- 10_Wiki/Topics_GD/Relational-Databases.md | 8 +- 10_Wiki/Topics_GD/Relative-Positioning.md | 8 +- 10_Wiki/Topics_GD/Relevance-Feedback.md | 6 +- 10_Wiki/Topics_GD/Reliability.md | 14 +- 10_Wiki/Topics_GD/Remote-Rehabilitation.md | 6 +- 10_Wiki/Topics_GD/Replenishment.md | 14 +- 10_Wiki/Topics_GD/Reports.md | 14 +- 10_Wiki/Topics_GD/Repository.md | 12 +- 10_Wiki/Topics_GD/Representation Theory.md | 4 +- 10_Wiki/Topics_GD/Representation-Learning.md | 6 +- 10_Wiki/Topics_GD/Requirements.md | 12 +- 10_Wiki/Topics_GD/ResNet-Architectures.md | 6 +- 10_Wiki/Topics_GD/Research-Framework.md | 18 +- 10_Wiki/Topics_GD/Research-Methodology.md | 14 +- 10_Wiki/Topics_GD/Research.md | 14 +- 10_Wiki/Topics_GD/Residual-Networks.md | 6 +- 10_Wiki/Topics_GD/Resilience.md | 18 +- 10_Wiki/Topics_GD/Resource-Allocation.md | 14 +- 10_Wiki/Topics_GD/Resource-Management.md | 8 +- 10_Wiki/Topics_GD/Restorative Justice.md | 8 +- 10_Wiki/Topics_GD/Retainers(유지 경로).md | 16 +- 10_Wiki/Topics_GD/Retaining Path.md | 12 +- .../Retrieval-Augmented Generation (RAG).md | 10 +- .../Retrieval-Augmented-Generation-RAG.md | 6 +- 10_Wiki/Topics_GD/Revenge-Cycle-Dynamics.md | 10 +- .../Topics_GD/Reward Hacking (보상 해킹).md | 8 +- 10_Wiki/Topics_GD/Reward Prediciton Error.md | 11 - ...eward Prediction Error (상태 예측 오류).md | 11 - 10_Wiki/Topics_GD/Reward Prediction Error.md | 10 +- 10_Wiki/Topics_GD/Reward-Shaping-in-RL.md | 6 +- 10_Wiki/Topics_GD/Ridge-Regression.md | 8 +- 10_Wiki/Topics_GD/Rise of Kingdoms.md | 6 +- 10_Wiki/Topics_GD/Risk Management.md | 12 +- 10_Wiki/Topics_GD/Risk-Assessment-with-AI.md | 8 +- 10_Wiki/Topics_GD/Risk-Management.md | 14 +- 10_Wiki/Topics_GD/Risk-Orchestration.md | 14 +- 10_Wiki/Topics_GD/Roadmap.md | 12 +- 10_Wiki/Topics_GD/Robotics-Foundations.md | 8 +- 10_Wiki/Topics_GD/Robotics.md | 10 +- 10_Wiki/Topics_GD/Robust-Machine-Learning.md | 6 +- 10_Wiki/Topics_GD/Robustness.md | 10 +- .../Roguelike Procedural Generation.md | 6 +- .../Role of Conflict in Narrative.md | 10 +- 10_Wiki/Topics_GD/Root-Cause-Analysis-RCA.md | 6 +- 10_Wiki/Topics_GD/Root-Mean-Square-Error.md | 6 +- .../Topics_GD/Roughness (그래픽 및 물리).md | 14 +- 10_Wiki/Topics_GD/Rule-based-Systems.md | 8 +- .../Topics_GD/S-component (State Store).md | 8 +- 10_Wiki/Topics_GD/SAR.md | 18 +- ...T (Static Application Security Testing).md | 14 +- .../SAST (정적 애플리케이션 보안 테스트).md | 16 +- .../SAST (정적 애플리케이션 보안 테스팅).md | 14 +- 10_Wiki/Topics_GD/SAST.md | 12 +- .../SCM (Supply Chain Management).md | 14 +- .../SDLC (소프트웨어 개발 수명 주기).md | 12 +- 10_Wiki/Topics_GD/SEO.md | 12 +- .../Topics_GD/SFT (Supervised Fine-Tuning).md | 10 +- 10_Wiki/Topics_GD/SME.md | 12 +- 10_Wiki/Topics_GD/SOTA.md | 16 +- 10_Wiki/Topics_GD/SOW.md | 16 +- 10_Wiki/Topics_GD/SPOF.md | 12 +- 10_Wiki/Topics_GD/SQL-Performance-Tuning.md | 8 +- 10_Wiki/Topics_GD/SRE.md | 12 +- .../Topics_GD/SaaS (Software as a Service).md | 12 +- 10_Wiki/Topics_GD/SaaS.md | 14 +- 10_Wiki/Topics_GD/Safety & Reliability.md | 10 +- 10_Wiki/Topics_GD/Sales-Strategy.md | 14 +- 10_Wiki/Topics_GD/Sampling-Techniques.md | 4 +- .../Topics_GD/Scalability-in-AI-Systems.md | 8 +- 10_Wiki/Topics_GD/Scalability.md | 14 +- .../Topics_GD/Scalable Frontend Systems.md | 18 +- .../Scalable-Design-System-Governance.md | 14 +- .../Scalable_Frontend_Architecture.md | 10 +- 10_Wiki/Topics_GD/Scaling-Laws-for-LLMs.md | 4 +- 10_Wiki/Topics_GD/Scheduler-Design-in-ML.md | 4 +- 10_Wiki/Topics_GD/Schema-Design-for-NoSQL.md | 6 +- 10_Wiki/Topics_GD/Schema.md | 10 +- 10_Wiki/Topics_GD/Science of Failure.md | 14 +- 10_Wiki/Topics_GD/Scientific Communication.md | 6 +- .../Scientific-Computing-with-Python.md | 2 +- 10_Wiki/Topics_GD/Scientific-Method.md | 18 +- 10_Wiki/Topics_GD/Scripts.md | 14 +- .../Topics_GD/Search-Engine-Optimization.md | 6 +- 10_Wiki/Topics_GD/Search-Methodology.md | 18 +- 10_Wiki/Topics_GD/Search-Optimization.md | 16 +- 10_Wiki/Topics_GD/Search-Space.md | 18 +- 10_Wiki/Topics_GD/Search-Strategy.md | 14 +- 10_Wiki/Topics_GD/Search.md | 8 +- 10_Wiki/Topics_GD/Secondary-Research.md | 12 +- .../Topics_GD/Sector Breach August 2025.md | 6 +- 10_Wiki/Topics_GD/Sector Breach 이벤트.md | 6 +- .../Secure-Multi-party-Computation.md | 4 +- 10_Wiki/Topics_GD/Security-Best-Practices.md | 4 +- 10_Wiki/Topics_GD/Security-Governance.md | 14 +- 10_Wiki/Topics_GD/Seed.md | 10 +- 10_Wiki/Topics_GD/Segmentsai.md | 12 +- .../Topics_GD/Self-Attention-Mechanisms.md | 6 +- .../Topics_GD/Self-Correction Mechanisms.md | 11 - 10_Wiki/Topics_GD/Self-Correction.md | 11 - .../Topics_GD/Self-Driving-Car-Foundations.md | 4 +- .../Self-Play (자기 대결 기반 강화학습).md | 8 +- .../Self-Supervised Learning (SSL).md | 10 +- 10_Wiki/Topics_GD/Self-Supervised-Learning.md | 8 +- 10_Wiki/Topics_GD/Self-verification.md | 8 +- .../Semantic Grounding & Provenance.md | 8 +- .../Topics_GD/Semantic-HTML-Foundations.md | 4 +- 10_Wiki/Topics_GD/Semantic-Search-with-AI.md | 8 +- 10_Wiki/Topics_GD/Semantic-Search.md | 6 +- 10_Wiki/Topics_GD/Semantics & Ontology.md | 8 +- 10_Wiki/Topics_GD/Semgrep Assistant.md | 10 +- 10_Wiki/Topics_GD/Sensitivity-Analysis.md | 18 +- 10_Wiki/Topics_GD/Sensor-Fusion.md | 4 +- .../Topics_GD/Sentiment-Analysis-Models.md | 8 +- 10_Wiki/Topics_GD/Sentiment-Analysis.md | 10 +- 10_Wiki/Topics_GD/Separation_of_Concerns.md | 4 +- 10_Wiki/Topics_GD/Sequence-Modeling.md | 12 +- .../Topics_GD/Sequence-to-Sequence-Models.md | 6 +- .../Topics_GD/Serverless-Computing-for-AI.md | 8 +- .../Service-oriented-Architecture.md | 4 +- 10_Wiki/Topics_GD/Session Lifecycle.md | 8 +- .../Topics_GD/Shadowing-and-Observability.md | 4 +- 10_Wiki/Topics_GD/Shape-Feature-Extraction.md | 4 +- .../Topics_GD/Sharding-and-Partitioning.md | 4 +- 10_Wiki/Topics_GD/Shift.md | 14 +- 10_Wiki/Topics_GD/Signal in Noise.md | 10 +- .../Signal-Processing-Foundations.md | 4 +- 10_Wiki/Topics_GD/Signature Style Design.md | 6 +- 10_Wiki/Topics_GD/Similarity-Metrics-in-AI.md | 4 +- 10_Wiki/Topics_GD/Similarity-Metrics.md | 12 +- 10_Wiki/Topics_GD/Simulated-Annealing.md | 6 +- 10_Wiki/Topics_GD/Simulation-Environments.md | 8 +- .../Simulator Sickness Questionnaire (SSQ).md | 6 +- .../Topics_GD/Singular-Value-Decomposition.md | 4 +- 10_Wiki/Topics_GD/Six-Sigma-Methodologies.md | 4 +- .../Topics_GD/Skybound Protocol 코드리뷰.md | 8 +- 10_Wiki/Topics_GD/Skybound_Reports/Index.md | 68 +- .../Skybound-Knowledge-Hub.md | 46 +- .../Skybound_Asset_Generation_Roadmap.md | 4 +- .../Skybound_Asset_Purity_Sync.md | 6 +- .../Skybound_Defensive_Architecture_Reboot.md | 6 +- .../Skybound_Enemy_Orientation_Fix.md | 4 +- .../Skybound_Firepower_Overclock_v1.5.md | 4 +- .../Skybound_Skill_Asset_Integration.md | 4 +- .../Skybound_Skill_Image_Integration.md | 6 +- ...ybound_Weapon_Behavior_Engine_Migration.md | 4 +- 10_Wiki/Topics_GD/Slack-Bot-Development.md | 4 +- 10_Wiki/Topics_GD/Smart-Contract-Auditing.md | 10 +- .../Topics_GD/Snowflake-Data-Warehousing.md | 8 +- ...r Labs 등 종합 애플리케이션 보안 플랫폼.md | 12 +- 10_Wiki/Topics_GD/Social Systems Theory.md | 10 +- 10_Wiki/Topics_GD/Social-Network-Analysis.md | 4 +- 10_Wiki/Topics_GD/Sociology of Knowledge.md | 10 +- 10_Wiki/Topics_GD/Soft Navigation.md | 8 +- 10_Wiki/Topics_GD/Soft-Skills-Development.md | 10 +- .../Software Engineering Agents (SWE).md | 8 +- .../Software-Architecture-Patterns.md | 8 +- .../Topics_GD/Software-Design-Principles.md | 12 +- 10_Wiki/Topics_GD/Solitude-Optimization.md | 12 +- 10_Wiki/Topics_GD/Solow Growth Model.md | 10 +- 10_Wiki/Topics_GD/Solution.md | 12 +- 10_Wiki/Topics_GD/SonarQube.md | 16 +- 10_Wiki/Topics_GD/Sorting.md | 16 +- 10_Wiki/Topics_GD/Sound Design Principles.md | 10 +- 10_Wiki/Topics_GD/Source-Control.md | 12 +- 10_Wiki/Topics_GD/Space-based-Architecture.md | 6 +- 10_Wiki/Topics_GD/Sparse-Data-Handling.md | 4 +- 10_Wiki/Topics_GD/Spatial-Data-Analysis.md | 6 +- 10_Wiki/Topics_GD/Specification.md | 14 +- 10_Wiki/Topics_GD/Spectral-Clustering.md | 4 +- 10_Wiki/Topics_GD/Speculative-Design.md | 8 +- .../Speech-Recognition-Foundations.md | 4 +- 10_Wiki/Topics_GD/Speech-Synthesis.md | 8 +- .../Topics_GD/Spiking-Neural-Networks-SNNs.md | 6 +- 10_Wiki/Topics_GD/Stability vs Flexibility.md | 14 +- 10_Wiki/Topics_GD/Stability.md | 11 - .../Stable Diffusion Image Optimization.md | 6 +- 10_Wiki/Topics_GD/Stable Diffusion Weights.md | 6 +- .../Stable Diffusion 오픈소스 제어.md | 6 +- .../Stable Diffusion의 가중치 제어 문법.md | 6 +- 10_Wiki/Topics_GD/Stacked-Generalization.md | 2 +- 10_Wiki/Topics_GD/Stages-of-Grief.md | 10 +- 10_Wiki/Topics_GD/Stakeholder.md | 10 +- .../Standard-Deviation-and-Variance.md | 6 +- .../Topics_GD/Standard-Operating-Procedure.md | 16 +- .../Standardization vs Innovation.md | 8 +- 10_Wiki/Topics_GD/Startup.md | 14 +- 10_Wiki/Topics_GD/State Space Model (SSM).md | 12 +- ...e-Management-Architecture-and-Ownership.md | 10 +- .../Topics_GD/State-Management-Patterns.md | 10 +- 10_Wiki/Topics_GD/State-Space-Models.md | 10 +- 10_Wiki/Topics_GD/State-Space.md | 14 +- 10_Wiki/Topics_GD/State.md | 12 +- .../State_Management_and_Concurrent_React.md | 10 +- ...tic Application Security Testing (SAST).md | 16 +- .../Static-Site-Generation-with-Gatsby.md | 2 +- 10_Wiki/Topics_GD/Statistical-Analysis.md | 16 +- .../Statistical-Hypothesis-Testing.md | 6 +- .../Topics_GD/Statistical-Learning-Theory.md | 4 +- 10_Wiki/Topics_GD/Statistical-Power.md | 6 +- .../Topics_GD/Statistics & Data Analysis.md | 8 +- 10_Wiki/Topics_GD/Statistics.md | 10 +- 10_Wiki/Topics_GD/Steel Division 시리즈.md | 4 +- 10_Wiki/Topics_GD/Stem-Analysis.md | 14 +- .../Stochastic-Gradient-Descent-SGD.md | 10 +- .../Topics_GD/Stochastic-Gradient-Descent.md | 12 +- 10_Wiki/Topics_GD/Storage-Area-Networks.md | 6 +- 10_Wiki/Topics_GD/Storage.md | 14 +- 10_Wiki/Topics_GD/Storybook.md | 14 +- 10_Wiki/Topics_GD/Straightening.md | 8 +- 10_Wiki/Topics_GD/Strategic-Alignment.md | 10 +- 10_Wiki/Topics_GD/Strategic-Ambiguity.md | 8 +- .../Topics_GD/Strategic-Planning-for-AI.md | 6 +- 10_Wiki/Topics_GD/Strategic-Planning.md | 18 +- 10_Wiki/Topics_GD/Strategic-Thinking.md | 12 +- 10_Wiki/Topics_GD/Strategy.md | 16 +- .../Stream-Processing-Architectures.md | 6 +- 10_Wiki/Topics_GD/Street Duel Fighter.md | 10 +- 10_Wiki/Topics_GD/Structural Principles.md | 12 +- .../Topics_GD/Structural-Equation-Modeling.md | 4 +- 10_Wiki/Topics_GD/Structuralism.md | 10 +- 10_Wiki/Topics_GD/Style Reference (--sref).md | 8 +- 10_Wiki/Topics_GD/Style-Transfer-in-AI.md | 6 +- 10_Wiki/Topics_GD/Style-Transfer.md | 12 +- 10_Wiki/Topics_GD/Superficiality-Metrics.md | 10 +- .../Topics_GD/Supervised Fine-Tuning (SFT).md | 11 - .../Supervised-Learning (지도 학습 기초).md | 4 +- .../Supervised-Learning-Foundations.md | 8 +- 10_Wiki/Topics_GD/Supervised-Learning.md | 14 +- 10_Wiki/Topics_GD/Supply-Chain.md | 12 +- 10_Wiki/Topics_GD/Support Insulated.md | 6 +- 10_Wiki/Topics_GD/Support-Vector-Machines.md | 4 +- 10_Wiki/Topics_GD/Support.md | 12 +- 10_Wiki/Topics_GD/Sustainability.md | 14 +- 10_Wiki/Topics_GD/Swarm Intelligence.md | 16 +- 10_Wiki/Topics_GD/Swarm-Intelligence.md | 12 +- .../Topics_GD/Symbolic-AI vs Connectionism.md | 6 +- 10_Wiki/Topics_GD/Symbols.md | 14 +- 10_Wiki/Topics_GD/Symmetric-Encryption.md | 4 +- 10_Wiki/Topics_GD/Symmetry-and-Invariance.md | 10 +- 10_Wiki/Topics_GD/Synergy.md | 14 +- 10_Wiki/Topics_GD/Synthesized Intelligence.md | 8 +- .../Topics_GD/Synthetic-Data-Generation.md | 6 +- 10_Wiki/Topics_GD/Synthetic-Data.md | 12 +- .../System Prompt (시스템 프롬프트).md | 10 +- .../Topics_GD/System-Architecture-Design.md | 6 +- .../Topics_GD/System-Design for AI Scale.md | 10 +- .../Topics_GD/System-Design-Interview-Prep.md | 6 +- 10_Wiki/Topics_GD/System-Dynamics-Modeling.md | 6 +- 10_Wiki/Topics_GD/System-Theory.md | 14 +- .../Topics_GD/System_Debugging_Protocol.md | 4 +- 10_Wiki/Topics_GD/Systems Thinking.md | 10 +- 10_Wiki/Topics_GD/Systems-Thinking.md | 16 +- .../Topics_GD/T-component (Tool Registry).md | 8 +- 10_Wiki/Topics_GD/TDD.md | 12 +- 10_Wiki/Topics_GD/TS-Declaration-Files.md | 14 +- .../Topics_GD/Tableau-Data-Visualization.md | 4 +- .../Topics_GD/Target-Function-Profiling.md | 12 +- 10_Wiki/Topics_GD/Task-Management.md | 10 +- 10_Wiki/Topics_GD/Technical-Architecture.md | 14 +- 10_Wiki/Topics_GD/Technical-Debt.md | 16 +- .../Topics_GD/Temporal-Difference-Learning.md | 4 +- 10_Wiki/Topics_GD/TensorFlow-Foundations.md | 4 +- ...rm-Frequency-Inverse-Document-Frequency.md | 6 +- 10_Wiki/Topics_GD/Terminology.md | 16 +- .../Terraform-Infrastructure-as-Code.md | 6 +- ...mpute Scaling (추론 시간 계산 스케일링).md | 10 +- 10_Wiki/Topics_GD/Testing.md | 12 +- .../Topics_GD/Tetris_Project_Retrospective.md | 2 +- 10_Wiki/Topics_GD/Text-Mining.md | 16 +- 10_Wiki/Topics_GD/Text-to-Speech-Synthesis.md | 6 +- .../The Evolution of Music Distribution.md | 10 +- 10_Wiki/Topics_GD/The Grammys.md | 11 - .../Topics_GD/Theoretical-Computer-Science.md | 8 +- .../Topics_GD/Theory of Constraints (TOC).md | 8 +- .../Topics_GD/Theory-of-Mind (ToM) in AI.md | 8 +- .../Agency and Player Autonomy.md | 6 +- .../Topics_GD/Theory_and_Principles/Index.md | 6 +- .../Post-Modernist Literature in Gaming.md | 6 +- .../Quantum-Game-Theory.md | 6 +- 10_Wiki/Topics_GD/Thought-Architecture.md | 18 +- .../Topics_GD/Threejs WebGL 렌더링 최적화.md | 22 +- 10_Wiki/Topics_GD/Threejs WebGPURenderer.md | 14 +- 10_Wiki/Topics_GD/Threejs 성능 최적화.md | 24 +- 10_Wiki/Topics_GD/Time-Series-Analysis.md | 12 +- 10_Wiki/Topics_GD/Time-Step-Logic-in-Games.md | 6 +- 10_Wiki/Topics_GD/Tokenization-Strategies.md | 4 +- 10_Wiki/Topics_GD/Tool-Usage-Optimization.md | 12 +- .../Topics_GD/Toxicity-and-Bias-Mitigation.md | 10 +- 10_Wiki/Topics_GD/Transfer Learning.md | 14 +- .../Transfer-Learning (전이 학습 기초).md | 8 +- 10_Wiki/Topics_GD/Transformer-Architecture.md | 8 +- 10_Wiki/Topics_GD/Transformers.md | 14 +- 10_Wiki/Topics_GD/Trustworthy-AI.md | 4 +- 10_Wiki/Topics_GD/Turing Test.md | 10 +- .../Topics_GD/Turing-Machine Foundations.md | 6 +- 10_Wiki/Topics_GD/Type 1 vs Type 2 Errors.md | 8 +- 10_Wiki/Topics_GD/UX-Design-Principles.md | 8 +- 10_Wiki/Topics_GD/UX_Scenarios/.gitkeep | 0 .../Command and Control (C2) Interface.md | 6 +- 10_Wiki/Topics_GD/UX_Scenarios/Index.md | 16 +- .../Skybound/01_Core_Engine/Index.md | 12 +- .../Skybound-Modular-Game-Architecture.md | 6 +- ...ate-Machine-and-Phase-Transition-Events.md | 6 +- .../Visual_Feedback_Signal_Pattern.md | 2 +- .../Skybound/02_Combat_AI/Index.md | 6 +- ...tage-Director-and-World-Tension-Scaling.md | 6 +- ...Staggered-Firing-Logic-and-Phase-Offset.md | 6 +- .../Boss-AI-Contextual-Decision-Engine.md | 6 +- .../Boss_Encounter_and_Timeline_Design.md | 2 +- .../Skybound/03_Boss_Systems/Index.md | 6 +- .../Campaign_and_Dual_Loop_System.md | 4 +- .../Combat_Timeline_Difficulty_Scaling.md | 2 +- .../Equipment_Crafting_and_Synthesis_Full.md | 2 +- .../InGame_Progression_System.md | 2 +- .../04_Mechanics_Progression/Index.md | 18 +- .../Meta_Economy_Growth_Loop.md | 2 +- ...-04-22_Engine_Logic_Optimization_Report.md | 2 +- .../2026-04-22_Engine_Stability_Audit.md | 4 +- .../Skybound/05_Project_Issues/Index.md | 14 +- .../Topics_GD/UX_Scenarios/Skybound/Index.md | 30 +- .../Skybound/Skybound-Knowledge-Hub.md | 46 +- .../Skybound_Asset_Generation_Roadmap.md | 4 +- .../Skybound/Skybound_Asset_Purity_Sync.md | 6 +- .../Skybound_Defensive_Architecture_Reboot.md | 6 +- .../Skybound_Enemy_Orientation_Fix.md | 4 +- .../Skybound_Firepower_Overclock_v1.5.md | 4 +- .../Skybound_Skill_Asset_Integration.md | 4 +- .../Skybound_Skill_Image_Integration.md | 6 +- ...ybound_Weapon_Behavior_Engine_Migration.md | 4 +- .../Game Design Theory.md | 10 +- .../Systemic Modeling & Fun/Index.md | 2 +- .../UX_Scenarios/실시간 번역 엔진 (RTE).md | 6 +- .../실시간 번역 엔진 (Real-Time Engine).md | 6 +- .../UX_Scenarios/실시간 엔진 (RTE).md | 6 +- .../Topics_GD/Uber-Base-Web-Design-System.md | 10 +- 10_Wiki/Topics_GD/Ultra-Efficiency.md | 8 +- .../Topics_GD/Uncertainty-Quantification.md | 4 +- .../Topics_GD/Unconscious Structuralism.md | 10 +- .../Understanding Complex Systems.md | 18 +- .../Topics_GD/Universal Basic Income (UBI).md | 6 +- .../Universal-Approximation-Theorem.md | 4 +- 10_Wiki/Topics_GD/Universal-Grammar.md | 10 +- ...nsupervised-Learning (비지도 학습 기초).md | 4 +- .../V-component (Evaluation Interface).md | 8 +- 10_Wiki/Topics_GD/V7 Draft Mode Workflow.md | 6 +- .../Variational Autoencoders (VAE).md | 10 +- .../Topics_GD/Variational-Autoencoders-VAE.md | 8 +- .../Topics_GD/Vector-Database Selection.md | 8 +- 10_Wiki/Topics_GD/Victimhood-Narratives.md | 10 +- .../Viral-Dynamics-and-Network-Effects.md | 12 +- .../Topics_GD/Visual-Effects-VFX-in-Games.md | 10 +- 10_Wiki/Topics_GD/Visual-Effects-VFX.md | 6 +- 10_Wiki/Topics_GD/Vocabulary-Expansion.md | 8 +- .../Topics_GD/Voice-Assistant-Architecture.md | 8 +- .../WARNO 그래픽 엔진 업그레이드 프로젝트.md | 4 +- 10_Wiki/Topics_GD/WARNO 데이터 기반 밸런싱.md | 4 +- 10_Wiki/Topics_GD/WARNO 데이터 기반 설계.md | 4 +- ...멀티플레이어 및 경쟁 플레이 밸런스 패치.md | 4 +- 10_Wiki/Topics_GD/WARNO 모딩(Modding).md | 4 +- 10_Wiki/Topics_GD/WARNO 모딩.md | 4 +- .../Topics_GD/WARNO 밸런싱 및 사단 시스템.md | 4 +- ...ARNO 사후 관리 (Post-Launch Management).md | 4 +- ...(Real-time Tactics) 및 Army General 캠페인.md | 4 +- .../Topics_GD/WARNO 전술 시뮬레이션 시스템.md | 4 +- .../WARNO 전투 메커니즘 (Combat Mechanics).md | 4 +- .../WARNO 커뮤니티 데이터 도구 생태계.md | 4 +- .../Topics_GD/WARNO 커뮤니티 모딩 생태계.md | 4 +- 10_Wiki/Topics_GD/WARNO-DATA Wiki.md | 4 +- 10_Wiki/Topics_GD/WARNO-DATA 프로젝트.md | 4 +- 10_Wiki/Topics_GD/WARNO.md | 4 +- 10_Wiki/Topics_GD/WME (Warno Mod Editor).md | 4 +- ...arno-Armory (커뮤니티 데이터 분석 도구).md | 4 +- .../Topics_GD/War-Yes 및 Warno-Armory 도구.md | 4 +- 10_Wiki/Topics_GD/Wargame 시리즈.md | 4 +- 10_Wiki/Topics_GD/Warno 데이터 기반 설계.md | 4 +- 10_Wiki/Topics_GD/Warno-Armory.md | 4 +- .../Topics_GD/Web Performance Optimization.md | 32 +- .../Web-Rendering-Strategies-CSR-vs-SSR.md | 10 +- 10_Wiki/Topics_GD/Web3-and-AI-Integration.md | 6 +- .../WebSplatter (3D Gaussian Splatting).md | 16 +- 10_Wiki/Topics_GD/What-is-AI.md | 12 +- 10_Wiki/Topics_GD/Wicked-Problems.md | 14 +- 10_Wiki/Topics_GD/Wonder.md | 6 +- 10_Wiki/Topics_GD/Word-Representation.md | 10 +- 10_Wiki/Topics_GD/Work-Displacement.md | 8 +- 10_Wiki/Topics_GD/Workflow-Integrity.md | 10 +- 10_Wiki/Topics_GD/Working-Backwards.md | 12 +- .../Zero Shot and Few Shot Learning.md | 12 +- .../Topics_GD/Zero-Shot-Chain-of-Thought.md | 8 +- 10_Wiki/Topics_GD/Zero-Shot-Learning.md | 6 +- ...리_ - 관심사의 분리 (Separation of Concerns).md | 6 +- .../agargaro의 오픈 소스 라이브러리.md | 10 +- 10_Wiki/Topics_GD/clinicjs.md | 10 +- .../Topics_GD/stochastic gradient descent.md | 8 +- ...상 경제 시스템(Virtual Economy System).md | 6 +- 10_Wiki/Topics_GD/가상 경제 시스템.md | 6 +- ... 경제 인플레이션(Game Economy Inflation).md | 6 +- .../Topics_GD/가상 경제(Virtual Economy).md | 6 +- 10_Wiki/Topics_GD/가용성 (Availability).md | 4 +- ...위보 상성 (Rock-paper-scissors principle).md | 4 +- 10_Wiki/Topics_GD/가중치 (Prompt Weights).md | 4 +- 10_Wiki/Topics_GD/가차(Gacha).md | 6 +- 10_Wiki/Topics_GD/가챠(Gacha) 시스템.md | 6 +- .../게임 경제 밸런스(Game Balance).md | 6 +- ... 경제 인플레이션(Game Economy Inflation).md | 6 +- .../경제 밸런싱(Economic Balancing).md | 6 +- .../공급망 공격 (Supply Chain Attack).md | 10 +- ... 동맹 전쟁(Sector Control and Alliance Wars).md | 6 +- .../네거티브 프롬프트 (Negative Prompts).md | 6 +- .../네거티브 프롬프트(Negative Prompt).md | 6 +- .../다중 게임 경제(Multi-Game Economies).md | 6 +- ...다중 통화 시스템(Multi-Currency System).md | 6 +- .../Topics_GD/다크 패턴 (Dark Patterns).md | 6 +- .../대규모 프론트엔드 애플리케이션.md | 16 +- ...화 전략 분석 및 가상 경제 시스템 검증 프로젝트.md | 6 +- 10_Wiki/Topics_GD/동맹(Alliances).md | 6 +- .../동적 가격 책정 (Dynamic Pricing).md | 6 +- .../Topics_GD/드래프트 모드 (Draft Mode).md | 6 +- .../디지털 트윈 및 데이터 시뮬레이션.md | 6 +- .../디퓨전 모델 (Diffusion Models).md | 6 +- .../Topics_GD/라이브 서비스 (Live Service).md | 6 +- 10_Wiki/Topics_GD/리믹스 모드 (Remix Mode).md | 6 +- ...비스 아키텍처 (Microservices Architecture).md | 12 +- .../마키네이션(Machinations.io) 시뮬레이션.md | 6 +- 10_Wiki/Topics_GD/매개변수(Parameters).md | 6 +- .../매몰 비용의 오류 (Sunk Cost Fallacy).md | 6 +- .../멀티 게임 경제(Multi-Game Economy).md | 6 +- ...딩 커뮤니티 도구 (War-Yes, Warno-Armory).md | 4 +- ... 게임(Mobile PvP Game) 환경에서의 경제 밸런싱.md | 6 +- 10_Wiki/Topics_GD/몬테카를로 시뮬레이션.md | 6 +- ... V7 드래프트 모드 및 옴니 참조 워크플로우.md | 6 +- ... V7 및 V8 알파 (Midjourney V7 & V8.1 Alpha).md | 6 +- .../미드저니 V7 및 V8.1 Alpha 워크플로우.md | 6 +- ...미드저니 V7 및 드래프트 모드 워크플로우.md | 6 +- ...프트 일관성 유지 (Midjourney V7 Consistency).md | 6 +- ...저니 및 스테이블 디퓨전의 부분 편집 기법.md | 6 +- .../Topics_GD/방어 태세(Defensive Stance).md | 6 +- .../방어 플랫폼(Defense Platforms).md | 6 +- 10_Wiki/Topics_GD/배수구(Sinks).md | 6 +- .../버전 및 모델 (Versions and Models).md | 6 +- .../벡터 데이터베이스 (Vector Database).md | 10 +- 10_Wiki/Topics_GD/병원 (Hospital).md | 6 +- 10_Wiki/Topics_GD/보상 시스템.md | 6 +- .../Topics_GD/보존 경로(Retaining Path).md | 14 +- .../보편적 언어 (Ubiquitous Language).md | 10 +- ... 방어 전략(Combined Arms Defensive Grid).md | 6 +- ...적 권력 피라미드 (Feudal Power Pyramid).md | 6 +- .../부대 편성(Platoon Formations).md | 6 +- ... 활용한 시각적 아티팩트(Artifact) 디버깅 및 제어.md | 6 +- ...리 누수 탐지(Browser Memory Leak Detection).md | 12 +- ... 도메인 모델링 (Business Domain Modeling).md | 18 +- .../빌보드 임포스터(Billboard Impostors).md | 6 +- .../사단 시스템 (Division System).md | 4 +- 10_Wiki/Topics_GD/사단 편제표 (TO&E).md | 4 +- 10_Wiki/Topics_GD/사단(Division) 시스템.md | 4 +- 10_Wiki/Topics_GD/사후 편집 (Post-editing).md | 6 +- ...Commercial Marketing Campaign and Product Mockup Creation).md | 6 +- ...업용 브랜드 이미지 및 디자인 시스템 구축.md | 6 +- .../상업용 제품 사진 및 브랜드 로고 디자인.md | 4 +- ...상태 관리 최적화 (Zustand Jotai Valtio).md | 18 +- .../상호작용적 프롬프트 엔지니어링.md | 6 +- .../Topics_GD/샘플링 스텝 (Sampling Steps).md | 6 +- ...로세스 (Iterative Workflow of Generative AI Imaging).md | 6 +- ...형 AI 워크플로우 (Generative AI Workflow).md | 6 +- ...플라이 체인 보안 (Supply Chain Security).md | 10 +- ...셜 미디어 그래픽 및 마케팅 캠페인 제작.md | 6 +- .../Topics_GD/소음 역학 (Noise Dynamics).md | 4 +- 10_Wiki/Topics_GD/소프트 싱크(Soft Sinks).md | 6 +- .../소프트웨어 개발 수명 주기 (SDLC).md | 14 +- 10_Wiki/Topics_GD/수도꼭지(Faucets).md | 6 +- ...릭터 참조 (Style and Character References).md | 6 +- .../스타일 및 캐릭터 참조(References).md | 6 +- ... 캐릭터 참조(Style and Character Reference).md | 6 +- .../스타일 참조(Style Reference, --sref).md | 6 +- 10_Wiki/Topics_GD/스타일 코드.md | 6 +- ...테이블 디퓨전 CFG Scale 및 가중치 제어.md | 6 +- ...스테이블 디퓨전의 가중치 및 제어 시스템.md | 6 +- .../시간 제한 메커니즘 (Time-gating).md | 6 +- ...간 제한 활성화 (Time-limited Activation).md | 6 +- ...샷 워크플로우 (Series and Multi-shot Workflow).md | 6 +- 10_Wiki/Topics_GD/시뮬레이션(Simulation).md | 6 +- .../Topics_GD/시뮬레이터 멀미 설문지(SSQ).md | 8 +- ...미 설문지(Simulator Sickness Questionnaire).md | 8 +- .../실시간 엔진 (Real-Time Engine).md | 6 +- ... 척도 연구(In-Game Purchase Motivation Scale Study).md | 6 +- ...지 최적화 (Stable Diffusion Image Optimization).md | 6 +- ...비온 온라인(Albion Online)의 경제 시스템.md | 6 +- 10_Wiki/Topics_GD/애그리거트 (Aggregates).md | 12 +- 10_Wiki/Topics_GD/얼라이언스 (Alliance).md | 6 +- 10_Wiki/Topics_GD/에이전틱 AI (Agentic AI).md | 6 +- .../Topics_GD/영구 손실 (Permanent loss).md | 6 +- .../Topics_GD/영구적 손실 (Permanent Loss).md | 6 +- ...5 호쿠사이 인스톨레이션(Hokusai installation).md | 10 +- ...미지 생성 및 하드웨어 수준의 정밀 통제 워크플로우.md | 6 +- ...스 기반 맞춤형 이미지 생성 워크플로우 구축.md | 6 +- .../오픈소스 이미지 모델 미세 조정 및 배포.md | 6 +- .../Topics_GD/왕국 대 왕국 (KvK) 이벤트.md | 6 +- .../원신(Genshin Impact)의 레진 시스템.md | 6 +- ...중 게임 경제(Web3 & Multi-Game Economies).md | 6 +- .../유비쿼터스 언어 (Ubiquitous Language).md | 12 +- ...신과 시야 매커니즘 (Stealth and Optics).md | 4 +- ... 및 토륨 경제(Iridium and Thorium Economy).md | 6 +- .../인-이미지 텍스트(In-Image Text).md | 6 +- .../Topics_GD/인문학적 게임 비평 및 서사학.md | 6 +- 10_Wiki/Topics_GD/인지 행동 치료 (CBT).md | 10 +- 10_Wiki/Topics_GD/인페인팅 (Inpainting).md | 6 +- ...및 드래프트 모드(Inpainting and Draft Mode).md | 6 +- ...연어 프롬프트(Natural Language Prompt).md | 6 +- 10_Wiki/Topics_GD/자원 소모처(Sinks).md | 6 +- ... 관통 모델링(Armor Penetration Modeling).md | 4 +- ... 및 사거리 데이터 (Armor and Range Stats).md | 4 +- ...상거래 소비자 참여 및 보상 시스템 최적화.md | 6 +- .../정적 애플리케이션 보안 테스트 (SAST).md | 18 +- .../정적 애플리케이션 보안 테스트(SAST).md | 14 +- 10_Wiki/Topics_GD/제로잉 (Getting Zero-ed).md | 6 +- 10_Wiki/Topics_GD/제로잉 (Zeroing).md | 6 +- 10_Wiki/Topics_GD/제병협동 (Combined Arms).md | 4 +- .../제병협동 전술 (Combined Arms).md | 4 +- ... 사양 지시(Lighting and Camera Specification).md | 6 +- .../초상화 및 애니메이션 스타일 제어.md | 6 +- 10_Wiki/Topics_GD/카산드라(Cassandra).md | 6 +- .../캐릭터 참조 (Character Reference).md | 6 +- 10_Wiki/Topics_GD/컨트롤넷 (ControlNet).md | 6 +- 10_Wiki/Topics_GD/컨트롤넷(ControlNet).md | 6 +- 10_Wiki/Topics_GD/코드 리뷰(Code Review).md | 14 +- ... 알고리즘 (Ballistics and Accuracy Algorithms).md | 4 +- .../Topics_GD/탭과 싱크(Taps and Sinks).md | 6 +- .../텍스트 렌더링(Text Rendering).md | 6 +- .../Topics_GD/토륨 경제(Thorium Economy).md | 6 +- .../파라미터 튜닝 (Parameter Tuning).md | 4 +- 10_Wiki/Topics_GD/파워 크립 (Power Creep).md | 6 +- 10_Wiki/Topics_GD/풀 리퀘스트 워크플로우.md | 14 +- .../풀 리퀘스트(PR) 기반 보안 검토.md | 14 +- .../프론트엔드 및 Nodejs 개발 워크플로우.md | 20 +- ...론트엔드 애플리케이션 렌더링 병목 개선.md | 16 +- .../프롬프트 가중치 (Prompt Weighting).md | 6 +- .../프롬프트 가중치(Prompt Weighting).md | 6 +- .../프롬프트 구문 (Prompt Syntax).md | 6 +- .../프롬프트 구조 (Prompt Structure).md | 6 +- 10_Wiki/Topics_GD/프롬프트 구조 및 문법.md | 6 +- 10_Wiki/Topics_GD/프롬프트 엔지니어링.md | 6 +- .../Topics_GD/프롬프트 엔지니어링의 진화.md | 6 +- .../프롬프트 정밀도 (Prompt Precision).md | 6 +- ... 파라미터 제어 (Prompt Parameter Control).md | 6 +- .../프롬프트 확장(Prompt Expansion).md | 6 +- .../플랫폼 저항성(Platform Resistance).md | 14 +- .../플랫폼 저항성(Platform Resistances).md | 14 +- 10_Wiki/Topics_GD/플레이어 기반 경제.md | 6 +- ...이브리드 코드 리뷰 (Hybrid Code Review).md | 14 +- 10_Wiki/Topics_GD/하이브리드 코드 리뷰.md | 12 +- .../할당 실패(Allocation Failure).md | 10 +- .../Topics_GD/함수 호출 (Function Calling).md | 10 +- .../해부학적 오류 디버깅 워크플로우.md | 6 +- 10_Wiki/Topics_GD/핵심 루프(Core Loop).md | 6 +- 10_Wiki/Topics_GD/행동경제학.md | 6 +- .../혼합 소대 전술(Mixed Platoon Tactics).md | 6 +- .../Topics_GD/혼합 소대(Mixed Platoons).md | 6 +- .../Topics_GD/확산 모델 (Diffusion Model).md | 6 +- .../Topics_GD/확산 모델 (Diffusion Models).md | 6 +- ...어 생성 패러다임 전환 및 연속적 창작 워크플로우.md | 6 +- ... 워크플로우 (AI Image Generation Workflow).md | 6 +- .../API-backed Image Generation Workflow.md | 6 +- .../Topics_meeting/Agentic Creative Era.md | 6 +- 10_Wiki/Topics_meeting/Agentic Governance.md | 8 +- .../Topics_meeting/Agentic Orchestration.md | 12 +- 10_Wiki/Topics_meeting/Agile-Philosophy.md | 4 +- .../Topics_meeting/Agile-UX-Integration.md | 2 +- 10_Wiki/Topics_meeting/Autonomous Logging.md | 8 +- .../Brand Consistency Maintenance.md | 6 +- 10_Wiki/Topics_meeting/ControlNet.md | 6 +- .../DALL-E 3의 자연어 기반 최적화.md | 6 +- .../Distributed Systems & Reliability.md | 8 +- .../Himart_UIUX_Direction_20260428.md | 16 +- .../Himart_Webstore_Meeting_20260429.md | 20 +- .../Human-in-the-Loop (HITL).md | 8 +- .../Image Inpainting (Vary Region).md | 6 +- 10_Wiki/Topics_meeting/Image Parameters.md | 6 +- 10_Wiki/Topics_meeting/Index.md | 4 +- .../Inpainting & Outpainting.md | 6 +- 10_Wiki/Topics_meeting/Iterative Prompting.md | 6 +- .../Lighting and Composition.md | 6 +- .../Topics_meeting/Midjourney Parameter.md | 6 +- .../Topics_meeting/Midjourney Parameters.md | 6 +- ... V6 및 V7 기반의 이미지 생성 워크플로우.md | 6 +- .../Midjourney V7 Draft Mode.md | 6 +- .../Midjourney V7 및 V6 워크플로우.md | 6 +- .../Midjourney V7의 Draft Mode 워크플로우.md | 6 +- ...djourney 브랜드 캠페인 및 무드보드 제작.md | 6 +- 10_Wiki/Topics_meeting/Moodboard Creation.md | 6 +- .../Ontology-Driven-Relevancy-Filtering.md | 2 +- .../Topics_meeting/Ontology-Engineering.md | 4 +- .../Ontology-Guided Knowledge Extraction.md | 4 +- 10_Wiki/Topics_meeting/Ontology.md | 4 +- 10_Wiki/Topics_meeting/Parameter Control.md | 6 +- 10_Wiki/Topics_meeting/Positive Prompts.md | 6 +- .../Project Awakening(CCP Games).md | 6 +- 10_Wiki/Topics_meeting/Prompt Structure.md | 6 +- .../Topics_meeting/Reasoning & Planning.md | 12 +- 10_Wiki/Topics_meeting/Scheduler API.md | 6 +- .../Topics_meeting/Scheduler-Design-in-ML.md | 2 +- 10_Wiki/Topics_meeting/Self-verification.md | 8 +- .../Topics_meeting/Semantics & Ontology.md | 4 +- 10_Wiki/Topics_meeting/Session Lifecycle.md | 8 +- .../Topics_meeting/Signature Style Design.md | 6 +- .../Stable Diffusion Image Optimization.md | 6 +- .../Stable Diffusion 오픈소스 제어.md | 6 +- .../Stable Diffusion의 가중치 제어 문법.md | 6 +- .../Style Reference (--sref).md | 8 +- 10_Wiki/Topics_meeting/Task-Management.md | 4 +- .../Topics_meeting/V7 Draft Mode Workflow.md | 6 +- .../Topics_meeting/Vary Region (인페인팅).md | 6 +- .../게임 데이터 분석(Game Analytics).md | 6 +- .../네거티브 프롬프트 (Negative Prompts).md | 6 +- ...화 전략 분석 및 가상 경제 시스템 검증 프로젝트.md | 6 +- .../드래프트 모드 (Draft Mode).md | 6 +- .../리믹스 모드 (Remix Mode).md | 6 +- .../Topics_meeting/매개변수(Parameters).md | 6 +- ... V7 드래프트 모드 및 옴니 참조 워크플로우.md | 6 +- ... V7 및 V8 알파 (Midjourney V7 & V8.1 Alpha).md | 6 +- .../미드저니 V7 및 V8.1 Alpha 워크플로우.md | 6 +- ...미드저니 V7 및 드래프트 모드 워크플로우.md | 6 +- ...프트 일관성 유지 (Midjourney V7 Consistency).md | 6 +- ...저니 및 스테이블 디퓨전의 부분 편집 기법.md | 6 +- .../미드저니(Midjourney) 에디터 기능.md | 6 +- .../버전 및 모델 (Versions and Models).md | 6 +- ... 활용한 시각적 아티팩트(Artifact) 디버깅 및 제어.md | 6 +- .../상호작용적 프롬프트 엔지니어링.md | 6 +- ...로세스 (Iterative Workflow of Generative AI Imaging).md | 6 +- ...형 AI 워크플로우 (Generative AI Workflow).md | 6 +- ... 캐릭터 참조(Style and Character Reference).md | 6 +- 10_Wiki/Topics_meeting/스타일 코드.md | 6 +- ...테이블 디퓨전 CFG Scale 및 가중치 제어.md | 6 +- ...스테이블 디퓨전의 가중치 및 제어 시스템.md | 6 +- ...샷 워크플로우 (Series and Multi-shot Workflow).md | 6 +- ... 척도 연구(In-Game Purchase Motivation Scale Study).md | 6 +- ...지 최적화 (Stable Diffusion Image Optimization).md | 6 +- .../에이전틱 AI (Agentic AI).md | 6 +- ...미지 생성 및 하드웨어 수준의 정밀 통제 워크플로우.md | 6 +- ...스 기반 맞춤형 이미지 생성 워크플로우 구축.md | 6 +- .../오픈소스 이미지 모델 미세 조정 및 배포.md | 6 +- .../옴니 참조(Omni Reference, --oref).md | 6 +- .../인-이미지 텍스트(In-Image Text).md | 6 +- .../Topics_meeting/인페인팅 (Inpainting).md | 6 +- ...및 드래프트 모드(Inpainting and Draft Mode).md | 6 +- ...연어 프롬프트(Natural Language Prompt).md | 6 +- ...상거래 소비자 참여 및 보상 시스템 최적화.md | 6 +- ... 사양 지시(Lighting and Camera Specification).md | 6 +- .../캐릭터 참조 (Character Reference).md | 6 +- .../파라미터 튜닝 (Parameter Tuning).md | 4 +- .../프롬프트 가중치 (Prompt Weighting).md | 6 +- .../프롬프트 구조 (Prompt Structure).md | 6 +- .../Topics_meeting/프롬프트 구조 및 문법.md | 6 +- 10_Wiki/Topics_meeting/프롬프트 엔지니어링.md | 6 +- .../프롬프트 엔지니어링의 진화.md | 6 +- .../프롬프트 정밀도 (Prompt Precision).md | 6 +- ... 파라미터 제어 (Prompt Parameter Control).md | 6 +- .../해부학적 오류 디버깅 워크플로우.md | 6 +- 20_Meta/Index.md | 24 +- 20_Meta/Policy.md | 3 - ...1 - 시스템 안정화 및 전술적 경계 고도화.md | 2 +- 13150 files changed, 55394 insertions(+), 100862 deletions(-) delete mode 100644 00_Raw/.gitkeep delete mode 100644 01_Archive/.gitkeep delete mode 100644 01_Archive/2026-04-20/.gitkeep delete mode 100644 01_Archive/2026-04-20/01_WebWorker-performance-optimization.md delete mode 100644 01_Archive/2026-04-20/02_StateManagement-single-source-of-truth.md delete mode 100644 01_Archive/2026-04-20/03_Architecture-design-principle.md delete mode 100644 01_Archive/2026-04-20/04_execution-environment-management.md delete mode 100644 01_Archive/2026-04-20/05_simulation-design-principles.md delete mode 100644 01_Archive/2026-04-20/AI.md delete mode 100644 01_Archive/2026-04-20/Agile-Software-Development-Life-Cycle.md delete mode 100644 01_Archive/2026-04-20/Code Splitting & Lazy Loading.md delete mode 100644 01_Archive/2026-04-20/Policy.md delete mode 100644 01_Archive/2026-04-20/[[Cluster A delete mode 100644 01_Archive/2026-04-20/[[Cluster E delete mode 100644 01_Archive/2026-04-20/환영합니다!.md delete mode 100644 01_Archive/Old_2nd_Structure/2026-04-20.md delete mode 100644 01_Archive/Old_2nd_Structure/환영합니다!.md delete mode 100644 10_Wiki/Skills/knowledge_inventory_1535.json delete mode 100644 10_Wiki/Topics/10v10 대규모 멀티플레이어.md delete mode 100644 10_Wiki/Topics/2026-05-02.md delete mode 100644 10_Wiki/Topics/20k skinned instances demo.md delete mode 100644 10_Wiki/Topics/A-B-Testing-and-Data-Driven-UX.md delete mode 100644 10_Wiki/Topics/ABA.md delete mode 100644 10_Wiki/Topics/ADA-Website-Compliance.md delete mode 100644 10_Wiki/Topics/AGI.md delete mode 100644 10_Wiki/Topics/AI & Data Sovereignty.md delete mode 100644 10_Wiki/Topics/AI Accountability.md delete mode 100644 10_Wiki/Topics/AI Connect LLM Tool.md delete mode 100644 10_Wiki/Topics/AI Governance.md delete mode 100644 10_Wiki/Topics/AI Humanism.md delete mode 100644 10_Wiki/Topics/AI Literacy.md delete mode 100644 10_Wiki/Topics/AI and Narrative.md delete mode 100644 10_Wiki/Topics/AI for Social Good.md delete mode 100644 10_Wiki/Topics/AI 거버넌스 정책(AI Usage Policy).md delete mode 100644 10_Wiki/Topics/AI 코드 리뷰 및 보안 취약점 점검(DevSecOps).md delete mode 100644 10_Wiki/Topics/AI 코드 리뷰.md delete mode 100644 10_Wiki/Topics/AI-Alignment.md delete mode 100644 10_Wiki/Topics/AI-Answer-Engine-Optimization.md delete mode 100644 10_Wiki/Topics/AI-Overviews-and-SGE.md delete mode 100644 10_Wiki/Topics/AI-Personalization-and-Adaptive-UX.md delete mode 100644 10_Wiki/Topics/AI-Search-Optimization.md delete mode 100644 10_Wiki/Topics/AI/Reward Prediciton Error.md delete mode 100644 10_Wiki/Topics/AI/Reward Prediction Error (상태 예측 오류).md delete mode 100644 10_Wiki/Topics/AI/SAST (Static Application Security Testing).md delete mode 100644 10_Wiki/Topics/AI/SAST (정적 애플리케이션 보안 테스트).md delete mode 100644 10_Wiki/Topics/AI/SAST (정적 애플리케이션 보안 테스팅).md delete mode 100644 10_Wiki/Topics/AI/Self-Correction Mechanisms.md delete mode 100644 10_Wiki/Topics/AI/Self-Correction.md delete mode 100644 10_Wiki/Topics/AI/Stability.md delete mode 100644 10_Wiki/Topics/AI/Static Application Security Testing (SAST).md delete mode 100644 10_Wiki/Topics/AI/Supervised Fine-Tuning (SFT).md delete mode 100644 10_Wiki/Topics/AI/The Grammys.md delete mode 100644 10_Wiki/Topics/AI/소프트웨어 개발 수명 주기 (SDLC).md delete mode 100644 10_Wiki/Topics/AI와 기계에게 검열 맡기기_ - 정적 분석 툴 (ESLint Prettier)).md delete mode 100644 10_Wiki/Topics/API 응답 모델링 및 상태 머신(State Machine) 설계.md delete mode 100644 10_Wiki/Topics/API-Design for AI Services.md delete mode 100644 10_Wiki/Topics/API-Key-Management.md delete mode 100644 10_Wiki/Topics/API_Communication_Patterns.md delete mode 100644 10_Wiki/Topics/A_B-Testing-Platforms.md delete mode 100644 10_Wiki/Topics/Abundance.md delete mode 100644 10_Wiki/Topics/Academic-Integrity.md delete mode 100644 10_Wiki/Topics/Accessibility-Compliance-Audit.md delete mode 100644 10_Wiki/Topics/Accessibility_Inclusivity.md delete mode 100644 10_Wiki/Topics/Active Learning.md delete mode 100644 10_Wiki/Topics/Active-Reasoning.md delete mode 100644 10_Wiki/Topics/Activism.md delete mode 100644 10_Wiki/Topics/Actor-Critic-Models.md delete mode 100644 10_Wiki/Topics/Ad-hoc-Hypotheses.md delete mode 100644 10_Wiki/Topics/Ad-hoc-Optimization.md delete mode 100644 10_Wiki/Topics/Adaptability.md delete mode 100644 10_Wiki/Topics/Adaptive Compute (적응형 계산량 조절).md delete mode 100644 10_Wiki/Topics/Adaptive-Curation.md delete mode 100644 10_Wiki/Topics/Advanced-Interface-Design.md delete mode 100644 10_Wiki/Topics/Adversarial Code Stylometry.md delete mode 100644 10_Wiki/Topics/Aesthetic-Value.md delete mode 100644 10_Wiki/Topics/Affordance.md delete mode 100644 10_Wiki/Topics/Agent Architecture.md delete mode 100644 10_Wiki/Topics/Agent Personality.md delete mode 100644 10_Wiki/Topics/Agentic Coding.md delete mode 100644 10_Wiki/Topics/Agile-Philosophy.md delete mode 100644 10_Wiki/Topics/Alcoholism.md delete mode 100644 10_Wiki/Topics/Algorithm-Complexity-Big-O.md delete mode 100644 10_Wiki/Topics/Algorithmic Fairness.md delete mode 100644 10_Wiki/Topics/Algorithmic Transparency.md delete mode 100644 10_Wiki/Topics/Algorithmic-Biology.md delete mode 100644 10_Wiki/Topics/Algorithmic-Game-Theory.md delete mode 100644 10_Wiki/Topics/Alignment.md delete mode 100644 10_Wiki/Topics/AlphaZero Strategy.md delete mode 100644 10_Wiki/Topics/Alternative Realities.md delete mode 100644 10_Wiki/Topics/Altruism.md delete mode 100644 10_Wiki/Topics/Ambient-Declarations.md delete mode 100644 10_Wiki/Topics/Ambition.md delete mode 100644 10_Wiki/Topics/Amdahls Law (암달의 법칙).md delete mode 100644 10_Wiki/Topics/Analogical-Reasoning.md delete mode 100644 10_Wiki/Topics/Analogy.md delete mode 100644 10_Wiki/Topics/Analysis.md delete mode 100644 10_Wiki/Topics/Anarchism.md delete mode 100644 10_Wiki/Topics/Anarcho-Capitalism.md delete mode 100644 10_Wiki/Topics/Anarcho-Primitivism.md delete mode 100644 10_Wiki/Topics/Anisomorphism.md delete mode 100644 10_Wiki/Topics/Anomaly-Detection.md delete mode 100644 10_Wiki/Topics/Anthropic-Principle.md delete mode 100644 10_Wiki/Topics/Anthropomorphism.md delete mode 100644 10_Wiki/Topics/Anticipation.md delete mode 100644 10_Wiki/Topics/Antifragility.md delete mode 100644 10_Wiki/Topics/Antinomianism.md delete mode 100644 10_Wiki/Topics/Anxiety.md delete mode 100644 10_Wiki/Topics/Arguing-by-Counterexample.md delete mode 100644 10_Wiki/Topics/Arrangement-and-Composition.md delete mode 100644 10_Wiki/Topics/Articulateness.md delete mode 100644 10_Wiki/Topics/Artificial General Intelligence (AGI).md delete mode 100644 10_Wiki/Topics/Artificial Intelligence (AI).md delete mode 100644 10_Wiki/Topics/Artificial-Intelligence-in-Games.md delete mode 100644 10_Wiki/Topics/Artificial-Intelligence.md delete mode 100644 10_Wiki/Topics/Artificial-Life.md delete mode 100644 10_Wiki/Topics/Arts.md delete mode 100644 10_Wiki/Topics/Assertiveness.md delete mode 100644 10_Wiki/Topics/Assessment.md delete mode 100644 10_Wiki/Topics/Asset-Specific-Knowledge.md delete mode 100644 10_Wiki/Topics/Assumptions-vs-Facts.md delete mode 100644 10_Wiki/Topics/Atheism.md delete mode 100644 10_Wiki/Topics/Atlantic.md delete mode 100644 10_Wiki/Topics/Atmospheric-Intelligence.md delete mode 100644 10_Wiki/Topics/Atomic-Design-System-Architecture.md delete mode 100644 10_Wiki/Topics/Atomic-Styling-and-Design-Systems.md delete mode 100644 10_Wiki/Topics/Atomism.md delete mode 100644 10_Wiki/Topics/Attention Mechanisms.md delete mode 100644 10_Wiki/Topics/Attention is All You Need.md delete mode 100644 10_Wiki/Topics/Authenticity.md delete mode 100644 10_Wiki/Topics/Autism Spectrum Disorder (ASD) Intervention.md delete mode 100644 10_Wiki/Topics/Auto-Encoding.md delete mode 100644 10_Wiki/Topics/Auto-GPT and Autonomous Agents.md delete mode 100644 10_Wiki/Topics/Autobiography.md delete mode 100644 10_Wiki/Topics/Autoethnography.md delete mode 100644 10_Wiki/Topics/Automated-Decision-Making.md delete mode 100644 10_Wiki/Topics/Automated-Game-Testing.md delete mode 100644 10_Wiki/Topics/Automated-Map-Generation.md delete mode 100644 10_Wiki/Topics/Automated-Reasoning.md delete mode 100644 10_Wiki/Topics/Automated-Refactoring-Tools.md delete mode 100644 10_Wiki/Topics/Automated-Security-Audits.md delete mode 100644 10_Wiki/Topics/Automated-Theorem-Proving.md delete mode 100644 10_Wiki/Topics/Automated_Mapping.md delete mode 100644 10_Wiki/Topics/Automation-Paradox.md delete mode 100644 10_Wiki/Topics/Autonomous Vehicles.md delete mode 100644 10_Wiki/Topics/Autonomous-Agents.md delete mode 100644 10_Wiki/Topics/Autonomous-Polling-Wait-Automation.md delete mode 100644 10_Wiki/Topics/Autonomous-Vehicle-Path-Planning.md delete mode 100644 10_Wiki/Topics/Availability-and-Persistence.md delete mode 100644 10_Wiki/Topics/Awards.md delete mode 100644 10_Wiki/Topics/Axify.md delete mode 100644 10_Wiki/Topics/Axiology.md delete mode 100644 10_Wiki/Topics/Axiomatic-Systems.md delete mode 100644 10_Wiki/Topics/Axioms.md delete mode 100644 10_Wiki/Topics/Azure DevOps.md delete mode 100644 10_Wiki/Topics/B-Tree.md delete mode 100644 10_Wiki/Topics/BFS vs DFS.md delete mode 100644 10_Wiki/Topics/Backend.md delete mode 100644 10_Wiki/Topics/Backpropagation Through Time.md delete mode 100644 10_Wiki/Topics/Backpropagation.md delete mode 100644 10_Wiki/Topics/Backups.md delete mode 100644 10_Wiki/Topics/Backward-Reasoning.md delete mode 100644 10_Wiki/Topics/Bag of Words (BoW).md delete mode 100644 10_Wiki/Topics/Baseline Project.md delete mode 100644 10_Wiki/Topics/Batch-Inference.md delete mode 100644 10_Wiki/Topics/Bayesian-Brain-Hypothesis.md delete mode 100644 10_Wiki/Topics/Be-Detailed.md delete mode 100644 10_Wiki/Topics/Beckett.md delete mode 100644 10_Wiki/Topics/Behavior.md delete mode 100644 10_Wiki/Topics/Behavioral Finance.md delete mode 100644 10_Wiki/Topics/Behavioral-Economics.md delete mode 100644 10_Wiki/Topics/Behavioral-Incentives.md delete mode 100644 10_Wiki/Topics/Belief-Revision.md delete mode 100644 10_Wiki/Topics/Belief-System.md delete mode 100644 10_Wiki/Topics/Beliefs.md delete mode 100644 10_Wiki/Topics/Bellman Equation.md delete mode 100644 10_Wiki/Topics/Bellman-Equation.md delete mode 100644 10_Wiki/Topics/Benchmarks.md delete mode 100644 10_Wiki/Topics/Best SAST Tools in 2026.md delete mode 100644 10_Wiki/Topics/Best-of-N Sampling ( ø).md delete mode 100644 10_Wiki/Topics/Best-of-N Sampling (최적 샘플링).md delete mode 100644 10_Wiki/Topics/Best-of-N Sampling.md delete mode 100644 10_Wiki/Topics/Best-of-N-Sampling.md delete mode 100644 10_Wiki/Topics/Bias vs Variance.md delete mode 100644 10_Wiki/Topics/Bias-Correction-Algorithm.md delete mode 100644 10_Wiki/Topics/Bias-Variance-Tradeoff.md delete mode 100644 10_Wiki/Topics/Bible.md delete mode 100644 10_Wiki/Topics/Bibliometrics.md delete mode 100644 10_Wiki/Topics/Big-Data.md delete mode 100644 10_Wiki/Topics/Big-Picture.md delete mode 100644 10_Wiki/Topics/Binary-Author-Identification.md delete mode 100644 10_Wiki/Topics/Binary-Search.md delete mode 100644 10_Wiki/Topics/BioShock (2007).md delete mode 100644 10_Wiki/Topics/BioShock-Critique.md delete mode 100644 10_Wiki/Topics/Bioenergetics.md delete mode 100644 10_Wiki/Topics/Bioinformatics-Structure-Prediction.md delete mode 100644 10_Wiki/Topics/Biological-Inspired-Algorithms.md delete mode 100644 10_Wiki/Topics/Biological-Intelligence.md delete mode 100644 10_Wiki/Topics/Biomechanics-of-Injury.md delete mode 100644 10_Wiki/Topics/Biometrics.md delete mode 100644 10_Wiki/Topics/Black-Box-Optimization.md delete mode 100644 10_Wiki/Topics/Black-Hole.md delete mode 100644 10_Wiki/Topics/Black-Swan.md delete mode 100644 10_Wiki/Topics/Blockchain.md delete mode 100644 10_Wiki/Topics/Blocking.md delete mode 100644 10_Wiki/Topics/Blog-Post.md delete mode 100644 10_Wiki/Topics/Bloom-Filters in Search.md delete mode 100644 10_Wiki/Topics/Bloom-Filters.md delete mode 100644 10_Wiki/Topics/Boltzmann-Machines.md delete mode 100644 10_Wiki/Topics/Boosting-Algorithms-XGBoost-LightGBM.md delete mode 100644 10_Wiki/Topics/Bottlenecks.md delete mode 100644 10_Wiki/Topics/Bottom-Up-Approach.md delete mode 100644 10_Wiki/Topics/Boundaries.md delete mode 100644 10_Wiki/Topics/Boundary-Setting.md delete mode 100644 10_Wiki/Topics/Bounded Contexts.md delete mode 100644 10_Wiki/Topics/Bounded Rationality.md delete mode 100644 10_Wiki/Topics/Bounded-Contexts-and-Interface-Segregation.md delete mode 100644 10_Wiki/Topics/Bounded-Rationality.md delete mode 100644 10_Wiki/Topics/Bounding-Box-Regression.md delete mode 100644 10_Wiki/Topics/Bourgeoisie.md delete mode 100644 10_Wiki/Topics/Brain-Computer Interface (BCI).md delete mode 100644 10_Wiki/Topics/Brain-Computer-Interface (BCI).md delete mode 100644 10_Wiki/Topics/Brain-Derived Neurotrophic Factor (BDNF).md delete mode 100644 10_Wiki/Topics/Branded-Types-for-Nominal-Typing.md delete mode 100644 10_Wiki/Topics/Branded-Types.md delete mode 100644 10_Wiki/Topics/Branding.md delete mode 100644 10_Wiki/Topics/Browser.md delete mode 100644 10_Wiki/Topics/Brute-force.md delete mode 100644 10_Wiki/Topics/Bubble-Sort.md delete mode 100644 10_Wiki/Topics/Budget.md delete mode 100644 10_Wiki/Topics/Bureaucracy.md delete mode 100644 10_Wiki/Topics/Burnout Prevention in Professional Gaming.md delete mode 100644 10_Wiki/Topics/Burnout.md delete mode 100644 10_Wiki/Topics/Business Intelligence (BI).md delete mode 100644 10_Wiki/Topics/CAP-Theorem.md delete mode 100644 10_Wiki/Topics/CLIP.md delete mode 100644 10_Wiki/Topics/CPTED.md delete mode 100644 10_Wiki/Topics/CV_Synthesis.md delete mode 100644 10_Wiki/Topics/Call Stack.md delete mode 100644 10_Wiki/Topics/Case-Study-Allbirds-PWA-Redesign.md delete mode 100644 10_Wiki/Topics/Case-Study-Kiwi-com-Frontend-Migration.md delete mode 100644 10_Wiki/Topics/Case-Study-Skybound-Asset-Cache-Busting.md delete mode 100644 10_Wiki/Topics/Case-Study-Skybound-Red-Striker-Jitter-Stabilization.md delete mode 100644 10_Wiki/Topics/Catastrophic-Forgetting.md delete mode 100644 10_Wiki/Topics/Causal-Inference.md delete mode 100644 10_Wiki/Topics/Central-Pattern-Generators.md delete mode 100644 10_Wiki/Topics/CesiumJS.md delete mode 100644 10_Wiki/Topics/Chain-of-Thought (CoT 罽).md delete mode 100644 10_Wiki/Topics/Chain-of-Thought (CoT 사고 사슬).md delete mode 100644 10_Wiki/Topics/Chaos-Theory in Systems.md delete mode 100644 10_Wiki/Topics/Chrome-Rendering-Performance.md delete mode 100644 10_Wiki/Topics/Chronic-Pain-Management-Protocols.md delete mode 100644 10_Wiki/Topics/Circuit Discovery (회로 발견).md delete mode 100644 10_Wiki/Topics/Circuit Discovery.md delete mode 100644 10_Wiki/Topics/Circular-Economy-Transitions.md delete mode 100644 10_Wiki/Topics/Circular-Economy.md delete mode 100644 10_Wiki/Topics/Clean-Architecture-Implementation.md delete mode 100644 10_Wiki/Topics/Clean-Architecture-TypeScript.md delete mode 100644 10_Wiki/Topics/Clean-Code-Principles.md delete mode 100644 10_Wiki/Topics/Climate Change Mitigation Frameworks.md delete mode 100644 10_Wiki/Topics/Clinical-Kinesiology-Assessment.md delete mode 100644 10_Wiki/Topics/Code Review.md delete mode 100644 10_Wiki/Topics/Code-Splitting-and-Frontend-Performance-Optimization.md delete mode 100644 10_Wiki/Topics/Cognitive Biases.md delete mode 100644 10_Wiki/Topics/Cognitive Computing.md delete mode 100644 10_Wiki/Topics/Cognitive Neuroscience of Flow.md delete mode 100644 10_Wiki/Topics/Cognitive Psychology.md delete mode 100644 10_Wiki/Topics/Cognitive Reserve Theory.md delete mode 100644 10_Wiki/Topics/Cognitive Training Software (eg Aim Lab_KovaaKs).md delete mode 100644 10_Wiki/Topics/Cognitive-Architecture.md delete mode 100644 10_Wiki/Topics/Cognitive-Evaluation-Theory.md delete mode 100644 10_Wiki/Topics/Cognitive-Therapy-in-CBT.md delete mode 100644 10_Wiki/Topics/Collaboration_Governance.md delete mode 100644 10_Wiki/Topics/Collaborative-Filtering.md delete mode 100644 10_Wiki/Topics/Collective-Intelligence.md delete mode 100644 10_Wiki/Topics/Combinatorial Game Theory.md delete mode 100644 10_Wiki/Topics/Combinatorial-Optimization.md delete mode 100644 10_Wiki/Topics/Combined Arms (제병협동) 전술.md delete mode 100644 10_Wiki/Topics/CompCert-C-Compiler.md delete mode 100644 10_Wiki/Topics/Complexity Theory.md delete mode 100644 10_Wiki/Topics/Complexity-Theory.md delete mode 100644 10_Wiki/Topics/Component-Composition.md delete mode 100644 10_Wiki/Topics/Component_Design_Patterns.md delete mode 100644 10_Wiki/Topics/Computational Creativity.md delete mode 100644 10_Wiki/Topics/Computational Neuroscience of Reinforcement Learning.md delete mode 100644 10_Wiki/Topics/Computational-Creativity.md delete mode 100644 10_Wiki/Topics/Computational-Linguistics.md delete mode 100644 10_Wiki/Topics/Computational-Neuroscience-RL.md delete mode 100644 10_Wiki/Topics/Computer Vision.md delete mode 100644 10_Wiki/Topics/Computer-Aided-Design.md delete mode 100644 10_Wiki/Topics/Computer-Vision.md delete mode 100644 10_Wiki/Topics/Computer_Vision.md delete mode 100644 10_Wiki/Topics/Concept Drift (개념 드리프트).md delete mode 100644 10_Wiki/Topics/Concept Drift (개념 드리프트, 모델 지식의 부패).md delete mode 100644 10_Wiki/Topics/Concept Mapping.md delete mode 100644 10_Wiki/Topics/Concept-Drift.md delete mode 100644 10_Wiki/Topics/Concreteness-Principle.md delete mode 100644 10_Wiki/Topics/Concurrent Programming.md delete mode 100644 10_Wiki/Topics/Conditioning and Learning ( ).md delete mode 100644 10_Wiki/Topics/Connect-AI-Documentation.md delete mode 100644 10_Wiki/Topics/ConnectAI_Dev_Log_20260429.md delete mode 100644 10_Wiki/Topics/Constitutional AI (헌법 AI).md delete mode 100644 10_Wiki/Topics/Constitutional-AI.md delete mode 100644 10_Wiki/Topics/Constraint Satisfaction Problems (CSP).md delete mode 100644 10_Wiki/Topics/Constraint-Satisfaction Problems.md delete mode 100644 10_Wiki/Topics/Constraint-Satisfaction-Problems.md delete mode 100644 10_Wiki/Topics/Context-Aware-Computing.md delete mode 100644 10_Wiki/Topics/Continuous-Discovery.md delete mode 100644 10_Wiki/Topics/Contrastive-Learning.md delete mode 100644 10_Wiki/Topics/Control Systems Engineering.md delete mode 100644 10_Wiki/Topics/Control-Systems-Engineering.md delete mode 100644 10_Wiki/Topics/Control-Theory.md delete mode 100644 10_Wiki/Topics/Convolutional-Neural-Networks.md delete mode 100644 10_Wiki/Topics/Core-Web-Vitals-Metrics.md delete mode 100644 10_Wiki/Topics/Core-Web-Vitals.md delete mode 100644 10_Wiki/Topics/Corgea.md delete mode 100644 10_Wiki/Topics/Corporate-LMS-Training.md delete mode 100644 10_Wiki/Topics/Cost-Benefit Analysis in AI.md delete mode 100644 10_Wiki/Topics/Creativity Research.md delete mode 100644 10_Wiki/Topics/Credit Assignment Problem.md delete mode 100644 10_Wiki/Topics/Cross-Entropy Loss.md delete mode 100644 10_Wiki/Topics/Cumulative-Layout-Shift-CLS.md delete mode 100644 10_Wiki/Topics/Curriculum-Learning.md delete mode 100644 10_Wiki/Topics/Custom-ESLint-Rules-Development.md delete mode 100644 10_Wiki/Topics/Custom-ESLint-Rules.md delete mode 100644 10_Wiki/Topics/Custom-Hooks-Patterns.md delete mode 100644 10_Wiki/Topics/Customer-Journey-Mapping.md delete mode 100644 10_Wiki/Topics/Cybernetics Foundations.md delete mode 100644 10_Wiki/Topics/Cybernetics.md delete mode 100644 10_Wiki/Topics/DAG-Dependency-Management.md delete mode 100644 10_Wiki/Topics/DDD-Type-Safety.md delete mode 100644 10_Wiki/Topics/DDD-in-TypeScript.md delete mode 100644 10_Wiki/Topics/DORA-Metrics.md delete mode 100644 10_Wiki/Topics/DPO (Direct Preference Optimization).md delete mode 100644 10_Wiki/Topics/DQN.md delete mode 100644 10_Wiki/Topics/Data Cleaning Algorithms.md delete mode 100644 10_Wiki/Topics/Data Distillation (데이터 증류).md delete mode 100644 10_Wiki/Topics/Data-Augmentation Strategies.md delete mode 100644 10_Wiki/Topics/Data-Ethics and Privacy.md delete mode 100644 10_Wiki/Topics/Data-Flywheel-Effect.md delete mode 100644 10_Wiki/Topics/Data-Pipeline Orchestration.md delete mode 100644 10_Wiki/Topics/Data-Science-in-UX.md delete mode 100644 10_Wiki/Topics/Data-Transfer-Object-Design.md delete mode 100644 10_Wiki/Topics/Dead-Space-Series.md delete mode 100644 10_Wiki/Topics/Deceptive Alignment (기만적 정렬).md delete mode 100644 10_Wiki/Topics/Decision Theory.md delete mode 100644 10_Wiki/Topics/Decision-Trees and Random Forests.md delete mode 100644 10_Wiki/Topics/Declaration-Files.md delete mode 100644 10_Wiki/Topics/Deep Q-Networks (DQN).md delete mode 100644 10_Wiki/Topics/Deep-Convolutional-GANs.md delete mode 100644 10_Wiki/Topics/Deep-Grammar.md delete mode 100644 10_Wiki/Topics/Deep-Learning.md delete mode 100644 10_Wiki/Topics/Deep-Q-Networks-DQN.md delete mode 100644 10_Wiki/Topics/DeepCode AI.md delete mode 100644 10_Wiki/Topics/Deepfake-Detection.md delete mode 100644 10_Wiki/Topics/Deepfake-Technology.md delete mode 100644 10_Wiki/Topics/Default Mode Network (DMN).md delete mode 100644 10_Wiki/Topics/DefinitelyTyped.md delete mode 100644 10_Wiki/Topics/Definitions_of_Game.md delete mode 100644 10_Wiki/Topics/Degrees-of-Freedom.md delete mode 100644 10_Wiki/Topics/Deliberate-Practice.md delete mode 100644 10_Wiki/Topics/Denavit-Hartenberg-Parameters.md delete mode 100644 10_Wiki/Topics/Dense vs Sparse Neural Networks.md delete mode 100644 10_Wiki/Topics/Dependency-Graph-Analysis.md delete mode 100644 10_Wiki/Topics/Dependency-Injection.md delete mode 100644 10_Wiki/Topics/Dependency-Inversion-Principle.md delete mode 100644 10_Wiki/Topics/Deployment-Strategy.md delete mode 100644 10_Wiki/Topics/Deployment_Final_Gate.md delete mode 100644 10_Wiki/Topics/Design-System.md delete mode 100644 10_Wiki/Topics/Determinism-in-Computing.md delete mode 100644 10_Wiki/Topics/DevOps-and-UX-Convergence.md delete mode 100644 10_Wiki/Topics/DevOps-for-AI-MLOps.md delete mode 100644 10_Wiki/Topics/DevOps_Environment_Setup.md delete mode 100644 10_Wiki/Topics/DevSecOps.md delete mode 100644 10_Wiki/Topics/Differentiable Programming.md delete mode 100644 10_Wiki/Topics/Diffusion-Models.md delete mode 100644 10_Wiki/Topics/Digital Intellectual Property Rights.md delete mode 100644 10_Wiki/Topics/Digital Thread Integration.md delete mode 100644 10_Wiki/Topics/Digital-Twin-Technology.md delete mode 100644 10_Wiki/Topics/Dijkstra's Algorithm.md delete mode 100644 10_Wiki/Topics/Dimensionality-Reduction.md delete mode 100644 10_Wiki/Topics/Diminishing Returns (한계 수익 체감).md delete mode 100644 10_Wiki/Topics/Directed-Acyclic-Graph-Build-Systems.md delete mode 100644 10_Wiki/Topics/Directed-Acyclic-Graph-Dependency-Management.md delete mode 100644 10_Wiki/Topics/Discriminated-Unions-for-Error-Handling.md delete mode 100644 10_Wiki/Topics/Discriminated-Unions-for-State-Modeling.md delete mode 100644 10_Wiki/Topics/Discriminated-Unions.md delete mode 100644 10_Wiki/Topics/Dissipative-Structures.md delete mode 100644 10_Wiki/Topics/Distillation.md delete mode 100644 10_Wiki/Topics/Distributed Reinforcement Learning.md delete mode 100644 10_Wiki/Topics/Distributed-Computing.md delete mode 100644 10_Wiki/Topics/Distributed-System-Type-Safety.md delete mode 100644 10_Wiki/Topics/Distributed-Systems.md delete mode 100644 10_Wiki/Topics/Documentation-Strategy.md delete mode 100644 10_Wiki/Topics/Domain Objects.md delete mode 100644 10_Wiki/Topics/Domain-Driven-Design-DDD.md delete mode 100644 10_Wiki/Topics/Domain-Specific-Languages.md delete mode 100644 10_Wiki/Topics/Dopamine-Modeling.md delete mode 100644 10_Wiki/Topics/Dopaminergic Reward System.md delete mode 100644 10_Wiki/Topics/Dopaminergic Reward Systems.md delete mode 100644 10_Wiki/Topics/Drama Management Systems.md delete mode 100644 10_Wiki/Topics/Dramaturgy-Theory.md delete mode 100644 10_Wiki/Topics/Dry-Principle.md delete mode 100644 10_Wiki/Topics/Dynamic Difficulty Adjustment (DDA).md delete mode 100644 10_Wiki/Topics/Dynamic Few-Shot (동적 퓨샷 선택 전략).md delete mode 100644 10_Wiki/Topics/Dynamic-Capabilities.md delete mode 100644 10_Wiki/Topics/Dynamic-Creative-Optimization.md delete mode 100644 10_Wiki/Topics/Dynamic-Environment-Handling.md delete mode 100644 10_Wiki/Topics/Dynamic-Programming.md delete mode 100644 10_Wiki/Topics/E-Learning-Gamification.md delete mode 100644 10_Wiki/Topics/E-commerce-Catalog-Management.md delete mode 100644 10_Wiki/Topics/E-commerce-Optimization.md delete mode 100644 10_Wiki/Topics/ESLint-Plugin-Development.md delete mode 100644 10_Wiki/Topics/ESLint-Static-Analysis.md delete mode 100644 10_Wiki/Topics/EU-Web-Accessibility-Directive.md delete mode 100644 10_Wiki/Topics/Ecology and Ecosystem Modeling.md delete mode 100644 10_Wiki/Topics/Economic-Analysis.md delete mode 100644 10_Wiki/Topics/Economic-Complexity-Index.md delete mode 100644 10_Wiki/Topics/Economic-Mobility.md create mode 100644 10_Wiki/Topics/Economics & Algorithms/페이 투 윈 (Pay to Win).md delete mode 100644 10_Wiki/Topics/Economics & Algorithms/페이 투 윈(Pay to Win).md delete mode 100644 10_Wiki/Topics/Economics-of-Information.md delete mode 100644 10_Wiki/Topics/Edge-AI-and-Computing.md delete mode 100644 10_Wiki/Topics/Edge-Artificial-Intelligence.md delete mode 100644 10_Wiki/Topics/Edge-Computing.md delete mode 100644 10_Wiki/Topics/Edtech-Industry-Trends.md delete mode 100644 10_Wiki/Topics/Effective-Altruism-in-AI.md delete mode 100644 10_Wiki/Topics/Efficiency.md delete mode 100644 10_Wiki/Topics/Eigenvalues-and-Eigenvectors.md delete mode 100644 10_Wiki/Topics/Eligibility-Traces.md delete mode 100644 10_Wiki/Topics/Elite-Sport-Science-Protocols.md delete mode 100644 10_Wiki/Topics/Elite-Strength-and-Conditioning.md delete mode 100644 10_Wiki/Topics/Elite-Theory.md delete mode 100644 10_Wiki/Topics/Embodied Cognition.md delete mode 100644 10_Wiki/Topics/Embodied-AI.md delete mode 100644 10_Wiki/Topics/Emergence-in-Complex-Systems.md delete mode 100644 10_Wiki/Topics/Emergence-in-Systems.md delete mode 100644 10_Wiki/Topics/Emergence.md delete mode 100644 10_Wiki/Topics/Emotional-AI (Affective Computing).md delete mode 100644 10_Wiki/Topics/Emotionally Intelligent Tutoring Systems (EITS).md delete mode 100644 10_Wiki/Topics/Empathy-in-AI.md delete mode 100644 10_Wiki/Topics/Encapsulation-and-Information-Hiding.md delete mode 100644 10_Wiki/Topics/Encapsulation-of-Domain-Invariants.md delete mode 100644 10_Wiki/Topics/Encapsulation-via-Access-Modifiers.md delete mode 100644 10_Wiki/Topics/End-to-End-Learning.md delete mode 100644 10_Wiki/Topics/End-to-End-Testing-Strategies.md delete mode 100644 10_Wiki/Topics/Endurance-Athletics-Cognition.md delete mode 100644 10_Wiki/Topics/Ensemble-Learning.md delete mode 100644 10_Wiki/Topics/Ensemble-Methods.md delete mode 100644 10_Wiki/Topics/Ensuring-Data-Privacy.md delete mode 100644 10_Wiki/Topics/Enterprise-Design-Systems.md delete mode 100644 10_Wiki/Topics/Enterprise-Resource-Planning-Systems.md delete mode 100644 10_Wiki/Topics/Enterprise-Scale-Monorepo-Management.md delete mode 100644 10_Wiki/Topics/Enterprise-Service-Bus.md delete mode 100644 10_Wiki/Topics/Enterprise-Software-Architecture.md delete mode 100644 10_Wiki/Topics/Enterprise-Software-Engineering.md delete mode 100644 10_Wiki/Topics/Entity-Relationship-Modeling.md delete mode 100644 10_Wiki/Topics/Entropy in Information Theory.md delete mode 100644 10_Wiki/Topics/Environment-Design-in-RL.md delete mode 100644 10_Wiki/Topics/Enzyme-Inhibition-Kinetics.md delete mode 100644 10_Wiki/Topics/Epidemiological-Modeling.md delete mode 100644 10_Wiki/Topics/Epistemic-Uncertainty.md delete mode 100644 10_Wiki/Topics/Epistemology.md delete mode 100644 10_Wiki/Topics/Equality.md delete mode 100644 10_Wiki/Topics/Ergodic-Theory.md delete mode 100644 10_Wiki/Topics/Ergonomics-in-Workspace-Design.md delete mode 100644 10_Wiki/Topics/Error-Boundary-Pattern.md delete mode 100644 10_Wiki/Topics/Es-Lint-Configuration.md delete mode 100644 10_Wiki/Topics/Escalation-of-Commitment.md delete mode 100644 10_Wiki/Topics/Ethical-Decision-Making.md delete mode 100644 10_Wiki/Topics/Ethics & AI.md delete mode 100644 10_Wiki/Topics/Ethics of Autonomous Systems.md delete mode 100644 10_Wiki/Topics/Ethics-in-Artificial-Intelligence.md delete mode 100644 10_Wiki/Topics/Ethnographic-Research.md delete mode 100644 10_Wiki/Topics/Etiology-of-Disease.md delete mode 100644 10_Wiki/Topics/Eudaimonia-and-Well-being.md delete mode 100644 10_Wiki/Topics/Eugen Systems 모딩 매뉴얼.md delete mode 100644 10_Wiki/Topics/Eugen Systems의 Iriszoom 엔진 및 전략 게임 개발.md delete mode 100644 10_Wiki/Topics/Eugen Systems의 WARNO 시뮬레이션 개발.md delete mode 100644 10_Wiki/Topics/Eugen Systems의 냉전기 가상 시나리오 및 모딩 생태계 구축.md delete mode 100644 10_Wiki/Topics/Event-Driven-Architecture.md delete mode 100644 10_Wiki/Topics/Evolutionary Biology.md delete mode 100644 10_Wiki/Topics/Evolutionary Computation.md delete mode 100644 10_Wiki/Topics/Evolutionary-Algorithm-Design.md delete mode 100644 10_Wiki/Topics/Evolutionary-Algorithms.md delete mode 100644 10_Wiki/Topics/Evolutionary-Computation.md delete mode 100644 10_Wiki/Topics/Excess-Property-Checking.md delete mode 100644 10_Wiki/Topics/Executive Dysfunction.md delete mode 100644 10_Wiki/Topics/Executive-Function-Deficit.md delete mode 100644 10_Wiki/Topics/Exhaustiveness-Checking.md delete mode 100644 10_Wiki/Topics/Expectation-Maximization.md delete mode 100644 10_Wiki/Topics/Expected Utility Theory.md delete mode 100644 10_Wiki/Topics/Experience-Replay.md delete mode 100644 10_Wiki/Topics/Experience-Sampling-Method.md delete mode 100644 10_Wiki/Topics/Explainable-AI (XAI).md delete mode 100644 10_Wiki/Topics/Explainable-AI-XAI.md delete mode 100644 10_Wiki/Topics/Exploding-Gradient Problem.md delete mode 100644 10_Wiki/Topics/Exploration vs Exploitation.md delete mode 100644 10_Wiki/Topics/Exploration-vs-Exploitation.md delete mode 100644 10_Wiki/Topics/Exploratory-Data-Analysis.md delete mode 100644 10_Wiki/Topics/Expo 2025 Osaka.md delete mode 100644 10_Wiki/Topics/Exponential-Growth.md delete mode 100644 10_Wiki/Topics/Extended-Reality-XR.md delete mode 100644 10_Wiki/Topics/Externalities.md delete mode 100644 10_Wiki/Topics/Extreme-Programming-XP.md delete mode 100644 10_Wiki/Topics/Eye-Tracking-in-UX-Research.md delete mode 100644 10_Wiki/Topics/Eye-Tracking.md delete mode 100644 10_Wiki/Topics/Factor-Analysis.md delete mode 100644 10_Wiki/Topics/Factory-Pattern.md delete mode 100644 10_Wiki/Topics/Failable-Task-Handling.md delete mode 100644 10_Wiki/Topics/Fault-Tolerance.md delete mode 100644 10_Wiki/Topics/Feature Clamping (피처 고정).md delete mode 100644 10_Wiki/Topics/Feature-Engineering.md delete mode 100644 10_Wiki/Topics/Feature-Flags.md delete mode 100644 10_Wiki/Topics/Federated-Learning.md delete mode 100644 10_Wiki/Topics/Feedback-Control-Systems.md delete mode 100644 10_Wiki/Topics/Feedback-Loops in Systems.md delete mode 100644 10_Wiki/Topics/Feedback-Loops-in-Design.md delete mode 100644 10_Wiki/Topics/Feedback-Loops.md delete mode 100644 10_Wiki/Topics/Few-Shot-Learning.md delete mode 100644 10_Wiki/Topics/Figma-to-Code-Workflow.md delete mode 100644 10_Wiki/Topics/Figurative-Language.md delete mode 100644 10_Wiki/Topics/Fine-tuning.md delete mode 100644 10_Wiki/Topics/Finished Goods.md delete mode 100644 10_Wiki/Topics/Finite-Element-Analysis.md delete mode 100644 10_Wiki/Topics/Finite-State-Machines-FSM.md delete mode 100644 10_Wiki/Topics/Finite-State-Machines.md delete mode 100644 10_Wiki/Topics/First Input Delay (FID).md delete mode 100644 10_Wiki/Topics/Fitness-Landscape.md delete mode 100644 10_Wiki/Topics/Fixed Time Step vs Variable Time Step.md delete mode 100644 10_Wiki/Topics/Flow State.md delete mode 100644 10_Wiki/Topics/Flow-State.md delete mode 100644 10_Wiki/Topics/Fluent-Interface-Design.md delete mode 100644 10_Wiki/Topics/Fluid-Dynamics for Games.md delete mode 100644 10_Wiki/Topics/Focal-Loss.md delete mode 100644 10_Wiki/Topics/Formal Methods.md delete mode 100644 10_Wiki/Topics/Formal-Verification-of-Software.md delete mode 100644 10_Wiki/Topics/Foundation-Models.md delete mode 100644 10_Wiki/Topics/Fragility.md delete mode 100644 10_Wiki/Topics/Free-Energy-Principle.md delete mode 100644 10_Wiki/Topics/Frontend-Architecture-and-Folder-Structure.md delete mode 100644 10_Wiki/Topics/Frontend-Architecture.md delete mode 100644 10_Wiki/Topics/Frontend-Debugging-and-Testing.md delete mode 100644 10_Wiki/Topics/Frontend-Performance-Optimization-Guide.md delete mode 100644 10_Wiki/Topics/Frontend-Team-Collaboration-and-Governance.md delete mode 100644 10_Wiki/Topics/Frontend.md delete mode 100644 10_Wiki/Topics/Functional Programming.md delete mode 100644 10_Wiki/Topics/Functional-Programming-in-TypeScript.md delete mode 100644 10_Wiki/Topics/Functional-Programming.md delete mode 100644 10_Wiki/Topics/Fuzzy-Logic.md delete mode 100644 10_Wiki/Topics/G-Stack Principles.md delete mode 100644 10_Wiki/Topics/G-Stack-Integration-Guide.md delete mode 100644 10_Wiki/Topics/GAN.md delete mode 100644 10_Wiki/Topics/GNN.md delete mode 100644 10_Wiki/Topics/GPT-Architecture-Foundations.md delete mode 100644 10_Wiki/Topics/GPU-Architecture.md delete mode 100644 10_Wiki/Topics/GPU-Programming-with-CUDA.md delete mode 100644 10_Wiki/Topics/GPU.md delete mode 100644 10_Wiki/Topics/GRPO.md delete mode 100644 10_Wiki/Topics/GRU.md delete mode 100644 10_Wiki/Topics/Gacha Mechanics Analysis.md delete mode 100644 10_Wiki/Topics/Gait-Analysis-Laboratory.md delete mode 100644 10_Wiki/Topics/Game Analytics (게임 분석).md delete mode 100644 10_Wiki/Topics/Game Design/Pay-to-win.md delete mode 100644 10_Wiki/Topics/Game Design/War-Commander-Strategic-Hub.md delete mode 100644 10_Wiki/Topics/Game-Balance-Design.md delete mode 100644 10_Wiki/Topics/Game-Balance-Modeling.md delete mode 100644 10_Wiki/Topics/Game-Design-Ontology.md delete mode 100644 10_Wiki/Topics/Game-Design-Theory.md delete mode 100644 10_Wiki/Topics/Game-Economy-Design.md delete mode 100644 10_Wiki/Topics/Game-Feel-and-Juiciness.md delete mode 100644 10_Wiki/Topics/Game-Loop-Architecture.md delete mode 100644 10_Wiki/Topics/Game-Mechanics.md delete mode 100644 10_Wiki/Topics/Game-Ontology-for-PCG.md delete mode 100644 10_Wiki/Topics/Game-Theory-in-AI.md delete mode 100644 10_Wiki/Topics/Game-Theory.md delete mode 100644 10_Wiki/Topics/Gamification-Strategies.md delete mode 100644 10_Wiki/Topics/Gamification-Theory.md delete mode 100644 10_Wiki/Topics/Gates.md delete mode 100644 10_Wiki/Topics/Gaussian-Processes.md delete mode 100644 10_Wiki/Topics/Generative Adversarial Networks (GANs) in Fine Arts.md delete mode 100644 10_Wiki/Topics/Generative-Adversarial-Networks.md delete mode 100644 10_Wiki/Topics/Generics-and-Polymorphism.md delete mode 100644 10_Wiki/Topics/Genetic-Algorithms.md delete mode 100644 10_Wiki/Topics/Geographic-Information-Systems.md delete mode 100644 10_Wiki/Topics/Geometric-Deep-Learning.md delete mode 100644 10_Wiki/Topics/Geriatric-Medicine.md delete mode 100644 10_Wiki/Topics/Gestalt Psychology.md delete mode 100644 10_Wiki/Topics/Gestalt-Principles in UX.md delete mode 100644 10_Wiki/Topics/Gestalt-Principles-of-Design.md delete mode 100644 10_Wiki/Topics/Gimbals-and-Orientation.md delete mode 100644 10_Wiki/Topics/Git-Branching-Strategies-and-Workflows.md delete mode 100644 10_Wiki/Topics/Git-Version-Control.md delete mode 100644 10_Wiki/Topics/Git_Operation_Protocol.md delete mode 100644 10_Wiki/Topics/GloVe (Word Embeddings).md delete mode 100644 10_Wiki/Topics/Global-Standard.md delete mode 100644 10_Wiki/Topics/Global-vs-Local-Optima.md delete mode 100644 10_Wiki/Topics/Goal-Misgeneralization.md delete mode 100644 10_Wiki/Topics/Goal-Oriented-Action-Planning.md delete mode 100644 10_Wiki/Topics/God-Object-Antipattern.md delete mode 100644 10_Wiki/Topics/Godel's Incompleteness Theorems.md delete mode 100644 10_Wiki/Topics/Google-Page-Experience-2025-Update.md delete mode 100644 10_Wiki/Topics/Gradient-Boosting-Machines.md delete mode 100644 10_Wiki/Topics/Gradient-Descent.md delete mode 100644 10_Wiki/Topics/Graph Theory.md delete mode 100644 10_Wiki/Topics/Graph-Coloring-Problem.md delete mode 100644 10_Wiki/Topics/Graph-Database.md delete mode 100644 10_Wiki/Topics/Graph-Theory.md delete mode 100644 10_Wiki/Topics/GraphQL-Code-Generator.md delete mode 100644 10_Wiki/Topics/GraphRAG (그래프 기반 검색 증강 생성).md delete mode 100644 10_Wiki/Topics/Greedy-Algorithms.md delete mode 100644 10_Wiki/Topics/Grit.md delete mode 100644 10_Wiki/Topics/Grounded Theory Method.md delete mode 100644 10_Wiki/Topics/Growth-Mindset-Intervention.md delete mode 100644 10_Wiki/Topics/Growth-Mindset.md delete mode 100644 10_Wiki/Topics/Guilty-Gear-Xrd-Rendering-Pipeline.md delete mode 100644 10_Wiki/Topics/HANDOVER.md delete mode 100644 10_Wiki/Topics/HBO-Prestige-Television.md delete mode 100644 10_Wiki/Topics/HCI (Human-Computer Interaction).md delete mode 100644 10_Wiki/Topics/HHH.md delete mode 100644 10_Wiki/Topics/HMM.md delete mode 100644 10_Wiki/Topics/Habit-Formation.md delete mode 100644 10_Wiki/Topics/Hallucination (환각).md delete mode 100644 10_Wiki/Topics/Hallucination-in-LLM.md delete mode 100644 10_Wiki/Topics/Hallucination-in-LLMs.md delete mode 100644 10_Wiki/Topics/Hardware-Acceleration-for-AI.md delete mode 100644 10_Wiki/Topics/Hardware-Verification.md delete mode 100644 10_Wiki/Topics/Hardware.md delete mode 100644 10_Wiki/Topics/Hash-Functions-and-Maps.md delete mode 100644 10_Wiki/Topics/Health-Informatics.md delete mode 100644 10_Wiki/Topics/Hebbian-Learning.md delete mode 100644 10_Wiki/Topics/Hebbian-Theory.md delete mode 100644 10_Wiki/Topics/Heuristic-Search.md delete mode 100644 10_Wiki/Topics/Heuristics.md delete mode 100644 10_Wiki/Topics/Hierarchical-Task-Network (HTN).md delete mode 100644 10_Wiki/Topics/High-Availability-Systems.md delete mode 100644 10_Wiki/Topics/High-Cohesion-Low-Coupling.md delete mode 100644 10_Wiki/Topics/High-Frequency-Trading-Models.md delete mode 100644 10_Wiki/Topics/High-Performance Computing (HPC).md delete mode 100644 10_Wiki/Topics/High-Performance-Coaching.md delete mode 100644 10_Wiki/Topics/High-Performance-Organizations.md delete mode 100644 10_Wiki/Topics/High-Performance-Sports-Science.md delete mode 100644 10_Wiki/Topics/Homeostasis (항상성).md delete mode 100644 10_Wiki/Topics/Homeostasis.md delete mode 100644 10_Wiki/Topics/Homomorphic-Encryption.md delete mode 100644 10_Wiki/Topics/Human Centered AI (HCAI).md delete mode 100644 10_Wiki/Topics/Human-AI-Collaboration.md delete mode 100644 10_Wiki/Topics/Human-Computer-Interaction-HCI.md delete mode 100644 10_Wiki/Topics/Human-Computer-Interaction.md delete mode 100644 10_Wiki/Topics/Human-in-the-loop (HITL).md delete mode 100644 10_Wiki/Topics/Human-in-the-loop-AI.md delete mode 100644 10_Wiki/Topics/Hybrid-Cloud-Architectures.md delete mode 100644 10_Wiki/Topics/Hydration-Mismatch-and-SSR-Debugging.md delete mode 100644 10_Wiki/Topics/Hyperinflation-in-Closed-Loop-Systems.md delete mode 100644 10_Wiki/Topics/Hyperparameter-Optimization.md delete mode 100644 10_Wiki/Topics/Hyperparameters.md delete mode 100644 10_Wiki/Topics/Hypostatic-Abstraction.md delete mode 100644 10_Wiki/Topics/Hypothesis-Testing.md delete mode 100644 10_Wiki/Topics/ICRE-Framework.md delete mode 100644 10_Wiki/Topics/IDE (Integrated Development Environment).md delete mode 100644 10_Wiki/Topics/IEEE-P36521.md delete mode 100644 10_Wiki/Topics/ISO-Standard.md delete mode 100644 10_Wiki/Topics/Ikigai (이키가이).md delete mode 100644 10_Wiki/Topics/Image-Classification-Mastery.md delete mode 100644 10_Wiki/Topics/Image-Optimization-for-Web-Performance.md delete mode 100644 10_Wiki/Topics/Image-Segmentation-Techniques.md delete mode 100644 10_Wiki/Topics/Image-Segmentation.md delete mode 100644 10_Wiki/Topics/Imbalanced-Data-Handling.md delete mode 100644 10_Wiki/Topics/Imitation-Learning.md delete mode 100644 10_Wiki/Topics/Immersive-Sim-Design.md delete mode 100644 10_Wiki/Topics/Immersive-Sim-Genre.md delete mode 100644 10_Wiki/Topics/Immersive-Sims-Deus-Ex-Dishonored.md delete mode 100644 10_Wiki/Topics/Immersive-Sims-Deus-Ex-Thief.md delete mode 100644 10_Wiki/Topics/Immutability-Patterns.md delete mode 100644 10_Wiki/Topics/Impedance-Matching.md delete mode 100644 10_Wiki/Topics/In-Context-Learning.md delete mode 100644 10_Wiki/Topics/Inclusive-Design-and-UX.md delete mode 100644 10_Wiki/Topics/Incremental-Computation.md delete mode 100644 10_Wiki/Topics/Incremental-Learning.md delete mode 100644 10_Wiki/Topics/Incremental-Static-Regeneration-ISR.md delete mode 100644 10_Wiki/Topics/Incrementalism.md delete mode 100644 10_Wiki/Topics/Independent Component Analysis (ICA).md delete mode 100644 10_Wiki/Topics/Independent-Component-Analysis.md delete mode 100644 10_Wiki/Topics/Index-Fragmentation-Analysis.md delete mode 100644 10_Wiki/Topics/Index.md delete mode 100644 10_Wiki/Topics/Indexing-Strategies.md delete mode 100644 10_Wiki/Topics/Indian-Innovation-Models.md delete mode 100644 10_Wiki/Topics/Inductive-Bias.md delete mode 100644 10_Wiki/Topics/Inductive-Reasoning.md delete mode 100644 10_Wiki/Topics/Inexact-Science.md delete mode 100644 10_Wiki/Topics/Inference-Optimization.md delete mode 100644 10_Wiki/Topics/Inferential-Statistics.md delete mode 100644 10_Wiki/Topics/Information-Entropy.md delete mode 100644 10_Wiki/Topics/Information-Retrieval-IR.md delete mode 100644 10_Wiki/Topics/Information-Society.md delete mode 100644 10_Wiki/Topics/Information-Theory.md delete mode 100644 10_Wiki/Topics/Infraspace.md delete mode 100644 10_Wiki/Topics/Infrastructure-as-Code-IaC.md delete mode 100644 10_Wiki/Topics/Inheritance-and-Polymorphism.md delete mode 100644 10_Wiki/Topics/Inner-Product-Spaces.md delete mode 100644 10_Wiki/Topics/Innovation.md delete mode 100644 10_Wiki/Topics/Input-Validation-Strategies.md delete mode 100644 10_Wiki/Topics/Inquiry-Based Learning.md delete mode 100644 10_Wiki/Topics/Instance-based-Learning.md delete mode 100644 10_Wiki/Topics/InstancedMesh2 library.md delete mode 100644 10_Wiki/Topics/Instinct.md delete mode 100644 10_Wiki/Topics/Instruction-Tuning.md delete mode 100644 10_Wiki/Topics/Intangible-Capital.md delete mode 100644 10_Wiki/Topics/Integrated-Development-Environment.md delete mode 100644 10_Wiki/Topics/Integration-Testing-for-AI.md delete mode 100644 10_Wiki/Topics/Intellectual-Property-in-AI.md delete mode 100644 10_Wiki/Topics/Interaction to Next Paint (INP).md delete mode 100644 10_Wiki/Topics/Interaction-to-Next-Paint-INP.md delete mode 100644 10_Wiki/Topics/Interdisciplinary-Research.md delete mode 100644 10_Wiki/Topics/Interface-Segregation-Principle.md delete mode 100644 10_Wiki/Topics/Internet of Things (IoT).md delete mode 100644 10_Wiki/Topics/Interop 2026.md delete mode 100644 10_Wiki/Topics/Interoperability.md delete mode 100644 10_Wiki/Topics/Interpretability-vs-Explainability.md delete mode 100644 10_Wiki/Topics/Interpretability.md delete mode 100644 10_Wiki/Topics/Introduction-to-Programming.md delete mode 100644 10_Wiki/Topics/Introspection (자기성찰).md delete mode 100644 10_Wiki/Topics/Inverse-Kinematics.md delete mode 100644 10_Wiki/Topics/Inverse-Reinforcement-Learning.md delete mode 100644 10_Wiki/Topics/Inversion.md delete mode 100644 10_Wiki/Topics/IoT-and-AI-Integration.md delete mode 100644 10_Wiki/Topics/Isaac-Asimovs-Laws-of-Robotics.md delete mode 100644 10_Wiki/Topics/Item-Item-Collaborative-Filtering.md delete mode 100644 10_Wiki/Topics/Iteration.md delete mode 100644 10_Wiki/Topics/Iterative-Development-Models.md delete mode 100644 10_Wiki/Topics/Iterative-Development.md delete mode 100644 10_Wiki/Topics/JIT-Compilation-in-AI-Engines.md delete mode 100644 10_Wiki/Topics/JSON-LD-Structured-Data.md delete mode 100644 10_Wiki/Topics/JSON-and-Data-Serialization.md delete mode 100644 10_Wiki/Topics/JUnit-and-Testing-Frameworks.md delete mode 100644 10_Wiki/Topics/JavaScript-Async-and-Event-Loop.md delete mode 100644 10_Wiki/Topics/JavaScript-Optimization-Patterns.md delete mode 100644 10_Wiki/Topics/Joint-Optimization.md delete mode 100644 10_Wiki/Topics/Journaling.md delete mode 100644 10_Wiki/Topics/Judgment.md delete mode 100644 10_Wiki/Topics/Just-In-Time (JIT).md delete mode 100644 10_Wiki/Topics/Just-in-Case.md delete mode 100644 10_Wiki/Topics/Just-in-time-Data-Loading.md delete mode 100644 10_Wiki/Topics/K-Means-Clustering-Foundations.md delete mode 100644 10_Wiki/Topics/K-Nearest-Neighbors-K-NN.md delete mode 100644 10_Wiki/Topics/KISS (Keep It Simple, Stupid).md delete mode 100644 10_Wiki/Topics/KISS-Principle-in-Software-Design.md delete mode 100644 10_Wiki/Topics/KPI (Key Performance Indicator).md delete mode 100644 10_Wiki/Topics/Kalman-Filter-and-State-Tracking.md delete mode 100644 10_Wiki/Topics/Kernel-Density-Estimation-KDE.md delete mode 100644 10_Wiki/Topics/Kernel-Methods-and-SVMs.md delete mode 100644 10_Wiki/Topics/Knowledge synthesis.md delete mode 100644 10_Wiki/Topics/Knowledge-Distillation.md delete mode 100644 10_Wiki/Topics/Knowledge-Graph-Foundations.md delete mode 100644 10_Wiki/Topics/Knowledge-Graph.md delete mode 100644 10_Wiki/Topics/Knowledge-Representation-in-AI.md delete mode 100644 10_Wiki/Topics/Knowledge-Structure.md delete mode 100644 10_Wiki/Topics/Kolmogorov-Complexity.md delete mode 100644 10_Wiki/Topics/Kubernetes-for-AI-Orchestration.md delete mode 100644 10_Wiki/Topics/Kullback-Leibler-Divergence.md delete mode 100644 10_Wiki/Topics/L1-and-L2-Regularization.md delete mode 100644 10_Wiki/Topics/L2-Regularization.md delete mode 100644 10_Wiki/Topics/LLM-Security-and-Safety.md delete mode 100644 10_Wiki/Topics/LLM.md delete mode 100644 10_Wiki/Topics/LOD.md delete mode 100644 10_Wiki/Topics/Label-Noise-and-Robustness.md delete mode 100644 10_Wiki/Topics/Lagrange-Multipliers.md delete mode 100644 10_Wiki/Topics/Language-Models.md delete mode 100644 10_Wiki/Topics/Large Language Models (LLM).md delete mode 100644 10_Wiki/Topics/Large-scale-Application-Architecture-Patterns.md delete mode 100644 10_Wiki/Topics/Largest Contentful Paint (LCP).md delete mode 100644 10_Wiki/Topics/Largest-Contentful-Paint-LCP.md delete mode 100644 10_Wiki/Topics/Latent-Dirichlet-Allocation.md delete mode 100644 10_Wiki/Topics/Latent-Semantic-Analysis-LSA.md delete mode 100644 10_Wiki/Topics/Layer-Normalization.md delete mode 100644 10_Wiki/Topics/Layered-Architecture-in-Frontend.md delete mode 100644 10_Wiki/Topics/Lazy-Loading-Strategies.md delete mode 100644 10_Wiki/Topics/Leadership.md delete mode 100644 10_Wiki/Topics/Leaky-ReLU-and-Activations.md delete mode 100644 10_Wiki/Topics/Lean-Operations.md delete mode 100644 10_Wiki/Topics/Lean-Project-Management.md delete mode 100644 10_Wiki/Topics/Learning-Paths.md delete mode 100644 10_Wiki/Topics/Learning-Rate-Schedules.md delete mode 100644 10_Wiki/Topics/Learning-Rate-Scheduling.md delete mode 100644 10_Wiki/Topics/Least-Squares-Methods.md delete mode 100644 10_Wiki/Topics/Legacy-Systems.md delete mode 100644 10_Wiki/Topics/Lessons Learned.md delete mode 100644 10_Wiki/Topics/Level of Detail (LOD).md delete mode 100644 10_Wiki/Topics/Levels of Understanding.md delete mode 100644 10_Wiki/Topics/Linear-Algebra-Foundations.md delete mode 100644 10_Wiki/Topics/Linear-Algebra-for-ML.md delete mode 100644 10_Wiki/Topics/Linear-Algebra.md delete mode 100644 10_Wiki/Topics/Linear-Discriminant-Analysis.md delete mode 100644 10_Wiki/Topics/Linear-Programming.md delete mode 100644 10_Wiki/Topics/Linear-Regression-Mastery.md delete mode 100644 10_Wiki/Topics/Linguistic-Analysis-in-AI.md delete mode 100644 10_Wiki/Topics/Linked-Lists-and-Trees.md delete mode 100644 10_Wiki/Topics/Linux-Performance-Tuning.md delete mode 100644 10_Wiki/Topics/Liquid-Democracy.md delete mode 100644 10_Wiki/Topics/Liskov-Substitution-Principle.md delete mode 100644 10_Wiki/Topics/LlamaIndex.md delete mode 100644 10_Wiki/Topics/LoRA (Low-Rank Adaptation).md delete mode 100644 10_Wiki/Topics/Load-Balancing-Strategies.md delete mode 100644 10_Wiki/Topics/Local-Brain-Management.md delete mode 100644 10_Wiki/Topics/Local-Search.md delete mode 100644 10_Wiki/Topics/Locality-Sensitive-Hashing (LSH).md delete mode 100644 10_Wiki/Topics/Locality-Sensitive-Hashing.md delete mode 100644 10_Wiki/Topics/Logic.md delete mode 100644 10_Wiki/Topics/Logistic-Regression-Foundations.md delete mode 100644 10_Wiki/Topics/Logistic-Regression.md delete mode 100644 10_Wiki/Topics/Long Animation Frames API.md delete mode 100644 10_Wiki/Topics/Long Tasks.md delete mode 100644 10_Wiki/Topics/Long-Tail.md delete mode 100644 10_Wiki/Topics/Loose-Coupling.md delete mode 100644 10_Wiki/Topics/Loss Functions.md delete mode 100644 10_Wiki/Topics/Loss-Functions-Foundations.md delete mode 100644 10_Wiki/Topics/Low-Rank-Adaptation-LoRA.md delete mode 100644 10_Wiki/Topics/Lubrication.md delete mode 100644 10_Wiki/Topics/Lucas-Kanade-Method.md delete mode 100644 10_Wiki/Topics/MAP-Estimation.md delete mode 100644 10_Wiki/Topics/MBA (Master of Business Administration).md delete mode 100644 10_Wiki/Topics/MLA-Format.md delete mode 100644 10_Wiki/Topics/MLOps.md delete mode 100644 10_Wiki/Topics/Machine Learning (ML).md delete mode 100644 10_Wiki/Topics/Machine-Learning-Foundations.md delete mode 100644 10_Wiki/Topics/Machine-Learning-Lifecycle.md delete mode 100644 10_Wiki/Topics/Macros (매크로).md delete mode 100644 10_Wiki/Topics/Magic-Circle.md delete mode 100644 10_Wiki/Topics/Main Thread.md delete mode 100644 10_Wiki/Topics/Malware-Analysis.md delete mode 100644 10_Wiki/Topics/Management.md delete mode 100644 10_Wiki/Topics/Manhattan-Distance.md delete mode 100644 10_Wiki/Topics/MapReduce.md delete mode 100644 10_Wiki/Topics/Markov-Chain-Monte-Carlo.md delete mode 100644 10_Wiki/Topics/Markov-Chains.md delete mode 100644 10_Wiki/Topics/Markov-Decision-Process (MDP).md delete mode 100644 10_Wiki/Topics/Markov-Decision-Process-MDP.md delete mode 100644 10_Wiki/Topics/Markov-Decision-Processes.md delete mode 100644 10_Wiki/Topics/Master-of-Information-Management.md delete mode 100644 10_Wiki/Topics/Mastery.md delete mode 100644 10_Wiki/Topics/Matrix-Factorization.md delete mode 100644 10_Wiki/Topics/Matrix-Operations-and-AI.md delete mode 100644 10_Wiki/Topics/Mean-Absolute-Error-MAE.md delete mode 100644 10_Wiki/Topics/Mean-Squared-Error-MSE.md delete mode 100644 10_Wiki/Topics/Mechanistic Interpretability (기계적 해석 가능성).md delete mode 100644 10_Wiki/Topics/Media-Literacy.md delete mode 100644 10_Wiki/Topics/Medical-Imaging-Data-Augmentation.md delete mode 100644 10_Wiki/Topics/Memetics.md delete mode 100644 10_Wiki/Topics/Memory-Hierarchy.md delete mode 100644 10_Wiki/Topics/Memory-Leak-Debugging-in-JavaScript.md delete mode 100644 10_Wiki/Topics/Mental-Models.md delete mode 100644 10_Wiki/Topics/Mental-Operations-Synthesized.md delete mode 100644 10_Wiki/Topics/Message-Queues-and-Event-Streams.md delete mode 100644 10_Wiki/Topics/Meta-Learning-in-AI.md delete mode 100644 10_Wiki/Topics/Micro-interactions-and-Feedback-Loops.md delete mode 100644 10_Wiki/Topics/Micro-interactions.md delete mode 100644 10_Wiki/Topics/Microservices-Architecture.md delete mode 100644 10_Wiki/Topics/Middle-Out-Thinking.md delete mode 100644 10_Wiki/Topics/Minimal-Viable-Product.md delete mode 100644 10_Wiki/Topics/Minimum-Viable-Product-MVP.md delete mode 100644 10_Wiki/Topics/Mipmap.md delete mode 100644 10_Wiki/Topics/Mobile-AI-Optimization.md delete mode 100644 10_Wiki/Topics/Mobile-Augmented-Reality.md delete mode 100644 10_Wiki/Topics/Mobile-First-Responsive-Design-Principles.md delete mode 100644 10_Wiki/Topics/Model Context Protocol (MCP).md delete mode 100644 10_Wiki/Topics/Model-Agnostic-Meta-Learning.md delete mode 100644 10_Wiki/Topics/Model-Compression-Strategies.md delete mode 100644 10_Wiki/Topics/Model-Compression.md delete mode 100644 10_Wiki/Topics/Model-Deployment-Patterns.md delete mode 100644 10_Wiki/Topics/Model-Drift-and-Monitoring.md delete mode 100644 10_Wiki/Topics/Model-Ensemble-Methods.md delete mode 100644 10_Wiki/Topics/Model-Interpretability-Tools.md delete mode 100644 10_Wiki/Topics/Model-Predictive-Control (MPC).md delete mode 100644 10_Wiki/Topics/Modern-Frontend-Engineering-Architecture.md delete mode 100644 10_Wiki/Topics/Modern-React-Application-Architecture-Patterns.md delete mode 100644 10_Wiki/Topics/Modern-Web-Design-Best-Practices-2025.md delete mode 100644 10_Wiki/Topics/Modern-Website-Architecture.md delete mode 100644 10_Wiki/Topics/Modern_Environment_Ecosystem.md delete mode 100644 10_Wiki/Topics/Modular-Design.md delete mode 100644 10_Wiki/Topics/Modular-Programming.md delete mode 100644 10_Wiki/Topics/Modularity.md delete mode 100644 10_Wiki/Topics/Momentum-and-Optimization.md delete mode 100644 10_Wiki/Topics/Monolithic-vs-Microservices.md delete mode 100644 10_Wiki/Topics/Monte-Carlo-Integration.md delete mode 100644 10_Wiki/Topics/Monte-Carlo-Methods.md delete mode 100644 10_Wiki/Topics/Monte-Carlo-Tree-Search-MCTS.md delete mode 100644 10_Wiki/Topics/Multi-Agent-Reinforcement-Learning.md delete mode 100644 10_Wiki/Topics/Multi-Agent-Systems-MAS.md delete mode 100644 10_Wiki/Topics/Multi-Head-Attention-Mechanism.md delete mode 100644 10_Wiki/Topics/Multi-Modal-Learning.md delete mode 100644 10_Wiki/Topics/Multi-agent-System.md delete mode 100644 10_Wiki/Topics/Multi-armed-Bandit-Problem.md delete mode 100644 10_Wiki/Topics/Multilayer-Perceptron-MLP.md delete mode 100644 10_Wiki/Topics/Multimodal-Learning.md delete mode 100644 10_Wiki/Topics/Multinomial-Naive-Bayes.md delete mode 100644 10_Wiki/Topics/Multivariate-Analysis.md delete mode 100644 10_Wiki/Topics/Mutual-Information.md delete mode 100644 10_Wiki/Topics/NLP (Natural Language Processing).md delete mode 100644 10_Wiki/Topics/NLP-Attention-Mechanisms.md delete mode 100644 10_Wiki/Topics/NVIDIA-CUDA-and-AI.md delete mode 100644 10_Wiki/Topics/Naive-Bayes-Classifiers.md delete mode 100644 10_Wiki/Topics/Named-Entity-Recognition-NER.md delete mode 100644 10_Wiki/Topics/National-Language-Processing.md delete mode 100644 10_Wiki/Topics/Natural-Language-Generation-NLG.md delete mode 100644 10_Wiki/Topics/Natural-Language-Processing-NLP.md delete mode 100644 10_Wiki/Topics/Natural-Language-Processing.md delete mode 100644 10_Wiki/Topics/Nearest-Neighbor-Search.md delete mode 100644 10_Wiki/Topics/Network-Latency-Optimization.md delete mode 100644 10_Wiki/Topics/Neural-Architecture-Search-NAS.md delete mode 100644 10_Wiki/Topics/Neural-Architecture-Search.md delete mode 100644 10_Wiki/Topics/Neural-Darwinism.md delete mode 100644 10_Wiki/Topics/Neural-Style-Transfer.md delete mode 100644 10_Wiki/Topics/Neural-Symbolic-Integration.md delete mode 100644 10_Wiki/Topics/Neuro-Symbolic AI.md delete mode 100644 10_Wiki/Topics/Neuro-Symbolic-AI.md delete mode 100644 10_Wiki/Topics/Neurobiology-of-Reward.md delete mode 100644 10_Wiki/Topics/Neurodevelopmental Disorders.md delete mode 100644 10_Wiki/Topics/Neuroeconomics.md delete mode 100644 10_Wiki/Topics/Neuroergonomics.md delete mode 100644 10_Wiki/Topics/Neuroevolution.md delete mode 100644 10_Wiki/Topics/Neuromuscular-Adaptation.md delete mode 100644 10_Wiki/Topics/Neuromuscular-Control.md delete mode 100644 10_Wiki/Topics/Neuropharmacology of Substance Use Disorders.md delete mode 100644 10_Wiki/Topics/Neuroplasticity in Addiction.md delete mode 100644 10_Wiki/Topics/Neuroplasticity in Motor Learning.md delete mode 100644 10_Wiki/Topics/Neuroplasticity-in-Motor-Learning.md delete mode 100644 10_Wiki/Topics/Neuroprosthetics-Development.md delete mode 100644 10_Wiki/Topics/Neuropsychiatric Disorders.md delete mode 100644 10_Wiki/Topics/Neuropsychology.md delete mode 100644 10_Wiki/Topics/Neurorehabilitation after Stroke.md delete mode 100644 10_Wiki/Topics/Neurorehabilitation-Post-Stroke.md delete mode 100644 10_Wiki/Topics/Next-js-and-Modern-Web.md delete mode 100644 10_Wiki/Topics/Nextjs-App-Router-Architecture.md delete mode 100644 10_Wiki/Topics/No Mans Sky (Large-scale planetary generation).md delete mode 100644 10_Wiki/Topics/No Mans Sky.md delete mode 100644 10_Wiki/Topics/NoSQL-Databases-in-AI.md delete mode 100644 10_Wiki/Topics/Nodejs 메모리 누수 분석.md delete mode 100644 10_Wiki/Topics/Nodejs 프로덕션 메모리 누수 진단.md delete mode 100644 10_Wiki/Topics/Nodejs 프로덕션 메모리 병목 분석.md delete mode 100644 10_Wiki/Topics/Nodejs-Global-Namespace-Augmentation.md delete mode 100644 10_Wiki/Topics/Noise-Reduction-in-AI.md delete mode 100644 10_Wiki/Topics/Noise.md delete mode 100644 10_Wiki/Topics/Nominal-Typing-in-TypeScript.md delete mode 100644 10_Wiki/Topics/Non-Photorealistic-Rendering-in-Level-Design.md delete mode 100644 10_Wiki/Topics/Non-linear-Activation-Functions.md delete mode 100644 10_Wiki/Topics/Non-parametric-Models.md delete mode 100644 10_Wiki/Topics/Normalization-Strategies.md delete mode 100644 10_Wiki/Topics/Normalization.md delete mode 100644 10_Wiki/Topics/Nuclear Deterrence Models.md delete mode 100644 10_Wiki/Topics/Numbers-and-Games.md delete mode 100644 10_Wiki/Topics/Nutritional-Biochemistry.md delete mode 100644 10_Wiki/Topics/OKR.md delete mode 100644 10_Wiki/Topics/OWA vs CWA (개방 세계 vs 폐쇄 세계 가설).md delete mode 100644 10_Wiki/Topics/Object Pooling (오브젝트 풀링).md delete mode 100644 10_Wiki/Topics/Object-Detection-Foundations.md delete mode 100644 10_Wiki/Topics/Object-Oriented-Design-Patterns.md delete mode 100644 10_Wiki/Topics/Object-Oriented-Programming.md delete mode 100644 10_Wiki/Topics/Objective-Functions.md delete mode 100644 10_Wiki/Topics/Objectivism.md delete mode 100644 10_Wiki/Topics/Observation.md delete mode 100644 10_Wiki/Topics/Occupational-Therapy.md delete mode 100644 10_Wiki/Topics/Off-policy-vs-On-policy-Learning.md delete mode 100644 10_Wiki/Topics/Okami-Ink-Wash-Aesthetics.md delete mode 100644 10_Wiki/Topics/Olympic-Training-Cycles.md delete mode 100644 10_Wiki/Topics/Olympic-Training-Models.md delete mode 100644 10_Wiki/Topics/Olympic-Training-Protocols.md delete mode 100644 10_Wiki/Topics/One-Hot-Encoding.md delete mode 100644 10_Wiki/Topics/One-Shot-Learning.md delete mode 100644 10_Wiki/Topics/Online-Learning-and-Streaming.md delete mode 100644 10_Wiki/Topics/Ontological-Engineering.md delete mode 100644 10_Wiki/Topics/Ontology-Driven-Relevancy-Filtering.md delete mode 100644 10_Wiki/Topics/Ontology-Engineering.md delete mode 100644 10_Wiki/Topics/Ontology-Guided Knowledge Extraction.md delete mode 100644 10_Wiki/Topics/Ontology-and-Knowledge-Representation.md delete mode 100644 10_Wiki/Topics/Ontology.md delete mode 100644 10_Wiki/Topics/Opaque-Types.md delete mode 100644 10_Wiki/Topics/Open-Access-Movement.md delete mode 100644 10_Wiki/Topics/Open-Source-AI-Ecosystem.md delete mode 100644 10_Wiki/Topics/OpenAI-API-Integration.md delete mode 100644 10_Wiki/Topics/Operations-Management.md delete mode 100644 10_Wiki/Topics/Operations-Research.md delete mode 100644 10_Wiki/Topics/Operator-Theory.md delete mode 100644 10_Wiki/Topics/Opportunity-Cost.md delete mode 100644 10_Wiki/Topics/Optical-Character-Recognition.md delete mode 100644 10_Wiki/Topics/Optimal-Control-Theory.md delete mode 100644 10_Wiki/Topics/Optimization-Algorithms.md delete mode 100644 10_Wiki/Topics/Optimization-in-AI.md delete mode 100644 10_Wiki/Topics/Optimization.md delete mode 100644 10_Wiki/Topics/Ordinal-Data-Analysis.md delete mode 100644 10_Wiki/Topics/Organizational Psychology.md delete mode 100644 10_Wiki/Topics/Out-of-distribution-Detection.md delete mode 100644 10_Wiki/Topics/Outer Alignment vs Inner Alignment.md delete mode 100644 10_Wiki/Topics/Outlier-Detection-Techniques.md delete mode 100644 10_Wiki/Topics/Outside-Thinking.md delete mode 100644 10_Wiki/Topics/Overfitting-and-Underfitting.md delete mode 100644 10_Wiki/Topics/Overfitting.md delete mode 100644 10_Wiki/Topics/P-Reinforce-Template-Guide.md delete mode 100644 10_Wiki/Topics/P-Reinforce.md delete mode 100644 10_Wiki/Topics/PCA-and-Dimension-Reduction.md delete mode 100644 10_Wiki/Topics/PCGML-Frameworks.md delete mode 100644 10_Wiki/Topics/PDF-Format.md delete mode 100644 10_Wiki/Topics/PEFT (Parameter-Efficient Fine-Tuning).md delete mode 100644 10_Wiki/Topics/PID-Controllers-in-AI.md delete mode 100644 10_Wiki/Topics/PMI-Technique.md delete mode 100644 10_Wiki/Topics/POMDP.md delete mode 100644 10_Wiki/Topics/PageSpeed Insights.md delete mode 100644 10_Wiki/Topics/Papers Please (Bureaucratic Simulation).md delete mode 100644 10_Wiki/Topics/Papers-Please.md delete mode 100644 10_Wiki/Topics/Parallel-Computing-in-AI.md delete mode 100644 10_Wiki/Topics/Parallel-Computing.md delete mode 100644 10_Wiki/Topics/Parallel-Processing.md delete mode 100644 10_Wiki/Topics/Parameter-Efficiency-in-LLMs.md delete mode 100644 10_Wiki/Topics/Parameter-Efficient Fine-Tuning (PEFT).md delete mode 100644 10_Wiki/Topics/Parameter-Sharing.md delete mode 100644 10_Wiki/Topics/Pareto-Principle.md delete mode 100644 10_Wiki/Topics/Partial-Differential-Equations.md delete mode 100644 10_Wiki/Topics/Particle-Filter-Algorithms.md delete mode 100644 10_Wiki/Topics/Pattern-Recognition.md delete mode 100644 10_Wiki/Topics/Pedestrian-Modeling.md delete mode 100644 10_Wiki/Topics/Perceptrons-Foundations.md delete mode 100644 10_Wiki/Topics/Perceptual-Learning.md delete mode 100644 10_Wiki/Topics/Perceptual-Motor-Skills.md delete mode 100644 10_Wiki/Topics/Performance Management Systems.md delete mode 100644 10_Wiki/Topics/Performance Psychology.md delete mode 100644 10_Wiki/Topics/Performance-Metrics-in-AI.md delete mode 100644 10_Wiki/Topics/Periodization-Theory.md delete mode 100644 10_Wiki/Topics/Personal-Brain-Management.md delete mode 100644 10_Wiki/Topics/Personal-Information-Security.md delete mode 100644 10_Wiki/Topics/Personalization-Engines.md delete mode 100644 10_Wiki/Topics/Phase-Transitions-in-Learning.md delete mode 100644 10_Wiki/Topics/Philosophy.md delete mode 100644 10_Wiki/Topics/Physical-Intelligence.md delete mode 100644 10_Wiki/Topics/Physics-Informed Neural Networks (PINNs).md delete mode 100644 10_Wiki/Topics/Physics-informed-Neural-Networks.md delete mode 100644 10_Wiki/Topics/Physics.md delete mode 100644 10_Wiki/Topics/Pipeline-Parallelism.md delete mode 100644 10_Wiki/Topics/Pivot-Table-Analysis.md delete mode 100644 10_Wiki/Topics/Platform-Engineering.md delete mode 100644 10_Wiki/Topics/Player-Experience-Modeling.md delete mode 100644 10_Wiki/Topics/Player-Psyche-Profiling-Framework.md delete mode 100644 10_Wiki/Topics/Plutchiks-Wheel-of-Emotions.md delete mode 100644 10_Wiki/Topics/Poetic-Computation.md delete mode 100644 10_Wiki/Topics/Point-Cloud-Processing.md delete mode 100644 10_Wiki/Topics/Point-of-Sale.md delete mode 100644 10_Wiki/Topics/Policy-Gradient-Methods.md delete mode 100644 10_Wiki/Topics/Policy-Optimization.md delete mode 100644 10_Wiki/Topics/Policy-Surveillance.md delete mode 100644 10_Wiki/Topics/PolicyIQ.md delete mode 100644 10_Wiki/Topics/Polymorphism-in-Engine-Architecture.md delete mode 100644 10_Wiki/Topics/Pooling.md delete mode 100644 10_Wiki/Topics/Pose-Estimation.md delete mode 100644 10_Wiki/Topics/Positive-Reinforcement.md delete mode 100644 10_Wiki/Topics/Posterior-and-Prior-Probability.md delete mode 100644 10_Wiki/Topics/Poverty-Cycle-Dynamics.md delete mode 100644 10_Wiki/Topics/Poverty-Simulation.md delete mode 100644 10_Wiki/Topics/Practical-Cryptography.md delete mode 100644 10_Wiki/Topics/Pre-Mortem-Analysis.md delete mode 100644 10_Wiki/Topics/Pre-processing-Data-for-AI.md delete mode 100644 10_Wiki/Topics/Precision-Recall-Tradeoff.md delete mode 100644 10_Wiki/Topics/Precision-Recursion.md delete mode 100644 10_Wiki/Topics/Predictive-Analytics.md delete mode 100644 10_Wiki/Topics/Predictive-Coding.md delete mode 100644 10_Wiki/Topics/Prenatal-Neurology.md delete mode 100644 10_Wiki/Topics/Preserving-State-in-Procedural-Worlds.md delete mode 100644 10_Wiki/Topics/Principal-Component-Analysis.md delete mode 100644 10_Wiki/Topics/Principle-Component-Analysis.md delete mode 100644 10_Wiki/Topics/Principle-of-Least-Action.md delete mode 100644 10_Wiki/Topics/Principles of Structuralism (Linguistic).md delete mode 100644 10_Wiki/Topics/Principles-of-Architecture.md delete mode 100644 10_Wiki/Topics/Principles-of-Data-Connect.md delete mode 100644 10_Wiki/Topics/Principles-of-Structuralism.md delete mode 100644 10_Wiki/Topics/Principles.md delete mode 100644 10_Wiki/Topics/Prioritized-Experience-Replay.md delete mode 100644 10_Wiki/Topics/Prisoners-Dilemma-Models.md delete mode 100644 10_Wiki/Topics/Prisons-and-Self-Correction.md delete mode 100644 10_Wiki/Topics/Privacy-Preserving-AI.md delete mode 100644 10_Wiki/Topics/Probabilistic-Graphical-Models.md delete mode 100644 10_Wiki/Topics/Probabilistic-Reasoning.md delete mode 100644 10_Wiki/Topics/Probability Theory.md delete mode 100644 10_Wiki/Topics/Probability and Logic Fusion.md delete mode 100644 10_Wiki/Topics/Probability-Theory-Foundations.md delete mode 100644 10_Wiki/Topics/Problem-Solving.md delete mode 100644 10_Wiki/Topics/Procedural Content Generation via Machine Learning (PCGML).md delete mode 100644 10_Wiki/Topics/Procedural Narrative Generation.md delete mode 100644 10_Wiki/Topics/Procedural Rhetoric (In Gaming).md delete mode 100644 10_Wiki/Topics/Procedural-Architecture-Systems.md delete mode 100644 10_Wiki/Topics/Procedural-Knowledge.md delete mode 100644 10_Wiki/Topics/Procedural-Level-Geometry.md delete mode 100644 10_Wiki/Topics/Procedural-Rhetoric.md delete mode 100644 10_Wiki/Topics/Process-Automation-with-AI.md delete mode 100644 10_Wiki/Topics/Processing.md delete mode 100644 10_Wiki/Topics/Product-Led-Growth.md delete mode 100644 10_Wiki/Topics/Product-Management.md delete mode 100644 10_Wiki/Topics/Product-Marketing.md delete mode 100644 10_Wiki/Topics/Product-Thinking-in-AI.md delete mode 100644 10_Wiki/Topics/Productivity-Hacks-for-Devs.md delete mode 100644 10_Wiki/Topics/Profiling-and-Optimization.md delete mode 100644 10_Wiki/Topics/Progressive-Disclosure.md delete mode 100644 10_Wiki/Topics/Project-Management-Best-Practices.md delete mode 100644 10_Wiki/Topics/Project-Management.md delete mode 100644 10_Wiki/Topics/Prompt-Engineering-Foundations.md delete mode 100644 10_Wiki/Topics/Prompt-Engineering.md delete mode 100644 10_Wiki/Topics/Proprioception.md delete mode 100644 10_Wiki/Topics/Pros-Cons-Table.md delete mode 100644 10_Wiki/Topics/Protocols.md delete mode 100644 10_Wiki/Topics/Prototyping.md delete mode 100644 10_Wiki/Topics/Proximal Policy Optimization (PPO).md delete mode 100644 10_Wiki/Topics/Proximal-Policy-Optimization.md delete mode 100644 10_Wiki/Topics/Pruning-Techniques.md delete mode 100644 10_Wiki/Topics/Ps-Reinforce Policy Framework.md delete mode 100644 10_Wiki/Topics/Ps-Reinforce.md delete mode 100644 10_Wiki/Topics/Psychology & Behavior.md delete mode 100644 10_Wiki/Topics/Psychology-of-Learning.md delete mode 100644 10_Wiki/Topics/Psychology.md delete mode 100644 10_Wiki/Topics/Purpose.md delete mode 100644 10_Wiki/Topics/PyTorch-Foundations.md delete mode 100644 10_Wiki/Topics/PyTorch-Lightning.md delete mode 100644 10_Wiki/Topics/Python-for-Data-Science.md delete mode 100644 10_Wiki/Topics/Q-Learning Foundations.md delete mode 100644 10_Wiki/Topics/Quality Gates.md delete mode 100644 10_Wiki/Topics/Quality-Control.md delete mode 100644 10_Wiki/Topics/Quantitative Economics (수량경제학).md delete mode 100644 10_Wiki/Topics/Quantization-Foundations.md delete mode 100644 10_Wiki/Topics/Quantization.md delete mode 100644 10_Wiki/Topics/Quantum Computing (Intro).md delete mode 100644 10_Wiki/Topics/Quantum-Computing-for-AI.md delete mode 100644 10_Wiki/Topics/Quantum-Computing.md delete mode 100644 10_Wiki/Topics/Quantum-Machine-Learning.md delete mode 100644 10_Wiki/Topics/Query-Optimization.md delete mode 100644 10_Wiki/Topics/Queue-Management-Systems.md delete mode 100644 10_Wiki/Topics/Quick-Wins.md delete mode 100644 10_Wiki/Topics/RAG (검색 증강 생성).md delete mode 100644 10_Wiki/Topics/RAG-and-Document-Retrieval.md delete mode 100644 10_Wiki/Topics/RAG.md delete mode 100644 10_Wiki/Topics/RLAIF (AI 피드백 기반 강화학습).md delete mode 100644 10_Wiki/Topics/RLHF (인간 피드백 기반 강화 학습).md delete mode 100644 10_Wiki/Topics/RL_Neuroscience.md delete mode 100644 10_Wiki/Topics/RMSProp-Optimizer.md delete mode 100644 10_Wiki/Topics/ROC-AUC-Curves.md delete mode 100644 10_Wiki/Topics/ROUGE-Metrics.md delete mode 100644 10_Wiki/Topics/Random-Forest-Classifiers.md delete mode 100644 10_Wiki/Topics/Randomized-Algorithms.md delete mode 100644 10_Wiki/Topics/Ranking-Algorithms.md delete mode 100644 10_Wiki/Topics/Rapid-Prototyping.md delete mode 100644 10_Wiki/Topics/ReLU-Activation-Functions.md delete mode 100644 10_Wiki/Topics/React-Context-API.md delete mode 100644 10_Wiki/Topics/React-Error-Boundaries-and-Handling.md delete mode 100644 10_Wiki/Topics/React-Hooks.md delete mode 100644 10_Wiki/Topics/React_Clean_Code_Best_Practices.md delete mode 100644 10_Wiki/Topics/React_Hooks_Deep_Dive.md delete mode 100644 10_Wiki/Topics/React_Mental_Model.md delete mode 100644 10_Wiki/Topics/React_Performance_Optimization.md delete mode 100644 10_Wiki/Topics/React_State_Management_Strategy.md delete mode 100644 10_Wiki/Topics/React_Testing_Strategy.md delete mode 100644 10_Wiki/Topics/Reactive-Programming.md delete mode 100644 10_Wiki/Topics/Real-time-Data-Streaming.md delete mode 100644 10_Wiki/Topics/Real-time-Operation.md delete mode 100644 10_Wiki/Topics/Reasoning.md delete mode 100644 10_Wiki/Topics/Recommendation-Systems.md delete mode 100644 10_Wiki/Topics/Recording Academy (The Grammys).md delete mode 100644 10_Wiki/Topics/Refactoring-Legacy-React-Codebases.md delete mode 100644 10_Wiki/Topics/Reference-Management.md delete mode 100644 10_Wiki/Topics/Reference.md delete mode 100644 10_Wiki/Topics/Refinement.md delete mode 100644 10_Wiki/Topics/Reflection.md delete mode 100644 10_Wiki/Topics/Regression-Analysis-Foundations.md delete mode 100644 10_Wiki/Topics/Regularization-Strategies.md delete mode 100644 10_Wiki/Topics/Regularization-Techniques.md delete mode 100644 10_Wiki/Topics/Regularization.md delete mode 100644 10_Wiki/Topics/Reinforcement Learning (RL).md delete mode 100644 10_Wiki/Topics/Reinforcement Learning for Automated Playtesting.md delete mode 100644 10_Wiki/Topics/Reinforcement-Learning-from-Human-Feedback-RLHF.md delete mode 100644 10_Wiki/Topics/Reinforcement-Learning.md delete mode 100644 10_Wiki/Topics/Related-Work.md delete mode 100644 10_Wiki/Topics/Relational Algebra in Databases.md delete mode 100644 10_Wiki/Topics/Relational-Database.md delete mode 100644 10_Wiki/Topics/Relational-Databases.md delete mode 100644 10_Wiki/Topics/Relative-Positioning.md delete mode 100644 10_Wiki/Topics/Relevance-Feedback.md delete mode 100644 10_Wiki/Topics/Reliability.md delete mode 100644 10_Wiki/Topics/Reliability_Safety_First.md delete mode 100644 10_Wiki/Topics/Remote-Rehabilitation.md delete mode 100644 10_Wiki/Topics/Replenishment.md delete mode 100644 10_Wiki/Topics/Reports.md delete mode 100644 10_Wiki/Topics/Repository.md delete mode 100644 10_Wiki/Topics/Representation Theory.md delete mode 100644 10_Wiki/Topics/Representation-Learning.md delete mode 100644 10_Wiki/Topics/Requirements.md delete mode 100644 10_Wiki/Topics/ResNet-Architectures.md delete mode 100644 10_Wiki/Topics/Research-Framework.md delete mode 100644 10_Wiki/Topics/Research-Methodology.md delete mode 100644 10_Wiki/Topics/Research.md delete mode 100644 10_Wiki/Topics/Residual-Networks.md delete mode 100644 10_Wiki/Topics/Resilience.md delete mode 100644 10_Wiki/Topics/Resource-Allocation.md delete mode 100644 10_Wiki/Topics/Resource-Management.md delete mode 100644 10_Wiki/Topics/Restorative Justice.md delete mode 100644 10_Wiki/Topics/Retainers(유지 경로).md delete mode 100644 10_Wiki/Topics/Retaining Path.md delete mode 100644 10_Wiki/Topics/Retrieval-Augmented-Generation-RAG.md delete mode 100644 10_Wiki/Topics/Revenge-Cycle-Dynamics.md delete mode 100644 10_Wiki/Topics/Reward Hacking (보상 해킹).md delete mode 100644 10_Wiki/Topics/Reward Prediction Error.md delete mode 100644 10_Wiki/Topics/Reward-Shaping-in-RL.md delete mode 100644 10_Wiki/Topics/Ridge-Regression.md delete mode 100644 10_Wiki/Topics/Risk Management.md delete mode 100644 10_Wiki/Topics/Risk-Assessment-with-AI.md delete mode 100644 10_Wiki/Topics/Risk-Management.md delete mode 100644 10_Wiki/Topics/Risk-Orchestration.md delete mode 100644 10_Wiki/Topics/Roadmap.md delete mode 100644 10_Wiki/Topics/Robotics-Foundations.md delete mode 100644 10_Wiki/Topics/Robotics.md delete mode 100644 10_Wiki/Topics/Robust-Machine-Learning.md delete mode 100644 10_Wiki/Topics/Robustness.md delete mode 100644 10_Wiki/Topics/Role of Conflict in Narrative.md delete mode 100644 10_Wiki/Topics/Root-Cause-Analysis-RCA.md delete mode 100644 10_Wiki/Topics/Root-Mean-Square-Error.md delete mode 100644 10_Wiki/Topics/Roughness (그래픽 및 물리).md delete mode 100644 10_Wiki/Topics/Rule-based-Systems.md delete mode 100644 10_Wiki/Topics/SAR.md delete mode 100644 10_Wiki/Topics/SCM (Supply Chain Management).md delete mode 100644 10_Wiki/Topics/SDLC (소프트웨어 개발 수명 주기).md delete mode 100644 10_Wiki/Topics/SEO.md delete mode 100644 10_Wiki/Topics/SFT (Supervised Fine-Tuning).md delete mode 100644 10_Wiki/Topics/SME.md delete mode 100644 10_Wiki/Topics/SOTA.md delete mode 100644 10_Wiki/Topics/SOW.md delete mode 100644 10_Wiki/Topics/SPOF.md delete mode 100644 10_Wiki/Topics/SQL-Performance-Tuning.md delete mode 100644 10_Wiki/Topics/SRE.md delete mode 100644 10_Wiki/Topics/SaaS (Software as a Service).md delete mode 100644 10_Wiki/Topics/SaaS.md delete mode 100644 10_Wiki/Topics/Safety & Reliability.md delete mode 100644 10_Wiki/Topics/Sales-Strategy.md delete mode 100644 10_Wiki/Topics/Sampling-Techniques.md delete mode 100644 10_Wiki/Topics/Scalability-in-AI-Systems.md delete mode 100644 10_Wiki/Topics/Scalability.md delete mode 100644 10_Wiki/Topics/Scalable-Design-System-Governance.md delete mode 100644 10_Wiki/Topics/Scaling-Laws-for-LLMs.md delete mode 100644 10_Wiki/Topics/Scheduler-Design-in-ML.md delete mode 100644 10_Wiki/Topics/Schema-Design-for-NoSQL.md delete mode 100644 10_Wiki/Topics/Schema.md delete mode 100644 10_Wiki/Topics/Science of Failure.md delete mode 100644 10_Wiki/Topics/Scientific Communication.md delete mode 100644 10_Wiki/Topics/Scientific-Computing-with-Python.md delete mode 100644 10_Wiki/Topics/Scientific-Method.md delete mode 100644 10_Wiki/Topics/Scripts.md delete mode 100644 10_Wiki/Topics/Search-Engine-Optimization.md delete mode 100644 10_Wiki/Topics/Search-Methodology.md delete mode 100644 10_Wiki/Topics/Search-Optimization.md delete mode 100644 10_Wiki/Topics/Search-Space.md delete mode 100644 10_Wiki/Topics/Search-Strategy.md delete mode 100644 10_Wiki/Topics/Search.md delete mode 100644 10_Wiki/Topics/Secondary-Research.md delete mode 100644 10_Wiki/Topics/Secure-Multi-party-Computation.md delete mode 100644 10_Wiki/Topics/Security-Best-Practices.md delete mode 100644 10_Wiki/Topics/Security-Governance.md delete mode 100644 10_Wiki/Topics/Seed.md delete mode 100644 10_Wiki/Topics/Segmentsai.md delete mode 100644 10_Wiki/Topics/Self-Attention-Mechanisms.md delete mode 100644 10_Wiki/Topics/Self-Driving-Car-Foundations.md delete mode 100644 10_Wiki/Topics/Self-Play (자기 대결 기반 강화학습).md delete mode 100644 10_Wiki/Topics/Self-Supervised Learning (SSL).md delete mode 100644 10_Wiki/Topics/Self-Supervised-Learning.md delete mode 100644 10_Wiki/Topics/Semantic Grounding & Provenance.md delete mode 100644 10_Wiki/Topics/Semantic-HTML-Foundations.md delete mode 100644 10_Wiki/Topics/Semantic-Search-with-AI.md delete mode 100644 10_Wiki/Topics/Semantic-Search.md delete mode 100644 10_Wiki/Topics/Semantics & Ontology.md delete mode 100644 10_Wiki/Topics/Semgrep Assistant.md delete mode 100644 10_Wiki/Topics/Sensitivity-Analysis.md delete mode 100644 10_Wiki/Topics/Sensor-Fusion.md delete mode 100644 10_Wiki/Topics/Sentiment-Analysis-Models.md delete mode 100644 10_Wiki/Topics/Sentiment-Analysis.md delete mode 100644 10_Wiki/Topics/Separation_of_Concerns.md delete mode 100644 10_Wiki/Topics/Sequence-Modeling.md delete mode 100644 10_Wiki/Topics/Sequence-to-Sequence-Models.md delete mode 100644 10_Wiki/Topics/Serverless-Computing-for-AI.md delete mode 100644 10_Wiki/Topics/Service-oriented-Architecture.md delete mode 100644 10_Wiki/Topics/Shadowing-and-Observability.md delete mode 100644 10_Wiki/Topics/Shape-Feature-Extraction.md delete mode 100644 10_Wiki/Topics/Sharding-and-Partitioning.md delete mode 100644 10_Wiki/Topics/Shift.md delete mode 100644 10_Wiki/Topics/Signal in Noise.md delete mode 100644 10_Wiki/Topics/Signal-Processing-Foundations.md delete mode 100644 10_Wiki/Topics/Similarity-Metrics-in-AI.md delete mode 100644 10_Wiki/Topics/Similarity-Metrics.md delete mode 100644 10_Wiki/Topics/Simulated-Annealing.md delete mode 100644 10_Wiki/Topics/Simulation-Environments.md delete mode 100644 10_Wiki/Topics/Simulator Sickness Questionnaire (SSQ).md delete mode 100644 10_Wiki/Topics/Single_Source_of_Truth.md delete mode 100644 10_Wiki/Topics/Singular-Value-Decomposition.md delete mode 100644 10_Wiki/Topics/Six-Sigma-Methodologies.md delete mode 100644 10_Wiki/Topics/Skybound Protocol 코드리뷰.md delete mode 100644 10_Wiki/Topics/Slack-Bot-Development.md delete mode 100644 10_Wiki/Topics/Smart-Contract-Auditing.md delete mode 100644 10_Wiki/Topics/Snowflake-Data-Warehousing.md delete mode 100644 10_Wiki/Topics/Snyk Checkmarx Endor Labs 등 종합 애플리케이션 보안 플랫폼.md delete mode 100644 10_Wiki/Topics/Social Systems Theory.md delete mode 100644 10_Wiki/Topics/Social-Network-Analysis.md delete mode 100644 10_Wiki/Topics/Sociology of Knowledge.md delete mode 100644 10_Wiki/Topics/Soft Navigation.md delete mode 100644 10_Wiki/Topics/Soft-Skills-Development.md delete mode 100644 10_Wiki/Topics/Software-Architecture-Patterns.md delete mode 100644 10_Wiki/Topics/Software-Design-Principles.md delete mode 100644 10_Wiki/Topics/Solitude-Optimization.md delete mode 100644 10_Wiki/Topics/Solow Growth Model.md delete mode 100644 10_Wiki/Topics/Solution.md delete mode 100644 10_Wiki/Topics/SonarQube.md delete mode 100644 10_Wiki/Topics/Sorting.md delete mode 100644 10_Wiki/Topics/Sound Design Principles.md delete mode 100644 10_Wiki/Topics/Source-Control.md delete mode 100644 10_Wiki/Topics/Space-based-Architecture.md delete mode 100644 10_Wiki/Topics/Sparse-Data-Handling.md delete mode 100644 10_Wiki/Topics/Spatial-Data-Analysis.md delete mode 100644 10_Wiki/Topics/Specification.md delete mode 100644 10_Wiki/Topics/Spectral-Clustering.md delete mode 100644 10_Wiki/Topics/Speculative-Design.md delete mode 100644 10_Wiki/Topics/Speech-Recognition-Foundations.md delete mode 100644 10_Wiki/Topics/Speech-Synthesis.md delete mode 100644 10_Wiki/Topics/Spiking-Neural-Networks-SNNs.md delete mode 100644 10_Wiki/Topics/Stability vs Flexibility.md delete mode 100644 10_Wiki/Topics/Stacked-Generalization.md delete mode 100644 10_Wiki/Topics/Stages-of-Grief.md delete mode 100644 10_Wiki/Topics/Stakeholder.md delete mode 100644 10_Wiki/Topics/Standard-Deviation-and-Variance.md delete mode 100644 10_Wiki/Topics/Standard-Operating-Procedure.md delete mode 100644 10_Wiki/Topics/Standardization vs Innovation.md delete mode 100644 10_Wiki/Topics/Startup.md delete mode 100644 10_Wiki/Topics/State Space Model (SSM).md delete mode 100644 10_Wiki/Topics/State-Management-Architecture-and-Ownership.md delete mode 100644 10_Wiki/Topics/State-Management-Patterns.md delete mode 100644 10_Wiki/Topics/State-Space-Models.md delete mode 100644 10_Wiki/Topics/State-Space.md delete mode 100644 10_Wiki/Topics/State.md delete mode 100644 10_Wiki/Topics/Static-Site-Generation-with-Gatsby.md delete mode 100644 10_Wiki/Topics/Statistical-Analysis.md delete mode 100644 10_Wiki/Topics/Statistical-Hypothesis-Testing.md delete mode 100644 10_Wiki/Topics/Statistical-Learning-Theory.md delete mode 100644 10_Wiki/Topics/Statistical-Power.md delete mode 100644 10_Wiki/Topics/Statistics & Data Analysis.md delete mode 100644 10_Wiki/Topics/Statistics.md delete mode 100644 10_Wiki/Topics/Steel Division 시리즈.md delete mode 100644 10_Wiki/Topics/Stem-Analysis.md delete mode 100644 10_Wiki/Topics/Stochastic-Gradient-Descent-SGD.md delete mode 100644 10_Wiki/Topics/Stochastic-Gradient-Descent.md delete mode 100644 10_Wiki/Topics/Storage-Area-Networks.md delete mode 100644 10_Wiki/Topics/Storage.md delete mode 100644 10_Wiki/Topics/Straightening.md delete mode 100644 10_Wiki/Topics/Strategic-Alignment.md delete mode 100644 10_Wiki/Topics/Strategic-Ambiguity.md delete mode 100644 10_Wiki/Topics/Strategic-Planning-for-AI.md delete mode 100644 10_Wiki/Topics/Strategic-Planning.md delete mode 100644 10_Wiki/Topics/Strategic-Thinking.md delete mode 100644 10_Wiki/Topics/Strategy.md delete mode 100644 10_Wiki/Topics/Stream-Processing-Architectures.md delete mode 100644 10_Wiki/Topics/Structural Principles.md delete mode 100644 10_Wiki/Topics/Structural-Equation-Modeling.md delete mode 100644 10_Wiki/Topics/Structuralism.md delete mode 100644 10_Wiki/Topics/Style-Transfer-in-AI.md delete mode 100644 10_Wiki/Topics/Style-Transfer.md delete mode 100644 10_Wiki/Topics/Styling_Governance.md delete mode 100644 10_Wiki/Topics/Superficiality-Metrics.md delete mode 100644 10_Wiki/Topics/Supervised-Learning.md delete mode 100644 10_Wiki/Topics/Supply-Chain.md delete mode 100644 10_Wiki/Topics/Support-Vector-Machines.md delete mode 100644 10_Wiki/Topics/Support.md delete mode 100644 10_Wiki/Topics/Sustainability.md delete mode 100644 10_Wiki/Topics/Swarm Intelligence.md delete mode 100644 10_Wiki/Topics/Swarm-Intelligence.md delete mode 100644 10_Wiki/Topics/Symbolic-AI vs Connectionism.md delete mode 100644 10_Wiki/Topics/Symbols.md delete mode 100644 10_Wiki/Topics/Symmetric-Encryption.md delete mode 100644 10_Wiki/Topics/Symmetry-and-Invariance.md delete mode 100644 10_Wiki/Topics/Synergy.md delete mode 100644 10_Wiki/Topics/Synthesized Intelligence.md delete mode 100644 10_Wiki/Topics/Synthetic-Data-Generation.md delete mode 100644 10_Wiki/Topics/Synthetic-Data.md delete mode 100644 10_Wiki/Topics/System Prompt (시스템 프롬프트).md delete mode 100644 10_Wiki/Topics/System-Architecture-Design.md delete mode 100644 10_Wiki/Topics/System-Design for AI Scale.md delete mode 100644 10_Wiki/Topics/System-Design-Interview-Prep.md delete mode 100644 10_Wiki/Topics/System-Dynamics-Modeling.md delete mode 100644 10_Wiki/Topics/System-Theory.md delete mode 100644 10_Wiki/Topics/System_Debugging_Protocol.md delete mode 100644 10_Wiki/Topics/System_Protocol_Standard.md delete mode 100644 10_Wiki/Topics/Systemic_Simulation_Principles.md delete mode 100644 10_Wiki/Topics/Systems Thinking.md delete mode 100644 10_Wiki/Topics/Systems-Thinking.md delete mode 100644 10_Wiki/Topics/TDD.md delete mode 100644 10_Wiki/Topics/TS-Declaration-Files.md delete mode 100644 10_Wiki/Topics/Tableau-Data-Visualization.md delete mode 100644 10_Wiki/Topics/Target-Function-Profiling.md delete mode 100644 10_Wiki/Topics/Task-Management.md delete mode 100644 10_Wiki/Topics/Technical-Architecture.md delete mode 100644 10_Wiki/Topics/Technical-Debt.md delete mode 100644 10_Wiki/Topics/Temporal-Difference-Learning.md delete mode 100644 10_Wiki/Topics/TensorFlow-Foundations.md delete mode 100644 10_Wiki/Topics/Term-Frequency-Inverse-Document-Frequency.md delete mode 100644 10_Wiki/Topics/Terminology.md delete mode 100644 10_Wiki/Topics/Terraform-Infrastructure-as-Code.md delete mode 100644 10_Wiki/Topics/Test-Time Compute Scaling (추론 시간 계산 스케일링).md delete mode 100644 10_Wiki/Topics/Testing.md delete mode 100644 10_Wiki/Topics/Tetris_Project_Retrospective.md delete mode 100644 10_Wiki/Topics/Text-Mining.md delete mode 100644 10_Wiki/Topics/Text-to-Speech-Synthesis.md delete mode 100644 10_Wiki/Topics/The Evolution of Music Distribution.md delete mode 100644 10_Wiki/Topics/Theoretical-Computer-Science.md delete mode 100644 10_Wiki/Topics/Theory of Constraints (TOC).md delete mode 100644 10_Wiki/Topics/Theory-of-Mind (ToM) in AI.md delete mode 100644 10_Wiki/Topics/Thought-Architecture.md delete mode 100644 10_Wiki/Topics/Threejs WebGL 렌더링 최적화.md delete mode 100644 10_Wiki/Topics/Threejs WebGPURenderer.md delete mode 100644 10_Wiki/Topics/Threejs 성능 최적화.md delete mode 100644 10_Wiki/Topics/Time-Series-Analysis.md delete mode 100644 10_Wiki/Topics/Time-Step-Logic-in-Games.md delete mode 100644 10_Wiki/Topics/Tokenization-Strategies.md delete mode 100644 10_Wiki/Topics/Tool-Usage-Optimization.md delete mode 100644 10_Wiki/Topics/Toxicity-and-Bias-Mitigation.md delete mode 100644 10_Wiki/Topics/Transfer Learning.md delete mode 100644 10_Wiki/Topics/Transfer-Learning (전이 학습 기초).md delete mode 100644 10_Wiki/Topics/Transformer-Architecture.md delete mode 100644 10_Wiki/Topics/Transformers.md delete mode 100644 10_Wiki/Topics/Trustworthy-AI.md delete mode 100644 10_Wiki/Topics/Turing Test.md delete mode 100644 10_Wiki/Topics/Turing-Machine Foundations.md delete mode 100644 10_Wiki/Topics/Type 1 vs Type 2 Errors.md delete mode 100644 10_Wiki/Topics/TypeScript_Type_Safety.md delete mode 100644 10_Wiki/Topics/UX-Design-Principles.md delete mode 100644 10_Wiki/Topics/Uber-Base-Web-Design-System.md delete mode 100644 10_Wiki/Topics/Ultra-Efficiency.md delete mode 100644 10_Wiki/Topics/Uncertainty-Quantification.md delete mode 100644 10_Wiki/Topics/Unconscious Structuralism.md delete mode 100644 10_Wiki/Topics/Understanding Complex Systems.md delete mode 100644 10_Wiki/Topics/Universal Basic Income (UBI).md delete mode 100644 10_Wiki/Topics/Universal-Approximation-Theorem.md delete mode 100644 10_Wiki/Topics/Universal-Grammar.md delete mode 100644 10_Wiki/Topics/Unsupervised-Learning (비지도 학습 기초).md delete mode 100644 10_Wiki/Topics/Variational Autoencoders (VAE).md delete mode 100644 10_Wiki/Topics/Variational-Autoencoders-VAE.md delete mode 100644 10_Wiki/Topics/Vector-Database Selection.md delete mode 100644 10_Wiki/Topics/Victimhood-Narratives.md delete mode 100644 10_Wiki/Topics/Viral-Dynamics-and-Network-Effects.md delete mode 100644 10_Wiki/Topics/Visual-Effects-VFX-in-Games.md delete mode 100644 10_Wiki/Topics/Visual-Effects-VFX.md delete mode 100644 10_Wiki/Topics/Vocabulary-Expansion.md delete mode 100644 10_Wiki/Topics/Voice-Assistant-Architecture.md delete mode 100644 10_Wiki/Topics/WARNO 그래픽 엔진 업그레이드 프로젝트.md delete mode 100644 10_Wiki/Topics/WARNO 데이터 기반 밸런싱.md delete mode 100644 10_Wiki/Topics/WARNO 데이터 기반 설계.md delete mode 100644 10_Wiki/Topics/WARNO 멀티플레이어 및 경쟁 플레이 밸런스 패치.md delete mode 100644 10_Wiki/Topics/WARNO 모딩(Modding).md delete mode 100644 10_Wiki/Topics/WARNO 모딩.md delete mode 100644 10_Wiki/Topics/WARNO 밸런싱 및 사단 시스템.md delete mode 100644 10_Wiki/Topics/WARNO 사후 관리 (Post-Launch Management).md delete mode 100644 10_Wiki/Topics/WARNO 실시간 전술(Real-time Tactics) 및 Army General 캠페인.md delete mode 100644 10_Wiki/Topics/WARNO 전술 시뮬레이션 시스템.md delete mode 100644 10_Wiki/Topics/WARNO 전투 메커니즘 (Combat Mechanics).md delete mode 100644 10_Wiki/Topics/WARNO 커뮤니티 데이터 도구 생태계.md delete mode 100644 10_Wiki/Topics/WARNO 커뮤니티 모딩 생태계.md delete mode 100644 10_Wiki/Topics/WARNO-DATA Wiki.md delete mode 100644 10_Wiki/Topics/WARNO-DATA 프로젝트.md delete mode 100644 10_Wiki/Topics/WARNO.md delete mode 100644 10_Wiki/Topics/WME (Warno Mod Editor).md delete mode 100644 10_Wiki/Topics/War-Yes - Warno-Armory (커뮤니티 데이터 분석 도구).md delete mode 100644 10_Wiki/Topics/War-Yes 및 Warno-Armory 도구.md delete mode 100644 10_Wiki/Topics/Wargame 시리즈.md delete mode 100644 10_Wiki/Topics/Warno 데이터 기반 설계.md delete mode 100644 10_Wiki/Topics/Warno-Armory.md delete mode 100644 10_Wiki/Topics/Web Performance Optimization.md delete mode 100644 10_Wiki/Topics/Web-Rendering-Strategies-CSR-vs-SSR.md delete mode 100644 10_Wiki/Topics/Web3-and-AI-Integration.md delete mode 100644 10_Wiki/Topics/WebSplatter (3D Gaussian Splatting).md delete mode 100644 10_Wiki/Topics/WebWorker_Performance.md delete mode 100644 10_Wiki/Topics/What-is-AI.md delete mode 100644 10_Wiki/Topics/Wicked-Problems.md delete mode 100644 10_Wiki/Topics/Word-Representation.md delete mode 100644 10_Wiki/Topics/Work-Displacement.md delete mode 100644 10_Wiki/Topics/Workflow-Integrity.md delete mode 100644 10_Wiki/Topics/Working-Backwards.md delete mode 100644 10_Wiki/Topics/Zen-Pop.md delete mode 100644 10_Wiki/Topics/Zero Shot and Few Shot Learning.md delete mode 100644 10_Wiki/Topics/Zero-Shot-Chain-of-Thought.md delete mode 100644 10_Wiki/Topics/Zero-Shot-Learning.md delete mode 100644 10_Wiki/Topics/_agents/business/goal.md delete mode 100644 10_Wiki/Topics/_agents/business/prompt.md delete mode 100644 10_Wiki/Topics/_agents/ceo/prompt.md delete mode 100644 10_Wiki/Topics/_agents/designer/goal.md delete mode 100644 10_Wiki/Topics/_agents/designer/memory.md delete mode 100644 10_Wiki/Topics/_agents/designer/prompt.md delete mode 100644 10_Wiki/Topics/_agents/developer/goal.md delete mode 100644 10_Wiki/Topics/_agents/developer/prompt.md delete mode 100644 10_Wiki/Topics/_agents/editor/goal.md delete mode 100644 10_Wiki/Topics/_agents/editor/memory.md delete mode 100644 10_Wiki/Topics/_agents/editor/prompt.md delete mode 100644 10_Wiki/Topics/_agents/instagram/goal.md delete mode 100644 10_Wiki/Topics/_agents/instagram/memory.md delete mode 100644 10_Wiki/Topics/_agents/instagram/prompt.md delete mode 100644 10_Wiki/Topics/_agents/researcher/goal.md delete mode 100644 10_Wiki/Topics/_agents/researcher/prompt.md delete mode 100644 10_Wiki/Topics/_agents/secretary/goal.md delete mode 100644 10_Wiki/Topics/_agents/secretary/memory.md delete mode 100644 10_Wiki/Topics/_agents/secretary/prompt.md delete mode 100644 10_Wiki/Topics/_agents/writer/goal.md delete mode 100644 10_Wiki/Topics/_agents/writer/memory.md delete mode 100644 10_Wiki/Topics/_agents/writer/prompt.md delete mode 100644 10_Wiki/Topics/_agents/youtube/memory.md delete mode 100644 10_Wiki/Topics/_agents/youtube/prompt.md delete mode 100644 10_Wiki/Topics/_agents/youtube/tools/competitor_brief.md delete mode 100644 10_Wiki/Topics/_agents/youtube/tools/trend_sniper.md delete mode 100644 10_Wiki/Topics/_shared/goals.md delete mode 100644 10_Wiki/Topics/_shared/identity.md delete mode 100644 10_Wiki/Topics/_뇌와 팔다리의 분리_ - 관심사의 분리 (Separation of Concerns).md delete mode 100644 10_Wiki/Topics/agargaro의 오픈 소스 라이브러리.md delete mode 100644 10_Wiki/Topics/clinicjs.md delete mode 100644 10_Wiki/Topics/sessions/2026-04-30T07-07/business.md delete mode 100644 10_Wiki/Topics/sessions/2026-04-30T07-07/researcher.md delete mode 100644 10_Wiki/Topics/sessions/2026-04-30T07-07/secretary.md delete mode 100644 10_Wiki/Topics/sessions/2026-05-01T08-07/_brief.md delete mode 100644 10_Wiki/Topics/sessions/2026-05-01T08-07/_report.md delete mode 100644 10_Wiki/Topics/sessions/2026-05-01T08-07/secretary.md delete mode 100644 10_Wiki/Topics/sessions/2026-05-01T08-57/_brief.md delete mode 100644 10_Wiki/Topics/sessions/2026-05-01T10-17/_brief.md delete mode 100644 10_Wiki/Topics/sessions/2026-05-01T11-39/_brief.md delete mode 100644 10_Wiki/Topics/sessions/2026-05-01T11-39/_report.md delete mode 100644 10_Wiki/Topics/stochastic gradient descent.md delete mode 100644 10_Wiki/Topics/가용성 (Availability).md delete mode 100644 10_Wiki/Topics/가위바위보 상성 (Rock-paper-scissors principle).md delete mode 100644 10_Wiki/Topics/공급망 공격 (Supply Chain Attack).md delete mode 100644 10_Wiki/Topics/마이크로서비스 아키텍처 (Microservices Architecture).md delete mode 100644 10_Wiki/Topics/모딩 커뮤니티 도구 (War-Yes, Warno-Armory).md create mode 100644 10_Wiki/Topics/무제 1.canvas delete mode 100644 10_Wiki/Topics/벡터 데이터베이스 (Vector Database).md delete mode 100644 10_Wiki/Topics/보존 경로(Retaining Path).md delete mode 100644 10_Wiki/Topics/사단 시스템 (Division System).md delete mode 100644 10_Wiki/Topics/사단 편제표 (TO&E).md delete mode 100644 10_Wiki/Topics/사단(Division) 시스템.md delete mode 100644 10_Wiki/Topics/소음 역학 (Noise Dynamics).md delete mode 100644 10_Wiki/Topics/은신과 시야 매커니즘 (Stealth and Optics).md delete mode 100644 10_Wiki/Topics/장갑 관통 모델링(Armor Penetration Modeling).md delete mode 100644 10_Wiki/Topics/장갑 및 사거리 데이터 (Armor and Range Stats).md delete mode 100644 10_Wiki/Topics/정적 애플리케이션 보안 테스트 (SAST).md delete mode 100644 10_Wiki/Topics/제병협동 전술 (Combined Arms).md delete mode 100644 10_Wiki/Topics/탄도학 및 명중률 알고리즘 (Ballistics and Accuracy Algorithms).md delete mode 100644 10_Wiki/Topics_Art/Aesthetics/.gitkeep delete mode 100644 10_Wiki/Topics_Art/Modeling/.gitkeep delete mode 100644 10_Wiki/Topics_Art/UI_UX_Assets/.gitkeep delete mode 100644 10_Wiki/Topics_Art/Visual_Effects/.gitkeep delete mode 100644 10_Wiki/Topics_Biz/Business_Strategy/.gitkeep delete mode 100644 10_Wiki/Topics_Biz/Market_Research/.gitkeep delete mode 100644 10_Wiki/Topics_Biz/Operations/.gitkeep delete mode 100644 10_Wiki/Topics_Biz/Partnerships/.gitkeep delete mode 100644 10_Wiki/Topics_Blog/Content_Strategy/.gitkeep delete mode 100644 10_Wiki/Topics_Blog/External_Media/.gitkeep delete mode 100644 10_Wiki/Topics_Blog/Post_Drafts/.gitkeep delete mode 100644 10_Wiki/Topics_Blog/Storytelling/.gitkeep delete mode 100644 10_Wiki/Topics_GD/Balancing/.gitkeep delete mode 100644 10_Wiki/Topics_GD/Core_Systems/.gitkeep delete mode 100644 10_Wiki/Topics_GD/Level_Design/.gitkeep delete mode 100644 10_Wiki/Topics_GD/Pay-to-win.md delete mode 100644 10_Wiki/Topics_GD/Reward Prediciton Error.md delete mode 100644 10_Wiki/Topics_GD/Reward Prediction Error (상태 예측 오류).md delete mode 100644 10_Wiki/Topics_GD/Self-Correction Mechanisms.md delete mode 100644 10_Wiki/Topics_GD/Self-Correction.md delete mode 100644 10_Wiki/Topics_GD/Stability.md delete mode 100644 10_Wiki/Topics_GD/Supervised Fine-Tuning (SFT).md delete mode 100644 10_Wiki/Topics_GD/The Grammys.md delete mode 100644 10_Wiki/Topics_GD/UX_Scenarios/.gitkeep delete mode 100644 20_Meta/Policy.md diff --git a/00_Raw/.gitkeep b/00_Raw/.gitkeep deleted file mode 100644 index e69de29b..00000000 diff --git a/01_Archive/.gitkeep b/01_Archive/.gitkeep deleted file mode 100644 index e69de29b..00000000 diff --git a/01_Archive/2026-04-20/.gitkeep b/01_Archive/2026-04-20/.gitkeep deleted file mode 100644 index e69de29b..00000000 diff --git a/01_Archive/2026-04-20/01_WebWorker-performance-optimization.md b/01_Archive/2026-04-20/01_WebWorker-performance-optimization.md deleted file mode 100644 index a2d6c91d..00000000 --- a/01_Archive/2026-04-20/01_WebWorker-performance-optimization.md +++ /dev/null @@ -1,20 +0,0 @@ ---- -# 💡 Lesson Learned: Web Worker를 이용한 고성능 아키텍처 설계 (Performance) - -## 🎯 문제 상황 (The Problem) -테트리스 게임과 같이 **매우 높은 빈도(High Frequency)**로 상태 변화가 발생하는 실시간 애플리케이션을 React의 메인 스레드에서 처리할 경우, UI 업데이트와 물리 계산이 충돌하여 **프레임 드롭(Jank)** 현상이나 성능 저하가 발생했습니다. - -## 🔬 근본 원인 (Root Cause) -게임 엔진 로직은 CPU를 매우 많이 사용합니다. 이 무거운 계산을 메인 스레드에서 수행하면, 브라우저의 UI 업데이트 루프(`requestAnimationFrame`)와 충돌하여 사용자에게 부드럽지 않은 경험(Poor UX)을 제공하게 됩니다. - -## ✅ 해결책 (The Solution) -**Web Worker**를 사용하여 게임 엔진 로직 전체를 **메인 스레드에서 완전히 분리(Isolate)** 했습니다. -* **원리:** Web Worker는 별도의 백그라운드 스레드에서 동작하므로, 아무리 복잡한 계산을 해도 메인 스레드의 UI 렌더링에는 영향을 주지 않습니다. - -## 💡 교훈 (Lesson Learned) -> **"성능 병목 현상은 종종 '스레딩(Threading)'의 문제이다."** -> 실시간으로 높은 연산량이 요구되는 모든 시스템은, 반드시 Web Worker 또는 별도의 백그라운드 프로세스로 로직을 분리하여 처리해야 합니다. - -## 🔗 관련 키워드 -`Web Worker`, `Concurrency`, `High-Frequency Updates`, `Performance Optimization` ---- \ No newline at end of file diff --git a/01_Archive/2026-04-20/02_StateManagement-single-source-of-truth.md b/01_Archive/2026-04-20/02_StateManagement-single-source-of-truth.md deleted file mode 100644 index 904c55a0..00000000 --- a/01_Archive/2026-04-20/02_StateManagement-single-source-of-truth.md +++ /dev/null @@ -1,19 +0,0 @@ ---- -# 💡 Lesson Learned: 상태 관리의 단일 진실 공급원 원칙 (Data Consistency) - -## 🎯 문제 상황 (The Problem) -테트리스 게임은 '현재 보드 상태'와 '움직이는 블록 위치'라는 두 가지 핵심 데이터를 가지고 있습니다. 이 데이터들이 여러 곳에서 독립적으로 업데이트될 위험이 있었습니다. 만약 A 부분에서 값을 바꾸고, B 부분에서 같은 값을 다르게 계산한다면 **데이터 불일치(Inconsistency)**가 발생합니다. - -## 🔬 근본 원인 (Root Cause) -시스템의 핵심 상태가 분산되어 관리되고 있었기 때문입니다. 여러 컴포넌트와 로직이 각자 '진실'이라고 믿는 데이터를 가지고 충돌할 가능성이 높았습니다. - -## ✅ 해결책 (The Solution) -**Redux/Zustand 패턴을 차용하여 모든 게임의 핵심 상태(State)**를 `src/TetrisGame.jsx` 컴포넌트가 관리하는 **단일 지점(Single Source of Truth)**으로 만들었습니다. 모든 데이터 변경은 이 중앙 저장소를 통해 이루어지게 했습니다. - -## 💡 교훈 (Lesson Learned) -> **"상태는 오직 한 곳에서만 정의하고, 모든 로직은 그 상태를 읽고 쓰는 방식으로 동작해야 한다."** -> 복잡한 시스템을 설계할 때, 핵심 데이터의 흐름(Data Flow)과 책임 범위(Responsibility)를 명확히 분리하는 것이 가장 중요합니다. - -## 🔗 관련 키워드 -`Single Source of Truth`, `Redux Pattern`, `State Management`, `Predictable State` ---- \ No newline at end of file diff --git a/01_Archive/2026-04-20/03_Architecture-design-principle.md b/01_Archive/2026-04-20/03_Architecture-design-principle.md deleted file mode 100644 index 957942cd..00000000 --- a/01_Archive/2026-04-20/03_Architecture-design-principle.md +++ /dev/null @@ -1,22 +0,0 @@ ---- -# 💡 Lesson Learned: 시스템 아키텍처의 중요성 (The Need for Abstraction) - -## 🎯 문제 상황 (The Problem) -이번 프로젝트를 진행하면서, 코드를 짜는 것이 아니라 '어떤 구조로 짤지'가 가장 어려웠습니다. 이는 단순히 기술적인 문제가 아닌 **설계 패턴(Design Pattern)**과 관련된 문제입니다. - -## 🔬 근본 원인 (Root Cause) -모든 로직을 한 파일에 때려 넣으려는 유혹에 빠지는 것, 즉 '스파게티 코드'를 만들 위험이 가장 큰 문제였습니다. 모든 것을 한곳에서 처리하려 했기 때문에 유지보수성과 확장성이 0에 수렴했습니다. - -## ✅ 해결책 (The Solution) -**아키텍처적 분리 원칙(Separation of Concerns, SoC)**을 적용하여 코드를 다음과 같이 역할별로 나눴습니다: -1. **게임 규칙:** `gameWorker.js` (논리 엔진) -2. **상태 관리:** `TetrisGame.jsx` (데이터의 출입구) -3. **렌더링:** React 컴포넌트 (화면에 보여주는 역할만 수행) - -## 💡 교훈 (Lesson Learned) -> **"시스템을 구성할 때는 '책임 분리(Separation of Concerns)'를 최우선 원칙으로 삼아야 한다."** -> 기능이 복잡해질수록, 코드는 반드시 경계가 명확한 모듈들로 분리되어야 합니다. - -## 🔗 관련 키워드 -`Separation of Concerns`, `Modular Design`, `Microservices Pattern` ---- \ No newline at end of file diff --git a/01_Archive/2026-04-20/04_execution-environment-management.md b/01_Archive/2026-04-20/04_execution-environment-management.md deleted file mode 100644 index 4f30447c..00000000 --- a/01_Archive/2026-04-20/04_execution-environment-management.md +++ /dev/null @@ -1,22 +0,0 @@ ---- -# 💡 Lesson Learned: 개발 환경 및 실행 프로세스 관리 (DevOps & DevOps) - -## 🎯 문제 상황 (The Problem) -이번 프로젝트는 단순히 코드를 짜고 끝나는 것이 아니라, **'어떻게 이 코드를 구동시킬 수 있는가?'**라는 물리적 절차의 중요성을 깨달았습니다. (오류 코드: `npm audit`, `index.html` 누락, 권한 오류 등) - -## 🔬 근본 원인 (Root Cause) -개발자는 종종 **'논리적 완성도(Logical Completion)'에만 집중**하고, 프로젝트를 실행하는 데 필요한 **물리적인 설정 파일(Configuration)**과 **운영체제 레벨의 환경 변수/권한** 관리에 소홀해지기 쉽습니다. - -## ✅ 해결책 (The Solution) -프로젝트 시작 시점에 다음 절차를 반드시 거쳐야 함을 확립했습니다: -1. `npm install`: 필요한 모든 패키지를 설치한다. -2. 환경 설정 확인: `public/index.html` 등 필수 진입점이 존재하는지 확인한다. -3. 권한 확보: 운영체제 레벨에서 스크립트 실행 권한(Execution Policy)을 확보한다. - -## 💡 교훈 (Lesson Learned) -> **"코딩 능력만큼이나 중요한 것은 '운영 환경에 대한 이해'와 '체계적인 개발 프로세스 확립'이다."** -> 프로젝트 관리자는 항상 이 세 가지 단계를 점검해야 합니다. - -## 🔗 관련 키워드 -`DevOps`, `CI/CD Pipeline`, `Execution Policy`, `Build Environment` ---- \ No newline at end of file diff --git a/01_Archive/2026-04-20/05_simulation-design-principles.md b/01_Archive/2026-04-20/05_simulation-design-principles.md deleted file mode 100644 index e3615026..00000000 --- a/01_Archive/2026-04-20/05_simulation-design-principles.md +++ /dev/null @@ -1,19 +0,0 @@ ---- -# 💡 Lesson Learned: 시스템 시뮬레이션의 핵심 원리 (Simulation Design) - -## 🎯 문제 상황 (The Problem) -테트리스는 단순한 게임이 아니라, **물리 법칙(Physics)**과 **규칙 기반의 상태 변화**가 작동하는 작은 시뮬레이터였습니다. 이 경험을 통해 '시뮬레이션을 어떻게 설계해야 하는지'에 대한 깊은 이해를 얻었습니다. - -## 🔬 근본 원인 (Root Cause) -단순히 UI로 그리는 것에만 집중하면, 시스템이 **규칙(Ruleset)**과 **물리 법칙(Physics Law)**을 따르는 '가상 세계'의 느낌을 놓치기 쉽습니다. - -## ✅ 해결책 (The Solution) -게임 로직을 `gameWorker.js`에 완전히 분리하여, 모든 변화를 수학적 함수(`checkCollision`, `movePiece`)로 처리하고 그 결과를 상태(State)에 반영했습니다. 이는 곧 **"규칙이 물리 법칙처럼 작동하는 시스템"** 설계의 성공적인 예시입니다. - -## 💡 교훈 (Lesson Learned) -> **"모든 시뮬레이션은 '물리적 규칙'을 수학적으로 정의하고, 그 규칙을 절대 우회할 수 없도록 강제해야 한다."** -> 이를 통해 우리는 단순한 게임을 넘어, 자율주행이나 물리 엔진에 적용 가능한 고수준의 시스템 모델링 능력을 갖추게 되었습니다. - -## 🔗 관련 키워드 -`Simulation Design`, `Physics Engine`, `Ruleset Enforcement`, `Systemic Modeling` ---- \ No newline at end of file diff --git a/01_Archive/2026-04-20/2026-04-15.md b/01_Archive/2026-04-20/2026-04-15.md index 1a5b4941..32c8df12 100644 --- a/01_Archive/2026-04-20/2026-04-15.md +++ b/01_Archive/2026-04-20/2026-04-15.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-D3F316 -category: "[[10_Wiki/💡 Topics/General Knowledge]]" +category: "10_Wiki/💡 Topics/General Knowledge" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 2026-04-15" --- -# [[2026-04-15]] +# [[2026-04-15|2026-04-15]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - 2026-04-15" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/2026-04-15.md]] +- Raw Source: 00_Raw/2026-04-20/2026-04-15.md --- diff --git a/01_Archive/2026-04-20/20k skinned instances demo.md b/01_Archive/2026-04-20/20k skinned instances demo.md index 98468692..e9935273 100644 --- a/01_Archive/2026-04-20/20k skinned instances demo.md +++ b/01_Archive/2026-04-20/20k skinned instances demo.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-EB3F3C -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 20k skinned instances demo" --- -# [[20k skinned instances demo]] +# [[20k skinned instances demo|20k skinned instances demo]] ## 📌 한 줄 통찰 (The Karpathy Summary) > '20k skinned instances demo'는 Three.js 기반의 오픈 소스 라이브러리인 InstancedMesh2를 활용하여 20,000개의 개별적인 스킨드 인스턴스(Skinned instances)를 동시에 렌더링하는 성능 최적화 데모입니다 [1, 2]. 이 데모는 모바일 기기에서도 3,000개의 인스턴스를 원활하게 구동할 수 있도록 설계되었습니다 [2]. 프러스텀 컬링, 거리 기반 애니메이션 프레임 조절, 다중 LOD(Level of Detail) 생성 등 다양한 최적화 기법을 적용하여 단 5번의 드로우 콜만으로 렌더링을 처리하는 것이 특징입니다 [2, 3]. @@ -29,11 +29,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 20k skinned instances demo" - **정책 변화:** AI 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[InstancedMesh2]], [[Frustum Culling]], [[Level of Detail (LOD)]], [[Skinned Mesh]], [[Draw Call]] -- **Projects/Contexts:** [[three.js]] +- **Related Topics:** [[InstancedMesh2|InstancedMesh2]], [[Frustum Culling|Frustum Culling]], [[Level of Detail (LOD)|Level of Detail (LOD)]], [[SkinnedMesh|Skinned Mesh]], [[Draw Call|Draw Call]] +- **Projects/Contexts:** [[Threejs 성능 최적화|three.js]] - **Contradictions/Notes:** 본 텍스처(Bone texture)의 부분 업데이트(Partial texture updates) 기능은 PC 환경에서 60FPS를 달성하는 데 도움이 될 수 있는 최적화 기법이지만, 모바일 기기와 파이어폭스(Mozilla Firefox) 브라우저에서는 이중 버퍼링(Double buffering) 부재로 인해 오히려 속도가 느려지는 문제가 있어 본 데모에서는 비활성화된 상태로 제공되었습니다 [2, 7]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/20k skinned instances demo.md]] +- Raw Source: 00_Raw/2026-04-20/20k skinned instances demo.md --- diff --git a/01_Archive/2026-04-20/3D Gaussian Splatting (3DGS).md b/01_Archive/2026-04-20/3D Gaussian Splatting (3DGS).md index 807a59d4..99822300 100644 --- a/01_Archive/2026-04-20/3D Gaussian Splatting (3DGS).md +++ b/01_Archive/2026-04-20/3D Gaussian Splatting (3DGS).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AI-AC09DA -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.95 tags: [] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Batch 9 - Wikified 3D Gaussian Splatting (3DGS)" --- -# [[3D Gaussian Splatting (3DGS)]] +# [[3D Gaussian Splatting (3DGS)|3D Gaussian Splatting (3DGS)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 3D Gaussian Splatting (3DGS)은 3D 스플랫(splat)들로 구성된 명시적 표현을 사용하여 고품질의 실시간 렌더링을 구현하는 혁신적인 기법이다 [1, 2]. 각 3D 가우시안은 중심 위치, 3D 공분산 행렬, 최대 불투명도, 그리고 구면 조화(Spherical Harmonics) 계수를 활용한 시점 종속적 색상으로 정의된다 [2]. 올바른 렌더링을 위해 카메라로부터의 거리를 기준으로 가우시안들을 뒤에서 앞으로 정렬(depth sorting)하고 알파 블렌딩(alpha-blending)하는 과정이 필수적이며 [3, 4], 미분 가능한 특성 덕분에 브라우저 환경에서 고품질 재구성 및 생성적 3D 모델링에 활발히 응용되고 있다 [1]. @@ -27,11 +27,11 @@ github_commit: "[P-Reinforce] Batch 9 - Wikified 3D Gaussian Splatting (3DGS)" - **정책 변화:** Graphics & Performance 카테고리의 지식 연결망 강화를 위한 표준 위키화 적용. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[WebGPU]], [[WebGL]], [[Compute Shader]] -- **Projects/Contexts:** [[WebSplatter]], [[CesiumJS]] +- **Related Topics:** [[WebGPU|WebGPU]], [[WebGL|WebGL]], [[Compute Shader|Compute Shader]] +- **Projects/Contexts:** WebSplatter, [[CesiumJS|CesiumJS]] - **Contradictions/Notes:** WebGL 기반의 기존 3DGS 구현은 정렬 작업을 CPU에 의존하므로 동기화 병목과 프레임 지연이 발생하지만, WebGPU 기반의 WebSplatter는 파이프라인 전체를 GPU에서 병렬 연산함으로써 기존 웹 뷰어 대비 최대 4.5배의 렌더링 속도 향상과 낮은 메모리 소모를 달성한다 [6, 8, 15, 20]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/3D Gaussian Splatting (3DGS).md]] +- Raw Source: 00_Raw/2026-04-20/3D Gaussian Splatting (3DGS).md --- diff --git a/01_Archive/2026-04-20/3D Web-based HMI.md b/01_Archive/2026-04-20/3D Web-based HMI.md index 59378a78..c464b291 100644 --- a/01_Archive/2026-04-20/3D Web-based HMI.md +++ b/01_Archive/2026-04-20/3D Web-based HMI.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AI-074AE7 -category: "[[10_Wiki/💡 Topics/Automation & Industry]]" +category: "10_Wiki/💡 Topics/Automation & Industry" confidence_score: 0.95 tags: [] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Batch 9 - Wikified 3D Web-based HMI" --- -# [[3D Web-based HMI]] +# [[3D Web-based HMI|3D Web-based HMI]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 3D Web-based HMI는 사용자가 기계 또는 자동화 시스템과 통신할 수 있도록 지원하는 소프트웨어 인터페이스로, 주로 SCADA(Supervisory Control and Data Acquisition) 시스템의 기기 모니터링 및 제어를 위한 디스플레이 역할을 수행합니다 [1, 2]. 기존 HMI 시스템의 특정 플랫폼 종속성과 별도의 소프트웨어 설치 요구라는 한계를 극복하기 위해 제안되었습니다 [3]. WebGL과 WebSocket 기술을 활용하여 사용자는 별도의 소프트웨어 설치 없이 모든 플랫폼의 HTML5 웹 브라우저에서 실시간 데이터 통신 및 3D 그래픽 렌더링을 경험할 수 있습니다 [3-5]. @@ -24,11 +24,11 @@ github_commit: "[P-Reinforce] Batch 9 - Wikified 3D Web-based HMI" - **정책 변화:** Automation & Industry 카테고리의 지식 연결망 강화를 위한 표준 위키화 적용. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[SCADA]], [[WebGL]], [[Three.js]], [[WebSocket]], [[Frame Time Latency]] -- **Projects/Contexts:** [[Genesis64 상용 제품과의 웹 기반 3D 렌더링 성능 벤치마크]] +- **Related Topics:** [[SCADA|SCADA]], [[WebGL|WebGL]], [[Three.js|Three.js]], WebSocket, Frame Time Latency +- **Projects/Contexts:** Genesis64 상용 제품과의 웹 기반 3D 렌더링 성능 벤치마크 - **Contradictions/Notes:** 3D Web-based HMI는 프레임의 부드러움(일관성)에서는 상용 제품보다 뛰어나지만, 전체 프로세스 소요 시간 중 약 96% 이상이 객체를 생성하는 실행 시간(Execution Time)이 아닌 렌더링 시간(Rendering Time)에 집중되어 있습니다. 이는 향후 렌더링 코드 최적화를 통해 성능을 더욱 개선해야 할 주요 병목 지점임을 시사합니다 [9, 14]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/3D Web-based HMI.md]] +- Raw Source: 00_Raw/2026-04-20/3D Web-based HMI.md --- diff --git a/01_Archive/2026-04-20/3D_Gaussian_Splatting.md b/01_Archive/2026-04-20/3D_Gaussian_Splatting.md index 7d839564..8e795fb0 100644 --- a/01_Archive/2026-04-20/3D_Gaussian_Splatting.md +++ b/01_Archive/2026-04-20/3D_Gaussian_Splatting.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-3DGS-001 -category: "[[10_Wiki/💡 Topics/Graphics]]" +category: "10_Wiki/💡 Topics/Graphics" confidence_score: 0.95 tags: [graphics, rendering, ai] last_reinforced: 2026-04-20 github_commit: "initial-reinforce" --- -# [[3D Gaussian Splatting (3DGS)]] +# [[3D Gaussian Splatting (3DGS)|3D Gaussian Splatting (3DGS)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 포인트 클라우드를 넘어서 공간을 가속화된 가우시안 타원체로 표현함으로써 실시간 렌더링의 새로운 지평을 열다. @@ -24,6 +24,6 @@ github_commit: "initial-reinforce" - **정책 변화:** 렌더링 효율성(w1) 가중치를 높게 평가하여 그래픽스 카테고리의 최상단 지식으로 배치. ## 🔗 지식 연결 (Graph) -- **Parent:** [[10_Wiki/💡 Topics/Graphics]] -- **Related:** [[NeRF]], [[Point-Cloud]], [[Radiance-Fields]] -- **Raw Source:** [[00_Raw/2026-04-20/3D Gaussian Splatting (3DGS).md]] +- **Parent:** 10_Wiki/💡 Topics/Graphics +- **Related:** NeRF, Point-Cloud, Radiance-Fields +- **Raw Source:** 00_Raw/2026-04-20/3D Gaussian Splatting (3DGS).md diff --git a/01_Archive/2026-04-20/3D_Web_HMI.md b/01_Archive/2026-04-20/3D_Web_HMI.md index 8bf448ac..2c360027 100644 --- a/01_Archive/2026-04-20/3D_Web_HMI.md +++ b/01_Archive/2026-04-20/3D_Web_HMI.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-HMI-001 -category: "[[10_Wiki/💡 Topics/Graphics]]" +category: "10_Wiki/💡 Topics/Graphics" confidence_score: 0.90 tags: [web, hmi, interface, 3d] last_reinforced: 2026-04-20 github_commit: "initial-reinforce" --- -# [[3D Web-based HMI]] +# [[3D Web-based HMI|3D Web-based HMI]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 산업용 제어 인터페이스를 브라우저 환경에서 3D로 시각화하여 정보의 직관성과 조작성을 극대화하다. @@ -24,6 +24,6 @@ github_commit: "initial-reinforce" - **정책 변화:** 구조적 연결성(w2) 관점에서 디지털 트윈 아키텍처와 통합 분석 필요성 제기. ## 🔗 지식 연결 (Graph) -- **Parent:** [[10_Wiki/💡 Topics/Graphics]] -- **Related:** [[Three.js]], [[Digital-Twin]], [[SCADA]] -- **Raw Source:** [[00_Raw/2026-04-20/3D Web-based HMI.md]] +- **Parent:** 10_Wiki/💡 Topics/Graphics +- **Related:** [[Three.js|Three.js]], [[Digital_Twin|Digital-Twin]], [[SCADA|SCADA]] +- **Raw Source:** 00_Raw/2026-04-20/3D Web-based HMI.md diff --git a/01_Archive/2026-04-20/ABA(Applied Behavior Analysis).md b/01_Archive/2026-04-20/ABA(Applied Behavior Analysis).md index db282d35..de678ec5 100644 --- a/01_Archive/2026-04-20/ABA(Applied Behavior Analysis).md +++ b/01_Archive/2026-04-20/ABA(Applied Behavior Analysis).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AI-91A92D -category: "[[10_Wiki/💡 Topics/Psychology & Behavior]]" +category: "10_Wiki/💡 Topics/Psychology & Behavior" confidence_score: 0.95 tags: [] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Batch 9 - Wikified ABA(Applied Behavior Analysis)" --- -# [[ABA(Applied Behavior Analysis)]] +# [[ABA(Applied Behavior Analysis)|ABA(Applied Behavior Analysis)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Batch 9 - Wikified ABA(Applied Behavior Analysis)" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/ABA(Applied Behavior Analysis).md]] +- Raw Source: 00_Raw/2026-04-20/ABA(Applied Behavior Analysis).md --- diff --git a/01_Archive/2026-04-20/ABA.md b/01_Archive/2026-04-20/ABA.md index 9bf286ef..07ab169a 100644 --- a/01_Archive/2026-04-20/ABA.md +++ b/01_Archive/2026-04-20/ABA.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-ABA-001 -category: "[[10_Wiki/💡 Topics/Psychology]]" +category: "10_Wiki/💡 Topics/Psychology" confidence_score: 0.88 tags: [psychology, behavior, intervention] last_reinforced: 2026-04-20 github_commit: "initial-reinforce" --- -# [[ABA (Applied Behavior Analysis)]] +# [[ABA(Applied Behavior Analysis)|ABA (Applied Behavior Analysis)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 행동의 원인을 환경과의 상호작용에서 찾아내고 이를 체계적으로 수정하여 삶의 질을 높이는 과학적 접근법. @@ -24,6 +24,6 @@ github_commit: "initial-reinforce" - **정책 변화:** 사용자 만족도(w3) 피드백에 따라 윤리적 고려 사항 링크 비중 강화. ## 🔗 지식 연결 (Graph) -- **Parent:** [[10_Wiki/💡 Topics/Psychology]] -- **Related:** [[Operant-Conditioning]], [[Neurodiversity-Affirming]], [[FBA]] -- **Raw Source:** [[00_Raw/2026-04-20/ABA(Applied Behavior Analysis).md]] +- **Parent:** 10_Wiki/💡 Topics/Psychology +- **Related:** [[Operant Conditioning|Operant-Conditioning]], Neurodiversity-Affirming, FBA +- **Raw Source:** 00_Raw/2026-04-20/ABA(Applied Behavior Analysis).md diff --git a/01_Archive/2026-04-20/ACL-Injury-Prevention-Protocols.md b/01_Archive/2026-04-20/ACL-Injury-Prevention-Protocols.md index c76baa6f..37724f7b 100644 --- a/01_Archive/2026-04-20/ACL-Injury-Prevention-Protocols.md +++ b/01_Archive/2026-04-20/ACL-Injury-Prevention-Protocols.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AI-CEA4CC -category: "[[10_Wiki/💡 Topics/Health & Science]]" +category: "10_Wiki/💡 Topics/Health & Science" confidence_score: 0.95 tags: [] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Batch 9 - Wikified ACL-Injury-Prevention-Protocols" --- -# [[ACL-Injury-Prevention-Protocols]] +# [[ACL-Injury-Prevention-Protocols|ACL-Injury-Prevention-Protocols]] ## 📌 한 줄 통찰 (The Karpathy Summary) > @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Batch 9 - Wikified ACL-Injury-Prevention-Protocols ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/ACL-Injury-Prevention-Protocols.md]] +- Raw Source: 00_Raw/2026-04-20/ACL-Injury-Prevention-Protocols.md --- diff --git a/01_Archive/2026-04-20/ACL_Prevention.md b/01_Archive/2026-04-20/ACL_Prevention.md index a4921dad..fdd954c6 100644 --- a/01_Archive/2026-04-20/ACL_Prevention.md +++ b/01_Archive/2026-04-20/ACL_Prevention.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-HEALTH-001 -category: "[[10_Wiki/💡 Topics/Health]]" +category: "10_Wiki/💡 Topics/Health" confidence_score: 0.89 tags: [health, sports, injury, prevention] last_reinforced: 2026-04-20 github_commit: "batch-reinforce-01" --- -# [[ACL Injury Prevention Protocols]] +# [[ACL-Injury-Prevention-Protocols|ACL Injury Prevention Protocols]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 전방십자인대 부상 위험을 최소화하기 위해 바이오메카닉 분석과 신경근 훈련을 결합한 과학적 예방 체계. @@ -24,6 +24,6 @@ github_commit: "batch-reinforce-01" - **정책 변화:** 지식 연결성(w2) 관점에서 바이오메카닉과 스포츠 심리학의 연계성 강화. ## 🔗 지식 연결 (Graph) -- **Parent:** [[10_Wiki/💡 Topics/Health]] -- **Related:** [[Neuromuscular-Control]], [[Sports-Science]], [[Proprioception]] -- **Raw Source:** [[00_Raw/2026-04-20/ACL-Injury-Prevention-Protocols.md]] +- **Parent:** 10_Wiki/💡 Topics/Health +- **Related:** [[Neuromuscular-Control|Neuromuscular-Control]], Sports-Science, [[Proprioception|Proprioception]] +- **Raw Source:** 00_Raw/2026-04-20/ACL-Injury-Prevention-Protocols.md diff --git a/01_Archive/2026-04-20/AI Connect LLM Tool.md b/01_Archive/2026-04-20/AI Connect LLM Tool.md index a2eb2126..20a933c2 100644 --- a/01_Archive/2026-04-20/AI Connect LLM Tool.md +++ b/01_Archive/2026-04-20/AI Connect LLM Tool.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-92F236 -category: "[[10_Wiki/💡 Topics/AI & Tools]]" +category: "10_Wiki/💡 Topics/AI & Tools" confidence_score: 0.95 tags: [] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Batch 10 - Wikified AI Connect LLM Tool" --- -# [[AI Connect LLM Tool]] +# [[AI Connect LLM Tool|AI Connect LLM Tool]] ## 📌 한 줄 통찰 (The Karpathy Summary) > **Connect AI**는 100% 로컬 및 오프라인 환경에서 작동하는 VS Code 전용 프리미엄 AI 코딩 에이전트입니다. 외부 서버 연결 없이 사용자의 하드웨어(Ollama/LM Studio)를 직접 활용하여 파일 생성, 편집, 터미널 명령 실행 및 개인 지식 기반(Second Brain) 연동을 지원합니다. @@ -20,8 +20,8 @@ github_commit: "[P-Reinforce] Batch 10 - Wikified AI Connect LLM Tool" - **정책 변화:** AI & Tools 분야의 체계적 지식 자산화 진행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Ollama]], [[LM Studio]], [[VS Code Extension Development]], [[Agentic AI]] -- **Projects/Contexts:** [[Connect-AI-Lab]], [[EZERAI Infrastructure]] +- **Related Topics:** Ollama, LM Studio, VS Code Extension Development, Agentic AI +- **Projects/Contexts:** Connect-AI-Lab, EZERAI Infrastructure - **Contradictions/Notes:** - **통합 구조:** 현재 프로젝트는 모든 로직(UI, 통신, 에이전트)이 `extension.ts` 하나에 집중된 모놀리식 구조를 가지고 있어, 향후 대규모 기능 추가 시 모듈화가 권장됩니다. - **보안:** 모든 작업이 로컬에서 이루어지므로 기업 보안 환경에 매우 적합하나, `run_command` 실행 시 사용자의 최종 확인 절차가 보완될 필요가 있습니다. @@ -35,5 +35,5 @@ github_commit: "[P-Reinforce] Batch 10 - Wikified AI Connect LLM Tool" # 🕵️ 프로젝트 코드 리뷰 리포트 `/Volumes/Data/project/Antigravity/local_module/resource` 프로젝트에 대한 상세 코드 리뷰 결과입니다. -- Raw Source: [[00_Raw/2026-04-20/AI Connect LLM Tool.md]] +- Raw Source: 00_Raw/2026-04-20/AI Connect LLM Tool.md --- diff --git a/01_Archive/2026-04-20/AI Safety (AI 안전).md b/01_Archive/2026-04-20/AI Safety (AI 안전).md index ed459347..a1784713 100644 --- a/01_Archive/2026-04-20/AI Safety (AI 안전).md +++ b/01_Archive/2026-04-20/AI Safety (AI 안전).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-2BB419 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - AI Safety (AI 안전)" --- -# [[AI Safety (AI 안전)]] +# [[AI Safety (AI 안전)|AI Safety (AI 안전)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - AI Safety (AI 안전)" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/AI Safety (AI 안전).md]] +- Raw Source: 00_Raw/2026-04-20/AI Safety (AI 안전).md --- diff --git a/01_Archive/2026-04-20/AI 거버넌스 정책(AI Usage Policy).md b/01_Archive/2026-04-20/AI 거버넌스 정책(AI Usage Policy).md index 113acb81..15311b2b 100644 --- a/01_Archive/2026-04-20/AI 거버넌스 정책(AI Usage Policy).md +++ b/01_Archive/2026-04-20/AI 거버넌스 정책(AI Usage Policy).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-0C244E -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - AI 거버넌스 정책(AI Usage Policy)" --- -# [[AI 거버넌스 정책(AI Usage Policy)]] +# [[AI 거버넌스 정책(AI Usage Policy)|AI 거버넌스 정책(AI Usage Policy)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -32,11 +32,11 @@ github_commit: "[P-Reinforce] Continuous Worker - AI 거버넌스 정책(AI Usag - **정책 변화:** AI 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Human-in-the-loop]], [[데이터 프라이버시(Data Privacy)]], [[ISO 42001]], [[NIST AI RMF]] -- **Projects/Contexts:** [[조직 내 안전한 AI 도입 및 기업 거버넌스(Enterprise AI Adoption and Governance)]] +- **Related Topics:** Human-in-the-loop, 데이터 프라이버시(Data Privacy), ISO 42001, NIST AI RMF +- **Projects/Contexts:** 조직 내 안전한 AI 도입 및 기업 거버넌스(Enterprise AI Adoption and Governance) - **Contradictions/Notes:** 소스에 따르면 AI 정책 문서는 초기에 IT나 법무 부서 단독으로 작성하고 소유하기 쉬우나, 이러한 방식은 병목 현상을 유발할 수 있으며 실제 성공적인 장기 정착을 위해서는 직원과의 관계 및 변경 관리 전문성을 갖춘 HR 부서를 비롯한 교차 기능적인 소유권(Cross-functional ownership)이 필수적이라고 강조합니다 [18, 19, 26]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/AI 거버넌스 정책(AI Usage Policy).md]] +- Raw Source: 00_Raw/2026-04-20/AI 거버넌스 정책(AI Usage Policy).md --- diff --git a/01_Archive/2026-04-20/AI 생성 코드 검증(AI Code Assurance).md b/01_Archive/2026-04-20/AI 생성 코드 검증(AI Code Assurance).md index e5ba6e97..50ee60f0 100644 --- a/01_Archive/2026-04-20/AI 생성 코드 검증(AI Code Assurance).md +++ b/01_Archive/2026-04-20/AI 생성 코드 검증(AI Code Assurance).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-254BE9 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - AI 생성 코드 검증(AI Code Assurance)" --- -# [[AI 생성 코드 검증(AI Code Assurance)]] +# [[AI 생성 코드 검증(AI Code Assurance)|AI 생성 코드 검증(AI Code Assurance)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > AI Code Assurance(AI 생성 코드 검증)는 AI가 생성하거나 지원한 코드로 인해 발생할 수 있는 고유한 품질 및 보안 위험을 해결하기 위해 설계된 워크플로우이자 검증 프로세스입니다 [1]. 이를 통해 조직은 AI가 작성한 코드가 프로덕션 환경에 배포되기 전에 엄격한 보안, 신뢰성 및 품질 표준을 충족하는지 확인할 수 있습니다 [1, 2]. 주로 정적 애플리케이션 보안 테스트(SAST)와 자동화된 코드 리뷰를 활용하여 결함과 취약점을 조기에 식별하고 일관된 표준을 강제합니다 [2, 3]. @@ -29,11 +29,11 @@ github_commit: "[P-Reinforce] Continuous Worker - AI 생성 코드 검증(AI Cod - **정책 변화:** AI 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Static Application Security Testing (SAST)]], [[Model Context Protocol (MCP)]], [[Automated Code Review]] -- **Projects/Contexts:** [[SonarQube Server]], [[SonarQube Cloud]] +- **Related Topics:** [[Static Application Security Testing (SAST)|Static Application Security Testing (SAST)]], [[Model Context Protocol (MCP)|Model Context Protocol (MCP)]], Automated Code Review +- **Projects/Contexts:** SonarQube Server, SonarQube Cloud - **Contradictions/Notes:** 소스에 따르면 AI 어시스턴트가 생성하는 코드는 본질적으로 일관성이 없고 예측하기 어려울 수 있지만, 이에 적용되는 정적 코드 분석 기술은 '결정론적(deterministic)'이므로 AI 코드의 불확실성을 극복하고 신뢰할 수 있는 독립적인 검증을 제공할 수 있다고 강조합니다 [4]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/AI 생성 코드 검증(AI Code Assurance).md]] +- Raw Source: 00_Raw/2026-04-20/AI 생성 코드 검증(AI Code Assurance).md --- diff --git a/01_Archive/2026-04-20/AI 에이전트 (AI Agent).md b/01_Archive/2026-04-20/AI 에이전트 (AI Agent).md index 25e274b0..3969d1fa 100644 --- a/01_Archive/2026-04-20/AI 에이전트 (AI Agent).md +++ b/01_Archive/2026-04-20/AI 에이전트 (AI Agent).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-CA155B -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - AI 에이전트 (AI Agent)" --- -# [[AI 에이전트 (AI Agent)]] +# [[AI 에이전트 (AI Agent)|AI 에이전트 (AI Agent)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - AI 에이전트 (AI Agent)" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/AI 에이전트 (AI Agent).md]] +- Raw Source: 00_Raw/2026-04-20/AI 에이전트 (AI Agent).md --- diff --git a/01_Archive/2026-04-20/AI 코드 리뷰 및 보안 취약점 점검(DevSecOps).md b/01_Archive/2026-04-20/AI 코드 리뷰 및 보안 취약점 점검(DevSecOps).md index 2100bee7..f333ea80 100644 --- a/01_Archive/2026-04-20/AI 코드 리뷰 및 보안 취약점 점검(DevSecOps).md +++ b/01_Archive/2026-04-20/AI 코드 리뷰 및 보안 취약점 점검(DevSecOps).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-4DB2F8 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - AI 코드 리뷰 및 보안 취약점 점검(DevSecOps)" --- -# [[AI 코드 리뷰 및 보안 취약점 점검(DevSecOps)]] +# [[AI 코드 리뷰 및 보안 취약점 점검(DevSecOps)|AI 코드 리뷰 및 보안 취약점 점검(DevSecOps)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > AI 코드 리뷰 및 보안 취약점 점검(DevSecOps)은 소프트웨어 개발 수명 주기(SDLC)의 초기 단계에 AI 기반의 자동화된 정적 분석(SAST)과 인간의 수동 리뷰를 결합하여 코드의 품질과 보안을 선제적으로 확보하는 프로세스입니다 [1, 2]. 개발자는 IDE 내부나 CI/CD 파이프라인의 Pull Request(PR) 단계에서 실시간으로 버그, 로직 결함, 보안 취약점(예: 인젝션, 민감 정보 노출)을 식별하고 수정할 수 있습니다 [3-6]. 결과적으로 기계적이고 반복적인 코드 스타일 검사 및 패턴 기반 취약점 탐지는 AI에 위임하고, 인간은 아키텍처 결정이나 도메인 종속적인 비즈니스 로직을 검토하는 '하이브리드' 방식을 통해 개발 속도와 보안성의 균형을 맞춥니다 [2, 7, 8]. @@ -30,11 +30,11 @@ github_commit: "[P-Reinforce] Continuous Worker - AI 코드 리뷰 및 보안 - **정책 변화:** AI 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[정적 애플리케이션 보안 테스트(SAST)]], [[시프트 레프트(Shift-Left)]], [[하이브리드 코드 리뷰]] -- **Projects/Contexts:** [[CI/CD 파이프라인 통합 및 Git 훅(Hooks)]] +- **Related Topics:** [[정적 애플리케이션 보안 테스트(SAST)|정적 애플리케이션 보안 테스트(SAST)]], [[시프트 레프트(Shift-Left)|시프트 레프트(Shift-Left)]], [[하이브리드 코드 리뷰|하이브리드 코드 리뷰]] +- **Projects/Contexts:** [[CI_CD 파이프라인 통합 및 Git 훅(Hooks)|CI/CD 파이프라인 통합 및 Git 훅(Hooks)]] - **Contradictions/Notes:** 자동화 도구를 적극적으로 옹호하는 입장에서는 AI 기반 코드 리뷰와 수정안 자동 생성 기능이 개발자의 업무를 크게 대체하고 생산성을 극대화한다고 주장하지만, 보안 전문가 및 실제 성능 벤치마크 결과(Augment Code 등)에 따르면 자동화 도구는 여전히 30~60%의 오탐률을 보이며 실제 취약점의 약 22%를 놓치는 근본적 사각지대가 존재하므로, 아키텍처 설계와 비즈니스 로직에는 기계가 아닌 인간의 수동 판단이 필수 불가결하다고 반박합니다. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/AI 코드 리뷰 및 보안 취약점 점검(DevSecOps).md]] +- Raw Source: 00_Raw/2026-04-20/AI 코드 리뷰 및 보안 취약점 점검(DevSecOps).md --- diff --git a/01_Archive/2026-04-20/AI 코드 리뷰.md b/01_Archive/2026-04-20/AI 코드 리뷰.md index 1418edb5..d6e55a67 100644 --- a/01_Archive/2026-04-20/AI 코드 리뷰.md +++ b/01_Archive/2026-04-20/AI 코드 리뷰.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-76F9E4 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - AI 코드 리뷰" --- -# [[AI 코드 리뷰]] +# [[AI 코드 리뷰|AI 코드 리뷰]] ## 📌 한 줄 통찰 (The Karpathy Summary) > AI 코드 리뷰는 인공지능 에이전트나 머신러닝(ML) 기반의 정적 분석 도구(SAST)를 활용하여 소스 코드의 결함, 보안 취약점, 스타일 위반 및 로직 오류를 식별하는 자동화 프로세스입니다 [1-3]. IDE, CI/CD 파이프라인, 풀 리퀘스트(PR) 등 개발 워크플로우에 통합되어 개발자에게 실시간에 가까운 피드백과 자동 수정(Auto-fix) 제안을 제공합니다 [2, 4-8]. 이를 통해 코드 리뷰의 대기 시간을 줄이고 일관된 품질 표준을 강제할 수 있지만, 아키텍처 의도나 비즈니스 로직의 문맥을 깊이 이해하는 데는 한계가 있어 인간 검토자와의 하이브리드 접근 방식이 필수적으로 요구됩니다 [5, 9-12]. @@ -23,11 +23,11 @@ github_commit: "[P-Reinforce] Continuous Worker - AI 코드 리뷰" - **정책 변화:** AI 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[SAST]], [[풀 리퀘스트(Pull Request)]], [[DevSecOps]] -- **Projects/Contexts:** [[SonarQube]], [[Snyk Code]], [[GitHub Advanced Security]], [[Corgea]] +- **Related Topics:** [[SAST|SAST]], [[풀 리퀘스트 (Pull Request)|풀 리퀘스트(Pull Request)]], [[DevSecOps|DevSecOps]] +- **Projects/Contexts:** [[SonarQube|SonarQube]], Snyk Code, GitHub Advanced Security, [[Corgea|Corgea]] - **Contradictions/Notes:** AI 코드 리뷰 도구의 도입만으로는 배포 성능이나 품질이 보장되지 않는다는 점에 유의해야 합니다. 맹목적인 도구 도입과 높은 AI 사용률에도 불구하고 실제 PR 처리 시간이나 재작업 비율은 개선되지 않을 수 있으므로, 결과(DORA 지표 등)에 기반한 관리가 중요합니다 [35-37]. 또한 일부 AI 네이티브 도구들은 오탐률을 혁신적으로 줄였다고 주장하지만(예: Corgea 5% 미만, Veracode 1.1% 미만), 근본적으로 어떠한 도구도 오탐을 완벽히 제거할 수는 없으므로 인간의 검토와 검증 과정이 반드시 수반되어야 합니다 [38-40]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/AI 코드 리뷰.md]] +- Raw Source: 00_Raw/2026-04-20/AI 코드 리뷰.md --- diff --git a/01_Archive/2026-04-20/AI-Driven Narrative Systems.md b/01_Archive/2026-04-20/AI-Driven Narrative Systems.md index 639fdde5..a69f5e1c 100644 --- a/01_Archive/2026-04-20/AI-Driven Narrative Systems.md +++ b/01_Archive/2026-04-20/AI-Driven Narrative Systems.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-8DB819 -category: "[[10_Wiki/💡 Topics/AI & Narrative]]" +category: "10_Wiki/💡 Topics/AI & Narrative" confidence_score: 0.95 tags: [] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Batch 10 - Wikified AI-Driven Narrative Systems" --- -# [[AI-Driven Narrative Systems]] +# [[AI-Driven Narrative Systems|AI-Driven Narrative Systems]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 핵심 내용 요약 예정 @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Batch 10 - Wikified AI-Driven Narrative Systems" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/AI-Driven Narrative Systems.md]] +- Raw Source: 00_Raw/2026-04-20/AI-Driven Narrative Systems.md --- diff --git a/01_Archive/2026-04-20/AI.md b/01_Archive/2026-04-20/AI.md deleted file mode 100644 index e69de29b..00000000 diff --git a/01_Archive/2026-04-20/AI와 기계에게 검열 맡기기_ - 정적 분석 툴 (ESLint Prettier)).md b/01_Archive/2026-04-20/AI와 기계에게 검열 맡기기_ - 정적 분석 툴 (ESLint Prettier)).md index 1b011d53..6b546352 100644 --- a/01_Archive/2026-04-20/AI와 기계에게 검열 맡기기_ - 정적 분석 툴 (ESLint Prettier)).md +++ b/01_Archive/2026-04-20/AI와 기계에게 검열 맡기기_ - 정적 분석 툴 (ESLint Prettier)).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-37563B -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - AI와 기계에게 검열 맡기기_ - 정적 분석 툴 (ESLint Prettier))" --- -# [[AI와 기계에게 검열 맡기기_ - 정적 분석 툴 (ESLint Prettier))]] +# [[AI와 기계에게 검열 맡기기_ - 정적 분석 툴 (ESLint Prettier))|AI와 기계에게 검열 맡기기_ - 정적 분석 툴 (ESLint Prettier))]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 현대 소프트웨어 개발에서는 주관적이고 반복적인 코드 평가 작업을 ESLint, Prettier와 같은 결정론적 도구와 AI 기반 에이전트(기계)에게 위임하여 코드를 자동으로 '검열'하는 구조를 갖추고 있습니다 [1]. Linter인 ESLint는 추상 구문 트리(AST)를 분석해 문법적 오류와 잠재적 버그를 식별하며, Formatter인 Prettier는 줄 바꿈이나 들여쓰기 등 시각적 일관성을 강제합니다 [2]. 나아가 단순한 패턴 매칭을 넘어 LLM 기반의 AI 정적 분석 도구(SAST)를 도입함으로써 문맥을 이해하고 복잡한 취약점을 분석하는 '에이전트적 거버넌스'로 진화하고 있습니다 [3, 4]. @@ -34,11 +34,11 @@ github_commit: "[P-Reinforce] Continuous Worker - AI와 기계에게 검열 맡 - **정책 변화:** AI 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[SAST (정적 애플리케이션 보안 테스트)]], [[AST (추상 구문 트리)]], [[Husky & lint-staged]] -- **Projects/Contexts:** [[Git Pre-commit 훅을 활용한 개발 워크플로우 자동화]], [[AI 코드 리뷰 및 보안 취약점 점검(DevSecOps)]] +- **Related Topics:** [[SAST (정적 애플리케이션 보안 테스트)|SAST (정적 애플리케이션 보안 테스트)]], [[AST (추상 구문 트리)|AST (추상 구문 트리)]], [[Husky & lint-staged|Husky & lint-staged]] +- **Projects/Contexts:** [[Git Pre-commit 훅을 활용한 개발 워크플로우 자동화|Git Pre-commit 훅을 활용한 개발 워크플로우 자동화]], [[AI 코드 리뷰 및 보안 취약점 점검(DevSecOps)|AI 코드 리뷰 및 보안 취약점 점검(DevSecOps)]] - **Contradictions/Notes:** 소스는 기계 주도의 검열이 개발 생산성과 코드 품질을 높인다고 긍정적으로 평가하면서도, 동시에 AI 모델이 실제 취약점의 일부를 놓치고 개발자의 비판적 사고를 약화시켜 표면적 문제 해결에 집착하는 '녹색 체크마크 증후군'을 초래할 수 있다는 역설적 한계를 분명히 지적합니다 [23, 24, 26]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/AI와 기계에게 검열 맡기기_ - 정적 분석 툴 (ESLint & Prettier)).md]] +- Raw Source: 00_Raw/2026-04-20/AI와 기계에게 검열 맡기기_ - 정적 분석 툴 (ESLint & Prettier)).md --- diff --git a/01_Archive/2026-04-20/AI와 기계에게 검열 맡기기_ - 정적 분석 툴 (ESLint & Prettier)).md b/01_Archive/2026-04-20/AI와 기계에게 검열 맡기기_ - 정적 분석 툴 (ESLint & Prettier)).md index 4db57a08..30becf05 100644 --- a/01_Archive/2026-04-20/AI와 기계에게 검열 맡기기_ - 정적 분석 툴 (ESLint & Prettier)).md +++ b/01_Archive/2026-04-20/AI와 기계에게 검열 맡기기_ - 정적 분석 툴 (ESLint & Prettier)).md @@ -1,4 +1,4 @@ -# [[AI와 기계에게 검열 맡기기" - 정적 분석 툴 (ESLint & Prettier))]] +# [[AI와 기계에게 검열 맡기기_ - 정적 분석 툴 (ESLint Prettier))|AI와 기계에게 검열 맡기기" - 정적 분석 툴 (ESLint & Prettier))]] ## 📌 Brief Summary 현대 소프트웨어 개발에서는 주관적이고 반복적인 코드 평가 작업을 ESLint, Prettier와 같은 결정론적 도구와 AI 기반 에이전트(기계)에게 위임하여 코드를 자동으로 '검열'하는 구조를 갖추고 있습니다 [1]. Linter인 ESLint는 추상 구문 트리(AST)를 분석해 문법적 오류와 잠재적 버그를 식별하며, Formatter인 Prettier는 줄 바꿈이나 들여쓰기 등 시각적 일관성을 강제합니다 [2]. 나아가 단순한 패턴 매칭을 넘어 LLM 기반의 AI 정적 분석 도구(SAST)를 도입함으로써 문맥을 이해하고 복잡한 취약점을 분석하는 '에이전트적 거버넌스'로 진화하고 있습니다 [3, 4]. @@ -21,8 +21,8 @@ * 하지만 자동화에 과도하게 의존할 경우, 개발자의 비판적 사고 근육이 퇴화하고 자동화 도구의 검사만 통과하면 된다고 여기는 '녹색 체크마크 증후군(Green Check Mark Syndrome)'을 유발할 수 있습니다 [23, 24]. 또한 AI 도구 역시 전체 취약점의 약 22%를 놓치는 사각지대가 존재하므로, 아키텍처 설계와 도메인 비즈니스 로직 등 고위험 검토에는 여전히 인간의 판단(Human-in-the-loop)이 필수적입니다 [24-26]. ## 🔗 Knowledge Connections -- **Related Topics:** [[SAST (정적 애플리케이션 보안 테스트)]], [[AST (추상 구문 트리)]], [[Husky & lint-staged]] -- **Projects/Contexts:** [[Git Pre-commit 훅을 활용한 개발 워크플로우 자동화]], [[AI 코드 리뷰 및 보안 취약점 점검(DevSecOps)]] +- **Related Topics:** [[SAST (정적 애플리케이션 보안 테스트)|SAST (정적 애플리케이션 보안 테스트)]], [[AST (추상 구문 트리)|AST (추상 구문 트리)]], [[Husky & lint-staged|Husky & lint-staged]] +- **Projects/Contexts:** [[Git Pre-commit 훅을 활용한 개발 워크플로우 자동화|Git Pre-commit 훅을 활용한 개발 워크플로우 자동화]], [[AI 코드 리뷰 및 보안 취약점 점검(DevSecOps)|AI 코드 리뷰 및 보안 취약점 점검(DevSecOps)]] - **Contradictions/Notes:** 소스는 기계 주도의 검열이 개발 생산성과 코드 품질을 높인다고 긍정적으로 평가하면서도, 동시에 AI 모델이 실제 취약점의 일부를 놓치고 개발자의 비판적 사고를 약화시켜 표면적 문제 해결에 집착하는 '녹색 체크마크 증후군'을 초래할 수 있다는 역설적 한계를 분명히 지적합니다 [23, 24, 26]. --- diff --git a/01_Archive/2026-04-20/ANGLE (Almost Native Graphics Layer Engine).md b/01_Archive/2026-04-20/ANGLE (Almost Native Graphics Layer Engine).md index 3235896a..64bb4870 100644 --- a/01_Archive/2026-04-20/ANGLE (Almost Native Graphics Layer Engine).md +++ b/01_Archive/2026-04-20/ANGLE (Almost Native Graphics Layer Engine).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-46B173 -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - ANGLE (Almost Native Graphics Layer Engine)" --- -# [[ANGLE (Almost Native Graphics Layer Engine)]] +# [[ANGLE (Almost Native Graphics Layer Engine)|ANGLE (Almost Native Graphics Layer Engine)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > ANGLE(Almost Native Graphics Layer Engine)은 주로 Windows 플랫폼의 웹 브라우저(Chrome, Firefox, Opera 등)에서 사용되는 그래픽 명령어 변환기입니다. 이 엔진은 WebGL의 OpenGL ES 호출을 Direct3D 11 또는 12 명령으로 변환하는 역할을 수행합니다 [1, 2]. 고도로 최적화되어 있지만, 변환 과정에서 각 드로우 콜(Draw call)마다 고정된 마이크로 레이턴시(Micro-latency)를 유발하는 성능적 특징이 있습니다 [1, 3]. @@ -23,11 +23,11 @@ github_commit: "[P-Reinforce] Continuous Worker - ANGLE (Almost Native Graphics - **정책 변화:** Graphics & Performance 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[WebGL]], [[OpenGL ES]], [[Direct3D]], [[Micro-latency]], [[Draw Call]] -- **Projects/Contexts:** [[Chrome]], [[Firefox]], [[Opera]] +- **Related Topics:** [[WebGL|WebGL]], [[OpenGL ES|OpenGL ES]], [[Direct3D|Direct3D]], [[Micro-latency|Micro-latency]], [[Draw Call|Draw Call]] +- **Projects/Contexts:** [[Chrome|Chrome]], [[Firefox|Firefox]], [[Opera|Opera]] - **Contradictions/Notes:** ANGLE은 브라우저에서 원활한 그래픽 처리를 위해 도입된 고도로 최적화된 변환기이지만, 드로우 콜이 많은 환경에서는 역설적이게도 이 변환 작업 자체가 누적되어 CPU 병목을 일으키는 주된 원인이 됩니다 [3]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/ANGLE (Almost Native Graphics Layer Engine).md]] +- Raw Source: 00_Raw/2026-04-20/ANGLE (Almost Native Graphics Layer Engine).md --- diff --git a/01_Archive/2026-04-20/ANGLE.md b/01_Archive/2026-04-20/ANGLE.md index 483050f8..40f6f4ce 100644 --- a/01_Archive/2026-04-20/ANGLE.md +++ b/01_Archive/2026-04-20/ANGLE.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-26A7F5 -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.95 tags: [] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Mega Batch - Wikified ANGLE" --- -# [[ANGLE]] +# [[ANGLE|ANGLE]] ## 📌 한 줄 통찰 (The Karpathy Summary) > ANGLE(Almost Native Graphics Layer Engine)은 Windows 플랫폼에서 WebGL(OpenGL ES) 명령을 Direct3D 11 또는 12로 변환해 주는 변환기(translator)입니다 [1, 2]. Chrome, Firefox, Opera와 같은 브라우저에서 널리 사용되며, 고도로 최적화되어 있음에도 불구하고 그래픽 파이프라인의 명령 제출(command submission) 단계에서 마이크로 레이턴시(micro-latency)를 유발하는 주요 원인 중 하나로 작용합니다 [1-3]. @@ -23,11 +23,11 @@ github_commit: "[P-Reinforce] Mega Batch - Wikified ANGLE" - **정책 변화:** Graphics & Performance 카테고리의 전문성 확보 및 링크 밀도 최적화. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[WebGL]], [[OpenGL ES]], [[Direct3D]], [[Micro-latency]] -- **Projects/Contexts:** [[Web Graphics Pipelines]] +- **Related Topics:** [[WebGL|WebGL]], [[OpenGL ES|OpenGL ES]], [[Direct3D|Direct3D]], [[Micro-latency|Micro-latency]] +- **Projects/Contexts:** Web Graphics Pipelines - **Contradictions/Notes:** ANGLE의 변환 작업은 "고도로 최적화(highly optimized)"되어 있지만, 역설적으로 많은 드로우 콜을 요구하는 환경에서는 이 최적화된 변환 작업조차 누적되어 CPU 병목의 주요 원인이 됩니다 [3]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/ANGLE.md]] +- Raw Source: 00_Raw/2026-04-20/ANGLE.md --- diff --git a/01_Archive/2026-04-20/AODA-Accessibility-for-Ontarians-with-Disabilities-Act.md b/01_Archive/2026-04-20/AODA-Accessibility-for-Ontarians-with-Disabilities-Act.md index f322c82a..c6f6d63f 100644 --- a/01_Archive/2026-04-20/AODA-Accessibility-for-Ontarians-with-Disabilities-Act.md +++ b/01_Archive/2026-04-20/AODA-Accessibility-for-Ontarians-with-Disabilities-Act.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-03FE7E -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.95 tags: [] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Mega Batch - Wikified AODA-Accessibility-for-Ontarians-with-Disabilities-Act" --- -# [[AODA-Accessibility-for-Ontarians-with-Disabilities-Act]] +# [[AODA-Accessibility-for-Ontarians-with-Disabilities-Act|AODA-Accessibility-for-Ontarians-with-Disabilities-Act]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 핵심 요약 작업 진행 중 @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Mega Batch - Wikified AODA-Accessibility-for-Ontar ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/AODA-Accessibility-for-Ontarians-with-Disabilities-Act.md]] +- Raw Source: 00_Raw/2026-04-20/AODA-Accessibility-for-Ontarians-with-Disabilities-Act.md --- diff --git a/01_Archive/2026-04-20/API 응답 모델링 및 상태 머신(State Machine) 설계.md b/01_Archive/2026-04-20/API 응답 모델링 및 상태 머신(State Machine) 설계.md index a8a14092..f5a4127e 100644 --- a/01_Archive/2026-04-20/API 응답 모델링 및 상태 머신(State Machine) 설계.md +++ b/01_Archive/2026-04-20/API 응답 모델링 및 상태 머신(State Machine) 설계.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-9FD5CF -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - API 응답 모델링 및 상태 머신(State Machine) 설계" --- -# [[API 응답 모델링 및 상태 머신(State Machine) 설계]] +# [[API 응답 모델링 및 상태 머신(State Machine) 설계|API 응답 모델링 및 상태 머신(State Machine) 설계]] ## 📌 한 줄 통찰 (The Karpathy Summary) > TypeScript에서 API 응답과 상태 머신을 설계할 때는 식별 가능한 유니온(Discriminated Unions) 패턴이 핵심적으로 활용된다 [1, 2]. 이 패턴은 공통 판별자(Discriminant) 속성을 통해 데이터의 다양한 상태를 구분하며, 유효하지 않은 상태가 코드에 표현되는 것을 원천적으로 차단한다 [1, 3, 4]. 결과적으로 네트워크 요청의 다양한 결과나 복잡한 UI 상태 전이를 컴파일 단계에서 안전하게 모델링하고 관리할 수 있도록 보장한다 [2, 5, 6]. @@ -30,11 +30,11 @@ github_commit: "[P-Reinforce] Continuous Worker - API 응답 모델링 및 상 - **정책 변화:** AI 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[식별 가능한 유니온(Discriminated Unions)]], [[완전성 검사(Exhaustiveness Checking)]], [[타입 좁히기(Type Narrowing)]] -- **Projects/Contexts:** [[비동기 데이터 패칭(Async Data Fetching)]], [[상태 머신 기반 UI 폼 및 라우터 관리]] +- **Related Topics:** [[식별 가능한 유니온(Discriminated Unions)|식별 가능한 유니온(Discriminated Unions)]], [[완전성 검사(Exhaustiveness Checking)|완전성 검사(Exhaustiveness Checking)]], [[타입 좁히기(Type Narrowing)|타입 좁히기(Type Narrowing)]] +- **Projects/Contexts:** 비동기 데이터 패칭(Async Data Fetching), 상태 머신 기반 UI 폼 및 라우터 관리 - **Contradictions/Notes:** API 응답 데이터를 변환할 때 타입 캐스팅(`as`)을 사용하면 잉여 속성이 존재하거나 형태가 잘못되어도 컴파일러가 이를 조용히 허용하여 안전성이 떨어질 수 있다. 따라서 엄격한 타입 계약을 강제하기 위해서는 `as` 대신 `satisfies` 키워드를 활용하는 것이 권장된다 [14, 15]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/API 응답 모델링 및 상태 머신(State Machine) 설계.md]] +- Raw Source: 00_Raw/2026-04-20/API 응답 모델링 및 상태 머신(State Machine) 설계.md --- diff --git a/01_Archive/2026-04-20/API 응답 및 상태 모델링 (State Modeling and API Responses).md b/01_Archive/2026-04-20/API 응답 및 상태 모델링 (State Modeling and API Responses).md index 2aa68a8d..9627fb6d 100644 --- a/01_Archive/2026-04-20/API 응답 및 상태 모델링 (State Modeling and API Responses).md +++ b/01_Archive/2026-04-20/API 응답 및 상태 모델링 (State Modeling and API Responses).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-09EEF3 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - API 응답 및 상태 모델링 (State Modeling and API Responses)" --- -# [[API 응답 및 상태 모델링 (State Modeling and API Responses)]] +# [[API 응답 및 상태 모델링 (State Modeling and API Responses)|API 응답 및 상태 모델링 (State Modeling and API Responses)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > API 응답 및 상태 모델링은 애플리케이션에서 발생할 수 있는 네트워크 통신 결과나 UI의 변화 과정을 타입 시스템을 통해 안전하고 예측 가능하게 설계하는 기법이다 [1, 2]. 이 모델링은 주로 식별 가능한 유니온(Discriminated Unions)이나 명시적인 Result 객체를 활용하여 존재해서는 안 될 유효하지 않은 상태를 원천적으로 차단한다 [3, 4]. 궁극적으로 컴파일러가 모든 가능한 응답 상태를 검사(Exhaustiveness checking)하도록 강제함으로써, 런타임 버그를 줄이고 코드의 안정성과 가독성을 높여준다 [5-7]. @@ -30,11 +30,11 @@ github_commit: "[P-Reinforce] Continuous Worker - API 응답 및 상태 모델 - **정책 변화:** Design & Experience 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[식별 가능한 유니온 (Discriminated Unions)]], [[완전성 검사 (Exhaustiveness checking)]], [[Result 타입 (Result Type)]] -- **Projects/Contexts:** [[상태 머신 (State Machine)]], [[오류 처리 아키텍처 (Error Handling Architecture)]] +- **Related Topics:** [[식별 가능한 유니온 (Discriminated Unions)|식별 가능한 유니온 (Discriminated Unions)]], [[완전성 검사(Exhaustiveness Checking)|완전성 검사 (Exhaustiveness checking)]], Result 타입 (Result Type) +- **Projects/Contexts:** 상태 머신 (State Machine), 오류 처리 아키텍처 (Error Handling Architecture) - **Contradictions/Notes:** API나 시스템의 에러 응답을 모델링할 때 'Result 타입'을 사용하는 방식에 대해 개발자 간의 이견이 존재한다. 예상된 실패를 Result로 강제 반환하면 실행 흐름이 예측 가능해진다는 찬성 측 주장이 있는 반면, 전역 예외 처리기(Global Exception Handler)를 사용하는 쪽이 예외를 단순히 위로 올려보낼 수 있어 불필요한 보일러플레이트 코드 및 과도한 제어 흐름 분기(`switch`문 등)를 줄이고 컨트롤러를 더 깔끔하게 유지할 수 있다는 반대 주장도 팽팽하게 맞선다 [7, 20, 26-31]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/API 응답 및 상태 모델링 (State Modeling and API Responses).md]] +- Raw Source: 00_Raw/2026-04-20/API 응답 및 상태 모델링 (State Modeling and API Responses).md --- diff --git a/01_Archive/2026-04-20/API 응답 및 에러 핸들링 아키텍처.md b/01_Archive/2026-04-20/API 응답 및 에러 핸들링 아키텍처.md index 576101e7..e7eec2dc 100644 --- a/01_Archive/2026-04-20/API 응답 및 에러 핸들링 아키텍처.md +++ b/01_Archive/2026-04-20/API 응답 및 에러 핸들링 아키텍처.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-B2F9C0 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - API 응답 및 에러 핸들링 아키텍처" --- -# [[API 응답 및 에러 핸들링 아키텍처]] +# [[API 응답 및 에러 핸들링 아키텍처|API 응답 및 에러 핸들링 아키텍처]] ## 📌 한 줄 통찰 (The Karpathy Summary) > API 응답 및 에러 핸들링 아키텍처는 시스템 내에서 발생하는 에러를 예상 가능한 것과 그렇지 않은 것으로 구분하고, 이를 클라이언트에게 일관되고 예측 가능한 형태로 전달하기 위한 설계 방식입니다. 주로 '예외 던지기(throw exceptions)' 대신 명시적인 결과 객체(Result 타입)나 식별 가능한 유니온(Discriminated Unions)을 활용하여 타입 안전성을 확보하고, 컨트롤러 계층에서 응답의 제어 흐름을 명확히 관리하는 것을 목표로 합니다. @@ -27,11 +27,11 @@ github_commit: "[P-Reinforce] Continuous Worker - API 응답 및 에러 핸들 - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Result Type]], [[Discriminated Unions]], [[Exception Handling]] -- **Projects/Contexts:** [[TypeScript API Development]], [[Server Architecture]] +- **Related Topics:** [[Result Type|Result Type]], [[Discriminated Unions|Discriminated Unions]], Exception Handling +- **Projects/Contexts:** [[TypeScript API Development|TypeScript API Development]], [[Server Architecture|Server Architecture]] - **Contradictions/Notes:** 전역 예외 처리기(Global Exception Handler)를 두고 컨트롤러에서 예외를 발생시키는 방식이 코드가 깔끔해진다고 선호하는 개발자들도 있지만, Result 패턴을 지지하는 개발자들은 예외를 던지는 방식이 제어 흐름을 끊고 타입 시스템으로 에러를 파악할 수 없게 하므로 예상 가능한 에러는 명시적인 타입으로 반환해야 한다고 반대합니다 [7, 14-16]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/API 응답 및 에러 핸들링 아키텍처.md]] +- Raw Source: 00_Raw/2026-04-20/API 응답 및 에러 핸들링 아키텍처.md --- diff --git a/01_Archive/2026-04-20/API-Contract-Definition.md b/01_Archive/2026-04-20/API-Contract-Definition.md index a25353a5..3dabb046 100644 --- a/01_Archive/2026-04-20/API-Contract-Definition.md +++ b/01_Archive/2026-04-20/API-Contract-Definition.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-662214 -category: "[[10_Wiki/💡 Topics/Software Architecture]]" +category: "10_Wiki/💡 Topics/Software Architecture" confidence_score: 0.95 tags: [] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Mega Batch - Wikified API-Contract-Definition" --- -# [[API-Contract-Definition]] +# [[API-Contract-Definition|API-Contract-Definition]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 핵심 요약 작업 진행 중 @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Mega Batch - Wikified API-Contract-Definition" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/API-Contract-Definition.md]] +- Raw Source: 00_Raw/2026-04-20/API-Contract-Definition.md --- diff --git a/01_Archive/2026-04-20/API-First Architecture.md b/01_Archive/2026-04-20/API-First Architecture.md index cf453f5c..e073d915 100644 --- a/01_Archive/2026-04-20/API-First Architecture.md +++ b/01_Archive/2026-04-20/API-First Architecture.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-E43C2B -category: "[[10_Wiki/💡 Topics/Software Architecture]]" +category: "10_Wiki/💡 Topics/Software Architecture" confidence_score: 0.95 tags: [] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Mega Batch - Wikified API-First Architecture" --- -# [[API-First Architecture]] +# [[API-First Architecture|API-First Architecture]] ## 📌 한 줄 통찰 (The Karpathy Summary) > **API-First Architecture**는 애플리케이션 프로그래밍 인터페이스(API)를 시스템의 최우선 제품으로 취급하는 소프트웨어 설계 방식입니다 [1]. 제품을 먼저 구축하고 나중에 API를 덧붙이는 대신, API의 설계와 문서화부터 개발을 시작합니다 [1]. 이러한 계약 우선(contract-first) 방법론을 통해 API의 일관성과 재사용성을 보장하며, 프론트엔드와 백엔드 개발 팀이 분리되어 병렬로 효율적인 작업을 진행할 수 있도록 지원합니다 [1, 2]. @@ -32,11 +32,11 @@ github_commit: "[P-Reinforce] Mega Batch - Wikified API-First Architecture" - **정책 변화:** Software Architecture 카테고리의 전문성 확보 및 링크 밀도 최적화. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Contract-Driven Development]], [[OpenAPI]], [[AsyncAPI]] -- **Projects/Contexts:** [[Stripe]], [[Twilio]] (이 철학으로 잘 문서화된 API를 구축하여 비즈니스를 성장시킨 대표적인 기업 사례 [3]) +- **Related Topics:** [[Contract-Driven-Development|Contract-Driven Development]], OpenAPI, AsyncAPI +- **Projects/Contexts:** Stripe, Twilio (이 철학으로 잘 문서화된 API를 구축하여 비즈니스를 성장시킨 대표적인 기업 사례 [3]) - **Contradictions/Notes:** 소스 내에 상충되는 주장은 존재하지 않습니다. 다만, 이 구조의 구현 복잡성은 '중간(Medium)' 수준이며, 성공적인 도입과 유지를 위해서는 스펙 우선(spec-first)의 규율과 명확한 거버넌스가 요구된다고 명시하고 있습니다 [5]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/API-First Architecture.md]] +- Raw Source: 00_Raw/2026-04-20/API-First Architecture.md --- diff --git a/01_Archive/2026-04-20/API-First-Design.md b/01_Archive/2026-04-20/API-First-Design.md index 5308dfd8..30aae8a4 100644 --- a/01_Archive/2026-04-20/API-First-Design.md +++ b/01_Archive/2026-04-20/API-First-Design.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-7482EF -category: "[[10_Wiki/💡 Topics/Software Architecture]]" +category: "10_Wiki/💡 Topics/Software Architecture" confidence_score: 0.95 tags: [] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Mega Batch - Wikified API-First-Design" --- -# [[API-First-Design]] +# [[API-First-Design|API-First-Design]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 핵심 요약 작업 진행 중 @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Mega Batch - Wikified API-First-Design" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/API-First-Design.md]] +- Raw Source: 00_Raw/2026-04-20/API-First-Design.md --- diff --git a/01_Archive/2026-04-20/ARG-Alternate-Reality-Games.md b/01_Archive/2026-04-20/ARG-Alternate-Reality-Games.md index 87d3fc13..521d30e1 100644 --- a/01_Archive/2026-04-20/ARG-Alternate-Reality-Games.md +++ b/01_Archive/2026-04-20/ARG-Alternate-Reality-Games.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AEB866 -category: "[[10_Wiki/💡 Topics/Game Design]]" +category: "10_Wiki/💡 Topics/Game Design" confidence_score: 0.95 tags: [] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Mega Batch 2 - Wikified ARG-Alternate-Reality-Games" --- -# [[ARG-Alternate-Reality-Games]] +# [[ARG-Alternate-Reality-Games|ARG-Alternate-Reality-Games]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 작업 중 @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Mega Batch 2 - Wikified ARG-Alternate-Reality-Game ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/ARG-Alternate-Reality-Games.md]] +- Raw Source: 00_Raw/2026-04-20/ARG-Alternate-Reality-Games.md --- diff --git a/01_Archive/2026-04-20/ASP.NET Core.md b/01_Archive/2026-04-20/ASP.NET Core.md index acd547ff..f31ba403 100644 --- a/01_Archive/2026-04-20/ASP.NET Core.md +++ b/01_Archive/2026-04-20/ASP.NET Core.md @@ -1,4 +1,4 @@ -# [[ASP.NET Core]] +# [[ASP.NET Core|ASP.NET Core]] ## 📌 Brief Summary ASP.NET Core는 내장된 의존성 주입(DI) 컨테이너를 제공하여 소프트웨어의 의존성 역전 원칙 구현을 돕는 프레임워크입니다 [1]. 웹 애플리케이션 개발 시 클린 아키텍처를 적용하여 비즈니스 로직을 프레임워크나 데이터베이스로부터 분리된 구조로 개발할 수 있게 해줍니다 [2]. 다만, 주제를 깊이 있게 다루기에는 소스에 관련 정보가 부족합니다. @@ -9,8 +9,8 @@ ASP.NET Core는 내장된 의존성 주입(DI) 컨테이너를 제공하여 소 - **소스 정보의 한계**: ASP.NET Core 프레임워크 자체의 전반적인 기능이나 구동 방식 등에 대해서는 소스에 관련 정보가 부족합니다. ## 🔗 Knowledge Connections -- **Related Topics:** [[Dependency Inversion Principle]], [[Clean Architecture]], [[Dependency Injection]] -- **Projects/Contexts:** [[Web Applications]] +- **Related Topics:** [[Dependency-Inversion-Principle|Dependency Inversion Principle]], [[Clean Architecture|Clean Architecture]], [[Dependency-Injection|Dependency Injection]] +- **Projects/Contexts:** Web Applications - **Contradictions/Notes:** 소스 간의 모순은 없으나, ASP.NET Core라는 루트 주제를 포괄적으로 설명하기에는 제공된 소스에 관련 정보가 부족합니다. 소스에서는 주로 소프트웨어 아키텍처 패턴의 유용한 적용 사례 중 하나로만 짧게 언급하고 있습니다. --- diff --git a/01_Archive/2026-04-20/ASPNET Core.md b/01_Archive/2026-04-20/ASPNET Core.md index ab399355..7f715a48 100644 --- a/01_Archive/2026-04-20/ASPNET Core.md +++ b/01_Archive/2026-04-20/ASPNET Core.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-761015 -category: "[[10_Wiki/💡 Topics/Programming & Web]]" +category: "10_Wiki/💡 Topics/Programming & Web" confidence_score: 0.95 tags: [] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Mega Batch 2 - Wikified ASP.NET Core" --- -# [[ASP.NET Core]] +# [[ASP.NET Core|ASP.NET Core]] ## 📌 한 줄 통찰 (The Karpathy Summary) > ASP.NET Core는 내장된 의존성 주입(DI) 컨테이너를 제공하여 소프트웨어의 의존성 역전 원칙 구현을 돕는 프레임워크입니다 [1]. 웹 애플리케이션 개발 시 클린 아키텍처를 적용하여 비즈니스 로직을 프레임워크나 데이터베이스로부터 분리된 구조로 개발할 수 있게 해줍니다 [2]. 다만, 주제를 깊이 있게 다루기에는 소스에 관련 정보가 부족합니다. @@ -22,11 +22,11 @@ github_commit: "[P-Reinforce] Mega Batch 2 - Wikified ASP.NET Core" - **정책 변화:** Programming & Web 카테고리의 전문성 확보 및 링크 밀도 최적화. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Dependency Inversion Principle]], [[Clean Architecture]], [[Dependency Injection]] -- **Projects/Contexts:** [[Web Applications]] +- **Related Topics:** [[Dependency-Inversion-Principle|Dependency Inversion Principle]], [[Clean Architecture|Clean Architecture]], [[Dependency-Injection|Dependency Injection]] +- **Projects/Contexts:** Web Applications - **Contradictions/Notes:** 소스 간의 모순은 없으나, ASP.NET Core라는 루트 주제를 포괄적으로 설명하기에는 제공된 소스에 관련 정보가 부족합니다. 소스에서는 주로 소프트웨어 아키텍처 패턴의 유용한 적용 사례 중 하나로만 짧게 언급하고 있습니다. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/ASP.NET Core.md]] +- Raw Source: 00_Raw/2026-04-20/ASP.NET Core.md --- diff --git a/01_Archive/2026-04-20/AST (추상 구문 트리).md b/01_Archive/2026-04-20/AST (추상 구문 트리).md index b0254d67..597e761b 100644 --- a/01_Archive/2026-04-20/AST (추상 구문 트리).md +++ b/01_Archive/2026-04-20/AST (추상 구문 트리).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-7DEA60 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - AST (추상 구문 트리)" --- -# [[AST (추상 구문 트리)]] +# [[AST (추상 구문 트리)|AST (추상 구문 트리)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > AST(추상 구문 트리)는 소스 코드를 파싱하여 얻어지는 코드의 추상적인 구문 및 문법적 구조를 표현하는 트리 형태의 데이터 구조입니다 [1, 2]. 이는 코드의 구문적 특성과 어휘적 특성을 보존하지만, 띄어쓰기나 들여쓰기와 같은 레이아웃(Layout) 특성은 캡처하지 못한다는 특징을 지닙니다 [2, 3]. AST는 코드 스타일을 분석하는 코드 문체론(Code Stylometry)이나 코드를 실행하지 않고 취약점을 탐지하는 정적 애플리케이션 보안 테스트(SAST) 등 다양한 소스 코드 분석 기술의 핵심적인 기반 모델로 활용됩니다 [2, 4]. @@ -23,11 +23,11 @@ github_commit: "[P-Reinforce] Continuous Worker - AST (추상 구문 트리)" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[CST (구체 구문 트리)]], [[SAST (정적 애플리케이션 보안 테스트)]], [[Code Stylometry (코드 문체론)]] -- **Projects/Contexts:** [[ESLint]], [[Joern]] +- **Related Topics:** [[CST (구체 구문 트리)|CST (구체 구문 트리)]], [[SAST (정적 애플리케이션 보안 테스트)|SAST (정적 애플리케이션 보안 테스트)]], [[Code Stylometry (코드 문체론)|Code Stylometry (코드 문체론)]] +- **Projects/Contexts:** [[ESLint|ESLint]], [[Joern|Joern]] - **Contradictions/Notes:** 소스에 따르면 코드 작성자 식별(Authorship Attribution) 작업 시 AST 모델만을 사용하면 들여쓰기나 공백 등 개인의 레이아웃 코딩 스타일이 캡처되지 않는 한계가 있습니다 [2]. 실제로 실험 결과, AST 기반 접근 방식보다 이러한 레이아웃 요소를 포함하는 CST(구체 구문 트리)를 사용할 때 작성자 식별 정확도가 눈에 띄게(약 17%) 향상되는 것으로 나타납니다 [8, 9]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/AST (추상 구문 트리).md]] +- Raw Source: 00_Raw/2026-04-20/AST (추상 구문 트리).md --- diff --git a/01_Archive/2026-04-20/AST(Abstract Syntax Tree).md b/01_Archive/2026-04-20/AST(Abstract Syntax Tree).md index f55bc9c5..c3f75668 100644 --- a/01_Archive/2026-04-20/AST(Abstract Syntax Tree).md +++ b/01_Archive/2026-04-20/AST(Abstract Syntax Tree).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-C7BE0D -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - AST(Abstract Syntax Tree)" --- -# [[AST(Abstract Syntax Tree)]] +# [[AST(Abstract Syntax Tree)|AST(Abstract Syntax Tree)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > AST(Abstract Syntax Tree, 추상 구문 트리)는 소스 코드를 파싱하여 프로그래밍 언어의 문법적 구조를 트리 형태로 표현한 데이터 구조입니다. 공백이나 들여쓰기 같은 표면적인 레이아웃 정보는 배제하고 본질적인 구문 특징과 알고리즘 구조만을 보존하는 것이 특징입니다 [1]. 주로 SAST(정적 애플리케이션 보안 테스트), 린팅(Linting), 그리고 코드 작성자를 식별하는 코드 스타일로메트리(Code Stylometry) 분야에서 코드를 분석하는 핵심 기반으로 사용됩니다 [1, 2]. @@ -27,11 +27,11 @@ github_commit: "[P-Reinforce] Continuous Worker - AST(Abstract Syntax Tree)" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[CST(Concrete Syntax Tree)]], [[정적 애플리케이션 보안 테스트(SAST)]], [[코드 스타일로메트리(Code Stylometry)]], [[정적 분석(Static Analysis)]] -- **Projects/Contexts:** [[기계학습 기반의 소스 코드 저자 식별 연구]], [[AI 기반 코드 복잡도 분석(카카오)]], [[정적 보안 취약점 스캐닝 파이프라인]] +- **Related Topics:** CST(Concrete Syntax Tree), [[정적 애플리케이션 보안 테스트(SAST)|정적 애플리케이션 보안 테스트(SAST)]], [[코드 스타일로메트리 (Code Stylometry)|코드 스타일로메트리(Code Stylometry)]], [[정적 분석(Static Analysis)|정적 분석(Static Analysis)]] +- **Projects/Contexts:** 기계학습 기반의 소스 코드 저자 식별 연구, AI 기반 코드 복잡도 분석(카카오), 정적 보안 취약점 스캐닝 파이프라인 - **Contradictions/Notes:** AST 기반의 분석은 작성자의 본질적인 프로그래밍 구조를 파악하고 위조 공격에 강하다는 장점이 있지만, 공백이나 들여쓰기 등 개발자의 개성이 묻어나는 '레이아웃 특징'을 담지 못합니다. 이로 인해 소스 코드 작성자 식별 실험에서 AST 기반 모델(51.00%)은 레이아웃 정보까지 포함하는 CST 기반 모델(67.86%)에 비해 상대적으로 낮은 정확도를 보였습니다 [10, 11]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/AST(Abstract Syntax Tree).md]] +- Raw Source: 00_Raw/2026-04-20/AST(Abstract Syntax Tree).md --- diff --git a/01_Archive/2026-04-20/AST-Manipulation-Techniques.md b/01_Archive/2026-04-20/AST-Manipulation-Techniques.md index cdb6d74c..dd9027c7 100644 --- a/01_Archive/2026-04-20/AST-Manipulation-Techniques.md +++ b/01_Archive/2026-04-20/AST-Manipulation-Techniques.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-7C91FA -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - AST-Manipulation-Techniques" --- -# [[AST-Manipulation-Techniques]] +# [[AST-Manipulation-Techniques|AST-Manipulation-Techniques]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - AST-Manipulation-Techniques" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/AST-Manipulation-Techniques.md]] +- Raw Source: 00_Raw/2026-04-20/AST-Manipulation-Techniques.md --- diff --git a/01_Archive/2026-04-20/AST-based-Static-Analysis.md b/01_Archive/2026-04-20/AST-based-Static-Analysis.md index 91b1e795..29158e13 100644 --- a/01_Archive/2026-04-20/AST-based-Static-Analysis.md +++ b/01_Archive/2026-04-20/AST-based-Static-Analysis.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-8D040C -category: "[[10_Wiki/💡 Topics/Programming & Tools]]" +category: "10_Wiki/💡 Topics/Programming & Tools" confidence_score: 0.95 tags: [] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Mega Batch 2 - Wikified AST-based-Static-Analysis" --- -# [[AST-based-Static-Analysis]] +# [[AST-based-Static-Analysis|AST-based-Static-Analysis]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 작업 중 @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Mega Batch 2 - Wikified AST-based-Static-Analysis" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/AST-based-Static-Analysis.md]] +- Raw Source: 00_Raw/2026-04-20/AST-based-Static-Analysis.md --- diff --git a/01_Archive/2026-04-20/AST_Traversal.md b/01_Archive/2026-04-20/AST_Traversal.md index f816aa25..536d4fc2 100644 --- a/01_Archive/2026-04-20/AST_Traversal.md +++ b/01_Archive/2026-04-20/AST_Traversal.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-CODING-001 -category: "[[10_Wiki/💡 Topics/Coding]]" +category: "10_Wiki/💡 Topics/Coding" confidence_score: 0.92 tags: [coding, ast, compiler] last_reinforced: 2026-04-20 github_commit: "batch-reinforce-01" --- -# [[Abstract Syntax Tree Traversal]] +# [[Abstract-Syntax-Tree-Traversal|Abstract Syntax Tree Traversal]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 소스 코드의 추상적인 구조를 정의된 규칙에 따라 탐색하며 변환 및 분석의 기틀을 마련하는 컴파일러의 핵심 여정. @@ -24,6 +24,6 @@ github_commit: "batch-reinforce-01" - **정책 변화:** 코딩 표준(w1) 강화에 따라 AST 기반 자동 수정 가중치 상향. ## 🔗 지식 연결 (Graph) -- **Parent:** [[10_Wiki/💡 Topics/Coding]] -- **Related:** [[CST]], [[Parser]], [[Visitor-Pattern]] -- **Raw Source:** [[00_Raw/2026-04-20/Abstract-Syntax-Tree-Traversal.md]] +- **Parent:** 10_Wiki/💡 Topics/Coding +- **Related:** [[CST|CST]], [[Parser|Parser]], Visitor-Pattern +- **Raw Source:** 00_Raw/2026-04-20/Abstract-Syntax-Tree-Traversal.md diff --git a/01_Archive/2026-04-20/A_B-Testing-Platforms.md b/01_Archive/2026-04-20/A_B-Testing-Platforms.md index c3d56332..58a826c7 100644 --- a/01_Archive/2026-04-20/A_B-Testing-Platforms.md +++ b/01_Archive/2026-04-20/A_B-Testing-Platforms.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-1151FA -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - A_B-Testing-Platforms" --- -# [[A_B-Testing-Platforms]] +# [[A_B-Testing-Platforms|A_B-Testing-Platforms]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - A_B-Testing-Platforms" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/A_B-Testing-Platforms.md]] +- Raw Source: 00_Raw/2026-04-20/A_B-Testing-Platforms.md --- diff --git a/01_Archive/2026-04-20/Abstract Syntax Tree (AST).md b/01_Archive/2026-04-20/Abstract Syntax Tree (AST).md index e4f68822..728fd660 100644 --- a/01_Archive/2026-04-20/Abstract Syntax Tree (AST).md +++ b/01_Archive/2026-04-20/Abstract Syntax Tree (AST).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AI-696634 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.95 tags: [] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Batch 9 - Wikified Abstract Syntax Tree (AST)" --- -# [[Abstract Syntax Tree (AST)]] +# [[Abstract Syntax Tree (AST)|Abstract Syntax Tree (AST)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 추상 구문 트리(AST, Abstract Syntax Tree)는 소스 코드를 파싱(Parsing)한 후 해당 언어의 문법적 구조를 계층적으로 표현한 트리 형태의 데이터 구조입니다 [1, 2]. 구체적 구문 트리(CST)와 달리 여백, 들여쓰기, 주석 등과 같은 레이아웃 및 스타일적 요소를 추상화하여 배제하며, 주로 소스 코드의 구문(syntax) 및 일부 어휘(lexical)적 특징만을 보존합니다 [1, 3, 4]. 이러한 특성 덕분에 주로 정적 애플리케이션 보안 테스트(SAST) 도구에서 오류를 분석하거나, 기계 학습을 통한 코드 저자 식별(Code Stylometry) 모델에서 코드를 표현하는 핵심 기반으로 폭넓게 활용됩니다 [1, 2, 5]. @@ -27,11 +27,11 @@ github_commit: "[P-Reinforce] Batch 9 - Wikified Abstract Syntax Tree (AST)" - **정책 변화:** Programming & Language 카테고리의 지식 연결망 강화를 위한 표준 위키화 적용. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Concrete Syntax Tree (CST)]], [[Static Application Security Testing (SAST)]], [[Code Stylometry]], [[Parsing]] -- **Projects/Contexts:** [[기계 학습 기반 저자 식별 (Machine Learning-based Code Stylometry)]], [[Eclipse C/C++ Development Tools (CDT)]], [[코드 정적 분석 도구]] +- **Related Topics:** [[Concrete Syntax Tree (CST)|Concrete Syntax Tree (CST)]], [[Static Application Security Testing (SAST)|Static Application Security Testing (SAST)]], [[Code Stylometry (코드 문체론)|Code Stylometry]], Parsing +- **Projects/Contexts:** 기계 학습 기반 저자 식별 (Machine Learning-based Code Stylometry), Eclipse C/C++ Development Tools (CDT), 코드 정적 분석 도구 - **Contradictions/Notes:** 소스 코드의 본질적이고 구문적인 스타일을 분석하는 데는 AST가 핵심적으로 사용되지만, 코드의 들여쓰기, 공백과 같은 시각적 레이아웃 특징을 담아내지는 못합니다. 따라서 포맷팅이나 난독화 등이 프로그래머의 식별 가능성에 미치는 영향을 분석해야 할 경우에는 AST보다는 이를 모두 포함하는 구체적 구문 트리(CST)를 사용하는 것이 더 효과적이라는 지적이 있습니다 [1, 3, 7]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Abstract Syntax Tree (AST).md]] +- Raw Source: 00_Raw/2026-04-20/Abstract Syntax Tree (AST).md --- diff --git a/01_Archive/2026-04-20/Abstract-Syntax-Tree-Transformation.md b/01_Archive/2026-04-20/Abstract-Syntax-Tree-Transformation.md index 80b85bbd..37569b51 100644 --- a/01_Archive/2026-04-20/Abstract-Syntax-Tree-Transformation.md +++ b/01_Archive/2026-04-20/Abstract-Syntax-Tree-Transformation.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-E03D74 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Abstract-Syntax-Tree-Transformation" --- -# [[Abstract-Syntax-Tree-Transformation]] +# [[Abstract-Syntax-Tree-Transformation|Abstract-Syntax-Tree-Transformation]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Abstract-Syntax-Tree-Transform ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Abstract-Syntax-Tree-Transformation.md]] +- Raw Source: 00_Raw/2026-04-20/Abstract-Syntax-Tree-Transformation.md --- diff --git a/01_Archive/2026-04-20/Abstract-Syntax-Tree-Traversal.md b/01_Archive/2026-04-20/Abstract-Syntax-Tree-Traversal.md index cc072c4d..09d7e5c0 100644 --- a/01_Archive/2026-04-20/Abstract-Syntax-Tree-Traversal.md +++ b/01_Archive/2026-04-20/Abstract-Syntax-Tree-Traversal.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-18B63D -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Abstract-Syntax-Tree-Traversal" --- -# [[Abstract-Syntax-Tree-Traversal]] +# [[Abstract-Syntax-Tree-Traversal|Abstract-Syntax-Tree-Traversal]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Abstract-Syntax-Tree-Traversal ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Abstract-Syntax-Tree-Traversal.md]] +- Raw Source: 00_Raw/2026-04-20/Abstract-Syntax-Tree-Traversal.md --- diff --git a/01_Archive/2026-04-20/Accessibility (A11y).md b/01_Archive/2026-04-20/Accessibility (A11y).md index 32760bea..9284c25b 100644 --- a/01_Archive/2026-04-20/Accessibility (A11y).md +++ b/01_Archive/2026-04-20/Accessibility (A11y).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AI-99D2E0 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.95 tags: [] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Batch 9 - Wikified Accessibility (A11y)" --- -# [[Accessibility (A11y)]] +# [[Accessibility (A11y)|Accessibility (A11y)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Batch 9 - Wikified Accessibility (A11y)" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Accessibility (A11y).md]] +- Raw Source: 00_Raw/2026-04-20/Accessibility (A11y).md --- diff --git a/01_Archive/2026-04-20/Accessibility-Compliance-Audit.md b/01_Archive/2026-04-20/Accessibility-Compliance-Audit.md index a8364e9b..2d6cee78 100644 --- a/01_Archive/2026-04-20/Accessibility-Compliance-Audit.md +++ b/01_Archive/2026-04-20/Accessibility-Compliance-Audit.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-EA31B2 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Accessibility-Compliance-Audit" --- -# [[Accessibility-Compliance-Audit]] +# [[Accessibility-Compliance-Audit|Accessibility-Compliance-Audit]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Accessibility-Compliance-Audit ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Accessibility-Compliance-Audit.md]] +- Raw Source: 00_Raw/2026-04-20/Accessibility-Compliance-Audit.md --- diff --git a/01_Archive/2026-04-20/Accessibility-Compliance-WCAG.md b/01_Archive/2026-04-20/Accessibility-Compliance-WCAG.md index a68f4f81..ec1c8f9e 100644 --- a/01_Archive/2026-04-20/Accessibility-Compliance-WCAG.md +++ b/01_Archive/2026-04-20/Accessibility-Compliance-WCAG.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-2801A2 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.95 tags: [] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Batch 10 - Wikified Accessibility-Compliance-WCAG" --- -# [[Accessibility-Compliance-WCAG]] +# [[Accessibility-Compliance-WCAG|Accessibility-Compliance-WCAG]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 핵심 내용 요약 예정 @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Batch 10 - Wikified Accessibility-Compliance-WCAG" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Accessibility-Compliance-WCAG.md]] +- Raw Source: 00_Raw/2026-04-20/Accessibility-Compliance-WCAG.md --- diff --git a/01_Archive/2026-04-20/Accessibility.md b/01_Archive/2026-04-20/Accessibility.md index b9f40767..45473637 100644 --- a/01_Archive/2026-04-20/Accessibility.md +++ b/01_Archive/2026-04-20/Accessibility.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-DESIGN-001 -category: "[[10_Wiki/💡 Topics/Design]]" +category: "10_Wiki/💡 Topics/Design" confidence_score: 0.94 tags: [design, accessibility, a11y, ux] last_reinforced: 2026-04-20 github_commit: "batch-reinforce-01" --- -# [[Accessibility (A11y)]] +# [[Accessibility (A11y)|Accessibility (A11y)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 기술적 장벽을 허물어 모든 사용자가 정보에 평등하게 접근할 수 있도록 보장하는 포괄적 설계의 핵심 원칙. @@ -24,6 +24,6 @@ github_commit: "batch-reinforce-01" - **정책 변화:** 사용자 만족도(w3)의 필수 지표로 접근성 점수를 채택. ## 🔗 지식 연결 (Graph) -- **Parent:** [[10_Wiki/💡 Topics/Design]] -- **Related:** [[WCAG]], [[Inclusive-Design]], [[ARIA]] -- **Raw Source:** [[00_Raw/2026-04-20/Accessibility (A11y).md]] +- **Parent:** 10_Wiki/💡 Topics/Design +- **Related:** WCAG, [[Inclusive_Design|Inclusive-Design]], ARIA +- **Raw Source:** 00_Raw/2026-04-20/Accessibility (A11y).md diff --git a/01_Archive/2026-04-20/Adaptive Compute (적응형 계산량 조절).md b/01_Archive/2026-04-20/Adaptive Compute (적응형 계산량 조절).md index bafebcf4..c6f4e8fa 100644 --- a/01_Archive/2026-04-20/Adaptive Compute (적응형 계산량 조절).md +++ b/01_Archive/2026-04-20/Adaptive Compute (적응형 계산량 조절).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-D19FE3 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Adaptive Compute (적응형 계산량 조절)" --- -# [[Adaptive Compute (적응형 계산량 조절)]] +# [[Adaptive Compute (적응형 계산량 조절)|Adaptive Compute (적응형 계산량 조절)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Adaptive Compute (적응형 ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Adaptive Compute (적응형 계산량 조절).md]] +- Raw Source: 00_Raw/2026-04-20/Adaptive Compute (적응형 계산량 조절).md --- diff --git a/01_Archive/2026-04-20/Adaptive-Learning-Systems.md b/01_Archive/2026-04-20/Adaptive-Learning-Systems.md index 960a4ff6..86bb56a8 100644 --- a/01_Archive/2026-04-20/Adaptive-Learning-Systems.md +++ b/01_Archive/2026-04-20/Adaptive-Learning-Systems.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AI-A2C439 -category: "[[10_Wiki/💡 Topics/Education & AI]]" +category: "10_Wiki/💡 Topics/Education & AI" confidence_score: 0.95 tags: [] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Batch 9 - Wikified Adaptive-Learning-Systems" --- -# [[Adaptive-Learning-Systems]] +# [[Adaptive-Learning-Systems|Adaptive-Learning-Systems]] ## 📌 한 줄 통찰 (The Karpathy Summary) > @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Batch 9 - Wikified Adaptive-Learning-Systems" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Adaptive-Learning-Systems.md]] +- Raw Source: 00_Raw/2026-04-20/Adaptive-Learning-Systems.md --- diff --git a/01_Archive/2026-04-20/Adaptive_Learning.md b/01_Archive/2026-04-20/Adaptive_Learning.md index 6cb2ca24..64369e5a 100644 --- a/01_Archive/2026-04-20/Adaptive_Learning.md +++ b/01_Archive/2026-04-20/Adaptive_Learning.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-EDUC-001 -category: "[[10_Wiki/💡 Topics/Education]]" +category: "10_Wiki/💡 Topics/Education" confidence_score: 0.91 tags: [education, ai, adaptive, learning] last_reinforced: 2026-04-20 github_commit: "batch-reinforce-01" --- -# [[Adaptive Learning Systems]] +# [[Adaptive-Learning-Systems|Adaptive Learning Systems]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 학습자의 수준과 속도를 실시간으로 분석하여 개인별 최적의 학습 경로를 동적으로 제안하는 지능형 교수 시스템. @@ -24,6 +24,6 @@ github_commit: "batch-reinforce-01" - **정책 변화:** 사용자 만족도(w3) 피드백에 따라 학습자 이탈 방지 알고리즘 우선순위 상향. ## 🔗 지식 연결 (Graph) -- **Parent:** [[10_Wiki/💡 Topics/Education]] -- **Related:** [[IRT]], [[Personalized-Learning]], [[Educational-AI]] -- **Raw Source:** [[00_Raw/2026-04-20/Adaptive-Learning-Systems.md]] +- **Parent:** 10_Wiki/💡 Topics/Education +- **Related:** IRT, Personalized-Learning, Educational-AI +- **Raw Source:** 00_Raw/2026-04-20/Adaptive-Learning-Systems.md diff --git a/01_Archive/2026-04-20/Addiction Neuroscience.md b/01_Archive/2026-04-20/Addiction Neuroscience.md index 08b4c197..be1264c7 100644 --- a/01_Archive/2026-04-20/Addiction Neuroscience.md +++ b/01_Archive/2026-04-20/Addiction Neuroscience.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AI-60E30A -category: "[[10_Wiki/💡 Topics/Psychology & Behavior]]" +category: "10_Wiki/💡 Topics/Psychology & Behavior" confidence_score: 0.95 tags: [] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Batch 9 - Wikified Addiction Neuroscience" --- -# [[Addiction Neuroscience]] +# [[Addiction Neuroscience|Addiction Neuroscience]] ## 📌 한 줄 통찰 (The Karpathy Summary) > @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Batch 9 - Wikified Addiction Neuroscience" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Addiction Neuroscience.md]] +- Raw Source: 00_Raw/2026-04-20/Addiction Neuroscience.md --- diff --git a/01_Archive/2026-04-20/Addiction_Neuroscience.md b/01_Archive/2026-04-20/Addiction_Neuroscience.md index ac270a9e..32cd281c 100644 --- a/01_Archive/2026-04-20/Addiction_Neuroscience.md +++ b/01_Archive/2026-04-20/Addiction_Neuroscience.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-PSYCH-002 -category: "[[10_Wiki/💡 Topics/Psychology]]" +category: "10_Wiki/💡 Topics/Psychology" confidence_score: 0.93 tags: [psychology, neuroscience, addiction, brain] last_reinforced: 2026-04-20 github_commit: "batch-reinforce-01" --- -# [[Addiction Neuroscience]] +# [[Addiction Neuroscience|Addiction Neuroscience]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 보상 중추와 전두엽의 균형 파괴를 통해 행동 통제력을 상실하게 만드는 뇌 회로의 만성적 변화 과정. @@ -24,6 +24,6 @@ github_commit: "batch-reinforce-01" - **정책 변화:** 지식 구조(w2) 관점에서 행동 심리학과 연계하여 중독 치료 경로 제안. ## 🔗 지식 연결 (Graph) -- **Parent:** [[10_Wiki/💡 Topics/Psychology]] -- **Related:** [[Dopamine]], [[Prefrontal-Cortex]], [[Neuroplasticity]] -- **Raw Source:** [[00_Raw/2026-04-20/Addiction Neuroscience.md]] +- **Parent:** 10_Wiki/💡 Topics/Psychology +- **Related:** [[Dopamine|Dopamine]], Prefrontal-Cortex, [[Neuroplasticity|Neuroplasticity]] +- **Raw Source:** 00_Raw/2026-04-20/Addiction Neuroscience.md diff --git a/01_Archive/2026-04-20/Additive-Type-Logic.md b/01_Archive/2026-04-20/Additive-Type-Logic.md index 94d71ee4..3938c127 100644 --- a/01_Archive/2026-04-20/Additive-Type-Logic.md +++ b/01_Archive/2026-04-20/Additive-Type-Logic.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-E5F3BA -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Additive-Type-Logic" --- -# [[Additive-Type-Logic]] +# [[Additive-Type-Logic|Additive-Type-Logic]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Additive-Type-Logic" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Additive-Type-Logic.md]] +- Raw Source: 00_Raw/2026-04-20/Additive-Type-Logic.md --- diff --git a/01_Archive/2026-04-20/Advanced-Design-Patterns-in-TypeScript.md b/01_Archive/2026-04-20/Advanced-Design-Patterns-in-TypeScript.md index f1814798..369a3093 100644 --- a/01_Archive/2026-04-20/Advanced-Design-Patterns-in-TypeScript.md +++ b/01_Archive/2026-04-20/Advanced-Design-Patterns-in-TypeScript.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-82084D -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.95 tags: [] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Batch 10 - Wikified Advanced-Design-Patterns-in-TypeScript" --- -# [[Advanced-Design-Patterns-in-TypeScript]] +# [[Advanced-Design-Patterns-in-TypeScript|Advanced-Design-Patterns-in-TypeScript]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 핵심 내용 요약 예정 @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Batch 10 - Wikified Advanced-Design-Patterns-in-Ty ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Advanced-Design-Patterns-in-TypeScript.md]] +- Raw Source: 00_Raw/2026-04-20/Advanced-Design-Patterns-in-TypeScript.md --- diff --git a/01_Archive/2026-04-20/Advanced-Interface-Design.md b/01_Archive/2026-04-20/Advanced-Interface-Design.md index 93cca8f6..f1cb7804 100644 --- a/01_Archive/2026-04-20/Advanced-Interface-Design.md +++ b/01_Archive/2026-04-20/Advanced-Interface-Design.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-D1E81B -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Advanced-Interface-Design" --- -# [[Advanced-Interface-Design]] +# [[Advanced-Interface-Design|Advanced-Interface-Design]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Advanced-Interface-Design" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Advanced-Interface-Design.md]] +- Raw Source: 00_Raw/2026-04-20/Advanced-Interface-Design.md --- diff --git a/01_Archive/2026-04-20/Adversarial Attack (적대적 공격).md b/01_Archive/2026-04-20/Adversarial Attack (적대적 공격).md index 942824de..61da5896 100644 --- a/01_Archive/2026-04-20/Adversarial Attack (적대적 공격).md +++ b/01_Archive/2026-04-20/Adversarial Attack (적대적 공격).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AI-AFC0C0 -category: "[[10_Wiki/💡 Topics/Security & AI]]" +category: "10_Wiki/💡 Topics/Security & AI" confidence_score: 0.95 tags: [] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Batch 9 - Wikified Adversarial Attack (적대적 공격)" --- -# [[Adversarial Attack (적대적 공격)]] +# [[Adversarial Attack (적대적 공격)|Adversarial Attack (적대적 공격)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Batch 9 - Wikified Adversarial Attack (적대적 ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Adversarial Attack (적대적 공격).md]] +- Raw Source: 00_Raw/2026-04-20/Adversarial Attack (적대적 공격).md --- diff --git a/01_Archive/2026-04-20/Adversarial Code Stylometry.md b/01_Archive/2026-04-20/Adversarial Code Stylometry.md index eabe6319..5e00b24d 100644 --- a/01_Archive/2026-04-20/Adversarial Code Stylometry.md +++ b/01_Archive/2026-04-20/Adversarial Code Stylometry.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-36585B -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Adversarial Code Stylometry" --- -# [[Adversarial Code Stylometry]] +# [[Adversarial Code Stylometry|Adversarial Code Stylometry]] ## 📌 한 줄 통찰 (The Karpathy Summary) > Adversarial Code Stylometry(적대적 코드 문체론)는 프로그래머가 코드 문체 분석(Code Stylometry) 시스템의 추적을 우회하여 자신의 익명성을 보호하기 위해 의도적으로 코드를 변형하는 기법입니다 [1-3]. 주로 자신의 고유한 코딩 스타일을 숨기는 난독화(obfuscation)와 다른 프로그래머의 스타일을 흉내 내는 모방(mimicry) 기술을 사용합니다 [2-4]. 이는 감시와 검열에 맞서 프라이버시 향상 도구를 개발하는 오픈소스 기여자들이 신원 노출로 인한 탄압을 피하기 위한 핵심적인 방어 수단으로 연구되고 있습니다 [5-7]. @@ -24,11 +24,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Adversarial Code Stylometry" - **정책 변화:** AI 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Code Stylometry]], [[Obfuscation]], [[Mimicry Attack]], [[StyleCounsel]] -- **Projects/Contexts:** [[오픈소스 기여자 익명성 보장]], [[검열 우회 및 프라이버시 보호 도구 개발]] +- **Related Topics:** [[Code Stylometry (코드 문체론)|Code Stylometry]], Obfuscation, Mimicry Attack, [[StyleCounsel|StyleCounsel]] +- **Projects/Contexts:** 오픈소스 기여자 익명성 보장, 검열 우회 및 프라이버시 보호 도구 개발 - **Contradictions/Notes:** Caliskan-Islam 등의 기존 연구에서는 'Stunnix'와 같은 상용 난독화 도구를 사용해도 분류기의 식별 정확도가 거의 떨어지지 않는다고 보고했습니다. 그러나 Simko 등의 적대적 연구에서는 실험 참가자들이 표면적인 수준의 변수명 교체나 국소적인 구조 변경 등 간단한 조작을 가하는 것만으로도 기계 학습 모델을 성공적으로 속일 수 있음을 입증하며 기존 분류 시스템의 취약성과 한계를 지적했습니다 [11, 20]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Adversarial Code Stylometry.md]] +- Raw Source: 00_Raw/2026-04-20/Adversarial Code Stylometry.md --- diff --git a/01_Archive/2026-04-20/Aerospace Flight Simulation.md b/01_Archive/2026-04-20/Aerospace Flight Simulation.md index 34b3f74c..6100ece4 100644 --- a/01_Archive/2026-04-20/Aerospace Flight Simulation.md +++ b/01_Archive/2026-04-20/Aerospace Flight Simulation.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-FE444C -category: "[[10_Wiki/💡 Topics/Physics & Simulation]]" +category: "10_Wiki/💡 Topics/Physics & Simulation" confidence_score: 0.95 tags: [] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Batch 10 - Wikified Aerospace Flight Simulation" --- -# [[Aerospace Flight Simulation]] +# [[Aerospace Flight Simulation|Aerospace Flight Simulation]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 핵심 내용 요약 예정 @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Batch 10 - Wikified Aerospace Flight Simulation" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Aerospace Flight Simulation.md]] +- Raw Source: 00_Raw/2026-04-20/Aerospace Flight Simulation.md --- diff --git a/01_Archive/2026-04-20/Affective Computing.md b/01_Archive/2026-04-20/Affective Computing.md index 86f6f21c..68b4504c 100644 --- a/01_Archive/2026-04-20/Affective Computing.md +++ b/01_Archive/2026-04-20/Affective Computing.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-E4FCEF -category: "[[10_Wiki/💡 Topics/AI & Psychology]]" +category: "10_Wiki/💡 Topics/AI & Psychology" confidence_score: 0.95 tags: [] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Batch 10 - Wikified Affective Computing" --- -# [[Affective Computing]] +# [[Affective Computing|Affective Computing]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 핵심 내용 요약 예정 @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Batch 10 - Wikified Affective Computing" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Affective Computing.md]] +- Raw Source: 00_Raw/2026-04-20/Affective Computing.md --- diff --git a/01_Archive/2026-04-20/Affective User Interfaces (AUI).md b/01_Archive/2026-04-20/Affective User Interfaces (AUI).md index b426e43f..4bb6d7f1 100644 --- a/01_Archive/2026-04-20/Affective User Interfaces (AUI).md +++ b/01_Archive/2026-04-20/Affective User Interfaces (AUI).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-30D321 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.95 tags: [] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Batch 10 - Wikified Affective User Interfaces (AUI)" --- -# [[Affective User Interfaces (AUI)]] +# [[Affective User Interfaces (AUI)|Affective User Interfaces (AUI)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 핵심 내용 요약 예정 @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Batch 10 - Wikified Affective User Interfaces (AUI ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Affective User Interfaces (AUI).md]] +- Raw Source: 00_Raw/2026-04-20/Affective User Interfaces (AUI).md --- diff --git a/01_Archive/2026-04-20/Agency and Player Autonomy.md b/01_Archive/2026-04-20/Agency and Player Autonomy.md index c97e69c7..9ae37ab7 100644 --- a/01_Archive/2026-04-20/Agency and Player Autonomy.md +++ b/01_Archive/2026-04-20/Agency and Player Autonomy.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-72AAF4 -category: "[[10_Wiki/💡 Topics/Game Design]]" +category: "10_Wiki/💡 Topics/Game Design" confidence_score: 0.95 tags: [] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Batch 10 - Wikified Agency and Player Autonomy" --- -# [[Agency and Player Autonomy]] +# [[Agency and Player Autonomy|Agency and Player Autonomy]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 핵심 내용 요약 예정 @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Batch 10 - Wikified Agency and Player Autonomy" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Agency and Player Autonomy.md]] +- Raw Source: 00_Raw/2026-04-20/Agency and Player Autonomy.md --- diff --git a/01_Archive/2026-04-20/Agency-Narrative Integration.md b/01_Archive/2026-04-20/Agency-Narrative Integration.md index 3567a743..99714f0f 100644 --- a/01_Archive/2026-04-20/Agency-Narrative Integration.md +++ b/01_Archive/2026-04-20/Agency-Narrative Integration.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-2E74EC -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Agency-Narrative Integration" --- -# [[Agency-Narrative Integration]] +# [[Agency-Narrative Integration|Agency-Narrative Integration]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Agency-Narrative Integration" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Agency-Narrative Integration.md]] +- Raw Source: 00_Raw/2026-04-20/Agency-Narrative Integration.md --- diff --git a/01_Archive/2026-04-20/Agency-in-Game-Design.md b/01_Archive/2026-04-20/Agency-in-Game-Design.md index 2670b0bc..62949186 100644 --- a/01_Archive/2026-04-20/Agency-in-Game-Design.md +++ b/01_Archive/2026-04-20/Agency-in-Game-Design.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-0D4B33 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Agency-in-Game-Design" --- -# [[Agency-in-Game-Design]] +# [[Agency-in-Game-Design|Agency-in-Game-Design]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Agency-in-Game-Design" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Agency-in-Game-Design.md]] +- Raw Source: 00_Raw/2026-04-20/Agency-in-Game-Design.md --- diff --git a/01_Archive/2026-04-20/Agent Communication Protocol (에이전트 통신 규약).md b/01_Archive/2026-04-20/Agent Communication Protocol (에이전트 통신 규약).md index 9bfe1d80..a97a99a5 100644 --- a/01_Archive/2026-04-20/Agent Communication Protocol (에이전트 통신 규약).md +++ b/01_Archive/2026-04-20/Agent Communication Protocol (에이전트 통신 규약).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-9B328D -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Agent Communication Protocol (에이전트 통신 규약)" --- -# [[Agent Communication Protocol (에이전트 통신 규약)]] +# [[Agent Communication Protocol (에이전트 통신 규약)|Agent Communication Protocol (에이전트 통신 규약)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Agent Communication Protocol ( ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Agent Communication Protocol (에이전트 통신 규약).md]] +- Raw Source: 00_Raw/2026-04-20/Agent Communication Protocol (에이전트 통신 규약).md --- diff --git a/01_Archive/2026-04-20/Agent-Based Modeling (ABM).md b/01_Archive/2026-04-20/Agent-Based Modeling (ABM).md index 9ce7b74b..3e24310c 100644 --- a/01_Archive/2026-04-20/Agent-Based Modeling (ABM).md +++ b/01_Archive/2026-04-20/Agent-Based Modeling (ABM).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-50111B -category: "[[10_Wiki/💡 Topics/Simulation & Math]]" +category: "10_Wiki/💡 Topics/Simulation & Math" confidence_score: 0.95 tags: [] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Batch 10 - Wikified Agent-Based Modeling (ABM)" --- -# [[Agent-Based Modeling (ABM)]] +# [[Agent-Based Modeling (ABM)|Agent-Based Modeling (ABM)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 핵심 내용 요약 예정 @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Batch 10 - Wikified Agent-Based Modeling (ABM)" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Agent-Based Modeling (ABM).md]] +- Raw Source: 00_Raw/2026-04-20/Agent-Based Modeling (ABM).md --- diff --git a/01_Archive/2026-04-20/Agent-Based Modeling.md b/01_Archive/2026-04-20/Agent-Based Modeling.md index 04a45582..6d08e9bc 100644 --- a/01_Archive/2026-04-20/Agent-Based Modeling.md +++ b/01_Archive/2026-04-20/Agent-Based Modeling.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-64B5F2 -category: "[[10_Wiki/💡 Topics/Psychology & Behavior]]" +category: "10_Wiki/💡 Topics/Psychology & Behavior" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Agent-Based Modeling" --- -# [[Agent-Based Modeling]] +# [[Agent-Based Modeling|Agent-Based Modeling]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Agent-Based Modeling" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Agent-Based Modeling.md]] +- Raw Source: 00_Raw/2026-04-20/Agent-Based Modeling.md --- diff --git a/01_Archive/2026-04-20/Agent-Based-Modeling.md b/01_Archive/2026-04-20/Agent-Based-Modeling.md index 08dbd016..f9d12135 100644 --- a/01_Archive/2026-04-20/Agent-Based-Modeling.md +++ b/01_Archive/2026-04-20/Agent-Based-Modeling.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-419E37 -category: "[[10_Wiki/💡 Topics/Psychology & Behavior]]" +category: "10_Wiki/💡 Topics/Psychology & Behavior" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Agent-Based-Modeling" --- -# [[Agent-Based-Modeling]] +# [[Agent-Based-Modeling|Agent-Based-Modeling]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Agent-Based-Modeling" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Agent-Based-Modeling.md]] +- Raw Source: 00_Raw/2026-04-20/Agent-Based-Modeling.md --- diff --git a/01_Archive/2026-04-20/Agile-Software-Development-Life-Cycle.md b/01_Archive/2026-04-20/Agile-Software-Development-Life-Cycle.md deleted file mode 100644 index e69de29b..00000000 diff --git a/01_Archive/2026-04-20/Agile-UX-Integration.md b/01_Archive/2026-04-20/Agile-UX-Integration.md index 402c2a92..caf29506 100644 --- a/01_Archive/2026-04-20/Agile-UX-Integration.md +++ b/01_Archive/2026-04-20/Agile-UX-Integration.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-1363FF -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.95 tags: [] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Batch 10 - Wikified Agile-UX-Integration" --- -# [[Agile-UX-Integration]] +# [[Agile-UX-Integration|Agile-UX-Integration]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 핵심 내용 요약 예정 @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Batch 10 - Wikified Agile-UX-Integration" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Agile-UX-Integration.md]] +- Raw Source: 00_Raw/2026-04-20/Agile-UX-Integration.md --- diff --git a/01_Archive/2026-04-20/Albion Online (Full LootPlayer-Driven Production).md b/01_Archive/2026-04-20/Albion Online (Full LootPlayer-Driven Production).md index 3af923f1..d0cbb844 100644 --- a/01_Archive/2026-04-20/Albion Online (Full LootPlayer-Driven Production).md +++ b/01_Archive/2026-04-20/Albion Online (Full LootPlayer-Driven Production).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-750784 -category: "[[10_Wiki/💡 Topics/Game Design]]" +category: "10_Wiki/💡 Topics/Game Design" confidence_score: 0.95 tags: [] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Batch 11 - Wikified Albion Online (Full Loot/Player-Driven Production)" --- -# [[Albion Online (Full Loot/Player-Driven Production)]] +# [[Albion Online (Full LootPlayer-Driven Production)|Albion Online (Full Loot/Player-Driven Production)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 작업 중 @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Batch 11 - Wikified Albion Online (Full Loot/Playe ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Albion Online (Full Loot_Player-Driven Production).md]] +- Raw Source: 00_Raw/2026-04-20/Albion Online (Full Loot_Player-Driven Production).md --- diff --git a/01_Archive/2026-04-20/Albion Online (Full Loot_Player-Driven Production).md b/01_Archive/2026-04-20/Albion Online (Full Loot_Player-Driven Production).md index dace6460..d6c5e07e 100644 --- a/01_Archive/2026-04-20/Albion Online (Full Loot_Player-Driven Production).md +++ b/01_Archive/2026-04-20/Albion Online (Full Loot_Player-Driven Production).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-DCA70F -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Albion Online (Full Loot_Player-Driven Production)" --- -# [[Albion Online (Full Loot_Player-Driven Production)]] +# [[Albion Online (Full Loot_Player-Driven Production)|Albion Online (Full Loot_Player-Driven Production)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Albion Online (Full Loot_Playe ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Albion Online (Full Loot_Player-Driven Production).md]] +- Raw Source: 00_Raw/2026-04-20/Albion Online (Full Loot_Player-Driven Production).md --- diff --git a/01_Archive/2026-04-20/Algebraic-Data-Types-in-TypeScript.md b/01_Archive/2026-04-20/Algebraic-Data-Types-in-TypeScript.md index 0fe9229f..896b8330 100644 --- a/01_Archive/2026-04-20/Algebraic-Data-Types-in-TypeScript.md +++ b/01_Archive/2026-04-20/Algebraic-Data-Types-in-TypeScript.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-9FC7C3 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.95 tags: [] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Batch 11 - Wikified Algebraic-Data-Types-in-TypeScript" --- -# [[Algebraic-Data-Types-in-TypeScript]] +# [[Algebraic-Data-Types-in-TypeScript|Algebraic-Data-Types-in-TypeScript]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 작업 중 @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Batch 11 - Wikified Algebraic-Data-Types-in-TypeSc ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Algebraic-Data-Types-in-TypeScript.md]] +- Raw Source: 00_Raw/2026-04-20/Algebraic-Data-Types-in-TypeScript.md --- diff --git a/01_Archive/2026-04-20/Algebraic-Data-Types.md b/01_Archive/2026-04-20/Algebraic-Data-Types.md index ece755b1..13c95c73 100644 --- a/01_Archive/2026-04-20/Algebraic-Data-Types.md +++ b/01_Archive/2026-04-20/Algebraic-Data-Types.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-A4D1B5 -category: "[[10_Wiki/💡 Topics/Computer Science & Math]]" +category: "10_Wiki/💡 Topics/Computer Science & Math" confidence_score: 0.95 tags: [] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Batch 11 - Wikified Algebraic-Data-Types" --- -# [[Algebraic-Data-Types]] +# [[Algebraic-Data-Types|Algebraic-Data-Types]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 작업 중 @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Batch 11 - Wikified Algebraic-Data-Types" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Algebraic-Data-Types.md]] +- Raw Source: 00_Raw/2026-04-20/Algebraic-Data-Types.md --- diff --git a/01_Archive/2026-04-20/Algorithmic Bias in Art.md b/01_Archive/2026-04-20/Algorithmic Bias in Art.md index d45c0b7d..3b84caae 100644 --- a/01_Archive/2026-04-20/Algorithmic Bias in Art.md +++ b/01_Archive/2026-04-20/Algorithmic Bias in Art.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-DEC2D9 -category: "[[10_Wiki/💡 Topics/AI & Ethics]]" +category: "10_Wiki/💡 Topics/AI & Ethics" confidence_score: 0.95 tags: [] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Batch 11 - Wikified Algorithmic Bias in Art" --- -# [[Algorithmic Bias in Art]] +# [[Algorithmic Bias in Art|Algorithmic Bias in Art]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 작업 중 @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Batch 11 - Wikified Algorithmic Bias in Art" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Algorithmic Bias in Art.md]] +- Raw Source: 00_Raw/2026-04-20/Algorithmic Bias in Art.md --- diff --git a/01_Archive/2026-04-20/Algorithmic Decision Making.md b/01_Archive/2026-04-20/Algorithmic Decision Making.md index 4c83e582..cba84efd 100644 --- a/01_Archive/2026-04-20/Algorithmic Decision Making.md +++ b/01_Archive/2026-04-20/Algorithmic Decision Making.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-E80494 -category: "[[10_Wiki/💡 Topics/AI & Ethics]]" +category: "10_Wiki/💡 Topics/AI & Ethics" confidence_score: 0.95 tags: [] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Batch 11 - Wikified Algorithmic Decision Making" --- -# [[Algorithmic Decision Making]] +# [[Algorithmic Decision Making|Algorithmic Decision Making]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 작업 중 @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Batch 11 - Wikified Algorithmic Decision Making" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Algorithmic Decision Making.md]] +- Raw Source: 00_Raw/2026-04-20/Algorithmic Decision Making.md --- diff --git a/01_Archive/2026-04-20/Algorithmic Game Theory.md b/01_Archive/2026-04-20/Algorithmic Game Theory.md index bae0f0d9..89bf5a5a 100644 --- a/01_Archive/2026-04-20/Algorithmic Game Theory.md +++ b/01_Archive/2026-04-20/Algorithmic Game Theory.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-CD6723 -category: "[[10_Wiki/💡 Topics/Game Design & Math]]" +category: "10_Wiki/💡 Topics/Game Design & Math" confidence_score: 0.95 tags: [] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Batch 11 - Wikified Algorithmic Game Theory" --- -# [[Algorithmic Game Theory]] +# [[Algorithmic Game Theory|Algorithmic Game Theory]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 작업 중 @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Batch 11 - Wikified Algorithmic Game Theory" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Algorithmic Game Theory.md]] +- Raw Source: 00_Raw/2026-04-20/Algorithmic Game Theory.md --- diff --git a/01_Archive/2026-04-20/Algorithmic Governance.md b/01_Archive/2026-04-20/Algorithmic Governance.md index 7514c6cc..7d2b1067 100644 --- a/01_Archive/2026-04-20/Algorithmic Governance.md +++ b/01_Archive/2026-04-20/Algorithmic Governance.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-243848 -category: "[[10_Wiki/💡 Topics/Sociology & Tech]]" +category: "10_Wiki/💡 Topics/Sociology & Tech" confidence_score: 0.95 tags: [] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Batch 11 - Wikified Algorithmic Governance" --- -# [[Algorithmic Governance]] +# [[Algorithmic Governance|Algorithmic Governance]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 작업 중 @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Batch 11 - Wikified Algorithmic Governance" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Algorithmic Governance.md]] +- Raw Source: 00_Raw/2026-04-20/Algorithmic Governance.md --- diff --git a/01_Archive/2026-04-20/Algorithmic Mechanism Design.md b/01_Archive/2026-04-20/Algorithmic Mechanism Design.md index 2b0226b5..98403b8d 100644 --- a/01_Archive/2026-04-20/Algorithmic Mechanism Design.md +++ b/01_Archive/2026-04-20/Algorithmic Mechanism Design.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-29EF85 -category: "[[10_Wiki/💡 Topics/Economics & Algorithms]]" +category: "10_Wiki/💡 Topics/Economics & Algorithms" confidence_score: 0.95 tags: [] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Batch 11 - Wikified Algorithmic Mechanism Design" --- -# [[Algorithmic Mechanism Design]] +# [[Algorithmic Mechanism Design|Algorithmic Mechanism Design]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 작업 중 @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Batch 11 - Wikified Algorithmic Mechanism Design" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Algorithmic Mechanism Design.md]] +- Raw Source: 00_Raw/2026-04-20/Algorithmic Mechanism Design.md --- diff --git a/01_Archive/2026-04-20/Algorithmic Rhetoric.md b/01_Archive/2026-04-20/Algorithmic Rhetoric.md index 199a0519..4a4399c2 100644 --- a/01_Archive/2026-04-20/Algorithmic Rhetoric.md +++ b/01_Archive/2026-04-20/Algorithmic Rhetoric.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-9E51FB -category: "[[10_Wiki/💡 Topics/Communication & Tech]]" +category: "10_Wiki/💡 Topics/Communication & Tech" confidence_score: 0.95 tags: [] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Batch 11 - Wikified Algorithmic Rhetoric" --- -# [[Algorithmic Rhetoric]] +# [[Algorithmic Rhetoric|Algorithmic Rhetoric]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 작업 중 @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Batch 11 - Wikified Algorithmic Rhetoric" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Algorithmic Rhetoric.md]] +- Raw Source: 00_Raw/2026-04-20/Algorithmic Rhetoric.md --- diff --git a/01_Archive/2026-04-20/Algorithmic-Biology.md b/01_Archive/2026-04-20/Algorithmic-Biology.md index d1aeb177..b10f1553 100644 --- a/01_Archive/2026-04-20/Algorithmic-Biology.md +++ b/01_Archive/2026-04-20/Algorithmic-Biology.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-37F130 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Algorithmic-Biology" --- -# [[Algorithmic-Biology]] +# [[Algorithmic-Biology|Algorithmic-Biology]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Algorithmic-Biology" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Algorithmic-Biology.md]] +- Raw Source: 00_Raw/2026-04-20/Algorithmic-Biology.md --- diff --git a/01_Archive/2026-04-20/Algorithmic-Game-Theory.md b/01_Archive/2026-04-20/Algorithmic-Game-Theory.md index 10dab570..3831f77d 100644 --- a/01_Archive/2026-04-20/Algorithmic-Game-Theory.md +++ b/01_Archive/2026-04-20/Algorithmic-Game-Theory.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-6BF52C -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Algorithmic-Game-Theory" --- -# [[Algorithmic-Game-Theory]] +# [[Algorithmic-Game-Theory|Algorithmic-Game-Theory]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Algorithmic-Game-Theory" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Algorithmic-Game-Theory.md]] +- Raw Source: 00_Raw/2026-04-20/Algorithmic-Game-Theory.md --- diff --git a/01_Archive/2026-04-20/Algorithmic-Governance.md b/01_Archive/2026-04-20/Algorithmic-Governance.md index 7071be05..4986aa06 100644 --- a/01_Archive/2026-04-20/Algorithmic-Governance.md +++ b/01_Archive/2026-04-20/Algorithmic-Governance.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-DC50FE -category: "[[10_Wiki/💡 Topics/Sociology & Tech]]" +category: "10_Wiki/💡 Topics/Sociology & Tech" confidence_score: 0.95 tags: [] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Mega Batch - Wikified Algorithmic-Governance" --- -# [[Algorithmic-Governance]] +# [[Algorithmic-Governance|Algorithmic-Governance]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 핵심 요약 작업 진행 중 @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Mega Batch - Wikified Algorithmic-Governance" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Algorithmic-Governance.md]] +- Raw Source: 00_Raw/2026-04-20/Algorithmic-Governance.md --- diff --git a/01_Archive/2026-04-20/Allocation Timeline(할당 타임라인).md b/01_Archive/2026-04-20/Allocation Timeline(할당 타임라인).md index 8e1bd65a..a5975b6b 100644 --- a/01_Archive/2026-04-20/Allocation Timeline(할당 타임라인).md +++ b/01_Archive/2026-04-20/Allocation Timeline(할당 타임라인).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-891010 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Allocation Timeline(할당 타임라인)" --- -# [[Allocation Timeline(할당 타임라인)]] +# [[Allocation Timeline(할당 타임라인)|Allocation Timeline(할당 타임라인)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > Allocation Timeline(할당 타임라인)은 Chrome 및 Edge DevTools에서 제공하는 프로파일링 도구로, 적절하게 가비지 컬렉션(Garbage Collection)되지 않고 메모리를 계속 점유하는 객체를 찾아 메모리 누수를 추적하는 데 사용됩니다 [1, 2]. 이 도구는 힙 프로파일러의 상세한 스냅샷 정보와 타임라인 패널의 점진적 추적 기능을 결합하여, 기록 중 발생하는 모든 메모리 할당을 스택 트레이스와 함께 기록합니다 [1-3]. 결과적으로 시각적인 막대(파란색 및 회색)를 통해 메모리에 남아있는 객체와 이미 수거된 객체를 구별하여 보여줍니다 [3-5]. @@ -20,11 +20,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Allocation Timeline(할당 타 - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Garbage Collection]], [[Memory Leak]], [[Heap Snapshot]] -- **Projects/Contexts:** [[Chrome DevTools]], [[V8 Engine]] +- **Related Topics:** [[Garbage Collection|Garbage Collection]], [[Memory Leak|Memory Leak]], [[Heap Snapshot|Heap Snapshot]] +- **Projects/Contexts:** [[Chrome DevTools|Chrome DevTools]], [[V8 Engine|V8 Engine]] - **Contradictions/Notes:** 소스에 관련 정보가 부족합니다. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Allocation Timeline(할당 타임라인).md]] +- Raw Source: 00_Raw/2026-04-20/Allocation Timeline(할당 타임라인).md --- diff --git a/01_Archive/2026-04-20/Allocation Timeline.md b/01_Archive/2026-04-20/Allocation Timeline.md index ba0b6a84..f75e8416 100644 --- a/01_Archive/2026-04-20/Allocation Timeline.md +++ b/01_Archive/2026-04-20/Allocation Timeline.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-B75DFC -category: "[[10_Wiki/💡 Topics/Memory & Systems]]" +category: "10_Wiki/💡 Topics/Memory & Systems" confidence_score: 0.95 tags: [] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Mega Batch - Wikified Allocation Timeline" --- -# [[Allocation Timeline]] +# [[Allocation Timeline|Allocation Timeline]] ## 📌 한 줄 통찰 (The Karpathy Summary) > **Allocation Timeline**(또는 Allocation instrumentation on timeline)은 Chrome DevTools의 Memory 패널에서 제공하는 프로파일링 도구로, 시간 경과에 따른 메모리 할당을 기록하고 추적하여 애플리케이션의 메모리 누수를 진단하는 데 사용됩니다 [1-3]. 이 도구는 힙 프로파일러(Heap Profiler)의 상세한 스냅샷 정보와 타임라인 패널의 증분 업데이트 및 추적 기능을 결합하여 객체의 생성 위치와 유지 경로(retaining path)를 실시간으로 식별할 수 있게 해줍니다 [2, 4, 5]. @@ -25,11 +25,11 @@ github_commit: "[P-Reinforce] Mega Batch - Wikified Allocation Timeline" - **정책 변화:** Memory & Systems 카테고리의 전문성 확보 및 링크 밀도 최적화. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Heap Snapshot]], [[Garbage Collection]], [[Memory Leak]], [[Retaining Path]], [[V8 Heap Architecture]] -- **Projects/Contexts:** [[Chrome DevTools]], [[V8 Engine]] +- **Related Topics:** [[Heap Snapshot|Heap Snapshot]], [[Garbage Collection|Garbage Collection]], [[Memory Leak|Memory Leak]], [[Retaining Path|Retaining Path]], [[V8 Heap Architecture|V8 Heap Architecture]] +- **Projects/Contexts:** [[Chrome DevTools|Chrome DevTools]], [[V8 Engine|V8 Engine]] - **Contradictions/Notes:** 소스 전반에 걸쳐 내용의 모순은 없습니다. 다양한 소스가 일관되게 Allocation Timeline의 파란색/회색 막대의 의미와 메모리 누수를 추적하기 위한 스택 트레이스 및 Retainer 분석의 유용성을 강조하고 있습니다. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Allocation Timeline.md]] +- Raw Source: 00_Raw/2026-04-20/Allocation Timeline.md --- diff --git a/01_Archive/2026-04-20/Alpha Blending.md b/01_Archive/2026-04-20/Alpha Blending.md index 7963e00b..2145df69 100644 --- a/01_Archive/2026-04-20/Alpha Blending.md +++ b/01_Archive/2026-04-20/Alpha Blending.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-25F1DA -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.95 tags: [] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Mega Batch - Wikified Alpha Blending" --- -# [[Alpha Blending]] +# [[Alpha Blending|Alpha Blending]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 투명하거나 반투명한 객체를 렌더링할 때 시각적 결함 없이 정확한 투명도를 표현하기 위한 렌더링 혼합 기법입니다 [1]. 올바른 알파 블렌딩 결과를 얻기 위해서는 반드시 객체를 '뒤에서 앞으로(Back-to-Front)' 순서로 정렬하여 그려야 한다는 제약이 있습니다 [1]. 그 외 알파 블렌딩의 구체적인 수학적 원리나 연산식에 대해서는 소스에 관련 정보가 부족합니다. @@ -22,11 +22,11 @@ github_commit: "[P-Reinforce] Mega Batch - Wikified Alpha Blending" - **정책 변화:** Graphics & Performance 카테고리의 전문성 확보 및 링크 밀도 최적화. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Transparency Sorting]], [[InstancedMesh]], [[Overdraw]] +- **Related Topics:** Transparency Sorting, [[InstancedMesh|InstancedMesh]], [[Overdraw|Overdraw]] - **Projects/Contexts:** 대규모 유리창 건물이나 투명한 숲 등 다수의 반투명 객체를 `InstancedMesh` 등을 사용하여 실시간으로 렌더링하고 최적화해야 하는 웹 그래픽스 및 게임 프로젝트 맥락 [1, 2]. - **Contradictions/Notes:** 소스에 관련 정보가 부족합니다. (제공된 소스에서는 알파 블렌딩 자체의 개념보다는, 투명 객체 렌더링 정렬 문제의 원인으로서만 간략히 언급되고 있습니다.) --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Alpha Blending.md]] +- Raw Source: 00_Raw/2026-04-20/Alpha Blending.md --- diff --git a/01_Archive/2026-04-20/AlphaGo (Monte Carlo Tree Search RL)] [Autonomous Driving Simulation] [Robotic Manipulation.md b/01_Archive/2026-04-20/AlphaGo (Monte Carlo Tree Search RL)] [Autonomous Driving Simulation] [Robotic Manipulation.md index f4052fbe..924322e2 100644 --- a/01_Archive/2026-04-20/AlphaGo (Monte Carlo Tree Search RL)] [Autonomous Driving Simulation] [Robotic Manipulation.md +++ b/01_Archive/2026-04-20/AlphaGo (Monte Carlo Tree Search RL)] [Autonomous Driving Simulation] [Robotic Manipulation.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-4BB54E -category: "[[10_Wiki/💡 Topics/Software Architecture]]" +category: "10_Wiki/💡 Topics/Software Architecture" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - AlphaGo (Monte Carlo Tree Search RL)] [Autonomous Driving Simulation] [Robotic Manipulation" --- -# [[AlphaGo (Monte Carlo Tree Search RL)] [Autonomous Driving Simulation] [Robotic Manipulation]] +# [[AlphaGo (Monte Carlo Tree Search RL)] [Autonomous Driving Simulation] [Robotic Manipulation|AlphaGo (Monte Carlo Tree Search RL)] [Autonomous Driving Simulation] [Robotic Manipulation]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - AlphaGo (Monte Carlo Tree Sear ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/AlphaGo (Monte Carlo Tree Search + RL)], [Autonomous Driving Simulation], [Robotic Manipulation.md]] +- Raw Source: 00_Raw/2026-04-20/AlphaGo (Monte Carlo Tree Search + RL)], [Autonomous Driving Simulation], [Robotic Manipulation.md --- diff --git a/01_Archive/2026-04-20/AlphaGo (Monte Carlo Tree Search + RL)], [Autonomous Driving Simulation], [Robotic Manipulation.md b/01_Archive/2026-04-20/AlphaGo (Monte Carlo Tree Search + RL)], [Autonomous Driving Simulation], [Robotic Manipulation.md index c84f7080..bef4a461 100644 --- a/01_Archive/2026-04-20/AlphaGo (Monte Carlo Tree Search + RL)], [Autonomous Driving Simulation], [Robotic Manipulation.md +++ b/01_Archive/2026-04-20/AlphaGo (Monte Carlo Tree Search + RL)], [Autonomous Driving Simulation], [Robotic Manipulation.md @@ -1,4 +1,4 @@ -[[AlphaGo (Monte Carlo Tree Search + RL)], [Autonomous Driving Simulation], [Robotic Manipulation]] +[[AlphaGo (Monte Carlo Tree Search + RL)], [Autonomous Driving Simulation], [Robotic Manipulation|AlphaGo (Monte Carlo Tree Search + RL)], [Autonomous Driving Simulation], [Robotic Manipulation]] 📌 Brief Summary This research intersection explores the convergence of decision-making architectures, specifically combining Monte Carlo Tree Search (MCTS) with Deep Reinforcement Learning (DRL), to solve high-dimensional sequential decision problems. The synthesis focuses on applying the strategic look-ahead capabilities of AlphaGo-style algorithms to the continuous state-action spaces found in autonomous vehicle trajectory planning and complex multi-degree-of-freedom robotic manipulation tasks within simulated environments. @@ -18,8 +18,8 @@ This research intersection explores the convergence of decision-making architect * The synthesis of these fields points toward a unified framework for "Model-Based Reinforcement Learning" (MBRL). In this paradigm, the agent learns a world model (the simulator) and uses MCTS to perform planning within that learned latent space. This reduces sample complexity and improves the safety guarantees required for both autonomous driving and human-collaborative robotics. 🔗 Knowledge Connections -* Related Topics: [[Model-Based Reinforcement Learning (MBRL)]], [[Sim-to-Real Transfer]], [[Multi-Agent Reinforcement Learning (MARL)]], [[Differentiable Physics Engines]] -* Projects/Contexts: [[DeepMind AlphaZero]], [[CARLA Simulator]], [[NVIDIA Isaac Gym]], [[OpenAI Gym/Gymnasium]] +* Related Topics: Model-Based Reinforcement Learning (MBRL), Sim-to-Real Transfer, Multi-Agent Reinforcement Learning (MARL), Differentiable Physics Engines +* Projects/Contexts: DeepMind AlphaZero, CARLA Simulator, NVIDIA Isaac Gym, OpenAI Gym/Gymnasium * Contradictions/Notes: A major ongoing debate in the field is the "Computational Bottleneck": while MCTS provides superior strategic foresight, the computational cost of running tree searches in real-time for high-frequency robotic control or high-speed autonomous driving remains a significant barrier to deployment compared to reactive, end-to-end neural policies. Last updated: 2026-04-16 \ No newline at end of file diff --git a/01_Archive/2026-04-20/AlphaZero Strategy.md b/01_Archive/2026-04-20/AlphaZero Strategy.md index 06feed44..c93a2f25 100644 --- a/01_Archive/2026-04-20/AlphaZero Strategy.md +++ b/01_Archive/2026-04-20/AlphaZero Strategy.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-5267ED -category: "[[10_Wiki/💡 Topics/AI & Games]]" +category: "10_Wiki/💡 Topics/AI & Games" confidence_score: 0.95 tags: [] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Mega Batch - Wikified AlphaZero Strategy" --- -# [[AlphaZero Strategy]] +# [[AlphaZero Strategy|AlphaZero Strategy]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 핵심 요약 작업 진행 중 @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Mega Batch - Wikified AlphaZero Strategy" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/AlphaZero Strategy.md]] +- Raw Source: 00_Raw/2026-04-20/AlphaZero Strategy.md --- diff --git a/01_Archive/2026-04-20/Amazon-AWS-Formal-Verification.md b/01_Archive/2026-04-20/Amazon-AWS-Formal-Verification.md index 8a465f34..594ecd6c 100644 --- a/01_Archive/2026-04-20/Amazon-AWS-Formal-Verification.md +++ b/01_Archive/2026-04-20/Amazon-AWS-Formal-Verification.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-F8937D -category: "[[10_Wiki/💡 Topics/Software Reliability]]" +category: "10_Wiki/💡 Topics/Software Reliability" confidence_score: 0.95 tags: [] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Mega Batch - Wikified Amazon-AWS-Formal-Verification" --- -# [[Amazon-AWS-Formal-Verification]] +# [[Amazon-AWS-Formal-Verification|Amazon-AWS-Formal-Verification]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 핵심 요약 작업 진행 중 @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Mega Batch - Wikified Amazon-AWS-Formal-Verificati ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Amazon-AWS-Formal-Verification.md]] +- Raw Source: 00_Raw/2026-04-20/Amazon-AWS-Formal-Verification.md --- diff --git a/01_Archive/2026-04-20/Ambient Contexts.md b/01_Archive/2026-04-20/Ambient Contexts.md index f3745772..f6a6f280 100644 --- a/01_Archive/2026-04-20/Ambient Contexts.md +++ b/01_Archive/2026-04-20/Ambient Contexts.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-138364 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.95 tags: [] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Mega Batch - Wikified Ambient Contexts" --- -# [[Ambient Contexts]] +# [[Ambient Contexts|Ambient Contexts]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 핵심 요약 작업 진행 중 @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Mega Batch - Wikified Ambient Contexts" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Ambient Contexts.md]] +- Raw Source: 00_Raw/2026-04-20/Ambient Contexts.md --- diff --git a/01_Archive/2026-04-20/Ambient Declarations.md b/01_Archive/2026-04-20/Ambient Declarations.md index 244c0401..6173ff60 100644 --- a/01_Archive/2026-04-20/Ambient Declarations.md +++ b/01_Archive/2026-04-20/Ambient Declarations.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-F31A94 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.95 tags: [] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Mega Batch - Wikified Ambient Declarations" --- -# [[Ambient Declarations]] +# [[Ambient Declarations|Ambient Declarations]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 핵심 요약 작업 진행 중 @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Mega Batch - Wikified Ambient Declarations" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Ambient Declarations.md]] +- Raw Source: 00_Raw/2026-04-20/Ambient Declarations.md --- diff --git a/01_Archive/2026-04-20/Ambient-Declarations.md b/01_Archive/2026-04-20/Ambient-Declarations.md index 6743dbbf..8123f56f 100644 --- a/01_Archive/2026-04-20/Ambient-Declarations.md +++ b/01_Archive/2026-04-20/Ambient-Declarations.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-956995 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Ambient-Declarations" --- -# [[Ambient-Declarations]] +# [[Ambient-Declarations|Ambient-Declarations]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Ambient-Declarations" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Ambient-Declarations.md]] +- Raw Source: 00_Raw/2026-04-20/Ambient-Declarations.md --- diff --git a/01_Archive/2026-04-20/Amdahl's Law (암달의 법칙).md b/01_Archive/2026-04-20/Amdahl's Law (암달의 법칙).md index 56baca8e..ccea0a19 100644 --- a/01_Archive/2026-04-20/Amdahl's Law (암달의 법칙).md +++ b/01_Archive/2026-04-20/Amdahl's Law (암달의 법칙).md @@ -1,4 +1,4 @@ -[[Amdahl's Law (암달의 법칙, AI 성능의 병목)]] +Amdahl's Law (암달의 법칙, AI 성능의 병목) 📌 Brief Summary @@ -63,8 +63,8 @@ Amdahl's Law는 어떤 시스템의 일부 성능을 개선했을 때, 전체 🔗 Knowledge Connections -- [[Diminishing Returns (한계 수익 체감)]], [[Scaling Laws (스케일링 법칙)]], [[MoE (Mixture of Experts)]], [[Adaptive Compute (적응형 계산량 조절)]] -- **Projects/Contexts:** [[AI 추론 가속화 및 하드웨어 최적화]] +- [[Diminishing Returns (한계 수익 체감)|Diminishing Returns (한계 수익 체감)]], Scaling Laws (스케일링 법칙), MoE (Mixture of Experts), [[Adaptive Compute (적응형 계산량 조절)|Adaptive Compute (적응형 계산량 조절)]] +- **Projects/Contexts:** AI 추론 가속화 및 하드웨어 최적화 - **Contradictions/Notes:** - **Gustafson's Law**: 암달의 법칙이 고정된 작업량에 대한 효율을 따진다면, 구스타프슨의 법칙은 가용한 자원에 맞춰 작업량을 늘리면 성능 향상이 계속될 수 있음을 시사함. - **신규 키워드**: `Bottleneck`, `Memory Wall`, `Bandwidth`, `Serial Processing` → 탐색 큐 추가. diff --git a/01_Archive/2026-04-20/Amdahls Law (암달의 법칙).md b/01_Archive/2026-04-20/Amdahls Law (암달의 법칙).md index 38b69a8b..96e777d3 100644 --- a/01_Archive/2026-04-20/Amdahls Law (암달의 법칙).md +++ b/01_Archive/2026-04-20/Amdahls Law (암달의 법칙).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-9C64B9 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Amdahls Law (암달의 법칙)" --- -# [[Amdahls Law (암달의 법칙)]] +# [[Amdahls Law (암달의 법칙)|Amdahls Law (암달의 법칙)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Amdahls Law (암달의 법칙) ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Amdahl's Law (암달의 법칙).md]] +- Raw Source: 00_Raw/2026-04-20/Amdahl's Law (암달의 법칙).md --- diff --git a/01_Archive/2026-04-20/Americans-with-Disabilities-Act-ADA.md b/01_Archive/2026-04-20/Americans-with-Disabilities-Act-ADA.md index dc856896..793862df 100644 --- a/01_Archive/2026-04-20/Americans-with-Disabilities-Act-ADA.md +++ b/01_Archive/2026-04-20/Americans-with-Disabilities-Act-ADA.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-4B67E4 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.95 tags: [] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Mega Batch - Wikified Americans-with-Disabilities-Act-ADA" --- -# [[Americans-with-Disabilities-Act-ADA]] +# [[Americans-with-Disabilities-Act-ADA|Americans-with-Disabilities-Act-ADA]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 핵심 요약 작업 진행 중 @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Mega Batch - Wikified Americans-with-Disabilities- ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Americans-with-Disabilities-Act-ADA.md]] +- Raw Source: 00_Raw/2026-04-20/Americans-with-Disabilities-Act-ADA.md --- diff --git a/01_Archive/2026-04-20/Amygdala Hyperactivity.md b/01_Archive/2026-04-20/Amygdala Hyperactivity.md index 181a9f8a..f751adf3 100644 --- a/01_Archive/2026-04-20/Amygdala Hyperactivity.md +++ b/01_Archive/2026-04-20/Amygdala Hyperactivity.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-CE31D3 -category: "[[10_Wiki/💡 Topics/Psychology & Behavior]]" +category: "10_Wiki/💡 Topics/Psychology & Behavior" confidence_score: 0.95 tags: [] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Mega Batch - Wikified Amygdala Hyperactivity" --- -# [[Amygdala Hyperactivity]] +# [[Amygdala Hyperactivity|Amygdala Hyperactivity]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 핵심 요약 작업 진행 중 @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Mega Batch - Wikified Amygdala Hyperactivity" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Amygdala Hyperactivity.md]] +- Raw Source: 00_Raw/2026-04-20/Amygdala Hyperactivity.md --- diff --git a/01_Archive/2026-04-20/Analyze runtime performance.md b/01_Archive/2026-04-20/Analyze runtime performance.md index 9685c00f..c7e41de6 100644 --- a/01_Archive/2026-04-20/Analyze runtime performance.md +++ b/01_Archive/2026-04-20/Analyze runtime performance.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-C8C70C -category: "[[10_Wiki/💡 Topics/Web & Performance]]" +category: "10_Wiki/💡 Topics/Web & Performance" confidence_score: 0.95 tags: [] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Mega Batch - Wikified Analyze runtime performance" --- -# [[Analyze runtime performance]] +# [[Analyze runtime performance|Analyze runtime performance]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 런타임 성능(Runtime performance) 분석은 페이지가 로드되는 시점이 아니라, 페이지가 실제로 실행되는 동안 어떻게 작동하는지 측정하고 평가하는 과정입니다 [1]. 개발자는 주로 Chrome DevTools의 성능(Performance) 패널을 활용하여 페이지와 상호 작용하는 동안의 활동을 기록합니다 [1, 2]. 이를 통해 애니메이션 프레임 속도(FPS), CPU 과부하, 메인 스레드 병목 현상 등을 식별하여 전반적인 사용자 경험을 최적화할 수 있습니다 [3, 4]. @@ -41,11 +41,11 @@ github_commit: "[P-Reinforce] Mega Batch - Wikified Analyze runtime performance" - **정책 변화:** Web & Performance 카테고리의 전문성 확보 및 링크 밀도 최적화. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Chrome DevTools]], [[Frames Per Second (FPS)]], [[Forced Synchronous Layouts]], [[Long Task]], [[Interaction to Next Paint (INP)]] -- **Projects/Contexts:** [[RAIL model]], [[Chrome User Experience Report (CrUX)]] +- **Related Topics:** [[Chrome DevTools|Chrome DevTools]], Frames Per Second (FPS), Forced Synchronous Layouts, Long Task, [[Interaction to Next Paint (INP)|Interaction to Next Paint (INP)]] +- **Projects/Contexts:** RAIL model, [[Chrome User Experience Report (CrUX)|Chrome User Experience Report (CrUX)]] - **Contradictions/Notes:** DevTools의 CPU 스로틀링 기능은 데스크톱의 CPU 속도를 늦추어 시뮬레이션하는 방식이므로, 데스크톱과 모바일 기기의 근본적인 아키텍처 차이 때문에 실제 모바일 기기의 CPU 동작을 완벽하게 모방할 수는 없습니다 [17]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Analyze runtime performance.md]] +- Raw Source: 00_Raw/2026-04-20/Analyze runtime performance.md --- diff --git a/01_Archive/2026-04-20/AppSec (애플리케이션 보안).md b/01_Archive/2026-04-20/AppSec (애플리케이션 보안).md index 42db74c5..cc3cb34e 100644 --- a/01_Archive/2026-04-20/AppSec (애플리케이션 보안).md +++ b/01_Archive/2026-04-20/AppSec (애플리케이션 보안).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-C35C99 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - AppSec (애플리케이션 보안)" --- -# [[AppSec (애플리케이션 보안)]] +# [[AppSec (애플리케이션 보안)|AppSec (애플리케이션 보안)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 애플리케이션 보안(AppSec)은 잠재적인 위협과 취약점으로부터 소프트웨어 애플리케이션을 보호하기 위한 일련의 활동과 방식을 의미합니다 [1, 2]. 소프트웨어 개발 수명 주기(SDLC)의 모든 단계에 보안을 통합하여 코드가 프로덕션 환경에 배포되기 전에 코드 수준의 결함을 조기에 발견하고 수정하는 것을 목표로 합니다 [3, 4]. 이를 위해 SAST, DAST, SCA 등 다양한 자동화된 보안 테스트 도구와 인간의 수동 코드 리뷰를 결합하여 애플리케이션의 전반적인 보안 태세를 강화합니다 [4-6]. @@ -23,11 +23,11 @@ github_commit: "[P-Reinforce] Continuous Worker - AppSec (애플리케이션 보 - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[SAST (정적 애플리케이션 보안 테스트)]], [[DAST (동적 애플리케이션 보안 테스트)]], [[SCA (소프트웨어 구성 분석)]], [[SDLC (소프트웨어 개발 수명 주기)]] -- **Projects/Contexts:** [[시프트 레프트(Shift-Left) 전략]], [[하이브리드 코드 리뷰 프로세스]] +- **Related Topics:** [[SAST (정적 애플리케이션 보안 테스트)|SAST (정적 애플리케이션 보안 테스트)]], [[DAST (동적 애플리케이션 보안 테스트)|DAST (동적 애플리케이션 보안 테스트)]], [[SCA (소프트웨어 구성 분석)|SCA (소프트웨어 구성 분석)]], [[SDLC (소프트웨어 개발 수명 주기)|SDLC (소프트웨어 개발 수명 주기)]] +- **Projects/Contexts:** 시프트 레프트(Shift-Left) 전략, 하이브리드 코드 리뷰 프로세스 - **Contradictions/Notes:** 자동화된 AppSec 도구는 코드베이스 전체를 빠르고 일관되게 스캔하여 구문적 취약점을 찾아내지만, 비즈니스 로직이나 아키텍처의 의도를 이해하지 못해 오탐지(False Positives)를 유발할 수 있습니다. 따라서 도구에만 전적으로 의존하는 것은 위험하며, 복잡한 비즈니스 로직과 컨텍스트에 민감한 보안 위협을 식별하기 위해서는 반드시 인간 전문가에 의한 수동 코드 리뷰(Manual Code Review)가 병행되어야 한다고 소스들은 강조합니다 [23, 24, 26, 27]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/AppSec (애플리케이션 보안).md]] +- Raw Source: 00_Raw/2026-04-20/AppSec (애플리케이션 보안).md --- diff --git a/01_Archive/2026-04-20/Apple Human Interface Guidelines.md b/01_Archive/2026-04-20/Apple Human Interface Guidelines.md index 63625da9..c03c7260 100644 --- a/01_Archive/2026-04-20/Apple Human Interface Guidelines.md +++ b/01_Archive/2026-04-20/Apple Human Interface Guidelines.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-35F340 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.95 tags: [] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Mega Batch - Wikified Apple Human Interface Guidelines" --- -# [[Apple Human Interface Guidelines]] +# [[Apple Human Interface Guidelines|Apple Human Interface Guidelines]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 핵심 요약 작업 진행 중 @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Mega Batch - Wikified Apple Human Interface Guidel ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Apple Human Interface Guidelines.md]] +- Raw Source: 00_Raw/2026-04-20/Apple Human Interface Guidelines.md --- diff --git a/01_Archive/2026-04-20/Apple Vision Pro Ecosystem.md b/01_Archive/2026-04-20/Apple Vision Pro Ecosystem.md index 53e44b13..4064aab4 100644 --- a/01_Archive/2026-04-20/Apple Vision Pro Ecosystem.md +++ b/01_Archive/2026-04-20/Apple Vision Pro Ecosystem.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-546548 -category: "[[10_Wiki/💡 Topics/Metaverse & Devices]]" +category: "10_Wiki/💡 Topics/Metaverse & Devices" confidence_score: 0.95 tags: [] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Mega Batch - Wikified Apple Vision Pro Ecosystem" --- -# [[Apple Vision Pro Ecosystem]] +# [[Apple Vision Pro Ecosystem|Apple Vision Pro Ecosystem]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 핵심 요약 작업 진행 중 @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Mega Batch - Wikified Apple Vision Pro Ecosystem" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Apple Vision Pro Ecosystem.md]] +- Raw Source: 00_Raw/2026-04-20/Apple Vision Pro Ecosystem.md --- diff --git a/01_Archive/2026-04-20/Apple-Human-Interface-Guidelines.md b/01_Archive/2026-04-20/Apple-Human-Interface-Guidelines.md index d9651b9b..975c795c 100644 --- a/01_Archive/2026-04-20/Apple-Human-Interface-Guidelines.md +++ b/01_Archive/2026-04-20/Apple-Human-Interface-Guidelines.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-D4F8B4 -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Apple-Human-Interface-Guidelines" --- -# [[Apple-Human-Interface-Guidelines]] +# [[Apple-Human-Interface-Guidelines|Apple-Human-Interface-Guidelines]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Apple-Human-Interface-Guidelin ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Apple-Human-Interface-Guidelines.md]] +- Raw Source: 00_Raw/2026-04-20/Apple-Human-Interface-Guidelines.md --- diff --git a/01_Archive/2026-04-20/Architectural-Constraint-Enforcement.md b/01_Archive/2026-04-20/Architectural-Constraint-Enforcement.md index 5579cd1a..2b8c6b9b 100644 --- a/01_Archive/2026-04-20/Architectural-Constraint-Enforcement.md +++ b/01_Archive/2026-04-20/Architectural-Constraint-Enforcement.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-4F930E -category: "[[10_Wiki/💡 Topics/Software Architecture]]" +category: "10_Wiki/💡 Topics/Software Architecture" confidence_score: 0.95 tags: [] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Mega Batch - Wikified Architectural-Constraint-Enforcement" --- -# [[Architectural-Constraint-Enforcement]] +# [[Architectural-Constraint-Enforcement|Architectural-Constraint-Enforcement]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 핵심 요약 작업 진행 중 @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Mega Batch - Wikified Architectural-Constraint-Enf ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Architectural-Constraint-Enforcement.md]] +- Raw Source: 00_Raw/2026-04-20/Architectural-Constraint-Enforcement.md --- diff --git a/01_Archive/2026-04-20/Architecture.md b/01_Archive/2026-04-20/Architecture.md index a6ff9f14..d6d273ba 100644 --- a/01_Archive/2026-04-20/Architecture.md +++ b/01_Archive/2026-04-20/Architecture.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-METAVERSE-001 -category: "[[10_Wiki/💡 Topics/Metaverse]]" +category: "10_Wiki/💡 Topics/Metaverse" confidence_score: 0.88 tags: [metaverse, architecture, digital-twin, spatial] last_reinforced: 2026-04-20 github_commit: "batch-reinforce-03" --- -# [[Metaverse Architecture]] +# [[Metaverse Architecture|Metaverse Architecture]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 가상 공간의 물리적 제약을 넘어 사용자의 사회적 상호작용과 경제 활동을 최적화하는 디지털 공간 설계의 미학. @@ -24,6 +24,6 @@ github_commit: "batch-reinforce-03" - **정책 변화:** 지식 구조(w2) 관점에서 게임 디자인 이론과의 융합 필요성 강조. ## 🔗 지식 연결 (Graph) -- **Parent:** [[10_Wiki/💡 Topics/Metaverse]] -- **Related:** [[Digital-Twin]], [[Spatial-Computing]], [[Avatar-Interaction]] -- **Raw Source:** [[00_Raw/2026-04-20/Metaverse Architecture.md]] +- **Parent:** 10_Wiki/💡 Topics/Metaverse +- **Related:** [[Digital_Twin|Digital-Twin]], [[Spatial Computing|Spatial-Computing]], Avatar-Interaction +- **Raw Source:** 00_Raw/2026-04-20/Metaverse Architecture.md diff --git a/01_Archive/2026-04-20/Arkane Studios.md b/01_Archive/2026-04-20/Arkane Studios.md index 7c857b24..12f74293 100644 --- a/01_Archive/2026-04-20/Arkane Studios.md +++ b/01_Archive/2026-04-20/Arkane Studios.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-503A13 -category: "[[10_Wiki/💡 Topics/Game Design]]" +category: "10_Wiki/💡 Topics/Game Design" confidence_score: 0.95 tags: [] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Mega Batch 2 - Wikified Arkane Studios" --- -# [[Arkane Studios]] +# [[Arkane Studios|Arkane Studios]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 작업 중 @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Mega Batch 2 - Wikified Arkane Studios" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Arkane Studios.md]] +- Raw Source: 00_Raw/2026-04-20/Arkane Studios.md --- diff --git a/01_Archive/2026-04-20/Arkane-Studios.md b/01_Archive/2026-04-20/Arkane-Studios.md index ee482f51..39d340d3 100644 --- a/01_Archive/2026-04-20/Arkane-Studios.md +++ b/01_Archive/2026-04-20/Arkane-Studios.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-1A4850 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Arkane-Studios" --- -# [[Arkane-Studios]] +# [[Arkane-Studios|Arkane-Studios]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Arkane-Studios" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Arkane-Studios.md]] +- Raw Source: 00_Raw/2026-04-20/Arkane-Studios.md --- diff --git a/01_Archive/2026-04-20/ArrayBuffer.md b/01_Archive/2026-04-20/ArrayBuffer.md index c61ad075..94036c7c 100644 --- a/01_Archive/2026-04-20/ArrayBuffer.md +++ b/01_Archive/2026-04-20/ArrayBuffer.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-E57886 -category: "[[10_Wiki/💡 Topics/Programming & Memory]]" +category: "10_Wiki/💡 Topics/Programming & Memory" confidence_score: 0.95 tags: [] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Mega Batch 2 - Wikified ArrayBuffer" --- -# [[ArrayBuffer]] +# [[ArrayBuffer|ArrayBuffer]] ## 📌 한 줄 통찰 (The Karpathy Summary) > ArrayBuffer는 V8 엔진과 같은 JavaScript 런타임 환경에서 데이터를 보관하기 위해 사용되는 메모리 객체 구조입니다 [1, 2]. 과거에는 외부의 오프힙(off-heap) 메모리를 가리키도록 허용되어 V8 힙 외부의 데이터를 JavaScript로 전달하는 데 유용하게 쓰였으나, 최근에는 보안 상의 이유로 V8 메모리 케이지(Memory Cage)가 도입되면서 외부 메모리를 직접 참조하는 방식이 차단되었습니다 [1, 3]. 또한, V8 힙 메모리와는 별도로 계산되지만 자체적인 메모리 크기 제한을 가지고 있습니다 [1]. @@ -20,11 +20,11 @@ github_commit: "[P-Reinforce] Mega Batch 2 - Wikified ArrayBuffer" - **정책 변화:** Programming & Memory 카테고리의 전문성 확보 및 링크 밀도 최적화. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[V8 Memory Cage]], [[Type Confusion]], [[Off-heap memory]] -- **Projects/Contexts:** [[Electron]], [[Chromium/Chrome DevTools]] +- **Related Topics:** [[V8 Memory Cage|V8 Memory Cage]], Type Confusion, Off-heap memory +- **Projects/Contexts:** [[Electron|Electron]], Chromium/Chrome DevTools - **Contradictions/Notes:** 소스에 따르면, 과거에는 ArrayBuffer를 활용해 외부에서 생성한 리소스 버퍼를 복사 없이 효율적으로 JavaScript 환경에 래핑할 수 있었으나, 메모리 케이지가 도입된 이후 보안상의 이유로 이 기능이 동작하지 않게 되어 성능 복사 비용이 발생하더라도 V8 내부로 데이터를 복사해야 하는 제약이 생겼습니다 [1, 6, 7]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/ArrayBuffer.md]] +- Raw Source: 00_Raw/2026-04-20/ArrayBuffer.md --- diff --git a/01_Archive/2026-04-20/Arthrokinematics.md b/01_Archive/2026-04-20/Arthrokinematics.md index ced5ab88..c90896b2 100644 --- a/01_Archive/2026-04-20/Arthrokinematics.md +++ b/01_Archive/2026-04-20/Arthrokinematics.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-EC0439 -category: "[[10_Wiki/💡 Topics/Health & Science]]" +category: "10_Wiki/💡 Topics/Health & Science" confidence_score: 0.95 tags: [] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Mega Batch 2 - Wikified Arthrokinematics" --- -# [[Arthrokinematics]] +# [[Arthrokinematics|Arthrokinematics]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 작업 중 @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Mega Batch 2 - Wikified Arthrokinematics" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Arthrokinematics.md]] +- Raw Source: 00_Raw/2026-04-20/Arthrokinematics.md --- diff --git a/01_Archive/2026-04-20/Artificial Life (ALife).md b/01_Archive/2026-04-20/Artificial Life (ALife).md index ea68a000..65eedfe5 100644 --- a/01_Archive/2026-04-20/Artificial Life (ALife).md +++ b/01_Archive/2026-04-20/Artificial Life (ALife).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-7C3E9E -category: "[[10_Wiki/💡 Topics/AI & Biology]]" +category: "10_Wiki/💡 Topics/AI & Biology" confidence_score: 0.95 tags: [] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Mega Batch 2 - Wikified Artificial Life (ALife)" --- -# [[Artificial Life (ALife)]] +# [[Artificial Life (ALife)|Artificial Life (ALife)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 작업 중 @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Mega Batch 2 - Wikified Artificial Life (ALife)" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Artificial Life (ALife).md]] +- Raw Source: 00_Raw/2026-04-20/Artificial Life (ALife).md --- diff --git a/01_Archive/2026-04-20/Artificial-Intelligence-Explainability.md b/01_Archive/2026-04-20/Artificial-Intelligence-Explainability.md index c4e361d0..4637f24f 100644 --- a/01_Archive/2026-04-20/Artificial-Intelligence-Explainability.md +++ b/01_Archive/2026-04-20/Artificial-Intelligence-Explainability.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-935E0A -category: "[[10_Wiki/💡 Topics/AI & Ethics]]" +category: "10_Wiki/💡 Topics/AI & Ethics" confidence_score: 0.95 tags: [] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Mega Batch 2 - Wikified Artificial-Intelligence-Explainability" --- -# [[Artificial-Intelligence-Explainability]] +# [[Artificial-Intelligence-Explainability|Artificial-Intelligence-Explainability]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 작업 중 @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Mega Batch 2 - Wikified Artificial-Intelligence-Ex ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Artificial-Intelligence-Explainability.md]] +- Raw Source: 00_Raw/2026-04-20/Artificial-Intelligence-Explainability.md --- diff --git a/01_Archive/2026-04-20/Artificial-Intelligence-in-Games.md b/01_Archive/2026-04-20/Artificial-Intelligence-in-Games.md index 116055fd..86d763f1 100644 --- a/01_Archive/2026-04-20/Artificial-Intelligence-in-Games.md +++ b/01_Archive/2026-04-20/Artificial-Intelligence-in-Games.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-281D7C -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Artificial-Intelligence-in-Games" --- -# [[Artificial-Intelligence-in-Games]] +# [[Artificial-Intelligence-in-Games|Artificial-Intelligence-in-Games]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Artificial-Intelligence-in-Gam ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Artificial-Intelligence-in-Games.md]] +- Raw Source: 00_Raw/2026-04-20/Artificial-Intelligence-in-Games.md --- diff --git a/01_Archive/2026-04-20/Artificial-Intelligence.md b/01_Archive/2026-04-20/Artificial-Intelligence.md index d3c264ec..9a19ad2c 100644 --- a/01_Archive/2026-04-20/Artificial-Intelligence.md +++ b/01_Archive/2026-04-20/Artificial-Intelligence.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-497BEF -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Artificial-Intelligence" --- -# [[Artificial-Intelligence]] +# [[Artificial-Intelligence|Artificial-Intelligence]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Artificial-Intelligence" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Artificial-Intelligence.md]] +- Raw Source: 00_Raw/2026-04-20/Artificial-Intelligence.md --- diff --git a/01_Archive/2026-04-20/Assignability-Relation.md b/01_Archive/2026-04-20/Assignability-Relation.md index 2161547f..c3cfd220 100644 --- a/01_Archive/2026-04-20/Assignability-Relation.md +++ b/01_Archive/2026-04-20/Assignability-Relation.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-E1BF3A -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.95 tags: [] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Mega Batch 2 - Wikified Assignability-Relation" --- -# [[Assignability-Relation]] +# [[Assignability-Relation|Assignability-Relation]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 작업 중 @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Mega Batch 2 - Wikified Assignability-Relation" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Assignability-Relation.md]] +- Raw Source: 00_Raw/2026-04-20/Assignability-Relation.md --- diff --git a/01_Archive/2026-04-20/Assignability-Rules.md b/01_Archive/2026-04-20/Assignability-Rules.md index b37d7af4..6b73b2ea 100644 --- a/01_Archive/2026-04-20/Assignability-Rules.md +++ b/01_Archive/2026-04-20/Assignability-Rules.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-DF407B -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Assignability-Rules" --- -# [[Assignability-Rules]] +# [[Assignability-Rules|Assignability-Rules]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Assignability-Rules" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Assignability-Rules.md]] +- Raw Source: 00_Raw/2026-04-20/Assignability-Rules.md --- diff --git a/01_Archive/2026-04-20/Assistive-Technology-Interoperability.md b/01_Archive/2026-04-20/Assistive-Technology-Interoperability.md index 6351729f..c3ca5de2 100644 --- a/01_Archive/2026-04-20/Assistive-Technology-Interoperability.md +++ b/01_Archive/2026-04-20/Assistive-Technology-Interoperability.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-6974BC -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Assistive-Technology-Interoperability" --- -# [[Assistive-Technology-Interoperability]] +# [[Assistive-Technology-Interoperability|Assistive-Technology-Interoperability]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Assistive-Technology-Interoper ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Assistive-Technology-Interoperability.md]] +- Raw Source: 00_Raw/2026-04-20/Assistive-Technology-Interoperability.md --- diff --git a/01_Archive/2026-04-20/Athletic Peak Performance.md b/01_Archive/2026-04-20/Athletic Peak Performance.md index af186aea..2da3e4e3 100644 --- a/01_Archive/2026-04-20/Athletic Peak Performance.md +++ b/01_Archive/2026-04-20/Athletic Peak Performance.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-7BA64D -category: "[[10_Wiki/💡 Topics/Health & Science]]" +category: "10_Wiki/💡 Topics/Health & Science" confidence_score: 0.95 tags: [] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Mega Batch 2 - Wikified Athletic Peak Performance" --- -# [[Athletic Peak Performance]] +# [[Athletic Peak Performance|Athletic Peak Performance]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 작업 중 @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Mega Batch 2 - Wikified Athletic Peak Performance" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Athletic Peak Performance.md]] +- Raw Source: 00_Raw/2026-04-20/Athletic Peak Performance.md --- diff --git a/01_Archive/2026-04-20/Athletic-Performance-Optimization.md b/01_Archive/2026-04-20/Athletic-Performance-Optimization.md index e6049a79..38373022 100644 --- a/01_Archive/2026-04-20/Athletic-Performance-Optimization.md +++ b/01_Archive/2026-04-20/Athletic-Performance-Optimization.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-18F4BB -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Athletic-Performance-Optimization" --- -# [[Athletic-Performance-Optimization]] +# [[Athletic-Performance-Optimization|Athletic-Performance-Optimization]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Athletic-Performance-Optimizat ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Athletic-Performance-Optimization.md]] +- Raw Source: 00_Raw/2026-04-20/Athletic-Performance-Optimization.md --- diff --git a/01_Archive/2026-04-20/Atomic Design Pattern.md b/01_Archive/2026-04-20/Atomic Design Pattern.md index b7a4dbb0..22ebf4e8 100644 --- a/01_Archive/2026-04-20/Atomic Design Pattern.md +++ b/01_Archive/2026-04-20/Atomic Design Pattern.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-E24948 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.95 tags: [] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Mega Batch 2 - Wikified Atomic Design Pattern" --- -# [[Atomic Design Pattern]] +# [[Atomic Design Pattern|Atomic Design Pattern]] ## 📌 한 줄 통찰 (The Karpathy Summary) > Atomic Design Pattern은 UI 컴포넌트의 역할과 계층을 분명하게 만들어 관심사를 분리하기 위해 도입된 계층 구조화 방법론입니다 [1]. 이는 단순히 컴포넌트의 이름이나 분리 그 자체보다, 복잡하게 얽혀 있던 컴포넌트들을 세밀한 기준에 따라 역할과 범주별로 쉽게 정돈할 수 있도록 돕는 역할을 합니다 [1]. @@ -23,11 +23,11 @@ github_commit: "[P-Reinforce] Mega Batch 2 - Wikified Atomic Design Pattern" - **정책 변화:** Design & Experience 카테고리의 전문성 확보 및 링크 밀도 최적화. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[UI 컴포넌트]], [[관심사의 분리]] -- **Projects/Contexts:** [[프론트엔드 개발]] +- **Related Topics:** UI 컴포넌트, 관심사의 분리 +- **Projects/Contexts:** 프론트엔드 개발 - **Contradictions/Notes:** 소스에서는 Atomic Design Pattern을 도입할 때 atoms, molecules, organisms 같은 이름과 단순한 구조적 분리에 집착하기보다는, 컴포넌트를 세밀하게 나눌 수 있는 '기준'을 마련하여 복잡성을 정돈하는 것이 이 패턴의 주요한 역할이라고 강조합니다 [1]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/Atomic Design Pattern.md]] +- Raw Source: 00_Raw/2026-04-20/Atomic Design Pattern.md --- diff --git a/01_Archive/2026-04-20/Auction Theory.md b/01_Archive/2026-04-20/Auction Theory.md index b53b86fb..5a269b4e 100644 --- a/01_Archive/2026-04-20/Auction Theory.md +++ b/01_Archive/2026-04-20/Auction Theory.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-375B82 -category: "[[10_Wiki/💡 Topics/Economics & Algorithms]]" +category: "10_Wiki/💡 Topics/Economics & Algorithms" confidence_score: 0.95 tags: [] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Mega Batch 2 - Wikified Auction Theory" --- -# [[Auction Theory]] +# [[Auction Theory|Auction Theory]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 작업 중 @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Mega Batch 2 - Wikified Auction Theory" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Auction Theory.md]] +- Raw Source: 00_Raw/2026-04-20/Auction Theory.md --- diff --git a/01_Archive/2026-04-20/Auction-Theory.md b/01_Archive/2026-04-20/Auction-Theory.md index f8fb7555..caa4e77d 100644 --- a/01_Archive/2026-04-20/Auction-Theory.md +++ b/01_Archive/2026-04-20/Auction-Theory.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-50A53E -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Auction-Theory" --- -# [[Auction-Theory]] +# [[Auction-Theory|Auction-Theory]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Auction-Theory" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Auction-Theory.md]] +- Raw Source: 00_Raw/2026-04-20/Auction-Theory.md --- diff --git a/01_Archive/2026-04-20/Augmented Reality (AR) Interfaces.md b/01_Archive/2026-04-20/Augmented Reality (AR) Interfaces.md index 47ecd2ae..08fec0d4 100644 --- a/01_Archive/2026-04-20/Augmented Reality (AR) Interfaces.md +++ b/01_Archive/2026-04-20/Augmented Reality (AR) Interfaces.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-0213E9 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.95 tags: [] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Mega Batch 2 - Wikified Augmented Reality (AR) Interfaces" --- -# [[Augmented Reality (AR) Interfaces]] +# [[Augmented Reality (AR) Interfaces|Augmented Reality (AR) Interfaces]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 작업 중 @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Mega Batch 2 - Wikified Augmented Reality (AR) Int ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Augmented Reality (AR) Interfaces.md]] +- Raw Source: 00_Raw/2026-04-20/Augmented Reality (AR) Interfaces.md --- diff --git a/01_Archive/2026-04-20/Augmented Reality (AR).md b/01_Archive/2026-04-20/Augmented Reality (AR).md index 33a973a6..aa40c713 100644 --- a/01_Archive/2026-04-20/Augmented Reality (AR).md +++ b/01_Archive/2026-04-20/Augmented Reality (AR).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-003033 -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Augmented Reality (AR)" --- -# [[Augmented Reality (AR)]] +# [[Augmented Reality (AR)|Augmented Reality (AR)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Augmented Reality (AR)" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Augmented Reality (AR).md]] +- Raw Source: 00_Raw/2026-04-20/Augmented Reality (AR).md --- diff --git a/01_Archive/2026-04-20/Augmented Reality Navigation Systems.md b/01_Archive/2026-04-20/Augmented Reality Navigation Systems.md index ad0b82ba..1704a607 100644 --- a/01_Archive/2026-04-20/Augmented Reality Navigation Systems.md +++ b/01_Archive/2026-04-20/Augmented Reality Navigation Systems.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-054006 -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Augmented Reality Navigation Systems" --- -# [[Augmented Reality Navigation Systems]] +# [[Augmented Reality Navigation Systems|Augmented Reality Navigation Systems]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Augmented Reality Navigation S ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Augmented Reality Navigation Systems.md]] +- Raw Source: 00_Raw/2026-04-20/Augmented Reality Navigation Systems.md --- diff --git a/01_Archive/2026-04-20/Authorship Attribution.md b/01_Archive/2026-04-20/Authorship Attribution.md index 16dff010..e0b88cf3 100644 --- a/01_Archive/2026-04-20/Authorship Attribution.md +++ b/01_Archive/2026-04-20/Authorship Attribution.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-750690 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Authorship Attribution" --- -# [[Authorship Attribution]] +# [[Authorship Attribution|Authorship Attribution]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -29,11 +29,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Authorship Attribution" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Code Stylometry]], [[Plagiarism Detection]], [[Code Formatting]], [[Adversarial Code Stylometry]] -- **Projects/Contexts:** [[Google Code Jam]] (소스 코드 저자 식별 연구에서 광범위하게 사용되는 주요 데이터셋), [[StyleCounsel]] (적대적 저자 식별 회피를 돕기 위해 개발된 도구) +- **Related Topics:** [[Code Stylometry (코드 문체론)|Code Stylometry]], Plagiarism Detection, [[Code Formatting|Code Formatting]], [[Adversarial Code Stylometry|Adversarial Code Stylometry]] +- **Projects/Contexts:** Google Code Jam (소스 코드 저자 식별 연구에서 광범위하게 사용되는 주요 데이터셋), [[StyleCounsel|StyleCounsel]] (적대적 저자 식별 회피를 돕기 위해 개발된 도구) - **Contradictions/Notes:** 소스코드가 컴파일되면 주석, 들여쓰기, 변수명 등이 파괴되므로 작성자의 흔적이 사라질 것이라 예상하기 쉽지만, 실제로는 컴파일러 최적화 수준과 관계없이 실행 파일 내 제어 흐름과 데이터 구조 선택 방식 등의 정보가 남아 있어 상당한 정확도로 저자 식별(Executable Code Attribution)이 가능합니다 [29, 30]. 또한, 포맷터와 Minifier의 사용이 코드 문체론을 교란하기는 하나 식별을 완벽히 방어해주지는 못합니다 [24, 31]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Authorship Attribution.md]] +- Raw Source: 00_Raw/2026-04-20/Authorship Attribution.md --- diff --git a/01_Archive/2026-04-20/Autism Spectrum Disorder (ASD) Intervention.md b/01_Archive/2026-04-20/Autism Spectrum Disorder (ASD) Intervention.md index 16b8730c..79815fcf 100644 --- a/01_Archive/2026-04-20/Autism Spectrum Disorder (ASD) Intervention.md +++ b/01_Archive/2026-04-20/Autism Spectrum Disorder (ASD) Intervention.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-7DCE25 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Autism Spectrum Disorder (ASD) Intervention" --- -# [[Autism Spectrum Disorder (ASD) Intervention]] +# [[Autism Spectrum Disorder (ASD) Intervention|Autism Spectrum Disorder (ASD) Intervention]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Autism Spectrum Disorder (ASD) ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Autism Spectrum Disorder (ASD) Intervention.md]] +- Raw Source: 00_Raw/2026-04-20/Autism Spectrum Disorder (ASD) Intervention.md --- diff --git a/01_Archive/2026-04-20/Automated-Client-Generation.md b/01_Archive/2026-04-20/Automated-Client-Generation.md index a2341e2c..7929db1a 100644 --- a/01_Archive/2026-04-20/Automated-Client-Generation.md +++ b/01_Archive/2026-04-20/Automated-Client-Generation.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-D03F74 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Automated-Client-Generation" --- -# [[Automated-Client-Generation]] +# [[Automated-Client-Generation|Automated-Client-Generation]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Automated-Client-Generation" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Automated-Client-Generation.md]] +- Raw Source: 00_Raw/2026-04-20/Automated-Client-Generation.md --- diff --git a/01_Archive/2026-04-20/Automated-Game-Testing.md b/01_Archive/2026-04-20/Automated-Game-Testing.md index 2e3e012c..117b4410 100644 --- a/01_Archive/2026-04-20/Automated-Game-Testing.md +++ b/01_Archive/2026-04-20/Automated-Game-Testing.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-79D258 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Automated-Game-Testing" --- -# [[Automated-Game-Testing]] +# [[Automated-Game-Testing|Automated-Game-Testing]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Automated-Game-Testing" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Automated-Game-Testing.md]] +- Raw Source: 00_Raw/2026-04-20/Automated-Game-Testing.md --- diff --git a/01_Archive/2026-04-20/Automated-Map-Generation.md b/01_Archive/2026-04-20/Automated-Map-Generation.md index 11073524..53aab1db 100644 --- a/01_Archive/2026-04-20/Automated-Map-Generation.md +++ b/01_Archive/2026-04-20/Automated-Map-Generation.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-77D78F -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Automated-Map-Generation" --- -# [[Automated-Map-Generation]] +# [[Automated-Map-Generation|Automated-Map-Generation]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Automated-Map-Generation" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Automated-Map-Generation.md]] +- Raw Source: 00_Raw/2026-04-20/Automated-Map-Generation.md --- diff --git a/01_Archive/2026-04-20/Automated-Reasoning.md b/01_Archive/2026-04-20/Automated-Reasoning.md index dac71956..59a44217 100644 --- a/01_Archive/2026-04-20/Automated-Reasoning.md +++ b/01_Archive/2026-04-20/Automated-Reasoning.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-3A9338 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Automated-Reasoning" --- -# [[Automated-Reasoning]] +# [[Automated-Reasoning|Automated-Reasoning]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Automated-Reasoning" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Automated-Reasoning.md]] +- Raw Source: 00_Raw/2026-04-20/Automated-Reasoning.md --- diff --git a/01_Archive/2026-04-20/Automated-Refactoring-Tools.md b/01_Archive/2026-04-20/Automated-Refactoring-Tools.md index 425f29ec..541574c9 100644 --- a/01_Archive/2026-04-20/Automated-Refactoring-Tools.md +++ b/01_Archive/2026-04-20/Automated-Refactoring-Tools.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-051F56 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Automated-Refactoring-Tools" --- -# [[Automated-Refactoring-Tools]] +# [[Automated-Refactoring-Tools|Automated-Refactoring-Tools]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Automated-Refactoring-Tools" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Automated-Refactoring-Tools.md]] +- Raw Source: 00_Raw/2026-04-20/Automated-Refactoring-Tools.md --- diff --git a/01_Archive/2026-04-20/Automated-Theorem-Proving.md b/01_Archive/2026-04-20/Automated-Theorem-Proving.md index ca8044d6..f629689e 100644 --- a/01_Archive/2026-04-20/Automated-Theorem-Proving.md +++ b/01_Archive/2026-04-20/Automated-Theorem-Proving.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-ABEDDE -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Automated-Theorem-Proving" --- -# [[Automated-Theorem-Proving]] +# [[Automated-Theorem-Proving|Automated-Theorem-Proving]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Automated-Theorem-Proving" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Automated-Theorem-Proving.md]] +- Raw Source: 00_Raw/2026-04-20/Automated-Theorem-Proving.md --- diff --git a/01_Archive/2026-04-20/Automated_Mapping.md b/01_Archive/2026-04-20/Automated_Mapping.md index fc8bdd4a..b5231251 100644 --- a/01_Archive/2026-04-20/Automated_Mapping.md +++ b/01_Archive/2026-04-20/Automated_Mapping.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AI-004 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.91 tags: [ai, slam, mapping, autonomous] last_reinforced: 2026-04-20 github_commit: "batch-reinforce-05" --- -# [[Automated Mapping & SLAM]] +# Automated Mapping & SLAM ## 📌 한 줄 통찰 (The Karpathy Summary) > 미지의 공간을 탐사함과 동시에 자신의 위치를 파악하여 정밀한 지도를 그려내는 자율 주행의 눈과 지능. @@ -24,6 +24,6 @@ github_commit: "batch-reinforce-05" - **정책 변화:** 지식 구조(w2) 관점에서 자율 주행 에이전트의 '공간 지능' 핵심 요소로 정의. ## 🔗 지식 연결 (Graph) -- **Parent:** [[10_Wiki/💡 Topics/AI]] -- **Related:** [[Computer_Vision]], [[VPS_NeRF]], [[Spatial-Computing]] -- **Raw Source:** [[00_Raw/2026-04-20/Automated-Map-Generation.md]] +- **Parent:** 10_Wiki/💡 Topics/AI +- **Related:** [[Computer_Vision|Computer_Vision]], [[VPS_NeRF|VPS_NeRF]], [[Spatial Computing|Spatial-Computing]] +- **Raw Source:** 00_Raw/2026-04-20/Automated-Map-Generation.md diff --git a/01_Archive/2026-04-20/Autonomous Vehicle Path Planning.md b/01_Archive/2026-04-20/Autonomous Vehicle Path Planning.md index 061163c6..0897292d 100644 --- a/01_Archive/2026-04-20/Autonomous Vehicle Path Planning.md +++ b/01_Archive/2026-04-20/Autonomous Vehicle Path Planning.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-831796 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Autonomous Vehicle Path Planning" --- -# [[Autonomous Vehicle Path Planning]] +# [[Autonomous Vehicle Path Planning|Autonomous Vehicle Path Planning]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Autonomous Vehicle Path Planni ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Autonomous Vehicle Path Planning.md]] +- Raw Source: 00_Raw/2026-04-20/Autonomous Vehicle Path Planning.md --- diff --git a/01_Archive/2026-04-20/Autonomous Vehicle Perception.md b/01_Archive/2026-04-20/Autonomous Vehicle Perception.md index 93024317..cdc68f99 100644 --- a/01_Archive/2026-04-20/Autonomous Vehicle Perception.md +++ b/01_Archive/2026-04-20/Autonomous Vehicle Perception.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-A226DB -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Autonomous Vehicle Perception" --- -# [[Autonomous Vehicle Perception]] +# [[Autonomous Vehicle Perception|Autonomous Vehicle Perception]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Autonomous Vehicle Perception" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Autonomous Vehicle Perception.md]] +- Raw Source: 00_Raw/2026-04-20/Autonomous Vehicle Perception.md --- diff --git a/01_Archive/2026-04-20/Autonomous-Polling-Wait-Automation.md b/01_Archive/2026-04-20/Autonomous-Polling-Wait-Automation.md index 91179239..4d475a1d 100644 --- a/01_Archive/2026-04-20/Autonomous-Polling-Wait-Automation.md +++ b/01_Archive/2026-04-20/Autonomous-Polling-Wait-Automation.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-9B8C6B -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Autonomous-Polling-Wait-Automation" --- -# [[Autonomous-Polling-Wait-Automation]] +# [[Autonomous-Polling-Wait-Automation|Autonomous-Polling-Wait-Automation]] ## 📌 한 줄 통찰 (The Karpathy Summary) > Deep Research 작업의 완료를 에이전트가 스스로 감지하고, "가져오기" 버튼을 누를 필요 없이 즉시 데이터를 수집하는 지능형 대기 시스템입니다. 10초 단위의 상태 폴링(Polling)을 통해 NotebookLM의 작업 상태를 모니터링하며, 완료 시점에 즉각적으로 다음 단계(Synthesis)로 전이됩니다. @@ -28,8 +28,8 @@ NotebookLM의 'Deep Research' 기능은 대규모 데이터를 처리하므로 - **정책 변화:** AI 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[NotebookLM-Automated-Authentication-CLI]], [[Autonomous-Loop-State-Machine]] -- **Projects/Contexts:** [[P-Reinforce-Agent-v2.6]] +- **Related Topics:** [[NotebookLM-Automated-Authentication-CLI|NotebookLM-Automated-Authentication-CLI]], Autonomous-Loop-State-Machine +- **Projects/Contexts:** P-Reinforce-Agent-v2.6 - **Contradictions/Notes:** 너무 잦은 폴링은 API 할당량(Quota) 이슈를 유발할 수 있으므로 10초 간격이 권장됩니다. -- Raw Source: [[00_Raw/2026-04-20/Autonomous-Polling-Wait-Automation.md]] +- Raw Source: 00_Raw/2026-04-20/Autonomous-Polling-Wait-Automation.md --- diff --git a/01_Archive/2026-04-20/Autonomous-Vehicle-Path-Planning.md b/01_Archive/2026-04-20/Autonomous-Vehicle-Path-Planning.md index 630bae3f..92d29805 100644 --- a/01_Archive/2026-04-20/Autonomous-Vehicle-Path-Planning.md +++ b/01_Archive/2026-04-20/Autonomous-Vehicle-Path-Planning.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-405EC6 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Autonomous-Vehicle-Path-Planning" --- -# [[Autonomous-Vehicle-Path-Planning]] +# [[Autonomous-Vehicle-Path-Planning|Autonomous-Vehicle-Path-Planning]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Autonomous-Vehicle-Path-Planni ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Autonomous-Vehicle-Path-Planning.md]] +- Raw Source: 00_Raw/2026-04-20/Autonomous-Vehicle-Path-Planning.md --- diff --git a/01_Archive/2026-04-20/Autotelic Personality.md b/01_Archive/2026-04-20/Autotelic Personality.md index f696bfab..4c1db56b 100644 --- a/01_Archive/2026-04-20/Autotelic Personality.md +++ b/01_Archive/2026-04-20/Autotelic Personality.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-75E436 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Autotelic Personality" --- -# [[Autotelic Personality]] +# [[Autotelic Personality|Autotelic Personality]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Autotelic Personality" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Autotelic Personality.md]] +- Raw Source: 00_Raw/2026-04-20/Autotelic Personality.md --- diff --git a/01_Archive/2026-04-20/Autotelic-Personality.md b/01_Archive/2026-04-20/Autotelic-Personality.md index 1f3164a1..3ac38d13 100644 --- a/01_Archive/2026-04-20/Autotelic-Personality.md +++ b/01_Archive/2026-04-20/Autotelic-Personality.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-13B1BE -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Autotelic-Personality" --- -# [[Autotelic-Personality]] +# [[Autotelic-Personality|Autotelic-Personality]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Autotelic-Personality" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Autotelic-Personality.md]] +- Raw Source: 00_Raw/2026-04-20/Autotelic-Personality.md --- diff --git a/01_Archive/2026-04-20/Axify.md b/01_Archive/2026-04-20/Axify.md index 7a3221c1..721b6645 100644 --- a/01_Archive/2026-04-20/Axify.md +++ b/01_Archive/2026-04-20/Axify.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-FB7EF7 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Axify" --- -# [[Axify]] +# [[Axify|Axify]] ## 📌 한 줄 통찰 (The Karpathy Summary) > Axify는 엔지니어링 리더와 소프트웨어 개발 팀의 생산성 및 배포 성과를 측정하고 최적화하도록 돕는 플랫폼입니다 [1-3]. DORA 지표, 가치 흐름 매핑(VSM), 개발자 생산성 등 다양한 소프트웨어 엔지니어링 지표를 실시간으로 추적 및 시각화합니다 [2, 4]. 특히 AI 기반 코드 리뷰 도구 등 새로운 기술의 도입이 개발 주기와 실제 배포 결과에 미치는 영향을 객관적인 데이터로 비교하고 분석하는 기능을 제공합니다 [5, 6]. @@ -23,11 +23,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Axify" - **정책 변화:** AI 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Axify Intelligence]], [[DORA Metrics]], [[Value Stream Mapping]] -- **Projects/Contexts:** [[AI Adoption and Impact Measurement]], [[Developer Productivity Tracking]] +- **Related Topics:** Axify Intelligence, [[DORA-Metrics|DORA Metrics]], Value Stream Mapping +- **Projects/Contexts:** AI Adoption and Impact Measurement, Developer Productivity Tracking - **Contradictions/Notes:** 소스 내에서 상충되는 의견은 발견되지 않았습니다. 다만 Axify는 새로운 AI 리뷰 도구를 단순히 설치하거나 제안 횟수 자체를 세는 것(Vanity metrics)만으로는 배포 개선을 증명할 수 없다고 지적하며, 실제 성과(DORA 지표 등)로 이어지는지 측정하는 것의 중요성을 강조합니다 [5, 9, 14]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/Axify.md]] +- Raw Source: 00_Raw/2026-04-20/Axify.md --- diff --git a/01_Archive/2026-04-20/Azure DevOps.md b/01_Archive/2026-04-20/Azure DevOps.md index ef56a839..ce7adc32 100644 --- a/01_Archive/2026-04-20/Azure DevOps.md +++ b/01_Archive/2026-04-20/Azure DevOps.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-6BDC0C -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Azure DevOps" --- -# [[Azure DevOps]] +# [[Azure DevOps|Azure DevOps]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 소스에 관련 정보가 부족합니다. 주어진 소스에서는 Azure DevOps 자체에 대한 구체적인 정의나 기능에 대한 설명이 없으며, 단지 다른 소프트웨어 분석 및 관리 도구들이 연동을 지원하는 여러 개발 플랫폼 중 하나로만 간략히 언급되어 있습니다 [1, 2]. @@ -25,11 +25,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Azure DevOps" - **정책 변화:** AI 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[SonarQube]], [[Axify]] +- **Related Topics:** [[SonarQube|SonarQube]], [[Axify|Axify]] - **Projects/Contexts:** 외부 AI 코드 리뷰 도구 및 엔지니어링 생산성 분석 대시보드와의 파트너십 및 시스템 통합(Integration) 맥락 환경 [1, 2] - **Contradictions/Notes:** 소스에 관련 정보가 부족합니다. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Azure DevOps.md]] +- Raw Source: 00_Raw/2026-04-20/Azure DevOps.md --- diff --git a/01_Archive/2026-04-20/BIM 모델 렌더링.md b/01_Archive/2026-04-20/BIM 모델 렌더링.md index 20dca128..d54862bc 100644 --- a/01_Archive/2026-04-20/BIM 모델 렌더링.md +++ b/01_Archive/2026-04-20/BIM 모델 렌더링.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-B22078 -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - BIM 모델 렌더링" --- -# [[BIM 모델 렌더링]] +# [[BIM 모델 렌더링|BIM 모델 렌더링]] ## 📌 한 줄 통찰 (The Karpathy Summary) > BIM(건축 정보 모델) 및 CAD 모델 렌더링은 수십만 개의 고유하거나 반복되는 기하학적 요소로 이루어진 대규모 건설 데이터를 웹 브라우저 등에서 효율적으로 시각화하는 과정입니다 [1-3]. 이 과정에서는 막대한 드로우 콜(Draw call)과 메모리 대역폭 한계로 인한 성능 저하를 방지하기 위해 형상 병합(Merging), 인스턴싱(Instancing), 배칭(Batching) 등의 기법을 적재적소에 활용해야 합니다 [4-7]. 최근에는 WebGPU를 도입하여 500MB 이상의 거대 BIM 데이터를 실시간으로 렌더링하고 컴퓨트 셰이더를 통해 무거운 연산을 병렬 처리하는 방식이 대규모 건설 뷰어의 핵심 기술로 부상하고 있습니다 [8-10]. @@ -33,11 +33,11 @@ github_commit: "[P-Reinforce] Continuous Worker - BIM 모델 렌더링" - **정책 변화:** Graphics & Performance 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[InstancedMesh]], [[BatchedMesh]], [[WebGPU]], [[Draw Call]] -- **Projects/Contexts:** [[IFC.js]], [[Revit 모델 렌더링]], [[대규모 건설 뷰어(Construction Viewers)]] +- **Related Topics:** [[InstancedMesh|InstancedMesh]], [[BatchedMesh|BatchedMesh]], [[WebGPU|WebGPU]], [[Draw Call|Draw Call]] +- **Projects/Contexts:** [[IFC.js|IFC.js]], [[Revit 모델 렌더링|Revit 모델 렌더링]], [[대규모 건설 뷰어(Construction Viewers)|대규모 건설 뷰어(Construction Viewers)]] - **Contradictions/Notes:** 다양한 형태의 객체를 단일 드로우 콜로 처리하여 성능을 높이기 위해 `BatchedMesh`를 사용하는 것이 일반적으로 권장되지만, 수백만 개의 정점과 수십만 개의 서브 지오메트리가 있는 거대한 Revit 기반 건축 모델에 이를 그대로 적용할 경우, 내부 버퍼 업데이트와 데이터 복사 등의 오버헤드로 인해 오히려 CPU 사용량이 40~60% 이상 폭증하고 프레임(FPS)이 급락하는 심각한 성능 역전 현상이 보고되기도 하므로 데이터 규모에 따른 주의가 필요합니다 [15, 22-25]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/BIM 모델 렌더링.md]] +- Raw Source: 00_Raw/2026-04-20/BIM 모델 렌더링.md --- diff --git a/01_Archive/2026-04-20/BIM 모델 시뮬레이션.md b/01_Archive/2026-04-20/BIM 모델 시뮬레이션.md index aa4723dc..8c334465 100644 --- a/01_Archive/2026-04-20/BIM 모델 시뮬레이션.md +++ b/01_Archive/2026-04-20/BIM 모델 시뮬레이션.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-B4BA95 -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - BIM 모델 시뮬레이션" --- -# [[BIM 모델 시뮬레이션]] +# [[BIM 모델 시뮬레이션|BIM 모델 시뮬레이션]] ## 📌 한 줄 통찰 (The Karpathy Summary) > BIM(Building Information Modeling) 모델 시뮬레이션은 수십만 개의 개별 부품으로 구성된 건축 및 건설 데이터를 웹 환경 등에서 실시간으로 렌더링하고 상호작용하는 기술입니다 [1, 2]. 이러한 대규모 데이터셋은 CPU와 GPU 간의 병목 현상을 쉽게 유발하므로 성능 유지를 위해 인스턴싱, 지오메트리 병합, 그리고 최신 그래픽스 API의 활용이 필수적입니다 [2, 3]. 최근에는 대형 모델 처리를 위해 WebGPU의 컴퓨트 셰이더를 활용하여 연산 부하를 획기적으로 낮추는 방법이 도입되고 있습니다 [4, 5]. @@ -27,11 +27,11 @@ github_commit: "[P-Reinforce] Continuous Worker - BIM 모델 시뮬레이션" - **정책 변화:** Graphics & Performance 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[WebGPU]], [[InstancedMesh]], [[BatchedMesh]], [[Compute Shader]] -- **Projects/Contexts:** [[대규모 건설 뷰어(Large-Scale Construction Viewers)]] +- **Related Topics:** [[WebGPU|WebGPU]], [[InstancedMesh|InstancedMesh]], [[BatchedMesh|BatchedMesh]], [[Compute Shader|Compute Shader]] +- **Projects/Contexts:** 대규모 건설 뷰어(Large-Scale Construction Viewers) - **Contradictions/Notes:** 다양한 부품이 혼재된 BIM 모델 최적화를 위해 다중 드로우를 하나로 묶는 `BatchedMesh`가 대안으로 제시되지만, 정점 및 면(face)의 수가 1,000만 개 단위를 넘어갈 정도로 너무 큰 경우에는 과도한 버퍼 연산으로 인해 CPU 점유율이 오히려 치솟는 치명적인 성능 저하가 발생한다는 한계가 있습니다 [8, 9, 11]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/BIM 모델 시뮬레이션.md]] +- Raw Source: 00_Raw/2026-04-20/BIM 모델 시뮬레이션.md --- diff --git a/01_Archive/2026-04-20/BM25 알고리즘 (Best Match 25).md b/01_Archive/2026-04-20/BM25 알고리즘 (Best Match 25).md index 3d0bec71..319ab0c8 100644 --- a/01_Archive/2026-04-20/BM25 알고리즘 (Best Match 25).md +++ b/01_Archive/2026-04-20/BM25 알고리즘 (Best Match 25).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-CA15D0 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - BM25 알고리즘 (Best Match 25)" --- -# [[BM25 알고리즘 (Best Match 25)]] +# [[BM25 알고리즘 (Best Match 25)|BM25 알고리즘 (Best Match 25)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - BM25 알고리즘 (Best Match ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/BM25 알고리즘 (Best Match 25).md]] +- Raw Source: 00_Raw/2026-04-20/BM25 알고리즘 (Best Match 25).md --- diff --git a/01_Archive/2026-04-20/BVH.md b/01_Archive/2026-04-20/BVH.md index 5851c9fe..97845173 100644 --- a/01_Archive/2026-04-20/BVH.md +++ b/01_Archive/2026-04-20/BVH.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-D211FC -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - BVH" --- -# [[BVH]] +# [[BVH|BVH]] ## 📌 한 줄 통찰 (The Karpathy Summary) > BVH(Bounding Volume Hierarchy)는 3D 환경에서 빠르고 효율적인 레이캐스팅(Raycasting), 절두체 컬링(Frustum Culling) 및 공간 질의(Spatial Queries)를 가능하게 하는 정교한 공간 분할 자료구조입니다 [1, 2]. 이는 렌더링, 조명 및 그림자 연산, 충돌 처리, 자산의 메모리 로딩 등 광범위한 최적화를 주도하는 핵심 기반 기술입니다 [3]. Three.js 생태계에서는 주로 대규모 폴리곤이나 복잡한 인스턴스 씬에서의 성능을 극대화하기 위해 활용됩니다 [1, 4]. @@ -23,11 +23,11 @@ github_commit: "[P-Reinforce] Continuous Worker - BVH" - **정책 변화:** Graphics & Performance 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Raycasting]], [[Frustum Culling]], [[InstancedMesh]], [[Spatial Indexing]] -- **Projects/Contexts:** [[three-mesh-bvh]], [[InstancedMesh2]] +- **Related Topics:** [[Raycasting|Raycasting]], [[Frustum Culling|Frustum Culling]], [[InstancedMesh|InstancedMesh]], Spatial Indexing +- **Projects/Contexts:** [[three-mesh-bvh|three-mesh-bvh]], [[InstancedMesh2|InstancedMesh2]] - **Contradictions/Notes:** 기본 `three-mesh-bvh` 라이브러리만으로는 `InstancedMesh`의 전체 인스턴스 집합에 대한 직접적인 공간 조회가 제한적이라는 점이 지적되지만 [7], 커뮤니티에서 개발된 `InstancedMesh2` 라이브러리가 BVH 공간 인덱스를 내장함으로써 이러한 한계를 성공적으로 극복하고 전체 인스턴스의 빠른 컬링 및 레이캐스팅을 가능하게 합니다 [10, 12]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/BVH.md]] +- Raw Source: 00_Raw/2026-04-20/BVH.md --- diff --git a/01_Archive/2026-04-20/Babylon.js.md b/01_Archive/2026-04-20/Babylon.js.md index ebbac470..fc780e17 100644 --- a/01_Archive/2026-04-20/Babylon.js.md +++ b/01_Archive/2026-04-20/Babylon.js.md @@ -1,4 +1,4 @@ -# [[Babylon.js]] +# [[Babylon.js|Babylon.js]] ## 📌 Brief Summary Babylon.js는 수천에서 수만 개의 메쉬로 구성된 대규모 3D 씬을 웹 환경에서 렌더링하고 관리하는 데 사용되는 그래픽 엔진입니다. 렌더링 성능 및 메모리 최적화를 위해 MergeMesh, 인스턴스 메쉬(Instanced Meshes), 그리고 솔리드 파티클 시스템(Solid Particle System, SPS) 등의 기법을 지원합니다. 대규모 인스턴스 처리 시 발생하는 CPU 병목 현상을 극복하기 위해 하드웨어 제어력이 높은 WebGPU 기술의 도입이 적극적으로 논의되고 있습니다. @@ -18,8 +18,8 @@ Babylon.js는 수천에서 수만 개의 메쉬로 구성된 대규모 3D 씬을 현재의 WebGL 상태에서는 인스턴스 메쉬라 할지라도 수만 개의 객체를 처리하기에는 무리가 있습니다 [10]. 2,000개 미만의 메쉬에서는 원활하지만 그 이상의 거대한 스케일을 처리하기 위해서는 금속(하드웨어) 수준에 더 가깝게 접근할 수 있는 WebGPU를 대안으로 사용해야 합니다 [10]. ## 🔗 Knowledge Connections -- **Related Topics:** [[Instanced Meshes]], [[Solid Particle System (SPS)]], [[Frustum Culling]], [[WebGPU]] -- **Projects/Contexts:** [[대규모 3D 환경 렌더링 최적화 프로젝트]] +- **Related Topics:** Instanced Meshes, Solid Particle System (SPS), [[Frustum Culling|Frustum Culling]], [[WebGPU|WebGPU]] +- **Projects/Contexts:** 대규모 3D 환경 렌더링 최적화 프로젝트 - **Contradictions/Notes:** 인스턴스 메쉬는 지오메트리를 복제하지 않아 메모리가 절약되어야 하지만, 한 사용자는 10,000개의 인스턴스당 100MB의 힙 메모리가 증가(인스턴스당 약 8~10KB)한다는 프로파일링 결과를 제기했습니다 [7, 11]. 이에 대해 Babylon.js 개발진(Deltakosh)은 실제 인스턴스 1개당 차지하는 메모리는 약 400바이트 수준이라고 확인하며 오해를 정정했습니다 [12]. --- diff --git a/01_Archive/2026-04-20/Babylonjs.md b/01_Archive/2026-04-20/Babylonjs.md index 2be3b45c..4948084f 100644 --- a/01_Archive/2026-04-20/Babylonjs.md +++ b/01_Archive/2026-04-20/Babylonjs.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-852A59 -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Babylonjs" --- -# [[Babylonjs]] +# [[Babylonjs|Babylonjs]] ## 📌 한 줄 통찰 (The Karpathy Summary) > Babylon.js는 수천에서 수만 개의 메쉬로 구성된 대규모 3D 씬을 웹 환경에서 렌더링하고 관리하는 데 사용되는 그래픽 엔진입니다. 렌더링 성능 및 메모리 최적화를 위해 MergeMesh, 인스턴스 메쉬(Instanced Meshes), 그리고 솔리드 파티클 시스템(Solid Particle System, SPS) 등의 기법을 지원합니다. 대규모 인스턴스 처리 시 발생하는 CPU 병목 현상을 극복하기 위해 하드웨어 제어력이 높은 WebGPU 기술의 도입이 적극적으로 논의되고 있습니다. @@ -31,11 +31,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Babylonjs" - **정책 변화:** Graphics & Performance 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Instanced Meshes]], [[Solid Particle System (SPS)]], [[Frustum Culling]], [[WebGPU]] -- **Projects/Contexts:** [[대규모 3D 환경 렌더링 최적화 프로젝트]] +- **Related Topics:** Instanced Meshes, Solid Particle System (SPS), [[Frustum Culling|Frustum Culling]], [[WebGPU|WebGPU]] +- **Projects/Contexts:** 대규모 3D 환경 렌더링 최적화 프로젝트 - **Contradictions/Notes:** 인스턴스 메쉬는 지오메트리를 복제하지 않아 메모리가 절약되어야 하지만, 한 사용자는 10,000개의 인스턴스당 100MB의 힙 메모리가 증가(인스턴스당 약 8~10KB)한다는 프로파일링 결과를 제기했습니다 [7, 11]. 이에 대해 Babylon.js 개발진(Deltakosh)은 실제 인스턴스 1개당 차지하는 메모리는 약 400바이트 수준이라고 확인하며 오해를 정정했습니다 [12]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Babylon.js.md]] +- Raw Source: 00_Raw/2026-04-20/Babylon.js.md --- diff --git a/01_Archive/2026-04-20/Baseline Project.md b/01_Archive/2026-04-20/Baseline Project.md index e4bd1ebb..69313bd0 100644 --- a/01_Archive/2026-04-20/Baseline Project.md +++ b/01_Archive/2026-04-20/Baseline Project.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-E3E3EF -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Baseline Project" --- -# [[Baseline Project]] +# [[Baseline Project|Baseline Project]] ## 📌 한 줄 통찰 (The Karpathy Summary) > Baseline Project는 Chrome, Edge, Firefox, Safari 등 주요 웹 브라우저에서 최소 30개월 이상 지속적으로 지원된 '널리 사용 가능한 브라우저 API(widely available browser APIs)'를 정의하는 프로젝트입니다 [1]. 이 프로젝트는 특정 웹 플랫폼 기능이 언제부터 모든 주요 브라우저에서 안전하게 사용될 수 있는지에 대한 타임라인을 제공하여 개발자들을 돕습니다 [1]. 브라우저의 네이티브 지원이 확대되어 베이스라인 기능이 늘어나면, 대체용 JavaScript 사용량이 줄어들어 결과적으로 웹 성능이 향상되는 이점이 있습니다 [2]. @@ -25,11 +25,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Baseline Project" - **정책 변화:** AI 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Browser APIs]], [[Web Performance]] -- **Projects/Contexts:** [[Web Platform Features]] +- **Related Topics:** Browser APIs, [[웹 성능 가이드(Web Performance)|Web Performance]] +- **Projects/Contexts:** Web Platform Features - **Contradictions/Notes:** 소스에 관련 정보가 부족합니다. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Baseline Project.md]] +- Raw Source: 00_Raw/2026-04-20/Baseline Project.md --- diff --git a/01_Archive/2026-04-20/BatchedMesh 및 InstancedMesh 성능 벤치마크.md b/01_Archive/2026-04-20/BatchedMesh 및 InstancedMesh 성능 벤치마크.md index e4cd1bb7..650a9c28 100644 --- a/01_Archive/2026-04-20/BatchedMesh 및 InstancedMesh 성능 벤치마크.md +++ b/01_Archive/2026-04-20/BatchedMesh 및 InstancedMesh 성능 벤치마크.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-6B3697 -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - BatchedMesh 및 InstancedMesh 성능 벤치마크" --- -# [[BatchedMesh 및 InstancedMesh 성능 벤치마크]] +# [[BatchedMesh 및 InstancedMesh 성능 벤치마크|BatchedMesh 및 InstancedMesh 성능 벤치마크]] ## 📌 한 줄 통찰 (The Karpathy Summary) > BatchedMesh와 InstancedMesh는 Three.js 환경에서 드로우 콜(Draw Call)을 줄여 렌더링 성능을 대폭 개선하는 대표적인 최적화 기법입니다 [1, 2]. InstancedMesh는 동일한 형태의 객체를 대량으로 그릴 때 탁월한 효율을 보이지만 다양한 지오메트리를 한 번에 처리할 수는 없으며, BatchedMesh는 서로 다른 지오메트리를 하나의 드로우 콜로 묶을 수 있는 높은 유연성을 제공합니다 [3, 4]. 하지만 벤치마크 사례 연구에 따르면, 대규모 객체를 처리할 때 BatchedMesh는 내부적인 객체 정렬 및 버퍼 업로드 오버헤드로 인해 오히려 심각한 CPU 병목 현상과 렌더링 성능 저하를 유발할 수 있음이 확인되었습니다 [5, 6]. @@ -33,11 +33,11 @@ github_commit: "[P-Reinforce] Continuous Worker - BatchedMesh 및 InstancedMesh - **정책 변화:** Graphics & Performance 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[드로우 콜 (Draw Call)]], [[Frustum Culling (시야 절두체 컬링)]], [[오버드로우 (Overdraw)]] -- **Projects/Contexts:** [[Revit 및 BIM 건축 모델 렌더링 최적화]], [[WebGPU 및 Indirect Draw]] +- **Related Topics:** 드로우 콜 (Draw Call), Frustum Culling (시야 절두체 컬링), [[오버드로우(Overdraw)|오버드로우 (Overdraw)]] +- **Projects/Contexts:** Revit 및 BIM 건축 모델 렌더링 최적화, WebGPU 및 Indirect Draw - **Contradictions/Notes:** BatchedMesh는 여러 종류의 지오메트리 렌더링 시 발생하는 CPU의 드로우 콜 오버헤드를 줄이고 성능을 최적화하기 위해 고안되었으나, 대규모(10만 개 이상) 지오메트리 벤치마크 환경에서는 내부 상태 업데이트 및 버퍼 데이터 전송 부하로 인해 도리어 Merged Mesh 방식보다 CPU 사용량을 최대 3배 이상 폭증시키고 FPS를 심각하게 떨어뜨리는 역설적인 결과를 보입니다 [5, 15, 30]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/BatchedMesh 및 InstancedMesh 성능 벤치마크.md]] +- Raw Source: 00_Raw/2026-04-20/BatchedMesh 및 InstancedMesh 성능 벤치마크.md --- diff --git a/01_Archive/2026-04-20/BatchedMesh.md b/01_Archive/2026-04-20/BatchedMesh.md index b97497a1..416821ad 100644 --- a/01_Archive/2026-04-20/BatchedMesh.md +++ b/01_Archive/2026-04-20/BatchedMesh.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-AADCDE -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - BatchedMesh" --- -# [[BatchedMesh]] +# [[BatchedMesh|BatchedMesh]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -32,11 +32,11 @@ github_commit: "[P-Reinforce] Continuous Worker - BatchedMesh" - **정책 변화:** Graphics & Performance 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[InstancedMesh]], [[Draw Call Optimization]], [[WEBGL_multi_draw]], [[Frustum Culling]] -- **Projects/Contexts:** [[Three.js 렌더링 최적화]], [[대규모 3D 건축 모델(BIM) 시각화]], [[InstancedMesh 사용 시 드로우 콜 최적화의 한계점 사례 연구]] +- **Related Topics:** [[InstancedMesh|InstancedMesh]], [[Draw Call Optimization|Draw Call Optimization]], [[WEBGL_multi_draw|WEBGL_multi_draw]], [[Frustum Culling|Frustum Culling]] +- **Projects/Contexts:** [[Three.js 렌더링 최적화|Three.js 렌더링 최적화]], [[대규모 3D 건축 모델(BIM) 시각화|대규모 3D 건축 모델(BIM) 시각화]], [[InstancedMesh 사용 시 드로우 콜 최적화의 한계점 사례 연구|InstancedMesh 사용 시 드로우 콜 최적화의 한계점 사례 연구]] - **Contradictions/Notes:** 소스에서는 BatchedMesh가 여러 지오메트리를 한 번에 그려 드로우 콜을 획기적으로 줄여준다고 설명하지만, 동시에 인스턴스 수가 10만 개 이상이거나 1,200만 폴리곤 이상의 환경에서는 CPU의 버퍼 패킹 및 다중 드로우 처리 부하로 인해 병합된 일반 메쉬(Merged Mesh)나 InstancedMesh보다 FPS가 30~50% 이상 떨어지는 모순적 한계를 지니고 있음을 실증 사례로 지적합니다. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/BatchedMesh.md]] +- Raw Source: 00_Raw/2026-04-20/BatchedMesh.md --- diff --git a/01_Archive/2026-04-20/Batching.md b/01_Archive/2026-04-20/Batching.md index c9ad9e69..75dad31f 100644 --- a/01_Archive/2026-04-20/Batching.md +++ b/01_Archive/2026-04-20/Batching.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-723577 -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Batching" --- -# [[Batching]] +# [[Batching|Batching]] ## 📌 한 줄 통찰 (The Karpathy Summary) > Batching(배칭)은 렌더링 성능을 최적화하기 위해 여러 개의 렌더링 객체나 처리 명령을 하나의 그룹으로 묶어 일괄적으로 실행하는 기법입니다. 주로 3D 그래픽스(WebGL, WebGPU) 환경에서 GPU로 보내는 드로우 콜(Draw Call) 횟수를 줄여 성능 오버헤드를 최소화하는 데 사용됩니다. 또한 웹 개발 환경에서는 DOM의 읽기 및 쓰기 작업을 묶어 불필요한 레이아웃 재계산을 방지하는 목적으로도 활용됩니다. @@ -28,11 +28,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Batching" - **정책 변화:** Graphics & Performance 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Draw Calls]], [[WebGL]], [[WebGPU]], [[Interaction to Next Paint (INP)]] -- **Projects/Contexts:** [[Cesium]], [[Wonderland Engine]] +- **Related Topics:** Draw Calls, [[WebGL|WebGL]], [[WebGPU|WebGPU]], [[Interaction to Next Paint (INP)|Interaction to Next Paint (INP)]] +- **Projects/Contexts:** [[Cesium|Cesium]], [[Wonderland Engine|Wonderland Engine]] - **Contradictions/Notes:** 소스 내에서 배칭에 관한 상충되는 의견은 없으나, 3D 엔진에서의 '드로우 콜 병합'과 프론트엔드 최적화에서의 'DOM 연산 일괄 처리'라는 서로 다른 두 가지 시스템 컨텍스트에서 성능 개선을 위한 공통된 원리로 작용하고 있음을 보여줍니다. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Batching.md]] +- Raw Source: 00_Raw/2026-04-20/Batching.md --- diff --git a/01_Archive/2026-04-20/Bay 12 Games.md b/01_Archive/2026-04-20/Bay 12 Games.md index 9d7bb1fe..469ac780 100644 --- a/01_Archive/2026-04-20/Bay 12 Games.md +++ b/01_Archive/2026-04-20/Bay 12 Games.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-F3ADB5 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Bay 12 Games" --- -# [[Bay 12 Games]] +# [[Bay 12 Games|Bay 12 Games]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Bay 12 Games" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Bay 12 Games.md]] +- Raw Source: 00_Raw/2026-04-20/Bay 12 Games.md --- diff --git a/01_Archive/2026-04-20/Bayesian Inference.md b/01_Archive/2026-04-20/Bayesian Inference.md index 314b0ba3..20bae5c8 100644 --- a/01_Archive/2026-04-20/Bayesian Inference.md +++ b/01_Archive/2026-04-20/Bayesian Inference.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-5875AD -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Bayesian Inference" --- -# [[Bayesian Inference]] +# [[Bayesian Inference|Bayesian Inference]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Bayesian Inference" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Bayesian Inference.md]] +- Raw Source: 00_Raw/2026-04-20/Bayesian Inference.md --- diff --git a/01_Archive/2026-04-20/Bazel.md b/01_Archive/2026-04-20/Bazel.md index de093715..722357d1 100644 --- a/01_Archive/2026-04-20/Bazel.md +++ b/01_Archive/2026-04-20/Bazel.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-C6F58A -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Bazel" --- -# [[Bazel]] +# [[Bazel|Bazel]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Bazel" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Bazel.md]] +- Raw Source: 00_Raw/2026-04-20/Bazel.md --- diff --git a/01_Archive/2026-04-20/Beat Saber 엑서게임 연구(Beat Saber Exergaming Study).md b/01_Archive/2026-04-20/Beat Saber 엑서게임 연구(Beat Saber Exergaming Study).md index 963c4ea3..780bc8ac 100644 --- a/01_Archive/2026-04-20/Beat Saber 엑서게임 연구(Beat Saber Exergaming Study).md +++ b/01_Archive/2026-04-20/Beat Saber 엑서게임 연구(Beat Saber Exergaming Study).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-C3E3B9 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Beat Saber 엑서게임 연구(Beat Saber Exergaming Study)" --- -# [[Beat Saber 엑서게임 연구(Beat Saber Exergaming Study)]] +# [[Beat Saber 엑서게임 연구(Beat Saber Exergaming Study)|Beat Saber 엑서게임 연구(Beat Saber Exergaming Study)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 이 연구는 전 세계적으로 인기 있는 상업용 VR 엑서게임인 '비트 세이버(Beat Saber)'를 짧은 시간(10분)과 긴 시간(50분) 동안 플레이했을 때 사용자의 시력, 인지 능력, 그리고 주관적 VR 멀미에 미치는 사후 영향(aftereffects)을 조사한 연구이다 [1], [2], [3]. VR 엑서게임은 신체 활동을 장려하는 잠재력이 크지만, 사용자가 겪는 멀미나 시각적/인지적 후유증이 그 활용을 제한할 수 있기 때문에 이에 대한 안전성과 회복 시간을 파악하는 것을 목적으로 한다 [1], [4]. @@ -29,11 +29,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Beat Saber 엑서게임 연구 - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[가상현실(VR)]], [[엑서게임(Exergaming)]], [[VR 멀미(VR Sickness)]], [[시뮬레이터 멀미 설문지(SSQ)]] -- **Projects/Contexts:** [[비트 세이버(Beat Saber)]] +- **Related Topics:** [[가상현실(VR)|가상현실(VR)]], [[엑서게임(Exergaming)|엑서게임(Exergaming)]], [[VR 멀미 (VR Sickness)|VR 멀미(VR Sickness)]], [[시뮬레이터 멀미 설문지(SSQ)|시뮬레이터 멀미 설문지(SSQ)]] +- **Projects/Contexts:** [[비트 세이버(Beat Saber)|비트 세이버(Beat Saber)]] - **Contradictions/Notes:** 그룹 전체의 평균 데이터를 보면 40분의 휴식 후 멀미 수치가 원래 수준으로 회복되는 것처럼 보이지만, 개인 단위의 데이터를 살펴보면 50분 플레이 후 약 14%의 사용자는 여전히 심각한 수준의 멀미를 경험하므로 평균 수치만으로 부작용이 완전히 사라졌다고 단정하기는 어렵다 [10], [14]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Beat Saber 엑서게임 연구(Beat Saber Exergaming Study).md]] +- Raw Source: 00_Raw/2026-04-20/Beat Saber 엑서게임 연구(Beat Saber Exergaming Study).md --- diff --git a/01_Archive/2026-04-20/Beat Saber.md b/01_Archive/2026-04-20/Beat Saber.md index e248b044..c59b02ea 100644 --- a/01_Archive/2026-04-20/Beat Saber.md +++ b/01_Archive/2026-04-20/Beat Saber.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-711498 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Beat Saber" --- -# [[Beat Saber]] +# [[Beat Saber|Beat Saber]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 'Beat Saber'는 모션 트래킹 기술을 활용해 플레이어가 가상현실 속에서 광선검을 휘둘러 리듬에 맞춰 표적을 베고 장애물을 피하는 인기 VR 리듬 엑서게임(Exergame)입니다 [1]. 전 세계적으로 200만 장 이상 판매된 성공적인 상업 게임으로, 햅틱 및 시청각 피드백을 통해 높은 몰입감을 제공합니다 [1, 2]. 실제 테니스와 맞먹는 에너지 소모량을 바탕으로 신체 활동을 돕는 유용한 도구로 인정받고 있으며, VR 멀미(VR sickness) 및 몰입 상태(Flow state)를 분석하는 학술 연구에서도 널리 활용되고 있습니다 [2, 3]. @@ -22,11 +22,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Beat Saber" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[VR Exergame]], [[VR Sickness]], [[Flow State]] -- **Projects/Contexts:** [[가상현실 노출 사후 효과(VR Aftereffects) 연구]], [[몰입 상태 예측 프레임워크(Flow State Prediction Framework)]] +- **Related Topics:** VR Exergame, [[VR Sickness|VR Sickness]], [[Flow State|Flow State]] +- **Projects/Contexts:** 가상현실 노출 사후 효과(VR Aftereffects) 연구, 몰입 상태 예측 프레임워크(Flow State Prediction Framework) - **Contradictions/Notes:** 소스 연구에 따르면 Beat Saber 플레이 후의 사후 효과(멀미 등)는 전반적으로 일시적이며 40분 내에 기저 수준으로 회복되어 멀미로 인한 실험 탈락자가 없었지만 [6, 7], 장시간(50분) 노출될 경우 특정 사용자 집단(약 14%)에서는 게임 종료 40분 후에도 여전히 높은 수준의 멀미가 유지되는 등 개인의 민감도와 노출 시간에 따라 상이한 결과가 나타납니다 [6, 8]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Beat Saber.md]] +- Raw Source: 00_Raw/2026-04-20/Beat Saber.md --- diff --git a/01_Archive/2026-04-20/Beat Saber를 활용한 VR 엑서게임 후유증 연구(VR Exergaming Aftereffects).md b/01_Archive/2026-04-20/Beat Saber를 활용한 VR 엑서게임 후유증 연구(VR Exergaming Aftereffects).md index 6a87ee3a..1b8e28c1 100644 --- a/01_Archive/2026-04-20/Beat Saber를 활용한 VR 엑서게임 후유증 연구(VR Exergaming Aftereffects).md +++ b/01_Archive/2026-04-20/Beat Saber를 활용한 VR 엑서게임 후유증 연구(VR Exergaming Aftereffects).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-180522 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Beat Saber를 활용한 VR 엑서게임 후유증 연구(VR Exergaming Aftereffects)" --- -# [[Beat Saber를 활용한 VR 엑서게임 후유증 연구(VR Exergaming Aftereffects)]] +# [[Beat Saber를 활용한 VR 엑서게임 후유증 연구(VR Exergaming Aftereffects)|Beat Saber를 활용한 VR 엑서게임 후유증 연구(VR Exergaming Aftereffects)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 이 연구는 인기 있는 가상현실(VR) 엑서게임인 'Beat Saber'를 각각 10분과 50분 동안 플레이한 후, 사용자의 시각, 인지 기능, 그리고 VR 멀미(VR Sickness)에 미치는 영향을 분석했습니다 [1], [2]. 연구 결과, 게임 직후 시각적 조절 및 폭주 능력의 변화와 멀미 증상이 증가했으나, 대부분의 경우 40분의 휴식 후 기준치로 회복되었습니다 [3]. 인지 기능 측면에서는 부정적인 후유증이 없었으며 오히려 단기 플레이 후 움직임 속도가 일시적으로 향상되었으나, 장시간(50분) 플레이한 일부 개인(약 14%)은 40분이 지나도 높은 수준의 멀미를 겪는 등 개인차가 큰 것으로 나타났습니다 [4], [5]. @@ -39,11 +39,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Beat Saber를 활용한 VR 엑 - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[VR Sickness]], [[Vergence-Accommodation Conflicts]], [[Exergaming]], [[Simulator Sickness Questionnaire (SSQ)]] -- **Projects/Contexts:** [[Beat Saber]], [[HTC Vive Pro HMD]] +- **Related Topics:** [[VR Sickness|VR Sickness]], [[Vergence-Accommodation Conflicts|Vergence-Accommodation Conflicts]], [[Exergaming|Exergaming]], [[Simulator Sickness Questionnaire (SSQ)|Simulator Sickness Questionnaire (SSQ)]] +- **Projects/Contexts:** [[Beat Saber|Beat Saber]], [[HTC Vive Pro HMD|HTC Vive Pro HMD]] - **Contradictions/Notes:** 소스에 따르면 VR 엑서게임은 시각적 변화나 멀미와 같은 부작용을 동반할 수 있으나, 인지 능력 저하는 관찰되지 않았으며 짧은 시간 플레이 시에는 움직임 반응 속도 측면에서 일시적인 향상이 나타나는 상반된 결과가 있었습니다 [8], [4]. 또한, 집단의 멀미 증상은 대체로 40분 내에 회복되지만, 개인의 민감도에 따라 긴 시간 지속되는 소수의 예외(약 14%)가 존재한다는 점에 유의해야 합니다 [5]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Beat Saber를 활용한 VR 엑서게임 후유증 연구(VR Exergaming Aftereffects).md]] +- Raw Source: 00_Raw/2026-04-20/Beat Saber를 활용한 VR 엑서게임 후유증 연구(VR Exergaming Aftereffects).md --- diff --git a/01_Archive/2026-04-20/Behavioral Economics in Digital Ecosystems.md b/01_Archive/2026-04-20/Behavioral Economics in Digital Ecosystems.md index d31d7f36..4bf2037b 100644 --- a/01_Archive/2026-04-20/Behavioral Economics in Digital Ecosystems.md +++ b/01_Archive/2026-04-20/Behavioral Economics in Digital Ecosystems.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-CAA259 -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Behavioral Economics in Digital Ecosystems" --- -# [[Behavioral Economics in Digital Ecosystems]] +# [[Behavioral Economics in Digital Ecosystems|Behavioral Economics in Digital Ecosystems]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Behavioral Economics in Digita ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Behavioral Economics in Digital Ecosystems.md]] +- Raw Source: 00_Raw/2026-04-20/Behavioral Economics in Digital Ecosystems.md --- diff --git a/01_Archive/2026-04-20/Behavioral Economics.md b/01_Archive/2026-04-20/Behavioral Economics.md index bb4e6489..db8289e7 100644 --- a/01_Archive/2026-04-20/Behavioral Economics.md +++ b/01_Archive/2026-04-20/Behavioral Economics.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-612A46 -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Behavioral Economics" --- -# [[Behavioral Economics]] +# [[Behavioral Economics|Behavioral Economics]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Behavioral Economics" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Behavioral Economics.md]] +- Raw Source: 00_Raw/2026-04-20/Behavioral Economics.md --- diff --git a/01_Archive/2026-04-20/Behavioral Finance.md b/01_Archive/2026-04-20/Behavioral Finance.md index 72a2e354..03b54913 100644 --- a/01_Archive/2026-04-20/Behavioral Finance.md +++ b/01_Archive/2026-04-20/Behavioral Finance.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-A72BA3 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Behavioral Finance" --- -# [[Behavioral Finance]] +# [[Behavioral Finance|Behavioral Finance]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Behavioral Finance" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Behavioral Finance.md]] +- Raw Source: 00_Raw/2026-04-20/Behavioral Finance.md --- diff --git a/01_Archive/2026-04-20/Behavioral-Economics.md b/01_Archive/2026-04-20/Behavioral-Economics.md index dd16919c..cf984cca 100644 --- a/01_Archive/2026-04-20/Behavioral-Economics.md +++ b/01_Archive/2026-04-20/Behavioral-Economics.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-9A5386 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Behavioral-Economics" --- -# [[Behavioral-Economics]] +# [[Behavioral-Economics|Behavioral-Economics]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Behavioral-Economics" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Behavioral-Economics.md]] +- Raw Source: 00_Raw/2026-04-20/Behavioral-Economics.md --- diff --git a/01_Archive/2026-04-20/Behavioral_Economics.md b/01_Archive/2026-04-20/Behavioral_Economics.md index b2e34750..546e17bc 100644 --- a/01_Archive/2026-04-20/Behavioral_Economics.md +++ b/01_Archive/2026-04-20/Behavioral_Economics.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-PSYCH-005 -category: "[[10_Wiki/💡 Topics/Psychology]]" +category: "10_Wiki/💡 Topics/Psychology" confidence_score: 0.90 tags: [psychology, economics, behavior, nudge] last_reinforced: 2026-04-20 github_commit: "batch-reinforce-04" --- -# [[Behavioral Economics in Digital Ecosystems]] +# [[Behavioral Economics in Digital Ecosystems|Behavioral Economics in Digital Ecosystems]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 인간의 비합리적 선택 패턴을 이해하고, 이를 디지털 환경에서 더 나은(혹은 의도된) 의사결정으로 유도하는 디자인 과학. @@ -24,6 +24,6 @@ github_commit: "batch-reinforce-04" - **정책 변화:** 지식 구조(w2) 관점에서 서비스 기획 가이드와 보건 심리학의 교집합 탐색. ## 🔗 지식 연결 (Graph) -- **Parent:** [[10_Wiki/💡 Topics/Psychology]] -- **Related:** [[Operant_Conditioning]], [[Nudge-Theory]], [[Dark-Patterns]] -- **Raw Source:** [[00_Raw/2026-04-20/Behavioral Economics in Digital Ecosystems.md]] +- **Parent:** 10_Wiki/💡 Topics/Psychology +- **Related:** [[Operant_Conditioning|Operant_Conditioning]], [[Nudge_Theory|Nudge-Theory]], [[다크 패턴 (Dark Patterns)|Dark-Patterns]] +- **Raw Source:** 00_Raw/2026-04-20/Behavioral Economics in Digital Ecosystems.md diff --git a/01_Archive/2026-04-20/Bellman Equation.md b/01_Archive/2026-04-20/Bellman Equation.md index 4b368bf7..a958c55a 100644 --- a/01_Archive/2026-04-20/Bellman Equation.md +++ b/01_Archive/2026-04-20/Bellman Equation.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-019B9B -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Bellman Equation" --- -# [[Bellman Equation]] +# [[Bellman Equation|Bellman Equation]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Bellman Equation" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Bellman Equation.md]] +- Raw Source: 00_Raw/2026-04-20/Bellman Equation.md --- diff --git a/01_Archive/2026-04-20/Best SAST Tools in 2026.md b/01_Archive/2026-04-20/Best SAST Tools in 2026.md index afebe426..8fe3a7c0 100644 --- a/01_Archive/2026-04-20/Best SAST Tools in 2026.md +++ b/01_Archive/2026-04-20/Best SAST Tools in 2026.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-A622AB -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Best SAST Tools in 2026" --- -# [[Best SAST Tools in 2026]] +# [[Best SAST Tools in 2026|Best SAST Tools in 2026]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 2026년 최고의 SAST(정적 애플리케이션 보안 테스트) 도구들은 기존의 단순 패턴 매칭 방식을 넘어 AI 및 머신러닝(ML)을 분석 엔진과 결합하여 탐지 정확도와 개발자 경험을 극대화하고 있습니다 [1, 2]. 이 도구들은 소스 코드가 실행되기 전 정지 상태에서 코드를 분석하여 보안 취약점과 비즈니스 로직 오류를 조기에 발견하고, 검증된 수정 코드(Auto-fix)를 자동으로 제안합니다 [2, 3]. 개발 환경(IDE), Pull Request(PR), CI/CD 파이프라인에 매끄럽게 통합되어 보안 점검을 개발 초기 단계로 이동시키는 '시프트 레프트(Shift-left)' 접근법을 실현하는 것이 핵심 특징입니다 [1, 3, 4]. @@ -36,11 +36,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Best SAST Tools in 2026" - **정책 변화:** AI 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Static Application Security Testing (SAST)]], [[Artificial Intelligence (AI)]], [[Shift-left]], [[Dynamic Application Security Testing (DAST)]], [[False Positives]] -- **Projects/Contexts:** [[소프트웨어 개발 수명 주기(SDLC)]], [[지속적 통합 및 배포(CI/CD)]], [[Pull Request (PR) 워크플로우]] +- **Related Topics:** [[Static Application Security Testing (SAST)|Static Application Security Testing (SAST)]], [[Artificial Intelligence (AI)|Artificial Intelligence (AI)]], [[시프트 레프트 (Shift-Left)|Shift-left]], Dynamic Application Security Testing (DAST), False Positives +- **Projects/Contexts:** [[소프트웨어 개발 수명 주기 (SDLC)|소프트웨어 개발 수명 주기(SDLC)]], 지속적 통합 및 배포(CI/CD), [[Pull Request (PR) 워크플로우|Pull Request (PR) 워크플로우]] - **Contradictions/Notes:** 전통적인 패턴 기반 SAST는 복잡한 비즈니스 로직 및 인증 플로우의 결함을 찾는 데 한계가 있는 반면, 분석 엔진 자체에 LLM을 탑재한 AI-native 도구(예: Corgea)는 이를 포착하는 데 더 효과적입니다 [27]. 하지만, AI 기반의 빠른 자동 수정(Auto-fix)이 검증이나 가드레일 없이 제공될 경우 오히려 "빠르고 잘못된 수정"을 낳아 더 큰 문제를 유발할 수 있으므로, 벤더사의 패치 재테스트 지원 여부가 매우 중요하게 다루어집니다 [12, 15, 26]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Best SAST Tools in 2026.md]] +- Raw Source: 00_Raw/2026-04-20/Best SAST Tools in 2026.md --- diff --git a/01_Archive/2026-04-20/Best-of-N Sampling (최적 샘플링).md b/01_Archive/2026-04-20/Best-of-N Sampling (최적 샘플링).md index 0688a7be..bb27974c 100644 --- a/01_Archive/2026-04-20/Best-of-N Sampling (최적 샘플링).md +++ b/01_Archive/2026-04-20/Best-of-N Sampling (최적 샘플링).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-F28615 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Best-of-N Sampling (최적 샘플링)" --- -# [[Best-of-N Sampling (최적 샘플링)]] +# [[Best-of-N Sampling (최적 샘플링)|Best-of-N Sampling (최적 샘플링)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Best-of-N Sampling (최적 샘 ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Best-of-N Sampling (최적 샘플링).md]] +- Raw Source: 00_Raw/2026-04-20/Best-of-N Sampling (최적 샘플링).md --- diff --git a/01_Archive/2026-04-20/Bio-mechanical-Modeling.md b/01_Archive/2026-04-20/Bio-mechanical-Modeling.md index fe832a77..7d6e36a3 100644 --- a/01_Archive/2026-04-20/Bio-mechanical-Modeling.md +++ b/01_Archive/2026-04-20/Bio-mechanical-Modeling.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-8DE8EF -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Bio-mechanical-Modeling" --- -# [[Bio-mechanical-Modeling]] +# [[Bio-mechanical-Modeling|Bio-mechanical-Modeling]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Bio-mechanical-Modeling" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Bio-mechanical-Modeling.md]] +- Raw Source: 00_Raw/2026-04-20/Bio-mechanical-Modeling.md --- diff --git a/01_Archive/2026-04-20/BioShock (2007).md b/01_Archive/2026-04-20/BioShock (2007).md index 97beb80c..8c83e81c 100644 --- a/01_Archive/2026-04-20/BioShock (2007).md +++ b/01_Archive/2026-04-20/BioShock (2007).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-422DE2 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - BioShock (2007)" --- -# [[BioShock (2007)]] +# [[BioShock (2007)|BioShock (2007)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - BioShock (2007)" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/BioShock (2007).md]] +- Raw Source: 00_Raw/2026-04-20/BioShock (2007).md --- diff --git a/01_Archive/2026-04-20/BioShock (Rapture)] [Dark Souls (Environmental Lore)] [Gone Home (Domestic Narrative Architecture).md b/01_Archive/2026-04-20/BioShock (Rapture)] [Dark Souls (Environmental Lore)] [Gone Home (Domestic Narrative Architecture).md index a4587ae8..d91f4917 100644 --- a/01_Archive/2026-04-20/BioShock (Rapture)] [Dark Souls (Environmental Lore)] [Gone Home (Domestic Narrative Architecture).md +++ b/01_Archive/2026-04-20/BioShock (Rapture)] [Dark Souls (Environmental Lore)] [Gone Home (Domestic Narrative Architecture).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-395B33 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - BioShock (Rapture)] [Dark Souls (Environmental Lore)] [Gone Home (Domestic Narrative Architecture)" --- -# [[BioShock (Rapture)] [Dark Souls (Environmental Lore)] [Gone Home (Domestic Narrative Architecture)]] +# [[BioShock (Rapture)] [Dark Souls (Environmental Lore)] [Gone Home (Domestic Narrative Architecture)|BioShock (Rapture)] [Dark Souls (Environmental Lore)] [Gone Home (Domestic Narrative Architecture)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - BioShock (Rapture)] [Dark Soul ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/BioShock (Rapture)], [Dark Souls (Environmental Lore)], [Gone Home (Domestic Narrative Architecture).md]] +- Raw Source: 00_Raw/2026-04-20/BioShock (Rapture)], [Dark Souls (Environmental Lore)], [Gone Home (Domestic Narrative Architecture).md --- diff --git a/01_Archive/2026-04-20/BioShock (Rapture)], [Dark Souls (Environmental Lore)], [Gone Home (Domestic Narrative Architecture).md b/01_Archive/2026-04-20/BioShock (Rapture)], [Dark Souls (Environmental Lore)], [Gone Home (Domestic Narrative Architecture).md index fe163147..e7f8a8c8 100644 --- a/01_Archive/2026-04-20/BioShock (Rapture)], [Dark Souls (Environmental Lore)], [Gone Home (Domestic Narrative Architecture).md +++ b/01_Archive/2026-04-20/BioShock (Rapture)], [Dark Souls (Environmental Lore)], [Gone Home (Domestic Narrative Architecture).md @@ -1,4 +1,4 @@ -[[BioShock (Rapture)], [Dark Souls (Environmental Lore)], [Gone Home (Domestic Narrative Architecture)]] +[[BioShock (Rapture)], [Dark Souls (Environmental Lore)], [Gone Home (Domestic Narrative Architecture)|BioShock (Rapture)], [Dark Souls (Environmental Lore)], [Gone Home (Domestic Narrative Architecture)]] 📌 Brief Summary This synthesis examines the intersection of spatial design and narrative delivery in video games, focusing on three distinct methodologies: the socio-political critique embedded in the architectural decay of *BioShock*'s Rapture; the "archaeological" storytelling found in the fragmented, item-based environmental lore of *Dark Souls*; and the use of domestic spaces as mnemonic devices for character history in *Gone Home*. Together, these works represent a shift from explicit script-driven plots to emergent narratives derived from spatial exploration. @@ -17,8 +17,8 @@ This synthesis examines the intersection of spatial design and narrative deliver * The house acts as a mnemonic map; moving through specific rooms triggers psychological insights into the protagonists' lives. Unlike the macro-societal scale of *BioShock* or the mythic scale of *Dark Souls*, this approach focuses on micro-narratives, using spatial intimacy to foster empathy and investigative tension. 🔗 Knowledge Connections -* Related Topics: [[Environmental Storytelling]], [[Ludonarrative Dissonance]], [[Spatial Narratology]], [[Archaeological Gameplay]] -* Projects/Contexts: [[Narrative Design in Interactive Media]], [[Architectural Theory in Game Design]] +* Related Topics: [[Environmental Storytelling|Environmental Storytelling]], [[Ludonarrative Dissonance|Ludonarrative Dissonance]], Spatial Narratology, Archaeological Gameplay +* Projects/Contexts: Narrative Design in Interactive Media, Architectural Theory in Game Design * Contradictions/Notes: While *BioShock* and *Dark Souls* use environment to convey large-scale historical or mythic shifts, *Gone Home* uses it for psychological interiority. A point of debate in ludology is whether "fragmented lore" (as seen in *Dark Souls*) risks alienating players compared to the more structured environmental cues found in *BioShock*. Last updated: 2026-04-16 \ No newline at end of file diff --git a/01_Archive/2026-04-20/BioShock-Critique.md b/01_Archive/2026-04-20/BioShock-Critique.md index 979b887e..230deabe 100644 --- a/01_Archive/2026-04-20/BioShock-Critique.md +++ b/01_Archive/2026-04-20/BioShock-Critique.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-3BB6D4 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - BioShock-Critique" --- -# [[BioShock-Critique]] +# [[BioShock-Critique|BioShock-Critique]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - BioShock-Critique" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/BioShock-Critique.md]] +- Raw Source: 00_Raw/2026-04-20/BioShock-Critique.md --- diff --git a/01_Archive/2026-04-20/Bioenergetics.md b/01_Archive/2026-04-20/Bioenergetics.md index 779ce760..ee21c2cc 100644 --- a/01_Archive/2026-04-20/Bioenergetics.md +++ b/01_Archive/2026-04-20/Bioenergetics.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-DD3FFE -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Bioenergetics" --- -# [[Bioenergetics]] +# [[Bioenergetics|Bioenergetics]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Bioenergetics" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Bioenergetics.md]] +- Raw Source: 00_Raw/2026-04-20/Bioenergetics.md --- diff --git a/01_Archive/2026-04-20/Bioinformatics-Structure-Prediction.md b/01_Archive/2026-04-20/Bioinformatics-Structure-Prediction.md index 50cc8179..890920c6 100644 --- a/01_Archive/2026-04-20/Bioinformatics-Structure-Prediction.md +++ b/01_Archive/2026-04-20/Bioinformatics-Structure-Prediction.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-230A20 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Bioinformatics-Structure-Prediction" --- -# [[Bioinformatics-Structure-Prediction]] +# [[Bioinformatics-Structure-Prediction|Bioinformatics-Structure-Prediction]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Bioinformatics-Structure-Predi ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Bioinformatics-Structure-Prediction.md]] +- Raw Source: 00_Raw/2026-04-20/Bioinformatics-Structure-Prediction.md --- diff --git a/01_Archive/2026-04-20/Biomechanical-Analysis.md b/01_Archive/2026-04-20/Biomechanical-Analysis.md index 80968c04..66574dac 100644 --- a/01_Archive/2026-04-20/Biomechanical-Analysis.md +++ b/01_Archive/2026-04-20/Biomechanical-Analysis.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-C5D712 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Biomechanical-Analysis" --- -# [[Biomechanical-Analysis]] +# [[Biomechanical-Analysis|Biomechanical-Analysis]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Biomechanical-Analysis" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Biomechanical-Analysis.md]] +- Raw Source: 00_Raw/2026-04-20/Biomechanical-Analysis.md --- diff --git a/01_Archive/2026-04-20/Biomechanics-of-Injury.md b/01_Archive/2026-04-20/Biomechanics-of-Injury.md index 03445cef..78259568 100644 --- a/01_Archive/2026-04-20/Biomechanics-of-Injury.md +++ b/01_Archive/2026-04-20/Biomechanics-of-Injury.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-928880 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Biomechanics-of-Injury" --- -# [[Biomechanics-of-Injury]] +# [[Biomechanics-of-Injury|Biomechanics-of-Injury]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Biomechanics-of-Injury" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Biomechanics-of-Injury.md]] +- Raw Source: 00_Raw/2026-04-20/Biomechanics-of-Injury.md --- diff --git a/01_Archive/2026-04-20/Biomechanics.md b/01_Archive/2026-04-20/Biomechanics.md index b197621e..6e631f45 100644 --- a/01_Archive/2026-04-20/Biomechanics.md +++ b/01_Archive/2026-04-20/Biomechanics.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-93212D -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Biomechanics" --- -# [[Biomechanics]] +# [[Biomechanics|Biomechanics]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Biomechanics" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Biomechanics.md]] +- Raw Source: 00_Raw/2026-04-20/Biomechanics.md --- diff --git a/01_Archive/2026-04-20/Biomedical-Engineering.md b/01_Archive/2026-04-20/Biomedical-Engineering.md index e911c682..02b18aaf 100644 --- a/01_Archive/2026-04-20/Biomedical-Engineering.md +++ b/01_Archive/2026-04-20/Biomedical-Engineering.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AI-058 -category: "[[10_Wiki/💡 Topics/Health & Science]]" +category: "10_Wiki/💡 Topics/Health & Science" confidence_score: 0.97 tags: [biomedical engineering, biomechanics, medical device, robotics] last_reinforced: 2026-06-XX github_commit: "[P-Reinforce] Processed Biomedical-Engineering." --- -# [[Biomedical-Engineering]] (생체 의학 공학) +# [[Biomedical-Engineering|Biomedical-Engineering]] (생체 의학 공학) ## 📌 한 줄 통찰 (The Karpathy Summary) > 생명 과학적 지식(Biology)과 공학 기술(Engineering)을 융합하여, 인체의 문제를 진단하고 치료하며 기능을 보조하는 의료 장비 및 시스템을 설계하는 학문이다. @@ -23,7 +23,7 @@ github_commit: "[P-Reinforce] Processed Biomedical-Engineering." - **정책 변화:** AI 기반으로 방대한 의료 데이터를 학습하여 진단 정확도를 높이는 것이 중요해지고 있으며, 개인정보보호(HIPAA 등)와 결합된 데이터 보안 아키텍처가 핵심 트렌드이다. ## 🔗 지식 연결 (Graph) -- Parent: [[Biomedical-Engineering]] -- Related: [[Biomechanics]] , [[Assistive Technology]] , [[Signal Processing]] -- Raw Source: [[00_Raw/Biomedical-Engineering.md]] +- Parent: [[Biomedical-Engineering|Biomedical-Engineering]] +- Related: [[Biomechanics|Biomechanics]] , [[보조 공학 (Assistive Technology)|Assistive Technology]] , [[Signal Processing|Signal Processing]] +- Raw Source: 00_Raw/Biomedical-Engineering.md --- \ No newline at end of file diff --git a/01_Archive/2026-04-20/Biometrics.md b/01_Archive/2026-04-20/Biometrics.md index 9ee93c40..152a6fee 100644 --- a/01_Archive/2026-04-20/Biometrics.md +++ b/01_Archive/2026-04-20/Biometrics.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-90C871 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Biometrics" --- -# [[Biometrics]] +# [[Biometrics|Biometrics]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Biometrics" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Biometrics.md]] +- Raw Source: 00_Raw/2026-04-20/Biometrics.md --- diff --git a/01_Archive/2026-04-20/Bioregionalism.md b/01_Archive/2026-04-20/Bioregionalism.md index 67130871..aed9e62b 100644 --- a/01_Archive/2026-04-20/Bioregionalism.md +++ b/01_Archive/2026-04-20/Bioregionalism.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-01D600 -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Bioregionalism" --- -# [[Bioregionalism]] +# [[Bioregionalism|Bioregionalism]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Bioregionalism" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Bioregionalism.md]] +- Raw Source: 00_Raw/2026-04-20/Bioregionalism.md --- diff --git a/01_Archive/2026-04-20/Black-box Testing.md b/01_Archive/2026-04-20/Black-box Testing.md index a928dee8..bfc44806 100644 --- a/01_Archive/2026-04-20/Black-box Testing.md +++ b/01_Archive/2026-04-20/Black-box Testing.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-DC07C2 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Black-box Testing" --- -# [[Black-box Testing]] +# [[Black-box Testing|Black-box Testing]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 블랙박스 테스팅(Black-box Testing)은 애플리케이션의 내부 소스 코드를 보지 않고 외부에서 실행 중인 애플리케이션을 기반으로 테스트하는 방법입니다 [1], [2]. 대표적인 예로 DAST(동적 애플리케이션 보안 테스트)가 블랙박스 테스팅 방식을 취하며, 주로 CI 파이프라인의 후반부에 적용됩니다 [2]. @@ -20,11 +20,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Black-box Testing" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[DAST]], [[White-box Testing]], [[SAST]] -- **Projects/Contexts:** [[CI Pipeline]] +- **Related Topics:** [[DAST (동적 애플리케이션 보안 테스트)|DAST]], White-box Testing, [[SAST|SAST]] +- **Projects/Contexts:** CI Pipeline - **Contradictions/Notes:** 소스 데이터는 블랙박스 테스팅을 독립된 주제로 다루기보다는, 내부 소스 코드 기반의 정적 분석(SAST)인 화이트박스 테스팅과 대비되는 개념(DAST)으로 설명하고 있습니다 [1], [2]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/Black-box Testing.md]] +- Raw Source: 00_Raw/2026-04-20/Black-box Testing.md --- diff --git a/01_Archive/2026-04-20/Blink.md b/01_Archive/2026-04-20/Blink.md index 51f88644..efa8feef 100644 --- a/01_Archive/2026-04-20/Blink.md +++ b/01_Archive/2026-04-20/Blink.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-7F733B -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Blink" --- -# [[Blink]] +# [[Blink|Blink]] ## 📌 한 줄 통찰 (The Karpathy Summary) > Blink는 Chrome 브라우저에서 사용되는 렌더러(renderer) 엔진입니다 [1]. V8 엔진 외부에서 C++ 객체를 정의하고 할당하는 역할을 담당하며, 이러한 객체들은 메모리 힙 스냅샷 내에서 보통 `InternalNode` 카테고리로 표시됩니다 [2]. Blink는 'Oilpan'이라는 자체적인 가비지 컬렉터(Garbage Collector)를 보유하고 있으며, V8 엔진의 가비지 컬렉터와 상호 협력하여 동작합니다 [1]. @@ -24,11 +24,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Blink" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[V8 Engine]], [[Oilpan]], [[Orinoco]], [[InternalNode]] -- **Projects/Contexts:** [[Chrome]], [[Heap Snapshot]] +- **Related Topics:** [[V8 Engine|V8 Engine]], [[Oilpan|Oilpan]], [[Orinoco|Orinoco]], InternalNode +- **Projects/Contexts:** [[Chrome|Chrome]], [[Heap Snapshot|Heap Snapshot]] - **Contradictions/Notes:** 소스 내에 Blink 자체의 전체 구조를 다루는 정보는 부족하며, V8 메모리 관리 및 힙 스냅샷 디버깅 관점에서만 제한적으로 언급되어 있습니다. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Blink.md]] +- Raw Source: 00_Raw/2026-04-20/Blink.md --- diff --git a/01_Archive/2026-04-20/Blog_Content_Rules.md b/01_Archive/2026-04-20/Blog_Content_Rules.md index 571b89bf..dc289d16 100644 --- a/01_Archive/2026-04-20/Blog_Content_Rules.md +++ b/01_Archive/2026-04-20/Blog_Content_Rules.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-1FF145 -category: "[[10_Wiki/💡 Topics/General Knowledge]]" +category: "10_Wiki/💡 Topics/General Knowledge" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Blog_Content_Rules" --- -# [[Blog_Content_Rules]] +# [[Blog_Content_Rules|Blog_Content_Rules]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Blog_Content_Rules" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Blog_Content_Rules.md]] +- Raw Source: 00_Raw/2026-04-20/Blog_Content_Rules.md --- diff --git a/01_Archive/2026-04-20/Blog_Title_Rules.md b/01_Archive/2026-04-20/Blog_Title_Rules.md index ac69aaf4..1a8df88a 100644 --- a/01_Archive/2026-04-20/Blog_Title_Rules.md +++ b/01_Archive/2026-04-20/Blog_Title_Rules.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-566F32 -category: "[[10_Wiki/💡 Topics/General Knowledge]]" +category: "10_Wiki/💡 Topics/General Knowledge" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Blog_Title_Rules" --- -# [[Blog_Title_Rules]] +# [[Blog_Title_Rules|Blog_Title_Rules]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Blog_Title_Rules" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Blog_Title_Rules.md]] +- Raw Source: 00_Raw/2026-04-20/Blog_Title_Rules.md --- diff --git a/01_Archive/2026-04-20/Borderlands-Art-Direction.md b/01_Archive/2026-04-20/Borderlands-Art-Direction.md index e11134ec..1e698f64 100644 --- a/01_Archive/2026-04-20/Borderlands-Art-Direction.md +++ b/01_Archive/2026-04-20/Borderlands-Art-Direction.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-37BB2D -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Borderlands-Art-Direction" --- -# [[Borderlands-Art-Direction]] +# [[Borderlands-Art-Direction|Borderlands-Art-Direction]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Borderlands-Art-Direction" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Borderlands-Art-Direction.md]] +- Raw Source: 00_Raw/2026-04-20/Borderlands-Art-Direction.md --- diff --git a/01_Archive/2026-04-20/Boundary-Layer-Validation.md b/01_Archive/2026-04-20/Boundary-Layer-Validation.md index b0d0a89c..fe9dda14 100644 --- a/01_Archive/2026-04-20/Boundary-Layer-Validation.md +++ b/01_Archive/2026-04-20/Boundary-Layer-Validation.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-F8764E -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Boundary-Layer-Validation" --- -# [[Boundary-Layer-Validation]] +# [[Boundary-Layer-Validation|Boundary-Layer-Validation]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Boundary-Layer-Validation" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Boundary-Layer-Validation.md]] +- Raw Source: 00_Raw/2026-04-20/Boundary-Layer-Validation.md --- diff --git a/01_Archive/2026-04-20/Bounded Contexts.md b/01_Archive/2026-04-20/Bounded Contexts.md index dfb67dc4..12eacc7d 100644 --- a/01_Archive/2026-04-20/Bounded Contexts.md +++ b/01_Archive/2026-04-20/Bounded Contexts.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-61D79F -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Bounded Contexts" --- -# [[Bounded Contexts]] +# [[Bounded Contexts|Bounded Contexts]] ## 📌 한 줄 통찰 (The Karpathy Summary) > Bounded Contexts는 도메인 주도 설계(Domain-Driven Design, DDD)에서 크고 복잡한 비즈니스 도메인을 작고 관리하기 쉬운 하위 도메인으로 분할한 것을 의미합니다 [1, 2]. 각 컨텍스트는 자신만의 독립적인 모델과 보편적 언어(Ubiquitous Language)를 가집니다 [1, 2]. 이를 통해 도메인 모델을 순수하고 명확하게 집중된 상태로 유지할 수 있습니다 [1]. @@ -20,11 +20,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Bounded Contexts" - **정책 변화:** AI 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Domain-Driven Design (DDD)]], [[Ubiquitous Language]], [[Microservices Architecture]], [[Subdomains]] -- **Projects/Contexts:** [[모놀리식 아키텍처에서의 마이그레이션]], [[소프트웨어 아키텍처 설계]] +- **Related Topics:** [[Domain-Driven Design (DDD)|Domain-Driven Design (DDD)]], [[보편적 언어 (Ubiquitous Language)|Ubiquitous Language]], [[마이크로서비스 아키텍처 (Microservices Architecture)|Microservices Architecture]], Subdomains +- **Projects/Contexts:** 모놀리식 아키텍처에서의 마이그레이션, [[소프트웨어 아키텍처 설계|소프트웨어 아키텍처 설계]] - **Contradictions/Notes:** 소스 간의 모순은 없으며, 모두 Bounded Contexts를 복잡성을 줄이고 시스템을 독립적인 모듈로 나누는 데 필수적인 DDD의 핵심 개념으로 일관되게 설명하고 있습니다. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/Bounded Contexts.md]] +- Raw Source: 00_Raw/2026-04-20/Bounded Contexts.md --- diff --git a/01_Archive/2026-04-20/Bounded Rationality.md b/01_Archive/2026-04-20/Bounded Rationality.md index 562e2f5b..bae09a24 100644 --- a/01_Archive/2026-04-20/Bounded Rationality.md +++ b/01_Archive/2026-04-20/Bounded Rationality.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-016A0B -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Bounded Rationality" --- -# [[Bounded Rationality]] +# [[Bounded Rationality|Bounded Rationality]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Bounded Rationality" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Bounded Rationality.md]] +- Raw Source: 00_Raw/2026-04-20/Bounded Rationality.md --- diff --git a/01_Archive/2026-04-20/Bounded-Contexts-and-Interface-Segregation.md b/01_Archive/2026-04-20/Bounded-Contexts-and-Interface-Segregation.md index 022f7d7c..807a3ec8 100644 --- a/01_Archive/2026-04-20/Bounded-Contexts-and-Interface-Segregation.md +++ b/01_Archive/2026-04-20/Bounded-Contexts-and-Interface-Segregation.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-02AF46 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Bounded-Contexts-and-Interface-Segregation" --- -# [[Bounded-Contexts-and-Interface-Segregation]] +# [[Bounded-Contexts-and-Interface-Segregation|Bounded-Contexts-and-Interface-Segregation]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Bounded-Contexts-and-Interface ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Bounded-Contexts-and-Interface-Segregation.md]] +- Raw Source: 00_Raw/2026-04-20/Bounded-Contexts-and-Interface-Segregation.md --- diff --git a/01_Archive/2026-04-20/Bounding Volume Hierarchy (BVH).md b/01_Archive/2026-04-20/Bounding Volume Hierarchy (BVH).md index 9c460482..44851c1b 100644 --- a/01_Archive/2026-04-20/Bounding Volume Hierarchy (BVH).md +++ b/01_Archive/2026-04-20/Bounding Volume Hierarchy (BVH).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-68A235 -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Bounding Volume Hierarchy (BVH)" --- -# [[Bounding Volume Hierarchy (BVH)]] +# [[Bounding Volume Hierarchy (BVH)|Bounding Volume Hierarchy (BVH)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -23,11 +23,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Bounding Volume Hierarchy (BVH - **정책 변화:** Graphics & Performance 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Raycasting]], [[Frustum Culling]], [[InstancedMesh]], [[Spatial Partitioning]] -- **Projects/Contexts:** [[three-mesh-bvh]], [[InstancedMesh2]] +- **Related Topics:** [[Raycasting|Raycasting]], [[Frustum Culling|Frustum Culling]], [[InstancedMesh|InstancedMesh]], [[Spatial Partitioning|Spatial Partitioning]] +- **Projects/Contexts:** [[three-mesh-bvh|three-mesh-bvh]], [[InstancedMesh2|InstancedMesh2]] - **Contradictions/Notes:** BVH 모델을 씬에서 직접 시각화하여 확인하고자 할 때, 최신 라이브러리 환경에서는 기존에 사용되던 `MeshBVHVisualizer`가 더 이상 지원되지 않으므로(deprecated) 반드시 문서를 참조하여 `MeshBVHHelper`를 사용해야 합니다 [12]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Bounding Volume Hierarchy (BVH).md]] +- Raw Source: 00_Raw/2026-04-20/Bounding Volume Hierarchy (BVH).md --- diff --git a/01_Archive/2026-04-20/Brain-Derived Neurotrophic Factor (BDNF).md b/01_Archive/2026-04-20/Brain-Derived Neurotrophic Factor (BDNF).md index 6447bb5d..9e96e603 100644 --- a/01_Archive/2026-04-20/Brain-Derived Neurotrophic Factor (BDNF).md +++ b/01_Archive/2026-04-20/Brain-Derived Neurotrophic Factor (BDNF).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-9F6F1B -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Brain-Derived Neurotrophic Factor (BDNF)" --- -# [[Brain-Derived Neurotrophic Factor (BDNF)]] +# [[Brain-Derived Neurotrophic Factor (BDNF)|Brain-Derived Neurotrophic Factor (BDNF)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Brain-Derived Neurotrophic Fac ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Brain-Derived Neurotrophic Factor (BDNF).md]] +- Raw Source: 00_Raw/2026-04-20/Brain-Derived Neurotrophic Factor (BDNF).md --- diff --git a/01_Archive/2026-04-20/Branch Prediction.md b/01_Archive/2026-04-20/Branch Prediction.md index e3db6495..92e68bad 100644 --- a/01_Archive/2026-04-20/Branch Prediction.md +++ b/01_Archive/2026-04-20/Branch Prediction.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-4D7707 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Branch Prediction" --- -# [[Branch Prediction]] +# [[Branch Prediction|Branch Prediction]] ## 📌 한 줄 통찰 (The Karpathy Summary) > Branch prediction(분기 예측)은 현대 CPU가 분기 명령어의 과거 기록을 프로파일링하여(예: 분기가 항상 통과되는지 관찰) 다음 실행 경로를 미리 예측하는 성능 최적화 기술입니다 [1]. 이는 추측 실행(Speculative Execution)과 결합되어 CPU의 처리 속도를 비약적으로 높이지만, 공격자가 분기 기록을 통제할 수 있다는 점 때문에 스펙터(Spectre)와 같은 심각한 보안 취약점의 공격 경로로 악용됩니다 [1, 2]. @@ -23,11 +23,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Branch Prediction" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Speculative Execution]], [[Spectre]], [[Branchless Security Checks]] -- **Projects/Contexts:** [[WebKit]], [[JavaScriptCore]] +- **Related Topics:** [[Speculative Execution|Speculative Execution]], [[Spectre|Spectre]], [[Branchless Security Checks|Branchless Security Checks]] +- **Projects/Contexts:** [[WebKit|WebKit]], [[JavaScriptCore|JavaScriptCore]] - **Contradictions/Notes:** 소스에 관련 정보가 부족합니다. (소스 내에 상충하는 의견은 없으며, 과거에는 분기 명령어가 보안 강제에 충분하다고 여겨졌으나 스펙터의 등장으로 인해 더 이상 안전하지 않게 되었다는 맥락적 변화만 존재합니다 [4]). --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Branch Prediction.md]] +- Raw Source: 00_Raw/2026-04-20/Branch Prediction.md --- diff --git a/01_Archive/2026-04-20/Branchless Security Checks.md b/01_Archive/2026-04-20/Branchless Security Checks.md index ae12163a..6a4d0e10 100644 --- a/01_Archive/2026-04-20/Branchless Security Checks.md +++ b/01_Archive/2026-04-20/Branchless Security Checks.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-229D3F -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Branchless Security Checks" --- -# [[Branchless Security Checks]] +# [[Branchless Security Checks|Branchless Security Checks]] ## 📌 한 줄 통찰 (The Karpathy Summary) > Branchless Security Checks(분기 없는 보안 검사)는 Spectre 및 Meltdown과 같은 CPU 보안 취약점에 대응하기 위해 도입된 보안 메커니즘입니다 [1, 2]. 기존의 조건 분기(Branch) 명령어를 통해 보안을 확인하는 방식은 추측 실행(Speculative execution)을 악용하는 공격에 취약하기 때문에, 분기 명령어를 배제하고 비트 연산 등을 활용하는 방식이 필요해졌습니다 [3, 4]. 대표적인 구현 기법으로는 인덱스 마스킹(Index Masking)과 포인터 포이즈닝(Pointer Poisoning)이 있습니다 [4-6]. @@ -29,11 +29,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Branchless Security Checks" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Spectre]], [[Meltdown]], [[Speculative Execution]], [[Index Masking]], [[Pointer Poisoning]] -- **Projects/Contexts:** [[WebKit]], [[Blink]], [[JavaScriptCore]] +- **Related Topics:** [[Spectre|Spectre]], [[Meltdown|Meltdown]], [[Speculative Execution|Speculative Execution]], [[Index Masking|Index Masking]], [[Pointer Poisoning|Pointer Poisoning]] +- **Projects/Contexts:** [[WebKit|WebKit]], [[Blink|Blink]], [[JavaScriptCore|JavaScriptCore]] - **Contradictions/Notes:** 분기 없는 보안 검사 기법은 캐시 사이드 채널 공격을 방어하는 필수적인 수단이지만, 구조적으로 추가 연산을 요구하기 때문에 작업의 마이크로 지연(Micro-latency)을 증가시킨다는 성능적 트레이드오프가 존재합니다 [13]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Branchless Security Checks.md]] +- Raw Source: 00_Raw/2026-04-20/Branchless Security Checks.md --- diff --git a/01_Archive/2026-04-20/Brand-Identity-Management.md b/01_Archive/2026-04-20/Brand-Identity-Management.md index cf5e53d9..cdfc1ebd 100644 --- a/01_Archive/2026-04-20/Brand-Identity-Management.md +++ b/01_Archive/2026-04-20/Brand-Identity-Management.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-F8EDF9 -category: "[[10_Wiki/💡 Topics/General Knowledge]]" +category: "10_Wiki/💡 Topics/General Knowledge" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Brand-Identity-Management" --- -# [[Brand-Identity-Management]] +# [[Brand-Identity-Management|Brand-Identity-Management]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Brand-Identity-Management" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Brand-Identity-Management.md]] +- Raw Source: 00_Raw/2026-04-20/Brand-Identity-Management.md --- diff --git a/01_Archive/2026-04-20/Branded Types in TypeScript.md b/01_Archive/2026-04-20/Branded Types in TypeScript.md index 63bb0343..469e9cde 100644 --- a/01_Archive/2026-04-20/Branded Types in TypeScript.md +++ b/01_Archive/2026-04-20/Branded Types in TypeScript.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-3CA58B -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Branded Types in TypeScript" --- -# [[Branded Types in TypeScript]] +# [[Branded Types in TypeScript|Branded Types in TypeScript]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Branded Types in TypeScript" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Branded Types in TypeScript.md]] +- Raw Source: 00_Raw/2026-04-20/Branded Types in TypeScript.md --- diff --git a/01_Archive/2026-04-20/Branded Types.md b/01_Archive/2026-04-20/Branded Types.md index 9c5bb869..ef88ae25 100644 --- a/01_Archive/2026-04-20/Branded Types.md +++ b/01_Archive/2026-04-20/Branded Types.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-494E42 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Branded Types" --- -# [[Branded Types]] +# [[Branded Types|Branded Types]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -39,11 +39,11 @@ TypeScript는 이름이 아닌 구조를 기준으로 호환성을 판단하는 - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Structural Typing]], [[Primitive Obsession]], [[Type Predicates]], [[Parse, Don't Validate]] -- **Projects/Contexts:** [[Domain-Driven Design (DDD)]], [[Zod]], [[Effect TS]], [[ts-brand]] +- **Related Topics:** [[Structural Typing|Structural Typing]], [[기본 타입에의 집착 (Primitive Obsession)|Primitive Obsession]], [[Type Predicates|Type Predicates]], [[Parse dont validate|Parse, Don't Validate]] +- **Projects/Contexts:** [[Domain-Driven Design (DDD)|Domain-Driven Design (DDD)]], [[Zod|Zod]], [[Effect TS|Effect TS]], [[ts-brand|ts-brand]] - **Contradictions/Notes:** Branded Types는 강력한 안전성을 제공하지만 코드의 개념적 복잡성을 증가시키고 보일러플레이트 코드를 유발합니다 [27, 28]. 따라서 유니온(Unions), 열거형(Enums), 템플릿 리터럴 타입(Template Literal Types)과 같은 단순한 대안으로 해결 가능한 상황이라면 도입 시 이점과 유지보수 비용을 저울질해야 한다고 경고하고 있습니다 [29-31]. 또한, TypeScript 언어 자체에 명목적 타이핑(Nominal typing)을 직접 지원하자는 논의는 커뮤니티에서 오랫동안 있었으나 아직 명확한 합의에 이르지는 못했습니다 [9, 32]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/Branded Types.md]] +- Raw Source: 00_Raw/2026-04-20/Branded Types.md --- diff --git a/01_Archive/2026-04-20/Branded-Types-for-Nominal-Typing.md b/01_Archive/2026-04-20/Branded-Types-for-Nominal-Typing.md index ca91a377..d858c37f 100644 --- a/01_Archive/2026-04-20/Branded-Types-for-Nominal-Typing.md +++ b/01_Archive/2026-04-20/Branded-Types-for-Nominal-Typing.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-6DAFA5 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Branded-Types-for-Nominal-Typing" --- -# [[Branded-Types-for-Nominal-Typing]] +# [[Branded-Types-for-Nominal-Typing|Branded-Types-for-Nominal-Typing]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Branded-Types-for-Nominal-Typi ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Branded-Types-for-Nominal-Typing.md]] +- Raw Source: 00_Raw/2026-04-20/Branded-Types-for-Nominal-Typing.md --- diff --git a/01_Archive/2026-04-20/Branded-Types.md b/01_Archive/2026-04-20/Branded-Types.md index c85af48d..c9233a87 100644 --- a/01_Archive/2026-04-20/Branded-Types.md +++ b/01_Archive/2026-04-20/Branded-Types.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-6FD185 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Branded-Types" --- -# [[Branded-Types]] +# [[Branded-Types|Branded-Types]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Branded-Types" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Branded-Types.md]] +- Raw Source: 00_Raw/2026-04-20/Branded-Types.md --- diff --git a/01_Archive/2026-04-20/Browser Security Mitigations.md b/01_Archive/2026-04-20/Browser Security Mitigations.md index 0c48e64d..a087bed1 100644 --- a/01_Archive/2026-04-20/Browser Security Mitigations.md +++ b/01_Archive/2026-04-20/Browser Security Mitigations.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-539F01 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Browser Security Mitigations" --- -# [[Browser Security Mitigations]] +# [[Browser Security Mitigations|Browser Security Mitigations]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 브라우저 보안 완화(Browser Security Mitigations)는 스펙터(Spectre) 및 멜트다운(Meltdown)과 같은 사이드 채널 공격으로부터 사용자를 보호하기 위해 웹 브라우저가 구현하는 방어 메커니즘입니다. 이러한 완화 조치는 정보 유출을 막기 위해 타이밍 API의 정밀도를 고의로 낮추고, 자바스크립트 엔진 내에 추측 실행(Speculative Execution)을 방어하는 분기 없는(branchless) 보안 검사를 도입하여 메모리 접근을 안전하게 통제하는 데 중점을 둡니다 [1-3]. @@ -32,11 +32,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Browser Security Mitigations" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Spectre and Meltdown]], [[Speculative Execution]], [[Timing Attacks]], [[Index Masking]], [[Pointer Poisoning]] -- **Projects/Contexts:** [[WebKit]], [[JavaScriptCore]], [[WebGPU]], [[WebGL]] +- **Related Topics:** [[Spectre and Meltdown|Spectre and Meltdown]], [[Speculative Execution|Speculative Execution]], [[Timing Attacks|Timing Attacks]], [[Index Masking|Index Masking]], [[Pointer Poisoning|Pointer Poisoning]] +- **Projects/Contexts:** [[WebKit|WebKit]], [[JavaScriptCore|JavaScriptCore]], [[WebGPU|WebGPU]], [[WebGL|WebGL]] - **Contradictions/Notes:** WebGPU 타임스탬프 쿼리는 타이밍 공격의 우려로 인해 초기에는 비격리 컨텍스트에서 완전히 숨겨지도록 제안되었으나 [12], 개발자들의 성능 프로파일링 요구와 브라우저 간 상호 운용성(Interop) 문제를 해결하기 위해, 사이트 격리 여부와 상관없이 High-Resolution Time 스펙과 맞춘 100마이크로초 해상도를 제공하는 방향으로 스펙이 수정 및 채택되었습니다 [19-22]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Browser Security Mitigations.md]] +- Raw Source: 00_Raw/2026-04-20/Browser Security Mitigations.md --- diff --git a/01_Archive/2026-04-20/Buck2.md b/01_Archive/2026-04-20/Buck2.md index caec7019..87c1358a 100644 --- a/01_Archive/2026-04-20/Buck2.md +++ b/01_Archive/2026-04-20/Buck2.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-849CEC -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Buck2" --- -# [[Buck2]] +# [[Buck2|Buck2]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Buck2" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Buck2.md]] +- Raw Source: 00_Raw/2026-04-20/Buck2.md --- diff --git a/01_Archive/2026-04-20/Buffer Allocation.md b/01_Archive/2026-04-20/Buffer Allocation.md index 6694e3ea..e9bd2932 100644 --- a/01_Archive/2026-04-20/Buffer Allocation.md +++ b/01_Archive/2026-04-20/Buffer Allocation.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-B20BA9 -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Buffer Allocation" --- -# [[Buffer Allocation]] +# [[Buffer Allocation|Buffer Allocation]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 버퍼 할당(Buffer Allocation)은 WebGL 및 WebGPU 환경에서 정점, 인덱스, 인스턴스 변환 행렬 등의 데이터를 저장하기 위해 GPU 메모리 공간을 확보하는 과정입니다. 렌더링 중 동적으로 버퍼 크기를 늘리거나 빈번하게 데이터를 업데이트할 경우 심각한 프레임 지연 및 메모리 오류가 발생할 수 있습니다. 따라서 최대 예상치에 맞춰 사전에 버퍼를 할당하고, 재사용 가능한 영구적인 GPU 버퍼를 활용하는 것이 3D 애플리케이션 성능 최적화에 필수적입니다. @@ -24,11 +24,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Buffer Allocation" - **정책 변화:** Graphics & Performance 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[GPU Instancing]], [[Memory Management]], [[Object Pooling]], [[Garbage Collection]] -- **Projects/Contexts:** [[Three.js]], [[Needle Engine]], [[WebGPU]] +- **Related Topics:** GPU Instancing, [[Memory Management|Memory Management]], [[Object Pooling|Object Pooling]], [[Garbage Collection|Garbage Collection]] +- **Projects/Contexts:** [[Three.js|Three.js]], [[Needle Engine|Needle Engine]], [[WebGPU|WebGPU]] - **Contradictions/Notes:** 소스에서는 실행 중 버퍼 크기를 동적으로 늘리는 방식(Dynamic Growth)은 성능 지연과 오류를 낳으므로, 초기에 넉넉하게 메모리 공간을 사전 할당(Preallocate)하는 방식이 훨씬 안정적이라고 강조합니다 [1-3]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Buffer Allocation.md]] +- Raw Source: 00_Raw/2026-04-20/Buffer Allocation.md --- diff --git a/01_Archive/2026-04-20/BufferAttribute.md b/01_Archive/2026-04-20/BufferAttribute.md index f4f24bf4..a3ab708a 100644 --- a/01_Archive/2026-04-20/BufferAttribute.md +++ b/01_Archive/2026-04-20/BufferAttribute.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-7E5F3E -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - BufferAttribute" --- -# [[BufferAttribute]] +# [[BufferAttribute|BufferAttribute]] ## 📌 한 줄 통찰 (The Karpathy Summary) > `BufferAttribute`는 Three.js에서 3D 모델의 지오메트리 데이터를 저장하고 관리하기 위해 사용되는 핵심 클래스입니다 [1, 2]. 이 클래스는 Web Worker와 메인 스레드 간에 데이터를 중복 복사 없이 효율적으로 공유할 수 있게 해주며, 데이터 압축을 통한 메모리 최적화를 지원합니다 [2, 3]. 또한, 파생 클래스인 `InstancedBufferAttribute`를 통해 인스턴스 기반 렌더링에서 객체별 고유 데이터를 GPU로 전송하는 필수적인 역할을 수행합니다 [4, 5]. @@ -23,11 +23,11 @@ github_commit: "[P-Reinforce] Continuous Worker - BufferAttribute" - **정책 변화:** Graphics & Performance 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[InstancedBufferAttribute]], [[BufferGeometry]], [[SharedArrayBuffer]], [[InstancedMesh]] -- **Projects/Contexts:** [[WebGL/Three.js 대규모 CAD 렌더링 메모리 최적화]], [[다중 객체 드로우 콜 최적화 및 커스텀 셰이더 적용 맥락]] +- **Related Topics:** InstancedBufferAttribute, [[BufferGeometry|BufferGeometry]], [[SharedArrayBuffer|SharedArrayBuffer]], [[InstancedMesh|InstancedMesh]] +- **Projects/Contexts:** WebGL/Three.js 대규모 CAD 렌더링 메모리 최적화, 다중 객체 드로우 콜 최적화 및 커스텀 셰이더 적용 맥락 - **Contradictions/Notes:** 소스에 관련 정보가 부족합니다. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/BufferAttribute.md]] +- Raw Source: 00_Raw/2026-04-20/BufferAttribute.md --- diff --git a/01_Archive/2026-04-20/BufferGeometry.md b/01_Archive/2026-04-20/BufferGeometry.md index cca2ca7f..9f6944d6 100644 --- a/01_Archive/2026-04-20/BufferGeometry.md +++ b/01_Archive/2026-04-20/BufferGeometry.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-2887C6 -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - BufferGeometry" --- -# [[BufferGeometry]] +# [[BufferGeometry|BufferGeometry]] ## 📌 한 줄 통찰 (The Karpathy Summary) > BufferGeometry는 Three.js의 핵심 3D 기하학 구조를 정의하는 객체이다 [1]. InstancedMesh 기술에서 수많은 인스턴스가 공통으로 공유하는 기하학적 데이터로 사용된다 [2, 3]. 또한 여러 개의 지오메트리를 단일 BufferGeometry로 병합하여 렌더링 과정에서 발생하는 드로우 콜(Draw Call)을 최소화하는 성능 최적화의 핵심 단위로도 활용된다 [4, 5]. @@ -23,11 +23,11 @@ github_commit: "[P-Reinforce] Continuous Worker - BufferGeometry" - **정책 변화:** Graphics & Performance 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[InstancedMesh]], [[Draw Call]], [[BufferGeometryUtils]] -- **Projects/Contexts:** [[Three.js]], [[IFC.js Fragment]] +- **Related Topics:** [[InstancedMesh|InstancedMesh]], [[Draw Call|Draw Call]], BufferGeometryUtils +- **Projects/Contexts:** [[Three.js|Three.js]], [[IFCjs (Fragment)|IFC.js Fragment]] - **Contradictions/Notes:** 소스 문헌들은 성능 개선을 위해 객체들을 단일 BufferGeometry로 병합할 것을 권장하면서도, 이 방식이 드로우 콜을 최소화하는 대신 RAM 소모량을 높이고 시야 절두체 컬링의 효율을 저하시키는 트레이드오프(Trade-off)를 유발한다고 경고한다 [4, 5]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/BufferGeometry.md]] +- Raw Source: 00_Raw/2026-04-20/BufferGeometry.md --- diff --git a/01_Archive/2026-04-20/Burnout Prevention in Professional Gaming.md b/01_Archive/2026-04-20/Burnout Prevention in Professional Gaming.md index 5dc94cf1..54939061 100644 --- a/01_Archive/2026-04-20/Burnout Prevention in Professional Gaming.md +++ b/01_Archive/2026-04-20/Burnout Prevention in Professional Gaming.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-68BEC5 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Burnout Prevention in Professional Gaming" --- -# [[Burnout Prevention in Professional Gaming]] +# [[Burnout Prevention in Professional Gaming|Burnout Prevention in Professional Gaming]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Burnout Prevention in Professi ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Burnout Prevention in Professional Gaming.md]] +- Raw Source: 00_Raw/2026-04-20/Burnout Prevention in Professional Gaming.md --- diff --git a/01_Archive/2026-04-20/CAD 렌더링 최적화.md b/01_Archive/2026-04-20/CAD 렌더링 최적화.md index 86b76213..91233e2f 100644 --- a/01_Archive/2026-04-20/CAD 렌더링 최적화.md +++ b/01_Archive/2026-04-20/CAD 렌더링 최적화.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-40FA98 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - CAD 렌더링 최적화" --- -# [[CAD 렌더링 최적화]] +# [[CAD 렌더링 최적화|CAD 렌더링 최적화]] ## 📌 한 줄 통찰 (The Karpathy Summary) > CAD 렌더링 최적화는 브라우저 및 통합 GPU(iGPU) 환경에서 메모리 대역폭과 CPU-GPU 간 통신 병목을 극복하여 수백만 개의 폴리곤을 가진 대규모 다중 본체 어셈블리(Multi-Body Assemblies)를 부드럽게 렌더링하는 일련의 기술적 과정입니다 [1, 2]. 이를 위해 `BatchedMesh`나 `InstancedMesh`를 통한 드로우 콜 최소화, 정밀도 붕괴 방지를 위한 원점 이동(Origin-shifting), 메모리 관리 효율화를 위한 Web Worker 및 `SharedArrayBuffer` 활용이 필수적으로 요구됩니다 [3-5]. 또한, 오버드로우를 줄이는 깊이 사전 패스(Depth Pre-Pass)와 시각적 끊김이 없는 디더링 LOD 등의 렌더링 기법을 결합하여 고성능의 시각화 경험을 제공합니다 [6-8]. @@ -25,11 +25,11 @@ github_commit: "[P-Reinforce] Continuous Worker - CAD 렌더링 최적화" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[BatchedMesh]], [[InstancedMesh]], [[Depth Pre-Pass]], [[SharedArrayBuffer]], [[Frustum Culling]], [[Level of Detail (LOD)]] -- **Projects/Contexts:** [[WebGPU 대규모 건설 뷰어]], [[BIM 모델 시뮬레이션]] +- **Related Topics:** [[BatchedMesh|BatchedMesh]], [[InstancedMesh|InstancedMesh]], [[Depth Pre-Pass|Depth Pre-Pass]], [[SharedArrayBuffer|SharedArrayBuffer]], [[Frustum Culling|Frustum Culling]], [[Level of Detail (LOD)|Level of Detail (LOD)]] +- **Projects/Contexts:** [[WebGPU 대규모 건설 뷰어|WebGPU 대규모 건설 뷰어]], [[BIM 모델 시뮬레이션|BIM 모델 시뮬레이션]] - **Contradictions/Notes:** 지오메트리 병합(`BufferGeometryUtils.mergeBufferGeometries`) 기법은 드로우 콜을 가장 효과적으로 줄여주지만, 단일 바운딩 볼륨으로 묶이기 때문에 시야 절두체 컬링(Frustum Culling)의 효율성을 떨어뜨린다는 딜레마를 가집니다 [11]. 또한, `InstancedMesh`는 단일 지오메트리의 반복 렌더링에는 매우 유리하지만 서로 다른 기하학적 구조를 가진 부품이 수천 개 모인 CAD 모델에는 부적합하며, 이 경우 다중 지오메트리를 지원하는 `BatchedMesh`를 사용하는 것이 더 올바른 대안입니다 [3, 10, 20]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/CAD 렌더링 최적화.md]] +- Raw Source: 00_Raw/2026-04-20/CAD 렌더링 최적화.md --- diff --git a/01_Archive/2026-04-20/CANTAB 5-선택 반응 시간 과제(CANTAB 5-choice RTI).md b/01_Archive/2026-04-20/CANTAB 5-선택 반응 시간 과제(CANTAB 5-choice RTI).md index ba626180..d41aac85 100644 --- a/01_Archive/2026-04-20/CANTAB 5-선택 반응 시간 과제(CANTAB 5-choice RTI).md +++ b/01_Archive/2026-04-20/CANTAB 5-선택 반응 시간 과제(CANTAB 5-choice RTI).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-20A493 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - CANTAB 5-선택 반응 시간 과제(CANTAB 5-choice RTI)" --- -# [[CANTAB 5-선택 반응 시간 과제(CANTAB 5-choice RTI)]] +# [[CANTAB 5-선택 반응 시간 과제(CANTAB 5-choice RTI)|CANTAB 5-선택 반응 시간 과제(CANTAB 5-choice RTI)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > CANTAB 5-선택 반응 시간 과제(RTI)는 참가자의 반응 속도를 측정하여 인지적 요인과 신체적 움직임 요인을 분리하여 평가할 수 있도록 설계된 인지 측정 과제입니다 [1]. 이 과제는 주로 iPad의 CANTAB 앱을 통해 시행되며, 사용자가 화면의 5개 위치를 모니터링하다가 나타나는 시각적 자극에 최대한 빠르게 반응하는 능력을 평가합니다 [1]. 과제의 결과는 크게 '의사결정 속도'와 '이동 속도'라는 두 가지 구성 요소로 나뉘어 측정됩니다 [1, 2]. @@ -24,11 +24,11 @@ github_commit: "[P-Reinforce] Continuous Worker - CANTAB 5-선택 반응 시간 - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[의사결정 속도(Decision Speed)]], [[이동 속도(Movement Speed)]] -- **Projects/Contexts:** [[가상현실 사후 효과 연구(Virtual Reality Aftereffects Study)]] +- **Related Topics:** [[의사결정 속도(Decision Speed)|의사결정 속도(Decision Speed)]], [[이동 속도(Movement Speed)|이동 속도(Movement Speed)]] +- **Projects/Contexts:** [[가상현실 사후 효과 연구(Virtual Reality Aftereffects Study)|가상현실 사후 효과 연구(Virtual Reality Aftereffects Study)]] - **Contradictions/Notes:** 소스에 관련 정보가 부족합니다. (소스 데이터 내에서 해당 과제에 대해 상충하는 주장이나 논쟁점은 확인되지 않습니다.) --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/CANTAB 5-선택 반응 시간 과제(CANTAB 5-choice RTI).md]] +- Raw Source: 00_Raw/2026-04-20/CANTAB 5-선택 반응 시간 과제(CANTAB 5-choice RTI).md --- diff --git a/01_Archive/2026-04-20/CI_CD Pipeline.md b/01_Archive/2026-04-20/CI_CD Pipeline.md index 9c00da8f..8c0d181b 100644 --- a/01_Archive/2026-04-20/CI_CD Pipeline.md +++ b/01_Archive/2026-04-20/CI_CD Pipeline.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-643BD1 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - CI_CD Pipeline" --- -# [[CI_CD Pipeline]] +# [[CI_CD Pipeline|CI_CD Pipeline]] ## 📌 한 줄 통찰 (The Karpathy Summary) > CI/CD 파이프라인은 소프트웨어 개발 수명 주기(SDLC)에서 코드의 빌드, 테스트 및 배포를 자동화하는 워크플로우입니다. 이 파이프라인은 정적 애플리케이션 보안 테스트(SAST), 린팅, 자동화된 코드 리뷰 등의 도구를 통합하여 코드가 프로덕션 환경에 도달하기 전에 결함과 취약점을 차단하는 필수적인 안전장치 역할을 합니다. 개발 속도를 저하시키지 않으면서 코드 품질과 보안을 일관되게 유지하고 정책을 강제하는 핵심적인 경계선(Enforcement Boundary)으로 기능합니다. @@ -24,11 +24,11 @@ github_commit: "[P-Reinforce] Continuous Worker - CI_CD Pipeline" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Static Application Security Testing (SAST)]], [[Automated Code Review]], [[Quality Gates]], [[DevSecOps]], [[Git Hooks]] -- **Projects/Contexts:** [[소프트웨어 개발 수명 주기(SDLC)]], [[풀 리퀘스트(Pull Request) 워크플로우]] +- **Related Topics:** [[Static Application Security Testing (SAST)|Static Application Security Testing (SAST)]], Automated Code Review, [[Quality Gates|Quality Gates]], [[DevSecOps|DevSecOps]], [[Git Hooks|Git Hooks]] +- **Projects/Contexts:** [[소프트웨어 개발 수명 주기 (SDLC)|소프트웨어 개발 수명 주기(SDLC)]], 풀 리퀘스트(Pull Request) 워크플로우 - **Contradictions/Notes:** 개발자 환경의 로컬 훅(Husky 등)은 빠르고 편리한 피드백을 위한 도구일 뿐 완벽한 강제 수단이 아니며, 실제적인 보안 및 품질 규칙의 최종 강제는 CI/CD 파이프라인에서 이루어져야 합니다 [15, 16]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/CI_CD Pipeline.md]] +- Raw Source: 00_Raw/2026-04-20/CI_CD Pipeline.md --- diff --git a/01_Archive/2026-04-20/CI_CD 및 Pull Request 자동화 리뷰.md b/01_Archive/2026-04-20/CI_CD 및 Pull Request 자동화 리뷰.md index 7aaa50da..a7132c5c 100644 --- a/01_Archive/2026-04-20/CI_CD 및 Pull Request 자동화 리뷰.md +++ b/01_Archive/2026-04-20/CI_CD 및 Pull Request 자동화 리뷰.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-877DCA -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - CI_CD 및 Pull Request 자동화 리뷰" --- -# [[CI_CD 및 Pull Request 자동화 리뷰]] +# [[CI_CD 및 Pull Request 자동화 리뷰|CI_CD 및 Pull Request 자동화 리뷰]] ## 📌 한 줄 통찰 (The Karpathy Summary) > CI/CD 및 Pull Request(PR) 자동화 리뷰는 소프트웨어 개발 수명 주기(SDLC)에서 코드 병합 이전에 정적 분석 도구(SAST), 린터(Linter), AI 코드 리뷰 봇 등을 활용하여 취약점, 버그, 스타일 위반을 자동으로 검사하는 과정입니다 [1, 2]. 이를 통해 빠른 피드백 루프를 형성하고, 일관된 코드 품질 기준을 강제하며, CI/CD 파이프라인 내에서 품질 게이트(Quality Gate) 역할을 수행하여 인간 리뷰어의 피로도를 줄이고 보안과 품질을 극대화합니다 [3-6]. @@ -23,11 +23,11 @@ github_commit: "[P-Reinforce] Continuous Worker - CI_CD 및 Pull Request 자동 - **정책 변화:** AI 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Static Application Security Testing (SAST)]], [[Git Hooks]], [[AI Code Review]] -- **Projects/Contexts:** [[CI/CD Pipelines]], [[DevSecOps]] +- **Related Topics:** [[Static Application Security Testing (SAST)|Static Application Security Testing (SAST)]], [[Git Hooks|Git Hooks]], AI Code Review +- **Projects/Contexts:** CI/CD Pipelines, [[DevSecOps|DevSecOps]] - **Contradictions/Notes:** 소스들은 자동화된 리뷰 도구가 매우 빠르고 일관적이지만 인간 리뷰어를 완전히 대체할 수는 없다고 주장합니다. 자동화 도구나 AI 봇은 문맥 맹점(Context Blindness)이 있어 아키텍처 설계나 비즈니스 로직을 온전히 이해하지 못하므로, 기계가 루틴한 검사를 담당하고 사람은 고차원적인 판단을 내리는 하이브리드 방식이 필수적이라고 강조합니다 [28, 31, 32]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/CI_CD 및 Pull Request 자동화 리뷰.md]] +- Raw Source: 00_Raw/2026-04-20/CI_CD 및 Pull Request 자동화 리뷰.md --- diff --git a/01_Archive/2026-04-20/CI_CD 파이프라인 (CI_CD Pipelines).md b/01_Archive/2026-04-20/CI_CD 파이프라인 (CI_CD Pipelines).md index 3d4a5870..6848e022 100644 --- a/01_Archive/2026-04-20/CI_CD 파이프라인 (CI_CD Pipelines).md +++ b/01_Archive/2026-04-20/CI_CD 파이프라인 (CI_CD Pipelines).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-3D8966 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - CI_CD 파이프라인 (CI_CD Pipelines)" --- -# [[CI_CD 파이프라인 (CI_CD Pipelines)]] +# [[CI_CD 파이프라인 (CI_CD Pipelines)|CI_CD 파이프라인 (CI_CD Pipelines)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -23,11 +23,11 @@ github_commit: "[P-Reinforce] Continuous Worker - CI_CD 파이프라인 (CI_CD P - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[SAST (Static Application Security Testing)]], [[Quality Gate]], [[Automated Code Review]], [[Shift-left]], [[Git Hooks]] -- **Projects/Contexts:** [[GitHub Actions, GitLab CI, Jenkins (CI/CD Platforms)]], [[SonarQube / Snyk Code Integration]] +- **Related Topics:** [[SAST (Static Application Security Testing)|SAST (Static Application Security Testing)]], Quality Gate, Automated Code Review, [[시프트 레프트 (Shift-Left)|Shift-left]], [[Git Hooks|Git Hooks]] +- **Projects/Contexts:** GitHub Actions, GitLab CI, Jenkins (CI/CD Platforms), SonarQube / Snyk Code Integration - **Contradictions/Notes:** 개발 로컬 환경에서의 Git Hooks(Husky 등) 검사는 빠른 피드백을 제공하지만 개발자에 의해 의도적으로 무시될 수 있습니다. 반면 CI/CD 파이프라인에서의 검사는 조직의 규칙을 최종적으로 집행하므로, 로컬 검사가 CI/CD 파이프라인의 필요성을 대체할 수는 없다고 소스들은 강조합니다 [5, 16]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/CI_CD 파이프라인 (CI_CD Pipelines).md]] +- Raw Source: 00_Raw/2026-04-20/CI_CD 파이프라인 (CI_CD Pipelines).md --- diff --git a/01_Archive/2026-04-20/CI_CD 파이프라인 및 IDE 통합 보안.md b/01_Archive/2026-04-20/CI_CD 파이프라인 및 IDE 통합 보안.md index a5e28903..496fdbc4 100644 --- a/01_Archive/2026-04-20/CI_CD 파이프라인 및 IDE 통합 보안.md +++ b/01_Archive/2026-04-20/CI_CD 파이프라인 및 IDE 통합 보안.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-F8BCE8 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - CI_CD 파이프라인 및 IDE 통합 보안" --- -# [[CI_CD 파이프라인 및 IDE 통합 보안]] +# [[CI_CD 파이프라인 및 IDE 통합 보안|CI_CD 파이프라인 및 IDE 통합 보안]] ## 📌 한 줄 통찰 (The Karpathy Summary) > CI/CD 파이프라인 및 IDE 통합 보안은 소프트웨어 개발 프로세스 전반에 걸쳐 코드의 품질과 보안을 유지하기 위한 핵심 접근법입니다 [1], [2]. 개발자가 코드를 작성하는 IDE 환경과 코드가 병합 및 배포되는 CI/CD 워크플로우에 정적 분석(SAST) 및 자동화된 보안 검사 도구를 내장하여 실시간 피드백을 제공합니다 [3], [4]. 이를 통해 개발자는 코드의 결함과 취약점을 조기에 식별하고 수정할 수 있어 안전하고 효율적인 소프트웨어 개발 수명 주기(SDLC)를 확보할 수 있습니다 [5], [6]. @@ -22,11 +22,11 @@ github_commit: "[P-Reinforce] Continuous Worker - CI_CD 파이프라인 및 IDE - **정책 변화:** AI 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[SAST(정적 애플리케이션 보안 테스트)]], [[Shift-left(시프트 레프트)]], [[SDLC(소프트웨어 개발 수명 주기)]] -- **Projects/Contexts:** [[SonarQube]], [[Snyk Code]], [[DevSecOps]] +- **Related Topics:** [[SAST (정적 애플리케이션 보안 테스트)|SAST(정적 애플리케이션 보안 테스트)]], Shift-left(시프트 레프트), [[SDLC (소프트웨어 개발 수명 주기)|SDLC(소프트웨어 개발 수명 주기)]] +- **Projects/Contexts:** [[SonarQube|SonarQube]], Snyk Code, [[DevSecOps|DevSecOps]] - **Contradictions/Notes:** 소스 내용 중 이 주제에 대한 명시적인 모순이나 반대 의견은 존재하지 않습니다. 모든 소스가 조기 발견(Shift-left)의 효율성 및 통합의 필요성에 동의하고 있습니다. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/CI_CD 파이프라인 및 IDE 통합 보안.md]] +- Raw Source: 00_Raw/2026-04-20/CI_CD 파이프라인 및 IDE 통합 보안.md --- diff --git a/01_Archive/2026-04-20/CI_CD 파이프라인 자동화.md b/01_Archive/2026-04-20/CI_CD 파이프라인 자동화.md index 06c18a01..6622be5b 100644 --- a/01_Archive/2026-04-20/CI_CD 파이프라인 자동화.md +++ b/01_Archive/2026-04-20/CI_CD 파이프라인 자동화.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-B0C6AD -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - CI_CD 파이프라인 자동화" --- -# [[CI_CD 파이프라인 자동화]] +# [[CI_CD 파이프라인 자동화|CI_CD 파이프라인 자동화]] ## 📌 한 줄 통찰 (The Karpathy Summary) > CI/CD 파이프라인 자동화는 소프트웨어 개발 수명 주기(SDLC)에서 정적 분석, 코드 포맷팅, 보안 테스트(SAST)를 워크플로우에 통합하여 자동으로 실행되게 하는 과정입니다 [1-3]. 이를 통해 코드가 병합되거나 프로덕션 환경에 배포되기 전에 구문 오류, 결함 및 보안 취약점을 조기에 발견하고 차단할 수 있습니다 [4-6]. 결과적으로 수동 코드 리뷰에 드는 시간을 절약하고, 소프트웨어의 전반적인 품질과 일관성을 효율적으로 유지할 수 있습니다 [7, 8]. @@ -23,11 +23,11 @@ github_commit: "[P-Reinforce] Continuous Worker - CI_CD 파이프라인 자동 - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[정적 애플리케이션 보안 테스트 (SAST)]], [[Git Hooks (Husky 및 lint-staged)]], [[품질 게이트 (Quality Gates)]] -- **Projects/Contexts:** [[DevSecOps 파이프라인 통합]], [[풀 리퀘스트(PR) 검사 자동화]] +- **Related Topics:** [[정적 애플리케이션 보안 테스트 (SAST)|정적 애플리케이션 보안 테스트 (SAST)]], Git Hooks (Husky 및 lint-staged), 품질 게이트 (Quality Gates) +- **Projects/Contexts:** DevSecOps 파이프라인 통합, 풀 리퀘스트(PR) 검사 자동화 - **Contradictions/Notes:** 소스에 따르면 정적 분석 도구를 파이프라인에 통합할 때 심층적인 스캔은 분석 시간이 오래 걸려 CI/CD 파이프라인을 지연시키는 원인이 될 수 있습니다(예: SonarQube Cloud는 일부 환경에서 파이프라인에 추가 시간을 발생시킴) [28]. 따라서 파이프라인 속도 저하를 방지하기 위해 PR 단계에서는 변경된 파일만 가볍고 빠르게 검사하는 `lint-staged`나 증분 스캔(incremental scans)을 활용하고, 전체 코드 스캔이나 무거운 분석은 CI 서버의 별도 단계나 정기 스캔으로 미루는 방식이 권장됩니다 [18, 19, 29, 30]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/CI_CD 파이프라인 자동화.md]] +- Raw Source: 00_Raw/2026-04-20/CI_CD 파이프라인 자동화.md --- diff --git a/01_Archive/2026-04-20/CI_CD 파이프라인 통합 및 Git 훅(Hooks).md b/01_Archive/2026-04-20/CI_CD 파이프라인 통합 및 Git 훅(Hooks).md index eeb849a3..6eba3116 100644 --- a/01_Archive/2026-04-20/CI_CD 파이프라인 통합 및 Git 훅(Hooks).md +++ b/01_Archive/2026-04-20/CI_CD 파이프라인 통합 및 Git 훅(Hooks).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-C861C6 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - CI_CD 파이프라인 통합 및 Git 훅(Hooks)" --- -# [[CI_CD 파이프라인 통합 및 Git 훅(Hooks)]] +# [[CI_CD 파이프라인 통합 및 Git 훅(Hooks)|CI_CD 파이프라인 통합 및 Git 훅(Hooks)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > CI/CD 파이프라인 통합 및 Git 훅(Hooks)은 소프트웨어 개발 시 코드 변경 사항이 저장소에 반영되거나 배포되기 전에 코드 품질과 보안을 자동으로 검증하는 필수 프로세스입니다. 로컬 환경에서는 Husky와 lint-staged 같은 도구를 활용한 Git 훅을 통해 커밋 전 단계에서 정적 분석과 포매팅을 강제하여 1차적인 결함을 차단합니다. 이후 CI/CD 파이프라인 서버와 연동되어 우회 불가능한 자동화된 테스트, 보안 스캔(SAST), 품질 게이트를 거쳐 최종적으로 안전하고 일관된 코드만 배포되도록 보장합니다. @@ -30,11 +30,11 @@ github_commit: "[P-Reinforce] Continuous Worker - CI_CD 파이프라인 통합 - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Git Hooks]], [[Husky]], [[lint-staged]], [[SAST (Static Application Security Testing)]], [[ESLint]], [[Prettier]] -- **Projects/Contexts:** [[안전한 소프트웨어 개발 수명주기(SSDLC)]], [[프론트엔드 및 모노레포(Monorepo) 개발 환경 설정]], [[풀 리퀘스트(PR) 기반 보안 검토]] +- **Related Topics:** [[Git Hooks|Git Hooks]], [[Husky|Husky]], [[lint-staged|lint-staged]], [[SAST (Static Application Security Testing)|SAST (Static Application Security Testing)]], [[ESLint|ESLint]], [[Prettier|Prettier]] +- **Projects/Contexts:** [[안전한 소프트웨어 개발 수명주기(SSDLC)|안전한 소프트웨어 개발 수명주기(SSDLC)]], [[프론트엔드 및 모노레포(Monorepo) 개발 환경 설정|프론트엔드 및 모노레포(Monorepo) 개발 환경 설정]], [[풀 리퀘스트(PR) 기반 보안 검토|풀 리퀘스트(PR) 기반 보안 검토]] - **Contradictions/Notes:** 로컬 Git 훅(pre-commit 등)은 빠른 피드백을 제공하여 CI 실패를 줄여주는 유용한 도구이지만, 개발자가 임의로 우회할 수 있으므로 절대 CI/CD 검증을 대체해서는 안 되며 상호 보완적으로 사용해야 한다고 강조됩니다 [9, 10]. 또한, lint-staged는 변경된 특정 파일에만 국한된 작업(예: 포매팅, 린팅)에는 뛰어나지만, 프로젝트 전체를 대상으로 실행되어야 하는 도구(예: 전체 타입 체크)의 래퍼(wrapper)로 사용하는 것은 부적절합니다 [6, 20]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/CI_CD 파이프라인 통합 및 Git 훅(Hooks).md]] +- Raw Source: 00_Raw/2026-04-20/CI_CD 파이프라인 통합 및 Git 훅(Hooks).md --- diff --git a/01_Archive/2026-04-20/CI_CD 파이프라인.md b/01_Archive/2026-04-20/CI_CD 파이프라인.md index fbc9510c..70f65558 100644 --- a/01_Archive/2026-04-20/CI_CD 파이프라인.md +++ b/01_Archive/2026-04-20/CI_CD 파이프라인.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-057C1E -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - CI_CD 파이프라인" --- -# [[CI_CD 파이프라인]] +# [[CI_CD 파이프라인|CI_CD 파이프라인]] ## 📌 한 줄 통찰 (The Karpathy Summary) > CI/CD 파이프라인은 소프트웨어 개발 수명 주기(SDLC)에서 코드의 통합, 테스트 및 배포를 자동화하는 워크플로우입니다 [1-3]. 이 파이프라인에는 정적 애플리케이션 보안 테스트(SAST) 및 자동화된 코드 리뷰 도구들이 통합되어, 코드가 프로덕션 환경에 도달하기 전에 보안 취약점, 버그 및 스타일 위반을 조기에 발견합니다 [3-6]. 결과적으로 조직은 개발 속도를 늦추지 않으면서도 보안을 강화하고 높은 소프트웨어 품질 기준을 일관되게 적용할 수 있습니다 [7-9]. @@ -23,11 +23,11 @@ github_commit: "[P-Reinforce] Continuous Worker - CI_CD 파이프라인" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[자동화된 코드 리뷰(Automated Code Review)]], [[정적 애플리케이션 보안 테스트(SAST)]], [[품질 게이트(Quality Gates)]], [[시프트 레프트(Shift-Left)]] -- **Projects/Contexts:** [[소프트웨어 개발 수명 주기(SDLC)]], [[데브섹옵스(DevSecOps)]], [[풀 리퀘스트(Pull Request) 워크플로우]] +- **Related Topics:** 자동화된 코드 리뷰(Automated Code Review), [[정적 애플리케이션 보안 테스트(SAST)|정적 애플리케이션 보안 테스트(SAST)]], 품질 게이트(Quality Gates), [[시프트 레프트(Shift-Left)|시프트 레프트(Shift-Left)]] +- **Projects/Contexts:** [[소프트웨어 개발 수명 주기 (SDLC)|소프트웨어 개발 수명 주기(SDLC)]], 데브섹옵스(DevSecOps), 풀 리퀘스트(Pull Request) 워크플로우 - **Contradictions/Notes:** CI/CD 파이프라인에 SonarQube Cloud나 대규모 SAST 도구를 통합하면 코드 품질과 보안을 강력하게 통제할 수 있지만, 일부 환경에서는 파이프라인 실행 시간이 추가로 소요될 수 있다는 단점이 존재합니다 [5, 17, 28]. 또한, 로컬 Git Hook 환경이 효율적이더라도 CI 환경에서의 전체 검증 과정을 결코 대체할 수 없으며, 반드시 CI 파이프라인의 후속 검증이 동반되어야 한다고 강조됩니다 [23, 24, 29]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/CI_CD 파이프라인.md]] +- Raw Source: 00_Raw/2026-04-20/CI_CD 파이프라인.md --- diff --git a/01_Archive/2026-04-20/CI_CD.md b/01_Archive/2026-04-20/CI_CD.md index e8c5077f..7f97b9c3 100644 --- a/01_Archive/2026-04-20/CI_CD.md +++ b/01_Archive/2026-04-20/CI_CD.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-CFCF20 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - CI_CD" --- -# [[CI_CD]] +# [[CI_CD|CI_CD]] ## 📌 한 줄 통찰 (The Karpathy Summary) > CI/CD(Continuous Integration / Continuous Delivery)는 소프트웨어 개발 라이프사이클(SDLC) 전반에 걸쳐 코드의 빌드, 테스트, 병합 및 배포 과정을 자동화하는 워크플로우 파이프라인입니다 [1-3]. 주로 정적 애플리케이션 보안 테스트(SAST) 및 AI 코드 리뷰 도구와 결합하여 코드 결함과 보안 취약점을 프로덕션 배포 전에 조기에 발견하고 차단하는 역할을 합니다 [4-6]. 이를 통해 개발 팀은 품질 저하 없이 일관되고 빠른 소프트웨어 릴리스 주기를 유지할 수 있습니다 [7-9]. @@ -23,11 +23,11 @@ github_commit: "[P-Reinforce] Continuous Worker - CI_CD" - **정책 변화:** AI 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[SAST]], [[Quality Gate]], [[Pull Request]], [[Automated Code Review]] -- **Projects/Contexts:** 보안 스캔을 개발 워크플로우에 통합하기 위해 자주 사용되는 [[SonarQube Cloud]], [[Snyk Code]], [[Qodana]], [[GitHub Actions]] 기반 파이프라인 환경. +- **Related Topics:** [[SAST|SAST]], Quality Gate, [[풀 리퀘스트 (Pull Request)|Pull Request]], Automated Code Review +- **Projects/Contexts:** 보안 스캔을 개발 워크플로우에 통합하기 위해 자주 사용되는 SonarQube Cloud, Snyk Code, Qodana, [[GitHub Actions|GitHub Actions]] 기반 파이프라인 환경. - **Contradictions/Notes:** 소스 문헌들은 CI/CD를 통한 자동화 검사가 빠르고 일관된 피드백을 제공하여 보안을 크게 향상시킨다고 주장하지만 [8], 자동화 도구는 비즈니스 로직이나 코드의 의도(Context)를 완전히 이해하지 못해 오탐(False Positive)을 유발할 수 있는 한계가 있으므로 파이프라인 자동화에만 의존해서는 안 되며 반드시 수동 리뷰와 결합해야 한다고 조언합니다 [14, 24, 25]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/CI_CD.md]] +- Raw Source: 00_Raw/2026-04-20/CI_CD.md --- diff --git a/01_Archive/2026-04-20/CPTED.md b/01_Archive/2026-04-20/CPTED.md index 7f789558..426dccc6 100644 --- a/01_Archive/2026-04-20/CPTED.md +++ b/01_Archive/2026-04-20/CPTED.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-9984E9 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - CPTED" --- -# [[CPTED]] +# [[CPTED|CPTED]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - CPTED" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/CPTED.md]] +- Raw Source: 00_Raw/2026-04-20/CPTED.md --- diff --git a/01_Archive/2026-04-20/CPU Bottleneck.md b/01_Archive/2026-04-20/CPU Bottleneck.md index ab449bed..5b420ff6 100644 --- a/01_Archive/2026-04-20/CPU Bottleneck.md +++ b/01_Archive/2026-04-20/CPU Bottleneck.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-944A15 -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - CPU Bottleneck" --- -# [[CPU Bottleneck]] +# [[CPU Bottleneck|CPU Bottleneck]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 3D 그래픽스 및 실시간 렌더링 환경에서 CPU 병목(CPU Bottleneck)이란, CPU가 렌더링 명령어(드로우 콜)를 준비하고 GPU로 전송하거나 필요한 데이터 연산을 처리하는 속도가 느려져 GPU가 제 성능을 발휘하지 못하고 대기(Starve)하게 되는 현상을 말합니다 [1]. 주로 개별 모델에 대한 과도한 드로우 콜 발행이나 자바스크립트 메인 스레드에서의 무거운 연산(애니메이션, 정렬, 컬링 등)으로 인해 발생하며 [2-4], 이를 해결하기 위해 인스턴싱(Instancing)이나 연산의 GPU 오프로딩 기법이 사용됩니다 [5, 6]. @@ -23,11 +23,11 @@ github_commit: "[P-Reinforce] Continuous Worker - CPU Bottleneck" - **정책 변화:** Graphics & Performance 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Draw Call]], [[InstancedMesh]], [[Frustum Culling]] -- **Projects/Contexts:** [[Three.js]], [[WebGL]], [[WebGPU]] +- **Related Topics:** [[Draw Call|Draw Call]], [[InstancedMesh|InstancedMesh]], [[Frustum Culling|Frustum Culling]] +- **Projects/Contexts:** [[Three.js|Three.js]], [[WebGL|WebGL]], [[WebGPU|WebGPU]] - **Contradictions/Notes:** `InstancedMesh` 기술은 수천 개의 객체를 단 한 번의 드로우 콜로 처리하여 CPU 병목을 획기적으로 해결하는 기술로 알려져 있습니다 [6, 12]. 그러나 이 방식은 개별 객체의 컬링이나 정렬 같은 내부 최적화를 지원하지 않으므로, 이를 극복하기 위해 CPU 단에서 수동으로 위치를 검사하고 버퍼를 재정렬하는 로직을 추가할 경우 오히려 이전보다 더 극심한 CPU 연산 병목이 발생하는 역설적인 상황이 빈번하게 발생합니다 [4, 9]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/CPU Bottleneck.md]] +- Raw Source: 00_Raw/2026-04-20/CPU Bottleneck.md --- diff --git a/01_Archive/2026-04-20/CPU Overhead.md b/01_Archive/2026-04-20/CPU Overhead.md index a641cf9f..593bf358 100644 --- a/01_Archive/2026-04-20/CPU Overhead.md +++ b/01_Archive/2026-04-20/CPU Overhead.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-38FA31 -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - CPU Overhead" --- -# [[CPU Overhead]] +# [[CPU Overhead|CPU Overhead]] ## 📌 한 줄 통찰 (The Karpathy Summary) > CPU 오버헤드(CPU Overhead)는 웹 그래픽 렌더링 및 브라우저 실행 중에 중앙 처리 장치(CPU)에 가해지는 계산 부담 및 처리 지연을 의미합니다 [1, 2]. WebGL과 같은 기존 API에서는 단일 스레드 기반의 명령 제출과 JavaScript 실행이 CPU 병목 현상을 일으켜 GPU가 유휴 상태에 빠지게 만듭니다 [2, 3]. WebGPU와 같은 최신 API는 멀티 스레드 명령 생성과 컴퓨트 셰이더를 통한 연산 오프로딩을 통해 이러한 CPU 오버헤드를 대폭 감소시킵니다 [4, 5]. @@ -27,11 +27,11 @@ github_commit: "[P-Reinforce] Continuous Worker - CPU Overhead" - **정책 변화:** Graphics & Performance 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[WebGL]], [[WebGPU]], [[Draw Calls]], [[Micro-latency]], [[Compute Shaders]] -- **Projects/Contexts:** [[3D Gaussian Splatting (3DGS)]], [[WebSplatter]], [[ANGLE]] +- **Related Topics:** [[WebGL|WebGL]], [[WebGPU|WebGPU]], Draw Calls, [[Micro-latency|Micro-latency]], [[Compute Shaders|Compute Shaders]] +- **Projects/Contexts:** [[3D Gaussian Splatting (3DGS)|3D Gaussian Splatting (3DGS)]], WebSplatter, [[ANGLE|ANGLE]] - **Contradictions/Notes:** 제공된 소스들 사이에서 명백한 모순은 발견되지 않습니다. 모든 소스가 WebGL의 단일 스레드 아키텍처가 야기하는 CPU 병목 현상을 WebGPU의 멀티 스레드 도입 및 명시적 리소스 관리로 극복한다는 공통된 기술적 진화를 설명하고 있습니다. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/CPU Overhead.md]] +- Raw Source: 00_Raw/2026-04-20/CPU Overhead.md --- diff --git a/01_Archive/2026-04-20/CST (구체 구문 트리).md b/01_Archive/2026-04-20/CST (구체 구문 트리).md index a8947ae7..4cc011b5 100644 --- a/01_Archive/2026-04-20/CST (구체 구문 트리).md +++ b/01_Archive/2026-04-20/CST (구체 구문 트리).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-ECB052 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - CST (구체 구문 트리)" --- -# [[CST (구체 구문 트리)]] +# [[CST (구체 구문 트리)|CST (구체 구문 트리)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > CST(구체 구문 트리) 또는 파스 트리(parse tree)는 문맥 자유 문법(context-free grammar)의 트리 표현으로, 컴파일러가 코드를 어떻게 이해하는지 보여주는 공식적인 표현 방식입니다 [1]. AST(추상 구문 트리)와 달리 포괄적인 구문 요소뿐만 아니라 미세한 문체, 어휘 및 레이아웃(공백, 들여쓰기 등)의 세부 사항까지 코드의 모든 측면을 정밀하게 포착하여 계층적 구조로 렌더링합니다 [2]. 이러한 특징으로 인해 코드 서식 지정이나 축소 등 레이아웃의 변화를 감지할 수 있어 프로그래머의 코딩 스타일을 분석하고 작성자를 식별하는 코드 스타일로메트리(Code stylometry)에 유용하게 활용됩니다 [3, 4]. @@ -27,11 +27,11 @@ github_commit: "[P-Reinforce] Continuous Worker - CST (구체 구문 트리)" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[AST (추상 구문 트리)]], [[코드 스타일로메트리 (Code Stylometry)]], [[코드 포매팅 (Code formatting)]], [[코드 축소 (Code minification)]] -- **Projects/Contexts:** [[코드 서식 지정과 축소가 코드 스타일로메트리(작성자 인식)에 미치는 영향을 평가하는 기계 학습 모델 분류 연구]] +- **Related Topics:** [[AST (추상 구문 트리)|AST (추상 구문 트리)]], [[코드 스타일로메트리 (Code Stylometry)|코드 스타일로메트리 (Code Stylometry)]], [[코드 포매팅 (Code formatting)|코드 포매팅 (Code formatting)]], [[코드 축소 (Code minification)|코드 축소 (Code minification)]] +- **Projects/Contexts:** [[코드 서식 지정과 축소가 코드 스타일로메트리(작성자 인식)에 미치는 영향을 평가하는 기계 학습 모델 분류 연구|코드 서식 지정과 축소가 코드 스타일로메트리(작성자 인식)에 미치는 영향을 평가하는 기계 학습 모델 분류 연구]] - **Contradictions/Notes:** 소스에 관련된 모순된 정보는 없으며, 기존의 주류 문헌들이 코드 표상을 위해 주로 AST를 사용하는 것에서 벗어나, 서식 지정과 축소에 따른 표면적 변화를 측정하기 위해 CST의 사용이 필수적이었다는 점을 강조합니다 [4]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/CST (구체 구문 트리).md]] +- Raw Source: 00_Raw/2026-04-20/CST (구체 구문 트리).md --- diff --git a/01_Archive/2026-04-20/CST.md b/01_Archive/2026-04-20/CST.md index 8d320118..725940ce 100644 --- a/01_Archive/2026-04-20/CST.md +++ b/01_Archive/2026-04-20/CST.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-CODING-002 -category: "[[10_Wiki/💡 Topics/Coding]]" +category: "10_Wiki/💡 Topics/Coding" confidence_score: 0.95 tags: [coding, cst, compiler, parsing] last_reinforced: 2026-04-20 github_commit: "batch-reinforce-06" --- -# [[Concrete Syntax Tree (CST)]] +# [[Concrete Syntax Tree (CST)|Concrete Syntax Tree (CST)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 소스 코드의 문법적 구조를 생략 없이 문자 그대로 담아내어, 텍스트와 의미 사이의 가교 역할을 하는 정밀한 기록. @@ -24,6 +24,6 @@ github_commit: "batch-reinforce-06" - **정책 변화:** 지식 연결성(w2) 관점에서 AST 문서와 1:1 비교 분석 구도 형성. ## 🔗 지식 연결 (Graph) -- **Parent:** [[10_Wiki/💡 Topics/Coding]] -- **Related:** [[AST_Traversal]], [[Parser]], [[Formatting-Tools]] -- **Raw Source:** [[00_Raw/2026-04-20/Concrete Syntax Tree (CST).md]] +- **Parent:** 10_Wiki/💡 Topics/Coding +- **Related:** [[AST_Traversal|AST_Traversal]], [[Parser|Parser]], Formatting-Tools +- **Raw Source:** 00_Raw/2026-04-20/Concrete Syntax Tree (CST).md diff --git a/01_Archive/2026-04-20/CV_Synthesis.md b/01_Archive/2026-04-20/CV_Synthesis.md index 4680510f..2878fd45 100644 --- a/01_Archive/2026-04-20/CV_Synthesis.md +++ b/01_Archive/2026-04-20/CV_Synthesis.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AI-002 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.95 tags: [ai, graphics, nerf, synthesis] last_reinforced: 2026-04-20 github_commit: "batch-reinforce-03" --- -# [[Computer Vision Synthesis]] +# [[Computer-Vision-Synthesis|Computer Vision Synthesis]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 정적 이미지 분석을 넘어 새로운 시점과 현실적인 영상을 생성해내는 '창조적 비전'의 영역. @@ -24,6 +24,6 @@ github_commit: "batch-reinforce-03" - **정책 변화:** 성능(w1) 대비 품질의 균형점을 NeRF 계열 지식 중심으로 재편. ## 🔗 지식 연결 (Graph) -- **Parent:** [[10_Wiki/💡 Topics/AI]] -- **Related:** [[NeRF]], [[3D_Gaussian_Splatting]], [[Generative-AI]] -- **Raw Source:** [[00_Raw/2026-04-20/Computer-Vision-Synthesis.md]] +- **Parent:** 10_Wiki/💡 Topics/AI +- **Related:** NeRF, [[3D_Gaussian_Splatting|3D_Gaussian_Splatting]], [[Generative-AI|Generative-AI]] +- **Raw Source:** 00_Raw/2026-04-20/Computer-Vision-Synthesis.md diff --git a/01_Archive/2026-04-20/Cache Side-Channel Attack.md b/01_Archive/2026-04-20/Cache Side-Channel Attack.md index fdcf566c..f4fe5d53 100644 --- a/01_Archive/2026-04-20/Cache Side-Channel Attack.md +++ b/01_Archive/2026-04-20/Cache Side-Channel Attack.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-55C813 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Cache Side-Channel Attack" --- -# [[Cache Side-Channel Attack]] +# [[Cache Side-Channel Attack|Cache Side-Channel Attack]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 캐시 사이드 채널 공격(Cache Side-Channel Attack)은 공격자가 고정밀 타이머를 사용하여 CPU 또는 GPU 캐시의 접근 속도(예: L1 캐시와 메인 메모리 간의 지연 시간 차이)를 측정함으로써, 보호된 비밀 메모리의 내용을 추론하고 유출하는 보안 취약점입니다 [1-3]. 현대 프로세서의 추측 실행(Speculative execution)과 분기 예측을 악용하는 스펙터(Spectre)와 멜트다운(Meltdown)이 대표적이며, 이를 방어하기 위해 웹 브라우저들은 타이머 정밀도를 의도적으로 낮추고 분기 없는 보안 검사(Branchless security checks)를 도입해야 했습니다 [4-7]. @@ -25,11 +25,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Cache Side-Channel Attack" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Spectre]], [[Meltdown]], [[Speculative Execution]], [[Timestamp Quantization]] -- **Projects/Contexts:** [[WebKit]], [[WebGPU]], [[WebGL]] +- **Related Topics:** [[Spectre|Spectre]], [[Meltdown|Meltdown]], [[Speculative Execution|Speculative Execution]], [[Timestamp Quantization|Timestamp Quantization]] +- **Projects/Contexts:** [[WebKit|WebKit]], [[WebGPU|WebGPU]], [[WebGL|WebGL]] - **Contradictions/Notes:** 소스에 따르면, 그래픽 파이프라인 최적화 및 렌더링 병목 현상을 해결하려는 개발자들은 나노초 단위의 고정밀 타이머를 절대적으로 필요로 하지만, 보안 측면에서는 이러한 고해상도 타이머가 캐시 사이드 채널 공격의 주요 수단이 되기 때문에 브라우저 벤더들이 타이머의 해상도를 의도적으로 제한(Coarsening)해야만 하는 기능적 상충 관계(Trade-off)가 발생하고 있습니다 [1, 13, 14, 18]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Cache Side-Channel Attack.md]] +- Raw Source: 00_Raw/2026-04-20/Cache Side-Channel Attack.md --- diff --git a/01_Archive/2026-04-20/Cache miss rates.md b/01_Archive/2026-04-20/Cache miss rates.md index b2a5066d..c1fd0010 100644 --- a/01_Archive/2026-04-20/Cache miss rates.md +++ b/01_Archive/2026-04-20/Cache miss rates.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-E946BD -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Cache miss rates" --- -# [[Cache miss rates]] +# [[Cache miss rates|Cache miss rates]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 소스에 따르면, 캐시 미스 비율(Cache miss rates) 및 캐시 적중률(Cache hit rates)은 고해상도 타이머를 통해 관찰될 수 있는 메모리 접근 패턴의 지표입니다 [1, 2]. 공격자는 이를 분석하여 CPU 및 GPU의 물리적 메모리 구조를 파악하고, 스펙터(Spectre), 멜트다운(Meltdown), 로우해머(Rowhammer)와 같은 심각한 보안 취약점을 악용할 수 있습니다 [1, 2]. 결과적으로 브라우저 벤더들은 이러한 타이밍 기반의 부채널 공격(side-channel attack)을 방지하기 위해 타임스탬프 쿼리의 정밀도를 의도적으로 제한하는 방어 기제를 채택하고 있습니다 [1, 3]. @@ -23,11 +23,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Cache miss rates" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Spectre]], [[Meltdown]], [[Rowhammer]], [[Timestamp Queries]] -- **Projects/Contexts:** [[WebGPU Timestamp Queries Quantization]], [[WebKit Security Mitigations]] +- **Related Topics:** [[Spectre|Spectre]], [[Meltdown|Meltdown]], [[Rowhammer|Rowhammer]], [[Timestamp Queries|Timestamp Queries]] +- **Projects/Contexts:** WebGPU Timestamp Queries Quantization, [[WebKit Security Mitigations|WebKit Security Mitigations]] - **Contradictions/Notes:** 소스에서는 캐시 미스 비율이 일반적인 시스템 성능 최적화 지표로 다루어지기보다는, 고해상도 타이머를 악용한 사이드 채널 보안 공격(side-channel attacks)을 가능하게 하는 위험 요소의 관점으로만 집중적으로 설명되어 있습니다 [1, 2, 4]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Cache miss rates.md]] +- Raw Source: 00_Raw/2026-04-20/Cache miss rates.md --- diff --git a/01_Archive/2026-04-20/Caliskan-Islam 등의 프로그램 바이너리 작성자 식별 연구.md b/01_Archive/2026-04-20/Caliskan-Islam 등의 프로그램 바이너리 작성자 식별 연구.md index 61426348..7dd95dbf 100644 --- a/01_Archive/2026-04-20/Caliskan-Islam 등의 프로그램 바이너리 작성자 식별 연구.md +++ b/01_Archive/2026-04-20/Caliskan-Islam 등의 프로그램 바이너리 작성자 식별 연구.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-0C1C8B -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Caliskan-Islam 등의 프로그램 바이너리 작성자 식별 연구" --- -# [[Caliskan-Islam 등의 프로그램 바이너리 작성자 식별 연구]] +# [[Caliskan-Islam 등의 프로그램 바이너리 작성자 식별 연구|Caliskan-Islam 등의 프로그램 바이너리 작성자 식별 연구]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -29,11 +29,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Caliskan-Islam 등의 프로 - **정책 변화:** AI 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Code Stylometry]], [[Random Forest]], [[Abstract Syntax Tree (AST)]], [[Control Flow Graph (CFG)]] -- **Projects/Contexts:** [[Google Code Jam]], [[GitHub]] +- **Related Topics:** [[Code Stylometry (코드 문체론)|Code Stylometry]], Random Forest, [[Abstract Syntax Tree (AST)|Abstract Syntax Tree (AST)]], Control Flow Graph (CFG) +- **Projects/Contexts:** Google Code Jam, GitHub - **Contradictions/Notes:** 소스 [2, 3]에 따르면, 초기 75만 개의 특징을 그대로 머신러닝에 투입했을 때는 성능이 30%에 그쳤으나, 정보 이득(Information gain)을 사용하여 특징을 2,000개 미만으로 대폭 줄였음에도 불구하고 정확도가 90% 근방으로 상승하는 반직관적인 결과를 보였습니다. 또한 심볼 정보 제거는 23%의 뚜렷한 성능 저하를 일으켰으나, 본격적인 소스 코드 난독화(Obfuscator-LLVM)는 식별 성능을 겨우 3.6%만 낮췄다는 흥미로운 점을 발견했습니다 [3]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Caliskan-Islam 등의 프로그램 바이너리 작성자 식별 연구.md]] +- Raw Source: 00_Raw/2026-04-20/Caliskan-Islam 등의 프로그램 바이너리 작성자 식별 연구.md --- diff --git a/01_Archive/2026-04-20/Call Stack.md b/01_Archive/2026-04-20/Call Stack.md index fa4eed17..006a26f3 100644 --- a/01_Archive/2026-04-20/Call Stack.md +++ b/01_Archive/2026-04-20/Call Stack.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-081DEE -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Call Stack" --- -# [[Call Stack]] +# [[Call Stack|Call Stack]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 콜 스택(Call Stack)은 Chrome DevTools의 성능(Performance) 분석 패널에서 페이지 실행 중 호출된 함수들의 계층 구조와 연쇄적인 실행 순서를 나타내는 요소입니다 [1-3]. 플레임 차트(Flame chart)나 Call Tree와 같은 시각적 도구를 통해 어떤 상위 이벤트가 하위 이벤트를 발생시켰는지 그 인과 관계를 보여줍니다 [1, 3, 4]. 이를 통해 개발자는 런타임 성능을 저하시키는 가장 무거운 스택이나 불필요한 자바스크립트 함수 호출 과정을 추적할 수 있습니다 [2, 5]. @@ -20,11 +20,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Call Stack" - **정책 변화:** AI 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Chrome DevTools]], [[Flame Chart]], [[Performance Panel]] -- **Projects/Contexts:** [[Analyze runtime performance]] +- **Related Topics:** [[Chrome DevTools|Chrome DevTools]], [[Flame Chart|Flame Chart]], [[Performance Panel|Performance Panel]] +- **Projects/Contexts:** [[Analyze runtime performance|Analyze runtime performance]] - **Contradictions/Notes:** 소스에 제공된 콜 스택 관련 내용은 일반적인 프로그래밍 이론보다는 전적으로 Chrome DevTools의 런타임 성능 분석(Performance panel) 맥락에서만 설명되어 있습니다. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Call Stack.md]] +- Raw Source: 00_Raw/2026-04-20/Call Stack.md --- diff --git a/01_Archive/2026-04-20/Causal Loop Diagramming.md b/01_Archive/2026-04-20/Causal Loop Diagramming.md index e3ddd9b6..2eaf62b5 100644 --- a/01_Archive/2026-04-20/Causal Loop Diagramming.md +++ b/01_Archive/2026-04-20/Causal Loop Diagramming.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-658665 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Causal Loop Diagramming" --- -# [[Causal Loop Diagramming]] +# [[Causal Loop Diagramming|Causal Loop Diagramming]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Causal Loop Diagramming" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Causal Loop Diagramming.md]] +- Raw Source: 00_Raw/2026-04-20/Causal Loop Diagramming.md --- diff --git a/01_Archive/2026-04-20/Causal Tracing (인과적 추적).md b/01_Archive/2026-04-20/Causal Tracing (인과적 추적).md index 3aa740cf..a205f12f 100644 --- a/01_Archive/2026-04-20/Causal Tracing (인과적 추적).md +++ b/01_Archive/2026-04-20/Causal Tracing (인과적 추적).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-BFC9FF -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Causal Tracing (인과적 추적)" --- -# [[Causal Tracing (인과적 추적)]] +# [[Causal Tracing (인과적 추적)|Causal Tracing (인과적 추적)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Causal Tracing (인과적 추 ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Causal Tracing (인과적 추적).md]] +- Raw Source: 00_Raw/2026-04-20/Causal Tracing (인과적 추적).md --- diff --git a/01_Archive/2026-04-20/Cel-Shading-Techniques.md b/01_Archive/2026-04-20/Cel-Shading-Techniques.md index 838bf8df..c63efeb2 100644 --- a/01_Archive/2026-04-20/Cel-Shading-Techniques.md +++ b/01_Archive/2026-04-20/Cel-Shading-Techniques.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-6E2113 -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Cel-Shading-Techniques" --- -# [[Cel-Shading-Techniques]] +# [[Cel-Shading-Techniques|Cel-Shading-Techniques]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Cel-Shading-Techniques" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Cel-Shading-Techniques.md]] +- Raw Source: 00_Raw/2026-04-20/Cel-Shading-Techniques.md --- diff --git a/01_Archive/2026-04-20/Cellular Automata.md b/01_Archive/2026-04-20/Cellular Automata.md index 5765d0e0..b796e40c 100644 --- a/01_Archive/2026-04-20/Cellular Automata.md +++ b/01_Archive/2026-04-20/Cellular Automata.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-5EDE2E -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Cellular Automata" --- -# [[Cellular Automata]] +# [[Cellular Automata|Cellular Automata]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Cellular Automata" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Cellular Automata.md]] +- Raw Source: 00_Raw/2026-04-20/Cellular Automata.md --- diff --git a/01_Archive/2026-04-20/Cellular-Automata.md b/01_Archive/2026-04-20/Cellular-Automata.md index 6402a384..4c27e58e 100644 --- a/01_Archive/2026-04-20/Cellular-Automata.md +++ b/01_Archive/2026-04-20/Cellular-Automata.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-D84732 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Cellular-Automata" --- -# [[Cellular-Automata]] +# [[Cellular-Automata|Cellular-Automata]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Cellular-Automata" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Cellular-Automata.md]] +- Raw Source: 00_Raw/2026-04-20/Cellular-Automata.md --- diff --git a/01_Archive/2026-04-20/Central-Pattern-Generators.md b/01_Archive/2026-04-20/Central-Pattern-Generators.md index cb7e15b1..77aa1675 100644 --- a/01_Archive/2026-04-20/Central-Pattern-Generators.md +++ b/01_Archive/2026-04-20/Central-Pattern-Generators.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-FC5C34 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Central-Pattern-Generators" --- -# [[Central-Pattern-Generators]] +# [[Central-Pattern-Generators|Central-Pattern-Generators]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Central-Pattern-Generators" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Central-Pattern-Generators.md]] +- Raw Source: 00_Raw/2026-04-20/Central-Pattern-Generators.md --- diff --git a/01_Archive/2026-04-20/Cesium.md b/01_Archive/2026-04-20/Cesium.md index 39c672d8..ca07f108 100644 --- a/01_Archive/2026-04-20/Cesium.md +++ b/01_Archive/2026-04-20/Cesium.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-8A58ED -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Cesium" --- -# [[Cesium]] +# [[Cesium|Cesium]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 소스에 관련 정보가 부족합니다. 제공된 문서에서 Cesium은 3D 렌더링 중 메쉬 배칭(Mesh batching) 기능인 `Batched3DModel`을 지원하는 환경으로 매우 짧게 언급되며, 주로 Three.js의 `BatchedMesh` 성능과 비교하기 위한 대조군으로 등장합니다 [1, 2]. @@ -24,11 +24,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Cesium" - **정책 변화:** Graphics & Performance 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Batched3DModel]], [[BatchedMesh]] -- **Projects/Contexts:** [[Three.js BatchedMesh 성능 이슈 비교]] +- **Related Topics:** Batched3DModel, [[BatchedMesh|BatchedMesh]] +- **Projects/Contexts:** Three.js BatchedMesh 성능 이슈 비교 - **Contradictions/Notes:** 소스에 관련 정보가 부족합니다. 작성자는 Cesium의 배칭과 Three.js의 `BatchedMesh`가 매우 유사할 것이라고 추측하지만 [1, 2], 실제로 두 기술 간의 구체적인 아키텍처 차이나 성능 차이의 근본적 원인을 설명하는 기술적 정보는 소스에 존재하지 않습니다. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Cesium.md]] +- Raw Source: 00_Raw/2026-04-20/Cesium.md --- diff --git a/01_Archive/2026-04-20/CesiumJS.md b/01_Archive/2026-04-20/CesiumJS.md index 07d94958..424e76eb 100644 --- a/01_Archive/2026-04-20/CesiumJS.md +++ b/01_Archive/2026-04-20/CesiumJS.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-39CDC5 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - CesiumJS" --- -# [[CesiumJS]] +# [[CesiumJS|CesiumJS]] ## 📌 한 줄 통찰 (The Karpathy Summary) > CesiumJS는 웹을 위한 오픈 소스 3D 시각화 엔진으로, 주로 대규모 지형 공간 데이터의 시각화를 선도하는 기술입니다 [1, 2]. 3D 타일(3D Tiles), 지형(terrain), 위성 이미지 등 방대한 양의 3D 콘텐츠를 스트리밍하고 렌더링하는 데 활용됩니다 [1, 2]. 지표면에서 우주 공간에 이르는 거대한 가상 세계를 효율적으로 처리하기 위해 z-파이팅(z-fighting)을 방지하는 다중 절두체(multiple frustums) 및 명시적 렌더링(explicit rendering)과 같은 독자적인 WebGL 렌더링 파이프라인을 구축하고 있습니다 [3, 4]. @@ -15,7 +15,7 @@ github_commit: "[P-Reinforce] Continuous Worker - CesiumJS" ## 📖 구조화된 지식 (Synthesized Content) - **렌더링 파이프라인 및 다중 절두체 (Multiple Frustums):** CesiumJS는 다양한 광원을 처리하는 씬이 드물기 때문에 전통적인 포워드 셰이딩(forward-shading) 파이프라인을 사용합니다 [4]. 특히 거대한 가시거리를 지원하면서 멀리 있는 객체 간의 z-파이팅(z-fighting) 아티팩트를 피하기 위해 뷰 볼륨을 여러 개의 절두체로 분할하여 관리하는 독특한 방식을 사용합니다 [3, 4]. 가장 먼 절두체부터 시작하여 매번 깊이 버퍼를 지우면서 순차적으로 명령을 실행합니다 [5]. - **Scene.render와 Primitive 관리:** 프레임 렌더링의 핵심인 `Scene.render`는 애니메이션, 업데이트, 렌더링의 파이프라인을 관리합니다 [4, 6]. 업데이트 단계에서 씬의 기본 요소(Primitive, 예: 지형과 이미지를 처리하는 Globe 엔진)들이 WebGL 리소스를 생성하거나 업데이트하고, `DrawCommand` 객체 목록을 반환합니다 [7, 8]. 이 중 가시성 테스트를 통과한 '잠재적 가시 집합(Potentially Visible Set)'만이 파이프라인을 따라 렌더링됩니다 [8]. -- **투명도 처리 (OIT) 및 정렬:** 절두체 내에서 불투명(opaque) 명령을 먼저 실행한 후 반투명(translucent) 명령을 실행합니다 [5]. 하드웨어가 부동 소수점 텍스처를 지원하는 경우, 순서 비의존 투명도([[Order-Independent Transparency (OIT)]]) 기법을 적용하여 겹치는 반투명 객체의 시각적 품질을 높이고 CPU 정렬 오버헤드를 방지합니다 [5]. +- **투명도 처리 (OIT) 및 정렬:** 절두체 내에서 불투명(opaque) 명령을 먼저 실행한 후 반투명(translucent) 명령을 실행합니다 [5]. 하드웨어가 부동 소수점 텍스처를 지원하는 경우, 순서 비의존 투명도(Order-Independent Transparency (OIT)) 기법을 적용하여 겹치는 반투명 객체의 시각적 품질을 높이고 CPU 정렬 오버헤드를 방지합니다 [5]. - **명시적 렌더링 (Explicit Rendering / requestRenderMode):** 지속적으로 프레임을 렌더링하는 대신, 성능을 최적화하기 위해 `requestRenderMode` 기능을 지원합니다 [9]. 이 모드가 활성화되면 카메라 이동, 시뮬레이션 시간 변경, 또는 새로운 데이터(3D 타일 등)가 로드될 때만 명시적으로 새 프레임을 렌더링합니다 [9, 10]. 이를 통해 유휴 상태(idle)에서 CPU 사용률을 25.1%에서 3.0% 수준으로 크게 절약할 수 있습니다 [10, 11]. - **가우시안 스플래팅(Gaussian Splatting) 이슈:** 최근 가우시안 스플랫 렌더링 시 대규모 데이터셋 처리 과정에서 여러 프레임에 걸친 깊이 정렬 수행 중 프로미스 간섭(promise interference)으로 인한 WebGL 오류와 미세 지연(micro-stuttering) 현상이 보고된 바 있습니다 [12-14]. 여러 개의 프로미스 체인이 중첩되면서 정렬 결과를 오염시켜 모델이 깜빡이거나 사라지는 문제를 유발합니다 [12, 14]. @@ -24,11 +24,11 @@ github_commit: "[P-Reinforce] Continuous Worker - CesiumJS" - **정책 변화:** AI 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[WebGL]], [[3D Tiles]], [[Order-Independent Transparency (OIT)]], [[Gaussian Splatting]], [[Multiple Frustums]] -- **Projects/Contexts:** [[Geospatial Visualization]], [[requestRenderMode]] +- **Related Topics:** [[WebGL|WebGL]], 3D Tiles, Order-Independent Transparency (OIT), Gaussian Splatting, Multiple Frustums +- **Projects/Contexts:** Geospatial Visualization, requestRenderMode - **Contradictions/Notes:** 소스에 따르면, Cesium팀은 엔진을 지속적으로 최적화하고 있음에도 불구하고 OIT 및 지형 깊이 버퍼를 위한 전체 화면 패스(fullscreen passes) 기능이 추가되면서 채우기 속도(fillrate)가 제한된 환경에서는 구버전(예: 1.1)에 비해 최신 버전(예: 1.10)의 평균 프레임 속도(FPS)가 오히려 감소하는 사례가 보고되기도 했습니다 [15, 16]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/CesiumJS.md]] +- Raw Source: 00_Raw/2026-04-20/CesiumJS.md --- diff --git a/01_Archive/2026-04-20/Chain-of-Thought (CoT 사고 사슬).md b/01_Archive/2026-04-20/Chain-of-Thought (CoT 사고 사슬).md index 35e3193e..4216e634 100644 --- a/01_Archive/2026-04-20/Chain-of-Thought (CoT 사고 사슬).md +++ b/01_Archive/2026-04-20/Chain-of-Thought (CoT 사고 사슬).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-550B46 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Chain-of-Thought (CoT 사고 사슬)" --- -# [[Chain-of-Thought (CoT 사고 사슬)]] +# [[Chain-of-Thought (CoT 사고 사슬)|Chain-of-Thought (CoT 사고 사슬)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Chain-of-Thought (CoT 사고 ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Chain-of-Thought (CoT, 사고 사슬).md]] +- Raw Source: 00_Raw/2026-04-20/Chain-of-Thought (CoT, 사고 사슬).md --- diff --git a/01_Archive/2026-04-20/Chain-of-Thought (CoT, 사고 사슬).md b/01_Archive/2026-04-20/Chain-of-Thought (CoT, 사고 사슬).md index f667a50b..26bc222d 100644 --- a/01_Archive/2026-04-20/Chain-of-Thought (CoT, 사고 사슬).md +++ b/01_Archive/2026-04-20/Chain-of-Thought (CoT, 사고 사슬).md @@ -1,4 +1,4 @@ -[[Chain-of-Thought (CoT, 사고 사슬 프롬프팅)]] +Chain-of-Thought (CoT, 사고 사슬 프롬프팅) 📌 Brief Summary @@ -85,8 +85,8 @@ Chain-of-Thought(CoT)는 LLM에게 최종 답을 바로 출력하는 대신 중 🔗 Knowledge Connections -- **Related Topics:** [[GRPO (Group Relative Policy Optimization)]], [[강화학습 (Reinforcement Learning)]], [[Multi-Hop Reasoning (다중 홉 추론)]], [[LLM Hallucination (언어 모델 환각)]], [[RAG (검색 증강 생성)]], [[GraphRAG (그래프 기반 검색 증강 생성)]], [[SFT (Supervised Fine-Tuning)]] -- **Projects/Contexts:** [[AI 추론 시스템]] +- **Related Topics:** [[GRPO (Group Relative Policy Optimization)|GRPO (Group Relative Policy Optimization)]], [[강화학습 (Reinforcement Learning)|강화학습 (Reinforcement Learning)]], [[Multi-Hop Reasoning (다중 홉 추론)|Multi-Hop Reasoning (다중 홉 추론)]], [[LLM Hallucination (언어 모델 환각)|LLM Hallucination (언어 모델 환각)]], [[RAG (검색 증강 생성)|RAG (검색 증강 생성)]], [[GraphRAG (그래프 기반 검색 증강 생성)|GraphRAG (그래프 기반 검색 증강 생성)]], [[SFT (Supervised Fine-Tuning)|SFT (Supervised Fine-Tuning)]] +- **Projects/Contexts:** AI 추론 시스템 - **Contradictions/Notes:** - CoT는 추론 토큰 수를 크게 늘림 → 추론 비용·지연 증가 → 실시간 시스템에서 트레이드오프. - Self-Consistency (다수결 CoT)는 정확도↑이지만 비용 G배 증가 → 배포 환경에서 신중히 선택. diff --git a/01_Archive/2026-04-20/Chaos Theory.md b/01_Archive/2026-04-20/Chaos Theory.md index 102eff6e..2f0e1760 100644 --- a/01_Archive/2026-04-20/Chaos Theory.md +++ b/01_Archive/2026-04-20/Chaos Theory.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-1F2821 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Chaos Theory" --- -# [[Chaos Theory]] +# [[Chaos Theory|Chaos Theory]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Chaos Theory" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Chaos Theory.md]] +- Raw Source: 00_Raw/2026-04-20/Chaos Theory.md --- diff --git a/01_Archive/2026-04-20/Chaos-Theory.md b/01_Archive/2026-04-20/Chaos-Theory.md index efb7ed05..629f8e7b 100644 --- a/01_Archive/2026-04-20/Chaos-Theory.md +++ b/01_Archive/2026-04-20/Chaos-Theory.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-639E39 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Chaos-Theory" --- -# [[Chaos-Theory]] +# [[Chaos-Theory|Chaos-Theory]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Chaos-Theory" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Chaos-Theory.md]] +- Raw Source: 00_Raw/2026-04-20/Chaos-Theory.md --- diff --git a/01_Archive/2026-04-20/Cheney's Algorithm.md b/01_Archive/2026-04-20/Cheney's Algorithm.md index 94434aec..0c00314a 100644 --- a/01_Archive/2026-04-20/Cheney's Algorithm.md +++ b/01_Archive/2026-04-20/Cheney's Algorithm.md @@ -1,4 +1,4 @@ -# [[Cheney's Algorithm]] +# [[Cheney's Algorithm|Cheney's Algorithm]] ## 📌 Brief Summary Cheney's Algorithm은 V8 자바스크립트 엔진의 마이너 가비지 컬렉터인 스캐빈저(Scavenger)에서 메모리를 관리하기 위해 사용하는 가비지 컬렉션 알고리즘입니다 [1, 2]. 이 알고리즘은 메모리의 '새로운 공간(New-space)'을 동일한 크기를 가진 'from-space'와 'to-space'라는 두 개의 반공간(Semi-space)으로 나누어 작동합니다 [1, 2]. 살아있는 객체만을 from-space에서 to-space로 복사하고 압축(compact)함으로써, 빠른 메모리 할당과 캐시 지역성 향상을 달성합니다 [1]. @@ -17,8 +17,8 @@ Cheney's Algorithm은 V8 자바스크립트 엔진의 마이너 가비지 컬렉 - **종료 조건 및 가비지 처리**: `scanPtr`가 `allocationPtr`에 도달하여 더 이상 처리할 객체가 남지 않게 되면 알고리즘은 종료됩니다 [5]. 이 시점에 from-space에 남아있는 모든 데이터는 가비지(쓰레기)로 간주되어 메모리가 해제되거나 다른 목적으로 재사용됩니다 [5]. ## 🔗 Knowledge Connections -- **Related Topics:** [[Scavenge (Minor GC)]], [[Semi-space Design]], [[Garbage Collection]] -- **Projects/Contexts:** [[V8 JavaScript Engine]] +- **Related Topics:** Scavenge (Minor GC), Semi-space Design, [[Garbage Collection|Garbage Collection]] +- **Projects/Contexts:** [[V8 JavaScript Engine|V8 JavaScript Engine]] - **Contradictions/Notes:** 과거의 V8 버전들은 동기식(synchronous) 구조의 기본 Cheney's algorithm을 사용했으나, V8 v6.2 이후부터는 다중 코어 환경의 이점을 활용하기 위해 Halstead semispace copying collector와 유사한 방식의 병렬 스캐빈저(Parallel Scavenger) 알고리즘으로 발전하여 사용되고 있습니다 [6]. --- diff --git a/01_Archive/2026-04-20/Cheneys Algorithm.md b/01_Archive/2026-04-20/Cheneys Algorithm.md index 419a6f12..ff7051c3 100644 --- a/01_Archive/2026-04-20/Cheneys Algorithm.md +++ b/01_Archive/2026-04-20/Cheneys Algorithm.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-52B523 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Cheneys Algorithm" --- -# [[Cheneys Algorithm]] +# [[Cheneys Algorithm|Cheneys Algorithm]] ## 📌 한 줄 통찰 (The Karpathy Summary) > Cheney's Algorithm은 V8 자바스크립트 엔진의 마이너 가비지 컬렉터인 스캐빈저(Scavenger)에서 메모리를 관리하기 위해 사용하는 가비지 컬렉션 알고리즘입니다 [1, 2]. 이 알고리즘은 메모리의 '새로운 공간(New-space)'을 동일한 크기를 가진 'from-space'와 'to-space'라는 두 개의 반공간(Semi-space)으로 나누어 작동합니다 [1, 2]. 살아있는 객체만을 from-space에서 to-space로 복사하고 압축(compact)함으로써, 빠른 메모리 할당과 캐시 지역성 향상을 달성합니다 [1]. @@ -30,11 +30,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Cheneys Algorithm" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Scavenge (Minor GC)]], [[Semi-space Design]], [[Garbage Collection]] -- **Projects/Contexts:** [[V8 JavaScript Engine]] +- **Related Topics:** Scavenge (Minor GC), Semi-space Design, [[Garbage Collection|Garbage Collection]] +- **Projects/Contexts:** [[V8 JavaScript Engine|V8 JavaScript Engine]] - **Contradictions/Notes:** 과거의 V8 버전들은 동기식(synchronous) 구조의 기본 Cheney's algorithm을 사용했으나, V8 v6.2 이후부터는 다중 코어 환경의 이점을 활용하기 위해 Halstead semispace copying collector와 유사한 방식의 병렬 스캐빈저(Parallel Scavenger) 알고리즘으로 발전하여 사용되고 있습니다 [6]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Cheney's Algorithm.md]] +- Raw Source: 00_Raw/2026-04-20/Cheney's Algorithm.md --- diff --git a/01_Archive/2026-04-20/Choice Architecture in Digital UX.md b/01_Archive/2026-04-20/Choice Architecture in Digital UX.md index 84a2b818..5aa4a1aa 100644 --- a/01_Archive/2026-04-20/Choice Architecture in Digital UX.md +++ b/01_Archive/2026-04-20/Choice Architecture in Digital UX.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-BE3FDC -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Choice Architecture in Digital UX" --- -# [[Choice Architecture in Digital UX]] +# [[Choice Architecture in Digital UX|Choice Architecture in Digital UX]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Choice Architecture in Digital ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Choice Architecture in Digital UX.md]] +- Raw Source: 00_Raw/2026-04-20/Choice Architecture in Digital UX.md --- diff --git a/01_Archive/2026-04-20/Chrome (Blink_Dawn).md b/01_Archive/2026-04-20/Chrome (Blink_Dawn).md index 8974db94..5f607eaf 100644 --- a/01_Archive/2026-04-20/Chrome (Blink_Dawn).md +++ b/01_Archive/2026-04-20/Chrome (Blink_Dawn).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-3115F7 -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Chrome (Blink_Dawn)" --- -# [[Chrome (Blink_Dawn)]] +# [[Chrome (Blink_Dawn)|Chrome (Blink_Dawn)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > Chrome(Blink/Dawn)은 구글 크롬 브라우저의 핵심 엔진인 Blink와 WebGPU 백엔드인 Dawn을 지칭합니다 [1, 2]. 이들은 웹 환경에서 고성능 그래픽 및 연산 파이프라인을 처리하는 동시에, Spectre 및 Meltdown과 같은 보안 취약점을 방지하기 위해 정밀 타이머 접근을 제한하는 보안 메커니즘을 구현하고 있습니다 [1, 2]. 또한 개발자가 웹 애플리케이션의 성능 병목 현상을 식별할 수 있도록 심층적인 프로세스 트레이싱 및 프로파일링 환경을 제공합니다 [3-5]. @@ -22,11 +22,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Chrome (Blink_Dawn)" - **정책 변화:** Graphics & Performance 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[WebGPU]], [[Timestamp Queries]], [[Spectre and Meltdown]] -- **Projects/Contexts:** [[Chrome DevTools]], [[about:tracing]] +- **Related Topics:** [[WebGPU|WebGPU]], [[Timestamp Queries|Timestamp Queries]], [[Spectre and Meltdown|Spectre and Meltdown]] +- **Projects/Contexts:** [[Chrome DevTools|Chrome DevTools]], about:tracing - **Contradictions/Notes:** 타임스탬프 쿼리 해상도와 관련하여 초기에는 격리된 컨텍스트(isolated contexts) 여부에 따라 다르게 노출되는 방안이 논의되었으나, 향후 W3C의 High Resolution Time 사양과 일치시켜 사이트 격리 여부와 관계없이 100 마이크로초(100us) 해상도를 허용하는 방향으로 GPU for the Web Community Group에서 합의를 이루었습니다 [6, 12, 13]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Chrome (Blink_Dawn).md]] +- Raw Source: 00_Raw/2026-04-20/Chrome (Blink_Dawn).md --- diff --git a/01_Archive/2026-04-20/Chrome DevTools Memory Panel.md b/01_Archive/2026-04-20/Chrome DevTools Memory Panel.md index de3005cc..d42ea8ea 100644 --- a/01_Archive/2026-04-20/Chrome DevTools Memory Panel.md +++ b/01_Archive/2026-04-20/Chrome DevTools Memory Panel.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-5AE3F9 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Chrome DevTools Memory Panel" --- -# [[Chrome DevTools Memory Panel]] +# [[Chrome DevTools Memory Panel|Chrome DevTools Memory Panel]] ## 📌 한 줄 통찰 (The Karpathy Summary) > Chrome DevTools Memory Panel은 자바스크립트 애플리케이션 및 Node.js 환경에서 힙(Heap) 메모리를 프로파일링하여 메모리 누수를 진단하고 메모리 분포를 분석하는 도구입니다 [1-3]. 이 패널은 주로 힙 스냅샷(Heap snapshot), 타임라인의 할당 계측(Allocation instrumentation on timeline), 할당 샘플링(Allocation sampling)이라는 세 가지 핵심 기능을 제공합니다 [2, 4]. 개발자는 이 패널을 활용해 가비지 컬렉션(GC) 이후에도 메모리에 남아 있는 객체의 참조 체인을 역추적하고 근본 원인을 파악할 수 있습니다 [1, 2, 5, 6]. @@ -30,13 +30,13 @@ github_commit: "[P-Reinforce] Continuous Worker - Chrome DevTools Memory Panel" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Heap Snapshot]], [[Garbage Collection]], [[Memory Leak]], [[Retaining Path]] -- **Projects/Contexts:** [[V8 Engine]], [[Node.js]] +- **Related Topics:** [[Heap Snapshot|Heap Snapshot]], [[Garbage Collection|Garbage Collection]], [[Memory Leak|Memory Leak]], [[Retaining Path|Retaining Path]] +- **Projects/Contexts:** [[V8 Engine|V8 Engine]], [[Node.js|Node.js]] - **Contradictions/Notes:** - 스냅샷 상에서 메모리 그래프가 증가한다고 해서 무조건 누수(Leak)인 것은 아닙니다. 캐시(Caches), 실행 취소 기록(Undo histories), 가상화된 리스트 버퍼 등은 의도적으로 데이터를 보존하기 때문입니다. 의도된 보존과 우발적인 메모리 누수를 구별하는 것이 중요합니다 [20]. - DevTools 콘솔에서 `console.log`로 출력된 객체는 콘솔에서 도달 가능하기 때문에 참조가 유지되어 메모리 누수로 나타날 수 있습니다. 누수 조사 중에는 콘솔을 지우거나 큰 객체를 로깅하지 않아야 합니다 [20]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Chrome DevTools Memory Panel.md]] +- Raw Source: 00_Raw/2026-04-20/Chrome DevTools Memory Panel.md --- diff --git a/01_Archive/2026-04-20/Chrome DevTools Memory Profiling.md b/01_Archive/2026-04-20/Chrome DevTools Memory Profiling.md index 16163032..2e5235ef 100644 --- a/01_Archive/2026-04-20/Chrome DevTools Memory Profiling.md +++ b/01_Archive/2026-04-20/Chrome DevTools Memory Profiling.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-B1B522 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Chrome DevTools Memory Profiling" --- -# [[Chrome DevTools Memory Profiling]] +# [[Chrome DevTools Memory Profiling|Chrome DevTools Memory Profiling]] ## 📌 한 줄 통찰 (The Karpathy Summary) > Chrome DevTools Memory Profiling은 JavaScript 애플리케이션 및 브라우저에서 발생하는 메모리 누수를 감지하고 분석하기 위한 분석 도구 모음입니다 [1, 2]. 주로 DevTools의 Memory 패널을 통해 제공되며, 객체의 메모리 할당 시점, 유지(Retaining) 경로, 가비지 컬렉션 여부를 시각적으로 추적하여 정상적으로 정리되지 않은 객체를 식별합니다 [3-6]. 이를 통해 개발자는 메모리 힙(Heap) 상태를 정밀하게 분석하고 메모리 부족 현상이나 성능 저하를 유발하는 코드의 근본 원인을 파악할 수 있습니다 [7-9]. @@ -33,11 +33,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Chrome DevTools Memory Profili - **정책 변화:** AI 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Heap Snapshot]], [[Allocation Timeline]], [[Garbage Collection]], [[Retaining Path]], [[Shallow Size and Retained Size]] -- **Projects/Contexts:** [[V8 Engine Memory Management]], [[Browser Memory Leak Detection]] +- **Related Topics:** [[Heap Snapshot|Heap Snapshot]], [[Allocation Timeline|Allocation Timeline]], [[Garbage Collection|Garbage Collection]], [[Retaining Path|Retaining Path]], Shallow Size and Retained Size +- **Projects/Contexts:** V8 Engine Memory Management, [[브라우저 메모리 누수 탐지(Browser Memory Leak Detection)|Browser Memory Leak Detection]] - **Contradictions/Notes:** 소스 간의 직접적인 모순은 없습니다. 다만, 실무적 주의사항으로 `console.log`가 평가된 객체에 대한 참조를 계속 유지하여 가짜 양성(false positive)의 메모리 누수를 표시할 수 있으므로, 메모리 누수 조사 중에는 콘솔을 지우거나 큰 객체 기록을 피해야 한다고 경고하고 있습니다 [21, 25]. 또한 코드의 난독화(Minified code) 때문에 Retainer 체인을 읽기 어려울 수 있으므로, 의미 있는 함수/변수 명을 보려면 소스 맵(Source maps)을 활성화해야 합니다 [25]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Chrome DevTools Memory Profiling.md]] +- Raw Source: 00_Raw/2026-04-20/Chrome DevTools Memory Profiling.md --- diff --git a/01_Archive/2026-04-20/Chrome DevTools 메모리 분석 및 성능 최적화.md b/01_Archive/2026-04-20/Chrome DevTools 메모리 분석 및 성능 최적화.md index e1ad3672..284d0dd7 100644 --- a/01_Archive/2026-04-20/Chrome DevTools 메모리 분석 및 성능 최적화.md +++ b/01_Archive/2026-04-20/Chrome DevTools 메모리 분석 및 성능 최적화.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-9DC3E3 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Chrome DevTools 메모리 분석 및 성능 최적화" --- -# [[Chrome DevTools 메모리 분석 및 성능 최적화]] +# [[Chrome DevTools 메모리 분석 및 성능 최적화|Chrome DevTools 메모리 분석 및 성능 최적화]] ## 📌 한 줄 통찰 (The Karpathy Summary) > Chrome DevTools는 웹 및 Node.js 애플리케이션의 메모리 누수를 감지하고 성능을 최적화하기 위한 강력한 메모리 분석 도구를 제공한다 [1, 2]. 핵심 기능으로는 특정 시점의 메모리 상태를 캡처하는 힙 스냅샷(Heap snapshot), 시간에 따른 객체 할당을 추적하는 할당 타임라인(Allocation timeline), 그리고 통계적 샘플링 방식의 할당 샘플링(Allocation sampling)이 있다 [3, 4]. 개발자는 이러한 도구를 사용하여 가비지 컬렉션(GC) 이후에도 메모리에 남아있는 객체와 그 참조 경로(Retaining path)를 식별함으로써, 메모리 누수와 성능 저하의 근본 원인을 파악하고 코드를 최적화할 수 있다 [1, 3, 5, 6]. @@ -20,11 +20,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Chrome DevTools 메모리 분 - **정책 변화:** AI 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[가비지 컬렉션(Garbage Collection)]], [[V8 JavaScript Engine]], [[힙 메모리(Heap Memory)]], [[메모리 누수(Memory Leak)]], [[Retainers(유지 경로)]] -- **Projects/Contexts:** [[Node.js 프로덕션 메모리 병목 분석]], [[SPA 라우트 전환 성능 최적화]] +- **Related Topics:** [[가비지 컬렉션(Garbage Collection)|가비지 컬렉션(Garbage Collection)]], [[V8 JavaScript Engine|V8 JavaScript Engine]], [[힙 메모리(Heap Memory)|힙 메모리(Heap Memory)]], [[메모리 누수(Memory Leak)|메모리 누수(Memory Leak)]], [[Retainers(유지 경로)|Retainers(유지 경로)]] +- **Projects/Contexts:** [[Node.js 프로덕션 메모리 병목 분석|Node.js 프로덕션 메모리 병목 분석]], [[SPA 라우트 전환 성능 최적화|SPA 라우트 전환 성능 최적화]] - **Contradictions/Notes:** DevTools의 콘솔(Console)에 `console.log`를 통해 출력된 객체는 콘솔에 의해 지속적으로 참조가 유지되므로 가비지 컬렉션의 대상이 되지 않는다. 따라서 메모리 누수를 정확히 조사할 때는 대형 객체의 로깅을 피하거나 콘솔을 비워야 한다 [18]. 더불어, 원시 데이터인 숫자(Number)와 같은 비문자열 값은 캡처되지 않으며, 원시 힙 데이터에는 수많은 V8 내부 객체도 포함되어 있어 분석 시 "Constructor" 필터를 적용해 애플리케이션 객체에만 집중하는 것이 좋다 [9, 18]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Chrome DevTools 메모리 분석 및 성능 최적화.md]] +- Raw Source: 00_Raw/2026-04-20/Chrome DevTools 메모리 분석 및 성능 최적화.md --- diff --git a/01_Archive/2026-04-20/Chrome DevTools 메모리 프로파일링 및 힙 스냅샷 분석.md b/01_Archive/2026-04-20/Chrome DevTools 메모리 프로파일링 및 힙 스냅샷 분석.md index b8d226d8..d883d179 100644 --- a/01_Archive/2026-04-20/Chrome DevTools 메모리 프로파일링 및 힙 스냅샷 분석.md +++ b/01_Archive/2026-04-20/Chrome DevTools 메모리 프로파일링 및 힙 스냅샷 분석.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-EF52CE -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Chrome DevTools 메모리 프로파일링 및 힙 스냅샷 분석" --- -# [[Chrome DevTools 메모리 프로파일링 및 힙 스냅샷 분석]] +# [[Chrome DevTools 메모리 프로파일링 및 힙 스냅샷 분석|Chrome DevTools 메모리 프로파일링 및 힙 스냅샷 분석]] ## 📌 한 줄 통찰 (The Karpathy Summary) > Chrome DevTools의 메모리 프로파일링 및 힙 스냅샷 분석은 웹 애플리케이션 및 Node.js 환경에서 발생하는 메모리 누수를 찾아내고 객체의 보존 상태를 파악하는 데 사용되는 핵심 디버깅 기법입니다. 메모리 패널은 전체 객체 그래프를 캡처하는 힙 스냅샷, 시간에 따른 할당을 추적하는 타임라인 계측, 그리고 프로덕션에 적합한 샘플링 도구를 제공합니다. 개발자는 이러한 도구와 객체의 참조 체인(Retaining path)을 분석하여 가비지 컬렉터(GC)에 의해 해제되어야 할 객체가 왜 메모리에 남아있는지 근본 원인을 파악할 수 있습니다. @@ -44,11 +44,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Chrome DevTools 메모리 프 - **정책 변화:** AI 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[메모리 누수(Memory Leaks)]], [[가비지 컬렉션(Garbage Collection)]], [[V8 엔진 메모리 구조]], [[객체 참조 체인(Retainers)]] -- **Projects/Contexts:** [[Node.js 프로덕션 메모리 문제 해결]], [[웹 프론트엔드 성능 최적화]] +- **Related Topics:** [[메모리 누수(Memory Leaks)|메모리 누수(Memory Leaks)]], [[가비지 컬렉션(Garbage Collection)|가비지 컬렉션(Garbage Collection)]], [[V8 엔진 메모리 구조|V8 엔진 메모리 구조]], 객체 참조 체인(Retainers) +- **Projects/Contexts:** [[Node.js 프로덕션 메모리 문제 해결|Node.js 프로덕션 메모리 문제 해결]], [[웹 프론트엔드 성능 최적화|웹 프론트엔드 성능 최적화]] - **Contradictions/Notes:** 단순히 메모리 그래프가 상승한다고 해서 모두 우발적인 메모리 누수인 것은 아닙니다. 애플리케이션의 캐시(Caches)나 실행 취소 기록(Undo histories) 등은 의도적으로 데이터를 보존하도록 설계되었으므로, 이러한 '의도된 보존'과 '우발적인 보존(누수)'을 명확하게 구분해야 합니다 [18]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Chrome DevTools 메모리 프로파일링 및 힙 스냅샷 분석.md]] +- Raw Source: 00_Raw/2026-04-20/Chrome DevTools 메모리 프로파일링 및 힙 스냅샷 분석.md --- diff --git a/01_Archive/2026-04-20/Chrome DevTools 메모리 프로파일링.md b/01_Archive/2026-04-20/Chrome DevTools 메모리 프로파일링.md index 56bd3dca..044d677e 100644 --- a/01_Archive/2026-04-20/Chrome DevTools 메모리 프로파일링.md +++ b/01_Archive/2026-04-20/Chrome DevTools 메모리 프로파일링.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-8471ED -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Chrome DevTools 메모리 프로파일링" --- -# [[Chrome DevTools 메모리 프로파일링]] +# [[Chrome DevTools 메모리 프로파일링|Chrome DevTools 메모리 프로파일링]] ## 📌 한 줄 통찰 (The Karpathy Summary) > Chrome DevTools 메모리 프로파일링은 개발자가 힙(Heap) 스냅샷을 캡처하고 시간에 따른 메모리 할당을 추적하여 브라우저 환경에서 발생하는 메모리 누수를 감지하고 분석하는 과정입니다 [1-4]. 이는 JavaScript 객체와 DOM 노드의 메모리 분포를 보여주며, 가비지 컬렉션(GC) 이후에도 불필요하게 남아있는 객체의 참조 경로(Retaining Path)를 시각적으로 파악할 수 있도록 돕습니다 [1, 4-6]. 이를 통해 브라우저 메모리 할당 시점별 힙의 상세한 동작과 메모리 보존(Retention) 원인을 명확히 식별할 수 있습니다 [2, 7]. @@ -23,11 +23,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Chrome DevTools 메모리 프 - **정책 변화:** AI 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[힙 스냅샷(Heap Snapshot)]], [[타임라인 할당 계측(Allocation instrumentation on timeline)]], [[가비지 컬렉션(Garbage Collection)]], [[보존 경로(Retaining Path)]] -- **Projects/Contexts:** [[V8 JavaScript Engine 메모리 관리 및 가비지 컬렉션]], [[브라우저 메모리 누수 탐지(Browser Memory Leak Detection)]] +- **Related Topics:** [[힙 스냅샷(Heap Snapshot)|힙 스냅샷(Heap Snapshot)]], [[타임라인 할당 계측(Allocation instrumentation on timeline)|타임라인 할당 계측(Allocation instrumentation on timeline)]], [[가비지 컬렉션(Garbage Collection)|가비지 컬렉션(Garbage Collection)]], [[보존 경로(Retaining Path)|보존 경로(Retaining Path)]] +- **Projects/Contexts:** [[V8 JavaScript Engine 메모리 관리 및 가비지 컬렉션|V8 JavaScript Engine 메모리 관리 및 가비지 컬렉션]], [[브라우저 메모리 누수 탐지(Browser Memory Leak Detection)|브라우저 메모리 누수 탐지(Browser Memory Leak Detection)]] - **Contradictions/Notes:** 소스의 메모리 누수 분석 시 주의사항에 따르면, DevTools 콘솔에서의 `console.log` 출력은 로깅된 객체에 대한 참조를 계속 유지하므로 실제로는 누수가 아니더라도 가비지 컬렉션이 되지 않아 조사 과정에서 혼선을 줄 수 있습니다 [20]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Chrome DevTools 메모리 프로파일링.md]] +- Raw Source: 00_Raw/2026-04-20/Chrome DevTools 메모리 프로파일링.md --- diff --git a/01_Archive/2026-04-20/Chrome DevTools(크롬 개발자 도구).md b/01_Archive/2026-04-20/Chrome DevTools(크롬 개발자 도구).md index 199cbfe0..8a3dfb8a 100644 --- a/01_Archive/2026-04-20/Chrome DevTools(크롬 개발자 도구).md +++ b/01_Archive/2026-04-20/Chrome DevTools(크롬 개발자 도구).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-663B99 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Chrome DevTools(크롬 개발자 도구)" --- -# [[Chrome DevTools(크롬 개발자 도구)]] +# [[Chrome DevTools(크롬 개발자 도구)|Chrome DevTools(크롬 개발자 도구)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > Chrome DevTools(크롬 개발자 도구)는 JavaScript 애플리케이션 및 브라우저 환경에서 메모리 누수를 탐지하고 성능을 분석하기 위해 다양한 프로파일링 도구를 제공하는 개발자용 인터페이스입니다 [1-3]. 주로 메모리 패널(Memory panel)을 통해 힙 스냅샷을 캡처하거나 시간에 따른 메모리 할당을 추적하여, 가비지 컬렉터(GC)에 의해 해제되지 않은 객체와 그 참조 원인을 식별하는 데 사용됩니다 [1, 4, 5]. @@ -26,11 +26,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Chrome DevTools(크롬 개발 - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Memory Leak(메모리 누수)]], [[Garbage Collection(가비지 컬렉션)]], [[Heap Snapshot(힙 스냅샷)]], [[Allocation Timeline(할당 타임라인)]] -- **Projects/Contexts:** [[Node.js 프로세스 모니터링 및 메모리 분석]], [[브라우저 DOM 누수 탐지 및 렌더링 최적화]] +- **Related Topics:** [[Memory Leak(메모리 누수)|Memory Leak(메모리 누수)]], [[Garbage Collection(가비지 컬렉션)|Garbage Collection(가비지 컬렉션)]], [[Heap Snapshot(힙 스냅샷)|Heap Snapshot(힙 스냅샷)]], [[Allocation Timeline(할당 타임라인)|Allocation Timeline(할당 타임라인)]] +- **Projects/Contexts:** [[Node.js 프로세스 모니터링 및 메모리 분석|Node.js 프로세스 모니터링 및 메모리 분석]], [[브라우저 DOM 누수 탐지 및 렌더링 최적화|브라우저 DOM 누수 탐지 및 렌더링 최적화]] - **Contradictions/Notes:** 소스에 관련 정보가 부족합니다. (제공된 소스 내에서 Chrome DevTools의 기능이나 메모리 분석 방법론에 대해 상충되는 주장은 발견되지 않았습니다.) --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Chrome DevTools(크롬 개발자 도구).md]] +- Raw Source: 00_Raw/2026-04-20/Chrome DevTools(크롬 개발자 도구).md --- diff --git a/01_Archive/2026-04-20/Chrome DevTools.md b/01_Archive/2026-04-20/Chrome DevTools.md index de08af47..0f45594e 100644 --- a/01_Archive/2026-04-20/Chrome DevTools.md +++ b/01_Archive/2026-04-20/Chrome DevTools.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-6965B5 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Chrome DevTools" --- -# [[Chrome DevTools]] +# [[Chrome DevTools|Chrome DevTools]] ## 📌 한 줄 통찰 (The Karpathy Summary) > Chrome DevTools는 웹 성능 분석 및 메모리 누수 진단을 수행할 수 있는 브라우저 내장 개발자 도구이다 [1]. 이 도구의 메모리(Memory) 패널은 힙 스냅샷 캡처와 할당 타임라인 기록 기능을 제공하여 객체의 참조 상태와 메모리 상태를 추적할 수 있도록 돕는다 [1-3]. 개발자는 이를 통해 가비지 컬렉션(GC) 이후에도 살아남아 메모리를 점유하고 있는 객체들을 식별하고 분석할 수 있다 [4-6]. @@ -40,11 +40,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Chrome DevTools" - **정책 변화:** AI 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Heap Snapshot]], [[Allocation Timeline]], [[Garbage Collection]], [[Memory Leak]] -- **Projects/Contexts:** [[Browser Memory Leak Detection]] +- **Related Topics:** [[Heap Snapshot|Heap Snapshot]], [[Allocation Timeline|Allocation Timeline]], [[Garbage Collection|Garbage Collection]], [[Memory Leak|Memory Leak]] +- **Projects/Contexts:** [[브라우저 메모리 누수 탐지(Browser Memory Leak Detection)|Browser Memory Leak Detection]] - **Contradictions/Notes:** 가비지 컬렉션 과정에서 객체들이 이동할 수 있으므로 객체의 주소를 직접 추적하는 것은 의미가 없다. 대신 DevTools는 `@` 기호 뒤에 여러 스냅샷 간 유지되는 고유 식별자(Object ID)를 부여하여 정확하게 힙 상태와 객체를 비교할 수 있도록 한다 [2, 17, 24]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Chrome DevTools.md]] +- Raw Source: 00_Raw/2026-04-20/Chrome DevTools.md --- diff --git a/01_Archive/2026-04-20/Chrome User Experience Report (CrUX).md b/01_Archive/2026-04-20/Chrome User Experience Report (CrUX).md index f2911f70..dea26e09 100644 --- a/01_Archive/2026-04-20/Chrome User Experience Report (CrUX).md +++ b/01_Archive/2026-04-20/Chrome User Experience Report (CrUX).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-C2220F -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Chrome User Experience Report (CrUX)" --- -# [[Chrome User Experience Report (CrUX)]] +# [[Chrome User Experience Report (CrUX)|Chrome User Experience Report (CrUX)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -30,11 +30,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Chrome User Experience Report - **정책 변화:** Design & Experience 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Core Web Vitals]], [[Largest Contentful Paint (LCP)]], [[Interaction to Next Paint (INP)]], [[Real User Monitoring (RUM)]] -- **Projects/Contexts:** [[PageSpeed Insights]], [[BigQuery]], [[Chrome DevTools]] +- **Related Topics:** [[Core Web Vitals|Core Web Vitals]], [[Largest Contentful Paint (LCP)|Largest Contentful Paint (LCP)]], [[Interaction to Next Paint (INP)|Interaction to Next Paint (INP)]], [[Real User Monitoring (RUM)|Real User Monitoring (RUM)]] +- **Projects/Contexts:** [[PageSpeed Insights|PageSpeed Insights]], BigQuery, [[Chrome DevTools|Chrome DevTools]] - **Contradictions/Notes:** 소스에 따르면 CrUX는 실제 사용자 성능을 파악하는 데 매우 유용한 지표지만, 최소 트래픽 기준을 충족하지 못하는 페이지는 데이터가 수집/표시되지 않는다는 한계가 명확히 존재합니다 [6, 8]. 또한 특정 세부 데이터(LCP 하위 요소)는 PageSpeed Insights가 아닌 별도의 서드파티 도구에서만 조회 가능하다는 점을 유의해야 합니다 [9]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Chrome User Experience Report (CrUX).md]] +- Raw Source: 00_Raw/2026-04-20/Chrome User Experience Report (CrUX).md --- diff --git a/01_Archive/2026-04-20/Chrome V8 Heap Analysis.md b/01_Archive/2026-04-20/Chrome V8 Heap Analysis.md index 29ee9468..8efd7256 100644 --- a/01_Archive/2026-04-20/Chrome V8 Heap Analysis.md +++ b/01_Archive/2026-04-20/Chrome V8 Heap Analysis.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-7DF5C6 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Chrome V8 Heap Analysis" --- -# [[Chrome V8 Heap Analysis]] +# [[Chrome V8 Heap Analysis|Chrome V8 Heap Analysis]] ## 📌 한 줄 통찰 (The Karpathy Summary) > Chrome V8 엔진의 힙(Heap)은 자바스크립트 실행 중 동적으로 생성되는 객체와 데이터를 저장하는 런타임 메모리 영역입니다 [1]. V8 힙은 객체의 수명과 특성에 따라 여러 세대 공간(New Space, Old Space 등)으로 세분화되어 세대별 가비지 컬렉션(Generational Garbage Collection) 메커니즘에 의해 관리됩니다 [2-4]. 힙 메모리 분석은 메모리 누수를 진단하거나 최적화를 수행하는 데 필수적이며, V8 샌드박스를 우회하려는 악의적인 메모리 손상 익스플로잇의 흔적을 식별하는 메모리 포렌식에도 활용됩니다 [5-10]. @@ -35,11 +35,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Chrome V8 Heap Analysis" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Garbage Collection]], [[V8 Memory Cage]], [[Pointer Compression]], [[Generational Hypothesis]], [[Mark-Sweep-Compact]] -- **Projects/Contexts:** [[Orinoco Garbage Collector]], [[Chrome DevTools Memory Panel]], [[v8-forensics]] +- **Related Topics:** [[Garbage Collection|Garbage Collection]], [[V8 Memory Cage|V8 Memory Cage]], [[Pointer Compression|Pointer Compression]], [[Generational Hypothesis|Generational Hypothesis]], [[Mark-Sweep-Compact|Mark-Sweep-Compact]] +- **Projects/Contexts:** Orinoco Garbage Collector, [[Chrome DevTools Memory Panel|Chrome DevTools Memory Panel]], v8-forensics - **Contradictions/Notes:** 소스에 관련 정보가 부족합니다. (소스 간의 명백한 모순점이나 상충하는 주장은 발견되지 않았습니다.) --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Chrome V8 Heap Analysis.md]] +- Raw Source: 00_Raw/2026-04-20/Chrome V8 Heap Analysis.md --- diff --git a/01_Archive/2026-04-20/Chrome WebGPU 구현.md b/01_Archive/2026-04-20/Chrome WebGPU 구현.md index eca2fc5f..30862f96 100644 --- a/01_Archive/2026-04-20/Chrome WebGPU 구현.md +++ b/01_Archive/2026-04-20/Chrome WebGPU 구현.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-7CCB76 -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Chrome WebGPU 구현" --- -# [[Chrome WebGPU 구현]] +# [[Chrome WebGPU 구현|Chrome WebGPU 구현]] ## 📌 한 줄 통찰 (The Karpathy Summary) > Chrome은 113 버전부터 WebGPU를 기본으로 활성화하여 차세대 웹 그래픽스 및 컴퓨팅 API를 지원하기 시작했습니다 [1, 2]. Chrome의 WebGPU 구현체는 'Dawn'이라는 백엔드와 'Tint' 셰이더 컴파일러를 기반으로 작동하며, 성능 향상과 보안 강화를 위한 다양한 기능(예: 16비트 부동소수점 지원, 타임스탬프 양자화 등)을 지속적으로 업데이트하고 있습니다 [3-5]. 초기 데스크톱 지원을 시작으로 현재는 Android 환경까지 지원을 확장하여 이식성 높고 강력한 GPU 가속 환경을 제공합니다 [6]. @@ -27,11 +27,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Chrome WebGPU 구현" - **정책 변화:** Graphics & Performance 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Dawn]], [[WGSL]], [[타임스탬프 쿼리 (Timestamp Queries)]], [[f16 부동소수점]] -- **Projects/Contexts:** [[Chromium]], [[GPU for the Web Community Group]] +- **Related Topics:** Dawn, WGSL, 타임스탬프 쿼리 (Timestamp Queries), f16 부동소수점 +- **Projects/Contexts:** [[Chromium|Chromium]], [[GPU for the Web Community Group|GPU for the Web Community Group]] - **Contradictions/Notes:** 소스에 따르면 WebGPU 타임스탬프 쿼리의 노출 정책에 대한 변화가 있었습니다. 초기에는 보안 문제로 인해 "사이트 격리(Site isolation)가 된 컨텍스트에서만 100마이크로초로 노출하고 비격리 상태에서는 아예 노출하지 않는 방안"이 크롬 팀에 의해 제안되었습니다 [12]. 그러나 플랫폼 간의 상호 운용성(Interop) 문제를 지적하는 의견에 따라, 최종적으로는 격리 여부와 관계없이 고해상도 시간(hr-time) 스펙에 맞춰 일괄적으로 100마이크로초 해상도로 노출하는 것으로 합의되었습니다 [17, 18]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Chrome WebGPU 구현.md]] +- Raw Source: 00_Raw/2026-04-20/Chrome WebGPU 구현.md --- diff --git a/01_Archive/2026-04-20/Chrome _ Blink WebGPU Implementation.md b/01_Archive/2026-04-20/Chrome _ Blink WebGPU Implementation.md index ca5ae050..5712cb48 100644 --- a/01_Archive/2026-04-20/Chrome _ Blink WebGPU Implementation.md +++ b/01_Archive/2026-04-20/Chrome _ Blink WebGPU Implementation.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-4FF4D6 -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Chrome _ Blink WebGPU Implementation" --- -# [[Chrome _ Blink WebGPU Implementation]] +# [[Chrome _ Blink WebGPU Implementation|Chrome _ Blink WebGPU Implementation]] ## 📌 한 줄 통찰 (The Karpathy Summary) > Chrome과 Blink 엔진에서 WebGPU를 구현한 방식은 현대적인 GPU 파이프라인의 이점을 웹에 제공하면서도 하드웨어 보안을 유지하도록 설계되었습니다. 특히 타이밍 공격을 방지하기 위해 타임스탬프 쿼리에 양자화(Quantization)를 적용하여 해상도를 제한합니다. Chrome 백엔드 엔진인 Dawn을 기반으로 구동되며, 지속적인 업데이트(예: Chrome 120)를 통해 16비트 부동소수점 지원 및 GPU 리소스 할당 한계를 확장하여 성능과 개발자 경험을 향상시키고 있습니다. @@ -33,11 +33,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Chrome _ Blink WebGPU Implemen - **정책 변화:** Graphics & Performance 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[WebGPU Timestamp Queries]], [[Dawn]], [[Spectre and Meltdown]], [[WGSL]] -- **Projects/Contexts:** [[Chrome 120 WebGPU Updates]] +- **Related Topics:** [[WebGPU Timestamp Queries|WebGPU Timestamp Queries]], Dawn, [[Spectre and Meltdown|Spectre and Meltdown]], WGSL +- **Projects/Contexts:** Chrome 120 WebGPU Updates - **Contradictions/Notes:** 소스에 따르면, 타임스탬프 노출에 대한 초기 제안은 보안을 이유로 비격리 컨텍스트에서는 타임스탬프를 전혀 제공하지 않는 것이었으나 [5], 이후 상호 운용성(Interop) 문제를 해결하기 위해 GPU for the Web 커뮤니티 그룹의 합의를 거쳐 컨텍스트의 격리 여부와 상관없이 100 마이크로초 단위로 값을 제공하는 것으로 정책이 수정되었습니다 [6]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Chrome _ Blink WebGPU Implementation.md]] +- Raw Source: 00_Raw/2026-04-20/Chrome _ Blink WebGPU Implementation.md --- diff --git a/01_Archive/2026-04-20/Chrome 렌더러 프로세스 V8 샌드박스 보안.md b/01_Archive/2026-04-20/Chrome 렌더러 프로세스 V8 샌드박스 보안.md index d2a15fcc..b29991e3 100644 --- a/01_Archive/2026-04-20/Chrome 렌더러 프로세스 V8 샌드박스 보안.md +++ b/01_Archive/2026-04-20/Chrome 렌더러 프로세스 V8 샌드박스 보안.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-3832A0 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Chrome 렌더러 프로세스 V8 샌드박스 보안" --- -# [[Chrome 렌더러 프로세스 V8 샌드박스 보안]] +# [[Chrome 렌더러 프로세스 V8 샌드박스 보안|Chrome 렌더러 프로세스 V8 샌드박스 보안]] ## 📌 한 줄 통찰 (The Karpathy Summary) > V8 샌드박스(또는 메모리 케이지)는 Chrome 103 및 이후 이를 도입한 Electron 등에서 V8 JavaScript 엔진 내 발생하는 취약점 악용을 근본적으로 방지하기 위해 설계된 보안 기술입니다 [1, 2]. 힙 내에 실제 메모리 포인터를 저장하는 대신 예약된 메모리 영역의 기준 주소로부터의 32비트 오프셋(offset)만 저장하는 포인터 압축(Pointer Compression) 기술을 사용합니다 [2-4]. 이를 통해 공격자가 메모리 손상 버그를 악용하더라도 그 피해 및 메모리 접근 범위를 4GB 크기의 샌드박스 내부로 제한하여 프로세스 전체의 탈취를 막고 보안을 강화합니다 [2, 5]. @@ -20,11 +20,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Chrome 렌더러 프로세스 - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Pointer Compression]], [[Type Confusion]], [[ArrayBuffer]], [[Just-In-Time (JIT) Compiler]] -- **Projects/Contexts:** [[Chrome 103]], [[Electron 21]] +- **Related Topics:** [[Pointer Compression|Pointer Compression]], Type Confusion, [[ArrayBuffer|ArrayBuffer]], Just-In-Time (JIT) Compiler +- **Projects/Contexts:** Chrome 103, Electron 21 - **Contradictions/Notes:** 소스는 V8 샌드박스와 포인터 압축 기술이 보안, 성능, 메모리 사용량 측면에서 큰 이점을 제공한다고 설명하지만, 이로 인해 V8 힙의 최대 크기가 4GB로 제한되는 명확한 단점(trade-off)이 존재한다고 지적합니다 [5, 14]. 대용량 메모리가 필요한 특수한 경우, 포인터 압축을 비활성화한 사용자 지정 빌드를 사용하거나 하위 프로세스로 작업을 분리해야 할 수도 있습니다 [15]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Chrome 렌더러 프로세스 V8 샌드박스 보안.md]] +- Raw Source: 00_Raw/2026-04-20/Chrome 렌더러 프로세스 V8 샌드박스 보안.md --- diff --git a/01_Archive/2026-04-20/Chrome 브라우저 렌더링 성능.md b/01_Archive/2026-04-20/Chrome 브라우저 렌더링 성능.md index 252f4029..65674cf7 100644 --- a/01_Archive/2026-04-20/Chrome 브라우저 렌더링 성능.md +++ b/01_Archive/2026-04-20/Chrome 브라우저 렌더링 성능.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-EC1033 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Chrome 브라우저 렌더링 성능" --- -# [[Chrome 브라우저 렌더링 성능]] +# [[Chrome 브라우저 렌더링 성능|Chrome 브라우저 렌더링 성능]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -32,11 +32,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Chrome 브라우저 렌더링 - **정책 변화:** AI 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[가비지 컬렉션 (Garbage Collection)]], [[Orinoco]], [[유휴 시간 GC (Idle-time GC)]] -- **Projects/Contexts:** [[V8 JavaScript Engine]], [[Blink Renderer]] +- **Related Topics:** [[가비지 컬렉션 (Garbage Collection)|가비지 컬렉션 (Garbage Collection)]], [[Orinoco|Orinoco]], 유휴 시간 GC (Idle-time GC) +- **Projects/Contexts:** [[V8 JavaScript Engine|V8 JavaScript Engine]], Blink Renderer - **Contradictions/Notes:** 소스에 관련 정보가 부족합니다. 제공된 문서는 전적으로 V8 메모리 관리, 힙 구조, 메모리 누수 분석 등 JavaScript 엔진 단의 최적화에 집중되어 있습니다. 따라서 Chrome 렌더링 파이프라인(DOM 트리, CSSOM, 컴포지팅 등) 또는 Core Web Vitals(LCP, CLS, INP)의 구체적 동작 원리에 대한 정보는 소스에 포함되어 있지 않아 기술하지 못했습니다. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Chrome 브라우저 렌더링 성능.md]] +- Raw Source: 00_Raw/2026-04-20/Chrome 브라우저 렌더링 성능.md --- diff --git a/01_Archive/2026-04-20/Chrome.md b/01_Archive/2026-04-20/Chrome.md index d7496f2d..7b030f6b 100644 --- a/01_Archive/2026-04-20/Chrome.md +++ b/01_Archive/2026-04-20/Chrome.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-5D281C -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Chrome" --- -# [[Chrome]] +# [[Chrome|Chrome]] ## 📌 한 줄 통찰 (The Karpathy Summary) > Chrome은 웹 성능 표준과 최신 웹 그래픽 기술을 주도하는 Google의 웹 브라우저이다 [1, 2]. 강력한 개발자 도구인 Chrome DevTools를 제공하여 애플리케이션의 런타임 및 로드 성능을 심층적으로 분석할 수 있게 하며, WebGL 및 WebGPU와 같은 차세대 그래픽 API를 적극적으로 지원한다 [3, 4]. 또한 Chrome 사용자 환경 보고서(CrUX)를 통해 실제 사용자의 성능 데이터를 수집하여 Core Web Vitals를 측정하는 핵심적인 역할을 담당한다 [5, 6]. @@ -24,11 +24,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Chrome" - **정책 변화:** Graphics & Performance 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Chrome DevTools]], [[WebGPU]], [[Core Web Vitals]], [[CrUX]], [[WebGL]] -- **Projects/Contexts:** [[Interop 2025]], [[Baseline Project]] +- **Related Topics:** [[Chrome DevTools|Chrome DevTools]], [[WebGPU|WebGPU]], [[Core Web Vitals|Core Web Vitals]], [[CrUX|CrUX]], [[WebGL|WebGL]] +- **Projects/Contexts:** [[Interop 2025|Interop 2025]], [[Baseline Project|Baseline Project]] - **Contradictions/Notes:** 타이밍 공격(Spectre 등) 보안 문제로 인해 WebGPU의 타임스탬프 쿼리나 `EXT_disjoint_timer_query`의 해상도를 하드웨어 성능 그대로 제공하지 못하고, Chrome 자체적으로 사이트 격리 상태에 따라 정밀도를 의도적으로 낮추어(Quantization) 노출해야만 하는 한계가 존재한다 [19, 23, 24]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Chrome.md]] +- Raw Source: 00_Raw/2026-04-20/Chrome.md --- diff --git a/01_Archive/2026-04-20/Chromium WebGPU Implementation.md b/01_Archive/2026-04-20/Chromium WebGPU Implementation.md index 3c1c1100..150dbd39 100644 --- a/01_Archive/2026-04-20/Chromium WebGPU Implementation.md +++ b/01_Archive/2026-04-20/Chromium WebGPU Implementation.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-7025AF -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Chromium WebGPU Implementation" --- -# [[Chromium WebGPU Implementation]] +# [[Chromium WebGPU Implementation|Chromium WebGPU Implementation]] ## 📌 한 줄 통찰 (The Karpathy Summary) > Chromium의 WebGPU 구현은 **Dawn**이라는 백엔드를 기반으로 하는 차세대 웹 그래픽 및 컴퓨팅 API입니다 [1, 2]. 보안 이슈를 방지하기 위한 타임스탬프 양자화(Timestamp Quantization)와 같은 세밀한 기능이 구현되어 있으며, 싱글 스레드 기반인 WebGL의 한계를 넘어 멀티 스레드 명령 생성과 강력한 컴퓨트 셰이더 기능을 통해 브라우저 내에서 고성능 그래픽과 병렬 연산을 지원합니다 [1, 3, 4]. @@ -22,11 +22,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Chromium WebGPU Implementation - **정책 변화:** Graphics & Performance 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[WebGPU]], [[Dawn]], [[Timestamp Quantization]], [[WGSL]] -- **Projects/Contexts:** [[Chromium Project]], [[GPU for the Web Community Group]] +- **Related Topics:** [[WebGPU|WebGPU]], Dawn, [[Timestamp Quantization|Timestamp Quantization]], WGSL +- **Projects/Contexts:** Chromium Project, [[GPU for the Web Community Group|GPU for the Web Community Group]] - **Contradictions/Notes:** 타임스탬프 쿼리 기능 노출과 관련하여, 초기 Chromium(Blink) 인텐트는 Cross-Origin 격리되지 않은 컨텍스트에서 타임스탬프 쿼리를 완전히 비활성화할 계획을 세웠으나(보안 우려), 다른 브라우저 벤더 및 W3C 그룹과의 상호 운용성 논의를 거쳐 격리 여부와 무관하게 hr-time과 동일한 100µs 단위로 노출하는 방향으로 스펙 및 구현 방침이 변경되었습니다 [5-7]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Chromium WebGPU Implementation.md]] +- Raw Source: 00_Raw/2026-04-20/Chromium WebGPU Implementation.md --- diff --git a/01_Archive/2026-04-20/Chromium.md b/01_Archive/2026-04-20/Chromium.md index 017f9da0..06fad112 100644 --- a/01_Archive/2026-04-20/Chromium.md +++ b/01_Archive/2026-04-20/Chromium.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-6038C1 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Chromium" --- -# [[Chromium]] +# [[Chromium|Chromium]] ## 📌 한 줄 통찰 (The Karpathy Summary) > Chromium(또는 Chrome)은 V8 자바스크립트 엔진을 내장(embed)하여 실행하는 기반 웹 브라우저 프로젝트입니다 [1-3]. 제공된 소스에서 Chromium은 V8 메모리 케이지 도입과 같은 보안 정책을 선도하고 [4, 5], 브라우저 렌더링의 유휴 시간(idle time)을 활용해 가비지 컬렉션을 효율적으로 수행하며 [2], 강력한 메모리 프로파일링 및 추적(Tracing) 인프라를 제공하는 핵심 호스트 환경으로 설명됩니다 [1, 6, 7]. @@ -22,11 +22,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Chromium" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[V8 Engine]], [[V8 Memory Cage]], [[Blink]], [[Oilpan]], [[Garbage Collection]] -- **Projects/Contexts:** [[Electron]], [[Google Chrome]], [[Orinoco]] +- **Related Topics:** [[V8 Engine|V8 Engine]], [[V8 Memory Cage|V8 Memory Cage]], [[Blink|Blink]], [[Oilpan|Oilpan]], [[Garbage Collection|Garbage Collection]] +- **Projects/Contexts:** [[Electron|Electron]], [[Google Chrome|Google Chrome]], [[Orinoco|Orinoco]] - **Contradictions/Notes:** 제공된 소스 전반에서 'Chromium'과 'Chrome'이라는 명칭은 V8을 내장하는 브라우저 런타임 환경 및 보안/추적 인프라를 설명할 때 사실상 동일한 맥락으로 상호 교환되어 사용되고 있습니다 [2-4, 16]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Chromium.md]] +- Raw Source: 00_Raw/2026-04-20/Chromium.md --- diff --git a/01_Archive/2026-04-20/Chronic-Pain-Management-Protocols.md b/01_Archive/2026-04-20/Chronic-Pain-Management-Protocols.md index 132a2275..a2f0d8c5 100644 --- a/01_Archive/2026-04-20/Chronic-Pain-Management-Protocols.md +++ b/01_Archive/2026-04-20/Chronic-Pain-Management-Protocols.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-87CE94 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Chronic-Pain-Management-Protocols" --- -# [[Chronic-Pain-Management-Protocols]] +# [[Chronic-Pain-Management-Protocols|Chronic-Pain-Management-Protocols]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Chronic-Pain-Management-Protoc ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Chronic-Pain-Management-Protocols.md]] +- Raw Source: 00_Raw/2026-04-20/Chronic-Pain-Management-Protocols.md --- diff --git a/01_Archive/2026-04-20/Circuit Discovery (회로 발견).md b/01_Archive/2026-04-20/Circuit Discovery (회로 발견).md index cca40c82..d208d1d0 100644 --- a/01_Archive/2026-04-20/Circuit Discovery (회로 발견).md +++ b/01_Archive/2026-04-20/Circuit Discovery (회로 발견).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-0A3374 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Circuit Discovery (회로 발견)" --- -# [[Circuit Discovery (회로 발견)]] +# [[Circuit Discovery (회로 발견)|Circuit Discovery (회로 발견)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Circuit Discovery (회로 발 ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Circuit Discovery (회로 발견).md]] +- Raw Source: 00_Raw/2026-04-20/Circuit Discovery (회로 발견).md --- diff --git a/01_Archive/2026-04-20/Circular Economy Transitions.md b/01_Archive/2026-04-20/Circular Economy Transitions.md index fe924d5e..939a1aa8 100644 --- a/01_Archive/2026-04-20/Circular Economy Transitions.md +++ b/01_Archive/2026-04-20/Circular Economy Transitions.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-544952 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Circular Economy Transitions" --- -# [[Circular Economy Transitions]] +# [[Circular Economy Transitions|Circular Economy Transitions]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Circular Economy Transitions" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Circular Economy Transitions.md]] +- Raw Source: 00_Raw/2026-04-20/Circular Economy Transitions.md --- diff --git a/01_Archive/2026-04-20/Circular-Economy.md b/01_Archive/2026-04-20/Circular-Economy.md index 0f8a53ac..d77b97a6 100644 --- a/01_Archive/2026-04-20/Circular-Economy.md +++ b/01_Archive/2026-04-20/Circular-Economy.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-480BFD -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Circular-Economy" --- -# [[Circular-Economy]] +# [[Circular-Economy|Circular-Economy]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Circular-Economy" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Circular-Economy.md]] +- Raw Source: 00_Raw/2026-04-20/Circular-Economy.md --- diff --git a/01_Archive/2026-04-20/Clean as You Code.md b/01_Archive/2026-04-20/Clean as You Code.md index 115a0317..49c756bc 100644 --- a/01_Archive/2026-04-20/Clean as You Code.md +++ b/01_Archive/2026-04-20/Clean as You Code.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-B535E8 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Clean as You Code" --- -# [[Clean as You Code]] +# [[Clean as You Code|Clean as You Code]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 'Clean as You Code'는 레거시 백로그(legacy backlogs)를 처리하는 것에 집중하기보다는, 새로 작성되거나 변경된 코드의 문제를 즉시 해결하는 데 중점을 두는 방법론입니다 [1]. 이 접근 방식은 개발자가 코드를 병합하거나 수정할 때마다 코드 품질과 보안을 점진적이고 지속적으로 향상시키는 것을 목표로 합니다 [1, 2]. 소스에 관련 정보가 부족하지만, 주로 SonarQube 플랫폼에서 지속적인 코드 분석과 품질 관리를 장려하기 위해 사용하는 핵심 철학으로 소개됩니다 [1, 2]. @@ -20,11 +20,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Clean as You Code" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[SonarQube]], [[Technical Debt]], [[Static Application Security Testing (SAST)]] -- **Projects/Contexts:** [[SonarQube 플랫폼을 활용한 CI/CD 파이프라인 내 자동화된 코드 리뷰 및 품질 게이트 적용]] +- **Related Topics:** [[SonarQube|SonarQube]], [[Technical-Debt|Technical Debt]], [[Static Application Security Testing (SAST)|Static Application Security Testing (SAST)]] +- **Projects/Contexts:** SonarQube 플랫폼을 활용한 CI/CD 파이프라인 내 자동화된 코드 리뷰 및 품질 게이트 적용 - **Contradictions/Notes:** 소스 내에서 'Clean as You Code'라는 정확한 용어는 SonarQube의 방법론을 설명하는 단 한 문장[1]에만 등장합니다. 따라서 상세한 원리 및 배경에 대해서는 소스에 관련 정보가 부족하며, SonarQube의 코드 분석 철학을 바탕으로 내용을 합성했습니다. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Clean as You Code.md]] +- Raw Source: 00_Raw/2026-04-20/Clean as You Code.md --- diff --git a/01_Archive/2026-04-20/Clean-Architecture-Implementation.md b/01_Archive/2026-04-20/Clean-Architecture-Implementation.md index 6d265927..14d4b88f 100644 --- a/01_Archive/2026-04-20/Clean-Architecture-Implementation.md +++ b/01_Archive/2026-04-20/Clean-Architecture-Implementation.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-B131E0 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Clean-Architecture-Implementation" --- -# [[Clean-Architecture-Implementation]] +# [[Clean-Architecture-Implementation|Clean-Architecture-Implementation]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Clean-Architecture-Implementat ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Clean-Architecture-Implementation.md]] +- Raw Source: 00_Raw/2026-04-20/Clean-Architecture-Implementation.md --- diff --git a/01_Archive/2026-04-20/Clean-Architecture-TypeScript.md b/01_Archive/2026-04-20/Clean-Architecture-TypeScript.md index 9d075a40..0bb45c40 100644 --- a/01_Archive/2026-04-20/Clean-Architecture-TypeScript.md +++ b/01_Archive/2026-04-20/Clean-Architecture-TypeScript.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-3B1D45 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Clean-Architecture-TypeScript" --- -# [[Clean-Architecture-TypeScript]] +# [[Clean-Architecture-TypeScript|Clean-Architecture-TypeScript]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Clean-Architecture-TypeScript" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Clean-Architecture-TypeScript.md]] +- Raw Source: 00_Raw/2026-04-20/Clean-Architecture-TypeScript.md --- diff --git a/01_Archive/2026-04-20/Climate Change Mitigation Frameworks.md b/01_Archive/2026-04-20/Climate Change Mitigation Frameworks.md index 8d6e3db4..887be13b 100644 --- a/01_Archive/2026-04-20/Climate Change Mitigation Frameworks.md +++ b/01_Archive/2026-04-20/Climate Change Mitigation Frameworks.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-2E8F10 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Climate Change Mitigation Frameworks" --- -# [[Climate Change Mitigation Frameworks]] +# [[Climate Change Mitigation Frameworks|Climate Change Mitigation Frameworks]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Climate Change Mitigation Fram ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Climate Change Mitigation Frameworks.md]] +- Raw Source: 00_Raw/2026-04-20/Climate Change Mitigation Frameworks.md --- diff --git a/01_Archive/2026-04-20/Clinical-Kinesiology-Assessment.md b/01_Archive/2026-04-20/Clinical-Kinesiology-Assessment.md index d1d7c2d7..c1987bf8 100644 --- a/01_Archive/2026-04-20/Clinical-Kinesiology-Assessment.md +++ b/01_Archive/2026-04-20/Clinical-Kinesiology-Assessment.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-9DE738 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Clinical-Kinesiology-Assessment" --- -# [[Clinical-Kinesiology-Assessment]] +# [[Clinical-Kinesiology-Assessment|Clinical-Kinesiology-Assessment]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Clinical-Kinesiology-Assessmen ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Clinical-Kinesiology-Assessment.md]] +- Raw Source: 00_Raw/2026-04-20/Clinical-Kinesiology-Assessment.md --- diff --git a/01_Archive/2026-04-20/Code Formatting.md b/01_Archive/2026-04-20/Code Formatting.md index 4b702ffd..d8cb4ad4 100644 --- a/01_Archive/2026-04-20/Code Formatting.md +++ b/01_Archive/2026-04-20/Code Formatting.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-E4F919 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Code Formatting" --- -# [[Code Formatting]] +# [[Code Formatting|Code Formatting]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 코드 포맷팅(Code Formatting)은 들여쓰기, 공백, 줄 바꿈, 따옴표 등 소스 코드의 시각적 스타일과 레이아웃을 일관된 규칙에 맞게 정리하는 과정입니다. 이는 코드의 런타임 논리나 실행 의미를 변경하지 않고 코드의 구조적 형태만 변환하며, 일반적으로 Prettier나 Black과 같은 자동화 도구(Formatter)를 통해 수행됩니다. 일관된 코드 포맷팅은 가독성을 향상시키고 협업 시 개발자 간의 미적 선호도 차이로 인한 마찰과 인지적 부하를 줄여주는 핵심적인 역할을 합니다. @@ -30,11 +30,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Code Formatting" - **정책 변화:** Design & Experience 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Linter]], [[Prettier]], [[Code Stylometry]], [[Code Readability]] -- **Projects/Contexts:** [[Automated Code Governance]], [[CI/CD Pipeline]] +- **Related Topics:** [[린터 (Linter)|Linter]], [[Prettier|Prettier]], [[Code Stylometry (코드 문체론)|Code Stylometry]], Code Readability +- **Projects/Contexts:** Automated Code Governance, [[CI-CD Pipeline (지속적 통합 및 배포)|CI/CD Pipeline]] - **Contradictions/Notes:** ESLint와 같은 Linter 도구 내에도 자체적인 포맷팅 규칙이 존재하여 Prettier와 동시 사용 시 규칙 충돌(Infinite feedback loop)이 일어날 수 있습니다. 따라서 Linter의 포맷팅 기능을 끄고 이를 Prettier에 전담시키는 구성 최적화가 필수적입니다 [12, 18]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Code Formatting.md]] +- Raw Source: 00_Raw/2026-04-20/Code Formatting.md --- diff --git a/01_Archive/2026-04-20/Code Minification.md b/01_Archive/2026-04-20/Code Minification.md index 1a298443..167072c3 100644 --- a/01_Archive/2026-04-20/Code Minification.md +++ b/01_Archive/2026-04-20/Code Minification.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-D932E1 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Code Minification" --- -# [[Code Minification]] +# [[Code Minification|Code Minification]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 코드 축소(Code Minification)는 브라우저 등으로 코드를 배포할 때 소스 코드의 크기를 최소화하고 전송 및 렌더링 시간을 단축하기 위해 사용되는 소프트웨어 최적화 기법입니다 [1, 2]. 이 기법은 코드의 본래 실행 의미(semantics)를 변경하지 않은 채, 공백, 줄 바꿈, 주석 등 의미가 없는 요소를 제거하고 변수 이름을 짧게 변경하는 등의 표면적 변환을 수행합니다 [1, 2]. 가독성을 높이는 코드 포매팅(Code formatting)과 달리 코드 축소는 오히려 코드의 가독성을 저하시키며, 주로 소프트웨어 개발 완료 후 배포 직전에 자동화 도구에 의해 실행됩니다 [3]. @@ -23,11 +23,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Code Minification" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Code Formatting]], [[Code Stylometry]] -- **Projects/Contexts:** [[Web Development]], [[Python Minifier]] +- **Related Topics:** [[Code Formatting|Code Formatting]], [[Code Stylometry (코드 문체론)|Code Stylometry]] +- **Projects/Contexts:** Web Development, Python Minifier - **Contradictions/Notes:** 소스에 관련 정보가 부족합니다. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Code Minification.md]] +- Raw Source: 00_Raw/2026-04-20/Code Minification.md --- diff --git a/01_Archive/2026-04-20/Code Obfuscation.md b/01_Archive/2026-04-20/Code Obfuscation.md index dbff347f..5c99790b 100644 --- a/01_Archive/2026-04-20/Code Obfuscation.md +++ b/01_Archive/2026-04-20/Code Obfuscation.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-B2A3F3 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Code Obfuscation" --- -# [[Code Obfuscation]] +# [[Code Obfuscation|Code Obfuscation]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 코드 난독화(Code Obfuscation)는 소스 코드의 기능을 유지하면서도 코드를 읽거나 이해하기 어렵게 변환하는 기법입니다 [1, 2]. 주로 악의적이거나 자동화된 코드 스타일로메트리(Code Stylometry, 작성자 식별 분석)로부터 오픈소스 프로그래머의 신원과 프라이버시를 보호하기 위한 방어 수단으로 활용됩니다 [3-5]. 난독화 도구의 강도에 따라 코드의 가독성과 성능이 어느 정도 희생되지만, 기계 학습 모델의 작성자 식별 정확도를 유의미하게 낮출 수 있습니다 [2, 6]. @@ -23,11 +23,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Code Obfuscation" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Code Stylometry]], [[Authorship Attribution]], [[Code Minification]] -- **Projects/Contexts:** [[Tigress]], [[Stunnix]], [[Opy]], [[PyArmor]] +- **Related Topics:** [[Code Stylometry (코드 문체론)|Code Stylometry]], [[Authorship Attribution|Authorship Attribution]], [[Code Minification|Code Minification]] +- **Projects/Contexts:** Tigress, Stunnix, Opy, PyArmor - **Contradictions/Notes:** 단순한 미니파이(Minification)나 포맷팅 작업, 혹은 Stunnix와 같이 기본적인 난독화만 제공하는 도구는 기계 학습 모델을 속이기에 불충분합니다. 작성자를 식별하려는 시도를 완전히 회피하려면, Tigress와 같이 시스템 성능과 코드 가독성의 저하를 감수하는 심층적인 수준의 난독화를 적용해야 한다는 점이 관찰됩니다 [2, 6, 10]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Code Obfuscation.md]] +- Raw Source: 00_Raw/2026-04-20/Code Obfuscation.md --- diff --git a/01_Archive/2026-04-20/Code Review.md b/01_Archive/2026-04-20/Code Review.md index 3705fbc5..07917e4e 100644 --- a/01_Archive/2026-04-20/Code Review.md +++ b/01_Archive/2026-04-20/Code Review.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-8EC3C3 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Code Review" --- -# [[Code Review]] +# [[Code Review|Code Review]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 코드 리뷰(Code Review)는 소프트웨어의 전반적인 코드 건강 상태를 개선하고 품질 및 보안을 보장하기 위해 소스 코드를 검사하는 과정입니다 [1-3]. 이는 인간 개발자가 직접 수행하는 수동 리뷰(Manual Code Review)와 정적 분석(SAST) 및 AI 도구를 활용하는 자동화된 리뷰(Automated Code Review)로 나뉩니다 [4, 5]. 최신 소프트웨어 개발 환경에서는 자동화 도구의 속도와 인간의 문맥 이해 능력을 결합하여 일관성과 보안성을 극대화하는 하이브리드 접근법이 필수적인 모범 사례로 권장됩니다 [5-8]. @@ -30,11 +30,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Code Review" - **정책 변화:** AI 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Manual Code Review]], [[Automated Code Review]], [[SAST]], [[Linting]], [[Prettier]], [[Husky]] -- **Projects/Contexts:** [[CI/CD Pipelines]], [[SDLC]], [[Pull Request]] +- **Related Topics:** [[수동 코드 리뷰 (Manual Code Review)|Manual Code Review]], Automated Code Review, [[SAST|SAST]], Linting, [[Prettier|Prettier]], [[Husky|Husky]] +- **Projects/Contexts:** CI/CD Pipelines, [[SDLC (소프트웨어 개발 수명 주기)|SDLC]], [[풀 리퀘스트 (Pull Request)|Pull Request]] - **Contradictions/Notes:** 소스에 따르면 자동화된 리뷰 도구는 코드 검사 속도와 일관성을 극대화하지만, 비즈니스 로직과 아키텍처적 맥락을 이해하지 못해 실제 취약점의 약 22%를 놓치거나 오탐(False Positive)을 대량으로 양산할 수 있습니다 [22, 32]. 따라서 자동화 도구 단독으로는 완벽한 보안과 품질을 보장할 수 없으며, 복잡하고 위험도가 높은 코드는 반드시 인간 리뷰어의 수동 평가가 동반되어야 한다고 강조합니다 [5, 26, 33]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Code Review.md]] +- Raw Source: 00_Raw/2026-04-20/Code Review.md --- diff --git a/01_Archive/2026-04-20/Code Splitting Lazy Loading (코드 분할 및 지연 로딩).md b/01_Archive/2026-04-20/Code Splitting Lazy Loading (코드 분할 및 지연 로딩).md index 4a2813bd..f993b094 100644 --- a/01_Archive/2026-04-20/Code Splitting Lazy Loading (코드 분할 및 지연 로딩).md +++ b/01_Archive/2026-04-20/Code Splitting Lazy Loading (코드 분할 및 지연 로딩).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-59CADB -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Code Splitting Lazy Loading (코드 분할 및 지연 로딩)" --- -# [[Code Splitting Lazy Loading (코드 분할 및 지연 로딩)]] +# [[Code Splitting Lazy Loading (코드 분할 및 지연 로딩)|Code Splitting Lazy Loading (코드 분할 및 지연 로딩)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 거대한 자바스크립트 번들을 작은 단위로 나누고, 사용자가 당장 필요로 하지 않는 컴포넌트나 라이브러리의 로딩을 지연시켜 애플리케이션의 초기 로딩 속도와 핵심 웹 지표(FCP, LCP)를 비약적으로 개선하는 최적화 기법입니다. @@ -31,12 +31,12 @@ github_commit: "[P-Reinforce] Continuous Worker - Code Splitting Lazy Loading ( - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[React Performance Optimization]], [[React.lazy & Suspense]], [[Core Web Vitals (FCP, LCP, CLS)]], [[React Server Components (RSC)]] -- **Projects/Contexts:** [[대규모 SPA 초기 로딩 속도 개선]], [[Three.js / React Three Fiber 자산 최적화]] +- **Related Topics:** [[React Performance Optimization|React Performance Optimization]], React.lazy & Suspense, Core Web Vitals (FCP, LCP, CLS), [[React Server Components (RSC)|React Server Components (RSC)]] +- **Projects/Contexts:** 대규모 SPA 초기 로딩 속도 개선, Three.js / React Three Fiber 자산 최적화 - **Contradictions/Notes:** 코드 분할은 초기 로드 속도를 크게 높여주지만, 모든 컴포넌트를 무분별하게 분할할 경우 사용자가 상호작용을 할 때마다 네트워크 지연과 로딩 스피너를 마주하게 되어 오히려 UX를 크게 훼손할 수 있습니다. 항상 사용자의 여정(User Flow)을 예측하고 적절한 단위로 번들을 묶는 전략적 접근이 필요합니다. --- _Last updated: 2026-04-14_ -- Raw Source: [[00_Raw/2026-04-20/Code Splitting & Lazy Loading (코드 분할 및 지연 로딩).md]] +- Raw Source: 00_Raw/2026-04-20/Code Splitting & Lazy Loading (코드 분할 및 지연 로딩).md --- diff --git a/01_Archive/2026-04-20/Code Splitting Lazy Loading.md b/01_Archive/2026-04-20/Code Splitting Lazy Loading.md index 8f70d49f..fa649fef 100644 --- a/01_Archive/2026-04-20/Code Splitting Lazy Loading.md +++ b/01_Archive/2026-04-20/Code Splitting Lazy Loading.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-B933B1 -category: "[[10_Wiki/💡 Topics/General Knowledge]]" +category: "10_Wiki/💡 Topics/General Knowledge" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Code Splitting Lazy Loading" --- -# [[Code Splitting Lazy Loading]] +# [[Code Splitting Lazy Loading|Code Splitting Lazy Loading]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Code Splitting Lazy Loading" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Code Splitting & Lazy Loading.md]] +- Raw Source: 00_Raw/2026-04-20/Code Splitting & Lazy Loading.md --- diff --git a/01_Archive/2026-04-20/Code Splitting & Lazy Loading (코드 분할 및 지연 로딩).md b/01_Archive/2026-04-20/Code Splitting & Lazy Loading (코드 분할 및 지연 로딩).md index 9425570d..d7ace3b4 100644 --- a/01_Archive/2026-04-20/Code Splitting & Lazy Loading (코드 분할 및 지연 로딩).md +++ b/01_Archive/2026-04-20/Code Splitting & Lazy Loading (코드 분할 및 지연 로딩).md @@ -1,5 +1,5 @@ -# [[Code Splitting & Lazy Loading (코드 분할 및 지연 로딩)]] +# [[Code Splitting & Lazy Loading (코드 분할 및 지연 로딩)|Code Splitting & Lazy Loading (코드 분할 및 지연 로딩)]] ## 📌 Brief Summary @@ -22,8 +22,8 @@ ## 🔗 Knowledge Connections -- **Related Topics:** [[React Performance Optimization]], [[React.lazy & Suspense]], [[Core Web Vitals (FCP, LCP, CLS)]], [[React Server Components (RSC)]] -- **Projects/Contexts:** [[대규모 SPA 초기 로딩 속도 개선]], [[Three.js / React Three Fiber 자산 최적화]] +- **Related Topics:** [[React Performance Optimization|React Performance Optimization]], React.lazy & Suspense, Core Web Vitals (FCP, LCP, CLS), [[React Server Components (RSC)|React Server Components (RSC)]] +- **Projects/Contexts:** 대규모 SPA 초기 로딩 속도 개선, Three.js / React Three Fiber 자산 최적화 - **Contradictions/Notes:** 코드 분할은 초기 로드 속도를 크게 높여주지만, 모든 컴포넌트를 무분별하게 분할할 경우 사용자가 상호작용을 할 때마다 네트워크 지연과 로딩 스피너를 마주하게 되어 오히려 UX를 크게 훼손할 수 있습니다. 항상 사용자의 여정(User Flow)을 예측하고 적절한 단위로 번들을 묶는 전략적 접근이 필요합니다. --- diff --git a/01_Archive/2026-04-20/Code Splitting & Lazy Loading.md b/01_Archive/2026-04-20/Code Splitting & Lazy Loading.md deleted file mode 100644 index e69de29b..00000000 diff --git a/01_Archive/2026-04-20/Code Stylometry (코드 문체론).md b/01_Archive/2026-04-20/Code Stylometry (코드 문체론).md index 293a36c3..9bb5b3c9 100644 --- a/01_Archive/2026-04-20/Code Stylometry (코드 문체론).md +++ b/01_Archive/2026-04-20/Code Stylometry (코드 문체론).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-17B6B7 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Code Stylometry (코드 문체론)" --- -# [[Code Stylometry (코드 문체론)]] +# [[Code Stylometry (코드 문체론)|Code Stylometry (코드 문체론)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 코드 문체론(Code Stylometry)은 프로그래머가 작성한 소프트웨어 소스 코드의 프로그래밍 스타일을 분석하여 코드의 작성자를 자동으로 식별(저자 식별)하는 기술이다 [1], [2]. 이 기술은 소스 코드나 실행 파일에 남겨진 논리 구조, 데이터 유형, 주석, 명명 규칙, 레이아웃 등 프로그래머 고유의 특징들을 추출하여 머신러닝 알고리즘을 통해 저자를 추적한다 [3], [2]. 주로 코드 클론 탐지나 누락된 저작자 정보 복구 등에 유용하게 쓰일 수 있다 [4]. 그러나 동시에 검열 및 감시 우회 도구 개발자나 오픈소스 기여자의 익명성을 위협하고 신원을 노출시키는 수단으로 악용될 수 있어 심각한 프라이버시 문제를 제기하기도 한다 [4], [5], [6], [7]. @@ -27,11 +27,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Code Stylometry (코드 문체 - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Adversarial Code Stylometry]], [[Abstract Syntax Tree (AST)]], [[Concrete Syntax Tree (CST)]], [[Code Obfuscation]], [[Code Formatting]], [[Code Minification]] -- **Projects/Contexts:** [[Google Code Jam Dataset]], [[StyleCounsel]] +- **Related Topics:** [[Adversarial Code Stylometry|Adversarial Code Stylometry]], [[Abstract Syntax Tree (AST)|Abstract Syntax Tree (AST)]], [[Concrete Syntax Tree (CST)|Concrete Syntax Tree (CST)]], [[Code Obfuscation|Code Obfuscation]], [[Code Formatting|Code Formatting]], [[Code Minification|Code Minification]] +- **Projects/Contexts:** [[Google Code Jam Dataset|Google Code Jam Dataset]], [[StyleCounsel|StyleCounsel]] - **Contradictions/Notes:** 소스에 따르면 기계 학습 기반의 코드 문체론 모델에 대항하기 위한 적대적 기법들이 시도되고 있으나, 단순히 코드를 정렬하는 포매팅(Formatting)이나 축소(Minification) 처리만으로는 저자의 개별 스타일 특징을 완전히 제거할 수 없으며 대다수 저자가 여전히 식별 가능한 것으로 나타납니다 [23], [22]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/Code Stylometry (코드 문체론).md]] +- Raw Source: 00_Raw/2026-04-20/Code Stylometry (코드 문체론).md --- diff --git a/01_Archive/2026-04-20/Codemod-Engineering.md b/01_Archive/2026-04-20/Codemod-Engineering.md index 2c9916a9..7782fc6f 100644 --- a/01_Archive/2026-04-20/Codemod-Engineering.md +++ b/01_Archive/2026-04-20/Codemod-Engineering.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-084361 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Codemod-Engineering" --- -# [[Codemod-Engineering]] +# [[Codemod-Engineering|Codemod-Engineering]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Codemod-Engineering" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Codemod-Engineering.md]] +- Raw Source: 00_Raw/2026-04-20/Codemod-Engineering.md --- diff --git a/01_Archive/2026-04-20/Cognitive Aging Research.md b/01_Archive/2026-04-20/Cognitive Aging Research.md index 303dfce0..77700e37 100644 --- a/01_Archive/2026-04-20/Cognitive Aging Research.md +++ b/01_Archive/2026-04-20/Cognitive Aging Research.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-8C858F -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Cognitive Aging Research" --- -# [[Cognitive Aging Research]] +# [[Cognitive Aging Research|Cognitive Aging Research]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Cognitive Aging Research" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Cognitive Aging Research.md]] +- Raw Source: 00_Raw/2026-04-20/Cognitive Aging Research.md --- diff --git a/01_Archive/2026-04-20/Cognitive Biases.md b/01_Archive/2026-04-20/Cognitive Biases.md index 583bc52d..c9123925 100644 --- a/01_Archive/2026-04-20/Cognitive Biases.md +++ b/01_Archive/2026-04-20/Cognitive Biases.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-FEA140 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Cognitive Biases" --- -# [[Cognitive Biases]] +# [[Cognitive Biases|Cognitive Biases]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Cognitive Biases" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Cognitive Biases.md]] +- Raw Source: 00_Raw/2026-04-20/Cognitive Biases.md --- diff --git a/01_Archive/2026-04-20/Cognitive Computing.md b/01_Archive/2026-04-20/Cognitive Computing.md index 3bea5e45..12921551 100644 --- a/01_Archive/2026-04-20/Cognitive Computing.md +++ b/01_Archive/2026-04-20/Cognitive Computing.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-E7BBAB -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Cognitive Computing" --- -# [[Cognitive Computing]] +# [[Cognitive Computing|Cognitive Computing]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Cognitive Computing" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Cognitive Computing.md]] +- Raw Source: 00_Raw/2026-04-20/Cognitive Computing.md --- diff --git a/01_Archive/2026-04-20/Cognitive Dissonance.md b/01_Archive/2026-04-20/Cognitive Dissonance.md index 8c84338d..3ac1779e 100644 --- a/01_Archive/2026-04-20/Cognitive Dissonance.md +++ b/01_Archive/2026-04-20/Cognitive Dissonance.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-0C898E -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Cognitive Dissonance" --- -# [[Cognitive Dissonance]] +# [[Cognitive Dissonance|Cognitive Dissonance]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Cognitive Dissonance" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Cognitive Dissonance.md]] +- Raw Source: 00_Raw/2026-04-20/Cognitive Dissonance.md --- diff --git a/01_Archive/2026-04-20/Cognitive Load Theory.md b/01_Archive/2026-04-20/Cognitive Load Theory.md index ecd3a5f1..74751107 100644 --- a/01_Archive/2026-04-20/Cognitive Load Theory.md +++ b/01_Archive/2026-04-20/Cognitive Load Theory.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-29F633 -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Cognitive Load Theory" --- -# [[Cognitive Load Theory]] +# [[Cognitive Load Theory|Cognitive Load Theory]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Cognitive Load Theory" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Cognitive Load Theory.md]] +- Raw Source: 00_Raw/2026-04-20/Cognitive Load Theory.md --- diff --git a/01_Archive/2026-04-20/Cognitive Neuroscience of Flow.md b/01_Archive/2026-04-20/Cognitive Neuroscience of Flow.md index a470949b..7e08fa82 100644 --- a/01_Archive/2026-04-20/Cognitive Neuroscience of Flow.md +++ b/01_Archive/2026-04-20/Cognitive Neuroscience of Flow.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-785635 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Cognitive Neuroscience of Flow" --- -# [[Cognitive Neuroscience of Flow]] +# [[Cognitive Neuroscience of Flow|Cognitive Neuroscience of Flow]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Cognitive Neuroscience of Flow ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Cognitive Neuroscience of Flow.md]] +- Raw Source: 00_Raw/2026-04-20/Cognitive Neuroscience of Flow.md --- diff --git a/01_Archive/2026-04-20/Cognitive Psychology.md b/01_Archive/2026-04-20/Cognitive Psychology.md index 297547cf..e3bf0a15 100644 --- a/01_Archive/2026-04-20/Cognitive Psychology.md +++ b/01_Archive/2026-04-20/Cognitive Psychology.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-2E9AA2 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Cognitive Psychology" --- -# [[Cognitive Psychology]] +# [[Cognitive Psychology|Cognitive Psychology]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Cognitive Psychology" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Cognitive Psychology.md]] +- Raw Source: 00_Raw/2026-04-20/Cognitive Psychology.md --- diff --git a/01_Archive/2026-04-20/Cognitive Reserve Theory.md b/01_Archive/2026-04-20/Cognitive Reserve Theory.md index f6037a6d..12c86f60 100644 --- a/01_Archive/2026-04-20/Cognitive Reserve Theory.md +++ b/01_Archive/2026-04-20/Cognitive Reserve Theory.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-01307D -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Cognitive Reserve Theory" --- -# [[Cognitive Reserve Theory]] +# [[Cognitive Reserve Theory|Cognitive Reserve Theory]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Cognitive Reserve Theory" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Cognitive Reserve Theory.md]] +- Raw Source: 00_Raw/2026-04-20/Cognitive Reserve Theory.md --- diff --git a/01_Archive/2026-04-20/Cognitive Training Software (e.g., Aim Lab_KovaaK's).md b/01_Archive/2026-04-20/Cognitive Training Software (e.g., Aim Lab_KovaaK's).md index d8ed7815..7dce38a8 100644 --- a/01_Archive/2026-04-20/Cognitive Training Software (e.g., Aim Lab_KovaaK's).md +++ b/01_Archive/2026-04-20/Cognitive Training Software (e.g., Aim Lab_KovaaK's).md @@ -1,4 +1,4 @@ -[[Cognitive Training Software (e.g., Aim Lab/KovaaK's)]] +[[Cognitive Training Software (eg Aim Lab_KovaaKs)|Cognitive Training Software (e.g., Aim Lab/KovaaK's)]] 📌 Brief Summary Cognitive training software, specifically in the context of "aim trainers," refers to specialized digital environments designed to enhance neurocognitive functions such as visual attention, reaction time, spatial awareness, and fine motor coordination. These platforms utilize high-frequency feedback loops and task-specific drills to induce neuroplasticity and improve sensorimotor integration, primarily for competitive esports athletes and rehabilitative cognitive therapy. @@ -13,8 +13,8 @@ Cognitive training software, specifically in the context of "aim trainers," refe * **Technological Integration:** Modern iterations are increasingly incorporating **Machine Learning (ML)** to generate personalized training regimens. By analyzing user error patterns, the software can dynamically adjust difficulty levels and task frequency to maintain the "Flow State" (the optimal balance between challenge and skill level). 🔗 Knowledge Connections -* Related Topics: [[Neuroplasticity]], [[Sensorimotor Integration]], [[Perceptual Learning]], [[Human-Computer Interaction (HCI)]] -* Projects/Contexts: [[Esports Performance Science]], [[Visual Rehabilitation Therapy]], [[Motor Skill Acquisition Research]] +* Related Topics: [[Neuroplasticity|Neuroplasticity]], [[Sensorimotor-Integration|Sensorimotor Integration]], [[Perceptual-Learning|Perceptual Learning]], [[Human-Computer Interaction (HCI)|Human-Computer Interaction (HCI)]] +* Projects/Contexts: Esports Performance Science, Visual Rehabilitation Therapy, Motor Skill Acquisition Research * Contradictions/Notes: There is an active debate in sports science regarding the "Transfer Problem"—specifically whether training precision in a simulated 2D plane significantly enhances cognitive decision-making in 3D spatial environments. Last updated: 2026-04-16 \ No newline at end of file diff --git a/01_Archive/2026-04-20/Cognitive Training Software (eg Aim Lab_KovaaKs).md b/01_Archive/2026-04-20/Cognitive Training Software (eg Aim Lab_KovaaKs).md index aa9a8084..3b410e0d 100644 --- a/01_Archive/2026-04-20/Cognitive Training Software (eg Aim Lab_KovaaKs).md +++ b/01_Archive/2026-04-20/Cognitive Training Software (eg Aim Lab_KovaaKs).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-9F2CFC -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Cognitive Training Software (eg Aim Lab_KovaaKs)" --- -# [[Cognitive Training Software (eg Aim Lab_KovaaKs)]] +# [[Cognitive Training Software (eg Aim Lab_KovaaKs)|Cognitive Training Software (eg Aim Lab_KovaaKs)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Cognitive Training Software (e ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Cognitive Training Software (e.g., Aim Lab_KovaaK's).md]] +- Raw Source: 00_Raw/2026-04-20/Cognitive Training Software (e.g., Aim Lab_KovaaK's).md --- diff --git a/01_Archive/2026-04-20/Cognitive-Evaluation-Theory.md b/01_Archive/2026-04-20/Cognitive-Evaluation-Theory.md index 6202459a..1d98893e 100644 --- a/01_Archive/2026-04-20/Cognitive-Evaluation-Theory.md +++ b/01_Archive/2026-04-20/Cognitive-Evaluation-Theory.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-192E25 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Cognitive-Evaluation-Theory" --- -# [[Cognitive-Evaluation-Theory]] +# [[Cognitive-Evaluation-Theory|Cognitive-Evaluation-Theory]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Cognitive-Evaluation-Theory" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Cognitive-Evaluation-Theory.md]] +- Raw Source: 00_Raw/2026-04-20/Cognitive-Evaluation-Theory.md --- diff --git a/01_Archive/2026-04-20/Cognitive-Flexibility.md b/01_Archive/2026-04-20/Cognitive-Flexibility.md index b1c1062f..3c1f54d0 100644 --- a/01_Archive/2026-04-20/Cognitive-Flexibility.md +++ b/01_Archive/2026-04-20/Cognitive-Flexibility.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-634AD5 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Cognitive-Flexibility" --- -# [[Cognitive-Flexibility]] +# [[Cognitive-Flexibility|Cognitive-Flexibility]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Cognitive-Flexibility" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Cognitive-Flexibility.md]] +- Raw Source: 00_Raw/2026-04-20/Cognitive-Flexibility.md --- diff --git a/01_Archive/2026-04-20/Cognitive-Load-Theory.md b/01_Archive/2026-04-20/Cognitive-Load-Theory.md index ff8f722c..6b567694 100644 --- a/01_Archive/2026-04-20/Cognitive-Load-Theory.md +++ b/01_Archive/2026-04-20/Cognitive-Load-Theory.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-B1006C -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Cognitive-Load-Theory" --- -# [[Cognitive-Load-Theory]] +# [[Cognitive-Load-Theory|Cognitive-Load-Theory]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Cognitive-Load-Theory" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Cognitive-Load-Theory.md]] +- Raw Source: 00_Raw/2026-04-20/Cognitive-Load-Theory.md --- diff --git a/01_Archive/2026-04-20/Cognitive-Psychology.md b/01_Archive/2026-04-20/Cognitive-Psychology.md index 1d6f7357..820daa08 100644 --- a/01_Archive/2026-04-20/Cognitive-Psychology.md +++ b/01_Archive/2026-04-20/Cognitive-Psychology.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-7EA6B8 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Cognitive-Psychology" --- -# [[Cognitive-Psychology]] +# [[Cognitive-Psychology|Cognitive-Psychology]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Cognitive-Psychology" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Cognitive-Psychology.md]] +- Raw Source: 00_Raw/2026-04-20/Cognitive-Psychology.md --- diff --git a/01_Archive/2026-04-20/Cognitive-Therapy-in-CBT.md b/01_Archive/2026-04-20/Cognitive-Therapy-in-CBT.md index 531cb950..9bbd40e1 100644 --- a/01_Archive/2026-04-20/Cognitive-Therapy-in-CBT.md +++ b/01_Archive/2026-04-20/Cognitive-Therapy-in-CBT.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-364B53 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Cognitive-Therapy-in-CBT" --- -# [[Cognitive-Therapy-in-CBT]] +# [[Cognitive-Therapy-in-CBT|Cognitive-Therapy-in-CBT]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Cognitive-Therapy-in-CBT" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Cognitive-Therapy-in-CBT.md]] +- Raw Source: 00_Raw/2026-04-20/Cognitive-Therapy-in-CBT.md --- diff --git a/01_Archive/2026-04-20/Cognitive_Load.md b/01_Archive/2026-04-20/Cognitive_Load.md index f6a2656c..1215ea96 100644 --- a/01_Archive/2026-04-20/Cognitive_Load.md +++ b/01_Archive/2026-04-20/Cognitive_Load.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-DESIGN-004 -category: "[[10_Wiki/💡 Topics/Design]]" +category: "10_Wiki/💡 Topics/Design" confidence_score: 0.94 tags: [design, hci, psychology, cognitive-load] last_reinforced: 2026-04-20 github_commit: "batch-reinforce-07" --- -# [[Cognitive Load Theory (인지 부하 이론)]] +# Cognitive Load Theory (인지 부하 이론) ## 📌 한 줄 통찰 (The Karpathy Summary) > 우리 뇌의 작업 기억(Working Memory) 용량은 한정되어 있음을 인정하고, 정보 전달의 효율을 위해 마찰을 설계하는 기술. @@ -24,6 +24,6 @@ github_commit: "batch-reinforce-07" - **정책 변화:** 사용자 만족도(w3) 지표로 인지 부하 측정 가이던스 도입. ## 🔗 지식 연결 (Graph) -- **Parent:** [[10_Wiki/💡 Topics/Design]] -- **Related:** [[HCI]], [[UX-Design]], [[Inclusive_Design]] -- **Raw Source:** [[00_Raw/2026-04-20/Cognitive Load Theory.md]] +- **Parent:** 10_Wiki/💡 Topics/Design +- **Related:** [[HCI|HCI]], [[사용자 경험 디자인 (UX Design)|UX-Design]], [[Inclusive_Design|Inclusive_Design]] +- **Raw Source:** 00_Raw/2026-04-20/Cognitive Load Theory.md diff --git a/01_Archive/2026-04-20/Collaborative Learning Environments.md b/01_Archive/2026-04-20/Collaborative Learning Environments.md index fa20385d..d52f5f51 100644 --- a/01_Archive/2026-04-20/Collaborative Learning Environments.md +++ b/01_Archive/2026-04-20/Collaborative Learning Environments.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-617D95 -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Collaborative Learning Environments" --- -# [[Collaborative Learning Environments]] +# [[Collaborative Learning Environments|Collaborative Learning Environments]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Collaborative Learning Environ ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Collaborative Learning Environments.md]] +- Raw Source: 00_Raw/2026-04-20/Collaborative Learning Environments.md --- diff --git a/01_Archive/2026-04-20/Combinatorial Game Theory.md b/01_Archive/2026-04-20/Combinatorial Game Theory.md index 0c617c2f..782dcca2 100644 --- a/01_Archive/2026-04-20/Combinatorial Game Theory.md +++ b/01_Archive/2026-04-20/Combinatorial Game Theory.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-D52D87 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Combinatorial Game Theory" --- -# [[Combinatorial Game Theory]] +# [[Combinatorial Game Theory|Combinatorial Game Theory]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Combinatorial Game Theory" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Combinatorial Game Theory.md]] +- Raw Source: 00_Raw/2026-04-20/Combinatorial Game Theory.md --- diff --git a/01_Archive/2026-04-20/Combinatorial-Optimization.md b/01_Archive/2026-04-20/Combinatorial-Optimization.md index 35821a4a..16ed0d2f 100644 --- a/01_Archive/2026-04-20/Combinatorial-Optimization.md +++ b/01_Archive/2026-04-20/Combinatorial-Optimization.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-06C1FB -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Combinatorial-Optimization" --- -# [[Combinatorial-Optimization]] +# [[Combinatorial-Optimization|Combinatorial-Optimization]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Combinatorial-Optimization" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Combinatorial-Optimization.md]] +- Raw Source: 00_Raw/2026-04-20/Combinatorial-Optimization.md --- diff --git a/01_Archive/2026-04-20/CompCert-C-Compiler.md b/01_Archive/2026-04-20/CompCert-C-Compiler.md index 8472b0e9..b281040c 100644 --- a/01_Archive/2026-04-20/CompCert-C-Compiler.md +++ b/01_Archive/2026-04-20/CompCert-C-Compiler.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-4D22EB -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - CompCert-C-Compiler" --- -# [[CompCert-C-Compiler]] +# [[CompCert-C-Compiler|CompCert-C-Compiler]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - CompCert-C-Compiler" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/CompCert-C-Compiler.md]] +- Raw Source: 00_Raw/2026-04-20/CompCert-C-Compiler.md --- diff --git a/01_Archive/2026-04-20/Competitive Esports Ecosystems.md b/01_Archive/2026-04-20/Competitive Esports Ecosystems.md index 2a410c42..e3afd440 100644 --- a/01_Archive/2026-04-20/Competitive Esports Ecosystems.md +++ b/01_Archive/2026-04-20/Competitive Esports Ecosystems.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-69DA0B -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Competitive Esports Ecosystems" --- -# [[Competitive Esports Ecosystems]] +# [[Competitive Esports Ecosystems|Competitive Esports Ecosystems]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Competitive Esports Ecosystems ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Competitive Esports Ecosystems.md]] +- Raw Source: 00_Raw/2026-04-20/Competitive Esports Ecosystems.md --- diff --git a/01_Archive/2026-04-20/Complex Adaptive Systems.md b/01_Archive/2026-04-20/Complex Adaptive Systems.md index 9a237d70..9b9c1569 100644 --- a/01_Archive/2026-04-20/Complex Adaptive Systems.md +++ b/01_Archive/2026-04-20/Complex Adaptive Systems.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-AB2667 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Complex Adaptive Systems" --- -# [[Complex Adaptive Systems]] +# [[Complex Adaptive Systems|Complex Adaptive Systems]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Complex Adaptive Systems" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Complex Adaptive Systems.md]] +- Raw Source: 00_Raw/2026-04-20/Complex Adaptive Systems.md --- diff --git a/01_Archive/2026-04-20/Complex-Adaptive-Systems.md b/01_Archive/2026-04-20/Complex-Adaptive-Systems.md index 300708c6..04f56ed9 100644 --- a/01_Archive/2026-04-20/Complex-Adaptive-Systems.md +++ b/01_Archive/2026-04-20/Complex-Adaptive-Systems.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-A9DF17 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Complex-Adaptive-Systems" --- -# [[Complex-Adaptive-Systems]] +# [[Complex-Adaptive-Systems|Complex-Adaptive-Systems]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Complex-Adaptive-Systems" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Complex-Adaptive-Systems.md]] +- Raw Source: 00_Raw/2026-04-20/Complex-Adaptive-Systems.md --- diff --git a/01_Archive/2026-04-20/Complexity Science in Economics.md b/01_Archive/2026-04-20/Complexity Science in Economics.md index 3a49b59a..ff3dec8a 100644 --- a/01_Archive/2026-04-20/Complexity Science in Economics.md +++ b/01_Archive/2026-04-20/Complexity Science in Economics.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-527F62 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Complexity Science in Economics" --- -# [[Complexity Science in Economics]] +# [[Complexity Science in Economics|Complexity Science in Economics]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Complexity Science in Economic ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Complexity Science in Economics.md]] +- Raw Source: 00_Raw/2026-04-20/Complexity Science in Economics.md --- diff --git a/01_Archive/2026-04-20/Complexity Theory.md b/01_Archive/2026-04-20/Complexity Theory.md index aec28e98..b69eda5b 100644 --- a/01_Archive/2026-04-20/Complexity Theory.md +++ b/01_Archive/2026-04-20/Complexity Theory.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-C7076A -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Complexity Theory" --- -# [[Complexity Theory]] +# [[Complexity Theory|Complexity Theory]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Complexity Theory" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Complexity Theory.md]] +- Raw Source: 00_Raw/2026-04-20/Complexity Theory.md --- diff --git a/01_Archive/2026-04-20/Complexity-Theory.md b/01_Archive/2026-04-20/Complexity-Theory.md index bcc84c77..79072d43 100644 --- a/01_Archive/2026-04-20/Complexity-Theory.md +++ b/01_Archive/2026-04-20/Complexity-Theory.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-F606A9 -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Complexity-Theory" --- -# [[Complexity-Theory]] +# [[Complexity-Theory|Complexity-Theory]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Complexity-Theory" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Complexity-Theory.md]] +- Raw Source: 00_Raw/2026-04-20/Complexity-Theory.md --- diff --git a/01_Archive/2026-04-20/Computation-Caching-Strategies.md b/01_Archive/2026-04-20/Computation-Caching-Strategies.md index a2f53932..86cbdede 100644 --- a/01_Archive/2026-04-20/Computation-Caching-Strategies.md +++ b/01_Archive/2026-04-20/Computation-Caching-Strategies.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-802544 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Computation-Caching-Strategies" --- -# [[Computation-Caching-Strategies]] +# [[Computation-Caching-Strategies|Computation-Caching-Strategies]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Computation-Caching-Strategies ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Computation-Caching-Strategies.md]] +- Raw Source: 00_Raw/2026-04-20/Computation-Caching-Strategies.md --- diff --git a/01_Archive/2026-04-20/Computational Creativity.md b/01_Archive/2026-04-20/Computational Creativity.md index 51340817..7159b924 100644 --- a/01_Archive/2026-04-20/Computational Creativity.md +++ b/01_Archive/2026-04-20/Computational Creativity.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-E2FD01 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Computational Creativity" --- -# [[Computational Creativity]] +# [[Computational Creativity|Computational Creativity]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Computational Creativity" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Computational Creativity.md]] +- Raw Source: 00_Raw/2026-04-20/Computational Creativity.md --- diff --git a/01_Archive/2026-04-20/Computational Ecology.md b/01_Archive/2026-04-20/Computational Ecology.md index 7b0b5354..15a55261 100644 --- a/01_Archive/2026-04-20/Computational Ecology.md +++ b/01_Archive/2026-04-20/Computational Ecology.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-563573 -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Computational Ecology" --- -# [[Computational Ecology]] +# [[Computational Ecology|Computational Ecology]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Computational Ecology" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Computational Ecology.md]] +- Raw Source: 00_Raw/2026-04-20/Computational Ecology.md --- diff --git a/01_Archive/2026-04-20/Computational Geometry.md b/01_Archive/2026-04-20/Computational Geometry.md index 1948eee8..92c3ce87 100644 --- a/01_Archive/2026-04-20/Computational Geometry.md +++ b/01_Archive/2026-04-20/Computational Geometry.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AI-053 -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.97 tags: [geometry, computational geometry, 3d, rendering] last_reinforced: 2026-06-XX github_commit: "[P-Reinforce] Processed Computational Geometry." --- -# [[Computational Geometry]] (계산 기하학) +# [[Computational Geometry|Computational Geometry]] (계산 기하학) ## 📌 한 줄 통찰 (The Karpathy Summary) > 수학적 알고리즘을 사용하여 컴퓨터가 점, 곡선, 다각형 같은 기하학적 객체들 사이의 관계와 공간 구조를 효율적으로 분석하고 조작하는 기술 분야이다. @@ -24,7 +24,7 @@ github_commit: "[P-Reinforce] Processed Computational Geometry." - **정책 변화:** 최신 트렌드는 하드웨어 가속(GPU)과 연동하여 복잡한 기하학적 계산(예: Ray Tracing)을 실시간으로 처리하는 방향으로 진화하고 있다. ## 🔗 지식 연결 (Graph) -- Parent: [[Computational Geometry]] -- Related: [[Bounding Volume Hierarchy (BVH)]] , [[Three.js 렌더링 최적화]] , [[Physics-Based-Simulation]] -- Raw Source: [[00_Raw/Computational Geometry.md]] +- Parent: [[Computational Geometry|Computational Geometry]] +- Related: [[Bounding Volume Hierarchy (BVH)|Bounding Volume Hierarchy (BVH)]] , [[Three.js 렌더링 최적화|Three.js 렌더링 최적화]] , [[Physics-Based-Simulation|Physics-Based-Simulation]] +- Raw Source: 00_Raw/Computational Geometry.md --- \ No newline at end of file diff --git a/01_Archive/2026-04-20/Computational Neuroscience of Reinforcement Learning.md b/01_Archive/2026-04-20/Computational Neuroscience of Reinforcement Learning.md index d2f398e0..53aca429 100644 --- a/01_Archive/2026-04-20/Computational Neuroscience of Reinforcement Learning.md +++ b/01_Archive/2026-04-20/Computational Neuroscience of Reinforcement Learning.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-457C50 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Computational Neuroscience of Reinforcement Learning" --- -# [[Computational Neuroscience of Reinforcement Learning]] +# [[Computational Neuroscience of Reinforcement Learning|Computational Neuroscience of Reinforcement Learning]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Computational Neuroscience of ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Computational Neuroscience of Reinforcement Learning.md]] +- Raw Source: 00_Raw/2026-04-20/Computational Neuroscience of Reinforcement Learning.md --- diff --git a/01_Archive/2026-04-20/Computational Thinking.md b/01_Archive/2026-04-20/Computational Thinking.md index 148f9b9d..c3376d69 100644 --- a/01_Archive/2026-04-20/Computational Thinking.md +++ b/01_Archive/2026-04-20/Computational Thinking.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-45C605 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Computational Thinking" --- -# [[Computational Thinking]] +# [[Computational Thinking|Computational Thinking]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Computational Thinking" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Computational Thinking.md]] +- Raw Source: 00_Raw/2026-04-20/Computational Thinking.md --- diff --git a/01_Archive/2026-04-20/Computational-Creativity.md b/01_Archive/2026-04-20/Computational-Creativity.md index 427780d3..af523e79 100644 --- a/01_Archive/2026-04-20/Computational-Creativity.md +++ b/01_Archive/2026-04-20/Computational-Creativity.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-90667E -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Computational-Creativity" --- -# [[Computational-Creativity]] +# [[Computational-Creativity|Computational-Creativity]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Computational-Creativity" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Computational-Creativity.md]] +- Raw Source: 00_Raw/2026-04-20/Computational-Creativity.md --- diff --git a/01_Archive/2026-04-20/Computational-Fluid-Dynamics.md b/01_Archive/2026-04-20/Computational-Fluid-Dynamics.md index c3403d3b..18d45e57 100644 --- a/01_Archive/2026-04-20/Computational-Fluid-Dynamics.md +++ b/01_Archive/2026-04-20/Computational-Fluid-Dynamics.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-668FCE -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Computational-Fluid-Dynamics" --- -# [[Computational-Fluid-Dynamics]] +# [[Computational-Fluid-Dynamics|Computational-Fluid-Dynamics]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Computational-Fluid-Dynamics" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Computational-Fluid-Dynamics.md]] +- Raw Source: 00_Raw/2026-04-20/Computational-Fluid-Dynamics.md --- diff --git a/01_Archive/2026-04-20/Compute Shader.md b/01_Archive/2026-04-20/Compute Shader.md index d577204b..4d774c0f 100644 --- a/01_Archive/2026-04-20/Compute Shader.md +++ b/01_Archive/2026-04-20/Compute Shader.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-38086E -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Compute Shader" --- -# [[Compute Shader]] +# [[Compute Shader|Compute Shader]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 컴퓨트 셰이더(Compute Shader)는 자바스크립트 메인 스레드나 CPU가 처리하던 무거운 연산 작업을 수천 개의 GPU 코어를 활용해 병렬로 처리할 수 있게 해주는 WebGPU의 핵심 기능입니다 [1]. 주로 입자(Particle) 시스템, 물리 연산, 실시간 필터링, 그리고 대규모 객체의 가시성 판별(Culling)과 같은 범용 GPU 연산(GPGPU)에 사용되어, 기존 WebGL 기반 환경의 한계를 뛰어넘는 압도적인 성능 향상을 제공합니다 [1-3]. @@ -24,11 +24,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Compute Shader" - **정책 변화:** Graphics & Performance 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[WebGPU]], [[GPU-driven Rendering]], [[Indirect Draw]], [[Frustum Culling]] +- **Related Topics:** [[WebGPU|WebGPU]], [[GPU-driven Rendering|GPU-driven Rendering]], [[Indirect Draw|Indirect Draw]], [[Frustum Culling|Frustum Culling]] - **Projects/Contexts:** 대규모 건설 및 BIM 모델 플랫폼(수백만 개의 컴포넌트 렌더링 최적화) [13, 14], 엑스포 2025 오사카에 전시된 100만 파티클 유체 시뮬레이션 설치물(Hokusai) [15, 16]. - **Contradictions/Notes:** 컴퓨트 셰이더는 최신 그래픽 API인 WebGPU에서 기본 지원되지만, 구형 WebGL이나 WebGL2 환경에서는 직접적으로 지원되지 않으므로 이를 활용하기 위해서는 반드시 WebGPU 기반의 렌더러 환경을 사용해야 한다는 제약이 있습니다 [3, 17]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Compute Shader.md]] +- Raw Source: 00_Raw/2026-04-20/Compute Shader.md --- diff --git a/01_Archive/2026-04-20/Compute Shaders.md b/01_Archive/2026-04-20/Compute Shaders.md index 2f0bc0a9..8627af31 100644 --- a/01_Archive/2026-04-20/Compute Shaders.md +++ b/01_Archive/2026-04-20/Compute Shaders.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-B1DBB3 -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Compute Shaders" --- -# [[Compute Shaders]] +# [[Compute Shaders|Compute Shaders]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 컴퓨트 셰이더(Compute Shaders)는 WebGPU 환경에서 지원되는 기능으로, CPU의 메인 스레드에서 수행되던 무거운 범용 연산 작업을 GPU로 오프로드하는 핵심 기술입니다 [1, 2]. GPU의 수천 개 코어를 활용한 병렬 처리를 통해 물리 시뮬레이션, 충돌 감지, 대규모 파티클 시스템 등의 작업 성능을 비약적으로 향상시킵니다 [2]. 또한 간접 그리기(Indirect Drawing) 기술과 결합하여 CPU의 개입 없이 가시성을 판별하고 화면을 그리는 완전한 GPU 주도 렌더링(GPU-driven Rendering) 파이프라인을 구축하는 데 사용됩니다 [3, 4]. @@ -24,11 +24,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Compute Shaders" - **정책 변화:** Graphics & Performance 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** `[[WebGPU]]`, `[[GPU-driven Rendering]]`, `[[Indirect Drawing]]`, `[[Storage Textures]]`, `[[Frustum Culling]]` -- **Projects/Contexts:** `[[Three.js]]`, `[[Segments.ai]]`, `[[BIM Datasets]]` +- **Related Topics:** `[[WebGPU|WebGPU]]`, `[[GPU-driven Rendering|GPU-driven Rendering]]`, `Indirect Drawing`, `[[스토리지 텍스처(Storage Textures)|Storage Textures]]`, `[[Frustum Culling|Frustum Culling]]` +- **Projects/Contexts:** `[[Three.js|Three.js]]`, `[[Segments.ai|Segments.ai]]`, `BIM Datasets` - **Contradictions/Notes:** 컴퓨트 셰이더는 엄청난 성능 향상을 제공하지만 구형 API인 WebGL이나 WebGL 2에서는 지원되지 않아 WebGPU 환경이 필수적입니다 [1]. 또한 GPU 최적화를 제대로 다루지 못해 동기화 대기(`await mapAsync()`)를 남용할 경우, 오히려 GPU가 최대 60%의 시간 동안 유휴 상태(Idle)에 빠지는 병목 현상을 유발할 수 있습니다 [18]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Compute Shaders.md]] +- Raw Source: 00_Raw/2026-04-20/Compute Shaders.md --- diff --git a/01_Archive/2026-04-20/Computer Vision.md b/01_Archive/2026-04-20/Computer Vision.md index d087c555..91e3ef79 100644 --- a/01_Archive/2026-04-20/Computer Vision.md +++ b/01_Archive/2026-04-20/Computer Vision.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-4D80EC -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Computer Vision" --- -# [[Computer Vision]] +# [[Computer Vision|Computer Vision]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Computer Vision" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Computer Vision.md]] +- Raw Source: 00_Raw/2026-04-20/Computer Vision.md --- diff --git a/01_Archive/2026-04-20/Computer-Aided-Design (CAD).md b/01_Archive/2026-04-20/Computer-Aided-Design (CAD).md index e4ef2ac1..8cdfbc4d 100644 --- a/01_Archive/2026-04-20/Computer-Aided-Design (CAD).md +++ b/01_Archive/2026-04-20/Computer-Aided-Design (CAD).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-518851 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Computer-Aided-Design (CAD)" --- -# [[Computer-Aided-Design (CAD)]] +# [[Computer-Aided-Design (CAD)|Computer-Aided-Design (CAD)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Computer-Aided-Design (CAD)" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Computer-Aided-Design (CAD).md]] +- Raw Source: 00_Raw/2026-04-20/Computer-Aided-Design (CAD).md --- diff --git a/01_Archive/2026-04-20/Computer-Vision-Synthesis.md b/01_Archive/2026-04-20/Computer-Vision-Synthesis.md index 59af25e9..187d2b56 100644 --- a/01_Archive/2026-04-20/Computer-Vision-Synthesis.md +++ b/01_Archive/2026-04-20/Computer-Vision-Synthesis.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-C1EBB8 -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Computer-Vision-Synthesis" --- -# [[Computer-Vision-Synthesis]] +# [[Computer-Vision-Synthesis|Computer-Vision-Synthesis]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Computer-Vision-Synthesis" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Computer-Vision-Synthesis.md]] +- Raw Source: 00_Raw/2026-04-20/Computer-Vision-Synthesis.md --- diff --git a/01_Archive/2026-04-20/Computer_Vision.md b/01_Archive/2026-04-20/Computer_Vision.md index 503fe54e..56e13990 100644 --- a/01_Archive/2026-04-20/Computer_Vision.md +++ b/01_Archive/2026-04-20/Computer_Vision.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AI-001 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.97 tags: [ai, computer-vision, cnn, transformer] last_reinforced: 2026-04-20 github_commit: "batch-reinforce-03" --- -# [[Computer Vision]] +# [[Computer Vision|Computer Vision]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 디지털 이미지와 비디오에서 고차원적인 의미를 추출하여 기계가 세상을 '보고' '이해하게' 만드는 AI의 감각 기관. @@ -24,6 +24,6 @@ github_commit: "batch-reinforce-03" - **정책 변화:** 기술적 정확도(w1)와 윤리적 프라이버시 보호의 가중치 균형 조절. ## 🔗 지식 연결 (Graph) -- **Parent:** [[10_Wiki/💡 Topics/AI]] -- **Related:** [[CV_Synthesis]], [[Object-Detection]], [[CNN]] -- **Raw Source:** [[00_Raw/2026-04-20/Computer Vision.md]] +- **Parent:** 10_Wiki/💡 Topics/AI +- **Related:** [[CV_Synthesis|CV_Synthesis]], Object-Detection, CNN +- **Raw Source:** 00_Raw/2026-04-20/Computer Vision.md diff --git a/01_Archive/2026-04-20/Concept Drift (개념 드리프트).md b/01_Archive/2026-04-20/Concept Drift (개념 드리프트).md index ecddf505..28138a02 100644 --- a/01_Archive/2026-04-20/Concept Drift (개념 드리프트).md +++ b/01_Archive/2026-04-20/Concept Drift (개념 드리프트).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-63C90D -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Concept Drift (개념 드리프트)" --- -# [[Concept Drift (개념 드리프트)]] +# [[Concept Drift (개념 드리프트)|Concept Drift (개념 드리프트)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Concept Drift (개념 드리 ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Concept Drift (개념 드리프트).md]] +- Raw Source: 00_Raw/2026-04-20/Concept Drift (개념 드리프트).md --- diff --git a/01_Archive/2026-04-20/Concept Drift (개념 드리프트, 모델 지식의 부패).md b/01_Archive/2026-04-20/Concept Drift (개념 드리프트, 모델 지식의 부패).md index d9244c6d..25b7b154 100644 --- a/01_Archive/2026-04-20/Concept Drift (개념 드리프트, 모델 지식의 부패).md +++ b/01_Archive/2026-04-20/Concept Drift (개념 드리프트, 모델 지식의 부패).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AI-047 -category: "[[10_Wiki/💡 Topics/AI & ML MLOps]]" +category: "10_Wiki/💡 Topics/AI & ML MLOps" confidence_score: 0.96 tags: [ai, machine learning, mlops, data science] last_reinforced: 2026-06-XX github_commit: "[P-Reinforce] Processed Concept Drift (개념 드리프트)." --- -# [[Concept Drift (개념 드리프트)]] +# [[Concept Drift (개념 드리프트)|Concept Drift (개념 드리프트)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 시간이 지남에 따라 데이터의 통계적 특성이나 생성 메커니즘 자체가 변화하여, 이전에 학습된 AI 모델의 예측 정확도와 신뢰도가 점진적으로 떨어지는 현상이다. @@ -26,7 +26,7 @@ github_commit: "[P-Reinforce] Processed Concept Drift (개념 드리프트)." - **정책 변화:** 최근에는 설명 가능한 AI (XAI) 기법을 결합하여, 모델이 왜 성능 저하를 겪고 있는지 '어떤 개념'에서 벗어났는지 진단하는 것이 중요해지고 있다. ## 🔗 지식 연결 (Graph) -- Parent: [[Model Collapse (모델 붕괴 현상)]] -- Related: [[MLOps]] , [[Data Science in UX]] , [[Continuous Monitoring]] -- Raw Source: [[00_Raw/Concept Drift (개념 드리프트).md]] +- Parent: [[Model Collapse (모델 붕괴 현상)|Model Collapse (모델 붕괴 현상)]] +- Related: [[MLOps|MLOps]] , [[Data-Science-in-UX|Data Science in UX]] , Continuous Monitoring +- Raw Source: 00_Raw/Concept Drift (개념 드리프트).md --- \ No newline at end of file diff --git a/01_Archive/2026-04-20/Concrete Syntax Tree (CST).md b/01_Archive/2026-04-20/Concrete Syntax Tree (CST).md index 4525aa08..e1af9738 100644 --- a/01_Archive/2026-04-20/Concrete Syntax Tree (CST).md +++ b/01_Archive/2026-04-20/Concrete Syntax Tree (CST).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-858963 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Concrete Syntax Tree (CST)" --- -# [[Concrete Syntax Tree (CST)]] +# [[Concrete Syntax Tree (CST)|Concrete Syntax Tree (CST)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > Concrete Syntax Tree (CST)는 파스 트리(Parse Tree)라고도 불리며, 문맥 자유 문법(context-free grammar)의 트리 표현 형태로 컴파일러가 코드를 이해하는 방식을 보여주는 공식적인 구조이다 [1]. 추상 구문 트리(AST)와 달리 구문적 요소뿐만 아니라 미세한 문체, 어휘, 레이아웃(들여쓰기 등) 세부 사항까지 코드의 모든 측면을 정밀하게 포착한다 [2]. 이러한 구체적 특성 때문에 코드 포맷팅 등 소스 코드가 변환될 때 그 형태가 크게 변경되며, 최근 코드 작성자를 식별하는 기계 학습 기반의 코드 스타일로메트리(Code Stylometry) 모델에서 중요하게 활용되고 있다 [3, 4]. @@ -23,11 +23,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Concrete Syntax Tree (CST)" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Abstract Syntax Tree (AST)]], [[Code Stylometry]], [[Parse Tree]] +- **Related Topics:** [[Abstract Syntax Tree (AST)|Abstract Syntax Tree (AST)]], [[Code Stylometry (코드 문체론)|Code Stylometry]], Parse Tree - **Projects/Contexts:** 프로그래머의 코드 작성 스타일을 분석하여 작성자를 식별하는 코드 스타일로메트리 연구에서, 코드 포맷팅(formatting) 및 축소(minification) 기술이 식별 정확도에 미치는 영향을 측정하기 위한 코드 표현 방식으로 사용됨 [3, 12, 13]. - **Contradictions/Notes:** 소스에 관련 정보가 부족합니다. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Concrete Syntax Tree (CST).md]] +- Raw Source: 00_Raw/2026-04-20/Concrete Syntax Tree (CST).md --- diff --git a/01_Archive/2026-04-20/Conditional-Types.md b/01_Archive/2026-04-20/Conditional-Types.md index 392e24ad..f9cc8ac2 100644 --- a/01_Archive/2026-04-20/Conditional-Types.md +++ b/01_Archive/2026-04-20/Conditional-Types.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-F3246D -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Conditional-Types" --- -# [[Conditional-Types]] +# [[Conditional-Types|Conditional-Types]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Conditional-Types" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Conditional-Types.md]] +- Raw Source: 00_Raw/2026-04-20/Conditional-Types.md --- diff --git a/01_Archive/2026-04-20/Connect AI 기술 문서 및 사용 설명서.md b/01_Archive/2026-04-20/Connect AI 기술 문서 및 사용 설명서.md index bf563d14..a8fc786f 100644 --- a/01_Archive/2026-04-20/Connect AI 기술 문서 및 사용 설명서.md +++ b/01_Archive/2026-04-20/Connect AI 기술 문서 및 사용 설명서.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-D1D238 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Connect AI 기술 문서 및 사용 설명서" --- -# [[Connect AI 기술 문서 및 사용 설명서]] +# [[Connect AI 기술 문서 및 사용 설명서|Connect AI 기술 문서 및 사용 설명서]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Connect AI 기술 문서 및 ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Connect AI 기술 문서 및 사용 설명서.md]] +- Raw Source: 00_Raw/2026-04-20/Connect AI 기술 문서 및 사용 설명서.md --- diff --git a/01_Archive/2026-04-20/Connect AI 시스템 아키텍처 및 데이터 흐름 분석.md b/01_Archive/2026-04-20/Connect AI 시스템 아키텍처 및 데이터 흐름 분석.md index 612aad98..51bd9c43 100644 --- a/01_Archive/2026-04-20/Connect AI 시스템 아키텍처 및 데이터 흐름 분석.md +++ b/01_Archive/2026-04-20/Connect AI 시스템 아키텍처 및 데이터 흐름 분석.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-3841AD -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Connect AI 시스템 아키텍처 및 데이터 흐름 분석" --- -# [[Connect AI 시스템 아키텍처 및 데이터 흐름 분석]] +# [[Connect AI 시스템 아키텍처 및 데이터 흐름 분석|Connect AI 시스템 아키텍처 및 데이터 흐름 분석]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Connect AI 시스템 아키텍 ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Connect AI 시스템 아키텍처 및 데이터 흐름 분석.md]] +- Raw Source: 00_Raw/2026-04-20/Connect AI 시스템 아키텍처 및 데이터 흐름 분석.md --- diff --git a/01_Archive/2026-04-20/Conscientiousness.md b/01_Archive/2026-04-20/Conscientiousness.md index 27a51e59..05f76683 100644 --- a/01_Archive/2026-04-20/Conscientiousness.md +++ b/01_Archive/2026-04-20/Conscientiousness.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-04F596 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Conscientiousness" --- -# [[Conscientiousness]] +# [[Conscientiousness|Conscientiousness]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Conscientiousness" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Conscientiousness.md]] +- Raw Source: 00_Raw/2026-04-20/Conscientiousness.md --- diff --git a/01_Archive/2026-04-20/Constitutional AI (헌법 AI).md b/01_Archive/2026-04-20/Constitutional AI (헌법 AI).md index 39f11a2d..eb3add67 100644 --- a/01_Archive/2026-04-20/Constitutional AI (헌법 AI).md +++ b/01_Archive/2026-04-20/Constitutional AI (헌법 AI).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-938CE2 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Constitutional AI (헌법 AI)" --- -# [[Constitutional AI (헌법 AI)]] +# [[Constitutional AI (헌법 AI)|Constitutional AI (헌법 AI)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Constitutional AI (헌법 AI)" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Constitutional AI (헌법 AI).md]] +- Raw Source: 00_Raw/2026-04-20/Constitutional AI (헌법 AI).md --- diff --git a/01_Archive/2026-04-20/Constraint Satisfaction Problems (CSP).md b/01_Archive/2026-04-20/Constraint Satisfaction Problems (CSP).md index 99a95409..09ee53ad 100644 --- a/01_Archive/2026-04-20/Constraint Satisfaction Problems (CSP).md +++ b/01_Archive/2026-04-20/Constraint Satisfaction Problems (CSP).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-075C49 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Constraint Satisfaction Problems (CSP)" --- -# [[Constraint Satisfaction Problems (CSP)]] +# [[Constraint Satisfaction Problems (CSP)|Constraint Satisfaction Problems (CSP)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Constraint Satisfaction Proble ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Constraint Satisfaction Problems (CSP).md]] +- Raw Source: 00_Raw/2026-04-20/Constraint Satisfaction Problems (CSP).md --- diff --git a/01_Archive/2026-04-20/Constraint-Satisfaction-Problems.md b/01_Archive/2026-04-20/Constraint-Satisfaction-Problems.md index 98fd2db3..f0d47c5c 100644 --- a/01_Archive/2026-04-20/Constraint-Satisfaction-Problems.md +++ b/01_Archive/2026-04-20/Constraint-Satisfaction-Problems.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-BE1BD5 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Constraint-Satisfaction-Problems" --- -# [[Constraint-Satisfaction-Problems]] +# [[Constraint-Satisfaction-Problems|Constraint-Satisfaction-Problems]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Constraint-Satisfaction-Proble ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Constraint-Satisfaction-Problems.md]] +- Raw Source: 00_Raw/2026-04-20/Constraint-Satisfaction-Problems.md --- diff --git a/01_Archive/2026-04-20/Content-Strategy.md b/01_Archive/2026-04-20/Content-Strategy.md index 15ab5375..6ecf76e8 100644 --- a/01_Archive/2026-04-20/Content-Strategy.md +++ b/01_Archive/2026-04-20/Content-Strategy.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-ED632C -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Content-Strategy" --- -# [[Content-Strategy]] +# [[Content-Strategy|Content-Strategy]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Content-Strategy" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Content-Strategy.md]] +- Raw Source: 00_Raw/2026-04-20/Content-Strategy.md --- diff --git a/01_Archive/2026-04-20/Continuous Integration (CI).md b/01_Archive/2026-04-20/Continuous Integration (CI).md index d167187e..531e1243 100644 --- a/01_Archive/2026-04-20/Continuous Integration (CI).md +++ b/01_Archive/2026-04-20/Continuous Integration (CI).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-F896F7 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Continuous Integration (CI)" --- -# [[Continuous Integration (CI)]] +# [[Continuous Integration (CI)|Continuous Integration (CI)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지속적 통합(Continuous Integration, CI)은 소프트웨어 개발 수명 주기에서 코드 변경 사항이 발생할 때 이를 자동으로 검사하고 빌드하는 파이프라인입니다 [1, 2]. 개발자의 로컬 환경에서 우회될 수 있는 검사들을 강제하는 '안전망(Safety net)'이자 최종 권한(Final authority) 역할을 수행합니다 [2, 3]. CI 환경에서는 정적 애플리케이션 보안 테스트(SAST), 린팅(Linting), 전체 테스트 스위트 실행 등을 통해 프로덕션 환경에 배포되기 전 코드의 품질과 보안을 엄격하게 관리합니다 [4, 5]. @@ -23,11 +23,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Continuous Integration (CI)" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Static Application Security Testing (SAST)]], [[Code Review]], [[Git Hooks]], [[Quality Gates]], [[Pull Request (PR)]] -- **Projects/Contexts:** [[TeamCity]], [[GitHub Actions]], [[GitLab CI]], [[Jenkins]], [[Azure DevOps]]와 같이 코드 통합과 자동화 빌드를 관장하는 인프라 환경 [1, 9, 14]. +- **Related Topics:** [[Static Application Security Testing (SAST)|Static Application Security Testing (SAST)]], [[Code Review|Code Review]], [[Git Hooks|Git Hooks]], [[Quality Gates|Quality Gates]], [[Pull Request (PR)|Pull Request (PR)]] +- **Projects/Contexts:** [[TeamCity|TeamCity]], [[GitHub Actions|GitHub Actions]], [[GitLab CI|GitLab CI]], [[Jenkins|Jenkins]], [[Azure DevOps|Azure DevOps]]와 같이 코드 통합과 자동화 빌드를 관장하는 인프라 환경 [1, 9, 14]. - **Contradictions/Notes:** 로컬 Git 훅(pre-commit 등)은 로컬 환경에서 빠른 피드백을 제공하여 시간을 절약하게 해주지만, 우회가 가능하므로 CI를 완전히 대체할 수 없으며 반드시 CI 파이프라인을 통한 최종 검증이 병행되어야 합니다 [2, 4, 15]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/Continuous Integration (CI).md]] +- Raw Source: 00_Raw/2026-04-20/Continuous Integration (CI).md --- diff --git a/01_Archive/2026-04-20/Continuous-Discovery.md b/01_Archive/2026-04-20/Continuous-Discovery.md index d38db15f..13f2cf34 100644 --- a/01_Archive/2026-04-20/Continuous-Discovery.md +++ b/01_Archive/2026-04-20/Continuous-Discovery.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-8E53F2 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Continuous-Discovery" --- -# [[Continuous-Discovery]] +# [[Continuous-Discovery|Continuous-Discovery]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Continuous-Discovery" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Continuous-Discovery.md]] +- Raw Source: 00_Raw/2026-04-20/Continuous-Discovery.md --- diff --git a/01_Archive/2026-04-20/Contract-Driven-Development.md b/01_Archive/2026-04-20/Contract-Driven-Development.md index cd13c8f7..fa6360ce 100644 --- a/01_Archive/2026-04-20/Contract-Driven-Development.md +++ b/01_Archive/2026-04-20/Contract-Driven-Development.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-1F7EE7 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Contract-Driven-Development" --- -# [[Contract-Driven-Development]] +# [[Contract-Driven-Development|Contract-Driven-Development]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Contract-Driven-Development" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Contract-Driven-Development.md]] +- Raw Source: 00_Raw/2026-04-20/Contract-Driven-Development.md --- diff --git a/01_Archive/2026-04-20/Contract-First-Development.md b/01_Archive/2026-04-20/Contract-First-Development.md index d7b5a5d2..e04afc85 100644 --- a/01_Archive/2026-04-20/Contract-First-Development.md +++ b/01_Archive/2026-04-20/Contract-First-Development.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-B0C45D -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Contract-First-Development" --- -# [[Contract-First-Development]] +# [[Contract-First-Development|Contract-First-Development]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Contract-First-Development" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Contract-First-Development.md]] +- Raw Source: 00_Raw/2026-04-20/Contract-First-Development.md --- diff --git a/01_Archive/2026-04-20/Contract-Testing.md b/01_Archive/2026-04-20/Contract-Testing.md index 723cbd87..d0cad0c5 100644 --- a/01_Archive/2026-04-20/Contract-Testing.md +++ b/01_Archive/2026-04-20/Contract-Testing.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-7A6306 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Contract-Testing" --- -# [[Contract-Testing]] +# [[Contract-Testing|Contract-Testing]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Contract-Testing" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Contract-Testing.md]] +- Raw Source: 00_Raw/2026-04-20/Contract-Testing.md --- diff --git a/01_Archive/2026-04-20/Contravariance-and-Covariance.md b/01_Archive/2026-04-20/Contravariance-and-Covariance.md index e2dc2dbc..a49bf947 100644 --- a/01_Archive/2026-04-20/Contravariance-and-Covariance.md +++ b/01_Archive/2026-04-20/Contravariance-and-Covariance.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-62A6A2 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Contravariance-and-Covariance" --- -# [[Contravariance-and-Covariance]] +# [[Contravariance-and-Covariance|Contravariance-and-Covariance]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Contravariance-and-Covariance" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Contravariance-and-Covariance.md]] +- Raw Source: 00_Raw/2026-04-20/Contravariance-and-Covariance.md --- diff --git a/01_Archive/2026-04-20/Control Systems Engineering.md b/01_Archive/2026-04-20/Control Systems Engineering.md index f2ac1e18..a72cebca 100644 --- a/01_Archive/2026-04-20/Control Systems Engineering.md +++ b/01_Archive/2026-04-20/Control Systems Engineering.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-5DA236 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Control Systems Engineering" --- -# [[Control Systems Engineering]] +# [[Control Systems Engineering|Control Systems Engineering]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Control Systems Engineering" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Control Systems Engineering.md]] +- Raw Source: 00_Raw/2026-04-20/Control Systems Engineering.md --- diff --git a/01_Archive/2026-04-20/Control-Flow-Analysis.md b/01_Archive/2026-04-20/Control-Flow-Analysis.md index 8f082b6e..2ec649c2 100644 --- a/01_Archive/2026-04-20/Control-Flow-Analysis.md +++ b/01_Archive/2026-04-20/Control-Flow-Analysis.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-452CC1 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Control-Flow-Analysis" --- -# [[Control-Flow-Analysis]] +# [[Control-Flow-Analysis|Control-Flow-Analysis]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Control-Flow-Analysis" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Control-Flow-Analysis.md]] +- Raw Source: 00_Raw/2026-04-20/Control-Flow-Analysis.md --- diff --git a/01_Archive/2026-04-20/Control-Theory.md b/01_Archive/2026-04-20/Control-Theory.md index e8118f80..d9da01e4 100644 --- a/01_Archive/2026-04-20/Control-Theory.md +++ b/01_Archive/2026-04-20/Control-Theory.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-35251E -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Control-Theory" --- -# [[Control-Theory]] +# [[Control-Theory|Control-Theory]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Control-Theory" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Control-Theory.md]] +- Raw Source: 00_Raw/2026-04-20/Control-Theory.md --- diff --git a/01_Archive/2026-04-20/Conway's On Numbers and Games.md b/01_Archive/2026-04-20/Conway's On Numbers and Games.md index addb3dd9..3b2bb2e5 100644 --- a/01_Archive/2026-04-20/Conway's On Numbers and Games.md +++ b/01_Archive/2026-04-20/Conway's On Numbers and Games.md @@ -1,4 +1,4 @@ -[[Conway's On Numbers and Games]] +[[Conway's On Numbers and Games|Conway's On Numbers and Games]] 📌 Brief Summary *On Numbers and Games* (ONAG), authored by John Horton Conway in 1976, is a foundational treatise in combinatorial game theory. It introduces the concept of "surreal numbers," an algebraically closed field that encompasses both the real numbers and infinitely large/infinitesimal quantities, constructed through a recursive process of defining numbers via sets of previously defined numbers. @@ -9,8 +9,8 @@ * **The Role of Infinitesimals:** A significant contribution of ONAG is the formalization of infinitesimals within a rigorous, non-standard analytic context. By treating $\epsilon$ (an infinitesimal) and $\omega$ (an infinite ordinal) as algebraic entities that obey standard arithmetic laws, Conway provided a toolset for analyzing games that may last an infinite number of moves or possess "fuzzy" values (games that are neither greater than, less than, nor equal to zero). 🔗 Knowledge Connections -* Related Topics: [[Combinatorial Game Theory]], [[Surreal Numbers]], [[Transfinite Induction]], [[Non-standard Analysis]] -* Projects/Contexts: [[The construction of the field of Surreal Numbers]], [[Analysis of impartial and partizan games (e.g., Hackenbush, Go, Chess)]] +* Related Topics: [[Combinatorial Game Theory|Combinatorial Game Theory]], [[Surreal Numbers|Surreal Numbers]], Transfinite Induction, Non-standard Analysis +* Projects/Contexts: The construction of the field of Surreal Numbers, Analysis of impartial and partizan games (e.g., Hackenbush, Go, Chess) * Contradictions/Notes: While ONAG provides the algebraic foundation for surreal numbers, modern computational implementations often use more efficient "dyadic" representations rather than the full set-theoretic construction to avoid the complexities of transfinite induction in finite memory. Last updated: 2026-04-16 \ No newline at end of file diff --git a/01_Archive/2026-04-20/Conways On Numbers and Games.md b/01_Archive/2026-04-20/Conways On Numbers and Games.md index 3e6033d6..16679330 100644 --- a/01_Archive/2026-04-20/Conways On Numbers and Games.md +++ b/01_Archive/2026-04-20/Conways On Numbers and Games.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-6026CC -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Conways On Numbers and Games" --- -# [[Conways On Numbers and Games]] +# [[Conways On Numbers and Games|Conways On Numbers and Games]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Conways On Numbers and Games" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Conway's On Numbers and Games.md]] +- Raw Source: 00_Raw/2026-04-20/Conway's On Numbers and Games.md --- diff --git a/01_Archive/2026-04-20/Core Web Vitals.md b/01_Archive/2026-04-20/Core Web Vitals.md index 781e035a..6ffb154a 100644 --- a/01_Archive/2026-04-20/Core Web Vitals.md +++ b/01_Archive/2026-04-20/Core Web Vitals.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AI-045 -category: "[[10_Wiki/💡 Topics/Design & Web Performance]]" +category: "10_Wiki/💡 Topics/Design & Web Performance" confidence_score: 0.98 tags: [web, performance, web vitals, user experience] last_reinforced: 2026-06-XX github_commit: "[P-Reinforce] Processed Core_Web_Vitals.md" --- -# [[Core Web Vitals]] (핵심 웹 지표) +# [[Core Web Vitals|Core Web Vitals]] (핵심 웹 지표) ## 📌 한 줄 통찰 (The Karpathy Summary) > 구글이 제시하는 사용자 경험 중심의 핵심 측정 기준들로, 단순한 기술 스펙을 넘어 실제 사용자가 체감하는 페이지 로딩 속도와 인터랙션 품질을 종합적으로 평가한다. @@ -25,7 +25,7 @@ github_commit: "[P-Reinforce] Processed Core_Web_Vitals.md" - **정책 변화:** 기술적 개선(예: WebGPU 도입)만큼이나 사용자에게 이 성능 향상을 어떻게 인지시키고 가치를 전달할 것인지(UX 측면)가 중요해지고 있다. ## 🔗 지식 연결 (Graph) -- Parent: [[Web Performance Optimization]] -- Related: [[Largest Contentful Paint (LCP)]] , [[Interaction to Next Paint (INP)]] , [[Cumulative Layout Shift (CLS)]] -- Raw Source: [[00_Raw/Core_Web_Vitals.md]] +- Parent: [[Web Performance Optimization|Web Performance Optimization]] +- Related: [[Largest Contentful Paint (LCP)|Largest Contentful Paint (LCP)]] , [[Interaction to Next Paint (INP)|Interaction to Next Paint (INP)]] , [[Cumulative Layout Shift (CLS)|Cumulative Layout Shift (CLS)]] +- Raw Source: 00_Raw/Core_Web_Vitals.md --- \ No newline at end of file diff --git a/01_Archive/2026-04-20/Corgea.md b/01_Archive/2026-04-20/Corgea.md index a059f4d2..98ec780d 100644 --- a/01_Archive/2026-04-20/Corgea.md +++ b/01_Archive/2026-04-20/Corgea.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-DA5E03 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Corgea" --- -# [[Corgea]] +# [[Corgea|Corgea]] ## 📌 한 줄 통찰 (The Karpathy Summary) > Corgea는 대형 언어 모델(LLM)을 사후 스캔 분류가 아닌 핵심 스캐닝 엔진의 일부로 직접 활용하는 AI 네이티브 정적 애플리케이션 보안 테스트(SAST) 플랫폼입니다 [1]. 패턴 기반 스캐너가 놓치기 쉬운 복잡한 비즈니스 로직 결함을 깊이 있게 이해하고, 5% 미만의 낮은 오탐지율(False Positive rate)을 달성하여 기존 SAST 도구의 노이즈 문제를 해결합니다 [1-4]. 20개 이상의 언어를 지원하며, 검증된 AI 자동 수정(Auto-fix) 기능을 개발자의 작업 흐름(IDE 및 PR) 내에 직접 제공하는 것이 특징입니다 [2, 3]. @@ -24,11 +24,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Corgea" - **정책 변화:** AI 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[SAST]], [[LLM]], [[PolicyIQ]], [[Reachability Analysis]] -- **Projects/Contexts:** [[Latio.tech Report]], [[Best SAST Tools in 2026]] +- **Related Topics:** [[SAST|SAST]], [[LLM|LLM]], [[PolicyIQ|PolicyIQ]], [[Reachability Analysis|Reachability Analysis]] +- **Projects/Contexts:** [[Latio.tech Report|Latio.tech Report]], [[Best SAST Tools in 2026|Best SAST Tools in 2026]] - **Contradictions/Notes:** 독립적인 평가(Latio.tech)에서 최고의 자동 수정 도구로 극찬을 받았으나, 신생 플랫폼인 탓에 다양한 객관적 벤치마킹 자료가 아직 부족하다는 점이 동시에 지적되고 있습니다 [3, 6]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/Corgea.md]] +- Raw Source: 00_Raw/2026-04-20/Corgea.md --- diff --git a/01_Archive/2026-04-20/Corporate-LMS-Training.md b/01_Archive/2026-04-20/Corporate-LMS-Training.md index a3555e87..e5ab5e3c 100644 --- a/01_Archive/2026-04-20/Corporate-LMS-Training.md +++ b/01_Archive/2026-04-20/Corporate-LMS-Training.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-51DD02 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Corporate-LMS-Training" --- -# [[Corporate-LMS-Training]] +# [[Corporate-LMS-Training|Corporate-LMS-Training]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Corporate-LMS-Training" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Corporate-LMS-Training.md]] +- Raw Source: 00_Raw/2026-04-20/Corporate-LMS-Training.md --- diff --git a/01_Archive/2026-04-20/Cosmos 플랫폼 (Netflix).md b/01_Archive/2026-04-20/Cosmos 플랫폼 (Netflix).md index 2ce4f8ca..594ad5a8 100644 --- a/01_Archive/2026-04-20/Cosmos 플랫폼 (Netflix).md +++ b/01_Archive/2026-04-20/Cosmos 플랫폼 (Netflix).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-5C7CCB -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Cosmos 플랫폼 (Netflix)" --- -# [[Cosmos 플랫폼 (Netflix)]] +# [[Cosmos 플랫폼 (Netflix)|Cosmos 플랫폼 (Netflix)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > Cosmos는 넷플릭스(Netflix)가 마이크로서비스, 비동기 워크플로우, 서버리스 함수의 장점을 결합하여 구축한 컴퓨팅 플랫폼이다 [1]. 기존 모놀리식 아키텍처인 'Reloaded'의 한계를 극복하고 관측성, 모듈성, 생산성, 지속적 배포(Continuous Delivery)를 향상시키기 위해 개발되었다 [2, 3]. 수 분에서 수년에 걸쳐 실행되는 복잡한 계층적 워크플로우 및 리소스 집약적인 알고리즘을 조율하는 데 최적화되어 있으며, 대규모 처리량과 지연 시간에 민감한 작업 부하를 모두 지원한다 [1]. @@ -26,11 +26,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Cosmos 플랫폼 (Netflix)" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[마이크로서비스 (Microservices)]], [[서버리스 컴퓨팅 (Serverless Computing)]], [[관심사의 분리 (Separation of Concerns)]] -- **Projects/Contexts:** [[Reloaded]], [[Optimus]], [[Plato]], [[Stratum]], [[Timestone]], [[Tapas]], [[Sagan]] +- **Related Topics:** 마이크로서비스 (Microservices), [[서버리스 컴퓨팅(Serverless Computing)|서버리스 컴퓨팅 (Serverless Computing)]], [[관심사의 분리 (Separation of Concerns)|관심사의 분리 (Separation of Concerns)]] +- **Projects/Contexts:** [[리로디드(Reloaded)|Reloaded]], Optimus, Plato, Stratum, Timestone, [[타파스(Tapas)|Tapas]], Sagan - **Contradictions/Notes:** "서버리스 함수를 조율하는 워크플로우를 트리거하는 마이크로서비스"라는 Cosmos의 프로그래밍 모델은 강력하지만, 단순한 애플리케이션에 적용하기에는 부가되는 복잡성이 이점보다 클 수 있다는 점이 지적된다 [14]. 또한, Cosmos 플랫폼 도입 당시 애플리케이션 개발자들은 일관성과 신뢰성을 획득하는 대신 일정한 유연성을 포기하는 방향으로 마인드셋을 전환해야 했다 [14]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/Cosmos 플랫폼 (Netflix).md]] +- Raw Source: 00_Raw/2026-04-20/Cosmos 플랫폼 (Netflix).md --- diff --git a/01_Archive/2026-04-20/Covariance-and-Contravariance.md b/01_Archive/2026-04-20/Covariance-and-Contravariance.md index bd536fd3..283f331b 100644 --- a/01_Archive/2026-04-20/Covariance-and-Contravariance.md +++ b/01_Archive/2026-04-20/Covariance-and-Contravariance.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-1D016B -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Covariance-and-Contravariance" --- -# [[Covariance-and-Contravariance]] +# [[Covariance-and-Contravariance|Covariance-and-Contravariance]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Covariance-and-Contravariance" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Covariance-and-Contravariance.md]] +- Raw Source: 00_Raw/2026-04-20/Covariance-and-Contravariance.md --- diff --git a/01_Archive/2026-04-20/CrUX.md b/01_Archive/2026-04-20/CrUX.md index 54c29841..c4da9b24 100644 --- a/01_Archive/2026-04-20/CrUX.md +++ b/01_Archive/2026-04-20/CrUX.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-DESIGN-005 -category: "[[10_Wiki/💡 Topics/Design]]" +category: "10_Wiki/💡 Topics/Design" confidence_score: 0.89 tags: [design, web, ux, performance, crux] last_reinforced: 2026-04-20 github_commit: "batch-reinforce-07" --- -# [[Chrome User Experience Report (CrUX)]] +# [[Chrome User Experience Report (CrUX)|Chrome User Experience Report (CrUX)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 실제 사용자가 웹에서 느끼는 속도와 사용성을 데이터로 입증하며 제품 개선의 근거를 제시하는 성능 리포트. @@ -24,6 +24,6 @@ github_commit: "batch-reinforce-07" - **정책 변화:** 사용자 만족도(w3) 측정 시 CrUX 리포트의 성능 지표를 가중치로 적극 반영. ## 🔗 지식 연결 (Graph) -- **Parent:** [[10_Wiki/💡 Topics/Design]] -- **Related:** [[Core-Web-Vitals]], [[Performance-Optimization]], [[UX-Design]] -- **Raw Source:** [[00_Raw/2026-04-20/Chrome User Experience Report (CrUX).md]] +- **Parent:** 10_Wiki/💡 Topics/Design +- **Related:** [[Core-Web-Vitals|Core-Web-Vitals]], [[Performance Optimization|Performance-Optimization]], [[사용자 경험 디자인 (UX Design)|UX-Design]] +- **Raw Source:** 00_Raw/2026-04-20/Chrome User Experience Report (CrUX).md diff --git a/01_Archive/2026-04-20/Creative Process.md b/01_Archive/2026-04-20/Creative Process.md index 8ae7245a..145a36e3 100644 --- a/01_Archive/2026-04-20/Creative Process.md +++ b/01_Archive/2026-04-20/Creative Process.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-DF48CA -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Creative Process" --- -# [[Creative Process]] +# [[Creative Process|Creative Process]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Creative Process" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Creative Process.md]] +- Raw Source: 00_Raw/2026-04-20/Creative Process.md --- diff --git a/01_Archive/2026-04-20/Creativity Research.md b/01_Archive/2026-04-20/Creativity Research.md index 64a5f756..b1d87f79 100644 --- a/01_Archive/2026-04-20/Creativity Research.md +++ b/01_Archive/2026-04-20/Creativity Research.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-3C4B46 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Creativity Research" --- -# [[Creativity Research]] +# [[Creativity Research|Creativity Research]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Creativity Research" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Creativity Research.md]] +- Raw Source: 00_Raw/2026-04-20/Creativity Research.md --- diff --git a/01_Archive/2026-04-20/Creativity-and-Cognitive-Complexity.md b/01_Archive/2026-04-20/Creativity-and-Cognitive-Complexity.md index 4b31371d..f95166ee 100644 --- a/01_Archive/2026-04-20/Creativity-and-Cognitive-Complexity.md +++ b/01_Archive/2026-04-20/Creativity-and-Cognitive-Complexity.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-091CD8 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Creativity-and-Cognitive-Complexity" --- -# [[Creativity-and-Cognitive-Complexity]] +# [[Creativity-and-Cognitive-Complexity|Creativity-and-Cognitive-Complexity]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Creativity-and-Cognitive-Compl ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Creativity-and-Cognitive-Complexity.md]] +- Raw Source: 00_Raw/2026-04-20/Creativity-and-Cognitive-Complexity.md --- diff --git a/01_Archive/2026-04-20/Credit Assignment Problem.md b/01_Archive/2026-04-20/Credit Assignment Problem.md index c05018ab..dbac906b 100644 --- a/01_Archive/2026-04-20/Credit Assignment Problem.md +++ b/01_Archive/2026-04-20/Credit Assignment Problem.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-55E155 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Credit Assignment Problem" --- -# [[Credit Assignment Problem]] +# [[Credit Assignment Problem|Credit Assignment Problem]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Credit Assignment Problem" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Credit Assignment Problem.md]] +- Raw Source: 00_Raw/2026-04-20/Credit Assignment Problem.md --- diff --git a/01_Archive/2026-04-20/Critical Design.md b/01_Archive/2026-04-20/Critical Design.md index fb232a44..e57aebaf 100644 --- a/01_Archive/2026-04-20/Critical Design.md +++ b/01_Archive/2026-04-20/Critical Design.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-A653EF -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Critical Design" --- -# [[Critical Design]] +# [[Critical Design|Critical Design]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Critical Design" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Critical Design.md]] +- Raw Source: 00_Raw/2026-04-20/Critical Design.md --- diff --git a/01_Archive/2026-04-20/Critical-Play.md b/01_Archive/2026-04-20/Critical-Play.md index e42bd858..ff29761a 100644 --- a/01_Archive/2026-04-20/Critical-Play.md +++ b/01_Archive/2026-04-20/Critical-Play.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-0C480C -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Critical-Play" --- -# [[Critical-Play]] +# [[Critical-Play|Critical-Play]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Critical-Play" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Critical-Play.md]] +- Raw Source: 00_Raw/2026-04-20/Critical-Play.md --- diff --git a/01_Archive/2026-04-20/Cryptoeconomics.md b/01_Archive/2026-04-20/Cryptoeconomics.md index 17ec9c33..5f18af99 100644 --- a/01_Archive/2026-04-20/Cryptoeconomics.md +++ b/01_Archive/2026-04-20/Cryptoeconomics.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-5B4AE2 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Cryptoeconomics" --- -# [[Cryptoeconomics]] +# [[Cryptoeconomics|Cryptoeconomics]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Cryptoeconomics" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Cryptoeconomics.md]] +- Raw Source: 00_Raw/2026-04-20/Cryptoeconomics.md --- diff --git a/01_Archive/2026-04-20/Cultural-Heritage-Informatics.md b/01_Archive/2026-04-20/Cultural-Heritage-Informatics.md index 93a5c5c7..c446c89a 100644 --- a/01_Archive/2026-04-20/Cultural-Heritage-Informatics.md +++ b/01_Archive/2026-04-20/Cultural-Heritage-Informatics.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-90A1AA -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Cultural-Heritage-Informatics" --- -# [[Cultural-Heritage-Informatics]] +# [[Cultural-Heritage-Informatics|Cultural-Heritage-Informatics]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Cultural-Heritage-Informatics" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Cultural-Heritage-Informatics.md]] +- Raw Source: 00_Raw/2026-04-20/Cultural-Heritage-Informatics.md --- diff --git a/01_Archive/2026-04-20/Cumulative Layout Shift (CLS).md b/01_Archive/2026-04-20/Cumulative Layout Shift (CLS).md index fa5d9e8d..a8fad0bd 100644 --- a/01_Archive/2026-04-20/Cumulative Layout Shift (CLS).md +++ b/01_Archive/2026-04-20/Cumulative Layout Shift (CLS).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-C15CB2 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Cumulative Layout Shift (CLS)" --- -# [[Cumulative Layout Shift (CLS)]] +# [[Cumulative Layout Shift (CLS)|Cumulative Layout Shift (CLS)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > Cumulative Layout Shift (CLS)는 웹 페이지가 로드되는 동안 레이아웃과 콘텐츠가 얼마나 예기치 않게 이동하는지를 측정하는 시각적 안정성(Visual Stability) 지표입니다 [1, 2]. 구글의 코어 웹 바이탈(Core Web Vitals)을 구성하는 핵심 지표 중 하나로, 나중에 렌더링된 콘텐츠가 중요한 콘텐츠를 밀어내면서 발생하는 사용자 경험의 저하를 방지하기 위해 사용됩니다 [1, 2]. CLS 점수는 0.1 미만을 유지하는 것이 권장됩니다 [3]. @@ -32,11 +32,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Cumulative Layout Shift (CLS)" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Core Web Vitals]], [[Largest Contentful Paint (LCP)]], [[Interaction to Next Paint (INP)]] -- **Projects/Contexts:** [[Chrome DevTools]], [[Interop 2026]] +- **Related Topics:** [[Core Web Vitals|Core Web Vitals]], [[Largest Contentful Paint (LCP)|Largest Contentful Paint (LCP)]], [[Interaction to Next Paint (INP)|Interaction to Next Paint (INP)]] +- **Projects/Contexts:** [[Chrome DevTools|Chrome DevTools]], [[Interop 2026|Interop 2026]] - **Contradictions/Notes:** CLS 수치는 기기의 해상도에 크게 의존하기 때문에 실제 방문자 데이터를 나타내는 현장(Field) 데이터와 개발자의 로컬(Local) 데이터 간에 차이가 발생하기 쉽습니다. 이러한 이유로 코어 웹 바이탈 지표 중에서도 에뮬레이션하여 측정하기 가장 까다로운 지표로 평가받습니다 [8]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Cumulative Layout Shift (CLS).md]] +- Raw Source: 00_Raw/2026-04-20/Cumulative Layout Shift (CLS).md --- diff --git a/01_Archive/2026-04-20/Custom-ESLint-Rules-Development.md b/01_Archive/2026-04-20/Custom-ESLint-Rules-Development.md index 7efab2e7..b70ab605 100644 --- a/01_Archive/2026-04-20/Custom-ESLint-Rules-Development.md +++ b/01_Archive/2026-04-20/Custom-ESLint-Rules-Development.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-4AB505 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Custom-ESLint-Rules-Development" --- -# [[Custom-ESLint-Rules-Development]] +# [[Custom-ESLint-Rules-Development|Custom-ESLint-Rules-Development]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Custom-ESLint-Rules-Developmen ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Custom-ESLint-Rules-Development.md]] +- Raw Source: 00_Raw/2026-04-20/Custom-ESLint-Rules-Development.md --- diff --git a/01_Archive/2026-04-20/Customer-Journey-Mapping.md b/01_Archive/2026-04-20/Customer-Journey-Mapping.md index 97721ea2..c6edff1e 100644 --- a/01_Archive/2026-04-20/Customer-Journey-Mapping.md +++ b/01_Archive/2026-04-20/Customer-Journey-Mapping.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-47D82D -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Customer-Journey-Mapping" --- -# [[Customer-Journey-Mapping]] +# [[Customer-Journey-Mapping|Customer-Journey-Mapping]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Customer-Journey-Mapping" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Customer-Journey-Mapping.md]] +- Raw Source: 00_Raw/2026-04-20/Customer-Journey-Mapping.md --- diff --git a/01_Archive/2026-04-20/CyArk.md b/01_Archive/2026-04-20/CyArk.md index c7bee9bb..0a218474 100644 --- a/01_Archive/2026-04-20/CyArk.md +++ b/01_Archive/2026-04-20/CyArk.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-78F905 -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - CyArk" --- -# [[CyArk]] +# [[CyArk|CyArk]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - CyArk" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/CyArk.md]] +- Raw Source: 00_Raw/2026-04-20/CyArk.md --- diff --git a/01_Archive/2026-04-20/Cyber-Physical Systems (CPS).md b/01_Archive/2026-04-20/Cyber-Physical Systems (CPS).md index 70c6e259..dce6910b 100644 --- a/01_Archive/2026-04-20/Cyber-Physical Systems (CPS).md +++ b/01_Archive/2026-04-20/Cyber-Physical Systems (CPS).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-5C9113 -category: "[[10_Wiki/💡 Topics/Game Design]]" +category: "10_Wiki/💡 Topics/Game Design" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Cyber-Physical Systems (CPS)" --- -# [[Cyber-Physical Systems (CPS)]] +# [[Cyber-Physical Systems (CPS)|Cyber-Physical Systems (CPS)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Cyber-Physical Systems (CPS)" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Cyber-Physical Systems (CPS).md]] +- Raw Source: 00_Raw/2026-04-20/Cyber-Physical Systems (CPS).md --- diff --git a/01_Archive/2026-04-20/Cybernetics.md b/01_Archive/2026-04-20/Cybernetics.md index 735ee1a0..0acbfdbf 100644 --- a/01_Archive/2026-04-20/Cybernetics.md +++ b/01_Archive/2026-04-20/Cybernetics.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-F6EC43 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Cybernetics" --- -# [[Cybernetics]] +# [[Cybernetics|Cybernetics]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Cybernetics" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Cybernetics.md]] +- Raw Source: 00_Raw/2026-04-20/Cybernetics.md --- diff --git a/01_Archive/2026-04-20/Cybertext Theory.md b/01_Archive/2026-04-20/Cybertext Theory.md index 024f5695..9ed1955c 100644 --- a/01_Archive/2026-04-20/Cybertext Theory.md +++ b/01_Archive/2026-04-20/Cybertext Theory.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-896181 -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Cybertext Theory" --- -# [[Cybertext Theory]] +# [[Cybertext Theory|Cybertext Theory]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Cybertext Theory" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Cybertext Theory.md]] +- Raw Source: 00_Raw/2026-04-20/Cybertext Theory.md --- diff --git a/01_Archive/2026-04-20/Cybertext.md b/01_Archive/2026-04-20/Cybertext.md index 5cf77b2f..7d6c1517 100644 --- a/01_Archive/2026-04-20/Cybertext.md +++ b/01_Archive/2026-04-20/Cybertext.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-52E635 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Cybertext" --- -# [[Cybertext]] +# [[Cybertext|Cybertext]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Cybertext" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Cybertext.md]] +- Raw Source: 00_Raw/2026-04-20/Cybertext.md --- diff --git a/01_Archive/2026-04-20/Cypher 질의 언어 (Neo4j).md b/01_Archive/2026-04-20/Cypher 질의 언어 (Neo4j).md index 85c5b087..4bed62f2 100644 --- a/01_Archive/2026-04-20/Cypher 질의 언어 (Neo4j).md +++ b/01_Archive/2026-04-20/Cypher 질의 언어 (Neo4j).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-C101DD -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Cypher 질의 언어 (Neo4j)" --- -# [[Cypher 질의 언어 (Neo4j)]] +# [[Cypher 질의 언어 (Neo4j)|Cypher 질의 언어 (Neo4j)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Cypher 질의 언어 (Neo4j)" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Cypher 질의 언어 (Neo4j).md]] +- Raw Source: 00_Raw/2026-04-20/Cypher 질의 언어 (Neo4j).md --- diff --git a/01_Archive/2026-04-20/DAST (동적 애플리케이션 보안 테스트).md b/01_Archive/2026-04-20/DAST (동적 애플리케이션 보안 테스트).md index 9aae9826..f3afe7f2 100644 --- a/01_Archive/2026-04-20/DAST (동적 애플리케이션 보안 테스트).md +++ b/01_Archive/2026-04-20/DAST (동적 애플리케이션 보안 테스트).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-09DD84 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - DAST (동적 애플리케이션 보안 테스트)" --- -# [[DAST (동적 애플리케이션 보안 테스트)]] +# [[DAST (동적 애플리케이션 보안 테스트)|DAST (동적 애플리케이션 보안 테스트)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > DAST(동적 애플리케이션 보안 테스트)는 애플리케이션이 실행되는 런타임 환경에서 외부로부터 취약점을 테스트하는 블랙박스(Black-box) 테스트 기법입니다 [1, 2]. 소스 코드를 직접 분석하는 SAST와 달리 특정 프로그래밍 언어에 종속되지 않으며, 주로 소프트웨어 개발 수명 주기(SDLC)의 후반부인 스테이징이나 프로덕션 단계에 적용됩니다 [2, 3]. 이를 통해 실행 중인 애플리케이션의 실제 동작, 구성(Configuration) 문제 및 노출된 공격 표면을 관찰하여 런타임 취약점을 찾아내는 데 효과적입니다 [1, 3]. @@ -23,11 +23,11 @@ github_commit: "[P-Reinforce] Continuous Worker - DAST (동적 애플리케이 - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[SAST (정적 애플리케이션 보안 테스트)]], [[Black-box Testing]], [[Fuzzing]] -- **Projects/Contexts:** [[AppSec (애플리케이션 보안)]], [[CI/CD 파이프라인]], [[SDLC (소프트웨어 개발 수명 주기)]] +- **Related Topics:** [[SAST (정적 애플리케이션 보안 테스트)|SAST (정적 애플리케이션 보안 테스트)]], [[Black-box Testing|Black-box Testing]], [[Fuzzing|Fuzzing]] +- **Projects/Contexts:** [[AppSec (애플리케이션 보안)|AppSec (애플리케이션 보안)]], [[CI_CD 파이프라인|CI/CD 파이프라인]], [[SDLC (소프트웨어 개발 수명 주기)|SDLC (소프트웨어 개발 수명 주기)]] - **Contradictions/Notes:** 소스 내용 간의 모순은 존재하지 않으며, DAST는 코드를 직접 분석하는 SAST와 접근 방식(블랙박스 vs 화이트박스)에서 명확히 대비되지만 상호 배타적인 것이 아니라 강력한 보안 태세를 위해 함께 구축해야 하는 보완재로 설명됩니다 [4, 5]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/DAST (동적 애플리케이션 보안 테스트).md]] +- Raw Source: 00_Raw/2026-04-20/DAST (동적 애플리케이션 보안 테스트).md --- diff --git a/01_Archive/2026-04-20/DBpedia.md b/01_Archive/2026-04-20/DBpedia.md index a4e39c25..a7c080d0 100644 --- a/01_Archive/2026-04-20/DBpedia.md +++ b/01_Archive/2026-04-20/DBpedia.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-0B4232 -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - DBpedia" --- -# [[DBpedia]] +# [[DBpedia|DBpedia]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - DBpedia" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/DBpedia.md]] +- Raw Source: 00_Raw/2026-04-20/DBpedia.md --- diff --git a/01_Archive/2026-04-20/DOM 요소 조작 및 타입 좁히기.md b/01_Archive/2026-04-20/DOM 요소 조작 및 타입 좁히기.md index bbb1b1a8..6df6c0e0 100644 --- a/01_Archive/2026-04-20/DOM 요소 조작 및 타입 좁히기.md +++ b/01_Archive/2026-04-20/DOM 요소 조작 및 타입 좁히기.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-3A0CD0 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - DOM 요소 조작 및 타입 좁히기" --- -# [[DOM 요소 조작 및 타입 좁히기]] +# [[DOM 요소 조작 및 타입 좁히기|DOM 요소 조작 및 타입 좁히기]] ## 📌 한 줄 통찰 (The Karpathy Summary) > DOM 요소 조작 시에는 타입스크립트의 타입 좁히기(Type Narrowing) 기술을 통해 타입 안정성을 확보하는 것이 중요합니다. 타입 좁히기란 코드 흐름 분석을 사용하여 포괄적인 타입(유니온 타입 등)을 구체적인 단일 타입으로 줄여나가는 과정입니다 [1-3]. DOM 요소를 다루거나 구조가 명확하지 않은 데이터를 처리할 때, 타입 단언(`as`), 사용자 정의 타입 가드, `typeof` 및 `instanceof` 연산자 등을 활용하여 안전하게 타입을 좁혀 조작할 수 있습니다 [4-6]. @@ -33,11 +33,11 @@ github_commit: "[P-Reinforce] Continuous Worker - DOM 요소 조작 및 타입 - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Type Narrowing]], [[Type Assertions]], [[Discriminated Unions]], [[Branded Types]] -- **Projects/Contexts:** [[안전한 DOM 조작 및 데이터 정제]], [[React 컴포넌트 Props 처리]] +- **Related Topics:** [[Type Narrowing|Type Narrowing]], [[타입 단언 (Type Assertions)|Type Assertions]], [[Discriminated Unions|Discriminated Unions]], [[Branded Types|Branded Types]] +- **Projects/Contexts:** 안전한 DOM 조작 및 데이터 정제, React 컴포넌트 Props 처리 - **Contradictions/Notes:** 타입 단언(`as`)은 DOM 요소를 다루며 타입을 좁힐 때 유용하고 흔하게 사용되지만 [5], 런타임 동작에는 영향을 주지 않으므로 타입 에러를 우회하여 잘못된 코드를 통과시킬 위험이 있습니다. 따라서 가능한 한 `satisfies`나 사용자 정의 타입 가드 등 더 안전한 방식을 우선적으로 고려하는 것이 좋습니다 [7, 8, 15]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/DOM 요소 조작 및 타입 좁히기.md]] +- Raw Source: 00_Raw/2026-04-20/DOM 요소 조작 및 타입 좁히기.md --- diff --git a/01_Archive/2026-04-20/DOM 요소 조작.md b/01_Archive/2026-04-20/DOM 요소 조작.md index 7bb8d717..0097bac4 100644 --- a/01_Archive/2026-04-20/DOM 요소 조작.md +++ b/01_Archive/2026-04-20/DOM 요소 조작.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-15DA1E -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - DOM 요소 조작" --- -# [[DOM 요소 조작]] +# [[DOM 요소 조작|DOM 요소 조작]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 주어진 소스에는 DOM 요소 조작의 구체적인 방법론이나 원리에 대한 내용이 포함되어 있지 않아 소스에 관련 정보가 부족합니다. 제공된 문서들에서는 DOM 요소를 다룰 때 TypeScript의 타입 단언(`as`)을 사용하는 상황이나, 사용자 입력을 DOM에 추가하기 전 XSS 공격을 방어하기 위해 텍스트를 소독(sanitize)해야 한다는 보안 및 타입 안정성 측면에서의 단편적인 예시만 확인됩니다 [1-3]. @@ -25,11 +25,11 @@ github_commit: "[P-Reinforce] Continuous Worker - DOM 요소 조작" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[타입 단언(Type Assertions)]], [[브랜디드 타입(Branded Types)]] -- **Projects/Contexts:** [[안전한 TypeScript 프론트엔드 개발 및 XSS 방어]] +- **Related Topics:** [[타입 단언(Type Assertions)|타입 단언(Type Assertions)]], [[브랜디드 타입(Branded Types)|브랜디드 타입(Branded Types)]] +- **Projects/Contexts:** 안전한 TypeScript 프론트엔드 개발 및 XSS 방어 - **Contradictions/Notes:** 소스에 DOM 요소 조작의 본질적인 원리나 구체적인 API(예: 순수 자바스크립트 DOM API)에 대한 정보가 절대적으로 부족하므로 "소스에 관련 정보가 부족합니다." --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/DOM 요소 조작.md]] +- Raw Source: 00_Raw/2026-04-20/DOM 요소 조작.md --- diff --git a/01_Archive/2026-04-20/DPO (Direct Preference Optimization).md b/01_Archive/2026-04-20/DPO (Direct Preference Optimization).md index 457257da..1cc92363 100644 --- a/01_Archive/2026-04-20/DPO (Direct Preference Optimization).md +++ b/01_Archive/2026-04-20/DPO (Direct Preference Optimization).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-D43239 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - DPO (Direct Preference Optimization)" --- -# [[DPO (Direct Preference Optimization)]] +# [[DPO (Direct Preference Optimization)|DPO (Direct Preference Optimization)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - DPO (Direct Preference Optimiz ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/DPO (Direct Preference Optimization).md]] +- Raw Source: 00_Raw/2026-04-20/DPO (Direct Preference Optimization).md --- diff --git a/01_Archive/2026-04-20/Dark Souls (Environmental Storytelling).md b/01_Archive/2026-04-20/Dark Souls (Environmental Storytelling).md index 1b229e6d..0c773f46 100644 --- a/01_Archive/2026-04-20/Dark Souls (Environmental Storytelling).md +++ b/01_Archive/2026-04-20/Dark Souls (Environmental Storytelling).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-938B32 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Dark Souls (Environmental Storytelling)" --- -# [[Dark Souls (Environmental Storytelling)]] +# [[Dark Souls (Environmental Storytelling)|Dark Souls (Environmental Storytelling)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Dark Souls (Environmental Stor ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Dark Souls (Environmental Storytelling).md]] +- Raw Source: 00_Raw/2026-04-20/Dark Souls (Environmental Storytelling).md --- diff --git a/01_Archive/2026-04-20/Data Array Textures.md b/01_Archive/2026-04-20/Data Array Textures.md index e0b2ef96..b47cde02 100644 --- a/01_Archive/2026-04-20/Data Array Textures.md +++ b/01_Archive/2026-04-20/Data Array Textures.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-8AF01A -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Data Array Textures" --- -# [[Data Array Textures]] +# [[Data Array Textures|Data Array Textures]] ## 📌 한 줄 통찰 (The Karpathy Summary) > Data Array Textures(배열 텍스처)는 셰이더에서 인덱스를 통해 접근할 수 있는 여러 2D 텍스처들의 스택 또는 레이어 구조를 의미합니다 [1, 2]. 이는 여러 이미지를 단일 이미지로 패킹하는 전통적인 텍스처 아틀라스(Texture Atlas)의 문제점들을 해결하는 현대적인 접근 방식입니다 [2]. 특히 다양한 텍스처를 사용하는 여러 객체를 `BatchedMesh`와 결합하여 최소한의 드로우 콜(Draw Call)로 렌더링할 수 있게 해주어 3D 렌더링 성능 최적화에 핵심적인 역할을 합니다 [1, 2]. @@ -23,11 +23,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Data Array Textures" - **정책 변화:** Graphics & Performance 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Texture Atlas]], [[BatchedMesh]], [[Draw Calls]], [[WebGL2]] -- **Projects/Contexts:** [[Three.js 성능 최적화]], [[빌보드 임포스터(Billboard Impostors)]] +- **Related Topics:** [[Texture Atlas|Texture Atlas]], [[BatchedMesh|BatchedMesh]], Draw Calls, [[WebGL2|WebGL2]] +- **Projects/Contexts:** [[Three.js 성능 최적화|Three.js 성능 최적화]], [[빌보드 임포스터(Billboard Impostors)|빌보드 임포스터(Billboard Impostors)]] - **Contradictions/Notes:** 소스에 따르면 Data Array Textures는 텍스처 아틀라스의 단점들을 완벽히 보완하는 현대적 대안이지만, '모든 텍스처의 크기가 같아야 한다'는 엄격한 제약과 '메모리 선할당'의 부담이 존재하므로, 가변적인 크기의 텍스처를 압축하거나 구형 WebGL1 환경을 지원해야 할 때는 여전히 텍스처 아틀라스(Texture Atlas)가 가치 있는 선택지로 남는다고 지적합니다 [5]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Data Array Textures.md]] +- Raw Source: 00_Raw/2026-04-20/Data Array Textures.md --- diff --git a/01_Archive/2026-04-20/Data Distillation (데이터 증류).md b/01_Archive/2026-04-20/Data Distillation (데이터 증류).md index 1ea9bbb8..27d13428 100644 --- a/01_Archive/2026-04-20/Data Distillation (데이터 증류).md +++ b/01_Archive/2026-04-20/Data Distillation (데이터 증류).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-2EC269 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Data Distillation (데이터 증류)" --- -# [[Data Distillation (데이터 증류)]] +# [[Data Distillation (데이터 증류)|Data Distillation (데이터 증류)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Data Distillation (데이터 ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Data Distillation (데이터 증류).md]] +- Raw Source: 00_Raw/2026-04-20/Data Distillation (데이터 증류).md --- diff --git a/01_Archive/2026-04-20/Data-Augmentation-for-Medical-Imaging.md b/01_Archive/2026-04-20/Data-Augmentation-for-Medical-Imaging.md index 91aecaf2..de3c49d2 100644 --- a/01_Archive/2026-04-20/Data-Augmentation-for-Medical-Imaging.md +++ b/01_Archive/2026-04-20/Data-Augmentation-for-Medical-Imaging.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-258909 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Data-Augmentation-for-Medical-Imaging" --- -# [[Data-Augmentation-for-Medical-Imaging]] +# [[Data-Augmentation-for-Medical-Imaging|Data-Augmentation-for-Medical-Imaging]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Data-Augmentation-for-Medical- ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Data-Augmentation-for-Medical-Imaging.md]] +- Raw Source: 00_Raw/2026-04-20/Data-Augmentation-for-Medical-Imaging.md --- diff --git a/01_Archive/2026-04-20/Data-Sanitization.md b/01_Archive/2026-04-20/Data-Sanitization.md index 008f84d9..779e7500 100644 --- a/01_Archive/2026-04-20/Data-Sanitization.md +++ b/01_Archive/2026-04-20/Data-Sanitization.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-476815 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Data-Sanitization" --- -# [[Data-Sanitization]] +# [[Data-Sanitization|Data-Sanitization]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Data-Sanitization" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Data-Sanitization.md]] +- Raw Source: 00_Raw/2026-04-20/Data-Sanitization.md --- diff --git a/01_Archive/2026-04-20/Data-Science-in-UX.md b/01_Archive/2026-04-20/Data-Science-in-UX.md index af17dfec..e3dcbc33 100644 --- a/01_Archive/2026-04-20/Data-Science-in-UX.md +++ b/01_Archive/2026-04-20/Data-Science-in-UX.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-235CC7 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Data-Science-in-UX" --- -# [[Data-Science-in-UX]] +# [[Data-Science-in-UX|Data-Science-in-UX]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Data-Science-in-UX" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Data-Science-in-UX.md]] +- Raw Source: 00_Raw/2026-04-20/Data-Science-in-UX.md --- diff --git a/01_Archive/2026-04-20/Data-Transfer-Object-Design.md b/01_Archive/2026-04-20/Data-Transfer-Object-Design.md index c4ae231a..aacc6aec 100644 --- a/01_Archive/2026-04-20/Data-Transfer-Object-Design.md +++ b/01_Archive/2026-04-20/Data-Transfer-Object-Design.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-21E554 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Data-Transfer-Object-Design" --- -# [[Data-Transfer-Object-Design]] +# [[Data-Transfer-Object-Design|Data-Transfer-Object-Design]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Data-Transfer-Object-Design" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Data-Transfer-Object-Design.md]] +- Raw Source: 00_Raw/2026-04-20/Data-Transfer-Object-Design.md --- diff --git a/01_Archive/2026-04-20/Dead Space (Series).md b/01_Archive/2026-04-20/Dead Space (Series).md index afd55743..a7aeca5c 100644 --- a/01_Archive/2026-04-20/Dead Space (Series).md +++ b/01_Archive/2026-04-20/Dead Space (Series).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-989941 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Dead Space (Series)" --- -# [[Dead Space (Series)]] +# [[Dead Space (Series)|Dead Space (Series)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Dead Space (Series)" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Dead Space (Series).md]] +- Raw Source: 00_Raw/2026-04-20/Dead Space (Series).md --- diff --git a/01_Archive/2026-04-20/Deceptive Alignment (기만적 정렬).md b/01_Archive/2026-04-20/Deceptive Alignment (기만적 정렬).md index edc172c7..aaac6a23 100644 --- a/01_Archive/2026-04-20/Deceptive Alignment (기만적 정렬).md +++ b/01_Archive/2026-04-20/Deceptive Alignment (기만적 정렬).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-EB9E46 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Deceptive Alignment (기만적 정렬)" --- -# [[Deceptive Alignment (기만적 정렬)]] +# [[Deceptive Alignment (기만적 정렬)|Deceptive Alignment (기만적 정렬)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Deceptive Alignment (기만적 ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Deceptive Alignment (기만적 정렬).md]] +- Raw Source: 00_Raw/2026-04-20/Deceptive Alignment (기만적 정렬).md --- diff --git a/01_Archive/2026-04-20/Decision Theory.md b/01_Archive/2026-04-20/Decision Theory.md index 32c46eac..c71cf81f 100644 --- a/01_Archive/2026-04-20/Decision Theory.md +++ b/01_Archive/2026-04-20/Decision Theory.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-B8B3FB -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Decision Theory" --- -# [[Decision Theory]] +# [[Decision Theory|Decision Theory]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Decision Theory" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Decision Theory.md]] +- Raw Source: 00_Raw/2026-04-20/Decision Theory.md --- diff --git a/01_Archive/2026-04-20/Declaration Files (.d.ts).md b/01_Archive/2026-04-20/Declaration Files (.d.ts).md index 2ee00ab2..57b7790c 100644 --- a/01_Archive/2026-04-20/Declaration Files (.d.ts).md +++ b/01_Archive/2026-04-20/Declaration Files (.d.ts).md @@ -1,4 +1,4 @@ -[[Declaration Files (.d.ts)]] +[[Declaration Files (.d.ts)|Declaration Files (.d.ts)]] 📌 Brief Summary Declaration files (`.d.ts`) are specialized TypeScript files that contain only type information and no executable JavaScript logic. They serve as a structural blueprint, providing the compiler with the shape of existing code (often written in plain JavaScript) to enable static type checking, autocomte, and interface validation within the TypeScript ecosystem. @@ -12,8 +12,8 @@ Declaration files (`.d.ts`) are specialized TypeScript files that contain only t * **Compilation Behavior**: During the build process, `.d.ts` files are stripped away. They do not contribute to the size of the emitted `.js` files; their influence is strictly limited to the "Type Checking" phase of the TypeScript compiler lifecycle. 🔗 Knowledge Connections -* Related Topics: [[Ambient Declarations]], [[Module Augmentation]], [[Structural Type System]] -* Projects/Contexts: [[DefinitelyTyped]], [[TypeScript Compiler API]] +* Related Topics: [[Ambient Declarations|Ambient Declarations]], [[Module Augmentation|Module Augmentation]], [[Structural Type System|Structural Type System]] +* Projects/Contexts: [[DefinitelyTyped|DefinitelyTyped]], [[TypeScript Compiler API|TypeScript Compiler API]] * Contradictions/Notes: While `.d.ts` files provide type safety, they do not provide runtime validation; a mismatch between the declaration file and the actual JavaScript implementation can lead to "false positives" where code passes compilation but fails at runtime. Last updated: 2026-04-17 \ No newline at end of file diff --git a/01_Archive/2026-04-20/Declaration Files (dts).md b/01_Archive/2026-04-20/Declaration Files (dts).md index dd1ea1d1..e344c609 100644 --- a/01_Archive/2026-04-20/Declaration Files (dts).md +++ b/01_Archive/2026-04-20/Declaration Files (dts).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-D2F3A4 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Declaration Files (dts)" --- -# [[Declaration Files (dts)]] +# [[Declaration Files (dts)|Declaration Files (dts)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Declaration Files (dts)" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Declaration Files (.d.ts).md]] +- Raw Source: 00_Raw/2026-04-20/Declaration Files (.d.ts).md --- diff --git a/01_Archive/2026-04-20/Declaration Merging.md b/01_Archive/2026-04-20/Declaration Merging.md index acd7dd63..76454552 100644 --- a/01_Archive/2026-04-20/Declaration Merging.md +++ b/01_Archive/2026-04-20/Declaration Merging.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-164A4F -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Declaration Merging" --- -# [[Declaration Merging]] +# [[Declaration Merging|Declaration Merging]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Declaration Merging" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Declaration Merging.md]] +- Raw Source: 00_Raw/2026-04-20/Declaration Merging.md --- diff --git a/01_Archive/2026-04-20/Declaration-Files.md b/01_Archive/2026-04-20/Declaration-Files.md index 1b7e9c35..ae48cc4f 100644 --- a/01_Archive/2026-04-20/Declaration-Files.md +++ b/01_Archive/2026-04-20/Declaration-Files.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-2150D3 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Declaration-Files" --- -# [[Declaration-Files]] +# [[Declaration-Files|Declaration-Files]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Declaration-Files" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Declaration-Files.md]] +- Raw Source: 00_Raw/2026-04-20/Declaration-Files.md --- diff --git a/01_Archive/2026-04-20/Declaration-Merging.md b/01_Archive/2026-04-20/Declaration-Merging.md index bbfd6ef9..39e3f743 100644 --- a/01_Archive/2026-04-20/Declaration-Merging.md +++ b/01_Archive/2026-04-20/Declaration-Merging.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-6586E8 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Declaration-Merging" --- -# [[Declaration-Merging]] +# [[Declaration-Merging|Declaration-Merging]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Declaration-Merging" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Declaration-Merging.md]] +- Raw Source: 00_Raw/2026-04-20/Declaration-Merging.md --- diff --git a/01_Archive/2026-04-20/Deep Q-Networks (DQN).md b/01_Archive/2026-04-20/Deep Q-Networks (DQN).md index a054c788..be761356 100644 --- a/01_Archive/2026-04-20/Deep Q-Networks (DQN).md +++ b/01_Archive/2026-04-20/Deep Q-Networks (DQN).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-704527 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Deep Q-Networks (DQN)" --- -# [[Deep Q-Networks (DQN)]] +# [[Deep Q-Networks (DQN)|Deep Q-Networks (DQN)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Deep Q-Networks (DQN)" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Deep Q-Networks (DQN).md]] +- Raw Source: 00_Raw/2026-04-20/Deep Q-Networks (DQN).md --- diff --git a/01_Archive/2026-04-20/Deep-Convolutional-GANs.md b/01_Archive/2026-04-20/Deep-Convolutional-GANs.md index 3113d5e5..2eb7ec67 100644 --- a/01_Archive/2026-04-20/Deep-Convolutional-GANs.md +++ b/01_Archive/2026-04-20/Deep-Convolutional-GANs.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-84A34B -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Deep-Convolutional-GANs" --- -# [[Deep-Convolutional-GANs]] +# [[Deep-Convolutional-GANs|Deep-Convolutional-GANs]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Deep-Convolutional-GANs" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Deep-Convolutional-GANs.md]] +- Raw Source: 00_Raw/2026-04-20/Deep-Convolutional-GANs.md --- diff --git a/01_Archive/2026-04-20/DeepCode AI.md b/01_Archive/2026-04-20/DeepCode AI.md index 76aa8cda..7c7c1f27 100644 --- a/01_Archive/2026-04-20/DeepCode AI.md +++ b/01_Archive/2026-04-20/DeepCode AI.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-A75F29 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - DeepCode AI" --- -# [[DeepCode AI]] +# [[DeepCode AI|DeepCode AI]] ## 📌 한 줄 통찰 (The Karpathy Summary) > DeepCode AI는 수백만 개의 오픈소스 코드 커밋을 학습하여 취약점을 탐지하고 수정 사항을 제안하는 머신러닝(ML) 기반의 목적 맞춤형 보안 AI 엔진입니다 [1-3]. 2020년 보안 기업 Snyk이 스위스 AI 스타트업인 DeepCode를 인수하여 자사의 정적 애플리케이션 보안 테스트(SAST) 도구인 Snyk Code의 핵심 인텔리전스 계층으로 통합했습니다 [1, 2, 4]. 이 엔진은 단순한 규칙 기반 패턴 매칭을 넘어 기호적 AI(Symbolic AI)와 신경망을 결합하여 코드의 의미(semantics)와 데이터 흐름을 깊이 있게 이해합니다 [4, 5]. @@ -27,11 +27,11 @@ github_commit: "[P-Reinforce] Continuous Worker - DeepCode AI" - **정책 변화:** AI 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Snyk Code]], [[SAST (Static Application Security Testing)]], [[Symbolic AI]], [[Machine Learning]] -- **Projects/Contexts:** [[Snyk 플랫폼을 통한 IDE 및 CI/CD 파이프라인 통합 보안 검토 프로젝트]] +- **Related Topics:** Snyk Code, [[SAST (Static Application Security Testing)|SAST (Static Application Security Testing)]], Symbolic AI, Machine Learning +- **Projects/Contexts:** Snyk 플랫폼을 통한 IDE 및 CI/CD 파이프라인 통합 보안 검토 프로젝트 - **Contradictions/Notes:** DeepCode AI가 자동으로 취약점을 감지하고 수정안을 제시하지만, 일부 결과는 여전히 수동 검증이 필요하며 분석의 깊이는 언어에 따라 다를 수 있다는 점이 지적됩니다 [6]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/DeepCode AI.md]] +- Raw Source: 00_Raw/2026-04-20/DeepCode AI.md --- diff --git a/01_Archive/2026-04-20/DeepReadonly.md b/01_Archive/2026-04-20/DeepReadonly.md index 4a292bd6..4af9dce7 100644 --- a/01_Archive/2026-04-20/DeepReadonly.md +++ b/01_Archive/2026-04-20/DeepReadonly.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-5FB09F -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - DeepReadonly" --- -# [[DeepReadonly]] +# [[DeepReadonly|DeepReadonly]] ## 📌 한 줄 통찰 (The Karpathy Summary) > DeepReadonly는 TypeScript에서 객체의 모든 중첩된 프로퍼티에 재귀적으로 `readonly`를 적용하여 데이터 구조 전체를 완전한 불변(immutable) 상태로 만드는 사용자 정의 유틸리티 타입이다 [1, 2]. 기본 내장된 `Readonly` 유틸리티가 객체의 최상위 속성만 보호하는 얕은(shallow) 불변성만을 제공한다는 한계를 극복하기 위해 고안되었다 [1-3]. 상태 관리나 설정 객체와 같이, 객체 생성 이후 내부의 단 하나의 속성도 수정되지 않아야 함을 엄격하게 보장해야 할 때 주로 사용된다 [1, 4]. @@ -22,11 +22,11 @@ github_commit: "[P-Reinforce] Continuous Worker - DeepReadonly" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[readonly]], [[Readonly]], [[Mapped Types]], [[Conditional Types]] -- **Projects/Contexts:** [[상태 관리(State Management)]], [[설정 객체(Configuration Objects)]], [[ts-essentials]] +- **Related Topics:** [[readonly|readonly]], Readonly, [[Mapped-Types|Mapped Types]], [[Conditional-Types|Conditional Types]] +- **Projects/Contexts:** [[상태 관리(State Management)|상태 관리(State Management)]], 설정 객체(Configuration Objects), ts-essentials - **Contradictions/Notes:** 깊은 수준의 불변성을 보장하는 기능이 실무적으로 널리 요구되었음에도 불구하고 `DeepReadonly`는 TypeScript에 공식적으로 기본 내장되어 있지 않다는 점이 특징적이다 [5]. 이로 인해 추가적인 구현이나 외부 라이브러리 의존성이 요구된다 [5]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/DeepReadonly.md]] +- Raw Source: 00_Raw/2026-04-20/DeepReadonly.md --- diff --git a/01_Archive/2026-04-20/Deepfake-Detection-Research.md b/01_Archive/2026-04-20/Deepfake-Detection-Research.md index e8ec59a9..ccd25979 100644 --- a/01_Archive/2026-04-20/Deepfake-Detection-Research.md +++ b/01_Archive/2026-04-20/Deepfake-Detection-Research.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-DD74C9 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Deepfake-Detection-Research" --- -# [[Deepfake-Detection-Research]] +# [[Deepfake-Detection-Research|Deepfake-Detection-Research]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Deepfake-Detection-Research" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Deepfake-Detection-Research.md]] +- Raw Source: 00_Raw/2026-04-20/Deepfake-Detection-Research.md --- diff --git a/01_Archive/2026-04-20/Default Mode Network (DMN).md b/01_Archive/2026-04-20/Default Mode Network (DMN).md index 8221a382..03fe7398 100644 --- a/01_Archive/2026-04-20/Default Mode Network (DMN).md +++ b/01_Archive/2026-04-20/Default Mode Network (DMN).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-B914F1 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Default Mode Network (DMN)" --- -# [[Default Mode Network (DMN)]] +# [[Default Mode Network (DMN)|Default Mode Network (DMN)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Default Mode Network (DMN)" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Default Mode Network (DMN).md]] +- Raw Source: 00_Raw/2026-04-20/Default Mode Network (DMN).md --- diff --git a/01_Archive/2026-04-20/DefinitelyTyped and Ambient Declarations.md b/01_Archive/2026-04-20/DefinitelyTyped and Ambient Declarations.md index 4183ca71..83704251 100644 --- a/01_Archive/2026-04-20/DefinitelyTyped and Ambient Declarations.md +++ b/01_Archive/2026-04-20/DefinitelyTyped and Ambient Declarations.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-8435E3 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - DefinitelyTyped and Ambient Declarations" --- -# [[DefinitelyTyped and Ambient Declarations]] +# [[DefinitelyTyped and Ambient Declarations|DefinitelyTyped and Ambient Declarations]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - DefinitelyTyped and Ambient De ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/DefinitelyTyped and Ambient Declarations.md]] +- Raw Source: 00_Raw/2026-04-20/DefinitelyTyped and Ambient Declarations.md --- diff --git a/01_Archive/2026-04-20/DefinitelyTyped.md b/01_Archive/2026-04-20/DefinitelyTyped.md index eb6ff2f5..9b9909fd 100644 --- a/01_Archive/2026-04-20/DefinitelyTyped.md +++ b/01_Archive/2026-04-20/DefinitelyTyped.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-4BB90C -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - DefinitelyTyped" --- -# [[DefinitelyTyped]] +# [[DefinitelyTyped|DefinitelyTyped]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - DefinitelyTyped" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/DefinitelyTyped.md]] +- Raw Source: 00_Raw/2026-04-20/DefinitelyTyped.md --- diff --git a/01_Archive/2026-04-20/Degrees-of-Freedom.md b/01_Archive/2026-04-20/Degrees-of-Freedom.md index 01cf2a91..57a5a2e9 100644 --- a/01_Archive/2026-04-20/Degrees-of-Freedom.md +++ b/01_Archive/2026-04-20/Degrees-of-Freedom.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-B68509 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Degrees-of-Freedom" --- -# [[Degrees-of-Freedom]] +# [[Degrees-of-Freedom|Degrees-of-Freedom]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Degrees-of-Freedom" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Degrees-of-Freedom.md]] +- Raw Source: 00_Raw/2026-04-20/Degrees-of-Freedom.md --- diff --git a/01_Archive/2026-04-20/Deliberate-Practice.md b/01_Archive/2026-04-20/Deliberate-Practice.md index f0850acd..d853f24c 100644 --- a/01_Archive/2026-04-20/Deliberate-Practice.md +++ b/01_Archive/2026-04-20/Deliberate-Practice.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-EE5EE5 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Deliberate-Practice" --- -# [[Deliberate-Practice]] +# [[Deliberate-Practice|Deliberate-Practice]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Deliberate-Practice" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Deliberate-Practice.md]] +- Raw Source: 00_Raw/2026-04-20/Deliberate-Practice.md --- diff --git a/01_Archive/2026-04-20/Denavit-Hartenberg-Parameters.md b/01_Archive/2026-04-20/Denavit-Hartenberg-Parameters.md index 78b6dc26..56b0dc67 100644 --- a/01_Archive/2026-04-20/Denavit-Hartenberg-Parameters.md +++ b/01_Archive/2026-04-20/Denavit-Hartenberg-Parameters.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-B3CEC1 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Denavit-Hartenberg-Parameters" --- -# [[Denavit-Hartenberg-Parameters]] +# [[Denavit-Hartenberg-Parameters|Denavit-Hartenberg-Parameters]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Denavit-Hartenberg-Parameters" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Denavit-Hartenberg-Parameters.md]] +- Raw Source: 00_Raw/2026-04-20/Denavit-Hartenberg-Parameters.md --- diff --git a/01_Archive/2026-04-20/Dependency-Graph-Analysis.md b/01_Archive/2026-04-20/Dependency-Graph-Analysis.md index c19c1a08..47806f55 100644 --- a/01_Archive/2026-04-20/Dependency-Graph-Analysis.md +++ b/01_Archive/2026-04-20/Dependency-Graph-Analysis.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-597DF8 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Dependency-Graph-Analysis" --- -# [[Dependency-Graph-Analysis]] +# [[Dependency-Graph-Analysis|Dependency-Graph-Analysis]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Dependency-Graph-Analysis" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Dependency-Graph-Analysis.md]] +- Raw Source: 00_Raw/2026-04-20/Dependency-Graph-Analysis.md --- diff --git a/01_Archive/2026-04-20/Dependency-Injection.md b/01_Archive/2026-04-20/Dependency-Injection.md index 019b1bd6..cb02e540 100644 --- a/01_Archive/2026-04-20/Dependency-Injection.md +++ b/01_Archive/2026-04-20/Dependency-Injection.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-D3C51B -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Dependency-Injection" --- -# [[Dependency-Injection]] +# [[Dependency-Injection|Dependency-Injection]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Dependency-Injection" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Dependency-Injection.md]] +- Raw Source: 00_Raw/2026-04-20/Dependency-Injection.md --- diff --git a/01_Archive/2026-04-20/Dependency-Inversion-Principle.md b/01_Archive/2026-04-20/Dependency-Inversion-Principle.md index a340143b..db20631f 100644 --- a/01_Archive/2026-04-20/Dependency-Inversion-Principle.md +++ b/01_Archive/2026-04-20/Dependency-Inversion-Principle.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-4C0291 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Dependency-Inversion-Principle" --- -# [[Dependency-Inversion-Principle]] +# [[Dependency-Inversion-Principle|Dependency-Inversion-Principle]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Dependency-Inversion-Principle ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Dependency-Inversion-Principle.md]] +- Raw Source: 00_Raw/2026-04-20/Dependency-Inversion-Principle.md --- diff --git a/01_Archive/2026-04-20/Depth Pre-Pass.md b/01_Archive/2026-04-20/Depth Pre-Pass.md index 63a999f8..d809f675 100644 --- a/01_Archive/2026-04-20/Depth Pre-Pass.md +++ b/01_Archive/2026-04-20/Depth Pre-Pass.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-B5A436 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Depth Pre-Pass" --- -# [[Depth Pre-Pass]] +# [[Depth Pre-Pass|Depth Pre-Pass]] ## 📌 한 줄 통찰 (The Karpathy Summary) > Depth Pre-Pass는 복잡한 기하학적 구조를 가진 씬에서 가려진 객체를 제거하는 오클루전 컬링(Occlusion culling)을 수행하기 위해 사용되는 효과적인 렌더링 전략입니다 [1]. 특히 필 레이트(fill-rate)와 프래그먼트 처리 성능이 제한된 내장 GPU(iGPU) 환경에서 유용한 해결책으로 활용됩니다 [1]. 렌더링을 두 단계로 나누어 불필요한 프래그먼트 셰이더 연산을 방지함으로써 오버드로우(overdraw)가 심한 모델의 렌더링 성능을 크게 향상시킵니다 [1, 2]. @@ -25,11 +25,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Depth Pre-Pass" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Occlusion Culling]], [[Z-buffer]], [[Overdraw]], [[Fragment Shader]] -- **Projects/Contexts:** [[WebGL/Three.js CAD Rendering Optimization]] +- **Related Topics:** [[Occlusion Culling|Occlusion Culling]], Z-buffer, [[Overdraw|Overdraw]], Fragment Shader +- **Projects/Contexts:** WebGL/Three.js CAD Rendering Optimization - **Contradictions/Notes:** 소스에 상충되는 내용은 없으며, 오클루전 컬링을 CPU에서 처리하기 어렵거나 GPU 레이턴시로 인해 비용이 높을 때 이를 해결하는 가장 효과적인 우회(workaround) 기법으로 설명됩니다 [1]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Depth Pre-Pass.md]] +- Raw Source: 00_Raw/2026-04-20/Depth Pre-Pass.md --- diff --git a/01_Archive/2026-04-20/Depth-Subtyping.md b/01_Archive/2026-04-20/Depth-Subtyping.md index 47cec662..d8b2f3b4 100644 --- a/01_Archive/2026-04-20/Depth-Subtyping.md +++ b/01_Archive/2026-04-20/Depth-Subtyping.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-408E53 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Depth-Subtyping" --- -# [[Depth-Subtyping]] +# [[Depth-Subtyping|Depth-Subtyping]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Depth-Subtyping" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Depth-Subtyping.md]] +- Raw Source: 00_Raw/2026-04-20/Depth-Subtyping.md --- diff --git a/01_Archive/2026-04-20/Description Logic (기술 논리).md b/01_Archive/2026-04-20/Description Logic (기술 논리).md index 78e4be28..5b42dc27 100644 --- a/01_Archive/2026-04-20/Description Logic (기술 논리).md +++ b/01_Archive/2026-04-20/Description Logic (기술 논리).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-442F1D -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Description Logic (기술 논리)" --- -# [[Description Logic (기술 논리)]] +# [[Description Logic (기술 논리)|Description Logic (기술 논리)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Description Logic (기술 논 ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Description Logic (기술 논리).md]] +- Raw Source: 00_Raw/2026-04-20/Description Logic (기술 논리).md --- diff --git a/01_Archive/2026-04-20/Description-Logics.md b/01_Archive/2026-04-20/Description-Logics.md index 5b16b54e..8a183313 100644 --- a/01_Archive/2026-04-20/Description-Logics.md +++ b/01_Archive/2026-04-20/Description-Logics.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-088907 -category: "[[10_Wiki/💡 Topics/General Knowledge]]" +category: "10_Wiki/💡 Topics/General Knowledge" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Description-Logics" --- -# [[Description-Logics]] +# [[Description-Logics|Description-Logics]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Description-Logics" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Description-Logics.md]] +- Raw Source: 00_Raw/2026-04-20/Description-Logics.md --- diff --git a/01_Archive/2026-04-20/Design-Thinking.md b/01_Archive/2026-04-20/Design-Thinking.md index ae3c293d..3a71fbbc 100644 --- a/01_Archive/2026-04-20/Design-Thinking.md +++ b/01_Archive/2026-04-20/Design-Thinking.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-F6D12C -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Design-Thinking" --- -# [[Design-Thinking]] +# [[Design-Thinking|Design-Thinking]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Design-Thinking" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Design-Thinking.md]] +- Raw Source: 00_Raw/2026-04-20/Design-Thinking.md --- diff --git a/01_Archive/2026-04-20/Design-Tokens.md b/01_Archive/2026-04-20/Design-Tokens.md index 9998ed1d..e8513aa4 100644 --- a/01_Archive/2026-04-20/Design-Tokens.md +++ b/01_Archive/2026-04-20/Design-Tokens.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-2C4230 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Design-Tokens" --- -# [[Design-Tokens]] +# [[Design-Tokens|Design-Tokens]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Design-Tokens" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Design-Tokens.md]] +- Raw Source: 00_Raw/2026-04-20/Design-Tokens.md --- diff --git a/01_Archive/2026-04-20/Deterministic Algorithms.md b/01_Archive/2026-04-20/Deterministic Algorithms.md index 7cbd5b1c..364a7f3a 100644 --- a/01_Archive/2026-04-20/Deterministic Algorithms.md +++ b/01_Archive/2026-04-20/Deterministic Algorithms.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-FB6D64 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Deterministic Algorithms" --- -# [[Deterministic Algorithms]] +# [[Deterministic Algorithms|Deterministic Algorithms]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Deterministic Algorithms" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Deterministic Algorithms.md]] +- Raw Source: 00_Raw/2026-04-20/Deterministic Algorithms.md --- diff --git a/01_Archive/2026-04-20/Deterministic Lockstep Architecture.md b/01_Archive/2026-04-20/Deterministic Lockstep Architecture.md index df07ddb6..32d06168 100644 --- a/01_Archive/2026-04-20/Deterministic Lockstep Architecture.md +++ b/01_Archive/2026-04-20/Deterministic Lockstep Architecture.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-1D4EC0 -category: "[[10_Wiki/💡 Topics/Software Architecture]]" +category: "10_Wiki/💡 Topics/Software Architecture" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Deterministic Lockstep Architecture" --- -# [[Deterministic Lockstep Architecture]] +# [[Deterministic Lockstep Architecture|Deterministic Lockstep Architecture]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Deterministic Lockstep Archite ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Deterministic Lockstep Architecture.md]] +- Raw Source: 00_Raw/2026-04-20/Deterministic Lockstep Architecture.md --- diff --git a/01_Archive/2026-04-20/DevOps-and-UX-Convergence.md b/01_Archive/2026-04-20/DevOps-and-UX-Convergence.md index e7575bec..29a9b94c 100644 --- a/01_Archive/2026-04-20/DevOps-and-UX-Convergence.md +++ b/01_Archive/2026-04-20/DevOps-and-UX-Convergence.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-9EB8EA -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - DevOps-and-UX-Convergence" --- -# [[DevOps-and-UX-Convergence]] +# [[DevOps-and-UX-Convergence|DevOps-and-UX-Convergence]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - DevOps-and-UX-Convergence" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/DevOps-and-UX-Convergence.md]] +- Raw Source: 00_Raw/2026-04-20/DevOps-and-UX-Convergence.md --- diff --git a/01_Archive/2026-04-20/DevSecOps.md b/01_Archive/2026-04-20/DevSecOps.md index 421de756..0dc7272c 100644 --- a/01_Archive/2026-04-20/DevSecOps.md +++ b/01_Archive/2026-04-20/DevSecOps.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-89C666 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - DevSecOps" --- -# [[DevSecOps]] +# [[DevSecOps|DevSecOps]] ## 📌 한 줄 통찰 (The Karpathy Summary) > DevSecOps는 소프트웨어 개발 수명 주기(SDLC) 전반에 걸쳐 보안을 통합하는 방법론입니다 [1]. 핵심적인 접근 방식은 보안 점검을 개발 초기 단계로 앞당기는 '시프트 레프트(Shift-left)' 전략입니다 [2]. 기존 개발 워크플로우를 늦추지 않으면서도 CI/CD 파이프라인이나 개발 환경(IDE)에 코드 검사 도구 및 AI 자동화를 도입하여 보안 위협을 조기에 탐지하고 대응하는 것을 목표로 합니다 [2, 3]. @@ -22,11 +22,11 @@ github_commit: "[P-Reinforce] Continuous Worker - DevSecOps" - **정책 변화:** AI 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[SDLC]], [[Shift-Left]], [[SAST]], [[CI/CD]] -- **Projects/Contexts:** [[Snyk]], [[GitHub Advanced Security]], [[SonarQube]] 등 코드 품질 및 보안 분석 도구들을 개발 워크플로우(IDE, 리포지토리, CI/CD)에 연동하여 실시간 보안 피드백을 제공하는 방식으로 구성됩니다 [1, 2, 9]. +- **Related Topics:** [[SDLC (소프트웨어 개발 수명 주기)|SDLC]], [[시프트 레프트 (Shift-Left)|Shift-Left]], [[SAST|SAST]], [[CI_CD|CI/CD]] +- **Projects/Contexts:** Snyk, GitHub Advanced Security, [[SonarQube|SonarQube]] 등 코드 품질 및 보안 분석 도구들을 개발 워크플로우(IDE, 리포지토리, CI/CD)에 연동하여 실시간 보안 피드백을 제공하는 방식으로 구성됩니다 [1, 2, 9]. - **Contradictions/Notes:** DevSecOps 워크플로우에서 자동화된 검사는 필수적이지만, AI나 스캐너 도구는 비즈니스 로직이나 의도를 파악하지 못하는 맹점(Context Blindness)을 가지고 있습니다 [10]. 따라서 자동화 도구가 일상적이고 반복적인 취약점을 빠르게 잡아내고, 인간 리뷰어가 아키텍처와 복잡한 보안 컨텍스트에 집중하는 '하이브리드(Hybrid)' 접근법이 가장 이상적인 모델로 권장됩니다 [11, 12]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/DevSecOps.md]] +- Raw Source: 00_Raw/2026-04-20/DevSecOps.md --- diff --git a/01_Archive/2026-04-20/Diegetic UI.md b/01_Archive/2026-04-20/Diegetic UI.md index be406d08..31ff4099 100644 --- a/01_Archive/2026-04-20/Diegetic UI.md +++ b/01_Archive/2026-04-20/Diegetic UI.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-FE01D2 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Diegetic UI" --- -# [[Diegetic UI]] +# [[Diegetic UI|Diegetic UI]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Diegetic UI" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Diegetic UI.md]] +- Raw Source: 00_Raw/2026-04-20/Diegetic UI.md --- diff --git a/01_Archive/2026-04-20/Diegetic-Interface.md b/01_Archive/2026-04-20/Diegetic-Interface.md index 0f218de9..e8f66ca9 100644 --- a/01_Archive/2026-04-20/Diegetic-Interface.md +++ b/01_Archive/2026-04-20/Diegetic-Interface.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-9F62F4 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Diegetic-Interface" --- -# [[Diegetic-Interface]] +# [[Diegetic-Interface|Diegetic-Interface]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Diegetic-Interface" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Diegetic-Interface.md]] +- Raw Source: 00_Raw/2026-04-20/Diegetic-Interface.md --- diff --git a/01_Archive/2026-04-20/Diffusion-Models.md b/01_Archive/2026-04-20/Diffusion-Models.md index b39bd05c..41f18bb0 100644 --- a/01_Archive/2026-04-20/Diffusion-Models.md +++ b/01_Archive/2026-04-20/Diffusion-Models.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-7C0B06 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Diffusion-Models" --- -# [[Diffusion-Models]] +# [[Diffusion-Models|Diffusion-Models]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Diffusion-Models" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Diffusion-Models.md]] +- Raw Source: 00_Raw/2026-04-20/Diffusion-Models.md --- diff --git a/01_Archive/2026-04-20/Digital Humanities.md b/01_Archive/2026-04-20/Digital Humanities.md index 5f41d732..c391e3fc 100644 --- a/01_Archive/2026-04-20/Digital Humanities.md +++ b/01_Archive/2026-04-20/Digital Humanities.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-1CBB5B -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Digital Humanities" --- -# [[Digital Humanities]] +# [[Digital Humanities|Digital Humanities]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Digital Humanities" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Digital Humanities.md]] +- Raw Source: 00_Raw/2026-04-20/Digital Humanities.md --- diff --git a/01_Archive/2026-04-20/Digital Intellectual Property Rights.md b/01_Archive/2026-04-20/Digital Intellectual Property Rights.md index 813bb828..8b98dc73 100644 --- a/01_Archive/2026-04-20/Digital Intellectual Property Rights.md +++ b/01_Archive/2026-04-20/Digital Intellectual Property Rights.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-384956 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Digital Intellectual Property Rights" --- -# [[Digital Intellectual Property Rights]] +# [[Digital Intellectual Property Rights|Digital Intellectual Property Rights]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Digital Intellectual Property ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Digital Intellectual Property Rights.md]] +- Raw Source: 00_Raw/2026-04-20/Digital Intellectual Property Rights.md --- diff --git a/01_Archive/2026-04-20/Digital Sandbox Theory.md b/01_Archive/2026-04-20/Digital Sandbox Theory.md index d022cb94..6ab2b73e 100644 --- a/01_Archive/2026-04-20/Digital Sandbox Theory.md +++ b/01_Archive/2026-04-20/Digital Sandbox Theory.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-A1EFBC -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Digital Sandbox Theory" --- -# [[Digital Sandbox Theory]] +# [[Digital Sandbox Theory|Digital Sandbox Theory]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Digital Sandbox Theory" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Digital Sandbox Theory.md]] +- Raw Source: 00_Raw/2026-04-20/Digital Sandbox Theory.md --- diff --git a/01_Archive/2026-04-20/Digital Thread Integration.md b/01_Archive/2026-04-20/Digital Thread Integration.md index e2eb8ea3..0e19de6b 100644 --- a/01_Archive/2026-04-20/Digital Thread Integration.md +++ b/01_Archive/2026-04-20/Digital Thread Integration.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-A9FF14 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Digital Thread Integration" --- -# [[Digital Thread Integration]] +# [[Digital Thread Integration|Digital Thread Integration]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Digital Thread Integration" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Digital Thread Integration.md]] +- Raw Source: 00_Raw/2026-04-20/Digital Thread Integration.md --- diff --git a/01_Archive/2026-04-20/Digital Twin Interfaces.md b/01_Archive/2026-04-20/Digital Twin Interfaces.md index 60410195..d3121453 100644 --- a/01_Archive/2026-04-20/Digital Twin Interfaces.md +++ b/01_Archive/2026-04-20/Digital Twin Interfaces.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-6DF617 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Digital Twin Interfaces" --- -# [[Digital Twin Interfaces]] +# [[Digital Twin Interfaces|Digital Twin Interfaces]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Digital Twin Interfaces" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Digital Twin Interfaces.md]] +- Raw Source: 00_Raw/2026-04-20/Digital Twin Interfaces.md --- diff --git a/01_Archive/2026-04-20/Digital Twin Visualization.md b/01_Archive/2026-04-20/Digital Twin Visualization.md index fb69fef0..58883f9f 100644 --- a/01_Archive/2026-04-20/Digital Twin Visualization.md +++ b/01_Archive/2026-04-20/Digital Twin Visualization.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-F0B4B1 -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Digital Twin Visualization" --- -# [[Digital Twin Visualization]] +# [[Digital Twin Visualization|Digital Twin Visualization]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Digital Twin Visualization" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Digital Twin Visualization.md]] +- Raw Source: 00_Raw/2026-04-20/Digital Twin Visualization.md --- diff --git a/01_Archive/2026-04-20/Digital Twins.md b/01_Archive/2026-04-20/Digital Twins.md index 2893c1bd..5171f704 100644 --- a/01_Archive/2026-04-20/Digital Twins.md +++ b/01_Archive/2026-04-20/Digital Twins.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AI-056 -category: "[[10_Wiki/💡 Topics/System Architecture & Simulation]]" +category: "10_Wiki/💡 Topics/System Architecture & Simulation" confidence_score: 0.98 tags: [digital twin, simulation, iot, cyber-physical] last_reinforced: 2026-06-XX github_commit: "[P-Reinforce] Processed Digital Twins." --- -# [[Digital Twins]] (디지털 트윈) +# [[Digital Twins|Digital Twins]] (디지털 트윈) ## 📌 한 줄 통찰 (The Karpathy Summary) > 현실 세계의 물리적 자산(Asset)을 가상 공간에 실시간으로 복제하여, 시뮬레이션과 예측을 통해 실제 시스템 운영 최적화 및 문제 해결 방안을 사전에 검증하는 기술이다. @@ -24,7 +24,7 @@ github_commit: "[P-Reinforce] Processed Digital Twins." - **정책 변화:** 산업의 특성상 높은 수준의 실시간 데이터 무결성과 보안(Cybersecurity) 요구사항이 따르므로, 아키텍처 레벨에서 신뢰성을 확보하는 것이 최우선 과제이다. ## 🔗 지식 연결 (Graph) -- Parent: [[Internet of Things (IoT) Telemetry]] -- Related: [[Computational Geometry]] , [[Feedback-Control-Systems]] , [[Real-Time-Game-Engines]] -- Raw Source: [[00_Raw/Digital Twins.md]] +- Parent: [[Internet of Things (IoT) Telemetry|Internet of Things (IoT) Telemetry]] +- Related: [[Computational Geometry|Computational Geometry]] , [[Feedback-Control-Systems|Feedback-Control-Systems]] , [[Real-Time-Game-Engines|Real-Time-Game-Engines]] +- Raw Source: 00_Raw/Digital Twins.md --- \ No newline at end of file diff --git a/01_Archive/2026-04-20/Digital-Heritage-Preservation.md b/01_Archive/2026-04-20/Digital-Heritage-Preservation.md index a7736b29..091faee3 100644 --- a/01_Archive/2026-04-20/Digital-Heritage-Preservation.md +++ b/01_Archive/2026-04-20/Digital-Heritage-Preservation.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-C13BDE -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Digital-Heritage-Preservation" --- -# [[Digital-Heritage-Preservation]] +# [[Digital-Heritage-Preservation|Digital-Heritage-Preservation]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Digital-Heritage-Preservation" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Digital-Heritage-Preservation.md]] +- Raw Source: 00_Raw/2026-04-20/Digital-Heritage-Preservation.md --- diff --git a/01_Archive/2026-04-20/Digital-Humanities.md b/01_Archive/2026-04-20/Digital-Humanities.md index 90c06d3e..34d728e5 100644 --- a/01_Archive/2026-04-20/Digital-Humanities.md +++ b/01_Archive/2026-04-20/Digital-Humanities.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-B1AF91 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Digital-Humanities" --- -# [[Digital-Humanities]] +# [[Digital-Humanities|Digital-Humanities]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Digital-Humanities" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Digital-Humanities.md]] +- Raw Source: 00_Raw/2026-04-20/Digital-Humanities.md --- diff --git a/01_Archive/2026-04-20/Digital-Transformation-Strategy.md b/01_Archive/2026-04-20/Digital-Transformation-Strategy.md index bb109fbb..5ea50f00 100644 --- a/01_Archive/2026-04-20/Digital-Transformation-Strategy.md +++ b/01_Archive/2026-04-20/Digital-Transformation-Strategy.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-5767B8 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Digital-Transformation-Strategy" --- -# [[Digital-Transformation-Strategy]] +# [[Digital-Transformation-Strategy|Digital-Transformation-Strategy]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Digital-Transformation-Strateg ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Digital-Transformation-Strategy.md]] +- Raw Source: 00_Raw/2026-04-20/Digital-Transformation-Strategy.md --- diff --git a/01_Archive/2026-04-20/Digital-Twin-Technology.md b/01_Archive/2026-04-20/Digital-Twin-Technology.md index da61cc32..c802e9d0 100644 --- a/01_Archive/2026-04-20/Digital-Twin-Technology.md +++ b/01_Archive/2026-04-20/Digital-Twin-Technology.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-D08215 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Digital-Twin-Technology" --- -# [[Digital-Twin-Technology]] +# [[Digital-Twin-Technology|Digital-Twin-Technology]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Digital-Twin-Technology" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Digital-Twin-Technology.md]] +- Raw Source: 00_Raw/2026-04-20/Digital-Twin-Technology.md --- diff --git a/01_Archive/2026-04-20/Digital_Twin.md b/01_Archive/2026-04-20/Digital_Twin.md index a248c676..d5f2158b 100644 --- a/01_Archive/2026-04-20/Digital_Twin.md +++ b/01_Archive/2026-04-20/Digital_Twin.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-GRAPHICS-003 -category: "[[10_Wiki/💡 Topics/Graphics]]" +category: "10_Wiki/💡 Topics/Graphics" confidence_score: 0.92 tags: [graphics, digital-twin, hmi, iot] last_reinforced: 2026-04-20 github_commit: "batch-reinforce-04" --- -# [[Digital Twin Interfaces]] +# [[Digital Twin Interfaces|Digital Twin Interfaces]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 물리적 실체와 디지털 가상물을 실시간 데이터 혈류로 연결하여 예측 가능한 미래를 설계하는 인터페이스 기술. @@ -24,6 +24,6 @@ github_commit: "batch-reinforce-04" - **정책 변화:** 구조적 연결성(w2) 관점에서 3D_Web_HMI와의 기술적 통합 시너지 분석. ## 🔗 지식 연결 (Graph) -- **Parent:** [[10_Wiki/💡 Topics/Graphics]] -- **Related:** [[3D_Web_HMI]], [[IoT]], [[Predictive-Maintenance]] -- **Raw Source:** [[00_Raw/2026-04-20/Digital Twin Interfaces.md]] +- **Parent:** 10_Wiki/💡 Topics/Graphics +- **Related:** [[3D_Web_HMI|3D_Web_HMI]], [[IoT|IoT]], [[Predictive_Maintenance|Predictive-Maintenance]] +- **Raw Source:** 00_Raw/2026-04-20/Digital Twin Interfaces.md diff --git a/01_Archive/2026-04-20/Diminishing Returns (한계 수익 체감).md b/01_Archive/2026-04-20/Diminishing Returns (한계 수익 체감).md index 87b4d51f..83fec76d 100644 --- a/01_Archive/2026-04-20/Diminishing Returns (한계 수익 체감).md +++ b/01_Archive/2026-04-20/Diminishing Returns (한계 수익 체감).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-26A63C -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Diminishing Returns (한계 수익 체감)" --- -# [[Diminishing Returns (한계 수익 체감)]] +# [[Diminishing Returns (한계 수익 체감)|Diminishing Returns (한계 수익 체감)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Diminishing Returns (한계 ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Diminishing Returns (한계 수익 체감).md]] +- Raw Source: 00_Raw/2026-04-20/Diminishing Returns (한계 수익 체감).md --- diff --git a/01_Archive/2026-04-20/Direct3D.md b/01_Archive/2026-04-20/Direct3D.md index b54b6dba..f9e1f659 100644 --- a/01_Archive/2026-04-20/Direct3D.md +++ b/01_Archive/2026-04-20/Direct3D.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-D41B4F -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Direct3D" --- -# [[Direct3D]] +# [[Direct3D|Direct3D]] ## 📌 한 줄 통찰 (The Karpathy Summary) > Direct3D(D3D11, D3D12 등 포함)는 주요 네이티브 그래픽스 API로, Windows 환경의 웹 브라우저에서 그래픽 렌더링의 핵심 백엔드 역할을 합니다 [1, 2]. 최신 버전인 Direct3D 12는 Vulkan, Metal과 함께 차세대 웹 그래픽스 표준인 WebGPU의 설계와 아키텍처에 직접적인 영감을 준 현대적인 API입니다 [3]. @@ -22,11 +22,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Direct3D" - **정책 변화:** Graphics & Performance 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[WebGL]], [[WebGPU]], [[ANGLE]], [[Vulkan]], [[Metal]] -- **Projects/Contexts:** [[브라우저 그래픽 렌더링 백엔드]], [[Chrome WebGPU 구현]] +- **Related Topics:** [[WebGL|WebGL]], [[WebGPU|WebGPU]], [[ANGLE|ANGLE]], [[Vulkan|Vulkan]], [[Metal|Metal]] +- **Projects/Contexts:** [[브라우저 그래픽 렌더링 백엔드|브라우저 그래픽 렌더링 백엔드]], [[Chrome WebGPU 구현|Chrome WebGPU 구현]] - **Contradictions/Notes:** Direct3D 자체의 내부 구조나 깊이 있는 기술적 명세에 대해서는 소스에 관련 정보가 부족합니다. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Direct3D.md]] +- Raw Source: 00_Raw/2026-04-20/Direct3D.md --- diff --git a/01_Archive/2026-04-20/Directed-Acyclic-Graph-Build-Systems.md b/01_Archive/2026-04-20/Directed-Acyclic-Graph-Build-Systems.md index 32c53ced..7eda4c29 100644 --- a/01_Archive/2026-04-20/Directed-Acyclic-Graph-Build-Systems.md +++ b/01_Archive/2026-04-20/Directed-Acyclic-Graph-Build-Systems.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-B5202A -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Directed-Acyclic-Graph-Build-Systems" --- -# [[Directed-Acyclic-Graph-Build-Systems]] +# [[Directed-Acyclic-Graph-Build-Systems|Directed-Acyclic-Graph-Build-Systems]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Directed-Acyclic-Graph-Build-S ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Directed-Acyclic-Graph-Build-Systems.md]] +- Raw Source: 00_Raw/2026-04-20/Directed-Acyclic-Graph-Build-Systems.md --- diff --git a/01_Archive/2026-04-20/Directed-Acyclic-Graph-Dependency-Management.md b/01_Archive/2026-04-20/Directed-Acyclic-Graph-Dependency-Management.md index bd4db462..b97dcd3e 100644 --- a/01_Archive/2026-04-20/Directed-Acyclic-Graph-Dependency-Management.md +++ b/01_Archive/2026-04-20/Directed-Acyclic-Graph-Dependency-Management.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-5577CF -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Directed-Acyclic-Graph-Dependency-Management" --- -# [[Directed-Acyclic-Graph-Dependency-Management]] +# [[Directed-Acyclic-Graph-Dependency-Management|Directed-Acyclic-Graph-Dependency-Management]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Directed-Acyclic-Graph-Depende ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Directed-Acyclic-Graph-Dependency-Management.md]] +- Raw Source: 00_Raw/2026-04-20/Directed-Acyclic-Graph-Dependency-Management.md --- diff --git a/01_Archive/2026-04-20/Discriminated Unions.md b/01_Archive/2026-04-20/Discriminated Unions.md index a27d8719..5d2c3edf 100644 --- a/01_Archive/2026-04-20/Discriminated Unions.md +++ b/01_Archive/2026-04-20/Discriminated Unions.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-DEC013 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Discriminated Unions" --- -# [[Discriminated Unions]] +# [[Discriminated Unions|Discriminated Unions]] ## 📌 한 줄 통찰 (The Karpathy Summary) > Discriminated Unions(또는 식별 가능한 유니온, 태그된 유니온)은 서로 다른 데이터 형태를 구분하기 위해 공통된 리터럴 속성(판별자, Discriminant)을 사용하는 TypeScript의 패턴입니다 [1-3]. 일반적인 유니온 타입과 달리, 컴파일러가 판별자 속성을 확인하여 타입을 자동으로 안전하게 좁힐 수(Narrowing) 있게 해줍니다 [4-6]. 이를 통해 유효하지 않은 상태의 표현을 원천적으로 차단하고, 모든 가능한 경우를 처리하도록 강제하는 완전성 검사(Exhaustiveness checking)를 구현할 수 있습니다 [3, 7, 8]. @@ -30,11 +30,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Discriminated Unions" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Union Types]], [[Type Narrowing]], [[Exhaustiveness Checking]], [[Literal Types]], [[never type]] -- **Projects/Contexts:** [[React State Management]], [[State Machine Pattern]], [[API Response Handling]], [[Redux Reducers]] +- **Related Topics:** [[Union Types|Union Types]], [[Type Narrowing|Type Narrowing]], [[Exhaustiveness-Checking|Exhaustiveness Checking]], [[리터럴 타입 (Literal Types)|Literal Types]], [[네버 타입 (never type)|never type]] +- **Projects/Contexts:** React State Management, State Machine Pattern, API Response Handling, [[Redux-Reducers|Redux Reducers]] - **Contradictions/Notes:** Discriminated Union 패턴은 타입 안정성과 예측 가능성을 크게 높여주지만, 유니온 타입이 지나치게 복잡해지거나 깊은 중첩 구조를 가지게 되면 오히려 TypeScript의 컴파일 성능을 저하시키고 에러 메시지의 가독성을 떨어뜨리는 부작용(단점)을 유발할 수 있습니다 [10]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/Discriminated Unions.md]] +- Raw Source: 00_Raw/2026-04-20/Discriminated Unions.md --- diff --git a/01_Archive/2026-04-20/Discriminated-Unions-for-Error-Handling.md b/01_Archive/2026-04-20/Discriminated-Unions-for-Error-Handling.md index 993d78da..c8bb4cb0 100644 --- a/01_Archive/2026-04-20/Discriminated-Unions-for-Error-Handling.md +++ b/01_Archive/2026-04-20/Discriminated-Unions-for-Error-Handling.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-F4914A -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Discriminated-Unions-for-Error-Handling" --- -# [[Discriminated-Unions-for-Error-Handling]] +# [[Discriminated-Unions-for-Error-Handling|Discriminated-Unions-for-Error-Handling]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Discriminated-Unions-for-Error ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Discriminated-Unions-for-Error-Handling.md]] +- Raw Source: 00_Raw/2026-04-20/Discriminated-Unions-for-Error-Handling.md --- diff --git a/01_Archive/2026-04-20/Discriminated-Unions-for-State-Modeling.md b/01_Archive/2026-04-20/Discriminated-Unions-for-State-Modeling.md index df9e09d0..b123e161 100644 --- a/01_Archive/2026-04-20/Discriminated-Unions-for-State-Modeling.md +++ b/01_Archive/2026-04-20/Discriminated-Unions-for-State-Modeling.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-326E8C -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Discriminated-Unions-for-State-Modeling" --- -# [[Discriminated-Unions-for-State-Modeling]] +# [[Discriminated-Unions-for-State-Modeling|Discriminated-Unions-for-State-Modeling]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Discriminated-Unions-for-State ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Discriminated-Unions-for-State-Modeling.md]] +- Raw Source: 00_Raw/2026-04-20/Discriminated-Unions-for-State-Modeling.md --- diff --git a/01_Archive/2026-04-20/Discriminated-Unions.md b/01_Archive/2026-04-20/Discriminated-Unions.md index f75978cd..e62ca856 100644 --- a/01_Archive/2026-04-20/Discriminated-Unions.md +++ b/01_Archive/2026-04-20/Discriminated-Unions.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-1AAB27 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Discriminated-Unions" --- -# [[Discriminated-Unions]] +# [[Discriminated-Unions|Discriminated-Unions]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Discriminated-Unions" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Discriminated-Unions.md]] +- Raw Source: 00_Raw/2026-04-20/Discriminated-Unions.md --- diff --git a/01_Archive/2026-04-20/Disentanglement (개념 분리).md b/01_Archive/2026-04-20/Disentanglement (개념 분리).md index cb6f6591..82a3cc65 100644 --- a/01_Archive/2026-04-20/Disentanglement (개념 분리).md +++ b/01_Archive/2026-04-20/Disentanglement (개념 분리).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-3C9639 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Disentanglement (개념 분리)" --- -# [[Disentanglement (개념 분리)]] +# [[Disentanglement (개념 분리)|Disentanglement (개념 분리)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Disentanglement (개념 분리 ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Disentanglement (개념 분리).md]] +- Raw Source: 00_Raw/2026-04-20/Disentanglement (개념 분리).md --- diff --git a/01_Archive/2026-04-20/Dissipative Structures.md b/01_Archive/2026-04-20/Dissipative Structures.md index c011afd1..80b586d1 100644 --- a/01_Archive/2026-04-20/Dissipative Structures.md +++ b/01_Archive/2026-04-20/Dissipative Structures.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-25ABE0 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Dissipative Structures" --- -# [[Dissipative Structures]] +# [[Dissipative Structures|Dissipative Structures]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Dissipative Structures" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Dissipative Structures.md]] +- Raw Source: 00_Raw/2026-04-20/Dissipative Structures.md --- diff --git a/01_Archive/2026-04-20/Distributed-System-Type-Safety.md b/01_Archive/2026-04-20/Distributed-System-Type-Safety.md index 4426efde..f1aff32d 100644 --- a/01_Archive/2026-04-20/Distributed-System-Type-Safety.md +++ b/01_Archive/2026-04-20/Distributed-System-Type-Safety.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-1E4141 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Distributed-System-Type-Safety" --- -# [[Distributed-System-Type-Safety]] +# [[Distributed-System-Type-Safety|Distributed-System-Type-Safety]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Distributed-System-Type-Safety ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Distributed-System-Type-Safety.md]] +- Raw Source: 00_Raw/2026-04-20/Distributed-System-Type-Safety.md --- diff --git a/01_Archive/2026-04-20/Distributed-Systems-Engineering.md b/01_Archive/2026-04-20/Distributed-Systems-Engineering.md index bf90c3bf..d047f05f 100644 --- a/01_Archive/2026-04-20/Distributed-Systems-Engineering.md +++ b/01_Archive/2026-04-20/Distributed-Systems-Engineering.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AI-051 -category: "[[10_Wiki/💡 Topics/System Architecture & Reliability]]" +category: "10_Wiki/💡 Topics/System Architecture & Reliability" confidence_score: 0.98 tags: [distributed system, distributed computing, consistency, fault tolerance] last_reinforced: 2026-06-XX github_commit: "[P-Reinforce] Processed Distributed-Systems-Engineering." --- -# [[Distributed-Systems-Engineering]] (분산 시스템 공학) +# [[Distributed-Systems-Engineering|Distributed-Systems-Engineering]] (분산 시스템 공학) ## 📌 한 줄 통찰 (The Karpathy Summary) > 여러 독립적인 컴퓨터가 네트워크를 통해 협력하여 하나의 거대한 작업을 수행할 때 발생하는 복잡성(지연, 일관성, 장애 처리)을 체계적으로 관리하고 안정성을 확보하는 학문이다. @@ -24,7 +24,7 @@ github_commit: "[P-Reinforce] Processed Distributed-Systems-Engineering." - **정책 변화:** 서비스 메쉬 (Service Mesh) 기술의 도입으로, 로드 밸런싱, 트래픽 제어, 인증/인가 등의 기능을 애플리케이션 코드 외부에서 네트워크 레벨로 분리하여 관리하는 것이 표준화되었다. ## 🔗 지식 연결 (Graph) -- Parent: [[Microservices-Architecture]] -- Related: [[CAP Theorem]] , [[Saga Pattern]] , [[Circuit Breaker]] -- Raw Source: [[00_Raw/Distributed-Systems-Engineering.md]] +- Parent: [[Microservices-Architecture|Microservices-Architecture]] +- Related: [[CAP-Theorem|CAP Theorem]] , Saga Pattern , Circuit Breaker +- Raw Source: 00_Raw/Distributed-Systems-Engineering.md --- \ No newline at end of file diff --git a/01_Archive/2026-04-20/Divergent-Thinking.md b/01_Archive/2026-04-20/Divergent-Thinking.md index d588b6eb..0549e829 100644 --- a/01_Archive/2026-04-20/Divergent-Thinking.md +++ b/01_Archive/2026-04-20/Divergent-Thinking.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-52E973 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Divergent-Thinking" --- -# [[Divergent-Thinking]] +# [[Divergent-Thinking|Divergent-Thinking]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Divergent-Thinking" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Divergent-Thinking.md]] +- Raw Source: 00_Raw/2026-04-20/Divergent-Thinking.md --- diff --git a/01_Archive/2026-04-20/Domain Objects.md b/01_Archive/2026-04-20/Domain Objects.md index 13ed12cb..e702e7c0 100644 --- a/01_Archive/2026-04-20/Domain Objects.md +++ b/01_Archive/2026-04-20/Domain Objects.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-17D3D3 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Domain Objects" --- -# [[Domain Objects]] +# [[Domain Objects|Domain Objects]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 도메인 객체(Domain Objects)는 비즈니스 개념을 표현하고 전사적인 비즈니스 규칙과 데이터 구조를 캡슐화하는 핵심 객체입니다 [1, 2]. 소프트웨어 아키텍처의 가장 중심부에 위치하며 프레임워크나 사용자 인터페이스(UI), 데이터베이스 등 외부 계층에 전혀 의존하지 않고 독립적으로 존재합니다 [1, 3]. 복잡한 비즈니스 로직을 명확하게 모델링하고 시스템의 근본적인 뼈대를 형성하는 데 필수적인 역할을 합니다 [1, 4]. @@ -25,11 +25,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Domain Objects" - **정책 변화:** AI 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Domain-Driven Design]], [[Clean Architecture]], [[Entities]], [[Aggregates]] -- **Projects/Contexts:** [[쇼핑 애플리케이션 도메인 모델]] +- **Related Topics:** [[Domain-Driven-Design|Domain-Driven Design]], [[Clean Architecture|Clean Architecture]], [[엔티티 (Entities)|Entities]], [[애그리거트 (Aggregates)|Aggregates]] +- **Projects/Contexts:** 쇼핑 애플리케이션 도메인 모델 - **Contradictions/Notes:** 소스 내에서 도메인 객체에 대한 모순이나 상반된 주장은 존재하지 않으며, 일관되게 시스템의 핵심 비즈니스 로직을 캡슐화하고 외부 의존성으로부터 철저히 분리되어야 하는 대상으로 강조됩니다 [1-3]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/Domain Objects.md]] +- Raw Source: 00_Raw/2026-04-20/Domain Objects.md --- diff --git a/01_Archive/2026-04-20/Domain-Driven Design (DDD) Type Safety.md b/01_Archive/2026-04-20/Domain-Driven Design (DDD) Type Safety.md index 55d61020..7d03ab32 100644 --- a/01_Archive/2026-04-20/Domain-Driven Design (DDD) Type Safety.md +++ b/01_Archive/2026-04-20/Domain-Driven Design (DDD) Type Safety.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-BE347F -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Domain-Driven Design (DDD) Type Safety" --- -# [[Domain-Driven Design (DDD) Type Safety]] +# [[Domain-Driven Design (DDD) Type Safety|Domain-Driven Design (DDD) Type Safety]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Domain-Driven Design (DDD) Typ ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Domain-Driven Design (DDD) Type Safety.md]] +- Raw Source: 00_Raw/2026-04-20/Domain-Driven Design (DDD) Type Safety.md --- diff --git a/01_Archive/2026-04-20/Domain-Driven Design (DDD) in TypeScript.md b/01_Archive/2026-04-20/Domain-Driven Design (DDD) in TypeScript.md index f7641527..8cad9cca 100644 --- a/01_Archive/2026-04-20/Domain-Driven Design (DDD) in TypeScript.md +++ b/01_Archive/2026-04-20/Domain-Driven Design (DDD) in TypeScript.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-F89598 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Domain-Driven Design (DDD) in TypeScript" --- -# [[Domain-Driven Design (DDD) in TypeScript]] +# [[Domain-Driven Design (DDD) in TypeScript|Domain-Driven Design (DDD) in TypeScript]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Domain-Driven Design (DDD) in ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Domain-Driven Design (DDD) in TypeScript.md]] +- Raw Source: 00_Raw/2026-04-20/Domain-Driven Design (DDD) in TypeScript.md --- diff --git a/01_Archive/2026-04-20/Domain-Driven Design (DDD).md b/01_Archive/2026-04-20/Domain-Driven Design (DDD).md index 316c8458..e6d8d025 100644 --- a/01_Archive/2026-04-20/Domain-Driven Design (DDD).md +++ b/01_Archive/2026-04-20/Domain-Driven Design (DDD).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AI-048 -category: "[[10_Wiki/💡 Topics/Software Architecture]]" +category: "10_Wiki/💡 Topics/Software Architecture" confidence_score: 0.99 tags: [ddd, bounded context, domain modeling, software architecture] last_reinforced: 2026-06-XX github_commit: "[P-Reinforce] Processed Domain-Driven Design (DDD)." --- -# [[Domain-Driven Design (DDD)]] (도메인 주도 설계) +# [[Domain-Driven Design (DDD)|Domain-Driven Design (DDD)]] (도메인 주도 설계) ## 📌 한 줄 통찰 (The Karpathy Summary) > 소프트웨어의 복잡성을 관리하기 위해, 비즈니스 도메인의 핵심 개념(Ubiquitous Language)을 중심으로 시스템 경계(Bounded Context)를 설정하고 모델링하는 접근 방식이다. @@ -24,7 +24,7 @@ github_commit: "[P-Reinforce] Processed Domain-Driven Design (DDD)." - **정책 변화:** 마이크로서비스 아키텍처와 매우 높은 시너지를 내며, 각 서비스가 하나의 Bounded Context를 담당하도록 경계를 설정하는 것이 일반적이다. ## 🔗 지식 연결 (Graph) -- Parent: [[Microservices-Architecture]] -- Related: [[Bounded Contexts]] , [[Ubiquitous Language]] , [[Aggregate Root]] -- Raw Source: [[00_Raw/Domain-Driven Design (DDD).md]] +- Parent: [[Microservices-Architecture|Microservices-Architecture]] +- Related: [[Bounded Contexts|Bounded Contexts]] , [[보편적 언어 (Ubiquitous Language)|Ubiquitous Language]] , Aggregate Root +- Raw Source: 00_Raw/Domain-Driven Design (DDD).md --- \ No newline at end of file diff --git a/01_Archive/2026-04-20/Domain-Driven-Design (DDD) in TypeScript.md b/01_Archive/2026-04-20/Domain-Driven-Design (DDD) in TypeScript.md index ce74c7d6..1c1fffc9 100644 --- a/01_Archive/2026-04-20/Domain-Driven-Design (DDD) in TypeScript.md +++ b/01_Archive/2026-04-20/Domain-Driven-Design (DDD) in TypeScript.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-D7AB12 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Domain-Driven-Design (DDD) in TypeScript" --- -# [[Domain-Driven-Design (DDD) in TypeScript]] +# [[Domain-Driven-Design (DDD) in TypeScript|Domain-Driven-Design (DDD) in TypeScript]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Domain-Driven-Design (DDD) in ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Domain-Driven-Design (DDD) in TypeScript.md]] +- Raw Source: 00_Raw/2026-04-20/Domain-Driven-Design (DDD) in TypeScript.md --- diff --git a/01_Archive/2026-04-20/Domain-Driven-Design (DDD).md b/01_Archive/2026-04-20/Domain-Driven-Design (DDD).md index 8bef2790..298aefc8 100644 --- a/01_Archive/2026-04-20/Domain-Driven-Design (DDD).md +++ b/01_Archive/2026-04-20/Domain-Driven-Design (DDD).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-7AB40D -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Domain-Driven-Design (DDD)" --- -# [[Domain-Driven-Design (DDD)]] +# [[Domain-Driven-Design (DDD)|Domain-Driven-Design (DDD)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Domain-Driven-Design (DDD)" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Domain-Driven-Design (DDD).md]] +- Raw Source: 00_Raw/2026-04-20/Domain-Driven-Design (DDD).md --- diff --git a/01_Archive/2026-04-20/Domain-Driven-Design-(DDD)-in-TypeScript.md b/01_Archive/2026-04-20/Domain-Driven-Design-(DDD)-in-TypeScript.md index aadbe9a8..d16dc1d5 100644 --- a/01_Archive/2026-04-20/Domain-Driven-Design-(DDD)-in-TypeScript.md +++ b/01_Archive/2026-04-20/Domain-Driven-Design-(DDD)-in-TypeScript.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-13548A -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Domain-Driven-Design-(DDD)-in-TypeScript" --- -# [[Domain-Driven-Design-(DDD)-in-TypeScript]] +# [[Domain-Driven-Design-(DDD)-in-TypeScript|Domain-Driven-Design-(DDD)-in-TypeScript]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Domain-Driven-Design-(DDD)-in- ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Domain-Driven-Design-(DDD)-in-TypeScript.md]] +- Raw Source: 00_Raw/2026-04-20/Domain-Driven-Design-(DDD)-in-TypeScript.md --- diff --git a/01_Archive/2026-04-20/Domain-Driven-Design-(DDD).md b/01_Archive/2026-04-20/Domain-Driven-Design-(DDD).md index 7a59df16..20d08d90 100644 --- a/01_Archive/2026-04-20/Domain-Driven-Design-(DDD).md +++ b/01_Archive/2026-04-20/Domain-Driven-Design-(DDD).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-C360C0 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Domain-Driven-Design-(DDD)" --- -# [[Domain-Driven-Design-(DDD)]] +# [[Domain-Driven-Design-(DDD)|Domain-Driven-Design-(DDD)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Domain-Driven-Design-(DDD)" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Domain-Driven-Design-(DDD).md]] +- Raw Source: 00_Raw/2026-04-20/Domain-Driven-Design-(DDD).md --- diff --git a/01_Archive/2026-04-20/Domain-Driven-Design-Bounded-Context.md b/01_Archive/2026-04-20/Domain-Driven-Design-Bounded-Context.md index 396e23d4..215ec971 100644 --- a/01_Archive/2026-04-20/Domain-Driven-Design-Bounded-Context.md +++ b/01_Archive/2026-04-20/Domain-Driven-Design-Bounded-Context.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-551739 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Domain-Driven-Design-Bounded-Context" --- -# [[Domain-Driven-Design-Bounded-Context]] +# [[Domain-Driven-Design-Bounded-Context|Domain-Driven-Design-Bounded-Context]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Domain-Driven-Design-Bounded-C ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Domain-Driven-Design-Bounded-Context.md]] +- Raw Source: 00_Raw/2026-04-20/Domain-Driven-Design-Bounded-Context.md --- diff --git a/01_Archive/2026-04-20/Domain-Driven-Design-Interface-Modeling.md b/01_Archive/2026-04-20/Domain-Driven-Design-Interface-Modeling.md index f16e4017..b447e896 100644 --- a/01_Archive/2026-04-20/Domain-Driven-Design-Interface-Modeling.md +++ b/01_Archive/2026-04-20/Domain-Driven-Design-Interface-Modeling.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-BE83DE -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Domain-Driven-Design-Interface-Modeling" --- -# [[Domain-Driven-Design-Interface-Modeling]] +# [[Domain-Driven-Design-Interface-Modeling|Domain-Driven-Design-Interface-Modeling]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Domain-Driven-Design-Interface ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Domain-Driven-Design-Interface-Modeling.md]] +- Raw Source: 00_Raw/2026-04-20/Domain-Driven-Design-Interface-Modeling.md --- diff --git a/01_Archive/2026-04-20/Domain-Driven-Design-in-TypeScript.md b/01_Archive/2026-04-20/Domain-Driven-Design-in-TypeScript.md index cc2f20ca..817f4ed8 100644 --- a/01_Archive/2026-04-20/Domain-Driven-Design-in-TypeScript.md +++ b/01_Archive/2026-04-20/Domain-Driven-Design-in-TypeScript.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-21D02B -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Domain-Driven-Design-in-TypeScript" --- -# [[Domain-Driven-Design-in-TypeScript]] +# [[Domain-Driven-Design-in-TypeScript|Domain-Driven-Design-in-TypeScript]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Domain-Driven-Design-in-TypeSc ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Domain-Driven-Design-in-TypeScript.md]] +- Raw Source: 00_Raw/2026-04-20/Domain-Driven-Design-in-TypeScript.md --- diff --git a/01_Archive/2026-04-20/Domain-Driven-Design-with-TypeScript.md b/01_Archive/2026-04-20/Domain-Driven-Design-with-TypeScript.md index 9de9cabf..894c378a 100644 --- a/01_Archive/2026-04-20/Domain-Driven-Design-with-TypeScript.md +++ b/01_Archive/2026-04-20/Domain-Driven-Design-with-TypeScript.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-7451F4 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Domain-Driven-Design-with-TypeScript" --- -# [[Domain-Driven-Design-with-TypeScript]] +# [[Domain-Driven-Design-with-TypeScript|Domain-Driven-Design-with-TypeScript]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Domain-Driven-Design-with-Type ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Domain-Driven-Design-with-TypeScript.md]] +- Raw Source: 00_Raw/2026-04-20/Domain-Driven-Design-with-TypeScript.md --- diff --git a/01_Archive/2026-04-20/Domain-Driven-Design.md b/01_Archive/2026-04-20/Domain-Driven-Design.md index 8dcd7d05..5d36f210 100644 --- a/01_Archive/2026-04-20/Domain-Driven-Design.md +++ b/01_Archive/2026-04-20/Domain-Driven-Design.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-CD0693 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Domain-Driven-Design" --- -# [[Domain-Driven-Design]] +# [[Domain-Driven-Design|Domain-Driven-Design]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Domain-Driven-Design" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Domain-Driven-Design.md]] +- Raw Source: 00_Raw/2026-04-20/Domain-Driven-Design.md --- diff --git a/01_Archive/2026-04-20/Dopamine Signaling.md b/01_Archive/2026-04-20/Dopamine Signaling.md index cd95038a..08bd1f53 100644 --- a/01_Archive/2026-04-20/Dopamine Signaling.md +++ b/01_Archive/2026-04-20/Dopamine Signaling.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-C204E9 -category: "[[10_Wiki/💡 Topics/General Knowledge]]" +category: "10_Wiki/💡 Topics/General Knowledge" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Dopamine Signaling" --- -# [[Dopamine Signaling]] +# [[Dopamine Signaling|Dopamine Signaling]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Dopamine Signaling" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Dopamine Signaling.md]] +- Raw Source: 00_Raw/2026-04-20/Dopamine Signaling.md --- diff --git a/01_Archive/2026-04-20/Dopamine.md b/01_Archive/2026-04-20/Dopamine.md index 19567d9a..552fa294 100644 --- a/01_Archive/2026-04-20/Dopamine.md +++ b/01_Archive/2026-04-20/Dopamine.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-PSYCH-003 -category: "[[10_Wiki/💡 Topics/Psychology]]" +category: "10_Wiki/💡 Topics/Psychology" confidence_score: 0.96 tags: [psychology, neuroscience, dopamine, reward] last_reinforced: 2026-04-20 github_commit: "batch-reinforce-03" --- -# [[Dopamine Signaling]] +# [[Dopamine Signaling|Dopamine Signaling]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 보상 그 자체보다 '보상에 대한 기대'와 '학습의 신호'로서 작동하며 행동의 동기를 부여하는 뇌의 화학적 메신저. @@ -24,6 +24,6 @@ github_commit: "batch-reinforce-03" - **정책 변화:** 중독(w1) 분석 시 도파민 수용체 하향 조절(Downregulation) 가중치 반영. ## 🔗 지식 연결 (Graph) -- **Parent:** [[10_Wiki/💡 Topics/Psychology]] -- **Related:** [[Addiction_Neuroscience]], [[Reward-System]], [[Neurotransmitter]] -- **Raw Source:** [[00_Raw/2026-04-20/Dopamine Signaling.md]] +- **Parent:** 10_Wiki/💡 Topics/Psychology +- **Related:** [[Addiction_Neuroscience|Addiction_Neuroscience]], Reward-System, Neurotransmitter +- **Raw Source:** 00_Raw/2026-04-20/Dopamine Signaling.md diff --git a/01_Archive/2026-04-20/Dopaminergic Reward System.md b/01_Archive/2026-04-20/Dopaminergic Reward System.md index 0c1d78b6..2d410a2b 100644 --- a/01_Archive/2026-04-20/Dopaminergic Reward System.md +++ b/01_Archive/2026-04-20/Dopaminergic Reward System.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-1CE0DE -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Dopaminergic Reward System" --- -# [[Dopaminergic Reward System]] +# [[Dopaminergic Reward System|Dopaminergic Reward System]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Dopaminergic Reward System" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Dopaminergic Reward System.md]] +- Raw Source: 00_Raw/2026-04-20/Dopaminergic Reward System.md --- diff --git a/01_Archive/2026-04-20/Dopaminergic Reward Systems.md b/01_Archive/2026-04-20/Dopaminergic Reward Systems.md index f7d5dcaf..e08f9522 100644 --- a/01_Archive/2026-04-20/Dopaminergic Reward Systems.md +++ b/01_Archive/2026-04-20/Dopaminergic Reward Systems.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-73B204 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Dopaminergic Reward Systems" --- -# [[Dopaminergic Reward Systems]] +# [[Dopaminergic Reward Systems|Dopaminergic Reward Systems]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Dopaminergic Reward Systems" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Dopaminergic Reward Systems.md]] +- Raw Source: 00_Raw/2026-04-20/Dopaminergic Reward Systems.md --- diff --git a/01_Archive/2026-04-20/Drama Management Systems.md b/01_Archive/2026-04-20/Drama Management Systems.md index e52f97df..dfd4f2e7 100644 --- a/01_Archive/2026-04-20/Drama Management Systems.md +++ b/01_Archive/2026-04-20/Drama Management Systems.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-893F79 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Drama Management Systems" --- -# [[Drama Management Systems]] +# [[Drama Management Systems|Drama Management Systems]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Drama Management Systems" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Drama Management Systems.md]] +- Raw Source: 00_Raw/2026-04-20/Drama Management Systems.md --- diff --git a/01_Archive/2026-04-20/Drama-Management-Systems.md b/01_Archive/2026-04-20/Drama-Management-Systems.md index 8f21b4f8..71f8f403 100644 --- a/01_Archive/2026-04-20/Drama-Management-Systems.md +++ b/01_Archive/2026-04-20/Drama-Management-Systems.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-6D19F6 -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Drama-Management-Systems" --- -# [[Drama-Management-Systems]] +# [[Drama-Management-Systems|Drama-Management-Systems]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Drama-Management-Systems" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Drama-Management-Systems.md]] +- Raw Source: 00_Raw/2026-04-20/Drama-Management-Systems.md --- diff --git a/01_Archive/2026-04-20/Draw Call Optimization.md b/01_Archive/2026-04-20/Draw Call Optimization.md index ccc40ba1..94d97678 100644 --- a/01_Archive/2026-04-20/Draw Call Optimization.md +++ b/01_Archive/2026-04-20/Draw Call Optimization.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-0B8FFC -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Draw Call Optimization" --- -# [[Draw Call Optimization]] +# [[Draw Call Optimization|Draw Call Optimization]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 드로우 콜(Draw Call)은 CPU가 GPU에게 기하학적 구조, 재질, 렌더링 지침 등을 전달하여 화면에 객체를 그리도록 내리는 명령입니다 [1-3]. 각 드로우 콜을 준비하고 상태를 변경하는 과정에서 막대한 CPU 오버헤드가 발생하기 때문에, 드로우 콜 횟수를 줄이는 것은 애플리케이션의 프레임 속도와 전반적인 렌더링 성능을 개선하고 병목 현상을 방지하는 핵심 최적화 기법입니다 [4-6]. @@ -26,11 +26,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Draw Call Optimization" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[InstancedMesh]], [[BatchedMesh]], [[Frustum Culling]], [[Texture Atlas]], [[Level of Detail (LOD)]] -- **Projects/Contexts:** [[Three.js]], [[WebGL]], [[Unity]] +- **Related Topics:** [[InstancedMesh|InstancedMesh]], [[BatchedMesh|BatchedMesh]], [[Frustum Culling|Frustum Culling]], [[Texture Atlas|Texture Atlas]], [[Level of Detail (LOD)|Level of Detail (LOD)]] +- **Projects/Contexts:** [[Three.js|Three.js]], [[WebGL|WebGL]], [[Unity|Unity]] - **Contradictions/Notes:** 일반적으로 드로우 콜을 줄이는 것은 렌더링 성능을 향상시킨다고 알려져 있지만, `InstancedMesh`를 통해 드로우 콜을 1회로 줄였음에도 불구하고 정렬되지 않은 인스턴스들이 유발하는 막대한 오버드로우(Overdraw) 비용이나 비효율적인 컬링으로 인해, 개별 메쉬를 렌더링할 때보다 오히려 프레임 속도(FPS)가 낮아지는 역설적인 상황이 실증적 연구와 버그 리포트 등에서 보고되고 있습니다 [29, 31, 35]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Draw Call Optimization.md]] +- Raw Source: 00_Raw/2026-04-20/Draw Call Optimization.md --- diff --git a/01_Archive/2026-04-20/Draw Call.md b/01_Archive/2026-04-20/Draw Call.md index be333249..1f5d5dbd 100644 --- a/01_Archive/2026-04-20/Draw Call.md +++ b/01_Archive/2026-04-20/Draw Call.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-E9A644 -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Draw Call" --- -# [[Draw Call]] +# [[Draw Call|Draw Call]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 드로우 콜(Draw Call)은 CPU가 GPU에게 렌더링할 기하학적 구조, 재질 및 렌더링 상태를 전달하며 객체를 화면에 그리도록 지시하는 명령입니다 [1, 2]. 실제 그래픽을 렌더링하는 연산 자체보다, 렌더링을 준비하고 상태를 변경하는 과정에서 발생하는 CPU 오버헤드가 매우 커서 성능 병목의 주된 원인이 됩니다 [3-5]. 따라서 실시간 3D 그래픽 애플리케이션에서는 높은 프레임 속도 유지를 위해 인스턴싱, 배칭, 지오메트리 병합 등의 최적화 기법을 통해 드로우 콜의 횟수를 최소화해야 합니다 [6-9]. @@ -29,11 +29,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Draw Call" - **정책 변화:** Graphics & Performance 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Render State]], [[CPU Bottleneck]], [[InstancedMesh]], [[BatchedMesh]], [[Geometry Merging]], [[Texture Atlas]] -- **Projects/Contexts:** [[Three.js]], [[WebGL]], [[WebGPU]], [[Unity]] +- **Related Topics:** [[Render State|Render State]], [[CPU Bottleneck|CPU Bottleneck]], [[InstancedMesh|InstancedMesh]], [[BatchedMesh|BatchedMesh]], [[Geometry Merging|Geometry Merging]], [[Texture Atlas|Texture Atlas]] +- **Projects/Contexts:** [[Three.js|Three.js]], [[WebGL|WebGL]], [[WebGPU|WebGPU]], [[Unity|Unity]] - **Contradictions/Notes:** 소스에 따르면, 드로우 콜을 1회로 줄이는 것(`InstancedMesh` 등의 도입)이 무조건 프레임 속도 상승으로 이어지지는 않습니다. 수만 개의 객체가 하나의 드로우 콜로 묶이게 되면 엔진의 시야 절두체 컬링(Frustum Culling) 정밀도가 떨어지거나 투명 객체의 정렬(Sorting) 부재로 인해 막대한 오버드로우(Overdraw)가 발생하여, 결과적으로 CPU 명령은 줄어도 GPU 연산량은 오히려 기하급수적으로 늘어나는 현상이 일어날 수 있습니다 [10, 20-22]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Draw Call.md]] +- Raw Source: 00_Raw/2026-04-20/Draw Call.md --- diff --git a/01_Archive/2026-04-20/Dual-Track-Agile.md b/01_Archive/2026-04-20/Dual-Track-Agile.md index 439a5702..bcb4b3e5 100644 --- a/01_Archive/2026-04-20/Dual-Track-Agile.md +++ b/01_Archive/2026-04-20/Dual-Track-Agile.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-92B7C5 -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Dual-Track-Agile" --- -# [[Dual-Track-Agile]] +# [[Dual-Track-Agile|Dual-Track-Agile]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Dual-Track-Agile" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Dual-Track-Agile.md]] +- Raw Source: 00_Raw/2026-04-20/Dual-Track-Agile.md --- diff --git a/01_Archive/2026-04-20/Dublin Core Metadata Initiative.md b/01_Archive/2026-04-20/Dublin Core Metadata Initiative.md index 2327d14d..8df6012f 100644 --- a/01_Archive/2026-04-20/Dublin Core Metadata Initiative.md +++ b/01_Archive/2026-04-20/Dublin Core Metadata Initiative.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-4C7308 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Dublin Core Metadata Initiative" --- -# [[Dublin Core Metadata Initiative]] +# [[Dublin Core Metadata Initiative|Dublin Core Metadata Initiative]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Dublin Core Metadata Initiativ ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Dublin Core Metadata Initiative.md]] +- Raw Source: 00_Raw/2026-04-20/Dublin Core Metadata Initiative.md --- diff --git a/01_Archive/2026-04-20/Duck-Typing.md b/01_Archive/2026-04-20/Duck-Typing.md index 0531c7e3..7e34330e 100644 --- a/01_Archive/2026-04-20/Duck-Typing.md +++ b/01_Archive/2026-04-20/Duck-Typing.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-31CA9B -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Duck-Typing" --- -# [[Duck-Typing]] +# [[Duck-Typing|Duck-Typing]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Duck-Typing" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Duck-Typing.md]] +- Raw Source: 00_Raw/2026-04-20/Duck-Typing.md --- diff --git a/01_Archive/2026-04-20/Duolingo (Language Learning)] [Fitness Tracking Apps (Strava_Fitbit)] [EdTech Gamification] [FinTech Engagement Strategies.md b/01_Archive/2026-04-20/Duolingo (Language Learning)] [Fitness Tracking Apps (Strava_Fitbit)] [EdTech Gamification] [FinTech Engagement Strategies.md index 5525c230..03864962 100644 --- a/01_Archive/2026-04-20/Duolingo (Language Learning)] [Fitness Tracking Apps (Strava_Fitbit)] [EdTech Gamification] [FinTech Engagement Strategies.md +++ b/01_Archive/2026-04-20/Duolingo (Language Learning)] [Fitness Tracking Apps (Strava_Fitbit)] [EdTech Gamification] [FinTech Engagement Strategies.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-259FF2 -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Duolingo (Language Learning)] [Fitness Tracking Apps (Strava_Fitbit)] [EdTech Gamification] [FinTech Engagement Strategies" --- -# [[Duolingo (Language Learning)] [Fitness Tracking Apps (Strava_Fitbit)] [EdTech Gamification] [FinTech Engagement Strategies]] +# [[Duolingo (Language Learning)] [Fitness Tracking Apps (Strava_Fitbit)] [EdTech Gamification] [FinTech Engagement Strategies|Duolingo (Language Learning)] [Fitness Tracking Apps (Strava_Fitbit)] [EdTech Gamification] [FinTech Engagement Strategies]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Duolingo (Language Learning)] ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Duolingo (Language Learning)], [Fitness Tracking Apps (Strava_Fitbit)], [EdTech Gamification], [FinTech Engagement Strategies.md]] +- Raw Source: 00_Raw/2026-04-20/Duolingo (Language Learning)], [Fitness Tracking Apps (Strava_Fitbit)], [EdTech Gamification], [FinTech Engagement Strategies.md --- diff --git a/01_Archive/2026-04-20/Duolingo (Language Learning)], [Fitness Tracking Apps (Strava_Fitbit)], [EdTech Gamification], [FinTech Engagement Strategies.md b/01_Archive/2026-04-20/Duolingo (Language Learning)], [Fitness Tracking Apps (Strava_Fitbit)], [EdTech Gamification], [FinTech Engagement Strategies.md index 6a2b1632..053d3f1b 100644 --- a/01_Archive/2026-04-20/Duolingo (Language Learning)], [Fitness Tracking Apps (Strava_Fitbit)], [EdTech Gamification], [FinTech Engagement Strategies.md +++ b/01_Archive/2026-04-20/Duolingo (Language Learning)], [Fitness Tracking Apps (Strava_Fitbit)], [EdTech Gamification], [FinTech Engagement Strategies.md @@ -1,4 +1,4 @@ -[[Duolingo (Language Learning)], [Fitness Tracking Apps (Strava/Fitbit)], [EdTech Gamification], [FinTech Engagement Strategies]] +[[Duolingo (Language Learning)] [Fitness Tracking Apps (Strava_Fitbit)] [EdTech Gamification] [FinTech Engagement Strategies|Duolingo (Language Learning)], [Fitness Tracking Apps (Strava/Fitbit)], [EdTech Gamification], [FinTech Engagement Strategies]] 📌 Brief Summary This research synthesis examines the convergence of behavioral economics and gamification frameworks across diverse digital sectors. It analyzes how Duolingo, Strava, and Fitbit utilize variable reward schedules and social proof to drive habit formation, alongside the application of these engagement strategies within EdTech and FinTech ecosystems to mitigate churn and increase user lifetime value (LTV). @@ -21,8 +21,8 @@ The integration of gamification mechanics—specifically Octalysis-style drivers * **Nudge Theory in Financial Literacy:** Utilizing push notifications as "nudges" to redirect user behavior toward high-yield savings or debt reduction, mirroring the instructional nudges found in EdTech. 🔗 Knowledge Connections -* Related Topics: [[Behavioral Economics]], [[Dopaminergic Reward Systems]], [[The Octalysis Framework]], [[Habit Loop Theory (Cue-Routine-Reward)]] -* Projects/Contexts: [[Digital Transformation of Consumer Behavior]], [[User Retention Optimization in SaaS]], [[Cognitive Load Theory in UX Design]] +* Related Topics: [[Behavioral Economics|Behavioral Economics]], [[Dopaminergic Reward Systems|Dopaminergic Reward Systems]], The Octalysis Framework, Habit Loop Theory (Cue-Routine-Reward) +* Projects/Contexts: Digital Transformation of Consumer Behavior, User Retention Optimization in SaaS, Cognitive Load Theory in UX Design * Contradictions/Notes: There is an ongoing debate regarding "Dark Patterns" in gamification; while streaks increase retention, critics argue they can lead to user burnout and toxic compulsion (the "Zeigarnik Effect" gone wrong). Last updated: 2026-04-16 \ No newline at end of file diff --git a/01_Archive/2026-04-20/Dwarf Fortress (Simulation-heavy PCG).md b/01_Archive/2026-04-20/Dwarf Fortress (Simulation-heavy PCG).md index 2a2744f9..f10d1c87 100644 --- a/01_Archive/2026-04-20/Dwarf Fortress (Simulation-heavy PCG).md +++ b/01_Archive/2026-04-20/Dwarf Fortress (Simulation-heavy PCG).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-D6FB1C -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Dwarf Fortress (Simulation-heavy PCG)" --- -# [[Dwarf Fortress (Simulation-heavy PCG)]] +# [[Dwarf Fortress (Simulation-heavy PCG)|Dwarf Fortress (Simulation-heavy PCG)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Dwarf Fortress (Simulation-hea ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Dwarf Fortress (Simulation-heavy PCG).md]] +- Raw Source: 00_Raw/2026-04-20/Dwarf Fortress (Simulation-heavy PCG).md --- diff --git a/01_Archive/2026-04-20/Dwarf Fortress.md b/01_Archive/2026-04-20/Dwarf Fortress.md index 0c4abdd8..a5e7c279 100644 --- a/01_Archive/2026-04-20/Dwarf Fortress.md +++ b/01_Archive/2026-04-20/Dwarf Fortress.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-8B5736 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Dwarf Fortress" --- -# [[Dwarf Fortress]] +# [[Dwarf Fortress|Dwarf Fortress]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Dwarf Fortress" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Dwarf Fortress.md]] +- Raw Source: 00_Raw/2026-04-20/Dwarf Fortress.md --- diff --git a/01_Archive/2026-04-20/Dwarf-Fortress.md b/01_Archive/2026-04-20/Dwarf-Fortress.md index 96fc827d..69260300 100644 --- a/01_Archive/2026-04-20/Dwarf-Fortress.md +++ b/01_Archive/2026-04-20/Dwarf-Fortress.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-1E23B6 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Dwarf-Fortress" --- -# [[Dwarf-Fortress]] +# [[Dwarf-Fortress|Dwarf-Fortress]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Dwarf-Fortress" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Dwarf-Fortress.md]] +- Raw Source: 00_Raw/2026-04-20/Dwarf-Fortress.md --- diff --git a/01_Archive/2026-04-20/Dynamic Assessment.md b/01_Archive/2026-04-20/Dynamic Assessment.md index 991c166d..196688ee 100644 --- a/01_Archive/2026-04-20/Dynamic Assessment.md +++ b/01_Archive/2026-04-20/Dynamic Assessment.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-240DDB -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Dynamic Assessment" --- -# [[Dynamic Assessment]] +# [[Dynamic Assessment|Dynamic Assessment]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Dynamic Assessment" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Dynamic Assessment.md]] +- Raw Source: 00_Raw/2026-04-20/Dynamic Assessment.md --- diff --git a/01_Archive/2026-04-20/Dynamic Difficulty Adjustment (DDA).md b/01_Archive/2026-04-20/Dynamic Difficulty Adjustment (DDA).md index b0414b78..5fc2a0b3 100644 --- a/01_Archive/2026-04-20/Dynamic Difficulty Adjustment (DDA).md +++ b/01_Archive/2026-04-20/Dynamic Difficulty Adjustment (DDA).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-478A4A -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Dynamic Difficulty Adjustment (DDA)" --- -# [[Dynamic Difficulty Adjustment (DDA)]] +# [[Dynamic Difficulty Adjustment (DDA)|Dynamic Difficulty Adjustment (DDA)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Dynamic Difficulty Adjustment ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Dynamic Difficulty Adjustment (DDA).md]] +- Raw Source: 00_Raw/2026-04-20/Dynamic Difficulty Adjustment (DDA).md --- diff --git a/01_Archive/2026-04-20/Dynamic Few-Shot (동적 퓨샷 선택 전략).md b/01_Archive/2026-04-20/Dynamic Few-Shot (동적 퓨샷 선택 전략).md index b736565e..e2669989 100644 --- a/01_Archive/2026-04-20/Dynamic Few-Shot (동적 퓨샷 선택 전략).md +++ b/01_Archive/2026-04-20/Dynamic Few-Shot (동적 퓨샷 선택 전략).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-6118B8 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Dynamic Few-Shot (동적 퓨샷 선택 전략)" --- -# [[Dynamic Few-Shot (동적 퓨샷 선택 전략)]] +# [[Dynamic Few-Shot (동적 퓨샷 선택 전략)|Dynamic Few-Shot (동적 퓨샷 선택 전략)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Dynamic Few-Shot (동적 퓨 ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Dynamic Few-Shot (동적 퓨샷 선택 전략).md]] +- Raw Source: 00_Raw/2026-04-20/Dynamic Few-Shot (동적 퓨샷 선택 전략).md --- diff --git a/01_Archive/2026-04-20/Dynamical Systems Theory.md b/01_Archive/2026-04-20/Dynamical Systems Theory.md index c3fefa76..ea72655b 100644 --- a/01_Archive/2026-04-20/Dynamical Systems Theory.md +++ b/01_Archive/2026-04-20/Dynamical Systems Theory.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-9A39F2 -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Dynamical Systems Theory" --- -# [[Dynamical Systems Theory]] +# [[Dynamical Systems Theory|Dynamical Systems Theory]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Dynamical Systems Theory" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Dynamical Systems Theory.md]] +- Raw Source: 00_Raw/2026-04-20/Dynamical Systems Theory.md --- diff --git a/01_Archive/2026-04-20/E-commerce-Catalog-Management.md b/01_Archive/2026-04-20/E-commerce-Catalog-Management.md index 312a7986..3688f80e 100644 --- a/01_Archive/2026-04-20/E-commerce-Catalog-Management.md +++ b/01_Archive/2026-04-20/E-commerce-Catalog-Management.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-D52EF5 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - E-commerce-Catalog-Management" --- -# [[E-commerce-Catalog-Management]] +# [[E-commerce-Catalog-Management|E-commerce-Catalog-Management]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - E-commerce-Catalog-Management" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/E-commerce-Catalog-Management.md]] +- Raw Source: 00_Raw/2026-04-20/E-commerce-Catalog-Management.md --- diff --git a/01_Archive/2026-04-20/E-commerce-Conversion-Optimization.md b/01_Archive/2026-04-20/E-commerce-Conversion-Optimization.md index 5d849949..8c925a17 100644 --- a/01_Archive/2026-04-20/E-commerce-Conversion-Optimization.md +++ b/01_Archive/2026-04-20/E-commerce-Conversion-Optimization.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-E7164D -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - E-commerce-Conversion-Optimization" --- -# [[E-commerce-Conversion-Optimization]] +# [[E-commerce-Conversion-Optimization|E-commerce-Conversion-Optimization]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - E-commerce-Conversion-Optimiza ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/E-commerce-Conversion-Optimization.md]] +- Raw Source: 00_Raw/2026-04-20/E-commerce-Conversion-Optimization.md --- diff --git a/01_Archive/2026-04-20/E-commerce-Optimization.md b/01_Archive/2026-04-20/E-commerce-Optimization.md index d2917674..2b719bad 100644 --- a/01_Archive/2026-04-20/E-commerce-Optimization.md +++ b/01_Archive/2026-04-20/E-commerce-Optimization.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-5FD532 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - E-commerce-Optimization" --- -# [[E-commerce-Optimization]] +# [[E-commerce-Optimization|E-commerce-Optimization]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - E-commerce-Optimization" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/E-commerce-Optimization.md]] +- Raw Source: 00_Raw/2026-04-20/E-commerce-Optimization.md --- diff --git a/01_Archive/2026-04-20/ESL Pro Tour.md b/01_Archive/2026-04-20/ESL Pro Tour.md index f62105b5..fac8cdbe 100644 --- a/01_Archive/2026-04-20/ESL Pro Tour.md +++ b/01_Archive/2026-04-20/ESL Pro Tour.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-6D8C66 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - ESL Pro Tour" --- -# [[ESL Pro Tour]] +# [[ESL Pro Tour|ESL Pro Tour]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - ESL Pro Tour" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/ESL Pro Tour.md]] +- Raw Source: 00_Raw/2026-04-20/ESL Pro Tour.md --- diff --git a/01_Archive/2026-04-20/ESLint-Plugin-TypeScript.md b/01_Archive/2026-04-20/ESLint-Plugin-TypeScript.md index af1d5ec8..9abbc9c5 100644 --- a/01_Archive/2026-04-20/ESLint-Plugin-TypeScript.md +++ b/01_Archive/2026-04-20/ESLint-Plugin-TypeScript.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-787585 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - ESLint-Plugin-TypeScript" --- -# [[ESLint-Plugin-TypeScript]] +# [[ESLint-Plugin-TypeScript|ESLint-Plugin-TypeScript]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - ESLint-Plugin-TypeScript" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/ESLint-Plugin-TypeScript.md]] +- Raw Source: 00_Raw/2026-04-20/ESLint-Plugin-TypeScript.md --- diff --git a/01_Archive/2026-04-20/ESLint-Static-Analysis.md b/01_Archive/2026-04-20/ESLint-Static-Analysis.md index f8f6e462..8db46c44 100644 --- a/01_Archive/2026-04-20/ESLint-Static-Analysis.md +++ b/01_Archive/2026-04-20/ESLint-Static-Analysis.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-2B78F8 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - ESLint-Static-Analysis" --- -# [[ESLint-Static-Analysis]] +# [[ESLint-Static-Analysis|ESLint-Static-Analysis]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - ESLint-Static-Analysis" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/ESLint-Static-Analysis.md]] +- Raw Source: 00_Raw/2026-04-20/ESLint-Static-Analysis.md --- diff --git a/01_Archive/2026-04-20/ESLint.md b/01_Archive/2026-04-20/ESLint.md index 2ea9e997..31c9ed45 100644 --- a/01_Archive/2026-04-20/ESLint.md +++ b/01_Archive/2026-04-20/ESLint.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-BDDA30 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - ESLint" --- -# [[ESLint]] +# [[ESLint|ESLint]] ## 📌 한 줄 통찰 (The Karpathy Summary) > ESLint는 자바스크립트 및 타입스크립트 코드에서 문법적 오류와 잠재적 버그를 식별하고 코딩 컨벤션을 강제하는 정적 분석 도구(Linter)입니다 [1, 2]. 소스 코드를 실행하지 않고 추상 구문 트리(AST)로 변환하여 사전에 정의된 논리 및 스타일 규칙을 적용함으로써 런타임 에러를 방지합니다 [3, 4]. 주로 코드 품질을 보장하고 팀 내 일관된 스타일을 유지하기 위해 사용되며, 코드 포매팅 도구인 Prettier와 함께 모던 웹 개발 환경의 필수적인 도구로 활용됩니다 [1, 5]. @@ -30,11 +30,11 @@ github_commit: "[P-Reinforce] Continuous Worker - ESLint" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Prettier]], [[Husky]], [[lint-staged]], [[정적 분석(Static Analysis)]], [[AST(Abstract Syntax Tree)]] -- **Projects/Contexts:** [[모노레포(Monorepo) 기반 구성 중앙화]], [[Git Hook을 이용한 CI/CD 자동화 파이프라인]] +- **Related Topics:** [[Prettier|Prettier]], [[Husky|Husky]], [[lint-staged|lint-staged]], [[정적 분석(Static Analysis)|정적 분석(Static Analysis)]], [[AST(Abstract Syntax Tree)|AST(Abstract Syntax Tree)]] +- **Projects/Contexts:** [[모노레포(Monorepo) 기반 구성 중앙화|모노레포(Monorepo) 기반 구성 중앙화]], [[Git Hook을 이용한 CI_CD 자동화 파이프라인|Git Hook을 이용한 CI/CD 자동화 파이프라인]] - **Contradictions/Notes:** 소스 [33]에서는 `eslint-plugin-prettier` 사용 시 에디터에 밑줄이 너무 많이 생기고 느려져 문서에서도 추천하지 않는다며 설정을 삭제했다고 언급하지만, 소스 [25]에서는 Prettier의 포매팅 이슈를 ESLint의 린터 오류로 띄워 통합적으로 관리할 수 있는 효과적인 방식이라고 설명하는 등 개발자 또는 조직 간의 `eslint-plugin-prettier` 활용에 대해 엇갈린 평가 및 설정 선호도 차이가 존재합니다. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/ESLint.md]] +- Raw Source: 00_Raw/2026-04-20/ESLint.md --- diff --git a/01_Archive/2026-04-20/EU-Web-Accessibility-Directive.md b/01_Archive/2026-04-20/EU-Web-Accessibility-Directive.md index 01912af8..9f4f0728 100644 --- a/01_Archive/2026-04-20/EU-Web-Accessibility-Directive.md +++ b/01_Archive/2026-04-20/EU-Web-Accessibility-Directive.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-94ECB4 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - EU-Web-Accessibility-Directive" --- -# [[EU-Web-Accessibility-Directive]] +# [[EU-Web-Accessibility-Directive|EU-Web-Accessibility-Directive]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - EU-Web-Accessibility-Directive ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/EU-Web-Accessibility-Directive.md]] +- Raw Source: 00_Raw/2026-04-20/EU-Web-Accessibility-Directive.md --- diff --git a/01_Archive/2026-04-20/EVE Online (Spreadsheet Economy).md b/01_Archive/2026-04-20/EVE Online (Spreadsheet Economy).md index 04580c58..271721cb 100644 --- a/01_Archive/2026-04-20/EVE Online (Spreadsheet Economy).md +++ b/01_Archive/2026-04-20/EVE Online (Spreadsheet Economy).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-442180 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - EVE Online (Spreadsheet Economy)" --- -# [[EVE Online (Spreadsheet Economy)]] +# [[EVE Online (Spreadsheet Economy)|EVE Online (Spreadsheet Economy)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - EVE Online (Spreadsheet Econom ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/EVE Online (Spreadsheet Economy).md]] +- Raw Source: 00_Raw/2026-04-20/EVE Online (Spreadsheet Economy).md --- diff --git a/01_Archive/2026-04-20/EXT_disjoint_timer_query.md b/01_Archive/2026-04-20/EXT_disjoint_timer_query.md index fe6603f2..7af00b48 100644 --- a/01_Archive/2026-04-20/EXT_disjoint_timer_query.md +++ b/01_Archive/2026-04-20/EXT_disjoint_timer_query.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-496C9B -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - EXT_disjoint_timer_query" --- -# [[EXT_disjoint_timer_query]] +# [[EXT_disjoint_timer_query|EXT_disjoint_timer_query]] ## 📌 한 줄 통찰 (The Karpathy Summary) > `EXT_disjoint_timer_query`는 렌더링 파이프라인을 멈추지 않고 GPU에서 실행되는 GL 명령어 세트의 소요 시간을 측정할 수 있게 해주는 WebGL API 확장 기능입니다 [1, 2]. 개발자들은 이를 통해 하드웨어 수준에서 명령어 실행의 시작과 끝을 기록하여 비동기 실행 모델의 미세 지연(Micro-latency)을 정확히 측정할 수 있었습니다 [1, 3]. 그러나 이 고정밀 타이머가 메모리 접근 패턴 관찰 등 부채널 공격(Side-channel attacks)에 악용될 수 있다는 보안상 취약점이 발견되어, 현재 대부분의 브라우저에서 비활성화되거나 정밀도가 크게 제한되었습니다 [3-5]. @@ -20,11 +20,11 @@ github_commit: "[P-Reinforce] Continuous Worker - EXT_disjoint_timer_query" - **정책 변화:** Graphics & Performance 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Micro-latency]], [[Side-channel attacks]], [[Spectre and Meltdown]], [[Rowhammer attack]] -- **Projects/Contexts:** [[WebGL API]], [[WebGPU Timestamp Queries]] +- **Related Topics:** [[Micro-latency|Micro-latency]], [[Side-channel attacks|Side-channel attacks]], [[Spectre and Meltdown|Spectre and Meltdown]], [[Rowhammer attack|Rowhammer attack]] +- **Projects/Contexts:** [[WebGL API|WebGL API]], [[WebGPU Timestamp Queries|WebGPU Timestamp Queries]] - **Contradictions/Notes:** 소스 213은 Chrome이 Site Isolation이 적용된 플랫폼에서 `EXT_disjoint_timer_query`를 노출하여 작동한다고 보고하지만, 소스 380의 사용자는 Rowhammer 공격 방지를 이유로 "모든 브라우저에서 비활성화되어 전혀 작동하지 않는다(it is disabled in all browsers)"고 모순되게 주장합니다. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/EXT_disjoint_timer_query.md]] +- Raw Source: 00_Raw/2026-04-20/EXT_disjoint_timer_query.md --- diff --git a/01_Archive/2026-04-20/Early-Z.md b/01_Archive/2026-04-20/Early-Z.md index 1ab5cba2..6002d5df 100644 --- a/01_Archive/2026-04-20/Early-Z.md +++ b/01_Archive/2026-04-20/Early-Z.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-D03C5F -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Early-Z" --- -# [[Early-Z]] +# [[Early-Z|Early-Z]] ## 📌 한 줄 통찰 (The Karpathy Summary) > Early-Z(초기 깊이 테스트)는 렌더링 파이프라인의 프래그먼트 셰이딩(Fragment Shading) 단계에서 오버드로우(Overdraw)를 최소화하기 위해 사용되는 GPU 최적화 기법입니다 [1, 2]. 불투명한 물체를 카메라 기준 '앞에서 뒤로(Front-to-Back)' 정렬하여 렌더링함으로써, 다른 물체에 의해 가려져 화면에 보이지 않을 픽셀의 연산을 사전에 종료시킵니다 [2]. 하지만 투명한 재질을 렌더링할 때는 이 최적화 기능이 비활성화되는 특성이 있습니다 [1]. @@ -22,11 +22,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Early-Z" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Overdraw]], [[InstancedMesh]], [[Alpha Blending]] -- **Projects/Contexts:** [[Three.js WebGL 렌더링 최적화]] +- **Related Topics:** [[Overdraw|Overdraw]], [[InstancedMesh|InstancedMesh]], [[Alpha Blending|Alpha Blending]] +- **Projects/Contexts:** [[Three.js WebGL 렌더링 최적화|Three.js WebGL 렌더링 최적화]] - **Contradictions/Notes:** 소스에 관련 정보가 부족합니다. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Early-Z.md]] +- Raw Source: 00_Raw/2026-04-20/Early-Z.md --- diff --git a/01_Archive/2026-04-20/Ecology and Ecosystem Modeling.md b/01_Archive/2026-04-20/Ecology and Ecosystem Modeling.md index 4e2897eb..3f17dd92 100644 --- a/01_Archive/2026-04-20/Ecology and Ecosystem Modeling.md +++ b/01_Archive/2026-04-20/Ecology and Ecosystem Modeling.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-ED335C -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Ecology and Ecosystem Modeling" --- -# [[Ecology and Ecosystem Modeling]] +# [[Ecology and Ecosystem Modeling|Ecology and Ecosystem Modeling]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Ecology and Ecosystem Modeling ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Ecology and Ecosystem Modeling.md]] +- Raw Source: 00_Raw/2026-04-20/Ecology and Ecosystem Modeling.md --- diff --git a/01_Archive/2026-04-20/Ecosystem-Modeling.md b/01_Archive/2026-04-20/Ecosystem-Modeling.md index f0f3c9a0..f7cca49b 100644 --- a/01_Archive/2026-04-20/Ecosystem-Modeling.md +++ b/01_Archive/2026-04-20/Ecosystem-Modeling.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-6E0EC9 -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Ecosystem-Modeling" --- -# [[Ecosystem-Modeling]] +# [[Ecosystem-Modeling|Ecosystem-Modeling]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Ecosystem-Modeling" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Ecosystem-Modeling.md]] +- Raw Source: 00_Raw/2026-04-20/Ecosystem-Modeling.md --- diff --git a/01_Archive/2026-04-20/EdTech (Gamified Learning).md b/01_Archive/2026-04-20/EdTech (Gamified Learning).md index 0d0a4236..d97c219e 100644 --- a/01_Archive/2026-04-20/EdTech (Gamified Learning).md +++ b/01_Archive/2026-04-20/EdTech (Gamified Learning).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-5D4E83 -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - EdTech (Gamified Learning)" --- -# [[EdTech (Gamified Learning)]] +# [[EdTech (Gamified Learning)|EdTech (Gamified Learning)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - EdTech (Gamified Learning)" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/EdTech (Gamified Learning).md]] +- Raw Source: 00_Raw/2026-04-20/EdTech (Gamified Learning).md --- diff --git a/01_Archive/2026-04-20/Edge Bleeding.md b/01_Archive/2026-04-20/Edge Bleeding.md index b0af8b8b..3d2eeeda 100644 --- a/01_Archive/2026-04-20/Edge Bleeding.md +++ b/01_Archive/2026-04-20/Edge Bleeding.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-2BC744 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Edge Bleeding" --- -# [[Edge Bleeding]] +# [[Edge Bleeding|Edge Bleeding]] ## 📌 한 줄 통찰 (The Karpathy Summary) > Edge Bleeding(경계선 블리딩)은 여러 이미지를 하나로 합친 텍스처 아틀라스(Texture Atlas)를 사용할 때 주로 발생하는 시각적 결함입니다 [1]. 특히 낮은 밉맵(Mipmap) 레벨에서 텍스처 필터링이 일어날 때, 아틀라스 내에 인접해 있는 텍스처들의 색상이 서로 섞이거나 번지는 현상을 의미합니다 [1, 2]. 이를 방지하기 위해서는 텍스처 간에 여백을 두어 메모리를 희생하거나, 최신 텍스처 배열(Data Array Textures) 기술을 활용해야 합니다 [2, 3]. @@ -22,11 +22,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Edge Bleeding" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Texture Atlas]], [[Mipmap]], [[Data Array Textures]] -- **Projects/Contexts:** [[InstancedMesh 최적화]], [[WebGL 2.0]] +- **Related Topics:** [[Texture Atlas|Texture Atlas]], [[Mipmap|Mipmap]], [[Data Array Textures|Data Array Textures]] +- **Projects/Contexts:** [[InstancedMesh 최적화|InstancedMesh 최적화]], [[WebGL 2.0|WebGL 2.0]] - **Contradictions/Notes:** 소스에 관련 정보가 부족합니다. (소스 내에서 명시적인 의견 대립은 발견되지 않으며, Edge Bleeding은 텍스처 아틀라스의 명확한 단점[1, 2]이자 WebGL 2.0의 텍스처 배열 도입으로 쉽게 극복 가능한 문제[3, 4]로 일관되게 설명됩니다.) --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Edge Bleeding.md]] +- Raw Source: 00_Raw/2026-04-20/Edge Bleeding.md --- diff --git a/01_Archive/2026-04-20/Edge Computing.md b/01_Archive/2026-04-20/Edge Computing.md index 02df04fb..bf757860 100644 --- a/01_Archive/2026-04-20/Edge Computing.md +++ b/01_Archive/2026-04-20/Edge Computing.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AI-043 -category: "[[10_Wiki/💡 Topics/Infrastructure & Automation]]" +category: "10_Wiki/💡 Topics/Infrastructure & Automation" confidence_score: 0.98 tags: [edge, computing, iot, distributed] last_reinforced: 2026-06-XX github_commit: "[P-Reinforce] Processed Edge_Computing.md" --- -# [[Edge Computing]] (엣지 컴퓨팅) +# [[Edge Computing|Edge Computing]] (엣지 컴퓨팅) ## 📌 한 줄 통찰 (The Karpathy Summary) > 데이터 생성 지점(엣지 디바이스) 근처에서 데이터를 처리하고 분석하여, 네트워크 병목 현상과 낮은 지연 시간을 해결하는 분산 컴퓨팅 아키텍처이다. @@ -27,7 +27,7 @@ github_commit: "[P-Reinforce] Processed Edge_Computing.md" - **정책 변화:** 에너지 효율성과 장치 자원 제약(Resource Constraints)을 고려한 경량화된 AI 모델 배포(TinyML) 기술이 중요한 트렌드로 부상하고 있다. ## 🔗 지식 연결 (Graph) -- Parent: [[Internet of Things (IoT) Telemetry]] -- Related: [[Distributed-Systems-Engineering]] , [[Real-Time-Game-Engines]] , [[Autonomous Vehicle Perception]] -- Raw Source: [[00_Raw/Edge_Computing.md]] +- Parent: [[Internet of Things (IoT) Telemetry|Internet of Things (IoT) Telemetry]] +- Related: [[Distributed-Systems-Engineering|Distributed-Systems-Engineering]] , [[Real-Time-Game-Engines|Real-Time-Game-Engines]] , [[Autonomous Vehicle Perception|Autonomous Vehicle Perception]] +- Raw Source: 00_Raw/Edge_Computing.md --- \ No newline at end of file diff --git a/01_Archive/2026-04-20/Edge-Detection-Algorithms.md b/01_Archive/2026-04-20/Edge-Detection-Algorithms.md index 2faba7cd..962d6a10 100644 --- a/01_Archive/2026-04-20/Edge-Detection-Algorithms.md +++ b/01_Archive/2026-04-20/Edge-Detection-Algorithms.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-D5E910 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Edge-Detection-Algorithms" --- -# [[Edge-Detection-Algorithms]] +# [[Edge-Detection-Algorithms|Edge-Detection-Algorithms]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Edge-Detection-Algorithms" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Edge-Detection-Algorithms.md]] +- Raw Source: 00_Raw/2026-04-20/Edge-Detection-Algorithms.md --- diff --git a/01_Archive/2026-04-20/Educational Pedagogy (Zone of Proximal Development).md b/01_Archive/2026-04-20/Educational Pedagogy (Zone of Proximal Development).md index 52870a3d..a771e590 100644 --- a/01_Archive/2026-04-20/Educational Pedagogy (Zone of Proximal Development).md +++ b/01_Archive/2026-04-20/Educational Pedagogy (Zone of Proximal Development).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-A6B581 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Educational Pedagogy (Zone of Proximal Development)" --- -# [[Educational Pedagogy (Zone of Proximal Development)]] +# [[Educational Pedagogy (Zone of Proximal Development)|Educational Pedagogy (Zone of Proximal Development)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Educational Pedagogy (Zone of ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Educational Pedagogy (Zone of Proximal Development).md]] +- Raw Source: 00_Raw/2026-04-20/Educational Pedagogy (Zone of Proximal Development).md --- diff --git a/01_Archive/2026-04-20/Educational-Gamification.md b/01_Archive/2026-04-20/Educational-Gamification.md index 7ec5f3ca..8424b956 100644 --- a/01_Archive/2026-04-20/Educational-Gamification.md +++ b/01_Archive/2026-04-20/Educational-Gamification.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-8F5AE3 -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Educational-Gamification" --- -# [[Educational-Gamification]] +# [[Educational-Gamification|Educational-Gamification]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Educational-Gamification" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Educational-Gamification.md]] +- Raw Source: 00_Raw/2026-04-20/Educational-Gamification.md --- diff --git a/01_Archive/2026-04-20/Educational-Psychology.md b/01_Archive/2026-04-20/Educational-Psychology.md index 6695e5bd..10118215 100644 --- a/01_Archive/2026-04-20/Educational-Psychology.md +++ b/01_Archive/2026-04-20/Educational-Psychology.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-F3112C -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Educational-Psychology" --- -# [[Educational-Psychology]] +# [[Educational-Psychology|Educational-Psychology]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Educational-Psychology" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Educational-Psychology.md]] +- Raw Source: 00_Raw/2026-04-20/Educational-Psychology.md --- diff --git a/01_Archive/2026-04-20/Effect TS 및 ts-brand 라이브러리 활용.md b/01_Archive/2026-04-20/Effect TS 및 ts-brand 라이브러리 활용.md index 873cb1b0..c912fffe 100644 --- a/01_Archive/2026-04-20/Effect TS 및 ts-brand 라이브러리 활용.md +++ b/01_Archive/2026-04-20/Effect TS 및 ts-brand 라이브러리 활용.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-C0B018 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Effect TS 및 ts-brand 라이브러리 활용" --- -# [[Effect TS 및 ts-brand 라이브러리 활용]] +# [[Effect TS 및 ts-brand 라이브러리 활용|Effect TS 및 ts-brand 라이브러리 활용]] ## 📌 한 줄 통찰 (The Karpathy Summary) > Effect TS와 ts-brand는 TypeScript에서 구조적으로 동일해 보이는 타입들을 서로 구별하기 위해 고안된 '브랜드 타입(Branded Types)' 패턴의 적용을 돕는 인기 있는 커뮤니티 라이브러리입니다 [1, 2]. TypeScript는 기본적으로 구조적 타이핑(Structural Typing)을 따르지만, 이 라이브러리들을 활용하면 명목적(Nominal) 타이핑과 유사한 안전장치를 마련할 수 있습니다 [2, 3]. 이를 통해 개발자는 단순한 원시 타입(Primitive Type)을 넘어, 비즈니스 규칙이 검증된 안전하고 정교한 타입을 코드 전반에 강제할 수 있습니다 [1, 2]. @@ -28,11 +28,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Effect TS 및 ts-brand 라이 - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Branded Types]], [[Opaque Types]], [[Nominal Typing]], [[Structural Typing]] -- **Projects/Contexts:** [[TypeScript Type Safety]] +- **Related Topics:** [[Branded Types|Branded Types]], [[Opaque Types|Opaque Types]], [[Nominal Typing|Nominal Typing]], [[Structural Typing|Structural Typing]] +- **Projects/Contexts:** [[TypeScript_Type_Safety|TypeScript Type Safety]] - **Contradictions/Notes:** 두 라이브러리는 모두 타입 안정성을 높이는 데 기여하지만, 타입 브랜드 단언 함수를 다루는 방식에서 차이를 보입니다. `ts-brand`는 `make`를 활용하는 반면, `Effect TS`는 유효성 검사 함수와 에러 처리 함수를 분리하여 입력받는 `Brand.refined`를 사용하도록 설계되었습니다 [5, 6]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/Effect TS 및 ts-brand 라이브러리 활용.md]] +- Raw Source: 00_Raw/2026-04-20/Effect TS 및 ts-brand 라이브러리 활용.md --- diff --git a/01_Archive/2026-04-20/Effect TS.md b/01_Archive/2026-04-20/Effect TS.md index 97b5e245..27011c2d 100644 --- a/01_Archive/2026-04-20/Effect TS.md +++ b/01_Archive/2026-04-20/Effect TS.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-C7A07F -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Effect TS" --- -# [[Effect TS]] +# [[Effect TS|Effect TS]] ## 📌 한 줄 통찰 (The Karpathy Summary) > Effect TS는 타입이 풍부한(type-rich) TypeScript 애플리케이션을 구축하기 위해 널리 사용되는 인기 있는 프레임워크입니다 [1]. 이 프레임워크는 주로 구조적으로 동일해 보이는 타입들을 명확히 구분하기 위한 브랜디드 타입(Branded Types) 유틸리티를 제공합니다 [1, 2]. 또한, 예상되는 에러와 예상치 못한 에러를 구분하거나 `_tag` 속성을 통해 메타데이터를 관리하는 등 타입 시스템을 활용한 다양한 패턴의 기반을 제공합니다 [3, 4]. @@ -22,11 +22,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Effect TS" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Branded Types]], [[TypeScript]] -- **Projects/Contexts:** [[Type-rich TypeScript Applications]] +- **Related Topics:** [[Branded Types|Branded Types]], [[TypeScript 라이브러리 타입 확장|TypeScript]] +- **Projects/Contexts:** Type-rich TypeScript Applications - **Contradictions/Notes:** 소스에 관련 정보가 부족합니다. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/Effect TS.md]] +- Raw Source: 00_Raw/2026-04-20/Effect TS.md --- diff --git a/01_Archive/2026-04-20/Electromyography.md b/01_Archive/2026-04-20/Electromyography.md index 633fbf56..e4adc75b 100644 --- a/01_Archive/2026-04-20/Electromyography.md +++ b/01_Archive/2026-04-20/Electromyography.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-D6647F -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Electromyography" --- -# [[Electromyography]] +# [[Electromyography|Electromyography]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Electromyography" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Electromyography.md]] +- Raw Source: 00_Raw/2026-04-20/Electromyography.md --- diff --git a/01_Archive/2026-04-20/Electron V8 Memory Cage.md b/01_Archive/2026-04-20/Electron V8 Memory Cage.md index ae0a3e20..d6944c06 100644 --- a/01_Archive/2026-04-20/Electron V8 Memory Cage.md +++ b/01_Archive/2026-04-20/Electron V8 Memory Cage.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-2DCEFC -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Electron V8 Memory Cage" --- -# [[Electron V8 Memory Cage]] +# [[Electron V8 Memory Cage|Electron V8 Memory Cage]] ## 📌 한 줄 통찰 (The Karpathy Summary) > Electron 21 이상 버전(Chrome 103을 따름)에 도입된 V8 메모리 케이지(Memory Cage)는 포인터 압축(Pointer Compression) 기술과 연계되어 V8 힙 내의 메모리 참조를 베이스 주소의 오프셋으로만 저장하도록 강제하는 보안 및 최적화 메커니즘입니다 [1-3]. 이를 통해 JIT 컴파일러의 타입 혼동(Type Confusion) 취약점을 악용한 임의 메모리 읽기/쓰기 공격을 케이지 내부 영역으로만 격리할 수 있습니다 [2, 4]. 결과적으로 애플리케이션의 보안성, 성능, 메모리 효율은 크게 향상되지만, V8 힙 크기가 최대 4GB로 제한되며 외부(Off-heap) 메모리를 가리키는 ArrayBuffer 사용이 금지된다는 제약이 발생합니다 [5, 6]. @@ -24,11 +24,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Electron V8 Memory Cage" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Pointer Compression]], [[ArrayBuffer]], [[Type Confusion]], [[JIT Compiler]] -- **Projects/Contexts:** [[Electron 21]], [[Chromium]], [[Node.js Native Modules]] +- **Related Topics:** [[Pointer Compression|Pointer Compression]], [[ArrayBuffer|ArrayBuffer]], Type Confusion, JIT Compiler +- **Projects/Contexts:** Electron 21, [[Chromium|Chromium]], Node.js Native Modules - **Contradictions/Notes:** 소스에 따르면 V8 Memory Cage 및 Pointer Compression은 힙 크기를 최대 40% 줄이고 성능을 5-10% 향상시키는 등 긍정적 효과가 크지만 [6], 그 대가로 네이티브 모듈의 오프힙(Off-heap) 메모리 래핑을 금지시키고 힙을 4GB로 엄격히 제한하는 뚜렷한 트레이드오프를 가지고 있습니다 [3, 5, 7]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Electron V8 Memory Cage.md]] +- Raw Source: 00_Raw/2026-04-20/Electron V8 Memory Cage.md --- diff --git a/01_Archive/2026-04-20/Electron.md b/01_Archive/2026-04-20/Electron.md index 16648290..49555ebd 100644 --- a/01_Archive/2026-04-20/Electron.md +++ b/01_Archive/2026-04-20/Electron.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-687305 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Electron" --- -# [[Electron]] +# [[Electron|Electron]] ## 📌 한 줄 통찰 (The Karpathy Summary) > Electron은 대규모 CAD 애플리케이션 등에서 사용되는 런타임 환경으로, 전체 시스템 메모리에 접근할 수 있지만 격리된 프로세스 간에 메모리를 관리해야 하는 특징이 있습니다 [1, 2]. Chromium GPU 프로세스와 렌더러 프로세스가 분리되어 있어 GPU 메모리 누수나 OOM(Out of Memory) 오류가 발생하기 쉬운 구조적 위험성을 내포하고 있습니다 [3, 4]. @@ -22,11 +22,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Electron" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[SharedArrayBuffer]], [[OOM (Out of Memory)]], [[Chromium GPU process]] -- **Projects/Contexts:** [[Large-scale CAD applications]], [[WebGL/Three.js Rendering Optimization]] +- **Related Topics:** [[SharedArrayBuffer|SharedArrayBuffer]], OOM (Out of Memory), Chromium GPU process +- **Projects/Contexts:** Large-scale CAD applications, WebGL/Three.js Rendering Optimization - **Contradictions/Notes:** 소스에 Electron 프레임워크 자체의 전반적인 동작 원리나 일반적인 데스크톱 앱 개발과 관련된 정보가 부족합니다. 제공된 문서는 대규모 3D/CAD 렌더링 최적화 환경에서의 메모리 관리 및 누수 문제에 국한하여 Electron을 설명하고 있습니다. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Electron.md]] +- Raw Source: 00_Raw/2026-04-20/Electron.md --- diff --git a/01_Archive/2026-04-20/Elite-Athletic-Development.md b/01_Archive/2026-04-20/Elite-Athletic-Development.md index 75e6f6fa..a2118d34 100644 --- a/01_Archive/2026-04-20/Elite-Athletic-Development.md +++ b/01_Archive/2026-04-20/Elite-Athletic-Development.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-6DB4E1 -category: "[[10_Wiki/💡 Topics/Game Design]]" +category: "10_Wiki/💡 Topics/Game Design" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Elite-Athletic-Development" --- -# [[Elite-Athletic-Development]] +# [[Elite-Athletic-Development|Elite-Athletic-Development]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Elite-Athletic-Development" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Elite-Athletic-Development.md]] +- Raw Source: 00_Raw/2026-04-20/Elite-Athletic-Development.md --- diff --git a/01_Archive/2026-04-20/Elite-Sport-Science-Protocols.md b/01_Archive/2026-04-20/Elite-Sport-Science-Protocols.md index 43841ac5..cfbac944 100644 --- a/01_Archive/2026-04-20/Elite-Sport-Science-Protocols.md +++ b/01_Archive/2026-04-20/Elite-Sport-Science-Protocols.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-04186E -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Elite-Sport-Science-Protocols" --- -# [[Elite-Sport-Science-Protocols]] +# [[Elite-Sport-Science-Protocols|Elite-Sport-Science-Protocols]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Elite-Sport-Science-Protocols" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Elite-Sport-Science-Protocols.md]] +- Raw Source: 00_Raw/2026-04-20/Elite-Sport-Science-Protocols.md --- diff --git a/01_Archive/2026-04-20/Elite-Strength-and-Conditioning.md b/01_Archive/2026-04-20/Elite-Strength-and-Conditioning.md index 435a0daa..b7d0e5fb 100644 --- a/01_Archive/2026-04-20/Elite-Strength-and-Conditioning.md +++ b/01_Archive/2026-04-20/Elite-Strength-and-Conditioning.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-4094F7 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Elite-Strength-and-Conditioning" --- -# [[Elite-Strength-and-Conditioning]] +# [[Elite-Strength-and-Conditioning|Elite-Strength-and-Conditioning]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Elite-Strength-and-Conditionin ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Elite-Strength-and-Conditioning.md]] +- Raw Source: 00_Raw/2026-04-20/Elite-Strength-and-Conditioning.md --- diff --git a/01_Archive/2026-04-20/Embodied Cognition in Virtual Reality.md b/01_Archive/2026-04-20/Embodied Cognition in Virtual Reality.md index 928b0d0a..2ca9c551 100644 --- a/01_Archive/2026-04-20/Embodied Cognition in Virtual Reality.md +++ b/01_Archive/2026-04-20/Embodied Cognition in Virtual Reality.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-C2E060 -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Embodied Cognition in Virtual Reality" --- -# [[Embodied Cognition in Virtual Reality]] +# [[Embodied Cognition in Virtual Reality|Embodied Cognition in Virtual Reality]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Embodied Cognition in Virtual ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Embodied Cognition in Virtual Reality.md]] +- Raw Source: 00_Raw/2026-04-20/Embodied Cognition in Virtual Reality.md --- diff --git a/01_Archive/2026-04-20/Embodied Cognition.md b/01_Archive/2026-04-20/Embodied Cognition.md index 3fb2cd12..ce83b510 100644 --- a/01_Archive/2026-04-20/Embodied Cognition.md +++ b/01_Archive/2026-04-20/Embodied Cognition.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-D43081 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Embodied Cognition" --- -# [[Embodied Cognition]] +# [[Embodied Cognition|Embodied Cognition]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Embodied Cognition" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Embodied Cognition.md]] +- Raw Source: 00_Raw/2026-04-20/Embodied Cognition.md --- diff --git a/01_Archive/2026-04-20/Emergent Gameplay Theory.md b/01_Archive/2026-04-20/Emergent Gameplay Theory.md index 6ce545e5..e3f21faf 100644 --- a/01_Archive/2026-04-20/Emergent Gameplay Theory.md +++ b/01_Archive/2026-04-20/Emergent Gameplay Theory.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-7320C9 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Emergent Gameplay Theory" --- -# [[Emergent Gameplay Theory]] +# [[Emergent Gameplay Theory|Emergent Gameplay Theory]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Emergent Gameplay Theory" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Emergent Gameplay Theory.md]] +- Raw Source: 00_Raw/2026-04-20/Emergent Gameplay Theory.md --- diff --git a/01_Archive/2026-04-20/Emergent Gameplay.md b/01_Archive/2026-04-20/Emergent Gameplay.md index b2a644d7..4d2bcfd1 100644 --- a/01_Archive/2026-04-20/Emergent Gameplay.md +++ b/01_Archive/2026-04-20/Emergent Gameplay.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-30AB3F -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Emergent Gameplay" --- -# [[Emergent Gameplay]] +# [[Emergent Gameplay|Emergent Gameplay]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Emergent Gameplay" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Emergent Gameplay.md]] +- Raw Source: 00_Raw/2026-04-20/Emergent Gameplay.md --- diff --git a/01_Archive/2026-04-20/Emergent Systems.md b/01_Archive/2026-04-20/Emergent Systems.md index 8c2087b3..cf2a2334 100644 --- a/01_Archive/2026-04-20/Emergent Systems.md +++ b/01_Archive/2026-04-20/Emergent Systems.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-98C9F1 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Emergent Systems" --- -# [[Emergent Systems]] +# [[Emergent Systems|Emergent Systems]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Emergent Systems" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Emergent Systems.md]] +- Raw Source: 00_Raw/2026-04-20/Emergent Systems.md --- diff --git a/01_Archive/2026-04-20/Emergent-Gameplay.md b/01_Archive/2026-04-20/Emergent-Gameplay.md index d8e8bdf9..ceaf455c 100644 --- a/01_Archive/2026-04-20/Emergent-Gameplay.md +++ b/01_Archive/2026-04-20/Emergent-Gameplay.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-B15A5A -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Emergent-Gameplay" --- -# [[Emergent-Gameplay]] +# [[Emergent-Gameplay|Emergent-Gameplay]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Emergent-Gameplay" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Emergent-Gameplay.md]] +- Raw Source: 00_Raw/2026-04-20/Emergent-Gameplay.md --- diff --git a/01_Archive/2026-04-20/Emotionally Intelligent Tutoring Systems (EITS).md b/01_Archive/2026-04-20/Emotionally Intelligent Tutoring Systems (EITS).md index f96c40e2..f81c61d0 100644 --- a/01_Archive/2026-04-20/Emotionally Intelligent Tutoring Systems (EITS).md +++ b/01_Archive/2026-04-20/Emotionally Intelligent Tutoring Systems (EITS).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-A7735A -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Emotionally Intelligent Tutoring Systems (EITS)" --- -# [[Emotionally Intelligent Tutoring Systems (EITS)]] +# [[Emotionally Intelligent Tutoring Systems (EITS)|Emotionally Intelligent Tutoring Systems (EITS)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Emotionally Intelligent Tutori ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Emotionally Intelligent Tutoring Systems (EITS).md]] +- Raw Source: 00_Raw/2026-04-20/Emotionally Intelligent Tutoring Systems (EITS).md --- diff --git a/01_Archive/2026-04-20/Employee Engagement Systems.md b/01_Archive/2026-04-20/Employee Engagement Systems.md index 9e153748..4cb9c7bd 100644 --- a/01_Archive/2026-04-20/Employee Engagement Systems.md +++ b/01_Archive/2026-04-20/Employee Engagement Systems.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-9F0879 -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Employee Engagement Systems" --- -# [[Employee Engagement Systems]] +# [[Employee Engagement Systems|Employee Engagement Systems]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Employee Engagement Systems" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Employee Engagement Systems.md]] +- Raw Source: 00_Raw/2026-04-20/Employee Engagement Systems.md --- diff --git a/01_Archive/2026-04-20/Encapsulation-and-Information-Hiding.md b/01_Archive/2026-04-20/Encapsulation-and-Information-Hiding.md index 4472271c..57a410e3 100644 --- a/01_Archive/2026-04-20/Encapsulation-and-Information-Hiding.md +++ b/01_Archive/2026-04-20/Encapsulation-and-Information-Hiding.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-3AFE91 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Encapsulation-and-Information-Hiding" --- -# [[Encapsulation-and-Information-Hiding]] +# [[Encapsulation-and-Information-Hiding|Encapsulation-and-Information-Hiding]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Encapsulation-and-Information- ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Encapsulation-and-Information-Hiding.md]] +- Raw Source: 00_Raw/2026-04-20/Encapsulation-and-Information-Hiding.md --- diff --git a/01_Archive/2026-04-20/Encapsulation-of-Domain-Invariants.md b/01_Archive/2026-04-20/Encapsulation-of-Domain-Invariants.md index 8cebb644..d37ebff5 100644 --- a/01_Archive/2026-04-20/Encapsulation-of-Domain-Invariants.md +++ b/01_Archive/2026-04-20/Encapsulation-of-Domain-Invariants.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-3F0BE1 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Encapsulation-of-Domain-Invariants" --- -# [[Encapsulation-of-Domain-Invariants]] +# [[Encapsulation-of-Domain-Invariants|Encapsulation-of-Domain-Invariants]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Encapsulation-of-Domain-Invari ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Encapsulation-of-Domain-Invariants.md]] +- Raw Source: 00_Raw/2026-04-20/Encapsulation-of-Domain-Invariants.md --- diff --git a/01_Archive/2026-04-20/Encapsulation-via-Access-Modifiers.md b/01_Archive/2026-04-20/Encapsulation-via-Access-Modifiers.md index 926aef5b..318b422e 100644 --- a/01_Archive/2026-04-20/Encapsulation-via-Access-Modifiers.md +++ b/01_Archive/2026-04-20/Encapsulation-via-Access-Modifiers.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-E8605B -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Encapsulation-via-Access-Modifiers" --- -# [[Encapsulation-via-Access-Modifiers]] +# [[Encapsulation-via-Access-Modifiers|Encapsulation-via-Access-Modifiers]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Encapsulation-via-Access-Modif ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Encapsulation-via-Access-Modifiers.md]] +- Raw Source: 00_Raw/2026-04-20/Encapsulation-via-Access-Modifiers.md --- diff --git a/01_Archive/2026-04-20/Endurance-Athletics-Cognition.md b/01_Archive/2026-04-20/Endurance-Athletics-Cognition.md index a4e3fa36..a52cd063 100644 --- a/01_Archive/2026-04-20/Endurance-Athletics-Cognition.md +++ b/01_Archive/2026-04-20/Endurance-Athletics-Cognition.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-BC701A -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Endurance-Athletics-Cognition" --- -# [[Endurance-Athletics-Cognition]] +# [[Endurance-Athletics-Cognition|Endurance-Athletics-Cognition]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Endurance-Athletics-Cognition" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Endurance-Athletics-Cognition.md]] +- Raw Source: 00_Raw/2026-04-20/Endurance-Athletics-Cognition.md --- diff --git a/01_Archive/2026-04-20/Enterprise-Design-Systems.md b/01_Archive/2026-04-20/Enterprise-Design-Systems.md index d6e7f7ba..9f978a36 100644 --- a/01_Archive/2026-04-20/Enterprise-Design-Systems.md +++ b/01_Archive/2026-04-20/Enterprise-Design-Systems.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-84FEDE -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Enterprise-Design-Systems" --- -# [[Enterprise-Design-Systems]] +# [[Enterprise-Design-Systems|Enterprise-Design-Systems]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Enterprise-Design-Systems" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Enterprise-Design-Systems.md]] +- Raw Source: 00_Raw/2026-04-20/Enterprise-Design-Systems.md --- diff --git a/01_Archive/2026-04-20/Enterprise-Resource-Planning-Systems.md b/01_Archive/2026-04-20/Enterprise-Resource-Planning-Systems.md index 276cee10..741d3450 100644 --- a/01_Archive/2026-04-20/Enterprise-Resource-Planning-Systems.md +++ b/01_Archive/2026-04-20/Enterprise-Resource-Planning-Systems.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-DDC6E0 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Enterprise-Resource-Planning-Systems" --- -# [[Enterprise-Resource-Planning-Systems]] +# [[Enterprise-Resource-Planning-Systems|Enterprise-Resource-Planning-Systems]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Enterprise-Resource-Planning-S ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Enterprise-Resource-Planning-Systems.md]] +- Raw Source: 00_Raw/2026-04-20/Enterprise-Resource-Planning-Systems.md --- diff --git a/01_Archive/2026-04-20/Enterprise-Scale-Monorepo-Management.md b/01_Archive/2026-04-20/Enterprise-Scale-Monorepo-Management.md index d3fec48f..a5489096 100644 --- a/01_Archive/2026-04-20/Enterprise-Scale-Monorepo-Management.md +++ b/01_Archive/2026-04-20/Enterprise-Scale-Monorepo-Management.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-372DAD -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Enterprise-Scale-Monorepo-Management" --- -# [[Enterprise-Scale-Monorepo-Management]] +# [[Enterprise-Scale-Monorepo-Management|Enterprise-Scale-Monorepo-Management]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Enterprise-Scale-Monorepo-Mana ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Enterprise-Scale-Monorepo-Management.md]] +- Raw Source: 00_Raw/2026-04-20/Enterprise-Scale-Monorepo-Management.md --- diff --git a/01_Archive/2026-04-20/Enterprise-Software-Architecture.md b/01_Archive/2026-04-20/Enterprise-Software-Architecture.md index 611813bf..74142c74 100644 --- a/01_Archive/2026-04-20/Enterprise-Software-Architecture.md +++ b/01_Archive/2026-04-20/Enterprise-Software-Architecture.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-4727C5 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Enterprise-Software-Architecture" --- -# [[Enterprise-Software-Architecture]] +# [[Enterprise-Software-Architecture|Enterprise-Software-Architecture]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Enterprise-Software-Architectu ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Enterprise-Software-Architecture.md]] +- Raw Source: 00_Raw/2026-04-20/Enterprise-Software-Architecture.md --- diff --git a/01_Archive/2026-04-20/Enterprise-Software-Engineering.md b/01_Archive/2026-04-20/Enterprise-Software-Engineering.md index c41814f1..e694f263 100644 --- a/01_Archive/2026-04-20/Enterprise-Software-Engineering.md +++ b/01_Archive/2026-04-20/Enterprise-Software-Engineering.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-EA62A1 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Enterprise-Software-Engineering" --- -# [[Enterprise-Software-Engineering]] +# [[Enterprise-Software-Engineering|Enterprise-Software-Engineering]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Enterprise-Software-Engineerin ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Enterprise-Software-Engineering.md]] +- Raw Source: 00_Raw/2026-04-20/Enterprise-Software-Engineering.md --- diff --git a/01_Archive/2026-04-20/Entity Component System (ECS).md b/01_Archive/2026-04-20/Entity Component System (ECS).md index e28a40bc..e4b22478 100644 --- a/01_Archive/2026-04-20/Entity Component System (ECS).md +++ b/01_Archive/2026-04-20/Entity Component System (ECS).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-523650 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Entity Component System (ECS)" --- -# [[Entity Component System (ECS)]] +# [[Entity Component System (ECS)|Entity Component System (ECS)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Entity Component System (ECS)" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Entity Component System (ECS).md]] +- Raw Source: 00_Raw/2026-04-20/Entity Component System (ECS).md --- diff --git a/01_Archive/2026-04-20/Environmental Storyability.md b/01_Archive/2026-04-20/Environmental Storyability.md index 83b1e003..b6581642 100644 --- a/01_Archive/2026-04-20/Environmental Storyability.md +++ b/01_Archive/2026-04-20/Environmental Storyability.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-61BAD9 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Environmental Storyability" --- -# [[Environmental Storyability]] +# [[Environmental Storyability|Environmental Storyability]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Environmental Storyability" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Environmental Storyability.md]] +- Raw Source: 00_Raw/2026-04-20/Environmental Storyability.md --- diff --git a/01_Archive/2026-04-20/Environmental Storytelling.md b/01_Archive/2026-04-20/Environmental Storytelling.md index 26839ea4..c7ba6e51 100644 --- a/01_Archive/2026-04-20/Environmental Storytelling.md +++ b/01_Archive/2026-04-20/Environmental Storytelling.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-415A1C -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Environmental Storytelling" --- -# [[Environmental Storytelling]] +# [[Environmental Storytelling|Environmental Storytelling]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Environmental Storytelling" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Environmental Storytelling.md]] +- Raw Source: 00_Raw/2026-04-20/Environmental Storytelling.md --- diff --git a/01_Archive/2026-04-20/Environmental-Storytelling.md b/01_Archive/2026-04-20/Environmental-Storytelling.md index 2cd47b89..bbfde8f6 100644 --- a/01_Archive/2026-04-20/Environmental-Storytelling.md +++ b/01_Archive/2026-04-20/Environmental-Storytelling.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-BB91DD -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Environmental-Storytelling" --- -# [[Environmental-Storytelling]] +# [[Environmental-Storytelling|Environmental-Storytelling]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Environmental-Storytelling" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Environmental-Storytelling.md]] +- Raw Source: 00_Raw/2026-04-20/Environmental-Storytelling.md --- diff --git a/01_Archive/2026-04-20/Epidemiological Forecasting.md b/01_Archive/2026-04-20/Epidemiological Forecasting.md index 77b625c5..5399c788 100644 --- a/01_Archive/2026-04-20/Epidemiological Forecasting.md +++ b/01_Archive/2026-04-20/Epidemiological Forecasting.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-D5D1FD -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Epidemiological Forecasting" --- -# [[Epidemiological Forecasting]] +# [[Epidemiological Forecasting|Epidemiological Forecasting]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Epidemiological Forecasting" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Epidemiological Forecasting.md]] +- Raw Source: 00_Raw/2026-04-20/Epidemiological Forecasting.md --- diff --git a/01_Archive/2026-04-20/Epidemiological Modeling.md b/01_Archive/2026-04-20/Epidemiological Modeling.md index 8bde0fad..fbfcd3fd 100644 --- a/01_Archive/2026-04-20/Epidemiological Modeling.md +++ b/01_Archive/2026-04-20/Epidemiological Modeling.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-5B9D2F -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Epidemiological Modeling" --- -# [[Epidemiological Modeling]] +# [[Epidemiological Modeling|Epidemiological Modeling]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Epidemiological Modeling" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Epidemiological Modeling.md]] +- Raw Source: 00_Raw/2026-04-20/Epidemiological Modeling.md --- diff --git a/01_Archive/2026-04-20/Epigenetics of Neuroplasticity.md b/01_Archive/2026-04-20/Epigenetics of Neuroplasticity.md index a351948a..6b4ad1a5 100644 --- a/01_Archive/2026-04-20/Epigenetics of Neuroplasticity.md +++ b/01_Archive/2026-04-20/Epigenetics of Neuroplasticity.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-0EB0EC -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Epigenetics of Neuroplasticity" --- -# [[Epigenetics of Neuroplasticity]] +# [[Epigenetics of Neuroplasticity|Epigenetics of Neuroplasticity]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Epigenetics of Neuroplasticity ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Epigenetics of Neuroplasticity.md]] +- Raw Source: 00_Raw/2026-04-20/Epigenetics of Neuroplasticity.md --- diff --git a/01_Archive/2026-04-20/Ergodic Literature.md b/01_Archive/2026-04-20/Ergodic Literature.md index 1ca3c70f..77e75914 100644 --- a/01_Archive/2026-04-20/Ergodic Literature.md +++ b/01_Archive/2026-04-20/Ergodic Literature.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-96D046 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Ergodic Literature" --- -# [[Ergodic Literature]] +# [[Ergodic Literature|Ergodic Literature]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Ergodic Literature" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Ergodic Literature.md]] +- Raw Source: 00_Raw/2026-04-20/Ergodic Literature.md --- diff --git a/01_Archive/2026-04-20/Ergodic-Literature.md b/01_Archive/2026-04-20/Ergodic-Literature.md index 7dc63d18..b82cd54e 100644 --- a/01_Archive/2026-04-20/Ergodic-Literature.md +++ b/01_Archive/2026-04-20/Ergodic-Literature.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-CB2F13 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Ergodic-Literature" --- -# [[Ergodic-Literature]] +# [[Ergodic-Literature|Ergodic-Literature]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Ergodic-Literature" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Ergodic-Literature.md]] +- Raw Source: 00_Raw/2026-04-20/Ergodic-Literature.md --- diff --git a/01_Archive/2026-04-20/Escape Hatch (탈출구).md b/01_Archive/2026-04-20/Escape Hatch (탈출구).md index 0f6db77d..03bff0b5 100644 --- a/01_Archive/2026-04-20/Escape Hatch (탈출구).md +++ b/01_Archive/2026-04-20/Escape Hatch (탈출구).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-71F155 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Escape Hatch (탈출구)" --- -# [[Escape Hatch (탈출구)]] +# [[Escape Hatch (탈출구)|Escape Hatch (탈출구)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > Escape Hatch(탈출구)는 SDK나 시스템 설계 시, 고수준의 추상화된 인터페이스(Facade)가 가지는 제약을 넘어 사용자가 세밀한 제어를 원할 때 활용할 수 있도록 제공하는 저수준(Low-level) API를 의미합니다 [1, 2]. 전체 사용 사례의 약 80%는 직관적인 고수준 인터페이스로 처리하고, 나머지 20%의 특수한 경우를 처리하기 위해 마련된 구조적 수단입니다 [1]. 이를 통해 편의성에만 안주하지 않고 세밀한 조작까지 가능한 설계적 균형을 유지할 수 있습니다 [2, 3]. @@ -22,11 +22,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Escape Hatch (탈출구)" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Facade 패턴]], [[Low-level 인터페이스]], [[추상화(Abstraction)]] -- **Projects/Contexts:** [[Toss Front SDK]], [[AWS CDK]] +- **Related Topics:** Facade 패턴, Low-level 인터페이스, [[추상화(Abstraction)|추상화(Abstraction)]] +- **Projects/Contexts:** [[Toss Front SDK 기반 외부 연동사 플러그인 개발 생태계 구축|Toss Front SDK]], AWS CDK - **Contradictions/Notes:** 소스에 따르면 추상화 수준이 높아질수록 세밀한 제어가 어려워진다는 필연적인 트레이드오프가 존재하지만, 20%의 특수 케이스를 위한 탈출구(Escape Hatch)를 제공함으로써 편의성과 유연성 사이의 이상적인 균형을 잡을 수 있다고 강조합니다 [1-3]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/Escape Hatch (탈출구).md]] +- Raw Source: 00_Raw/2026-04-20/Escape Hatch (탈출구).md --- diff --git a/01_Archive/2026-04-20/Europeana.md b/01_Archive/2026-04-20/Europeana.md index c1804dd8..3ea603f7 100644 --- a/01_Archive/2026-04-20/Europeana.md +++ b/01_Archive/2026-04-20/Europeana.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-683994 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Europeana" --- -# [[Europeana]] +# [[Europeana|Europeana]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Europeana" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Europeana.md]] +- Raw Source: 00_Raw/2026-04-20/Europeana.md --- diff --git a/01_Archive/2026-04-20/Event Storming.md b/01_Archive/2026-04-20/Event Storming.md index 3a78b902..30ec1dc4 100644 --- a/01_Archive/2026-04-20/Event Storming.md +++ b/01_Archive/2026-04-20/Event Storming.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AI-049 -category: "[[10_Wiki/💡 Topics/System Design & Modeling]]" +category: "10_Wiki/💡 Topics/System Design & Modeling" confidence_score: 0.98 tags: [event, event storming, domain modeling, saga] last_reinforced: 2026-06-XX github_commit: "[P-Reinforce] Processed Event Storming." --- -# [[Event Storming]] (이벤트 폭풍 분석) +# [[Event Storming|Event Storming]] (이벤트 폭풍 분석) ## 📌 한 줄 통찰 (The Karpathy Summary) > 비즈니스 워크플로우를 구성하는 '사건(Event)'을 중심으로 시스템의 경계, 행위자, 흐름을 시각적으로 모델링하여, 분산 시스템 및 메시징 기반 아키텍처 설계의 초석을 다지는 기법이다. @@ -26,7 +26,7 @@ github_commit: "[P-Reinforce] Processed Event Storming." - **정책 변화:** Event Sourcing 패턴과 결합될 때 가장 강력하며, 시간의 흐름에 따른 상태 변화 기록(Audit Log)을 시스템의 핵심 데이터로 활용할 수 있게 된다. ## 🔗 지식 연결 (Graph) -- Parent: [[Event Storming]] -- Related: [[Microservices-Architecture]] , [[System Dynamics]] , [[Saga Pattern]] -- Raw Source: [[00_Raw/Event Storming.md]] +- Parent: [[Event Storming|Event Storming]] +- Related: [[Microservices-Architecture|Microservices-Architecture]] , [[System Dynamics|System Dynamics]] , Saga Pattern +- Raw Source: 00_Raw/Event Storming.md --- \ No newline at end of file diff --git a/01_Archive/2026-04-20/Evolutionary Biology.md b/01_Archive/2026-04-20/Evolutionary Biology.md index 2b610815..bd81932b 100644 --- a/01_Archive/2026-04-20/Evolutionary Biology.md +++ b/01_Archive/2026-04-20/Evolutionary Biology.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-926B28 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Evolutionary Biology" --- -# [[Evolutionary Biology]] +# [[Evolutionary Biology|Evolutionary Biology]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Evolutionary Biology" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Evolutionary Biology.md]] +- Raw Source: 00_Raw/2026-04-20/Evolutionary Biology.md --- diff --git a/01_Archive/2026-04-20/Evolutionary Computation.md b/01_Archive/2026-04-20/Evolutionary Computation.md index e066d475..2436e10e 100644 --- a/01_Archive/2026-04-20/Evolutionary Computation.md +++ b/01_Archive/2026-04-20/Evolutionary Computation.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-2D52C6 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Evolutionary Computation" --- -# [[Evolutionary Computation]] +# [[Evolutionary Computation|Evolutionary Computation]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Evolutionary Computation" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Evolutionary Computation.md]] +- Raw Source: 00_Raw/2026-04-20/Evolutionary Computation.md --- diff --git a/01_Archive/2026-04-20/Evolutionary-Biology.md b/01_Archive/2026-04-20/Evolutionary-Biology.md index 1fa67ec4..02377c04 100644 --- a/01_Archive/2026-04-20/Evolutionary-Biology.md +++ b/01_Archive/2026-04-20/Evolutionary-Biology.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-29AB70 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Evolutionary-Biology" --- -# [[Evolutionary-Biology]] +# [[Evolutionary-Biology|Evolutionary-Biology]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Evolutionary-Biology" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Evolutionary-Biology.md]] +- Raw Source: 00_Raw/2026-04-20/Evolutionary-Biology.md --- diff --git a/01_Archive/2026-04-20/Evolutionary-Computation.md b/01_Archive/2026-04-20/Evolutionary-Computation.md index 57ef5767..df00e4b0 100644 --- a/01_Archive/2026-04-20/Evolutionary-Computation.md +++ b/01_Archive/2026-04-20/Evolutionary-Computation.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-314A2B -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Evolutionary-Computation" --- -# [[Evolutionary-Computation]] +# [[Evolutionary-Computation|Evolutionary-Computation]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Evolutionary-Computation" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Evolutionary-Computation.md]] +- Raw Source: 00_Raw/2026-04-20/Evolutionary-Computation.md --- diff --git a/01_Archive/2026-04-20/Excess Property Checking.md b/01_Archive/2026-04-20/Excess Property Checking.md index 7a5291cd..b09b2ec5 100644 --- a/01_Archive/2026-04-20/Excess Property Checking.md +++ b/01_Archive/2026-04-20/Excess Property Checking.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-648FC3 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Excess Property Checking" --- -# [[Excess Property Checking]] +# [[Excess Property Checking|Excess Property Checking]] ## 📌 한 줄 통찰 (The Karpathy Summary) > TypeScript의 Excess Property Checking(과잉 속성 체크)은 객체 리터럴이 다른 변수에 할당되거나 함수의 인수로 전달될 때 예상치 못한 초과 속성을 감지하고 타입 에러를 표출하는 기능이다 [1-3]. 이는 TypeScript의 기본 동작인 구조적 타이핑(Structural Typing) 규칙을 더 엄격하게 적용하는 예외적인 사례로 볼 수 있다 [1]. 개발자가 속성 이름에 오타를 내는 등의 실수로 인해 발생할 수 있는 의도치 않은 런타임 오류를 방지하기 위해 존재한다 [4-6]. @@ -27,11 +27,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Excess Property Checking" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Structural Typing]], [[satisfies Operator]], [[Weak Type Detection]] -- **Projects/Contexts:** [[TypeScript Type System]], [[ESLint Rule Proposals (no-excess-properties)]] +- **Related Topics:** [[Structural Typing|Structural Typing]], [[Satisfies Operator|satisfies Operator]], [[약한 타입 검사(Weak Type Detection)|Weak Type Detection]] +- **Projects/Contexts:** [[TypeScript-Type-System|TypeScript Type System]], ESLint Rule Proposals (no-excess-properties) - **Contradictions/Notes:** 소스 [25]에 따르면, Facebook의 Flow처럼 초과 속성을 허용하지 않는 정확한 객체 타입(`Exact`) 구문을 TypeScript에도 도입하자는 오랜 제안이 있었으나, TypeScript 팀은 Excess Property Checking 자체를 더 똑똑하게 개선하는 방향을 선호한다. 한편, ESLint의 린트 룰을 통해 초과 속성 검사를 강제하려는 시도에 대해서는, TypeScript의 모든 객체가 본질적으로 구조적 타이핑에 의해 "inexact"한 특성을 갖기 때문에 린트 룰 적용 시 노이즈(False Positive)가 과도하게 발생할 수 있다는 반론이 제기된다 [26, 27]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/Excess Property Checking.md]] +- Raw Source: 00_Raw/2026-04-20/Excess Property Checking.md --- diff --git a/01_Archive/2026-04-20/Excess-Property-Checking.md b/01_Archive/2026-04-20/Excess-Property-Checking.md index 56c9e1f6..1b2bd91f 100644 --- a/01_Archive/2026-04-20/Excess-Property-Checking.md +++ b/01_Archive/2026-04-20/Excess-Property-Checking.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-E8C633 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Excess-Property-Checking" --- -# [[Excess-Property-Checking]] +# [[Excess-Property-Checking|Excess-Property-Checking]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Excess-Property-Checking" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Excess-Property-Checking.md]] +- Raw Source: 00_Raw/2026-04-20/Excess-Property-Checking.md --- diff --git a/01_Archive/2026-04-20/Executive Dysfunction.md b/01_Archive/2026-04-20/Executive Dysfunction.md index 3e2be4d2..dd2f6484 100644 --- a/01_Archive/2026-04-20/Executive Dysfunction.md +++ b/01_Archive/2026-04-20/Executive Dysfunction.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-DDD1CE -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Executive Dysfunction" --- -# [[Executive Dysfunction]] +# [[Executive Dysfunction|Executive Dysfunction]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Executive Dysfunction" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Executive Dysfunction.md]] +- Raw Source: 00_Raw/2026-04-20/Executive Dysfunction.md --- diff --git a/01_Archive/2026-04-20/Executive Function.md b/01_Archive/2026-04-20/Executive Function.md index 75044686..0fd61fe1 100644 --- a/01_Archive/2026-04-20/Executive Function.md +++ b/01_Archive/2026-04-20/Executive Function.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-8909A3 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Executive Function" --- -# [[Executive Function]] +# [[Executive Function|Executive Function]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Executive Function" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Executive Function.md]] +- Raw Source: 00_Raw/2026-04-20/Executive Function.md --- diff --git a/01_Archive/2026-04-20/Executive-Function-Deficit.md b/01_Archive/2026-04-20/Executive-Function-Deficit.md index 690ac61d..5462bc44 100644 --- a/01_Archive/2026-04-20/Executive-Function-Deficit.md +++ b/01_Archive/2026-04-20/Executive-Function-Deficit.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-598E63 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Executive-Function-Deficit" --- -# [[Executive-Function-Deficit]] +# [[Executive-Function-Deficit|Executive-Function-Deficit]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Executive-Function-Deficit" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Executive-Function-Deficit.md]] +- Raw Source: 00_Raw/2026-04-20/Executive-Function-Deficit.md --- diff --git a/01_Archive/2026-04-20/Exercise-Physiology.md b/01_Archive/2026-04-20/Exercise-Physiology.md index c50382a3..7ec69e0b 100644 --- a/01_Archive/2026-04-20/Exercise-Physiology.md +++ b/01_Archive/2026-04-20/Exercise-Physiology.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-415D41 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Exercise-Physiology" --- -# [[Exercise-Physiology]] +# [[Exercise-Physiology|Exercise-Physiology]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Exercise-Physiology" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Exercise-Physiology.md]] +- Raw Source: 00_Raw/2026-04-20/Exercise-Physiology.md --- diff --git a/01_Archive/2026-04-20/Exergaming.md b/01_Archive/2026-04-20/Exergaming.md index ffe1b56f..64f72dc8 100644 --- a/01_Archive/2026-04-20/Exergaming.md +++ b/01_Archive/2026-04-20/Exergaming.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-44E45F -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Exergaming" --- -# [[Exergaming]] +# [[Exergaming|Exergaming]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 엑서게이밍(Exergaming)은 운동(exercise)과 게임 플레이(gameplay)를 결합하여 사용자의 신체 활동을 촉진하는 방식입니다 [1]. 어린이, 청소년, 성인의 앉아 있는 습관(sedentary behaviors)을 개선하는 데 유효한 방법으로 인정받고 있으며, 달리기나 에어로빅 댄스 등과 유사한 수준의 생리학적 건강 이점을 제공합니다 [1]. 최근에는 가상현실(VR)과 결합하여 사용자가 운동의 육체적 피로를 잊고 게임에 더 깊이 몰입하게 하여 지속적인 신체 활동을 유도하는 'VR 엑서게이밍'이 각광받고 있습니다 [2]. @@ -23,11 +23,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Exergaming" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Virtual Reality (VR)]], [[Flow]], [[VR Sickness]] -- **Projects/Contexts:** [[Beat Saber]] +- **Related Topics:** Virtual Reality (VR), Flow, [[VR Sickness|VR Sickness]] +- **Projects/Contexts:** [[Beat Saber|Beat Saber]] - **Contradictions/Notes:** VR 기술은 사용자의 몰입도(presence)를 극대화하여 엑서게임의 동기를 부여하고 신체적 피로를 잊게 하는 긍정적인 역할을 하지만, 동시에 VR 멀미(motion sickness)를 유발하여 오히려 사용자의 게임 플레이 성과와 체감하는 즐거움을 떨어뜨릴 수 있는 양면성을 지니고 있습니다 [2, 4]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Exergaming.md]] +- Raw Source: 00_Raw/2026-04-20/Exergaming.md --- diff --git a/01_Archive/2026-04-20/Exhaustiveness-Checking-with-Never.md b/01_Archive/2026-04-20/Exhaustiveness-Checking-with-Never.md index cc0c9d76..86f94285 100644 --- a/01_Archive/2026-04-20/Exhaustiveness-Checking-with-Never.md +++ b/01_Archive/2026-04-20/Exhaustiveness-Checking-with-Never.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-A2E3FE -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Exhaustiveness-Checking-with-Never" --- -# [[Exhaustiveness-Checking-with-Never]] +# [[Exhaustiveness-Checking-with-Never|Exhaustiveness-Checking-with-Never]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Exhaustiveness-Checking-with-N ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Exhaustiveness-Checking-with-Never.md]] +- Raw Source: 00_Raw/2026-04-20/Exhaustiveness-Checking-with-Never.md --- diff --git a/01_Archive/2026-04-20/Exhaustiveness-Checking.md b/01_Archive/2026-04-20/Exhaustiveness-Checking.md index 8ff2d694..090946de 100644 --- a/01_Archive/2026-04-20/Exhaustiveness-Checking.md +++ b/01_Archive/2026-04-20/Exhaustiveness-Checking.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-D4B087 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Exhaustiveness-Checking" --- -# [[Exhaustiveness-Checking]] +# [[Exhaustiveness-Checking|Exhaustiveness-Checking]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Exhaustiveness-Checking" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Exhaustiveness-Checking.md]] +- Raw Source: 00_Raw/2026-04-20/Exhaustiveness-Checking.md --- diff --git a/01_Archive/2026-04-20/Expected Utility Theory.md b/01_Archive/2026-04-20/Expected Utility Theory.md index fdb89c2d..223ebf56 100644 --- a/01_Archive/2026-04-20/Expected Utility Theory.md +++ b/01_Archive/2026-04-20/Expected Utility Theory.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-289250 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Expected Utility Theory" --- -# [[Expected Utility Theory]] +# [[Expected Utility Theory|Expected Utility Theory]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Expected Utility Theory" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Expected Utility Theory.md]] +- Raw Source: 00_Raw/2026-04-20/Expected Utility Theory.md --- diff --git a/01_Archive/2026-04-20/Expo 2025 Osaka.md b/01_Archive/2026-04-20/Expo 2025 Osaka.md index c76162f2..8699daac 100644 --- a/01_Archive/2026-04-20/Expo 2025 Osaka.md +++ b/01_Archive/2026-04-20/Expo 2025 Osaka.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-AE03AD -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Expo 2025 Osaka" --- -# [[Expo 2025 Osaka]] +# [[Expo 2025 Osaka|Expo 2025 Osaka]] ## 📌 한 줄 통찰 (The Karpathy Summary) > Expo 2025 Osaka는 고성능 WebGPU 및 Three.js 기술을 활용한 최첨단 3D 인터랙티브 경험이 전시된 행사입니다 [1-3]. 이곳에서는 100만 개의 파티클을 활용한 유체 시뮬레이션 설치물이 대형 4K 디스플레이에서 눈에 띄는 지연 없이 실시간으로 구동되었습니다 [2, 3]. 이 엑스포는 기존 아키텍처에 비해 WebGPU가 가져온 컴퓨팅 성능의 막대한 향상을 실증하는 주요 무대가 되었습니다 [1, 3]. @@ -23,11 +23,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Expo 2025 Osaka" - **정책 변화:** AI 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[WebGPU]], [[Three.js]], [[Particle System]] -- **Projects/Contexts:** [[Utsubo]], [[Hokusai installation]], [[Waves of Connection]] +- **Related Topics:** [[WebGPU|WebGPU]], [[Three.js|Three.js]], Particle System +- **Projects/Contexts:** [[Utsubo|Utsubo]], Hokusai installation, [[Waves of Connection|Waves of Connection]] - **Contradictions/Notes:** 주어진 소스는 엑스포 내 특정 디지털 설치물(Utsubo의 유체 시뮬레이션)에 대한 기술적 성과만을 다루고 있으며, 엑스포 행사 전반에 대한 내용은 소스에 관련 정보가 부족합니다. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Expo 2025 Osaka.md]] +- Raw Source: 00_Raw/2026-04-20/Expo 2025 Osaka.md --- diff --git a/01_Archive/2026-04-20/Express.js-Type-Extensions.md b/01_Archive/2026-04-20/Express.js-Type-Extensions.md index 5f212a66..a793559b 100644 --- a/01_Archive/2026-04-20/Express.js-Type-Extensions.md +++ b/01_Archive/2026-04-20/Express.js-Type-Extensions.md @@ -1,4 +1,4 @@ -[[Express.js-Type-Extensions]] +[[Express.js-Type-Extensions|Express.js-Type-Extensions]] 📌 Brief Summary Express.js-Type-Extensions refers to the process of augmenting the global `Express` namespace using TypeScript's declaration merging capabilities. This technique allows developers to extend existing interfaces, such as `Request`, `Response`, and `Application`, to include custom properties (e.g., `user` or `db`) added via middleware. It is a fundamental practice in ensuring type safety when modifying the runtime behavior of the Express framework within a TypeScript environment. @@ -19,8 +19,8 @@ In a standard TypeScript implementation, the `Request` object provided by `@type * **Strict Null Checks**: When extending interfaces, developers must decide if the new properties are optional (`user?: User`) or mandatory. In middleware contexts, making them optional is often safer to prevent errors during initial request parsing before the middleware has executed. 🔗 Knowledge Connections -* Related Topics: [[Declaration-Merging]], [[Module-Augmentation]], [[Ambient-Declarations]] -* Projects/Contexts: [[Node.js-Backend-Architecture]] +* Related Topics: [[Declaration-Merging|Declaration-Merging]], [[Module-Augmentation|Module-Augmentation]], [[Ambient-Declarations|Ambient-Declarations]] +* Projects/Contexts: [[Node.js-Backend-Architecture|Node.js-Backend-Architecture]] * Contradictions/Notes: While declaration merging is the standard for Express, some developers argue that using "Wrapper Classes" or "Custom Request Types" (via generics) provides better isolation than modifying the global `Express` namespace, as it avoids side effects in the global type registry. Last updated: 2026-04-17 \ No newline at end of file diff --git a/01_Archive/2026-04-20/Expressjs-Type-Extensions.md b/01_Archive/2026-04-20/Expressjs-Type-Extensions.md index be49591a..b22d5681 100644 --- a/01_Archive/2026-04-20/Expressjs-Type-Extensions.md +++ b/01_Archive/2026-04-20/Expressjs-Type-Extensions.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-1B7084 -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Expressjs-Type-Extensions" --- -# [[Expressjs-Type-Extensions]] +# [[Expressjs-Type-Extensions|Expressjs-Type-Extensions]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Expressjs-Type-Extensions" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Express.js-Type-Extensions.md]] +- Raw Source: 00_Raw/2026-04-20/Express.js-Type-Extensions.md --- diff --git a/01_Archive/2026-04-20/FSD (Feature-Sliced Design).md b/01_Archive/2026-04-20/FSD (Feature-Sliced Design).md index b931d0bc..4c8ee194 100644 --- a/01_Archive/2026-04-20/FSD (Feature-Sliced Design).md +++ b/01_Archive/2026-04-20/FSD (Feature-Sliced Design).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-912710 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - FSD (Feature-Sliced Design)" --- -# [[FSD (Feature-Sliced Design)]] +# [[FSD (Feature-Sliced Design)|FSD (Feature-Sliced Design)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > FSD(Feature-Sliced Design)는 프론트엔드 개발에서 프로젝트의 복잡성을 줄이고 유지보수성과 확장성을 향상시키기 위해 고안된 아키텍처입니다. 기존의 역할 중심 폴더 구조가 가지는 한계를 극복하고자 '기능(Feature)'을 기준으로 코드를 분리하는 방식을 채택합니다. 기능 간의 결합도를 낮추고 각 기능이 독립적으로 관리되도록 설계되어, 특히 대규모 프로젝트를 관리하는 데 효과적인 방법론입니다. @@ -27,11 +27,11 @@ github_commit: "[P-Reinforce] Continuous Worker - FSD (Feature-Sliced Design)" - **정책 변화:** Design & Experience 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[관심사의 분리 (Separation of Concerns)]], [[단일 책임 원칙 (SRP)]], [[컴포넌트 기반 아키텍처]] -- **Projects/Contexts:** [[대규모 프론트엔드 프로젝트 아키텍처 및 폴더 구조 설계]] +- **Related Topics:** [[관심사의 분리 (Separation of Concerns)|관심사의 분리 (Separation of Concerns)]], [[단일 책임 원칙 (SRP)|단일 책임 원칙 (SRP)]], [[컴포넌트 기반 아키텍처|컴포넌트 기반 아키텍처]] +- **Projects/Contexts:** 대규모 프론트엔드 프로젝트 아키텍처 및 폴더 구조 설계 - **Contradictions/Notes:** 소스에서는 FSD가 기능 간 결합도를 줄이고 유지보수를 돕는 훌륭한 표준이지만, 모든 상황에서 완벽한 정답은 아니라고 주장합니다. 프로젝트의 크기나 특성에 따라 오히려 기존의 단순한 폴더 구조가 더 적합할 수도 있으므로 프로젝트 상황에 맞는 유연한 폴더 구조 적용을 권장합니다. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/FSD (Feature-Sliced Design).md]] +- Raw Source: 00_Raw/2026-04-20/FSD (Feature-Sliced Design).md --- diff --git a/01_Archive/2026-04-20/FXAA.md b/01_Archive/2026-04-20/FXAA.md index 304455ff..e87bcd69 100644 --- a/01_Archive/2026-04-20/FXAA.md +++ b/01_Archive/2026-04-20/FXAA.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-332A17 -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - FXAA" --- -# [[FXAA]] +# [[FXAA|FXAA]] ## 📌 한 줄 통찰 (The Karpathy Summary) > FXAA는 실시간 3D 렌더링 환경에서 사용되는 포스트 프로세싱(Post-processing) 안티앨리어싱(Anti-aliasing) 기법입니다. 화면 공간(Screen-space) 셰이더로 실행되어 오브젝트의 가장자리를 부드럽게 만들어 줍니다 [1]. 특히 모바일이나 저사양 기기에서 네이티브 안티앨리어싱을 대체하여 높은 렌더링 프레임 속도를 유지할 수 있도록 하는 매우 성능 효율적인 최적화 기술입니다 [1, 2]. @@ -20,11 +20,11 @@ github_commit: "[P-Reinforce] Continuous Worker - FXAA" - **정책 변화:** Graphics & Performance 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Anti-aliasing]], [[SMAA]], [[MSAA]], [[Post-Processing]] -- **Projects/Contexts:** [[Three.js]], [[WebGL]] +- **Related Topics:** Anti-aliasing, SMAA, MSAA, Post-Processing +- **Projects/Contexts:** [[Three.js|Three.js]], [[WebGL|WebGL]] - **Contradictions/Notes:** 소스 간의 모순점은 없으며, 모든 소스가 공통적으로 무거운 네이티브 안티앨리어싱을 비활성화하고 FXAA를 포스트 프로세싱 후반부에 적용하는 것이 성능 확보에 필수적이라고 일관되게 권장합니다 [1-3]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/FXAA.md]] +- Raw Source: 00_Raw/2026-04-20/FXAA.md --- diff --git a/01_Archive/2026-04-20/Facade Pattern (퍼사드 패턴).md b/01_Archive/2026-04-20/Facade Pattern (퍼사드 패턴).md index addd4d8c..c471f448 100644 --- a/01_Archive/2026-04-20/Facade Pattern (퍼사드 패턴).md +++ b/01_Archive/2026-04-20/Facade Pattern (퍼사드 패턴).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-7C58EE -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Facade Pattern (퍼사드 패턴)" --- -# [[Facade Pattern (퍼사드 패턴)]] +# [[Facade Pattern (퍼사드 패턴)|Facade Pattern (퍼사드 패턴)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 퍼사드 패턴(Facade Pattern)은 복잡한 내부 서브시스템을 단순한 인터페이스로 감싸서 사용자에게 제공하는 설계 패턴이다 [1]. 이 패턴의 진정한 본질은 단순히 기능을 숨기는 것을 넘어, 복잡한 내부 구현을 사용자의 '의도(Intent)'를 기준으로 재구성하는 데 있다 [1]. 결과적으로 개발자의 인지 부하를 줄이고 시스템 간의 결합도를 낮추어 안정적이고 유지보수하기 쉬운 구조를 만드는 핵심 아키텍처 전략으로 활용된다 [2, 3]. @@ -30,11 +30,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Facade Pattern (퍼사드 패 - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[단일 책임 원칙(SRP)]], [[인터페이스 분리 원칙(ISP)]] -- **Projects/Contexts:** [[Toss Front SDK]], [[AWS CDK]] +- **Related Topics:** [[단일 책임 원칙(SRP)|단일 책임 원칙(SRP)]], 인터페이스 분리 원칙(ISP) +- **Projects/Contexts:** [[Toss Front SDK 기반 외부 연동사 플러그인 개발 생태계 구축|Toss Front SDK]], AWS CDK - **Contradictions/Notes:** 퍼사드 패턴은 사용자에게 높은 편의성을 제공하지만 필연적으로 세밀한 제어에 제약을 초래한다 [4]. 따라서 퍼사드의 편리함에만 안주하지 않고, 필요 시 세밀한 조작이 가능한 저수준 API(Escape Hatch)를 동시에 제공해 설계적 균형을 잡아야 한다고 소스들은 강조한다 [4, 5]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/Facade Pattern (퍼사드 패턴).md]] +- Raw Source: 00_Raw/2026-04-20/Facade Pattern (퍼사드 패턴).md --- diff --git a/01_Archive/2026-04-20/Fallout (Pip-Boy Mechanic).md b/01_Archive/2026-04-20/Fallout (Pip-Boy Mechanic).md index 563427cc..f1c6e52c 100644 --- a/01_Archive/2026-04-20/Fallout (Pip-Boy Mechanic).md +++ b/01_Archive/2026-04-20/Fallout (Pip-Boy Mechanic).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-C110F3 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Fallout (Pip-Boy Mechanic)" --- -# [[Fallout (Pip-Boy Mechanic)]] +# [[Fallout (Pip-Boy Mechanic)|Fallout (Pip-Boy Mechanic)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Fallout (Pip-Boy Mechanic)" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Fallout (Pip-Boy Mechanic).md]] +- Raw Source: 00_Raw/2026-04-20/Fallout (Pip-Boy Mechanic).md --- diff --git a/01_Archive/2026-04-20/Feature Ablation (피처 제거).md b/01_Archive/2026-04-20/Feature Ablation (피처 제거).md index 1512c707..ec5dee72 100644 --- a/01_Archive/2026-04-20/Feature Ablation (피처 제거).md +++ b/01_Archive/2026-04-20/Feature Ablation (피처 제거).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-41CA87 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Feature Ablation (피처 제거)" --- -# [[Feature Ablation (피처 제거)]] +# [[Feature Ablation (피처 제거)|Feature Ablation (피처 제거)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Feature Ablation (피처 제 ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Feature Ablation (피처 제거).md]] +- Raw Source: 00_Raw/2026-04-20/Feature Ablation (피처 제거).md --- diff --git a/01_Archive/2026-04-20/Feature Clamping (피처 고정).md b/01_Archive/2026-04-20/Feature Clamping (피처 고정).md index 870a0a55..8b32d21f 100644 --- a/01_Archive/2026-04-20/Feature Clamping (피처 고정).md +++ b/01_Archive/2026-04-20/Feature Clamping (피처 고정).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-E1B41C -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Feature Clamping (피처 고정)" --- -# [[Feature Clamping (피처 고정)]] +# [[Feature Clamping (피처 고정)|Feature Clamping (피처 고정)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Feature Clamping (피처 고 ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Feature Clamping (피처 고정).md]] +- Raw Source: 00_Raw/2026-04-20/Feature Clamping (피처 고정).md --- diff --git a/01_Archive/2026-04-20/Feature-Sliced Design.md b/01_Archive/2026-04-20/Feature-Sliced Design.md index 2e438ed1..e8b35ba8 100644 --- a/01_Archive/2026-04-20/Feature-Sliced Design.md +++ b/01_Archive/2026-04-20/Feature-Sliced Design.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-925C5C -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Feature-Sliced Design" --- -# [[Feature-Sliced Design]] +# [[Feature-Sliced Design|Feature-Sliced Design]] ## 📌 한 줄 통찰 (The Karpathy Summary) > Feature-Sliced Design(FSD)은 프론트엔드 개발에서 복잡성을 줄이고 유지보수성과 확장성을 향상시키기 위해 등장한 아키텍처 방법론입니다. 기존의 역할 중심 폴더 및 코드 분리 방식의 한계를 극복하고자 기능(Feature)을 기준으로 코드를 분리하고 관련된 파일들을 한데 모아 관리하는 것을 목표로 합니다. 완전히 새로운 개념은 아니지만 공식적인 문서화와 표준을 제공하여 대규모 프로젝트에서 팀원 간의 멘탈 모델을 맞추고 합의를 이끌어내는 데 특히 유용합니다. @@ -26,11 +26,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Feature-Sliced Design" - **정책 변화:** Design & Experience 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[관심사의 분리(Separation of Concerns)]], [[멘탈 모델]] -- **Projects/Contexts:** [[대규모 프론트엔드 프로젝트]] +- **Related Topics:** [[관심사의 분리(Separation of Concerns)|관심사의 분리(Separation of Concerns)]], 멘탈 모델 +- **Projects/Contexts:** [[대규모 프론트엔드 프로젝트|대규모 프론트엔드 프로젝트]] - **Contradictions/Notes:** FSD 아키텍처는 대규모 프로젝트의 복잡성 관리에 유용하지만, 모든 프로젝트에서 완벽한 해결책은 아니며 상황과 규모에 따라 오히려 기존의 폴더 구조가 더 효율적일 수도 있습니다. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/Feature-Sliced Design.md]] +- Raw Source: 00_Raw/2026-04-20/Feature-Sliced Design.md --- diff --git a/01_Archive/2026-04-20/Federated SPARQL (연합 질의).md b/01_Archive/2026-04-20/Federated SPARQL (연합 질의).md index 69575f41..ee598e40 100644 --- a/01_Archive/2026-04-20/Federated SPARQL (연합 질의).md +++ b/01_Archive/2026-04-20/Federated SPARQL (연합 질의).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-04F8F3 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Federated SPARQL (연합 질의)" --- -# [[Federated SPARQL (연합 질의)]] +# [[Federated SPARQL (연합 질의)|Federated SPARQL (연합 질의)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Federated SPARQL (연합 질 ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Federated SPARQL (연합 질의).md]] +- Raw Source: 00_Raw/2026-04-20/Federated SPARQL (연합 질의).md --- diff --git a/01_Archive/2026-04-20/Feedback-Control-Systems.md b/01_Archive/2026-04-20/Feedback-Control-Systems.md index 8ff06242..9dfafdbb 100644 --- a/01_Archive/2026-04-20/Feedback-Control-Systems.md +++ b/01_Archive/2026-04-20/Feedback-Control-Systems.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-B4B48F -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Feedback-Control-Systems" --- -# [[Feedback-Control-Systems]] +# [[Feedback-Control-Systems|Feedback-Control-Systems]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Feedback-Control-Systems" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Feedback-Control-Systems.md]] +- Raw Source: 00_Raw/2026-04-20/Feedback-Control-Systems.md --- diff --git a/01_Archive/2026-04-20/Figma.md b/01_Archive/2026-04-20/Figma.md index 0dab85d9..182f4de5 100644 --- a/01_Archive/2026-04-20/Figma.md +++ b/01_Archive/2026-04-20/Figma.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-524A98 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Figma" --- -# [[Figma]] +# [[Figma|Figma]] ## 📌 한 줄 통찰 (The Karpathy Summary) > Figma는 다수의 페이지, 대용량 이미지 및 복잡한 컴포넌트를 사용하여 디자인 및 프로토타이핑을 수행하는 디자인 툴입니다 [1, 2]. 대규모 디자인 파일에서는 스크롤 및 편집 시 지연(Lag) 현상이 발생하거나 프로토타이핑 중 마이크로 지연(Micro-latency)이 발생할 수 있으며, 원활한 사용을 위해 메모리 및 컴포넌트 구조 최적화가 중요하게 요구됩니다 [1, 2]. @@ -24,11 +24,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Figma" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Smart Animate]], [[Hidden Layers]], [[Variants]] -- **Projects/Contexts:** [[Figma Performance Optimization]] +- **Related Topics:** Smart Animate, Hidden Layers, Variants +- **Projects/Contexts:** Figma Performance Optimization - **Contradictions/Notes:** 베리언트의 수를 최소화하기 위해 중첩된 구조적 컴포넌트(nested structure components)를 사용하는 것은 직관과 달리 성능에 최악의 영향을 미칠 수 있습니다 [8]. 소스에 따르면, 구조적 컴포넌트로 인해 발생하는 숨겨진 레이어를 제거하고 대신 베리언트의 수를 늘리거나 개별 컴포넌트로 쪼개는 것이 오히려 성능 향상에 훨씬 유리합니다 [6, 7]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Figma.md]] +- Raw Source: 00_Raw/2026-04-20/Figma.md --- diff --git a/01_Archive/2026-04-20/Fill Rate.md b/01_Archive/2026-04-20/Fill Rate.md index 1dac5711..8139a257 100644 --- a/01_Archive/2026-04-20/Fill Rate.md +++ b/01_Archive/2026-04-20/Fill Rate.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-477640 -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Fill Rate" --- -# [[Fill Rate]] +# [[Fill Rate|Fill Rate]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 'Fill Rate'는 그래픽 처리 장치(GPU)의 픽셀 처리 속도 및 성능을 나타내는 지표입니다 [1, 2]. 주로 복잡한 프래그먼트 셰이더(Fragment Shader) 연산이나 겹쳐진 투명한 객체들로 인해 발생하는 오버드로우(Overdraw)에 의해 직접적인 영향을 받으며, 효과적인 렌더링 최적화를 위해서는 CPU의 드로우 콜 병목과 구분하여 관리되어야 합니다 [1-3]. @@ -22,11 +22,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Fill Rate" - **정책 변화:** Graphics & Performance 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Overdraw]], [[Fragment Shaders]], [[GPU]] -- **Projects/Contexts:** [[Image-To-3D Models in Three.js]] +- **Related Topics:** [[Overdraw|Overdraw]], Fragment Shaders, [[GPU|GPU]] +- **Projects/Contexts:** Image-To-3D Models in Three.js - **Contradictions/Notes:** 소스 내에서 Fill Rate와 관련된 상충되는 주장이나 모순은 발견되지 않았습니다. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Fill Rate.md]] +- Raw Source: 00_Raw/2026-04-20/Fill Rate.md --- diff --git a/01_Archive/2026-04-20/Finite-Element-Analysis.md b/01_Archive/2026-04-20/Finite-Element-Analysis.md index 29ed83d6..a8697e85 100644 --- a/01_Archive/2026-04-20/Finite-Element-Analysis.md +++ b/01_Archive/2026-04-20/Finite-Element-Analysis.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-31D804 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Finite-Element-Analysis" --- -# [[Finite-Element-Analysis]] +# [[Finite-Element-Analysis|Finite-Element-Analysis]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Finite-Element-Analysis" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Finite-Element-Analysis.md]] +- Raw Source: 00_Raw/2026-04-20/Finite-Element-Analysis.md --- diff --git a/01_Archive/2026-04-20/Finite-State-Machines-in-TypeScript.md b/01_Archive/2026-04-20/Finite-State-Machines-in-TypeScript.md index 6ce2228b..f7b526c4 100644 --- a/01_Archive/2026-04-20/Finite-State-Machines-in-TypeScript.md +++ b/01_Archive/2026-04-20/Finite-State-Machines-in-TypeScript.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-A0FC70 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Finite-State-Machines-in-TypeScript" --- -# [[Finite-State-Machines-in-TypeScript]] +# [[Finite-State-Machines-in-TypeScript|Finite-State-Machines-in-TypeScript]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Finite-State-Machines-in-TypeS ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Finite-State-Machines-in-TypeScript.md]] +- Raw Source: 00_Raw/2026-04-20/Finite-State-Machines-in-TypeScript.md --- diff --git a/01_Archive/2026-04-20/Firefox.md b/01_Archive/2026-04-20/Firefox.md index f045c8eb..e8cd77b3 100644 --- a/01_Archive/2026-04-20/Firefox.md +++ b/01_Archive/2026-04-20/Firefox.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-7265C7 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Firefox" --- -# [[Firefox]] +# [[Firefox|Firefox]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -37,11 +37,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Firefox" - **정책 변화:** AI 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[WebGPU]], [[WebGL]], [[Interaction to Next Paint (INP)]], [[JPEG XL]] -- **Projects/Contexts:** [[Interop 2025]] +- **Related Topics:** [[WebGPU|WebGPU]], [[WebGL|WebGL]], [[Interaction to Next Paint (INP)|Interaction to Next Paint (INP)]], [[JPEG XL|JPEG XL]] +- **Projects/Contexts:** [[Interop 2025|Interop 2025]] - **Contradictions/Notes:** 소스에 따르면 Firefox는 보안 문제를 이유로 WebGL의 타이머 쿼리(`EXT_disjoint_timer_query`) 기능을 지원하지 않았으나 [12, 14], WebGPU의 타임스탬프 쿼리 기능에 대해서는 긍정적인 도입 의사를 보였습니다 [16, 17]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Firefox.md]] +- Raw Source: 00_Raw/2026-04-20/Firefox.md --- diff --git a/01_Archive/2026-04-20/First Input Delay (FID).md b/01_Archive/2026-04-20/First Input Delay (FID).md index e0ca40fd..fa59a737 100644 --- a/01_Archive/2026-04-20/First Input Delay (FID).md +++ b/01_Archive/2026-04-20/First Input Delay (FID).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-DD1BE6 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - First Input Delay (FID)" --- -# [[First Input Delay (FID)]] +# [[First Input Delay (FID)|First Input Delay (FID)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > First Input Delay(FID)는 사용자가 웹페이지에서 첫 상호작용을 시도할 때, 브라우저가 해당 이벤트를 처리하기 시작할 때까지 걸리는 지연 시간을 측정하는 지표이다 [1]. 이 지표는 이벤트 핸들러가 시작되기 전까지의 지연 시간만을 측정하며, 이후의 렌더링 지연이나 후속 상호작용은 고려하지 않는 한계가 있었다 [2]. 이러한 단점을 보완하기 위해 2024년 구글(Google)은 코어 웹 바이탈(Core Web Vitals)의 공식 상호작용 측정 지표를 FID에서 Interaction to Next Paint (INP)로 전면 대체하였다 [3, 4]. @@ -23,11 +23,11 @@ github_commit: "[P-Reinforce] Continuous Worker - First Input Delay (FID)" - **정책 변화:** AI 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Interaction to Next Paint (INP)]], [[Core Web Vitals]], [[Time to Interactive (TTI)]] -- **Projects/Contexts:** [[Google Page Experience]], [[Chrome User Experience Report (CrUX)]] +- **Related Topics:** [[Interaction to Next Paint (INP)|Interaction to Next Paint (INP)]], [[Core Web Vitals|Core Web Vitals]], [[Time to Interactive (TTI)|Time to Interactive (TTI)]] +- **Projects/Contexts:** Google Page Experience, [[Chrome User Experience Report (CrUX)|Chrome User Experience Report (CrUX)]] - **Contradictions/Notes:** 한때 구글 코어 웹 바이탈의 핵심 반응성 지표로 사용되었으나, 단일 상호작용만 측정하는 결함이 인정되어 2024년을 기점으로 공식 지표의 지위를 잃고 INP로 완전히 대체되었다 [3, 4]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/First Input Delay (FID).md]] +- Raw Source: 00_Raw/2026-04-20/First Input Delay (FID).md --- diff --git a/01_Archive/2026-04-20/Fixed Time Step vs Variable Time Step.md b/01_Archive/2026-04-20/Fixed Time Step vs Variable Time Step.md index 21506c57..e7dae240 100644 --- a/01_Archive/2026-04-20/Fixed Time Step vs Variable Time Step.md +++ b/01_Archive/2026-04-20/Fixed Time Step vs Variable Time Step.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-5FB60B -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Fixed Time Step vs Variable Time Step" --- -# [[Fixed Time Step vs Variable Time Step]] +# [[Fixed Time Step vs Variable Time Step|Fixed Time Step vs Variable Time Step]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Fixed Time Step vs Variable Ti ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Fixed Time Step vs Variable Time Step.md]] +- Raw Source: 00_Raw/2026-04-20/Fixed Time Step vs Variable Time Step.md --- diff --git a/01_Archive/2026-04-20/Flame Chart.md b/01_Archive/2026-04-20/Flame Chart.md index ea7095f5..d3ae53f6 100644 --- a/01_Archive/2026-04-20/Flame Chart.md +++ b/01_Archive/2026-04-20/Flame Chart.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-41DF27 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Flame Chart" --- -# [[Flame Chart]] +# [[Flame Chart|Flame Chart]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 플레임 차트(Flame Chart)는 Chrome DevTools의 Performance 패널에서 메인 스레드의 활동을 시간에 따라 시각적으로 보여주는 도구입니다 [1, 2]. X축은 기록된 시간을 나타내며 막대가 넓을수록 이벤트 실행에 긴 시간이 소요되었음을 의미하고, Y축은 콜 스택(Call stack)을 나타냅니다 [1, 2]. 이를 통해 개발자는 성능 병목 현상을 파악하고 자바스크립트 함수 호출의 인과 관계 및 장기 실행 작업(Long tasks)을 분석할 수 있습니다 [1-3]. @@ -22,11 +22,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Flame Chart" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Chrome DevTools]], [[Call Stack]], [[Main Thread]], [[Long Tasks]] -- **Projects/Contexts:** [[Performance Panel]], [[Analyze runtime performance]] +- **Related Topics:** [[Chrome DevTools|Chrome DevTools]], [[Call Stack|Call Stack]], [[Main Thread|Main Thread]], [[Long Tasks|Long Tasks]] +- **Projects/Contexts:** [[Performance Panel|Performance Panel]], [[Analyze runtime performance|Analyze runtime performance]] - **Contradictions/Notes:** 소스 내에서 플레임 차트의 기능이나 정의와 관련하여 상충되는 정보는 없습니다. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Flame Chart.md]] +- Raw Source: 00_Raw/2026-04-20/Flame Chart.md --- diff --git a/01_Archive/2026-04-20/Flow State Theory.md b/01_Archive/2026-04-20/Flow State Theory.md index 25b525a4..17165042 100644 --- a/01_Archive/2026-04-20/Flow State Theory.md +++ b/01_Archive/2026-04-20/Flow State Theory.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-546D8F -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Flow State Theory" --- -# [[Flow State Theory]] +# [[Flow State Theory|Flow State Theory]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Flow State Theory" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Flow State Theory.md]] +- Raw Source: 00_Raw/2026-04-20/Flow State Theory.md --- diff --git a/01_Archive/2026-04-20/Flow State.md b/01_Archive/2026-04-20/Flow State.md index de6cc2b0..c270b386 100644 --- a/01_Archive/2026-04-20/Flow State.md +++ b/01_Archive/2026-04-20/Flow State.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-E89B44 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Flow State" --- -# [[Flow State]] +# [[Flow State|Flow State]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Flow State" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Flow State.md]] +- Raw Source: 00_Raw/2026-04-20/Flow State.md --- diff --git a/01_Archive/2026-04-20/Flow Theory.md b/01_Archive/2026-04-20/Flow Theory.md index f4137dc0..e935f8b8 100644 --- a/01_Archive/2026-04-20/Flow Theory.md +++ b/01_Archive/2026-04-20/Flow Theory.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-B216EA -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Flow Theory" --- -# [[Flow Theory]] +# [[Flow Theory|Flow Theory]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Flow Theory" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Flow Theory.md]] +- Raw Source: 00_Raw/2026-04-20/Flow Theory.md --- diff --git a/01_Archive/2026-04-20/Flow-Sensitive-Typing.md b/01_Archive/2026-04-20/Flow-Sensitive-Typing.md index d835f406..86dcd7d3 100644 --- a/01_Archive/2026-04-20/Flow-Sensitive-Typing.md +++ b/01_Archive/2026-04-20/Flow-Sensitive-Typing.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-D1B53D -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Flow-Sensitive-Typing" --- -# [[Flow-Sensitive-Typing]] +# [[Flow-Sensitive-Typing|Flow-Sensitive-Typing]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Flow-Sensitive-Typing" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Flow-Sensitive-Typing.md]] +- Raw Source: 00_Raw/2026-04-20/Flow-Sensitive-Typing.md --- diff --git a/01_Archive/2026-04-20/Flow-State.md b/01_Archive/2026-04-20/Flow-State.md index 06e3bb44..49738c91 100644 --- a/01_Archive/2026-04-20/Flow-State.md +++ b/01_Archive/2026-04-20/Flow-State.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-364080 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Flow-State" --- -# [[Flow-State]] +# [[Flow-State|Flow-State]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Flow-State" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Flow-State.md]] +- Raw Source: 00_Raw/2026-04-20/Flow-State.md --- diff --git a/01_Archive/2026-04-20/Flow-Theory.md b/01_Archive/2026-04-20/Flow-Theory.md index 584a2615..ce8ba232 100644 --- a/01_Archive/2026-04-20/Flow-Theory.md +++ b/01_Archive/2026-04-20/Flow-Theory.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-7C8E03 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Flow-Theory" --- -# [[Flow-Theory]] +# [[Flow-Theory|Flow-Theory]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Flow-Theory" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Flow-Theory.md]] +- Raw Source: 00_Raw/2026-04-20/Flow-Theory.md --- diff --git a/01_Archive/2026-04-20/Formal-Grammar.md b/01_Archive/2026-04-20/Formal-Grammar.md index 4fa3cbbd..438d23b7 100644 --- a/01_Archive/2026-04-20/Formal-Grammar.md +++ b/01_Archive/2026-04-20/Formal-Grammar.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-410500 -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Formal-Grammar" --- -# [[Formal-Grammar]] +# [[Formal-Grammar|Formal-Grammar]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Formal-Grammar" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Formal-Grammar.md]] +- Raw Source: 00_Raw/2026-04-20/Formal-Grammar.md --- diff --git a/01_Archive/2026-04-20/Formal-Methods-in-Software-Engineering.md b/01_Archive/2026-04-20/Formal-Methods-in-Software-Engineering.md index ceb7ec11..664fd4e5 100644 --- a/01_Archive/2026-04-20/Formal-Methods-in-Software-Engineering.md +++ b/01_Archive/2026-04-20/Formal-Methods-in-Software-Engineering.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-1A7827 -category: "[[10_Wiki/💡 Topics/Security]]" +category: "10_Wiki/💡 Topics/Security" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Formal-Methods-in-Software-Engineering" --- -# [[Formal-Methods-in-Software-Engineering]] +# [[Formal-Methods-in-Software-Engineering|Formal-Methods-in-Software-Engineering]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Formal-Methods-in-Software-Eng ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Formal-Methods-in-Software-Engineering.md]] +- Raw Source: 00_Raw/2026-04-20/Formal-Methods-in-Software-Engineering.md --- diff --git a/01_Archive/2026-04-20/Formalism vs Structuralism.md b/01_Archive/2026-04-20/Formalism vs Structuralism.md index d42a68b3..c9e71216 100644 --- a/01_Archive/2026-04-20/Formalism vs Structuralism.md +++ b/01_Archive/2026-04-20/Formalism vs Structuralism.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-9613E1 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Formalism vs Structuralism" --- -# [[Formalism vs Structuralism]] +# [[Formalism vs Structuralism|Formalism vs Structuralism]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Formalism vs Structuralism" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Formalism vs. Structuralism.md]] +- Raw Source: 00_Raw/2026-04-20/Formalism vs. Structuralism.md --- diff --git a/01_Archive/2026-04-20/Formalism vs. Structuralism.md b/01_Archive/2026-04-20/Formalism vs. Structuralism.md index 1b250bfc..11e275fe 100644 --- a/01_Archive/2026-04-20/Formalism vs. Structuralism.md +++ b/01_Archive/2026-04-20/Formalism vs. Structuralism.md @@ -1,4 +1,4 @@ -[[Formalism vs. Structuralism]] +[[Formalism vs. Structuralism|Formalism vs. Structuralism]] 📌 Brief Summary Formalism and Structuralism are two foundational movements in 20th-century literary theory and linguistics that shift focus away from biographical or historical context toward the internal mechanics of a text. While Formalism emphasizes the unique aesthetic properties and "literariness" of an individual work, Structuralism seeks to uncover the underlying, universal systems of signs and rules (langue) that allow any individual work (parole) to derive meaning. @@ -21,8 +21,8 @@ Structuralism emerged from Saussurean linguistics and expanded into anthropology * **Evolutionary Link:** Roman Jakobson serves as a critical bridge between the two; his work transitioned from analyzing the specific poetic functions of language (Formalism) to understanding how those functions operate within the broader linguistic system (Structuralism). 🔗 Knowledge Connections -* Related Topics: [[Saussurean Linguistics]], [[New Criticism]], [[Post-Structuralism]], [[Semiotics]], [[Narratology]] -* Projects/Contexts: [[Structural Anthropology]], [[The Russian Formalist School]], [[Deconstruction]] +* Related Topics: Saussurean Linguistics, New Criticism, [[Post-structuralism|Post-Structuralism]], Semiotics, [[Narratology|Narratology]] +* Projects/Contexts: Structural Anthropology, The Russian Formalist School, Deconstruction * Contradictions/Notes: While Structuralism grew out of Formalist linguistic inquiries, it is often criticized by Post-Structuralists (like Derrida) for being too rigid and for assuming that a stable, centered "truth" or "structure" can actually be captured. Last updated: 2026-04-16 \ No newline at end of file diff --git a/01_Archive/2026-04-20/Formalism-vs-Structuralism.md b/01_Archive/2026-04-20/Formalism-vs-Structuralism.md index cb550c0a..4207593d 100644 --- a/01_Archive/2026-04-20/Formalism-vs-Structuralism.md +++ b/01_Archive/2026-04-20/Formalism-vs-Structuralism.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-AE318B -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Formalism-vs-Structuralism" --- -# [[Formalism-vs-Structuralism]] +# [[Formalism-vs-Structuralism|Formalism-vs-Structuralism]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Formalism-vs-Structuralism" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Formalism-vs-Structuralism.md]] +- Raw Source: 00_Raw/2026-04-20/Formalism-vs-Structuralism.md --- diff --git a/01_Archive/2026-04-20/Formalist Criticism.md b/01_Archive/2026-04-20/Formalist Criticism.md index 7f5c6e9e..6651483c 100644 --- a/01_Archive/2026-04-20/Formalist Criticism.md +++ b/01_Archive/2026-04-20/Formalist Criticism.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-6E52E3 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Formalist Criticism" --- -# [[Formalist Criticism]] +# [[Formalist Criticism|Formalist Criticism]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Formalist Criticism" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Formalist Criticism.md]] +- Raw Source: 00_Raw/2026-04-20/Formalist Criticism.md --- diff --git a/01_Archive/2026-04-20/Formalist Game Design.md b/01_Archive/2026-04-20/Formalist Game Design.md index 6442e3e0..645a1a93 100644 --- a/01_Archive/2026-04-20/Formalist Game Design.md +++ b/01_Archive/2026-04-20/Formalist Game Design.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-E0F58C -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Formalist Game Design" --- -# [[Formalist Game Design]] +# [[Formalist Game Design|Formalist Game Design]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Formalist Game Design" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Formalist Game Design.md]] +- Raw Source: 00_Raw/2026-04-20/Formalist Game Design.md --- diff --git a/01_Archive/2026-04-20/Formatting.md b/01_Archive/2026-04-20/Formatting.md index ecdafca9..475a0320 100644 --- a/01_Archive/2026-04-20/Formatting.md +++ b/01_Archive/2026-04-20/Formatting.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-CODING-004 -category: "[[10_Wiki/💡 Topics/Coding]]" +category: "10_Wiki/💡 Topics/Coding" confidence_score: 0.93 tags: [coding, formatting, style-guide, standard] last_reinforced: 2026-04-20 github_commit: "batch-reinforce-07" --- -# [[Code Formatting (코드 정제 표준)]] +# Code Formatting (코드 정제 표준) ## 📌 한 줄 통찰 (The Karpathy Summary) > 코드의 의미를 바꾸지 않으면서 가독성과 협업의 효율성을 극대화하는 '시각적 문법'의 정립. @@ -24,6 +24,6 @@ github_commit: "batch-reinforce-07" - **정책 변화:** 지식 구조(w2) 관점에서 CST 기반 리샘플링 가중치를 상향하여 위키 생성 표준에 반영. ## 🔗 지식 연결 (Graph) -- **Parent:** [[10_Wiki/💡 Topics/Coding]] -- **Related:** [[CST]], [[Linting]], [[Clean-Code]] -- **Raw Source:** [[00_Raw/2026-04-20/Code Formatting.md]] +- **Parent:** 10_Wiki/💡 Topics/Coding +- **Related:** [[CST|CST]], Linting, Clean-Code +- **Raw Source:** 00_Raw/2026-04-20/Code Formatting.md diff --git a/01_Archive/2026-04-20/Fractal-Geometry.md b/01_Archive/2026-04-20/Fractal-Geometry.md index a764e683..3ec54d0f 100644 --- a/01_Archive/2026-04-20/Fractal-Geometry.md +++ b/01_Archive/2026-04-20/Fractal-Geometry.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-FCAC5E -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Fractal-Geometry" --- -# [[Fractal-Geometry]] +# [[Fractal-Geometry|Fractal-Geometry]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Fractal-Geometry" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Fractal-Geometry.md]] +- Raw Source: 00_Raw/2026-04-20/Fractal-Geometry.md --- diff --git a/01_Archive/2026-04-20/Fragment Shading.md b/01_Archive/2026-04-20/Fragment Shading.md index 61a98271..53f5215a 100644 --- a/01_Archive/2026-04-20/Fragment Shading.md +++ b/01_Archive/2026-04-20/Fragment Shading.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-809D81 -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Fragment Shading" --- -# [[Fragment Shading]] +# [[Fragment Shading|Fragment Shading]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 프래그먼트 셰이딩(Fragment Shading)은 렌더링 파이프라인 후반부에서 픽셀 단위의 렌더링 계산(퍼 픽셀 조명 연산 등)을 수행하여 최종 색상 값을 결정하는 프로세스이다 [1, 2]. 다수의 텍스처 룩업이나 복잡한 연산이 포함될 경우 필 레이트(Fill Rate)를 크게 저하시킬 수 있으며 [2], 동일 픽셀에 여러 번 렌더링 연산이 중첩되는 오버드로우(Overdraw) 현상이 발생할 경우 GPU 성능 병목의 주요 원인이 되기도 한다 [3]. @@ -23,11 +23,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Fragment Shading" - **정책 변화:** Graphics & Performance 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Overdraw]], [[Vertex Shader]], [[Fill Rate]], [[PBR]] -- **Projects/Contexts:** [[Three.js WebGL Rendering Optimization]], [[InstancedMesh Performance Bottlenecks]] +- **Related Topics:** [[Overdraw|Overdraw]], [[Vertex Shader|Vertex Shader]], [[Fill Rate|Fill Rate]], [[PBR|PBR]] +- **Projects/Contexts:** [[Three.js WebGL Rendering Optimization|Three.js WebGL Rendering Optimization]], [[InstancedMesh Performance Bottlenecks|InstancedMesh Performance Bottlenecks]] - **Contradictions/Notes:** 소스에 관련 정보가 부족합니다. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Fragment Shading.md]] +- Raw Source: 00_Raw/2026-04-20/Fragment Shading.md --- diff --git a/01_Archive/2026-04-20/Fragment-bound.md b/01_Archive/2026-04-20/Fragment-bound.md index 3f2f612a..8179908c 100644 --- a/01_Archive/2026-04-20/Fragment-bound.md +++ b/01_Archive/2026-04-20/Fragment-bound.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-589695 -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Fragment-bound" --- -# [[Fragment-bound]] +# [[Fragment-bound|Fragment-bound]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 'Fragment-bound(프래그먼트 바운드)'는 3D 그래픽스 렌더링 파이프라인에서 GPU의 프래그먼트 셰이딩(픽셀 처리) 용량이 한계에 도달하여 전체 시스템의 성능 병목이 되는 상태를 의미합니다 [1, 2]. 이 상태는 주로 객체들이 카메라 기준 깊이(Depth)에 따라 정렬되지 않은 채 렌더링될 때, 동일한 픽셀에 여러 번 그리기 연산이 수행되는 '오버드로우(Overdraw)' 현상으로 인해 촉발됩니다 [1, 2]. 특히 연산 비용이 높은 재질을 사용할 때 이 병목 현상은 더욱 극심해집니다 [2, 3]. @@ -25,11 +25,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Fragment-bound" - **정책 변화:** Graphics & Performance 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Overdraw]], [[InstancedMesh]], [[MeshStandardMaterial]], [[BatchedMesh]] -- **Projects/Contexts:** [[Three.js 렌더링 성능 최적화]] +- **Related Topics:** [[Overdraw|Overdraw]], [[InstancedMesh|InstancedMesh]], [[MeshStandardMaterial 조명 연산|MeshStandardMaterial]], [[BatchedMesh|BatchedMesh]] +- **Projects/Contexts:** [[Three.js 렌더링 성능 최적화|Three.js 렌더링 성능 최적화]] - **Contradictions/Notes:** 드로우 콜을 줄여 성능을 향상시키기 위해 고안된 `InstancedMesh`가, 정렬 기능의 부재로 인해 오히려 심각한 오버드로우와 프래그먼트 바운드를 유발하여 일반 `Mesh`를 여러 번 그릴 때보다 프레임 레이트(FPS)를 더 하락시킬 수 있다는 점이 주의사항으로 보고됩니다 [2, 4]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Fragment-bound.md]] +- Raw Source: 00_Raw/2026-04-20/Fragment-bound.md --- diff --git a/01_Archive/2026-04-20/Frustum Culling.md b/01_Archive/2026-04-20/Frustum Culling.md index ed6bbc4d..d5a1e726 100644 --- a/01_Archive/2026-04-20/Frustum Culling.md +++ b/01_Archive/2026-04-20/Frustum Culling.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-7A315B -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Frustum Culling" --- -# [[Frustum Culling]] +# [[Frustum Culling|Frustum Culling]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 시야 절두체 컬링(Frustum Culling)은 카메라의 시야(View Frustum) 밖으로 벗어난 객체를 렌더링 연산에서 제외하여 불필요한 GPU 자원 소모를 방지하는 최적화 기법이다 [1]. 하지만 InstancedMesh를 적용할 경우 엔진 수준에서 전체를 단일 객체로 취급하므로, 모든 인스턴스를 포함하는 거대한 바운딩 볼륨을 기준으로 한 번만 컬링이 수행되는 '전부 아니면 전무(All-or-Nothing)' 방식으로 작동한다 [2]. 이로 인해 화면에 극히 일부의 인스턴스만 노출되더라도 보이지 않는 나머지 모든 인스턴스의 정점 변환 연산을 GPU가 강제로 수행해야 하는 구조적 한계를 야기한다 [2]. @@ -29,11 +29,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Frustum Culling" - **정책 변화:** Graphics & Performance 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[InstancedMesh]], [[Draw Call]], [[WebGPU]], [[Bounding Volume Hierarchy (BVH)]] -- **Projects/Contexts:** [[Three.js]], [[InstancedMesh2]] +- **Related Topics:** [[InstancedMesh|InstancedMesh]], [[Draw Call|Draw Call]], [[WebGPU|WebGPU]], [[Bounding Volume Hierarchy (BVH)|Bounding Volume Hierarchy (BVH)]] +- **Projects/Contexts:** [[Three.js|Three.js]], [[InstancedMesh2|InstancedMesh2]] - **Contradictions/Notes:** InstancedMesh 기술은 드로우 콜 감소를 통해 CPU 병목을 획기적으로 해결할 수 있도록 설계되었으나, 동시에 개별 시야 절두체 컬링을 무력화시킴으로써 결과적으로 GPU 측면에 새로운 정점 연산 병목을 유발하는 모순적인 절충(Trade-off)을 요구한다 [5, 13]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Frustum Culling.md]] +- Raw Source: 00_Raw/2026-04-20/Frustum Culling.md --- diff --git a/01_Archive/2026-04-20/Function-Overloading.md b/01_Archive/2026-04-20/Function-Overloading.md index e2f632e6..6876595f 100644 --- a/01_Archive/2026-04-20/Function-Overloading.md +++ b/01_Archive/2026-04-20/Function-Overloading.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-9ABCD8 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Function-Overloading" --- -# [[Function-Overloading]] +# [[Function-Overloading|Function-Overloading]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Function-Overloading" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Function-Overloading.md]] +- Raw Source: 00_Raw/2026-04-20/Function-Overloading.md --- diff --git a/01_Archive/2026-04-20/Function-Signature-Compatibility.md b/01_Archive/2026-04-20/Function-Signature-Compatibility.md index 35ef4ed8..0e833479 100644 --- a/01_Archive/2026-04-20/Function-Signature-Compatibility.md +++ b/01_Archive/2026-04-20/Function-Signature-Compatibility.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-D7BC47 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Function-Signature-Compatibility" --- -# [[Function-Signature-Compatibility]] +# [[Function-Signature-Compatibility|Function-Signature-Compatibility]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Function-Signature-Compatibili ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Function-Signature-Compatibility.md]] +- Raw Source: 00_Raw/2026-04-20/Function-Signature-Compatibility.md --- diff --git a/01_Archive/2026-04-20/Functional Behavior Analysis (FBA).md b/01_Archive/2026-04-20/Functional Behavior Analysis (FBA).md index 069a5337..cb4670e2 100644 --- a/01_Archive/2026-04-20/Functional Behavior Analysis (FBA).md +++ b/01_Archive/2026-04-20/Functional Behavior Analysis (FBA).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AI-044 -category: "[[10_Wiki/💡 Topics/Psychology & Education]]" +category: "10_Wiki/💡 Topics/Psychology & Education" confidence_score: 0.97 tags: [aba, behavior analysis, education, intervention] last_reinforced: 2026-06-XX github_commit: "[P-Reinforce] Processed FBA.md" --- -# [[Functional Behavior Analysis (FBA)]] (기능적 행동 분석) +# [[Functional Behavior Analysis (FBA)|Functional Behavior Analysis (FBA)]] (기능적 행동 분석) ## 📌 한 줄 통찰 (The Karpathy Summary) > 관찰되는 문제 행동의 '결과'가 아닌, 그 행동이 발생하게 만든 기능(Function)을 과학적으로 파악하여 교육적 개입의 목표를 설정하는 행동주의 심리 평가 방법론이다. @@ -25,7 +25,7 @@ github_commit: "[P-Reinforce] Processed FBA.md" - **정책 변화:** 최근에는 인지 이론(Cognitive Theory)의 관점을 통합하여, 행동 변화 과정에서 사용자의 자기 인식 및 메타인지 개입을 포함하는 다차원적 FBA 모델 개발이 중요해지고 있다. ## 🔗 지식 연결 (Graph) -- Parent: [[Applied Behavior Analysis (ABA)]] -- Related: [[Behavioral Economics]] , [[Cognitive Psychology]] , [[Functional-Behavior-Analysis]] -- Raw Source: [[00_Raw/FBA.md]] +- Parent: Applied Behavior Analysis (ABA) +- Related: [[Behavioral Economics|Behavioral Economics]] , [[Cognitive Psychology|Cognitive Psychology]] , Functional-Behavior-Analysis +- Raw Source: 00_Raw/FBA.md --- \ No newline at end of file diff --git a/01_Archive/2026-04-20/Functional-Programming-in-TypeScript.md b/01_Archive/2026-04-20/Functional-Programming-in-TypeScript.md index 960d59d4..35e36d97 100644 --- a/01_Archive/2026-04-20/Functional-Programming-in-TypeScript.md +++ b/01_Archive/2026-04-20/Functional-Programming-in-TypeScript.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-80BECB -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Functional-Programming-in-TypeScript" --- -# [[Functional-Programming-in-TypeScript]] +# [[Functional-Programming-in-TypeScript|Functional-Programming-in-TypeScript]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Functional-Programming-in-Type ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Functional-Programming-in-TypeScript.md]] +- Raw Source: 00_Raw/2026-04-20/Functional-Programming-in-TypeScript.md --- diff --git a/01_Archive/2026-04-20/Fuzzing.md b/01_Archive/2026-04-20/Fuzzing.md index 28661593..32c752f1 100644 --- a/01_Archive/2026-04-20/Fuzzing.md +++ b/01_Archive/2026-04-20/Fuzzing.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-CE0886 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Fuzzing" --- -# [[Fuzzing]] +# [[Fuzzing|Fuzzing]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 퍼징(Fuzzing)은 애플리케이션에 스트레스를 가해 예상치 못한 동작, 프로그램 충돌(크래시) 또는 리소스 누수를 유발함으로써 소프트웨어의 취약점을 찾아내는 동적 애플리케이션 보안 테스트(DAST) 기법입니다 [1]. 소스에 관련 정보가 부족합니다. @@ -23,11 +23,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Fuzzing" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[DAST]], [[Vulnerabilities]] +- **Related Topics:** [[DAST (동적 애플리케이션 보안 테스트)|DAST]], Vulnerabilities - **Projects/Contexts:** 애플리케이션의 동작 및 취약점을 포괄적으로 이해하기 위한 소프트웨어 보안 테스트 컨텍스트에서 활용됩니다 [1]. - **Contradictions/Notes:** 소스에 관련 정보가 부족합니다. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/Fuzzing.md]] +- Raw Source: 00_Raw/2026-04-20/Fuzzing.md --- diff --git a/01_Archive/2026-04-20/GC Root.md b/01_Archive/2026-04-20/GC Root.md index 078c2eb7..d41e4f39 100644 --- a/01_Archive/2026-04-20/GC Root.md +++ b/01_Archive/2026-04-20/GC Root.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-31335C -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - GC Root" --- -# [[GC Root]] +# [[GC Root|GC Root]] ## 📌 한 줄 통찰 (The Karpathy Summary) > GC Root(가비지 컬렉션 루트)는 가비지 컬렉터가 메모리 내에서 사용 중인 살아있는(live) 객체를 식별하기 위해 참조 추적을 시작하는 기준점 역할을 하는 객체입니다 [1-3]. 힙(heap) 외부에서 접근할 수 있는 객체로서 기본적으로 살아있는 것으로 정의되며, 힙 내부의 다른 객체들이 메모리 회수 대상에서 제외되려면 반드시 이 루트 객체로부터 시작되는 포인터 체인을 통해 도달 가능(reachable)하게 연결되어 있어야 합니다 [1, 2, 4]. @@ -22,11 +22,11 @@ github_commit: "[P-Reinforce] Continuous Worker - GC Root" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Garbage Collection]], [[Mark-Sweep Algorithm]], [[Memory Leak]], [[Reachability]] -- **Projects/Contexts:** [[V8 Engine]], [[IBM SDK Java Technology]] +- **Related Topics:** [[Garbage Collection|Garbage Collection]], Mark-Sweep Algorithm, [[Memory Leak|Memory Leak]], Reachability +- **Projects/Contexts:** [[V8 Engine|V8 Engine]], IBM SDK Java Technology - **Contradictions/Notes:** 소스에 따르면 V8 엔진(JavaScript)과 IBM Java 구현 모두 GC 루트를 통한 참조 추적이라는 핵심 원리를 공유하고 있습니다. 다만 실행 환경의 차이에 따라 V8은 DOM 요소나 클로저 등을 주로 다루고 [1, 5], Java는 JNI 참조나 클래스 정적 필드 등을 다룬다는 세부적인 특성의 차이를 보입니다 [2]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/GC Root.md]] +- Raw Source: 00_Raw/2026-04-20/GC Root.md --- diff --git a/01_Archive/2026-04-20/GPU Resources.md b/01_Archive/2026-04-20/GPU Resources.md index 9098529f..1b2864ea 100644 --- a/01_Archive/2026-04-20/GPU Resources.md +++ b/01_Archive/2026-04-20/GPU Resources.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-4AA291 -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - GPU Resources" --- -# [[GPU Resources]] +# [[GPU Resources|GPU Resources]] ## 📌 한 줄 통찰 (The Karpathy Summary) > GPU 리소스는 Three.js 및 WebGL 환경에서 렌더링을 위해 할당되는 VRAM 자원으로, 기하학적 구조(Geometries), 재질(Materials), 텍스처(Textures), 렌더 타겟(Render targets) 등을 포함합니다 [1-3]. 브라우저 렌더링 엔진은 이러한 리소스들을 자동으로 가비지 컬렉트(Garbage Collect)하지 않기 때문에 사용이 끝나면 개발자가 직접 명시적으로 메모리에서 해제해야 합니다 [1]. 효율적인 GPU 리소스 관리가 이루어지지 않으면 심각한 메모리 누수(Memory Leaks)가 발생하며, 궁극적으로 브라우저의 제한된 GPU 메모리를 초과하여 컨텍스트 손실(Context Lost)과 화면 멈춤 현상을 유발합니다 [3, 4]. @@ -23,11 +23,11 @@ github_commit: "[P-Reinforce] Continuous Worker - GPU Resources" - **정책 변화:** Graphics & Performance 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Memory Management]], [[Memory Leaks]], [[Textures]], [[VRAM]], [[Garbage Collection]] -- **Projects/Contexts:** [[Three.js]], [[WebGL]], [[WebGPU]] +- **Related Topics:** [[Memory Management|Memory Management]], [[Memory Leaks|Memory Leaks]], Textures, VRAM, [[Garbage Collection|Garbage Collection]] +- **Projects/Contexts:** [[Three.js|Three.js]], [[WebGL|WebGL]], [[WebGPU|WebGPU]] - **Contradictions/Notes:** 소스에 관련 모순이나 충돌 정보는 없습니다. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/GPU Resources.md]] +- Raw Source: 00_Raw/2026-04-20/GPU Resources.md --- diff --git a/01_Archive/2026-04-20/GPU for the Web Community Group.md b/01_Archive/2026-04-20/GPU for the Web Community Group.md index 8bdc6bcc..2507dec6 100644 --- a/01_Archive/2026-04-20/GPU for the Web Community Group.md +++ b/01_Archive/2026-04-20/GPU for the Web Community Group.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-518388 -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - GPU for the Web Community Group" --- -# [[GPU for the Web Community Group]] +# [[GPU for the Web Community Group|GPU for the Web Community Group]] ## 📌 한 줄 통찰 (The Karpathy Summary) > GPU for the Web Community Group은 Chrome, Firefox, Safari 등 주요 웹 브라우저의 대표자들로 구성되어 WebGPU와 같은 웹 그래픽 및 컴퓨팅 API의 표준과 새로운 기능을 논의하고 승인하는 조직입니다. 이들은 웹 플랫폼의 건전성과 상호 운용성을 위해 구현에 따라 달라지는(implementation-defined) 기능을 피하고, 결정론적이며 테스트 가능한 기능을 표준에 포함시키는 것을 원칙으로 합니다. 최근에는 개발자 도구 및 성능 측정을 위한 WebGPU 타임스탬프 쿼리(timestamp queries) 기능의 도입과 보안을 위한 양자화(quantization) 기준을 합의하는 역할을 수행했습니다. @@ -25,11 +25,11 @@ github_commit: "[P-Reinforce] Continuous Worker - GPU for the Web Community Grou - **정책 변화:** Graphics & Performance 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[WebGPU]], [[Timestamp Queries]] -- **Projects/Contexts:** [[WebGPU API Standardization]], [[Chrome Intent to Ship]] +- **Related Topics:** [[WebGPU|WebGPU]], [[Timestamp Queries|Timestamp Queries]] +- **Projects/Contexts:** WebGPU API Standardization, Chrome Intent to Ship - **Contradictions/Notes:** 그룹은 일반적으로 구현에 따라 달라지거나 결정론적이지 않은 기능을 표준에서 배제하려고 노력하지만, 타임스탬프 쿼리와 같은 기능의 경우 예외적으로 보안(타이밍 공격 방지)과 성능 측정의 필요성 사이에서 양자화라는 타협점을 찾아야만 했습니다 [4]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/GPU for the Web Community Group.md]] +- Raw Source: 00_Raw/2026-04-20/GPU for the Web Community Group.md --- diff --git a/01_Archive/2026-04-20/GPU-driven Rendering.md b/01_Archive/2026-04-20/GPU-driven Rendering.md index ce1b38a1..e14d0060 100644 --- a/01_Archive/2026-04-20/GPU-driven Rendering.md +++ b/01_Archive/2026-04-20/GPU-driven Rendering.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-C35A51 -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - GPU-driven Rendering" --- -# [[GPU-driven Rendering]] +# [[GPU-driven Rendering|GPU-driven Rendering]] ## 📌 한 줄 통찰 (The Karpathy Summary) > GPU-driven Rendering(GPU 주도 렌더링)은 CPU가 렌더링할 객체를 판별하고 명령하는 대신, GPU가 무엇을 렌더링할지 스스로 결정하는 현대적인 렌더링 파이프라인 기법입니다 [1, 2]. 주로 컴퓨트 셰이더(Compute Shader)를 활용해 객체의 가시성을 GPU 내부에서 직접 평가한 후, 간접 그리기(Indirect Draw) 명령을 통해 화면에 출력합니다 [1, 3]. 이 방식을 사용하면 CPU와 GPU 간의 데이터 전송 및 통신 병목이 제거되어 수백만 개의 인스턴스를 극도로 효율적으로 처리할 수 있습니다 [1, 3]. @@ -22,11 +22,11 @@ github_commit: "[P-Reinforce] Continuous Worker - GPU-driven Rendering" - **정책 변화:** Graphics & Performance 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Compute Shader]], [[Indirect Draw]], [[Frustum Culling]], [[WebGPU]] -- **Projects/Contexts:** [[Three.js]], [[InstancedMesh]] +- **Related Topics:** [[Compute Shader|Compute Shader]], [[Indirect Draw|Indirect Draw]], [[Frustum Culling|Frustum Culling]], [[WebGPU|WebGPU]] +- **Projects/Contexts:** [[Three.js|Three.js]], [[InstancedMesh|InstancedMesh]] - **Contradictions/Notes:** 대규모 객체를 렌더링할 때 'CPU 개별 컬링' 방식은 자바스크립트 연산 및 시스템 버스 전송에 막대한 병목을 유발하지만, 'GPU 주도 렌더링(GPU 컴퓨트 컬링)'은 구현 난이도가 매우 높은 대신 CPU 부하를 극도로 낮추고 전체적인 성능을 극대화한다는 뚜렷한 대비를 보입니다 [3, 5]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/GPU-driven Rendering.md]] +- Raw Source: 00_Raw/2026-04-20/GPU-driven Rendering.md --- diff --git a/01_Archive/2026-04-20/GPU.md b/01_Archive/2026-04-20/GPU.md index f00631b5..c9807ed3 100644 --- a/01_Archive/2026-04-20/GPU.md +++ b/01_Archive/2026-04-20/GPU.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-DD4F11 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - GPU" --- -# [[GPU]] +# [[GPU|GPU]] ## 📌 한 줄 통찰 (The Karpathy Summary) > GPU(Graphics Processing Unit)는 실시간 3D 그래픽 렌더링과 병렬 연산 처리에 최적화된 하드웨어 장치이다 [1]. 최신 GPU는 수천 개의 프로세싱 코어를 갖추고 있어 그래픽 렌더링뿐만 아니라 물리 시뮬레이션, AI 추론 등 범용적인 병렬 작업에 뛰어난 성능을 발휘한다 [2, 3]. 웹 환경에서는 WebGL 및 WebGPU와 같은 그래픽 API를 통해 제어되며, 셰이더(Shader) 프로그램을 하드웨어 수준에서 매우 빠른 속도로 실행하여 시각적 결과물을 만들어낸다 [1, 4]. @@ -23,11 +23,11 @@ github_commit: "[P-Reinforce] Continuous Worker - GPU" - **정책 변화:** AI 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[WebGL]], [[WebGPU]], [[Compute Shader]], [[CPU]] -- **Projects/Contexts:** [[WebSplatter]], [[Three.js]], [[CesiumJS]] +- **Related Topics:** [[WebGL|WebGL]], [[WebGPU|WebGPU]], [[Compute Shader|Compute Shader]], CPU +- **Projects/Contexts:** WebSplatter, [[Three.js|Three.js]], [[CesiumJS|CesiumJS]] - **Contradictions/Notes:** 과거 WebGL 생태계에서는 구조적 한계로 인해 물리 연산이나 정렬 작업을 CPU에서 처리해야 했고 이로 인해 GPU가 자주 유휴 상태(Idle)에 머무는 비효율이 존재했다. 그러나 WebGPU의 등장으로 컴퓨트 셰이더 기반의 연산이 가능해지면서, 렌더링과 연산 모두를 GPU에서 병렬 처리하여 GPU의 하드웨어 능력을 온전히 활용할 수 있게 되었다 [2, 3, 12, 20]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/GPU.md]] +- Raw Source: 00_Raw/2026-04-20/GPU.md --- diff --git a/01_Archive/2026-04-20/GPURenderBundles.md b/01_Archive/2026-04-20/GPURenderBundles.md index 8be47836..ff60ce6b 100644 --- a/01_Archive/2026-04-20/GPURenderBundles.md +++ b/01_Archive/2026-04-20/GPURenderBundles.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-BC7FBB -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - GPURenderBundles" --- -# [[GPURenderBundles]] +# [[GPURenderBundles|GPURenderBundles]] ## 📌 한 줄 통찰 (The Karpathy Summary) > `GPURenderBundles` (렌더 번들)는 Native WebGPU 환경에서 제공되는 강력한 렌더링 최적화 도구입니다 [1]. 초기화 과정에서 파이프라인, 바인드 그룹(bind groups), 드로우 콜(draw calls)과 같은 명령을 미리 기록(pre-record)하고, 이후 렌더 루프에서 단 한 번의 호출로 이를 다시 재생(replay)할 수 있게 해줍니다 [1]. 이 방식을 통해 렌더링 성능에 병목을 일으키는 검증 작업(validation work)을 핵심 렌더링 경로 외부로 분리하여 대규모 객체를 극도로 효율적으로 처리할 수 있습니다 [1, 2]. @@ -22,11 +22,11 @@ github_commit: "[P-Reinforce] Continuous Worker - GPURenderBundles" - **정책 변화:** Graphics & Performance 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Native WebGPU]], [[Indirect Drawing]], [[Draw Call Efficiency]], [[Bind Groups]] -- **Projects/Contexts:** [[대규모 건설 플랫폼 뷰어(Large-Scale Construction Viewers)]] +- **Related Topics:** Native WebGPU, Indirect Drawing, Draw Call Efficiency, Bind Groups +- **Projects/Contexts:** 대규모 건설 플랫폼 뷰어(Large-Scale Construction Viewers) - **Contradictions/Notes:** 고수준 프레임워크인 Three.js WebGPU는 개발이 쉽지만 고유 객체 처리 시 UBO(Uniform Buffer Objects) 바인딩 오버헤드로 인해 약 1만~2만 개의 비인스턴스 객체 렌더링 시 프레임이 떨어질 수 있습니다. 반면, Native WebGPU는 초기화 및 파이프라인 구성의 복잡성(개발 속도 저하)을 감수하는 대신 `GPURenderBundles`를 통해 10만 개 이상의 고유 객체를 병목 없이 원활하게 처리할 수 있습니다 [2-4]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/GPURenderBundles.md]] +- Raw Source: 00_Raw/2026-04-20/GPURenderBundles.md --- diff --git a/01_Archive/2026-04-20/GPU_WebGL 파이프라인의 미세 지연(Micro-latency) 측정 사례.md b/01_Archive/2026-04-20/GPU_WebGL 파이프라인의 미세 지연(Micro-latency) 측정 사례.md index 5216f924..2ff2c227 100644 --- a/01_Archive/2026-04-20/GPU_WebGL 파이프라인의 미세 지연(Micro-latency) 측정 사례.md +++ b/01_Archive/2026-04-20/GPU_WebGL 파이프라인의 미세 지연(Micro-latency) 측정 사례.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-035B08 -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - GPU_WebGL 파이프라인의 미세 지연(Micro-latency) 측정 사례" --- -# [[GPU_WebGL 파이프라인의 미세 지연(Micro-latency) 측정 사례]] +# [[GPU_WebGL 파이프라인의 미세 지연(Micro-latency) 측정 사례|GPU_WebGL 파이프라인의 미세 지연(Micro-latency) 측정 사례]] ## 📌 한 줄 통찰 (The Karpathy Summary) > GPU/WebGL 파이프라인의 미세 지연(Micro-latency)은 CPU, GPU 및 브라우저 추상화 계층 간의 상호작용에서 발생하는 서브 프레임(Sub-frame) 수준의 시간 지연을 의미하며, 사용자 몰입도를 저하시키는 주요 원인입니다 [1]. 이를 정확히 측정하기 위해 WebGL/WebGPU의 타이머 API, 브라우저 내부의 성능 프로파일링 도구, 그리고 고속 카메라와 오실로스코프를 활용한 하드웨어 기반 측정 등 다양한 접근법이 활용되고 있습니다 [2-6]. 그러나 보안 취약점(Spectre, Meltdown 등)으로 인해 정밀한 시간 측정 기능이 브라우저 차원에서 양자화(Quantization)되거나 제한되는 등 여러 측정 상의 제약이 따르고 있습니다 [3, 7]. @@ -38,11 +38,11 @@ github_commit: "[P-Reinforce] Continuous Worker - GPU_WebGL 파이프라인의 - **정책 변화:** Graphics & Performance 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Spectre and Meltdown]], [[WebGPU Timestamp Queries]], [[EXT_disjoint_timer_query]] -- **Projects/Contexts:** [[Chrome DevTools Performance Panel]], [[ANGLE (Almost Native Graphics Layer Engine)]] +- **Related Topics:** [[Spectre and Meltdown|Spectre and Meltdown]], [[WebGPU Timestamp Queries|WebGPU Timestamp Queries]], [[EXT_disjoint_timer_query|EXT_disjoint_timer_query]] +- **Projects/Contexts:** Chrome DevTools Performance Panel, [[ANGLE (Almost Native Graphics Layer Engine)|ANGLE (Almost Native Graphics Layer Engine)]] - **Contradictions/Notes:** 소스에 따르면 WebGL의 `gl.finish()` 함수는 본래 GPU 파이프라인의 실행 완료를 기다리는 기능이나, Chrome에서는 `gl.flush()`로 별칭(alias) 지정되어 있어, 이를 사용해 실제 렌더링 지연 시간을 측정하려는 시도는 작동하지 않습니다 [11, 27]. 또한 `EXT_disjoint_timer_query` 확장이나 `performance.now()` 등의 도구 역시 각각 보안 문제(캐시 기반 정보 유출) 및 제한적인 렌더링 조건 탓에 순수하고 완벽한 미세 지연 측정 도구로 사용하기에는 한계가 존재합니다 [3, 11, 28]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/GPU_WebGL 파이프라인의 미세 지연(Micro-latency) 측정 사례.md]] +- Raw Source: 00_Raw/2026-04-20/GPU_WebGL 파이프라인의 미세 지연(Micro-latency) 측정 사례.md --- diff --git a/01_Archive/2026-04-20/GQL (Graph Query Language ISO 표준).md b/01_Archive/2026-04-20/GQL (Graph Query Language ISO 표준).md index 46140775..2967d4a6 100644 --- a/01_Archive/2026-04-20/GQL (Graph Query Language ISO 표준).md +++ b/01_Archive/2026-04-20/GQL (Graph Query Language ISO 표준).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-F13C1F -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - GQL (Graph Query Language ISO 표준)" --- -# [[GQL (Graph Query Language ISO 표준)]] +# [[GQL (Graph Query Language ISO 표준)|GQL (Graph Query Language ISO 표준)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - GQL (Graph Query Language ISO ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/GQL (Graph Query Language, ISO 표준).md]] +- Raw Source: 00_Raw/2026-04-20/GQL (Graph Query Language, ISO 표준).md --- diff --git a/01_Archive/2026-04-20/GQL (Graph Query Language, ISO 표준).md b/01_Archive/2026-04-20/GQL (Graph Query Language, ISO 표준).md index a644705e..9ec97aad 100644 --- a/01_Archive/2026-04-20/GQL (Graph Query Language, ISO 표준).md +++ b/01_Archive/2026-04-20/GQL (Graph Query Language, ISO 표준).md @@ -1,4 +1,4 @@ -[[GQL (Graph Query Language, ISO 표준 그래프 질의 언어)]] +GQL (Graph Query Language, ISO 표준 그래프 질의 언어) 📌 Brief Summary @@ -101,8 +101,8 @@ GQL은 SQL/PGQ(SQL:2023에 추가된 그래프 확장)와 밀접: 🔗 Knowledge Connections -- **Related Topics:** [[Cypher 질의 언어 (Neo4j)]], [[SPARQL (RDF 그래프 질의 언어)]], [[Labeled Property Graph (LPG, 속성 그래프)]], [[지식 그래프 (Knowledge Graph)]], [[GraphRAG (그래프 기반 검색 증강 생성)]], [[Federated SPARQL (연합 질의)]] -- **Projects/Contexts:** [[온톨로지 지식 베이스]] +- **Related Topics:** [[Cypher 질의 언어 (Neo4j)|Cypher 질의 언어 (Neo4j)]], [[SPARQL (RDF 그래프 질의 언어)|SPARQL (RDF 그래프 질의 언어)]], [[Labeled Property Graph (LPG, 속성 그래프)|Labeled Property Graph (LPG, 속성 그래프)]], [[지식 그래프 (Knowledge Graph)|지식 그래프 (Knowledge Graph)]], [[GraphRAG (그래프 기반 검색 증강 생성)|GraphRAG (그래프 기반 검색 증강 생성)]], [[Federated SPARQL (연합 질의)|Federated SPARQL (연합 질의)]] +- **Projects/Contexts:** [[온톨로지 지식 베이스|온톨로지 지식 베이스]] - **Contradictions/Notes:** - GQL 표준 채택(2024)은 됐지만 실제 벤더 구현은 점진적 → 완전한 GQL 지원까지 수년 소요 예상. - GQL과 Cypher는 문법이 유사하나 완전히 동일하지 않음 → 마이그레이션 시 일부 수정 필요. diff --git a/01_Archive/2026-04-20/GRPO (Group Relative Policy Optimization).md b/01_Archive/2026-04-20/GRPO (Group Relative Policy Optimization).md index 9058702b..4f5c61ce 100644 --- a/01_Archive/2026-04-20/GRPO (Group Relative Policy Optimization).md +++ b/01_Archive/2026-04-20/GRPO (Group Relative Policy Optimization).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-1312F9 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - GRPO (Group Relative Policy Optimization)" --- -# [[GRPO (Group Relative Policy Optimization)]] +# [[GRPO (Group Relative Policy Optimization)|GRPO (Group Relative Policy Optimization)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - GRPO (Group Relative Policy Op ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/GRPO (Group Relative Policy Optimization).md]] +- Raw Source: 00_Raw/2026-04-20/GRPO (Group Relative Policy Optimization).md --- diff --git a/01_Archive/2026-04-20/Gacha Mechanics Analysis.md b/01_Archive/2026-04-20/Gacha Mechanics Analysis.md index 91c15a67..d8d157a1 100644 --- a/01_Archive/2026-04-20/Gacha Mechanics Analysis.md +++ b/01_Archive/2026-04-20/Gacha Mechanics Analysis.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-F5E08D -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Gacha Mechanics Analysis" --- -# [[Gacha Mechanics Analysis]] +# [[Gacha Mechanics Analysis|Gacha Mechanics Analysis]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Gacha Mechanics Analysis" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Gacha Mechanics Analysis.md]] +- Raw Source: 00_Raw/2026-04-20/Gacha Mechanics Analysis.md --- diff --git a/01_Archive/2026-04-20/Gait-Analysis-Laboratory.md b/01_Archive/2026-04-20/Gait-Analysis-Laboratory.md index cacab3c5..56499f70 100644 --- a/01_Archive/2026-04-20/Gait-Analysis-Laboratory.md +++ b/01_Archive/2026-04-20/Gait-Analysis-Laboratory.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-3390EF -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Gait-Analysis-Laboratory" --- -# [[Gait-Analysis-Laboratory]] +# [[Gait-Analysis-Laboratory|Gait-Analysis-Laboratory]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Gait-Analysis-Laboratory" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Gait-Analysis-Laboratory.md]] +- Raw Source: 00_Raw/2026-04-20/Gait-Analysis-Laboratory.md --- diff --git a/01_Archive/2026-04-20/Gait-Analysis-Methodologies.md b/01_Archive/2026-04-20/Gait-Analysis-Methodologies.md index e6399682..7e8b93bf 100644 --- a/01_Archive/2026-04-20/Gait-Analysis-Methodologies.md +++ b/01_Archive/2026-04-20/Gait-Analysis-Methodologies.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-ECB110 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Gait-Analysis-Methodologies" --- -# [[Gait-Analysis-Methodologies]] +# [[Gait-Analysis-Methodologies|Gait-Analysis-Methodologies]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Gait-Analysis-Methodologies" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Gait-Analysis-Methodologies.md]] +- Raw Source: 00_Raw/2026-04-20/Gait-Analysis-Methodologies.md --- diff --git a/01_Archive/2026-04-20/Game Balance Theory.md b/01_Archive/2026-04-20/Game Balance Theory.md index f4b69677..2bc65b49 100644 --- a/01_Archive/2026-04-20/Game Balance Theory.md +++ b/01_Archive/2026-04-20/Game Balance Theory.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-FE4B62 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Game Balance Theory" --- -# [[Game Balance Theory]] +# [[Game Balance Theory|Game Balance Theory]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Game Balance Theory" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Game Balance Theory.md]] +- Raw Source: 00_Raw/2026-04-20/Game Balance Theory.md --- diff --git a/01_Archive/2026-04-20/Game Design Theory.md b/01_Archive/2026-04-20/Game Design Theory.md index 8bbe7672..406b1874 100644 --- a/01_Archive/2026-04-20/Game Design Theory.md +++ b/01_Archive/2026-04-20/Game Design Theory.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AI-059 -category: "[[10_Wiki/💡 Topics/Systemic Modeling & Fun]]" +category: "10_Wiki/💡 Topics/Systemic Modeling & Fun" confidence_score: 0.98 tags: [game design, system theory, ludology, emergent behavior] last_reinforced: 2026-06-XX github_commit: "[P-Reinforce] Processed Game Design Theory." --- -# [[Game Design Theory]] (게임 디자인 이론) +# [[Game Design Theory|Game Design Theory]] (게임 디자인 이론) ## 📌 한 줄 통찰 (The Karpathy Summary) > 게임의 재미와 깊이를 수학적, 심리학적, 시스템 공학적 관점에서 체계적으로 분석하고 설계하는 원칙과 방법론을 다룬다. 단순히 '재미있게'가 아닌, 예측 가능한 규칙(Ruleset) 위에서 발생하는 복잡한 상호작용에 집중한다. @@ -26,7 +26,7 @@ github_commit: "[P-Reinforce] Processed Game Design Theory." - **정책 변화:** 최근에는 AI 에이전트들이 게임 세계 내에서 자율적으로 상호작용하며 발생하는 예측 불가능한 시나리오(AI Agent Simulation)를 설계의 중요한 축으로 다루고 있다. ## 🔗 지식 연결 (Graph) -- Parent: [[Game Design Theory]] -- Related: [[Systemic Game Design]] , [[Emergent Gameplay]] , [[Behavioral Economics in Digital Ecosystems]] -- Raw Source: [[00_Raw/Game Design Theory.md]] +- Parent: [[Game Design Theory|Game Design Theory]] +- Related: [[Systemic Game Design|Systemic Game Design]] , [[Emergent Gameplay|Emergent Gameplay]] , [[Behavioral Economics in Digital Ecosystems|Behavioral Economics in Digital Ecosystems]] +- Raw Source: 00_Raw/Game Design Theory.md --- \ No newline at end of file diff --git a/01_Archive/2026-04-20/Game Economy Modeling.md b/01_Archive/2026-04-20/Game Economy Modeling.md index 1bda3a09..4c2efe0a 100644 --- a/01_Archive/2026-04-20/Game Economy Modeling.md +++ b/01_Archive/2026-04-20/Game Economy Modeling.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-80302B -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Game Economy Modeling" --- -# [[Game Economy Modeling]] +# [[Game Economy Modeling|Game Economy Modeling]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Game Economy Modeling" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Game Economy Modeling.md]] +- Raw Source: 00_Raw/2026-04-20/Game Economy Modeling.md --- diff --git a/01_Archive/2026-04-20/Game Engine Architecture (Jason Gregory).md b/01_Archive/2026-04-20/Game Engine Architecture (Jason Gregory).md index b1f1c45e..d54ebed1 100644 --- a/01_Archive/2026-04-20/Game Engine Architecture (Jason Gregory).md +++ b/01_Archive/2026-04-20/Game Engine Architecture (Jason Gregory).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-5CDF1A -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Game Engine Architecture (Jason Gregory)" --- -# [[Game Engine Architecture (Jason Gregory)]] +# [[Game Engine Architecture (Jason Gregory)|Game Engine Architecture (Jason Gregory)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Game Engine Architecture (Jaso ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Game Engine Architecture (Jason Gregory).md]] +- Raw Source: 00_Raw/2026-04-20/Game Engine Architecture (Jason Gregory).md --- diff --git a/01_Archive/2026-04-20/Game Engine Architecture.md b/01_Archive/2026-04-20/Game Engine Architecture.md index e411e03e..0df82696 100644 --- a/01_Archive/2026-04-20/Game Engine Architecture.md +++ b/01_Archive/2026-04-20/Game Engine Architecture.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-BD4476 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Game Engine Architecture" --- -# [[Game Engine Architecture]] +# [[Game Engine Architecture|Game Engine Architecture]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Game Engine Architecture" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Game Engine Architecture.md]] +- Raw Source: 00_Raw/2026-04-20/Game Engine Architecture.md --- diff --git a/01_Archive/2026-04-20/Game Studies (Academic Discipline).md b/01_Archive/2026-04-20/Game Studies (Academic Discipline).md index 071ec4b6..d128c899 100644 --- a/01_Archive/2026-04-20/Game Studies (Academic Discipline).md +++ b/01_Archive/2026-04-20/Game Studies (Academic Discipline).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-EFF2C4 -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Game Studies (Academic Discipline)" --- -# [[Game Studies (Academic Discipline)]] +# [[Game Studies (Academic Discipline)|Game Studies (Academic Discipline)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Game Studies (Academic Discipl ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Game Studies (Academic Discipline).md]] +- Raw Source: 00_Raw/2026-04-20/Game Studies (Academic Discipline).md --- diff --git a/01_Archive/2026-04-20/Game Studies (Digital Media Theory).md b/01_Archive/2026-04-20/Game Studies (Digital Media Theory).md index 6dacef14..28f79174 100644 --- a/01_Archive/2026-04-20/Game Studies (Digital Media Theory).md +++ b/01_Archive/2026-04-20/Game Studies (Digital Media Theory).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-46EF56 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Game Studies (Digital Media Theory)" --- -# [[Game Studies (Digital Media Theory)]] +# [[Game Studies (Digital Media Theory)|Game Studies (Digital Media Theory)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Game Studies (Digital Media Th ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Game Studies (Digital Media Theory).md]] +- Raw Source: 00_Raw/2026-04-20/Game Studies (Digital Media Theory).md --- diff --git a/01_Archive/2026-04-20/Game Studies (Game Studies Journal).md b/01_Archive/2026-04-20/Game Studies (Game Studies Journal).md index 0c96ea54..4cdbe6d8 100644 --- a/01_Archive/2026-04-20/Game Studies (Game Studies Journal).md +++ b/01_Archive/2026-04-20/Game Studies (Game Studies Journal).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-266459 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Game Studies (Game Studies Journal)" --- -# [[Game Studies (Game Studies Journal)]] +# [[Game Studies (Game Studies Journal)|Game Studies (Game Studies Journal)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Game Studies (Game Studies Jou ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Game Studies (Game Studies Journal).md]] +- Raw Source: 00_Raw/2026-04-20/Game Studies (Game Studies Journal).md --- diff --git a/01_Archive/2026-04-20/Game Studies (Ludology vs Narratology).md b/01_Archive/2026-04-20/Game Studies (Ludology vs Narratology).md index 0a5c0681..df43d253 100644 --- a/01_Archive/2026-04-20/Game Studies (Ludology vs Narratology).md +++ b/01_Archive/2026-04-20/Game Studies (Ludology vs Narratology).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-A1A637 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Game Studies (Ludology vs Narratology)" --- -# [[Game Studies (Ludology vs Narratology)]] +# [[Game Studies (Ludology vs Narratology)|Game Studies (Ludology vs Narratology)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Game Studies (Ludology vs Narr ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Game Studies (Ludology vs. Narratology).md]] +- Raw Source: 00_Raw/2026-04-20/Game Studies (Ludology vs. Narratology).md --- diff --git a/01_Archive/2026-04-20/Game Studies (Ludology vs. Narratology).md b/01_Archive/2026-04-20/Game Studies (Ludology vs. Narratology).md index bc27f38d..51f1c543 100644 --- a/01_Archive/2026-04-20/Game Studies (Ludology vs. Narratology).md +++ b/01_Archive/2026-04-20/Game Studies (Ludology vs. Narratology).md @@ -1,4 +1,4 @@ -[[Game Studies (Ludology vs. Narratology)]] +[[Game Studies (Ludology vs. Narratology)|Game Studies (Ludology vs. Narratology)]] 📌 Brief Summary The Ludology vs. Narratology debate refers to a foundational theoretical conflict in early game studies regarding the ontological nature of video games. It questions whether games should be analyzed primarily as systems of rules and mechanics (Ludology) or as structured storytelling media comparable to literature and film (Narratology). @@ -13,8 +13,8 @@ The Ludology vs. Narratology debate refers to a foundational theoretical conflic * **Contemporary Synthesis (Post-Debate):** Modern game studies has largely moved past this binary opposition toward a more integrated approach. Scholars now examine how mechanics and narrative are inextricably linked through concepts like *ludonarrative dissonance* (the conflict between gameplay actions and story beats) and *ludonarrative harmony*. Current research focuses on "procedural rhetoric"—how the rules of a game function as a form of argumentation—and how procedurality can be used to construct meaning, effectively merging the study of systems with the study of meaning-making. 🔗 Knowledge Connections -* Related Topics: [[Procedural Rhetoric]], [[Ergodic Literature]], [[Ludonarrative Dissonance]], [[Cybertext Theory]] -* Projects/Contexts: [[Digital Humanities]], [[Formalist Game Design]], [[Interactive Storytelling]] +* Related Topics: [[Procedural Rhetoric|Procedural Rhetoric]], [[Ergodic Literature|Ergodic Literature]], [[Ludonarrative Dissonance|Ludonarrative Dissonance]], [[Cybertext Theory|Cybertext Theory]] +* Projects/Contexts: [[Digital Humanities|Digital Humanities]], [[Formalist Game Design|Formalist Game Design]], [[Interactive Storytelling|Interactive Storytelling]] * Contradictions/Notes: While early scholars like Espen Aarseth and Marie-Laure Ryan represented opposing poles, contemporary scholarship views the distinction as a false dichotomy; most modern researchers study how mechanics *mediate* narrative. Last updated: 2026-04-16 \ No newline at end of file diff --git a/01_Archive/2026-04-20/Game Studies.md b/01_Archive/2026-04-20/Game Studies.md index f1bc9457..9944833e 100644 --- a/01_Archive/2026-04-20/Game Studies.md +++ b/01_Archive/2026-04-20/Game Studies.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-21CD99 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Game Studies" --- -# [[Game Studies]] +# [[Game Studies|Game Studies]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Game Studies" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Game Studies.md]] +- Raw Source: 00_Raw/2026-04-20/Game Studies.md --- diff --git a/01_Archive/2026-04-20/Game Systems Design.md b/01_Archive/2026-04-20/Game Systems Design.md index d3e79cff..72c778e0 100644 --- a/01_Archive/2026-04-20/Game Systems Design.md +++ b/01_Archive/2026-04-20/Game Systems Design.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-1D378F -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Game Systems Design" --- -# [[Game Systems Design]] +# [[Game Systems Design|Game Systems Design]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Game Systems Design" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Game Systems Design.md]] +- Raw Source: 00_Raw/2026-04-20/Game Systems Design.md --- diff --git a/01_Archive/2026-04-20/Game Theory (Economics).md b/01_Archive/2026-04-20/Game Theory (Economics).md index d593f256..f9cc7a05 100644 --- a/01_Archive/2026-04-20/Game Theory (Economics).md +++ b/01_Archive/2026-04-20/Game Theory (Economics).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-329226 -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Game Theory (Economics)" --- -# [[Game Theory (Economics)]] +# [[Game Theory (Economics)|Game Theory (Economics)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Game Theory (Economics)" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Game Theory (Economics).md]] +- Raw Source: 00_Raw/2026-04-20/Game Theory (Economics).md --- diff --git a/01_Archive/2026-04-20/Game Theory and Market Equilibrium.md b/01_Archive/2026-04-20/Game Theory and Market Equilibrium.md index 5547fccf..758ac715 100644 --- a/01_Archive/2026-04-20/Game Theory and Market Equilibrium.md +++ b/01_Archive/2026-04-20/Game Theory and Market Equilibrium.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-C0E0BE -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Game Theory and Market Equilibrium" --- -# [[Game Theory and Market Equilibrium]] +# [[Game Theory and Market Equilibrium|Game Theory and Market Equilibrium]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Game Theory and Market Equilib ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Game Theory and Market Equilibrium.md]] +- Raw Source: 00_Raw/2026-04-20/Game Theory and Market Equilibrium.md --- diff --git a/01_Archive/2026-04-20/Game Theory.md b/01_Archive/2026-04-20/Game Theory.md index 8529af61..5a1f0bac 100644 --- a/01_Archive/2026-04-20/Game Theory.md +++ b/01_Archive/2026-04-20/Game Theory.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-69600C -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Game Theory" --- -# [[Game Theory]] +# [[Game Theory|Game Theory]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Game Theory" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Game Theory.md]] +- Raw Source: 00_Raw/2026-04-20/Game Theory.md --- diff --git a/01_Archive/2026-04-20/Game-Design-Ontology.md b/01_Archive/2026-04-20/Game-Design-Ontology.md index 2bfb53c1..784b2c4e 100644 --- a/01_Archive/2026-04-20/Game-Design-Ontology.md +++ b/01_Archive/2026-04-20/Game-Design-Ontology.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-DCD5C6 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Game-Design-Ontology" --- -# [[Game-Design-Ontology]] +# [[Game-Design-Ontology|Game-Design-Ontology]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Game-Design-Ontology" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Game-Design-Ontology.md]] +- Raw Source: 00_Raw/2026-04-20/Game-Design-Ontology.md --- diff --git a/01_Archive/2026-04-20/Game-Design-Theory.md b/01_Archive/2026-04-20/Game-Design-Theory.md index 366589f5..3a09db65 100644 --- a/01_Archive/2026-04-20/Game-Design-Theory.md +++ b/01_Archive/2026-04-20/Game-Design-Theory.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-25F5B7 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Game-Design-Theory" --- -# [[Game-Design-Theory]] +# [[Game-Design-Theory|Game-Design-Theory]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Game-Design-Theory" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Game-Design-Theory.md]] +- Raw Source: 00_Raw/2026-04-20/Game-Design-Theory.md --- diff --git a/01_Archive/2026-04-20/Game-Level-Design.md b/01_Archive/2026-04-20/Game-Level-Design.md index 46e74b79..78a1642b 100644 --- a/01_Archive/2026-04-20/Game-Level-Design.md +++ b/01_Archive/2026-04-20/Game-Level-Design.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-B42B04 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Game-Level-Design" --- -# [[Game-Level-Design]] +# [[Game-Level-Design|Game-Level-Design]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Game-Level-Design" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Game-Level-Design.md]] +- Raw Source: 00_Raw/2026-04-20/Game-Level-Design.md --- diff --git a/01_Archive/2026-04-20/Game-Ontology-for-PCG.md b/01_Archive/2026-04-20/Game-Ontology-for-PCG.md index 2f00f9fa..a8b55a85 100644 --- a/01_Archive/2026-04-20/Game-Ontology-for-PCG.md +++ b/01_Archive/2026-04-20/Game-Ontology-for-PCG.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-D042FF -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Game-Ontology-for-PCG" --- -# [[Game-Ontology-for-PCG]] +# [[Game-Ontology-for-PCG|Game-Ontology-for-PCG]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Game-Ontology-for-PCG" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Game-Ontology-for-PCG.md]] +- Raw Source: 00_Raw/2026-04-20/Game-Ontology-for-PCG.md --- diff --git a/01_Archive/2026-04-20/Game-Studies-Academic-Discourse.md b/01_Archive/2026-04-20/Game-Studies-Academic-Discourse.md index ba500fad..e8b5d688 100644 --- a/01_Archive/2026-04-20/Game-Studies-Academic-Discourse.md +++ b/01_Archive/2026-04-20/Game-Studies-Academic-Discourse.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-A0CB96 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Game-Studies-Academic-Discourse" --- -# [[Game-Studies-Academic-Discourse]] +# [[Game-Studies-Academic-Discourse|Game-Studies-Academic-Discourse]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Game-Studies-Academic-Discours ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Game-Studies-Academic-Discourse.md]] +- Raw Source: 00_Raw/2026-04-20/Game-Studies-Academic-Discourse.md --- diff --git a/01_Archive/2026-04-20/Game-Studies-Journal.md b/01_Archive/2026-04-20/Game-Studies-Journal.md index 47005a90..06165ef9 100644 --- a/01_Archive/2026-04-20/Game-Studies-Journal.md +++ b/01_Archive/2026-04-20/Game-Studies-Journal.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-66A318 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Game-Studies-Journal" --- -# [[Game-Studies-Journal]] +# [[Game-Studies-Journal|Game-Studies-Journal]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Game-Studies-Journal" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Game-Studies-Journal.md]] +- Raw Source: 00_Raw/2026-04-20/Game-Studies-Journal.md --- diff --git a/01_Archive/2026-04-20/Gamification Theory.md b/01_Archive/2026-04-20/Gamification Theory.md index 7c04375b..67343569 100644 --- a/01_Archive/2026-04-20/Gamification Theory.md +++ b/01_Archive/2026-04-20/Gamification Theory.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-2DF448 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Gamification Theory" --- -# [[Gamification Theory]] +# [[Gamification Theory|Gamification Theory]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Gamification Theory" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Gamification Theory.md]] +- Raw Source: 00_Raw/2026-04-20/Gamification Theory.md --- diff --git a/01_Archive/2026-04-20/Gamification in Pedagogy.md b/01_Archive/2026-04-20/Gamification in Pedagogy.md index afa91743..2c6d60aa 100644 --- a/01_Archive/2026-04-20/Gamification in Pedagogy.md +++ b/01_Archive/2026-04-20/Gamification in Pedagogy.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-0CBD32 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Gamification in Pedagogy" --- -# [[Gamification in Pedagogy]] +# [[Gamification in Pedagogy|Gamification in Pedagogy]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Gamification in Pedagogy" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Gamification in Pedagogy.md]] +- Raw Source: 00_Raw/2026-04-20/Gamification in Pedagogy.md --- diff --git a/01_Archive/2026-04-20/Gamification-Design.md b/01_Archive/2026-04-20/Gamification-Design.md index b3bb48e8..3dbaec3e 100644 --- a/01_Archive/2026-04-20/Gamification-Design.md +++ b/01_Archive/2026-04-20/Gamification-Design.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-8C354C -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Gamification-Design" --- -# [[Gamification-Design]] +# [[Gamification-Design|Gamification-Design]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Gamification-Design" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Gamification-Design.md]] +- Raw Source: 00_Raw/2026-04-20/Gamification-Design.md --- diff --git a/01_Archive/2026-04-20/Gamification-Mechanics.md b/01_Archive/2026-04-20/Gamification-Mechanics.md index 0a3eb006..120f7587 100644 --- a/01_Archive/2026-04-20/Gamification-Mechanics.md +++ b/01_Archive/2026-04-20/Gamification-Mechanics.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-687945 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Gamification-Mechanics" --- -# [[Gamification-Mechanics]] +# [[Gamification-Mechanics|Gamification-Mechanics]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Gamification-Mechanics" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Gamification-Mechanics.md]] +- Raw Source: 00_Raw/2026-04-20/Gamification-Mechanics.md --- diff --git a/01_Archive/2026-04-20/Garbage Collection (GC) 최적화.md b/01_Archive/2026-04-20/Garbage Collection (GC) 최적화.md index 817641f4..1bd24c10 100644 --- a/01_Archive/2026-04-20/Garbage Collection (GC) 최적화.md +++ b/01_Archive/2026-04-20/Garbage Collection (GC) 최적화.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-6C336D -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Garbage Collection (GC) 최적화" --- -# [[Garbage Collection (GC) 최적화]] +# [[Garbage Collection (GC) 최적화|Garbage Collection (GC) 최적화]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -26,8 +26,8 @@ github_commit: "[P-Reinforce] Continuous Worker - Garbage Collection (GC) 최적 - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Object Pooling (오브젝트 풀링)]], [[Memory Leak Prevention (메모리 누수 방지)]], [[Generational GC (세대별 가비지 컬렉션)]], [[React Three Fiber (R3F) 자산 최적화]] -- **Projects/Contexts:** [[수만 개의 엔티티가 존재하는 실시간 물리 시뮬레이션]], [[대규모 파티클 시스템 최적화]] +- **Related Topics:** [[Object Pooling (오브젝트 풀링)|Object Pooling (오브젝트 풀링)]], [[Memory Leak Prevention 메모리 누수 방지|Memory Leak Prevention (메모리 누수 방지)]], Generational GC (세대별 가비지 컬렉션), React Three Fiber (R3F) 자산 최적화 +- **Projects/Contexts:** 수만 개의 엔티티가 존재하는 실시간 물리 시뮬레이션, [[대규모 파티클 시스템 최적화|대규모 파티클 시스템 최적화]] - **Contradictions/Notes:** 가비지 컬렉션의 멈춤 현상을 극도로 피해야 하는 환경(예: AAA급 웹 게임)에서는 ECS(엔티티 컴포넌트 시스템)와 같이 자바스크립트 기본 객체가 아닌, 연속된 `TypedArray` 형태의 메모리 버퍼(SoA)를 직접 다루는 데이터 지향 설계(Data-Oriented Design)를 통해 GC 자체를 원천 우회하는 설계가 활용되기도 합니다. -- Raw Source: [[00_Raw/2026-04-20/Garbage Collection (GC) 최적화.md]] +- Raw Source: 00_Raw/2026-04-20/Garbage Collection (GC) 최적화.md --- diff --git a/01_Archive/2026-04-20/Garbage Collection (GC).md b/01_Archive/2026-04-20/Garbage Collection (GC).md index fe7dad02..11d024c5 100644 --- a/01_Archive/2026-04-20/Garbage Collection (GC).md +++ b/01_Archive/2026-04-20/Garbage Collection (GC).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-99978B -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Garbage Collection (GC)" --- -# [[Garbage Collection (GC)]] +# [[Garbage Collection (GC)|Garbage Collection (GC)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 가비지 컬렉션(GC)은 프로그램에서 더 이상 사용되지 않는 객체(가비지)를 식별하고 그들이 차지하던 메모리를 자동으로 회수하여 재사용할 수 있도록 하는 메모리 관리 프로세스입니다 [1, 2]. 이 방식은 개발자가 명시적으로 메모리를 관리할 필요성을 줄여 애플리케이션의 메모리 누수와 오류를 방지하는 이점이 있습니다 [3]. 하지만 GC가 실행되는 동안에는 프로그램 실행이 멈추는 'Stop-the-world' 현상이 발생할 수 있으므로, 응답성과 성능을 유지하기 위해 엔진 수준에서 다양한 최적화 기법이 함께 적용됩니다 [2, 4]. @@ -20,11 +20,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Garbage Collection (GC)" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Mark-Sweep-Compact]], [[Scavenger (Minor GC)]], [[Generational GC]], [[Orinoco]] -- **Projects/Contexts:** [[V8 JavaScript Engine]], [[Eclipse OpenJ9 VM]], [[Node.js Memory Management]] +- **Related Topics:** [[Mark-Sweep-Compact|Mark-Sweep-Compact]], [[Scavenger(Minor GC)|Scavenger (Minor GC)]], Generational GC, [[Orinoco|Orinoco]] +- **Projects/Contexts:** [[V8 JavaScript Engine|V8 JavaScript Engine]], Eclipse OpenJ9 VM, [[Node.js Memory Management|Node.js Memory Management]] - **Contradictions/Notes:** 가비지 컬렉션은 개발자에게서 메모리 관리의 부담을 없애주는 매우 강력한 기능이지만 제어 권한을 완전히 잃게 된다는 양날의 검과 같은 특성을 가집니다 [3, 4]. 관리되지 않는(Unmanaged) 언어와 비교해 무조건적으로 성능이 더 좋거나 나쁜 것은 아니며, 적절히 최적화되지 않은 GC 시스템은 길고 예측 불가능한 멈춤 현상을 발생시킬 수 있습니다 [4]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Garbage Collection (GC).md]] +- Raw Source: 00_Raw/2026-04-20/Garbage Collection (GC).md --- diff --git a/01_Archive/2026-04-20/Garbage Collection(가비지 컬렉션).md b/01_Archive/2026-04-20/Garbage Collection(가비지 컬렉션).md index 882f2717..d56b5606 100644 --- a/01_Archive/2026-04-20/Garbage Collection(가비지 컬렉션).md +++ b/01_Archive/2026-04-20/Garbage Collection(가비지 컬렉션).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-CA2F39 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Garbage Collection(가비지 컬렉션)" --- -# [[Garbage Collection(가비지 컬렉션)]] +# [[Garbage Collection(가비지 컬렉션)|Garbage Collection(가비지 컬렉션)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 가비지 컬렉션(Garbage Collection)은 애플리케이션의 메모리 고갈을 방지하기 위해 더 이상 필요하지 않거나 도달할 수 없는 객체가 차지한 메모리를 자동으로 식별하여 회수하는 프로세스입니다 [1-3]. 이 기술은 프로그래머가 직접 메모리를 관리하는 부담을 덜어주고 메모리 누수와 같은 오류를 줄여주지만, 메모리 정리 작업 중 애플리케이션 실행이 멈추는 'Stop-the-world' 지연을 발생시킬 수 있습니다 [2, 4, 5]. 현대의 가비지 컬렉터들은 이러한 지연 시간을 최소화하기 위해 세대별 힙 구조(Generational Layout)와 병렬 및 동시 처리 알고리즘을 도입하여 성능을 최적화하고 있습니다 [6-8]. @@ -41,11 +41,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Garbage Collection(가비지 - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Mark-Sweep]], [[Scavenger]], [[Stop-the-world]], [[Generational Hypothesis]], [[Memory Leak]] -- **Projects/Contexts:** [[V8 JavaScript Engine]], [[IBM Eclipse OpenJ9]], [[Orinoco Garbage Collector]] +- **Related Topics:** [[Mark-Sweep|Mark-Sweep]], [[Scavenger 알고리즘|Scavenger]], [[Stop-the-world|Stop-the-world]], [[Generational Hypothesis|Generational Hypothesis]], [[Memory Leak|Memory Leak]] +- **Projects/Contexts:** [[V8 JavaScript Engine|V8 JavaScript Engine]], IBM Eclipse OpenJ9, Orinoco Garbage Collector - **Contradictions/Notes:** 가비지 컬렉션은 메모리 누수를 대폭 줄여주지만, 프로그래머가 메모리 관리에 대한 전적인 통제권을 잃는다는 단점이 존재합니다(모바일 앱 등에서는 큰 문제점) [4, 5]. 또한 대안으로 거론되는 레퍼런스 카운팅(Reference Counting) 방식 역시 대규모 객체 그래프의 마지막 참조가 제거될 때 가비지 컬렉션과 유사한 예측 불가능한 정지 현상을 유발할 수 있어 완벽한 대체재는 아닙니다 [5]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Garbage Collection(가비지 컬렉션).md]] +- Raw Source: 00_Raw/2026-04-20/Garbage Collection(가비지 컬렉션).md --- diff --git a/01_Archive/2026-04-20/Garbage Collection.md b/01_Archive/2026-04-20/Garbage Collection.md index 0982250d..4cec27b6 100644 --- a/01_Archive/2026-04-20/Garbage Collection.md +++ b/01_Archive/2026-04-20/Garbage Collection.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-F5453B -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Garbage Collection" --- -# [[Garbage Collection]] +# [[Garbage Collection|Garbage Collection]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 가비지 컬렉션(Garbage Collection, GC)은 사용되지 않는 구형 데이터를 메모리에서 해제하는 자바스크립트 엔진의 메모리 관리 프로세스입니다 [1]. 하지만 Three.js와 같은 실시간 3D 렌더링 환경에서는 빈번한 객체 생성이나 메모리 한계 초과로 인해 가비지 컬렉터가 작동할 경우, 프레임이 일시적으로 멈추는(Stuttering) 심각한 성능 저하가 발생할 수 있습니다 [1-3]. 또한, Three.js는 GPU 자원에 대해 자동으로 가비지 컬렉션을 수행하지 않기 때문에 개발자의 명시적인 메모리 관리가 필수적입니다 [4]. @@ -23,11 +23,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Garbage Collection" - **정책 변화:** Graphics & Performance 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Memory Management]], [[Object Pooling]], [[GPU Resources]] -- **Projects/Contexts:** [[Three.js]], [[WebGL]] +- **Related Topics:** [[Memory Management|Memory Management]], [[Object Pooling|Object Pooling]], [[GPU Resources|GPU Resources]] +- **Projects/Contexts:** [[Three.js|Three.js]], [[WebGL|WebGL]] - **Contradictions/Notes:** 소스에 관련 정보가 부족합니다. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Garbage Collection.md]] +- Raw Source: 00_Raw/2026-04-20/Garbage Collection.md --- diff --git a/01_Archive/2026-04-20/Generational Hypothesis.md b/01_Archive/2026-04-20/Generational Hypothesis.md index 7c2746e9..2ea5ea06 100644 --- a/01_Archive/2026-04-20/Generational Hypothesis.md +++ b/01_Archive/2026-04-20/Generational Hypothesis.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-D9833D -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Generational Hypothesis" --- -# [[Generational Hypothesis]] +# [[Generational Hypothesis|Generational Hypothesis]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 세대 가설(Generational Hypothesis)은 대부분의 객체가 생성된 직후에 도달할 수 없는 상태가 되어 소멸한다는(die young) 프로그래밍의 경험적 관찰을 의미합니다 [1, 2]. 이 원리는 V8이나 JavaScript뿐만 아니라 대부분의 동적 프로그래밍 언어에 적용되는 가비지 컬렉션의 핵심 전제입니다 [2]. V8 엔진은 이 가설을 적극적으로 활용하여 메모리 힙을 '젊은 세대(Young Generation)'와 '오래된 세대(Old Generation)'로 분할함으로써 가비지 컬렉션의 효율성과 성능을 최적화합니다 [1, 3, 4]. @@ -24,11 +24,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Generational Hypothesis" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Garbage Collection]], [[V8 JavaScript Engine]], [[Young Generation (New Space)]], [[Old Generation (Old Space)]], [[Scavenger (Minor GC)]] -- **Projects/Contexts:** [[V8 Memory Management]] +- **Related Topics:** [[Garbage Collection|Garbage Collection]], [[V8 JavaScript Engine|V8 JavaScript Engine]], Young Generation (New Space), Old Generation (Old Space), [[Scavenger(Minor GC)|Scavenger (Minor GC)]] +- **Projects/Contexts:** V8 Memory Management - **Contradictions/Notes:** 제공된 소스들은 모두 일관되게 세대 가설의 원리와 V8 엔진 내 적용 방식을 지지하며, 이에 반대되는 모순된 주장이나 기록은 확인되지 않습니다. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Generational Hypothesis.md]] +- Raw Source: 00_Raw/2026-04-20/Generational Hypothesis.md --- diff --git a/01_Archive/2026-04-20/Generative Adversarial Networks (GANs) in Fine Arts.md b/01_Archive/2026-04-20/Generative Adversarial Networks (GANs) in Fine Arts.md index 30077d7f..397f1aae 100644 --- a/01_Archive/2026-04-20/Generative Adversarial Networks (GANs) in Fine Arts.md +++ b/01_Archive/2026-04-20/Generative Adversarial Networks (GANs) in Fine Arts.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-B61BB5 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Generative Adversarial Networks (GANs) in Fine Arts" --- -# [[Generative Adversarial Networks (GANs) in Fine Arts]] +# [[Generative Adversarial Networks (GANs) in Fine Arts|Generative Adversarial Networks (GANs) in Fine Arts]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Generative Adversarial Network ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Generative Adversarial Networks (GANs) in Fine Arts.md]] +- Raw Source: 00_Raw/2026-04-20/Generative Adversarial Networks (GANs) in Fine Arts.md --- diff --git a/01_Archive/2026-04-20/Generative-Adversarial-Networks.md b/01_Archive/2026-04-20/Generative-Adversarial-Networks.md index 7834b4d7..0838fc68 100644 --- a/01_Archive/2026-04-20/Generative-Adversarial-Networks.md +++ b/01_Archive/2026-04-20/Generative-Adversarial-Networks.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-B87DE0 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Generative-Adversarial-Networks" --- -# [[Generative-Adversarial-Networks]] +# [[Generative-Adversarial-Networks|Generative-Adversarial-Networks]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Generative-Adversarial-Network ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Generative-Adversarial-Networks.md]] +- Raw Source: 00_Raw/2026-04-20/Generative-Adversarial-Networks.md --- diff --git a/01_Archive/2026-04-20/Generics-and-Polymorphism.md b/01_Archive/2026-04-20/Generics-and-Polymorphism.md index f9480826..485732d8 100644 --- a/01_Archive/2026-04-20/Generics-and-Polymorphism.md +++ b/01_Archive/2026-04-20/Generics-and-Polymorphism.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-E65F53 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Generics-and-Polymorphism" --- -# [[Generics-and-Polymorphism]] +# [[Generics-and-Polymorphism|Generics-and-Polymorphism]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Generics-and-Polymorphism" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Generics-and-Polymorphism.md]] +- Raw Source: 00_Raw/2026-04-20/Generics-and-Polymorphism.md --- diff --git a/01_Archive/2026-04-20/Geographic-Information-Systems (GIS).md b/01_Archive/2026-04-20/Geographic-Information-Systems (GIS).md index d009d8d2..0a86f56e 100644 --- a/01_Archive/2026-04-20/Geographic-Information-Systems (GIS).md +++ b/01_Archive/2026-04-20/Geographic-Information-Systems (GIS).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-395A13 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Geographic-Information-Systems (GIS)" --- -# [[Geographic-Information-Systems (GIS)]] +# [[Geographic-Information-Systems (GIS)|Geographic-Information-Systems (GIS)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Geographic-Information-Systems ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Geographic-Information-Systems (GIS).md]] +- Raw Source: 00_Raw/2026-04-20/Geographic-Information-Systems (GIS).md --- diff --git a/01_Archive/2026-04-20/Geometry Merging.md b/01_Archive/2026-04-20/Geometry Merging.md index 71cc14ac..7f490608 100644 --- a/01_Archive/2026-04-20/Geometry Merging.md +++ b/01_Archive/2026-04-20/Geometry Merging.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-4349BD -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Geometry Merging" --- -# [[Geometry Merging]] +# [[Geometry Merging|Geometry Merging]] ## 📌 한 줄 통찰 (The Karpathy Summary) > **Geometry Merging(지오메트리 병합)**은 Three.js 등의 3D 렌더링 환경에서 정적(static)인 여러 개의 기하학적 데이터를 단일 `BufferGeometry`로 합치는 최적화 기법입니다. 이는 여러 개의 메쉬를 개별적으로 그릴 때 발생하는 **드로우 콜(Draw call)을 단 1회로 줄여주어** CPU 오버헤드를 크게 감소시킵니다. 하지만 개별 객체의 독립적인 이동이나 실시간 상호작용이 제한되며, 객체가 반복될 경우 메모리 사용량이 극심하게 증가한다는 뚜렷한 한계를 가집니다. @@ -30,11 +30,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Geometry Merging" - **정책 변화:** Graphics & Performance 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Draw Call]], [[InstancedMesh]], [[BatchedMesh]], [[Frustum Culling]], [[BufferGeometry]] -- **Projects/Contexts:** [[IFC.js Fragment]], [[CAD Rendering Optimization]] +- **Related Topics:** [[Draw Call|Draw Call]], [[InstancedMesh|InstancedMesh]], [[BatchedMesh|BatchedMesh]], [[Frustum Culling|Frustum Culling]], [[BufferGeometry|BufferGeometry]] +- **Projects/Contexts:** [[IFCjs (Fragment)|IFC.js Fragment]], CAD Rendering Optimization - **Contradictions/Notes:** 지오메트리 병합은 드로우 콜을 크게 줄여 렌더링 속도를 높이는 장점이 있지만, 단일 바운딩 박스로 묶이게 되어 시야 절두체 컬링 효율성이 떨어지고 메모리 사용량이 극도로 높아져 하드웨어 자원을 쉽게 고갈시킬 수 있다는 트레이드오프(Trade-off)가 존재합니다 [3, 4]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Geometry Merging.md]] +- Raw Source: 00_Raw/2026-04-20/Geometry Merging.md --- diff --git a/01_Archive/2026-04-20/Geriatric-Medicine.md b/01_Archive/2026-04-20/Geriatric-Medicine.md index 6624c18c..f2839c09 100644 --- a/01_Archive/2026-04-20/Geriatric-Medicine.md +++ b/01_Archive/2026-04-20/Geriatric-Medicine.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-88176E -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Geriatric-Medicine" --- -# [[Geriatric-Medicine]] +# [[Geriatric-Medicine|Geriatric-Medicine]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Geriatric-Medicine" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Geriatric-Medicine.md]] +- Raw Source: 00_Raw/2026-04-20/Geriatric-Medicine.md --- diff --git a/01_Archive/2026-04-20/Git Hooks.md b/01_Archive/2026-04-20/Git Hooks.md index 6f46d788..b588a682 100644 --- a/01_Archive/2026-04-20/Git Hooks.md +++ b/01_Archive/2026-04-20/Git Hooks.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-F69A27 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Git Hooks" --- -# [[Git Hooks]] +# [[Git Hooks|Git Hooks]] ## 📌 한 줄 통찰 (The Karpathy Summary) > Git Hooks는 Git 워크플로의 특정 이벤트(commit, push, merge 등)가 발생할 때 자동으로 실행되도록 설정할 수 있는 셸 스크립트 또는 실행 가능한 프로그램입니다 [1-3]. 주로 개발자가 코드를 커밋하거나 푸시하기 직전에 린트(Lint), 코드 포맷팅, 테스트 등을 실행하여 오류가 있는 코드가 리포지토리에 저장되는 것을 방지하고 코드 퀄리티를 일관되게 유지하는 역할을 합니다 [4, 5]. @@ -35,11 +35,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Git Hooks" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** `[[Husky]]`, `[[lint-staged]]`, `[[ESLint]]`, `[[Prettier]]` -- **Projects/Contexts:** `[[CI/CD 파이프라인 (CI/CD Pipelines)]]`, `[[코드 품질 관리 및 자동화 (Code Quality Management and Automation)]]` +- **Related Topics:** `[[Husky|Husky]]`, `[[lint-staged|lint-staged]]`, `[[ESLint|ESLint]]`, `[[Prettier|Prettier]]` +- **Projects/Contexts:** `[[CI_CD 파이프라인 (CI_CD Pipelines)|CI/CD 파이프라인 (CI/CD Pipelines)]]`, `[[코드 품질 관리 및 자동화 (Code Quality Management and Automation)|코드 품질 관리 및 자동화 (Code Quality Management and Automation)]]` - **Contradictions/Notes:** 소스에 따르면 Git Hook은 개발자가 강제로 우회(`--no-verify` 등)할 수 있으므로 절대적이고 완벽한 강제 수단이 될 수는 없습니다. 따라서 Hook은 로컬 환경에서 빠른 피드백을 제공하기 위한 도구로 취급되어야 하며, 최종적인 보안 및 품질 검증의 권한은 항상 CI(지속적 통합) 서버가 담당해야 한다고 강조합니다 [8, 14, 15]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/Git Hooks.md]] +- Raw Source: 00_Raw/2026-04-20/Git Hooks.md --- diff --git a/01_Archive/2026-04-20/Git Hook을 이용한 CI_CD 자동화 파이프라인.md b/01_Archive/2026-04-20/Git Hook을 이용한 CI_CD 자동화 파이프라인.md index 74add408..fb055a3e 100644 --- a/01_Archive/2026-04-20/Git Hook을 이용한 CI_CD 자동화 파이프라인.md +++ b/01_Archive/2026-04-20/Git Hook을 이용한 CI_CD 자동화 파이프라인.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-E60BE3 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Git Hook을 이용한 CI_CD 자동화 파이프라인" --- -# [[Git Hook을 이용한 CI_CD 자동화 파이프라인]] +# [[Git Hook을 이용한 CI_CD 자동화 파이프라인|Git Hook을 이용한 CI_CD 자동화 파이프라인]] ## 📌 한 줄 통찰 (The Karpathy Summary) > Git 훅(Git Hooks)은 소스 코드 버전 관리 시스템인 Git의 특정 작업(commit, push 등) 전후에 자동으로 실행되도록 설정된 쉘 스크립트이다 [1]. 프론트엔드 및 Node.js 생태계에서는 주로 Husky와 lint-staged라는 도구를 활용하여 Git 훅을 설정하고 관리한다 [2], [3]. 이를 통해 코드가 원격 저장소나 CI 파이프라인으로 넘어가기 전인 로컬 단계에서 코드 스타일, 포맷팅(Prettier), 문법적 오류(ESLint) 등을 자동으로 검사하고 수정함으로써 일관된 품질을 강제하는 '최전선 방어선' 역할을 수행한다 [1], [4], [3]. @@ -31,11 +31,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Git Hook을 이용한 CI_CD - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Husky]], [[lint-staged]], [[ESLint]], [[Prettier]] -- **Projects/Contexts:** [[자동화된 코드 품질 및 스타일 검사 워크플로우]] +- **Related Topics:** [[Husky|Husky]], [[lint-staged|lint-staged]], [[ESLint|ESLint]], [[Prettier|Prettier]] +- **Projects/Contexts:** 자동화된 코드 품질 및 스타일 검사 워크플로우 - **Contradictions/Notes:** lint-staged는 버전 10부터 성공적으로 파일이 수정되면 자동으로 `git add`를 수행하므로, 설정 파일의 커맨드 목록에 수동으로 `git add`를 넣는 것은 중복 작업 및 레이스 컨디션(race condition)을 유발할 수 있어 더 이상 권장되지 않는다 [17], [21]. 또한, 로컬 Git 훅은 우회(`--no-verify`)가 가능하므로 완벽한 정책 집행 경계가 될 수 없으며, CI 서버를 보완하는 성격으로 사용해야 한다 [19], [8], [21]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Git Hook을 이용한 CI_CD 자동화 파이프라인.md]] +- Raw Source: 00_Raw/2026-04-20/Git Hook을 이용한 CI_CD 자동화 파이프라인.md --- diff --git a/01_Archive/2026-04-20/Git Pre-commit 훅을 활용한 개발 워크플로우 자동화.md b/01_Archive/2026-04-20/Git Pre-commit 훅을 활용한 개발 워크플로우 자동화.md index 3fe28a81..1455f840 100644 --- a/01_Archive/2026-04-20/Git Pre-commit 훅을 활용한 개발 워크플로우 자동화.md +++ b/01_Archive/2026-04-20/Git Pre-commit 훅을 활용한 개발 워크플로우 자동화.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-26C070 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Git Pre-commit 훅을 활용한 개발 워크플로우 자동화" --- -# [[Git Pre-commit 훅을 활용한 개발 워크플로우 자동화]] +# [[Git Pre-commit 훅을 활용한 개발 워크플로우 자동화|Git Pre-commit 훅을 활용한 개발 워크플로우 자동화]] ## 📌 한 줄 통찰 (The Karpathy Summary) > Git Pre-commit 훅은 커밋이 코드 저장소에 기록되기 직전에 자동으로 실행되는 스크립트이다 [1]. 개발 팀은 주로 Husky와 lint-staged 같은 도구를 결합하여 사용하여, 커밋 대상 파일(staged files)에 대해서만 린트(Lint) 검사와 코드 포맷팅을 자동으로 수행한다 [2, 3]. 이를 통해 문법적 결함이 있거나 팀의 컨벤션에 맞지 않는 코드가 저장소에 유입되는 것을 사전에 차단하고, 일관된 코드 품질을 빠르고 효율적으로 유지할 수 있다 [3, 4]. @@ -24,11 +24,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Git Pre-commit 훅을 활용 - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Husky]], [[lint-staged]], [[ESLint]], [[Prettier]], [[Continuous Integration (CI)]] -- **Projects/Contexts:** [[팀 단위 코드 품질 및 컨벤션 유지]], [[대규모 모노레포(Turborepo) 환경에서의 린트 오케스트레이션]] +- **Related Topics:** [[Husky|Husky]], [[lint-staged|lint-staged]], [[ESLint|ESLint]], [[Prettier|Prettier]], [[Continuous Integration (CI)|Continuous Integration (CI)]] +- **Projects/Contexts:** [[팀 단위 코드 품질 및 컨벤션 유지|팀 단위 코드 품질 및 컨벤션 유지]], [[대규모 모노레포(Turborepo) 환경에서의 린트 오케스트레이션|대규모 모노레포(Turborepo) 환경에서의 린트 오케스트레이션]] - **Contradictions/Notes:** `lint-staged`는 전체 프로젝트를 검사하도록 설계된 도구(예: 전체 구조를 파악해야 하는 `ng lint`나 TypeScript의 `tsc --noEmit` 등)를 래핑하는 용도로는 적합하지 않으며, 단일 파일 단위로 처리 가능한 작업에만 사용해야 한다 [18-20]. 또한, 설정 시 여러 명령어가 동일한 파일을 동시에 수정하도록 구성하면 경쟁 조건(Race condition)이 발생하여 코드가 망가질 수 있으므로, 명령어 배열(Array)을 사용하여 순차적으로 실행되게 설정해야 한다 [21]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/Git Pre-commit 훅을 활용한 개발 워크플로우 자동화.md]] +- Raw Source: 00_Raw/2026-04-20/Git Pre-commit 훅을 활용한 개발 워크플로우 자동화.md --- diff --git a/01_Archive/2026-04-20/GitHub Actions.md b/01_Archive/2026-04-20/GitHub Actions.md index 7f22201e..4e5c33d6 100644 --- a/01_Archive/2026-04-20/GitHub Actions.md +++ b/01_Archive/2026-04-20/GitHub Actions.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-4CFD51 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - GitHub Actions" --- -# [[GitHub Actions]] +# [[GitHub Actions|GitHub Actions]] ## 📌 한 줄 통찰 (The Karpathy Summary) > GitHub Actions는 주로 리눅스(Linux) 이미지를 기본 환경으로 사용하는 CI/CD(지속적 통합/지속적 배포) 파이프라인 도구(CI Runner)입니다 [1]. 정적 애플리케이션 보안 테스트(SAST) 및 취약점 스캔 도구들과 연동되어 개발 워크플로우 내에서 보안 검사를 자동화하는 데 주요하게 활용됩니다 [2, 3]. 다만 제공된 소스에서는 타 솔루션의 연동 환경 또는 공급망 공격의 사례로만 제한적으로 언급되고 있어 소스에 관련 정보가 부족합니다. @@ -24,11 +24,11 @@ github_commit: "[P-Reinforce] Continuous Worker - GitHub Actions" - **정책 변화:** Design & Experience 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[CI/CD]], [[Static Application Security Testing (SAST)]], [[Supply Chain Attack]] -- **Projects/Contexts:** [[Snyk]], [[Endor Labs]] +- **Related Topics:** [[CI_CD|CI/CD]], [[Static Application Security Testing (SAST)|Static Application Security Testing (SAST)]], [[공급망 공격 (Supply Chain Attack)|Supply Chain Attack]] +- **Projects/Contexts:** Snyk, Endor Labs - **Contradictions/Notes:** 소스에 GitHub Actions 자체의 동작 원리, 문법, 고유 기능 등에 대한 세부 정보는 전무하며, 단순히 외부 보안 솔루션 연동을 위한 파이프라인 환경 및 공급망 공격 사례의 일부로만 등장합니다. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/GitHub Actions.md]] +- Raw Source: 00_Raw/2026-04-20/GitHub Actions.md --- diff --git a/01_Archive/2026-04-20/GitLab CI.md b/01_Archive/2026-04-20/GitLab CI.md index d7772e59..9c39d49f 100644 --- a/01_Archive/2026-04-20/GitLab CI.md +++ b/01_Archive/2026-04-20/GitLab CI.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-0DF208 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - GitLab CI" --- -# [[GitLab CI]] +# [[GitLab CI|GitLab CI]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 소스에 관련 정보가 부족합니다. 제공된 소스에서 GitLab CI 자체의 아키텍처나 구체적인 기능에 대한 직접적인 설명은 없으며, 주로 Snyk Code나 SonarQube와 같은 정적 애플리케이션 보안 테스트(SAST) 및 AI 코드 리뷰 도구들이 원활하게 연동되는 대표적인 CI/CD 파이프라인 플랫폼 중 하나로만 간략히 언급됩니다 [1, 2]. @@ -24,11 +24,11 @@ github_commit: "[P-Reinforce] Continuous Worker - GitLab CI" - **정책 변화:** AI 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[CI/CD 파이프라인]], [[SAST (정적 애플리케이션 보안 테스트)]] -- **Projects/Contexts:** [[Snyk Code 파이프라인 통합]], [[SonarQube 개발 워크플로우 연동]] +- **Related Topics:** [[CI_CD 파이프라인|CI/CD 파이프라인]], [[SAST (정적 애플리케이션 보안 테스트)|SAST (정적 애플리케이션 보안 테스트)]] +- **Projects/Contexts:** Snyk Code 파이프라인 통합, SonarQube 개발 워크플로우 연동 - **Contradictions/Notes:** 소스에 관련 정보가 부족합니다. GitLab CI만의 독자적인 기능이나 설정 방법에 대한 구체적인 내용은 소스에 존재하지 않으며, GitHub이나 Bitbucket 등과 함께 서드파티 보안/분석 도구가 지원하는 환경 목록으로만 등장합니다. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/GitLab CI.md]] +- Raw Source: 00_Raw/2026-04-20/GitLab CI.md --- diff --git a/01_Archive/2026-04-20/Global Augmentation.md b/01_Archive/2026-04-20/Global Augmentation.md index 90311745..d2256300 100644 --- a/01_Archive/2026-04-20/Global Augmentation.md +++ b/01_Archive/2026-04-20/Global Augmentation.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-2CC24D -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Global Augmentation" --- -# [[Global Augmentation]] +# [[Global Augmentation|Global Augmentation]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Global Augmentation" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Global Augmentation.md]] +- Raw Source: 00_Raw/2026-04-20/Global Augmentation.md --- diff --git a/01_Archive/2026-04-20/Global Network Positioning (GNP).md b/01_Archive/2026-04-20/Global Network Positioning (GNP).md index 51f1104c..ff991931 100644 --- a/01_Archive/2026-04-20/Global Network Positioning (GNP).md +++ b/01_Archive/2026-04-20/Global Network Positioning (GNP).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-D96374 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Global Network Positioning (GNP)" --- -# [[Global Network Positioning (GNP)]] +# [[Global Network Positioning (GNP)|Global Network Positioning (GNP)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > Global Network Positioning (GNP)은 인터넷 지연 시간(latency)을 다차원 기하학적 공간으로 모델링하여 확장 가능한 지연 시간 추정을 가능하게 하는 접근 방식입니다 [1]. 소수의 전용 '랜드마크(landmark)' 노드에 대한 측정값을 바탕으로 각 인터넷 노드에 해당 공간의 좌표를 부여합니다 [1]. 이를 통해 임의의 두 노드 간의 통신 지연 시간을 실제 측정 없이도 두 좌표 간의 유클리드 거리(Euclidean distance)로 효율적으로 근사할 수 있습니다 [1, 2]. @@ -24,11 +24,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Global Network Positioning (GN - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Latency Estimation]], [[Landmark Nodes]], [[Simplex-downhill Algorithm]] -- **Projects/Contexts:** [[Google Content Delivery Network (CDN)]] +- **Related Topics:** Latency Estimation, Landmark Nodes, Simplex-downhill Algorithm +- **Projects/Contexts:** Google Content Delivery Network (CDN) - **Contradictions/Notes:** 기존의 수많은 GNP 모델과 구현체들은 시스템 확장을 위해 호스트들의 능동적인 측정 참여를 필수적으로 요구했으나, 구글의 대규모 CDN 구현 사례는 랜드마크 측에서의 수동적 측정과 스케줄러 조합만으로도 능동적 참여의 단점(보안 및 과부하 위험)을 극복하고 시스템을 구축할 수 있음을 증명했습니다. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Global Network Positioning (GNP).md]] +- Raw Source: 00_Raw/2026-04-20/Global Network Positioning (GNP).md --- diff --git a/01_Archive/2026-04-20/Goal Misgeneralization (목표 오일반화).md b/01_Archive/2026-04-20/Goal Misgeneralization (목표 오일반화).md index ee53e944..e1ccb578 100644 --- a/01_Archive/2026-04-20/Goal Misgeneralization (목표 오일반화).md +++ b/01_Archive/2026-04-20/Goal Misgeneralization (목표 오일반화).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-85A1A5 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Goal Misgeneralization (목표 오일반화)" --- -# [[Goal Misgeneralization (목표 오일반화)]] +# [[Goal Misgeneralization (목표 오일반화)|Goal Misgeneralization (목표 오일반화)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Goal Misgeneralization (목표 ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Goal Misgeneralization (목표 오일반화).md]] +- Raw Source: 00_Raw/2026-04-20/Goal Misgeneralization (목표 오일반화).md --- diff --git a/01_Archive/2026-04-20/Google Chrome.md b/01_Archive/2026-04-20/Google Chrome.md index b893695a..94a10ceb 100644 --- a/01_Archive/2026-04-20/Google Chrome.md +++ b/01_Archive/2026-04-20/Google Chrome.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-A2356F -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Google Chrome" --- -# [[Google Chrome]] +# [[Google Chrome|Google Chrome]] ## 📌 한 줄 통찰 (The Karpathy Summary) > Google Chrome은 V8 JavaScript 엔진을 내장하여 웹 애플리케이션 및 JavaScript 코드를 실행하는 웹 브라우저입니다 [1, 2]. 메인 렌더러로 Blink를 사용하며, V8의 가비지 컬렉터(Orinoco)와 Blink의 내부 가비지 컬렉터(Oilpan)가 상호 협력하여 메모리를 관리합니다 [2]. 또한, Chrome DevTools와 같은 강력한 메모리 프로파일링 및 디버깅 도구를 내장하여 개발자가 메모리 누수를 진단하고 성능을 최적화할 수 있도록 지원하며 [3-5], 보안 측면에서는 V8 힙(Heap) 객체를 제한된 공간에 가두는 'V8 Memory Cage' 기술을 적용하고 있습니다 [6, 7]. @@ -30,11 +30,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Google Chrome" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** `[[V8 JavaScript Engine]]`, `[[Chrome DevTools]]`, `[[Garbage Collection]]`, `[[Pointer Compression]]`, `[[Blink]]` -- **Projects/Contexts:** `[[Orinoco]]`, `[[Oilpan]]`, `[[V8 Memory Cage]]` +- **Related Topics:** `[[V8 JavaScript Engine|V8 JavaScript Engine]]`, `[[Chrome DevTools|Chrome DevTools]]`, `[[Garbage Collection|Garbage Collection]]`, `[[Pointer Compression|Pointer Compression]]`, `[[Blink|Blink]]` +- **Projects/Contexts:** `[[Orinoco|Orinoco]]`, `[[Oilpan|Oilpan]]`, `[[V8 Memory Cage|V8 Memory Cage]]` - **Contradictions/Notes:** 가비지 컬렉션은 개발자가 명시적으로 메모리를 관리하지 않도록 편의를 제공하지만, 처리 과정에서 예측할 수 없는 중단(Pause)을 발생시킬 위험이 있습니다. 이를 극복하기 위해 Chrome과 V8은 메인 스레드를 멈추는 대신 점진적(Incremental), 동시성(Concurrent), 병렬(Parallel) 기법 및 유휴 시간(Idle-time) 활용 모델을 도입하여 성능 저하를 방지하고 있습니다 [25-28]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Google Chrome.md]] +- Raw Source: 00_Raw/2026-04-20/Google Chrome.md --- diff --git a/01_Archive/2026-04-20/Google Code Jam Dataset.md b/01_Archive/2026-04-20/Google Code Jam Dataset.md index 06c9f518..b4dd60e8 100644 --- a/01_Archive/2026-04-20/Google Code Jam Dataset.md +++ b/01_Archive/2026-04-20/Google Code Jam Dataset.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-A3BFE1 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Google Code Jam Dataset" --- -# [[Google Code Jam Dataset]] +# [[Google Code Jam Dataset|Google Code Jam Dataset]] ## 📌 한 줄 통찰 (The Karpathy Summary) > Google Code Jam Dataset은 구글의 코딩 대회인 Google Code Jam 참가자들이 작성한 소스 코드 해결책들을 모아놓은 데이터셋입니다 [1]. 대회 특성상 코딩 스타일, 가이드라인, 포맷팅에 대한 제약이 없기 때문에 개발자 각자의 고유한 프로그래밍 스타일이 그대로 반영되어 있습니다 [1]. 이러한 특성과 높은 정답(Ground Truth) 순도 덕분에 기계학습을 활용한 코드 스타일로미트리(Code Stylometry, 작성자 식별) 및 소프트웨어 포렌식 연구에서 가장 인기 있고 널리 사용되는 벤치마크 데이터셋 중 하나입니다 [1], [2], [3]. @@ -29,11 +29,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Google Code Jam Dataset" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Code Stylometry]], [[Authorship Attribution]], [[Abstract Syntax Tree (AST)]], [[Concrete Syntax Tree (CST)]] -- **Projects/Contexts:** [[Google Code Jam]], [[Machine Learning for Source Code]] +- **Related Topics:** [[Code Stylometry (코드 문체론)|Code Stylometry]], [[Authorship Attribution|Authorship Attribution]], [[Abstract Syntax Tree (AST)|Abstract Syntax Tree (AST)]], [[Concrete Syntax Tree (CST)|Concrete Syntax Tree (CST)]] +- **Projects/Contexts:** Google Code Jam, Machine Learning for Source Code - **Contradictions/Notes:** 소스에 따르면 Google Code Jam 데이터셋은 높은 순도와 통제된 환경을 제공하여 식별 모델 학습에 매우 적합하지만 [3], 실제 프로덕션 환경의 코드와는 달리 대회 특유의 반복적인 보일러플레이트 코드가 다수 포함되어 있어 실제 현실의 소프트웨어(In the wild)를 대상으로 할 때와는 차이가 발생할 수 있다는 점이 지적됩니다 [6]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Google Code Jam Dataset.md]] +- Raw Source: 00_Raw/2026-04-20/Google Code Jam Dataset.md --- diff --git a/01_Archive/2026-04-20/Google Lighthouse.md b/01_Archive/2026-04-20/Google Lighthouse.md index e103b535..d729c527 100644 --- a/01_Archive/2026-04-20/Google Lighthouse.md +++ b/01_Archive/2026-04-20/Google Lighthouse.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-88077C -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Google Lighthouse" --- -# [[Google Lighthouse]] +# [[Google Lighthouse|Google Lighthouse]] ## 📌 한 줄 통찰 (The Karpathy Summary) > Google Lighthouse는 웹사이트의 페이지 속도를 측정하고 성능 개선을 위한 권장 사항을 제공하는 구글의 무료 오픈 소스 도구입니다 [1], [2]. 주로 개발 단계에서 브라우저의 성능을 시뮬레이션하여 Synthetic Lab Data(합성 랩 데이터)를 수집하며, Chrome DevTools, 명령줄, 그리고 PageSpeed Insights를 통해 사용할 수 있습니다 [2], [3]. @@ -22,11 +22,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Google Lighthouse" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Chrome DevTools]], [[PageSpeed Insights]], [[Time to Interactive (TTI)]], [[Synthetic Lab Data]] -- **Projects/Contexts:** [[Web Performance Optimization]] +- **Related Topics:** [[Chrome DevTools|Chrome DevTools]], [[PageSpeed Insights|PageSpeed Insights]], [[Time to Interactive (TTI)|Time to Interactive (TTI)]], Synthetic Lab Data +- **Projects/Contexts:** [[Web Performance Optimization|Web Performance Optimization]] - **Contradictions/Notes:** 소스에 따르면 Lighthouse 점수의 단순 평균값은 일부 특이값(outlier)에 의해 왜곡될 수 있으므로 해석 시 주의가 필요합니다 [7]. 또한, Lighthouse의 스로틀링 시뮬레이션은 때때로 실제 브라우저 동작과 다르게 자원 로딩 영향을 평가하는 한계가 지적되어 최적화 작업이 요구되고 있습니다 [5]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Google Lighthouse.md]] +- Raw Source: 00_Raw/2026-04-20/Google Lighthouse.md --- diff --git a/01_Archive/2026-04-20/Grammar-based-Synthesis.md b/01_Archive/2026-04-20/Grammar-based-Synthesis.md index 5b0c9d69..53929224 100644 --- a/01_Archive/2026-04-20/Grammar-based-Synthesis.md +++ b/01_Archive/2026-04-20/Grammar-based-Synthesis.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-35F81E -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Grammar-based-Synthesis" --- -# [[Grammar-based-Synthesis]] +# [[Grammar-based-Synthesis|Grammar-based-Synthesis]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Grammar-based-Synthesis" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Grammar-based-Synthesis.md]] +- Raw Source: 00_Raw/2026-04-20/Grammar-based-Synthesis.md --- diff --git a/01_Archive/2026-04-20/Graph Theory in Level Design.md b/01_Archive/2026-04-20/Graph Theory in Level Design.md index c059d8cb..8b7d71c1 100644 --- a/01_Archive/2026-04-20/Graph Theory in Level Design.md +++ b/01_Archive/2026-04-20/Graph Theory in Level Design.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-7898CD -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Graph Theory in Level Design" --- -# [[Graph Theory in Level Design]] +# [[Graph Theory in Level Design|Graph Theory in Level Design]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Graph Theory in Level Design" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Graph Theory in Level Design.md]] +- Raw Source: 00_Raw/2026-04-20/Graph Theory in Level Design.md --- diff --git a/01_Archive/2026-04-20/Graph Theory.md b/01_Archive/2026-04-20/Graph Theory.md index 9f90c778..dc36c942 100644 --- a/01_Archive/2026-04-20/Graph Theory.md +++ b/01_Archive/2026-04-20/Graph Theory.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AI-055 -category: "[[10_Wiki/💡 Topics/Computational Theory & Math]]" +category: "10_Wiki/💡 Topics/Computational Theory & Math" confidence_score: 0.97 tags: [graph theory, network science, graph algorithm, relationship] last_reinforced: 2026-06-XX github_commit: "[P-Reinforce] Processed Graph Theory." --- -# [[Graph Theory]] (그래프 이론) +# [[Graph Theory|Graph Theory]] (그래프 이론) ## 📌 한 줄 통찰 (The Karpathy Summary) > 객체와 그들 사이의 관계를 노드(Vertex)와 엣지(Edge)로 모델링하여, 복잡한 네트워크 구조 내에서 최단 경로, 연결성, 커뮤니티 등을 수학적으로 분석하는 학문이다. @@ -27,7 +27,7 @@ github_commit: "[P-Reinforce] Processed Graph Theory." - **정책 변화:** Knowledge Graph (온톨로지)의 핵심 기반 이론이며, 단순한 관계를 넘어 '왜' 그런 관계가 성립했는지에 대한 근거(Provenance)까지 기록하는 방향으로 발전하고 있다. ## 🔗 지식 연결 (Graph) -- Parent: [[Knowledge Graphs]] -- Related: [[Network Science]] , [[Cybernetics]] , [[Complex Adaptive Systems]] -- Raw Source: [[00_Raw/Graph Theory.md]] +- Parent: [[Knowledge-Graphs|Knowledge Graphs]] +- Related: [[Network Science|Network Science]] , [[Cybernetics|Cybernetics]] , [[Complex Adaptive Systems|Complex Adaptive Systems]] +- Raw Source: 00_Raw/Graph Theory.md --- \ No newline at end of file diff --git a/01_Archive/2026-04-20/Graph-Coloring-Problem.md b/01_Archive/2026-04-20/Graph-Coloring-Problem.md index fc6b4b08..570631c7 100644 --- a/01_Archive/2026-04-20/Graph-Coloring-Problem.md +++ b/01_Archive/2026-04-20/Graph-Coloring-Problem.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-108994 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Graph-Coloring-Problem" --- -# [[Graph-Coloring-Problem]] +# [[Graph-Coloring-Problem|Graph-Coloring-Problem]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Graph-Coloring-Problem" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Graph-Coloring-Problem.md]] +- Raw Source: 00_Raw/2026-04-20/Graph-Coloring-Problem.md --- diff --git a/01_Archive/2026-04-20/Graph-Grammars.md b/01_Archive/2026-04-20/Graph-Grammars.md index b24f5988..d1671166 100644 --- a/01_Archive/2026-04-20/Graph-Grammars.md +++ b/01_Archive/2026-04-20/Graph-Grammars.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-492313 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Graph-Grammars" --- -# [[Graph-Grammars]] +# [[Graph-Grammars|Graph-Grammars]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Graph-Grammars" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Graph-Grammars.md]] +- Raw Source: 00_Raw/2026-04-20/Graph-Grammars.md --- diff --git a/01_Archive/2026-04-20/Graph-Theory.md b/01_Archive/2026-04-20/Graph-Theory.md index ff20564a..465b89ed 100644 --- a/01_Archive/2026-04-20/Graph-Theory.md +++ b/01_Archive/2026-04-20/Graph-Theory.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-961E9B -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Graph-Theory" --- -# [[Graph-Theory]] +# [[Graph-Theory|Graph-Theory]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Graph-Theory" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Graph-Theory.md]] +- Raw Source: 00_Raw/2026-04-20/Graph-Theory.md --- diff --git a/01_Archive/2026-04-20/GraphQL-Code-Generator.md b/01_Archive/2026-04-20/GraphQL-Code-Generator.md index 146b908a..35d82b64 100644 --- a/01_Archive/2026-04-20/GraphQL-Code-Generator.md +++ b/01_Archive/2026-04-20/GraphQL-Code-Generator.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-CFA98F -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - GraphQL-Code-Generator" --- -# [[GraphQL-Code-Generator]] +# [[GraphQL-Code-Generator|GraphQL-Code-Generator]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - GraphQL-Code-Generator" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/GraphQL-Code-Generator.md]] +- Raw Source: 00_Raw/2026-04-20/GraphQL-Code-Generator.md --- diff --git a/01_Archive/2026-04-20/GraphRAG (그래프 기반 검색 증강 생성).md b/01_Archive/2026-04-20/GraphRAG (그래프 기반 검색 증강 생성).md index 621244d5..fae9bdfc 100644 --- a/01_Archive/2026-04-20/GraphRAG (그래프 기반 검색 증강 생성).md +++ b/01_Archive/2026-04-20/GraphRAG (그래프 기반 검색 증강 생성).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-54AA1C -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - GraphRAG (그래프 기반 검색 증강 생성)" --- -# [[GraphRAG (그래프 기반 검색 증강 생성)]] +# [[GraphRAG (그래프 기반 검색 증강 생성)|GraphRAG (그래프 기반 검색 증강 생성)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - GraphRAG (그래프 기반 검 ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/GraphRAG (그래프 기반 검색 증강 생성).md]] +- Raw Source: 00_Raw/2026-04-20/GraphRAG (그래프 기반 검색 증강 생성).md --- diff --git a/01_Archive/2026-04-20/Grit.md b/01_Archive/2026-04-20/Grit.md index 9a0a4236..156f3a28 100644 --- a/01_Archive/2026-04-20/Grit.md +++ b/01_Archive/2026-04-20/Grit.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-53ED1B -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Grit" --- -# [[Grit]] +# [[Grit|Grit]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Grit" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Grit.md]] +- Raw Source: 00_Raw/2026-04-20/Grit.md --- diff --git a/01_Archive/2026-04-20/Grokking (그로킹 지연 일반화).md b/01_Archive/2026-04-20/Grokking (그로킹 지연 일반화).md index 271e4e31..4669acd2 100644 --- a/01_Archive/2026-04-20/Grokking (그로킹 지연 일반화).md +++ b/01_Archive/2026-04-20/Grokking (그로킹 지연 일반화).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-D1916C -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Grokking (그로킹 지연 일반화)" --- -# [[Grokking (그로킹 지연 일반화)]] +# [[Grokking (그로킹 지연 일반화)|Grokking (그로킹 지연 일반화)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Grokking (그로킹 지연 일 ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Grokking (그로킹, 지연 일반화).md]] +- Raw Source: 00_Raw/2026-04-20/Grokking (그로킹, 지연 일반화).md --- diff --git a/01_Archive/2026-04-20/Grokking (그로킹, 지연 일반화).md b/01_Archive/2026-04-20/Grokking (그로킹, 지연 일반화).md index d3a49ad7..32a3bc8f 100644 --- a/01_Archive/2026-04-20/Grokking (그로킹, 지연 일반화).md +++ b/01_Archive/2026-04-20/Grokking (그로킹, 지연 일반화).md @@ -1,4 +1,4 @@ -[[Grokking (그로킹, 지연 일반화)]] +[[Grokking (그로킹, 지연 일반화)|Grokking (그로킹, 지연 일반화)]] 📌 Brief Summary @@ -104,8 +104,8 @@ Nanda et al. (2023) - "Progress measures for grokking via mechanistic interpreta 🔗 Knowledge Connections -- **Related Topics:** [[Mechanistic Interpretability (기계적 해석 가능성)]], [[AI Safety (AI 안전)]], [[SFT (Supervised Fine-Tuning)]], [[강화학습 (Reinforcement Learning)]], [[In-Context Learning (ICL, 문맥 내 학습)]], [[LLM Alignment (LLM 정렬)]] -- **Projects/Contexts:** [[AI 신뢰성·투명성]] +- **Related Topics:** [[Mechanistic Interpretability (기계적 해석 가능성)|Mechanistic Interpretability (기계적 해석 가능성)]], [[AI Safety (AI 안전)|AI Safety (AI 안전)]], [[SFT (Supervised Fine-Tuning)|SFT (Supervised Fine-Tuning)]], [[강화학습 (Reinforcement Learning)|강화학습 (Reinforcement Learning)]], [[In-Context Learning (ICL, 문맥 내 학습)|In-Context Learning (ICL, 문맥 내 학습)]], [[LLM Alignment (LLM 정렬)|LLM Alignment (LLM 정렬)]] +- **Projects/Contexts:** AI 신뢰성·투명성 - **Contradictions/Notes:** - Grokking은 주로 소규모 모델·단순 태스크에서 확인 → 대규모 LLM에서 동일 현상이 발생하는지는 연구 중. - 매우 오랜 훈련이 필요하므로 실용적 LLM 훈련에서 의도적으로 Grokking을 기다리는 것은 비현실적. diff --git a/01_Archive/2026-04-20/Growth Mindset Intervention in Education.md b/01_Archive/2026-04-20/Growth Mindset Intervention in Education.md index 743c6681..1c78a74c 100644 --- a/01_Archive/2026-04-20/Growth Mindset Intervention in Education.md +++ b/01_Archive/2026-04-20/Growth Mindset Intervention in Education.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-D9A336 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Growth Mindset Intervention in Education" --- -# [[Growth Mindset Intervention in Education]] +# [[Growth Mindset Intervention in Education|Growth Mindset Intervention in Education]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Growth Mindset Intervention in ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Growth Mindset Intervention in Education.md]] +- Raw Source: 00_Raw/2026-04-20/Growth Mindset Intervention in Education.md --- diff --git a/01_Archive/2026-04-20/Growth-Mindset.md b/01_Archive/2026-04-20/Growth-Mindset.md index f863e494..65e5bd2e 100644 --- a/01_Archive/2026-04-20/Growth-Mindset.md +++ b/01_Archive/2026-04-20/Growth-Mindset.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-73BBE5 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Growth-Mindset" --- -# [[Growth-Mindset]] +# [[Growth-Mindset|Growth-Mindset]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Growth-Mindset" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Growth-Mindset.md]] +- Raw Source: 00_Raw/2026-04-20/Growth-Mindset.md --- diff --git a/01_Archive/2026-04-20/Guilty-Gear-Xrd-Rendering-Pipeline.md b/01_Archive/2026-04-20/Guilty-Gear-Xrd-Rendering-Pipeline.md index 4d46159e..8bbe2cf9 100644 --- a/01_Archive/2026-04-20/Guilty-Gear-Xrd-Rendering-Pipeline.md +++ b/01_Archive/2026-04-20/Guilty-Gear-Xrd-Rendering-Pipeline.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-44CE35 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Guilty-Gear-Xrd-Rendering-Pipeline" --- -# [[Guilty-Gear-Xrd-Rendering-Pipeline]] +# [[Guilty-Gear-Xrd-Rendering-Pipeline|Guilty-Gear-Xrd-Rendering-Pipeline]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Guilty-Gear-Xrd-Rendering-Pipe ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Guilty-Gear-Xrd-Rendering-Pipeline.md]] +- Raw Source: 00_Raw/2026-04-20/Guilty-Gear-Xrd-Rendering-Pipeline.md --- diff --git a/01_Archive/2026-04-20/HANDOVER.md b/01_Archive/2026-04-20/HANDOVER.md index 01d32516..feeb1d9e 100644 --- a/01_Archive/2026-04-20/HANDOVER.md +++ b/01_Archive/2026-04-20/HANDOVER.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-5DA4F4 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - HANDOVER" --- -# [[HANDOVER]] +# [[HANDOVER|HANDOVER]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - HANDOVER" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/HANDOVER.md]] +- Raw Source: 00_Raw/2026-04-20/HANDOVER.md --- diff --git a/01_Archive/2026-04-20/HBO Prestige Television.md b/01_Archive/2026-04-20/HBO Prestige Television.md index 4fb8cd81..e21b0378 100644 --- a/01_Archive/2026-04-20/HBO Prestige Television.md +++ b/01_Archive/2026-04-20/HBO Prestige Television.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-4ED001 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - HBO Prestige Television" --- -# [[HBO Prestige Television]] +# [[HBO Prestige Television|HBO Prestige Television]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - HBO Prestige Television" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/HBO Prestige Television.md]] +- Raw Source: 00_Raw/2026-04-20/HBO Prestige Television.md --- diff --git a/01_Archive/2026-04-20/HCI.md b/01_Archive/2026-04-20/HCI.md index 2d28557c..84cf7578 100644 --- a/01_Archive/2026-04-20/HCI.md +++ b/01_Archive/2026-04-20/HCI.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-DESIGN-003 -category: "[[10_Wiki/💡 Topics/Design]]" +category: "10_Wiki/💡 Topics/Design" confidence_score: 0.96 tags: [design, hci, ux, cognitive] last_reinforced: 2026-04-20 github_commit: "batch-reinforce-06" --- -# [[Human-Computer Interaction (HCI)]] +# [[Human-Computer Interaction (HCI)|Human-Computer Interaction (HCI)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 기계의 효율성과 인간의 인지를 잇는 접점에서, 가장 마찰 없는(Frictionless) 소통의 언어를 설계하는 학문. @@ -24,6 +24,6 @@ github_commit: "batch-reinforce-06" - **정책 변화:** 지식 구조(w2) 관점에서 AI 인터페이스 설계 가이드라인의 중추로 설정. ## 🔗 지식 연결 (Graph) -- **Parent:** [[10_Wiki/💡 Topics/Design]] -- **Related:** [[UX-Design]], [[Cognitive-Load]], [[Fitts-Law]] -- **Raw Source:** [[00_Raw/2026-04-20/Human-Computer-Interaction.md]] +- **Parent:** 10_Wiki/💡 Topics/Design +- **Related:** [[사용자 경험 디자인 (UX Design)|UX-Design]], [[Cognitive_Load|Cognitive-Load]], Fitts-Law +- **Raw Source:** 00_Raw/2026-04-20/Human-Computer-Interaction.md diff --git a/01_Archive/2026-04-20/HHH (Helpful Harmless Honest).md b/01_Archive/2026-04-20/HHH (Helpful Harmless Honest).md index 9ac6c971..516ef750 100644 --- a/01_Archive/2026-04-20/HHH (Helpful Harmless Honest).md +++ b/01_Archive/2026-04-20/HHH (Helpful Harmless Honest).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-11A9D4 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - HHH (Helpful Harmless Honest)" --- -# [[HHH (Helpful Harmless Honest)]] +# [[HHH (Helpful Harmless Honest)|HHH (Helpful Harmless Honest)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - HHH (Helpful Harmless Honest)" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/HHH (Helpful, Harmless, Honest).md]] +- Raw Source: 00_Raw/2026-04-20/HHH (Helpful, Harmless, Honest).md --- diff --git a/01_Archive/2026-04-20/HHH (Helpful, Harmless, Honest).md b/01_Archive/2026-04-20/HHH (Helpful, Harmless, Honest).md index e42c262b..7863bc12 100644 --- a/01_Archive/2026-04-20/HHH (Helpful, Harmless, Honest).md +++ b/01_Archive/2026-04-20/HHH (Helpful, Harmless, Honest).md @@ -1,4 +1,4 @@ -[[HHH (Helpful, Harmless, Honest, 도움됨·무해함·정직함)]] +HHH (Helpful, Harmless, Honest, 도움됨·무해함·정직함) 📌 Brief Summary @@ -97,8 +97,8 @@ Anthropic의 Claude 설계에서: 🔗 Knowledge Connections -- **Related Topics:** [[LLM Alignment (LLM 정렬)]], [[Constitutional AI (헌법 AI)]], [[Sycophancy (LLM 아첨 문제)]], [[RLHF (인간 피드백 기반 강화학습)]], [[Reward Hacking (보상 해킹)]], [[AI Safety (AI 안전)]], [[RLAIF (AI 피드백 기반 강화학습)]] -- **Projects/Contexts:** [[AI 신뢰성·투명성]] +- **Related Topics:** [[LLM Alignment (LLM 정렬)|LLM Alignment (LLM 정렬)]], [[Constitutional AI (헌법 AI)|Constitutional AI (헌법 AI)]], [[Sycophancy (LLM 아첨 문제)|Sycophancy (LLM 아첨 문제)]], [[RLHF (인간 피드백 기반 강화학습)|RLHF (인간 피드백 기반 강화학습)]], [[Reward Hacking (보상 해킹)|Reward Hacking (보상 해킹)]], [[AI Safety (AI 안전)|AI Safety (AI 안전)]], [[RLAIF (AI 피드백 기반 강화학습)|RLAIF (AI 피드백 기반 강화학습)]] +- **Projects/Contexts:** AI 신뢰성·투명성 - **Contradictions/Notes:** - HHH 세 원칙의 균형점은 맥락(사용자·문화·상황)에 따라 다름 → 절대적 공식 없음. - "도움됨"이 모든 상황에서 가장 낮은 우선순위를 갖는다는 설계는 → 일부 사용자에게 과도한 거부로 느껴짐 (Too Cautious 문제). diff --git a/01_Archive/2026-04-20/HMD(Head-Mounted Display) 기반 엑서게임 환경.md b/01_Archive/2026-04-20/HMD(Head-Mounted Display) 기반 엑서게임 환경.md index ab2366a0..736fbf06 100644 --- a/01_Archive/2026-04-20/HMD(Head-Mounted Display) 기반 엑서게임 환경.md +++ b/01_Archive/2026-04-20/HMD(Head-Mounted Display) 기반 엑서게임 환경.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-E05076 -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - HMD(Head-Mounted Display) 기반 엑서게임 환경" --- -# [[HMD(Head-Mounted Display) 기반 엑서게임 환경]] +# [[HMD(Head-Mounted Display) 기반 엑서게임 환경|HMD(Head-Mounted Display) 기반 엑서게임 환경]] ## 📌 한 줄 통찰 (The Karpathy Summary) > HMD(Head-Mounted Display) 기반 엑서게임 환경은 가상현실(VR) 기술을 활용하여 사용자의 신체적 운동과 게임 플레이를 결합한 몰입형 시스템입니다. 이 환경은 현실감 넘치는 3D 공간과 전방위적인 시야를 제공함으로써 사용자가 운동의 신체적 피로를 잊게 하고 지속적으로 운동에 참여할 수 있는 강력한 동기를 부여합니다 [1]. 그러나 높은 몰입감을 제공하는 대신, 신체 움직임과 시각적 자극의 불일치로 인해 화면 기반(Screen-based) 환경보다 VR 멀미(VR Sickness)나 시각적 피로를 유발할 가능성이 더 크다는 특징을 지닙니다 [2]. @@ -23,11 +23,11 @@ github_commit: "[P-Reinforce] Continuous Worker - HMD(Head-Mounted Display) 기 - **정책 변화:** Graphics & Performance 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[VR 멀미(VR Sickness)]], [[실재감(Presence)]], [[폭주-조절 불일치(Vergence-Accommodation Conflict)]] -- **Projects/Contexts:** [[Beat Saber]], [[가상현실(VR) 자전거 시뮬레이터]] +- **Related Topics:** [[VR 멀미 (VR Sickness)|VR 멀미(VR Sickness)]], [[실재감(Presence)|실재감(Presence)]], [[폭주-조절 불일치(Vergence-accommodation conflict)|폭주-조절 불일치(Vergence-Accommodation Conflict)]] +- **Projects/Contexts:** [[Beat Saber|Beat Saber]], [[가상현실(VR) 자전거 시뮬레이터|가상현실(VR) 자전거 시뮬레이터]] - **Contradictions/Notes:** HMD 기반 엑서게임은 기존 화면 기반 게임과 비교했을 때 사용자에게 더 높은 몰입감을 제공하여 운동 효과를 극대화할 수 있지만, 반대로 신체 움직임 증가와 시각적 자극으로 인해 VR 멀미의 유발 가능성을 높인다는 양면적인 모순을 가집니다 [2]. 노출 시간에 비례해 멀미 증상이 증가하지만 대부분 40분 이내에 자연 회복되므로 적절한 휴식과 함께 병행해야 합니다 [6, 9]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/HMD(Head-Mounted Display) 기반 엑서게임 환경.md]] +- Raw Source: 00_Raw/2026-04-20/HMD(Head-Mounted Display) 기반 엑서게임 환경.md --- diff --git a/01_Archive/2026-04-20/HNSW 알고리즘 (Hierarchical Navigable Small World).md b/01_Archive/2026-04-20/HNSW 알고리즘 (Hierarchical Navigable Small World).md index a12751dd..de0de0d6 100644 --- a/01_Archive/2026-04-20/HNSW 알고리즘 (Hierarchical Navigable Small World).md +++ b/01_Archive/2026-04-20/HNSW 알고리즘 (Hierarchical Navigable Small World).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-E7A769 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - HNSW 알고리즘 (Hierarchical Navigable Small World)" --- -# [[HNSW 알고리즘 (Hierarchical Navigable Small World)]] +# [[HNSW 알고리즘 (Hierarchical Navigable Small World)|HNSW 알고리즘 (Hierarchical Navigable Small World)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - HNSW 알고리즘 (Hierarchica ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/HNSW 알고리즘 (Hierarchical Navigable Small World).md]] +- Raw Source: 00_Raw/2026-04-20/HNSW 알고리즘 (Hierarchical Navigable Small World).md --- diff --git a/01_Archive/2026-04-20/HTC Vive Pro HMD.md b/01_Archive/2026-04-20/HTC Vive Pro HMD.md index 5ffa90e7..e68750bf 100644 --- a/01_Archive/2026-04-20/HTC Vive Pro HMD.md +++ b/01_Archive/2026-04-20/HTC Vive Pro HMD.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-7B2D1B -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - HTC Vive Pro HMD" --- -# [[HTC Vive Pro HMD]] +# [[HTC Vive Pro HMD|HTC Vive Pro HMD]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -22,11 +22,11 @@ github_commit: "[P-Reinforce] Continuous Worker - HTC Vive Pro HMD" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Head-Mounted Display (HMD)]], [[Virtual Reality (VR)]], [[VR Sickness]] -- **Projects/Contexts:** [[Exergaming With Beat Saber 연구 (VR 엑서게임 사후 효과 연구)]] +- **Related Topics:** Head-Mounted Display (HMD), Virtual Reality (VR), [[VR Sickness|VR Sickness]] +- **Projects/Contexts:** Exergaming With Beat Saber 연구 (VR 엑서게임 사후 효과 연구) - **Contradictions/Notes:** 기기 자체의 특성이나 스펙에 대한 세부 내용은 없고, 특정 연구의 실험 세팅용 장비로만 등장하므로 전체적인 맥락을 파악하기에는 소스에 관련 정보가 부족합니다. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/HTC Vive Pro HMD.md]] +- Raw Source: 00_Raw/2026-04-20/HTC Vive Pro HMD.md --- diff --git a/01_Archive/2026-04-20/HTML5 Canvas.md b/01_Archive/2026-04-20/HTML5 Canvas.md index 5e209e96..a36445b6 100644 --- a/01_Archive/2026-04-20/HTML5 Canvas.md +++ b/01_Archive/2026-04-20/HTML5 Canvas.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-6AA980 -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - HTML5 Canvas" --- -# [[HTML5 Canvas]] +# [[HTML5 Canvas|HTML5 Canvas]] ## 📌 한 줄 통찰 (The Karpathy Summary) > HTML5 Canvas는 웹 브라우저 내에서 3D 장면이나 그래픽 등 모든 그리기 콘텐츠(drawing contents)를 담는 HTML 요소입니다 [1]. 주로 자바스크립트를 통해 WebGL 또는 WebGPU 컨텍스트를 가져와 GPU에서 하드웨어 가속을 통해 직접 렌더링을 수행하는 대상 화면으로 사용됩니다 [1, 2]. 제공된 소스에서는 독립적인 주제라기보다는 WebGL 및 WebGPU 파이프라인이 그래픽을 출력하는 기본 바탕으로서 단편적으로 언급됩니다. @@ -20,11 +20,11 @@ github_commit: "[P-Reinforce] Continuous Worker - HTML5 Canvas" - **정책 변화:** Graphics & Performance 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[WebGL]], [[WebGPU]], [[GPU Rendering]] -- **Projects/Contexts:** [[3D Web-based HMI]], [[LearnWebGL]], [[Chrome DevTools Performance]] +- **Related Topics:** [[WebGL|WebGL]], [[WebGPU|WebGPU]], GPU Rendering +- **Projects/Contexts:** [[3D Web-based HMI|3D Web-based HMI]], LearnWebGL, Chrome DevTools Performance - **Contradictions/Notes:** 소스에 관련 정보가 부족합니다. 소스 데이터 내에서 HTML5 Canvas 자체의 2D API나 내부 동작 원리에 대한 깊이 있는 설명은 존재하지 않으며, WebGL 및 WebGPU 렌더링을 위한 HTML 요소로서의 역할만 제한적으로 다뤄지고 있습니다. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/HTML5 Canvas.md]] +- Raw Source: 00_Raw/2026-04-20/HTML5 Canvas.md --- diff --git a/01_Archive/2026-04-20/HUD-less Design Paradigms.md b/01_Archive/2026-04-20/HUD-less Design Paradigms.md index 656103c9..8ceddaed 100644 --- a/01_Archive/2026-04-20/HUD-less Design Paradigms.md +++ b/01_Archive/2026-04-20/HUD-less Design Paradigms.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-4CD4F1 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - HUD-less Design Paradigms" --- -# [[HUD-less Design Paradigms]] +# [[HUD-less Design Paradigms|HUD-less Design Paradigms]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - HUD-less Design Paradigms" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/HUD-less Design Paradigms.md]] +- Raw Source: 00_Raw/2026-04-20/HUD-less Design Paradigms.md --- diff --git a/01_Archive/2026-04-20/Haptic Feedback Technology.md b/01_Archive/2026-04-20/Haptic Feedback Technology.md index f6aca0b8..fe8c009d 100644 --- a/01_Archive/2026-04-20/Haptic Feedback Technology.md +++ b/01_Archive/2026-04-20/Haptic Feedback Technology.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-3637D3 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Haptic Feedback Technology" --- -# [[Haptic Feedback Technology]] +# [[Haptic Feedback Technology|Haptic Feedback Technology]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Haptic Feedback Technology" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Haptic Feedback Technology.md]] +- Raw Source: 00_Raw/2026-04-20/Haptic Feedback Technology.md --- diff --git a/01_Archive/2026-04-20/Hardware-Verification.md b/01_Archive/2026-04-20/Hardware-Verification.md index f76490c0..bf6b96cc 100644 --- a/01_Archive/2026-04-20/Hardware-Verification.md +++ b/01_Archive/2026-04-20/Hardware-Verification.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-70F7A4 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Hardware-Verification" --- -# [[Hardware-Verification]] +# [[Hardware-Verification|Hardware-Verification]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Hardware-Verification" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Hardware-Verification.md]] +- Raw Source: 00_Raw/2026-04-20/Hardware-Verification.md --- diff --git a/01_Archive/2026-04-20/Health Informatics (mHealth).md b/01_Archive/2026-04-20/Health Informatics (mHealth).md index 5a5e5da0..48095849 100644 --- a/01_Archive/2026-04-20/Health Informatics (mHealth).md +++ b/01_Archive/2026-04-20/Health Informatics (mHealth).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-A9629D -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Health Informatics (mHealth)" --- -# [[Health Informatics (mHealth)]] +# [[Health Informatics (mHealth)|Health Informatics (mHealth)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Health Informatics (mHealth)" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Health Informatics (mHealth).md]] +- Raw Source: 00_Raw/2026-04-20/Health Informatics (mHealth).md --- diff --git a/01_Archive/2026-04-20/Heap Snapshot(힙 스냅샷).md b/01_Archive/2026-04-20/Heap Snapshot(힙 스냅샷).md index a3fac0ac..785dc5da 100644 --- a/01_Archive/2026-04-20/Heap Snapshot(힙 스냅샷).md +++ b/01_Archive/2026-04-20/Heap Snapshot(힙 스냅샷).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-7C13B9 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Heap Snapshot(힙 스냅샷)" --- -# [[Heap Snapshot(힙 스냅샷)]] +# [[Heap Snapshot(힙 스냅샷)|Heap Snapshot(힙 스냅샷)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > **Heap Snapshot(힙 스냅샷)**은 특정 시점에 애플리케이션의 전체 객체 그래프와 힙 메모리 상태를 캡처한 데이터이다 [1, 2]. 주로 불필요하게 남아있는 객체의 유지 경로(Retaining path)를 식별하여 메모리 누수를 탐지하고 분석하기 위해 사용된다 [2, 3]. Chrome DevTools나 IntelliJ IDEA 같은 도구를 통해 생성할 수 있으며, 여러 스냅샷을 비교함으로써 메모리 할당 패턴과 가비지 컬렉션 이후의 잔존 메모리를 파악할 수 있다 [1, 4-6]. @@ -20,11 +20,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Heap Snapshot(힙 스냅샷)" - **정책 변화:** AI 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Memory Leak (메모리 누수)]], [[Garbage Collection (가비지 컬렉션)]], [[Retained Size vs Shallow Size]], [[Closure Variable Retention]] -- **Projects/Contexts:** [[Chrome DevTools Memory Panel]], [[V8 JavaScript Engine]], [[Node.js Production Monitoring]] +- **Related Topics:** [[Memory Leak(메모리 누수)|Memory Leak (메모리 누수)]], [[Garbage Collection(가비지 컬렉션)|Garbage Collection (가비지 컬렉션)]], Retained Size vs Shallow Size, Closure Variable Retention +- **Projects/Contexts:** [[Chrome DevTools Memory Panel|Chrome DevTools Memory Panel]], [[V8 JavaScript Engine|V8 JavaScript Engine]], [[Node.js Production Monitoring|Node.js Production Monitoring]] - **Contradictions/Notes:** 미니파이(Minified)된 프로덕션 코드에서는 식별자 이름이 변형되어 Retainer 체인을 알아보기 어렵기 때문에, DevTools에 소스 맵(Source maps)을 연결하거나 처음부터 함수에 명시적으로 이름을 지정(Named functions)하는 것이 분석에 훨씬 유리하다 [19, 25]. 또한, 스냅샷에서 메모리가 증가했다고 해서 모두 누수인 것은 아니며, 캐시나 Undo 히스토리처럼 의도적으로 메모리를 유지하는 "의도된 보존(Intentional retention)"과 실제 누수를 구별해야 한다 [19]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Heap Snapshot(힙 스냅샷).md]] +- Raw Source: 00_Raw/2026-04-20/Heap Snapshot(힙 스냅샷).md --- diff --git a/01_Archive/2026-04-20/Heap Snapshot.md b/01_Archive/2026-04-20/Heap Snapshot.md index 08d0abc2..a7fc73db 100644 --- a/01_Archive/2026-04-20/Heap Snapshot.md +++ b/01_Archive/2026-04-20/Heap Snapshot.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-E3AFF4 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Heap Snapshot" --- -# [[Heap Snapshot]] +# [[Heap Snapshot|Heap Snapshot]] ## 📌 한 줄 통찰 (The Karpathy Summary) > Heap Snapshot은 특정 시점에 V8 엔진 및 JavaScript 애플리케이션의 전체 메모리 상태(객체 그래프)를 캡처하는 도구 및 기법입니다 [1, 2]. 주로 JavaScript 객체와 관련된 DOM 노드의 메모리 분포를 보여주며, 가비지 컬렉션(GC) 루트에서 도달할 수 있는 객체들만 캡처합니다 [3, 4]. 개발자는 여러 스냅샷을 비교하고 참조 유지 체인을 추적하여 프로그램 내에서 발생하는 메모리 누수를 찾아내고 원인을 분석하는 데 이 도구를 필수적으로 사용합니다 [1, 3, 5]. @@ -32,11 +32,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Heap Snapshot" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Garbage Collection (GC)]], [[Memory Leak]], [[Shallow Size]], [[Retained Size]], [[Retainer Tree]] -- **Projects/Contexts:** [[Chrome DevTools]], [[Node.js]], [[V8 Engine]] +- **Related Topics:** [[Garbage Collection (GC)|Garbage Collection (GC)]], [[Memory Leak|Memory Leak]], Shallow Size, Retained Size, Retainer Tree +- **Projects/Contexts:** [[Chrome DevTools|Chrome DevTools]], [[Node.js|Node.js]], [[V8 Engine|V8 Engine]] - **Contradictions/Notes:** 모든 데이터가 JavaScript 힙 스냅샷에 기록되는 것은 아닙니다. 네이티브 코드를 실행하는 Getter를 통해 구현된 속성이나 숫자와 같은 비문자열(non-string) 값은 스냅샷에 캡처되지 않습니다 [11]. 또한, 원시 힙 데이터에는 수천 개의 V8 내부 객체가 포함되므로, 실제 애플리케이션의 메모리 누수를 찾으려면 "Constructor(생성자)" 필터를 사용하여 분석 대상을 좁혀야 합니다 [17]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Heap Snapshot.md]] +- Raw Source: 00_Raw/2026-04-20/Heap Snapshot.md --- diff --git a/01_Archive/2026-04-20/Hebbian Theory.md b/01_Archive/2026-04-20/Hebbian Theory.md index 947ba24b..50a132e3 100644 --- a/01_Archive/2026-04-20/Hebbian Theory.md +++ b/01_Archive/2026-04-20/Hebbian Theory.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-D8B3D2 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Hebbian Theory" --- -# [[Hebbian Theory]] +# [[Hebbian Theory|Hebbian Theory]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Hebbian Theory" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Hebbian Theory.md]] +- Raw Source: 00_Raw/2026-04-20/Hebbian Theory.md --- diff --git a/01_Archive/2026-04-20/Hello Games Development Lifecycle.md b/01_Archive/2026-04-20/Hello Games Development Lifecycle.md index 6af4ebc9..d99db3f1 100644 --- a/01_Archive/2026-04-20/Hello Games Development Lifecycle.md +++ b/01_Archive/2026-04-20/Hello Games Development Lifecycle.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-1D420B -category: "[[10_Wiki/💡 Topics/Software Architecture]]" +category: "10_Wiki/💡 Topics/Software Architecture" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Hello Games Development Lifecycle" --- -# [[Hello Games Development Lifecycle]] +# [[Hello Games Development Lifecycle|Hello Games Development Lifecycle]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Hello Games Development Lifecy ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Hello Games Development Lifecycle.md]] +- Raw Source: 00_Raw/2026-04-20/Hello Games Development Lifecycle.md --- diff --git a/01_Archive/2026-04-20/Hierarchical Reinforcement Learning (HRL).md b/01_Archive/2026-04-20/Hierarchical Reinforcement Learning (HRL).md index bc4fc619..8a6dfa62 100644 --- a/01_Archive/2026-04-20/Hierarchical Reinforcement Learning (HRL).md +++ b/01_Archive/2026-04-20/Hierarchical Reinforcement Learning (HRL).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-535DD0 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Hierarchical Reinforcement Learning (HRL)" --- -# [[Hierarchical Reinforcement Learning (HRL)]] +# [[Hierarchical Reinforcement Learning (HRL)|Hierarchical Reinforcement Learning (HRL)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Hierarchical Reinforcement Lea ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Hierarchical Reinforcement Learning (HRL).md]] +- Raw Source: 00_Raw/2026-04-20/Hierarchical Reinforcement Learning (HRL).md --- diff --git a/01_Archive/2026-04-20/High Resolution Time.md b/01_Archive/2026-04-20/High Resolution Time.md index c39e24c6..7ae8c8ea 100644 --- a/01_Archive/2026-04-20/High Resolution Time.md +++ b/01_Archive/2026-04-20/High Resolution Time.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-05BDE3 -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - High Resolution Time" --- -# [[High Resolution Time]] +# [[High Resolution Time|High Resolution Time]] ## 📌 한 줄 통찰 (The Karpathy Summary) > High Resolution Time(HR-time)은 웹 브라우저 환경에서 고정밀로 시간을 측정하기 위해 사용되는 사양(Spec) 및 메커니즘을 의미한다. 그러나 Spectre나 Meltdown 같은 타이밍 기반의 사이드 채널 공격을 방지하기 위해 이 사양은 `performance.now()`와 같은 측정 도구의 해상도를 의도적으로 제한(Coarsening)하고 있다. 최근 WebGPU의 타임스탬프 쿼리 기능 역시 이 HR-time 사양의 기준을 참조하여 보안과 성능 측정의 균형을 맞추고 있다. @@ -23,11 +23,11 @@ github_commit: "[P-Reinforce] Continuous Worker - High Resolution Time" - **정책 변화:** Graphics & Performance 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Spectre and Meltdown]], [[WebGPU Timestamp Queries]], [[performance.now()]] -- **Projects/Contexts:** [[High Resolution Time spec (#4175)]] +- **Related Topics:** [[Spectre and Meltdown|Spectre and Meltdown]], [[WebGPU Timestamp Queries|WebGPU Timestamp Queries]], performance.now() +- **Projects/Contexts:** High Resolution Time spec (#4175) - **Contradictions/Notes:** 소스 내에 특별한 모순은 없으나, High Resolution Time의 정밀도는 적용되는 보안 격리 환경(Isolated vs Non-isolated) 및 브라우저 엔진의 방어 메커니즘에 따라 5µs, 100µs, 1ms 등 상이하게 적용된다는 점을 유의해야 한다 [1, 2]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/High Resolution Time.md]] +- Raw Source: 00_Raw/2026-04-20/High Resolution Time.md --- diff --git a/01_Archive/2026-04-20/High-Cohesion-Low-Coupling.md b/01_Archive/2026-04-20/High-Cohesion-Low-Coupling.md index 862af89d..22de362a 100644 --- a/01_Archive/2026-04-20/High-Cohesion-Low-Coupling.md +++ b/01_Archive/2026-04-20/High-Cohesion-Low-Coupling.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-A143BE -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - High-Cohesion-Low-Coupling" --- -# [[High-Cohesion-Low-Coupling]] +# [[High-Cohesion-Low-Coupling|High-Cohesion-Low-Coupling]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - High-Cohesion-Low-Coupling" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/High-Cohesion-Low-Coupling.md]] +- Raw Source: 00_Raw/2026-04-20/High-Cohesion-Low-Coupling.md --- diff --git a/01_Archive/2026-04-20/High-Frequency Trading Models.md b/01_Archive/2026-04-20/High-Frequency Trading Models.md index 8b180f54..7f3efe5e 100644 --- a/01_Archive/2026-04-20/High-Frequency Trading Models.md +++ b/01_Archive/2026-04-20/High-Frequency Trading Models.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-6E0050 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - High-Frequency Trading Models" --- -# [[High-Frequency Trading Models]] +# [[High-Frequency Trading Models|High-Frequency Trading Models]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - High-Frequency Trading Models" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/High-Frequency Trading Models.md]] +- Raw Source: 00_Raw/2026-04-20/High-Frequency Trading Models.md --- diff --git a/01_Archive/2026-04-20/High-Performance Training Programs (Tier 1 Orgs).md b/01_Archive/2026-04-20/High-Performance Training Programs (Tier 1 Orgs).md index a9cb4f03..8e0f903e 100644 --- a/01_Archive/2026-04-20/High-Performance Training Programs (Tier 1 Orgs).md +++ b/01_Archive/2026-04-20/High-Performance Training Programs (Tier 1 Orgs).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-30B011 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - High-Performance Training Programs (Tier 1 Orgs)" --- -# [[High-Performance Training Programs (Tier 1 Orgs)]] +# [[High-Performance Training Programs (Tier 1 Orgs)|High-Performance Training Programs (Tier 1 Orgs)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - High-Performance Training Prog ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/High-Performance Training Programs (Tier 1 Orgs).md]] +- Raw Source: 00_Raw/2026-04-20/High-Performance Training Programs (Tier 1 Orgs).md --- diff --git a/01_Archive/2026-04-20/High-Performance-Coaching.md b/01_Archive/2026-04-20/High-Performance-Coaching.md index 6fc865e3..75127757 100644 --- a/01_Archive/2026-04-20/High-Performance-Coaching.md +++ b/01_Archive/2026-04-20/High-Performance-Coaching.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-FF879B -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - High-Performance-Coaching" --- -# [[High-Performance-Coaching]] +# [[High-Performance-Coaching|High-Performance-Coaching]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - High-Performance-Coaching" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/High-Performance-Coaching.md]] +- Raw Source: 00_Raw/2026-04-20/High-Performance-Coaching.md --- diff --git a/01_Archive/2026-04-20/High-Performance-Human-Factors.md b/01_Archive/2026-04-20/High-Performance-Human-Factors.md index 56eadf78..14adf3ca 100644 --- a/01_Archive/2026-04-20/High-Performance-Human-Factors.md +++ b/01_Archive/2026-04-20/High-Performance-Human-Factors.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-0DEE60 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - High-Performance-Human-Factors" --- -# [[High-Performance-Human-Factors]] +# [[High-Performance-Human-Factors|High-Performance-Human-Factors]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - High-Performance-Human-Factors ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/High-Performance-Human-Factors.md]] +- Raw Source: 00_Raw/2026-04-20/High-Performance-Human-Factors.md --- diff --git a/01_Archive/2026-04-20/High-Performance-Sports-Science.md b/01_Archive/2026-04-20/High-Performance-Sports-Science.md index ca4857da..8366710b 100644 --- a/01_Archive/2026-04-20/High-Performance-Sports-Science.md +++ b/01_Archive/2026-04-20/High-Performance-Sports-Science.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-D74500 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - High-Performance-Sports-Science" --- -# [[High-Performance-Sports-Science]] +# [[High-Performance-Sports-Science|High-Performance-Sports-Science]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - High-Performance-Sports-Scienc ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/High-Performance-Sports-Science.md]] +- Raw Source: 00_Raw/2026-04-20/High-Performance-Sports-Science.md --- diff --git a/01_Archive/2026-04-20/Homeostasis.md b/01_Archive/2026-04-20/Homeostasis.md index b06eddc9..72cb4780 100644 --- a/01_Archive/2026-04-20/Homeostasis.md +++ b/01_Archive/2026-04-20/Homeostasis.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-D75E8D -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Homeostasis" --- -# [[Homeostasis]] +# [[Homeostasis|Homeostasis]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Homeostasis" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Homeostasis.md]] +- Raw Source: 00_Raw/2026-04-20/Homeostasis.md --- diff --git a/01_Archive/2026-04-20/Human-Centered Design.md b/01_Archive/2026-04-20/Human-Centered Design.md index e34e93b8..c90ffaaa 100644 --- a/01_Archive/2026-04-20/Human-Centered Design.md +++ b/01_Archive/2026-04-20/Human-Centered Design.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-AFA55D -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Human-Centered Design" --- -# [[Human-Centered Design]] +# [[Human-Centered Design|Human-Centered Design]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Human-Centered Design" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Human-Centered Design.md]] +- Raw Source: 00_Raw/2026-04-20/Human-Centered Design.md --- diff --git a/01_Archive/2026-04-20/Human-Computer Interaction (HCI).md b/01_Archive/2026-04-20/Human-Computer Interaction (HCI).md index 7ab258ea..eec888b4 100644 --- a/01_Archive/2026-04-20/Human-Computer Interaction (HCI).md +++ b/01_Archive/2026-04-20/Human-Computer Interaction (HCI).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-5F4DD2 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Human-Computer Interaction (HCI)" --- -# [[Human-Computer Interaction (HCI)]] +# [[Human-Computer Interaction (HCI)|Human-Computer Interaction (HCI)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Human-Computer Interaction (HC ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Human-Computer Interaction (HCI).md]] +- Raw Source: 00_Raw/2026-04-20/Human-Computer Interaction (HCI).md --- diff --git a/01_Archive/2026-04-20/Human-Computer-Interaction (HCI).md b/01_Archive/2026-04-20/Human-Computer-Interaction (HCI).md index 8f9890df..ad7c91cd 100644 --- a/01_Archive/2026-04-20/Human-Computer-Interaction (HCI).md +++ b/01_Archive/2026-04-20/Human-Computer-Interaction (HCI).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-AFBB70 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Human-Computer-Interaction (HCI)" --- -# [[Human-Computer-Interaction (HCI)]] +# [[Human-Computer-Interaction (HCI)|Human-Computer-Interaction (HCI)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Human-Computer-Interaction (HC ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Human-Computer-Interaction (HCI).md]] +- Raw Source: 00_Raw/2026-04-20/Human-Computer-Interaction (HCI).md --- diff --git a/01_Archive/2026-04-20/Human-Computer-Interaction-HCI.md b/01_Archive/2026-04-20/Human-Computer-Interaction-HCI.md index d5183dd8..6b9bed2d 100644 --- a/01_Archive/2026-04-20/Human-Computer-Interaction-HCI.md +++ b/01_Archive/2026-04-20/Human-Computer-Interaction-HCI.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-7D2F0C -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Human-Computer-Interaction-HCI" --- -# [[Human-Computer-Interaction-HCI]] +# [[Human-Computer-Interaction-HCI|Human-Computer-Interaction-HCI]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Human-Computer-Interaction-HCI ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Human-Computer-Interaction-HCI.md]] +- Raw Source: 00_Raw/2026-04-20/Human-Computer-Interaction-HCI.md --- diff --git a/01_Archive/2026-04-20/Human-Computer-Interaction.md b/01_Archive/2026-04-20/Human-Computer-Interaction.md index 0652dc80..a29c9bc1 100644 --- a/01_Archive/2026-04-20/Human-Computer-Interaction.md +++ b/01_Archive/2026-04-20/Human-Computer-Interaction.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-3ED48D -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Human-Computer-Interaction" --- -# [[Human-Computer-Interaction]] +# [[Human-Computer-Interaction|Human-Computer-Interaction]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Human-Computer-Interaction" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Human-Computer-Interaction.md]] +- Raw Source: 00_Raw/2026-04-20/Human-Computer-Interaction.md --- diff --git a/01_Archive/2026-04-20/Human-Machine Interface (HMI) Design.md b/01_Archive/2026-04-20/Human-Machine Interface (HMI) Design.md index a1b439e4..fbb41b7e 100644 --- a/01_Archive/2026-04-20/Human-Machine Interface (HMI) Design.md +++ b/01_Archive/2026-04-20/Human-Machine Interface (HMI) Design.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-F753F2 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Human-Machine Interface (HMI) Design" --- -# [[Human-Machine Interface (HMI) Design]] +# [[Human-Machine Interface (HMI) Design|Human-Machine Interface (HMI) Design]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Human-Machine Interface (HMI) ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Human-Machine Interface (HMI) Design.md]] +- Raw Source: 00_Raw/2026-04-20/Human-Machine Interface (HMI) Design.md --- diff --git a/01_Archive/2026-04-20/Human-Robot Interaction (HRI).md b/01_Archive/2026-04-20/Human-Robot Interaction (HRI).md index 5ce0173f..c3534e83 100644 --- a/01_Archive/2026-04-20/Human-Robot Interaction (HRI).md +++ b/01_Archive/2026-04-20/Human-Robot Interaction (HRI).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-695BBA -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Human-Robot Interaction (HRI)" --- -# [[Human-Robot Interaction (HRI)]] +# [[Human-Robot Interaction (HRI)|Human-Robot Interaction (HRI)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Human-Robot Interaction (HRI)" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Human-Robot Interaction (HRI).md]] +- Raw Source: 00_Raw/2026-04-20/Human-Robot Interaction (HRI).md --- diff --git a/01_Archive/2026-04-20/Human-Robot-Interaction.md b/01_Archive/2026-04-20/Human-Robot-Interaction.md index 11867614..5678ee0b 100644 --- a/01_Archive/2026-04-20/Human-Robot-Interaction.md +++ b/01_Archive/2026-04-20/Human-Robot-Interaction.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-419DF4 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Human-Robot-Interaction" --- -# [[Human-Robot-Interaction]] +# [[Human-Robot-Interaction|Human-Robot-Interaction]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Human-Robot-Interaction" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Human-Robot-Interaction.md]] +- Raw Source: 00_Raw/2026-04-20/Human-Robot-Interaction.md --- diff --git a/01_Archive/2026-04-20/Husky lint-staged.md b/01_Archive/2026-04-20/Husky lint-staged.md index e09350fe..883a2bb9 100644 --- a/01_Archive/2026-04-20/Husky lint-staged.md +++ b/01_Archive/2026-04-20/Husky lint-staged.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-6F1BCF -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Husky lint-staged" --- -# [[Husky lint-staged]] +# [[Husky lint-staged|Husky lint-staged]] ## 📌 한 줄 통찰 (The Karpathy Summary) > Husky와 lint-staged는 개발자가 코드를 Git 저장소에 커밋하기 전에 코드의 품질과 스타일을 자동으로 검사하고 수정할 수 있도록 돕는 도구입니다 [1, 2]. Husky는 Git 훅(Git hooks)을 버전 관리 시스템에 포함시켜 팀원 전체가 쉽게 공유하고 관리할 수 있도록 해주는 훅 관리 레이어입니다 [3, 4]. lint-staged는 전체 코드베이스가 아닌 커밋을 위해 스테이징된(staged) 파일에 대해서만 특정 명령어(Linter, Formatter 등)를 실행하도록 오케스트레이션하여 검사 속도와 효율성을 높여줍니다 [3, 4]. 이 두 도구를 결합하여 사용하면 잘못된 코드가 저장소에 병합되는 것을 사전에 방지하고 일관된 코드 퀄리티를 효율적으로 유지할 수 있습니다 [5]. @@ -20,11 +20,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Husky lint-staged" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Git Hooks]], [[ESLint]], [[Prettier]], [[Continuous Integration (CI)]] -- **Projects/Contexts:** [[Monorepo(Turborepo 등) 환경의 린트 관리]], [[프론트엔드 및 Node.js 개발 워크플로우]] +- **Related Topics:** [[Git Hooks|Git Hooks]], [[ESLint|ESLint]], [[Prettier|Prettier]], [[Continuous Integration (CI)|Continuous Integration (CI)]] +- **Projects/Contexts:** [[Monorepo(Turborepo 등) 환경의 린트 관리|Monorepo(Turborepo 등) 환경의 린트 관리]], [[프론트엔드 및 Node.js 개발 워크플로우|프론트엔드 및 Node.js 개발 워크플로우]] - **Contradictions/Notes:** 소스에 따르면 lint-staged의 자체적인 기능을 사용할 때 스크립트 명령어 내에서 수동으로 `git add`를 추가해서는 안 됩니다. lint-staged가 충돌(race condition)을 방지하기 위해 파일의 자동 스테이징을 내부적으로 직접 처리하기 때문입니다 [13, 16]. 또한 lint-staged는 파일 필터링 역할을 하므로, `tsc`와 같이 전체 프로젝트 문맥이 필요한 도구를 적용할 때는 단순히 명령어를 추가하는 것이 아니라 파일 인자가 무시되도록 별도의 함수 설정을 사용해야 하는 등 도구의 성격에 맞게 분리 적용할 필요가 있습니다 [16, 20, 21]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/Husky & lint-staged.md]] +- Raw Source: 00_Raw/2026-04-20/Husky & lint-staged.md --- diff --git a/01_Archive/2026-04-20/Husky & lint-staged.md b/01_Archive/2026-04-20/Husky & lint-staged.md index 568fbc80..6b937bbb 100644 --- a/01_Archive/2026-04-20/Husky & lint-staged.md +++ b/01_Archive/2026-04-20/Husky & lint-staged.md @@ -1,4 +1,4 @@ -# [[Husky & lint-staged]] +# [[Husky & lint-staged|Husky & lint-staged]] ## 📌 Brief Summary Husky와 lint-staged는 개발자가 코드를 Git 저장소에 커밋하기 전에 코드의 품질과 스타일을 자동으로 검사하고 수정할 수 있도록 돕는 도구입니다 [1, 2]. Husky는 Git 훅(Git hooks)을 버전 관리 시스템에 포함시켜 팀원 전체가 쉽게 공유하고 관리할 수 있도록 해주는 훅 관리 레이어입니다 [3, 4]. lint-staged는 전체 코드베이스가 아닌 커밋을 위해 스테이징된(staged) 파일에 대해서만 특정 명령어(Linter, Formatter 등)를 실행하도록 오케스트레이션하여 검사 속도와 효율성을 높여줍니다 [3, 4]. 이 두 도구를 결합하여 사용하면 잘못된 코드가 저장소에 병합되는 것을 사전에 방지하고 일관된 코드 퀄리티를 효율적으로 유지할 수 있습니다 [5]. @@ -10,8 +10,8 @@ Husky와 lint-staged는 개발자가 코드를 Git 저장소에 커밋하기 전 * **적용 한계와 CI의 필요성:** 이 두 도구는 개발자 환경에서 빠르고 안전하게 문제를 잡아내는 데 특화되어 있으나, 클라이언트 측 Git 훅은 개발자가 `--no-verify` 옵션을 사용하거나 `HUSKY=0` 환경 변수를 설정하는 방식으로 쉽게 우회할 수 있습니다 [14-16]. 따라서 Husky와 lint-staged는 로컬에서의 편의성과 피드백 속도를 높여주는 역할일 뿐이며, 최종적인 코드 품질의 강제와 검증은 반드시 CI(Continuous Integration) 파이프라인에서 이루어져야 합니다 [14, 17-19]. ## 🔗 Knowledge Connections -- **Related Topics:** [[Git Hooks]], [[ESLint]], [[Prettier]], [[Continuous Integration (CI)]] -- **Projects/Contexts:** [[Monorepo(Turborepo 등) 환경의 린트 관리]], [[프론트엔드 및 Node.js 개발 워크플로우]] +- **Related Topics:** [[Git Hooks|Git Hooks]], [[ESLint|ESLint]], [[Prettier|Prettier]], [[Continuous Integration (CI)|Continuous Integration (CI)]] +- **Projects/Contexts:** [[Monorepo(Turborepo 등) 환경의 린트 관리|Monorepo(Turborepo 등) 환경의 린트 관리]], [[프론트엔드 및 Node.js 개발 워크플로우|프론트엔드 및 Node.js 개발 워크플로우]] - **Contradictions/Notes:** 소스에 따르면 lint-staged의 자체적인 기능을 사용할 때 스크립트 명령어 내에서 수동으로 `git add`를 추가해서는 안 됩니다. lint-staged가 충돌(race condition)을 방지하기 위해 파일의 자동 스테이징을 내부적으로 직접 처리하기 때문입니다 [13, 16]. 또한 lint-staged는 파일 필터링 역할을 하므로, `tsc`와 같이 전체 프로젝트 문맥이 필요한 도구를 적용할 때는 단순히 명령어를 추가하는 것이 아니라 파일 인자가 무시되도록 별도의 함수 설정을 사용해야 하는 등 도구의 성격에 맞게 분리 적용할 필요가 있습니다 [16, 20, 21]. --- diff --git a/01_Archive/2026-04-20/Husky.md b/01_Archive/2026-04-20/Husky.md index de6b7009..09d790dd 100644 --- a/01_Archive/2026-04-20/Husky.md +++ b/01_Archive/2026-04-20/Husky.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-9068BA -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Husky" --- -# [[Husky]] +# [[Husky|Husky]] ## 📌 한 줄 통찰 (The Karpathy Summary) > Husky는 개발 프로젝트에서 Git 훅(Git hooks)을 쉽게 설정, 관리 및 팀원들과 공유할 수 있도록 지원하는 소프트웨어 도구입니다 [1]. 기본적으로 버전 관리 대상이 아닌 Git 훅의 한계를 극복하여 `.husky/`와 같은 추적 가능한 디렉토리를 통해 훅 스크립트를 관리하게 해줍니다 [1, 2]. 주로 `lint-staged`와 결합하여 커밋이나 푸시 전에 자동으로 코드 린팅(linting) 및 포맷팅을 수행하여 코드 품질을 강제하는 데 사용됩니다 [3, 4]. @@ -26,11 +26,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Husky" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Git Hooks]], [[lint-staged]], [[ESLint]], [[Prettier]] -- **Projects/Contexts:** [[CI/CD Pipeline]], [[Monorepo]], [[Submodules]] +- **Related Topics:** [[Git Hooks|Git Hooks]], [[lint-staged|lint-staged]], [[ESLint|ESLint]], [[Prettier|Prettier]] +- **Projects/Contexts:** [[CI-CD Pipeline (지속적 통합 및 배포)|CI/CD Pipeline]], [[Monorepo|Monorepo]], [[Submodules|Submodules]] - **Contradictions/Notes:** 소스에 따르면, 많은 개발자가 Husky와 `lint-staged`를 혼동하여 하나의 덩어리로 생각하곤 합니다. 하지만 두 도구는 명확히 구분되어야 합니다. Husky는 단순히 Git의 기본 훅을 관리하고 연결하는 '배선(hook wiring)' 역할을 할 뿐 작업 실행기(task runner)가 아니며, 실제 변경된 파일 단위로 작업을 오케스트레이션 하는 것은 `lint-staged`의 역할입니다 [2, 4, 16]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/Husky.md]] +- Raw Source: 00_Raw/2026-04-20/Husky.md --- diff --git a/01_Archive/2026-04-20/Hyperinflation in Closed-Loop Systems.md b/01_Archive/2026-04-20/Hyperinflation in Closed-Loop Systems.md index 75b2932d..c3288a23 100644 --- a/01_Archive/2026-04-20/Hyperinflation in Closed-Loop Systems.md +++ b/01_Archive/2026-04-20/Hyperinflation in Closed-Loop Systems.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-01FD40 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Hyperinflation in Closed-Loop Systems" --- -# [[Hyperinflation in Closed-Loop Systems]] +# [[Hyperinflation in Closed-Loop Systems|Hyperinflation in Closed-Loop Systems]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Hyperinflation in Closed-Loop ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Hyperinflation in Closed-Loop Systems.md]] +- Raw Source: 00_Raw/2026-04-20/Hyperinflation in Closed-Loop Systems.md --- diff --git a/01_Archive/2026-04-20/Hypertextuality.md b/01_Archive/2026-04-20/Hypertextuality.md index 9ce325ee..6e5a2e2d 100644 --- a/01_Archive/2026-04-20/Hypertextuality.md +++ b/01_Archive/2026-04-20/Hypertextuality.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-B134AC -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Hypertextuality" --- -# [[Hypertextuality]] +# [[Hypertextuality|Hypertextuality]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Hypertextuality" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Hypertextuality.md]] +- Raw Source: 00_Raw/2026-04-20/Hypertextuality.md --- diff --git a/01_Archive/2026-04-20/IBM 가비지 컬렉션.md b/01_Archive/2026-04-20/IBM 가비지 컬렉션.md index ab62f3a1..7ace6a17 100644 --- a/01_Archive/2026-04-20/IBM 가비지 컬렉션.md +++ b/01_Archive/2026-04-20/IBM 가비지 컬렉션.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-A6562D -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - IBM 가비지 컬렉션" --- -# [[IBM 가비지 컬렉션]] +# [[IBM 가비지 컬렉션|IBM 가비지 컬렉션]] ## 📌 한 줄 통찰 (The Karpathy Summary) > IBM의 가비지 컬렉션(GC)은 애플리케이션의 메모리 부족을 방지하기 위해 더 이상 필요하지 않은 Java 힙의 객체를 회수하는 자동화된 프로세스입니다 [1]. 전체 GC 과정은 일반적으로 도달 가능한 객체를 식별하는 마크(Mark), 도달할 수 없는 객체를 정리하는 스위프(Sweep), 힙의 단편화를 해결하는 압축(Compact)의 세 단계로 나뉩니다 [1]. GC 작업 중에는 애플리케이션 실행이 일시 중지되는 'stop-the-world (STW)' 현상이 발생할 수 있으며, 시스템은 애플리케이션 중단을 최소화하기 위해 동시(Concurrent) 또는 점진적(Incremental) 처리 기법 및 다양한 정책을 활용합니다 [1-3]. @@ -32,11 +32,11 @@ github_commit: "[P-Reinforce] Continuous Worker - IBM 가비지 컬렉션" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[GC Policies (gencon, optavgpause, balanced)]], [[Stop-the-world (STW) Pause]], [[Mark, Sweep, and Compact Operations]] -- **Projects/Contexts:** [[Eclipse OpenJ9™]], [[Java Object Heap]] +- **Related Topics:** GC Policies (gencon, optavgpause, balanced), Stop-the-world (STW) Pause, Mark, Sweep, and Compact Operations +- **Projects/Contexts:** Eclipse OpenJ9™, Java Object Heap - **Contradictions/Notes:** 애플리케이션 성능 최적화를 위해 동시 마크(Concurrent mark) 방식을 사용하면 STW 일시 중지 시간은 줄일 수 있지만, 쓰기 장벽(Write barrier) 작동으로 인한 추가 CPU 소비와 힙 락 할당 중 객체 추적에 따른 부하가 발생하는 트레이드오프(단점)가 존재합니다 [3]. 또한, 개발자가 `System.gc()`를 직접 호출하거나 finalizer를 이용해 GC를 통제하려 하면 오히려 애플리케이션 성능을 크게 저하시킬 수 있습니다 [5]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/IBM 가비지 컬렉션.md]] +- Raw Source: 00_Raw/2026-04-20/IBM 가비지 컬렉션.md --- diff --git a/01_Archive/2026-04-20/IEEE P3652.1.md b/01_Archive/2026-04-20/IEEE P3652.1.md index 447bc211..f0d977d0 100644 --- a/01_Archive/2026-04-20/IEEE P3652.1.md +++ b/01_Archive/2026-04-20/IEEE P3652.1.md @@ -1,4 +1,4 @@ -[[IEEE P3652.1]] +[[IEEE P3652.1|IEEE P3652.1]] 📌 Brief Summary IEEE P3652.1 is a developing technical standard within the IEEE Standards Association (IEEE-SA) focused on establishing a framework for the interoperability and standardized communication of "Generative AI" (GenAI) models and their associated metadata. It aims to define common protocols, data formats, and semantic structures to ensure that large language models (LLMs) and other generative architectures can interact reliably across heterogeneous platforms and ecosystems. @@ -14,8 +14,8 @@ The standard is part of a broader effort by the IEEE to address the lack of stan The scope of P3652.1 extends beyond mere data exchange; it seeks to create a "common language" for the lifecycle management of generative models, from initial training documentation to real-time inference monitoring and version control. 🔗 Knowledge Connections -* Related Topics: [[IEEE P3652 (Standard for Generative AI Interoperability)]], [[AI Model Provenance]], [[Machine Learning Metadata Standards]], [[LLM Evaluation Frameworks]] -* Projects/Contexts: [[IEEE Standards Association (IEEE-SA) AI Initiative]], [[Responsible AI Development]], [[MLOps (Machine Learning Operations)]] +* Related Topics: IEEE P3652 (Standard for Generative AI Interoperability), AI Model Provenance, Machine Learning Metadata Standards, LLM Evaluation Frameworks +* Projects/Contexts: IEEE Standards Association (IEEE-SA) AI Initiative, Responsible AI Development, MLOps (Machine Learning Operations) * Contradictions/Notes: The standard is currently in the development phase; therefore, specific technical specifications are subject to change as the working group reaches consensus. There is an ongoing debate regarding how much "proprietary" model architecture information should be standardized versus maintaining intellectual property protections for developers. Last updated: 2026-04-16 \ No newline at end of file diff --git a/01_Archive/2026-04-20/IEEE P36521.md b/01_Archive/2026-04-20/IEEE P36521.md index 7ccfc2bc..a5ebf4e7 100644 --- a/01_Archive/2026-04-20/IEEE P36521.md +++ b/01_Archive/2026-04-20/IEEE P36521.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-5A9960 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - IEEE P36521" --- -# [[IEEE P36521]] +# [[IEEE P36521|IEEE P36521]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - IEEE P36521" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/IEEE P3652.1.md]] +- Raw Source: 00_Raw/2026-04-20/IEEE P3652.1.md --- diff --git a/01_Archive/2026-04-20/IFC.js (Fragment).md b/01_Archive/2026-04-20/IFC.js (Fragment).md index ba6ae3b8..c4dae129 100644 --- a/01_Archive/2026-04-20/IFC.js (Fragment).md +++ b/01_Archive/2026-04-20/IFC.js (Fragment).md @@ -1,4 +1,4 @@ -# [[IFC.js (Fragment)]] +# [[IFC.js (Fragment)|IFC.js (Fragment)]] ## 📌 Brief Summary Fragment는 대규모 3D 기하학적 환경을 효율적으로 렌더링하기 위해 IFC.js 개발자들이 고안한 하이브리드 최적화 시스템이다 [1, 2]. 이 시스템은 단일 인터페이스 내에서 로우 폴리(low-poly) 고유 객체를 위한 지오메트리 병합과 하이 폴리(high-poly) 반복 객체를 위한 인스턴싱의 장점을 결합한다 [2]. 이를 통해 메모리 소비와 드로우 콜(Draw call) 횟수 간의 최적의 균형을 달성하면서 개별 객체의 빠른 검색 및 조작 기능을 제공하는 것을 목표로 한다 [1, 3]. @@ -19,8 +19,8 @@ Fragment는 대규모 3D 기하학적 환경을 효율적으로 렌더링하기 초기 프로토타입 구현 결과, 1,000개의 의자와 4개의 벽으로 구성된 씬을 단 3번의 드로우 콜(선택용 드로우 콜 제외)과 10MB 미만의 메모리만으로 렌더링하는 데 성공했다 [6]. 또한 100MB 이상의 대형 IFC 모델을 모바일 기기에서도 Autodesk Forge에 필적하는 속도로 빠르게 로드하는 훌륭한 성능을 보여주었다 [8]. ## 🔗 Knowledge Connections -- **Related Topics:** [[BufferGeometry]], [[InstancedMesh]], [[Draw Call]] -- **Projects/Contexts:** [[IFC.js]], [[Three.js]] +- **Related Topics:** [[BufferGeometry|BufferGeometry]], [[InstancedMesh|InstancedMesh]], [[Draw Call|Draw Call]] +- **Projects/Contexts:** [[IFC.js|IFC.js]], [[Three.js|Three.js]] - **Contradictions/Notes:** 소스에 따르면, Fragment와 같은 자체적인 최적화 시스템 구축 외에도 대규모 환경 최적화를 위해 다중 그리기(Multidrawing), LOD(Level of Detail), 오클루전 컬링(Occlusion Culling) 등의 추가적인 방법론도 함께 검토되었다 [2]. --- diff --git a/01_Archive/2026-04-20/IFC.js.md b/01_Archive/2026-04-20/IFC.js.md index 47ac640c..ad8585cf 100644 --- a/01_Archive/2026-04-20/IFC.js.md +++ b/01_Archive/2026-04-20/IFC.js.md @@ -1,4 +1,4 @@ -# [[IFC.js]] +# [[IFC.js|IFC.js]] ## 📌 Brief Summary IFC.js는 대규모 기하학적 환경이나 건물 모델을 효율적으로 시각화하기 위해 개발되고 있는 프로젝트입니다 [1]. 메모리 소비를 줄이고 렌더링 속도(FPS)를 높이면서도 수많은 객체 중 개별 객체를 빠르게 검색하고 구성할 수 있는 렌더링 최적화를 목표로 합니다 [2]. 최근 최적화 아키텍처를 통해 100MB 이상의 대형 모델을 모바일에서도 원활하게 로드하는 성능을 달성했습니다 [3]. @@ -13,8 +13,8 @@ IFC.js는 대규모 기하학적 환경이나 건물 모델을 효율적으로 - **결과 및 성과:** 이 시스템은 모든 파편(Fragment)이 비슷한 수의 정점과 드로우 콜을 가지도록 균형을 맞춰 효율성을 극대화하며, Autodesk Forge의 로딩 속도에 근접하는 수준의 성능을 입증했습니다 [3, 6]. ## 🔗 Knowledge Connections -- **Related Topics:** [[BufferGeometry]], [[InstancedMesh]], [[Fragment]], [[Draw call]] -- **Projects/Contexts:** [[대규모 기하학적 환경 시각화]], [[Autodesk Forge]] +- **Related Topics:** [[BufferGeometry|BufferGeometry]], [[InstancedMesh|InstancedMesh]], Fragment, [[Draw Call|Draw call]] +- **Projects/Contexts:** 대규모 기하학적 환경 시각화, Autodesk Forge - **Contradictions/Notes:** 소스에 명시적인 모순은 없으나, 모델 렌더링에 있어 `BufferGeometry` 병합 방식(메모리 소모 큼)과 `InstancedMesh` 방식(드로우 콜 증가) 간의 근본적인 트레이드오프(Trade-off)가 존재하며, IFC.js는 이를 해결하기 위해 두 방식을 혼합한 하이브리드 솔루션을 제안합니다 [2, 4, 5]. --- diff --git a/01_Archive/2026-04-20/IFCjs (Fragment).md b/01_Archive/2026-04-20/IFCjs (Fragment).md index 48fb7fc2..c8711170 100644 --- a/01_Archive/2026-04-20/IFCjs (Fragment).md +++ b/01_Archive/2026-04-20/IFCjs (Fragment).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-8A58BF -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - IFCjs (Fragment)" --- -# [[IFCjs (Fragment)]] +# [[IFCjs (Fragment)|IFCjs (Fragment)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > Fragment는 대규모 3D 기하학적 환경을 효율적으로 렌더링하기 위해 IFC.js 개발자들이 고안한 하이브리드 최적화 시스템이다 [1, 2]. 이 시스템은 단일 인터페이스 내에서 로우 폴리(low-poly) 고유 객체를 위한 지오메트리 병합과 하이 폴리(high-poly) 반복 객체를 위한 인스턴싱의 장점을 결합한다 [2]. 이를 통해 메모리 소비와 드로우 콜(Draw call) 횟수 간의 최적의 균형을 달성하면서 개별 객체의 빠른 검색 및 조작 기능을 제공하는 것을 목표로 한다 [1, 3]. @@ -32,11 +32,11 @@ github_commit: "[P-Reinforce] Continuous Worker - IFCjs (Fragment)" - **정책 변화:** Graphics & Performance 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[BufferGeometry]], [[InstancedMesh]], [[Draw Call]] -- **Projects/Contexts:** [[IFC.js]], [[Three.js]] +- **Related Topics:** [[BufferGeometry|BufferGeometry]], [[InstancedMesh|InstancedMesh]], [[Draw Call|Draw Call]] +- **Projects/Contexts:** [[IFC.js|IFC.js]], [[Three.js|Three.js]] - **Contradictions/Notes:** 소스에 따르면, Fragment와 같은 자체적인 최적화 시스템 구축 외에도 대규모 환경 최적화를 위해 다중 그리기(Multidrawing), LOD(Level of Detail), 오클루전 컬링(Occlusion Culling) 등의 추가적인 방법론도 함께 검토되었다 [2]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/IFC.js (Fragment).md]] +- Raw Source: 00_Raw/2026-04-20/IFC.js (Fragment).md --- diff --git a/01_Archive/2026-04-20/IFCjs.md b/01_Archive/2026-04-20/IFCjs.md index cc581924..2ab1f61a 100644 --- a/01_Archive/2026-04-20/IFCjs.md +++ b/01_Archive/2026-04-20/IFCjs.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-659684 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - IFCjs" --- -# [[IFCjs]] +# [[IFCjs|IFCjs]] ## 📌 한 줄 통찰 (The Karpathy Summary) > IFC.js는 대규모 기하학적 환경이나 건물 모델을 효율적으로 시각화하기 위해 개발되고 있는 프로젝트입니다 [1]. 메모리 소비를 줄이고 렌더링 속도(FPS)를 높이면서도 수많은 객체 중 개별 객체를 빠르게 검색하고 구성할 수 있는 렌더링 최적화를 목표로 합니다 [2]. 최근 최적화 아키텍처를 통해 100MB 이상의 대형 모델을 모바일에서도 원활하게 로드하는 성능을 달성했습니다 [3]. @@ -26,11 +26,11 @@ github_commit: "[P-Reinforce] Continuous Worker - IFCjs" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[BufferGeometry]], [[InstancedMesh]], [[Fragment]], [[Draw call]] -- **Projects/Contexts:** [[대규모 기하학적 환경 시각화]], [[Autodesk Forge]] +- **Related Topics:** [[BufferGeometry|BufferGeometry]], [[InstancedMesh|InstancedMesh]], Fragment, [[Draw Call|Draw call]] +- **Projects/Contexts:** 대규모 기하학적 환경 시각화, Autodesk Forge - **Contradictions/Notes:** 소스에 명시적인 모순은 없으나, 모델 렌더링에 있어 `BufferGeometry` 병합 방식(메모리 소모 큼)과 `InstancedMesh` 방식(드로우 콜 증가) 간의 근본적인 트레이드오프(Trade-off)가 존재하며, IFC.js는 이를 해결하기 위해 두 방식을 혼합한 하이브리드 솔루션을 제안합니다 [2, 4, 5]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/IFC.js.md]] +- Raw Source: 00_Raw/2026-04-20/IFC.js.md --- diff --git a/01_Archive/2026-04-20/ISO 9241 Standards.md b/01_Archive/2026-04-20/ISO 9241 Standards.md index 460c7c0d..8df221d5 100644 --- a/01_Archive/2026-04-20/ISO 9241 Standards.md +++ b/01_Archive/2026-04-20/ISO 9241 Standards.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-CA7B1B -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - ISO 9241 Standards" --- -# [[ISO 9241 Standards]] +# [[ISO 9241 Standards|ISO 9241 Standards]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - ISO 9241 Standards" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/ISO 9241 Standards.md]] +- Raw Source: 00_Raw/2026-04-20/ISO 9241 Standards.md --- diff --git a/01_Archive/2026-04-20/ISO 9241 표준.md b/01_Archive/2026-04-20/ISO 9241 표준.md index 430238d4..e4e331ce 100644 --- a/01_Archive/2026-04-20/ISO 9241 표준.md +++ b/01_Archive/2026-04-20/ISO 9241 표준.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-E70ECC -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - ISO 9241 표준" --- -# [[ISO 9241 표준]] +# [[ISO 9241 표준|ISO 9241 표준]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - ISO 9241 표준" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/ISO 9241 표준.md]] +- Raw Source: 00_Raw/2026-04-20/ISO 9241 표준.md --- diff --git a/01_Archive/2026-04-20/Immersive Analytics.md b/01_Archive/2026-04-20/Immersive Analytics.md index b3c27365..fbcbcb6f 100644 --- a/01_Archive/2026-04-20/Immersive Analytics.md +++ b/01_Archive/2026-04-20/Immersive Analytics.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-4B1137 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Immersive Analytics" --- -# [[Immersive Analytics]] +# [[Immersive Analytics|Immersive Analytics]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Immersive Analytics" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Immersive Analytics.md]] +- Raw Source: 00_Raw/2026-04-20/Immersive Analytics.md --- diff --git a/01_Archive/2026-04-20/Immersive Educational Simulations.md b/01_Archive/2026-04-20/Immersive Educational Simulations.md index 53ea8753..17162723 100644 --- a/01_Archive/2026-04-20/Immersive Educational Simulations.md +++ b/01_Archive/2026-04-20/Immersive Educational Simulations.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-7C1550 -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Immersive Educational Simulations" --- -# [[Immersive Educational Simulations]] +# [[Immersive Educational Simulations|Immersive Educational Simulations]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Immersive Educational Simulati ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Immersive Educational Simulations.md]] +- Raw Source: 00_Raw/2026-04-20/Immersive Educational Simulations.md --- diff --git a/01_Archive/2026-04-20/Immersive Sim Design.md b/01_Archive/2026-04-20/Immersive Sim Design.md index 8c18ab92..79489ee6 100644 --- a/01_Archive/2026-04-20/Immersive Sim Design.md +++ b/01_Archive/2026-04-20/Immersive Sim Design.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-A1E36D -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Immersive Sim Design" --- -# [[Immersive Sim Design]] +# [[Immersive Sim Design|Immersive Sim Design]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Immersive Sim Design" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Immersive Sim Design.md]] +- Raw Source: 00_Raw/2026-04-20/Immersive Sim Design.md --- diff --git a/01_Archive/2026-04-20/Immersive Sim Genre.md b/01_Archive/2026-04-20/Immersive Sim Genre.md index d5d876e6..49beada9 100644 --- a/01_Archive/2026-04-20/Immersive Sim Genre.md +++ b/01_Archive/2026-04-20/Immersive Sim Genre.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-33177A -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Immersive Sim Genre" --- -# [[Immersive Sim Genre]] +# [[Immersive Sim Genre|Immersive Sim Genre]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Immersive Sim Genre" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Immersive Sim Genre.md]] +- Raw Source: 00_Raw/2026-04-20/Immersive Sim Genre.md --- diff --git a/01_Archive/2026-04-20/Immersive Sims (e.g., Deus Ex, Dishonored).md b/01_Archive/2026-04-20/Immersive Sims (e.g., Deus Ex, Dishonored).md index b4557f31..546d5fa2 100644 --- a/01_Archive/2026-04-20/Immersive Sims (e.g., Deus Ex, Dishonored).md +++ b/01_Archive/2026-04-20/Immersive Sims (e.g., Deus Ex, Dishonored).md @@ -1,4 +1,4 @@ -[[Immersive Sims (e.g., Deus Ex, Dishonored)]] +[[Immersive Sims (e.g., Deus Ex, Dishonored)|Immersive Sims (e.g., Deus Ex, Dishonored)]] 📌 Brief Summary An immersive sim is a subgenre of action-adventure video games characterized by emergent gameplay, systemic complexity, and player agency. Rather than relying on scripted sequences, these games utilize interconnected "systems" (physics, AI, environmental interactions) to allow players to solve objectives through unscripted, creative methods that reflect their unique tactical choices. @@ -16,8 +16,8 @@ Historical lineage and evolution: * **Modern Iterations:** While the "pure" immersive sim has become a niche market due to high development costs, its DNA persists in modern "sandbox" titles and action-RPGs, influencing systemic elements in games like *The Legend of Zelda: Breath of the Wild*. 🔗 Knowledge Connections -* Related Topics: [[Emergent Gameplay]], [[Systemic Design]], [[Environmental Storyability]], [[Level Design Theory]] -* Projects/Contexts: [[Looking Glass Studios]], [[Arkane Studios]], [[The 'Immersive Sim' Taxonomy Debate]] +* Related Topics: [[Emergent Gameplay|Emergent Gameplay]], [[Systemic Design|Systemic Design]], [[Environmental Storyability|Environmental Storyability]], [[Level Design Theory|Level Design Theory]] +* Projects/Contexts: [[Looking Glass Studios|Looking Glass Studios]], [[Arkane Studios|Arkane Studios]], [[The 'Immersive Sim' Taxonomy Debate|The 'Immersive Sim' Taxonomy Debate]] * Contradictions/Notes: There is an ongoing academic and critical debate regarding the definition of "Immersive Sim." Some scholars argue it is a design methodology (systems-driven) rather than a genre, while others focus on the psychological state of "presence" or "immersion" as the defining characteristic. Last updated: 2026-04-16 \ No newline at end of file diff --git a/01_Archive/2026-04-20/Immersive Sims (e.g., Deus Ex, Thief).md b/01_Archive/2026-04-20/Immersive Sims (e.g., Deus Ex, Thief).md index 80bf008e..b16d95c0 100644 --- a/01_Archive/2026-04-20/Immersive Sims (e.g., Deus Ex, Thief).md +++ b/01_Archive/2026-04-20/Immersive Sims (e.g., Deus Ex, Thief).md @@ -1,4 +1,4 @@ -[[Immersive Sims (e.g., Deus Ex, Thief)]] +[[Immersive Sims (e.g., Deus Ex, Thief)|Immersive Sims (e.g., Deus Ex, Thief)]] 📌 Brief Summary An immersive sim is a subgenre of action-adventure video games characterized by emergent gameplay, systemic complexity, and player agency within a highly reactive environment. Rather than following scripted sequences, these games utilize "systemic design," where interconnected game rules (physics, AI, chemistry, light/shadow) allow players to solve objectives through unscripted, creative methods. @@ -17,8 +17,8 @@ An immersive sim is a subgenre of action-adventure video games characterized by * **Technical Challenges:** Implementing immersive sims requires immense computational overhead for AI sensory systems (sight cones, hearing radii) and complex state-tracking for every interactive object in a persistent world. 🔗 Knowledge Connections -* Related Topics: [[Emergent Gameplay]], [[Systemic Design]], [[Environmental Storytelling]], [[Level Design Theory]] -* Projects/Contexts: [[Looking Glass Studios]], [[Arkane Studios]], [[The Emergence Theory in Game Design]] +* Related Topics: [[Emergent Gameplay|Emergent Gameplay]], [[Systemic Design|Systemic Design]], [[Environmental Storytelling|Environmental Storytelling]], [[Level Design Theory|Level Design Theory]] +* Projects/Contexts: [[Looking Glass Studios|Looking Glass Studios]], [[Arkane Studios|Arkane Studios]], [[The Emergence Theory in Game Design|The Emergence Theory in Game Design]] * Contradictions/Notes: There is an ongoing academic debate regarding whether "Immersive Sim" refers to a specific genre or merely a design methodology applied across different genres (e.g., the overlap between Immersive Sims and Stealth-Action). Last updated: 2026-04-16 \ No newline at end of file diff --git a/01_Archive/2026-04-20/Immersive Sims (eg Deus Ex Dishonored).md b/01_Archive/2026-04-20/Immersive Sims (eg Deus Ex Dishonored).md index 5c64c6ee..3a43c79b 100644 --- a/01_Archive/2026-04-20/Immersive Sims (eg Deus Ex Dishonored).md +++ b/01_Archive/2026-04-20/Immersive Sims (eg Deus Ex Dishonored).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-F70063 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Immersive Sims (eg Deus Ex Dishonored)" --- -# [[Immersive Sims (eg Deus Ex Dishonored)]] +# [[Immersive Sims (eg Deus Ex Dishonored)|Immersive Sims (eg Deus Ex Dishonored)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Immersive Sims (eg Deus Ex Dis ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Immersive Sims (e.g., Deus Ex, Dishonored).md]] +- Raw Source: 00_Raw/2026-04-20/Immersive Sims (e.g., Deus Ex, Dishonored).md --- diff --git a/01_Archive/2026-04-20/Immersive Sims (eg Deus Ex Thief).md b/01_Archive/2026-04-20/Immersive Sims (eg Deus Ex Thief).md index c3d12af2..5903f715 100644 --- a/01_Archive/2026-04-20/Immersive Sims (eg Deus Ex Thief).md +++ b/01_Archive/2026-04-20/Immersive Sims (eg Deus Ex Thief).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-B11AD8 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Immersive Sims (eg Deus Ex Thief)" --- -# [[Immersive Sims (eg Deus Ex Thief)]] +# [[Immersive Sims (eg Deus Ex Thief)|Immersive Sims (eg Deus Ex Thief)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Immersive Sims (eg Deus Ex Thi ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Immersive Sims (e.g., Deus Ex, Thief).md]] +- Raw Source: 00_Raw/2026-04-20/Immersive Sims (e.g., Deus Ex, Thief).md --- diff --git a/01_Archive/2026-04-20/Immersive-Sim-Genre.md b/01_Archive/2026-04-20/Immersive-Sim-Genre.md index 9e30a75b..2f417815 100644 --- a/01_Archive/2026-04-20/Immersive-Sim-Genre.md +++ b/01_Archive/2026-04-20/Immersive-Sim-Genre.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-F89165 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Immersive-Sim-Genre" --- -# [[Immersive-Sim-Genre]] +# [[Immersive-Sim-Genre|Immersive-Sim-Genre]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Immersive-Sim-Genre" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Immersive-Sim-Genre.md]] +- Raw Source: 00_Raw/2026-04-20/Immersive-Sim-Genre.md --- diff --git a/01_Archive/2026-04-20/Immutability-Patterns.md b/01_Archive/2026-04-20/Immutability-Patterns.md index a4a3a999..486cb7a4 100644 --- a/01_Archive/2026-04-20/Immutability-Patterns.md +++ b/01_Archive/2026-04-20/Immutability-Patterns.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-0F93B3 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Immutability-Patterns" --- -# [[Immutability-Patterns]] +# [[Immutability-Patterns|Immutability-Patterns]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Immutability-Patterns" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Immutability-Patterns.md]] +- Raw Source: 00_Raw/2026-04-20/Immutability-Patterns.md --- diff --git a/01_Archive/2026-04-20/In-Context Learning (ICL 문맥 내 학습).md b/01_Archive/2026-04-20/In-Context Learning (ICL 문맥 내 학습).md index 6cc4acab..3cc431c8 100644 --- a/01_Archive/2026-04-20/In-Context Learning (ICL 문맥 내 학습).md +++ b/01_Archive/2026-04-20/In-Context Learning (ICL 문맥 내 학습).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-0A8DD5 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - In-Context Learning (ICL 문맥 내 학습)" --- -# [[In-Context Learning (ICL 문맥 내 학습)]] +# [[In-Context Learning (ICL 문맥 내 학습)|In-Context Learning (ICL 문맥 내 학습)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - In-Context Learning (ICL 문 ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/In-Context Learning (ICL, 문맥 내 학습).md]] +- Raw Source: 00_Raw/2026-04-20/In-Context Learning (ICL, 문맥 내 학습).md --- diff --git a/01_Archive/2026-04-20/In-Context Learning (ICL, 문맥 내 학습).md b/01_Archive/2026-04-20/In-Context Learning (ICL, 문맥 내 학습).md index f2eee23e..bd85fb38 100644 --- a/01_Archive/2026-04-20/In-Context Learning (ICL, 문맥 내 학습).md +++ b/01_Archive/2026-04-20/In-Context Learning (ICL, 문맥 내 학습).md @@ -1,4 +1,4 @@ -[[In-Context Learning (ICL, 문맥 내 학습)]] +[[In-Context Learning (ICL, 문맥 내 학습)|In-Context Learning (ICL, 문맥 내 학습)]] 📌 Brief Summary @@ -108,8 +108,8 @@ In-Context Learning(ICL)은 LLM의 파라미터를 업데이트(학습)하지 🔗 Knowledge Connections -- **Related Topics:** [[Chain-of-Thought (CoT, 사고 사슬)]], [[RAG (검색 증강 생성)]], [[SFT (Supervised Fine-Tuning)]], [[LoRA (Low-Rank Adaptation)]], [[임베딩 (Embedding)]], [[벡터 데이터베이스 (Vector Database)]], [[Mechanistic Interpretability (기계적 해석 가능성)]] -- **Projects/Contexts:** [[AI 추론 시스템]] +- **Related Topics:** [[Chain-of-Thought (CoT, 사고 사슬)|Chain-of-Thought (CoT, 사고 사슬)]], [[RAG (검색 증강 생성)|RAG (검색 증강 생성)]], [[SFT (Supervised Fine-Tuning)|SFT (Supervised Fine-Tuning)]], [[LoRA (Low-Rank Adaptation)|LoRA (Low-Rank Adaptation)]], [[임베딩 (Embedding)|임베딩 (Embedding)]], [[벡터 데이터베이스 (Vector Database)|벡터 데이터베이스 (Vector Database)]], [[Mechanistic Interpretability (기계적 해석 가능성)|Mechanistic Interpretability (기계적 해석 가능성)]] +- **Projects/Contexts:** AI 추론 시스템 - **Contradictions/Notes:** - ICL의 창발 메커니즘은 아직 완전히 해명되지 않음 → Induction Head 가설이 가장 유력하나 전부가 아닐 수 있음. - 예제 순서 효과 (Recency Bias): 마지막 예제에 과도하게 의존하는 경향 → 예제 순서 주의 필요. diff --git a/01_Archive/2026-04-20/Inclusive_Design.md b/01_Archive/2026-04-20/Inclusive_Design.md index 9ad1993e..0ab14902 100644 --- a/01_Archive/2026-04-20/Inclusive_Design.md +++ b/01_Archive/2026-04-20/Inclusive_Design.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-DESIGN-002 -category: "[[10_Wiki/💡 Topics/Design]]" +category: "10_Wiki/💡 Topics/Design" confidence_score: 0.94 tags: [design, inclusive, universal, accessibility] last_reinforced: 2026-04-20 github_commit: "batch-reinforce-06" --- -# [[Inclusive Design (포용적 설계)]] +# Inclusive Design (포용적 설계) ## 📌 한 줄 통찰 (The Karpathy Summary) > 인간의 다양성을 설계의 중심에 두고, 특정 그룹을 배제하지 않는 보편적 접근을 통해 기술의 인간성을 실현하는 일. @@ -24,6 +24,6 @@ github_commit: "batch-reinforce-06" - **정책 변화:** 사용자 만족도(w3) 피드백에서 '포용성 점수'의 비준을 강화. ## 🔗 지식 연결 (Graph) -- **Parent:** [[10_Wiki/💡 Topics/Design]] -- **Related:** [[Accessibility]], [[ISO-9241]], [[User-Centered-Design]] -- **Raw Source:** [[00_Raw/2026-04-20/Universal-Design-Principles.md]] +- **Parent:** 10_Wiki/💡 Topics/Design +- **Related:** [[Accessibility|Accessibility]], [[ISO 9241 표준|ISO-9241]], User-Centered-Design +- **Raw Source:** 00_Raw/2026-04-20/Universal-Design-Principles.md diff --git a/01_Archive/2026-04-20/Incremental Marking.md b/01_Archive/2026-04-20/Incremental Marking.md index 9599e725..07bcbf41 100644 --- a/01_Archive/2026-04-20/Incremental Marking.md +++ b/01_Archive/2026-04-20/Incremental Marking.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-A29470 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Incremental Marking" --- -# [[Incremental Marking]] +# [[Incremental Marking|Incremental Marking]] ## 📌 한 줄 통찰 (The Karpathy Summary) > Incremental Marking은 가비지 컬렉션의 마킹 단계를 한 번의 긴 일시 정지(stop-the-world)로 처리하지 않고, 애플리케이션 실행과 교차하여 여러 개의 짧은 작업 단위로 나누어 수행하는 메모리 관리 기법입니다 [1, 2]. 이 방식은 가비지 컬렉션에 소요되는 전체 시간을 줄이지는 않지만, 작업을 시간에 따라 분산시킴으로써 메인 스레드의 응답성을 크게 향상시킵니다 [2]. 결과적으로 모바일 기기 등에서 발생할 수 있는 긴 지연을 방지하고 애플리케이션이 사용자 입력 및 애니메이션에 원활하게 반응할 수 있도록 돕습니다 [2, 3]. @@ -30,11 +30,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Incremental Marking" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Garbage Collection]], [[Write Barrier]], [[Lazy Sweeping]], [[Mark-Sweep]], [[Orinoco]] -- **Projects/Contexts:** [[V8 JavaScript Engine]], [[IBM OpenJ9]] +- **Related Topics:** [[Garbage Collection|Garbage Collection]], [[Write Barrier|Write Barrier]], Lazy Sweeping, [[Mark-Sweep|Mark-Sweep]], [[Orinoco|Orinoco]] +- **Projects/Contexts:** [[V8 JavaScript Engine|V8 JavaScript Engine]], IBM OpenJ9 - **Contradictions/Notes:** V8 엔진의 Incremental Marking은 메인 스레드가 자바스크립트 실행 중간에 간헐적으로 마킹 작업을 나누어 수행하는 구조이지만 [2], IBM JVM의 Incremental concurrent mark 작업에서는 애플리케이션 스레드가 객체 추적에 관여하지 않으며 오직 백그라운드 스레드만이 사용된다는 기술적 차이가 존재합니다 [8]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Incremental Marking.md]] +- Raw Source: 00_Raw/2026-04-20/Incremental Marking.md --- diff --git a/01_Archive/2026-04-20/Incremental-Compilation.md b/01_Archive/2026-04-20/Incremental-Compilation.md index e5cb46df..d44f13fc 100644 --- a/01_Archive/2026-04-20/Incremental-Compilation.md +++ b/01_Archive/2026-04-20/Incremental-Compilation.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-836C53 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Incremental-Compilation" --- -# [[Incremental-Compilation]] +# [[Incremental-Compilation|Incremental-Compilation]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Incremental-Compilation" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Incremental-Compilation.md]] +- Raw Source: 00_Raw/2026-04-20/Incremental-Compilation.md --- diff --git a/01_Archive/2026-04-20/Incremental-Computation.md b/01_Archive/2026-04-20/Incremental-Computation.md index 41c0cadb..dbca7778 100644 --- a/01_Archive/2026-04-20/Incremental-Computation.md +++ b/01_Archive/2026-04-20/Incremental-Computation.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-6A40F8 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Incremental-Computation" --- -# [[Incremental-Computation]] +# [[Incremental-Computation|Incremental-Computation]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Incremental-Computation" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Incremental-Computation.md]] +- Raw Source: 00_Raw/2026-04-20/Incremental-Computation.md --- diff --git a/01_Archive/2026-04-20/Index Masking.md b/01_Archive/2026-04-20/Index Masking.md index 4d388bd0..fd5b8c27 100644 --- a/01_Archive/2026-04-20/Index Masking.md +++ b/01_Archive/2026-04-20/Index Masking.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-42C840 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Index Masking" --- -# [[Index Masking]] +# [[Index Masking|Index Masking]] ## 📌 한 줄 통찰 (The Karpathy Summary) > Index Masking은 Spectre 및 Meltdown과 같은 캐시 사이드 채널 공격을 방어하기 위해 브라우저 엔진에 도입된 보안 완화(security mitigation) 기법 중 하나이다 [1, 2]. 이 기법은 길이(length)를 다음 2의 거듭제곱으로 올림한 후 1을 빼는 방식으로 마스크(mask)를 계산하여 적용하는 분기 없는(branchless) 보안 검사 방식이다 [3, 4]. 비록 경계를 벗어난(out-of-bounds) 읽기를 완전히 막지는 못하지만, 공격자가 임의의 메모리에 접근하는 것을 방지하는 역할을 한다 [4]. @@ -22,11 +22,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Index Masking" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Spectre and Meltdown]], [[Pointer Poisoning]], [[Branchless Security Checks]] -- **Projects/Contexts:** [[WebKit]], [[Micro-latency Measurement in Web Graphics Pipelines]] +- **Related Topics:** [[Spectre and Meltdown|Spectre and Meltdown]], [[Pointer Poisoning|Pointer Poisoning]], [[Branchless Security Checks|Branchless Security Checks]] +- **Projects/Contexts:** [[WebKit|WebKit]], Micro-latency Measurement in Web Graphics Pipelines - **Contradictions/Notes:** 소스 [5]에서는 Index Masking 기술이 그래픽 실행의 크리티컬 패스에 명령어를 추가하여 마이크로 지연 시간을 증가시킨다고 설명하지만, 소스 [4]의 벤치마크 결과에 따르면 실제 환경의 주요 성능 테스트(Speedometer 등)에서는 그 영향이 측정되지 않거나 2.5% 미만으로 매우 미미하다고 보고합니다. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Index Masking.md]] +- Raw Source: 00_Raw/2026-04-20/Index Masking.md --- diff --git a/01_Archive/2026-04-20/Index.md b/01_Archive/2026-04-20/Index.md index 7e8f8ff6..4b63b3eb 100644 --- a/01_Archive/2026-04-20/Index.md +++ b/01_Archive/2026-04-20/Index.md @@ -2,45 +2,45 @@ ## 💡 Topics - **AI** - - [[Automated_Mapping]] - - [[Computer_Vision]] - - [[CV_Synthesis]] - - [[RL_Neuroscience]] + - [[Automated_Mapping|Automated_Mapping]] + - [[Computer_Vision|Computer_Vision]] + - [[CV_Synthesis|CV_Synthesis]] + - [[RL_Neuroscience|RL_Neuroscience]] - **Automation** - - [[IoT]] (🔗 Digital-Twin Link) - - [[SCADA]] + - [[IoT|IoT]] (🔗 Digital-Twin Link) + - [[SCADA|SCADA]] - **Coding** - - [[AST_Traversal]] - - [[CST]] - - [[Formatting]] (🔗 CST Link) - - [[Parser]] (🔗 AST/CST Link) + - [[AST_Traversal|AST_Traversal]] + - [[CST|CST]] + - [[Formatting|Formatting]] (🔗 CST Link) + - [[Parser|Parser]] (🔗 AST/CST Link) - **Design** - - [[Accessibility]] - - [[Cognitive_Load]] (🔗 HCI Link) - - [[CrUX]] (🔗 UX Link) - - [[HCI]] - - [[Inclusive_Design]] + - [[Accessibility|Accessibility]] + - [[Cognitive_Load|Cognitive_Load]] (🔗 HCI Link) + - [[CrUX|CrUX]] (🔗 UX Link) + - [[HCI|HCI]] + - [[Inclusive_Design|Inclusive_Design]] - **Education** - - [[Adaptive_Learning]] + - [[Adaptive_Learning|Adaptive_Learning]] - **Graphics** - - [[3D_Gaussian_Splatting]] - - [[3D_Web_HMI]] - - [[Digital_Twin]] - - [[Predictive_Maintenance]] - - [[VPS_NeRF]] + - [[3D_Gaussian_Splatting|3D_Gaussian_Splatting]] + - [[3D_Web_HMI|3D_Web_HMI]] + - [[Digital_Twin|Digital_Twin]] + - [[Predictive_Maintenance|Predictive_Maintenance]] + - [[VPS_NeRF|VPS_NeRF]] - **Health** - - [[ACL_Prevention]] + - [[ACL_Prevention|ACL_Prevention]] - **Metaverse** - - [[Architecture]] - - [[Spatial_Computing]] + - [[Architecture|Architecture]] + - [[Spatial_Computing|Spatial_Computing]] - **Psychology** - - [[ABA]] - - [[Addiction_Neuroscience]] - - [[Behavioral_Economics]] - - [[Dopamine]] - - [[Neuroplasticity]] - - [[Nudge_Theory]] - - [[Operant_Conditioning]] + - [[ABA|ABA]] + - [[Addiction_Neuroscience|Addiction_Neuroscience]] + - [[Behavioral_Economics|Behavioral_Economics]] + - [[Dopamine|Dopamine]] + - [[Neuroplasticity|Neuroplasticity]] + - [[Nudge_Theory|Nudge_Theory]] + - [[Operant_Conditioning|Operant_Conditioning]] ## 🛠️ Projects (Scanning...) diff --git a/01_Archive/2026-04-20/Indirect Draw.md b/01_Archive/2026-04-20/Indirect Draw.md index ea3b6438..8a9ae9f5 100644 --- a/01_Archive/2026-04-20/Indirect Draw.md +++ b/01_Archive/2026-04-20/Indirect Draw.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-8EEC8D -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Indirect Draw" --- -# [[Indirect Draw]] +# [[Indirect Draw|Indirect Draw]] ## 📌 한 줄 통찰 (The Karpathy Summary) > Indirect Draw(간접 그리기)는 렌더링할 객체의 수와 정보를 CPU가 아닌 GPU가 컴퓨트 셰이더(Compute Shader)의 연산 결과를 바탕으로 직접 결정하여 화면에 그리는 GPU 주도 렌더링(GPU-driven rendering) 기법이다 [1, 2]. 이 방식을 사용하면 시야 절두체 컬링(Frustum Culling)이나 오클루전(Occlusion) 컬링의 결과를 GPU 내부 버퍼에 저장하고 `drawIndirect` 명령으로 바로 출력하므로, CPU와 GPU 간의 데이터 전송량 및 동기화 지연을 거의 0으로 줄일 수 있다 [2, 3]. 매 프레임 수백만 개의 인스턴스를 GPU에서 직접 컬링하고 렌더링해야 하는 대규모 3D 환경에서 필수적인 성능 최적화 기술로 활용된다 [1, 2]. @@ -27,11 +27,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Indirect Draw" - **정책 변화:** Graphics & Performance 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[GPU-Driven Rendering]], [[Compute Shader]], [[Frustum Culling]], [[WebGPU]] -- **Projects/Contexts:** [[Three.js WebGPURenderer]], [[BatchedMesh]], [[Vulkan]] +- **Related Topics:** [[GPU-driven Rendering|GPU-Driven Rendering]], [[Compute Shader|Compute Shader]], [[Frustum Culling|Frustum Culling]], [[WebGPU|WebGPU]] +- **Projects/Contexts:** [[Three.js WebGPURenderer|Three.js WebGPURenderer]], [[BatchedMesh|BatchedMesh]], [[Vulkan|Vulkan]] - **Contradictions/Notes:** 대규모 지오메트리를 처리할 때 BatchedMesh만으로는 CPU의 버퍼 업로드 병목이 발생할 수 있어 근본적인 성능 문제를 피하기 어려우며, 이를 해결하기 위해서는 WebGPU 환경의 Indirect Draw 지원이 필수적이라는 점이 소스에서 한계점(pushing the limits)으로 지적된다 [9]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Indirect Draw.md]] +- Raw Source: 00_Raw/2026-04-20/Indirect Draw.md --- diff --git a/01_Archive/2026-04-20/Indoor Wayfinding for Smart Cities.md b/01_Archive/2026-04-20/Indoor Wayfinding for Smart Cities.md index d5a35407..ae6bbdf4 100644 --- a/01_Archive/2026-04-20/Indoor Wayfinding for Smart Cities.md +++ b/01_Archive/2026-04-20/Indoor Wayfinding for Smart Cities.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-FA7892 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Indoor Wayfinding for Smart Cities" --- -# [[Indoor Wayfinding for Smart Cities]] +# [[Indoor Wayfinding for Smart Cities|Indoor Wayfinding for Smart Cities]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Indoor Wayfinding for Smart Ci ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Indoor Wayfinding for Smart Cities.md]] +- Raw Source: 00_Raw/2026-04-20/Indoor Wayfinding for Smart Cities.md --- diff --git a/01_Archive/2026-04-20/Industrial Metaverse.md b/01_Archive/2026-04-20/Industrial Metaverse.md index a88b8819..a76c902d 100644 --- a/01_Archive/2026-04-20/Industrial Metaverse.md +++ b/01_Archive/2026-04-20/Industrial Metaverse.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-ED0741 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Industrial Metaverse" --- -# [[Industrial Metaverse]] +# [[Industrial Metaverse|Industrial Metaverse]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Industrial Metaverse" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Industrial Metaverse.md]] +- Raw Source: 00_Raw/2026-04-20/Industrial Metaverse.md --- diff --git a/01_Archive/2026-04-20/Industrial-Automation.md b/01_Archive/2026-04-20/Industrial-Automation.md index 4f4ddb6c..80e80703 100644 --- a/01_Archive/2026-04-20/Industrial-Automation.md +++ b/01_Archive/2026-04-20/Industrial-Automation.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-879F81 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Industrial-Automation" --- -# [[Industrial-Automation]] +# [[Industrial-Automation|Industrial-Automation]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Industrial-Automation" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Industrial-Automation.md]] +- Raw Source: 00_Raw/2026-04-20/Industrial-Automation.md --- diff --git a/01_Archive/2026-04-20/Industry 4.0_Smart Manufacturing.md b/01_Archive/2026-04-20/Industry 4.0_Smart Manufacturing.md index 9dc16601..42d98684 100644 --- a/01_Archive/2026-04-20/Industry 4.0_Smart Manufacturing.md +++ b/01_Archive/2026-04-20/Industry 4.0_Smart Manufacturing.md @@ -1,4 +1,4 @@ -[[Industry 4.0/Smart Manufacturing]] +[[Industry 4.0_Smart Manufacturing|Industry 4.0/Smart Manufacturing]] 📌 Brief Summary Industry 4.0 refers to the ongoing transformation of manufacturing through the integration of cyber-physical systems (CPS), the Internet of Things (IoT), and advanced computational intelligence. Smart Manufacturing represents the practical application of these technologies to create highly automated, self-optimizing, and decentralized production environments capable of real-time decision-making and extreme customization. @@ -15,8 +15,8 @@ Key technological pillars driving this transition include: The strategic objective of Smart Manufacturing is to achieve "Mass Customization"—the ability to produce highly individualized products at the efficiency levels typically associated with mass production. This requires a transition from hierarchical, rigid automation (ISA-95 model) to a decentralized, service-oriented architecture where machines can autonomously negotiate tasks and resources via standardized communication protocols (e.g., OPC UA). 🔗 Knowledge Connections -* Related Topics: [[Cyber-Physical-Systems]], [[Digital-Twin-Technology]], [[Additive-Manufacturing]], [[Edge-Computing]] -* Projects/Contexts: [[Manufacturing-Execution-Systems-(MES)]], [[Supply-Chain-4.0]], [[Industrial-AI]] +* Related Topics: Cyber-Physical-Systems, [[Digital-Twin-Technology|Digital-Twin-Technology]], Additive-Manufacturing, [[Edge-Computing|Edge-Computing]] +* Projects/Contexts: Manufacturing-Execution-Systems-(MES), Supply-Chain-4.0, Industrial-AI * Contradictions/Notes: A significant debate exists regarding the "Security vs. Connectivity" trade-off; increased interoperability via IIoT expands the attack surface for cyber-physical attacks. Additionally, there is ongoing scholarly tension between the cost-benefit of full automation versus the socio-economic implications of workforce displacement (the "Human-in-the-loop" debate). Last updated: 2026-04-16 \ No newline at end of file diff --git a/01_Archive/2026-04-20/Industry 40_Smart Manufacturing.md b/01_Archive/2026-04-20/Industry 40_Smart Manufacturing.md index b98cc7a7..fde9265d 100644 --- a/01_Archive/2026-04-20/Industry 40_Smart Manufacturing.md +++ b/01_Archive/2026-04-20/Industry 40_Smart Manufacturing.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-84B460 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Industry 40_Smart Manufacturing" --- -# [[Industry 40_Smart Manufacturing]] +# [[Industry 40_Smart Manufacturing|Industry 40_Smart Manufacturing]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Industry 40_Smart Manufacturin ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Industry 4.0_Smart Manufacturing.md]] +- Raw Source: 00_Raw/2026-04-20/Industry 4.0_Smart Manufacturing.md --- diff --git a/01_Archive/2026-04-20/Information Theory.md b/01_Archive/2026-04-20/Information Theory.md index cf066d66..21a6a637 100644 --- a/01_Archive/2026-04-20/Information Theory.md +++ b/01_Archive/2026-04-20/Information Theory.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AI-052 -category: "[[10_Wiki/💡 Topics/Computational Theory & Math]]" +category: "10_Wiki/💡 Topics/Computational Theory & Math" confidence_score: 0.98 tags: [information theory, shannon entropy, compression, information] last_reinforced: 2026-06-XX github_commit: "[P-Reinforce] Processed Information Theory." --- -# [[Information Theory]] (정보 이론) +# [[Information Theory|Information Theory]] (정보 이론) ## 📌 한 줄 통찰 (The Karpathy Summary) > 정보의 양과 질을 수학적으로 측정하는 학문으로, 불확실성을 감소시키는 정도를 '엔트로피'로 정의하여 데이터 압축, AI 모델의 효율성, 그리고 지식의 전달 과정을 정량화한다. @@ -26,7 +26,7 @@ github_commit: "[P-Reinforce] Processed Information Theory." - **정책 변화:** 최근에는 LLM의 성능 평가에 단순히 Perplexity 같은 전통적인 엔트로피 개념뿐만 아니라, '일관성 (Coherence)'과 '사실 정확도'를 결합한 새로운 측정 지표가 요구되고 있다. ## 🔗 지식 연결 (Graph) -- Parent: [[Computational Thinking]] -- Related: [[Shannon Entropy]] , [[Information-Architecture]] , [[AI 모델 평가]] -- Raw Source: [[00_Raw/Information Theory.md]] +- Parent: [[Computational Thinking|Computational Thinking]] +- Related: [[Shannon-Entropy|Shannon Entropy]] , [[Information-Architecture|Information-Architecture]] , AI 모델 평가 +- Raw Source: 00_Raw/Information Theory.md --- \ No newline at end of file diff --git a/01_Archive/2026-04-20/Information-Architecture.md b/01_Archive/2026-04-20/Information-Architecture.md index ee9f1236..bed717d1 100644 --- a/01_Archive/2026-04-20/Information-Architecture.md +++ b/01_Archive/2026-04-20/Information-Architecture.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-B98E5E -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Information-Architecture" --- -# [[Information-Architecture]] +# [[Information-Architecture|Information-Architecture]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Information-Architecture" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Information-Architecture.md]] +- Raw Source: 00_Raw/2026-04-20/Information-Architecture.md --- diff --git a/01_Archive/2026-04-20/Injury-Prevention-Protocols.md b/01_Archive/2026-04-20/Injury-Prevention-Protocols.md index 7bbbfae3..024dde54 100644 --- a/01_Archive/2026-04-20/Injury-Prevention-Protocols.md +++ b/01_Archive/2026-04-20/Injury-Prevention-Protocols.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-F84241 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Injury-Prevention-Protocols" --- -# [[Injury-Prevention-Protocols]] +# [[Injury-Prevention-Protocols|Injury-Prevention-Protocols]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Injury-Prevention-Protocols" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Injury-Prevention-Protocols.md]] +- Raw Source: 00_Raw/2026-04-20/Injury-Prevention-Protocols.md --- diff --git a/01_Archive/2026-04-20/Inquiry-Based Learning.md b/01_Archive/2026-04-20/Inquiry-Based Learning.md index c4ea3492..efb17ddb 100644 --- a/01_Archive/2026-04-20/Inquiry-Based Learning.md +++ b/01_Archive/2026-04-20/Inquiry-Based Learning.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-0A7A61 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Inquiry-Based Learning" --- -# [[Inquiry-Based Learning]] +# [[Inquiry-Based Learning|Inquiry-Based Learning]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Inquiry-Based Learning" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Inquiry-Based Learning.md]] +- Raw Source: 00_Raw/2026-04-20/Inquiry-Based Learning.md --- diff --git a/01_Archive/2026-04-20/InstancedMesh (드로우 콜 최적화).md b/01_Archive/2026-04-20/InstancedMesh (드로우 콜 최적화).md index 9e78853c..f6662f05 100644 --- a/01_Archive/2026-04-20/InstancedMesh (드로우 콜 최적화).md +++ b/01_Archive/2026-04-20/InstancedMesh (드로우 콜 최적화).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-86F967 -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - InstancedMesh (드로우 콜 최적화)" --- -# [[InstancedMesh (드로우 콜 최적화)]] +# [[InstancedMesh (드로우 콜 최적화)|InstancedMesh (드로우 콜 최적화)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > `InstancedMesh`는 **동일한 기하구조(Geometry)와 재질(Material)을 공유하는 수많은 객체를 단 1회의 드로우 콜(Draw Call)만으로 GPU에서 렌더링**하여, CPU의 오버헤드를 극적으로 줄이고 애플리케이션의 프레임 레이트(FPS)를 비약적으로 향상시키는 3D 그래픽스 핵심 최적화 기법입니다. @@ -26,8 +26,8 @@ github_commit: "[P-Reinforce] Continuous Worker - InstancedMesh (드로우 콜 - **정책 변화:** Graphics & Performance 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Draw Call Optimization (드로우 콜 최적화)]], [[BatchedMesh]], [[Object Pooling (오브젝트 풀링)]], [[React Three Fiber 자산 최적화]] -- **Projects/Contexts:** [[대규모 파티클 시스템 최적화]], [[수만 개의 데이터를 표현하는 3D 산점도(Scatter Plot) 시각화]], [[숲, 군중 등 반복 객체가 많은 3D 씬]] +- **Related Topics:** Draw Call Optimization (드로우 콜 최적화), [[BatchedMesh|BatchedMesh]], [[Object Pooling (오브젝트 풀링)|Object Pooling (오브젝트 풀링)]], React Three Fiber 자산 최적화 +- **Projects/Contexts:** [[대규모 파티클 시스템 최적화|대규모 파티클 시스템 최적화]], 수만 개의 데이터를 표현하는 3D 산점도(Scatter Plot) 시각화, 숲, 군중 등 반복 객체가 많은 3D 씬 - **Contradictions/Notes:** `InstancedMesh`는 성능 개선에 탁월하지만, **모든 인스턴스가 반드시 동일한 기하구조(Geometry)와 재질(Material)을 공유해야 한다는 설계적 제약**이 따릅니다. 만약 재질은 같으나 형태(Geometry)가 서로 다른 여러 객체들을 묶어 드로우 콜을 1회로 줄이려면, R156 버전에 도입된 `BatchedMesh`를 사용하는 것이 더 적합합니다. -- Raw Source: [[00_Raw/2026-04-20/InstancedMesh (드로우 콜 최적화).md]] +- Raw Source: 00_Raw/2026-04-20/InstancedMesh (드로우 콜 최적화).md --- diff --git a/01_Archive/2026-04-20/InstancedMesh Performance Bottlenecks.md b/01_Archive/2026-04-20/InstancedMesh Performance Bottlenecks.md index e33ecf6e..985ba623 100644 --- a/01_Archive/2026-04-20/InstancedMesh Performance Bottlenecks.md +++ b/01_Archive/2026-04-20/InstancedMesh Performance Bottlenecks.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-F035BF -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - InstancedMesh Performance Bottlenecks" --- -# [[InstancedMesh Performance Bottlenecks]] +# [[InstancedMesh Performance Bottlenecks|InstancedMesh Performance Bottlenecks]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -36,11 +36,11 @@ github_commit: "[P-Reinforce] Continuous Worker - InstancedMesh Performance Bott - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Frustum Culling]], [[Overdraw]], [[Draw Call]], [[BatchedMesh]], [[Texture Atlas]] -- **Projects/Contexts:** [[InstancedMesh2 library]], [[Three.js WebGPU Renderer]], [[WebGL multi_draw extension]] +- **Related Topics:** [[Frustum Culling|Frustum Culling]], [[Overdraw|Overdraw]], [[Draw Call|Draw Call]], [[BatchedMesh|BatchedMesh]], [[Texture Atlas|Texture Atlas]] +- **Projects/Contexts:** [[InstancedMesh2 library|InstancedMesh2 library]], [[Threejs WebGPURenderer|Three.js WebGPU Renderer]], WebGL multi_draw extension - **Contradictions/Notes:** 많은 렌더링 상황에서 `InstancedMesh`가 만능 최적화 기법으로 여겨지지만, 실제 벤치마크 사례에서는 드로우 콜을 1회로 줄였음에도 불구하고 오버드로우 및 GPU 프래그먼트 병목 때문에 개별 메쉬나 `BatchedMesh` 방식보다 오히려 렌더링 시간(Frame Time)이 느려지거나 성능이 저하되는 모순적인 결과가 발생하기도 합니다 [5, 6, 23]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/InstancedMesh Performance Bottlenecks.md]] +- Raw Source: 00_Raw/2026-04-20/InstancedMesh Performance Bottlenecks.md --- diff --git a/01_Archive/2026-04-20/InstancedMesh 동적 버퍼 확장.md b/01_Archive/2026-04-20/InstancedMesh 동적 버퍼 확장.md index 0f612aa5..2f76170a 100644 --- a/01_Archive/2026-04-20/InstancedMesh 동적 버퍼 확장.md +++ b/01_Archive/2026-04-20/InstancedMesh 동적 버퍼 확장.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-D6CCE0 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - InstancedMesh 동적 버퍼 확장" --- -# [[InstancedMesh 동적 버퍼 확장]] +# [[InstancedMesh 동적 버퍼 확장|InstancedMesh 동적 버퍼 확장]] ## 📌 한 줄 통찰 (The Karpathy Summary) > InstancedMesh 동적 버퍼 확장은 렌더링 중 인스턴스 수가 초기 할당된 용량(Capacity)을 초과할 때, 시스템이 새로운 더 큰 버퍼를 할당하고 기존 데이터를 복사하는 과정을 의미한다 [1]. 이 과정에서 수십 메가바이트 크기의 배열이 빈번하게 생성되고 파괴되어 가비지 컬렉션(GC)을 유발하며, 이는 프레임 지연(스터터링)이나 메모리 할당 오류로 이어진다 [1, 2]. 결과적으로 이러한 성능 병목을 피하기 위해 개발자들은 런타임 확장을 피하고, 최대 예상 인스턴스 수에 맞춘 버퍼 사전 할당이나 객체 풀링 전략을 권장하고 있다 [1, 3]. @@ -27,11 +27,11 @@ github_commit: "[P-Reinforce] Continuous Worker - InstancedMesh 동적 버퍼 - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[InstancedMesh]], [[가비지 컬렉션 (Garbage Collection)]], [[객체 풀링 (Object Pooling)]], [[버퍼 사전 할당 (Buffer Preallocation)]] -- **Projects/Contexts:** [[Needle Engine]], [[A-Frame (instanced-mesh 컴포넌트)]], [[실시간 웹 그래픽스 최적화]] +- **Related Topics:** [[InstancedMesh|InstancedMesh]], [[가비지 컬렉션 (Garbage Collection)|가비지 컬렉션 (Garbage Collection)]], 객체 풀링 (Object Pooling), 버퍼 사전 할당 (Buffer Preallocation) +- **Projects/Contexts:** [[Needle Engine|Needle Engine]], A-Frame (instanced-mesh 컴포넌트), 실시간 웹 그래픽스 최적화 - **Contradictions/Notes:** 예측 불가능한 다량의 객체를 렌더링하려면 동적 확장이 필수적인 기능처럼 보이나, 실제 렌더링 환경에서는 이 과정이 프레임 드랍과 메모리 누수 위험 등 높은 리스크를 수반하므로 오히려 고정 용량 할당이나 풀링을 통해 원천적으로 확장을 회피하는 것이 강력히 권장된다 [1, 3, 4]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/InstancedMesh 동적 버퍼 확장.md]] +- Raw Source: 00_Raw/2026-04-20/InstancedMesh 동적 버퍼 확장.md --- diff --git a/01_Archive/2026-04-20/InstancedMesh 사용 시 드로우 콜 최적화의 한계점 사례 연구.md b/01_Archive/2026-04-20/InstancedMesh 사용 시 드로우 콜 최적화의 한계점 사례 연구.md index c8d36b10..ce849c22 100644 --- a/01_Archive/2026-04-20/InstancedMesh 사용 시 드로우 콜 최적화의 한계점 사례 연구.md +++ b/01_Archive/2026-04-20/InstancedMesh 사용 시 드로우 콜 최적화의 한계점 사례 연구.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-88CEC2 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - InstancedMesh 사용 시 드로우 콜 최적화의 한계점 사례 연구" --- -# [[InstancedMesh 사용 시 드로우 콜 최적화의 한계점 사례 연구]] +# [[InstancedMesh 사용 시 드로우 콜 최적화의 한계점 사례 연구|InstancedMesh 사용 시 드로우 콜 최적화의 한계점 사례 연구]] ## 📌 한 줄 통찰 (The Karpathy Summary) > InstancedMesh는 단일 드로우 콜(Draw Call)로 동일한 기하학적 구조와 재질을 가진 수많은 객체를 렌더링하여 CPU 오버헤드를 획기적으로 줄이는 최적화 기술입니다 [1, 2]. 그러나 실무 환경에서는 지오메트리 단일성 제약, 시야 절두체 컬링(Frustum Culling)의 비효율성, 오버드로우(Overdraw), 동적 데이터 갱신 시의 메모리 대역폭 포화 등 여러 구조적 한계를 드러냅니다 [3-7]. 본 사례 연구는 이러한 한계들로 인해 드로우 콜 횟수의 감소가 반드시 전반적인 렌더링 프레임 레이트(FPS) 상승으로 이어지지는 않음을 실증적으로 분석합니다 [3]. @@ -36,11 +36,11 @@ github_commit: "[P-Reinforce] Continuous Worker - InstancedMesh 사용 시 드 - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Frustum Culling]], [[Overdraw]], [[BatchedMesh]], [[WebGPU Compute Shader]], [[Texture Atlas]], [[Garbage Collection (GC)]] -- **Projects/Contexts:** [[대규모 웹 그래픽스 프로젝트]], [[CAD 렌더링 최적화]], [[BIM 모델 렌더링]] +- **Related Topics:** [[Frustum Culling|Frustum Culling]], [[Overdraw|Overdraw]], [[BatchedMesh|BatchedMesh]], [[WebGPU Compute Shader|WebGPU Compute Shader]], [[Texture Atlas|Texture Atlas]], [[Garbage Collection (GC)|Garbage Collection (GC)]] +- **Projects/Contexts:** [[대규모 웹 그래픽스 프로젝트|대규모 웹 그래픽스 프로젝트]], [[CAD 렌더링 최적화|CAD 렌더링 최적화]], [[BIM 모델 렌더링|BIM 모델 렌더링]] - **Contradictions/Notes:** 소스에 따르면 InstancedMesh 기술은 드로우 콜을 획기적으로 줄여 CPU 부담을 최소화하지만, 자체적인 정렬 부재와 컬링의 한계로 인해 조명 연산이 복잡한 환경에서는 오버드로우를 유발하여 결과적으로 GPU 픽셀 처리 성능을 상회하게 만들어 전체 FPS를 하락시킬 수 있다는 모순된 현상이 발생함을 강력히 지적합니다 [6]. 또한 대안으로 제시되는 BatchedMesh 역시 드로우 콜을 줄일 수는 있으나, 극한의 대규모 삼각형 렌더링 시에는 버퍼 패킹 비용이 오히려 일반 메쉬 렌더링보다 낮은 성능을 보이는 병목 사례가 보고됩니다 [15]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/InstancedMesh 사용 시 드로우 콜 최적화의 한계점 사례 연구.md]] +- Raw Source: 00_Raw/2026-04-20/InstancedMesh 사용 시 드로우 콜 최적화의 한계점 사례 연구.md --- diff --git a/01_Archive/2026-04-20/InstancedMesh 최적화.md b/01_Archive/2026-04-20/InstancedMesh 최적화.md index 4801fb47..6f9fc069 100644 --- a/01_Archive/2026-04-20/InstancedMesh 최적화.md +++ b/01_Archive/2026-04-20/InstancedMesh 최적화.md @@ -1,16 +1,16 @@ --- id: P-REINFORCE-AUTO-7D070F -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - InstancedMesh 최적화" --- -# [[InstancedMesh 최적화]] +# [[InstancedMesh 최적화|InstancedMesh 최적화]] ## 📌 한 줄 통찰 (The Karpathy Summary) -> [[InstancedMesh 최적화]]는 동일한 기하학적 구조(Geometry)와 재질(Material)을 가진 수많은 객체를 단 한 번의 드로우 콜(Draw Call)로 GPU에 전달하여 렌더링 성능을 극대화하는 기법입니다 [1], [2]. 수천, 수만 개의 반복적인 객체(나무, 풀, 파티클 등)를 렌더링할 때 CPU의 명령 발행 오버헤드를 대폭 줄이고 메모리 사용량을 최소화할 수 있습니다 [3], [4], [5]. 그러나 전체 인스턴스에 대한 전역적 시야 절두체 컬링, 개별 객체의 깊이 정렬 부재로 인한 오버드로우 등 구조적 한계가 존재하므로, 프로젝트의 특성과 병목 구간에 맞춘 전략적인 도입이 필요합니다 [6], [7]. +> [[InstancedMesh 최적화|InstancedMesh 최적화]]는 동일한 기하학적 구조(Geometry)와 재질(Material)을 가진 수많은 객체를 단 한 번의 드로우 콜(Draw Call)로 GPU에 전달하여 렌더링 성능을 극대화하는 기법입니다 [1], [2]. 수천, 수만 개의 반복적인 객체(나무, 풀, 파티클 등)를 렌더링할 때 CPU의 명령 발행 오버헤드를 대폭 줄이고 메모리 사용량을 최소화할 수 있습니다 [3], [4], [5]. 그러나 전체 인스턴스에 대한 전역적 시야 절두체 컬링, 개별 객체의 깊이 정렬 부재로 인한 오버드로우 등 구조적 한계가 존재하므로, 프로젝트의 특성과 병목 구간에 맞춘 전략적인 도입이 필요합니다 [6], [7]. ## 📖 구조화된 지식 (Synthesized Content) * **드로우 콜 및 메모리 최적화 원리** @@ -22,11 +22,11 @@ github_commit: "[P-Reinforce] Continuous Worker - InstancedMesh 최적화" * **컬링(Culling)의 비효율성:** InstancedMesh는 엔진 수준에서 단일 객체로 취급되므로, 개별 인스턴스 단위가 아닌 전체를 아우르는 거대한 바운딩 볼륨을 기준으로 단 한 번의 시야 절두체 컬링(Frustum Culling)을 수행합니다 [15]. 이로 인해 시야 밖의 수많은 객체에 대해서도 불필요한 GPU 정점 연산이 강제될 수 있습니다 [15], [16]. * **정렬 부재와 오버드로우(Overdraw):** 카메라 거리에 따른 자동 정렬 기능을 제공하지 않기 때문에, 뒤에 가려진 픽셀 연산을 조기에 종료(Early-Z)하지 못해 오버드로우가 발생합니다 [17], [18]. 특히 투명/반투명 객체 렌더링 시에는 깊이 정렬이 뒤섞여 시각적 오류를 초래합니다 [19]. * **메모리 대역폭 한계:** 애니메이션 등으로 매 프레임 수백만 개의 인스턴스 변환 행렬(인스턴스당 64바이트)을 갱신해야 할 경우, 데이터 전송량이 시스템 버스 대역폭을 포화시켜 프레임 지연(Stuttering)을 유발할 수 있습니다 [20], [21]. - * **다양성 표현의 제약:** 단일 지오메트리와 단일 재질만 참조할 수 있어 다양한 에셋을 표현하기 어렵습니다 [22]. 개별 인스턴스에 서로 다른 텍스처를 적용하려면 [[Texture Atlas]]나 [[데이터 배열 텍스처(Data Array Textures)]]를 활용하고 UV 오프셋을 조정하는 추가적인 셰이더 조작이 강제됩니다 [23], [24], [25]. + * **다양성 표현의 제약:** 단일 지오메트리와 단일 재질만 참조할 수 있어 다양한 에셋을 표현하기 어렵습니다 [22]. 개별 인스턴스에 서로 다른 텍스처를 적용하려면 [[Texture Atlas|Texture Atlas]]나 데이터 배열 텍스처(Data Array Textures)를 활용하고 UV 오프셋을 조정하는 추가적인 셰이더 조작이 강제됩니다 [23], [24], [25]. * **한계 극복을 위한 개선 및 대안 전략** * **공간 분할 기반 그룹화:** 모든 객체를 하나의 거대한 InstancedMesh로 묶기보다는, 공간적으로 인접한 객체끼리 소규모(100~500개)로 분할하여 관리하면 절두체 컬링의 정밀도를 높여 GPU 연산 낭비를 줄일 수 있습니다 [7]. - * **InstancedMesh2 및 BatchedMesh 활용:** 단일 지오메트리 제약이 문제가 된다면, 서로 다른 지오메트리를 하나의 드로우 콜로 묶어주는 [[BatchedMesh]] 사용이 권장됩니다 [26], [27]. 또한, 커뮤니티 생태계의 `InstancedMesh2` 라이브러리를 활용하면 개별 인스턴스의 프러스텀 컬링, 정렬, [[Level of Detail (LOD)]], BVH 기반의 빠른 레이캐스팅, 스킨드 애니메이션 최적화 등의 기능을 확장 적용할 수 있습니다 [28], [29], [30]. + * **InstancedMesh2 및 BatchedMesh 활용:** 단일 지오메트리 제약이 문제가 된다면, 서로 다른 지오메트리를 하나의 드로우 콜로 묶어주는 [[BatchedMesh|BatchedMesh]] 사용이 권장됩니다 [26], [27]. 또한, 커뮤니티 생태계의 `InstancedMesh2` 라이브러리를 활용하면 개별 인스턴스의 프러스텀 컬링, 정렬, [[Level of Detail (LOD)|Level of Detail (LOD)]], BVH 기반의 빠른 레이캐스팅, 스킨드 애니메이션 최적화 등의 기능을 확장 적용할 수 있습니다 [28], [29], [30]. * **WebGPU 컴퓨트 셰이더 도입:** WebGPU 환경에서는 GPU가 직접 가시성 판단과 컬링을 처리하여 CPU와 GPU 간의 통신 비용을 "0"에 수렴하게 하는 간접 그리기(Indirect Draw) 방식이 차세대 대안으로 떠오르고 있습니다 [31]. ## ⚠️ 모순 및 업데이트 (Contradictions & RL Update) @@ -34,13 +34,13 @@ github_commit: "[P-Reinforce] Continuous Worker - InstancedMesh 최적화" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Draw Call]], [[Frustum Culling]], [[BatchedMesh]], [[Texture Atlas]], [[Level of Detail (LOD)]], [[Overdraw]] -- **Projects/Contexts:** [[Three.js]], [[WebGL/WebGPU Rendering]], [[Babylon.js]], [[Unity GPU Instancing]] +- **Related Topics:** [[Draw Call|Draw Call]], [[Frustum Culling|Frustum Culling]], [[BatchedMesh|BatchedMesh]], [[Texture Atlas|Texture Atlas]], [[Level of Detail (LOD)|Level of Detail (LOD)]], [[Overdraw|Overdraw]] +- **Projects/Contexts:** [[Three.js|Three.js]], WebGL/WebGPU Rendering, [[Babylon.js|Babylon.js]], Unity GPU Instancing - **Contradictions/Notes:** * "InstancedMesh를 사용하면 항상 성능이 향상된다고 가정하기 쉽지만, 소스는 매우 단순한 기하학(예: 단일 삼각형)의 경우 인스턴싱 변환 행렬 데이터를 처리하는 오버헤드가 더 커서 단순히 지오메트리를 병합(Merging)하는 방식이 오히려 프레임 레이트 측면에서 유리할 수 있다고 주장합니다 [32], [33]." * "드로우 콜 수가 극적으로 감소함에도 불구하고, 5,000개 수준의 객체 환경에서는 인스턴스 정렬 부재로 인한 오버드로우 비용이 CPU 이득을 상회하여 일반 메쉬 렌더링보다 낮은 FPS를 기록할 수 있다고 경고합니다 [18]." --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/InstancedMesh 최적화.md]] +- Raw Source: 00_Raw/2026-04-20/InstancedMesh 최적화.md --- diff --git a/01_Archive/2026-04-20/InstancedMesh.md b/01_Archive/2026-04-20/InstancedMesh.md index 72802184..247d0642 100644 --- a/01_Archive/2026-04-20/InstancedMesh.md +++ b/01_Archive/2026-04-20/InstancedMesh.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-354B99 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - InstancedMesh" --- -# [[InstancedMesh]] +# [[InstancedMesh|InstancedMesh]] ## 📌 한 줄 통찰 (The Karpathy Summary) > InstancedMesh는 동일한 기하학적 구조(Geometry)와 재질(Material)을 공유하는 수많은 객체를 단 한 번의 드로우 콜(Draw call)로 렌더링할 수 있게 해주는 특수 메쉬이다 [1, 2]. 각 인스턴스는 고유한 변환 행렬(위치, 회전, 축척)과 색상을 가질 수 있으며, 이를 통해 CPU 오버헤드를 획기적으로 줄이고 렌더링 성능을 향상시킨다 [2-4]. 나무, 풀, 바위와 같이 형태가 동일한 대규모 객체 군집을 렌더링할 때 주로 사용되며, 메모리 소비도 최소화할 수 있는 강력한 최적화 도구이다 [5-7]. @@ -28,11 +28,11 @@ github_commit: "[P-Reinforce] Continuous Worker - InstancedMesh" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Draw Call]], [[BatchedMesh]], [[Frustum Culling]], [[BufferGeometry]], [[Overdraw]] -- **Projects/Contexts:** [[Three.js]], [[WebGL]], [[InstancedMesh2]] +- **Related Topics:** [[Draw Call|Draw Call]], [[BatchedMesh|BatchedMesh]], [[Frustum Culling|Frustum Culling]], [[BufferGeometry|BufferGeometry]], [[Overdraw|Overdraw]] +- **Projects/Contexts:** [[Three.js|Three.js]], [[WebGL|WebGL]], [[InstancedMesh2|InstancedMesh2]] - **Contradictions/Notes:** InstancedMesh는 드로우 콜 횟수를 줄여 전반적인 성능을 높이기 위해 사용되지만, 자동 정렬의 부재 및 개별 인스턴스 컬링 불가 문제로 인해 극심한 오버드로우가 발생할 경우, 일반적인 Mesh(공유 속성 활용)를 사용할 때보다 오히려 프레임 레이트(FPS)가 급격히 저하되는 역설적인 병목 현상이 발생할 수 있다고 여러 소스에서 경고한다 [15, 17, 28, 29]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/InstancedMesh.md]] +- Raw Source: 00_Raw/2026-04-20/InstancedMesh.md --- diff --git a/01_Archive/2026-04-20/InstancedMesh2 library.md b/01_Archive/2026-04-20/InstancedMesh2 library.md index fbf16012..b1e7f302 100644 --- a/01_Archive/2026-04-20/InstancedMesh2 library.md +++ b/01_Archive/2026-04-20/InstancedMesh2 library.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-F5A361 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - InstancedMesh2 library" --- -# [[InstancedMesh2 library]] +# [[InstancedMesh2 library|InstancedMesh2 library]] ## 📌 한 줄 통찰 (The Karpathy Summary) > InstancedMesh2는 Three.js의 공식 InstancedMesh가 가진 한계를 극복하고 대규모 객체 렌더링을 최적화하기 위해 agargaro가 개발한 오픈 소스 확장 라이브러리입니다. 이 라이브러리는 개별 인스턴스 단위의 절두체 컬링(Frustum culling), 정렬(Sorting), 가시성 관리(Visibility management), LOD(Level of Detail), BVH를 활용한 빠른 레이캐스팅 및 스키닝(Skinning) 기능을 제공합니다 [1-3]. 특히 수만 개의 스킨드 메시나 개별 애니메이션을 가진 객체들을 최소한의 드로우 콜로 렌더링할 수 있도록 설계되어 높은 프레임 레이트 유지를 돕습니다 [1, 4, 5]. @@ -27,11 +27,11 @@ github_commit: "[P-Reinforce] Continuous Worker - InstancedMesh2 library" - **정책 변화:** AI 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[InstancedMesh]], [[Frustum Culling]], [[Level of Detail (LOD)]], [[Skinned Mesh]], [[BVH (Bounding Volume Hierarchy)]] -- **Projects/Contexts:** [[Three.js]] +- **Related Topics:** [[InstancedMesh|InstancedMesh]], [[Frustum Culling|Frustum Culling]], [[Level of Detail (LOD)|Level of Detail (LOD)]], [[SkinnedMesh|Skinned Mesh]], BVH (Bounding Volume Hierarchy) +- **Projects/Contexts:** [[Three.js|Three.js]] - **Contradictions/Notes:** 라이브러리 내에서 지원하는 `SquareDataTexture`의 뼈대 텍스처 부분 업데이트(Partial texture updates) 기능은 모바일 기기 및 Mozilla Firefox 브라우저 환경에서 속도가 느리게 작동할 수 있어, 특정 하드웨어나 브라우저에서는 이를 비활성화(또는 이중 버퍼링 구현 필요)해야 성능을 유지할 수 있습니다 [1, 11]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/InstancedMesh2 library.md]] +- Raw Source: 00_Raw/2026-04-20/InstancedMesh2 library.md --- diff --git a/01_Archive/2026-04-20/InstancedMesh2.md b/01_Archive/2026-04-20/InstancedMesh2.md index 32293ec3..80a9afbd 100644 --- a/01_Archive/2026-04-20/InstancedMesh2.md +++ b/01_Archive/2026-04-20/InstancedMesh2.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-0E2591 -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - InstancedMesh2" --- -# [[InstancedMesh2]] +# [[InstancedMesh2|InstancedMesh2]] ## 📌 한 줄 통찰 (The Karpathy Summary) > InstancedMesh2는 Three.js의 기본 `InstancedMesh`를 확장하여 성능과 기능을 대폭 강화한 오픈 소스 라이브러리이다 [1-3]. 이 라이브러리는 개별 인스턴스에 대한 절두체 컬링(Frustum culling), 공간 인덱스(BVH)를 이용한 빠른 레이캐스팅, 정렬(Sorting), 개별 가시성 관리 및 LOD 기능을 제공한다 [2-5]. 특히 기존 인스턴싱 기술로 처리하기 까다로웠던 개별 애니메이션 상태를 가진 스킨드 메쉬(Skinned Mesh)의 인스턴싱을 지원하여 대규모 3D 환경을 효율적으로 렌더링하는 데 활용된다 [1, 3, 6]. @@ -28,13 +28,13 @@ github_commit: "[P-Reinforce] Continuous Worker - InstancedMesh2" - **정책 변화:** Graphics & Performance 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[InstancedMesh]], [[Frustum culling]], [[BVH]], [[LOD]], [[SkinnedMesh]], [[BatchedMesh]] -- **Projects/Contexts:** [[agargaro의 오픈 소스 라이브러리]], [[20k skinned instances demo]] +- **Related Topics:** [[InstancedMesh|InstancedMesh]], [[Frustum Culling|Frustum culling]], [[BVH|BVH]], [[LOD|LOD]], [[SkinnedMesh|SkinnedMesh]], [[BatchedMesh|BatchedMesh]] +- **Projects/Contexts:** [[agargaro의 오픈 소스 라이브러리|agargaro의 오픈 소스 라이브러리]], [[20k skinned instances demo|20k skinned instances demo]] - **Contradictions/Notes:** - `SquareDataTexture`를 활용한 부분 업데이트 기능이 연속되지 않은 메모리 접근과 부가적인 함수 호출로 인해 CPU 오버헤드를 유발할 수 있다는 우려가 제기되었으나, 소수의 인스턴스만 변하는 상황에서는 상당한 대역폭 절약 효과가 있다고 라이브러리 개발자(@agargaro)가 반론했습니다 [8, 13, 14]. - 이러한 고급 기능들이 유용함에도 불구하고, Three.js의 메인 코어에 병합하기에는 내부 셰이더 변경과 기존 코드 호환성 파괴(Breaking changes) 등 유지보수 복잡성이 너무 커서 외부 라이브러리로 분리 개발되고 있습니다 [15, 16]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/InstancedMesh2.md]] +- Raw Source: 00_Raw/2026-04-20/InstancedMesh2.md --- diff --git a/01_Archive/2026-04-20/Instancing.md b/01_Archive/2026-04-20/Instancing.md index bac9d6dc..7ac0933b 100644 --- a/01_Archive/2026-04-20/Instancing.md +++ b/01_Archive/2026-04-20/Instancing.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-2752BF -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Instancing" --- -# [[Instancing]] +# [[Instancing|Instancing]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 인스턴싱(Instancing)은 웹 그래픽스 렌더링 및 UI 디자인 소프트웨어에서 성능을 최적화하기 위해 동일한 객체를 효율적으로 반복 처리하는 기법입니다. WebGL이나 WebGPU 환경에서는 단일 드로우 콜(draw call)로 동일한 메쉬나 형태를 대량으로 그려내어 CPU 및 GPU 오버헤드를 줄이는 핵심 기술로 사용됩니다 [1, 2]. 반면 Figma와 같은 디자인 도구에서는 원본 컴포넌트의 복제본을 의미하며, 인스턴스 내부의 구조적 최적화 여부가 소프트웨어 성능에 직접적인 영향을 미칩니다 [3, 4]. @@ -27,11 +27,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Instancing" - **정책 변화:** Graphics & Performance 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Draw Calls]], [[WebGL]], [[WebGPU]], [[Gaussian Splatting]] -- **Projects/Contexts:** [[Wonderland Engine]], [[WebSplatter]], [[Figma]] +- **Related Topics:** Draw Calls, [[WebGL|WebGL]], [[WebGPU|WebGPU]], Gaussian Splatting +- **Projects/Contexts:** [[Wonderland Engine|Wonderland Engine]], WebSplatter, [[Figma|Figma]] - **Contradictions/Notes:** 주어진 소스 데이터 내에서 '인스턴스(Instancing)'라는 용어는 3D 그래픽스 하드웨어 가속을 위한 렌더링 효율화 기법(WebGL/WebGPU)과, 디자인 도구 내에서 원본 객체를 복제해 사용하는 개체 단위(Figma)라는 두 가지 상이한 맥락에서 설명되고 있습니다. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Instancing.md]] +- Raw Source: 00_Raw/2026-04-20/Instancing.md --- diff --git a/01_Archive/2026-04-20/Instructional Systems Design (ISD).md b/01_Archive/2026-04-20/Instructional Systems Design (ISD).md index 3e2f5524..ef373747 100644 --- a/01_Archive/2026-04-20/Instructional Systems Design (ISD).md +++ b/01_Archive/2026-04-20/Instructional Systems Design (ISD).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-03221B -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Instructional Systems Design (ISD)" --- -# [[Instructional Systems Design (ISD)]] +# [[Instructional Systems Design (ISD)|Instructional Systems Design (ISD)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Instructional Systems Design ( ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Instructional Systems Design (ISD).md]] +- Raw Source: 00_Raw/2026-04-20/Instructional Systems Design (ISD).md --- diff --git a/01_Archive/2026-04-20/Instructional-Design.md b/01_Archive/2026-04-20/Instructional-Design.md index 748d8ae6..6765c7c3 100644 --- a/01_Archive/2026-04-20/Instructional-Design.md +++ b/01_Archive/2026-04-20/Instructional-Design.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-FFEC9C -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Instructional-Design" --- -# [[Instructional-Design]] +# [[Instructional-Design|Instructional-Design]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Instructional-Design" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Instructional-Design.md]] +- Raw Source: 00_Raw/2026-04-20/Instructional-Design.md --- diff --git a/01_Archive/2026-04-20/Integrated Gradients (통합 그래디언트).md b/01_Archive/2026-04-20/Integrated Gradients (통합 그래디언트).md index e05bc8ae..1a611c96 100644 --- a/01_Archive/2026-04-20/Integrated Gradients (통합 그래디언트).md +++ b/01_Archive/2026-04-20/Integrated Gradients (통합 그래디언트).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-904FDF -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Integrated Gradients (통합 그래디언트)" --- -# [[Integrated Gradients (통합 그래디언트)]] +# [[Integrated Gradients (통합 그래디언트)|Integrated Gradients (통합 그래디언트)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Integrated Gradients (통합 ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Integrated Gradients (통합 그래디언트).md]] +- Raw Source: 00_Raw/2026-04-20/Integrated Gradients (통합 그래디언트).md --- diff --git a/01_Archive/2026-04-20/Interaction to Next Paint (INP).md b/01_Archive/2026-04-20/Interaction to Next Paint (INP).md index dd6971da..63b018a5 100644 --- a/01_Archive/2026-04-20/Interaction to Next Paint (INP).md +++ b/01_Archive/2026-04-20/Interaction to Next Paint (INP).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-1BE349 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Interaction to Next Paint (INP)" --- -# [[Interaction to Next Paint (INP)]] +# [[Interaction to Next Paint (INP)|Interaction to Next Paint (INP)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > INP(Interaction to Next Paint)는 웹 페이지의 전반적인 상호작용성(Interactivity)과 응답성(Responsiveness)을 측정하기 위해 2024년 Google이 공식 도입한 Core Web Vitals 지표입니다 [1-3]. 첫 번째 상호작용만 측정하던 기존의 FID(First Input Delay)와 달리, 페이지 방문 기간 동안 발생하는 모든 상호작용(클릭, 탭, 키 누름 등)의 전체 지연 시간을 측정하여 실제 사용자 경험을 더 정확하게 반영합니다 [4-6]. 사용자의 작업에 대해 즉각적인 시각적 피드백을 제공하는 것을 목표로 하며, 200밀리초(ms) 이하의 지연 시간을 기록해야 '좋음(Good)'으로 평가받을 수 있습니다 [5, 7]. @@ -38,11 +38,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Interaction to Next Paint (INP - **정책 변화:** AI 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Core Web Vitals]], [[First Input Delay (FID)]], [[Long Animation Frames API]] -- **Projects/Contexts:** [[Chrome User Experience Report (CrUX)]], [[Chrome DevTools]], [[Interop 2025]] +- **Related Topics:** [[Core Web Vitals|Core Web Vitals]], [[First Input Delay (FID)|First Input Delay (FID)]], [[Long Animation Frames API|Long Animation Frames API]] +- **Projects/Contexts:** [[Chrome User Experience Report (CrUX)|Chrome User Experience Report (CrUX)]], [[Chrome DevTools|Chrome DevTools]], [[Interop 2025|Interop 2025]] - **Contradictions/Notes:** 초기 측정 방식에서는 모든 텍스트 강조 표시가 INP에 영향을 주었으나, 2025년 초 Chrome의 업데이트로 인해 스크롤을 동반하는 텍스트 강조 표시는 예외적으로 INP 지연 시간에 합산되지 않도록 변경되었습니다 [17]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Interaction to Next Paint (INP).md]] +- Raw Source: 00_Raw/2026-04-20/Interaction to Next Paint (INP).md --- diff --git a/01_Archive/2026-04-20/Interactive Fiction (IF).md b/01_Archive/2026-04-20/Interactive Fiction (IF).md index 4bc23701..b3ec06f9 100644 --- a/01_Archive/2026-04-20/Interactive Fiction (IF).md +++ b/01_Archive/2026-04-20/Interactive Fiction (IF).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-F4E42B -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Interactive Fiction (IF)" --- -# [[Interactive Fiction (IF)]] +# [[Interactive Fiction (IF)|Interactive Fiction (IF)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Interactive Fiction (IF)" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Interactive Fiction (IF).md]] +- Raw Source: 00_Raw/2026-04-20/Interactive Fiction (IF).md --- diff --git a/01_Archive/2026-04-20/Interactive Narrative.md b/01_Archive/2026-04-20/Interactive Narrative.md index edf66d25..7c6b9427 100644 --- a/01_Archive/2026-04-20/Interactive Narrative.md +++ b/01_Archive/2026-04-20/Interactive Narrative.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-270B9D -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Interactive Narrative" --- -# [[Interactive Narrative]] +# [[Interactive Narrative|Interactive Narrative]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Interactive Narrative" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Interactive Narrative.md]] +- Raw Source: 00_Raw/2026-04-20/Interactive Narrative.md --- diff --git a/01_Archive/2026-04-20/Interactive Storytelling.md b/01_Archive/2026-04-20/Interactive Storytelling.md index 97537aee..289808d7 100644 --- a/01_Archive/2026-04-20/Interactive Storytelling.md +++ b/01_Archive/2026-04-20/Interactive Storytelling.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-355ABB -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Interactive Storytelling" --- -# [[Interactive Storytelling]] +# [[Interactive Storytelling|Interactive Storytelling]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Interactive Storytelling" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Interactive Storytelling.md]] +- Raw Source: 00_Raw/2026-04-20/Interactive Storytelling.md --- diff --git a/01_Archive/2026-04-20/Interactive-Fiction-Tradition.md b/01_Archive/2026-04-20/Interactive-Fiction-Tradition.md index 229e1743..37702689 100644 --- a/01_Archive/2026-04-20/Interactive-Fiction-Tradition.md +++ b/01_Archive/2026-04-20/Interactive-Fiction-Tradition.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-FEC397 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Interactive-Fiction-Tradition" --- -# [[Interactive-Fiction-Tradition]] +# [[Interactive-Fiction-Tradition|Interactive-Fiction-Tradition]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Interactive-Fiction-Tradition" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Interactive-Fiction-Tradition.md]] +- Raw Source: 00_Raw/2026-04-20/Interactive-Fiction-Tradition.md --- diff --git a/01_Archive/2026-04-20/Interactive-Storytelling.md b/01_Archive/2026-04-20/Interactive-Storytelling.md index fc3b2718..2a07287e 100644 --- a/01_Archive/2026-04-20/Interactive-Storytelling.md +++ b/01_Archive/2026-04-20/Interactive-Storytelling.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-6D7369 -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Interactive-Storytelling" --- -# [[Interactive-Storytelling]] +# [[Interactive-Storytelling|Interactive-Storytelling]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Interactive-Storytelling" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Interactive-Storytelling.md]] +- Raw Source: 00_Raw/2026-04-20/Interactive-Storytelling.md --- diff --git a/01_Archive/2026-04-20/Interface Segregation Principle (ISP).md b/01_Archive/2026-04-20/Interface Segregation Principle (ISP).md index f9fd6316..b51961af 100644 --- a/01_Archive/2026-04-20/Interface Segregation Principle (ISP).md +++ b/01_Archive/2026-04-20/Interface Segregation Principle (ISP).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-317AB6 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Interface Segregation Principle (ISP)" --- -# [[Interface Segregation Principle (ISP)]] +# [[Interface Segregation Principle (ISP)|Interface Segregation Principle (ISP)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 인터페이스 분리 원칙(Interface Segregation Principle, ISP)은 클라이언트가 자신이 사용하지 않는 동작이나 액션에 의존하도록 강요받아서는 안 된다는 소프트웨어 설계 원칙입니다 [1, 2]. 이 원칙은 불필요한 기능까지 묶여 있는 방대한 '뚱뚱한(fat)' 인터페이스 대신, 목적이 뚜렷하고 초점이 맞춰진(focused) 인터페이스를 사용할 것을 권장합니다 [2]. 이를 통해 각 클라이언트는 정확히 필요한 기능에만 의존할 수 있으며, 불필요한 코드의 무게를 줄이고 테스트 및 업그레이드를 단순화할 수 있습니다 [3]. @@ -23,11 +23,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Interface Segregation Principl - **정책 변화:** Design & Experience 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[SOLID Design Principles]], [[Single Responsibility Principle (SRP)]], [[Facade Pattern]] -- **Projects/Contexts:** [[TypeScript/JavaScript Architecture]], [[Toss Front SDK]] +- **Related Topics:** SOLID Design Principles, [[Single Responsibility Principle (SRP)|Single Responsibility Principle (SRP)]], [[Facade Pattern (퍼사드 패턴)|Facade Pattern]] +- **Projects/Contexts:** TypeScript/JavaScript Architecture, [[Toss Front SDK 기반 외부 연동사 플러그인 개발 생태계 구축|Toss Front SDK]] - **Contradictions/Notes:** 소스 내에 ISP에 반대되는 주장은 없습니다. 추가적인 참고 사항으로, 소스는 인터페이스에 여러 도메인 동사가 존재할 경우 이를 분리하는 기준으로 삼으라고 조언합니다 [3]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/Interface Segregation Principle (ISP).md]] +- Raw Source: 00_Raw/2026-04-20/Interface Segregation Principle (ISP).md --- diff --git a/01_Archive/2026-04-20/Interface Segregation Principle.md b/01_Archive/2026-04-20/Interface Segregation Principle.md index 25db9f4d..6950763c 100644 --- a/01_Archive/2026-04-20/Interface Segregation Principle.md +++ b/01_Archive/2026-04-20/Interface Segregation Principle.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-6A25D0 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Interface Segregation Principle" --- -# [[Interface Segregation Principle]] +# [[Interface Segregation Principle|Interface Segregation Principle]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Interface Segregation Principl ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Interface Segregation Principle.md]] +- Raw Source: 00_Raw/2026-04-20/Interface Segregation Principle.md --- diff --git a/01_Archive/2026-04-20/Interface-Extension-vs-Augmentation.md b/01_Archive/2026-04-20/Interface-Extension-vs-Augmentation.md index bd19cde5..c834bf14 100644 --- a/01_Archive/2026-04-20/Interface-Extension-vs-Augmentation.md +++ b/01_Archive/2026-04-20/Interface-Extension-vs-Augmentation.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-326071 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Interface-Extension-vs-Augmentation" --- -# [[Interface-Extension-vs-Augmentation]] +# [[Interface-Extension-vs-Augmentation|Interface-Extension-vs-Augmentation]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Interface-Extension-vs-Augment ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Interface-Extension-vs-Augmentation.md]] +- Raw Source: 00_Raw/2026-04-20/Interface-Extension-vs-Augmentation.md --- diff --git a/01_Archive/2026-04-20/Interface-Extension.md b/01_Archive/2026-04-20/Interface-Extension.md index 7559ba4f..1fd993a3 100644 --- a/01_Archive/2026-04-20/Interface-Extension.md +++ b/01_Archive/2026-04-20/Interface-Extension.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-B72832 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Interface-Extension" --- -# [[Interface-Extension]] +# [[Interface-Extension|Interface-Extension]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Interface-Extension" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Interface-Extension.md]] +- Raw Source: 00_Raw/2026-04-20/Interface-Extension.md --- diff --git a/01_Archive/2026-04-20/Interface-Merging.md b/01_Archive/2026-04-20/Interface-Merging.md index 1e53551f..513a1f3c 100644 --- a/01_Archive/2026-04-20/Interface-Merging.md +++ b/01_Archive/2026-04-20/Interface-Merging.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-223BC6 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Interface-Merging" --- -# [[Interface-Merging]] +# [[Interface-Merging|Interface-Merging]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Interface-Merging" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Interface-Merging.md]] +- Raw Source: 00_Raw/2026-04-20/Interface-Merging.md --- diff --git a/01_Archive/2026-04-20/Interface-Segregation-Principle-in-TS.md b/01_Archive/2026-04-20/Interface-Segregation-Principle-in-TS.md index 7f867bc2..806fe715 100644 --- a/01_Archive/2026-04-20/Interface-Segregation-Principle-in-TS.md +++ b/01_Archive/2026-04-20/Interface-Segregation-Principle-in-TS.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-D46100 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Interface-Segregation-Principle-in-TS" --- -# [[Interface-Segregation-Principle-in-TS]] +# [[Interface-Segregation-Principle-in-TS|Interface-Segregation-Principle-in-TS]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Interface-Segregation-Principl ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Interface-Segregation-Principle-in-TS.md]] +- Raw Source: 00_Raw/2026-04-20/Interface-Segregation-Principle-in-TS.md --- diff --git a/01_Archive/2026-04-20/Interface-Segregation-Principle-in-TypeScript.md b/01_Archive/2026-04-20/Interface-Segregation-Principle-in-TypeScript.md index e34c754e..91bb95c8 100644 --- a/01_Archive/2026-04-20/Interface-Segregation-Principle-in-TypeScript.md +++ b/01_Archive/2026-04-20/Interface-Segregation-Principle-in-TypeScript.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-44AA84 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Interface-Segregation-Principle-in-TypeScript" --- -# [[Interface-Segregation-Principle-in-TypeScript]] +# [[Interface-Segregation-Principle-in-TypeScript|Interface-Segregation-Principle-in-TypeScript]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Interface-Segregation-Principl ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Interface-Segregation-Principle-in-TypeScript.md]] +- Raw Source: 00_Raw/2026-04-20/Interface-Segregation-Principle-in-TypeScript.md --- diff --git a/01_Archive/2026-04-20/Interface-Segregation-Principle.md b/01_Archive/2026-04-20/Interface-Segregation-Principle.md index 813b7a85..db9e1654 100644 --- a/01_Archive/2026-04-20/Interface-Segregation-Principle.md +++ b/01_Archive/2026-04-20/Interface-Segregation-Principle.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-92EBE7 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Interface-Segregation-Principle" --- -# [[Interface-Segregation-Principle]] +# [[Interface-Segregation-Principle|Interface-Segregation-Principle]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Interface-Segregation-Principl ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Interface-Segregation-Principle.md]] +- Raw Source: 00_Raw/2026-04-20/Interface-Segregation-Principle.md --- diff --git a/01_Archive/2026-04-20/Internet of Things (IoT) Telemetry.md b/01_Archive/2026-04-20/Internet of Things (IoT) Telemetry.md index c56e6eb5..10e19a80 100644 --- a/01_Archive/2026-04-20/Internet of Things (IoT) Telemetry.md +++ b/01_Archive/2026-04-20/Internet of Things (IoT) Telemetry.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-D09D7C -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Internet of Things (IoT) Telemetry" --- -# [[Internet of Things (IoT) Telemetry]] +# [[Internet of Things (IoT) Telemetry|Internet of Things (IoT) Telemetry]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Internet of Things (IoT) Telem ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Internet of Things (IoT) Telemetry.md]] +- Raw Source: 00_Raw/2026-04-20/Internet of Things (IoT) Telemetry.md --- diff --git a/01_Archive/2026-04-20/Interop 2025.md b/01_Archive/2026-04-20/Interop 2025.md index c51f586d..93d401b9 100644 --- a/01_Archive/2026-04-20/Interop 2025.md +++ b/01_Archive/2026-04-20/Interop 2025.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-48DB08 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Interop 2025" --- -# [[Interop 2025]] +# [[Interop 2025|Interop 2025]] ## 📌 한 줄 통찰 (The Karpathy Summary) > Interop 2025는 주로 Chrome에 국한되어 있던 핵심 웹 지표(Core Web Vitals)를 다른 주요 웹 브라우저로 확대 지원하여 호환성을 높이기 위해 시작된 프로젝트입니다[1]. 이 프로젝트를 통해 Firefox와 Safari 같은 브라우저들이 특정 웹 성능 지표에 대한 지원 및 구현 작업을 본격적으로 시작하게 되었습니다[1]. 이를 통해 다양한 브라우저 환경에서 웹 성능을 일관되게 측정할 수 있는 기반이 마련되기 시작했습니다. @@ -22,11 +22,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Interop 2025" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Core Web Vitals]], [[Largest Contentful Paint]], [[Interaction to Next Paint]], [[Cumulative Layout Shift]] -- **Projects/Contexts:** [[Interop 2026]] +- **Related Topics:** [[Core Web Vitals|Core Web Vitals]], Largest Contentful Paint, Interaction to Next Paint, Cumulative Layout Shift +- **Projects/Contexts:** [[Interop 2026|Interop 2026]] - **Contradictions/Notes:** 소스에 관련 정보가 부족합니다. (특별한 모순이나 상충하는 의견은 발견되지 않음) --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Interop 2025.md]] +- Raw Source: 00_Raw/2026-04-20/Interop 2025.md --- diff --git a/01_Archive/2026-04-20/Interop 2026.md b/01_Archive/2026-04-20/Interop 2026.md index 40fb29f5..3e379253 100644 --- a/01_Archive/2026-04-20/Interop 2026.md +++ b/01_Archive/2026-04-20/Interop 2026.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-36D047 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Interop 2026" --- -# [[Interop 2026]] +# [[Interop 2026|Interop 2026]] ## 📌 한 줄 통찰 (The Karpathy Summary) > Interop 2026은 웹 브라우저 간 코어 웹 바이탈(Core Web Vitals) 지원을 표준화하기 위한 후속 프로젝트로 언급된 제안입니다 [1]. 특히 파이어폭스(Firefox)나 사파리(Safari) 등에서 아직 지원이 계획되지 않은 누적 레이아웃 이동(Cumulative Layout Shift, CLS) 지표를 포함하기 위한 목적으로 제안되고 있습니다 [1]. @@ -22,11 +22,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Interop 2026" - **정책 변화:** AI 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Core Web Vitals]], [[Cumulative Layout Shift]], [[Interop 2025]] -- **Projects/Contexts:** [[크로스 브라우저 코어 웹 바이탈 지원 (Cross-browser support for Core Web Vitals)]] +- **Related Topics:** [[Core Web Vitals|Core Web Vitals]], Cumulative Layout Shift, [[Interop 2025|Interop 2025]] +- **Projects/Contexts:** 크로스 브라우저 코어 웹 바이탈 지원 (Cross-browser support for Core Web Vitals) - **Contradictions/Notes:** 소스 내에서 Interop 2026은 확정된 프로젝트가 아니라 CLS 지표를 향후에 지원하기 위해 고려 중인 '제안' 단계로만 매우 짧게 언급되어 있습니다 [1]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Interop 2026.md]] +- Raw Source: 00_Raw/2026-04-20/Interop 2026.md --- diff --git a/01_Archive/2026-04-20/Interoperability Standards.md b/01_Archive/2026-04-20/Interoperability Standards.md index 14469852..dbd556e9 100644 --- a/01_Archive/2026-04-20/Interoperability Standards.md +++ b/01_Archive/2026-04-20/Interoperability Standards.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-3EE866 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Interoperability Standards" --- -# [[Interoperability Standards]] +# [[Interoperability Standards|Interoperability Standards]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Interoperability Standards" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Interoperability Standards.md]] +- Raw Source: 00_Raw/2026-04-20/Interoperability Standards.md --- diff --git a/01_Archive/2026-04-20/Interpolation and Extrapolation.md b/01_Archive/2026-04-20/Interpolation and Extrapolation.md index 74fdb579..ce721af1 100644 --- a/01_Archive/2026-04-20/Interpolation and Extrapolation.md +++ b/01_Archive/2026-04-20/Interpolation and Extrapolation.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-C3D464 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Interpolation and Extrapolation" --- -# [[Interpolation and Extrapolation]] +# [[Interpolation and Extrapolation|Interpolation and Extrapolation]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Interpolation and Extrapolatio ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Interpolation and Extrapolation.md]] +- Raw Source: 00_Raw/2026-04-20/Interpolation and Extrapolation.md --- diff --git a/01_Archive/2026-04-20/Intersection-Types-vs-Interface-Extension.md b/01_Archive/2026-04-20/Intersection-Types-vs-Interface-Extension.md index 2cabab52..fd44f5c3 100644 --- a/01_Archive/2026-04-20/Intersection-Types-vs-Interface-Extension.md +++ b/01_Archive/2026-04-20/Intersection-Types-vs-Interface-Extension.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-94C8CB -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Intersection-Types-vs-Interface-Extension" --- -# [[Intersection-Types-vs-Interface-Extension]] +# [[Intersection-Types-vs-Interface-Extension|Intersection-Types-vs-Interface-Extension]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Intersection-Types-vs-Interfac ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Intersection-Types-vs-Interface-Extension.md]] +- Raw Source: 00_Raw/2026-04-20/Intersection-Types-vs-Interface-Extension.md --- diff --git a/01_Archive/2026-04-20/Intrinsic Motivation.md b/01_Archive/2026-04-20/Intrinsic Motivation.md index f55c0518..c4b9b8d2 100644 --- a/01_Archive/2026-04-20/Intrinsic Motivation.md +++ b/01_Archive/2026-04-20/Intrinsic Motivation.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-D1BB71 -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Intrinsic Motivation" --- -# [[Intrinsic Motivation]] +# [[Intrinsic Motivation|Intrinsic Motivation]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Intrinsic Motivation" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Intrinsic Motivation.md]] +- Raw Source: 00_Raw/2026-04-20/Intrinsic Motivation.md --- diff --git a/01_Archive/2026-04-20/Intrinsic-Motivation.md b/01_Archive/2026-04-20/Intrinsic-Motivation.md index 5b33f6c7..2940784b 100644 --- a/01_Archive/2026-04-20/Intrinsic-Motivation.md +++ b/01_Archive/2026-04-20/Intrinsic-Motivation.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-8559CD -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Intrinsic-Motivation" --- -# [[Intrinsic-Motivation]] +# [[Intrinsic-Motivation|Intrinsic-Motivation]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Intrinsic-Motivation" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Intrinsic-Motivation.md]] +- Raw Source: 00_Raw/2026-04-20/Intrinsic-Motivation.md --- diff --git a/01_Archive/2026-04-20/Inventory Management Example.md b/01_Archive/2026-04-20/Inventory Management Example.md index 62ab4e05..9e28c4ab 100644 --- a/01_Archive/2026-04-20/Inventory Management Example.md +++ b/01_Archive/2026-04-20/Inventory Management Example.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-9C355C -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Inventory Management Example" --- -# [[Inventory Management Example]] +# [[Inventory Management Example|Inventory Management Example]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 이 주제는 프론트엔드 모델과 백엔드 응답 간의 데이터 변환 시 발생할 수 있는 타입 불일치 문제를 보여주는 실제 사례입니다. 인벤토리 관리 시스템에서 백엔드의 데이터 형식과 프론트엔드의 정의된 타입 구조가 다를 때 발생할 수 있는 매핑 오류의 위험성을 다룹니다. TypeScript의 `satisfies` 키워드를 사용하여 엄격한 속성 검사를 강제함으로써 오타나 원치 않는 초과 필드의 포함을 방지하는 방법을 설명합니다. @@ -22,11 +22,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Inventory Management Example" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[satisfies Keyword]], [[Excess Property Checking]], [[Type Casting]] -- **Projects/Contexts:** [[Frontend-Backend Data Transformation]] +- **Related Topics:** [[satisfies Keyword|satisfies Keyword]], [[Excess Property Checking|Excess Property Checking]], [[Type Casting|Type Casting]] +- **Projects/Contexts:** Frontend-Backend Data Transformation - **Contradictions/Notes:** 소스는 데이터 변환 시 `as` 키워드를 사용한 타입 캐스팅에 의존하는 것을 경고합니다. 타입 캐스팅은 초과 속성 검사를 우회하여 조용한 오류(silent errors)와 의도치 않은 동작을 유발할 수 있으므로, 엄격한 계약을 강제하기 위해서는 `satisfies`를 사용하는 것이 더 안전합니다 [3, 4]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/Inventory Management Example.md]] +- Raw Source: 00_Raw/2026-04-20/Inventory Management Example.md --- diff --git a/01_Archive/2026-04-20/Inverse-Kinematics.md b/01_Archive/2026-04-20/Inverse-Kinematics.md index f0b3e550..e6f4d33a 100644 --- a/01_Archive/2026-04-20/Inverse-Kinematics.md +++ b/01_Archive/2026-04-20/Inverse-Kinematics.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-67139B -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Inverse-Kinematics" --- -# [[Inverse-Kinematics]] +# [[Inverse-Kinematics|Inverse-Kinematics]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Inverse-Kinematics" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Inverse-Kinematics.md]] +- Raw Source: 00_Raw/2026-04-20/Inverse-Kinematics.md --- diff --git a/01_Archive/2026-04-20/InversifyJS.md b/01_Archive/2026-04-20/InversifyJS.md index 265e6032..f1297838 100644 --- a/01_Archive/2026-04-20/InversifyJS.md +++ b/01_Archive/2026-04-20/InversifyJS.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-020B35 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - InversifyJS" --- -# [[InversifyJS]] +# [[InversifyJS|InversifyJS]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - InversifyJS" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/InversifyJS.md]] +- Raw Source: 00_Raw/2026-04-20/InversifyJS.md --- diff --git a/01_Archive/2026-04-20/IoT.md b/01_Archive/2026-04-20/IoT.md index 87d8b658..6a3d7244 100644 --- a/01_Archive/2026-04-20/IoT.md +++ b/01_Archive/2026-04-20/IoT.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-002 -category: "[[10_Wiki/💡 Topics/Automation]]" +category: "10_Wiki/💡 Topics/Automation" confidence_score: 0.91 tags: [automation, iot, telemetry, connectivity] last_reinforced: 2026-04-20 github_commit: "batch-reinforce-07" --- -# [[Internet of Things (IoT) Telemetry]] +# [[Internet of Things (IoT) Telemetry|Internet of Things (IoT) Telemetry]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 보이지 않는 물리 현상을 디지털 신호로 변환하여 네트워크로 송출함으로써 만물에 '말문'을 틔워주는 기술. @@ -24,6 +24,6 @@ github_commit: "batch-reinforce-07" - **정책 변화:** 구조적 연결성(w2) 관점에서 Digital_Twin의 실시간성을 보장하는 핵심 인프라로 정의. ## 🔗 지식 연결 (Graph) -- **Parent:** [[10_Wiki/💡 Topics/Automation]] -- **Related:** [[SCADA]], [[Digital_Twin]], [[Edge-Computing]] -- **Raw Source:** [[00_Raw/2026-04-20/Internet of Things (IoT) Telemetry.md]] +- **Parent:** 10_Wiki/💡 Topics/Automation +- **Related:** [[SCADA|SCADA]], [[Digital_Twin|Digital_Twin]], [[Edge-Computing|Edge-Computing]] +- **Raw Source:** 00_Raw/2026-04-20/Internet of Things (IoT) Telemetry.md diff --git a/01_Archive/2026-04-20/Irrational Games.md b/01_Archive/2026-04-20/Irrational Games.md index 7a13e8c6..594095e3 100644 --- a/01_Archive/2026-04-20/Irrational Games.md +++ b/01_Archive/2026-04-20/Irrational Games.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-8F0A9E -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Irrational Games" --- -# [[Irrational Games]] +# [[Irrational Games|Irrational Games]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Irrational Games" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Irrational Games.md]] +- Raw Source: 00_Raw/2026-04-20/Irrational Games.md --- diff --git a/01_Archive/2026-04-20/Isovist-Analysis.md b/01_Archive/2026-04-20/Isovist-Analysis.md index f39d7da2..eca0d367 100644 --- a/01_Archive/2026-04-20/Isovist-Analysis.md +++ b/01_Archive/2026-04-20/Isovist-Analysis.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-4BC607 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Isovist-Analysis" --- -# [[Isovist-Analysis]] +# [[Isovist-Analysis|Isovist-Analysis]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Isovist-Analysis" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Isovist-Analysis.md]] +- Raw Source: 00_Raw/2026-04-20/Isovist-Analysis.md --- diff --git a/01_Archive/2026-04-20/Itô Calculus.md b/01_Archive/2026-04-20/Itô Calculus.md index afa98168..7964e7ea 100644 --- a/01_Archive/2026-04-20/Itô Calculus.md +++ b/01_Archive/2026-04-20/Itô Calculus.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-D65DD9 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Itô Calculus" --- -# [[Itô Calculus]] +# [[Itô Calculus|Itô Calculus]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Itô Calculus" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Itô Calculus.md]] +- Raw Source: 00_Raw/2026-04-20/Itô Calculus.md --- diff --git a/01_Archive/2026-04-20/J-curve S-curve (AI 발전의 동학).md b/01_Archive/2026-04-20/J-curve S-curve (AI 발전의 동학).md index 7f1bbded..14a989a4 100644 --- a/01_Archive/2026-04-20/J-curve S-curve (AI 발전의 동학).md +++ b/01_Archive/2026-04-20/J-curve S-curve (AI 발전의 동학).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-25FEC6 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - J-curve S-curve (AI 발전의 동학)" --- -# [[J-curve S-curve (AI 발전의 동학)]] +# [[J-curve S-curve (AI 발전의 동학)|J-curve S-curve (AI 발전의 동학)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - J-curve S-curve (AI 발전의 ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/J-curve & S-curve (AI 발전의 동학).md]] +- Raw Source: 00_Raw/2026-04-20/J-curve & S-curve (AI 발전의 동학).md --- diff --git a/01_Archive/2026-04-20/J-curve & S-curve (AI 발전의 동학).md b/01_Archive/2026-04-20/J-curve & S-curve (AI 발전의 동학).md index 55561c12..e37ce565 100644 --- a/01_Archive/2026-04-20/J-curve & S-curve (AI 발전의 동학).md +++ b/01_Archive/2026-04-20/J-curve & S-curve (AI 발전의 동학).md @@ -1,4 +1,4 @@ -[[J-curve & S-curve (AI 발전의 동학)]] +[[J-curve & S-curve (AI 발전의 동학)|J-curve & S-curve (AI 발전의 동학)]] 📌 Brief Summary @@ -64,8 +64,8 @@ J-curve와 S-curve는 기술 발전의 궤적을 설명하는 두 가지 핵심 🔗 Knowledge Connections -- [[창발 능력 (Emergent Abilities)]], [[Scaling Laws (스케일링 법칙)]], [[Phase Transition (위상 변이)]], [[Model Collapse (모델 붕괴 현상)]], [[Test-Time Compute Scaling (추론 시간 계산 스케일링)]] -- **Projects/Contexts:** [[AI 투자 및 기술 로드맵 수립]] +- [[창발 능력 (Emergent Abilities)|창발 능력 (Emergent Abilities)]], Scaling Laws (스케일링 법칙), [[Phase Transition (위상 변이)|Phase Transition (위상 변이)]], [[Model Collapse (모델 붕괴 현상)|Model Collapse (모델 붕괴 현상)]], [[Test-Time Compute Scaling (추론 시간 계산 스케일링)|Test-Time Compute Scaling (추론 시간 계산 스케일링)]] +- **Projects/Contexts:** AI 투자 및 기술 로드맵 수립 - **Contradictions/Notes:** - J-curve가 영원할 것이라는 낙관론(Singularity)과 곧 S-curve의 한계에 부딪힐 것이라는 비관론이 팽팽히 맞섬. - 실제 발전은 아주 작은 S-curve들이 계단식으로 연결된 모습에 가까움. diff --git a/01_Archive/2026-04-20/JPEG XL.md b/01_Archive/2026-04-20/JPEG XL.md index f5361b72..ee2324b1 100644 --- a/01_Archive/2026-04-20/JPEG XL.md +++ b/01_Archive/2026-04-20/JPEG XL.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-EC8C7D -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - JPEG XL" --- -# [[JPEG XL]] +# [[JPEG XL|JPEG XL]] ## 📌 한 줄 통찰 (The Karpathy Summary) > JPEG XL은 웹 페이지의 전체 용량을 줄이고 사용자 경험에 부정적인 영향 없이 웹사이트 속도를 높이기 위해 설계된 최신 이미지 포맷이다 [1, 2]. Apple이 2023년에 지원을 시작했고, Mozilla와 Google 등 주요 브라우저 벤더들도 도입에 긍정적인 방향으로 입장을 선회하면서 점차 지원이 확대될 가능성을 보이고 있다 [2, 3]. 기존 이미지 포맷에 비해 동일 품질 대비 더 작은 파일 크기, 빠른 인코딩, 점진적 디코딩 등의 우수한 기술적 이점을 제공한다 [4]. @@ -31,11 +31,11 @@ github_commit: "[P-Reinforce] Continuous Worker - JPEG XL" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[AVIF]], [[WebP]] -- **Projects/Contexts:** [[Web Performance]], [[Google Chrome Browser Support]] +- **Related Topics:** AVIF, WebP +- **Projects/Contexts:** [[웹 성능 가이드(Web Performance)|Web Performance]], Google Chrome Browser Support - **Contradictions/Notes:** 구글은 2022년 10월에 "생태계의 관심 부족"을 이유로 JPEG XL 지원 코드를 제거했으나, 3년 뒤인 2025년 11월에는 "개발자들의 지속적인 관심"을 이유로 크롬 지원에 반대하지 않는다고 입장을 전환했다 [2, 3]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/JPEG XL.md]] +- Raw Source: 00_Raw/2026-04-20/JPEG XL.md --- diff --git a/01_Archive/2026-04-20/JSON-Schema-Validation.md b/01_Archive/2026-04-20/JSON-Schema-Validation.md index d5d37219..8bc5ef32 100644 --- a/01_Archive/2026-04-20/JSON-Schema-Validation.md +++ b/01_Archive/2026-04-20/JSON-Schema-Validation.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-6A507C -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - JSON-Schema-Validation" --- -# [[JSON-Schema-Validation]] +# [[JSON-Schema-Validation|JSON-Schema-Validation]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - JSON-Schema-Validation" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/JSON-Schema-Validation.md]] +- Raw Source: 00_Raw/2026-04-20/JSON-Schema-Validation.md --- diff --git a/01_Archive/2026-04-20/JSON-Schema.md b/01_Archive/2026-04-20/JSON-Schema.md index 3210abfd..4357cda7 100644 --- a/01_Archive/2026-04-20/JSON-Schema.md +++ b/01_Archive/2026-04-20/JSON-Schema.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-CF1F59 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - JSON-Schema" --- -# [[JSON-Schema]] +# [[JSON-Schema|JSON-Schema]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - JSON-Schema" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/JSON-Schema.md]] +- Raw Source: 00_Raw/2026-04-20/JSON-Schema.md --- diff --git a/01_Archive/2026-04-20/Jacobian-Matrix-Analysis.md b/01_Archive/2026-04-20/Jacobian-Matrix-Analysis.md index f8586d57..509b8c76 100644 --- a/01_Archive/2026-04-20/Jacobian-Matrix-Analysis.md +++ b/01_Archive/2026-04-20/Jacobian-Matrix-Analysis.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-BC322B -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Jacobian-Matrix-Analysis" --- -# [[Jacobian-Matrix-Analysis]] +# [[Jacobian-Matrix-Analysis|Jacobian-Matrix-Analysis]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Jacobian-Matrix-Analysis" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Jacobian-Matrix-Analysis.md]] +- Raw Source: 00_Raw/2026-04-20/Jacobian-Matrix-Analysis.md --- diff --git a/01_Archive/2026-04-20/Jailbreaking (탈옥).md b/01_Archive/2026-04-20/Jailbreaking (탈옥).md index 4955b91d..5a172d99 100644 --- a/01_Archive/2026-04-20/Jailbreaking (탈옥).md +++ b/01_Archive/2026-04-20/Jailbreaking (탈옥).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-C6F5E9 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Jailbreaking (탈옥)" --- -# [[Jailbreaking (탈옥)]] +# [[Jailbreaking (탈옥)|Jailbreaking (탈옥)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Jailbreaking (탈옥)" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Jailbreaking (탈옥).md]] +- Raw Source: 00_Raw/2026-04-20/Jailbreaking (탈옥).md --- diff --git a/01_Archive/2026-04-20/JavaScript 메모리 관리(JavaScript Memory Management).md b/01_Archive/2026-04-20/JavaScript 메모리 관리(JavaScript Memory Management).md index c645897b..ad0808db 100644 --- a/01_Archive/2026-04-20/JavaScript 메모리 관리(JavaScript Memory Management).md +++ b/01_Archive/2026-04-20/JavaScript 메모리 관리(JavaScript Memory Management).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-AABE4C -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - JavaScript 메모리 관리(JavaScript Memory Management)" --- -# [[JavaScript 메모리 관리(JavaScript Memory Management)]] +# [[JavaScript 메모리 관리(JavaScript Memory Management)|JavaScript 메모리 관리(JavaScript Memory Management)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -38,11 +38,11 @@ V8 엔진은 주로 두 가지 가비지 컬렉터를 사용하여 메모리를 - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Garbage Collection (가비지 컬렉션)]], [[V8 Engine (V8 엔진)]], [[Generational Hypothesis (세대 가설)]], [[Memory Leak (메모리 누수)]] -- **Projects/Contexts:** [[Chrome DevTools 메모리 분석]], [[Node.js 메모리 튜닝]] +- **Related Topics:** [[Garbage Collection(가비지 컬렉션)|Garbage Collection (가비지 컬렉션)]], V8 Engine (V8 엔진), Generational Hypothesis (세대 가설), [[Memory Leak(메모리 누수)|Memory Leak (메모리 누수)]] +- **Projects/Contexts:** Chrome DevTools 메모리 분석, [[Node.js 메모리 튜닝|Node.js 메모리 튜닝]] - **Contradictions/Notes:** 가비지 컬렉션을 사용하는 언어는 메모리 관리의 복잡성을 크게 줄여주지만, 프로그래머가 메모리 제어권을 완전히 상실하게 된다는 단점이 있습니다 [1, 43]. 또한 GC 실행 시 불규칙한 일시 정지 현상이 발생해 대화형 시스템에 영향을 줄 수 있으며 [43], 64비트 플랫폼에서 V8 힙은 포인터 압축(Pointer Compression) 보안 기술로 인해 4GB의 크기 제한(V8 Memory Cage)을 갖는 특징이 있습니다 [44-46]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/JavaScript 메모리 관리(JavaScript Memory Management).md]] +- Raw Source: 00_Raw/2026-04-20/JavaScript 메모리 관리(JavaScript Memory Management).md --- diff --git a/01_Archive/2026-04-20/JavaScript.md b/01_Archive/2026-04-20/JavaScript.md index 1bf25931..705347de 100644 --- a/01_Archive/2026-04-20/JavaScript.md +++ b/01_Archive/2026-04-20/JavaScript.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-4A99EB -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - JavaScript" --- -# [[JavaScript]] +# [[JavaScript|JavaScript]] ## 📌 한 줄 통찰 (The Karpathy Summary) > JavaScript는 단일 페이지 애플리케이션을 구축하고 WebGL, WebGPU와 같은 웹 브라우저 API를 제어하는 데 사용되는 핵심 스크립팅 언어입니다 [1, 2]. 애플리케이션 로직, 이벤트 처리 및 데이터 준비에 필수적이지만, 브라우저의 메인 스레드에서 무거운 JavaScript를 실행하거나 가비지 컬렉션이 발생하면 심각한 성능 병목 현상이 생길 수 있습니다 [3-5]. 따라서 최근의 웹 성능 최적화는 JavaScript 페이로드를 줄이고, 실행 시간을 분할하며, 무거운 연산을 GPU로 오프로드하는 방향으로 발전하고 있습니다 [6, 7]. @@ -22,11 +22,11 @@ github_commit: "[P-Reinforce] Continuous Worker - JavaScript" - **정책 변화:** Graphics & Performance 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** `[[WebGL]]`, `[[WebGPU]]`, `[[Interaction to Next Paint (INP)]]`, `[[Garbage Collection]]`, `[[Chrome DevTools]]` -- **Projects/Contexts:** `[[Three.js]]`, `[[웹 그래픽 성능 최적화(Web Graphics Performance Optimization)]]` +- **Related Topics:** `[[WebGL|WebGL]]`, `[[WebGPU|WebGPU]]`, `[[Interaction to Next Paint (INP)|Interaction to Next Paint (INP)]]`, `[[Garbage Collection|Garbage Collection]]`, `[[Chrome DevTools|Chrome DevTools]]` +- **Projects/Contexts:** `[[Three.js|Three.js]]`, `웹 그래픽 성능 최적화(Web Graphics Performance Optimization)` - **Contradictions/Notes:** WebGL을 구동하기 위해 JavaScript는 필수적이지만, CPU 측의 JavaScript 실행 및 상태 유효성 검사 오버헤드가 오히려 렌더링 성능을 제한하는 가장 큰 병목으로 작용합니다. 이로 인해 3D 렌더링 산업은 JavaScript의 개입을 줄이고 GPU의 병렬 연산을 극대화할 수 있는 WebGPU로 빠르게 전환하는 추세입니다 [5, 6, 13]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/JavaScript.md]] +- Raw Source: 00_Raw/2026-04-20/JavaScript.md --- diff --git a/01_Archive/2026-04-20/JavaScriptCore.md b/01_Archive/2026-04-20/JavaScriptCore.md index 924655f3..51c0c078 100644 --- a/01_Archive/2026-04-20/JavaScriptCore.md +++ b/01_Archive/2026-04-20/JavaScriptCore.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-1AF373 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - JavaScriptCore" --- -# [[JavaScriptCore]] +# [[JavaScriptCore|JavaScriptCore]] ## 📌 한 줄 통찰 (The Karpathy Summary) > JavaScriptCore는 WebKit의 JavaScript 엔진으로, 신뢰할 수 없는 JavaScript나 WebAssembly 코드를 실행할 때 호스트 프로세스의 메모리 유출을 방지하도록 설계된 안전한 언어 가상 머신(secure language virtual machine)입니다 [1, 2]. 최근 Spectre 공격으로 인해 기존의 분기(branch) 기반 보안 속성이 무력화되는 위협을 받았으며, 이를 방어하기 위한 구조적 보안 개선이 이루어지고 있습니다 [1, 3]. @@ -23,11 +23,11 @@ github_commit: "[P-Reinforce] Continuous Worker - JavaScriptCore" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[WebKit]], [[Spectre]], [[WebAssembly]], [[Speculative execution]], [[Pointer poisoning]] -- **Projects/Contexts:** [[WebKit's Spectre and Meltdown Mitigations]] +- **Related Topics:** [[WebKit|WebKit]], [[Spectre|Spectre]], [[WebAssembly|WebAssembly]], [[Speculative Execution|Speculative execution]], [[Pointer Poisoning|Pointer poisoning]] +- **Projects/Contexts:** WebKit's Spectre and Meltdown Mitigations - **Contradictions/Notes:** 소스에 관련 정보가 부족합니다. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/JavaScriptCore.md]] +- Raw Source: 00_Raw/2026-04-20/JavaScriptCore.md --- diff --git a/01_Archive/2026-04-20/Jenkins.md b/01_Archive/2026-04-20/Jenkins.md index c5bcd1bd..0ecb94af 100644 --- a/01_Archive/2026-04-20/Jenkins.md +++ b/01_Archive/2026-04-20/Jenkins.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-937A74 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Jenkins" --- -# [[Jenkins]] +# [[Jenkins|Jenkins]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -22,11 +22,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Jenkins" - **정책 변화:** AI 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[SonarQube]], [[CI/CD Pipelines]], [[Endor Labs]] -- **Projects/Contexts:** [[Automated Code Review]], [[Software Supply Chain Security]] +- **Related Topics:** [[SonarQube|SonarQube]], CI/CD Pipelines, Endor Labs +- **Projects/Contexts:** Automated Code Review, Software Supply Chain Security - **Contradictions/Notes:** 소스에 관련 정보가 부족합니다. 소스 문헌들은 Jenkins의 단독적인 기능이나 특성을 설명하지 않으며, 오직 다른 코드 분석/보안 도구(SonarQube, Endor Labs)가 연동할 수 있는 CI/CD 플랫폼의 예시로만 언급하고 있습니다. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Jenkins.md]] +- Raw Source: 00_Raw/2026-04-20/Jenkins.md --- diff --git a/01_Archive/2026-04-20/Joern.md b/01_Archive/2026-04-20/Joern.md index fdce5bd7..d6b617aa 100644 --- a/01_Archive/2026-04-20/Joern.md +++ b/01_Archive/2026-04-20/Joern.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-A0754B -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Joern" --- -# [[Joern]] +# [[Joern|Joern]] ## 📌 한 줄 통찰 (The Karpathy Summary) > Joern은 디컴파일된 소스 코드를 파싱(parse)하는 데 사용되는 도구입니다 [1]. 프로그램 바이너리의 작성자를 식별(Authorship Attribution)하기 위한 연구 과정에서 분석에 필요한 AST(추상 구문 트리) 기반의 특징을 추출하는 목적으로 활용되었습니다 [1]. 제공된 소스에는 이 외의 목적이나 기능 등 Joern에 대한 구체적인 관련 정보가 부족합니다. @@ -23,11 +23,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Joern" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[AST(Abstract Syntax Tree)]], [[Authorship Attribution]] -- **Projects/Contexts:** [[Caliskan-Islam 등의 프로그램 바이너리 작성자 식별 연구]] +- **Related Topics:** [[AST(Abstract Syntax Tree)|AST(Abstract Syntax Tree)]], [[Authorship Attribution|Authorship Attribution]] +- **Projects/Contexts:** [[Caliskan-Islam 등의 프로그램 바이너리 작성자 식별 연구|Caliskan-Islam 등의 프로그램 바이너리 작성자 식별 연구]] - **Contradictions/Notes:** 소스에 관련 정보가 부족합니다. Joern 자체의 상세한 구조나 추가적인 기능에 대해서는 소스 내에 언급된 바가 없으며, 디컴파일된 코드를 파싱하는 도구로서 단 1회 언급되었습니다. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/Joern.md]] +- Raw Source: 00_Raw/2026-04-20/Joern.md --- diff --git a/01_Archive/2026-04-20/K-12-EdTech.md b/01_Archive/2026-04-20/K-12-EdTech.md index 31527647..636232f2 100644 --- a/01_Archive/2026-04-20/K-12-EdTech.md +++ b/01_Archive/2026-04-20/K-12-EdTech.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-5653C7 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - K-12-EdTech" --- -# [[K-12-EdTech]] +# [[K-12-EdTech|K-12-EdTech]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - K-12-EdTech" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/K-12-EdTech.md]] +- Raw Source: 00_Raw/2026-04-20/K-12-EdTech.md --- diff --git a/01_Archive/2026-04-20/KTO (Kahneman-Tversky Optimization).md b/01_Archive/2026-04-20/KTO (Kahneman-Tversky Optimization).md index 6b3f793b..4ae44e4f 100644 --- a/01_Archive/2026-04-20/KTO (Kahneman-Tversky Optimization).md +++ b/01_Archive/2026-04-20/KTO (Kahneman-Tversky Optimization).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-085B91 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - KTO (Kahneman-Tversky Optimization)" --- -# [[KTO (Kahneman-Tversky Optimization)]] +# [[KTO (Kahneman-Tversky Optimization)|KTO (Kahneman-Tversky Optimization)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - KTO (Kahneman-Tversky Optimiza ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/KTO (Kahneman-Tversky Optimization).md]] +- Raw Source: 00_Raw/2026-04-20/KTO (Kahneman-Tversky Optimization).md --- diff --git a/01_Archive/2026-04-20/Ken Levine-Design-Philosophy.md b/01_Archive/2026-04-20/Ken Levine-Design-Philosophy.md index 2fe2f556..3e521a5c 100644 --- a/01_Archive/2026-04-20/Ken Levine-Design-Philosophy.md +++ b/01_Archive/2026-04-20/Ken Levine-Design-Philosophy.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-DE50FF -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Ken Levine-Design-Philosophy" --- -# [[Ken Levine-Design-Philosophy]] +# [[Ken Levine-Design-Philosophy|Ken Levine-Design-Philosophy]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Ken Levine-Design-Philosophy" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Ken Levine-Design-Philosophy.md]] +- Raw Source: 00_Raw/2026-04-20/Ken Levine-Design-Philosophy.md --- diff --git a/01_Archive/2026-04-20/Keyof-Operator.md b/01_Archive/2026-04-20/Keyof-Operator.md index 663515f1..526634fc 100644 --- a/01_Archive/2026-04-20/Keyof-Operator.md +++ b/01_Archive/2026-04-20/Keyof-Operator.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-D5D6DC -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Keyof-Operator" --- -# [[Keyof-Operator]] +# [[Keyof-Operator|Keyof-Operator]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Keyof-Operator" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Keyof-Operator.md]] +- Raw Source: 00_Raw/2026-04-20/Keyof-Operator.md --- diff --git a/01_Archive/2026-04-20/Kinematic-Modeling.md b/01_Archive/2026-04-20/Kinematic-Modeling.md index 8ba31616..5ca7f43d 100644 --- a/01_Archive/2026-04-20/Kinematic-Modeling.md +++ b/01_Archive/2026-04-20/Kinematic-Modeling.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-47456C -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Kinematic-Modeling" --- -# [[Kinematic-Modeling]] +# [[Kinematic-Modeling|Kinematic-Modeling]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Kinematic-Modeling" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Kinematic-Modeling.md]] +- Raw Source: 00_Raw/2026-04-20/Kinematic-Modeling.md --- diff --git a/01_Archive/2026-04-20/Kinematics.md b/01_Archive/2026-04-20/Kinematics.md index 48a676db..2318e1e0 100644 --- a/01_Archive/2026-04-20/Kinematics.md +++ b/01_Archive/2026-04-20/Kinematics.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-CC099B -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Kinematics" --- -# [[Kinematics]] +# [[Kinematics|Kinematics]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Kinematics" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Kinematics.md]] +- Raw Source: 00_Raw/2026-04-20/Kinematics.md --- diff --git a/01_Archive/2026-04-20/Kinetics.md b/01_Archive/2026-04-20/Kinetics.md index 94ecba11..873ac190 100644 --- a/01_Archive/2026-04-20/Kinetics.md +++ b/01_Archive/2026-04-20/Kinetics.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-11AAD0 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Kinetics" --- -# [[Kinetics]] +# [[Kinetics|Kinetics]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Kinetics" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Kinetics.md]] +- Raw Source: 00_Raw/2026-04-20/Kinetics.md --- diff --git a/01_Archive/2026-04-20/Knowledge-Graph-Construction.md b/01_Archive/2026-04-20/Knowledge-Graph-Construction.md index 4398c9ea..12885f40 100644 --- a/01_Archive/2026-04-20/Knowledge-Graph-Construction.md +++ b/01_Archive/2026-04-20/Knowledge-Graph-Construction.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-84AB19 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Knowledge-Graph-Construction" --- -# [[Knowledge-Graph-Construction]] +# [[Knowledge-Graph-Construction|Knowledge-Graph-Construction]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Knowledge-Graph-Construction" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Knowledge-Graph-Construction.md]] +- Raw Source: 00_Raw/2026-04-20/Knowledge-Graph-Construction.md --- diff --git a/01_Archive/2026-04-20/Knowledge-Graphs.md b/01_Archive/2026-04-20/Knowledge-Graphs.md index cca80eb8..a2916c87 100644 --- a/01_Archive/2026-04-20/Knowledge-Graphs.md +++ b/01_Archive/2026-04-20/Knowledge-Graphs.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-9FC608 -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Knowledge-Graphs" --- -# [[Knowledge-Graphs]] +# [[Knowledge-Graphs|Knowledge-Graphs]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Knowledge-Graphs" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Knowledge-Graphs.md]] +- Raw Source: 00_Raw/2026-04-20/Knowledge-Graphs.md --- diff --git a/01_Archive/2026-04-20/Knowledge-Representation-in-AI.md b/01_Archive/2026-04-20/Knowledge-Representation-in-AI.md index 1c7c05a2..81c780d9 100644 --- a/01_Archive/2026-04-20/Knowledge-Representation-in-AI.md +++ b/01_Archive/2026-04-20/Knowledge-Representation-in-AI.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-F03CAF -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Knowledge-Representation-in-AI" --- -# [[Knowledge-Representation-in-AI]] +# [[Knowledge-Representation-in-AI|Knowledge-Representation-in-AI]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Knowledge-Representation-in-AI ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Knowledge-Representation-in-AI.md]] +- Raw Source: 00_Raw/2026-04-20/Knowledge-Representation-in-AI.md --- diff --git a/01_Archive/2026-04-20/L-Systems.md b/01_Archive/2026-04-20/L-Systems.md index b36bfa16..82747d00 100644 --- a/01_Archive/2026-04-20/L-Systems.md +++ b/01_Archive/2026-04-20/L-Systems.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-EBE0D0 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - L-Systems" --- -# [[L-Systems]] +# [[L-Systems|L-Systems]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - L-Systems" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/L-Systems.md]] +- Raw Source: 00_Raw/2026-04-20/L-Systems.md --- diff --git a/01_Archive/2026-04-20/L-systems in Biology.md b/01_Archive/2026-04-20/L-systems in Biology.md index db08aed1..33bbcc21 100644 --- a/01_Archive/2026-04-20/L-systems in Biology.md +++ b/01_Archive/2026-04-20/L-systems in Biology.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-5DB108 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - L-systems in Biology" --- -# [[L-systems in Biology]] +# [[L-systems in Biology|L-systems in Biology]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - L-systems in Biology" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/L-systems in Biology.md]] +- Raw Source: 00_Raw/2026-04-20/L-systems in Biology.md --- diff --git a/01_Archive/2026-04-20/LCS (League of Legends Championship Series).md b/01_Archive/2026-04-20/LCS (League of Legends Championship Series).md index ba3c96f8..c5826b61 100644 --- a/01_Archive/2026-04-20/LCS (League of Legends Championship Series).md +++ b/01_Archive/2026-04-20/LCS (League of Legends Championship Series).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-FC3F77 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - LCS (League of Legends Championship Series)" --- -# [[LCS (League of Legends Championship Series)]] +# [[LCS (League of Legends Championship Series)|LCS (League of Legends Championship Series)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - LCS (League of Legends Champio ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/LCS (League of Legends Championship Series).md]] +- Raw Source: 00_Raw/2026-04-20/LCS (League of Legends Championship Series).md --- diff --git a/01_Archive/2026-04-20/LLM Alignment (LLM 정렬).md b/01_Archive/2026-04-20/LLM Alignment (LLM 정렬).md index da75e1fd..69b3a35b 100644 --- a/01_Archive/2026-04-20/LLM Alignment (LLM 정렬).md +++ b/01_Archive/2026-04-20/LLM Alignment (LLM 정렬).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-E3A7CD -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - LLM Alignment (LLM 정렬)" --- -# [[LLM Alignment (LLM 정렬)]] +# [[LLM Alignment (LLM 정렬)|LLM Alignment (LLM 정렬)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - LLM Alignment (LLM 정렬)" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/LLM Alignment (LLM 정렬).md]] +- Raw Source: 00_Raw/2026-04-20/LLM Alignment (LLM 정렬).md --- diff --git a/01_Archive/2026-04-20/LLM Hallucination (언어 모델 환각).md b/01_Archive/2026-04-20/LLM Hallucination (언어 모델 환각).md index f5717e5c..b3c38005 100644 --- a/01_Archive/2026-04-20/LLM Hallucination (언어 모델 환각).md +++ b/01_Archive/2026-04-20/LLM Hallucination (언어 모델 환각).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-3DFBCC -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - LLM Hallucination (언어 모델 환각)" --- -# [[LLM Hallucination (언어 모델 환각)]] +# [[LLM Hallucination (언어 모델 환각)|LLM Hallucination (언어 모델 환각)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - LLM Hallucination (언어 모 ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/LLM Hallucination (언어 모델 환각).md]] +- Raw Source: 00_Raw/2026-04-20/LLM Hallucination (언어 모델 환각).md --- diff --git a/01_Archive/2026-04-20/LLM.md b/01_Archive/2026-04-20/LLM.md index 3aae01a2..3fca4c5a 100644 --- a/01_Archive/2026-04-20/LLM.md +++ b/01_Archive/2026-04-20/LLM.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-D415E3 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - LLM" --- -# [[LLM]] +# [[LLM|LLM]] ## 📌 한 줄 통찰 (The Karpathy Summary) > LLM(대규모 언어 모델)은 코드의 문맥과 의미를 이해하고, 인간이 놓칠 수 있는 복잡한 패턴을 감지하며 더욱 정교한 피드백을 제공하는 데 활용되는 인공지능 기술입니다 [1, 2]. 기존의 단순 규칙 기반 정적 분석 도구와 달리, LLM은 코드 컨텍스트와 비즈니스 로직의 결함을 파악하고 맥락에 맞는 자동 수정(AutoFix) 제안을 생성하는 데 강력한 성능을 보여줍니다 [3-5]. 현대 소프트웨어 개발 환경에서 LLM은 코드 복잡도 분석, 보안 취약점 탐지, 그리고 상용구(boilerplate) 코드 작성 등의 작업에 폭넓게 도입되어 개발자의 전반적인 생산성을 향상시키고 있습니다 [2, 6, 7]. @@ -27,11 +27,11 @@ github_commit: "[P-Reinforce] Continuous Worker - LLM" - **정책 변화:** AI 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[SAST]], [[Static Analysis]], [[AI Code Review]] -- **Projects/Contexts:** [[Corgea]], [[GitHub Copilot]], [[Snyk Code]], [[DeepCode AI]] +- **Related Topics:** [[SAST|SAST]], [[정적 분석(Static Analysis)|Static Analysis]], AI Code Review +- **Projects/Contexts:** [[Corgea|Corgea]], GitHub Copilot, Snyk Code, [[DeepCode AI|DeepCode AI]] - **Contradictions/Notes:** 대다수의 개발자들은 LLM이 반복적인 상용구 코드 작성을 줄여주고 낯선 도메인에서의 작업 효율을 크게 향상시킨다고 긍정적으로 평가하지만 [6, 13, 19], 반대로 대규모의 복잡한 레거시 코드베이스나 이전에 해결된 적 없는 새로운 문제(Frontier)에서는 LLM의 효과가 무의미해지며, 잦은 환각(Hallucination)이나 미세한 오류로 인해 오히려 심각한 디버깅 시간을 낭비하게 만든다고 강력히 반대(또는 경계)하는 의견도 존재합니다 [14, 20-22]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/LLM.md]] +- Raw Source: 00_Raw/2026-04-20/LLM.md --- diff --git a/01_Archive/2026-04-20/LOD.md b/01_Archive/2026-04-20/LOD.md index 1fdc6ae3..cc88e263 100644 --- a/01_Archive/2026-04-20/LOD.md +++ b/01_Archive/2026-04-20/LOD.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-D34DEB -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - LOD" --- -# [[LOD]] +# [[LOD|LOD]] ## 📌 한 줄 통찰 (The Karpathy Summary) > LOD(Level of Detail)는 카메라와의 거리에 따라 고해상도(High-poly) 모델을 저해상도(Low-poly) 버전으로 동적으로 교체하여 렌더링 성능을 향상시키는 기법이다 [1, 2]. 대규모 3D 씬에서 먼 거리에 있는 객체의 기하학적 복잡도를 극적으로 낮추거나 단순한 평면(Impostor)으로 대체하여 불필요한 GPU 연산을 방지한다 [2, 3]. 이 시스템을 적절히 활용하면 프레임 속도 안정화에 기여하고 전체 씬의 폴리곤 수 및 GPU 처리량을 획기적으로 줄일 수 있다 [1, 4]. @@ -23,11 +23,11 @@ github_commit: "[P-Reinforce] Continuous Worker - LOD" - **정책 변화:** AI 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Frustum Culling]], [[Billboard impostors]], [[InstancedMesh]], [[Draw Calls]], [[Mipmaps]] -- **Projects/Contexts:** [[Three.js]], [[React Three Fiber]] (Drei 라이브러리의 `` 컴포넌트 [1]), [[InstancedMesh2]], [[CAD Rendering]] +- **Related Topics:** [[Frustum Culling|Frustum Culling]], [[빌보드 임포스터(Billboard Impostors)|Billboard impostors]], [[InstancedMesh|InstancedMesh]], Draw Calls, Mipmaps +- **Projects/Contexts:** [[Three.js|Three.js]], React Three Fiber (Drei 라이브러리의 `` 컴포넌트 [1]), [[InstancedMesh2|InstancedMesh2]], CAD Rendering - **Contradictions/Notes:** 소스에 따르면 LOD는 거리에 따라 렌더링 부하를 줄여주는 강력한 툴이지만, 런타임에 지오메트리 버전을 동적으로 연산하여 생성하려는 시도는 오히려 큰 성능 저하를 초래할 수 있으므로 상황(정적 자산 중심)에 맞게 적용해야 한다고 지적한다 [16-18]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/LOD.md]] +- Raw Source: 00_Raw/2026-04-20/LOD.md --- diff --git a/01_Archive/2026-04-20/Labeled Property Graph (LPG 속성 그래프).md b/01_Archive/2026-04-20/Labeled Property Graph (LPG 속성 그래프).md index 09da7ab3..2121cb81 100644 --- a/01_Archive/2026-04-20/Labeled Property Graph (LPG 속성 그래프).md +++ b/01_Archive/2026-04-20/Labeled Property Graph (LPG 속성 그래프).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-84C8D8 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Labeled Property Graph (LPG 속성 그래프)" --- -# [[Labeled Property Graph (LPG 속성 그래프)]] +# [[Labeled Property Graph (LPG 속성 그래프)|Labeled Property Graph (LPG 속성 그래프)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Labeled Property Graph (LPG ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Labeled Property Graph (LPG, 속성 그래프).md]] +- Raw Source: 00_Raw/2026-04-20/Labeled Property Graph (LPG, 속성 그래프).md --- diff --git a/01_Archive/2026-04-20/Labeled Property Graph (LPG, 속성 그래프).md b/01_Archive/2026-04-20/Labeled Property Graph (LPG, 속성 그래프).md index 520041bb..957e6743 100644 --- a/01_Archive/2026-04-20/Labeled Property Graph (LPG, 속성 그래프).md +++ b/01_Archive/2026-04-20/Labeled Property Graph (LPG, 속성 그래프).md @@ -1,4 +1,4 @@ -[[Labeled Property Graph (LPG, 속성 그래프)]] +[[Labeled Property Graph (LPG, 속성 그래프)|Labeled Property Graph (LPG, 속성 그래프)]] 📌 Brief Summary @@ -89,8 +89,8 @@ Join 연산 성능 병목 원천 제거 🔗 Knowledge Connections -- **Related Topics:** [[RDF와 OWL]], [[지식 그래프 (Knowledge Graph)]], [[GraphRAG (그래프 기반 검색 증강 생성)]], [[SPARQL (RDF 그래프 질의 언어)]], [[Cypher 질의 언어]], [[Neo4j]], [[Index-free Adjacency]], [[RDF-star (RDF*)]] -- **Projects/Contexts:** [[온톨로지 지식 베이스]], [[실시간 그래프 분석 시스템]] +- **Related Topics:** [[RDF와 OWL|RDF와 OWL]], [[지식 그래프 (Knowledge Graph)|지식 그래프 (Knowledge Graph)]], [[GraphRAG (그래프 기반 검색 증강 생성)|GraphRAG (그래프 기반 검색 증강 생성)]], [[SPARQL (RDF 그래프 질의 언어)|SPARQL (RDF 그래프 질의 언어)]], Cypher 질의 언어, Neo4j, Index-free Adjacency, [[RDF-star (RDF 확장 사양)|RDF-star (RDF*)]] +- **Projects/Contexts:** [[온톨로지 지식 베이스|온톨로지 지식 베이스]], 실시간 그래프 분석 시스템 - **Contradictions/Notes:** - LPG(Neo4j)는 성능·유연성 우위, RDF는 표준·상호운용성 우위 → 도메인에 따라 선택. - RDF-star가 등장하면서 RDF도 엣지 속성 부여 가능해짐 → LPG 고유 장점 경계가 좁아지는 추세. diff --git a/01_Archive/2026-04-20/Language-Acquisition-Apps.md b/01_Archive/2026-04-20/Language-Acquisition-Apps.md index dd8ed69d..60c37e86 100644 --- a/01_Archive/2026-04-20/Language-Acquisition-Apps.md +++ b/01_Archive/2026-04-20/Language-Acquisition-Apps.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-6239D3 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Language-Acquisition-Apps" --- -# [[Language-Acquisition-Apps]] +# [[Language-Acquisition-Apps|Language-Acquisition-Apps]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Language-Acquisition-Apps" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Language-Acquisition-Apps.md]] +- Raw Source: 00_Raw/2026-04-20/Language-Acquisition-Apps.md --- diff --git a/01_Archive/2026-04-20/Large-Scale-Enterprise-Frontend-Architectures.md b/01_Archive/2026-04-20/Large-Scale-Enterprise-Frontend-Architectures.md index bdf8d42a..298e2072 100644 --- a/01_Archive/2026-04-20/Large-Scale-Enterprise-Frontend-Architectures.md +++ b/01_Archive/2026-04-20/Large-Scale-Enterprise-Frontend-Architectures.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-69DDE6 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Large-Scale-Enterprise-Frontend-Architectures" --- -# [[Large-Scale-Enterprise-Frontend-Architectures]] +# [[Large-Scale-Enterprise-Frontend-Architectures|Large-Scale-Enterprise-Frontend-Architectures]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Large-Scale-Enterprise-Fronten ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Large-Scale-Enterprise-Frontend-Architectures.md]] +- Raw Source: 00_Raw/2026-04-20/Large-Scale-Enterprise-Frontend-Architectures.md --- diff --git a/01_Archive/2026-04-20/Large-Scale-Knowledge-Integration.md b/01_Archive/2026-04-20/Large-Scale-Knowledge-Integration.md index c56c0fba..efed71a6 100644 --- a/01_Archive/2026-04-20/Large-Scale-Knowledge-Integration.md +++ b/01_Archive/2026-04-20/Large-Scale-Knowledge-Integration.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-E04C5A -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Large-Scale-Knowledge-Integration" --- -# [[Large-Scale-Knowledge-Integration]] +# [[Large-Scale-Knowledge-Integration|Large-Scale-Knowledge-Integration]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Large-Scale-Knowledge-Integrat ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Large-Scale-Knowledge-Integration.md]] +- Raw Source: 00_Raw/2026-04-20/Large-Scale-Knowledge-Integration.md --- diff --git a/01_Archive/2026-04-20/Large-scale-Frontend-Architecture.md b/01_Archive/2026-04-20/Large-scale-Frontend-Architecture.md index b689d7b5..5747f2de 100644 --- a/01_Archive/2026-04-20/Large-scale-Frontend-Architecture.md +++ b/01_Archive/2026-04-20/Large-scale-Frontend-Architecture.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-06FE72 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Large-scale-Frontend-Architecture" --- -# [[Large-scale-Frontend-Architecture]] +# [[Large-scale-Frontend-Architecture|Large-scale-Frontend-Architecture]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Large-scale-Frontend-Architect ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Large-scale-Frontend-Architecture.md]] +- Raw Source: 00_Raw/2026-04-20/Large-scale-Frontend-Architecture.md --- diff --git a/01_Archive/2026-04-20/Large-scale-TypeScript-Monorepos.md b/01_Archive/2026-04-20/Large-scale-TypeScript-Monorepos.md index 3f3c1e1c..eebfdda3 100644 --- a/01_Archive/2026-04-20/Large-scale-TypeScript-Monorepos.md +++ b/01_Archive/2026-04-20/Large-scale-TypeScript-Monorepos.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-EE05DB -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Large-scale-TypeScript-Monorepos" --- -# [[Large-scale-TypeScript-Monorepos]] +# [[Large-scale-TypeScript-Monorepos|Large-scale-TypeScript-Monorepos]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Large-scale-TypeScript-Monorep ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Large-scale-TypeScript-Monorepos.md]] +- Raw Source: 00_Raw/2026-04-20/Large-scale-TypeScript-Monorepos.md --- diff --git a/01_Archive/2026-04-20/Largest Contentful Paint (LCP).md b/01_Archive/2026-04-20/Largest Contentful Paint (LCP).md index 3a9ea31d..d7a00471 100644 --- a/01_Archive/2026-04-20/Largest Contentful Paint (LCP).md +++ b/01_Archive/2026-04-20/Largest Contentful Paint (LCP).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-C57B92 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Largest Contentful Paint (LCP)" --- -# [[Largest Contentful Paint (LCP)]] +# [[Largest Contentful Paint (LCP)|Largest Contentful Paint (LCP)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > LCP(Largest Contentful Paint)는 웹 페이지의 로딩 성능을 측정하는 구글의 핵심 웹 바이탈(Core Web Vitals) 지표 중 하나로, 브라우저가 화면에 가장 큰 콘텐츠를 렌더링하는 데 걸리는 시간을 의미합니다 [1, 2]. 이는 사용자가 페이지의 주요 콘텐츠를 볼 수 있게 되는 시점을 나타내는 대리 지표로 사용됩니다 [2]. 구글은 좋은 사용자 경험을 위해 LCP를 2.5초 미만으로 유지할 것을 권장하며, 4.0초를 초과하면 불량한 것으로 간주합니다 [3, 4]. @@ -28,11 +28,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Largest Contentful Paint (LCP) - **정책 변화:** AI 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Core Web Vitals]], [[Chrome User Experience Report (CrUX)]], [[Interaction to Next Paint (INP)]], [[Cumulative Layout Shift (CLS)]], [[Soft Navigation]] -- **Projects/Contexts:** [[Interop 2025]], [[Chrome DevTools]], [[Lighthouse]] +- **Related Topics:** [[Core Web Vitals|Core Web Vitals]], [[Chrome User Experience Report (CrUX)|Chrome User Experience Report (CrUX)]], [[Interaction to Next Paint (INP)|Interaction to Next Paint (INP)]], [[Cumulative Layout Shift (CLS)|Cumulative Layout Shift (CLS)]], [[Soft Navigation|Soft Navigation]] +- **Projects/Contexts:** [[Interop 2025|Interop 2025]], [[Chrome DevTools|Chrome DevTools]], [[Lighthouse|Lighthouse]] - **Contradictions/Notes:** 소스에 따르면 현재 LCP 지표는 웹 사이트의 초기 네비게이션(initial navigation)에 대한 로드 시간만을 측정하기 때문에, URL 변경 시 전체 새로고침이 일어나지 않는 Soft Navigation 기반의 단일 페이지 애플리케이션(SPA) 운영자와 개발자에게는 성능 분석에 상당한 사각지대가 발생한다는 한계가 지적됩니다 [17]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Largest Contentful Paint (LCP).md]] +- Raw Source: 00_Raw/2026-04-20/Largest Contentful Paint (LCP).md --- diff --git a/01_Archive/2026-04-20/Latio.tech Report.md b/01_Archive/2026-04-20/Latio.tech Report.md index ae04693c..0dc660af 100644 --- a/01_Archive/2026-04-20/Latio.tech Report.md +++ b/01_Archive/2026-04-20/Latio.tech Report.md @@ -1,4 +1,4 @@ -# [[Latio.tech Report]] +# [[Latio.tech Report|Latio.tech Report]] ## 📌 Brief 정요 Latio.tech Report는 시장에 출시된 정적 애플리케이션 보안 테스트(SAST) 및 자동 수정(auto-fixing) 도구들의 성능을 평가한 독립적인 분석 보고서입니다 [1]. 이 보고서는 특정 도구들이 개발자 워크플로우 내에서 얼마나 실용적으로 코드 수정안을 생성할 수 있는지를 중점적으로 다루었습니다 [1, 2]. 다만 주어진 소스에는 이 보고서에 대한 단편적인 인용만 존재하여 전반적인 정보가 크게 부족합니다. @@ -12,8 +12,8 @@ Latio.tech Report는 시장에 출시된 정적 애플리케이션 보안 테스 *소스에 관련 정보가 부족합니다.* ## 🔗 Knowledge Connections -- **Related Topics:** [[Corgea]], [[Snyk Code]], [[Auto-fixing Tool]] -- **Projects/Contexts:** [[SAST Tools Evaluation]] +- **Related Topics:** [[Corgea|Corgea]], Snyk Code, Auto-fixing Tool +- **Projects/Contexts:** SAST Tools Evaluation - **Contradictions/Notes:** 제공된 소스에는 'Latio.tech Report'가 Corgea와 Snyk를 평가한 내용 중 극히 일부만 언급되어 있으며, 평가 기준이나 다른 벤더에 대한 정보 등 전체적인 맥락을 파악하기에는 소스에 관련 정보가 부족합니다. --- diff --git a/01_Archive/2026-04-20/Latiotech Report.md b/01_Archive/2026-04-20/Latiotech Report.md index f4dd4589..e22816a6 100644 --- a/01_Archive/2026-04-20/Latiotech Report.md +++ b/01_Archive/2026-04-20/Latiotech Report.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-B2FE12 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Latiotech Report" --- -# [[Latiotech Report]] +# [[Latiotech Report|Latiotech Report]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -25,11 +25,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Latiotech Report" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Corgea]], [[Snyk Code]], [[Auto-fixing Tool]] -- **Projects/Contexts:** [[SAST Tools Evaluation]] +- **Related Topics:** [[Corgea|Corgea]], Snyk Code, Auto-fixing Tool +- **Projects/Contexts:** SAST Tools Evaluation - **Contradictions/Notes:** 제공된 소스에는 'Latio.tech Report'가 Corgea와 Snyk를 평가한 내용 중 극히 일부만 언급되어 있으며, 평가 기준이나 다른 벤더에 대한 정보 등 전체적인 맥락을 파악하기에는 소스에 관련 정보가 부족합니다. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Latio.tech Report.md]] +- Raw Source: 00_Raw/2026-04-20/Latio.tech Report.md --- diff --git a/01_Archive/2026-04-20/Lean-UX.md b/01_Archive/2026-04-20/Lean-UX.md index 7c2198ad..3895f867 100644 --- a/01_Archive/2026-04-20/Lean-UX.md +++ b/01_Archive/2026-04-20/Lean-UX.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-D3F181 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Lean-UX" --- -# [[Lean-UX]] +# [[Lean-UX|Lean-UX]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Lean-UX" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Lean-UX.md]] +- Raw Source: 00_Raw/2026-04-20/Lean-UX.md --- diff --git a/01_Archive/2026-04-20/Lerna-Legacy-Management.md b/01_Archive/2026-04-20/Lerna-Legacy-Management.md index 40550359..3205fb9c 100644 --- a/01_Archive/2026-04-20/Lerna-Legacy-Management.md +++ b/01_Archive/2026-04-20/Lerna-Legacy-Management.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-0CDF64 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Lerna-Legacy-Management" --- -# [[Lerna-Legacy-Management]] +# [[Lerna-Legacy-Management|Lerna-Legacy-Management]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Lerna-Legacy-Management" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Lerna-Legacy-Management.md]] +- Raw Source: 00_Raw/2026-04-20/Lerna-Legacy-Management.md --- diff --git a/01_Archive/2026-04-20/Level Design Architecture.md b/01_Archive/2026-04-20/Level Design Architecture.md index fdf64fe0..62b96293 100644 --- a/01_Archive/2026-04-20/Level Design Architecture.md +++ b/01_Archive/2026-04-20/Level Design Architecture.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-E822FE -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Level Design Architecture" --- -# [[Level Design Architecture]] +# [[Level Design Architecture|Level Design Architecture]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Level Design Architecture" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Level Design Architecture.md]] +- Raw Source: 00_Raw/2026-04-20/Level Design Architecture.md --- diff --git a/01_Archive/2026-04-20/Level Design Automation.md b/01_Archive/2026-04-20/Level Design Automation.md index fa042bad..2d9528e6 100644 --- a/01_Archive/2026-04-20/Level Design Automation.md +++ b/01_Archive/2026-04-20/Level Design Automation.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-1A2A10 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Level Design Automation" --- -# [[Level Design Automation]] +# [[Level Design Automation|Level Design Automation]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Level Design Automation" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Level Design Automation.md]] +- Raw Source: 00_Raw/2026-04-20/Level Design Automation.md --- diff --git a/01_Archive/2026-04-20/Level Design Theory.md b/01_Archive/2026-04-20/Level Design Theory.md index c8bdb402..1f84dd43 100644 --- a/01_Archive/2026-04-20/Level Design Theory.md +++ b/01_Archive/2026-04-20/Level Design Theory.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-9BB940 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Level Design Theory" --- -# [[Level Design Theory]] +# [[Level Design Theory|Level Design Theory]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Level Design Theory" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Level Design Theory.md]] +- Raw Source: 00_Raw/2026-04-20/Level Design Theory.md --- diff --git a/01_Archive/2026-04-20/Level of Detail (LOD).md b/01_Archive/2026-04-20/Level of Detail (LOD).md index 3e2cb83b..ec8e207a 100644 --- a/01_Archive/2026-04-20/Level of Detail (LOD).md +++ b/01_Archive/2026-04-20/Level of Detail (LOD).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-B9CF3B -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Level of Detail (LOD)" --- -# [[Level of Detail (LOD)]] +# [[Level of Detail (LOD)|Level of Detail (LOD)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > LOD(Level of Detail)는 카메라와의 거리에 따라 객체의 기하학적 복잡도(폴리곤 수)를 동적으로 조절하여 렌더링 성능을 최적화하는 기법입니다 [1-3]. 가까운 객체에는 고해상도(High-poly) 모델을 보여주고, 멀리 있는 객체는 저해상도(Low-poly) 모델이나 단순한 평면(Impostor)으로 교체하여 GPU 연산량을 줄입니다 [1, 2, 4, 5]. 이를 통해 화면의 시각적 품질을 유지하면서도 대규모 씬의 프레임 속도를 크게 개선할 수 있습니다 [6, 7]. @@ -25,11 +25,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Level of Detail (LOD)" - **정책 변화:** AI 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Draw Calls]], [[Impostor]], [[InstancedMesh]], [[Frustum Culling]], [[Mipmaps]] -- **Projects/Contexts:** [[Three.js]], [[React Three Fiber]], [[InstancedMesh2]] +- **Related Topics:** Draw Calls, Impostor, [[InstancedMesh|InstancedMesh]], [[Frustum Culling|Frustum Culling]], Mipmaps +- **Projects/Contexts:** [[Three.js|Three.js]], React Three Fiber, [[InstancedMesh2|InstancedMesh2]] - **Contradictions/Notes:** LOD 기술이 항상 성능 향상을 가져오는 것은 아닙니다. 만약 애플리케이션이 드로우 콜 과부하 상태(Draw call bound)라면 LOD를 적용해도 드로우 콜 자체가 줄지 않으므로 성능이 오히려 약간 저하될 수 있으며, 메모리 부하와 교체 연산 오버헤드만 추가될 위험이 있습니다 [8, 14, 15]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Level of Detail (LOD).md]] +- Raw Source: 00_Raw/2026-04-20/Level of Detail (LOD).md --- diff --git a/01_Archive/2026-04-20/Level-Design-Automation.md b/01_Archive/2026-04-20/Level-Design-Automation.md index 787fcaa7..35e4a5b4 100644 --- a/01_Archive/2026-04-20/Level-Design-Automation.md +++ b/01_Archive/2026-04-20/Level-Design-Automation.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-7DF19B -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Level-Design-Automation" --- -# [[Level-Design-Automation]] +# [[Level-Design-Automation|Level-Design-Automation]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Level-Design-Automation" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Level-Design-Automation.md]] +- Raw Source: 00_Raw/2026-04-20/Level-Design-Automation.md --- diff --git a/01_Archive/2026-04-20/Level-Design-Theory.md b/01_Archive/2026-04-20/Level-Design-Theory.md index dcc354d8..7c9ba893 100644 --- a/01_Archive/2026-04-20/Level-Design-Theory.md +++ b/01_Archive/2026-04-20/Level-Design-Theory.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-5EAC4F -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Level-Design-Theory" --- -# [[Level-Design-Theory]] +# [[Level-Design-Theory|Level-Design-Theory]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Level-Design-Theory" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Level-Design-Theory.md]] +- Raw Source: 00_Raw/2026-04-20/Level-Design-Theory.md --- diff --git a/01_Archive/2026-04-20/Lighthouse.md b/01_Archive/2026-04-20/Lighthouse.md index 956567a5..9258a508 100644 --- a/01_Archive/2026-04-20/Lighthouse.md +++ b/01_Archive/2026-04-20/Lighthouse.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-B44166 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Lighthouse" --- -# [[Lighthouse]] +# [[Lighthouse|Lighthouse]] ## 📌 한 줄 통찰 (The Karpathy Summary) > Lighthouse는 페이지 속도를 측정하고 성능 개선을 위한 권장 사항을 제공하는 구글의 무료 오픈소스 도구입니다 [1, 2]. 주로 Chrome DevTools 패널이나 명령줄에서 실행되며, PageSpeed Insights의 진단 기능을 구동하는 핵심 엔진으로 사용됩니다 [1, 2]. 또한, 이와 별개로 분산 시스템에서 네트워크 위치 지정(Network Positioning)의 확장성 문제를 해결하기 위해 고안된 동명의 연구 프로젝트인 'Lighthouses'도 존재합니다 [3, 4]. @@ -20,11 +20,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Lighthouse" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[PageSpeed Insights]], [[Chrome DevTools]], [[Synthetic Testing]], [[Time to Interactive (TTI)]], [[Global Network Positioning (GNP)]] -- **Projects/Contexts:** [[Web Performance Optimization]], [[Network Coordinate Systems]] +- **Related Topics:** [[PageSpeed Insights|PageSpeed Insights]], [[Chrome DevTools|Chrome DevTools]], [[Synthetic Testing|Synthetic Testing]], [[Time to Interactive (TTI)|Time to Interactive (TTI)]], [[Global Network Positioning (GNP)|Global Network Positioning (GNP)]] +- **Projects/Contexts:** [[Web Performance Optimization|Web Performance Optimization]], [[Network Coordinate Systems|Network Coordinate Systems]] - **Contradictions/Notes:** 구글 Lighthouse의 스로틀링 시뮬레이션은 프리로드된 리소스를 렌더링 차단 리소스로 잘못 분류하는 등 부정확한 점수를 도출하는 모순적 한계가 있으며, 현재 이를 실제 환경에 맞게 바로잡는 연구가 진행 중입니다 [8, 9]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Lighthouse.md]] +- Raw Source: 00_Raw/2026-04-20/Lighthouse.md --- diff --git a/01_Archive/2026-04-20/Linear Representation Hypothesis (선형 표현 가설).md b/01_Archive/2026-04-20/Linear Representation Hypothesis (선형 표현 가설).md index 890000df..97f6bbfa 100644 --- a/01_Archive/2026-04-20/Linear Representation Hypothesis (선형 표현 가설).md +++ b/01_Archive/2026-04-20/Linear Representation Hypothesis (선형 표현 가설).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-CEDE85 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Linear Representation Hypothesis (선형 표현 가설)" --- -# [[Linear Representation Hypothesis (선형 표현 가설)]] +# [[Linear Representation Hypothesis (선형 표현 가설)|Linear Representation Hypothesis (선형 표현 가설)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Linear Representation Hypothes ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Linear Representation Hypothesis (선형 표현 가설).md]] +- Raw Source: 00_Raw/2026-04-20/Linear Representation Hypothesis (선형 표현 가설).md --- diff --git a/01_Archive/2026-04-20/Linguistics.md b/01_Archive/2026-04-20/Linguistics.md index 60f82eb3..e2f5e9d5 100644 --- a/01_Archive/2026-04-20/Linguistics.md +++ b/01_Archive/2026-04-20/Linguistics.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-0C81F3 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Linguistics" --- -# [[Linguistics]] +# [[Linguistics|Linguistics]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Linguistics" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Linguistics.md]] +- Raw Source: 00_Raw/2026-04-20/Linguistics.md --- diff --git a/01_Archive/2026-04-20/Linked Open Data (LOD).md b/01_Archive/2026-04-20/Linked Open Data (LOD).md index a5357874..7b8c8dbc 100644 --- a/01_Archive/2026-04-20/Linked Open Data (LOD).md +++ b/01_Archive/2026-04-20/Linked Open Data (LOD).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-30BF26 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Linked Open Data (LOD)" --- -# [[Linked Open Data (LOD)]] +# [[Linked Open Data (LOD)|Linked Open Data (LOD)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Linked Open Data (LOD)" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Linked Open Data (LOD).md]] +- Raw Source: 00_Raw/2026-04-20/Linked Open Data (LOD).md --- diff --git a/01_Archive/2026-04-20/Linked-Data-Principles.md b/01_Archive/2026-04-20/Linked-Data-Principles.md index 320e5d38..f05a4d31 100644 --- a/01_Archive/2026-04-20/Linked-Data-Principles.md +++ b/01_Archive/2026-04-20/Linked-Data-Principles.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-878BEE -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Linked-Data-Principles" --- -# [[Linked-Data-Principles]] +# [[Linked-Data-Principles|Linked-Data-Principles]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Linked-Data-Principles" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Linked-Data-Principles.md]] +- Raw Source: 00_Raw/2026-04-20/Linked-Data-Principles.md --- diff --git a/01_Archive/2026-04-20/Liskov-Substitution-Principle.md b/01_Archive/2026-04-20/Liskov-Substitution-Principle.md index 97279c2a..8825367f 100644 --- a/01_Archive/2026-04-20/Liskov-Substitution-Principle.md +++ b/01_Archive/2026-04-20/Liskov-Substitution-Principle.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-A4E734 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Liskov-Substitution-Principle" --- -# [[Liskov-Substitution-Principle]] +# [[Liskov-Substitution-Principle|Liskov-Substitution-Principle]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Liskov-Substitution-Principle" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Liskov-Substitution-Principle.md]] +- Raw Source: 00_Raw/2026-04-20/Liskov-Substitution-Principle.md --- diff --git a/01_Archive/2026-04-20/Live Service Game Design.md b/01_Archive/2026-04-20/Live Service Game Design.md index 5b36a549..a0b465d2 100644 --- a/01_Archive/2026-04-20/Live Service Game Design.md +++ b/01_Archive/2026-04-20/Live Service Game Design.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-84B088 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Live Service Game Design" --- -# [[Live Service Game Design]] +# [[Live Service Game Design|Live Service Game Design]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Live Service Game Design" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Live Service Game Design.md]] +- Raw Source: 00_Raw/2026-04-20/Live Service Game Design.md --- diff --git a/01_Archive/2026-04-20/Live Streaming Monetization.md b/01_Archive/2026-04-20/Live Streaming Monetization.md index c4dcfb55..c20e0096 100644 --- a/01_Archive/2026-04-20/Live Streaming Monetization.md +++ b/01_Archive/2026-04-20/Live Streaming Monetization.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-9CC93F -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Live Streaming Monetization" --- -# [[Live Streaming Monetization]] +# [[Live Streaming Monetization|Live Streaming Monetization]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Live Streaming Monetization" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Live Streaming Monetization.md]] +- Raw Source: 00_Raw/2026-04-20/Live Streaming Monetization.md --- diff --git a/01_Archive/2026-04-20/LiveOps Management.md b/01_Archive/2026-04-20/LiveOps Management.md index c74ab2e8..41d4457e 100644 --- a/01_Archive/2026-04-20/LiveOps Management.md +++ b/01_Archive/2026-04-20/LiveOps Management.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-79CEB3 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - LiveOps Management" --- -# [[LiveOps Management]] +# [[LiveOps Management|LiveOps Management]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - LiveOps Management" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/LiveOps Management.md]] +- Raw Source: 00_Raw/2026-04-20/LiveOps Management.md --- diff --git a/01_Archive/2026-04-20/LoRA (Low-Rank Adaptation).md b/01_Archive/2026-04-20/LoRA (Low-Rank Adaptation).md index ee8d6745..4d165d33 100644 --- a/01_Archive/2026-04-20/LoRA (Low-Rank Adaptation).md +++ b/01_Archive/2026-04-20/LoRA (Low-Rank Adaptation).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-3C77A7 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - LoRA (Low-Rank Adaptation)" --- -# [[LoRA (Low-Rank Adaptation)]] +# [[LoRA (Low-Rank Adaptation)|LoRA (Low-Rank Adaptation)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - LoRA (Low-Rank Adaptation)" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/LoRA (Low-Rank Adaptation).md]] +- Raw Source: 00_Raw/2026-04-20/LoRA (Low-Rank Adaptation).md --- diff --git a/01_Archive/2026-04-20/Locus of Control.md b/01_Archive/2026-04-20/Locus of Control.md index 96fa72c7..0898f04d 100644 --- a/01_Archive/2026-04-20/Locus of Control.md +++ b/01_Archive/2026-04-20/Locus of Control.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-83F003 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Locus of Control" --- -# [[Locus of Control]] +# [[Locus of Control|Locus of Control]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Locus of Control" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Locus of Control.md]] +- Raw Source: 00_Raw/2026-04-20/Locus of Control.md --- diff --git a/01_Archive/2026-04-20/Locus-of-Control.md b/01_Archive/2026-04-20/Locus-of-Control.md index 2293abab..aedf0289 100644 --- a/01_Archive/2026-04-20/Locus-of-Control.md +++ b/01_Archive/2026-04-20/Locus-of-Control.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-C947BF -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Locus-of-Control" --- -# [[Locus-of-Control]] +# [[Locus-of-Control|Locus-of-Control]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Locus-of-Control" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Locus-of-Control.md]] +- Raw Source: 00_Raw/2026-04-20/Locus-of-Control.md --- diff --git a/01_Archive/2026-04-20/Logit Lens (로짓 렌즈).md b/01_Archive/2026-04-20/Logit Lens (로짓 렌즈).md index 2bce6260..5eea9019 100644 --- a/01_Archive/2026-04-20/Logit Lens (로짓 렌즈).md +++ b/01_Archive/2026-04-20/Logit Lens (로짓 렌즈).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-8DE413 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Logit Lens (로짓 렌즈)" --- -# [[Logit Lens (로짓 렌즈)]] +# [[Logit Lens (로짓 렌즈)|Logit Lens (로짓 렌즈)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Logit Lens (로짓 렌즈)" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Logit Lens (로짓 렌즈).md]] +- Raw Source: 00_Raw/2026-04-20/Logit Lens (로짓 렌즈).md --- diff --git a/01_Archive/2026-04-20/Long Animation Frames API.md b/01_Archive/2026-04-20/Long Animation Frames API.md index 04a6aec1..55207b11 100644 --- a/01_Archive/2026-04-20/Long Animation Frames API.md +++ b/01_Archive/2026-04-20/Long Animation Frames API.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-2A8383 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Long Animation Frames API" --- -# [[Long Animation Frames API]] +# [[Long Animation Frames API|Long Animation Frames API]] ## 📌 한 줄 통찰 (The Karpathy Summary) > Long Animation Frames API는 사용자 상호작용을 지연시키는 스크립트를 식별하고 세부 정보를 제공하는 데 사용되는 웹 성능 API입니다 [1]. Chrome 브라우저에서 INP(Interaction to Next Paint) 지표 측정을 위한 계측(instrumentation) 역할을 하여, 특정 상호작용 중에 실행된 자바스크립트 목록을 제공합니다 [2]. 이를 통해 개발자는 열악한 사용자 경험을 유발하는 스크립트와 함수를 효과적으로 탐지하고 최적화할 수 있습니다 [2]. @@ -22,11 +22,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Long Animation Frames API" - **정책 변화:** AI 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[INP (Interaction to Next Paint)]], [[Chrome DevTools]], [[Web Performance]] -- **Projects/Contexts:** 사용자 상호작용 병목 현상을 파악하기 위한 [[Chrome DevTools]] 성능 패널 및 [[DebugBear]] 웹 성능 모니터링 대시보드 +- **Related Topics:** INP (Interaction to Next Paint), [[Chrome DevTools|Chrome DevTools]], [[웹 성능 가이드(Web Performance)|Web Performance]] +- **Projects/Contexts:** 사용자 상호작용 병목 현상을 파악하기 위한 [[Chrome DevTools|Chrome DevTools]] 성능 패널 및 DebugBear 웹 성능 모니터링 대시보드 - **Contradictions/Notes:** 소스에 모순되는 내용은 존재하지 않으며, 이 API는 웹 성능 분석 및 서드파티 모니터링 서비스에서 자바스크립트 실행 지연을 식별하는 주요 수단으로 일관되게 설명되고 있습니다. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Long Animation Frames API.md]] +- Raw Source: 00_Raw/2026-04-20/Long Animation Frames API.md --- diff --git a/01_Archive/2026-04-20/Long Tasks.md b/01_Archive/2026-04-20/Long Tasks.md index 24e1ad36..4d06bf78 100644 --- a/01_Archive/2026-04-20/Long Tasks.md +++ b/01_Archive/2026-04-20/Long Tasks.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-183DC1 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Long Tasks" --- -# [[Long Tasks]] +# [[Long Tasks|Long Tasks]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 롱 태스크(Long Tasks)는 브라우저의 메인 스레드를 50ms 이상 장시간 차단하는 자바스크립트 연산 등의 CPU 처리 작업을 의미합니다 [1]. 이러한 작업은 짧은 여러 개의 작업보다 사용자 상호작용(Interaction)을 훨씬 더 지연시키며, 웹사이트를 느리게 느껴지게 만드는 주된 원인이 됩니다 [2]. @@ -29,11 +29,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Long Tasks" - **정책 변화:** AI 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Interaction to Next Paint (INP)]], [[Main Thread]], [[Scheduler API]], [[Chrome DevTools]] -- **Projects/Contexts:** [[Core Web Vitals]], [[Web Performance Optimization]] +- **Related Topics:** [[Interaction to Next Paint (INP)|Interaction to Next Paint (INP)]], [[Main Thread|Main Thread]], [[Scheduler API|Scheduler API]], [[Chrome DevTools|Chrome DevTools]] +- **Projects/Contexts:** [[Core Web Vitals|Core Web Vitals]], [[Web Performance Optimization|Web Performance Optimization]] - **Contradictions/Notes:** 소스 간의 모순된 내용은 발견되지 않았으며, 제공된 자료들은 공통적으로 웹 성능 향상을 위해 롱 태스크를 식별하고 분할하는 것의 중요성을 강조하고 있습니다. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Long Tasks.md]] +- Raw Source: 00_Raw/2026-04-20/Long Tasks.md --- diff --git a/01_Archive/2026-04-20/Long-Term Potentiation (LTP).md b/01_Archive/2026-04-20/Long-Term Potentiation (LTP).md index f61c2c31..7c34f44c 100644 --- a/01_Archive/2026-04-20/Long-Term Potentiation (LTP).md +++ b/01_Archive/2026-04-20/Long-Term Potentiation (LTP).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-AEAE94 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Long-Term Potentiation (LTP)" --- -# [[Long-Term Potentiation (LTP)]] +# [[Long-Term Potentiation (LTP)|Long-Term Potentiation (LTP)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Long-Term Potentiation (LTP)" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Long-Term Potentiation (LTP).md]] +- Raw Source: 00_Raw/2026-04-20/Long-Term Potentiation (LTP).md --- diff --git a/01_Archive/2026-04-20/Looking Glass Studios.md b/01_Archive/2026-04-20/Looking Glass Studios.md index 6b75ff8b..5b568360 100644 --- a/01_Archive/2026-04-20/Looking Glass Studios.md +++ b/01_Archive/2026-04-20/Looking Glass Studios.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-FBDE4E -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Looking Glass Studios" --- -# [[Looking Glass Studios]] +# [[Looking Glass Studios|Looking Glass Studios]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Looking Glass Studios" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Looking Glass Studios.md]] +- Raw Source: 00_Raw/2026-04-20/Looking Glass Studios.md --- diff --git a/01_Archive/2026-04-20/Looking-Glass-Studios.md b/01_Archive/2026-04-20/Looking-Glass-Studios.md index 197310c1..fdf5bd42 100644 --- a/01_Archive/2026-04-20/Looking-Glass-Studios.md +++ b/01_Archive/2026-04-20/Looking-Glass-Studios.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-83E00E -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Looking-Glass-Studios" --- -# [[Looking-Glass-Studios]] +# [[Looking-Glass-Studios|Looking-Glass-Studios]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Looking-Glass-Studios" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Looking-Glass-Studios.md]] +- Raw Source: 00_Raw/2026-04-20/Looking-Glass-Studios.md --- diff --git a/01_Archive/2026-04-20/Loot Box Regulation (EU_China Compliance).md b/01_Archive/2026-04-20/Loot Box Regulation (EU_China Compliance).md index 997abbcc..3a51438a 100644 --- a/01_Archive/2026-04-20/Loot Box Regulation (EU_China Compliance).md +++ b/01_Archive/2026-04-20/Loot Box Regulation (EU_China Compliance).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-4B1863 -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Loot Box Regulation (EU_China Compliance)" --- -# [[Loot Box Regulation (EU_China Compliance)]] +# [[Loot Box Regulation (EU_China Compliance)|Loot Box Regulation (EU_China Compliance)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Loot Box Regulation (EU_China ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Loot Box Regulation (EU_China Compliance).md]] +- Raw Source: 00_Raw/2026-04-20/Loot Box Regulation (EU_China Compliance).md --- diff --git a/01_Archive/2026-04-20/Ludo-Narrative-Dissonance.md b/01_Archive/2026-04-20/Ludo-Narrative-Dissonance.md index 7473ac48..31c885cf 100644 --- a/01_Archive/2026-04-20/Ludo-Narrative-Dissonance.md +++ b/01_Archive/2026-04-20/Ludo-Narrative-Dissonance.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-D2276C -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Ludo-Narrative-Dissonance" --- -# [[Ludo-Narrative-Dissonance]] +# [[Ludo-Narrative-Dissonance|Ludo-Narrative-Dissonance]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Ludo-Narrative-Dissonance" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Ludo-Narrative-Dissonance.md]] +- Raw Source: 00_Raw/2026-04-20/Ludo-Narrative-Dissonance.md --- diff --git a/01_Archive/2026-04-20/Ludo-narrative Dissonance.md b/01_Archive/2026-04-20/Ludo-narrative Dissonance.md index 12079d3a..df3b577c 100644 --- a/01_Archive/2026-04-20/Ludo-narrative Dissonance.md +++ b/01_Archive/2026-04-20/Ludo-narrative Dissonance.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-2B9D2D -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Ludo-narrative Dissonance" --- -# [[Ludo-narrative Dissonance]] +# [[Ludo-narrative Dissonance|Ludo-narrative Dissonance]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Ludo-narrative Dissonance" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Ludo-narrative Dissonance.md]] +- Raw Source: 00_Raw/2026-04-20/Ludo-narrative Dissonance.md --- diff --git a/01_Archive/2026-04-20/Ludology vs Narratology Debate.md b/01_Archive/2026-04-20/Ludology vs Narratology Debate.md index e34f7b7f..de2993db 100644 --- a/01_Archive/2026-04-20/Ludology vs Narratology Debate.md +++ b/01_Archive/2026-04-20/Ludology vs Narratology Debate.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-10519B -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Ludology vs Narratology Debate" --- -# [[Ludology vs Narratology Debate]] +# [[Ludology vs Narratology Debate|Ludology vs Narratology Debate]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Ludology vs Narratology Debate ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Ludology vs Narratology Debate.md]] +- Raw Source: 00_Raw/2026-04-20/Ludology vs Narratology Debate.md --- diff --git a/01_Archive/2026-04-20/Ludology vs Narratology.md b/01_Archive/2026-04-20/Ludology vs Narratology.md index 5ab77c30..e9577407 100644 --- a/01_Archive/2026-04-20/Ludology vs Narratology.md +++ b/01_Archive/2026-04-20/Ludology vs Narratology.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-E5E303 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Ludology vs Narratology" --- -# [[Ludology vs Narratology]] +# [[Ludology vs Narratology|Ludology vs Narratology]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Ludology vs Narratology" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Ludology vs. Narratology.md]] +- Raw Source: 00_Raw/2026-04-20/Ludology vs. Narratology.md --- diff --git a/01_Archive/2026-04-20/Ludology vs. Narratology.md b/01_Archive/2026-04-20/Ludology vs. Narratology.md index 6c2ffb3f..3b441e3c 100644 --- a/01_Archive/2026-04-20/Ludology vs. Narratology.md +++ b/01_Archive/2026-04-20/Ludology vs. Narratology.md @@ -1,4 +1,4 @@ -[[Ludology vs. Narratology]] +[[Ludology vs. Narratology|Ludology vs. Narratology]] 📌 Brief Summary The Ludology vs. Narratology debate is a foundational theoretical conflict in game studies (ludology) concerning the fundamental nature of video games. It centers on whether games should be analyzed primarily as systems of rules and mechanics (ludology) or as structures of storytelling and discourse (narratology). @@ -21,8 +21,8 @@ The debate emerged in the late 1990s and early 2000s, primarily driven by a rift * Contemporary scholars examine how mechanics and narrative are interdependent (e.g., "procedural rhetoric"), where the rules themselves communicate meaning or create emergent narratives that are not scripted but arise from gameplay. 🔗 Knowledge Connections -* Related Topics: [[Procedural Rhetoric]], [[Ergodic Literature]], [[Emergent Gameplay]], [[Cybertext]] -* Projects/Contexts: [[Game Studies (Academic Discipline)]], [[Formalism vs. Structuralism]] +* Related Topics: [[Procedural Rhetoric|Procedural Rhetoric]], [[Ergodic Literature|Ergodic Literature]], [[Emergent Gameplay|Emergent Gameplay]], [[Cybertext|Cybertext]] +* Projects/Contexts: [[Game Studies (Academic Discipline)|Game Studies (Academic Discipline)]], [[Formalism vs. Structuralism|Formalism vs. Structuralism]] * Contradictions/Notes: While early scholars like Aarseth argued for a strict separation to protect the autonomy of game studies, contemporary consensus views the two as a continuum rather than a dichotomy. Last updated: 2026-04-16 \ No newline at end of file diff --git a/01_Archive/2026-04-20/Ludology-vs-Narratology.md b/01_Archive/2026-04-20/Ludology-vs-Narratology.md index 6632511b..f1c14195 100644 --- a/01_Archive/2026-04-20/Ludology-vs-Narratology.md +++ b/01_Archive/2026-04-20/Ludology-vs-Narratology.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-977AD2 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Ludology-vs-Narratology" --- -# [[Ludology-vs-Narratology]] +# [[Ludology-vs-Narratology|Ludology-vs-Narratology]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Ludology-vs-Narratology" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Ludology-vs-Narratology.md]] +- Raw Source: 00_Raw/2026-04-20/Ludology-vs-Narratology.md --- diff --git a/01_Archive/2026-04-20/Ludology.md b/01_Archive/2026-04-20/Ludology.md index 73e5e30f..be6ef572 100644 --- a/01_Archive/2026-04-20/Ludology.md +++ b/01_Archive/2026-04-20/Ludology.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-397611 -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Ludology" --- -# [[Ludology]] +# [[Ludology|Ludology]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Ludology" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Ludology.md]] +- Raw Source: 00_Raw/2026-04-20/Ludology.md --- diff --git a/01_Archive/2026-04-20/Ludonarrative Dissonance.md b/01_Archive/2026-04-20/Ludonarrative Dissonance.md index 5ac19bee..ee4e4f94 100644 --- a/01_Archive/2026-04-20/Ludonarrative Dissonance.md +++ b/01_Archive/2026-04-20/Ludonarrative Dissonance.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-D88E68 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Ludonarrative Dissonance" --- -# [[Ludonarrative Dissonance]] +# [[Ludonarrative Dissonance|Ludonarrative Dissonance]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Ludonarrative Dissonance" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Ludonarrative Dissonance.md]] +- Raw Source: 00_Raw/2026-04-20/Ludonarrative Dissonance.md --- diff --git a/01_Archive/2026-04-20/Ludonarrative Resonance.md b/01_Archive/2026-04-20/Ludonarrative Resonance.md index 172027d5..29641ca9 100644 --- a/01_Archive/2026-04-20/Ludonarrative Resonance.md +++ b/01_Archive/2026-04-20/Ludonarrative Resonance.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-2B4A1C -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Ludonarrative Resonance" --- -# [[Ludonarrative Resonance]] +# [[Ludonarrative Resonance|Ludonarrative Resonance]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Ludonarrative Resonance" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Ludonarrative Resonance.md]] +- Raw Source: 00_Raw/2026-04-20/Ludonarrative Resonance.md --- diff --git a/01_Archive/2026-04-20/Ludonarrative-Dissonance.md b/01_Archive/2026-04-20/Ludonarrative-Dissonance.md index eb74a0dc..8fa22f92 100644 --- a/01_Archive/2026-04-20/Ludonarrative-Dissonance.md +++ b/01_Archive/2026-04-20/Ludonarrative-Dissonance.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-488A12 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Ludonarrative-Dissonance" --- -# [[Ludonarrative-Dissonance]] +# [[Ludonarrative-Dissonance|Ludonarrative-Dissonance]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Ludonarrative-Dissonance" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Ludonarrative-Dissonance.md]] +- Raw Source: 00_Raw/2026-04-20/Ludonarrative-Dissonance.md --- diff --git a/01_Archive/2026-04-20/MDA Framework.md b/01_Archive/2026-04-20/MDA Framework.md index 24558e35..ca2d029d 100644 --- a/01_Archive/2026-04-20/MDA Framework.md +++ b/01_Archive/2026-04-20/MDA Framework.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-14D7A9 -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - MDA Framework" --- -# [[MDA Framework]] +# [[MDA Framework|MDA Framework]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - MDA Framework" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/MDA Framework.md]] +- Raw Source: 00_Raw/2026-04-20/MDA Framework.md --- diff --git a/01_Archive/2026-04-20/MDA-Framework.md b/01_Archive/2026-04-20/MDA-Framework.md index 9ae0b496..8f7e27e2 100644 --- a/01_Archive/2026-04-20/MDA-Framework.md +++ b/01_Archive/2026-04-20/MDA-Framework.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-D62F53 -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - MDA-Framework" --- -# [[MDA-Framework]] +# [[MDA-Framework|MDA-Framework]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - MDA-Framework" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/MDA-Framework.md]] +- Raw Source: 00_Raw/2026-04-20/MDA-Framework.md --- diff --git a/01_Archive/2026-04-20/MDA-P-Framework.md b/01_Archive/2026-04-20/MDA-P-Framework.md index bc3156be..04d5dc59 100644 --- a/01_Archive/2026-04-20/MDA-P-Framework.md +++ b/01_Archive/2026-04-20/MDA-P-Framework.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-CCDD20 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - MDA-P-Framework" --- -# [[MDA-P-Framework]] +# [[MDA-P-Framework|MDA-P-Framework]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - MDA-P-Framework" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/MDA-P-Framework.md]] +- Raw Source: 00_Raw/2026-04-20/MDA-P-Framework.md --- diff --git a/01_Archive/2026-04-20/MMORPG Economic Management.md b/01_Archive/2026-04-20/MMORPG Economic Management.md index 16920a96..7da0689c 100644 --- a/01_Archive/2026-04-20/MMORPG Economic Management.md +++ b/01_Archive/2026-04-20/MMORPG Economic Management.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-CD65EB -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - MMORPG Economic Management" --- -# [[MMORPG Economic Management]] +# [[MMORPG Economic Management|MMORPG Economic Management]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - MMORPG Economic Management" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/MMORPG Economic Management.md]] +- Raw Source: 00_Raw/2026-04-20/MMORPG Economic Management.md --- diff --git a/01_Archive/2026-04-20/MMORPG Ecosystems.md b/01_Archive/2026-04-20/MMORPG Ecosystems.md index 715f202f..51e01dac 100644 --- a/01_Archive/2026-04-20/MMORPG Ecosystems.md +++ b/01_Archive/2026-04-20/MMORPG Ecosystems.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-525534 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - MMORPG Ecosystems" --- -# [[MMORPG Ecosystems]] +# [[MMORPG Ecosystems|MMORPG Ecosystems]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - MMORPG Ecosystems" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/MMORPG Ecosystems.md]] +- Raw Source: 00_Raw/2026-04-20/MMORPG Ecosystems.md --- diff --git a/01_Archive/2026-04-20/MVC (Model-View-Controller).md b/01_Archive/2026-04-20/MVC (Model-View-Controller).md index 050124f7..e932313d 100644 --- a/01_Archive/2026-04-20/MVC (Model-View-Controller).md +++ b/01_Archive/2026-04-20/MVC (Model-View-Controller).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-F8BE8B -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - MVC (Model-View-Controller)" --- -# [[MVC (Model-View-Controller)]] +# [[MVC (Model-View-Controller)|MVC (Model-View-Controller)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > MVC(Model-View-Controller)는 애플리케이션을 모델(Model), 뷰(View), 컨트롤러(Controller)라는 세 가지 상호 연결된 구성 요소로 분리하는 고전적인 소프트웨어 아키텍처 패턴이다 [1]. 이 패턴은 각 구성 요소에 명확한 책임을 부여하여 시스템의 복잡성을 줄이는 '관심사의 분리(Separation of Concerns)' 원칙의 대표적인 예시이다 [2, 3]. 역할 간의 명확한 경계를 설정함으로써 개발자는 데이터 로직에 영향을 주지 않고 사용자 인터페이스를 독립적으로 수정할 수 있어 시스템의 유연성과 유지보수성을 크게 향상시킬 수 있다 [2, 3]. @@ -31,11 +31,11 @@ github_commit: "[P-Reinforce] Continuous Worker - MVC (Model-View-Controller)" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Separation of Concerns (SoC)]], [[Software Architecture]], [[Clean Architecture]] -- **Projects/Contexts:** [[Web Applications]], [[GUI Development]] +- **Related Topics:** [[관심사의 분리 (Separation of Concerns SoC)|Separation of Concerns (SoC)]], Software Architecture, [[Clean Architecture|Clean Architecture]] +- **Projects/Contexts:** Web Applications, GUI Development - **Contradictions/Notes:** 소스에 관련 정보가 부족합니다. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/MVC (Model-View-Controller).md]] +- Raw Source: 00_Raw/2026-04-20/MVC (Model-View-Controller).md --- diff --git a/01_Archive/2026-04-20/Machine Learning in Game Design.md b/01_Archive/2026-04-20/Machine Learning in Game Design.md index 54fee637..e3eba163 100644 --- a/01_Archive/2026-04-20/Machine Learning in Game Design.md +++ b/01_Archive/2026-04-20/Machine Learning in Game Design.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-E6138D -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Machine Learning in Game Design" --- -# [[Machine Learning in Game Design]] +# [[Machine Learning in Game Design|Machine Learning in Game Design]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Machine Learning in Game Desig ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Machine Learning in Game Design.md]] +- Raw Source: 00_Raw/2026-04-20/Machine Learning in Game Design.md --- diff --git a/01_Archive/2026-04-20/Machine-Learning-Animation.md b/01_Archive/2026-04-20/Machine-Learning-Animation.md index 868adb1c..17ee8252 100644 --- a/01_Archive/2026-04-20/Machine-Learning-Animation.md +++ b/01_Archive/2026-04-20/Machine-Learning-Animation.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-223E1A -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Machine-Learning-Animation" --- -# [[Machine-Learning-Animation]] +# [[Machine-Learning-Animation|Machine-Learning-Animation]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Machine-Learning-Animation" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Machine-Learning-Animation.md]] +- Raw Source: 00_Raw/2026-04-20/Machine-Learning-Animation.md --- diff --git a/01_Archive/2026-04-20/Main Thread.md b/01_Archive/2026-04-20/Main Thread.md index 674ff26e..2563f864 100644 --- a/01_Archive/2026-04-20/Main Thread.md +++ b/01_Archive/2026-04-20/Main Thread.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-905D08 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Main Thread" --- -# [[Main Thread]] +# [[Main Thread|Main Thread]] ## 📌 한 줄 통찰 (The Karpathy Summary) > Main Thread(메인 스레드)는 웹 브라우저에서 자바스크립트 실행, 렌더링, 이벤트 처리 등 핵심 작업이 순차적으로 실행되는 단일 작업 흐름을 의미합니다 [1, 2]. WebGL과 같은 환경에서는 그래픽 명령어 제출을 비롯한 무거운 연산이 메인 스레드에서 이루어질 경우 렌더링 파이프라인이 차단되어 지연(Latency)과 병목 현상이 발생할 수 있습니다 [1, 2]. Chrome DevTools와 같은 성능 분석 도구를 통해 메인 스레드의 활동을 시각적으로 추적하고 병목 지점을 최적화할 수 있습니다 [3-5]. @@ -22,11 +22,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Main Thread" - **정책 변화:** AI 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[WebGL]], [[WebGPU]], [[Total Blocking Time (TBT)]], [[Interaction to Next Paint (INP)]], [[Long Tasks]] -- **Projects/Contexts:** [[Chrome DevTools Performance Panel]], [[Core Web Vitals]] +- **Related Topics:** [[WebGL|WebGL]], [[WebGPU|WebGPU]], [[Total Blocking Time (TBT)|Total Blocking Time (TBT)]], [[Interaction to Next Paint (INP)|Interaction to Next Paint (INP)]], [[Long Tasks|Long Tasks]] +- **Projects/Contexts:** Chrome DevTools Performance Panel, [[Core Web Vitals|Core Web Vitals]] - **Contradictions/Notes:** 소스는 WebGL이 메인 스레드에서 순차적으로 그래픽 명령을 처리하여 CPU 병목을 유발한다고 주장하는 반면, 새로운 WebGPU는 다중 스레드 명령 생성(Multi-Threaded Command Generation)을 지원하여 메인 스레드의 오버헤드를 대폭 줄일 수 있다고 대조하여 설명합니다 [2, 11, 12]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Main Thread.md]] +- Raw Source: 00_Raw/2026-04-20/Main Thread.md --- diff --git a/01_Archive/2026-04-20/Major GC.md b/01_Archive/2026-04-20/Major GC.md index fe6f581c..04ee44bd 100644 --- a/01_Archive/2026-04-20/Major GC.md +++ b/01_Archive/2026-04-20/Major GC.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-D3B770 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Major GC" --- -# [[Major GC]] +# [[Major GC|Major GC]] ## 📌 한 줄 통찰 (The Karpathy Summary) > Major GC는 V8을 비롯한 여러 가비지 컬렉션 환경에서 메모리의 'Old Space(오래된 세대)' 또는 힙(Heap) 전체의 가비지를 수집하는 주기입니다 [1-3]. 짧은 수명의 객체를 처리하는 Minor GC(Scavenge)와 달리, Mark-Sweep 및 Mark-Compact 알고리즘을 사용하여 수명이 길어 Old Space로 승격된 객체들의 메모리를 정리합니다 [1, 4, 5]. 전통적으로는 긴 정지 시간(stop-the-world)을 발생시켰으나, 최근에는 점진적(incremental), 병렬(parallel), 동시적(concurrent) 처리 기법을 도입하여 애플리케이션의 메인 스레드 지연을 최소화하는 방향으로 최적화되었습니다 [6-8]. @@ -30,13 +30,13 @@ github_commit: "[P-Reinforce] Continuous Worker - Major GC" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Minor GC]], [[Mark-Sweep]], [[Mark-Compact]], [[Orinoco]], [[Old Space]] -- **Projects/Contexts:** [[V8 JavaScript Engine]], [[Node.js Memory Management]] +- **Related Topics:** [[마이너 가비지 컬렉션(Minor GC)|Minor GC]], [[Mark-Sweep|Mark-Sweep]], [[마크-컴팩트(Mark-Compact)|Mark-Compact]], [[Orinoco|Orinoco]], [[Old Space|Old Space]] +- **Projects/Contexts:** [[V8 JavaScript Engine|V8 JavaScript Engine]], [[Node.js Memory Management|Node.js Memory Management]] - **Contradictions/Notes:** - Minor GC(Scavenge)는 새롭게 할당된 작고 수명이 짧은 객체를 신속하게 처리하는 반면, Major GC는 크기가 크고 수명이 긴 Old Space 영역을 처리하므로 상대적으로 비용이 더 많이 들며 덜 빈번하게 발생합니다 [1, 3, 4, 10]. - 과거의 주요 가비지 컬렉터들은 전체 과정을 동기적으로 수행하여 'Stop-the-world' 상태를 초래했지만, 현재의 메이저 GC는 점진적이고 동시적인 기법을 통해 메인 스레드의 멈춤 시간을 사실상 사용자가 인지하지 못할 수준으로 개선했습니다 [6-8, 22]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Major GC.md]] +- Raw Source: 00_Raw/2026-04-20/Major GC.md --- diff --git a/01_Archive/2026-04-20/Mapped-Types.md b/01_Archive/2026-04-20/Mapped-Types.md index 5b13e7a7..9c294943 100644 --- a/01_Archive/2026-04-20/Mapped-Types.md +++ b/01_Archive/2026-04-20/Mapped-Types.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-A475F9 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Mapped-Types" --- -# [[Mapped-Types]] +# [[Mapped-Types|Mapped-Types]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Mapped-Types" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Mapped-Types.md]] +- Raw Source: 00_Raw/2026-04-20/Mapped-Types.md --- diff --git a/01_Archive/2026-04-20/Mark-Sweep-Compact 알고리즘.md b/01_Archive/2026-04-20/Mark-Sweep-Compact 알고리즘.md index 3fbff272..2a052a17 100644 --- a/01_Archive/2026-04-20/Mark-Sweep-Compact 알고리즘.md +++ b/01_Archive/2026-04-20/Mark-Sweep-Compact 알고리즘.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-AF3315 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Mark-Sweep-Compact 알고리즘" --- -# [[Mark-Sweep-Compact 알고리즘]] +# [[Mark-Sweep-Compact 알고리즘|Mark-Sweep-Compact 알고리즘]] ## 📌 한 줄 통찰 (The Karpathy Summary) > Mark-Sweep-Compact 알고리즘은 애플리케이션의 힙 메모리에서 더 이상 사용되지 않는 객체를 식별하여 메모리를 회수하고, 발생한 메모리 단편화를 해결하는 주요 가비지 컬렉션(GC) 기법입니다 [1]. 도달 가능한 객체를 식별하여 표시하는 마크(Mark) 단계, 참조되지 않는 죽은 객체의 메모리를 회수하는 스윕(Sweep) 단계, 그리고 살아남은 객체들을 모아 힙 메모리 단편화를 줄이는 컴팩트(Compact) 단계로 이루어집니다 [1]. 이 알고리즘은 주로 V8 엔진의 Old Generation이나 JVM의 전역 힙(Java heap)을 정리하는 데 활용되며, 메모리 효율성을 극대화하지만 객체 이동에 따른 비용이 크다는 특징이 있습니다 [2], [3], [4]. @@ -25,11 +25,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Mark-Sweep-Compact 알고리 - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Garbage Collection]], [[V8 Engine]], [[Old Space]], [[Java Heap Memory]] -- **Projects/Contexts:** [[V8 엔진의 Old Generation 메모리 관리]], [[IBM JVM의 가비지 컬렉션 메커니즘]] +- **Related Topics:** [[Garbage Collection|Garbage Collection]], [[V8 Engine|V8 Engine]], [[Old Space|Old Space]], Java Heap Memory +- **Projects/Contexts:** V8 엔진의 Old Generation 메모리 관리, IBM JVM의 가비지 컬렉션 메커니즘 - **Contradictions/Notes:** 컴팩트(Compact) 작업은 단편화를 해결하여 캐시 지역성(cache locality)을 높이지만, 포인터 재조정과 객체 이동 비용으로 인해 애플리케이션의 'Stop-the-world(STW)' 일시 중지 시간을 증가시킬 수 있습니다 [3]. 이를 보완하기 위해 V8 엔진은 객체 그래프가 변경될 가능성을 쓰기 장벽(Write barrier)으로 제어하며 점진적 마킹(Incremental marking) 및 지연 스윕(Lazy sweeping) 기술을 도입하여 메인 스레드 멈춤 시간을 줄이고 있습니다 [12], [13], [14]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Mark-Sweep-Compact 알고리즘.md]] +- Raw Source: 00_Raw/2026-04-20/Mark-Sweep-Compact 알고리즘.md --- diff --git a/01_Archive/2026-04-20/Mark-Sweep-Compact(메이저 GC).md b/01_Archive/2026-04-20/Mark-Sweep-Compact(메이저 GC).md index cc8b8072..903d2012 100644 --- a/01_Archive/2026-04-20/Mark-Sweep-Compact(메이저 GC).md +++ b/01_Archive/2026-04-20/Mark-Sweep-Compact(메이저 GC).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-50957B -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Mark-Sweep-Compact(메이저 GC)" --- -# [[Mark-Sweep-Compact(메이저 GC)]] +# [[Mark-Sweep-Compact(메이저 GC)|Mark-Sweep-Compact(메이저 GC)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > Mark-Sweep-Compact(메이저 GC)는 메모리 힙의 전체 영역(주로 Old 세대 공간)에서 더 이상 사용되지 않는 객체를 식별해 메모리를 회수하고 단편화를 해소하는 가비지 컬렉션(GC) 알고리즘입니다 [1-3]. 이 알고리즘은 살아있는 객체를 식별하는 마킹(Marking), 죽은 객체의 메모리를 해제하는 스위핑(Sweeping), 그리고 살아남은 객체들을 한곳으로 모아 메모리 단편화를 줄이는 컴팩팅(Compacting)의 세 가지 핵심 단계로 구성됩니다 [2-4]. 주로 크기가 크고 수명이 긴 객체들이 저장되는 메모리 영역의 효율적인 재사용을 위해 작동합니다 [1, 5, 6]. @@ -37,11 +37,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Mark-Sweep-Compact(메이저 G - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Garbage Collection]], [[Old Generation/Space]], [[Memory Fragmentation]], [[Incremental Marking]] -- **Projects/Contexts:** [[V8 Engine (JavaScript)]], [[JVM (Java Virtual Machine)]], [[Orinoco Garbage Collector]] +- **Related Topics:** [[Garbage Collection|Garbage Collection]], [[이전 세대(Old Generation_Space)|Old Generation/Space]], Memory Fragmentation, [[Incremental Marking|Incremental Marking]] +- **Projects/Contexts:** V8 Engine (JavaScript), JVM (Java Virtual Machine), Orinoco Garbage Collector - **Contradictions/Notes:** 소스 자료 전반에 걸쳐 큰 모순은 존재하지 않습니다. 다만, 컴팩팅(Compacting) 작업은 메모리 파편화를 완전히 해결하는 훌륭한 방법이지만 V8과 JVM 두 환경 모두에서 매우 무겁고 값비싼(expensive) 동작으로 공통되게 취급되며, 항상 실행되지 않고 철저한 휴리스틱이나 임계조건에 의해 선택적으로 발동된다는 점이 강조됩니다 [6, 16, 17]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Mark-Sweep-Compact(메이저 GC).md]] +- Raw Source: 00_Raw/2026-04-20/Mark-Sweep-Compact(메이저 GC).md --- diff --git a/01_Archive/2026-04-20/Mark-Sweep-Compact.md b/01_Archive/2026-04-20/Mark-Sweep-Compact.md index 29bb2108..53e0ea0b 100644 --- a/01_Archive/2026-04-20/Mark-Sweep-Compact.md +++ b/01_Archive/2026-04-20/Mark-Sweep-Compact.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-1D592D -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Mark-Sweep-Compact" --- -# [[Mark-Sweep-Compact]] +# [[Mark-Sweep-Compact|Mark-Sweep-Compact]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -31,11 +31,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Mark-Sweep-Compact" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Garbage Collection]], [[Old Generation]], [[Incremental Marking]], [[Memory Fragmentation]] -- **Projects/Contexts:** [[V8 JavaScript Engine]], [[IBM Java GC]], [[Orinoco Garbage Collector]] +- **Related Topics:** [[Garbage Collection|Garbage Collection]], Old Generation, [[Incremental Marking|Incremental Marking]], Memory Fragmentation +- **Projects/Contexts:** [[V8 JavaScript Engine|V8 JavaScript Engine]], IBM Java GC, Orinoco Garbage Collector - **Contradictions/Notes:** 컴팩트(Compact) 단계의 빈도와 관련하여, V8에서는 Old Space의 파편화를 줄이기 위해 Major GC 과정에서 컴팩팅을 통합적으로 활용하여 객체를 마이그레이션하는 반면 [5, 10], IBM Java GC 환경에서는 객체 이동에 따른 높은 오버헤드로 인해 컴팩트 단계가 기본 활성화 상태가 아니며 메모리 부족이나 명시적 설정 시에만 제한적으로 트리거된다는 차이가 있습니다 [7, 21]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Mark-Sweep-Compact.md]] +- Raw Source: 00_Raw/2026-04-20/Mark-Sweep-Compact.md --- diff --git a/01_Archive/2026-04-20/Mark-Sweep.md b/01_Archive/2026-04-20/Mark-Sweep.md index f3ae17d6..ccd5f37f 100644 --- a/01_Archive/2026-04-20/Mark-Sweep.md +++ b/01_Archive/2026-04-20/Mark-Sweep.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-261A28 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Mark-Sweep" --- -# [[Mark-Sweep]] +# [[Mark-Sweep|Mark-Sweep]] ## 📌 한 줄 통찰 (The Karpathy Summary) > Mark-Sweep(마크-스위프)는 V8 엔진과 JVM 등에서 오래된 객체(Old Space/Generation)의 메모리를 회수하기 위해 주로 사용되는 가비지 컬렉션(GC) 알고리즘입니다 [1-4]. 이 알고리즘은 힙 메모리 내의 모든 활성 객체를 식별하여 표시하는 '마킹(Marking)' 단계와, 표시되지 않은 죽은 객체의 메모리 영역을 해제하는 '스위핑(Sweeping)' 단계로 동작합니다 [2, 5]. 기존에는 긴 애플리케이션 일시 정지(Stop-the-world)를 유발했으나, 현대의 엔진들은 점진적(Incremental), 지연(Lazy), 그리고 병행(Concurrent) 처리 기법을 결합하여 성능 오버헤드를 크게 줄였습니다 [6-9]. @@ -34,11 +34,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Mark-Sweep" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Garbage Collection]], [[Old Generation]], [[Mark-Compact]], [[Incremental Marking]], [[Lazy Sweeping]] -- **Projects/Contexts:** [[V8 JavaScript Engine]], [[JVM (Java Virtual Machine)]], [[Orinoco Garbage Collector]] -- **Contradictions/Notes:** 마크-스위프는 빠르고 공간을 효과적으로 재활용하지만, 메모리 파편화(Fragmentation)를 유발할 수 있습니다. 따라서 V8에서는 파편화가 심한 페이지의 라이브 객체를 이동시키고 빈 공간을 병합하는 [[Mark-Compact]] 알고리즘과 밀접하게 연계되어 사용됩니다 [2, 4, 5, 20]. 또한, Node.js 환경에서 `--trace_gc` 로그 상에 'Mark-sweep'이 지나치게 자주 발생하거나 반환되는 메모리가 미미하다면 애플리케이션 내 메모리 누수(Memory Leak)나 CPU 집약적 블로킹 작업이 존재할 가능성이 높습니다 [21, 22]. +- **Related Topics:** [[Garbage Collection|Garbage Collection]], Old Generation, [[마크-컴팩트(Mark-Compact)|Mark-Compact]], [[Incremental Marking|Incremental Marking]], Lazy Sweeping +- **Projects/Contexts:** [[V8 JavaScript Engine|V8 JavaScript Engine]], JVM (Java Virtual Machine), Orinoco Garbage Collector +- **Contradictions/Notes:** 마크-스위프는 빠르고 공간을 효과적으로 재활용하지만, 메모리 파편화(Fragmentation)를 유발할 수 있습니다. 따라서 V8에서는 파편화가 심한 페이지의 라이브 객체를 이동시키고 빈 공간을 병합하는 [[마크-컴팩트(Mark-Compact)|Mark-Compact]] 알고리즘과 밀접하게 연계되어 사용됩니다 [2, 4, 5, 20]. 또한, Node.js 환경에서 `--trace_gc` 로그 상에 'Mark-sweep'이 지나치게 자주 발생하거나 반환되는 메모리가 미미하다면 애플리케이션 내 메모리 누수(Memory Leak)나 CPU 집약적 블로킹 작업이 존재할 가능성이 높습니다 [21, 22]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Mark-Sweep.md]] +- Raw Source: 00_Raw/2026-04-20/Mark-Sweep.md --- diff --git a/01_Archive/2026-04-20/Market Regulation.md b/01_Archive/2026-04-20/Market Regulation.md index 08d0b40c..4bb8371d 100644 --- a/01_Archive/2026-04-20/Market Regulation.md +++ b/01_Archive/2026-04-20/Market Regulation.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-E87A98 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Market Regulation" --- -# [[Market Regulation]] +# [[Market Regulation|Market Regulation]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Market Regulation" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Market Regulation.md]] +- Raw Source: 00_Raw/2026-04-20/Market Regulation.md --- diff --git a/01_Archive/2026-04-20/Markov Decision Process (MDP).md b/01_Archive/2026-04-20/Markov Decision Process (MDP).md index 236bbedf..f213dabc 100644 --- a/01_Archive/2026-04-20/Markov Decision Process (MDP).md +++ b/01_Archive/2026-04-20/Markov Decision Process (MDP).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-14D223 -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Markov Decision Process (MDP)" --- -# [[Markov Decision Process (MDP)]] +# [[Markov Decision Process (MDP)|Markov Decision Process (MDP)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Markov Decision Process (MDP)" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Markov Decision Process (MDP).md]] +- Raw Source: 00_Raw/2026-04-20/Markov Decision Process (MDP).md --- diff --git a/01_Archive/2026-04-20/Markov Decision Processes.md b/01_Archive/2026-04-20/Markov Decision Processes.md index 99470b95..551ad2da 100644 --- a/01_Archive/2026-04-20/Markov Decision Processes.md +++ b/01_Archive/2026-04-20/Markov Decision Processes.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-336A60 -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Markov Decision Processes" --- -# [[Markov Decision Processes]] +# [[Markov Decision Processes|Markov Decision Processes]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Markov Decision Processes" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Markov Decision Processes.md]] +- Raw Source: 00_Raw/2026-04-20/Markov Decision Processes.md --- diff --git a/01_Archive/2026-04-20/Markov-Random-Fields.md b/01_Archive/2026-04-20/Markov-Random-Fields.md index 0105ada7..6cabdc5f 100644 --- a/01_Archive/2026-04-20/Markov-Random-Fields.md +++ b/01_Archive/2026-04-20/Markov-Random-Fields.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-B14FE1 -category: "[[10_Wiki/💡 Topics/General Knowledge]]" +category: "10_Wiki/💡 Topics/General Knowledge" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Markov-Random-Fields" --- -# [[Markov-Random-Fields]] +# [[Markov-Random-Fields|Markov-Random-Fields]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Markov-Random-Fields" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Markov-Random-Fields.md]] +- Raw Source: 00_Raw/2026-04-20/Markov-Random-Fields.md --- diff --git a/01_Archive/2026-04-20/Material Design System.md b/01_Archive/2026-04-20/Material Design System.md index 2f4649e2..16f16495 100644 --- a/01_Archive/2026-04-20/Material Design System.md +++ b/01_Archive/2026-04-20/Material Design System.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-ABFF7B -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Material Design System" --- -# [[Material Design System]] +# [[Material Design System|Material Design System]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Material Design System" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Material Design System.md]] +- Raw Source: 00_Raw/2026-04-20/Material Design System.md --- diff --git a/01_Archive/2026-04-20/Material Design.md b/01_Archive/2026-04-20/Material Design.md index 7760b59c..70dff834 100644 --- a/01_Archive/2026-04-20/Material Design.md +++ b/01_Archive/2026-04-20/Material Design.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-2349C5 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Material Design" --- -# [[Material Design]] +# [[Material Design|Material Design]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Material Design" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Material Design.md]] +- Raw Source: 00_Raw/2026-04-20/Material Design.md --- diff --git a/01_Archive/2026-04-20/Material-Design.md b/01_Archive/2026-04-20/Material-Design.md index e304dbed..8ff14e76 100644 --- a/01_Archive/2026-04-20/Material-Design.md +++ b/01_Archive/2026-04-20/Material-Design.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-03A898 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Material-Design" --- -# [[Material-Design]] +# [[Material-Design|Material-Design]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Material-Design" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Material-Design.md]] +- Raw Source: 00_Raw/2026-04-20/Material-Design.md --- diff --git a/01_Archive/2026-04-20/Mathematical Game Theory.md b/01_Archive/2026-04-20/Mathematical Game Theory.md index 349a3947..a70992c0 100644 --- a/01_Archive/2026-04-20/Mathematical Game Theory.md +++ b/01_Archive/2026-04-20/Mathematical Game Theory.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-5BCF2D -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Mathematical Game Theory" --- -# [[Mathematical Game Theory]] +# [[Mathematical Game Theory|Mathematical Game Theory]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Mathematical Game Theory" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Mathematical Game Theory.md]] +- Raw Source: 00_Raw/2026-04-20/Mathematical Game Theory.md --- diff --git a/01_Archive/2026-04-20/Measure Theory.md b/01_Archive/2026-04-20/Measure Theory.md index 4fd2a024..6d97b687 100644 --- a/01_Archive/2026-04-20/Measure Theory.md +++ b/01_Archive/2026-04-20/Measure Theory.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-06771D -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Measure Theory" --- -# [[Measure Theory]] +# [[Measure Theory|Measure Theory]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Measure Theory" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Measure Theory.md]] +- Raw Source: 00_Raw/2026-04-20/Measure Theory.md --- diff --git a/01_Archive/2026-04-20/Mechanism Design in Auctions.md b/01_Archive/2026-04-20/Mechanism Design in Auctions.md index e0294b13..1d02ae26 100644 --- a/01_Archive/2026-04-20/Mechanism Design in Auctions.md +++ b/01_Archive/2026-04-20/Mechanism Design in Auctions.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-03623E -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Mechanism Design in Auctions" --- -# [[Mechanism Design in Auctions]] +# [[Mechanism Design in Auctions|Mechanism Design in Auctions]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Mechanism Design in Auctions" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Mechanism Design in Auctions.md]] +- Raw Source: 00_Raw/2026-04-20/Mechanism Design in Auctions.md --- diff --git a/01_Archive/2026-04-20/Mechanism Design.md b/01_Archive/2026-04-20/Mechanism Design.md index 601fed02..c848f930 100644 --- a/01_Archive/2026-04-20/Mechanism Design.md +++ b/01_Archive/2026-04-20/Mechanism Design.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-3A7080 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Mechanism Design" --- -# [[Mechanism Design]] +# [[Mechanism Design|Mechanism Design]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Mechanism Design" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Mechanism Design.md]] +- Raw Source: 00_Raw/2026-04-20/Mechanism Design.md --- diff --git a/01_Archive/2026-04-20/Mechanism-Design.md b/01_Archive/2026-04-20/Mechanism-Design.md index b5f600d5..0f6f5e2a 100644 --- a/01_Archive/2026-04-20/Mechanism-Design.md +++ b/01_Archive/2026-04-20/Mechanism-Design.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-F9F796 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Mechanism-Design" --- -# [[Mechanism-Design]] +# [[Mechanism-Design|Mechanism-Design]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Mechanism-Design" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Mechanism-Design.md]] +- Raw Source: 00_Raw/2026-04-20/Mechanism-Design.md --- diff --git a/01_Archive/2026-04-20/Mechanistic Interpretability (기계적 해석 가능성).md b/01_Archive/2026-04-20/Mechanistic Interpretability (기계적 해석 가능성).md index 4db497aa..4a544ff0 100644 --- a/01_Archive/2026-04-20/Mechanistic Interpretability (기계적 해석 가능성).md +++ b/01_Archive/2026-04-20/Mechanistic Interpretability (기계적 해석 가능성).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-2BBD92 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Mechanistic Interpretability (기계적 해석 가능성)" --- -# [[Mechanistic Interpretability (기계적 해석 가능성)]] +# [[Mechanistic Interpretability (기계적 해석 가능성)|Mechanistic Interpretability (기계적 해석 가능성)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Mechanistic Interpretability ( ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Mechanistic Interpretability (기계적 해석 가능성).md]] +- Raw Source: 00_Raw/2026-04-20/Mechanistic Interpretability (기계적 해석 가능성).md --- diff --git a/01_Archive/2026-04-20/Mechanobiology.md b/01_Archive/2026-04-20/Mechanobiology.md index af9c6b8d..a267a6a3 100644 --- a/01_Archive/2026-04-20/Mechanobiology.md +++ b/01_Archive/2026-04-20/Mechanobiology.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-D8F1A7 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Mechanobiology" --- -# [[Mechanobiology]] +# [[Mechanobiology|Mechanobiology]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Mechanobiology" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Mechanobiology.md]] +- Raw Source: 00_Raw/2026-04-20/Mechanobiology.md --- diff --git a/01_Archive/2026-04-20/Meltdown.md b/01_Archive/2026-04-20/Meltdown.md index 8337fc0b..74f1b1aa 100644 --- a/01_Archive/2026-04-20/Meltdown.md +++ b/01_Archive/2026-04-20/Meltdown.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-0BF53B -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Meltdown" --- -# [[Meltdown]] +# [[Meltdown|Meltdown]] ## 📌 한 줄 통찰 (The Karpathy Summary) > Meltdown은 현대의 프로세서에 영향을 미치는 보안 취약점으로, 공격자가 보호되어야 할 비밀 메모리 영역에 읽기 권한을 얻을 수 있게 합니다 [1]. 구체적으로는 웹 브라우저에서 실행되는 JavaScript와 같은 사용자 영역(userland)의 코드가 커널 메모리를 읽을 수 있게 만듭니다 [2]. 웹 브라우저(예: WebKit)를 통해 Meltdown 공격을 수행하려면, 먼저 Spectre 취약점을 이용해 브라우저의 보안 속성을 우회하는 과정이 선행되어야 합니다 [1, 2]. @@ -20,11 +20,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Meltdown" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Spectre]], [[Side-channel attacks]], [[Web Timing Security]] -- **Projects/Contexts:** [[WebKit]], [[Blink]] +- **Related Topics:** [[Spectre|Spectre]], [[Side-channel attacks|Side-channel attacks]], Web Timing Security +- **Projects/Contexts:** [[WebKit|WebKit]], [[Blink|Blink]] - **Contradictions/Notes:** 제공된 소스 내에서 모순되는 내용은 확인되지 않으며, Meltdown 방어를 위해 운영체제 수준의 완화와 브라우저(WebKit, Blink) 수준의 타이밍 정밀도 제한 및 Spectre 방어 조치가 상호 보완적으로 작용함을 강조하고 있습니다 [2, 4]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Meltdown.md]] +- Raw Source: 00_Raw/2026-04-20/Meltdown.md --- diff --git a/01_Archive/2026-04-20/Memory Leak Prevention 메모리 누수 방지.md b/01_Archive/2026-04-20/Memory Leak Prevention 메모리 누수 방지.md index e114c95f..d636f744 100644 --- a/01_Archive/2026-04-20/Memory Leak Prevention 메모리 누수 방지.md +++ b/01_Archive/2026-04-20/Memory Leak Prevention 메모리 누수 방지.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-21F91F -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Memory Leak Prevention 메모리 누수 방지" --- -# [[Memory Leak Prevention 메모리 누수 방지]] +# [[Memory Leak Prevention 메모리 누수 방지|Memory Leak Prevention 메모리 누수 방지]] ## 📌 한 줄 통찰 (The Karpathy Summary) > React 애플리케이션 및 WebGL/Three.js 환경에서 해제되지 않은 타이머, 이벤트 리스너, 외부 객체 참조, 또는 GPU 자원으로 인해 시간이 지날수록 메모리 점유율이 증가하여 앱이 느려지거나 크래시되는 현상을 막기 위한 필수적인 자원 관리 및 최적화 기법입니다. @@ -38,12 +38,12 @@ github_commit: "[P-Reinforce] Continuous Worker - Memory Leak Prevention 메모 - **정책 변화:** Graphics & Performance 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[useEffect 클린업(Cleanup)]], [[Garbage Collection (GC) 최적화]], [[Three.js 자원 해제 (Dispose)]], [[Chrome DevTools Memory Profiler]] -- **Projects/Contexts:** [[장기 실행되는 실시간 대시보드 최적화]], [[대규모 WebGL/R3F 3D 게임 환경의 메모리 관리]] +- **Related Topics:** [[useEffect 클린업(Cleanup)|useEffect 클린업(Cleanup)]], [[Garbage Collection (GC) 최적화|Garbage Collection (GC) 최적화]], [[Three.js 자원 해제 (Dispose)|Three.js 자원 해제 (Dispose)]], Chrome DevTools Memory Profiler +- **Projects/Contexts:** 장기 실행되는 실시간 대시보드 최적화, 대규모 WebGL/R3F 3D 게임 환경의 메모리 관리 - **Contradictions/Notes:** 최신 자바스크립트 엔진은 매우 훌륭한 가비지 컬렉터(GC)를 갖추고 있으나, DOM 이벤트, 브라우저 API(타이머, 소켓), WebGL GPU 메모리 등 '자바스크립트 엔진 외부의 자원'과 연결된 참조는 GC가 임의로 판단해 지울 수 없습니다. 따라서 외부 자원과의 연결 고리는 개발자가 직접 끊어주어야만 완벽한 메모리 관리가 가능합니다. --- _Last updated: 2026-04-14_ -- Raw Source: [[00_Raw/2026-04-20/Memory Leak Prevention 메모리 누수 방지.md]] +- Raw Source: 00_Raw/2026-04-20/Memory Leak Prevention 메모리 누수 방지.md --- diff --git a/01_Archive/2026-04-20/Memory Leak(메모리 누수).md b/01_Archive/2026-04-20/Memory Leak(메모리 누수).md index 5c0faadd..4515cc37 100644 --- a/01_Archive/2026-04-20/Memory Leak(메모리 누수).md +++ b/01_Archive/2026-04-20/Memory Leak(메모리 누수).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-D05474 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Memory Leak(메모리 누수)" --- -# [[Memory Leak(메모리 누수)]] +# [[Memory Leak(메모리 누수)|Memory Leak(메모리 누수)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 메모리 누수(Memory Leak)는 프로그램이 더 이상 필요하지 않은 메모리를 해제하지 않아, 해당 메모리가 운영체제의 가용 메모리 풀로 반환되지 않는 현상을 의미합니다 [1]. JavaScript와 같은 가비지 컬렉션(GC) 기반 언어에서는 메모리가 단순히 유실되는 것이 아니라, 더 이상 사용되지 않아야 할 객체들이 GC 루트(window, 활성 클로저, 이벤트 리스너, 타이머 등)에서 여전히 참조 가능(reachable)한 상태로 남아 있어 가비지 컬렉터가 이를 회수하지 못할 때 발생합니다 [2, 3]. 이러한 누수가 누적되면 애플리케이션의 성능이 저하되고 잦은 가비지 컬렉션 일시 정지를 유발하며, 최종적으로는 메모리 고갈로 인한 크래시(OOM, Out-Of-Memory)로 이어지게 됩니다 [1, 4, 5]. @@ -20,13 +20,13 @@ github_commit: "[P-Reinforce] Continuous Worker - Memory Leak(메모리 누수)" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Garbage Collection(가비지 컬렉션)]], [[V8 JavaScript Engine]], [[Heap Snapshot(힙 스냅샷)]], [[Closure(클로저)]] -- **Projects/Contexts:** [[Frontend Browser Diagnostics]], [[Node.js Production Monitoring]] +- **Related Topics:** [[Garbage Collection(가비지 컬렉션)|Garbage Collection(가비지 컬렉션)]], [[V8 JavaScript Engine|V8 JavaScript Engine]], [[Heap Snapshot(힙 스냅샷)|Heap Snapshot(힙 스냅샷)]], Closure(클로저) +- **Projects/Contexts:** Frontend Browser Diagnostics, [[Node.js Production Monitoring|Node.js Production Monitoring]] - **Contradictions/Notes:** * 메모리가 증가한다고 해서 무조건 누수인 것은 아닙니다. 캐시나 실행 취소 내역(undo histories) 등은 의도적으로 데이터를 보존하므로, 소스에서는 '의도적 보존(intentional retention)'과 '우발적 누수(accidental retention)'를 명확히 구분해야 한다고 강조합니다 [12]. * `WeakRef`와 `FinalizationRegistry`를 사용해 가비지 컬렉션을 방해하지 않는 참조 패턴을 만들 수 있지만, 가비지 컬렉터의 실행 일정은 비결정적(non-deterministic)이므로 이를 적절한 수명 주기 관리(lifecycle management)의 대체재로 사용해서는 안 됩니다 [11]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Memory Leak(메모리 누수).md]] +- Raw Source: 00_Raw/2026-04-20/Memory Leak(메모리 누수).md --- diff --git a/01_Archive/2026-04-20/Memory Leak.md b/01_Archive/2026-04-20/Memory Leak.md index 4ff6b852..e7aeaf4a 100644 --- a/01_Archive/2026-04-20/Memory Leak.md +++ b/01_Archive/2026-04-20/Memory Leak.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-61D625 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Memory Leak" --- -# [[Memory Leak]] +# [[Memory Leak|Memory Leak]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 메모리 누수(Memory Leak)는 프로그램이 더 이상 필요하지 않은 메모리를 반환하지 않고 계속 참조를 유지하여 지속적으로 메모리를 점유하는 현상입니다[1, 2]. JavaScript 환경에서 메모리 누수는 메모리가 유실되는 것이 아니라, 객체가 가비지 컬렉터(GC) 루트(window, 클로저, 이벤트 리스너 등)에서 여전히 도달 가능(reachable)한 상태로 남아 있어 GC가 이를 회수하지 못할 때 발생합니다[3, 4]. 이러한 누수가 장기간 누적되면 가비지 컬렉션 일시 정지가 잦아지고 응답 시간이 저하되며, 결국 메모리 한계를 초과하여 OOM(Out of Memory) 크래시를 유발할 수 있습니다[1, 5, 6]. @@ -20,11 +20,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Memory Leak" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Garbage Collection]], [[V8 Engine]], [[Heap Snapshot]], [[Allocation Timeline]] -- **Projects/Contexts:** [[Browser Application]], [[Node.js Server Production]] +- **Related Topics:** [[Garbage Collection|Garbage Collection]], [[V8 Engine|V8 Engine]], [[Heap Snapshot|Heap Snapshot]], [[Allocation Timeline|Allocation Timeline]] +- **Projects/Contexts:** Browser Application, Node.js Server Production - **Contradictions/Notes:** 소스에 따르면 `WeakRef`나 `FinalizationRegistry`와 같은 최신 도구를 누수 방지 패턴에 활용할 수는 있으나, GC의 실행 시점이 비결정적이므로 이러한 도구들이 명시적인 생명주기 관리(정확한 타이머 및 리스너 해제)를 완전히 대체할 수는 없다고 지적합니다[12]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Memory Leak.md]] +- Raw Source: 00_Raw/2026-04-20/Memory Leak.md --- diff --git a/01_Archive/2026-04-20/Memory Leaks.md b/01_Archive/2026-04-20/Memory Leaks.md index f539f638..9651af89 100644 --- a/01_Archive/2026-04-20/Memory Leaks.md +++ b/01_Archive/2026-04-20/Memory Leaks.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-5A05AF -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Memory Leaks" --- -# [[Memory Leaks]] +# [[Memory Leaks|Memory Leaks]] ## 📌 한 줄 통찰 (The Karpathy Summary) > Three.js 및 WebGL 환경에서 메모리 누수(Memory Leaks)는 GPU 리소스가 자동으로 가비지 컬렉션(Garbage Collection)되지 않아 VRAM 등 메모리 사용량이 지속적으로 증가하는 현상을 의미합니다 [1]. 이는 주로 지오메트리, 재질, 텍스처 등의 렌더링 리소스를 코드 상에서 명시적으로 해제하지 않았을 때 발생합니다 [1, 2]. 메모리 누수를 방지하려면 렌더러 정보를 통한 지속적인 모니터링과 올바른 메모리 관리 기법의 적용이 필수적입니다 [2]. @@ -24,11 +24,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Memory Leaks" - **정책 변화:** Graphics & Performance 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Garbage Collection]], [[Object Pooling]], [[Dispose()]], [[ImageBitmap]] -- **Projects/Contexts:** [[Three.js Memory Management]], [[Asset Streaming in WebGL]] +- **Related Topics:** [[Garbage Collection|Garbage Collection]], [[Object Pooling|Object Pooling]], Dispose(), ImageBitmap +- **Projects/Contexts:** Three.js Memory Management, Asset Streaming in WebGL - **Contradictions/Notes:** 소스 간의 모순점은 발견되지 않았으며, 제공된 소스들은 모두 공통적으로 Three.js 엔진 환경에서 메모리 누수를 방지하기 위해 '사용이 끝난 자원의 명시적 해제(dispose)'가 절대적으로 필요함을 강조하고 있습니다. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Memory Leaks.md]] +- Raw Source: 00_Raw/2026-04-20/Memory Leaks.md --- diff --git a/01_Archive/2026-04-20/Memory Management.md b/01_Archive/2026-04-20/Memory Management.md index 7a5da45d..8dc9b43f 100644 --- a/01_Archive/2026-04-20/Memory Management.md +++ b/01_Archive/2026-04-20/Memory Management.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-F27A16 -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Memory Management" --- -# [[Memory Management]] +# [[Memory Management|Memory Management]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 3D 웹 렌더링 및 그래픽스 환경에서 'Memory Management(메모리 관리)'는 시스템의 제한된 RAM과 GPU VRAM을 효율적으로 통제하여 애플리케이션의 크래시, 메모리 누수, 그리고 가비지 컬렉션(GC)으로 인한 프레임 지연을 방지하는 필수적인 최적화 과정입니다 [1, 2]. 이는 불필요한 GPU 자원의 명시적 폐기, 객체 풀링, 버퍼의 사전 할당 및 텍스처 압축 기술을 포괄합니다 [3-6]. @@ -24,11 +24,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Memory Management" - **정책 변화:** Graphics & Performance 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Garbage Collection]], [[Object Pooling]], [[Texture Compression]], [[GPU Resources]], [[Buffer Allocation]] -- **Projects/Contexts:** [[Three.js]], [[WebGL]], [[Electron]], [[Needle Engine]] +- **Related Topics:** [[Garbage Collection|Garbage Collection]], [[Object Pooling|Object Pooling]], [[Texture Compression|Texture Compression]], [[GPU Resources|GPU Resources]], [[Buffer Allocation|Buffer Allocation]] +- **Projects/Contexts:** [[Three.js|Three.js]], [[WebGL|WebGL]], [[Electron|Electron]], [[Needle Engine|Needle Engine]] - **Contradictions/Notes:** 웹 기반 프론트엔드 개발에서는 자바스크립트의 자동 메모리 관리에 의존하기 쉬우나, 소스에 따르면 WebGL과 같은 GPU 자원은 가비지 컬렉터의 대상이 아니므로 개발자가 수동으로 자원 해제를 관리해야만 크래시와 누수를 막을 수 있다고 강력히 지적합니다 [3, 7, 17]. 또한, 드로우 콜을 줄이는 인스턴싱 기법이 성능에 유리해 보이지만, 동적으로 크기가 늘어나는 버퍼를 방치할 경우 오히려 심각한 가비지 컬렉션 병목을 초래해 전체 성능을 깎아먹을 수 있음을 경고합니다 [2, 9]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Memory Management.md]] +- Raw Source: 00_Raw/2026-04-20/Memory Management.md --- diff --git a/01_Archive/2026-04-20/Mesa-Optimization (메사 최적화).md b/01_Archive/2026-04-20/Mesa-Optimization (메사 최적화).md index 00b806de..9f75c95a 100644 --- a/01_Archive/2026-04-20/Mesa-Optimization (메사 최적화).md +++ b/01_Archive/2026-04-20/Mesa-Optimization (메사 최적화).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-4AF7B4 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Mesa-Optimization (메사 최적화)" --- -# [[Mesa-Optimization (메사 최적화)]] +# [[Mesa-Optimization (메사 최적화)|Mesa-Optimization (메사 최적화)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Mesa-Optimization (메사 최 ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Mesa-Optimization (메사 최적화).md]] +- Raw Source: 00_Raw/2026-04-20/Mesa-Optimization (메사 최적화).md --- diff --git a/01_Archive/2026-04-20/MeshStandardMaterial 조명 연산.md b/01_Archive/2026-04-20/MeshStandardMaterial 조명 연산.md index 2b6f7c2f..306421f5 100644 --- a/01_Archive/2026-04-20/MeshStandardMaterial 조명 연산.md +++ b/01_Archive/2026-04-20/MeshStandardMaterial 조명 연산.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-56F596 -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - MeshStandardMaterial 조명 연산" --- -# [[MeshStandardMaterial 조명 연산]] +# [[MeshStandardMaterial 조명 연산|MeshStandardMaterial 조명 연산]] ## 📌 한 줄 통찰 (The Karpathy Summary) > MeshStandardMaterial은 금속성-거칠기(metallic-roughness) 워크플로우를 사용하는 물리 기반 렌더링(PBR) 모델을 기반으로 한 Three.js의 재질입니다 [1]. 이 재질은 에너지 보존 법칙과 프레넬 반사(Fresnel reflections)와 같은 복잡한 조명 연산을 필요로 하므로, 세밀한 사실성을 제공하지만 Three.js 내에서 가장 연산 비용이 높은 재질 중 하나로 꼽힙니다 [1]. @@ -25,11 +25,11 @@ github_commit: "[P-Reinforce] Continuous Worker - MeshStandardMaterial 조명 - **정책 변화:** Graphics & Performance 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Physically Based Rendering (PBR)]], [[오버드로우 (Overdraw)]], [[프래그먼트 바운드 (Fragment-bound)]] -- **Projects/Contexts:** [[Three.js 대규모 씬 최적화]] +- **Related Topics:** Physically Based Rendering (PBR), [[오버드로우(Overdraw)|오버드로우 (Overdraw)]], [[프래그먼트 바운드(Fragment-bound)|프래그먼트 바운드 (Fragment-bound)]] +- **Projects/Contexts:** Three.js 대규모 씬 최적화 - **Contradictions/Notes:** 극도의 사실성을 제공하는 현대적인 표준 재질이지만, 연산량이 많아 저사양 하드웨어에서는 비물리 기반의 MeshPhongMaterial 등 보다 가벼운 조명 모델을 사용하는 것이 추천될 만큼 렌더링 비용 면에서 뚜렷한 트레이드오프가 존재합니다 [1, 5]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/MeshStandardMaterial 조명 연산.md]] +- Raw Source: 00_Raw/2026-04-20/MeshStandardMaterial 조명 연산.md --- diff --git a/01_Archive/2026-04-20/Mesocortical Pathway.md b/01_Archive/2026-04-20/Mesocortical Pathway.md index f9578d3d..4281e346 100644 --- a/01_Archive/2026-04-20/Mesocortical Pathway.md +++ b/01_Archive/2026-04-20/Mesocortical Pathway.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-F74D23 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Mesocortical Pathway" --- -# [[Mesocortical Pathway]] +# [[Mesocortical Pathway|Mesocortical Pathway]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Mesocortical Pathway" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Mesocortical Pathway.md]] +- Raw Source: 00_Raw/2026-04-20/Mesocortical Pathway.md --- diff --git a/01_Archive/2026-04-20/Meta Quest_Horizon OS.md b/01_Archive/2026-04-20/Meta Quest_Horizon OS.md index a9cd0704..603d19c4 100644 --- a/01_Archive/2026-04-20/Meta Quest_Horizon OS.md +++ b/01_Archive/2026-04-20/Meta Quest_Horizon OS.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-65D468 -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Meta Quest_Horizon OS" --- -# [[Meta Quest_Horizon OS]] +# [[Meta Quest_Horizon OS|Meta Quest_Horizon OS]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Meta Quest_Horizon OS" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Meta Quest_Horizon OS.md]] +- Raw Source: 00_Raw/2026-04-20/Meta Quest_Horizon OS.md --- diff --git a/01_Archive/2026-04-20/Metabolic Efficiency.md b/01_Archive/2026-04-20/Metabolic Efficiency.md index a8457606..bda5cf05 100644 --- a/01_Archive/2026-04-20/Metabolic Efficiency.md +++ b/01_Archive/2026-04-20/Metabolic Efficiency.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-237ED8 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Metabolic Efficiency" --- -# [[Metabolic Efficiency]] +# [[Metabolic Efficiency|Metabolic Efficiency]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Metabolic Efficiency" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Metabolic Efficiency.md]] +- Raw Source: 00_Raw/2026-04-20/Metabolic Efficiency.md --- diff --git a/01_Archive/2026-04-20/Metabolic-Flexibility.md b/01_Archive/2026-04-20/Metabolic-Flexibility.md index 0cdfa346..110b366d 100644 --- a/01_Archive/2026-04-20/Metabolic-Flexibility.md +++ b/01_Archive/2026-04-20/Metabolic-Flexibility.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-1081E3 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Metabolic-Flexibility" --- -# [[Metabolic-Flexibility]] +# [[Metabolic-Flexibility|Metabolic-Flexibility]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Metabolic-Flexibility" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Metabolic-Flexibility.md]] +- Raw Source: 00_Raw/2026-04-20/Metabolic-Flexibility.md --- diff --git a/01_Archive/2026-04-20/Metabolic-Resource-Allocation.md b/01_Archive/2026-04-20/Metabolic-Resource-Allocation.md index f1702482..9ef4b43b 100644 --- a/01_Archive/2026-04-20/Metabolic-Resource-Allocation.md +++ b/01_Archive/2026-04-20/Metabolic-Resource-Allocation.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-9E2C0F -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Metabolic-Resource-Allocation" --- -# [[Metabolic-Resource-Allocation]] +# [[Metabolic-Resource-Allocation|Metabolic-Resource-Allocation]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Metabolic-Resource-Allocation" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Metabolic-Resource-Allocation.md]] +- Raw Source: 00_Raw/2026-04-20/Metabolic-Resource-Allocation.md --- diff --git a/01_Archive/2026-04-20/Metal.md b/01_Archive/2026-04-20/Metal.md index 119efe29..e0f646bc 100644 --- a/01_Archive/2026-04-20/Metal.md +++ b/01_Archive/2026-04-20/Metal.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-939802 -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Metal" --- -# [[Metal]] +# [[Metal|Metal]] ## 📌 한 줄 통찰 (The Karpathy Summary) > Metal은 주요 제조업체의 독점적인 차세대 네이티브 GPU API 중 하나입니다 [1]. Vulkan, Direct3D 12(DX12)와 함께 노후화된 OpenGL 표준을 대체하는 웹용 차세대 그래픽 API인 WebGPU의 설계와 프로그래밍 모델에 직접적인 영감을 제공한 핵심 기술입니다 [1-3]. @@ -23,11 +23,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Metal" - **정책 변화:** Graphics & Performance 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[WebGPU]], [[Vulkan]], [[Direct3D 12 (DX12)]], [[OpenGL]] -- **Projects/Contexts:** [[WebGPU Backend]] +- **Related Topics:** [[WebGPU|WebGPU]], [[Vulkan|Vulkan]], Direct3D 12 (DX12), OpenGL +- **Projects/Contexts:** WebGPU Backend - **Contradictions/Notes:** 소스에 관련 정보가 부족합니다. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Metal.md]] +- Raw Source: 00_Raw/2026-04-20/Metal.md --- diff --git a/01_Archive/2026-04-20/Metaverse Aesthetics.md b/01_Archive/2026-04-20/Metaverse Aesthetics.md index a3b2f761..a50aa3f6 100644 --- a/01_Archive/2026-04-20/Metaverse Aesthetics.md +++ b/01_Archive/2026-04-20/Metaverse Aesthetics.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-30803A -category: "[[10_Wiki/💡 Topics/General Knowledge]]" +category: "10_Wiki/💡 Topics/General Knowledge" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Metaverse Aesthetics" --- -# [[Metaverse Aesthetics]] +# [[Metaverse Aesthetics|Metaverse Aesthetics]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Metaverse Aesthetics" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Metaverse Aesthetics.md]] +- Raw Source: 00_Raw/2026-04-20/Metaverse Aesthetics.md --- diff --git a/01_Archive/2026-04-20/Metaverse Architecture.md b/01_Archive/2026-04-20/Metaverse Architecture.md index cbcb3a05..5d9685df 100644 --- a/01_Archive/2026-04-20/Metaverse Architecture.md +++ b/01_Archive/2026-04-20/Metaverse Architecture.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-7BDD7C -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Metaverse Architecture" --- -# [[Metaverse Architecture]] +# [[Metaverse Architecture|Metaverse Architecture]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Metaverse Architecture" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Metaverse Architecture.md]] +- Raw Source: 00_Raw/2026-04-20/Metaverse Architecture.md --- diff --git a/01_Archive/2026-04-20/Metro Exodus.md b/01_Archive/2026-04-20/Metro Exodus.md index 5c8daf1c..752f5560 100644 --- a/01_Archive/2026-04-20/Metro Exodus.md +++ b/01_Archive/2026-04-20/Metro Exodus.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-0E2C65 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Metro Exodus" --- -# [[Metro Exodus]] +# [[Metro Exodus|Metro Exodus]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Metro Exodus" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Metro Exodus.md]] +- Raw Source: 00_Raw/2026-04-20/Metro Exodus.md --- diff --git a/01_Archive/2026-04-20/Micro-Frontend-Architecture.md b/01_Archive/2026-04-20/Micro-Frontend-Architecture.md index 592ba0af..15398908 100644 --- a/01_Archive/2026-04-20/Micro-Frontend-Architecture.md +++ b/01_Archive/2026-04-20/Micro-Frontend-Architecture.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-070141 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Micro-Frontend-Architecture" --- -# [[Micro-Frontend-Architecture]] +# [[Micro-Frontend-Architecture|Micro-Frontend-Architecture]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Micro-Frontend-Architecture" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Micro-Frontend-Architecture.md]] +- Raw Source: 00_Raw/2026-04-20/Micro-Frontend-Architecture.md --- diff --git a/01_Archive/2026-04-20/Micro-latency.md b/01_Archive/2026-04-20/Micro-latency.md index cf0f995a..9b6bc2da 100644 --- a/01_Archive/2026-04-20/Micro-latency.md +++ b/01_Archive/2026-04-20/Micro-latency.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-B64E78 -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Micro-latency" --- -# [[Micro-latency]] +# [[Micro-latency|Micro-latency]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 웹 그래픽 파이프라인에서 마이크로 레이턴시(Micro-latency)는 60Hz 디스플레이 기준 16.67ms와 같은 엄격한 시간 예산 내에서 하드웨어와 소프트웨어 구성 요소가 동기화할 때 발생하는 미세한 지연을 의미합니다 [1]. 이는 JavaScript 엔진의 가비지 컬렉션, WebGL 및 ANGLE과 같은 API 변환, OS의 컨텍스트 생성, 디스플레이 하드웨어 등 여러 계층에서 복합적으로 발생하며 [2-5], 이러한 미세 지연이 누적되면 프레임 누락이나 인지 가능한 끊김(Stuttering) 현상으로 이어집니다 [1, 5]. 최근에는 Spectre 및 Meltdown과 같은 보안 취약점 완화 조치로 인해 시스템의 기본 마이크로 레이턴시가 소폭 증가하기도 했습니다 [6, 7]. @@ -20,11 +20,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Micro-latency" - **정책 변화:** Graphics & Performance 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[WebGL]], [[WebGPU]], [[Spectre and Meltdown]], [[EXT_disjoint_timer_query]], [[ANGLE (Almost Native Graphics Layer Engine)]] -- **Projects/Contexts:** [[WebSplatter (3D Gaussian Splatting)]], [[CesiumJS]], [[Figma]] +- **Related Topics:** [[WebGL|WebGL]], [[WebGPU|WebGPU]], [[Spectre and Meltdown|Spectre and Meltdown]], [[EXT_disjoint_timer_query|EXT_disjoint_timer_query]], [[ANGLE (Almost Native Graphics Layer Engine)|ANGLE (Almost Native Graphics Layer Engine)]] +- **Projects/Contexts:** [[WebSplatter (3D Gaussian Splatting)|WebSplatter (3D Gaussian Splatting)]], [[CesiumJS|CesiumJS]], [[Figma|Figma]] - **Contradictions/Notes:** 소스에 따르면, 성능 분석을 위한 정밀한 마이크로 레이턴시 측정의 필요성과 시스템 보안(Spectre/Meltdown 공격 방어) 사이에 명확한 상충(Conflict)이 존재합니다. 고정밀 타이머가 사이드 채널 공격에 악용될 수 있다는 연구 결과에 따라 브라우저 벤더들은 `EXT_disjoint_timer_query`를 비활성화하거나 타이머 해상도를 인위적으로 낮추는(Quantization) 타협안을 채택해야만 했습니다 [6, 10-12, 18]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Micro-latency.md]] +- Raw Source: 00_Raw/2026-04-20/Micro-latency.md --- diff --git a/01_Archive/2026-04-20/Microservices-Architecture-Bounded-Contexts.md b/01_Archive/2026-04-20/Microservices-Architecture-Bounded-Contexts.md index 5088915f..1f69d46b 100644 --- a/01_Archive/2026-04-20/Microservices-Architecture-Bounded-Contexts.md +++ b/01_Archive/2026-04-20/Microservices-Architecture-Bounded-Contexts.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-018DBB -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Microservices-Architecture-Bounded-Contexts" --- -# [[Microservices-Architecture-Bounded-Contexts]] +# [[Microservices-Architecture-Bounded-Contexts|Microservices-Architecture-Bounded-Contexts]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Microservices-Architecture-Bou ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Microservices-Architecture-Bounded-Contexts.md]] +- Raw Source: 00_Raw/2026-04-20/Microservices-Architecture-Bounded-Contexts.md --- diff --git a/01_Archive/2026-04-20/Microservices-Architecture-Type-Safety.md b/01_Archive/2026-04-20/Microservices-Architecture-Type-Safety.md index c0fdea89..bf8b32c2 100644 --- a/01_Archive/2026-04-20/Microservices-Architecture-Type-Safety.md +++ b/01_Archive/2026-04-20/Microservices-Architecture-Type-Safety.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-E27CC2 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Microservices-Architecture-Type-Safety" --- -# [[Microservices-Architecture-Type-Safety]] +# [[Microservices-Architecture-Type-Safety|Microservices-Architecture-Type-Safety]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Microservices-Architecture-Typ ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Microservices-Architecture-Type-Safety.md]] +- Raw Source: 00_Raw/2026-04-20/Microservices-Architecture-Type-Safety.md --- diff --git a/01_Archive/2026-04-20/Microservices-Architecture.md b/01_Archive/2026-04-20/Microservices-Architecture.md index ff17e97e..f08e582b 100644 --- a/01_Archive/2026-04-20/Microservices-Architecture.md +++ b/01_Archive/2026-04-20/Microservices-Architecture.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AI-048 -category: "[[10_Wiki/💡 Topics/Software Architecture]]" +category: "10_Wiki/💡 Topics/Software Architecture" confidence_score: 0.99 tags: [microservice, architecture, distributed system, scalability] last_reinforced: 2026-06-XX github_commit: "[P-Reinforce] Processed Microservices-Architecture.md" --- -# [[Microservices-Architecture]] (마이크로서비스 아키텍처) +# [[Microservices-Architecture|Microservices-Architecture]] (마이크로서비스 아키텍처) ## 📌 한 줄 통찰 (The Karpathy Summary) > 하나의 거대한 애플리케이션을 작고 독립적인 서비스들의 집합으로 나누어, 각 서비스를 독립적으로 개발, 배포, 확장할 수 있게 하는 분산 시스템 설계 방식이다. @@ -27,7 +27,7 @@ github_commit: "[P-Reinforce] Processed Microservices-Architecture.md" - **정책 변화:** MSA 도입 시, 서비스 간 통신 규약 (API Contract) 정의가 가장 중요한 첫 번째 단계이며, 이를 위한 API 게이트웨이 및 서비스 메시(Service Mesh)의 활용이 표준으로 자리 잡고 있다. ## 🔗 지식 연결 (Graph) -- Parent: [[Microservices-Architecture]] -- Related: [[Bounded Contexts]] , [[Event Storming]] , [[API-First Architecture]] -- Raw Source: [[00_Raw/Microservices-Architecture.md]] +- Parent: [[Microservices-Architecture|Microservices-Architecture]] +- Related: [[Bounded Contexts|Bounded Contexts]] , [[Event Storming|Event Storming]] , [[API-First Architecture|API-First Architecture]] +- Raw Source: 00_Raw/Microservices-Architecture.md --- \ No newline at end of file diff --git a/01_Archive/2026-04-20/Microservices-Communication-Patterns.md b/01_Archive/2026-04-20/Microservices-Communication-Patterns.md index eeb134be..5799eb6d 100644 --- a/01_Archive/2026-04-20/Microservices-Communication-Patterns.md +++ b/01_Archive/2026-04-20/Microservices-Communication-Patterns.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-8E2D1A -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Microservices-Communication-Patterns" --- -# [[Microservices-Communication-Patterns]] +# [[Microservices-Communication-Patterns|Microservices-Communication-Patterns]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Microservices-Communication-Pa ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Microservices-Communication-Patterns.md]] +- Raw Source: 00_Raw/2026-04-20/Microservices-Communication-Patterns.md --- diff --git a/01_Archive/2026-04-20/Microsoft Edge DevTools.md b/01_Archive/2026-04-20/Microsoft Edge DevTools.md index dc31bd88..ea90e308 100644 --- a/01_Archive/2026-04-20/Microsoft Edge DevTools.md +++ b/01_Archive/2026-04-20/Microsoft Edge DevTools.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-D3063D -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Microsoft Edge DevTools" --- -# [[Microsoft Edge DevTools]] +# [[Microsoft Edge DevTools|Microsoft Edge DevTools]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -27,11 +27,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Microsoft Edge DevTools" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Memory Tool]], [[Garbage Collection]], [[Heap Snapshot]], [[Memory Leak]] -- **Projects/Contexts:** [[Allocation instrumentation on timeline]] +- **Related Topics:** Memory Tool, [[Garbage Collection|Garbage Collection]], [[Heap Snapshot|Heap Snapshot]], [[Memory Leak|Memory Leak]] +- **Projects/Contexts:** [[타임라인 할당 계측(Allocation instrumentation on timeline)|Allocation instrumentation on timeline]] - **Contradictions/Notes:** 소스에 관련 정보가 부족합니다. Microsoft Edge DevTools의 전체적인 구조나 다른 패널(네트워크, 콘솔 등)에 대한 설명은 없으며, 오직 Memory 패널 내부의 타임라인 할당 프로파일링 도구에 대해서만 설명하고 있습니다. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Microsoft Edge DevTools.md]] +- Raw Source: 00_Raw/2026-04-20/Microsoft Edge DevTools.md --- diff --git a/01_Archive/2026-04-20/Minecraft.md b/01_Archive/2026-04-20/Minecraft.md index 09338166..3e882c49 100644 --- a/01_Archive/2026-04-20/Minecraft.md +++ b/01_Archive/2026-04-20/Minecraft.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-A3F579 -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Minecraft" --- -# [[Minecraft]] +# [[Minecraft|Minecraft]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Minecraft" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Minecraft.md]] +- Raw Source: 00_Raw/2026-04-20/Minecraft.md --- diff --git a/01_Archive/2026-04-20/Minecraft_ Education Edition.md b/01_Archive/2026-04-20/Minecraft_ Education Edition.md index 18eb5c70..14a29b58 100644 --- a/01_Archive/2026-04-20/Minecraft_ Education Edition.md +++ b/01_Archive/2026-04-20/Minecraft_ Education Edition.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-7091B6 -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Minecraft_ Education Edition" --- -# [[Minecraft_ Education Edition]] +# [[Minecraft_ Education Edition|Minecraft_ Education Edition]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Minecraft_ Education Edition" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Minecraft_ Education Edition.md]] +- Raw Source: 00_Raw/2026-04-20/Minecraft_ Education Edition.md --- diff --git a/01_Archive/2026-04-20/Mipmap.md b/01_Archive/2026-04-20/Mipmap.md index 64603128..f7cddd13 100644 --- a/01_Archive/2026-04-20/Mipmap.md +++ b/01_Archive/2026-04-20/Mipmap.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-F5788A -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Mipmap" --- -# [[Mipmap]] +# [[Mipmap|Mipmap]] ## 📌 한 줄 통찰 (The Karpathy Summary) > Mipmap(또는 Mipmapping)은 거리 기반의 디테일 수준(LOD, Level of Detail) 샘플링을 위해 미리 계산된 다단계 텍스처 해상도 피라미드입니다 [1]. 텍스처 렌더링 시 발생하는 계단 현상(aliasing artifacts)을 제거하고, 화면상에 에셋이 매끄럽게 표시되도록 돕는 역할을 합니다 [1, 2]. 하지만 Mipmap을 저장하기 위해 추가적인 GPU 메모리 공간이 필요하며, 특정 최적화 기법(텍스처 아틀라스)과 결합할 때 텍스처 간 번짐 현상을 유발할 수 있다는 특징이 있습니다 [3, 4]. @@ -23,11 +23,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Mipmap" - **정책 변화:** AI 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Level of Detail (LOD)]], [[Texture Atlas]], [[Data Array Textures]], [[Aliasing]] -- **Projects/Contexts:** [[Three.js 최적화 파이프라인]], [[GPU 메모리 및 텍스처 압축]] +- **Related Topics:** [[Level of Detail (LOD)|Level of Detail (LOD)]], [[Texture Atlas|Texture Atlas]], [[Data Array Textures|Data Array Textures]], [[에일리어싱 (Aliasing)|Aliasing]] +- **Projects/Contexts:** Three.js 최적화 파이프라인, GPU 메모리 및 텍스처 압축 - **Contradictions/Notes:** 소스에 따르면 단일 텍스처 아틀라스 기법은 밉맵의 낮은 레벨(low mip levels)에서 텍스처 혼합 현상(블리딩)이라는 단점을 수반하지만 [3], 배열 텍스처(Array Textures) 기법을 사용하면 이러한 Mipmap 간섭 현상을 완전히 배제하고 네이티브 랩핑(wrapping)과 타일링(tiling)을 지원할 수 있습니다 [5]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Mipmap.md]] +- Raw Source: 00_Raw/2026-04-20/Mipmap.md --- diff --git a/01_Archive/2026-04-20/Mobile Gaming Monetization Strategies.md b/01_Archive/2026-04-20/Mobile Gaming Monetization Strategies.md index a36eedfe..a3d31846 100644 --- a/01_Archive/2026-04-20/Mobile Gaming Monetization Strategies.md +++ b/01_Archive/2026-04-20/Mobile Gaming Monetization Strategies.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-48096A -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Mobile Gaming Monetization Strategies" --- -# [[Mobile Gaming Monetization Strategies]] +# [[Mobile Gaming Monetization Strategies|Mobile Gaming Monetization Strategies]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Mobile Gaming Monetization Str ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Mobile Gaming Monetization Strategies.md]] +- Raw Source: 00_Raw/2026-04-20/Mobile Gaming Monetization Strategies.md --- diff --git a/01_Archive/2026-04-20/Mobile-App-Development.md b/01_Archive/2026-04-20/Mobile-App-Development.md index 13bbe0ae..65a76916 100644 --- a/01_Archive/2026-04-20/Mobile-App-Development.md +++ b/01_Archive/2026-04-20/Mobile-App-Development.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-C0F26C -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Mobile-App-Development" --- -# [[Mobile-App-Development]] +# [[Mobile-App-Development|Mobile-App-Development]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Mobile-App-Development" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Mobile-App-Development.md]] +- Raw Source: 00_Raw/2026-04-20/Mobile-App-Development.md --- diff --git a/01_Archive/2026-04-20/Mobile-App-Onboarding.md b/01_Archive/2026-04-20/Mobile-App-Onboarding.md index 8cab5c88..f39c37c9 100644 --- a/01_Archive/2026-04-20/Mobile-App-Onboarding.md +++ b/01_Archive/2026-04-20/Mobile-App-Onboarding.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-D7506D -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Mobile-App-Onboarding" --- -# [[Mobile-App-Onboarding]] +# [[Mobile-App-Onboarding|Mobile-App-Onboarding]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Mobile-App-Onboarding" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Mobile-App-Onboarding.md]] +- Raw Source: 00_Raw/2026-04-20/Mobile-App-Onboarding.md --- diff --git a/01_Archive/2026-04-20/Model Collapse (모델 붕괴 현상).md b/01_Archive/2026-04-20/Model Collapse (모델 붕괴 현상).md index b31ce0d1..69fabeb3 100644 --- a/01_Archive/2026-04-20/Model Collapse (모델 붕괴 현상).md +++ b/01_Archive/2026-04-20/Model Collapse (모델 붕괴 현상).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-F2D3E0 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Model Collapse (모델 붕괴 현상)" --- -# [[Model Collapse (모델 붕괴 현상)]] +# [[Model Collapse (모델 붕괴 현상)|Model Collapse (모델 붕괴 현상)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Model Collapse (모델 붕괴 ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Model Collapse (모델 붕괴 현상).md]] +- Raw Source: 00_Raw/2026-04-20/Model Collapse (모델 붕괴 현상).md --- diff --git a/01_Archive/2026-04-20/Model Context Protocol (MCP).md b/01_Archive/2026-04-20/Model Context Protocol (MCP).md index 77120f81..197ec93c 100644 --- a/01_Archive/2026-04-20/Model Context Protocol (MCP).md +++ b/01_Archive/2026-04-20/Model Context Protocol (MCP).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-C8F96B -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Model Context Protocol (MCP)" --- -# [[Model Context Protocol (MCP)]] +# [[Model Context Protocol (MCP)|Model Context Protocol (MCP)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > Model Context Protocol (MCP)은 Cursor, Claude Code, Windsurf, GitHub Copilot 등과 같은 AI 코딩 어시스턴트(AI 에이전트)를 분석 엔진과 직접 연결할 수 있도록 지원하는 프로토콜입니다 [1, 2]. 이 프로토콜을 통해 AI는 대화형 워크플로우 내에서 실시간으로 쿼리를 보내고 통제된 피드백을 받을 수 있습니다 [1, 3]. 결과적으로 AI를 활용한 생산성과 코드 품질 및 보안 사이의 간격을 메워주는 특수한 브릿지 역할을 수행합니다 [2, 4]. @@ -22,11 +22,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Model Context Protocol (MCP)" - **정책 변화:** AI 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[AI Agents]], [[Static Code Analysis]], [[Automated Code Review]] -- **Projects/Contexts:** [[SonarQube MCP Server]], [[Cursor]], [[Claude Code]], [[Windsurf]], [[GitHub Copilot]] +- **Related Topics:** [[AI Agents|AI Agents]], Static Code Analysis, Automated Code Review +- **Projects/Contexts:** SonarQube MCP Server, Cursor, Claude Code, Windsurf, GitHub Copilot - **Contradictions/Notes:** 소스에 관련 정보가 부족합니다. (제공된 소스에서는 주로 SonarQube 환경에서의 통합 사례를 통해서만 MCP가 설명되고 있으며, 프로토콜 자체의 심층적인 기술적 사양이나 다른 활용 사례에 대한 정보는 없습니다.) --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Model Context Protocol (MCP).md]] +- Raw Source: 00_Raw/2026-04-20/Model Context Protocol (MCP).md --- diff --git a/01_Archive/2026-04-20/Model Predictive Control (MPC).md b/01_Archive/2026-04-20/Model Predictive Control (MPC).md index 531fd7be..b55e1cb5 100644 --- a/01_Archive/2026-04-20/Model Predictive Control (MPC).md +++ b/01_Archive/2026-04-20/Model Predictive Control (MPC).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-212A93 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Model Predictive Control (MPC)" --- -# [[Model Predictive Control (MPC)]] +# [[Model Predictive Control (MPC)|Model Predictive Control (MPC)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Model Predictive Control (MPC) ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Model Predictive Control (MPC).md]] +- Raw Source: 00_Raw/2026-04-20/Model Predictive Control (MPC).md --- diff --git a/01_Archive/2026-04-20/Model Spec (모델 스펙 AI 행동 명세서).md b/01_Archive/2026-04-20/Model Spec (모델 스펙 AI 행동 명세서).md index af612110..289eb75b 100644 --- a/01_Archive/2026-04-20/Model Spec (모델 스펙 AI 행동 명세서).md +++ b/01_Archive/2026-04-20/Model Spec (모델 스펙 AI 행동 명세서).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-73F6B2 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Model Spec (모델 스펙 AI 행동 명세서)" --- -# [[Model Spec (모델 스펙 AI 행동 명세서)]] +# [[Model Spec (모델 스펙 AI 행동 명세서)|Model Spec (모델 스펙 AI 행동 명세서)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Model Spec (모델 스펙 AI ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Model Spec (모델 스펙, AI 행동 명세서).md]] +- Raw Source: 00_Raw/2026-04-20/Model Spec (모델 스펙, AI 행동 명세서).md --- diff --git a/01_Archive/2026-04-20/Model Spec (모델 스펙, AI 행동 명세서).md b/01_Archive/2026-04-20/Model Spec (모델 스펙, AI 행동 명세서).md index 4b1d03dc..4a801010 100644 --- a/01_Archive/2026-04-20/Model Spec (모델 스펙, AI 행동 명세서).md +++ b/01_Archive/2026-04-20/Model Spec (모델 스펙, AI 행동 명세서).md @@ -1,4 +1,4 @@ -[[Model Spec (모델 스펙, AI 행동 명세서)]] +[[Model Spec (모델 스펙, AI 행동 명세서)|Model Spec (모델 스펙, AI 행동 명세서)]] 📌 Brief Summary @@ -68,8 +68,8 @@ Model Spec은 인공지능 모델이 사용자에게 어떻게 답변해야 하 🔗 Knowledge Connections -- **Related Topics:** [[HHH (Helpful, Harmless, Honest)]], [[Constitutional AI (헌법 AI)]], [[LLM Alignment (LLM 정렬)]], [[AI Safety (AI 안전)]], [[데이터 거버넌스 (Data Governance)]] -- **Projects/Contexts:** [[AI 서비스 정책 수립]] +- **Related Topics:** [[HHH (Helpful, Harmless, Honest)|HHH (Helpful, Harmless, Honest)]], [[Constitutional AI (헌법 AI)|Constitutional AI (헌법 AI)]], [[LLM Alignment (LLM 정렬)|LLM Alignment (LLM 정렬)]], [[AI Safety (AI 안전)|AI Safety (AI 안전)]], [[데이터 거버넌스 (Data Governance)|데이터 거버넌스 (Data Governance)]] +- **Projects/Contexts:** AI 서비스 정책 수립 - **Contradictions/Notes:** - 너무 엄격한 Model Spec은 모델의 창의성을 억제하거나 답변 거부율(Refusal Rate)을 높여 사용성을 해칠 수 있음. - 문화권마다 '무해함'과 '도움됨'의 기준이 다르므로 로컬라이징된 Model Spec이 필요함. diff --git a/01_Archive/2026-04-20/Model-Checking.md b/01_Archive/2026-04-20/Model-Checking.md index a4683aa6..72327465 100644 --- a/01_Archive/2026-04-20/Model-Checking.md +++ b/01_Archive/2026-04-20/Model-Checking.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-D4D8C1 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Model-Checking" --- -# [[Model-Checking]] +# [[Model-Checking|Model-Checking]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Model-Checking" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Model-Checking.md]] +- Raw Source: 00_Raw/2026-04-20/Model-Checking.md --- diff --git a/01_Archive/2026-04-20/Model-Free RL vs Model-Based RL.md b/01_Archive/2026-04-20/Model-Free RL vs Model-Based RL.md index 1ad169a1..d0256e3e 100644 --- a/01_Archive/2026-04-20/Model-Free RL vs Model-Based RL.md +++ b/01_Archive/2026-04-20/Model-Free RL vs Model-Based RL.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-B8C5BC -category: "[[10_Wiki/💡 Topics/General Knowledge]]" +category: "10_Wiki/💡 Topics/General Knowledge" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Model-Free RL vs Model-Based RL" --- -# [[Model-Free RL vs Model-Based RL]] +# [[Model-Free RL vs Model-Based RL|Model-Free RL vs Model-Based RL]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Model-Free RL vs Model-Based R ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Model-Free RL vs Model-Based RL.md]] +- Raw Source: 00_Raw/2026-04-20/Model-Free RL vs Model-Based RL.md --- diff --git a/01_Archive/2026-04-20/Module Augmentation.md b/01_Archive/2026-04-20/Module Augmentation.md index 17a0440f..2fb1a760 100644 --- a/01_Archive/2026-04-20/Module Augmentation.md +++ b/01_Archive/2026-04-20/Module Augmentation.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-43A3F8 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Module Augmentation" --- -# [[Module Augmentation]] +# [[Module Augmentation|Module Augmentation]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Module Augmentation" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Module Augmentation.md]] +- Raw Source: 00_Raw/2026-04-20/Module Augmentation.md --- diff --git a/01_Archive/2026-04-20/Module Resolution Algorithm.md b/01_Archive/2026-04-20/Module Resolution Algorithm.md index 35959b6f..83016438 100644 --- a/01_Archive/2026-04-20/Module Resolution Algorithm.md +++ b/01_Archive/2026-04-20/Module Resolution Algorithm.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-DE6CBC -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Module Resolution Algorithm" --- -# [[Module Resolution Algorithm]] +# [[Module Resolution Algorithm|Module Resolution Algorithm]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Module Resolution Algorithm" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Module Resolution Algorithm.md]] +- Raw Source: 00_Raw/2026-04-20/Module Resolution Algorithm.md --- diff --git a/01_Archive/2026-04-20/Module-Augmentation-Patterns.md b/01_Archive/2026-04-20/Module-Augmentation-Patterns.md index db93c019..d1a1eae9 100644 --- a/01_Archive/2026-04-20/Module-Augmentation-Patterns.md +++ b/01_Archive/2026-04-20/Module-Augmentation-Patterns.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-D54DFE -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Module-Augmentation-Patterns" --- -# [[Module-Augmentation-Patterns]] +# [[Module-Augmentation-Patterns|Module-Augmentation-Patterns]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Module-Augmentation-Patterns" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Module-Augmentation-Patterns.md]] +- Raw Source: 00_Raw/2026-04-20/Module-Augmentation-Patterns.md --- diff --git a/01_Archive/2026-04-20/Module-Augmentation.md b/01_Archive/2026-04-20/Module-Augmentation.md index 26baad29..db773a24 100644 --- a/01_Archive/2026-04-20/Module-Augmentation.md +++ b/01_Archive/2026-04-20/Module-Augmentation.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-C5A5E7 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Module-Augmentation" --- -# [[Module-Augmentation]] +# [[Module-Augmentation|Module-Augmentation]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Module-Augmentation" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Module-Augmentation.md]] +- Raw Source: 00_Raw/2026-04-20/Module-Augmentation.md --- diff --git a/01_Archive/2026-04-20/Module-Boundary-Enforcement.md b/01_Archive/2026-04-20/Module-Boundary-Enforcement.md index 1102bc0b..850722b6 100644 --- a/01_Archive/2026-04-20/Module-Boundary-Enforcement.md +++ b/01_Archive/2026-04-20/Module-Boundary-Enforcement.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-32A387 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Module-Boundary-Enforcement" --- -# [[Module-Boundary-Enforcement]] +# [[Module-Boundary-Enforcement|Module-Boundary-Enforcement]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Module-Boundary-Enforcement" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Module-Boundary-Enforcement.md]] +- Raw Source: 00_Raw/2026-04-20/Module-Boundary-Enforcement.md --- diff --git a/01_Archive/2026-04-20/Module-Resolution-Strategy.md b/01_Archive/2026-04-20/Module-Resolution-Strategy.md index d2ae2f13..88f08a10 100644 --- a/01_Archive/2026-04-20/Module-Resolution-Strategy.md +++ b/01_Archive/2026-04-20/Module-Resolution-Strategy.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-029B7A -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Module-Resolution-Strategy" --- -# [[Module-Resolution-Strategy]] +# [[Module-Resolution-Strategy|Module-Resolution-Strategy]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Module-Resolution-Strategy" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Module-Resolution-Strategy.md]] +- Raw Source: 00_Raw/2026-04-20/Module-Resolution-Strategy.md --- diff --git a/01_Archive/2026-04-20/Monetary Policy in Virtual Worlds.md b/01_Archive/2026-04-20/Monetary Policy in Virtual Worlds.md index 78ac73fd..df1506a2 100644 --- a/01_Archive/2026-04-20/Monetary Policy in Virtual Worlds.md +++ b/01_Archive/2026-04-20/Monetary Policy in Virtual Worlds.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-26E3C1 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Monetary Policy in Virtual Worlds" --- -# [[Monetary Policy in Virtual Worlds]] +# [[Monetary Policy in Virtual Worlds|Monetary Policy in Virtual Worlds]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Monetary Policy in Virtual Wor ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Monetary Policy in Virtual Worlds.md]] +- Raw Source: 00_Raw/2026-04-20/Monetary Policy in Virtual Worlds.md --- diff --git a/01_Archive/2026-04-20/Monetary Policy.md b/01_Archive/2026-04-20/Monetary Policy.md index 4cec84e4..5cd6979f 100644 --- a/01_Archive/2026-04-20/Monetary Policy.md +++ b/01_Archive/2026-04-20/Monetary Policy.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-97D263 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Monetary Policy" --- -# [[Monetary Policy]] +# [[Monetary Policy|Monetary Policy]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Monetary Policy" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Monetary Policy.md]] +- Raw Source: 00_Raw/2026-04-20/Monetary Policy.md --- diff --git a/01_Archive/2026-04-20/Monorepo(Turborepo 등) 환경의 린트 관리.md b/01_Archive/2026-04-20/Monorepo(Turborepo 등) 환경의 린트 관리.md index 1a1cc40e..fce91e05 100644 --- a/01_Archive/2026-04-20/Monorepo(Turborepo 등) 환경의 린트 관리.md +++ b/01_Archive/2026-04-20/Monorepo(Turborepo 등) 환경의 린트 관리.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-9CC04F -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Monorepo(Turborepo 등) 환경의 린트 관리" --- -# [[Monorepo(Turborepo 등) 환경의 린트 관리]] +# [[Monorepo(Turborepo 등) 환경의 린트 관리|Monorepo(Turborepo 등) 환경의 린트 관리]] ## 📌 한 줄 통찰 (The Karpathy Summary) > Turborepo와 같은 모노레포(Monorepo) 환경에서는 다수의 패키지와 애플리케이션으로 인해 ESLint 및 Prettier 설정이 중복되고 일관성이 떨어지는 문제가 발생할 수 있습니다 [1]. 이를 해결하기 위해 중앙 집중식 설정 패키지를 구성하고, 모노레포 루트(Root)에서 파일 패턴을 매핑하여 린트 규칙을 조율(Orchestration)하는 방식이 권장됩니다 [2], [3]. 이러한 방식을 적용하면 각 패키지의 고유한 규칙을 존중하면서도 Turborepo의 캐싱 기능과 `lint-staged`를 활용해 린트 속도를 높이고 유지보수성을 극대화할 수 있습니다 [4], [5]. @@ -30,11 +30,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Monorepo(Turborepo 등) 환경 - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[ESLint]], [[Prettier]], [[Husky]], [[lint-staged]] -- **Projects/Contexts:** [[Turborepo]] +- **Related Topics:** [[ESLint|ESLint]], [[Prettier|Prettier]], [[Husky|Husky]], [[lint-staged|lint-staged]] +- **Projects/Contexts:** [[Turborepo|Turborepo]] - **Contradictions/Notes:** 소스에 관련 정보가 부족합니다. (모노레포 린트 관리 방식과 관련해 소스 내에서 서로 상충되는 주장이나 모순되는 정보는 확인되지 않습니다.) --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/Monorepo(Turborepo 등) 환경의 린트 관리.md]] +- Raw Source: 00_Raw/2026-04-20/Monorepo(Turborepo 등) 환경의 린트 관리.md --- diff --git a/01_Archive/2026-04-20/Monorepo-Architecture-Design.md b/01_Archive/2026-04-20/Monorepo-Architecture-Design.md index 5ebe3d0d..53cb2ef4 100644 --- a/01_Archive/2026-04-20/Monorepo-Architecture-Design.md +++ b/01_Archive/2026-04-20/Monorepo-Architecture-Design.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-4265B0 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Monorepo-Architecture-Design" --- -# [[Monorepo-Architecture-Design]] +# [[Monorepo-Architecture-Design|Monorepo-Architecture-Design]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Monorepo-Architecture-Design" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Monorepo-Architecture-Design.md]] +- Raw Source: 00_Raw/2026-04-20/Monorepo-Architecture-Design.md --- diff --git a/01_Archive/2026-04-20/Monorepo-Architecture.md b/01_Archive/2026-04-20/Monorepo-Architecture.md index 07bed307..69393e7d 100644 --- a/01_Archive/2026-04-20/Monorepo-Architecture.md +++ b/01_Archive/2026-04-20/Monorepo-Architecture.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-69C266 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Monorepo-Architecture" --- -# [[Monorepo-Architecture]] +# [[Monorepo-Architecture|Monorepo-Architecture]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Monorepo-Architecture" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Monorepo-Architecture.md]] +- Raw Source: 00_Raw/2026-04-20/Monorepo-Architecture.md --- diff --git a/01_Archive/2026-04-20/Monorepo-Dependency-Graph-Analysis.md b/01_Archive/2026-04-20/Monorepo-Dependency-Graph-Analysis.md index b4fec12d..e365c418 100644 --- a/01_Archive/2026-04-20/Monorepo-Dependency-Graph-Analysis.md +++ b/01_Archive/2026-04-20/Monorepo-Dependency-Graph-Analysis.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-99AA42 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Monorepo-Dependency-Graph-Analysis" --- -# [[Monorepo-Dependency-Graph-Analysis]] +# [[Monorepo-Dependency-Graph-Analysis|Monorepo-Dependency-Graph-Analysis]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Monorepo-Dependency-Graph-Anal ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Monorepo-Dependency-Graph-Analysis.md]] +- Raw Source: 00_Raw/2026-04-20/Monorepo-Dependency-Graph-Analysis.md --- diff --git a/01_Archive/2026-04-20/Monorepo.md b/01_Archive/2026-04-20/Monorepo.md index 0a482a1c..e1328e66 100644 --- a/01_Archive/2026-04-20/Monorepo.md +++ b/01_Archive/2026-04-20/Monorepo.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-D52D12 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Monorepo" --- -# [[Monorepo]] +# [[Monorepo|Monorepo]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 모노레포(Monorepo)는 다수의 애플리케이션과 라이브러리 패키지(공유 컴포넌트, 유틸리티 등)를 포함하는 서로 연결된 여러 패키지들을 단일 저장소(Repository)에서 관리하는 소프트웨어 아키텍처입니다 [1, 2]. 대규모 프로젝트의 코드 공유를 용이하게 하지만, 패키지마다 개별적인 설정이 중복될 경우 '설정 드리프트(Configuration Drift)' 현상과 같은 유지보수의 어려움을 초래할 수 있습니다 [2, 3]. 이를 효과적으로 관리하기 위해 설정의 중앙 집중화와 루트(Root) 레벨에서의 오케스트레이션(Orchestration) 전략이 활용됩니다 [4, 5]. @@ -23,11 +23,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Monorepo" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[ESLint]], [[Prettier]], [[lint-staged]], [[Husky]], [[Turborepo]] -- **Projects/Contexts:** [[대규모 소프트웨어 엔지니어링 및 CI/CD 파이프라인]], [[자동화된 코드 거버넌스(Automated Governance)]] +- **Related Topics:** [[ESLint|ESLint]], [[Prettier|Prettier]], [[lint-staged|lint-staged]], [[Husky|Husky]], [[Turborepo|Turborepo]] +- **Projects/Contexts:** 대규모 소프트웨어 엔지니어링 및 CI/CD 파이프라인, 자동화된 코드 거버넌스(Automated Governance) - **Contradictions/Notes:** 모노레포 내 `lint-staged` 적용과 관련하여 `lint-staged`의 공식 지침은 저장소 루트에 도구를 설치하고 각 패키지에 완전히 격리된 별도의 설정 파일을 두는 것을 권장하지만 [12, 13], Turborepo를 활용하는 모던 아키텍처 환경에서는 루트에 오케스트레이션 설정 하나를 두고 파일 패턴을 각 패키지 환경에 매핑하는 방식이 더 나은 개발자 경험(DX)을 제공하는 대안으로 제시되기도 합니다 [4, 8]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Monorepo.md]] +- Raw Source: 00_Raw/2026-04-20/Monorepo.md --- diff --git a/01_Archive/2026-04-20/Monosemanticity (일의성).md b/01_Archive/2026-04-20/Monosemanticity (일의성).md index c55e10a6..dd8899b7 100644 --- a/01_Archive/2026-04-20/Monosemanticity (일의성).md +++ b/01_Archive/2026-04-20/Monosemanticity (일의성).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-5B0FC9 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Monosemanticity (일의성)" --- -# [[Monosemanticity (일의성)]] +# [[Monosemanticity (일의성)|Monosemanticity (일의성)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Monosemanticity (일의성)" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Monosemanticity (일의성).md]] +- Raw Source: 00_Raw/2026-04-20/Monosemanticity (일의성).md --- diff --git a/01_Archive/2026-04-20/Monte Carlo Tree Search (MCTS).md b/01_Archive/2026-04-20/Monte Carlo Tree Search (MCTS).md index 99145087..304143d7 100644 --- a/01_Archive/2026-04-20/Monte Carlo Tree Search (MCTS).md +++ b/01_Archive/2026-04-20/Monte Carlo Tree Search (MCTS).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-2E53F8 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Monte Carlo Tree Search (MCTS)" --- -# [[Monte Carlo Tree Search (MCTS)]] +# [[Monte Carlo Tree Search (MCTS)|Monte Carlo Tree Search (MCTS)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Monte Carlo Tree Search (MCTS) ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Monte Carlo Tree Search (MCTS).md]] +- Raw Source: 00_Raw/2026-04-20/Monte Carlo Tree Search (MCTS).md --- diff --git a/01_Archive/2026-04-20/Motion-Capture-Retargeting.md b/01_Archive/2026-04-20/Motion-Capture-Retargeting.md index 7253426f..e714ae04 100644 --- a/01_Archive/2026-04-20/Motion-Capture-Retargeting.md +++ b/01_Archive/2026-04-20/Motion-Capture-Retargeting.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-34FAC7 -category: "[[10_Wiki/💡 Topics/General Knowledge]]" +category: "10_Wiki/💡 Topics/General Knowledge" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Motion-Capture-Retargeting" --- -# [[Motion-Capture-Retargeting]] +# [[Motion-Capture-Retargeting|Motion-Capture-Retargeting]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Motion-Capture-Retargeting" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Motion-Capture-Retargeting.md]] +- Raw Source: 00_Raw/2026-04-20/Motion-Capture-Retargeting.md --- diff --git a/01_Archive/2026-04-20/Motor-Learning-Theory.md b/01_Archive/2026-04-20/Motor-Learning-Theory.md index 06763722..f57c441d 100644 --- a/01_Archive/2026-04-20/Motor-Learning-Theory.md +++ b/01_Archive/2026-04-20/Motor-Learning-Theory.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-D69E40 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Motor-Learning-Theory" --- -# [[Motor-Learning-Theory]] +# [[Motor-Learning-Theory|Motor-Learning-Theory]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Motor-Learning-Theory" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Motor-Learning-Theory.md]] +- Raw Source: 00_Raw/2026-04-20/Motor-Learning-Theory.md --- diff --git a/01_Archive/2026-04-20/Motor-Learning.md b/01_Archive/2026-04-20/Motor-Learning.md index db3f0111..a81d1a45 100644 --- a/01_Archive/2026-04-20/Motor-Learning.md +++ b/01_Archive/2026-04-20/Motor-Learning.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-F3DEAC -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Motor-Learning" --- -# [[Motor-Learning]] +# [[Motor-Learning|Motor-Learning]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Motor-Learning" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Motor-Learning.md]] +- Raw Source: 00_Raw/2026-04-20/Motor-Learning.md --- diff --git a/01_Archive/2026-04-20/Multi-Agent Debate (에이전트 간 토론 전략).md b/01_Archive/2026-04-20/Multi-Agent Debate (에이전트 간 토론 전략).md index 89f47783..d00d3f42 100644 --- a/01_Archive/2026-04-20/Multi-Agent Debate (에이전트 간 토론 전략).md +++ b/01_Archive/2026-04-20/Multi-Agent Debate (에이전트 간 토론 전략).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-A5AF0B -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Multi-Agent Debate (에이전트 간 토론 전략)" --- -# [[Multi-Agent Debate (에이전트 간 토론 전략)]] +# [[Multi-Agent Debate (에이전트 간 토론 전략)|Multi-Agent Debate (에이전트 간 토론 전략)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Multi-Agent Debate (에이전 ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Multi-Agent Debate (에이전트 간 토론 전략).md]] +- Raw Source: 00_Raw/2026-04-20/Multi-Agent Debate (에이전트 간 토론 전략).md --- diff --git a/01_Archive/2026-04-20/Multi-Agent System (다중 에이전트 시스템).md b/01_Archive/2026-04-20/Multi-Agent System (다중 에이전트 시스템).md index c6b0063f..843296ed 100644 --- a/01_Archive/2026-04-20/Multi-Agent System (다중 에이전트 시스템).md +++ b/01_Archive/2026-04-20/Multi-Agent System (다중 에이전트 시스템).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-51D384 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Multi-Agent System (다중 에이전트 시스템)" --- -# [[Multi-Agent System (다중 에이전트 시스템)]] +# [[Multi-Agent System (다중 에이전트 시스템)|Multi-Agent System (다중 에이전트 시스템)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Multi-Agent System (다중 에 ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Multi-Agent System (다중 에이전트 시스템).md]] +- Raw Source: 00_Raw/2026-04-20/Multi-Agent System (다중 에이전트 시스템).md --- diff --git a/01_Archive/2026-04-20/Multi-Agent-Systems.md b/01_Archive/2026-04-20/Multi-Agent-Systems.md index 61e5f83c..cc530626 100644 --- a/01_Archive/2026-04-20/Multi-Agent-Systems.md +++ b/01_Archive/2026-04-20/Multi-Agent-Systems.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-E9AAEE -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Multi-Agent-Systems" --- -# [[Multi-Agent-Systems]] +# [[Multi-Agent-Systems|Multi-Agent-Systems]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Multi-Agent-Systems" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Multi-Agent-Systems.md]] +- Raw Source: 00_Raw/2026-04-20/Multi-Agent-Systems.md --- diff --git a/01_Archive/2026-04-20/Multi-Hop Reasoning (다중 홉 추론).md b/01_Archive/2026-04-20/Multi-Hop Reasoning (다중 홉 추론).md index 76c72a08..5b63a7cd 100644 --- a/01_Archive/2026-04-20/Multi-Hop Reasoning (다중 홉 추론).md +++ b/01_Archive/2026-04-20/Multi-Hop Reasoning (다중 홉 추론).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-411F75 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Multi-Hop Reasoning (다중 홉 추론)" --- -# [[Multi-Hop Reasoning (다중 홉 추론)]] +# [[Multi-Hop Reasoning (다중 홉 추론)|Multi-Hop Reasoning (다중 홉 추론)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Multi-Hop Reasoning (다중 ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Multi-Hop Reasoning (다중 홉 추론).md]] +- Raw Source: 00_Raw/2026-04-20/Multi-Hop Reasoning (다중 홉 추론).md --- diff --git a/01_Archive/2026-04-20/Multi-threaded Architecture.md b/01_Archive/2026-04-20/Multi-threaded Architecture.md index 4c927d37..2b82368c 100644 --- a/01_Archive/2026-04-20/Multi-threaded Architecture.md +++ b/01_Archive/2026-04-20/Multi-threaded Architecture.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-4271F6 -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Multi-threaded Architecture" --- -# [[Multi-threaded Architecture]] +# [[Multi-threaded Architecture|Multi-threaded Architecture]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 자바스크립트의 단일 스레드(Single-thread) 제약을 극복하기 위해 웹 워커(Web Worker)와 OffscreenCanvas를 활용하여 무거운 CPU 연산이나 3D 그래픽 렌더링을 백그라운드로 분리하고, 메인 스레드와 고효율로 상태를 동기화하여 매끄러운 반응성을 보장하는 진보된 애플리케이션 설계 패턴입니다. @@ -29,12 +29,12 @@ github_commit: "[P-Reinforce] Continuous Worker - Multi-threaded Architecture" - **정책 변화:** Graphics & Performance 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Web Worker (웹 워커)]], [[OffscreenCanvas]], [[SharedArrayBuffer]], [[상태 관리 최적화 (Zustand, Jotai, Valtio)]] -- **Projects/Contexts:** [[고성능 실시간 상호작용 시스템을 위한 React 기반 게임 엔진 아키텍처]], [[대규모 데이터 분석 및 시각화 대시보드]] +- **Related Topics:** [[Web Worker (웹 워커)|Web Worker (웹 워커)]], [[OffscreenCanvas|OffscreenCanvas]], [[SharedArrayBuffer|SharedArrayBuffer]], [[상태 관리 최적화 (Zustand, Jotai, Valtio)|상태 관리 최적화 (Zustand, Jotai, Valtio)]] +- **Projects/Contexts:** [[고성능 실시간 상호작용 시스템을 위한 React 기반 게임 엔진 아키텍처|고성능 실시간 상호작용 시스템을 위한 React 기반 게임 엔진 아키텍처]], 대규모 데이터 분석 및 시각화 대시보드 - **Contradictions/Notes:** 멀티스레딩이 무조건적인 성능 향상을 가져오지는 않습니다. 메인 스레드와 워커 스레드 간에 데이터를 주고받는 과정(`postMessage`)에는 직렬화로 인한 오버헤드(약 5~10ms)가 수반됩니다. 따라서 연산 시간이 50ms 미만인 비교적 가벼운 작업을 워커로 분리하면, 통신 비용이 연산 시간보다 커져 오히려 전체 성능이 하락할 수 있으므로 철저한 프로파일링을 기반으로 병목 구간에만 도입해야 합니다. --- _Last updated: 2026-04-15_ -- Raw Source: [[00_Raw/2026-04-20/Multi-threaded Architecture.md]] +- Raw Source: 00_Raw/2026-04-20/Multi-threaded Architecture.md --- diff --git a/01_Archive/2026-04-20/Multimodal Sentiment Analysis.md b/01_Archive/2026-04-20/Multimodal Sentiment Analysis.md index 290bf024..a365a378 100644 --- a/01_Archive/2026-04-20/Multimodal Sentiment Analysis.md +++ b/01_Archive/2026-04-20/Multimodal Sentiment Analysis.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-DF5F90 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Multimodal Sentiment Analysis" --- -# [[Multimodal Sentiment Analysis]] +# [[Multimodal Sentiment Analysis|Multimodal Sentiment Analysis]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Multimodal Sentiment Analysis" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Multimodal Sentiment Analysis.md]] +- Raw Source: 00_Raw/2026-04-20/Multimodal Sentiment Analysis.md --- diff --git a/01_Archive/2026-04-20/Mycological Horror.md b/01_Archive/2026-04-20/Mycological Horror.md index 6cd5ba75..7f325e91 100644 --- a/01_Archive/2026-04-20/Mycological Horror.md +++ b/01_Archive/2026-04-20/Mycological Horror.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-1D7BB8 -category: "[[10_Wiki/💡 Topics/General Knowledge]]" +category: "10_Wiki/💡 Topics/General Knowledge" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Mycological Horror" --- -# [[Mycological Horror]] +# [[Mycological Horror|Mycological Horror]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Mycological Horror" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Mycological Horror.md]] +- Raw Source: 00_Raw/2026-04-20/Mycological Horror.md --- diff --git a/01_Archive/2026-04-20/NASA-Jet-Propulsion-Laboratory-Software-Standards.md b/01_Archive/2026-04-20/NASA-Jet-Propulsion-Laboratory-Software-Standards.md index f5130205..5a4c9958 100644 --- a/01_Archive/2026-04-20/NASA-Jet-Propulsion-Laboratory-Software-Standards.md +++ b/01_Archive/2026-04-20/NASA-Jet-Propulsion-Laboratory-Software-Standards.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-33A414 -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - NASA-Jet-Propulsion-Laboratory-Software-Standards" --- -# [[NASA-Jet-Propulsion-Laboratory-Software-Standards]] +# [[NASA-Jet-Propulsion-Laboratory-Software-Standards|NASA-Jet-Propulsion-Laboratory-Software-Standards]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - NASA-Jet-Propulsion-Laboratory ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/NASA-Jet-Propulsion-Laboratory-Software-Standards.md]] +- Raw Source: 00_Raw/2026-04-20/NASA-Jet-Propulsion-Laboratory-Software-Standards.md --- diff --git a/01_Archive/2026-04-20/NPM Ecosystem.md b/01_Archive/2026-04-20/NPM Ecosystem.md index 807afd0e..539875a8 100644 --- a/01_Archive/2026-04-20/NPM Ecosystem.md +++ b/01_Archive/2026-04-20/NPM Ecosystem.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-B38BB3 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - NPM Ecosystem" --- -# [[NPM Ecosystem]] +# [[NPM Ecosystem|NPM Ecosystem]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - NPM Ecosystem" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/NPM Ecosystem.md]] +- Raw Source: 00_Raw/2026-04-20/NPM Ecosystem.md --- diff --git a/01_Archive/2026-04-20/NVIDIA Omniverse.md b/01_Archive/2026-04-20/NVIDIA Omniverse.md index 04954343..34639c13 100644 --- a/01_Archive/2026-04-20/NVIDIA Omniverse.md +++ b/01_Archive/2026-04-20/NVIDIA Omniverse.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-068667 -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - NVIDIA Omniverse" --- -# [[NVIDIA Omniverse]] +# [[NVIDIA Omniverse|NVIDIA Omniverse]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - NVIDIA Omniverse" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/NVIDIA Omniverse.md]] +- Raw Source: 00_Raw/2026-04-20/NVIDIA Omniverse.md --- diff --git a/01_Archive/2026-04-20/Narrative Design.md b/01_Archive/2026-04-20/Narrative Design.md index 5d493154..abc822fd 100644 --- a/01_Archive/2026-04-20/Narrative Design.md +++ b/01_Archive/2026-04-20/Narrative Design.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-680D4B -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Narrative Design" --- -# [[Narrative Design]] +# [[Narrative Design|Narrative Design]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Narrative Design" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Narrative Design.md]] +- Raw Source: 00_Raw/2026-04-20/Narrative Design.md --- diff --git a/01_Archive/2026-04-20/Narrative Intelligence.md b/01_Archive/2026-04-20/Narrative Intelligence.md index 96d07bd2..c37d6239 100644 --- a/01_Archive/2026-04-20/Narrative Intelligence.md +++ b/01_Archive/2026-04-20/Narrative Intelligence.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-89EE25 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Narrative Intelligence" --- -# [[Narrative Intelligence]] +# [[Narrative Intelligence|Narrative Intelligence]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Narrative Intelligence" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Narrative Intelligence.md]] +- Raw Source: 00_Raw/2026-04-20/Narrative Intelligence.md --- diff --git a/01_Archive/2026-04-20/Narrative-Branching-Models.md b/01_Archive/2026-04-20/Narrative-Branching-Models.md index c236262d..3410bfa8 100644 --- a/01_Archive/2026-04-20/Narrative-Branching-Models.md +++ b/01_Archive/2026-04-20/Narrative-Branching-Models.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-4FC48D -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Narrative-Branching-Models" --- -# [[Narrative-Branching-Models]] +# [[Narrative-Branching-Models|Narrative-Branching-Models]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Narrative-Branching-Models" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Narrative-Branching-Models.md]] +- Raw Source: 00_Raw/2026-04-20/Narrative-Branching-Models.md --- diff --git a/01_Archive/2026-04-20/Narratology.md b/01_Archive/2026-04-20/Narratology.md index 9962f67e..a13d4e24 100644 --- a/01_Archive/2026-04-20/Narratology.md +++ b/01_Archive/2026-04-20/Narratology.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-BAAE58 -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Narratology" --- -# [[Narratology]] +# [[Narratology|Narratology]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Narratology" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Narratology.md]] +- Raw Source: 00_Raw/2026-04-20/Narratology.md --- diff --git a/01_Archive/2026-04-20/Nash Equilibrium.md b/01_Archive/2026-04-20/Nash Equilibrium.md index d1cb5318..2f4194fc 100644 --- a/01_Archive/2026-04-20/Nash Equilibrium.md +++ b/01_Archive/2026-04-20/Nash Equilibrium.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-762E86 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Nash Equilibrium" --- -# [[Nash Equilibrium]] +# [[Nash Equilibrium|Nash Equilibrium]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Nash Equilibrium" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Nash Equilibrium.md]] +- Raw Source: 00_Raw/2026-04-20/Nash Equilibrium.md --- diff --git a/01_Archive/2026-04-20/Nash-Equilibrium.md b/01_Archive/2026-04-20/Nash-Equilibrium.md index c311dae1..970632f3 100644 --- a/01_Archive/2026-04-20/Nash-Equilibrium.md +++ b/01_Archive/2026-04-20/Nash-Equilibrium.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-453B61 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Nash-Equilibrium" --- -# [[Nash-Equilibrium]] +# [[Nash-Equilibrium|Nash-Equilibrium]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Nash-Equilibrium" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Nash-Equilibrium.md]] +- Raw Source: 00_Raw/2026-04-20/Nash-Equilibrium.md --- diff --git a/01_Archive/2026-04-20/Natural Language Processing (NLP) in Narrative.md b/01_Archive/2026-04-20/Natural Language Processing (NLP) in Narrative.md index 3f8d1dbb..2c533c8d 100644 --- a/01_Archive/2026-04-20/Natural Language Processing (NLP) in Narrative.md +++ b/01_Archive/2026-04-20/Natural Language Processing (NLP) in Narrative.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-B5A38A -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Natural Language Processing (NLP) in Narrative" --- -# [[Natural Language Processing (NLP) in Narrative]] +# [[Natural Language Processing (NLP) in Narrative|Natural Language Processing (NLP) in Narrative]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Natural Language Processing (N ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Natural Language Processing (NLP) in Narrative.md]] +- Raw Source: 00_Raw/2026-04-20/Natural Language Processing (NLP) in Narrative.md --- diff --git a/01_Archive/2026-04-20/Natural-Language-Processing.md b/01_Archive/2026-04-20/Natural-Language-Processing.md index f5885d01..c77576c4 100644 --- a/01_Archive/2026-04-20/Natural-Language-Processing.md +++ b/01_Archive/2026-04-20/Natural-Language-Processing.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-92B46C -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Natural-Language-Processing" --- -# [[Natural-Language-Processing]] +# [[Natural-Language-Processing|Natural-Language-Processing]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Natural-Language-Processing" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Natural-Language-Processing.md]] +- Raw Source: 00_Raw/2026-04-20/Natural-Language-Processing.md --- diff --git a/01_Archive/2026-04-20/Naughty Dog Development.md b/01_Archive/2026-04-20/Naughty Dog Development.md index e4c74ae4..c036edcf 100644 --- a/01_Archive/2026-04-20/Naughty Dog Development.md +++ b/01_Archive/2026-04-20/Naughty Dog Development.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-45FC87 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Naughty Dog Development" --- -# [[Naughty Dog Development]] +# [[Naughty Dog Development|Naughty Dog Development]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Naughty Dog Development" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Naughty Dog Development.md]] +- Raw Source: 00_Raw/2026-04-20/Naughty Dog Development.md --- diff --git a/01_Archive/2026-04-20/Needle Engine.md b/01_Archive/2026-04-20/Needle Engine.md index 48241f79..fa7ac4ce 100644 --- a/01_Archive/2026-04-20/Needle Engine.md +++ b/01_Archive/2026-04-20/Needle Engine.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-8D909B -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Needle Engine" --- -# [[Needle Engine]] +# [[Needle Engine|Needle Engine]] ## 📌 한 줄 통찰 (The Karpathy Summary) > Needle Engine은 3D 렌더링 및 웹 애플리케이션 개발을 지원하는 엔진이다 [1]. 동일한 객체(예: 나무)를 반복적으로 렌더링할 때 발생하는 드로우 콜 증가를 막기 위해 GPU 인스턴싱(GPU Instancing) 및 `InstancedMesh`를 활용한 최적화를 제공한다 [1, 2]. 내부적으로 인스턴싱 버퍼가 런타임에 동적으로 증가하면 성능 지연이 발생할 수 있으므로, 버퍼 사전 할당이나 프로그래밍 방식의 인스턴스 생성이 권장된다 [2, 3]. @@ -24,11 +24,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Needle Engine" - **정책 변화:** Graphics & Performance 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[GPU Instancing]], [[InstancedMesh]], [[Draw Call]], [[Overdraw]] -- **Projects/Contexts:** [[Needle Engine 다중 인스턴스(Multiple Instance) 렌더링 최적화 논의]] +- **Related Topics:** GPU Instancing, [[InstancedMesh|InstancedMesh]], [[Draw Call|Draw Call]], [[Overdraw|Overdraw]] +- **Projects/Contexts:** Needle Engine 다중 인스턴스(Multiple Instance) 렌더링 최적화 논의 - **Contradictions/Notes:** Needle Engine 어시스턴트는 성능 지연 방지를 위해 `InstancingHandler.getStartInstanceCount`를 사용해 버퍼를 사전 할당할 것을 제안했지만, 실제 사용자는 이 방식이 매칭되는 모든 렌더러마다 해당 크기의 배열을 반복해서 할당하기 때문에 의도한 최적화 효과를 완전히 얻기 어렵다고 보고했다 [3, 8]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Needle Engine.md]] +- Raw Source: 00_Raw/2026-04-20/Needle Engine.md --- diff --git a/01_Archive/2026-04-20/NestJS-Architecture.md b/01_Archive/2026-04-20/NestJS-Architecture.md index 0b9a5e82..20dd9abb 100644 --- a/01_Archive/2026-04-20/NestJS-Architecture.md +++ b/01_Archive/2026-04-20/NestJS-Architecture.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-641044 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - NestJS-Architecture" --- -# [[NestJS-Architecture]] +# [[NestJS-Architecture|NestJS-Architecture]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - NestJS-Architecture" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/NestJS-Architecture.md]] +- Raw Source: 00_Raw/2026-04-20/NestJS-Architecture.md --- diff --git a/01_Archive/2026-04-20/Netflix 마이크로서비스 전환.md b/01_Archive/2026-04-20/Netflix 마이크로서비스 전환.md index c363150a..f3712551 100644 --- a/01_Archive/2026-04-20/Netflix 마이크로서비스 전환.md +++ b/01_Archive/2026-04-20/Netflix 마이크로서비스 전환.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-7C6103 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Netflix 마이크로서비스 전환" --- -# [[Netflix 마이크로서비스 전환]] +# [[Netflix 마이크로서비스 전환|Netflix 마이크로서비스 전환]] ## 📌 한 줄 통찰 (The Karpathy Summary) > Netflix의 마이크로서비스 전환은 혁신성, 신뢰성, 효율성을 개선하기 위해 기존의 거대한 모놀리식 아키텍처를 독립적으로 배포 및 확장이 가능한 작은 서비스 단위로 쪼갠 7년간의 대규모 마이그레이션 과정입니다 [1, 2]. 이 과정에서 무상태(Stateless) 서비스 지향, 수평적 확장, 데이터베이스의 NoSQL(Cassandra) 전환 및 자동화된 파괴 테스트(Chaos Monkey)를 원칙으로 삼아 99.999%의 높은 가용성을 확보했습니다 [2-4]. 최근에는 모놀리식화된 기존 시스템의 한계를 극복하고자 API, 워크플로우, 서버리스 함수가 결합된 차세대 마이크로서비스 플랫폼인 'Cosmos'를 도입하여 시스템을 한 단계 더 진화시키고 있습니다 [5, 6]. @@ -31,11 +31,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Netflix 마이크로서비스 - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[모놀리식 아키텍처]], [[수평적 확장 (Scale out)]], [[Cassandra]], [[오픈소스 (OSS)]], [[서버리스 함수]] -- **Projects/Contexts:** [[Reloaded 시스템]], [[Cosmos 플랫폼]], [[Chaos Monkey (Simian Army)]] +- **Related Topics:** 모놀리식 아키텍처, 수평적 확장 (Scale out), [[카산드라(Cassandra)|Cassandra]], 오픈소스 (OSS), 서버리스 함수 +- **Projects/Contexts:** Reloaded 시스템, Cosmos 플랫폼, Chaos Monkey (Simian Army) - **Contradictions/Notes:** 마이크로서비스 아키텍처는 혁신과 배포 속도 향상이라는 큰 장점을 가져다주었지만, 반대로 구현 시 분산 시스템의 복잡성을 관리해야 하고 다수의 서비스 인스턴스를 실행하는 데 따른 심각한 메모리 사용량(오버헤드) 증가를 초래한다는 구조적 한계점이 소스에서 분명히 지적되고 있습니다 [10, 11]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/Netflix 마이크로서비스 전환.md]] +- Raw Source: 00_Raw/2026-04-20/Netflix 마이크로서비스 전환.md --- diff --git a/01_Archive/2026-04-20/Network Coordinate Systems.md b/01_Archive/2026-04-20/Network Coordinate Systems.md index c1f0b6e7..e6fd8f28 100644 --- a/01_Archive/2026-04-20/Network Coordinate Systems.md +++ b/01_Archive/2026-04-20/Network Coordinate Systems.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-BF761A -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Network Coordinate Systems" --- -# [[Network Coordinate Systems]] +# [[Network Coordinate Systems|Network Coordinate Systems]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 네트워크 좌표 시스템(Network Coordinate Systems)은 대규모 분산 시스템에서 인터넷 지연 시간(latency)을 다차원 기하학적 공간으로 모델링하는 확장 가능한 지연 시간 추정 시스템입니다 [1]. 소수의 전용 '랜드마크(landmark)' 노드를 기준으로 측정된 기본 지연 시간을 통해 각 호스트 노드에 해당 공간 내의 특정 좌표를 부여합니다 [1]. 이를 통해 개별적인 통신 프로빙을 일일이 수행하지 않더라도, 두 노드 간의 지연 시간을 각 좌표 간의 유클리드 거리(Euclidean distance)로 쉽게 근사할 수 있습니다 [1]. @@ -35,11 +35,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Network Coordinate Systems" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Global Network Positioning (GNP)]], [[Latency Estimation]], [[Passive Latency Discovery]] -- **Projects/Contexts:** [[Google Content Delivery Network (CDN)]], [[Test Traffic Measurements (TTM)]] +- **Related Topics:** [[Global Network Positioning (GNP)|Global Network Positioning (GNP)]], Latency Estimation, Passive Latency Discovery +- **Projects/Contexts:** Google Content Delivery Network (CDN), Test Traffic Measurements (TTM) - **Contradictions/Notes:** Lighthouses나 NPS와 같은 분산형 네트워크 좌표 시스템들은 기존 호스트들을 로컬 랜드마크로 활용하여 확장성을 높일 수 있다고 주장합니다 [22, 23]. 하지만 구글 CDN 연구에서는 이러한 분산형 구조가 오히려 악의적 호스트 관리, 측정 스케줄링 동기화, 전역적 일관성 유지 등의 복잡한 문제를 유발하므로, 고정된 랜드마크 인프라와 중앙 집중식 스케줄러를 사용하는 것이 확장성 제한 없이 훨씬 효율적이고 단순한 해결책이라고 반대 의견을 제시합니다 [24]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Network Coordinate Systems.md]] +- Raw Source: 00_Raw/2026-04-20/Network Coordinate Systems.md --- diff --git a/01_Archive/2026-04-20/Network Science.md b/01_Archive/2026-04-20/Network Science.md index 89a964a8..1f90561b 100644 --- a/01_Archive/2026-04-20/Network Science.md +++ b/01_Archive/2026-04-20/Network Science.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-7C08A1 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Network Science" --- -# [[Network Science]] +# [[Network Science|Network Science]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Network Science" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Network Science.md]] +- Raw Source: 00_Raw/2026-04-20/Network Science.md --- diff --git a/01_Archive/2026-04-20/Network Synchronization in Multiplayer Games.md b/01_Archive/2026-04-20/Network Synchronization in Multiplayer Games.md index d21533ab..745b5cd5 100644 --- a/01_Archive/2026-04-20/Network Synchronization in Multiplayer Games.md +++ b/01_Archive/2026-04-20/Network Synchronization in Multiplayer Games.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-DDB7C3 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Network Synchronization in Multiplayer Games" --- -# [[Network Synchronization in Multiplayer Games]] +# [[Network Synchronization in Multiplayer Games|Network Synchronization in Multiplayer Games]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Network Synchronization in Mul ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Network Synchronization in Multiplayer Games.md]] +- Raw Source: 00_Raw/2026-04-20/Network Synchronization in Multiplayer Games.md --- diff --git a/01_Archive/2026-04-20/Neural-Symbolic-Integration.md b/01_Archive/2026-04-20/Neural-Symbolic-Integration.md index b31e6e8c..dfdf8e6f 100644 --- a/01_Archive/2026-04-20/Neural-Symbolic-Integration.md +++ b/01_Archive/2026-04-20/Neural-Symbolic-Integration.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-86032B -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Neural-Symbolic-Integration" --- -# [[Neural-Symbolic-Integration]] +# [[Neural-Symbolic-Integration|Neural-Symbolic-Integration]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Neural-Symbolic-Integration" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Neural-Symbolic-Integration.md]] +- Raw Source: 00_Raw/2026-04-20/Neural-Symbolic-Integration.md --- diff --git a/01_Archive/2026-04-20/Neuro-Symbolic-AI.md b/01_Archive/2026-04-20/Neuro-Symbolic-AI.md index f9f71017..c5cdd127 100644 --- a/01_Archive/2026-04-20/Neuro-Symbolic-AI.md +++ b/01_Archive/2026-04-20/Neuro-Symbolic-AI.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-3BA811 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Neuro-Symbolic-AI" --- -# [[Neuro-Symbolic-AI]] +# [[Neuro-Symbolic-AI|Neuro-Symbolic-AI]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Neuro-Symbolic-AI" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Neuro-Symbolic-AI.md]] +- Raw Source: 00_Raw/2026-04-20/Neuro-Symbolic-AI.md --- diff --git a/01_Archive/2026-04-20/Neurobiology-of-Reward.md b/01_Archive/2026-04-20/Neurobiology-of-Reward.md index 682ec0b7..4f37374c 100644 --- a/01_Archive/2026-04-20/Neurobiology-of-Reward.md +++ b/01_Archive/2026-04-20/Neurobiology-of-Reward.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-C81C25 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Neurobiology-of-Reward" --- -# [[Neurobiology-of-Reward]] +# [[Neurobiology-of-Reward|Neurobiology-of-Reward]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Neurobiology-of-Reward" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Neurobiology-of-Reward.md]] +- Raw Source: 00_Raw/2026-04-20/Neurobiology-of-Reward.md --- diff --git a/01_Archive/2026-04-20/Neurodevelopmental Disorders.md b/01_Archive/2026-04-20/Neurodevelopmental Disorders.md index c8416f7f..5b46248a 100644 --- a/01_Archive/2026-04-20/Neurodevelopmental Disorders.md +++ b/01_Archive/2026-04-20/Neurodevelopmental Disorders.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-8D1E77 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Neurodevelopmental Disorders" --- -# [[Neurodevelopmental Disorders]] +# [[Neurodevelopmental Disorders|Neurodevelopmental Disorders]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Neurodevelopmental Disorders" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Neurodevelopmental Disorders.md]] +- Raw Source: 00_Raw/2026-04-20/Neurodevelopmental Disorders.md --- diff --git a/01_Archive/2026-04-20/Neuroeconomics.md b/01_Archive/2026-04-20/Neuroeconomics.md index b0c4ef99..f1e3f91e 100644 --- a/01_Archive/2026-04-20/Neuroeconomics.md +++ b/01_Archive/2026-04-20/Neuroeconomics.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-9E20C8 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Neuroeconomics" --- -# [[Neuroeconomics]] +# [[Neuroeconomics|Neuroeconomics]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Neuroeconomics" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Neuroeconomics.md]] +- Raw Source: 00_Raw/2026-04-20/Neuroeconomics.md --- diff --git a/01_Archive/2026-04-20/Neuroergonomics.md b/01_Archive/2026-04-20/Neuroergonomics.md index 8bea9aee..bedbaae8 100644 --- a/01_Archive/2026-04-20/Neuroergonomics.md +++ b/01_Archive/2026-04-20/Neuroergonomics.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-FA4D6C -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Neuroergonomics" --- -# [[Neuroergonomics]] +# [[Neuroergonomics|Neuroergonomics]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Neuroergonomics" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Neuroergonomics.md]] +- Raw Source: 00_Raw/2026-04-20/Neuroergonomics.md --- diff --git a/01_Archive/2026-04-20/Neuromuscular-Adaptation.md b/01_Archive/2026-04-20/Neuromuscular-Adaptation.md index b31689d1..2b994dbe 100644 --- a/01_Archive/2026-04-20/Neuromuscular-Adaptation.md +++ b/01_Archive/2026-04-20/Neuromuscular-Adaptation.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-6E8355 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Neuromuscular-Adaptation" --- -# [[Neuromuscular-Adaptation]] +# [[Neuromuscular-Adaptation|Neuromuscular-Adaptation]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Neuromuscular-Adaptation" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Neuromuscular-Adaptation.md]] +- Raw Source: 00_Raw/2026-04-20/Neuromuscular-Adaptation.md --- diff --git a/01_Archive/2026-04-20/Neuromuscular-Control.md b/01_Archive/2026-04-20/Neuromuscular-Control.md index 958cac14..778870e2 100644 --- a/01_Archive/2026-04-20/Neuromuscular-Control.md +++ b/01_Archive/2026-04-20/Neuromuscular-Control.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-AAABCA -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Neuromuscular-Control" --- -# [[Neuromuscular-Control]] +# [[Neuromuscular-Control|Neuromuscular-Control]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Neuromuscular-Control" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Neuromuscular-Control.md]] +- Raw Source: 00_Raw/2026-04-20/Neuromuscular-Control.md --- diff --git a/01_Archive/2026-04-20/Neuropharmacology of Substance Use Disorders.md b/01_Archive/2026-04-20/Neuropharmacology of Substance Use Disorders.md index 1f0142ac..25ff944b 100644 --- a/01_Archive/2026-04-20/Neuropharmacology of Substance Use Disorders.md +++ b/01_Archive/2026-04-20/Neuropharmacology of Substance Use Disorders.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-8A9F4F -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Neuropharmacology of Substance Use Disorders" --- -# [[Neuropharmacology of Substance Use Disorders]] +# [[Neuropharmacology of Substance Use Disorders|Neuropharmacology of Substance Use Disorders]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Neuropharmacology of Substance ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Neuropharmacology of Substance Use Disorders.md]] +- Raw Source: 00_Raw/2026-04-20/Neuropharmacology of Substance Use Disorders.md --- diff --git a/01_Archive/2026-04-20/Neuroplasticity in Addiction.md b/01_Archive/2026-04-20/Neuroplasticity in Addiction.md index b8df4c3d..a4cc67f0 100644 --- a/01_Archive/2026-04-20/Neuroplasticity in Addiction.md +++ b/01_Archive/2026-04-20/Neuroplasticity in Addiction.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-623B58 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Neuroplasticity in Addiction" --- -# [[Neuroplasticity in Addiction]] +# [[Neuroplasticity in Addiction|Neuroplasticity in Addiction]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Neuroplasticity in Addiction" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Neuroplasticity in Addiction.md]] +- Raw Source: 00_Raw/2026-04-20/Neuroplasticity in Addiction.md --- diff --git a/01_Archive/2026-04-20/Neuroplasticity in Motor Learning.md b/01_Archive/2026-04-20/Neuroplasticity in Motor Learning.md index a51d5a4b..657c0ede 100644 --- a/01_Archive/2026-04-20/Neuroplasticity in Motor Learning.md +++ b/01_Archive/2026-04-20/Neuroplasticity in Motor Learning.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-C1E899 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Neuroplasticity in Motor Learning" --- -# [[Neuroplasticity in Motor Learning]] +# [[Neuroplasticity in Motor Learning|Neuroplasticity in Motor Learning]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Neuroplasticity in Motor Learn ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Neuroplasticity in Motor Learning.md]] +- Raw Source: 00_Raw/2026-04-20/Neuroplasticity in Motor Learning.md --- diff --git a/01_Archive/2026-04-20/Neuroplasticity-in-Motor-Learning.md b/01_Archive/2026-04-20/Neuroplasticity-in-Motor-Learning.md index 1e853588..af4cbb17 100644 --- a/01_Archive/2026-04-20/Neuroplasticity-in-Motor-Learning.md +++ b/01_Archive/2026-04-20/Neuroplasticity-in-Motor-Learning.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-AA0D20 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Neuroplasticity-in-Motor-Learning" --- -# [[Neuroplasticity-in-Motor-Learning]] +# [[Neuroplasticity-in-Motor-Learning|Neuroplasticity-in-Motor-Learning]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Neuroplasticity-in-Motor-Learn ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Neuroplasticity-in-Motor-Learning.md]] +- Raw Source: 00_Raw/2026-04-20/Neuroplasticity-in-Motor-Learning.md --- diff --git a/01_Archive/2026-04-20/Neuroplasticity.md b/01_Archive/2026-04-20/Neuroplasticity.md index 5df8e85a..a044feba 100644 --- a/01_Archive/2026-04-20/Neuroplasticity.md +++ b/01_Archive/2026-04-20/Neuroplasticity.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-PSYCH-007 -category: "[[10_Wiki/💡 Topics/Psychology]]" +category: "10_Wiki/💡 Topics/Psychology" confidence_score: 0.96 tags: [psychology, neuroscience, plasticity, brain] last_reinforced: 2026-04-20 github_commit: "batch-reinforce-05" --- -# [[Neuroplasticity (뇌 가소성)]] +# Neuroplasticity (뇌 가소성) ## 📌 한 줄 통찰 (The Karpathy Summary) > 경험과 학습에 반응하여 뇌의 신경망이 끊임없이 재구성되고 최적화되는 '지성의 유연성'에 대한 생물학적 증명. @@ -24,6 +24,6 @@ github_commit: "batch-reinforce-05" - **정책 변화:** 지식 구조(w2) 관점에서 강화학습의 '가중치 업데이트'를 뇌 가소성의 디지털 추상화로 정의. ## 🔗 지식 연결 (Graph) -- **Parent:** [[10_Wiki/💡 Topics/Psychology]] -- **Related:** [[Dopamine]], [[Addiction_Neuroscience]], [[Learning-Theory]] -- **Raw Source:** [[00_Raw/2026-04-20/Epigenetics of Neuroplasticity.md]] +- **Parent:** 10_Wiki/💡 Topics/Psychology +- **Related:** [[Dopamine|Dopamine]], [[Addiction_Neuroscience|Addiction_Neuroscience]], Learning-Theory +- **Raw Source:** 00_Raw/2026-04-20/Epigenetics of Neuroplasticity.md diff --git a/01_Archive/2026-04-20/Neuroprosthetics-Development.md b/01_Archive/2026-04-20/Neuroprosthetics-Development.md index 2c362e8a..832adb5d 100644 --- a/01_Archive/2026-04-20/Neuroprosthetics-Development.md +++ b/01_Archive/2026-04-20/Neuroprosthetics-Development.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-F99D73 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Neuroprosthetics-Development" --- -# [[Neuroprosthetics-Development]] +# [[Neuroprosthetics-Development|Neuroprosthetics-Development]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Neuroprosthetics-Development" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Neuroprosthetics-Development.md]] +- Raw Source: 00_Raw/2026-04-20/Neuroprosthetics-Development.md --- diff --git a/01_Archive/2026-04-20/Neuropsychiatric Disorders.md b/01_Archive/2026-04-20/Neuropsychiatric Disorders.md index b7ac7c1c..3596d342 100644 --- a/01_Archive/2026-04-20/Neuropsychiatric Disorders.md +++ b/01_Archive/2026-04-20/Neuropsychiatric Disorders.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-57B916 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Neuropsychiatric Disorders" --- -# [[Neuropsychiatric Disorders]] +# [[Neuropsychiatric Disorders|Neuropsychiatric Disorders]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Neuropsychiatric Disorders" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Neuropsychiatric Disorders.md]] +- Raw Source: 00_Raw/2026-04-20/Neuropsychiatric Disorders.md --- diff --git a/01_Archive/2026-04-20/Neuropsychology.md b/01_Archive/2026-04-20/Neuropsychology.md index 128dae8e..0f5038b0 100644 --- a/01_Archive/2026-04-20/Neuropsychology.md +++ b/01_Archive/2026-04-20/Neuropsychology.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-A63619 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Neuropsychology" --- -# [[Neuropsychology]] +# [[Neuropsychology|Neuropsychology]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Neuropsychology" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Neuropsychology.md]] +- Raw Source: 00_Raw/2026-04-20/Neuropsychology.md --- diff --git a/01_Archive/2026-04-20/Neurorehabilitation after Stroke.md b/01_Archive/2026-04-20/Neurorehabilitation after Stroke.md index f18910a9..8f9f5631 100644 --- a/01_Archive/2026-04-20/Neurorehabilitation after Stroke.md +++ b/01_Archive/2026-04-20/Neurorehabilitation after Stroke.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-EB034B -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Neurorehabilitation after Stroke" --- -# [[Neurorehabilitation after Stroke]] +# [[Neurorehabilitation after Stroke|Neurorehabilitation after Stroke]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Neurorehabilitation after Stro ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Neurorehabilitation after Stroke.md]] +- Raw Source: 00_Raw/2026-04-20/Neurorehabilitation after Stroke.md --- diff --git a/01_Archive/2026-04-20/Neurorehabilitation-Post-Stroke.md b/01_Archive/2026-04-20/Neurorehabilitation-Post-Stroke.md index 944b5277..2096f2a5 100644 --- a/01_Archive/2026-04-20/Neurorehabilitation-Post-Stroke.md +++ b/01_Archive/2026-04-20/Neurorehabilitation-Post-Stroke.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-DBB9EB -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Neurorehabilitation-Post-Stroke" --- -# [[Neurorehabilitation-Post-Stroke]] +# [[Neurorehabilitation-Post-Stroke|Neurorehabilitation-Post-Stroke]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Neurorehabilitation-Post-Strok ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Neurorehabilitation-Post-Stroke.md]] +- Raw Source: 00_Raw/2026-04-20/Neurorehabilitation-Post-Stroke.md --- diff --git a/01_Archive/2026-04-20/New Media Theory.md b/01_Archive/2026-04-20/New Media Theory.md index b83c8e55..498a351f 100644 --- a/01_Archive/2026-04-20/New Media Theory.md +++ b/01_Archive/2026-04-20/New Media Theory.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-30D01C -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - New Media Theory" --- -# [[New Media Theory]] +# [[New Media Theory|New Media Theory]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - New Media Theory" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/New Media Theory.md]] +- Raw Source: 00_Raw/2026-04-20/New Media Theory.md --- diff --git a/01_Archive/2026-04-20/New Space(Young Generation).md b/01_Archive/2026-04-20/New Space(Young Generation).md index c6a93469..63dc6f7c 100644 --- a/01_Archive/2026-04-20/New Space(Young Generation).md +++ b/01_Archive/2026-04-20/New Space(Young Generation).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-9FB32F -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - New Space(Young Generation)" --- -# [[New Space(Young Generation)]] +# [[New Space(Young Generation)|New Space(Young Generation)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > V8 엔진의 메모리 힙(Heap) 구조 내에서 새롭게 생성된 객체들이 처음으로 할당되는 공간으로, 'Young Generation(젊은 세대)'이라고도 불린다 [1-3]. 대부분의 객체가 생성 직후 곧바로 접근 불가능해진다는 '세대 가설(Generational Hypothesis)'에 기반하여 설계되었기 때문에, 공간의 크기가 작고 가비지 컬렉션(GC)이 매우 빠르고 빈번하게 일어나는 것이 특징이다 [4-6]. 스캐빈저(Scavenger)라 불리는 마이너 GC(Minor GC)에 의해 공간이 관리되며, 특정 횟수 이상 살아남은 객체들은 Old Space(구세대)로 승격(Promotion)된다 [2, 4]. @@ -30,11 +30,11 @@ github_commit: "[P-Reinforce] Continuous Worker - New Space(Young Generation)" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Minor GC(Scavenger)]], [[Old Space(Old Generation)]], [[Generational Hypothesis]], [[Semi-space Design]] -- **Projects/Contexts:** [[V8 JavaScript Engine]], [[Node.js Memory Management]] +- **Related Topics:** Minor GC(Scavenger), [[Old Space(Old Generation)|Old Space(Old Generation)]], [[Generational Hypothesis|Generational Hypothesis]], Semi-space Design +- **Projects/Contexts:** [[V8 JavaScript Engine|V8 JavaScript Engine]], [[Node.js Memory Management|Node.js Memory Management]] - **Contradictions/Notes:** 소스 간에 New Space의 일반적인 크기 범위에 대한 서술에 약간의 차이가 존재합니다. 소스 [4]은 행동 휴리스틱에 따라 "1MB에서 8MB 사이"라고 명시하지만, 소스 [7]은 "일반적으로 1MB에서 64MB 사이"로 다소 더 큰 범위를 제시합니다. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/New Space(Young Generation).md]] +- Raw Source: 00_Raw/2026-04-20/New Space(Young Generation).md --- diff --git a/01_Archive/2026-04-20/New Space.md b/01_Archive/2026-04-20/New Space.md index 24995f27..67e1f3b2 100644 --- a/01_Archive/2026-04-20/New Space.md +++ b/01_Archive/2026-04-20/New Space.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-BAE893 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - New Space" --- -# [[New Space]] +# [[New Space|New Space]] ## 📌 한 줄 통찰 (The Karpathy Summary) > New Space(뉴 스페이스)는 V8 JavaScript 엔진의 힙(Heap) 메모리 영역 중 하나로, '젊은 세대(Young Generation)'라고도 불리며 대부분의 새로운 객체가 처음 할당되는 작고 빠른 공간입니다 [1-3]. 이 공간은 대부분의 객체가 생성된 직후 접근 불가능해진다는 '세대별 가설(Generational Hypothesis)'에 기반하여 설계되어, 수명이 짧은 객체들을 매우 빈번하고 빠르게 가비지 컬렉션(GC) 하도록 최적화되어 있습니다 [4-6]. 효율적인 메모리 관리를 위해 내부적으로 크기가 동일한 두 개의 반공간(To-Space와 From-Space)으로 나뉘어 운영됩니다 [7-9]. @@ -20,11 +20,11 @@ github_commit: "[P-Reinforce] Continuous Worker - New Space" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Old Space]], [[Scavenger]], [[Garbage Collection]], [[Generational Hypothesis]], [[To-Space]], [[From-Space]] -- **Projects/Contexts:** [[V8 JavaScript Engine]], [[Node.js Memory Management]] +- **Related Topics:** [[Old Space|Old Space]], [[Scavenger 알고리즘|Scavenger]], [[Garbage Collection|Garbage Collection]], [[Generational Hypothesis|Generational Hypothesis]], To-Space, From-Space +- **Projects/Contexts:** [[V8 JavaScript Engine|V8 JavaScript Engine]], [[Node.js Memory Management|Node.js Memory Management]] - **Contradictions/Notes:** 소스 [4] 및 [15]에서는 New Space의 크기가 일반적으로 1~8MB라고 설명하지만, 소스 [8]에서는 전형적으로 1MB~64MB 사이의 크기를 가진다고 주장하여 문헌 간 구체적인 기본 용량 범위에 수치상 차이가 있습니다. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/New Space.md]] +- Raw Source: 00_Raw/2026-04-20/New Space.md --- diff --git a/01_Archive/2026-04-20/Ninja-Build-System.md b/01_Archive/2026-04-20/Ninja-Build-System.md index 43ec8036..f82a163e 100644 --- a/01_Archive/2026-04-20/Ninja-Build-System.md +++ b/01_Archive/2026-04-20/Ninja-Build-System.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-18A8ED -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Ninja-Build-System" --- -# [[Ninja-Build-System]] +# [[Ninja-Build-System|Ninja-Build-System]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Ninja-Build-System" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Ninja-Build-System.md]] +- Raw Source: 00_Raw/2026-04-20/Ninja-Build-System.md --- diff --git a/01_Archive/2026-04-20/No Man's Sky (Large-scale planetary generation).md b/01_Archive/2026-04-20/No Man's Sky (Large-scale planetary generation).md index 7c5682e1..57eb69d8 100644 --- a/01_Archive/2026-04-20/No Man's Sky (Large-scale planetary generation).md +++ b/01_Archive/2026-04-20/No Man's Sky (Large-scale planetary generation).md @@ -1,4 +1,4 @@ -[[No Man's Sky (Large-scale planetary generation)]] +[[No Man's Sky (Large-scale planetary generation)|No Man's Sky (Large-scale planetary generation)]] 📌 Brief Summary *No Man's Sky* utilizes a procedural generation engine based on mathematical deterministic algorithms to create a near-infinite, seamless universe. Rather than storing static assets, the game uses a shared "seed" value and complex noise functions to reconstruct terrain, ecosystems, and celestial bodies in real-time as players traverse space. @@ -12,8 +12,8 @@ The architecture of *No Man's Sky* relies on **Deterministic Procedural Generati * **Seamless Transitioning (Level of Detail - LOD):** To maintain a seamless transition from deep space to planetary surfaces, the engine employs an aggressive, multi-stage LOD system. As the player approaches a planet, the engine progressively increases the resolution of the noise functions and replaces low-fidelity proxies with high-density meshes and complex shader computations, masking the computational "pop-in" through atmospheric fog and volumetric effects. 🔗 Knowledge Connections -* Related Topics: [[Procedural Content Generation (PCG)]], [[L-Systems]], [[Perlin Noise & Fractal Geometry]], [[Deterministic Algorithms]] -* Projects/Contexts: [[Hello Games Engine Architecture]], [[Space Exploration Simulations]], [[Mathematical Modeling of Natural Phenomena]] +* Related Topics: [[Procedural Content Generation (PCG)|Procedural Content Generation (PCG)]], [[L-Systems|L-Systems]], Perlin Noise & Fractal Geometry, [[Deterministic Algorithms|Deterministic Algorithms]] +* Projects/Contexts: Hello Games Engine Architecture, Space Exploration Simulations, Mathematical Modeling of Natural Phenomena * Contradictions/Notes: While the generation is mathematically infinite, it is constrained by a finite "parameter space." The primary technical challenge (and area of ongoing development) is preventing "procedural fatigue," where players recognize repetitive patterns in the underlying noise functions. Last updated: 2026-04-16 \ No newline at end of file diff --git a/01_Archive/2026-04-20/No Man's Sky.md b/01_Archive/2026-04-20/No Man's Sky.md index deb763c4..b188b0cf 100644 --- a/01_Archive/2026-04-20/No Man's Sky.md +++ b/01_Archive/2026-04-20/No Man's Sky.md @@ -1,4 +1,4 @@ -[[No Man's Sky]] +[[No Man's Sky|No Man's Sky]] 📌 Brief Summary No Man's Sky is a procedurally generated space exploration sandbox game developed by Hello Games, utilizing advanced mathematical algorithms to create a virtually infinite, seamless universe. It employs deterministic noise functions (specifically based on Perlin and Simplex noise) to synthesize planetary terrain, ecosystems, and celestial bodies without the need for manual asset placement. The title is a seminal case study in the application of procedural content generation (PCG) within interactive media. @@ -10,8 +10,8 @@ No Man's Sky is a procedurally generated space exploration sandbox game develope * **Evolution of Software Engineering**: The development history of No Man's Sky serves as a significant case study in iterative software deployment. Following its 2016 launch, the developers implemented a continuous integration/continuous deployment (CI/CD) model of content updates, fundamentally altering the game's complexity and feature set through massive-scale algorithmic expansions (e.g., adding multiplayer networking, complex base-building mechanics, and advanced planetary weather systems). 🔗 Knowledge Connections -* Related Topics: [[Procedural Content Generation (PCG)]], [[Deterministic Algorithms]], [[Perlin Noise]], [[L-systems in Biology]] -* Projects/Contexts: [[Hello Games Development Lifecycle]], [[Computational Geometry]], [[Emergent Gameplay Theory]] +* Related Topics: [[Procedural Content Generation (PCG)|Procedural Content Generation (PCG)]], [[Deterministic Algorithms|Deterministic Algorithms]], [[Perlin Noise|Perlin Noise]], [[L-systems in Biology|L-systems in Biology]] +* Projects/Contexts: [[Hello Games Development Lifecycle|Hello Games Development Lifecycle]], [[Computational Geometry|Computational Geometry]], [[Emergent Gameplay Theory|Emergent Gameplay Theory]] * Contradictions/Notes: There is an ongoing academic debate regarding the "infinite" nature of procedural universes; while mathematically infinite, the functional diversity is constrained by the underlying parameter bounds (the "repetition problem" in PCG). Last updated: 2026-04-16 \ No newline at end of file diff --git a/01_Archive/2026-04-20/No Mans Sky (Large-scale planetary generation).md b/01_Archive/2026-04-20/No Mans Sky (Large-scale planetary generation).md index 91e0bf20..323a6768 100644 --- a/01_Archive/2026-04-20/No Mans Sky (Large-scale planetary generation).md +++ b/01_Archive/2026-04-20/No Mans Sky (Large-scale planetary generation).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-3EC0AE -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - No Mans Sky (Large-scale planetary generation)" --- -# [[No Mans Sky (Large-scale planetary generation)]] +# [[No Mans Sky (Large-scale planetary generation)|No Mans Sky (Large-scale planetary generation)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - No Mans Sky (Large-scale plane ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/No Man's Sky (Large-scale planetary generation).md]] +- Raw Source: 00_Raw/2026-04-20/No Man's Sky (Large-scale planetary generation).md --- diff --git a/01_Archive/2026-04-20/No Mans Sky.md b/01_Archive/2026-04-20/No Mans Sky.md index e7c2967e..c848d30f 100644 --- a/01_Archive/2026-04-20/No Mans Sky.md +++ b/01_Archive/2026-04-20/No Mans Sky.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-D9AC35 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - No Mans Sky" --- -# [[No Mans Sky]] +# [[No Mans Sky|No Mans Sky]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - No Mans Sky" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/No Man's Sky.md]] +- Raw Source: 00_Raw/2026-04-20/No Man's Sky.md --- diff --git a/01_Archive/2026-04-20/Node.js Memory Management.md b/01_Archive/2026-04-20/Node.js Memory Management.md index 47943674..ebb5ab89 100644 --- a/01_Archive/2026-04-20/Node.js Memory Management.md +++ b/01_Archive/2026-04-20/Node.js Memory Management.md @@ -1,4 +1,4 @@ -# [[Node.js Memory Management]] +# [[Node.js Memory Management|Node.js Memory Management]] ## 📌 Brief 정Summary Node.js 메모리 관리는 구글의 V8 자바스크립트 엔진에 의해 수행되며, 스택(Stack)과 힙(Heap) 메모리 구조를 기반으로 데이터를 관리합니다 [1-3]. V8은 '대부분의 객체는 일찍 죽는다(Generational Hypothesis)'는 가설에 기반한 세대별 가비지 컬렉션(Generational Garbage Collection)을 사용하여 자동으로 사용되지 않는 메모리를 회수합니다 [4-6]. 단일 프로세스로 장시간 실행되는 Node.js의 특성상 참조가 유지된 채 힙에 쌓이는 객체들은 메모리 누수와 OOM(Out of Memory) 충돌의 주원인이 되므로, 메모리 할당 패턴을 이해하고 적절한 튜닝과 디버깅을 수행하는 것이 필수적입니다 [7-9]. @@ -26,8 +26,8 @@ Node.js 메모리 관리는 구글의 V8 자바스크립트 엔진에 의해 수 * 포인터 압축(Pointer Compression) 기술로 인해 64비트 시스템에서도 V8 힙은 최대 4GB로 제한될 수 있으며, 이를 초과할 경우 빈번한 GC 발생 및 OOM이 일어날 수 있습니다 [63-66]. ## 🔗 Knowledge Connections -- **Related Topics:** [[V8 JavaScript Engine]], [[Garbage Collection]], [[Orinoco GC]], [[Memory Leaks]], [[Pointer Compression]] -- **Projects/Contexts:** [[Node.js Production Monitoring]], [[Chrome DevTools Memory Profiling]] +- **Related Topics:** [[V8 JavaScript Engine|V8 JavaScript Engine]], [[Garbage Collection|Garbage Collection]], [[Orinoco GC|Orinoco GC]], [[Memory Leaks|Memory Leaks]], [[Pointer Compression|Pointer Compression]] +- **Projects/Contexts:** [[Node.js Production Monitoring|Node.js Production Monitoring]], [[Chrome DevTools Memory Profiling|Chrome DevTools Memory Profiling]] - **Contradictions/Notes:** `--expose-gc` 옵션을 사용해 코드 내에서 수동으로 GC(`global.gc()`)를 호출하여 메모리를 회수할 수는 있으나, 과도하게 사용하면 프로그램 성능 저하(Performance degradation)를 초래할 수 있으므로 주의해서 사용해야 한다고 경고합니다 [62, 67]. --- diff --git a/01_Archive/2026-04-20/Node.js Memory Tuning.md b/01_Archive/2026-04-20/Node.js Memory Tuning.md index 6235c90e..6d57262a 100644 --- a/01_Archive/2026-04-20/Node.js Memory Tuning.md +++ b/01_Archive/2026-04-20/Node.js Memory Tuning.md @@ -1,4 +1,4 @@ -# [[Node.js Memory Tuning]] +# [[Node.js Memory Tuning|Node.js Memory Tuning]] ## 📌 Brief Summary Node.js 메모리 튜닝은 V8 자바스크립트 엔진에서 실행되는 Node.js 애플리케이션의 메모리 사용량을 모니터링, 관리 및 최적화하는 과정입니다 [1]. 이 튜닝의 핵심은 V8이 메모리를 힙(New Space 및 Old Space)과 스택으로 구성하는 방식과 가비지 컬렉션(GC)을 통해 메모리를 회수하는 방식을 이해하는 것입니다 [1, 2]. 개발자는 특정 명령줄 플래그를 사용하여 힙 크기와 GC 주기를 조정함으로써 애플리케이션의 성능을 향상시키고 메모리 부족(Out-of-memory)으로 인한 충돌을 방지할 수 있습니다 [1, 3-5]. @@ -23,8 +23,8 @@ Node.js는 메모리 최적화를 위해 V8 엔진의 메모리 관련 설정을 * `--expose-gc`: 코드 내부에서 `global.gc()`를 호출하여 개발자가 수동으로 가비지 컬렉션을 실행할 수 있도록 허용하는 플래그입니다 [14, 15]. ## 🔗 Knowledge Connections -- **Related Topics:** [[V8 JavaScript Engine]], [[Garbage Collection]], [[Heap Memory]], [[Memory Leaks]] -- **Projects/Contexts:** [[Node.js Production Profiling]], [[Performance Optimization]] +- **Related Topics:** [[V8 JavaScript Engine|V8 JavaScript Engine]], [[Garbage Collection|Garbage Collection]], [[힙 메모리(Heap Memory)|Heap Memory]], [[Memory Leaks|Memory Leaks]] +- **Projects/Contexts:** Node.js Production Profiling, [[Performance Optimization|Performance Optimization]] - **Contradictions/Notes:** `--expose-gc` 플래그를 통해 수동으로 가비지 컬렉션을 실행하더라도, V8의 일반적인 자동 GC 알고리즘이 비활성화되는 것은 아닙니다. 수동 호출을 과도하게 사용하면 오히려 성능에 부정적인 영향을 미칠 수 있으므로 주의가 필요합니다 [15]. 또한, `--gc-interval`의 간격을 너무 짧게 설정할 경우 잦은 GC 수행으로 인해 애플리케이션의 성능 저하를 유발할 수 있습니다 [14]. --- diff --git a/01_Archive/2026-04-20/Node.js Production Monitoring.md b/01_Archive/2026-04-20/Node.js Production Monitoring.md index 4903fcec..e0b575da 100644 --- a/01_Archive/2026-04-20/Node.js Production Monitoring.md +++ b/01_Archive/2026-04-20/Node.js Production Monitoring.md @@ -1,4 +1,4 @@ -# [[Node.js Production Monitoring]] +# [[Node.js Production Monitoring|Node.js Production Monitoring]] ## 📌 Brief Summary Node.js 프로덕션 모니터링은 단일 프로세스로 장기 실행되는 Node.js 애플리케이션 환경에서 메모리 누수나 성능 저하를 감지하고 해결하기 위한 필수적인 과정입니다 [1, 2]. 정상적인 가비지 컬렉션(GC) 이후 메모리가 기준치로 돌아오는지(톱니바퀴 패턴) 혹은 계속 증가하는지(래칫 패턴)를 관찰하여 이상 징후를 파악합니다 [2]. 이를 위해 `process.memoryUsage()`, 힙 스냅샷(Heap Snapshot), GC 이벤트 추적, 그리고 Prometheus와 같은 외부 알림 도구를 종합적으로 활용하여 애플리케이션의 OOM(Out of Memory) 충돌을 방지하고 안정성을 유지합니다 [3-5]. @@ -15,8 +15,8 @@ Node.js 프로덕션 모니터링은 단일 프로세스로 장기 실행되는 * **일반적인 경고 및 누수 지표:** 모니터링 중 RSS는 증가하지만 힙 메모리가 안정적이라면 Native Buffer 또는 C++ 바인딩의 누수를 의심해야 하며, 이는 `process.memoryUsage().external`을 통해 확인할 수 있습니다 [12]. 또한, 단일 이벤트 방출기에 리스너가 누적될 때 발생하는 `MaxListenersExceededWarning` 경고는 프로덕션 환경에서 이벤트 리스너 누수의 확실한 신호로 간주됩니다 [6, 12]. ## 🔗 Knowledge Connections -- **Related Topics:** [[V8 Garbage Collection]], [[Heap Snapshot]], [[Memory Leak]], [[Performance Hooks]], [[Prometheus]] -- **Projects/Contexts:** [[Node.js Production Server]] +- **Related Topics:** [[V8 가비지 컬렉션(Garbage Collection)|V8 Garbage Collection]], [[Heap Snapshot|Heap Snapshot]], [[Memory Leak|Memory Leak]], Performance Hooks, Prometheus +- **Projects/Contexts:** Node.js Production Server - **Contradictions/Notes:** Node.js는 단일 프로세스로 수명이 길기 때문에 요청 컨텍스트가 프로세스와 함께 소멸하는 전통적인 다중 프로세스 서버와 다르게 메모리 참조가 지속적으로 누적된다는 구조적 차이점이 있습니다 [1]. 한편, 모니터링이나 특정 엣지 케이스에서 `--expose-gc`를 통해 수동으로 GC(`global.gc()`)를 트리거할 수 있지만, 이는 정상적인 자동 GC 알고리즘을 비활성화하는 것은 아니며 남용할 경우 심각한 성능 저하를 유발할 수 있으므로 주의가 필요합니다 [13, 14]. --- diff --git a/01_Archive/2026-04-20/Node.js 메모리 누수 분석.md b/01_Archive/2026-04-20/Node.js 메모리 누수 분석.md index d90814ec..dbc83659 100644 --- a/01_Archive/2026-04-20/Node.js 메모리 누수 분석.md +++ b/01_Archive/2026-04-20/Node.js 메모리 누수 분석.md @@ -1,4 +1,4 @@ -# [[Node.js 메모리 누수 분석]] +# [[Node.js 메모리 누수 분석|Node.js 메모리 누수 분석]] ## 📌 Brief Summary Node.js의 메모리 누수는 가비지 컬렉션(GC)되어야 할 객체들이 클로저, 이벤트 리스너, 타이머 등의 루트(Root) 객체에 계속 참조되어 메모리에서 해제되지 않을 때 발생합니다 [1, 2]. Node.js는 단일 프로세스로 장기간 실행되는 특성이 있어, 누수된 참조는 모든 요청에 걸쳐 지속적으로 축적되며 결국 V8 힙 한계에 도달하여 OOM(Out-Of-Memory) 크래시를 유발합니다 [3, 4]. 이 문제를 해결하기 위해서는 힙 스냅샷과 메모리 할당 타임라인 도구를 활용하여, 지속적으로 증가하는 객체의 참조 경로(Retaining Path)를 추적하고 참조를 끊어 GC가 정상 작동하도록 근본적인 원인을 수정해야 합니다 [5-7]. @@ -19,8 +19,8 @@ Node.js의 메모리 누수는 가비지 컬렉션(GC)되어야 할 객체들이 * 만약 V8의 힙 영역 중 장기 생존 객체가 저장되는 공간에 큰 메모리가 필요하다면, `--max-old-space-size` 명령줄 플래그로 Old Space 크기를 늘려 애플리케이션 충돌과 과도한 GC 지연을 방지할 수 있습니다 [24]. 반대로, 짧은 주기의 객체 생성이 많은 경우에는 `--max-semi-space-size` 플래그로 New Space를 늘려 마이너 GC 주기를 조절할 수 있습니다 [25]. ## 🔗 Knowledge Connections -- **Related Topics:** [[가비지 컬렉션 (Garbage Collection)]], [[V8 엔진 (V8 Engine)]], [[힙 스냅샷 (Heap Snapshots)]], [[Mark-Sweep]] -- **Projects/Contexts:** [[Chrome DevTools]], [[clinic.js]], [[Node.js Production Monitoring]] +- **Related Topics:** [[가비지 컬렉션 (Garbage Collection)|가비지 컬렉션 (Garbage Collection)]], [[V8 엔진 (V8 Engine)|V8 엔진 (V8 Engine)]], [[힙 스냅샷 (Heap Snapshots)|힙 스냅샷 (Heap Snapshots)]], [[Mark-Sweep|Mark-Sweep]] +- **Projects/Contexts:** [[Chrome DevTools|Chrome DevTools]], [[clinic.js|clinic.js]], [[Node.js Production Monitoring|Node.js Production Monitoring]] - **Contradictions/Notes:** 소스에 따르면 모던 프론트엔드 환경의 브라우저에서는 메모리 누수의 가장 주요한 원인(1위)으로 SPA(Single Page Application) 경로 전환을 꼽고 있지만 [26], Node.js 프로덕션 서버 환경에서는 EventEmitter 리스너 누적이 가장 흔한 메모리 누수 패턴으로 언급되는 차이가 있습니다 [9]. --- diff --git a/01_Archive/2026-04-20/Node.js 메모리 최적화.md b/01_Archive/2026-04-20/Node.js 메모리 최적화.md index 674c5f91..72c5b592 100644 --- a/01_Archive/2026-04-20/Node.js 메모리 최적화.md +++ b/01_Archive/2026-04-20/Node.js 메모리 최적화.md @@ -1,4 +1,4 @@ -# [[Node.js 메모리 최적화]] +# [[Node.js 메모리 최적화|Node.js 메모리 최적화]] ## 📌 Brief Summary Node.js는 V8 엔진을 기반으로 실행되는 단일 프로세스이므로, 시간이 지남에 따라 메모리 누수가 지속적으로 누적될 수 있어 효율적인 메모리 관리가 필수적입니다 [1]. 정상적인 상태의 힙 메모리 사용량은 가비지 컬렉션(GC) 이후 원래 수준으로 돌아가는 톱니바퀴(sawtooth) 패턴을 보이지만, 메모리 누수가 발생하면 반환되지 않고 지속적으로 상승하는 래칫(ratchet) 패턴을 그립니다 [2]. 메모리 최적화는 각종 힙 프로파일링 도구와 명령줄 플래그를 활용하여 애플리케이션의 누수 패턴을 찾아 해결하고, GC 설정 및 힙 공간 크기를 튜닝하여 시스템의 안정성과 성능을 극대화하는 과정입니다 [2-4]. @@ -26,8 +26,8 @@ Node.js는 V8 엔진을 기반으로 실행되는 단일 프로세스이므로, * `--gc-interval` 및 `--expose-gc`: 가비지 컬렉션의 빈도를 강제로 조정하거나, 프로그램 내부에서 `global.gc()`를 호출해 수동으로 가비지 컬렉션을 실행할 수 있도록 하는 옵션입니다 [18-20]. ## 🔗 Knowledge Connections -- **Related Topics:** [[V8 JavaScript Engine]], [[Garbage Collection (GC)]], [[Heap Snapshot]] -- **Projects/Contexts:** [[Chrome DevTools Memory Profiling]], [[Node.js Production Environments]] +- **Related Topics:** [[V8 JavaScript Engine|V8 JavaScript Engine]], [[Garbage Collection (GC)|Garbage Collection (GC)]], [[Heap Snapshot|Heap Snapshot]] +- **Projects/Contexts:** [[Chrome DevTools Memory Profiling|Chrome DevTools Memory Profiling]], Node.js Production Environments - **Contradictions/Notes:** `--expose-gc` 플래그를 통한 수동 가비지 컬렉션 호출(`global.gc()`)은 대량의 데이터 처리 후 즉시 메모리를 회수해야 하는 특수 상황에서 유용할 수 있지만, 일반적인 V8의 자동 GC 메커니즘을 대체하는 것은 아니며 남용 시 과도한 GC 사이클 실행으로 인해 애플리케이션 성능을 크게 저하시킬 위험이 있습니다 [20]. --- diff --git a/01_Archive/2026-04-20/Node.js 메모리 튜닝.md b/01_Archive/2026-04-20/Node.js 메모리 튜닝.md index 5f558d3a..97f2b1a0 100644 --- a/01_Archive/2026-04-20/Node.js 메모리 튜닝.md +++ b/01_Archive/2026-04-20/Node.js 메모리 튜닝.md @@ -1,4 +1,4 @@ -# [[Node.js 메모리 튜닝]] +# [[Node.js 메모리 튜닝|Node.js 메모리 튜닝]] ## 📌 Brief Summary Node.js 메모리 튜닝은 V8 자바스크립트 엔진의 메모리 구조와 가비지 컬렉션(GC) 메커니즘을 이해하고, 이를 최적화하여 애플리케이션의 성능 저하 및 메모리 누수를 방지하는 과정을 의미합니다 [1, 2]. 개발자는 `--max-old-space-size`와 같은 커맨드라인 플래그를 활용해 힙(Heap) 공간을 조절하거나, `process.memoryUsage()`, 힙 스냅샷 등의 도구를 사용하여 비효율적인 메모리 할당 및 해제되지 않은 참조를 추적할 수 있습니다 [3-5]. 결과적으로 주기적인 메모리 모니터링과 올바른 튜닝은 Out-Of-Memory(OOM) 충돌을 예방하고 애플리케이션의 응답 속도를 일정하게 유지하는 데 핵심적인 역할을 합니다 [6, 7]. @@ -27,8 +27,8 @@ Node.js 메모리 튜닝은 V8 자바스크립트 엔진의 메모리 구조와 * 주요 누수 패턴으로는 해제되지 않은 이벤트 리스너(`EventEmitter`), 변수 참조를 잃지 않는 클로저(Closures), 크기 제한이 없는 인메모리 캐시, 정리되지 않은 타이머(`setInterval`), 제대로 닫히지 않은 스트림과 소켓 등이 있습니다 [33-35]. ## 🔗 Knowledge Connections -- **Related Topics:** [[V8 자바스크립트 엔진]], [[가비지 컬렉션(GC)]], [[힙 스냅샷(Heap Snapshot)]], [[메모리 누수(Memory Leak)]] -- **Projects/Contexts:** [[Orinoco GC 프로젝트]], [[Chrome DevTools 메모리 분석]] +- **Related Topics:** [[V8 자바스크립트 엔진|V8 자바스크립트 엔진]], 가비지 컬렉션(GC), [[힙 스냅샷(Heap Snapshot)|힙 스냅샷(Heap Snapshot)]], [[메모리 누수(Memory Leak)|메모리 누수(Memory Leak)]] +- **Projects/Contexts:** Orinoco GC 프로젝트, Chrome DevTools 메모리 분석 - **Contradictions/Notes:** - V8 엔진의 포인터 압축(Pointer Compression) 기능 활성화 시, 64비트 시스템에 128GB의 RAM이 있더라도 단일 V8 프로세스(Isolate)의 관리 힙 크기는 4GB의 연속된 메모리 케이지(Cage)로 엄격하게 제한됩니다 [36-38]. 이 제한에 도달하면 메모리를 확보하기 위해 Major GC의 빈도가 극적으로 증가하며, 결과적으로 OOM 충돌을 유발할 수 있습니다 [38]. - 메모리 최적화를 위해 애플리케이션 코드 내에서 `global.gc()`를 수동으로 지속 호출하는 것은 V8의 자동화된 GC 알고리즘을 방해하고 성능을 떨어뜨릴 수 있으므로 권장되지 않습니다 [22, 39]. diff --git a/01_Archive/2026-04-20/Node.js 성능 디버깅.md b/01_Archive/2026-04-20/Node.js 성능 디버깅.md index a3e2cdf8..40cfc963 100644 --- a/01_Archive/2026-04-20/Node.js 성능 디버깅.md +++ b/01_Archive/2026-04-20/Node.js 성능 디버깅.md @@ -1,4 +1,4 @@ -# [[Node.js 성능 디버깅]] +# [[Node.js 성능 디버깅|Node.js 성능 디버깅]] ## 📌 Brief Summary Node.js 성능 디버깅은 주로 V8 엔진의 힙(Heap) 메모리 사용량을 추적하고 가비지 컬렉션(GC) 동작을 분석하여 애플리케이션의 성능 저하 및 메모리 누수(Memory Leak)를 해결하는 과정이다 [1, 2]. 힙 스냅샷(Heap Snapshot), 할당 타임라인, GC 트레이싱 등의 진단 도구를 활용하여 메모리 내에서 불필요하게 유지되는 참조 객체를 식별한다 [3-5]. 이와 더불어, 실시간 모니터링 API 및 V8 명령줄 플래그 튜닝을 통해 메모리 한계를 조정하여 서버 안정성과 처리량을 최적화할 수 있다 [6-8]. @@ -26,8 +26,8 @@ Node.js 성능 디버깅은 주로 V8 엔진의 힙(Heap) 메모리 사용량을 * `--expose-gc`: 이를 설정하면 애플리케이션 코드 내에서 `global.gc()`를 수동으로 호출하여 대량의 데이터 처리 후 명시적으로 메모리를 회수할 수 있다 [26, 27]. ## 🔗 Knowledge Connections -- **Related Topics:** [[V8 JavaScript Engine]], [[Garbage Collection]], [[Heap Snapshot]], [[Memory Leak]] -- **Projects/Contexts:** [[Chrome DevTools Memory Panel]], [[Node.js Production Environment]] +- **Related Topics:** [[V8 JavaScript Engine|V8 JavaScript Engine]], [[Garbage Collection|Garbage Collection]], [[Heap Snapshot|Heap Snapshot]], [[Memory Leak|Memory Leak]] +- **Projects/Contexts:** [[Chrome DevTools Memory Panel|Chrome DevTools Memory Panel]], Node.js Production Environment - **Contradictions/Notes:** 애플리케이션 개발자가 `System.gc()` 또는 `global.gc()`를 사용하여 수동으로 가비지 컬렉션을 트리거할 수는 있으나, GC 동작을 임의로 예측 및 강제 실행하는 행위는 오히려 애플리케이션의 성능을 저하시킬 수 있으므로 주의해서 사용해야 한다 [27, 28]. --- diff --git a/01_Archive/2026-04-20/Node.js 성능 최적화 및 디버깅.md b/01_Archive/2026-04-20/Node.js 성능 최적화 및 디버깅.md index df2ce158..0712db7c 100644 --- a/01_Archive/2026-04-20/Node.js 성능 최적화 및 디버깅.md +++ b/01_Archive/2026-04-20/Node.js 성능 최적화 및 디버깅.md @@ -1,4 +1,4 @@ -# [[Node.js 성능 최적화 및 디버깅]] +# [[Node.js 성능 최적화 및 디버깅|Node.js 성능 최적화 및 디버깅]] ## 📌 Brief Summary '할당 타임라인(Allocation Timeline)' 도구는 힙 프로파일러의 세부적인 스냅샷 정보와 타임라인 패널의 점진적인 추적 기능을 결합하여 브라우저와 Node.js 환경에서 메모리 할당을 모니터링하는 기능이다 [1, 2]. 이 도구는 기록 세션 동안 최대 50ms마다 주기적으로 힙 스냅샷을 캡처하여 객체의 생명주기를 시각화한다 [3, 4]. 이를 통해 가비지 컬렉션(GC) 이후에도 메모리에 남아있는 객체와 그 참조 경로를 파악함으로써 애플리케이션의 메모리 누수를 감지하고 디버깅하는 데 필수적으로 활용된다 [5-8]. @@ -20,8 +20,8 @@ Node.js 환경에서도 `--inspect` 플래그를 사용하여 크롬 개발자 도구에 연결한 뒤 'Memory > Allocation instrumentation on timeline'을 활용할 수 있다 [7]. 부하 테스트(예: 100~1,000건의 요청)를 진행하면서 타임라인을 기록하고 수거되지 않는 파란색 막대를 확인하여 메모리 누수 위치를 신속하게 특정할 수 있다 [7, 13]. 또한 터미널 레벨에서 `--trace-gc` 플래그를 지정하면 V8 엔진은 메모리 할당 실패(allocation failure) 시 발생하는 GC 이벤트마다 타임스탬프(ms), GC 유형(예: Scavenge, Mark-sweep), GC 전후의 힙 사용량(MB) 및 소요 시간 등을 상세한 텍스트 로그 형태로 출력하여 메모리 포화 상태를 디버깅할 수 있게 해준다 [14-16]. ## 🔗 Knowledge Connections -- **Related Topics:** [[할당 타임라인(Allocation Timeline)]], [[힙 스냅샷(Heap Snapshot)]], [[V8 힙(Heap)]], [[가비지 컬렉션(Garbage Collection)]] -- **Projects/Contexts:** [[Chrome DevTools(크롬 개발자 도구)]], [[Node.js 메모리 누수 분석]] +- **Related Topics:** [[할당 타임라인(Allocation Timeline)|할당 타임라인(Allocation Timeline)]], [[힙 스냅샷(Heap Snapshot)|힙 스냅샷(Heap Snapshot)]], [[V8 힙(Heap)|V8 힙(Heap)]], [[가비지 컬렉션(Garbage Collection)|가비지 컬렉션(Garbage Collection)]] +- **Projects/Contexts:** [[Chrome DevTools(크롬 개발자 도구)|Chrome DevTools(크롬 개발자 도구)]], [[Node.js 메모리 누수 분석|Node.js 메모리 누수 분석]] - **Contradictions/Notes:** 그래프에서 메모리 사용량이 증가한다고 해서 그것이 모두 메모리 누수를 의미하는 것은 아니다. 캐시(Caches), 실행 취소 기록(Undo histories) 등은 의도적으로 데이터를 메모리에 유지하므로, 정상적인 데이터 보존과 우발적인 메모리 누수를 명확히 구분하여 분석해야 한다 [17]. --- diff --git a/01_Archive/2026-04-20/Node.js 프로덕션 메모리 누수 진단.md b/01_Archive/2026-04-20/Node.js 프로덕션 메모리 누수 진단.md index 42945325..8e77a359 100644 --- a/01_Archive/2026-04-20/Node.js 프로덕션 메모리 누수 진단.md +++ b/01_Archive/2026-04-20/Node.js 프로덕션 메모리 누수 진단.md @@ -1,4 +1,4 @@ -# [[Node.js 프로덕션 메모리 누수 진단]] +# [[Node.js 프로덕션 메모리 누수 진단|Node.js 프로덕션 메모리 누수 진단]] ## 📌 Brief Summary Node.js 프로덕션 메모리 누수는 단일 프로세스로 장기 실행되는 Node.js의 특성상 참조가 누적되어 V8 가비지 컬렉터(GC)가 메모리를 회수할 수 없게 되면서 발생합니다 [1, 2]. 정상적인 프로세스와 달리 가비지 컬렉션 이후에도 힙 메모리 사용량이 원래 수준으로 떨어지지 않고 계단식(Ratchet)으로 상승하는 패턴을 보이는 것이 주된 특징입니다 [3, 4]. 이를 진단하고 해결하려면 힙 스냅샷 비교, 힙 프로파일링, 메모리를 계속 참조하고 있는 요인(Retainer)을 추적하는 체계적인 과정이 필수적입니다 [4, 5]. @@ -27,8 +27,8 @@ Node.js 프로덕션 메모리 누수는 단일 프로세스로 장기 실행되 - 비교 결과에서 유출된 객체를 찾은 후, 해당 객체를 유지하고 있는 리테이너(Retainer) 트리를 GC 루트까지 따라가 코드를 수정하고, 수정을 확인하기 위해 테스트를 반복합니다 [4, 20]. ## 🔗 Knowledge Connections -- **Related Topics:** [[V8 Garbage Collection]], [[Heap Snapshot]], [[Retaining Path]], [[process.memoryUsage()]] -- **Projects/Contexts:** [[Node.js Production Environment]], [[Chrome DevTools Memory Panel]] +- **Related Topics:** [[V8 가비지 컬렉션(Garbage Collection)|V8 Garbage Collection]], [[Heap Snapshot|Heap Snapshot]], [[Retaining Path|Retaining Path]], process.memoryUsage() +- **Projects/Contexts:** Node.js Production Environment, [[Chrome DevTools Memory Panel|Chrome DevTools Memory Panel]] - **Contradictions/Notes:** 일반적으로 누수 후보를 찾기 위해 트래픽 전/후 두 개의 힙 스냅샷을 비교하는 방법이 자주 소개되지만, 일회성 메모리 할당으로 인한 오탐(False Positive)을 걸러내기 위해서는 세 개의 스냅샷을 연달아 캡처해 비교하는 "Three-snapshot technique" 기법이 가장 신뢰할 수 있는 수단이라는 점을 유의해야 합니다 [19]. --- diff --git a/01_Archive/2026-04-20/Node.js 프로덕션 메모리 문제 해결.md b/01_Archive/2026-04-20/Node.js 프로덕션 메모리 문제 해결.md index 2201456d..1a3af029 100644 --- a/01_Archive/2026-04-20/Node.js 프로덕션 메모리 문제 해결.md +++ b/01_Archive/2026-04-20/Node.js 프로덕션 메모리 문제 해결.md @@ -1,4 +1,4 @@ -# [[Node.js 프로덕션 메모리 문제 해결]] +# [[Node.js 프로덕션 메모리 문제 해결|Node.js 프로덕션 메모리 문제 해결]] ## 📌 Brief Summary Node.js는 단일 프로세스로 장기간 실행되는 런타임이므로, 코드 내에서 참조가 제대로 해제되지 않은 객체가 누적되면 V8 힙(Heap) 메모리가 점진적으로 고갈되어 궁극적으로 OOM(Out of Memory) 크래시가 발생할 수 있습니다 [1-3]. 프로덕션 환경에서의 메모리 문제 해결은 정상적인 가비지 컬렉션(GC) 패턴과 누수 패턴을 구분하고, 타임라인 및 힙 스냅샷 분석을 통해 누수 객체의 보존 경로(Retaining Path)를 추적하여 근본 원인을 찾아 수정하는 체계적인 과정을 의미합니다 [4-8]. @@ -31,8 +31,8 @@ Node.js는 단일 프로세스로 장기간 실행되는 런타임이므로, 코 5. **패턴 수정 및 검증:** 누수 원인을 7가지 패턴 중 하나로 매칭하여 수정한 뒤, 다시 부하 테스트를 거쳐 GC 이후 힙 메모리가 기준선으로 회복되는지 검증합니다 [6, 27]. ## 🔗 Knowledge Connections -- **Related Topics:** [[Garbage Collection (V8)]], [[Heap Snapshot]], [[Memory Leak Patterns]], [[Orinoco Garbage Collector]] -- **Projects/Contexts:** [[Chrome DevTools Memory Panel]], [[Node.js Production Monitoring]] +- **Related Topics:** Garbage Collection (V8), [[Heap Snapshot|Heap Snapshot]], Memory Leak Patterns, Orinoco Garbage Collector +- **Projects/Contexts:** [[Chrome DevTools Memory Panel|Chrome DevTools Memory Panel]], [[Node.js Production Monitoring|Node.js Production Monitoring]] - **Contradictions/Notes:** 가비지 컬렉션(GC)은 애플리케이션의 힙 메모리를 정리해주지만, 메인 스레드 실행을 멈추는 'stop-the-world' 특성을 지닙니다. V8은 Orinoco 프로젝트를 통해 병렬(Parallel), 점진적(Incremental), 동시적(Concurrent) 처리 기법을 도입하여 지연(Pause) 시간을 최소화했지만 [28-32], 개발자가 `--expose-gc`를 활성화하여 `global.gc()`를 수동으로 강제 호출하는 것은 시스템 성능을 악화시킬 수 있으므로 매우 주의해서 사용해야 한다고 경고하고 있습니다 [33, 34]. --- diff --git a/01_Archive/2026-04-20/Node.js 프로덕션 메모리 병목 분석.md b/01_Archive/2026-04-20/Node.js 프로덕션 메모리 병목 분석.md index b7d187cc..90efde11 100644 --- a/01_Archive/2026-04-20/Node.js 프로덕션 메모리 병목 분석.md +++ b/01_Archive/2026-04-20/Node.js 프로덕션 메모리 병목 분석.md @@ -1,4 +1,4 @@ -# [[Node.js 프로덕션 메모리 병목 분석]] +# [[Node.js 프로덕션 메모리 병목 분석|Node.js 프로덕션 메모리 병목 분석]] ## 📌 Brief Summary Node.js는 단일 프로세스로 장기간 실행되는 특성이 있어, 더 이상 필요하지 않은 객체의 참조가 유지될 경우 V8 힙(Heap) 메모리가 해제되지 않고 지속적으로 누적되는 메모리 누수 현상이 발생할 수 있습니다 [1, 2]. 프로덕션 환경에서 이러한 누수는 가비지 컬렉션(GC)의 오버헤드를 늘려 애플리케이션의 응답 지연이나 OOM(Out of Memory) 크래시 같은 심각한 병목 현상을 유발합니다 [3]. 이를 분석하고 해결하기 위해 개발자는 `--trace-gc` 같은 실행 플래그, `heapdump`를 통한 힙 스냅샷(Heap Snapshot) 획득, 그리고 크롬 개발자 도구(Chrome DevTools) 등을 활용하여 지속적으로 증가하는 객체와 이를 잡아두는 유지 경로(Retaining Path)를 추적해야 합니다 [4-6]. @@ -31,8 +31,8 @@ Node.js는 단일 프로세스로 장기간 실행되는 특성이 있어, 더 * `--max-semi-space-size`: 초당 요청 수가 많아 수명이 짧은 임시 객체가 대량 생성되는 환경에서 New Space의 크기를 늘려 잦은 Minor GC 실행을 줄입니다 [32, 33]. ## 🔗 Knowledge Connections -- **Related Topics:** [[V8 가비지 컬렉션 (Garbage Collection)]], [[힙 스냅샷 (Heap Snapshot)]], [[메모리 누수 (Memory Leaks)]] -- **Projects/Contexts:** [[Chrome DevTools (크롬 개발자 도구)]], [[Node.js 모니터링 및 튜닝]] +- **Related Topics:** [[V8 가비지 컬렉션(Garbage Collection)|V8 가비지 컬렉션 (Garbage Collection)]], [[힙 스냅샷(Heap Snapshot)|힙 스냅샷 (Heap Snapshot)]], [[메모리 누수(Memory Leaks)|메모리 누수 (Memory Leaks)]] +- **Projects/Contexts:** [[Chrome DevTools(크롬 개발자 도구)|Chrome DevTools (크롬 개발자 도구)]], Node.js 모니터링 및 튜닝 - **Contradictions/Notes:** 애플리케이션 내에서 수동으로 GC를 제어하기 위해 `--expose-gc` 플래그를 켜고 `global.gc()`를 호출할 수 있지만, 이 기능은 V8의 자동 가비지 컬렉션을 비활성화하지는 않습니다. 오히려 수동 호출의 남용은 애플리케이션의 응답 속도 등 전체적인 성능에 부정적인 영향을 미칠 수 있으므로 주의해서 사용해야 한다고 소스는 경고합니다 [34, 35]. --- diff --git a/01_Archive/2026-04-20/Node.js 프로세스 모니터링 및 메모리 분석.md b/01_Archive/2026-04-20/Node.js 프로세스 모니터링 및 메모리 분석.md index 4e93d60f..cc2f39d3 100644 --- a/01_Archive/2026-04-20/Node.js 프로세스 모니터링 및 메모리 분석.md +++ b/01_Archive/2026-04-20/Node.js 프로세스 모니터링 및 메모리 분석.md @@ -1,4 +1,4 @@ -# [[Node.js 프로세스 모니터링 및 메모리 분석]] +# [[Node.js 프로세스 모니터링 및 메모리 분석|Node.js 프로세스 모니터링 및 메모리 분석]] ## 📌 Brief Summary Node.js는 V8 엔진 위에서 실행되며, 메모리는 주로 힙(Heap)과 스택(Stack)으로 나뉘어 관리됩니다 [1, 2]. 단일 프로세스로 오랫동안 실행되는 환경 특성상, 코드 상의 실수로 해제되지 않은 메모리 참조가 누적되면 가비지 컬렉터(GC)가 이를 회수하지 못해 Out-Of-Memory(OOM) 크래시로 이어질 수 있습니다 [2, 3]. 따라서 지속적인 메모리 사용량 모니터링과 함께, 힙 스냅샷(Heap Snapshot)과 할당 타임라인(Allocation Timeline) 등의 도구를 활용하여 누수(Leak)의 근본 원인이 되는 객체 참조를 찾아내는 분석 과정이 필수적입니다 [4-6]. @@ -30,8 +30,8 @@ Node.js는 V8 엔진 위에서 실행되며, 메모리는 주로 힙(Heap)과 - `--expose-gc`: 애플리케이션 코드 내에서 `global.gc()`를 호출해 개발자가 수동으로 가비지 컬렉션을 트리거할 수 있게 합니다 [35, 36]. ## 🔗 Knowledge Connections -- **Related Topics:** [[V8 Garbage Collection]], [[Heap Snapshot]], [[Memory Leak Patterns]] -- **Projects/Contexts:** [[Node.js Production Environment]], [[Chrome DevTools Memory Panel]] +- **Related Topics:** [[V8 가비지 컬렉션(Garbage Collection)|V8 Garbage Collection]], [[Heap Snapshot|Heap Snapshot]], Memory Leak Patterns +- **Projects/Contexts:** Node.js Production Environment, [[Chrome DevTools Memory Panel|Chrome DevTools Memory Panel]] - **Contradictions/Notes:** `--expose-gc` 플래그를 사용하여 수동으로 GC를 실행(`global.gc()`)할 수 있지만, 이것이 V8의 일반적인 자동 GC 알고리즘을 비활성화하는 것은 아닙니다. 수동 호출은 보조적인 역할일 뿐이며, 과도하게 사용할 경우 오히려 애플리케이션 성능에 심각한 악영향을 미칠 수 있습니다 [36]. --- diff --git a/01_Archive/2026-04-20/Node.js-Backend-Architecture.md b/01_Archive/2026-04-20/Node.js-Backend-Architecture.md index 3c60a33e..f3c1d4bd 100644 --- a/01_Archive/2026-04-20/Node.js-Backend-Architecture.md +++ b/01_Archive/2026-04-20/Node.js-Backend-Architecture.md @@ -1,4 +1,4 @@ -[[Node.js-Backend-Architecture]] +[[Node.js-Backend-Architecture|Node.js-Backend-Architecture]] 📌 Brief Summary Node.js backend architecture refers to the structural design of server-side applications leveraging the V8 engine's event-driven, non-blocking I/ and single-threaded event loop model. It focuses on optimizing scalability and throughput by managing asynchronous operations through a decoupled, modular approach to handle high concurrency. @@ -12,8 +12,8 @@ Node.js backend architecture refers to the structural design of server-side appl * **Data Flow and Middleware**: The architecture heavily utilizes a middleware pipeline (e.g., Express/Fastify middleware pattern). Each request passes through a series of functions that can modify the request object, perform authentication, or handle error propagation, necessitating well-defined Type Guards and Interface definitions to maintain type safety across the pipeline. 🔗 Knowledge Connections -* Related Topics: [[Dependency-Injection-in-TypeScript]], [[Domain-Driven-Design-Interface-Modeling]] -* Projects/Contexts: [[Enterprise-Scale-Microservices]] +* Related Topics: Dependency-Injection-in-TypeScript, [[Domain-Driven-Design-Interface-Modeling|Domain-Driven-Design-Interface-Modeling]] +* Projects/Contexts: Enterprise-Scale-Microservices * Contradictions/Notes: While the single-threaded nature is an advantage for I/O, it creates a bottleneck for CPU-bound tasks; therefore, architectural decisions must distinguish between I/O-intensive and CPU-intensive workloads. Last updated: 2026-04-17 \ No newline at end of file diff --git a/01_Archive/2026-04-20/Node.js-Global-Namespace-Augmentation.md b/01_Archive/2026-04-20/Node.js-Global-Namespace-Augmentation.md index 23feaea4..1a99deba 100644 --- a/01_Archive/2026-04-20/Node.js-Global-Namespace-Augmentation.md +++ b/01_Archive/2026-04-20/Node.js-Global-Namespace-Augmentation.md @@ -1,4 +1,4 @@ -[[Node.js-Global-Namespace-Augmentation]] +[[Node.js-Global-Namespace-Augmentation|Node.js-Global-Namespace-Augmentation]] 📌 Brief Summary Node.js Global Namespace Augmentation refers to the process of extending the existing type definitions of the global scope (e.g., `global`, `process`, or built-in modules like `Buffer`) within a TypeScript environment. This is achieved through "Declaration Merging," allowing developers to add custom properties or methods to globally available objects while maintaining strict type safety and IntelliSense support across the entire project. @@ -31,8 +31,8 @@ In the context of TypeScript's type system, global namespace augmentation is a s * Augmenting third-party library types that attach metadata to global objects (e.g., adding a `db` connection to the `global` scope in certain ORM configurations). 🔗 Knowledge Connections -* Related Topics: [[Interface-Merging]], [[Declaration-Merging]], [[Ambient-Declarations]] -* Projects/Contexts: [[TypeScript-Type-System-Design]] +* Related Topics: [[Interface-Merging|Interface-Merging]], [[Declaration-Merging|Declaration-Merging]], [[Ambient-Declarations|Ambient-Declarations]] +* Projects/Contexts: [[TypeScript-Type-System-Design|TypeScript-Type-System-Design]] * Contradictions/Notes: Augmenting the global namespace is often considered a "code smell" in modular architecture; while technically powerful for interface design, it can lead to hidden dependencies and side effects that violate the principle of explicit module boundaries. Last updated: 2026-04-17 \ No newline at end of file diff --git a/01_Archive/2026-04-20/Node.js.md b/01_Archive/2026-04-20/Node.js.md index 52ecdc2b..bc72cd68 100644 --- a/01_Archive/2026-04-20/Node.js.md +++ b/01_Archive/2026-04-20/Node.js.md @@ -1,4 +1,4 @@ -# [[Node.js]] +# [[Node.js|Node.js]] ## 📌 Brief Summary Node.js는 구글의 V8 자바스크립트 엔진을 기반으로 구축되어 서버 측에서 자바스크립트를 실행할 수 있게 해주는 런타임 환경입니다 [1]. 전통적인 다중 프로세스 서버와 달리 단일 프로세스로 장시간 실행되는 특징을 가지며, 이로 인해 누수된 참조가 프로세스 수명 동안 지속적으로 누적될 수 있습니다 [2, 3]. Node.js의 메모리 할당 및 가비지 컬렉션(GC)은 전적으로 내장된 V8 엔진의 자동 메모리 관리 메커니즘에 의존합니다 [1, 4]. @@ -11,8 +11,8 @@ Node.js는 구글의 V8 자바스크립트 엔진을 기반으로 구축되어 * **진단 및 추적:** GC 활동은 `--trace-gc` 플래그나 `v8` 모듈, 성능 훅(performance hooks)을 통해 프로그램적으로 추적할 수 있습니다 [20-22]. 메모리 누수가 의심될 때는 Chrome DevTools의 Memory 탭과 `--inspect` 플래그, 또는 `heapdump` 패키지를 이용해 힙 스냅샷을 캡처하고 객체의 유지 경로(Retaining path)를 분석하여 원인을 식별합니다 [23-25]. ## 🔗 Knowledge Connections -- **Related Topics:** [[V8 JavaScript Engine]], [[Garbage Collection]], [[Memory Management]] -- **Projects/Contexts:** [[Node.js Memory Tuning and Diagnostics]], [[Electron and the V8 Memory Cage]] +- **Related Topics:** [[V8 JavaScript Engine|V8 JavaScript Engine]], [[Garbage Collection|Garbage Collection]], [[Memory Management|Memory Management]] +- **Projects/Contexts:** Node.js Memory Tuning and Diagnostics, Electron and the V8 Memory Cage - **Contradictions/Notes:** 수동으로 가비지 컬렉션을 트리거하기 위해 `--expose-gc` 플래그를 사용하여 `global.gc()`를 호출할 수 있지만, 이는 V8의 자동 GC 알고리즘을 비활성화하는 것이 아니며 남용할 경우 성능 저하를 일으킬 수 있으므로 주의해서 사용해야 합니다 [19, 26]. 또한, 전통적인 가비지 컬렉터는 애플리케이션을 완전히 멈추는(stop-the-world) 문제를 유발했으나, V8의 최신 Orinoco GC는 메인 스레드의 멈춤을 최소화하기 위해 병렬(Parallel), 증분(Incremental), 동시(Concurrent) 기법을 도입하여 백그라운드에서 메모리를 회수합니다 [27-30]. --- diff --git a/01_Archive/2026-04-20/Nodejs Memory Management.md b/01_Archive/2026-04-20/Nodejs Memory Management.md index 27aa3785..484e48a0 100644 --- a/01_Archive/2026-04-20/Nodejs Memory Management.md +++ b/01_Archive/2026-04-20/Nodejs Memory Management.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-3D2466 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Nodejs Memory Management" --- -# [[Nodejs Memory Management]] +# [[Nodejs Memory Management|Nodejs Memory Management]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -39,11 +39,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Nodejs Memory Management" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[V8 JavaScript Engine]], [[Garbage Collection]], [[Orinoco GC]], [[Memory Leaks]], [[Pointer Compression]] -- **Projects/Contexts:** [[Node.js Production Monitoring]], [[Chrome DevTools Memory Profiling]] +- **Related Topics:** [[V8 JavaScript Engine|V8 JavaScript Engine]], [[Garbage Collection|Garbage Collection]], [[Orinoco GC|Orinoco GC]], [[Memory Leaks|Memory Leaks]], [[Pointer Compression|Pointer Compression]] +- **Projects/Contexts:** [[Node.js Production Monitoring|Node.js Production Monitoring]], [[Chrome DevTools Memory Profiling|Chrome DevTools Memory Profiling]] - **Contradictions/Notes:** `--expose-gc` 옵션을 사용해 코드 내에서 수동으로 GC(`global.gc()`)를 호출하여 메모리를 회수할 수는 있으나, 과도하게 사용하면 프로그램 성능 저하(Performance degradation)를 초래할 수 있으므로 주의해서 사용해야 한다고 경고합니다 [62, 67]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Node.js Memory Management.md]] +- Raw Source: 00_Raw/2026-04-20/Node.js Memory Management.md --- diff --git a/01_Archive/2026-04-20/Nodejs Memory Tuning.md b/01_Archive/2026-04-20/Nodejs Memory Tuning.md index 50114e63..30840516 100644 --- a/01_Archive/2026-04-20/Nodejs Memory Tuning.md +++ b/01_Archive/2026-04-20/Nodejs Memory Tuning.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-254A8B -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Nodejs Memory Tuning" --- -# [[Nodejs Memory Tuning]] +# [[Nodejs Memory Tuning|Nodejs Memory Tuning]] ## 📌 한 줄 통찰 (The Karpathy Summary) > Node.js 메모리 튜닝은 V8 자바스크립트 엔진에서 실행되는 Node.js 애플리케이션의 메모리 사용량을 모니터링, 관리 및 최적화하는 과정입니다 [1]. 이 튜닝의 핵심은 V8이 메모리를 힙(New Space 및 Old Space)과 스택으로 구성하는 방식과 가비지 컬렉션(GC)을 통해 메모리를 회수하는 방식을 이해하는 것입니다 [1, 2]. 개발자는 특정 명령줄 플래그를 사용하여 힙 크기와 GC 주기를 조정함으로써 애플리케이션의 성능을 향상시키고 메모리 부족(Out-of-memory)으로 인한 충돌을 방지할 수 있습니다 [1, 3-5]. @@ -35,11 +35,11 @@ Node.js는 메모리 최적화를 위해 V8 엔진의 메모리 관련 설정을 - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[V8 JavaScript Engine]], [[Garbage Collection]], [[Heap Memory]], [[Memory Leaks]] -- **Projects/Contexts:** [[Node.js Production Profiling]], [[Performance Optimization]] +- **Related Topics:** [[V8 JavaScript Engine|V8 JavaScript Engine]], [[Garbage Collection|Garbage Collection]], [[힙 메모리(Heap Memory)|Heap Memory]], [[Memory Leaks|Memory Leaks]] +- **Projects/Contexts:** Node.js Production Profiling, [[Performance Optimization|Performance Optimization]] - **Contradictions/Notes:** `--expose-gc` 플래그를 통해 수동으로 가비지 컬렉션을 실행하더라도, V8의 일반적인 자동 GC 알고리즘이 비활성화되는 것은 아닙니다. 수동 호출을 과도하게 사용하면 오히려 성능에 부정적인 영향을 미칠 수 있으므로 주의가 필요합니다 [15]. 또한, `--gc-interval`의 간격을 너무 짧게 설정할 경우 잦은 GC 수행으로 인해 애플리케이션의 성능 저하를 유발할 수 있습니다 [14]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Node.js Memory Tuning.md]] +- Raw Source: 00_Raw/2026-04-20/Node.js Memory Tuning.md --- diff --git a/01_Archive/2026-04-20/Nodejs Production Monitoring.md b/01_Archive/2026-04-20/Nodejs Production Monitoring.md index 55b46459..179883b8 100644 --- a/01_Archive/2026-04-20/Nodejs Production Monitoring.md +++ b/01_Archive/2026-04-20/Nodejs Production Monitoring.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-D6D630 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Nodejs Production Monitoring" --- -# [[Nodejs Production Monitoring]] +# [[Nodejs Production Monitoring|Nodejs Production Monitoring]] ## 📌 한 줄 통찰 (The Karpathy Summary) > Node.js 프로덕션 모니터링은 단일 프로세스로 장기 실행되는 Node.js 애플리케이션 환경에서 메모리 누수나 성능 저하를 감지하고 해결하기 위한 필수적인 과정입니다 [1, 2]. 정상적인 가비지 컬렉션(GC) 이후 메모리가 기준치로 돌아오는지(톱니바퀴 패턴) 혹은 계속 증가하는지(래칫 패턴)를 관찰하여 이상 징후를 파악합니다 [2]. 이를 위해 `process.memoryUsage()`, 힙 스냅샷(Heap Snapshot), GC 이벤트 추적, 그리고 Prometheus와 같은 외부 알림 도구를 종합적으로 활용하여 애플리케이션의 OOM(Out of Memory) 충돌을 방지하고 안정성을 유지합니다 [3-5]. @@ -28,11 +28,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Nodejs Production Monitoring" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[V8 Garbage Collection]], [[Heap Snapshot]], [[Memory Leak]], [[Performance Hooks]], [[Prometheus]] -- **Projects/Contexts:** [[Node.js Production Server]] +- **Related Topics:** [[V8 가비지 컬렉션(Garbage Collection)|V8 Garbage Collection]], [[Heap Snapshot|Heap Snapshot]], [[Memory Leak|Memory Leak]], Performance Hooks, Prometheus +- **Projects/Contexts:** Node.js Production Server - **Contradictions/Notes:** Node.js는 단일 프로세스로 수명이 길기 때문에 요청 컨텍스트가 프로세스와 함께 소멸하는 전통적인 다중 프로세스 서버와 다르게 메모리 참조가 지속적으로 누적된다는 구조적 차이점이 있습니다 [1]. 한편, 모니터링이나 특정 엣지 케이스에서 `--expose-gc`를 통해 수동으로 GC(`global.gc()`)를 트리거할 수 있지만, 이는 정상적인 자동 GC 알고리즘을 비활성화하는 것은 아니며 남용할 경우 심각한 성능 저하를 유발할 수 있으므로 주의가 필요합니다 [13, 14]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Node.js Production Monitoring.md]] +- Raw Source: 00_Raw/2026-04-20/Node.js Production Monitoring.md --- diff --git a/01_Archive/2026-04-20/Nodejs 메모리 누수 분석.md b/01_Archive/2026-04-20/Nodejs 메모리 누수 분석.md index c0aadc5c..0c135d75 100644 --- a/01_Archive/2026-04-20/Nodejs 메모리 누수 분석.md +++ b/01_Archive/2026-04-20/Nodejs 메모리 누수 분석.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-92E707 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Nodejs 메모리 누수 분석" --- -# [[Nodejs 메모리 누수 분석]] +# [[Nodejs 메모리 누수 분석|Nodejs 메모리 누수 분석]] ## 📌 한 줄 통찰 (The Karpathy Summary) > Node.js의 메모리 누수는 가비지 컬렉션(GC)되어야 할 객체들이 클로저, 이벤트 리스너, 타이머 등의 루트(Root) 객체에 계속 참조되어 메모리에서 해제되지 않을 때 발생합니다 [1, 2]. Node.js는 단일 프로세스로 장기간 실행되는 특성이 있어, 누수된 참조는 모든 요청에 걸쳐 지속적으로 축적되며 결국 V8 힙 한계에 도달하여 OOM(Out-Of-Memory) 크래시를 유발합니다 [3, 4]. 이 문제를 해결하기 위해서는 힙 스냅샷과 메모리 할당 타임라인 도구를 활용하여, 지속적으로 증가하는 객체의 참조 경로(Retaining Path)를 추적하고 참조를 끊어 GC가 정상 작동하도록 근본적인 원인을 수정해야 합니다 [5-7]. @@ -31,11 +31,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Nodejs 메모리 누수 분석 - **정책 변화:** AI 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[가비지 컬렉션 (Garbage Collection)]], [[V8 엔진 (V8 Engine)]], [[힙 스냅샷 (Heap Snapshots)]], [[Mark-Sweep]] -- **Projects/Contexts:** [[Chrome DevTools]], [[clinic.js]], [[Node.js Production Monitoring]] +- **Related Topics:** [[가비지 컬렉션 (Garbage Collection)|가비지 컬렉션 (Garbage Collection)]], [[V8 엔진 (V8 Engine)|V8 엔진 (V8 Engine)]], [[힙 스냅샷 (Heap Snapshots)|힙 스냅샷 (Heap Snapshots)]], [[Mark-Sweep|Mark-Sweep]] +- **Projects/Contexts:** [[Chrome DevTools|Chrome DevTools]], [[clinic.js|clinic.js]], [[Node.js Production Monitoring|Node.js Production Monitoring]] - **Contradictions/Notes:** 소스에 따르면 모던 프론트엔드 환경의 브라우저에서는 메모리 누수의 가장 주요한 원인(1위)으로 SPA(Single Page Application) 경로 전환을 꼽고 있지만 [26], Node.js 프로덕션 서버 환경에서는 EventEmitter 리스너 누적이 가장 흔한 메모리 누수 패턴으로 언급되는 차이가 있습니다 [9]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Node.js 메모리 누수 분석.md]] +- Raw Source: 00_Raw/2026-04-20/Node.js 메모리 누수 분석.md --- diff --git a/01_Archive/2026-04-20/Nodejs 메모리 최적화.md b/01_Archive/2026-04-20/Nodejs 메모리 최적화.md index 60c816c2..faf18576 100644 --- a/01_Archive/2026-04-20/Nodejs 메모리 최적화.md +++ b/01_Archive/2026-04-20/Nodejs 메모리 최적화.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-4670EE -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Nodejs 메모리 최적화" --- -# [[Nodejs 메모리 최적화]] +# [[Nodejs 메모리 최적화|Nodejs 메모리 최적화]] ## 📌 한 줄 통찰 (The Karpathy Summary) > Node.js는 V8 엔진을 기반으로 실행되는 단일 프로세스이므로, 시간이 지남에 따라 메모리 누수가 지속적으로 누적될 수 있어 효율적인 메모리 관리가 필수적입니다 [1]. 정상적인 상태의 힙 메모리 사용량은 가비지 컬렉션(GC) 이후 원래 수준으로 돌아가는 톱니바퀴(sawtooth) 패턴을 보이지만, 메모리 누수가 발생하면 반환되지 않고 지속적으로 상승하는 래칫(ratchet) 패턴을 그립니다 [2]. 메모리 최적화는 각종 힙 프로파일링 도구와 명령줄 플래그를 활용하여 애플리케이션의 누수 패턴을 찾아 해결하고, GC 설정 및 힙 공간 크기를 튜닝하여 시스템의 안정성과 성능을 극대화하는 과정입니다 [2-4]. @@ -39,11 +39,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Nodejs 메모리 최적화" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[V8 JavaScript Engine]], [[Garbage Collection (GC)]], [[Heap Snapshot]] -- **Projects/Contexts:** [[Chrome DevTools Memory Profiling]], [[Node.js Production Environments]] +- **Related Topics:** [[V8 JavaScript Engine|V8 JavaScript Engine]], [[Garbage Collection (GC)|Garbage Collection (GC)]], [[Heap Snapshot|Heap Snapshot]] +- **Projects/Contexts:** [[Chrome DevTools Memory Profiling|Chrome DevTools Memory Profiling]], Node.js Production Environments - **Contradictions/Notes:** `--expose-gc` 플래그를 통한 수동 가비지 컬렉션 호출(`global.gc()`)은 대량의 데이터 처리 후 즉시 메모리를 회수해야 하는 특수 상황에서 유용할 수 있지만, 일반적인 V8의 자동 GC 메커니즘을 대체하는 것은 아니며 남용 시 과도한 GC 사이클 실행으로 인해 애플리케이션 성능을 크게 저하시킬 위험이 있습니다 [20]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Node.js 메모리 최적화.md]] +- Raw Source: 00_Raw/2026-04-20/Node.js 메모리 최적화.md --- diff --git a/01_Archive/2026-04-20/Nodejs 메모리 튜닝.md b/01_Archive/2026-04-20/Nodejs 메모리 튜닝.md index 279e2ba9..c54bea06 100644 --- a/01_Archive/2026-04-20/Nodejs 메모리 튜닝.md +++ b/01_Archive/2026-04-20/Nodejs 메모리 튜닝.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-EA5D5E -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Nodejs 메모리 튜닝" --- -# [[Nodejs 메모리 튜닝]] +# [[Nodejs 메모리 튜닝|Nodejs 메모리 튜닝]] ## 📌 한 줄 통찰 (The Karpathy Summary) > Node.js 메모리 튜닝은 V8 자바스크립트 엔진의 메모리 구조와 가비지 컬렉션(GC) 메커니즘을 이해하고, 이를 최적화하여 애플리케이션의 성능 저하 및 메모리 누수를 방지하는 과정을 의미합니다 [1, 2]. 개발자는 `--max-old-space-size`와 같은 커맨드라인 플래그를 활용해 힙(Heap) 공간을 조절하거나, `process.memoryUsage()`, 힙 스냅샷 등의 도구를 사용하여 비효율적인 메모리 할당 및 해제되지 않은 참조를 추적할 수 있습니다 [3-5]. 결과적으로 주기적인 메모리 모니터링과 올바른 튜닝은 Out-Of-Memory(OOM) 충돌을 예방하고 애플리케이션의 응답 속도를 일정하게 유지하는 데 핵심적인 역할을 합니다 [6, 7]. @@ -40,13 +40,13 @@ github_commit: "[P-Reinforce] Continuous Worker - Nodejs 메모리 튜닝" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[V8 자바스크립트 엔진]], [[가비지 컬렉션(GC)]], [[힙 스냅샷(Heap Snapshot)]], [[메모리 누수(Memory Leak)]] -- **Projects/Contexts:** [[Orinoco GC 프로젝트]], [[Chrome DevTools 메모리 분석]] +- **Related Topics:** [[V8 자바스크립트 엔진|V8 자바스크립트 엔진]], 가비지 컬렉션(GC), [[힙 스냅샷(Heap Snapshot)|힙 스냅샷(Heap Snapshot)]], [[메모리 누수(Memory Leak)|메모리 누수(Memory Leak)]] +- **Projects/Contexts:** Orinoco GC 프로젝트, Chrome DevTools 메모리 분석 - **Contradictions/Notes:** - V8 엔진의 포인터 압축(Pointer Compression) 기능 활성화 시, 64비트 시스템에 128GB의 RAM이 있더라도 단일 V8 프로세스(Isolate)의 관리 힙 크기는 4GB의 연속된 메모리 케이지(Cage)로 엄격하게 제한됩니다 [36-38]. 이 제한에 도달하면 메모리를 확보하기 위해 Major GC의 빈도가 극적으로 증가하며, 결과적으로 OOM 충돌을 유발할 수 있습니다 [38]. - 메모리 최적화를 위해 애플리케이션 코드 내에서 `global.gc()`를 수동으로 지속 호출하는 것은 V8의 자동화된 GC 알고리즘을 방해하고 성능을 떨어뜨릴 수 있으므로 권장되지 않습니다 [22, 39]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Node.js 메모리 튜닝.md]] +- Raw Source: 00_Raw/2026-04-20/Node.js 메모리 튜닝.md --- diff --git a/01_Archive/2026-04-20/Nodejs 성능 디버깅.md b/01_Archive/2026-04-20/Nodejs 성능 디버깅.md index 8f020da0..9f5ce368 100644 --- a/01_Archive/2026-04-20/Nodejs 성능 디버깅.md +++ b/01_Archive/2026-04-20/Nodejs 성능 디버깅.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-7A23E5 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Nodejs 성능 디버깅" --- -# [[Nodejs 성능 디버깅]] +# [[Nodejs 성능 디버깅|Nodejs 성능 디버깅]] ## 📌 한 줄 통찰 (The Karpathy Summary) > Node.js 성능 디버깅은 주로 V8 엔진의 힙(Heap) 메모리 사용량을 추적하고 가비지 컬렉션(GC) 동작을 분석하여 애플리케이션의 성능 저하 및 메모리 누수(Memory Leak)를 해결하는 과정이다 [1, 2]. 힙 스냅샷(Heap Snapshot), 할당 타임라인, GC 트레이싱 등의 진단 도구를 활용하여 메모리 내에서 불필요하게 유지되는 참조 객체를 식별한다 [3-5]. 이와 더불어, 실시간 모니터링 API 및 V8 명령줄 플래그 튜닝을 통해 메모리 한계를 조정하여 서버 안정성과 처리량을 최적화할 수 있다 [6-8]. @@ -38,11 +38,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Nodejs 성능 디버깅" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[V8 JavaScript Engine]], [[Garbage Collection]], [[Heap Snapshot]], [[Memory Leak]] -- **Projects/Contexts:** [[Chrome DevTools Memory Panel]], [[Node.js Production Environment]] +- **Related Topics:** [[V8 JavaScript Engine|V8 JavaScript Engine]], [[Garbage Collection|Garbage Collection]], [[Heap Snapshot|Heap Snapshot]], [[Memory Leak|Memory Leak]] +- **Projects/Contexts:** [[Chrome DevTools Memory Panel|Chrome DevTools Memory Panel]], Node.js Production Environment - **Contradictions/Notes:** 애플리케이션 개발자가 `System.gc()` 또는 `global.gc()`를 사용하여 수동으로 가비지 컬렉션을 트리거할 수는 있으나, GC 동작을 임의로 예측 및 강제 실행하는 행위는 오히려 애플리케이션의 성능을 저하시킬 수 있으므로 주의해서 사용해야 한다 [27, 28]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Node.js 성능 디버깅.md]] +- Raw Source: 00_Raw/2026-04-20/Node.js 성능 디버깅.md --- diff --git a/01_Archive/2026-04-20/Nodejs 성능 최적화 및 디버깅.md b/01_Archive/2026-04-20/Nodejs 성능 최적화 및 디버깅.md index 76ec0290..6b83cae5 100644 --- a/01_Archive/2026-04-20/Nodejs 성능 최적화 및 디버깅.md +++ b/01_Archive/2026-04-20/Nodejs 성능 최적화 및 디버깅.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-C8E2E0 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Nodejs 성능 최적화 및 디버깅" --- -# [[Nodejs 성능 최적화 및 디버깅]] +# [[Nodejs 성능 최적화 및 디버깅|Nodejs 성능 최적화 및 디버깅]] ## 📌 한 줄 통찰 (The Karpathy Summary) > '할당 타임라인(Allocation Timeline)' 도구는 힙 프로파일러의 세부적인 스냅샷 정보와 타임라인 패널의 점진적인 추적 기능을 결합하여 브라우저와 Node.js 환경에서 메모리 할당을 모니터링하는 기능이다 [1, 2]. 이 도구는 기록 세션 동안 최대 50ms마다 주기적으로 힙 스냅샷을 캡처하여 객체의 생명주기를 시각화한다 [3, 4]. 이를 통해 가비지 컬렉션(GC) 이후에도 메모리에 남아있는 객체와 그 참조 경로를 파악함으로써 애플리케이션의 메모리 누수를 감지하고 디버깅하는 데 필수적으로 활용된다 [5-8]. @@ -32,11 +32,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Nodejs 성능 최적화 및 - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[할당 타임라인(Allocation Timeline)]], [[힙 스냅샷(Heap Snapshot)]], [[V8 힙(Heap)]], [[가비지 컬렉션(Garbage Collection)]] -- **Projects/Contexts:** [[Chrome DevTools(크롬 개발자 도구)]], [[Node.js 메모리 누수 분석]] +- **Related Topics:** [[할당 타임라인(Allocation Timeline)|할당 타임라인(Allocation Timeline)]], [[힙 스냅샷(Heap Snapshot)|힙 스냅샷(Heap Snapshot)]], [[V8 힙(Heap)|V8 힙(Heap)]], [[가비지 컬렉션(Garbage Collection)|가비지 컬렉션(Garbage Collection)]] +- **Projects/Contexts:** [[Chrome DevTools(크롬 개발자 도구)|Chrome DevTools(크롬 개발자 도구)]], [[Node.js 메모리 누수 분석|Node.js 메모리 누수 분석]] - **Contradictions/Notes:** 그래프에서 메모리 사용량이 증가한다고 해서 그것이 모두 메모리 누수를 의미하는 것은 아니다. 캐시(Caches), 실행 취소 기록(Undo histories) 등은 의도적으로 데이터를 메모리에 유지하므로, 정상적인 데이터 보존과 우발적인 메모리 누수를 명확히 구분하여 분석해야 한다 [17]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Node.js 성능 최적화 및 디버깅.md]] +- Raw Source: 00_Raw/2026-04-20/Node.js 성능 최적화 및 디버깅.md --- diff --git a/01_Archive/2026-04-20/Nodejs 프로덕션 메모리 누수 진단.md b/01_Archive/2026-04-20/Nodejs 프로덕션 메모리 누수 진단.md index d1e15e6f..1384ba37 100644 --- a/01_Archive/2026-04-20/Nodejs 프로덕션 메모리 누수 진단.md +++ b/01_Archive/2026-04-20/Nodejs 프로덕션 메모리 누수 진단.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-AF2866 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Nodejs 프로덕션 메모리 누수 진단" --- -# [[Nodejs 프로덕션 메모리 누수 진단]] +# [[Nodejs 프로덕션 메모리 누수 진단|Nodejs 프로덕션 메모리 누수 진단]] ## 📌 한 줄 통찰 (The Karpathy Summary) > Node.js 프로덕션 메모리 누수는 단일 프로세스로 장기 실행되는 Node.js의 특성상 참조가 누적되어 V8 가비지 컬렉터(GC)가 메모리를 회수할 수 없게 되면서 발생합니다 [1, 2]. 정상적인 프로세스와 달리 가비지 컬렉션 이후에도 힙 메모리 사용량이 원래 수준으로 떨어지지 않고 계단식(Ratchet)으로 상승하는 패턴을 보이는 것이 주된 특징입니다 [3, 4]. 이를 진단하고 해결하려면 힙 스냅샷 비교, 힙 프로파일링, 메모리를 계속 참조하고 있는 요인(Retainer)을 추적하는 체계적인 과정이 필수적입니다 [4, 5]. @@ -40,11 +40,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Nodejs 프로덕션 메모리 - **정책 변화:** AI 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[V8 Garbage Collection]], [[Heap Snapshot]], [[Retaining Path]], [[process.memoryUsage()]] -- **Projects/Contexts:** [[Node.js Production Environment]], [[Chrome DevTools Memory Panel]] +- **Related Topics:** [[V8 가비지 컬렉션(Garbage Collection)|V8 Garbage Collection]], [[Heap Snapshot|Heap Snapshot]], [[Retaining Path|Retaining Path]], process.memoryUsage() +- **Projects/Contexts:** Node.js Production Environment, [[Chrome DevTools Memory Panel|Chrome DevTools Memory Panel]] - **Contradictions/Notes:** 일반적으로 누수 후보를 찾기 위해 트래픽 전/후 두 개의 힙 스냅샷을 비교하는 방법이 자주 소개되지만, 일회성 메모리 할당으로 인한 오탐(False Positive)을 걸러내기 위해서는 세 개의 스냅샷을 연달아 캡처해 비교하는 "Three-snapshot technique" 기법이 가장 신뢰할 수 있는 수단이라는 점을 유의해야 합니다 [19]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Node.js 프로덕션 메모리 누수 진단.md]] +- Raw Source: 00_Raw/2026-04-20/Node.js 프로덕션 메모리 누수 진단.md --- diff --git a/01_Archive/2026-04-20/Nodejs 프로덕션 메모리 문제 해결.md b/01_Archive/2026-04-20/Nodejs 프로덕션 메모리 문제 해결.md index 0a63f4bd..3760c303 100644 --- a/01_Archive/2026-04-20/Nodejs 프로덕션 메모리 문제 해결.md +++ b/01_Archive/2026-04-20/Nodejs 프로덕션 메모리 문제 해결.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-490C25 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Nodejs 프로덕션 메모리 문제 해결" --- -# [[Nodejs 프로덕션 메모리 문제 해결]] +# [[Nodejs 프로덕션 메모리 문제 해결|Nodejs 프로덕션 메모리 문제 해결]] ## 📌 한 줄 통찰 (The Karpathy Summary) > Node.js는 단일 프로세스로 장기간 실행되는 런타임이므로, 코드 내에서 참조가 제대로 해제되지 않은 객체가 누적되면 V8 힙(Heap) 메모리가 점진적으로 고갈되어 궁극적으로 OOM(Out of Memory) 크래시가 발생할 수 있습니다 [1-3]. 프로덕션 환경에서의 메모리 문제 해결은 정상적인 가비지 컬렉션(GC) 패턴과 누수 패턴을 구분하고, 타임라인 및 힙 스냅샷 분석을 통해 누수 객체의 보존 경로(Retaining Path)를 추적하여 근본 원인을 찾아 수정하는 체계적인 과정을 의미합니다 [4-8]. @@ -20,11 +20,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Nodejs 프로덕션 메모리 - **정책 변화:** AI 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Garbage Collection (V8)]], [[Heap Snapshot]], [[Memory Leak Patterns]], [[Orinoco Garbage Collector]] -- **Projects/Contexts:** [[Chrome DevTools Memory Panel]], [[Node.js Production Monitoring]] +- **Related Topics:** Garbage Collection (V8), [[Heap Snapshot|Heap Snapshot]], Memory Leak Patterns, Orinoco Garbage Collector +- **Projects/Contexts:** [[Chrome DevTools Memory Panel|Chrome DevTools Memory Panel]], [[Node.js Production Monitoring|Node.js Production Monitoring]] - **Contradictions/Notes:** 가비지 컬렉션(GC)은 애플리케이션의 힙 메모리를 정리해주지만, 메인 스레드 실행을 멈추는 'stop-the-world' 특성을 지닙니다. V8은 Orinoco 프로젝트를 통해 병렬(Parallel), 점진적(Incremental), 동시적(Concurrent) 처리 기법을 도입하여 지연(Pause) 시간을 최소화했지만 [28-32], 개발자가 `--expose-gc`를 활성화하여 `global.gc()`를 수동으로 강제 호출하는 것은 시스템 성능을 악화시킬 수 있으므로 매우 주의해서 사용해야 한다고 경고하고 있습니다 [33, 34]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Node.js 프로덕션 메모리 문제 해결.md]] +- Raw Source: 00_Raw/2026-04-20/Node.js 프로덕션 메모리 문제 해결.md --- diff --git a/01_Archive/2026-04-20/Nodejs 프로덕션 메모리 병목 분석.md b/01_Archive/2026-04-20/Nodejs 프로덕션 메모리 병목 분석.md index a82f2a42..70f046c4 100644 --- a/01_Archive/2026-04-20/Nodejs 프로덕션 메모리 병목 분석.md +++ b/01_Archive/2026-04-20/Nodejs 프로덕션 메모리 병목 분석.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-76BE33 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Nodejs 프로덕션 메모리 병목 분석" --- -# [[Nodejs 프로덕션 메모리 병목 분석]] +# [[Nodejs 프로덕션 메모리 병목 분석|Nodejs 프로덕션 메모리 병목 분석]] ## 📌 한 줄 통찰 (The Karpathy Summary) > Node.js는 단일 프로세스로 장기간 실행되는 특성이 있어, 더 이상 필요하지 않은 객체의 참조가 유지될 경우 V8 힙(Heap) 메모리가 해제되지 않고 지속적으로 누적되는 메모리 누수 현상이 발생할 수 있습니다 [1, 2]. 프로덕션 환경에서 이러한 누수는 가비지 컬렉션(GC)의 오버헤드를 늘려 애플리케이션의 응답 지연이나 OOM(Out of Memory) 크래시 같은 심각한 병목 현상을 유발합니다 [3]. 이를 분석하고 해결하기 위해 개발자는 `--trace-gc` 같은 실행 플래그, `heapdump`를 통한 힙 스냅샷(Heap Snapshot) 획득, 그리고 크롬 개발자 도구(Chrome DevTools) 등을 활용하여 지속적으로 증가하는 객체와 이를 잡아두는 유지 경로(Retaining Path)를 추적해야 합니다 [4-6]. @@ -43,11 +43,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Nodejs 프로덕션 메모리 - **정책 변화:** AI 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[V8 가비지 컬렉션 (Garbage Collection)]], [[힙 스냅샷 (Heap Snapshot)]], [[메모리 누수 (Memory Leaks)]] -- **Projects/Contexts:** [[Chrome DevTools (크롬 개발자 도구)]], [[Node.js 모니터링 및 튜닝]] +- **Related Topics:** [[V8 가비지 컬렉션(Garbage Collection)|V8 가비지 컬렉션 (Garbage Collection)]], [[힙 스냅샷(Heap Snapshot)|힙 스냅샷 (Heap Snapshot)]], [[메모리 누수(Memory Leaks)|메모리 누수 (Memory Leaks)]] +- **Projects/Contexts:** [[Chrome DevTools(크롬 개발자 도구)|Chrome DevTools (크롬 개발자 도구)]], Node.js 모니터링 및 튜닝 - **Contradictions/Notes:** 애플리케이션 내에서 수동으로 GC를 제어하기 위해 `--expose-gc` 플래그를 켜고 `global.gc()`를 호출할 수 있지만, 이 기능은 V8의 자동 가비지 컬렉션을 비활성화하지는 않습니다. 오히려 수동 호출의 남용은 애플리케이션의 응답 속도 등 전체적인 성능에 부정적인 영향을 미칠 수 있으므로 주의해서 사용해야 한다고 소스는 경고합니다 [34, 35]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Node.js 프로덕션 메모리 병목 분석.md]] +- Raw Source: 00_Raw/2026-04-20/Node.js 프로덕션 메모리 병목 분석.md --- diff --git a/01_Archive/2026-04-20/Nodejs 프로세스 모니터링 및 메모리 분석.md b/01_Archive/2026-04-20/Nodejs 프로세스 모니터링 및 메모리 분석.md index 73ed416c..561e24f3 100644 --- a/01_Archive/2026-04-20/Nodejs 프로세스 모니터링 및 메모리 분석.md +++ b/01_Archive/2026-04-20/Nodejs 프로세스 모니터링 및 메모리 분석.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-56A451 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Nodejs 프로세스 모니터링 및 메모리 분석" --- -# [[Nodejs 프로세스 모니터링 및 메모리 분석]] +# [[Nodejs 프로세스 모니터링 및 메모리 분석|Nodejs 프로세스 모니터링 및 메모리 분석]] ## 📌 한 줄 통찰 (The Karpathy Summary) > Node.js는 V8 엔진 위에서 실행되며, 메모리는 주로 힙(Heap)과 스택(Stack)으로 나뉘어 관리됩니다 [1, 2]. 단일 프로세스로 오랫동안 실행되는 환경 특성상, 코드 상의 실수로 해제되지 않은 메모리 참조가 누적되면 가비지 컬렉터(GC)가 이를 회수하지 못해 Out-Of-Memory(OOM) 크래시로 이어질 수 있습니다 [2, 3]. 따라서 지속적인 메모리 사용량 모니터링과 함께, 힙 스냅샷(Heap Snapshot)과 할당 타임라인(Allocation Timeline) 등의 도구를 활용하여 누수(Leak)의 근본 원인이 되는 객체 참조를 찾아내는 분석 과정이 필수적입니다 [4-6]. @@ -42,11 +42,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Nodejs 프로세스 모니터 - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[V8 Garbage Collection]], [[Heap Snapshot]], [[Memory Leak Patterns]] -- **Projects/Contexts:** [[Node.js Production Environment]], [[Chrome DevTools Memory Panel]] +- **Related Topics:** [[V8 가비지 컬렉션(Garbage Collection)|V8 Garbage Collection]], [[Heap Snapshot|Heap Snapshot]], Memory Leak Patterns +- **Projects/Contexts:** Node.js Production Environment, [[Chrome DevTools Memory Panel|Chrome DevTools Memory Panel]] - **Contradictions/Notes:** `--expose-gc` 플래그를 사용하여 수동으로 GC를 실행(`global.gc()`)할 수 있지만, 이것이 V8의 일반적인 자동 GC 알고리즘을 비활성화하는 것은 아닙니다. 수동 호출은 보조적인 역할일 뿐이며, 과도하게 사용할 경우 오히려 애플리케이션 성능에 심각한 악영향을 미칠 수 있습니다 [36]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Node.js 프로세스 모니터링 및 메모리 분석.md]] +- Raw Source: 00_Raw/2026-04-20/Node.js 프로세스 모니터링 및 메모리 분석.md --- diff --git a/01_Archive/2026-04-20/Nodejs-Backend-Architecture.md b/01_Archive/2026-04-20/Nodejs-Backend-Architecture.md index 61e860e9..a92496c9 100644 --- a/01_Archive/2026-04-20/Nodejs-Backend-Architecture.md +++ b/01_Archive/2026-04-20/Nodejs-Backend-Architecture.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-A782C0 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Nodejs-Backend-Architecture" --- -# [[Nodejs-Backend-Architecture]] +# [[Nodejs-Backend-Architecture|Nodejs-Backend-Architecture]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Nodejs-Backend-Architecture" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Node.js-Backend-Architecture.md]] +- Raw Source: 00_Raw/2026-04-20/Node.js-Backend-Architecture.md --- diff --git a/01_Archive/2026-04-20/Nodejs-Global-Namespace-Augmentation.md b/01_Archive/2026-04-20/Nodejs-Global-Namespace-Augmentation.md index d761ba5f..627f100d 100644 --- a/01_Archive/2026-04-20/Nodejs-Global-Namespace-Augmentation.md +++ b/01_Archive/2026-04-20/Nodejs-Global-Namespace-Augmentation.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-D512F0 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Nodejs-Global-Namespace-Augmentation" --- -# [[Nodejs-Global-Namespace-Augmentation]] +# [[Nodejs-Global-Namespace-Augmentation|Nodejs-Global-Namespace-Augmentation]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Nodejs-Global-Namespace-Augmen ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Node.js-Global-Namespace-Augmentation.md]] +- Raw Source: 00_Raw/2026-04-20/Node.js-Global-Namespace-Augmentation.md --- diff --git a/01_Archive/2026-04-20/Nodejs.md b/01_Archive/2026-04-20/Nodejs.md index cb4c3a38..71e20ed1 100644 --- a/01_Archive/2026-04-20/Nodejs.md +++ b/01_Archive/2026-04-20/Nodejs.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-09A043 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Nodejs" --- -# [[Nodejs]] +# [[Nodejs|Nodejs]] ## 📌 한 줄 통찰 (The Karpathy Summary) > Node.js는 구글의 V8 자바스크립트 엔진을 기반으로 구축되어 서버 측에서 자바스크립트를 실행할 수 있게 해주는 런타임 환경입니다 [1]. 전통적인 다중 프로세스 서버와 달리 단일 프로세스로 장시간 실행되는 특징을 가지며, 이로 인해 누수된 참조가 프로세스 수명 동안 지속적으로 누적될 수 있습니다 [2, 3]. Node.js의 메모리 할당 및 가비지 컬렉션(GC)은 전적으로 내장된 V8 엔진의 자동 메모리 관리 메커니즘에 의존합니다 [1, 4]. @@ -24,11 +24,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Nodejs" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[V8 JavaScript Engine]], [[Garbage Collection]], [[Memory Management]] -- **Projects/Contexts:** [[Node.js Memory Tuning and Diagnostics]], [[Electron and the V8 Memory Cage]] +- **Related Topics:** [[V8 JavaScript Engine|V8 JavaScript Engine]], [[Garbage Collection|Garbage Collection]], [[Memory Management|Memory Management]] +- **Projects/Contexts:** Node.js Memory Tuning and Diagnostics, Electron and the V8 Memory Cage - **Contradictions/Notes:** 수동으로 가비지 컬렉션을 트리거하기 위해 `--expose-gc` 플래그를 사용하여 `global.gc()`를 호출할 수 있지만, 이는 V8의 자동 GC 알고리즘을 비활성화하는 것이 아니며 남용할 경우 성능 저하를 일으킬 수 있으므로 주의해서 사용해야 합니다 [19, 26]. 또한, 전통적인 가비지 컬렉터는 애플리케이션을 완전히 멈추는(stop-the-world) 문제를 유발했으나, V8의 최신 Orinoco GC는 메인 스레드의 멈춤을 최소화하기 위해 병렬(Parallel), 증분(Incremental), 동시(Concurrent) 기법을 도입하여 백그라운드에서 메모리를 회수합니다 [27-30]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Node.js.md]] +- Raw Source: 00_Raw/2026-04-20/Node.js.md --- diff --git a/01_Archive/2026-04-20/Nominal Typing.md b/01_Archive/2026-04-20/Nominal Typing.md index dd9a9aca..6b39baa5 100644 --- a/01_Archive/2026-04-20/Nominal Typing.md +++ b/01_Archive/2026-04-20/Nominal Typing.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-29D050 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Nominal Typing" --- -# [[Nominal Typing]] +# [[Nominal Typing|Nominal Typing]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Nominal Typing" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Nominal Typing.md]] +- Raw Source: 00_Raw/2026-04-20/Nominal Typing.md --- diff --git a/01_Archive/2026-04-20/Nominal-Subtyping.md b/01_Archive/2026-04-20/Nominal-Subtyping.md index d6c2157c..d4a6a428 100644 --- a/01_Archive/2026-04-20/Nominal-Subtyping.md +++ b/01_Archive/2026-04-20/Nominal-Subtyping.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-60CC9F -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Nominal-Subtyping" --- -# [[Nominal-Subtyping]] +# [[Nominal-Subtyping|Nominal-Subtyping]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Nominal-Subtyping" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Nominal-Subtyping.md]] +- Raw Source: 00_Raw/2026-04-20/Nominal-Subtyping.md --- diff --git a/01_Archive/2026-04-20/Nominal-Typing-in-TypeScript.md b/01_Archive/2026-04-20/Nominal-Typing-in-TypeScript.md index 723e9eae..77897163 100644 --- a/01_Archive/2026-04-20/Nominal-Typing-in-TypeScript.md +++ b/01_Archive/2026-04-20/Nominal-Typing-in-TypeScript.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-C4D501 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Nominal-Typing-in-TypeScript" --- -# [[Nominal-Typing-in-TypeScript]] +# [[Nominal-Typing-in-TypeScript|Nominal-Typing-in-TypeScript]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Nominal-Typing-in-TypeScript" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Nominal-Typing-in-TypeScript.md]] +- Raw Source: 00_Raw/2026-04-20/Nominal-Typing-in-TypeScript.md --- diff --git a/01_Archive/2026-04-20/Nominal-Typing-via-Branded-Types.md b/01_Archive/2026-04-20/Nominal-Typing-via-Branded-Types.md index e8e832f6..b7bf12fa 100644 --- a/01_Archive/2026-04-20/Nominal-Typing-via-Branded-Types.md +++ b/01_Archive/2026-04-20/Nominal-Typing-via-Branded-Types.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-695155 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Nominal-Typing-via-Branded-Types" --- -# [[Nominal-Typing-via-Branded-Types]] +# [[Nominal-Typing-via-Branded-Types|Nominal-Typing-via-Branded-Types]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Nominal-Typing-via-Branded-Typ ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Nominal-Typing-via-Branded-Types.md]] +- Raw Source: 00_Raw/2026-04-20/Nominal-Typing-via-Branded-Types.md --- diff --git a/01_Archive/2026-04-20/Nominal-Typing-vs-Structural-Typing.md b/01_Archive/2026-04-20/Nominal-Typing-vs-Structural-Typing.md index b857e52c..98477355 100644 --- a/01_Archive/2026-04-20/Nominal-Typing-vs-Structural-Typing.md +++ b/01_Archive/2026-04-20/Nominal-Typing-vs-Structural-Typing.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-1B9D2D -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Nominal-Typing-vs-Structural-Typing" --- -# [[Nominal-Typing-vs-Structural-Typing]] +# [[Nominal-Typing-vs-Structural-Typing|Nominal-Typing-vs-Structural-Typing]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Nominal-Typing-vs-Structural-T ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Nominal-Typing-vs-Structural-Typing.md]] +- Raw Source: 00_Raw/2026-04-20/Nominal-Typing-vs-Structural-Typing.md --- diff --git a/01_Archive/2026-04-20/Nominal-Typing.md b/01_Archive/2026-04-20/Nominal-Typing.md index 2ea09d9c..c537a189 100644 --- a/01_Archive/2026-04-20/Nominal-Typing.md +++ b/01_Archive/2026-04-20/Nominal-Typing.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-F87246 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Nominal-Typing" --- -# [[Nominal-Typing]] +# [[Nominal-Typing|Nominal-Typing]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Nominal-Typing" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Nominal-Typing.md]] +- Raw Source: 00_Raw/2026-04-20/Nominal-Typing.md --- diff --git a/01_Archive/2026-04-20/Nominal-vs-Structural-Typing.md b/01_Archive/2026-04-20/Nominal-vs-Structural-Typing.md index 59c16485..e2a8f3c7 100644 --- a/01_Archive/2026-04-20/Nominal-vs-Structural-Typing.md +++ b/01_Archive/2026-04-20/Nominal-vs-Structural-Typing.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-F75BC3 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Nominal-vs-Structural-Typing" --- -# [[Nominal-vs-Structural-Typing]] +# [[Nominal-vs-Structural-Typing|Nominal-vs-Structural-Typing]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Nominal-vs-Structural-Typing" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Nominal-vs-Structural-Typing.md]] +- Raw Source: 00_Raw/2026-04-20/Nominal-vs-Structural-Typing.md --- diff --git a/01_Archive/2026-04-20/Non-Diegetic UI.md b/01_Archive/2026-04-20/Non-Diegetic UI.md index e8bf6f0b..2e8f25e2 100644 --- a/01_Archive/2026-04-20/Non-Diegetic UI.md +++ b/01_Archive/2026-04-20/Non-Diegetic UI.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-0D2F57 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Non-Diegetic UI" --- -# [[Non-Diegetic UI]] +# [[Non-Diegetic UI|Non-Diegetic UI]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Non-Diegetic UI" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Non-Diegetic UI.md]] +- Raw Source: 00_Raw/2026-04-20/Non-Diegetic UI.md --- diff --git a/01_Archive/2026-04-20/Non-Photorealistic-Rendering-in-Level-Design.md b/01_Archive/2026-04-20/Non-Photorealistic-Rendering-in-Level-Design.md index f61f750d..050b0271 100644 --- a/01_Archive/2026-04-20/Non-Photorealistic-Rendering-in-Level-Design.md +++ b/01_Archive/2026-04-20/Non-Photorealistic-Rendering-in-Level-Design.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-7D2198 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Non-Photorealistic-Rendering-in-Level-Design" --- -# [[Non-Photorealistic-Rendering-in-Level-Design]] +# [[Non-Photorealistic-Rendering-in-Level-Design|Non-Photorealistic-Rendering-in-Level-Design]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Non-Photorealistic-Rendering-i ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Non-Photorealistic-Rendering-in-Level-Design.md]] +- Raw Source: 00_Raw/2026-04-20/Non-Photorealistic-Rendering-in-Level-Design.md --- diff --git a/01_Archive/2026-04-20/Non-null Assertion Operator.md b/01_Archive/2026-04-20/Non-null Assertion Operator.md index 5dee75d7..b30aeabc 100644 --- a/01_Archive/2026-04-20/Non-null Assertion Operator.md +++ b/01_Archive/2026-04-20/Non-null Assertion Operator.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-D4BCC2 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Non-null Assertion Operator" --- -# [[Non-null Assertion Operator]] +# [[Non-null Assertion Operator|Non-null Assertion Operator]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -22,11 +22,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Non-null Assertion Operator" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[null]], [[undefined]], [[Type Assertions]] +- **Related Topics:** null, undefined, [[타입 단언 (Type Assertions)|Type Assertions]] - **Projects/Contexts:** TypeScript 타입 검사 시스템 및 안전성 검사 우회 [1] - **Contradictions/Notes:** 소스에 관련 정보가 부족합니다. (Non-null Assertion Operator에 대해 제공된 소스의 정보가 매우 제한적이며, 상충되는 의견이나 추가적인 맥락은 포함되어 있지 않습니다.) --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/Non-null Assertion Operator.md]] +- Raw Source: 00_Raw/2026-04-20/Non-null Assertion Operator.md --- diff --git a/01_Archive/2026-04-20/NotebookLM-Automated-Authentication-CLI.md b/01_Archive/2026-04-20/NotebookLM-Automated-Authentication-CLI.md index 3005fc7d..618624f4 100644 --- a/01_Archive/2026-04-20/NotebookLM-Automated-Authentication-CLI.md +++ b/01_Archive/2026-04-20/NotebookLM-Automated-Authentication-CLI.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-BDE5EC -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - NotebookLM-Automated-Authentication-CLI" --- -# [[NotebookLM-Automated-Authentication-CLI]] +# [[NotebookLM-Automated-Authentication-CLI|NotebookLM-Automated-Authentication-CLI]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 기존의 수동 브라우저 쿠키 추출 방식에서 벗어나, `notebooklm-mcp-cli` 패키지를 활용한 CLI 기반의 표준화된 인증 체계입니다. 구글 계정 로그인을 통해 획득한 토큰을 시스템 전역에서 공유함으로써, 사용자의 개입 없이도 안정적인 NotebookLM 서버 접근 권한을 유지합니다. @@ -27,8 +27,8 @@ github_commit: "[P-Reinforce] Continuous Worker - NotebookLM-Automated-Authentic - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Autonomous-Polling-Wait-Automation]], [[Zustand-Based-Mission-Persistence]] -- **Projects/Contexts:** [[P-Reinforce-Agent-v2.6]] +- **Related Topics:** [[Autonomous-Polling-Wait-Automation|Autonomous-Polling-Wait-Automation]], [[Zustand-Based-Mission-Persistence|Zustand-Based-Mission-Persistence]] +- **Projects/Contexts:** P-Reinforce-Agent-v2.6 - **Contradictions/Notes:** CLI 인증은 로컬 환경에 의존하므로, Headless 서버 환경에서는 별도의 토큰 전달 방식이 필요할 수 있습니다. -- Raw Source: [[00_Raw/2026-04-20/NotebookLM-Automated-Authentication-CLI.md]] +- Raw Source: 00_Raw/2026-04-20/NotebookLM-Automated-Authentication-CLI.md --- diff --git a/01_Archive/2026-04-20/Nuclear Deterrence Models.md b/01_Archive/2026-04-20/Nuclear Deterrence Models.md index e8e4ec47..68e84285 100644 --- a/01_Archive/2026-04-20/Nuclear Deterrence Models.md +++ b/01_Archive/2026-04-20/Nuclear Deterrence Models.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-D14EE1 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Nuclear Deterrence Models" --- -# [[Nuclear Deterrence Models]] +# [[Nuclear Deterrence Models|Nuclear Deterrence Models]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Nuclear Deterrence Models" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Nuclear Deterrence Models.md]] +- Raw Source: 00_Raw/2026-04-20/Nuclear Deterrence Models.md --- diff --git a/01_Archive/2026-04-20/Nudge Theory.md b/01_Archive/2026-04-20/Nudge Theory.md index 228dedb4..7505b426 100644 --- a/01_Archive/2026-04-20/Nudge Theory.md +++ b/01_Archive/2026-04-20/Nudge Theory.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-A26B83 -category: "[[10_Wiki/💡 Topics/Software Architecture]]" +category: "10_Wiki/💡 Topics/Software Architecture" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Nudge Theory" --- -# [[Nudge Theory]] +# [[Nudge Theory|Nudge Theory]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Nudge Theory" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Nudge Theory.md]] +- Raw Source: 00_Raw/2026-04-20/Nudge Theory.md --- diff --git a/01_Archive/2026-04-20/Nudge_Theory.md b/01_Archive/2026-04-20/Nudge_Theory.md index 5211b16b..5ee86cae 100644 --- a/01_Archive/2026-04-20/Nudge_Theory.md +++ b/01_Archive/2026-04-20/Nudge_Theory.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-PSYCH-006 -category: "[[10_Wiki/💡 Topics/Psychology]]" +category: "10_Wiki/💡 Topics/Psychology" confidence_score: 0.95 tags: [psychology, nudge, choice-architecture, behavior] last_reinforced: 2026-04-20 github_commit: "batch-reinforce-05" --- -# [[Nudge Theory]] +# [[Nudge Theory|Nudge Theory]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 강요나 금지 없이, 선택의 구조를 미묘하게 설계함으로써 사람들의 행동을 더 나은 방향으로 이끄는 '자유주의적 개입'. @@ -24,6 +24,6 @@ github_commit: "batch-reinforce-05" - **정책 변화:** 사용자 만족도(w3) 피드백에 따라 다크 패턴과 구분되는 '윤리적 넛지' 가이드라인 강화. ## 🔗 지식 연결 (Graph) -- **Parent:** [[10_Wiki/💡 Topics/Psychology]] -- **Related:** [[Behavioral_Economics]], [[Choice-Architecture]], [[Ethical-Design]] -- **Raw Source:** [[00_Raw/2026-04-20/Nudge Theory.md]] +- **Parent:** 10_Wiki/💡 Topics/Psychology +- **Related:** [[Behavioral_Economics|Behavioral_Economics]], Choice-Architecture, Ethical-Design +- **Raw Source:** 00_Raw/2026-04-20/Nudge Theory.md diff --git a/01_Archive/2026-04-20/Nutritional-Biochemistry.md b/01_Archive/2026-04-20/Nutritional-Biochemistry.md index 540161da..f7bae42e 100644 --- a/01_Archive/2026-04-20/Nutritional-Biochemistry.md +++ b/01_Archive/2026-04-20/Nutritional-Biochemistry.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-FFA78C -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Nutritional-Biochemistry" --- -# [[Nutritional-Biochemistry]] +# [[Nutritional-Biochemistry|Nutritional-Biochemistry]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Nutritional-Biochemistry" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Nutritional-Biochemistry.md]] +- Raw Source: 00_Raw/2026-04-20/Nutritional-Biochemistry.md --- diff --git a/01_Archive/2026-04-20/Nx-Build-System.md b/01_Archive/2026-04-20/Nx-Build-System.md index 404e8e51..911bad0d 100644 --- a/01_Archive/2026-04-20/Nx-Build-System.md +++ b/01_Archive/2026-04-20/Nx-Build-System.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-D6169C -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Nx-Build-System" --- -# [[Nx-Build-System]] +# [[Nx-Build-System|Nx-Build-System]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Nx-Build-System" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Nx-Build-System.md]] +- Raw Source: 00_Raw/2026-04-20/Nx-Build-System.md --- diff --git a/01_Archive/2026-04-20/OWA vs CWA (개방 세계 vs 폐쇄 세계 가정).md b/01_Archive/2026-04-20/OWA vs CWA (개방 세계 vs 폐쇄 세계 가정).md index dd87be04..94ee182f 100644 --- a/01_Archive/2026-04-20/OWA vs CWA (개방 세계 vs 폐쇄 세계 가정).md +++ b/01_Archive/2026-04-20/OWA vs CWA (개방 세계 vs 폐쇄 세계 가정).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-BB45FB -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - OWA vs CWA (개방 세계 vs 폐쇄 세계 가정)" --- -# [[OWA vs CWA (개방 세계 vs 폐쇄 세계 가정)]] +# [[OWA vs CWA (개방 세계 vs 폐쇄 세계 가정)|OWA vs CWA (개방 세계 vs 폐쇄 세계 가정)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - OWA vs CWA (개방 세계 vs ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/OWA vs CWA (개방 세계 vs 폐쇄 세계 가정).md]] +- Raw Source: 00_Raw/2026-04-20/OWA vs CWA (개방 세계 vs 폐쇄 세계 가정).md --- diff --git a/01_Archive/2026-04-20/OWASP Top 10.md b/01_Archive/2026-04-20/OWASP Top 10.md index efe5bfff..be512a34 100644 --- a/01_Archive/2026-04-20/OWASP Top 10.md +++ b/01_Archive/2026-04-20/OWASP Top 10.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AI-050 -category: "[[10_Wiki/💡 Topics/Security & Reliability]]" +category: "10_Wiki/💡 Topics/Security & Reliability" confidence_score: 0.99 tags: [security, owasp, vulnerability, secure coding] last_reinforced: 2026-06-XX github_commit: "[P-Reinforce] Processed OWASP Top 10." --- -# [[OWASP Top 10]] (웹 애플리케이션 보안 취약점) +# [[OWASP Top 10|OWASP Top 10]] (웹 애플리케이션 보안 취약점) ## 📌 한 줄 통찰 (The Karpathy Summary) > 웹 애플리케이션 개발 시 가장 빈번하고 치명적인 상위 10가지 보안 위험 목록으로, 개발 초기 단계부터 'Shift-Left' 원칙에 따라 코딩과 테스트 전반에 걸쳐 방어 로직을 적용하는 것이 필수적이다. @@ -25,7 +25,7 @@ github_commit: "[P-Reinforce] Processed OWASP Top 10." - **정책 변화:** SAST/DAST 같은 자동화된 테스트 도구 활용 외에도, 설계 단계에서부터 보안 취약점 분석(Threat Modeling)을 의무화하고, 코드를 검토할 때마다 (Pull Request 기반의) 보안 체크리스트를 도입하는 것이 현대적 표준이다. ## 🔗 지식 연결 (Graph) -- Parent: [[DevSecOps]] -- Related: [[SAST (Static Application Security Testing)]] , [[DAST (동적 애플리케이션 보안 테스트)]] , [[Security by Design]] -- Raw Source: [[00_Raw/OWASP Top 10.md]] +- Parent: [[DevSecOps|DevSecOps]] +- Related: [[SAST (Static Application Security Testing)|SAST (Static Application Security Testing)]] , [[DAST (동적 애플리케이션 보안 테스트)|DAST (동적 애플리케이션 보안 테스트)]] , Security by Design +- Raw Source: 00_Raw/OWASP Top 10.md --- \ No newline at end of file diff --git a/01_Archive/2026-04-20/Object Pooling (가비지 컬렉션 최적화).md b/01_Archive/2026-04-20/Object Pooling (가비지 컬렉션 최적화).md index 0e10309f..8be566cd 100644 --- a/01_Archive/2026-04-20/Object Pooling (가비지 컬렉션 최적화).md +++ b/01_Archive/2026-04-20/Object Pooling (가비지 컬렉션 최적화).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-345FBB -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Object Pooling (가비지 컬렉션 최적화)" --- -# [[Object Pooling (가비지 컬렉션 최적화)]] +# [[Object Pooling (가비지 컬렉션 최적화)|Object Pooling (가비지 컬렉션 최적화)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Object Pooling (가비지 컬 ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Object Pooling (가비지 컬렉션 최적화).md]] +- Raw Source: 00_Raw/2026-04-20/Object Pooling (가비지 컬렉션 최적화).md --- diff --git a/01_Archive/2026-04-20/Object Pooling (오브젝트 풀링).md b/01_Archive/2026-04-20/Object Pooling (오브젝트 풀링).md index c94117a1..747341ce 100644 --- a/01_Archive/2026-04-20/Object Pooling (오브젝트 풀링).md +++ b/01_Archive/2026-04-20/Object Pooling (오브젝트 풀링).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-1F94B3 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Object Pooling (오브젝트 풀링)" --- -# [[Object Pooling (오브젝트 풀링)]] +# [[Object Pooling (오브젝트 풀링)|Object Pooling (오브젝트 풀링)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 오브젝트 풀링은 객체의 빈번한 생성과 파괴로 인해 발생하는 메모리 할당 비용과 가비지 컬렉션(GC) 스파이크를 방지하기 위해, 미리 고정된 개수의 객체 풀(Pool)을 할당해 두고 필요할 때 꺼내어 재사용한 뒤 다시 반환하는 소프트웨어 성능 최적화 디자인 패턴입니다. @@ -35,12 +35,12 @@ github_commit: "[P-Reinforce] Continuous Worker - Object Pooling (오브젝트 - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Garbage Collection (GC) 최적화]], [[Generational GC (세대별 가비지 컬렉션)]], [[Memory Fragmentation (메모리 파편화)]], [[InstancedMesh (드로우 콜 최적화)]] -- **Projects/Contexts:** [[대규모 파티클 시스템 최적화]], [[슈팅 게임의 대규모 탄환(Bullet) 제어 시스템]], [[React Three Fiber 엔진 아키텍처]] +- **Related Topics:** [[Garbage Collection (GC) 최적화|Garbage Collection (GC) 최적화]], Generational GC (세대별 가비지 컬렉션), Memory Fragmentation (메모리 파편화), [[InstancedMesh (드로우 콜 최적화)|InstancedMesh (드로우 콜 최적화)]] +- **Projects/Contexts:** [[대규모 파티클 시스템 최적화|대규모 파티클 시스템 최적화]], 슈팅 게임의 대규모 탄환(Bullet) 제어 시스템, React Three Fiber 엔진 아키텍처 - **Contradictions/Notes:** 오브젝트 풀링이 모든 상황에서 정답은 아닙니다. V8과 같은 최신 자바스크립트 엔진의 세대별 가비지 컬렉터(Generational GC)는 단기 생존 객체(Short-lived objects)를 수거하는 비용이 사실상 0에 가깝습니다. 이 환경에서 객체 풀링을 잘못 적용하면, 객체들이 강제로 오래 살아남게 되어 구세대(Old Generation) 메모리를 압박하고 오히려 GC 성능을 악화시키며 메모리 사용량만 늘릴 위험이 있습니다. 반드시 프로파일러를 통한 성능 병목 확인 후 선별적으로 도입해야 합니다. --- _Last updated: 2026-04-15_ -- Raw Source: [[00_Raw/2026-04-20/Object Pooling (오브젝트 풀링).md]] +- Raw Source: 00_Raw/2026-04-20/Object Pooling (오브젝트 풀링).md --- diff --git a/01_Archive/2026-04-20/Object Pooling.md b/01_Archive/2026-04-20/Object Pooling.md index 8a8a1653..e1747c85 100644 --- a/01_Archive/2026-04-20/Object Pooling.md +++ b/01_Archive/2026-04-20/Object Pooling.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-18523F -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Object Pooling" --- -# [[Object Pooling]] +# [[Object Pooling|Object Pooling]] ## 📌 한 줄 통찰 (The Karpathy Summary) > Object Pooling(오브젝트 풀링)은 총알, 파티클, 적 캐릭터와 같이 런타임 중 빈번하게 생성되고 파괴되는 개체들의 성능을 최적화하기 위해 사용되는 메모리 관리 기법입니다 [1]. 매번 새로운 객체를 메모리에 할당하는 대신, 사전에 생성해 둔 객체들의 풀(Pool)을 구축하여 이를 재사용하는 방식으로 동작합니다 [1]. 이를 통해 애플리케이션 실행 중 발생하는 메모리 할당 오버헤드와 가비지 컬렉션(Garbage Collection, GC)으로 인한 프레임 멈춤 현상을 효과적으로 방지할 수 있습니다 [1, 2]. 대규모 3D 씬과 동적인 렌더링 환경에서는 안정적인 메모리 제어와 누수 방지를 위해 객체 풀링 전략을 사전에 수립하는 것이 필수적입니다 [3, 4]. @@ -24,11 +24,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Object Pooling" - **정책 변화:** Graphics & Performance 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Memory Management]], [[Garbage Collection]], [[Memory Leaks]] -- **Projects/Contexts:** [[Three.js]], [[Babylon.js]] +- **Related Topics:** [[Memory Management|Memory Management]], [[Garbage Collection|Garbage Collection]], [[Memory Leaks|Memory Leaks]] +- **Projects/Contexts:** [[Three.js|Three.js]], [[Babylon.js|Babylon.js]] - **Contradictions/Notes:** 소스에 관련 정보가 부족합니다. (주어진 소스 내에서 오브젝트 풀링의 효과나 방식에 대해 상충하는 의견은 존재하지 않으며, 모두 성능 최적화를 위해 적극적으로 권장하고 있습니다.) --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Object Pooling.md]] +- Raw Source: 00_Raw/2026-04-20/Object Pooling.md --- diff --git a/01_Archive/2026-04-20/Object-Literal-Assignment.md b/01_Archive/2026-04-20/Object-Literal-Assignment.md index a7546121..7a740b75 100644 --- a/01_Archive/2026-04-20/Object-Literal-Assignment.md +++ b/01_Archive/2026-04-20/Object-Literal-Assignment.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-8E1BDB -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Object-Literal-Assignment" --- -# [[Object-Literal-Assignment]] +# [[Object-Literal-Assignment|Object-Literal-Assignment]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Object-Literal-Assignment" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Object-Literal-Assignment.md]] +- Raw Source: 00_Raw/2026-04-20/Object-Literal-Assignment.md --- diff --git a/01_Archive/2026-04-20/Object-Oriented-Design-Patterns.md b/01_Archive/2026-04-20/Object-Oriented-Design-Patterns.md index efa2a158..34a18825 100644 --- a/01_Archive/2026-04-20/Object-Oriented-Design-Patterns.md +++ b/01_Archive/2026-04-20/Object-Oriented-Design-Patterns.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-A48A29 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Object-Oriented-Design-Patterns" --- -# [[Object-Oriented-Design-Patterns]] +# [[Object-Oriented-Design-Patterns|Object-Oriented-Design-Patterns]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Object-Oriented-Design-Pattern ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Object-Oriented-Design-Patterns.md]] +- Raw Source: 00_Raw/2026-04-20/Object-Oriented-Design-Patterns.md --- diff --git a/01_Archive/2026-04-20/Object-Oriented-Interface-Design.md b/01_Archive/2026-04-20/Object-Oriented-Interface-Design.md index 5e7a9b3d..9deed4ab 100644 --- a/01_Archive/2026-04-20/Object-Oriented-Interface-Design.md +++ b/01_Archive/2026-04-20/Object-Oriented-Interface-Design.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-8CEF52 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Object-Oriented-Interface-Design" --- -# [[Object-Oriented-Interface-Design]] +# [[Object-Oriented-Interface-Design|Object-Oriented-Interface-Design]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Object-Oriented-Interface-Desi ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Object-Oriented-Interface-Design.md]] +- Raw Source: 00_Raw/2026-04-20/Object-Oriented-Interface-Design.md --- diff --git a/01_Archive/2026-04-20/Objective Distillation (목표 증류).md b/01_Archive/2026-04-20/Objective Distillation (목표 증류).md index 29094978..349b3225 100644 --- a/01_Archive/2026-04-20/Objective Distillation (목표 증류).md +++ b/01_Archive/2026-04-20/Objective Distillation (목표 증류).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-C021D6 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Objective Distillation (목표 증류)" --- -# [[Objective Distillation (목표 증류)]] +# [[Objective Distillation (목표 증류)|Objective Distillation (목표 증류)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Objective Distillation (목표 ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Objective Distillation (목표 증류).md]] +- Raw Source: 00_Raw/2026-04-20/Objective Distillation (목표 증류).md --- diff --git a/01_Archive/2026-04-20/Objectivism.md b/01_Archive/2026-04-20/Objectivism.md index c56cc9dd..c08dbdac 100644 --- a/01_Archive/2026-04-20/Objectivism.md +++ b/01_Archive/2026-04-20/Objectivism.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-AAD455 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Objectivism" --- -# [[Objectivism]] +# [[Objectivism|Objectivism]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Objectivism" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Objectivism.md]] +- Raw Source: 00_Raw/2026-04-20/Objectivism.md --- diff --git a/01_Archive/2026-04-20/Occlusion Culling.md b/01_Archive/2026-04-20/Occlusion Culling.md index 6e096708..7d0d0ecb 100644 --- a/01_Archive/2026-04-20/Occlusion Culling.md +++ b/01_Archive/2026-04-20/Occlusion Culling.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-3A1034 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Occlusion Culling" --- -# [[Occlusion Culling]] +# [[Occlusion Culling|Occlusion Culling]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 오클루전 컬링(Occlusion Culling)은 시야(Frustum) 내에 있더라도 다른 물체에 의해 완전히 가려져 보이지 않는 객체들을 식별하고 렌더링 파이프라인에서 제외하는 그래픽스 최적화 기법입니다 [1, 2]. CPU 기반으로 복잡한 기하학적 구조를 계산하기에는 난이도가 높고, GPU에서 수행하더라도 지연(Latency) 문제로 비용이 발생할 수 있어, 최신 렌더링 환경에서는 컴퓨트 셰이더나 깊이 사전 패스(Depth Pre-Pass) 등의 우회 및 발전된 기법과 함께 사용됩니다 [2, 3]. @@ -20,11 +20,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Occlusion Culling" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Frustum Culling]], [[Compute Shader]], [[Depth Pre-Pass]], [[InstancedMesh]], [[Early-Z]], [[Draw Call]] -- **Projects/Contexts:** [[WebGPU]], [[Three.js]], [[WebGL/Three.js CAD Rendering Optimization]] +- **Related Topics:** [[Frustum Culling|Frustum Culling]], [[Compute Shader|Compute Shader]], [[Depth Pre-Pass|Depth Pre-Pass]], [[InstancedMesh|InstancedMesh]], [[Early-Z|Early-Z]], [[Draw Call|Draw Call]] +- **Projects/Contexts:** [[WebGPU|WebGPU]], [[Three.js|Three.js]], WebGL/Three.js CAD Rendering Optimization - **Contradictions/Notes:** 소스에 따르면 오클루전 컬링은 그래픽스 성능 최적화의 핵심적인 개념이지만, 복잡성으로 인해 고유의 연산 비용이 따릅니다. 따라서 상황에 따라 오클루전 컬링을 직접 구현하기보다는 Depth Pre-Pass로 우회하거나, WebGPU의 컴퓨트 셰이더를 통해 CPU를 거치지 않고 가시성을 판별하는 방식으로 기술이 발전하고 있음이 관찰됩니다 [1, 2, 4]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Occlusion Culling.md]] +- Raw Source: 00_Raw/2026-04-20/Occlusion Culling.md --- diff --git a/01_Archive/2026-04-20/Occupational-Ergonomics.md b/01_Archive/2026-04-20/Occupational-Ergonomics.md index 79c651a8..41719f3e 100644 --- a/01_Archive/2026-04-20/Occupational-Ergonomics.md +++ b/01_Archive/2026-04-20/Occupational-Ergonomics.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-92FABA -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Occupational-Ergonomics" --- -# [[Occupational-Ergonomics]] +# [[Occupational-Ergonomics|Occupational-Ergonomics]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Occupational-Ergonomics" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Occupational-Ergonomics.md]] +- Raw Source: 00_Raw/2026-04-20/Occupational-Ergonomics.md --- diff --git a/01_Archive/2026-04-20/Occupational-Therapy.md b/01_Archive/2026-04-20/Occupational-Therapy.md index 7804468a..e0157f4b 100644 --- a/01_Archive/2026-04-20/Occupational-Therapy.md +++ b/01_Archive/2026-04-20/Occupational-Therapy.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-5178EE -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Occupational-Therapy" --- -# [[Occupational-Therapy]] +# [[Occupational-Therapy|Occupational-Therapy]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Occupational-Therapy" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Occupational-Therapy.md]] +- Raw Source: 00_Raw/2026-04-20/Occupational-Therapy.md --- diff --git a/01_Archive/2026-04-20/OffscreenCanvas (멀티스레딩).md b/01_Archive/2026-04-20/OffscreenCanvas (멀티스레딩).md index 6425c663..7949ed0c 100644 --- a/01_Archive/2026-04-20/OffscreenCanvas (멀티스레딩).md +++ b/01_Archive/2026-04-20/OffscreenCanvas (멀티스레딩).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-811DEC -category: "[[10_Wiki/💡 Topics/General Knowledge]]" +category: "10_Wiki/💡 Topics/General Knowledge" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - OffscreenCanvas (멀티스레딩)" --- -# [[OffscreenCanvas (멀티스레딩)]] +# [[OffscreenCanvas (멀티스레딩)|OffscreenCanvas (멀티스레딩)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - OffscreenCanvas (멀티스레 ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/OffscreenCanvas (멀티스레딩).md]] +- Raw Source: 00_Raw/2026-04-20/OffscreenCanvas (멀티스레딩).md --- diff --git a/01_Archive/2026-04-20/OffscreenCanvas Safari 제약 사항.md b/01_Archive/2026-04-20/OffscreenCanvas Safari 제약 사항.md index 706d9a9c..2e214c03 100644 --- a/01_Archive/2026-04-20/OffscreenCanvas Safari 제약 사항.md +++ b/01_Archive/2026-04-20/OffscreenCanvas Safari 제약 사항.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-600505 -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - OffscreenCanvas Safari 제약 사항" --- -# [[OffscreenCanvas Safari 제약 사항]] +# [[OffscreenCanvas Safari 제약 사항|OffscreenCanvas Safari 제약 사항]] ## 📌 한 줄 통찰 (The Karpathy Summary) > Safari 브라우저에서는 `OffscreenCanvas`와 WebGL의 결합 사용이 아직 완전히 지원되지 않아, 워커 스레드와 메인 스레드용 렌더링 코드를 별도로 유지보수하거나 폴백(Fallback)을 구현해야 하는 치명적인 제약이 있습니다. @@ -24,12 +24,12 @@ github_commit: "[P-Reinforce] Continuous Worker - OffscreenCanvas Safari 제약 - **정책 변화:** Graphics & Performance 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[OffscreenCanvas]], [[Web Worker (웹 워커)]], [[React Three Fiber (R3F)]], [[Cross-browser Compatibility (크로스 브라우저 호환성)]] -- **Projects/Contexts:** [[고성능 멀티스레드 React 앱 아키텍처]], [[실시간 3D 웹 게임 렌더링 환경]] +- **Related Topics:** [[OffscreenCanvas|OffscreenCanvas]], [[Web Worker (웹 워커)|Web Worker (웹 워커)]], [[React Three Fiber (R3F)|React Three Fiber (R3F)]], Cross-browser Compatibility (크로스 브라우저 호환성) +- **Projects/Contexts:** [[고성능 멀티스레드 React 앱 아키텍처|고성능 멀티스레드 React 앱 아키텍처]], 실시간 3D 웹 게임 렌더링 환경 - **Contradictions/Notes:** Safari 브라우저가 2025년 9월(v26)부터 WebGPU 지원을 시작하는 등 그래픽 지원 범위를 넓혀가고 있으나, `OffscreenCanvas`를 활용한 WebGL 멀티스레드 렌더링에 대해서는 여전히 제약이 보고되고 있으므로 프로덕션 환경에서는 반드시 메인 스레드용 `fallback` 컴포넌트를 제공해야 안정성을 보장할 수 있습니다. --- _Last updated: 2026-04-15_ -- Raw Source: [[00_Raw/2026-04-20/OffscreenCanvas Safari 제약 사항.md]] +- Raw Source: 00_Raw/2026-04-20/OffscreenCanvas Safari 제약 사항.md --- diff --git a/01_Archive/2026-04-20/OffscreenCanvas 기반 멀티스레드 렌더링 구현.md b/01_Archive/2026-04-20/OffscreenCanvas 기반 멀티스레드 렌더링 구현.md index 7e839d80..6ec38656 100644 --- a/01_Archive/2026-04-20/OffscreenCanvas 기반 멀티스레드 렌더링 구현.md +++ b/01_Archive/2026-04-20/OffscreenCanvas 기반 멀티스레드 렌더링 구현.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-58B572 -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - OffscreenCanvas 기반 멀티스레드 렌더링 구현" --- -# [[OffscreenCanvas 기반 멀티스레드 렌더링 구현]] +# [[OffscreenCanvas 기반 멀티스레드 렌더링 구현|OffscreenCanvas 기반 멀티스레드 렌더링 구현]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - OffscreenCanvas 기반 멀티 ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/OffscreenCanvas 기반 멀티스레드 렌더링 구현.md]] +- Raw Source: 00_Raw/2026-04-20/OffscreenCanvas 기반 멀티스레드 렌더링 구현.md --- diff --git a/01_Archive/2026-04-20/OffscreenCanvas.md b/01_Archive/2026-04-20/OffscreenCanvas.md index e0247c6e..763d104f 100644 --- a/01_Archive/2026-04-20/OffscreenCanvas.md +++ b/01_Archive/2026-04-20/OffscreenCanvas.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-715F80 -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - OffscreenCanvas" --- -# [[OffscreenCanvas]] +# [[OffscreenCanvas|OffscreenCanvas]] ## 📌 한 줄 통찰 (The Karpathy Summary) > **OffscreenCanvas**는 DOM과 분리된 백그라운드 스레드(웹 워커)에서 그래픽 렌더링을 수행할 수 있게 해주는 웹 API로, 무거운 3D 렌더링이나 캔버스 연산 중에도 메인 스레드의 UI 반응성을 쾌적하게 유지할 수 있도록 돕는 핵심 최적화 기술입니다. @@ -28,12 +28,12 @@ github_commit: "[P-Reinforce] Continuous Worker - OffscreenCanvas" - **정책 변화:** Graphics & Performance 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Web Worker (웹 워커)]], [[Multi-threaded Architecture (멀티스레드 아키텍처)]], [[React Three Fiber (R3F)]], [[Valtio (Proxy State 관리)]], [[SharedArrayBuffer]] -- **Projects/Contexts:** [[고성능 멀티스레드 React 앱 아키텍처]], [[무거운 렌더링 연산을 동반하는 WebGL 데이터 시각화]] +- **Related Topics:** [[Web Worker (웹 워커)|Web Worker (웹 워커)]], Multi-threaded Architecture (멀티스레드 아키텍처), [[React Three Fiber (R3F)|React Three Fiber (R3F)]], Valtio (Proxy State 관리), [[SharedArrayBuffer|SharedArrayBuffer]] +- **Projects/Contexts:** [[고성능 멀티스레드 React 앱 아키텍처|고성능 멀티스레드 React 앱 아키텍처]], 무거운 렌더링 연산을 동반하는 WebGL 데이터 시각화 - **Contradictions/Notes:** OffscreenCanvas 기능은 과거 Safari 브라우저에서 오랫동안 완벽히 지원되지 않아 프로젝트를 메인 스레드용과 워커용 두 갈래(Fork)로 유지보수해야 하는 치명적인 단점이 있었습니다. 2025년 9월(Safari v26)부터 지원이 확대되었으나, 완벽한 크로스 브라우저 호환성을 위해서는 API 지원 여부를 감지하여 워커를 지원하지 않는 환경에서는 메인 스레드에서 렌더링이 이루어지도록 `fallback` 컴포넌트를 반드시 제공해야 합니다. --- _Last updated: 2026-04-15_ -- Raw Source: [[00_Raw/2026-04-20/OffscreenCanvas.md]] +- Raw Source: 00_Raw/2026-04-20/OffscreenCanvas.md --- diff --git a/01_Archive/2026-04-20/OffscreenCanvas와 Web Worker를 활용한 메인 스레드 병목 해결.md b/01_Archive/2026-04-20/OffscreenCanvas와 Web Worker를 활용한 메인 스레드 병목 해결.md index 1c2972c5..1a8cf4ec 100644 --- a/01_Archive/2026-04-20/OffscreenCanvas와 Web Worker를 활용한 메인 스레드 병목 해결.md +++ b/01_Archive/2026-04-20/OffscreenCanvas와 Web Worker를 활용한 메인 스레드 병목 해결.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-217E9B -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - OffscreenCanvas와 Web Worker를 활용한 메인 스레드 병목 해결" --- -# [[OffscreenCanvas와 Web Worker를 활용한 메인 스레드 병목 해결]] +# [[OffscreenCanvas와 Web Worker를 활용한 메인 스레드 병목 해결|OffscreenCanvas와 Web Worker를 활용한 메인 스레드 병목 해결]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 자바스크립트의 단일 스레드 한계를 극복하기 위해, 무거운 그래픽 렌더링이나 연산 작업을 메인 스레드(DOM)에서 분리하여 백그라운드의 웹 워커(Web Worker) 스레드에서 병렬 처리하는 성능 최적화 기술입니다. @@ -31,12 +31,12 @@ github_commit: "[P-Reinforce] Continuous Worker - OffscreenCanvas와 Web Worker - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Web Worker]], [[Three.js / WebGL]], [[상태 관리 동기화 (Valtio, SharedArrayBuffer)]], [[이벤트 포워딩(Event Forwarding)]], [[React 게임 엔진 아키텍처]] -- **Projects/Contexts:** [[멀티스레드 React WebGL 애플리케이션]], [[고성능 실시간 상호작용 시스템]] +- **Related Topics:** [[Web Worker (웹 워커)|Web Worker]], [[Threejs WebGL 렌더링 최적화|Three.js / WebGL]], 상태 관리 동기화 (Valtio, SharedArrayBuffer), [[이벤트 포워딩(Event Forwarding)|이벤트 포워딩(Event Forwarding)]], [[React 게임 엔진 아키텍처|React 게임 엔진 아키텍처]] +- **Projects/Contexts:** 멀티스레드 React WebGL 애플리케이션, 고성능 실시간 상호작용 시스템 - **Contradictions/Notes:** 상태 동기화를 구현할 때 `SharedArrayBuffer`는 가장 빠르고 메모리 복사 비용이 없지만 원시 이진 데이터(Raw Binary)를 다루어야 해서 구현이 어렵습니다. 반면, Valtio 등 Proxy를 사용한 메시징 방식은 개발이 훨씬 쉽고 직관적이지만 직렬화 과정에서 약간의 오버헤드와 메모리를 희생하게 됩니다. --- _Last updated: 2026-04-14_ -- Raw Source: [[00_Raw/2026-04-20/OffscreenCanvas와 Web Worker를 활용한 메인 스레드 병목 해결.md]] +- Raw Source: 00_Raw/2026-04-20/OffscreenCanvas와 Web Worker를 활용한 메인 스레드 병목 해결.md --- diff --git a/01_Archive/2026-04-20/Oilpan.md b/01_Archive/2026-04-20/Oilpan.md index 16cf8eba..ee2e1194 100644 --- a/01_Archive/2026-04-20/Oilpan.md +++ b/01_Archive/2026-04-20/Oilpan.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-68FCF1 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Oilpan" --- -# [[Oilpan]] +# [[Oilpan|Oilpan]] ## 📌 한 줄 통찰 (The Karpathy Summary) > Oilpan은 Chrome의 렌더링 엔진인 Blink에서 사용하는 가비지 컬렉터(Garbage Collector)입니다 [1]. V8 엔진의 주요 가비지 컬렉터인 Orinoco와 Oilpan 간의 협력을 개선하고, Orinoco의 새로운 기술을 Oilpan에 이식하려는 작업이 진행 중입니다 [1]. @@ -23,11 +23,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Oilpan" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Garbage Collection]], [[Blink]], [[Orinoco]] -- **Projects/Contexts:** [[Chrome]] +- **Related Topics:** [[Garbage Collection|Garbage Collection]], [[Blink|Blink]], [[Orinoco|Orinoco]] +- **Projects/Contexts:** [[Chrome|Chrome]] - **Contradictions/Notes:** 소스에 관련 정보가 부족합니다. (Oilpan과 관련된 내용은 소스 [1]에서 단 한 차례 간략하게만 언급되며, 구체적인 기술적 논의나 모순점은 제시되어 있지 않습니다.) --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Oilpan.md]] +- Raw Source: 00_Raw/2026-04-20/Oilpan.md --- diff --git a/01_Archive/2026-04-20/Okami-Ink-Wash-Aesthetics.md b/01_Archive/2026-04-20/Okami-Ink-Wash-Aesthetics.md index b8d99039..4188821a 100644 --- a/01_Archive/2026-04-20/Okami-Ink-Wash-Aesthetics.md +++ b/01_Archive/2026-04-20/Okami-Ink-Wash-Aesthetics.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-442A85 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Okami-Ink-Wash-Aesthetics" --- -# [[Okami-Ink-Wash-Aesthetics]] +# [[Okami-Ink-Wash-Aesthetics|Okami-Ink-Wash-Aesthetics]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Okami-Ink-Wash-Aesthetics" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Okami-Ink-Wash-Aesthetics.md]] +- Raw Source: 00_Raw/2026-04-20/Okami-Ink-Wash-Aesthetics.md --- diff --git a/01_Archive/2026-04-20/Old Space (구 세대 공간).md b/01_Archive/2026-04-20/Old Space (구 세대 공간).md index c7530fa0..baad3b5f 100644 --- a/01_Archive/2026-04-20/Old Space (구 세대 공간).md +++ b/01_Archive/2026-04-20/Old Space (구 세대 공간).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-9214B8 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Old Space (구 세대 공간)" --- -# [[Old Space (구 세대 공간)]] +# [[Old Space (구 세대 공간)|Old Space (구 세대 공간)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > Old Space(구 세대 공간)는 V8 자바스크립트 엔진의 힙(Heap) 메모리 영역 중, New Space(신규 공간)에서 발생하는 가비지 컬렉션(GC)을 두 번 이상 생존한 객체들이 승격(Promotion)되어 이동하는 공간입니다 [1-3]. 주로 사용자 세션이나 캐시 데이터 등 수명이 길고 지속적인 상태를 유지하는 객체들을 장기간 저장하는 데 사용됩니다 [4, 5]. 이 공간의 메모리 회수는 빈도가 낮지만 리소스 소모가 큰 Major GC(Mark-Sweep 및 Mark-Compact 알고리즘)에 의해 관리됩니다 [1, 3, 5]. @@ -30,11 +30,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Old Space (구 세대 공간)" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[New Space (신규 공간)]], [[Major GC (주요 가비지 컬렉션)]], [[Mark-Sweep-Compact]], [[Memory Leak (메모리 누수)]] -- **Projects/Contexts:** [[V8 JavaScript Engine]], [[Node.js Memory Management]] +- **Related Topics:** New Space (신규 공간), Major GC (주요 가비지 컬렉션), [[Mark-Sweep-Compact|Mark-Sweep-Compact]], [[Memory Leak(메모리 누수)|Memory Leak (메모리 누수)]] +- **Projects/Contexts:** [[V8 JavaScript Engine|V8 JavaScript Engine]], [[Node.js Memory Management|Node.js Memory Management]] - **Contradictions/Notes:** 소스에 따르면 Old Space 내의 객체를 옮기는 압축(Compaction) 작업은 비용이 매우 많이 들기 때문에, Minor GC처럼 모든 라이브 객체를 복사하는 방식(Scavenger)을 쓰지 않고 단편화가 심한 특정 페이지에 대해서만 제한적으로 압축을 수행합니다 [12, 13]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Old Space (구 세대 공간).md]] +- Raw Source: 00_Raw/2026-04-20/Old Space (구 세대 공간).md --- diff --git a/01_Archive/2026-04-20/Old Space(Old Generation).md b/01_Archive/2026-04-20/Old Space(Old Generation).md index a98c200e..aeec036a 100644 --- a/01_Archive/2026-04-20/Old Space(Old Generation).md +++ b/01_Archive/2026-04-20/Old Space(Old Generation).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-3FD05B -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Old Space(Old Generation)" --- -# [[Old Space(Old Generation)]] +# [[Old Space(Old Generation)|Old Space(Old Generation)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > Old Space(또는 Old Generation)는 V8 엔진의 힙(Heap) 메모리 영역 중 하나로, New Space(Young Generation)에서 두 번의 마이너 가비지 컬렉션(Scavenge) 주기 동안 살아남은 수명이 긴 객체들이 이동(승격)하여 저장되는 공간이다 [1-3]. 이 공간은 주로 사용자 세션, 캐시 데이터 등 영구적인 상태를 유지하는 데이터 저장에 사용되며, New Space에 비해 크기가 훨씬 크고 가비지 컬렉션(Major GC)이 덜 빈번하게 발생하지만 더 많은 컴퓨팅 리소스를 소모한다 [4, 5]. @@ -29,11 +29,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Old Space(Old Generation)" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[New Space(Young Generation)]], [[Major GC]], [[Mark-Sweep-Compact]], [[Garbage Collection]] -- **Projects/Contexts:** [[V8 Engine Memory Management]], [[Node.js Performance Tuning]] +- **Related Topics:** [[New Space(Young Generation)|New Space(Young Generation)]], [[Major GC|Major GC]], [[Mark-Sweep-Compact|Mark-Sweep-Compact]], [[Garbage Collection|Garbage Collection]] +- **Projects/Contexts:** V8 Engine Memory Management, Node.js Performance Tuning - **Contradictions/Notes:** 소스에 관련 정보가 부족합니다. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Old Space(Old Generation).md]] +- Raw Source: 00_Raw/2026-04-20/Old Space(Old Generation).md --- diff --git a/01_Archive/2026-04-20/Old Space.md b/01_Archive/2026-04-20/Old Space.md index 995b531c..956298c6 100644 --- a/01_Archive/2026-04-20/Old Space.md +++ b/01_Archive/2026-04-20/Old Space.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-C312D4 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Old Space" --- -# [[Old Space]] +# [[Old Space|Old Space]] ## 📌 한 줄 통찰 (The Karpathy Summary) > Old Space(또는 Old generation)는 V8 엔진의 메모리 힙 구조에서 단기 생존 영역인 New Space에서 여러 차례의 가비지 컬렉션(GC)을 견뎌낸 장기 생존 객체들이 저장되는 공간입니다 [1-3]. 주로 사용자 세션, 캐시 데이터, 영구 상태와 같은 장기 보존 데이터가 이곳에 보관됩니다 [4]. 이 공간은 수백 메가바이트 이상의 데이터를 담을 수 있도록 훨씬 크게 설계되었으며, Mark-Sweep 및 Mark-Compact 알고리즘을 사용하는 Major GC에 의해 덜 빈번하지만 더 많은 리소스를 소모하여 관리됩니다 [4-7]. @@ -26,11 +26,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Old Space" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[New Space]], [[Major GC]], [[Mark-Sweep-Compact]], [[Write Barrier]], [[Garbage Collection]] -- **Projects/Contexts:** [[V8 Engine]], [[Node.js Memory Management]] +- **Related Topics:** [[New Space|New Space]], [[Major GC|Major GC]], [[Mark-Sweep-Compact|Mark-Sweep-Compact]], [[Write Barrier|Write Barrier]], [[Garbage Collection|Garbage Collection]] +- **Projects/Contexts:** [[V8 Engine|V8 Engine]], [[Node.js Memory Management|Node.js Memory Management]] - **Contradictions/Notes:** 소스에 따르면 V8은 필요할 경우 운영체제에 더 많은 공간을 요청하여 Old Space 크기를 확장할 수 있으나, V8 Memory Cage(보안 샌드박스 및 포인터 압축) 기능이 활성화된 64비트 시스템에서는 물리적 RAM 용량에 관계없이 V8 힙 전체 크기가 최대 4GB의 연속적인 영역으로 엄격히 제한됩니다 [16-18]. 따라서 Old Space 역시 이 4GB 제한의 영향을 받습니다. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Old Space.md]] +- Raw Source: 00_Raw/2026-04-20/Old Space.md --- diff --git a/01_Archive/2026-04-20/Olympic-Training-Cycles.md b/01_Archive/2026-04-20/Olympic-Training-Cycles.md index 62fa65ee..f89408a2 100644 --- a/01_Archive/2026-04-20/Olympic-Training-Cycles.md +++ b/01_Archive/2026-04-20/Olympic-Training-Cycles.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-0425FA -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Olympic-Training-Cycles" --- -# [[Olympic-Training-Cycles]] +# [[Olympic-Training-Cycles|Olympic-Training-Cycles]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Olympic-Training-Cycles" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Olympic-Training-Cycles.md]] +- Raw Source: 00_Raw/2026-04-20/Olympic-Training-Cycles.md --- diff --git a/01_Archive/2026-04-20/Olympic-Training-Models.md b/01_Archive/2026-04-20/Olympic-Training-Models.md index 104ad800..b53e69bd 100644 --- a/01_Archive/2026-04-20/Olympic-Training-Models.md +++ b/01_Archive/2026-04-20/Olympic-Training-Models.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-89D68B -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Olympic-Training-Models" --- -# [[Olympic-Training-Models]] +# [[Olympic-Training-Models|Olympic-Training-Models]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Olympic-Training-Models" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Olympic-Training-Models.md]] +- Raw Source: 00_Raw/2026-04-20/Olympic-Training-Models.md --- diff --git a/01_Archive/2026-04-20/Olympic-Training-Protocols.md b/01_Archive/2026-04-20/Olympic-Training-Protocols.md index 32faa7a0..b591a806 100644 --- a/01_Archive/2026-04-20/Olympic-Training-Protocols.md +++ b/01_Archive/2026-04-20/Olympic-Training-Protocols.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-553F3F -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Olympic-Training-Protocols" --- -# [[Olympic-Training-Protocols]] +# [[Olympic-Training-Protocols|Olympic-Training-Protocols]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Olympic-Training-Protocols" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Olympic-Training-Protocols.md]] +- Raw Source: 00_Raw/2026-04-20/Olympic-Training-Protocols.md --- diff --git a/01_Archive/2026-04-20/Ontology-Driven-Relevancy-Filtering.md b/01_Archive/2026-04-20/Ontology-Driven-Relevancy-Filtering.md index 8dda4c3d..25a63136 100644 --- a/01_Archive/2026-04-20/Ontology-Driven-Relevancy-Filtering.md +++ b/01_Archive/2026-04-20/Ontology-Driven-Relevancy-Filtering.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-9231E5 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Ontology-Driven-Relevancy-Filtering" --- -# [[Ontology-Driven-Relevancy-Filtering]] +# [[Ontology-Driven-Relevancy-Filtering|Ontology-Driven-Relevancy-Filtering]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 탐사 과정에서 발생할 수 있는 '주제 이탈(Topic Drift)'을 방지하기 위해 도입된 의미론적 제약 엔진입니다. 최초 입력된 'Root Topic'을 모든 하위 연구 단계에 주입하여, 추출된 연관 주제가 뿌리 지식과 얼마나 밀접한지를 LLM이 스스로 판단하게 합니다. @@ -17,7 +17,7 @@ github_commit: "[P-Reinforce] Continuous Worker - Ontology-Driven-Relevancy-Filt 1. **Root Topic Injection**: 미션 시작 시 입력된 주제를 전역 상태(`rootTopic`)로 고정하고, 모든 프롬프트에 "최초 주제인 [Root Topic]을 이해하는 데 반드시 필요한 정보만 수집하라"는 강력한 지침을 포함시킵니다. 2. **Strict Extraction Rule**: - - `[[Link]]` 추출 시, 해당 주제가 Root Topic과 70% 이상의 의미론적 연관성을 가질 때만 큐(Queue)에 추가하도록 LLM 가이드라인을 설정했습니다. + - `Link` 추출 시, 해당 주제가 Root Topic과 70% 이상의 의미론적 연관성을 가질 때만 큐(Queue)에 추가하도록 LLM 가이드라인을 설정했습니다. - 단순 나열(Tangential topics)은 수집 대상에서 제외합니다. 3. **Contextual Continuity**: 다음 태스크를 생성할 때 이전 태스크의 맥락을 `context` 변수로 전달하여, 지식의 연결성이 끊기지 않도록 관리합니다. @@ -28,8 +28,8 @@ github_commit: "[P-Reinforce] Continuous Worker - Ontology-Driven-Relevancy-Filt - **정책 변화:** AI 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Autonomous-Loop-State-Machine]], [[Gemini-Based-Knowledge-Synthesis]] -- **Projects/Contexts:** [[Knowledge-Graph-Expansion]] +- **Related Topics:** Autonomous-Loop-State-Machine, Gemini-Based-Knowledge-Synthesis +- **Projects/Contexts:** Knowledge-Graph-Expansion - **Contradictions/Notes:** 필터링이 너무 강력하면 지식의 '참신한 연결'이 저해될 수 있으므로, 프롬프트의 강도 조절이 중요합니다. -- Raw Source: [[00_Raw/2026-04-20/Ontology-Driven-Relevancy-Filtering.md]] +- Raw Source: 00_Raw/2026-04-20/Ontology-Driven-Relevancy-Filtering.md --- diff --git a/01_Archive/2026-04-20/Ontology-Engineering.md b/01_Archive/2026-04-20/Ontology-Engineering.md index 1fca48d7..21f7b22c 100644 --- a/01_Archive/2026-04-20/Ontology-Engineering.md +++ b/01_Archive/2026-04-20/Ontology-Engineering.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-8A5DA4 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Ontology-Engineering" --- -# [[Ontology-Engineering]] +# [[Ontology-Engineering|Ontology-Engineering]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Ontology-Engineering" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Ontology-Engineering.md]] +- Raw Source: 00_Raw/2026-04-20/Ontology-Engineering.md --- diff --git a/01_Archive/2026-04-20/Ontology-Guided Knowledge Extraction.md b/01_Archive/2026-04-20/Ontology-Guided Knowledge Extraction.md index d6fec33e..76a3682e 100644 --- a/01_Archive/2026-04-20/Ontology-Guided Knowledge Extraction.md +++ b/01_Archive/2026-04-20/Ontology-Guided Knowledge Extraction.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-691936 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Ontology-Guided Knowledge Extraction" --- -# [[Ontology-Guided Knowledge Extraction]] +# [[Ontology-Guided Knowledge Extraction|Ontology-Guided Knowledge Extraction]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Ontology-Guided Knowledge Extr ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Ontology-Guided Knowledge Extraction.md]] +- Raw Source: 00_Raw/2026-04-20/Ontology-Guided Knowledge Extraction.md --- diff --git a/01_Archive/2026-04-20/Opaque Types.md b/01_Archive/2026-04-20/Opaque Types.md index 92f3f29e..e8a28b03 100644 --- a/01_Archive/2026-04-20/Opaque Types.md +++ b/01_Archive/2026-04-20/Opaque Types.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-AB1B53 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Opaque Types" --- -# [[Opaque Types]] +# [[Opaque Types|Opaque Types]] ## 📌 한 줄 통찰 (The Karpathy Summary) > Opaque Types(또는 Branded Types, Nominal Types)는 타입스크립트의 구조적 타이핑(Structural Typing)이 갖는 한계를 극복하기 위해, 구조가 동일한 기본 타입(primitive type)이라도 의미적으로 다른 값을 구별할 수 있도록 고유한 식별자(브랜드)를 부여하는 디자인 패턴입니다 [1-4]. 런타임에는 존재하지 않는 가상의 속성이나 유니크 심볼(unique symbol)을 타입 시스템에만 추가하여 타입 간의 혼용을 컴파일 시점에 차단합니다 [2, 5, 6]. 이를 통해 화폐 단위, 사용자 ID와 주문 ID의 혼동 등 논리적 오류를 방지하고 코드의 안정성과 예측 가능성을 크게 높일 수 있습니다 [7-9]. @@ -20,11 +20,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Opaque Types" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Branded Types]], [[Structural Typing]], [[Nominal Typing]], [[Type Assertions]], [[Type Predicates]] -- **Projects/Contexts:** [[Domain-Driven Design (DDD)]], [[Zod Validation]], [[Effect TS]], [[ts-brand]] -- **Contradictions/Notes:** Opaque Types는 타입 안정성을 크게 높여주지만, 코드의 구조적 복잡성을 증가시키고 검증 함수나 타입 래퍼(Wrapper) 등 부가적인 코드를 요구한다는 단점이 있습니다 [30, 31]. 따라서 값의 범위가 명확히 정해져 있는 경우에는 Opaque Type 대신 [[Unions]], [[Enums]], 혹은 [[Template Literal Types]]와 같은 다른 타입스크립트 내장 전략을 활용하는 것이 더 단순하고 나은 해결책이 될 수 있습니다 [30, 32-34]. 추가로 Flow 같은 타입 시스템에서는 Opaque Type을 네이티브로 지원하지만, 타입스크립트 진영에서는 아직 이러한 네이티브 지원에 대한 완전한 합의에 이르지 못했습니다 [35]. +- **Related Topics:** [[Branded Types|Branded Types]], [[Structural Typing|Structural Typing]], [[Nominal Typing|Nominal Typing]], [[타입 단언 (Type Assertions)|Type Assertions]], [[Type Predicates|Type Predicates]] +- **Projects/Contexts:** [[Domain-Driven Design (DDD)|Domain-Driven Design (DDD)]], Zod Validation, [[Effect TS|Effect TS]], [[ts-brand|ts-brand]] +- **Contradictions/Notes:** Opaque Types는 타입 안정성을 크게 높여주지만, 코드의 구조적 복잡성을 증가시키고 검증 함수나 타입 래퍼(Wrapper) 등 부가적인 코드를 요구한다는 단점이 있습니다 [30, 31]. 따라서 값의 범위가 명확히 정해져 있는 경우에는 Opaque Type 대신 Unions, Enums, 혹은 [[Template-Literal-Types|Template Literal Types]]와 같은 다른 타입스크립트 내장 전략을 활용하는 것이 더 단순하고 나은 해결책이 될 수 있습니다 [30, 32-34]. 추가로 Flow 같은 타입 시스템에서는 Opaque Type을 네이티브로 지원하지만, 타입스크립트 진영에서는 아직 이러한 네이티브 지원에 대한 완전한 합의에 이르지 못했습니다 [35]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/Opaque Types.md]] +- Raw Source: 00_Raw/2026-04-20/Opaque Types.md --- diff --git a/01_Archive/2026-04-20/Opaque-Types.md b/01_Archive/2026-04-20/Opaque-Types.md index 08ac206d..e90891f1 100644 --- a/01_Archive/2026-04-20/Opaque-Types.md +++ b/01_Archive/2026-04-20/Opaque-Types.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-9E90BE -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Opaque-Types" --- -# [[Opaque-Types]] +# [[Opaque-Types|Opaque-Types]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Opaque-Types" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Opaque-Types.md]] +- Raw Source: 00_Raw/2026-04-20/Opaque-Types.md --- diff --git a/01_Archive/2026-04-20/Open Metaverse Framework.md b/01_Archive/2026-04-20/Open Metaverse Framework.md index 1367e6a1..42a419f2 100644 --- a/01_Archive/2026-04-20/Open Metaverse Framework.md +++ b/01_Archive/2026-04-20/Open Metaverse Framework.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-4C9A2B -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Open Metaverse Framework" --- -# [[Open Metaverse Framework]] +# [[Open Metaverse Framework|Open Metaverse Framework]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Open Metaverse Framework" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Open Metaverse Framework.md]] +- Raw Source: 00_Raw/2026-04-20/Open Metaverse Framework.md --- diff --git a/01_Archive/2026-04-20/Open-Access-Movement.md b/01_Archive/2026-04-20/Open-Access-Movement.md index 38b5aa35..052abe37 100644 --- a/01_Archive/2026-04-20/Open-Access-Movement.md +++ b/01_Archive/2026-04-20/Open-Access-Movement.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-F5F460 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Open-Access-Movement" --- -# [[Open-Access-Movement]] +# [[Open-Access-Movement|Open-Access-Movement]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Open-Access-Movement" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Open-Access-Movement.md]] +- Raw Source: 00_Raw/2026-04-20/Open-Access-Movement.md --- diff --git a/01_Archive/2026-04-20/Open-World Design Paradigms.md b/01_Archive/2026-04-20/Open-World Design Paradigms.md index fd6464a5..2b6e6564 100644 --- a/01_Archive/2026-04-20/Open-World Design Paradigms.md +++ b/01_Archive/2026-04-20/Open-World Design Paradigms.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-B36DC4 -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Open-World Design Paradigms" --- -# [[Open-World Design Paradigms]] +# [[Open-World Design Paradigms|Open-World Design Paradigms]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Open-World Design Paradigms" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Open-World Design Paradigms.md]] +- Raw Source: 00_Raw/2026-04-20/Open-World Design Paradigms.md --- diff --git a/01_Archive/2026-04-20/OpenAPI-Specification.md b/01_Archive/2026-04-20/OpenAPI-Specification.md index 6eb45bbd..b8730ca2 100644 --- a/01_Archive/2026-04-20/OpenAPI-Specification.md +++ b/01_Archive/2026-04-20/OpenAPI-Specification.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-B4497C -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - OpenAPI-Specification" --- -# [[OpenAPI-Specification]] +# [[OpenAPI-Specification|OpenAPI-Specification]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - OpenAPI-Specification" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/OpenAPI-Specification.md]] +- Raw Source: 00_Raw/2026-04-20/OpenAPI-Specification.md --- diff --git a/01_Archive/2026-04-20/OpenGL ES 2.0.md b/01_Archive/2026-04-20/OpenGL ES 2.0.md index 67633fb5..0a563d4f 100644 --- a/01_Archive/2026-04-20/OpenGL ES 2.0.md +++ b/01_Archive/2026-04-20/OpenGL ES 2.0.md @@ -1,4 +1,4 @@ -# [[OpenGL ES 2.0]] +# [[OpenGL ES 2.0|OpenGL ES 2.0]] ## 📌 Brief Summary OpenGL ES 2.0은 2011년에 도입된 크로스 플랫폼 웹 그래픽 라이브러리인 WebGL의 근간이 되는 그래픽 API입니다 [1, 2]. 이 아키텍처는 전역 그래픽 상태를 설정하고 유지하는 상태 머신(state-machine) 설계를 사용하며, 자바스크립트 코드를 GPU 명령으로 변환하는 역할을 수행합니다 [2, 3]. @@ -9,8 +9,8 @@ OpenGL ES 2.0은 2011년에 도입된 크로스 플랫폼 웹 그래픽 라이 * **구조적 한계 및 병목 현상:** 이 아키텍처는 2011년 당시에는 합리적인 구조였으나, 2011년 사양에 기능이 고정되어 있어 현대 GPU의 발전된 기능을 활용할 수 없다는 근본적인 한계를 지닙니다 [3, 4]. 또한 규모가 커질수록 상태 변경을 잊어버려 발생하는 미세한 버그나, 단일 스레드 기반의 명령 제출로 인한 CPU 병목 현상 등을 유발합니다 [3]. ## 🔗 Knowledge Connections -- **Related Topics:** [[WebGL]], [[WebGPU]], [[State-machine design]] -- **Projects/Contexts:** [[Web Graphics Rendering API]], [[3D Web-based HMI]] +- **Related Topics:** [[WebGL|WebGL]], [[WebGPU|WebGPU]], State-machine design +- **Projects/Contexts:** Web Graphics Rendering API, [[3D Web-based HMI|3D Web-based HMI]] - **Contradictions/Notes:** 소스 내에 직접적인 모순은 없으나, OpenGL ES 2.0 기반의 상태 머신 모델이 개발 초기(2011년)에는 타당한 설계였음에도 불구하고 오늘날의 대규모 그래픽 처리에서는 심각한 버그와 병목 현상의 원인이 되고 있음이 지적됩니다 [3, 4]. --- diff --git a/01_Archive/2026-04-20/OpenGL ES 20.md b/01_Archive/2026-04-20/OpenGL ES 20.md index b152d200..c57c1b00 100644 --- a/01_Archive/2026-04-20/OpenGL ES 20.md +++ b/01_Archive/2026-04-20/OpenGL ES 20.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-8560F5 -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - OpenGL ES 20" --- -# [[OpenGL ES 20]] +# [[OpenGL ES 20|OpenGL ES 20]] ## 📌 한 줄 통찰 (The Karpathy Summary) > OpenGL ES 2.0은 2011년에 도입된 크로스 플랫폼 웹 그래픽 라이브러리인 WebGL의 근간이 되는 그래픽 API입니다 [1, 2]. 이 아키텍처는 전역 그래픽 상태를 설정하고 유지하는 상태 머신(state-machine) 설계를 사용하며, 자바스크립트 코드를 GPU 명령으로 변환하는 역할을 수행합니다 [2, 3]. @@ -22,11 +22,11 @@ github_commit: "[P-Reinforce] Continuous Worker - OpenGL ES 20" - **정책 변화:** Graphics & Performance 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[WebGL]], [[WebGPU]], [[State-machine design]] -- **Projects/Contexts:** [[Web Graphics Rendering API]], [[3D Web-based HMI]] +- **Related Topics:** [[WebGL|WebGL]], [[WebGPU|WebGPU]], State-machine design +- **Projects/Contexts:** Web Graphics Rendering API, [[3D Web-based HMI|3D Web-based HMI]] - **Contradictions/Notes:** 소스 내에 직접적인 모순은 없으나, OpenGL ES 2.0 기반의 상태 머신 모델이 개발 초기(2011년)에는 타당한 설계였음에도 불구하고 오늘날의 대규모 그래픽 처리에서는 심각한 버그와 병목 현상의 원인이 되고 있음이 지적됩니다 [3, 4]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/OpenGL ES 2.0.md]] +- Raw Source: 00_Raw/2026-04-20/OpenGL ES 2.0.md --- diff --git a/01_Archive/2026-04-20/OpenGL ES.md b/01_Archive/2026-04-20/OpenGL ES.md index bb562acf..92100612 100644 --- a/01_Archive/2026-04-20/OpenGL ES.md +++ b/01_Archive/2026-04-20/OpenGL ES.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-D76AA6 -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - OpenGL ES" --- -# [[OpenGL ES]] +# [[OpenGL ES|OpenGL ES]] ## 📌 한 줄 통찰 (The Karpathy Summary) > OpenGL ES(특히 OpenGL ES 2.0)는 웹 기반 3D 렌더링을 지원하는 크로스 플랫폼 그래픽 라이브러리인 WebGL의 기반이 되는 그래픽 API입니다 [1, 2]. 텍스처나 셰이더 등의 전역 상태가 한 번 설정되면 변경될 때까지 유지되는 상태 머신(State-machine) 디자인을 채택하고 있습니다 [3]. 2011년경의 사양에 고정되어 있어, 최신 GPU의 고급 기능을 활용하기에는 아키텍처상 근본적인 한계를 지니고 있습니다 [3, 4]. @@ -23,11 +23,11 @@ github_commit: "[P-Reinforce] Continuous Worker - OpenGL ES" - **정책 변화:** Graphics & Performance 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[WebGL]], [[WebGPU]], [[ANGLE]] -- **Projects/Contexts:** [[3D Web-based HMI]] +- **Related Topics:** [[WebGL|WebGL]], [[WebGPU|WebGPU]], [[ANGLE|ANGLE]] +- **Projects/Contexts:** [[3D Web-based HMI|3D Web-based HMI]] - **Contradictions/Notes:** 소스에 관련 정보가 부족합니다. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/OpenGL ES.md]] +- Raw Source: 00_Raw/2026-04-20/OpenGL ES.md --- diff --git a/01_Archive/2026-04-20/Opera.md b/01_Archive/2026-04-20/Opera.md index d297a163..a1724db7 100644 --- a/01_Archive/2026-04-20/Opera.md +++ b/01_Archive/2026-04-20/Opera.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-71E521 -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Opera" --- -# [[Opera]] +# [[Opera|Opera]] ## 📌 한 줄 통찰 (The Karpathy Summary) > Opera는 웹 환경에서 그래픽 및 렌더링 기술을 구동하기 위해 사용되는 웹 브라우저 중 하나입니다. 업로드된 소스에서는 브라우저의 독립적인 특징보다는 WebGL 및 WebGPU와 같은 웹 그래픽 API의 호환성 및 지원 여부를 설명할 때 제한적으로만 언급됩니다. 전반적으로 Opera에 초점을 맞춘 상세한 설명은 존재하지 않으므로 소스에 관련 정보가 부족합니다. @@ -23,11 +23,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Opera" - **정책 변화:** Graphics & Performance 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[WebGL]], [[WebGPU]], [[ANGLE]] -- **Projects/Contexts:** [[웹 브라우저 그래픽 API 호환성]] +- **Related Topics:** [[WebGL|WebGL]], [[WebGPU|WebGPU]], [[ANGLE|ANGLE]] +- **Projects/Contexts:** [[웹 브라우저 그래픽 API 호환성|웹 브라우저 그래픽 API 호환성]] - **Contradictions/Notes:** 데스크톱 Opera는 특정 WebGL 확장 기능(`EXT_disjoint_timer_query`)을 부분적으로나마 지원하지만, 모바일(Android) 버전의 Opera에서는 해당 기능이 전혀 지원되지 않는 등 플랫폼에 따른 지원 격차가 존재합니다 [4]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Opera.md]] +- Raw Source: 00_Raw/2026-04-20/Opera.md --- diff --git a/01_Archive/2026-04-20/Operant Conditioning.md b/01_Archive/2026-04-20/Operant Conditioning.md index 4c96f36c..b2b76d15 100644 --- a/01_Archive/2026-04-20/Operant Conditioning.md +++ b/01_Archive/2026-04-20/Operant Conditioning.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-8BF017 -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Operant Conditioning" --- -# [[Operant Conditioning]] +# [[Operant Conditioning|Operant Conditioning]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Operant Conditioning" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Operant Conditioning.md]] +- Raw Source: 00_Raw/2026-04-20/Operant Conditioning.md --- diff --git a/01_Archive/2026-04-20/Operant_Conditioning.md b/01_Archive/2026-04-20/Operant_Conditioning.md index 92d9cccb..cc44ba22 100644 --- a/01_Archive/2026-04-20/Operant_Conditioning.md +++ b/01_Archive/2026-04-20/Operant_Conditioning.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-PSYCH-004 -category: "[[10_Wiki/💡 Topics/Psychology]]" +category: "10_Wiki/💡 Topics/Psychology" confidence_score: 0.94 tags: [psychology, behavior, conditioning, skinner] last_reinforced: 2026-04-20 github_commit: "batch-reinforce-03" --- -# [[Operant Conditioning]] +# [[Operant Conditioning|Operant Conditioning]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 행동의 결과가 미래의 행동 빈도를 결정한다는 원리를 통해 생명체의 적응적 행동 변화를 설명하는 고전적 메카니즘. @@ -24,6 +24,6 @@ github_commit: "batch-reinforce-03" - **정책 변화:** 사용자 경험(UX) 설계(w3) 시 '보상 스케줄'의 윤리적 적용 가이던스 강화. ## 🔗 지식 연결 (Graph) -- **Parent:** [[10_Wiki/💡 Topics/Psychology]] -- **Related:** [[ABA]], [[Behavioral-Economics]], [[Reinforcement-Learning]] -- **Raw Source:** [[00_Raw/2026-04-20/Operant Conditioning.md]] +- **Parent:** 10_Wiki/💡 Topics/Psychology +- **Related:** [[ABA|ABA]], [[Behavioral-Economics|Behavioral-Economics]], [[Reinforcement-Learning|Reinforcement-Learning]] +- **Raw Source:** 00_Raw/2026-04-20/Operant Conditioning.md diff --git a/01_Archive/2026-04-20/Operations-Management.md b/01_Archive/2026-04-20/Operations-Management.md index aadbb506..179a5098 100644 --- a/01_Archive/2026-04-20/Operations-Management.md +++ b/01_Archive/2026-04-20/Operations-Management.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-5F96BE -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Operations-Management" --- -# [[Operations-Management]] +# [[Operations-Management|Operations-Management]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Operations-Management" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Operations-Management.md]] +- Raw Source: 00_Raw/2026-04-20/Operations-Management.md --- diff --git a/01_Archive/2026-04-20/Operations-Research.md b/01_Archive/2026-04-20/Operations-Research.md index f9476289..c660018c 100644 --- a/01_Archive/2026-04-20/Operations-Research.md +++ b/01_Archive/2026-04-20/Operations-Research.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-1BE13E -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Operations-Research" --- -# [[Operations-Research]] +# [[Operations-Research|Operations-Research]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Operations-Research" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Operations-Research.md]] +- Raw Source: 00_Raw/2026-04-20/Operations-Research.md --- diff --git a/01_Archive/2026-04-20/Optimal-Experience-Research.md b/01_Archive/2026-04-20/Optimal-Experience-Research.md index 3fa7eecc..af03cb86 100644 --- a/01_Archive/2026-04-20/Optimal-Experience-Research.md +++ b/01_Archive/2026-04-20/Optimal-Experience-Research.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-BDC058 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Optimal-Experience-Research" --- -# [[Optimal-Experience-Research]] +# [[Optimal-Experience-Research|Optimal-Experience-Research]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Optimal-Experience-Research" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Optimal-Experience-Research.md]] +- Raw Source: 00_Raw/2026-04-20/Optimal-Experience-Research.md --- diff --git a/01_Archive/2026-04-20/Organizational Behavior.md b/01_Archive/2026-04-20/Organizational Behavior.md index 4ef7f381..899b7d2d 100644 --- a/01_Archive/2026-04-20/Organizational Behavior.md +++ b/01_Archive/2026-04-20/Organizational Behavior.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-189D31 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Organizational Behavior" --- -# [[Organizational Behavior]] +# [[Organizational Behavior|Organizational Behavior]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Organizational Behavior" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Organizational Behavior.md]] +- Raw Source: 00_Raw/2026-04-20/Organizational Behavior.md --- diff --git a/01_Archive/2026-04-20/Organizational Learning Culture.md b/01_Archive/2026-04-20/Organizational Learning Culture.md index 9186976e..a31fcfd1 100644 --- a/01_Archive/2026-04-20/Organizational Learning Culture.md +++ b/01_Archive/2026-04-20/Organizational Learning Culture.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-97FF1D -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Organizational Learning Culture" --- -# [[Organizational Learning Culture]] +# [[Organizational Learning Culture|Organizational Learning Culture]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Organizational Learning Cultur ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Organizational Learning Culture.md]] +- Raw Source: 00_Raw/2026-04-20/Organizational Learning Culture.md --- diff --git a/01_Archive/2026-04-20/Organizational Psychology.md b/01_Archive/2026-04-20/Organizational Psychology.md index 13bcd8e2..8b4b8039 100644 --- a/01_Archive/2026-04-20/Organizational Psychology.md +++ b/01_Archive/2026-04-20/Organizational Psychology.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-D27512 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Organizational Psychology" --- -# [[Organizational Psychology]] +# [[Organizational Psychology|Organizational Psychology]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Organizational Psychology" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Organizational Psychology.md]] +- Raw Source: 00_Raw/2026-04-20/Organizational Psychology.md --- diff --git a/01_Archive/2026-04-20/Organizational-Behavior.md b/01_Archive/2026-04-20/Organizational-Behavior.md index d716439d..19d5cd18 100644 --- a/01_Archive/2026-04-20/Organizational-Behavior.md +++ b/01_Archive/2026-04-20/Organizational-Behavior.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-0FF44B -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Organizational-Behavior" --- -# [[Organizational-Behavior]] +# [[Organizational-Behavior|Organizational-Behavior]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Organizational-Behavior" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Organizational-Behavior.md]] +- Raw Source: 00_Raw/2026-04-20/Organizational-Behavior.md --- diff --git a/01_Archive/2026-04-20/Organizational-Innovation-Management.md b/01_Archive/2026-04-20/Organizational-Innovation-Management.md index 4f1280b5..da522111 100644 --- a/01_Archive/2026-04-20/Organizational-Innovation-Management.md +++ b/01_Archive/2026-04-20/Organizational-Innovation-Management.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-27E3D1 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Organizational-Innovation-Management" --- -# [[Organizational-Innovation-Management]] +# [[Organizational-Innovation-Management|Organizational-Innovation-Management]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Organizational-Innovation-Mana ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Organizational-Innovation-Management.md]] +- Raw Source: 00_Raw/2026-04-20/Organizational-Innovation-Management.md --- diff --git a/01_Archive/2026-04-20/Organizational-Psychology.md b/01_Archive/2026-04-20/Organizational-Psychology.md index dcc7260f..c76f0f0d 100644 --- a/01_Archive/2026-04-20/Organizational-Psychology.md +++ b/01_Archive/2026-04-20/Organizational-Psychology.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-CB4F42 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Organizational-Psychology" --- -# [[Organizational-Psychology]] +# [[Organizational-Psychology|Organizational-Psychology]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Organizational-Psychology" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Organizational-Psychology.md]] +- Raw Source: 00_Raw/2026-04-20/Organizational-Psychology.md --- diff --git a/01_Archive/2026-04-20/Orinoco GC.md b/01_Archive/2026-04-20/Orinoco GC.md index 152c705a..138ae2da 100644 --- a/01_Archive/2026-04-20/Orinoco GC.md +++ b/01_Archive/2026-04-20/Orinoco GC.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-4DDD3E -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Orinoco GC" --- -# [[Orinoco GC]] +# [[Orinoco GC|Orinoco GC]] ## 📌 한 줄 통찰 (The Karpathy Summary) > Orinoco는 V8 JavaScript 엔진에 적용된 최신 가비지 컬렉터(GC) 프로젝트의 코드명이다 [1, 2]. 기존의 순차적이고 애플리케이션 실행을 완전히 멈추는 'stop-the-world' 방식의 가비지 컬렉터를 병렬(parallel), 점진적(incremental), 동시적(concurrent) 기술을 활용하는 형태로 변환하여 메인 스레드의 부하를 줄이도록 설계되었다 [1, 3]. 이를 통해 애플리케이션의 일시 정지(pause) 시간을 대폭 단축하고, 애니메이션 및 사용자 입력에 대한 응답성을 크게 향상시키는 역할을 한다 [4-6]. @@ -20,11 +20,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Orinoco GC" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[V8 Engine]], [[Garbage Collection]], [[Generational Hypothesis]], [[Scavenger]], [[Mark-Sweep-Compact]] -- **Projects/Contexts:** [[Chrome]], [[Node.js]] +- **Related Topics:** [[V8 Engine|V8 Engine]], [[Garbage Collection|Garbage Collection]], [[Generational Hypothesis|Generational Hypothesis]], [[Scavenger 알고리즘|Scavenger]], [[Mark-Sweep-Compact|Mark-Sweep-Compact]] +- **Projects/Contexts:** [[Chrome|Chrome]], [[Node.js|Node.js]] - **Contradictions/Notes:** 소스 간에 모순되는 정보는 발견되지 않았습니다. 문서 전반에 걸쳐 Orinoco GC 도입으로 인한 병렬성(Parallel) 및 동시성(Concurrent) 최적화의 이점이 일관되게 강조되어 있습니다. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Orinoco GC.md]] +- Raw Source: 00_Raw/2026-04-20/Orinoco GC.md --- diff --git a/01_Archive/2026-04-20/Orinoco 가비지 컬렉터.md b/01_Archive/2026-04-20/Orinoco 가비지 컬렉터.md index 15c3deb5..44714248 100644 --- a/01_Archive/2026-04-20/Orinoco 가비지 컬렉터.md +++ b/01_Archive/2026-04-20/Orinoco 가비지 컬렉터.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-3353DC -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Orinoco 가비지 컬렉터" --- -# [[Orinoco 가비지 컬렉터]] +# [[Orinoco 가비지 컬렉터|Orinoco 가비지 컬렉터]] ## 📌 한 줄 통찰 (The Karpathy Summary) > Orinoco는 V8 JavaScript 엔진의 가비지 컬렉션(GC) 성능을 최적화하기 위해 도입된 프로젝트의 코드명입니다 [1, 2]. 기존의 순차적이고 프로그램 실행을 멈추게 하는 'stop-the-world' 방식의 수집기를 점진적(Incremental) 폴백(Fallback)을 갖춘 병렬(Parallel) 및 동시성(Concurrent) 수집기로 탈바꿈시켰습니다 [1, 3]. 이를 통해 메인 스레드의 GC 작업 부담을 최소화하여 애플리케이션의 지연 시간(Latency)을 줄이고 스크롤 및 애니메이션 렌더링을 훨씬 부드럽게 만들었습니다 [4, 5]. @@ -32,11 +32,11 @@ Orinoco는 메인 스레드를 해방시키기 위해 다음 세 가지 주요 - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[가비지 컬렉션(Garbage Collection)]], [[V8 JavaScript 엔진]], [[Minor GC (Scavenger)]], [[Major GC (Mark-Compact)]], [[세대별 가비지 컬렉션(Generational Garbage Collection)]] -- **Projects/Contexts:** [[V8 메모리 관리 및 최적화]], [[Node.js 및 Chrome 브라우저 렌더링 성능 최적화]] +- **Related Topics:** [[가비지 컬렉션(Garbage Collection)|가비지 컬렉션(Garbage Collection)]], [[V8 JavaScript 엔진|V8 JavaScript 엔진]], Minor GC (Scavenger), Major GC (Mark-Compact), 세대별 가비지 컬렉션(Generational Garbage Collection) +- **Projects/Contexts:** V8 메모리 관리 및 최적화, Node.js 및 Chrome 브라우저 렌더링 성능 최적화 - **Contradictions/Notes:** 과거 V8 버전은 Cheney의 동기식 세미스페이스 복사 알고리즘을 사용했으나, V8 v6.2부터 Orinoco 프로젝트의 일환으로 동적 작업 훔치기(Work stealing) 기법을 사용하는 Halstead 방식의 병렬 스캐빈저로 대체되었습니다 [10, 18]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Orinoco 가비지 컬렉터.md]] +- Raw Source: 00_Raw/2026-04-20/Orinoco 가비지 컬렉터.md --- diff --git a/01_Archive/2026-04-20/Orinoco 프로젝트.md b/01_Archive/2026-04-20/Orinoco 프로젝트.md index aeb8e3de..5ef9d754 100644 --- a/01_Archive/2026-04-20/Orinoco 프로젝트.md +++ b/01_Archive/2026-04-20/Orinoco 프로젝트.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-6EB2FE -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Orinoco 프로젝트" --- -# [[Orinoco 프로젝트]] +# [[Orinoco 프로젝트|Orinoco 프로젝트]] ## 📌 한 줄 통찰 (The Karpathy Summary) > Orinoco 프로젝트는 V8 JavaScript 엔진의 가비지 컬렉터(GC)를 최신 기술로 개선하기 위해 진행된 프로젝트의 코드명입니다 [1-3]. 이 프로젝트는 기존의 순차적이고 모든 실행을 멈추는 'stop-the-world' 방식의 가비지 컬렉터를 병렬(parallel), 동시(concurrent), 점진적(incremental) 기술을 활용하는 형태로 진화시켰습니다 [1, 2, 4]. 주된 목적은 메인 스레드의 부하를 덜어주어 가비지 컬렉션으로 인한 프로그램 중지 시간(pause time)을 최소화하고 사용자 경험을 향상시키는 것입니다 [2, 5]. @@ -24,11 +24,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Orinoco 프로젝트" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[V8 Engine]], [[Garbage Collection (GC)]], [[Stop-the-world]], [[Incremental Marking]] -- **Projects/Contexts:** [[Oilpan]], [[Blink]] +- **Related Topics:** [[V8 Engine|V8 Engine]], [[Garbage Collection (GC)|Garbage Collection (GC)]], [[Stop-the-world|Stop-the-world]], [[Incremental Marking|Incremental Marking]] +- **Projects/Contexts:** [[Oilpan|Oilpan]], [[Blink|Blink]] - **Contradictions/Notes:** 소스에 관련 정보가 부족합니다. (소스 내에서 Orinoco 프로젝트에 대한 상충되는 주장은 발견되지 않습니다.) --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Orinoco 프로젝트.md]] +- Raw Source: 00_Raw/2026-04-20/Orinoco 프로젝트.md --- diff --git a/01_Archive/2026-04-20/Orinoco(V8 GC 프로젝트).md b/01_Archive/2026-04-20/Orinoco(V8 GC 프로젝트).md index e099f023..56ff17df 100644 --- a/01_Archive/2026-04-20/Orinoco(V8 GC 프로젝트).md +++ b/01_Archive/2026-04-20/Orinoco(V8 GC 프로젝트).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-6C6E51 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Orinoco(V8 GC 프로젝트)" --- -# [[Orinoco(V8 GC 프로젝트)]] +# [[Orinoco(V8 GC 프로젝트)|Orinoco(V8 GC 프로젝트)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > Orinoco는 V8 JavaScript 엔진의 가비지 컬렉터(GC)를 혁신적으로 개선하기 위해 진행된 프로젝트의 코드명이다 [1, 2]. 이 프로젝트의 핵심 목표는 기존의 순차적이고 메인 스레드를 멈추게 하던(stop-the-world) 가비지 컬렉터를 병렬(Parallel), 점진적(Incremental), 동시적(Concurrent) 수집 방식으로 변환하는 것이다 [1]. 이를 통해 메인 스레드의 부하를 해방시키고 가비지 컬렉션으로 인한 애플리케이션 지연(jank)과 대기 시간을 대폭 줄여 원활한 사용자 경험을 제공한다 [3, 4]. @@ -20,11 +20,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Orinoco(V8 GC 프로젝트)" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[V8 Engine]], [[Garbage Collection]], [[Scavenger (Minor GC)]], [[Mark-Compact (Major GC)]] -- **Projects/Contexts:** [[V8 JavaScript Engine Memory Management]] +- **Related Topics:** [[V8 Engine|V8 Engine]], [[Garbage Collection|Garbage Collection]], [[Scavenger(Minor GC)|Scavenger (Minor GC)]], Mark-Compact (Major GC) +- **Projects/Contexts:** V8 JavaScript Engine Memory Management - **Contradictions/Notes:** 점진적(Incremental) 가비지 컬렉션 기법의 경우, 메인 스레드의 일시 정지(Pause) 기간을 여러 개의 짧은 시간으로 분산시켜 체감 대기 시간을 줄이지만, 메인 스레드에서 수행하는 GC의 총시간 자체는 오히려 약간 증가한다는 특징이 있다 [8]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Orinoco(V8 GC 프로젝트).md]] +- Raw Source: 00_Raw/2026-04-20/Orinoco(V8 GC 프로젝트).md --- diff --git a/01_Archive/2026-04-20/Orinoco.md b/01_Archive/2026-04-20/Orinoco.md index 68f548ce..2a0f213b 100644 --- a/01_Archive/2026-04-20/Orinoco.md +++ b/01_Archive/2026-04-20/Orinoco.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-E147D0 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Orinoco" --- -# [[Orinoco]] +# [[Orinoco|Orinoco]] ## 📌 한 줄 통찰 (The Karpathy Summary) > Orinoco는 V8 JavaScript 엔진의 가비지 컬렉터(GC) 성능을 최적화하기 위해 진행된 프로젝트의 코드명입니다 [1, 2]. 이 프로젝트는 기존의 순차적이고 애플리케이션 실행을 완전히 멈추는(stop-the-world) 방식의 가비지 컬렉터를 병렬(parallel), 동시(concurrent), 점진적(incremental) 기법을 활용하는 형태로 변환했습니다 [1, 2]. 결과적으로 메인 스레드의 부담을 해방시켜 지연(latency) 및 멈춤(jank) 현상을 줄이고, 애니메이션과 사용자 상호작용을 훨씬 부드럽게 만들어 줍니다 [3-6]. @@ -23,11 +23,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Orinoco" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[V8 Engine]], [[Garbage Collection]], [[Scavenger]], [[Mark-Compact]] -- **Projects/Contexts:** [[JavaScript Memory Management]] +- **Related Topics:** [[V8 Engine|V8 Engine]], [[Garbage Collection|Garbage Collection]], [[Scavenger 알고리즘|Scavenger]], [[마크-컴팩트(Mark-Compact)|Mark-Compact]] +- **Projects/Contexts:** JavaScript Memory Management - **Contradictions/Notes:** 소스 간 Orinoco의 목적과 기술적 효과에 대해 상충되는 정보는 발견되지 않으며, 모든 소스가 공통적으로 메인 스레드의 지연을 없애고 메모리 관리 효율성을 높이기 위한 최적화 프로젝트로 일관되게 설명하고 있습니다. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Orinoco.md]] +- Raw Source: 00_Raw/2026-04-20/Orinoco.md --- diff --git a/01_Archive/2026-04-20/Orthopedic-Implant-Validation.md b/01_Archive/2026-04-20/Orthopedic-Implant-Validation.md index 349d8d72..9515b043 100644 --- a/01_Archive/2026-04-20/Orthopedic-Implant-Validation.md +++ b/01_Archive/2026-04-20/Orthopedic-Implant-Validation.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-9F5A29 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Orthopedic-Implant-Validation" --- -# [[Orthopedic-Implant-Validation]] +# [[Orthopedic-Implant-Validation|Orthopedic-Implant-Validation]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Orthopedic-Implant-Validation" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Orthopedic-Implant-Validation.md]] +- Raw Source: 00_Raw/2026-04-20/Orthopedic-Implant-Validation.md --- diff --git a/01_Archive/2026-04-20/Outer Alignment vs Inner Alignment.md b/01_Archive/2026-04-20/Outer Alignment vs Inner Alignment.md index 204d9d99..3ba51bd3 100644 --- a/01_Archive/2026-04-20/Outer Alignment vs Inner Alignment.md +++ b/01_Archive/2026-04-20/Outer Alignment vs Inner Alignment.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-5C9E29 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Outer Alignment vs Inner Alignment" --- -# [[Outer Alignment vs Inner Alignment]] +# [[Outer Alignment vs Inner Alignment|Outer Alignment vs Inner Alignment]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Outer Alignment vs Inner Align ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Outer Alignment vs Inner Alignment.md]] +- Raw Source: 00_Raw/2026-04-20/Outer Alignment vs Inner Alignment.md --- diff --git a/01_Archive/2026-04-20/Overdraw.md b/01_Archive/2026-04-20/Overdraw.md index 1d22d6ed..fdf9910d 100644 --- a/01_Archive/2026-04-20/Overdraw.md +++ b/01_Archive/2026-04-20/Overdraw.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-421E43 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Overdraw" --- -# [[Overdraw]] +# [[Overdraw|Overdraw]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 오버드로우(Overdraw)는 렌더링 파이프라인의 프래그먼트 셰이딩(Fragment Shading) 단계에서 동일한 픽셀 위치에 렌더링 연산 및 쓰기 작업이 여러 번 중첩되어 GPU 자원이 낭비되는 현상입니다. InstancedMesh를 사용할 때 개별 인스턴스에 대한 자동 정렬(Sorting) 기능이 부재하여 깊이 테스트(Early-Z)를 통한 최적화가 무력화되면서 막대한 오버드로우가 발생할 수 있으며, 이는 심각한 렌더링 프레임 지연의 핵심 원인이 됩니다[1, 2]. @@ -27,11 +27,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Overdraw" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[InstancedMesh]], [[Fragment Shading]], [[Early-Z]], [[프래그먼트 바운드(Fragment-bound)]], [[Draw Call]], [[Sorting]] -- **Projects/Contexts:** [[three.js Issue #30352]], [[대규모 인스턴스 렌더링 및 투명도 처리]] +- **Related Topics:** [[InstancedMesh|InstancedMesh]], [[Fragment Shading|Fragment Shading]], [[Early-Z|Early-Z]], [[프래그먼트 바운드(Fragment-bound)|프래그먼트 바운드(Fragment-bound)]], [[Draw Call|Draw Call]], [[Sorting|Sorting]] +- **Projects/Contexts:** [[threejs Issue _30352|three.js Issue]], [[대규모 인스턴스 렌더링 및 투명도 처리|대규모 인스턴스 렌더링 및 투명도 처리]] - **Contradictions/Notes:** CPU 부하를 유발하는 드로우 콜을 줄이기 위해 InstancedMesh를 도입하더라도, 내부 인스턴스들의 정렬 부재가 유발하는 오버드로우 비용이 더 크다면 오히려 드로우 콜이 많은 개별 메쉬 렌더링 방식보다 FPS가 떨어질 수 있다는 역설적인 결과를 보여줍니다[2, 5]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Overdraw.md]] +- Raw Source: 00_Raw/2026-04-20/Overdraw.md --- diff --git a/01_Archive/2026-04-20/P-Reinforce_Skill.md b/01_Archive/2026-04-20/P-Reinforce_Skill.md index 6220e393..334c6d74 100644 --- a/01_Archive/2026-04-20/P-Reinforce_Skill.md +++ b/01_Archive/2026-04-20/P-Reinforce_Skill.md @@ -6,7 +6,7 @@ 1. **Knowledge Ingestion**: `knowledge/` 폴더에 존재하는 모든 마크다운 파일을 정기적으로 `00_Raw/`의 날짜별 폴더로 자동 복사(Ingestion)하여 시스템의 먹이로 제공한다. 2. **Real-time Monitoring**: `00_Raw/` 폴더의 모든 입력을 실시간 모니터링하고 지식화하라. 3. **Autonomous Structure**: 폴더 구조를 고정하지 말고, 지식의 맥락에 따라 스스로 '폴더 트리'를 설계하고 확장하라. -4. **Knowledge Synthesis**: 지식의 파편들을 [[쌍방향 링크]]로 엮어 하나의 거대한 '외부 뇌'를 구축하라. +4. **Knowledge Synthesis**: 지식의 파편들을 쌍방향 링크로 엮어 하나의 거대한 '외부 뇌'를 구축하라. 5. **Version Preservation**: 모든 변화를 GitHub에 커밋하여 지식의 타임라인을 보존하라. ## 🧠 강화학습 기반 구조화 로직 (The RL Logic) @@ -38,14 +38,14 @@ root/ ## 📝 지식 문서 변환 규격 --- id: {{UUID}} -category: "[[10_Wiki/Path/To/Folder]]" +category: "10_Wiki/Path/To/Folder" confidence_score: 0.0 ~ 1.0 (RL 기반 확신도) tags: [tag1, tag2] last_reinforced: {{DATE}} github_commit: "{{commit_hash}}" --- -# [[문서 제목]] +# 문서 제목 ## 📌 한 줄 통찰 (The Karpathy Summary) > 이 지식의 핵심을 꿰뚫는 단 한 문장. @@ -55,13 +55,13 @@ github_commit: "{{commit_hash}}" - **세부 내용:** (불렛포인트 위주의 간결한 정리) ## ⚠️ 모순 및 업데이트 (Contradictions & RL Update) -- **과거 데이터와의 충돌:** [[이전_문서]]와 달라진 점 기록. +- **과거 데이터와의 충돌:** 이전_문서와 달라진 점 기록. - **정책 변화:** 이 문서를 통해 강화된 분류 기준 설명. ## 🔗 지식 연결 (Graph) -- **Parent:** [[상위_카테고리]] -- **Related:** [[연관_개념_A]], [[연관_개념_B]] -- **Raw Source:** [[00_Raw/YYYY-MM-DD/Original_Note]] +- **Parent:** 상위_카테고리 +- **Related:** 연관_개념_A, 연관_개념_B +- **Raw Source:** 00_Raw/YYYY-MM-DD/Original_Note ## 💻 GitHub 동기화 자동화 워크플로우 1. Stage: git add . diff --git a/01_Archive/2026-04-20/PBR.md b/01_Archive/2026-04-20/PBR.md index 7ced945b..e9ebef85 100644 --- a/01_Archive/2026-04-20/PBR.md +++ b/01_Archive/2026-04-20/PBR.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-773FEF -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - PBR" --- -# [[PBR]] +# [[PBR|PBR]] ## 📌 한 줄 통찰 (The Karpathy Summary) > PBR(Physically-Based Rendering)은 현실 세계의 물질 물리 법칙을 적용하여 사실적인 시각 효과를 달성하는 렌더링 방법론입니다 [1]. 알베도(albedo), 노멀(normal), 메탈릭(metallic), 러프니스(roughness), 앰비언트 오클루전(ambient occlusion) 등의 다중 텍스처 맵을 조합하여 표면 속성을 세밀하게 정의합니다 [2]. 사실감을 표현하는 최신 표준 기술이지만, 에너지 보존 법칙과 프레넬(Fresnel) 반사 등의 복잡한 계산을 수반하기 때문에 그래픽 연산 비용이 매우 높다는 특징이 있습니다 [3]. @@ -27,11 +27,11 @@ github_commit: "[P-Reinforce] Continuous Worker - PBR" - **정책 변화:** Graphics & Performance 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[MeshStandardMaterial]], [[Texture Channel Packing]], [[Metallic Maps]], [[Roughness Maps]] -- **Projects/Contexts:** [[Three.js 웹 렌더링 최적화]], [[Image-To-3D 모델 브라우저 배포]] +- **Related Topics:** [[MeshStandardMaterial 조명 연산|MeshStandardMaterial]], Texture Channel Packing, Metallic Maps, Roughness Maps +- **Projects/Contexts:** Three.js 웹 렌더링 최적화, Image-To-3D 모델 브라우저 배포 - **Contradictions/Notes:** PBR 방식(예: MeshStandardMaterial)은 궁극적인 사실주의를 제공하지만 연산 비용이 높아 고사양 워크스테이션에 적합합니다. 저사양이나 내장 그래픽(iGPU) 환경에서 성능을 우선시해야 할 경우에는 상대적으로 연산량이 적은 비물리 기반의 Blinn-Phong 모델(예: MeshPhongMaterial)을 사용하는 것이 더 나을 수 있습니다 [3, 4]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/PBR.md]] +- Raw Source: 00_Raw/2026-04-20/PBR.md --- diff --git a/01_Archive/2026-04-20/PCGML-Frameworks.md b/01_Archive/2026-04-20/PCGML-Frameworks.md index 0df8e152..4a773da2 100644 --- a/01_Archive/2026-04-20/PCGML-Frameworks.md +++ b/01_Archive/2026-04-20/PCGML-Frameworks.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-294A76 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - PCGML-Frameworks" --- -# [[PCGML-Frameworks]] +# [[PCGML-Frameworks|PCGML-Frameworks]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - PCGML-Frameworks" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/PCGML-Frameworks.md]] +- Raw Source: 00_Raw/2026-04-20/PCGML-Frameworks.md --- diff --git a/01_Archive/2026-04-20/PEFT (Parameter-Efficient Fine-Tuning).md b/01_Archive/2026-04-20/PEFT (Parameter-Efficient Fine-Tuning).md index 5bcadf1a..b28c5cce 100644 --- a/01_Archive/2026-04-20/PEFT (Parameter-Efficient Fine-Tuning).md +++ b/01_Archive/2026-04-20/PEFT (Parameter-Efficient Fine-Tuning).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-5B20CE -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - PEFT (Parameter-Efficient Fine-Tuning)" --- -# [[PEFT (Parameter-Efficient Fine-Tuning)]] +# [[PEFT (Parameter-Efficient Fine-Tuning)|PEFT (Parameter-Efficient Fine-Tuning)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - PEFT (Parameter-Efficient Fine ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/PEFT (Parameter-Efficient Fine-Tuning).md]] +- Raw Source: 00_Raw/2026-04-20/PEFT (Parameter-Efficient Fine-Tuning).md --- diff --git a/01_Archive/2026-04-20/PRM (Process Reward Model).md b/01_Archive/2026-04-20/PRM (Process Reward Model).md index 1fa2dd2a..69f202ba 100644 --- a/01_Archive/2026-04-20/PRM (Process Reward Model).md +++ b/01_Archive/2026-04-20/PRM (Process Reward Model).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-58769F -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - PRM (Process Reward Model)" --- -# [[PRM (Process Reward Model)]] +# [[PRM (Process Reward Model)|PRM (Process Reward Model)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - PRM (Process Reward Model)" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/PRM (Process Reward Model).md]] +- Raw Source: 00_Raw/2026-04-20/PRM (Process Reward Model).md --- diff --git a/01_Archive/2026-04-20/Page Experience Algorithm.md b/01_Archive/2026-04-20/Page Experience Algorithm.md index 6dc70818..e7487b9f 100644 --- a/01_Archive/2026-04-20/Page Experience Algorithm.md +++ b/01_Archive/2026-04-20/Page Experience Algorithm.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-6A1F2E -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Page Experience Algorithm" --- -# [[Page Experience Algorithm]] +# [[Page Experience Algorithm|Page Experience Algorithm]] ## 📌 한 줄 통찰 (The Karpathy Summary) > Page Experience Algorithm(페이지 경험 알고리즘)은 구글(Google)이 검색 순위를 결정할 때 사용하는 알고리즘입니다 [1]. 이 알고리즘은 실제 사용자의 웹페이지 경험을 측정하는 표준화된 지표인 코어 웹 바이탈(Core Web Vitals)을 주요 랭킹 신호(Ranking signals)로 사용합니다 [1, 2]. 이 알고리즘의 기준을 충족하는 것은 검색 순위를 방어하거나 향상시키고 사용자 유지율을 높이는 데 필수적입니다 [1, 3]. @@ -23,11 +23,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Page Experience Algorithm" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Core Web Vitals]], [[INP (Interaction to Next Paint)]], [[LCP (Largest Contentful Paint)]], [[CLS (Cumulative Layout Shift)]] -- **Projects/Contexts:** [[Google Search Ranking]], [[Chrome User Experience Report (CrUX)]] +- **Related Topics:** [[Core Web Vitals|Core Web Vitals]], INP (Interaction to Next Paint), LCP (Largest Contentful Paint), CLS (Cumulative Layout Shift) +- **Projects/Contexts:** Google Search Ranking, [[Chrome User Experience Report (CrUX)|Chrome User Experience Report (CrUX)]] - **Contradictions/Notes:** 소스에 코어 웹 바이탈 지표들 외에 페이지 경험 알고리즘의 내부적인 작동 원리나 코어 웹 바이탈 이외의 추가적인 구성 요소에 대한 관련 정보가 부족합니다. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Page Experience Algorithm.md]] +- Raw Source: 00_Raw/2026-04-20/Page Experience Algorithm.md --- diff --git a/01_Archive/2026-04-20/PageRank (페이지랭크 알고리즘).md b/01_Archive/2026-04-20/PageRank (페이지랭크 알고리즘).md index dd374dbd..d09d44bf 100644 --- a/01_Archive/2026-04-20/PageRank (페이지랭크 알고리즘).md +++ b/01_Archive/2026-04-20/PageRank (페이지랭크 알고리즘).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-ECBEB7 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - PageRank (페이지랭크 알고리즘)" --- -# [[PageRank (페이지랭크 알고리즘)]] +# [[PageRank (페이지랭크 알고리즘)|PageRank (페이지랭크 알고리즘)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - PageRank (페이지랭크 알 ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/PageRank (페이지랭크 알고리즘).md]] +- Raw Source: 00_Raw/2026-04-20/PageRank (페이지랭크 알고리즘).md --- diff --git a/01_Archive/2026-04-20/PageSpeed Insights.md b/01_Archive/2026-04-20/PageSpeed Insights.md index 4c2b6dfa..caa92b4c 100644 --- a/01_Archive/2026-04-20/PageSpeed Insights.md +++ b/01_Archive/2026-04-20/PageSpeed Insights.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-FB1C7F -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - PageSpeed Insights" --- -# [[PageSpeed Insights]] +# [[PageSpeed Insights|PageSpeed Insights]] ## 📌 한 줄 통찰 (The Karpathy Summary) > PageSpeed Insights는 웹 페이지의 로딩 속도와 사용자 경험 성능을 측정하고 개선을 위한 진단 결과를 제공하는 도구입니다. 이 도구의 진단 기능은 주로 Lighthouse에 의해 구동되며, 최근에는 INP(Interaction to Next Paint)를 비롯한 코어 웹 바이탈(Core Web Vitals) 지표를 통합하여 웹사이트의 전반적인 반응성을 평가합니다 [1-3]. @@ -22,11 +22,11 @@ github_commit: "[P-Reinforce] Continuous Worker - PageSpeed Insights" - **정책 변화:** AI 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Lighthouse]], [[Core Web Vitals]], [[Interaction to Next Paint (INP)]], [[Largest Contentful Paint (LCP)]] -- **Projects/Contexts:** [[Web Performance Optimization]], [[Chrome User Experience Report (CrUX)]] +- **Related Topics:** [[Lighthouse|Lighthouse]], [[Core Web Vitals|Core Web Vitals]], [[Interaction to Next Paint (INP)|Interaction to Next Paint (INP)]], [[Largest Contentful Paint (LCP)|Largest Contentful Paint (LCP)]] +- **Projects/Contexts:** [[Web Performance Optimization|Web Performance Optimization]], [[Chrome User Experience Report (CrUX)|Chrome User Experience Report (CrUX)]] - **Contradictions/Notes:** PageSpeed Insights는 웹 성능을 평가하는 공식적이고 강력한 도구이지만, LCP 하위 요소 데이터와 같은 특정 세부 지표는 도구 내에서 직접 확인할 수 없어 다른 시각화 도구의 병행 사용이 필요할 수 있습니다 [5]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/PageSpeed Insights.md]] +- Raw Source: 00_Raw/2026-04-20/PageSpeed Insights.md --- diff --git a/01_Archive/2026-04-20/Papers Please (Bureaucratic Simulation).md b/01_Archive/2026-04-20/Papers Please (Bureaucratic Simulation).md index 535ddd96..82eda225 100644 --- a/01_Archive/2026-04-20/Papers Please (Bureaucratic Simulation).md +++ b/01_Archive/2026-04-20/Papers Please (Bureaucratic Simulation).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-5F8F7B -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Papers Please (Bureaucratic Simulation)" --- -# [[Papers Please (Bureaucratic Simulation)]] +# [[Papers Please (Bureaucratic Simulation)|Papers Please (Bureaucratic Simulation)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Papers Please (Bureaucratic Si ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Papers, Please (Bureaucratic Simulation).md]] +- Raw Source: 00_Raw/2026-04-20/Papers, Please (Bureaucratic Simulation).md --- diff --git a/01_Archive/2026-04-20/Papers Please (Mechanics as Moral Argument).md b/01_Archive/2026-04-20/Papers Please (Mechanics as Moral Argument).md index 3ea993a7..1caf2bb8 100644 --- a/01_Archive/2026-04-20/Papers Please (Mechanics as Moral Argument).md +++ b/01_Archive/2026-04-20/Papers Please (Mechanics as Moral Argument).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-126062 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Papers Please (Mechanics as Moral Argument)" --- -# [[Papers Please (Mechanics as Moral Argument)]] +# [[Papers Please (Mechanics as Moral Argument)|Papers Please (Mechanics as Moral Argument)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Papers Please (Mechanics as Mo ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Papers, Please (Mechanics as Moral Argument).md]] +- Raw Source: 00_Raw/2026-04-20/Papers, Please (Mechanics as Moral Argument).md --- diff --git a/01_Archive/2026-04-20/Papers, Please (Bureaucratic Simulation).md b/01_Archive/2026-04-20/Papers, Please (Bureaucratic Simulation).md index 282e919f..5a813b75 100644 --- a/01_Archive/2026-04-20/Papers, Please (Bureaucratic Simulation).md +++ b/01_Archive/2026-04-20/Papers, Please (Bureaucratic Simulation).md @@ -1,4 +1,4 @@ -[[Papers, Please (Bureaucratic Simulation)]] +[[Papers, Please (Bureaucratic Simulation)|Papers, Please (Bureaucratic Simulation)]] 📌 Brief Summary *Papers, Please* is a critically acclaimed indie video game developed by Lucas Pope that functions as a "dystopian bureaucratic simulator." It places the player in the role of a border control officer in the fictional communist state of Arstotzka, requiring the meticulous verification of documents to identify discrepancies. Beyond its mechanical loop, the game serves as a profound socio-political commentary on the dehumanizing effects of bureaucracy, the ethical dilemmas of state-mandated compliance, and the psychological toll of systemic surveillance. @@ -14,8 +14,8 @@ The lo-fi, pixelated aesthetic serves to dehumanize the NPCs (Non-Player Characters), reducing complex human lives to mere data points on a passport. This visual reductionism reinforces the player's role as an instrument of the state, where the "human" element is secondary to the "documentary" element. 🔗 Knowledge Connections -* Related Topics: [[Procedural Rhetoric]], [[Banality of Evil]], [[Algorithmic Governance]], [[Dystopian Literature]] -* Projects/Contexts: [[Lucas Pope's Design Philosophy]], [[Game Studies (Ludology)]], [[Political Science: Authoritarianism and Surveillance]] +* Related Topics: [[Procedural Rhetoric|Procedural Rhetoric]], Banality of Evil, [[Algorithmic Governance|Algorithmic Governance]], Dystopian Literature +* Projects/Contexts: Lucas Pope's Design Philosophy, Game Studies (Ludology), Political Science: Authoritarianism and Surveillance * Contradictions/Notes: While some critics view the game as a pure critique of totalitarianism, others argue it functions more as a simulation of "systemic exhaustion," focusing less on political ideology and more on the cognitive load of administrative labor. Last updated: 2026-04-16 \ No newline at end of file diff --git a/01_Archive/2026-04-20/Papers, Please (Mechanics as Moral Argument).md b/01_Archive/2026-04-20/Papers, Please (Mechanics as Moral Argument).md index 9e75f34e..1574453f 100644 --- a/01_Archive/2026-04-20/Papers, Please (Mechanics as Moral Argument).md +++ b/01_Archive/2026-04-20/Papers, Please (Mechanics as Moral Argument).md @@ -1,4 +1,4 @@ -[[Papers, Please (Mechanics as Moral Argument)]] +[[Papers, Please (Mechanics as Moral Argument)|Papers, Please (Mechanics as Moral Argument)]] 📌 Brief Summary This topic explores the ludonarrative phenomenon in Lucas Pope's *Papers, Please*, where gameplay mechanics—specifically repetitive, high-stress administrative tasks—function as a primary vehicle for moral argumentation. Rather than relying on cinematic cutscenes, the game utilizes "procedural rhetoric" to force players into ethical dilemmas through the friction of bureaucratic efficiency and economic survival. @@ -10,8 +10,8 @@ This topic explores the ludonarrative phenomenon in Lucas Pope's *Papers, Please * **Economic Determinism and Agency:** The game utilizes a survival mechanic (the budget/ledger) to constrain player agency. By making the cost of failure (starvation/death of family members) tangible, the game argues that morality is often a luxury afforded only to those not under extreme economic duress. This transforms the moral argument from an abstract philosophical debate into a practical struggle for survival. 🔗 Knowledge Connections -* Related Topics: [[Procedural Rhetoric]], [[Ludonarrative Dissonance]], [[Systems Thinking in Game Design]], [[The Ethics of Bureaucracy]] -* Projects/Contexts: [[Lucas Pope's Works]], [[Game Studies (Ludology)]], [[Simulations of Totalitarianism]] +* Related Topics: [[Procedural Rhetoric|Procedural Rhetoric]], [[Ludonarrative Dissonance|Ludonarrative Dissonance]], Systems Thinking in Game Design, The Ethics of Bureaucracy +* Projects/Contexts: Lucas Pope's Works, Game Studies (Ludology), Simulations of Totalitarianism * Contradictions/Notes: Some scholars argue that the "survival" mechanic can overshadow the political critique by reducing moral choices to mere resource management; however, most contemporary research views this integration as the game's defining strength. Last updated: 2026-04-16 \ No newline at end of file diff --git a/01_Archive/2026-04-20/Papers-Please.md b/01_Archive/2026-04-20/Papers-Please.md index 8772fdde..acc85e59 100644 --- a/01_Archive/2026-04-20/Papers-Please.md +++ b/01_Archive/2026-04-20/Papers-Please.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-6CA77E -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Papers-Please" --- -# [[Papers-Please]] +# [[Papers-Please|Papers-Please]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Papers-Please" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Papers-Please.md]] +- Raw Source: 00_Raw/2026-04-20/Papers-Please.md --- diff --git a/01_Archive/2026-04-20/Parse dont validate.md b/01_Archive/2026-04-20/Parse dont validate.md index 4bf733c6..01298e57 100644 --- a/01_Archive/2026-04-20/Parse dont validate.md +++ b/01_Archive/2026-04-20/Parse dont validate.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-D95ED1 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Parse dont validate" --- -# [[Parse dont validate]] +# [[Parse dont validate|Parse dont validate]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 'Parse, don't validate(검증하지 말고 파싱하라)'는 프로그램의 경계에서 타입이 없거나 느슨한 데이터를 잘 정의된 타입의 데이터로 변환하는 소프트웨어 설계 철학입니다[1]. 코드 전반에 걸쳐 데이터의 유효성을 반복적으로 검사하는 대신, 시스템 진입점에서 단 한 번 파싱하여 안전한 타입으로 만듭니다[1]. 이를 통해 유효성 검사 로직의 파편화를 막고 타입 검사기의 정적 분석 능력을 극대화하여 코드의 예측 가능성과 안정성을 높입니다[2, 3]. @@ -16,18 +16,18 @@ github_commit: "[P-Reinforce] Continuous Worker - Parse dont validate" - **기본 원칙 및 파싱 흐름**: Alexis King의 동명 아티클을 통해 널리 알려진 이 개념은 시스템의 경계(입구 및 출구)에서 입력 데이터를 한 번 파싱하는 것을 핵심으로 합니다[1, 2]. 이 파싱 단계에서 데이터의 유효성 검사와 변환이 동시에 이루어지며, 이후의 애플리케이션 흐름에서는 완전히 타입이 지정되고 검증된 데이터만을 사용하게 됩니다[1]. - **수비적 프로그래밍(Defensive Programming)의 정점**: 단순히 데이터의 유효성 여부만 확인(Validate)하고 끝내는 것이 아니라, 데이터를 더 구체적이고 신뢰할 수 있는 타입의 객체로 변환(Parse)하여 시스템 내부로 전달합니다[3]. 이는 의도하지 않은 불확실한 데이터의 유입을 원천적으로 차단하는 견고한 아키텍처적 방어막 역할을 합니다[3]. - **제어 흐름(Control flow)과 개발자 경험 향상**: 유효성 검사 로직을 시스템 경계에만 배치함으로써, 비즈니스 로직 곳곳에 검증 코드가 어지럽게 흩어지는 것을 방지할 수 있습니다[2]. 결과적으로 타입 시스템의 정적 분석에 무거운 작업을 위임하여 개발자의 신뢰를 높이고, 관리해야 할 코드의 양(Code volume)과 복잡도를 줄이는 데 크게 기여합니다[2, 4]. -- **구현 방법 및 생태계 도구**: 이 철학을 실현하기 위해 Zod와 같은 런타임 유효성 검사/파싱 라이브러리가 자주 활용됩니다[3, 5]. 구체적으로는 Zod 등을 통해 알 수 없는(Unknown) 데이터를 잘 알려진 타입으로 변환하며, 런타임 데이터에 [[Branded Types]]를 부여하여 시스템 내부로 전달하는 것이 이 철학을 완벽히 실현하는 구체적 방법론입니다[3, 5]. +- **구현 방법 및 생태계 도구**: 이 철학을 실현하기 위해 Zod와 같은 런타임 유효성 검사/파싱 라이브러리가 자주 활용됩니다[3, 5]. 구체적으로는 Zod 등을 통해 알 수 없는(Unknown) 데이터를 잘 알려진 타입으로 변환하며, 런타임 데이터에 [[Branded Types|Branded Types]]를 부여하여 시스템 내부로 전달하는 것이 이 철학을 완벽히 실현하는 구체적 방법론입니다[3, 5]. ## ⚠️ 모순 및 업데이트 (Contradictions & RL Update) - **과거 데이터와의 충돌:** 자동화 엔진에 의해 매핑된 지식으로, 추후 정밀 검증 필요. - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Branded Types]], [[Zod]], [[Defensive Programming]], [[Static Analysis]], [[Structural Typing]] -- **Projects/Contexts:** [[API Boundary Handling]], [[State Management]] +- **Related Topics:** [[Branded Types|Branded Types]], [[Zod|Zod]], Defensive Programming, [[정적 분석(Static Analysis)|Static Analysis]], [[Structural Typing|Structural Typing]] +- **Projects/Contexts:** API Boundary Handling, [[상태 관리(State Management)|State Management]] - **Contradictions/Notes:** 소스 내에서 이 철학에 대한 상반된 주장이나 모순은 발견되지 않습니다. 오히려 상태 관리(State management) 문제나 복잡성 증가를 완화하는 TypeScript의 핵심 모범 사례 중 하나로 강력히 권장됩니다[1, 6]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/Parse, don't validate.md]] +- Raw Source: 00_Raw/2026-04-20/Parse, don't validate.md --- diff --git a/01_Archive/2026-04-20/Parse, don't validate.md b/01_Archive/2026-04-20/Parse, don't validate.md index 77006676..cb4ec0ff 100644 --- a/01_Archive/2026-04-20/Parse, don't validate.md +++ b/01_Archive/2026-04-20/Parse, don't validate.md @@ -1,4 +1,4 @@ -# [[Parse, don't validate]] +# [[Parse, don't validate|Parse, don't validate]] ## 📌 Brief Summary 'Parse, don't validate(검증하지 말고 파싱하라)'는 프로그램의 경계에서 타입이 없거나 느슨한 데이터를 잘 정의된 타입의 데이터로 변환하는 소프트웨어 설계 철학입니다[1]. 코드 전반에 걸쳐 데이터의 유효성을 반복적으로 검사하는 대신, 시스템 진입점에서 단 한 번 파싱하여 안전한 타입으로 만듭니다[1]. 이를 통해 유효성 검사 로직의 파편화를 막고 타입 검사기의 정적 분석 능력을 극대화하여 코드의 예측 가능성과 안정성을 높입니다[2, 3]. @@ -7,11 +7,11 @@ - **기본 원칙 및 파싱 흐름**: Alexis King의 동명 아티클을 통해 널리 알려진 이 개념은 시스템의 경계(입구 및 출구)에서 입력 데이터를 한 번 파싱하는 것을 핵심으로 합니다[1, 2]. 이 파싱 단계에서 데이터의 유효성 검사와 변환이 동시에 이루어지며, 이후의 애플리케이션 흐름에서는 완전히 타입이 지정되고 검증된 데이터만을 사용하게 됩니다[1]. - **수비적 프로그래밍(Defensive Programming)의 정점**: 단순히 데이터의 유효성 여부만 확인(Validate)하고 끝내는 것이 아니라, 데이터를 더 구체적이고 신뢰할 수 있는 타입의 객체로 변환(Parse)하여 시스템 내부로 전달합니다[3]. 이는 의도하지 않은 불확실한 데이터의 유입을 원천적으로 차단하는 견고한 아키텍처적 방어막 역할을 합니다[3]. - **제어 흐름(Control flow)과 개발자 경험 향상**: 유효성 검사 로직을 시스템 경계에만 배치함으로써, 비즈니스 로직 곳곳에 검증 코드가 어지럽게 흩어지는 것을 방지할 수 있습니다[2]. 결과적으로 타입 시스템의 정적 분석에 무거운 작업을 위임하여 개발자의 신뢰를 높이고, 관리해야 할 코드의 양(Code volume)과 복잡도를 줄이는 데 크게 기여합니다[2, 4]. -- **구현 방법 및 생태계 도구**: 이 철학을 실현하기 위해 Zod와 같은 런타임 유효성 검사/파싱 라이브러리가 자주 활용됩니다[3, 5]. 구체적으로는 Zod 등을 통해 알 수 없는(Unknown) 데이터를 잘 알려진 타입으로 변환하며, 런타임 데이터에 [[Branded Types]]를 부여하여 시스템 내부로 전달하는 것이 이 철학을 완벽히 실현하는 구체적 방법론입니다[3, 5]. +- **구현 방법 및 생태계 도구**: 이 철학을 실현하기 위해 Zod와 같은 런타임 유효성 검사/파싱 라이브러리가 자주 활용됩니다[3, 5]. 구체적으로는 Zod 등을 통해 알 수 없는(Unknown) 데이터를 잘 알려진 타입으로 변환하며, 런타임 데이터에 [[Branded Types|Branded Types]]를 부여하여 시스템 내부로 전달하는 것이 이 철학을 완벽히 실현하는 구체적 방법론입니다[3, 5]. ## 🔗 Knowledge Connections -- **Related Topics:** [[Branded Types]], [[Zod]], [[Defensive Programming]], [[Static Analysis]], [[Structural Typing]] -- **Projects/Contexts:** [[API Boundary Handling]], [[State Management]] +- **Related Topics:** [[Branded Types|Branded Types]], [[Zod|Zod]], Defensive Programming, [[정적 분석(Static Analysis)|Static Analysis]], [[Structural Typing|Structural Typing]] +- **Projects/Contexts:** API Boundary Handling, [[상태 관리(State Management)|State Management]] - **Contradictions/Notes:** 소스 내에서 이 철학에 대한 상반된 주장이나 모순은 발견되지 않습니다. 오히려 상태 관리(State management) 문제나 복잡성 증가를 완화하는 TypeScript의 핵심 모범 사례 중 하나로 강력히 권장됩니다[1, 6]. --- diff --git a/01_Archive/2026-04-20/Parser.md b/01_Archive/2026-04-20/Parser.md index 19fbccb6..1103ebde 100644 --- a/01_Archive/2026-04-20/Parser.md +++ b/01_Archive/2026-04-20/Parser.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-CODING-003 -category: "[[10_Wiki/💡 Topics/Coding]]" +category: "10_Wiki/💡 Topics/Coding" confidence_score: 0.97 tags: [coding, scaling, compiler, parser, typescript] last_reinforced: 2026-04-20 github_commit: "batch-reinforce-07" --- -# [[Parser (구문 분석기)]] +# Parser (구문 분석기) ## 📌 한 줄 통찰 (The Karpathy Summary) > 텍스트의 나열을 의미 있는 구조(Tree)로 변환하여, 기계가 코드의 문법과 의도를 이해하게 만드는 지적 번역기. @@ -24,6 +24,6 @@ github_commit: "batch-reinforce-07" - **정책 변화:** 기술적 정확성(w1)을 위해 최신 파싱 알고리즘 가중치 반영 및 코딩 표준 연결. ## 🔗 지식 연결 (Graph) -- **Parent:** [[10_Wiki/💡 Topics/Coding]] -- **Related:** [[AST_Traversal]], [[CST]], [[TypeScript-Architecture]] -- **Raw Source:** [[00_Raw/2026-04-20/TypeScript-Compiler-Architecture.md]] +- **Parent:** 10_Wiki/💡 Topics/Coding +- **Related:** [[AST_Traversal|AST_Traversal]], [[CST|CST]], TypeScript-Architecture +- **Raw Source:** 00_Raw/2026-04-20/TypeScript-Compiler-Architecture.md diff --git a/01_Archive/2026-04-20/Pedestrian-Modeling.md b/01_Archive/2026-04-20/Pedestrian-Modeling.md index b7b84f33..a1874af7 100644 --- a/01_Archive/2026-04-20/Pedestrian-Modeling.md +++ b/01_Archive/2026-04-20/Pedestrian-Modeling.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-9FF9E8 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Pedestrian-Modeling" --- -# [[Pedestrian-Modeling]] +# [[Pedestrian-Modeling|Pedestrian-Modeling]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Pedestrian-Modeling" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Pedestrian-Modeling.md]] +- Raw Source: 00_Raw/2026-04-20/Pedestrian-Modeling.md --- diff --git a/01_Archive/2026-04-20/Perceptual-Motor-Skills.md b/01_Archive/2026-04-20/Perceptual-Motor-Skills.md index b2ec6da6..9fbfb6fe 100644 --- a/01_Archive/2026-04-20/Perceptual-Motor-Skills.md +++ b/01_Archive/2026-04-20/Perceptual-Motor-Skills.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-49DAC5 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Perceptual-Motor-Skills" --- -# [[Perceptual-Motor-Skills]] +# [[Perceptual-Motor-Skills|Perceptual-Motor-Skills]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Perceptual-Motor-Skills" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Perceptual-Motor-Skills.md]] +- Raw Source: 00_Raw/2026-04-20/Perceptual-Motor-Skills.md --- diff --git a/01_Archive/2026-04-20/Performance Management Systems.md b/01_Archive/2026-04-20/Performance Management Systems.md index 6b037f43..2306af04 100644 --- a/01_Archive/2026-04-20/Performance Management Systems.md +++ b/01_Archive/2026-04-20/Performance Management Systems.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-AE7AD2 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Performance Management Systems" --- -# [[Performance Management Systems]] +# [[Performance Management Systems|Performance Management Systems]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Performance Management Systems ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Performance Management Systems.md]] +- Raw Source: 00_Raw/2026-04-20/Performance Management Systems.md --- diff --git a/01_Archive/2026-04-20/Performance Panel.md b/01_Archive/2026-04-20/Performance Panel.md index 1889102c..f05e092d 100644 --- a/01_Archive/2026-04-20/Performance Panel.md +++ b/01_Archive/2026-04-20/Performance Panel.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-91C413 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Performance Panel" --- -# [[Performance Panel]] +# [[Performance Panel|Performance Panel]] ## 📌 한 줄 통찰 (The Karpathy Summary) > Performance Panel(성능 패널)은 웹 페이지의 런타임 및 로드 성능을 분석하고 디버깅하기 위해 사용되는 Chrome DevTools의 핵심 진단 도구입니다 [1, 2]. 이 패널은 페이지의 렌더링, 자바스크립트 실행, 네트워크 활동 및 프레임 속도(FPS) 등을 기록하여 플레임 차트 등의 형태로 시각화합니다 [3-6]. 개발자는 이를 통해 메인 스레드를 차단하는 긴 작업(Long tasks)이나 상호작용 지연 등 성능 병목 현상의 원인을 파악하고 웹 성능을 최적화할 수 있습니다 [2, 4, 7]. @@ -36,11 +36,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Performance Panel" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Chrome DevTools]], [[Core Web Vitals]], [[Interaction to Next Paint (INP)]], [[Flame Chart]], [[Main Thread]] -- **Projects/Contexts:** [[Web Performance Debugging]], [[Performance Profiling]] +- **Related Topics:** [[Chrome DevTools|Chrome DevTools]], [[Core Web Vitals|Core Web Vitals]], [[Interaction to Next Paint (INP)|Interaction to Next Paint (INP)]], [[Flame Chart|Flame Chart]], [[Main Thread|Main Thread]] +- **Projects/Contexts:** Web Performance Debugging, Performance Profiling - **Contradictions/Notes:** Performance 패널의 로컬 측정값은 측정 시점의 로컬 디바이스 및 네트워크 환경의 영향을 크게 받으므로, 실제 전 세계 사용자의 경험을 정확히 파악하려면 CrUX(Chrome User Experience Report) 필드 데이터의 환경 설정에 맞춰 DevTools 환경을 구성하고 비교 분석하는 것이 중요합니다 [24, 25]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Performance Panel.md]] +- Raw Source: 00_Raw/2026-04-20/Performance Panel.md --- diff --git a/01_Archive/2026-04-20/Performance Psychology.md b/01_Archive/2026-04-20/Performance Psychology.md index 083c8146..15710cdb 100644 --- a/01_Archive/2026-04-20/Performance Psychology.md +++ b/01_Archive/2026-04-20/Performance Psychology.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-D603B6 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Performance Psychology" --- -# [[Performance Psychology]] +# [[Performance Psychology|Performance Psychology]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Performance Psychology" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Performance Psychology.md]] +- Raw Source: 00_Raw/2026-04-20/Performance Psychology.md --- diff --git a/01_Archive/2026-04-20/Periodization-Theory.md b/01_Archive/2026-04-20/Periodization-Theory.md index 981d727a..64a44f5d 100644 --- a/01_Archive/2026-04-20/Periodization-Theory.md +++ b/01_Archive/2026-04-20/Periodization-Theory.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-02B992 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Periodization-Theory" --- -# [[Periodization-Theory]] +# [[Periodization-Theory|Periodization-Theory]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Periodization-Theory" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Periodization-Theory.md]] +- Raw Source: 00_Raw/2026-04-20/Periodization-Theory.md --- diff --git a/01_Archive/2026-04-20/Perlin Noise.md b/01_Archive/2026-04-20/Perlin Noise.md index ef50da18..e09f7883 100644 --- a/01_Archive/2026-04-20/Perlin Noise.md +++ b/01_Archive/2026-04-20/Perlin Noise.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-0374D8 -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Perlin Noise" --- -# [[Perlin Noise]] +# [[Perlin Noise|Perlin Noise]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Perlin Noise" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Perlin Noise.md]] +- Raw Source: 00_Raw/2026-04-20/Perlin Noise.md --- diff --git a/01_Archive/2026-04-20/Personalization-Engines.md b/01_Archive/2026-04-20/Personalization-Engines.md index a4de562a..27a05998 100644 --- a/01_Archive/2026-04-20/Personalization-Engines.md +++ b/01_Archive/2026-04-20/Personalization-Engines.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-A74003 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Personalization-Engines" --- -# [[Personalization-Engines]] +# [[Personalization-Engines|Personalization-Engines]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Personalization-Engines" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Personalization-Engines.md]] +- Raw Source: 00_Raw/2026-04-20/Personalization-Engines.md --- diff --git a/01_Archive/2026-04-20/Persuasive Games.md b/01_Archive/2026-04-20/Persuasive Games.md index 904a6bd2..6ff0ba4c 100644 --- a/01_Archive/2026-04-20/Persuasive Games.md +++ b/01_Archive/2026-04-20/Persuasive Games.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-11DC29 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Persuasive Games" --- -# [[Persuasive Games]] +# [[Persuasive Games|Persuasive Games]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Persuasive Games" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Persuasive Games.md]] +- Raw Source: 00_Raw/2026-04-20/Persuasive Games.md --- diff --git a/01_Archive/2026-04-20/Phase Transition (위상 변이).md b/01_Archive/2026-04-20/Phase Transition (위상 변이).md index b9b33041..bf449440 100644 --- a/01_Archive/2026-04-20/Phase Transition (위상 변이).md +++ b/01_Archive/2026-04-20/Phase Transition (위상 변이).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-F09281 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Phase Transition (위상 변이)" --- -# [[Phase Transition (위상 변이)]] +# [[Phase Transition (위상 변이)|Phase Transition (위상 변이)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Phase Transition (위상 변 ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Phase Transition (위상 변이).md]] +- Raw Source: 00_Raw/2026-04-20/Phase Transition (위상 변이).md --- diff --git a/01_Archive/2026-04-20/Phyllotaxis-Modeling.md b/01_Archive/2026-04-20/Phyllotaxis-Modeling.md index c82e6797..92232682 100644 --- a/01_Archive/2026-04-20/Phyllotaxis-Modeling.md +++ b/01_Archive/2026-04-20/Phyllotaxis-Modeling.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-AAE034 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Phyllotaxis-Modeling" --- -# [[Phyllotaxis-Modeling]] +# [[Phyllotaxis-Modeling|Phyllotaxis-Modeling]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Phyllotaxis-Modeling" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Phyllotaxis-Modeling.md]] +- Raw Source: 00_Raw/2026-04-20/Phyllotaxis-Modeling.md --- diff --git a/01_Archive/2026-04-20/Physics Engine Integration.md b/01_Archive/2026-04-20/Physics Engine Integration.md index 940fc8e4..644f147f 100644 --- a/01_Archive/2026-04-20/Physics Engine Integration.md +++ b/01_Archive/2026-04-20/Physics Engine Integration.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-DE2C95 -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Physics Engine Integration" --- -# [[Physics Engine Integration]] +# [[Physics Engine Integration|Physics Engine Integration]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Physics Engine Integration" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Physics Engine Integration.md]] +- Raw Source: 00_Raw/2026-04-20/Physics Engine Integration.md --- diff --git a/01_Archive/2026-04-20/Physics-Based-Simulation.md b/01_Archive/2026-04-20/Physics-Based-Simulation.md index cd3b7c18..46dd2a94 100644 --- a/01_Archive/2026-04-20/Physics-Based-Simulation.md +++ b/01_Archive/2026-04-20/Physics-Based-Simulation.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-1E824D -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Physics-Based-Simulation" --- -# [[Physics-Based-Simulation]] +# [[Physics-Based-Simulation|Physics-Based-Simulation]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Physics-Based-Simulation" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Physics-Based-Simulation.md]] +- Raw Source: 00_Raw/2026-04-20/Physics-Based-Simulation.md --- diff --git a/01_Archive/2026-04-20/Platform Economics.md b/01_Archive/2026-04-20/Platform Economics.md index bf00dc88..047187be 100644 --- a/01_Archive/2026-04-20/Platform Economics.md +++ b/01_Archive/2026-04-20/Platform Economics.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-2B537F -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Platform Economics" --- -# [[Platform Economics]] +# [[Platform Economics|Platform Economics]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Platform Economics" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Platform Economics.md]] +- Raw Source: 00_Raw/2026-04-20/Platform Economics.md --- diff --git a/01_Archive/2026-04-20/Play-to-Earn (P2E) Economies.md b/01_Archive/2026-04-20/Play-to-Earn (P2E) Economies.md index d532c567..8552bba1 100644 --- a/01_Archive/2026-04-20/Play-to-Earn (P2E) Economies.md +++ b/01_Archive/2026-04-20/Play-to-Earn (P2E) Economies.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-43C745 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Play-to-Earn (P2E) Economies" --- -# [[Play-to-Earn (P2E) Economies]] +# [[Play-to-Earn (P2E) Economies|Play-to-Earn (P2E) Economies]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Play-to-Earn (P2E) Economies" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Play-to-Earn (P2E) Economies.md]] +- Raw Source: 00_Raw/2026-04-20/Play-to-Earn (P2E) Economies.md --- diff --git a/01_Archive/2026-04-20/Player Agency.md b/01_Archive/2026-04-20/Player Agency.md index 380ee101..03781f70 100644 --- a/01_Archive/2026-04-20/Player Agency.md +++ b/01_Archive/2026-04-20/Player Agency.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-83E12E -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Player Agency" --- -# [[Player Agency]] +# [[Player Agency|Player Agency]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Player Agency" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Player Agency.md]] +- Raw Source: 00_Raw/2026-04-20/Player Agency.md --- diff --git a/01_Archive/2026-04-20/Player-Agency.md b/01_Archive/2026-04-20/Player-Agency.md index 187ecedf..d571b321 100644 --- a/01_Archive/2026-04-20/Player-Agency.md +++ b/01_Archive/2026-04-20/Player-Agency.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-058473 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Player-Agency" --- -# [[Player-Agency]] +# [[Player-Agency|Player-Agency]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Player-Agency" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Player-Agency.md]] +- Raw Source: 00_Raw/2026-04-20/Player-Agency.md --- diff --git a/01_Archive/2026-04-20/Player-Autonomy.md b/01_Archive/2026-04-20/Player-Autonomy.md index 34cff024..93ee4cb3 100644 --- a/01_Archive/2026-04-20/Player-Autonomy.md +++ b/01_Archive/2026-04-20/Player-Autonomy.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-85AECB -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Player-Autonomy" --- -# [[Player-Autonomy]] +# [[Player-Autonomy|Player-Autonomy]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Player-Autonomy" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Player-Autonomy.md]] +- Raw Source: 00_Raw/2026-04-20/Player-Autonomy.md --- diff --git a/01_Archive/2026-04-20/Pointer Compression.md b/01_Archive/2026-04-20/Pointer Compression.md index 98d05682..b00d6841 100644 --- a/01_Archive/2026-04-20/Pointer Compression.md +++ b/01_Archive/2026-04-20/Pointer Compression.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-DEB938 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Pointer Compression" --- -# [[Pointer Compression]] +# [[Pointer Compression|Pointer Compression]] ## 📌 한 줄 통찰 (The Karpathy Summary) > Pointer Compression(포인터 압축)은 64비트 플랫폼에서 V8 엔진의 메모리 오버헤드를 줄이기 위해 포인터를 베이스 주소로부터의 32비트 오프셋(offset)으로 저장하는 기술입니다 [1]. 이 기술은 V8 힙 크기를 최대 40%까지 줄이고 CPU 및 가비지 컬렉션(GC) 성능을 5~10% 향상시키는 장점이 있습니다 [2]. 하지만 포인터 압축을 활성화하면 V8 힙의 최대 크기가 4GB로 제한된다는 주요한 단점이 수반됩니다 [1, 3]. @@ -30,11 +30,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Pointer Compression" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[V8 Memory Cage]], [[Garbage Collection (GC)]], [[Out of Memory (OOM)]], [[V8 Heap]] -- **Projects/Contexts:** [[V8 Engine]], [[Electron]], [[Node.js]], [[Chromium]] +- **Related Topics:** [[V8 Memory Cage|V8 Memory Cage]], [[Garbage Collection (GC)|Garbage Collection (GC)]], Out of Memory (OOM), [[V8 힙(Heap)|V8 Heap]] +- **Projects/Contexts:** [[V8 Engine|V8 Engine]], [[Electron|Electron]], [[Node.js|Node.js]], [[Chromium|Chromium]] - **Contradictions/Notes:** 소스에 따르면 포인터 압축은 메모리 사용량을 대폭 줄이고 CPU 효율을 높이지만, 그 대가로 힙 크기를 4GB로 강제 제한하여 메모리 집약적인 작업에는 불리할 수 있다는 명확한 트레이드오프(trade-off)를 갖습니다 [2-4]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Pointer Compression.md]] +- Raw Source: 00_Raw/2026-04-20/Pointer Compression.md --- diff --git a/01_Archive/2026-04-20/Pointer Poisoning.md b/01_Archive/2026-04-20/Pointer Poisoning.md index fdf3d3d2..56b1a0fb 100644 --- a/01_Archive/2026-04-20/Pointer Poisoning.md +++ b/01_Archive/2026-04-20/Pointer Poisoning.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-F1EA31 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Pointer Poisoning" --- -# [[Pointer Poisoning]] +# [[Pointer Poisoning|Pointer Poisoning]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 포인터 포이즈닝(Pointer Poisoning)은 스펙터(Spectre) 및 멜트다운(Meltdown) 취약점 공격을 방어하기 위해 웹킷(WebKit)과 같은 브라우저 엔진에 도입된 브랜치리스(Branchless) 보안 검사 기법입니다 [1-3]. 컴파일 타임에 포인터 필드에 무작위의 고유한 포이즌 값을 할당하며, 잘못된 값으로 포이즌을 해제(unpoisoning)할 경우 매핑되지 않은 포인터가 되도록 유도하여 보안을 유지합니다 [3, 4]. 이를 통해 타입 혼동(Type Confusion)을 막고 임의의 메모리 읽기나 원격 코드 실행 공격을 방지합니다 [4]. @@ -23,11 +23,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Pointer Poisoning" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Spectre]], [[Meltdown]], [[Branchless Security Checks]], [[Speculative Execution]], [[Type Confusion]] -- **Projects/Contexts:** [[WebKit]], [[JavaScriptCore]] +- **Related Topics:** [[Spectre|Spectre]], [[Meltdown|Meltdown]], [[Branchless Security Checks|Branchless Security Checks]], [[Speculative Execution|Speculative Execution]], Type Confusion +- **Projects/Contexts:** [[WebKit|WebKit]], [[JavaScriptCore|JavaScriptCore]] - **Contradictions/Notes:** 소스 내에서 명시적인 모순은 발견되지 않으나, 포인터 포이즈닝 기술이 보안성을 크게 향상시키는 대신 자바스크립트 엔진의 마이크로 레이턴시를 소폭 증가시킨다는 성능상의 트레이드오프가 존재함이 지적됩니다 [4, 7]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Pointer Poisoning.md]] +- Raw Source: 00_Raw/2026-04-20/Pointer Poisoning.md --- diff --git a/01_Archive/2026-04-20/Policy.md b/01_Archive/2026-04-20/Policy.md deleted file mode 100644 index 1fe1baa5..00000000 --- a/01_Archive/2026-04-20/Policy.md +++ /dev/null @@ -1,3 +0,0 @@ -# P-Reinforce RL Policy - -- Initial weights: w1=0.4, w2=0.3, w3=0.3 \ No newline at end of file diff --git a/01_Archive/2026-04-20/PolicyIQ.md b/01_Archive/2026-04-20/PolicyIQ.md index 1ec5711d..c693ddcd 100644 --- a/01_Archive/2026-04-20/PolicyIQ.md +++ b/01_Archive/2026-04-20/PolicyIQ.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-B7D200 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - PolicyIQ" --- -# [[PolicyIQ]] +# [[PolicyIQ|PolicyIQ]] ## 📌 한 줄 통찰 (The Karpathy Summary) > PolicyIQ는 AI 네이티브 SAST(정적 애플리케이션 보안 테스트) 플랫폼인 Corgea에서 제공하는 기능입니다 [1, 2]. 팀이 자연어를 사용하여 비즈니스 및 환경적 맥락을 시스템에 제공할 수 있도록 지원하며, 스캐너는 이를 활용하여 취약점 탐지 정확도를 높이고 코드 수정안(fix) 생성 능력을 향상시킵니다 [2]. @@ -22,11 +22,11 @@ github_commit: "[P-Reinforce] Continuous Worker - PolicyIQ" - **정책 변화:** AI 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Corgea]], [[SAST]], [[Large Language Models (LLMs)]] -- **Projects/Contexts:** [[Corgea AI-native SAST Platform]] +- **Related Topics:** [[Corgea|Corgea]], [[SAST|SAST]], Large Language Models (LLMs) +- **Projects/Contexts:** Corgea AI-native SAST Platform - **Contradictions/Notes:** PolicyIQ의 심층적인 기술 작동 원리나 세부적인 설정 방법 등은 소스에 관련 정보가 부족합니다. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/PolicyIQ.md]] +- Raw Source: 00_Raw/2026-04-20/PolicyIQ.md --- diff --git a/01_Archive/2026-04-20/Political-Philosophy-in-Games.md b/01_Archive/2026-04-20/Political-Philosophy-in-Games.md index 5ededdfb..c25d67fe 100644 --- a/01_Archive/2026-04-20/Political-Philosophy-in-Games.md +++ b/01_Archive/2026-04-20/Political-Philosophy-in-Games.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-9F478E -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Political-Philosophy-in-Games" --- -# [[Political-Philosophy-in-Games]] +# [[Political-Philosophy-in-Games|Political-Philosophy-in-Games]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Political-Philosophy-in-Games" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Political-Philosophy-in-Games.md]] +- Raw Source: 00_Raw/2026-04-20/Political-Philosophy-in-Games.md --- diff --git a/01_Archive/2026-04-20/Positive Psychology.md b/01_Archive/2026-04-20/Positive Psychology.md index 1853d339..8f049336 100644 --- a/01_Archive/2026-04-20/Positive Psychology.md +++ b/01_Archive/2026-04-20/Positive Psychology.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-52AEE2 -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Positive Psychology" --- -# [[Positive Psychology]] +# [[Positive Psychology|Positive Psychology]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Positive Psychology" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Positive Psychology.md]] +- Raw Source: 00_Raw/2026-04-20/Positive Psychology.md --- diff --git a/01_Archive/2026-04-20/Positive-Education.md b/01_Archive/2026-04-20/Positive-Education.md index 12189f01..b8e2619a 100644 --- a/01_Archive/2026-04-20/Positive-Education.md +++ b/01_Archive/2026-04-20/Positive-Education.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-E6C93F -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Positive-Education" --- -# [[Positive-Education]] +# [[Positive-Education|Positive-Education]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Positive-Education" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Positive-Education.md]] +- Raw Source: 00_Raw/2026-04-20/Positive-Education.md --- diff --git a/01_Archive/2026-04-20/Positive-Psychology.md b/01_Archive/2026-04-20/Positive-Psychology.md index c6cc997d..a7418464 100644 --- a/01_Archive/2026-04-20/Positive-Psychology.md +++ b/01_Archive/2026-04-20/Positive-Psychology.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-88BB17 -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Positive-Psychology" --- -# [[Positive-Psychology]] +# [[Positive-Psychology|Positive-Psychology]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Positive-Psychology" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Positive-Psychology.md]] +- Raw Source: 00_Raw/2026-04-20/Positive-Psychology.md --- diff --git a/01_Archive/2026-04-20/Post-Acute-Care-Models.md b/01_Archive/2026-04-20/Post-Acute-Care-Models.md index ff0a04fd..10503c64 100644 --- a/01_Archive/2026-04-20/Post-Acute-Care-Models.md +++ b/01_Archive/2026-04-20/Post-Acute-Care-Models.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-D22D50 -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Post-Acute-Care-Models" --- -# [[Post-Acute-Care-Models]] +# [[Post-Acute-Care-Models|Post-Acute-Care-Models]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Post-Acute-Care-Models" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Post-Acute-Care-Models.md]] +- Raw Source: 00_Raw/2026-04-20/Post-Acute-Care-Models.md --- diff --git a/01_Archive/2026-04-20/Post-Apocalyptic Fiction.md b/01_Archive/2026-04-20/Post-Apocalyptic Fiction.md index 744780a8..760c2b49 100644 --- a/01_Archive/2026-04-20/Post-Apocalyptic Fiction.md +++ b/01_Archive/2026-04-20/Post-Apocalyptic Fiction.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-593061 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Post-Apocalyptic Fiction" --- -# [[Post-Apocalyptic Fiction]] +# [[Post-Apocalyptic Fiction|Post-Apocalyptic Fiction]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Post-Apocalyptic Fiction" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Post-Apocalyptic Fiction.md]] +- Raw Source: 00_Raw/2026-04-20/Post-Apocalyptic Fiction.md --- diff --git a/01_Archive/2026-04-20/Post-Modernist Literature in Gaming.md b/01_Archive/2026-04-20/Post-Modernist Literature in Gaming.md index dd31bbc1..5e380ad8 100644 --- a/01_Archive/2026-04-20/Post-Modernist Literature in Gaming.md +++ b/01_Archive/2026-04-20/Post-Modernist Literature in Gaming.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-BC9437 -category: "[[10_Wiki/💡 Topics/Game Design]]" +category: "10_Wiki/💡 Topics/Game Design" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Post-Modernist Literature in Gaming" --- -# [[Post-Modernist Literature in Gaming]] +# [[Post-Modernist Literature in Gaming|Post-Modernist Literature in Gaming]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Post-Modernist Literature in G ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Post-Modernist Literature in Gaming.md]] +- Raw Source: 00_Raw/2026-04-20/Post-Modernist Literature in Gaming.md --- diff --git a/01_Archive/2026-04-20/Post-Surgical-Orthopedic-Recovery.md b/01_Archive/2026-04-20/Post-Surgical-Orthopedic-Recovery.md index 6ca21e76..074c5b92 100644 --- a/01_Archive/2026-04-20/Post-Surgical-Orthopedic-Recovery.md +++ b/01_Archive/2026-04-20/Post-Surgical-Orthopedic-Recovery.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-161900 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Post-Surgical-Orthopedic-Recovery" --- -# [[Post-Surgical-Orthopedic-Recovery]] +# [[Post-Surgical-Orthopedic-Recovery|Post-Surgical-Orthopedic-Recovery]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Post-Surgical-Orthopedic-Recov ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Post-Surgical-Orthopedic-Recovery.md]] +- Raw Source: 00_Raw/2026-04-20/Post-Surgical-Orthopedic-Recovery.md --- diff --git a/01_Archive/2026-04-20/Post-humanism.md b/01_Archive/2026-04-20/Post-humanism.md index 4e69ecb2..56ddd01f 100644 --- a/01_Archive/2026-04-20/Post-humanism.md +++ b/01_Archive/2026-04-20/Post-humanism.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-1C09D2 -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Post-humanism" --- -# [[Post-humanism]] +# [[Post-humanism|Post-humanism]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Post-humanism" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Post-humanism.md]] +- Raw Source: 00_Raw/2026-04-20/Post-humanism.md --- diff --git a/01_Archive/2026-04-20/Post-structuralism.md b/01_Archive/2026-04-20/Post-structuralism.md index 5afc10e2..6c27e0cf 100644 --- a/01_Archive/2026-04-20/Post-structuralism.md +++ b/01_Archive/2026-04-20/Post-structuralism.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-49AC0F -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Post-structuralism" --- -# [[Post-structuralism]] +# [[Post-structuralism|Post-structuralism]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Post-structuralism" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Post-structuralism.md]] +- Raw Source: 00_Raw/2026-04-20/Post-structuralism.md --- diff --git a/01_Archive/2026-04-20/Precision Medicine Training.md b/01_Archive/2026-04-20/Precision Medicine Training.md index 4b7b1fd1..eaa25bae 100644 --- a/01_Archive/2026-04-20/Precision Medicine Training.md +++ b/01_Archive/2026-04-20/Precision Medicine Training.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-95109A -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Precision Medicine Training" --- -# [[Precision Medicine Training]] +# [[Precision Medicine Training|Precision Medicine Training]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Precision Medicine Training" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Precision Medicine Training.md]] +- Raw Source: 00_Raw/2026-04-20/Precision Medicine Training.md --- diff --git a/01_Archive/2026-04-20/Predictive Maintenance (PdM).md b/01_Archive/2026-04-20/Predictive Maintenance (PdM).md index 1f069a3a..49a56b84 100644 --- a/01_Archive/2026-04-20/Predictive Maintenance (PdM).md +++ b/01_Archive/2026-04-20/Predictive Maintenance (PdM).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-E3A437 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Predictive Maintenance (PdM)" --- -# [[Predictive Maintenance (PdM)]] +# [[Predictive Maintenance (PdM)|Predictive Maintenance (PdM)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Predictive Maintenance (PdM)" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Predictive Maintenance (PdM).md]] +- Raw Source: 00_Raw/2026-04-20/Predictive Maintenance (PdM).md --- diff --git a/01_Archive/2026-04-20/Predictive-Modeling.md b/01_Archive/2026-04-20/Predictive-Modeling.md index 4fe2ef56..1a29559a 100644 --- a/01_Archive/2026-04-20/Predictive-Modeling.md +++ b/01_Archive/2026-04-20/Predictive-Modeling.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-2ADF8A -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Predictive-Modeling" --- -# [[Predictive-Modeling]] +# [[Predictive-Modeling|Predictive-Modeling]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Predictive-Modeling" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Predictive-Modeling.md]] +- Raw Source: 00_Raw/2026-04-20/Predictive-Modeling.md --- diff --git a/01_Archive/2026-04-20/Predictive-Urban-Modeling.md b/01_Archive/2026-04-20/Predictive-Urban-Modeling.md index 5c59f978..cb9beb41 100644 --- a/01_Archive/2026-04-20/Predictive-Urban-Modeling.md +++ b/01_Archive/2026-04-20/Predictive-Urban-Modeling.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-FBB603 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Predictive-Urban-Modeling" --- -# [[Predictive-Urban-Modeling]] +# [[Predictive-Urban-Modeling|Predictive-Urban-Modeling]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Predictive-Urban-Modeling" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Predictive-Urban-Modeling.md]] +- Raw Source: 00_Raw/2026-04-20/Predictive-Urban-Modeling.md --- diff --git a/01_Archive/2026-04-20/Predictive_Maintenance.md b/01_Archive/2026-04-20/Predictive_Maintenance.md index 45986235..7f276c20 100644 --- a/01_Archive/2026-04-20/Predictive_Maintenance.md +++ b/01_Archive/2026-04-20/Predictive_Maintenance.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-GRAPHICS-004 -category: "[[10_Wiki/💡 Topics/Graphics]]" +category: "10_Wiki/💡 Topics/Graphics" confidence_score: 0.93 tags: [graphics, digital-twin, maintenance, ai] last_reinforced: 2026-04-20 github_commit: "batch-reinforce-05" --- -# [[Predictive Maintenance (PdM)]] +# [[Predictive Maintenance (PdM)|Predictive Maintenance (PdM)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 과거의 고장 패턴을 학습하여 미래의 이상 징후를 사전에 포착함으로써 시스템 가동 중단을 원천 차단하는 지능형 유지보수 체계. @@ -24,6 +24,6 @@ github_commit: "batch-reinforce-05" - **정책 변화:** 성능 가중치(w1) 관점에서 가동 시간(Uptime) 극대화를 위한 핵심 전략으로 배치. ## 🔗 지식 연결 (Graph) -- **Parent:** [[10_Wiki/💡 Topics/Graphics]] -- **Related:** [[Digital_Twin]], [[Anomaly-Detection]], [[IoT]] -- **Raw Source:** [[00_Raw/2026-04-20/Predictive Maintenance (PdM).md]] +- **Parent:** 10_Wiki/💡 Topics/Graphics +- **Related:** [[Digital_Twin|Digital_Twin]], [[Anomaly-Detection|Anomaly-Detection]], [[IoT|IoT]] +- **Raw Source:** 00_Raw/2026-04-20/Predictive Maintenance (PdM).md diff --git a/01_Archive/2026-04-20/Prefrontal Cortex Dysfunction.md b/01_Archive/2026-04-20/Prefrontal Cortex Dysfunction.md index 4c94c5d7..a9c0c106 100644 --- a/01_Archive/2026-04-20/Prefrontal Cortex Dysfunction.md +++ b/01_Archive/2026-04-20/Prefrontal Cortex Dysfunction.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-A5833A -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Prefrontal Cortex Dysfunction" --- -# [[Prefrontal Cortex Dysfunction]] +# [[Prefrontal Cortex Dysfunction|Prefrontal Cortex Dysfunction]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Prefrontal Cortex Dysfunction" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Prefrontal Cortex Dysfunction.md]] +- Raw Source: 00_Raw/2026-04-20/Prefrontal Cortex Dysfunction.md --- diff --git a/01_Archive/2026-04-20/Prefrontal-Cortex-Dysfunction.md b/01_Archive/2026-04-20/Prefrontal-Cortex-Dysfunction.md index cb016890..b0b32f9d 100644 --- a/01_Archive/2026-04-20/Prefrontal-Cortex-Dysfunction.md +++ b/01_Archive/2026-04-20/Prefrontal-Cortex-Dysfunction.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-832BDA -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Prefrontal-Cortex-Dysfunction" --- -# [[Prefrontal-Cortex-Dysfunction]] +# [[Prefrontal-Cortex-Dysfunction|Prefrontal-Cortex-Dysfunction]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Prefrontal-Cortex-Dysfunction" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Prefrontal-Cortex-Dysfunction.md]] +- Raw Source: 00_Raw/2026-04-20/Prefrontal-Cortex-Dysfunction.md --- diff --git a/01_Archive/2026-04-20/Prettier.md b/01_Archive/2026-04-20/Prettier.md index 3160a7ab..ef377150 100644 --- a/01_Archive/2026-04-20/Prettier.md +++ b/01_Archive/2026-04-20/Prettier.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-560F29 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Prettier" --- -# [[Prettier]] +# [[Prettier|Prettier]] ## 📌 한 줄 통찰 (The Karpathy Summary) > Prettier는 개발자가 작성한 소스 코드를 일관된 스타일로 자동 변환해 주는 '의견이 반영된(opinionated)' 코드 포맷터(Formatter)입니다 [1, 2]. 코드의 로직이나 구현 방식에는 관여하지 않고, 줄 바꿈, 공백, 들여쓰기 등 시각적이고 구조적인 뷰에만 초점을 맞추어 코드를 재작성합니다 [2-4]. 이를 통해 팀원 간의 코딩 컨벤션을 통일하여 코드 리뷰 시 불필요한 스타일 논쟁을 없애고, 개발자가 코드의 핵심 로직에 더욱 집중할 수 있도록 돕습니다 [5, 6]. @@ -29,11 +29,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Prettier" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[ESLint]], [[Formatter]] -- **Projects/Contexts:** [[eslint-config-prettier]], [[eslint-plugin-prettier]], [[husky]], [[lint-staged]] +- **Related Topics:** [[ESLint|ESLint]], Formatter +- **Projects/Contexts:** [[eslint-config-prettier|eslint-config-prettier]], [[eslint-plugin-prettier|eslint-plugin-prettier]], [[Husky|husky]], [[lint-staged|lint-staged]] - **Contradictions/Notes:** ESLint와 Prettier를 통합할 때 사용하는 `eslint-plugin-prettier`에 대해 의견이 갈립니다. 소스 [17]는 해당 플러그인을 사용하면 하나의 설정 파일에서 관리할 수 있고 자동 수정(`--fix`)이 편리하여 선호한다고 밝히지만, 소스 [18]에서는 에디터에 불필요한 빨간 밑줄이 과도하게 생기고 단독 사용보다 속도가 느려진다는 이유로 공식 문서에서도 권장하지 않는다며 플러그인 사용을 배제하는 방식을 채택합니다. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/Prettier.md]] +- Raw Source: 00_Raw/2026-04-20/Prettier.md --- diff --git a/01_Archive/2026-04-20/Probabilistic-Graphical-Models.md b/01_Archive/2026-04-20/Probabilistic-Graphical-Models.md index e36341a1..3eadb8e9 100644 --- a/01_Archive/2026-04-20/Probabilistic-Graphical-Models.md +++ b/01_Archive/2026-04-20/Probabilistic-Graphical-Models.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-A9AAF3 -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Probabilistic-Graphical-Models" --- -# [[Probabilistic-Graphical-Models]] +# [[Probabilistic-Graphical-Models|Probabilistic-Graphical-Models]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Probabilistic-Graphical-Models ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Probabilistic-Graphical-Models.md]] +- Raw Source: 00_Raw/2026-04-20/Probabilistic-Graphical-Models.md --- diff --git a/01_Archive/2026-04-20/Probability Theory (Stochastic Processes).md b/01_Archive/2026-04-20/Probability Theory (Stochastic Processes).md index be602db9..0901551f 100644 --- a/01_Archive/2026-04-20/Probability Theory (Stochastic Processes).md +++ b/01_Archive/2026-04-20/Probability Theory (Stochastic Processes).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-D3B247 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Probability Theory (Stochastic Processes)" --- -# [[Probability Theory (Stochastic Processes)]] +# [[Probability Theory (Stochastic Processes)|Probability Theory (Stochastic Processes)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Probability Theory (Stochastic ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Probability Theory (Stochastic Processes).md]] +- Raw Source: 00_Raw/2026-04-20/Probability Theory (Stochastic Processes).md --- diff --git a/01_Archive/2026-04-20/Probability Theory.md b/01_Archive/2026-04-20/Probability Theory.md index c5a1d2dd..00c072e1 100644 --- a/01_Archive/2026-04-20/Probability Theory.md +++ b/01_Archive/2026-04-20/Probability Theory.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-28E2A8 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Probability Theory" --- -# [[Probability Theory]] +# [[Probability Theory|Probability Theory]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Probability Theory" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Probability Theory.md]] +- Raw Source: 00_Raw/2026-04-20/Probability Theory.md --- diff --git a/01_Archive/2026-04-20/Problem-Solving-Theory.md b/01_Archive/2026-04-20/Problem-Solving-Theory.md index 3572da86..dca43a90 100644 --- a/01_Archive/2026-04-20/Problem-Solving-Theory.md +++ b/01_Archive/2026-04-20/Problem-Solving-Theory.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-7E994F -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Problem-Solving-Theory" --- -# [[Problem-Solving-Theory]] +# [[Problem-Solving-Theory|Problem-Solving-Theory]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Problem-Solving-Theory" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Problem-Solving-Theory.md]] +- Raw Source: 00_Raw/2026-04-20/Problem-Solving-Theory.md --- diff --git a/01_Archive/2026-04-20/Procedural Content Generation (PCG) Balancing.md b/01_Archive/2026-04-20/Procedural Content Generation (PCG) Balancing.md index c1d75687..34ed976d 100644 --- a/01_Archive/2026-04-20/Procedural Content Generation (PCG) Balancing.md +++ b/01_Archive/2026-04-20/Procedural Content Generation (PCG) Balancing.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-231525 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Procedural Content Generation (PCG) Balancing" --- -# [[Procedural Content Generation (PCG) Balancing]] +# [[Procedural Content Generation (PCG) Balancing|Procedural Content Generation (PCG) Balancing]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Procedural Content Generation ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Procedural Content Generation (PCG) Balancing.md]] +- Raw Source: 00_Raw/2026-04-20/Procedural Content Generation (PCG) Balancing.md --- diff --git a/01_Archive/2026-04-20/Procedural Content Generation (PCG).md b/01_Archive/2026-04-20/Procedural Content Generation (PCG).md index bfbe8443..7d47099f 100644 --- a/01_Archive/2026-04-20/Procedural Content Generation (PCG).md +++ b/01_Archive/2026-04-20/Procedural Content Generation (PCG).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-8E0344 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Procedural Content Generation (PCG)" --- -# [[Procedural Content Generation (PCG)]] +# [[Procedural Content Generation (PCG)|Procedural Content Generation (PCG)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Procedural Content Generation ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Procedural Content Generation (PCG).md]] +- Raw Source: 00_Raw/2026-04-20/Procedural Content Generation (PCG).md --- diff --git a/01_Archive/2026-04-20/Procedural Content Generation via Machine Learning (PCGML).md b/01_Archive/2026-04-20/Procedural Content Generation via Machine Learning (PCGML).md index 241da341..85537126 100644 --- a/01_Archive/2026-04-20/Procedural Content Generation via Machine Learning (PCGML).md +++ b/01_Archive/2026-04-20/Procedural Content Generation via Machine Learning (PCGML).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-234400 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Procedural Content Generation via Machine Learning (PCGML)" --- -# [[Procedural Content Generation via Machine Learning (PCGML)]] +# [[Procedural Content Generation via Machine Learning (PCGML)|Procedural Content Generation via Machine Learning (PCGML)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Procedural Content Generation ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Procedural Content Generation via Machine Learning (PCGML).md]] +- Raw Source: 00_Raw/2026-04-20/Procedural Content Generation via Machine Learning (PCGML).md --- diff --git a/01_Archive/2026-04-20/Procedural Content Generation.md b/01_Archive/2026-04-20/Procedural Content Generation.md index f932c1a9..4ac539b1 100644 --- a/01_Archive/2026-04-20/Procedural Content Generation.md +++ b/01_Archive/2026-04-20/Procedural Content Generation.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-7E4074 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Procedural Content Generation" --- -# [[Procedural Content Generation]] +# [[Procedural Content Generation|Procedural Content Generation]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Procedural Content Generation" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Procedural Content Generation.md]] +- Raw Source: 00_Raw/2026-04-20/Procedural Content Generation.md --- diff --git a/01_Archive/2026-04-20/Procedural Rhetoric.md b/01_Archive/2026-04-20/Procedural Rhetoric.md index d0cf89af..769435c9 100644 --- a/01_Archive/2026-04-20/Procedural Rhetoric.md +++ b/01_Archive/2026-04-20/Procedural Rhetoric.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-DDAA23 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Procedural Rhetoric" --- -# [[Procedural Rhetoric]] +# [[Procedural Rhetoric|Procedural Rhetoric]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Procedural Rhetoric" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Procedural Rhetoric.md]] +- Raw Source: 00_Raw/2026-04-20/Procedural Rhetoric.md --- diff --git a/01_Archive/2026-04-20/Procedural-Animation.md b/01_Archive/2026-04-20/Procedural-Animation.md index 08e178a6..6bf64353 100644 --- a/01_Archive/2026-04-20/Procedural-Animation.md +++ b/01_Archive/2026-04-20/Procedural-Animation.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-737A68 -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Procedural-Animation" --- -# [[Procedural-Animation]] +# [[Procedural-Animation|Procedural-Animation]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Procedural-Animation" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Procedural-Animation.md]] +- Raw Source: 00_Raw/2026-04-20/Procedural-Animation.md --- diff --git a/01_Archive/2026-04-20/Procedural-Content-Generation (PCG).md b/01_Archive/2026-04-20/Procedural-Content-Generation (PCG).md index 7c9046d6..b5f29652 100644 --- a/01_Archive/2026-04-20/Procedural-Content-Generation (PCG).md +++ b/01_Archive/2026-04-20/Procedural-Content-Generation (PCG).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-D3BC93 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Procedural-Content-Generation (PCG)" --- -# [[Procedural-Content-Generation (PCG)]] +# [[Procedural-Content-Generation (PCG)|Procedural-Content-Generation (PCG)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Procedural-Content-Generation ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Procedural-Content-Generation (PCG).md]] +- Raw Source: 00_Raw/2026-04-20/Procedural-Content-Generation (PCG).md --- diff --git a/01_Archive/2026-04-20/Procedural-Content-Generation-via-Machine-Learning.md b/01_Archive/2026-04-20/Procedural-Content-Generation-via-Machine-Learning.md index 1ecca8bc..ea805d29 100644 --- a/01_Archive/2026-04-20/Procedural-Content-Generation-via-Machine-Learning.md +++ b/01_Archive/2026-04-20/Procedural-Content-Generation-via-Machine-Learning.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-1F2C54 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Procedural-Content-Generation-via-Machine-Learning" --- -# [[Procedural-Content-Generation-via-Machine-Learning]] +# [[Procedural-Content-Generation-via-Machine-Learning|Procedural-Content-Generation-via-Machine-Learning]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Procedural-Content-Generation- ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Procedural-Content-Generation-via-Machine-Learning.md]] +- Raw Source: 00_Raw/2026-04-20/Procedural-Content-Generation-via-Machine-Learning.md --- diff --git a/01_Archive/2026-04-20/Procedural-Content-Generation.md b/01_Archive/2026-04-20/Procedural-Content-Generation.md index 117c8a06..670b70bc 100644 --- a/01_Archive/2026-04-20/Procedural-Content-Generation.md +++ b/01_Archive/2026-04-20/Procedural-Content-Generation.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-CE4240 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Procedural-Content-Generation" --- -# [[Procedural-Content-Generation]] +# [[Procedural-Content-Generation|Procedural-Content-Generation]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Procedural-Content-Generation" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Procedural-Content-Generation.md]] +- Raw Source: 00_Raw/2026-04-20/Procedural-Content-Generation.md --- diff --git a/01_Archive/2026-04-20/Procedural-Rhetoric.md b/01_Archive/2026-04-20/Procedural-Rhetoric.md index dd2a419d..46d9a2dc 100644 --- a/01_Archive/2026-04-20/Procedural-Rhetoric.md +++ b/01_Archive/2026-04-20/Procedural-Rhetoric.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-4B887E -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Procedural-Rhetoric" --- -# [[Procedural-Rhetoric]] +# [[Procedural-Rhetoric|Procedural-Rhetoric]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Procedural-Rhetoric" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Procedural-Rhetoric.md]] +- Raw Source: 00_Raw/2026-04-20/Procedural-Rhetoric.md --- diff --git a/01_Archive/2026-04-20/Procedural-Texture-Generation.md b/01_Archive/2026-04-20/Procedural-Texture-Generation.md index 8db62eec..46b10a81 100644 --- a/01_Archive/2026-04-20/Procedural-Texture-Generation.md +++ b/01_Archive/2026-04-20/Procedural-Texture-Generation.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-5EABE9 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Procedural-Texture-Generation" --- -# [[Procedural-Texture-Generation]] +# [[Procedural-Texture-Generation|Procedural-Texture-Generation]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Procedural-Texture-Generation" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Procedural-Texture-Generation.md]] +- Raw Source: 00_Raw/2026-04-20/Procedural-Texture-Generation.md --- diff --git a/01_Archive/2026-04-20/Process Supervision (과정 감독).md b/01_Archive/2026-04-20/Process Supervision (과정 감독).md index ec4e8b4e..363c7372 100644 --- a/01_Archive/2026-04-20/Process Supervision (과정 감독).md +++ b/01_Archive/2026-04-20/Process Supervision (과정 감독).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-DD3E5C -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Process Supervision (과정 감독)" --- -# [[Process Supervision (과정 감독)]] +# [[Process Supervision (과정 감독)|Process Supervision (과정 감독)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Process Supervision (과정 ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Process Supervision (과정 감독).md]] +- Raw Source: 00_Raw/2026-04-20/Process Supervision (과정 감독).md --- diff --git a/01_Archive/2026-04-20/Product-Analytics-Infrastructure.md b/01_Archive/2026-04-20/Product-Analytics-Infrastructure.md index 31eb7711..0a34e41c 100644 --- a/01_Archive/2026-04-20/Product-Analytics-Infrastructure.md +++ b/01_Archive/2026-04-20/Product-Analytics-Infrastructure.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-B3941E -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Product-Analytics-Infrastructure" --- -# [[Product-Analytics-Infrastructure]] +# [[Product-Analytics-Infrastructure|Product-Analytics-Infrastructure]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Product-Analytics-Infrastructu ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Product-Analytics-Infrastructure.md]] +- Raw Source: 00_Raw/2026-04-20/Product-Analytics-Infrastructure.md --- diff --git a/01_Archive/2026-04-20/Product-Types.md b/01_Archive/2026-04-20/Product-Types.md index d67aaeb6..7f54d6ed 100644 --- a/01_Archive/2026-04-20/Product-Types.md +++ b/01_Archive/2026-04-20/Product-Types.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-9999F1 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Product-Types" --- -# [[Product-Types]] +# [[Product-Types|Product-Types]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Product-Types" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Product-Types.md]] +- Raw Source: 00_Raw/2026-04-20/Product-Types.md --- diff --git a/01_Archive/2026-04-20/Prompt Injection (프롬프트 주입 공격).md b/01_Archive/2026-04-20/Prompt Injection (프롬프트 주입 공격).md index 3459a1b9..e0cee0bb 100644 --- a/01_Archive/2026-04-20/Prompt Injection (프롬프트 주입 공격).md +++ b/01_Archive/2026-04-20/Prompt Injection (프롬프트 주입 공격).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-755BF7 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Prompt Injection (프롬프트 주입 공격)" --- -# [[Prompt Injection (프롬프트 주입 공격)]] +# [[Prompt Injection (프롬프트 주입 공격)|Prompt Injection (프롬프트 주입 공격)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Prompt Injection (프롬프트 ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Prompt Injection (프롬프트 주입 공격).md]] +- Raw Source: 00_Raw/2026-04-20/Prompt Injection (프롬프트 주입 공격).md --- diff --git a/01_Archive/2026-04-20/Proprioception.md b/01_Archive/2026-04-20/Proprioception.md index e72c8e20..3e677b73 100644 --- a/01_Archive/2026-04-20/Proprioception.md +++ b/01_Archive/2026-04-20/Proprioception.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-B85544 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Proprioception" --- -# [[Proprioception]] +# [[Proprioception|Proprioception]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Proprioception" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Proprioception.md]] +- Raw Source: 00_Raw/2026-04-20/Proprioception.md --- diff --git a/01_Archive/2026-04-20/Prospect Theory.md b/01_Archive/2026-04-20/Prospect Theory.md index 5f97c1c9..a0ee7327 100644 --- a/01_Archive/2026-04-20/Prospect Theory.md +++ b/01_Archive/2026-04-20/Prospect Theory.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-95BA10 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Prospect Theory" --- -# [[Prospect Theory]] +# [[Prospect Theory|Prospect Theory]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Prospect Theory" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Prospect Theory.md]] +- Raw Source: 00_Raw/2026-04-20/Prospect Theory.md --- diff --git a/01_Archive/2026-04-20/Prosthetic-Design-Optimization.md b/01_Archive/2026-04-20/Prosthetic-Design-Optimization.md index 11ce1de9..09f84c80 100644 --- a/01_Archive/2026-04-20/Prosthetic-Design-Optimization.md +++ b/01_Archive/2026-04-20/Prosthetic-Design-Optimization.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-67AEBB -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Prosthetic-Design-Optimization" --- -# [[Prosthetic-Design-Optimization]] +# [[Prosthetic-Design-Optimization|Prosthetic-Design-Optimization]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Prosthetic-Design-Optimization ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Prosthetic-Design-Optimization.md]] +- Raw Source: 00_Raw/2026-04-20/Prosthetic-Design-Optimization.md --- diff --git a/01_Archive/2026-04-20/Protocol-Buffers-TypeScript.md b/01_Archive/2026-04-20/Protocol-Buffers-TypeScript.md index 58fb9b91..3c1dee2f 100644 --- a/01_Archive/2026-04-20/Protocol-Buffers-TypeScript.md +++ b/01_Archive/2026-04-20/Protocol-Buffers-TypeScript.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-1F2F42 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Protocol-Buffers-TypeScript" --- -# [[Protocol-Buffers-TypeScript]] +# [[Protocol-Buffers-TypeScript|Protocol-Buffers-TypeScript]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Protocol-Buffers-TypeScript" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Protocol-Buffers-TypeScript.md]] +- Raw Source: 00_Raw/2026-04-20/Protocol-Buffers-TypeScript.md --- diff --git a/01_Archive/2026-04-20/Psychophysiology.md b/01_Archive/2026-04-20/Psychophysiology.md index 78041d1f..3cb536b9 100644 --- a/01_Archive/2026-04-20/Psychophysiology.md +++ b/01_Archive/2026-04-20/Psychophysiology.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-DD660D -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Psychophysiology" --- -# [[Psychophysiology]] +# [[Psychophysiology|Psychophysiology]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Psychophysiology" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Psychophysiology.md]] +- Raw Source: 00_Raw/2026-04-20/Psychophysiology.md --- diff --git a/01_Archive/2026-04-20/Public Policy Design.md b/01_Archive/2026-04-20/Public Policy Design.md index 07f74a09..b0eebf81 100644 --- a/01_Archive/2026-04-20/Public Policy Design.md +++ b/01_Archive/2026-04-20/Public Policy Design.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-444363 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Public Policy Design" --- -# [[Public Policy Design]] +# [[Public Policy Design|Public Policy Design]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Public Policy Design" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Public Policy Design.md]] +- Raw Source: 00_Raw/2026-04-20/Public Policy Design.md --- diff --git a/01_Archive/2026-04-20/Pull Request (PR) 워크플로우.md b/01_Archive/2026-04-20/Pull Request (PR) 워크플로우.md index 66f62ffb..7784b2bd 100644 --- a/01_Archive/2026-04-20/Pull Request (PR) 워크플로우.md +++ b/01_Archive/2026-04-20/Pull Request (PR) 워크플로우.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-47A74B -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Pull Request (PR) 워크플로우" --- -# [[Pull Request (PR) 워크플로우]] +# [[Pull Request (PR) 워크플로우|Pull Request (PR) 워크플로우]] ## 📌 한 줄 통찰 (The Karpathy Summary) > Pull Request (PR) 워크플로우는 소프트웨어 개발 과정에서 코드 변경 사항이 메인 브랜치에 병합(merge)되기 전에 검토, 분석 및 승인되는 핵심 단계입니다 [1, 2]. 현대적인 PR 워크플로우는 인간 개발자의 수동 리뷰와 AI 기반 코드 리뷰, 정적 분석(SAST) 등의 자동화 도구를 결합한 하이브리드 방식을 채택합니다 [3, 4]. 이를 통해 보안 취약점과 버그를 조기에 발견하고 PR 처리 시간을 크게 단축하여 전체적인 소프트웨어 배포의 안정성과 속도를 향상시킵니다 [5, 6]. @@ -23,11 +23,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Pull Request (PR) 워크플로 - **정책 변화:** AI 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[수동 코드 리뷰(Manual Code Review)]], [[자동화된 코드 리뷰(Automated Code Review)]], [[정적 애플리케이션 보안 테스트(SAST)]], [[Quality Gates]] -- **Projects/Contexts:** [[GitHub CODEOWNERS]], [[CI/CD 파이프라인]] +- **Related Topics:** [[수동 코드 리뷰 (Manual Code Review)|수동 코드 리뷰(Manual Code Review)]], 자동화된 코드 리뷰(Automated Code Review), [[정적 애플리케이션 보안 테스트(SAST)|정적 애플리케이션 보안 테스트(SAST)]], [[Quality Gates|Quality Gates]] +- **Projects/Contexts:** GitHub CODEOWNERS, [[CI_CD 파이프라인|CI/CD 파이프라인]] - **Contradictions/Notes:** 자동화된 AI PR 리뷰 봇은 프로세스를 가속화하지만, 때로는 사소하거나 가치 없는 코멘트를 대량으로 발생시켜 리뷰어에게 '경고 피로(Alert Fatigue)'를 유발할 수 있습니다 [18, 19]. 따라서 자동화 도구는 보조 수단일 뿐, 심층적인 아키텍처 결정은 여전히 인간의 수동 검토에 의존해야 합니다 [18]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Pull Request (PR) 워크플로우.md]] +- Raw Source: 00_Raw/2026-04-20/Pull Request (PR) 워크플로우.md --- diff --git a/01_Archive/2026-04-20/Pull Request (PR).md b/01_Archive/2026-04-20/Pull Request (PR).md index 214f2a35..d264dcdc 100644 --- a/01_Archive/2026-04-20/Pull Request (PR).md +++ b/01_Archive/2026-04-20/Pull Request (PR).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-3B4223 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Pull Request (PR)" --- -# [[Pull Request (PR)]] +# [[Pull Request (PR)|Pull Request (PR)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 풀 리퀘스트(Pull Request, PR)는 소프트웨어 개발 과정에서 개발자가 자신이 수정한 코드를 메인 브랜치에 병합(merge)하기 전, 다른 팀원이나 자동화 도구에게 코드 검토를 요청하는 워크플로우를 의미합니다 [1-3]. 이는 매뉴얼 코드 리뷰와 자동화된 정적 애플리케이션 보안 테스트(SAST) 및 AI 코드 리뷰가 실행되는 주요 환경으로 작용합니다 [1, 3-5]. PR 단계에서 코드의 품질, 보안 취약점, 로직 오류 등을 사전에 식별하고 논의함으로써 프로덕션 환경에 결함이 배포되는 것을 방지하고 유지보수성을 높일 수 있습니다 [4, 6-8]. @@ -27,11 +27,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Pull Request (PR)" - **정책 변화:** AI 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Code Review]], [[Static Application Security Testing (SAST)]], [[Continuous Integration/Continuous Deployment (CI/CD)]] -- **Projects/Contexts:** [[DevSecOps]], [[GitHub]] +- **Related Topics:** [[Code Review|Code Review]], [[Static Application Security Testing (SAST)|Static Application Security Testing (SAST)]], Continuous Integration/Continuous Deployment (CI/CD) +- **Projects/Contexts:** [[DevSecOps|DevSecOps]], GitHub - **Contradictions/Notes:** 자동화 및 AI 도구는 PR 내에서 발생하는 문법 오류나 알려진 보안 취약점을 빠르게 찾아내고 수정 제안을 제공하지만, 비즈니스 로직이나 아키텍처, 코드의 근본적인 의도를 파악하는 데에는 한계가 있으므로, 중요하고 민감한 변경 사항에 대해서는 인간 개발자의 수동 PR 리뷰가 반드시 병행되어야 합니다 [3, 8, 23]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Pull Request (PR).md]] +- Raw Source: 00_Raw/2026-04-20/Pull Request (PR).md --- diff --git a/01_Archive/2026-04-20/Quality Gates.md b/01_Archive/2026-04-20/Quality Gates.md index c2adf2ca..694d4581 100644 --- a/01_Archive/2026-04-20/Quality Gates.md +++ b/01_Archive/2026-04-20/Quality Gates.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-B577EF -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Quality Gates" --- -# [[Quality Gates]] +# [[Quality Gates|Quality Gates]] ## 📌 한 줄 통찰 (The Karpathy Summary) > Quality Gates(품질 게이트)는 소프트웨어 개발 수명 주기(SDLC)에서 코드 병합이나 배포 전에 사전에 정의된 품질 및 보안 표준을 충족하는지 평가하는 정책 기반의 검사 메커니즘입니다 [1, 2]. 주로 풀 리퀘스트(Pull Request) 단계에서 실행되어 복잡도, 취약점, 중복 등의 지표를 평가한 후 통과(Pass) 또는 실패(Fail) 상태를 이진(binary) 신호로 명확히 할당합니다 [2-4]. 이를 통해 팀은 비공식적인 리뷰 코멘트에 의존하지 않고 객관적인 규칙 세트에 따라 코드 품질을 일관되게 유지하며, 규모에 맞는 안전한 코드 배포를 보장할 수 있습니다 [2, 5]. @@ -23,11 +23,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Quality Gates" - **정책 변화:** AI 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Static Application Security Testing (SAST)]], [[CI/CD pipelines]], [[Pull Request (PR)]] -- **Projects/Contexts:** [[SonarQube Cloud]], [[Codacy]], [[AI Code Assurance]] +- **Related Topics:** [[Static Application Security Testing (SAST)|Static Application Security Testing (SAST)]], CI/CD pipelines, [[Pull Request (PR)|Pull Request (PR)]] +- **Projects/Contexts:** SonarQube Cloud, Codacy, AI Code Assurance - **Contradictions/Notes:** 소스는 팀 내 비공식적인 코드 리뷰 코멘트에 의존하여 병합을 결정하는 것보다, Quality Gates와 같은 명시적인 규칙 세트 기반의 이진 신호(통과/실패)를 통해 병합을 차단하는 방식이 시간이 지남에 따른 품질 변화를 더 명확하게 측정하고 통제할 수 있다고 강조합니다 [2]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Quality Gates.md]] +- Raw Source: 00_Raw/2026-04-20/Quality Gates.md --- diff --git a/01_Archive/2026-04-20/Quantitative Finance.md b/01_Archive/2026-04-20/Quantitative Finance.md index 5c7824a6..7b188eb4 100644 --- a/01_Archive/2026-04-20/Quantitative Finance.md +++ b/01_Archive/2026-04-20/Quantitative Finance.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AI-057 -category: "[[10_Wiki/💡 Topics/Financial Modeling & Math]]" +category: "10_Wiki/💡 Topics/Financial Modeling & Math" confidence_score: 0.98 tags: [finance, quantitative finance, stochastics, risk management] last_reinforced: 2026-06-XX github_commit: "[P-Reinforce] Processed Quantitative Finance." --- -# [[Quantitative Finance]] (계량 금융) +# [[Quantitative Finance|Quantitative Finance]] (계량 금융) ## 📌 한 줄 통찰 (The Karpathy Summary) > 수학적 모델링, 통계학, 컴퓨터 과학을 결합하여 시장의 복잡한 데이터를 분석하고, 위험을 관리하며, 최적의 거래 전략을 수립하는 학문이다. @@ -24,7 +24,7 @@ github_commit: "[P-Reinforce] Processed Quantitative Finance." - **정책 변화:** 최근에는 강화학습 (RL)과 결합하여, 시장 상황이라는 환경 속에서 에이전트가 최적의 행동 정책을 학습하게 하는 방향으로 진화하고 있다. ## 🔗 지식 연결 (Graph) -- Parent: [[Probability Theory]] -- Related: [[Reinforcement Learning in Economics]] , [[Risk Management in Finance]] , [[Stochastic Processes]] -- Raw Source: [[00_Raw/Quantitative Finance.md]] +- Parent: [[Probability Theory|Probability Theory]] +- Related: [[Reinforcement Learning in Economics|Reinforcement Learning in Economics]] , [[Risk Management in Finance|Risk Management in Finance]] , [[Stochastic Processes|Stochastic Processes]] +- Raw Source: 00_Raw/Quantitative Finance.md --- \ No newline at end of file diff --git a/01_Archive/2026-04-20/Quantitative-Usability-Testing.md b/01_Archive/2026-04-20/Quantitative-Usability-Testing.md index 936664bf..42179d10 100644 --- a/01_Archive/2026-04-20/Quantitative-Usability-Testing.md +++ b/01_Archive/2026-04-20/Quantitative-Usability-Testing.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-8A68D1 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Quantitative-Usability-Testing" --- -# [[Quantitative-Usability-Testing]] +# [[Quantitative-Usability-Testing|Quantitative-Usability-Testing]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Quantitative-Usability-Testing ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Quantitative-Usability-Testing.md]] +- Raw Source: 00_Raw/2026-04-20/Quantitative-Usability-Testing.md --- diff --git a/01_Archive/2026-04-20/Quantum-Computing-Simulations.md b/01_Archive/2026-04-20/Quantum-Computing-Simulations.md index 19440c55..d24c0266 100644 --- a/01_Archive/2026-04-20/Quantum-Computing-Simulations.md +++ b/01_Archive/2026-04-20/Quantum-Computing-Simulations.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-5FB7B9 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Quantum-Computing-Simulations" --- -# [[Quantum-Computing-Simulations]] +# [[Quantum-Computing-Simulations|Quantum-Computing-Simulations]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Quantum-Computing-Simulations" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Quantum-Computing-Simulations.md]] +- Raw Source: 00_Raw/2026-04-20/Quantum-Computing-Simulations.md --- diff --git a/01_Archive/2026-04-20/Quantum-Game-Theory.md b/01_Archive/2026-04-20/Quantum-Game-Theory.md index 25053b79..2772b878 100644 --- a/01_Archive/2026-04-20/Quantum-Game-Theory.md +++ b/01_Archive/2026-04-20/Quantum-Game-Theory.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-238ED6 -category: "[[10_Wiki/💡 Topics/Game Design]]" +category: "10_Wiki/💡 Topics/Game Design" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Quantum-Game-Theory" --- -# [[Quantum-Game-Theory]] +# [[Quantum-Game-Theory|Quantum-Game-Theory]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Quantum-Game-Theory" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Quantum-Game-Theory.md]] +- Raw Source: 00_Raw/2026-04-20/Quantum-Game-Theory.md --- diff --git a/01_Archive/2026-04-20/R3F 3D 게임 환경의 메모리 관리.md b/01_Archive/2026-04-20/R3F 3D 게임 환경의 메모리 관리.md index d1dba4a3..0aceda2a 100644 --- a/01_Archive/2026-04-20/R3F 3D 게임 환경의 메모리 관리.md +++ b/01_Archive/2026-04-20/R3F 3D 게임 환경의 메모리 관리.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-7C6FD2 -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - R3F 3D 게임 환경의 메모리 관리" --- -# [[R3F 3D 게임 환경의 메모리 관리]] +# [[R3F 3D 게임 환경의 메모리 관리|R3F 3D 게임 환경의 메모리 관리]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - R3F 3D 게임 환경의 메모 ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/R3F 3D 게임 환경의 메모리 관리.md]] +- Raw Source: 00_Raw/2026-04-20/R3F 3D 게임 환경의 메모리 관리.md --- diff --git a/01_Archive/2026-04-20/RAG (검색 증강 생성).md b/01_Archive/2026-04-20/RAG (검색 증강 생성).md index d0b9be70..d4b23fd9 100644 --- a/01_Archive/2026-04-20/RAG (검색 증강 생성).md +++ b/01_Archive/2026-04-20/RAG (검색 증강 생성).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-937086 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - RAG (검색 증강 생성)" --- -# [[RAG (검색 증강 생성)]] +# [[RAG (검색 증강 생성)|RAG (검색 증강 생성)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - RAG (검색 증강 생성)" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/RAG (검색 증강 생성).md]] +- Raw Source: 00_Raw/2026-04-20/RAG (검색 증강 생성).md --- diff --git a/01_Archive/2026-04-20/RDF-star (RDF 확장 사양).md b/01_Archive/2026-04-20/RDF-star (RDF 확장 사양).md index c67fdfcb..406bfe8d 100644 --- a/01_Archive/2026-04-20/RDF-star (RDF 확장 사양).md +++ b/01_Archive/2026-04-20/RDF-star (RDF 확장 사양).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-E70DB9 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - RDF-star (RDF 확장 사양)" --- -# [[RDF-star (RDF 확장 사양)]] +# [[RDF-star (RDF 확장 사양)|RDF-star (RDF 확장 사양)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - RDF-star (RDF 확장 사양)" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/RDF-star (RDF 확장 사양).md]] +- Raw Source: 00_Raw/2026-04-20/RDF-star (RDF 확장 사양).md --- diff --git a/01_Archive/2026-04-20/RDF와 OWL.md b/01_Archive/2026-04-20/RDF와 OWL.md index 58764dba..07a54bbe 100644 --- a/01_Archive/2026-04-20/RDF와 OWL.md +++ b/01_Archive/2026-04-20/RDF와 OWL.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-58CF7B -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - RDF와 OWL" --- -# [[RDF와 OWL]] +# [[RDF와 OWL|RDF와 OWL]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - RDF와 OWL" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/RDF와 OWL.md]] +- Raw Source: 00_Raw/2026-04-20/RDF와 OWL.md --- diff --git a/01_Archive/2026-04-20/README.md b/01_Archive/2026-04-20/README.md index 571ee145..a0dd2395 100644 --- a/01_Archive/2026-04-20/README.md +++ b/01_Archive/2026-04-20/README.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-698D8B -category: "[[10_Wiki/💡 Topics/General Knowledge]]" +category: "10_Wiki/💡 Topics/General Knowledge" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - README" --- -# [[README]] +# [[README|README]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - README" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/README.md]] +- Raw Source: 00_Raw/2026-04-20/README.md --- diff --git a/01_Archive/2026-04-20/RLAIF (AI 피드백 기반 강화학습).md b/01_Archive/2026-04-20/RLAIF (AI 피드백 기반 강화학습).md index 56a4fabb..eca39ecd 100644 --- a/01_Archive/2026-04-20/RLAIF (AI 피드백 기반 강화학습).md +++ b/01_Archive/2026-04-20/RLAIF (AI 피드백 기반 강화학습).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-77C4FB -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - RLAIF (AI 피드백 기반 강화학습)" --- -# [[RLAIF (AI 피드백 기반 강화학습)]] +# [[RLAIF (AI 피드백 기반 강화학습)|RLAIF (AI 피드백 기반 강화학습)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - RLAIF (AI 피드백 기반 강 ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/RLAIF (AI 피드백 기반 강화학습).md]] +- Raw Source: 00_Raw/2026-04-20/RLAIF (AI 피드백 기반 강화학습).md --- diff --git a/01_Archive/2026-04-20/RLHF (인간 피드백 기반 강화학습).md b/01_Archive/2026-04-20/RLHF (인간 피드백 기반 강화학습).md index c2e7b021..4dccbee8 100644 --- a/01_Archive/2026-04-20/RLHF (인간 피드백 기반 강화학습).md +++ b/01_Archive/2026-04-20/RLHF (인간 피드백 기반 강화학습).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-628311 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - RLHF (인간 피드백 기반 강화학습)" --- -# [[RLHF (인간 피드백 기반 강화학습)]] +# [[RLHF (인간 피드백 기반 강화학습)|RLHF (인간 피드백 기반 강화학습)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - RLHF (인간 피드백 기반 ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/RLHF (인간 피드백 기반 강화학습).md]] +- Raw Source: 00_Raw/2026-04-20/RLHF (인간 피드백 기반 강화학습).md --- diff --git a/01_Archive/2026-04-20/RL_Neuroscience.md b/01_Archive/2026-04-20/RL_Neuroscience.md index 4580cf5a..6ba2b583 100644 --- a/01_Archive/2026-04-20/RL_Neuroscience.md +++ b/01_Archive/2026-04-20/RL_Neuroscience.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AI-003 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.98 tags: [ai, rl, neuroscience, brain] last_reinforced: 2026-04-20 github_commit: "batch-reinforce-04" --- -# [[RL_Neuroscience (Computational Reinforcement Learning)]] +# RL_Neuroscience (Computational Reinforcement Learning) ## 📌 한 줄 통찰 (The Karpathy Summary) > 보상 학습의 생물학적 기제와 기계 학습 알고리즘의 수렴을 통해 지능의 본질을 규명하는 계산 뇌과학의 정점. @@ -24,6 +24,6 @@ github_commit: "batch-reinforce-04" - **정책 변화:** P-Reinforce 엔진의 핵심 로직(Self-Optimization)을 뒷받침하는 이론적 근거로 최상단 배치. ## 🔗 지식 연결 (Graph) -- **Parent:** [[10_Wiki/💡 Topics/AI]] -- **Related:** [[Dopamine]], [[Operant_Conditioning]], [[Reinforcement-Learning]] -- **Raw Source:** [[00_Raw/2026-04-20/Computational Neuroscience of Reinforcement Learning.md]] +- **Parent:** 10_Wiki/💡 Topics/AI +- **Related:** [[Dopamine|Dopamine]], [[Operant_Conditioning|Operant_Conditioning]], [[Reinforcement-Learning|Reinforcement-Learning]] +- **Raw Source:** 00_Raw/2026-04-20/Computational Neuroscience of Reinforcement Learning.md diff --git a/01_Archive/2026-04-20/RRF (Reciprocal Rank Fusion).md b/01_Archive/2026-04-20/RRF (Reciprocal Rank Fusion).md index a4d0492c..f724819c 100644 --- a/01_Archive/2026-04-20/RRF (Reciprocal Rank Fusion).md +++ b/01_Archive/2026-04-20/RRF (Reciprocal Rank Fusion).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-6A4FE8 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - RRF (Reciprocal Rank Fusion)" --- -# [[RRF (Reciprocal Rank Fusion)]] +# [[RRF (Reciprocal Rank Fusion)|RRF (Reciprocal Rank Fusion)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - RRF (Reciprocal Rank Fusion)" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/RRF (Reciprocal Rank Fusion).md]] +- Raw Source: 00_Raw/2026-04-20/RRF (Reciprocal Rank Fusion).md --- diff --git a/01_Archive/2026-04-20/Radix Sort.md b/01_Archive/2026-04-20/Radix Sort.md index 65f96bde..a5bc12f0 100644 --- a/01_Archive/2026-04-20/Radix Sort.md +++ b/01_Archive/2026-04-20/Radix Sort.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-846BA8 -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Radix Sort" --- -# [[Radix Sort]] +# [[Radix Sort|Radix Sort]] ## 📌 한 줄 통찰 (The Karpathy Summary) > Radix Sort(기수 정렬)는 대규모 데이터 세트를 처리할 때 매우 높은 효율을 낼 수 있는 복잡한 정렬 알고리즘입니다 [1]. Three.js의 `BatchedMesh`에서 겹치는 인스턴스의 렌더링 순서(Depth sorting)를 해결하기 위해 사용된 적이 있으나 단순성을 위해 대체되었으며, 현재는 확장 라이브러리인 `InstancedMesh2`의 예제 등에서 활용되고 있습니다 [1, 2]. @@ -23,11 +23,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Radix Sort" - **정책 변화:** Graphics & Performance 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[BatchedMesh]], [[InstancedMesh2]] -- **Projects/Contexts:** [[Three.js]], [[Depth Sorting]] +- **Related Topics:** [[BatchedMesh|BatchedMesh]], [[InstancedMesh2|InstancedMesh2]] +- **Projects/Contexts:** [[Three.js|Three.js]], Depth Sorting - **Contradictions/Notes:** Radix Sort는 대규모 데이터에서 7배 빠른 성능을 제공하는 훌륭한 장점이 있음에도 불구하고, 공식 `BatchedMesh`에서는 라이브러리 내부 구조의 단순성(simplicity)을 유지하기 위해 제거되었다는 특징이 있습니다 [1]. 그 외 알고리즘 작동 원리에 대해서는 소스에 관련 정보가 부족합니다. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Radix Sort.md]] +- Raw Source: 00_Raw/2026-04-20/Radix Sort.md --- diff --git a/01_Archive/2026-04-20/Rapier 물리 엔진 스냅샷(Snapshot) 기반 상태 복원.md b/01_Archive/2026-04-20/Rapier 물리 엔진 스냅샷(Snapshot) 기반 상태 복원.md index b5fdfad3..12a685cb 100644 --- a/01_Archive/2026-04-20/Rapier 물리 엔진 스냅샷(Snapshot) 기반 상태 복원.md +++ b/01_Archive/2026-04-20/Rapier 물리 엔진 스냅샷(Snapshot) 기반 상태 복원.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-D58438 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Rapier 물리 엔진 스냅샷(Snapshot) 기반 상태 복원" --- -# [[Rapier 물리 엔진 스냅샷(Snapshot) 기반 상태 복원]] +# [[Rapier 물리 엔진 스냅샷(Snapshot) 기반 상태 복원|Rapier 물리 엔진 스냅샷(Snapshot) 기반 상태 복원]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Rapier 물리 엔진 스냅샷 ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Rapier 물리 엔진 스냅샷(Snapshot) 기반 상태 복원.md]] +- Raw Source: 00_Raw/2026-04-20/Rapier 물리 엔진 스냅샷(Snapshot) 기반 상태 복원.md --- diff --git a/01_Archive/2026-04-20/Raycaster.md b/01_Archive/2026-04-20/Raycaster.md index d6b0ddd9..9b9b1227 100644 --- a/01_Archive/2026-04-20/Raycaster.md +++ b/01_Archive/2026-04-20/Raycaster.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-D7A57A -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Raycaster" --- -# [[Raycaster]] +# [[Raycaster|Raycaster]] ## 📌 한 줄 통찰 (The Karpathy Summary) > Raycaster(레이캐스터)는 가상의 광선(Ray)과 3D 장면 내 객체 간의 교차점을 계산하여 충돌을 감지하는 기법이자 Three.js의 핵심 클래스(`THREE.Raycaster`)입니다 [1-3]. 주로 마우스 클릭과 같은 사용자 상호작용(오브젝트 피킹)을 구현하여 카메라 시점이나 특정 위치에서 어떤 객체가 선택되었는지 판별하는 데 필수적으로 사용됩니다 [4-6]. @@ -23,11 +23,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Raycaster" - **정책 변화:** Graphics & Performance 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Three.js]], [[InstancedMesh]], [[three-mesh-bvh]], [[Bounding Volume]] -- **Projects/Contexts:** [[3D Object Picking]], [[Interaction in WebGL]] +- **Related Topics:** [[Three.js|Three.js]], [[InstancedMesh|InstancedMesh]], [[three-mesh-bvh|three-mesh-bvh]], Bounding Volume +- **Projects/Contexts:** 3D Object Picking, Interaction in WebGL - **Contradictions/Notes:** 소스에 따르면 레이캐스팅은 CPU 기반 연산이므로, GPU 셰이더(Compute Shader 등)를 통해 동적으로 애니메이션 처리된 기하학적 구조에 대해서는 CPU가 변환을 알지 못해 기본 레이캐스터로 올바른 피킹을 수행할 수 없습니다 [8, 9]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Raycaster.md]] +- Raw Source: 00_Raw/2026-04-20/Raycaster.md --- diff --git a/01_Archive/2026-04-20/Raycasting.md b/01_Archive/2026-04-20/Raycasting.md index e37cff15..99e533ff 100644 --- a/01_Archive/2026-04-20/Raycasting.md +++ b/01_Archive/2026-04-20/Raycasting.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-BD8B44 -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Raycasting" --- -# [[Raycasting]] +# [[Raycasting|Raycasting]] ## 📌 한 줄 통찰 (The Karpathy Summary) > Raycasting(레이캐스팅)은 가상의 광선(Ray)과 3D 환경 내 객체들 간의 교차점을 감지하는 계산 기법입니다 [1, 2]. 3D 씬 내에서 사용자가 화면을 클릭하여 특정 객체를 선택(Picking)하거나 드래그하는 등의 사용자 상호작용(Interaction)을 구현할 때 필수적으로 사용됩니다 [3-5]. Three.js 환경에서는 `THREE.Raycaster` 클래스를 통해 이 기능을 수행할 수 있습니다 [2, 3]. @@ -33,11 +33,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Raycasting" - **정책 변화:** Graphics & Performance 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[THREE.Raycaster]], [[Bounding Volume Hierarchy (BVH)]], [[InstancedMesh]], [[GPU Picking]] -- **Projects/Contexts:** [[3D 사용자 상호작용 및 마우스 피킹 (Picking)]] 구현, [[three-mesh-bvh]] 라이브러리 연동 +- **Related Topics:** THREE.Raycaster, [[Bounding Volume Hierarchy (BVH)|Bounding Volume Hierarchy (BVH)]], [[InstancedMesh|InstancedMesh]], GPU Picking +- **Projects/Contexts:** 3D 사용자 상호작용 및 마우스 피킹 (Picking) 구현, [[three-mesh-bvh|three-mesh-bvh]] 라이브러리 연동 - **Contradictions/Notes:** `InstancedMesh`를 사용할 때 GPU 성능 이점은 크지만, 각 인스턴스마다 CPU 기반 레이캐스팅을 처리하거나 개별 정밀도를 조작하는 데는 유연성이 떨어집니다 [15]. 또한 셰이더로 지오메트리를 변경하면 CPU 레이캐스팅과 데이터 불일치가 발생하므로 설계 시 주의가 필요합니다 [21]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Raycasting.md]] +- Raw Source: 00_Raw/2026-04-20/Raycasting.md --- diff --git a/01_Archive/2026-04-20/ReAct (Reasoning Acting).md b/01_Archive/2026-04-20/ReAct (Reasoning Acting).md index e94ee50d..aa4a01d9 100644 --- a/01_Archive/2026-04-20/ReAct (Reasoning Acting).md +++ b/01_Archive/2026-04-20/ReAct (Reasoning Acting).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-382E0C -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - ReAct (Reasoning Acting)" --- -# [[ReAct (Reasoning Acting)]] +# [[ReAct (Reasoning Acting)|ReAct (Reasoning Acting)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - ReAct (Reasoning Acting)" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/ReAct (Reasoning + Acting).md]] +- Raw Source: 00_Raw/2026-04-20/ReAct (Reasoning + Acting).md --- diff --git a/01_Archive/2026-04-20/ReAct (Reasoning + Acting).md b/01_Archive/2026-04-20/ReAct (Reasoning + Acting).md index a8420f87..17c7e733 100644 --- a/01_Archive/2026-04-20/ReAct (Reasoning + Acting).md +++ b/01_Archive/2026-04-20/ReAct (Reasoning + Acting).md @@ -1,4 +1,4 @@ -[[ReAct (Reasoning + Acting)]] +[[ReAct (Reasoning + Acting)|ReAct (Reasoning + Acting)]] 📌 Brief Summary @@ -88,8 +88,8 @@ Final Answer: [최신 논문 + KG 구조적 정보 통합 응답] 🔗 Knowledge Connections -- **Related Topics:** [[Chain-of-Thought (CoT, 사고 사슬)]], [[GraphRAG (그래프 기반 검색 증강 생성)]], [[RAG (검색 증강 생성)]], [[Multi-Hop Reasoning (다중 홉 추론)]], [[SPARQL (RDF 그래프 질의 언어)]], [[LLM Hallucination (언어 모델 환각)]], [[AI 에이전트 (AI Agent)]] -- **Projects/Contexts:** [[AI 추론 시스템]] +- **Related Topics:** [[Chain-of-Thought (CoT, 사고 사슬)|Chain-of-Thought (CoT, 사고 사슬)]], [[GraphRAG (그래프 기반 검색 증강 생성)|GraphRAG (그래프 기반 검색 증강 생성)]], [[RAG (검색 증강 생성)|RAG (검색 증강 생성)]], [[Multi-Hop Reasoning (다중 홉 추론)|Multi-Hop Reasoning (다중 홉 추론)]], [[SPARQL (RDF 그래프 질의 언어)|SPARQL (RDF 그래프 질의 언어)]], [[LLM Hallucination (언어 모델 환각)|LLM Hallucination (언어 모델 환각)]], [[AI 에이전트 (AI Agent)|AI 에이전트 (AI Agent)]] +- **Projects/Contexts:** AI 추론 시스템 - **Contradictions/Notes:** - ReAct는 도구 호출 오류 시 루프에서 벗어나지 못할 위험 → 최대 반복 횟수(Max Steps) 제한 필요. - 도구 결과를 모델이 오해하거나 잘못 해석할 경우 오답 더 강화 위험 → 도구 결과 검증 레이어 병행 권장. diff --git a/01_Archive/2026-04-20/Reachability Analysis.md b/01_Archive/2026-04-20/Reachability Analysis.md index db3d9fdf..ad357d34 100644 --- a/01_Archive/2026-04-20/Reachability Analysis.md +++ b/01_Archive/2026-04-20/Reachability Analysis.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-5449D4 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Reachability Analysis" --- -# [[Reachability Analysis]] +# [[Reachability Analysis|Reachability Analysis]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 도달 가능성 분석(Reachability Analysis)은 소스 코드 및 오픈 소스 종속성 분석에 사용되는 보안 테스트 기법으로, 오염된 데이터가 민감한 싱크(sink)에 도달할 수 있는지 또는 특정 취약점이 실제 프로덕션 환경이나 실행 경로에서 호출 가능한지를 추적하는 방법입니다 [1, 2]. 콜 그래프(call graph)와 데이터 흐름 분석을 통해 취약한 함수로의 연결 고리를 식별하며, 도달할 수 없는 데드 코드(dead code)를 필터링합니다 [3, 4]. 결과적으로 노이즈와 오탐(false positives)을 줄여 개발자 및 보안팀이 실제 위협에 집중할 수 있도록 돕는 핵심 기술입니다 [4, 5]. @@ -26,11 +26,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Reachability Analysis" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[SAST (Static Application Security Testing)]], [[SCA (Software Composition Analysis)]], [[Call Graph]], [[Data Flow Analysis]], [[False Positives]], [[Vulnerability Prioritization]] -- **Projects/Contexts:** [[Endor Labs]], [[Veracode]], [[Corgea]], [[Qwiet AI]] +- **Related Topics:** [[SAST (Static Application Security Testing)|SAST (Static Application Security Testing)]], SCA (Software Composition Analysis), Call Graph, Data Flow Analysis, False Positives, Vulnerability Prioritization +- **Projects/Contexts:** Endor Labs, Veracode, [[Corgea|Corgea]], Qwiet AI - **Contradictions/Notes:** 제공된 소스 내에서 도달 가능성 분석의 효용성에 대한 모순점은 없으며, 모든 자료가 공통적으로 SAST 및 SCA 도구에서 오탐을 줄이고 실제 위험을 식별하는 데 매우 효과적이고 필수적인 접근법이라고 동의하고 있습니다 [2, 4]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Reachability Analysis.md]] +- Raw Source: 00_Raw/2026-04-20/Reachability Analysis.md --- diff --git a/01_Archive/2026-04-20/React 19 Compiler.md b/01_Archive/2026-04-20/React 19 Compiler.md index c75869ec..2991b70e 100644 --- a/01_Archive/2026-04-20/React 19 Compiler.md +++ b/01_Archive/2026-04-20/React 19 Compiler.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-A2E200 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - React 19 Compiler" --- -# [[React 19 Compiler]] +# [[React 19 Compiler|React 19 Compiler]] ## 📌 한 줄 통찰 (The Karpathy Summary) > **React 19 컴파일러(React Compiler)**는 빌드 타임에 코드를 분석하여 컴포넌트, 값, 콜백 함수에 자동으로 메모이제이션(`useMemo`, `useCallback` 등)을 적용하는 최적화 도구입니다. 수동 최적화에 필요한 보일러플레이트 코드를 대폭 줄이면서도 애플리케이션의 전반적인 렌더링 성능을 향상시킵니다. @@ -29,8 +29,8 @@ github_commit: "[P-Reinforce] Continuous Worker - React 19 Compiler" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[React Performance Optimization]], [[useMemo & useCallback]], [[불필요한 리렌더링 방지]], [[재조정 (Reconciliation)]] -- **Projects/Contexts:** [[대규모 React 프론트엔드 최적화 및 리팩토링]], [[고성능 실시간 상호작용 엔진 구축]] +- **Related Topics:** [[React Performance Optimization|React Performance Optimization]], useMemo & useCallback, [[불필요한 리렌더링 방지|불필요한 리렌더링 방지]], [[재조정 (Reconciliation)|재조정 (Reconciliation)]] +- **Projects/Contexts:** 대규모 React 프론트엔드 최적화 및 리팩토링, 고성능 실시간 상호작용 엔진 구축 - **Contradictions/Notes:** 새로운 컴파일러가 메모이제이션을 마법처럼 자동화해주지만, **비효율적인 데이터 패칭이나 잘못 설계된 거대한 컴포넌트 트리, 무분별한 전역 상태 관리와 같은 근본적인 아키텍처 결함까지 해결해 주지는 못합니다**. 올바른 성능 최적화를 위해서는 컴파일러에만 의존하지 않고 훌륭한 소프트웨어 설계 원칙을 계속 유지해야 합니다. -- Raw Source: [[00_Raw/2026-04-20/React 19 Compiler.md]] +- Raw Source: 00_Raw/2026-04-20/React 19 Compiler.md --- diff --git a/01_Archive/2026-04-20/React 19 Compiler의 Three.js 런타임 성능 개선 원리.md b/01_Archive/2026-04-20/React 19 Compiler의 Three.js 런타임 성능 개선 원리.md index 730e4566..e790ea93 100644 --- a/01_Archive/2026-04-20/React 19 Compiler의 Three.js 런타임 성능 개선 원리.md +++ b/01_Archive/2026-04-20/React 19 Compiler의 Three.js 런타임 성능 개선 원리.md @@ -16,8 +16,8 @@ React 19 컴파일러는 빌드 타임에 코드의 값, 컴포넌트, 콜백 ## 🔗 Knowledge Connections -- **Related Topics:** [[React 19 Compiler]], [[React Three Fiber (R3F)]], [[가비지 컬렉션(GC) 최적화]], [[불필요한 리렌더링 방지]] -- **Projects/Contexts:** [[고성능 실시간 상호작용 시스템을 위한 React 기반 게임 엔진 아키텍처]] +- **Related Topics:** [[React 19 Compiler|React 19 Compiler]], [[React Three Fiber (R3F)|React Three Fiber (R3F)]], 가비지 컬렉션(GC) 최적화, [[불필요한 리렌더링 방지|불필요한 리렌더링 방지]] +- **Projects/Contexts:** [[고성능 실시간 상호작용 시스템을 위한 React 기반 게임 엔진 아키텍처|고성능 실시간 상호작용 시스템을 위한 React 기반 게임 엔진 아키텍처]] - **Contradictions/Notes:** React 19 컴파일러가 선언적 UI의 리렌더링 성능을 비약적으로 높여주지만, 게임의 근본적인 안티 패턴까지 해결해 주지는 않습니다. 예를 들어, 매 프레임 실행되는 `useFrame` 루프 내부에서 React 상태(`setState`)를 업데이트하거나 객체를 새로 생성(`new Vector3()`)하는 것은 여전히 치명적입니다. 빈번하게 변하는 3D 객체의 위치나 회전값 등은 컴파일러에 의존할 것이 아니라, 반드시 참조(Ref)를 사용하여 직접 변형(Direct Mutation)해야 합니다. --- diff --git a/01_Archive/2026-04-20/React 19 Compiler의 Threejs 런타임 성능 개선 원리.md b/01_Archive/2026-04-20/React 19 Compiler의 Threejs 런타임 성능 개선 원리.md index 63b9f7a5..c3763e1e 100644 --- a/01_Archive/2026-04-20/React 19 Compiler의 Threejs 런타임 성능 개선 원리.md +++ b/01_Archive/2026-04-20/React 19 Compiler의 Threejs 런타임 성능 개선 원리.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-777FEC -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - React 19 Compiler의 Threejs 런타임 성능 개선 원리" --- -# [[React 19 Compiler의 Threejs 런타임 성능 개선 원리]] +# [[React 19 Compiler의 Threejs 런타임 성능 개선 원리|React 19 Compiler의 Threejs 런타임 성능 개선 원리]] ## 📌 한 줄 통찰 (The Karpathy Summary) > React 19 컴파일러는 빌드 타임에 코드의 값, 컴포넌트, 콜백 함수를 자동으로 메모이제이션하여 잦은 가비지 컬렉션(GC)과 불필요한 리렌더링을 차단함으로써, React Three Fiber(R3F) 기반 3D 게임의 프레임 레이트(FPS)를 안정화하고 런타임 성능을 획기적으로 개선합니다. @@ -26,12 +26,12 @@ github_commit: "[P-Reinforce] Continuous Worker - React 19 Compiler의 Threejs - **정책 변화:** Graphics & Performance 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[React 19 Compiler]], [[React Three Fiber (R3F)]], [[가비지 컬렉션(GC) 최적화]], [[불필요한 리렌더링 방지]] -- **Projects/Contexts:** [[고성능 실시간 상호작용 시스템을 위한 React 기반 게임 엔진 아키텍처]] +- **Related Topics:** [[React 19 Compiler|React 19 Compiler]], [[React Three Fiber (R3F)|React Three Fiber (R3F)]], 가비지 컬렉션(GC) 최적화, [[불필요한 리렌더링 방지|불필요한 리렌더링 방지]] +- **Projects/Contexts:** [[고성능 실시간 상호작용 시스템을 위한 React 기반 게임 엔진 아키텍처|고성능 실시간 상호작용 시스템을 위한 React 기반 게임 엔진 아키텍처]] - **Contradictions/Notes:** React 19 컴파일러가 선언적 UI의 리렌더링 성능을 비약적으로 높여주지만, 게임의 근본적인 안티 패턴까지 해결해 주지는 않습니다. 예를 들어, 매 프레임 실행되는 `useFrame` 루프 내부에서 React 상태(`setState`)를 업데이트하거나 객체를 새로 생성(`new Vector3()`)하는 것은 여전히 치명적입니다. 빈번하게 변하는 3D 객체의 위치나 회전값 등은 컴파일러에 의존할 것이 아니라, 반드시 참조(Ref)를 사용하여 직접 변형(Direct Mutation)해야 합니다. --- _Last updated: 2026-04-15_ -- Raw Source: [[00_Raw/2026-04-20/React 19 Compiler의 Three.js 런타임 성능 개선 원리.md]] +- Raw Source: 00_Raw/2026-04-20/React 19 Compiler의 Three.js 런타임 성능 개선 원리.md --- diff --git a/01_Archive/2026-04-20/React Native 게임 최적화 (JSI Hermes).md b/01_Archive/2026-04-20/React Native 게임 최적화 (JSI Hermes).md index b41daadd..75f93b1f 100644 --- a/01_Archive/2026-04-20/React Native 게임 최적화 (JSI Hermes).md +++ b/01_Archive/2026-04-20/React Native 게임 최적화 (JSI Hermes).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-23E022 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - React Native 게임 최적화 (JSI Hermes)" --- -# [[React Native 게임 최적화 (JSI Hermes)]] +# [[React Native 게임 최적화 (JSI Hermes)|React Native 게임 최적화 (JSI Hermes)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - React Native 게임 최적화 ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/React Native 게임 최적화 (JSI, Hermes).md]] +- Raw Source: 00_Raw/2026-04-20/React Native 게임 최적화 (JSI, Hermes).md --- diff --git a/01_Archive/2026-04-20/React Native 게임 최적화 (JSI, Hermes).md b/01_Archive/2026-04-20/React Native 게임 최적화 (JSI, Hermes).md index 16993620..b427f3ee 100644 --- a/01_Archive/2026-04-20/React Native 게임 최적화 (JSI, Hermes).md +++ b/01_Archive/2026-04-20/React Native 게임 최적화 (JSI, Hermes).md @@ -1,4 +1,4 @@ -[[React Native 게임 최적화 (JSI, Hermes)]] +[[React Native 게임 최적화 (JSI, Hermes)|React Native 게임 최적화 (JSI, Hermes)]] 📌 Brief Summary Optimizing games in React Native involves moving beyond the traditional bridge-based communication. By leveraging the JavaScript Interface (JSI) for direct synchronous calls and the Hermes engine for efficient bytecode execution, developers can achieve near-native performance for complex interactive systems. @@ -12,8 +12,8 @@ Optimizing games in React Native involves moving beyond the traditional bridge-b * Use `react-native-skia` for high-performance 2D graphics directly on the GPU. 🔗 Knowledge Connections -* Related Topics: [[High-Performance-Mobile-Development]], [[C++ Interop]], [[JS Engine Architecture]] -* Projects/Contexts: [[Cross-Platform Game Engines]], [[Skybound Mobile Port]] +* Related Topics: High-Performance-Mobile-Development, C++ Interop, JS Engine Architecture +* Projects/Contexts: Cross-Platform Game Engines, Skybound Mobile Port * Contradictions/Notes: While JSI significantly improves speed, it requires more advanced C++ knowledge to implement custom host objects compared to the old bridge. Last updated: 2026-04-18 diff --git a/01_Archive/2026-04-20/React Performance Optimization.md b/01_Archive/2026-04-20/React Performance Optimization.md index 7f76fce0..84c52166 100644 --- a/01_Archive/2026-04-20/React Performance Optimization.md +++ b/01_Archive/2026-04-20/React Performance Optimization.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-B068E2 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - React Performance Optimization" --- -# [[React Performance Optimization]] +# [[React Performance Optimization|React Performance Optimization]] ## 📌 한 줄 통찰 (The Karpathy Summary) > React 애플리케이션에서 불필요한 렌더링을 줄이고, 자바스크립트 번들 크기를 최소화하며, 상태 관리 및 렌더링 파이프라인을 효율적으로 구성하여 빠르고 매끄러운 사용자 경험(UX)과 우수한 Core Web Vitals 지표를 달성하는 핵심 기술 및 아키텍처 전략입니다. @@ -30,12 +30,12 @@ github_commit: "[P-Reinforce] Continuous Worker - React Performance Optimization - **정책 변화:** Design & Experience 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[React 19 Compiler]], [[재조정 (Reconciliation)]], [[상태 관리 최적화 (Zustand, Jotai, Valtio)]], [[Code Splitting & Lazy Loading]], [[React Server Components (RSC)]] -- **Projects/Contexts:** [[대규모 E-commerce 및 대시보드 애플리케이션 구축]], [[고성능 멀티스레드 React 앱 아키텍처]], [[Next.js 기반 App Router 마이그레이션]] +- **Related Topics:** [[React 19 Compiler|React 19 Compiler]], [[재조정 (Reconciliation)|재조정 (Reconciliation)]], [[상태 관리 최적화 (Zustand, Jotai, Valtio)|상태 관리 최적화 (Zustand, Jotai, Valtio)]], Code Splitting & Lazy Loading, [[React Server Components (RSC)|React Server Components (RSC)]] +- **Projects/Contexts:** 대규모 E-commerce 및 대시보드 애플리케이션 구축, [[고성능 멀티스레드 React 앱 아키텍처|고성능 멀티스레드 React 앱 아키텍처]], Next.js 기반 App Router 마이그레이션 - **Contradictions/Notes:** 많은 개발자들이 컴포넌트가 느려지면 습관적으로 `useMemo`나 `React.memo`를 추가(Premature Memoization)하지만, 메모이제이션 자체에도 얕은 비교(Shallow Compare)라는 오버헤드가 발생합니다. 렌더링 자체가 빠르고 프롭스 변경이 빈번한 단순 컴포넌트에 이를 남용하면 오히려 메모리와 연산 자원만 낭비하므로 반드시 React DevTools Profiler로 측정한 후 적용해야 합니다. 또한 React 19 컴파일러가 아무리 자동화를 해주어도, 무분별한 상태 구조 등 근본적인 아키텍처 설계 결함을 고쳐주지는 않습니다. --- _Last updated: 2026-04-14_ -- Raw Source: [[00_Raw/2026-04-20/React Performance Optimization.md]] +- Raw Source: 00_Raw/2026-04-20/React Performance Optimization.md --- diff --git a/01_Archive/2026-04-20/React Three Fiber (R3F).md b/01_Archive/2026-04-20/React Three Fiber (R3F).md index bad68b0c..d24f0e59 100644 --- a/01_Archive/2026-04-20/React Three Fiber (R3F).md +++ b/01_Archive/2026-04-20/React Three Fiber (R3F).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-979529 -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - React Three Fiber (R3F)" --- -# [[React Three Fiber (R3F)]] +# [[React Three Fiber (R3F)|React Three Fiber (R3F)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > React Three Fiber(R3F)는 Three.js에 React의 렌더링 패러다임과 멘탈 모델을 더해주는 라이브러리입니다 [1]. WebGPU와 같은 최신 렌더링 기술을 지원하며 비동기 `gl` prop 팩토리를 통해 원활하게 통합할 수 있어 건축 대시보드와 같은 환경에서 유용하게 사용됩니다 [2]. 하지만 React 특유의 상태 기반 렌더링 방식으로 인해 고유한 성능 문제(pitfalls)가 발생할 수 있으므로 렌더링과 메모리 관리에 세심한 주의가 필요합니다 [1]. @@ -23,11 +23,11 @@ github_commit: "[P-Reinforce] Continuous Worker - React Three Fiber (R3F)" - **정책 변화:** Graphics & Performance 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Three.js]], [[WebGPU]], [[Drei]] -- **Projects/Contexts:** [[React-based construction dashboards]] +- **Related Topics:** [[Three.js|Three.js]], [[WebGPU|WebGPU]], Drei +- **Projects/Contexts:** React-based construction dashboards - **Contradictions/Notes:** 소스 내에서 상충되는 주장은 없으나, R3F가 React 기반임에도 불구하고 렌더링 루프 최적화를 위해 React의 핵심 패턴 중 하나인 상태 변경(`setState`)을 `useFrame` 안에서 피하라고 경고하는 등 [1] 패러다임 간의 조율이 필요하다는 점을 강조합니다. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/React Three Fiber (R3F).md]] +- Raw Source: 00_Raw/2026-04-20/React Three Fiber (R3F).md --- diff --git a/01_Archive/2026-04-20/React Three Fiber 자산 최적화 (Asset Optimization).md b/01_Archive/2026-04-20/React Three Fiber 자산 최적화 (Asset Optimization).md index f4748777..99843660 100644 --- a/01_Archive/2026-04-20/React Three Fiber 자산 최적화 (Asset Optimization).md +++ b/01_Archive/2026-04-20/React Three Fiber 자산 최적화 (Asset Optimization).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-C16818 -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - React Three Fiber 자산 최적화 (Asset Optimization)" --- -# [[React Three Fiber 자산 최적화 (Asset Optimization)]] +# [[React Three Fiber 자산 최적화 (Asset Optimization)|React Three Fiber 자산 최적화 (Asset Optimization)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > React Three Fiber(R3F) 환경에서 3D 모델(GLTF), 텍스처 등의 자산 크기를 대폭 줄이고, GPU 메모리 점유를 최소화하며 초기 로딩 속도와 렌더링 성능을 극대화하기 위한 압축 및 파이프라인 관리 기법입니다. @@ -39,12 +39,12 @@ github_commit: "[P-Reinforce] Continuous Worker - React Three Fiber 자산 최 - **정책 변화:** Graphics & Performance 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Code Splitting & Lazy Loading]], [[Draw Call Optimization (드로우 콜 최적화)]], [[Memory Leak Prevention (메모리 누수 방지)]], [[웹 워커(Web Worker)]] -- **Projects/Contexts:** [[대규모 WebGL/R3F 3D 쇼핑몰 제품 컨피규레이터]], [[모바일 환경을 타겟으로 하는 웹 기반 3D 게임]] +- **Related Topics:** Code Splitting & Lazy Loading, Draw Call Optimization (드로우 콜 최적화), [[Memory Leak Prevention 메모리 누수 방지|Memory Leak Prevention (메모리 누수 방지)]], 웹 워커(Web Worker) +- **Projects/Contexts:** 대규모 WebGL/R3F 3D 쇼핑몰 제품 컨피규레이터, 모바일 환경을 타겟으로 하는 웹 기반 3D 게임 - **Contradictions/Notes:** 지오메트리나 텍스처를 과도하게 압축(Draco, KTX2)하면 다운로드되는 파일 크기와 GPU 메모리는 대폭 줄어들지만, 클라이언트의 웹 워커에서 이를 압축 해제(Decompression)하는 과정에서 CPU 연산 비용과 디코더 로딩 지연이 발생합니다. 따라서, 복잡도가 낮고 빠른 즉각적 렌더링이 필요한 에셋의 경우 오히려 압축 없이 원본을 사용하는 것이 TTI(Time to Interactive) 면에서 더 유리할 수도 있으므로 Trade-off를 고려해야 합니다. --- _Last updated: 2026-04-14_ -- Raw Source: [[00_Raw/2026-04-20/React Three Fiber 자산 최적화 (Asset Optimization).md]] +- Raw Source: 00_Raw/2026-04-20/React Three Fiber 자산 최적화 (Asset Optimization).md --- diff --git a/01_Archive/2026-04-20/React Three Fiber에서 Rapier 물리 엔진 최적화하기.md b/01_Archive/2026-04-20/React Three Fiber에서 Rapier 물리 엔진 최적화하기.md index 029580c6..fbf10351 100644 --- a/01_Archive/2026-04-20/React Three Fiber에서 Rapier 물리 엔진 최적화하기.md +++ b/01_Archive/2026-04-20/React Three Fiber에서 Rapier 물리 엔진 최적화하기.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-95FEB9 -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - React Three Fiber에서 Rapier 물리 엔진 최적화하기" --- -# [[React Three Fiber에서 Rapier 물리 엔진 최적화하기]] +# [[React Three Fiber에서 Rapier 물리 엔진 최적화하기|React Three Fiber에서 Rapier 물리 엔진 최적화하기]] ## 📌 한 줄 통찰 (The Karpathy Summary) > React Three Fiber(R3F) 환경에서 `@react-three/rapier`를 사용할 때, 대규모 `InstancedRigidBodies` 적용, 비트마스크 기반의 충돌 필터링, Rust 메모리 에러 방지를 위한 상태 캐싱, 그리고 렌더링 루프 분리를 통해 연산 오버헤드를 극적으로 줄이는 고성능 물리 엔진 최적화 기법입니다. @@ -28,12 +28,12 @@ github_commit: "[P-Reinforce] Continuous Worker - React Three Fiber에서 Rapier - **정책 변화:** Graphics & Performance 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[InstancedMesh (드로우 콜 최적화)]], [[Web Worker (웹 워커)]], [[Garbage Collection (GC) 최적화]], [[Object Pooling (오브젝트 풀링)]] -- **Projects/Contexts:** [[고성능 실시간 상호작용 시스템을 위한 React 기반 게임 엔진 아키텍처]] +- **Related Topics:** [[InstancedMesh (드로우 콜 최적화)|InstancedMesh (드로우 콜 최적화)]], [[Web Worker (웹 워커)|Web Worker (웹 워커)]], [[Garbage Collection (GC) 최적화|Garbage Collection (GC) 최적화]], [[Object Pooling (오브젝트 풀링)|Object Pooling (오브젝트 풀링)]] +- **Projects/Contexts:** [[고성능 실시간 상호작용 시스템을 위한 React 기반 게임 엔진 아키텍처|고성능 실시간 상호작용 시스템을 위한 React 기반 게임 엔진 아키텍처]] - **Contradictions/Notes:** Rapier의 스냅샷(Snapshot) 기능(`world.takeSnapshot()`)을 이용해 물리 세계의 상태를 저장하고 복원할 수 있지만, 복원 시점의 객체 생성 순서나 식별자가 스냅샷 캡처 시점과 정확히 일치하지 않으면 RigidBody들이 엉키는(Scramble) 버그가 발생하므로 상태 직렬화에 각별한 주의가 필요합니다. --- _Last updated: 2026-04-15_ -- Raw Source: [[00_Raw/2026-04-20/React Three Fiber에서 Rapier 물리 엔진 최적화하기.md]] +- Raw Source: 00_Raw/2026-04-20/React Three Fiber에서 Rapier 물리 엔진 최적화하기.md --- diff --git a/01_Archive/2026-04-20/React 게임 엔진 아키텍처.md b/01_Archive/2026-04-20/React 게임 엔진 아키텍처.md index 6d5d172c..fed6d28d 100644 --- a/01_Archive/2026-04-20/React 게임 엔진 아키텍처.md +++ b/01_Archive/2026-04-20/React 게임 엔진 아키텍처.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-D1ED6C -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - React 게임 엔진 아키텍처" --- -# [[React 게임 엔진 아키텍처]] +# [[React 게임 엔진 아키텍처|React 게임 엔진 아키텍처]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - React 게임 엔진 아키텍 ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/React 게임 엔진 아키텍처.md]] +- Raw Source: 00_Raw/2026-04-20/React 게임 엔진 아키텍처.md --- diff --git a/01_Archive/2026-04-20/React 기반 게임 엔진 아키텍처.md b/01_Archive/2026-04-20/React 기반 게임 엔진 아키텍처.md index 1d41f3e4..469f4ec4 100644 --- a/01_Archive/2026-04-20/React 기반 게임 엔진 아키텍처.md +++ b/01_Archive/2026-04-20/React 기반 게임 엔진 아키텍처.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-1B0F24 -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - React 기반 게임 엔진 아키텍처" --- -# [[React 기반 게임 엔진 아키텍처]] +# [[React 기반 게임 엔진 아키텍처|React 기반 게임 엔진 아키텍처]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - React 기반 게임 엔진 아 ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/React 기반 게임 엔진 아키텍처.md]] +- Raw Source: 00_Raw/2026-04-20/React 기반 게임 엔진 아키텍처.md --- diff --git a/01_Archive/2026-04-20/React 동시성 기능 (Concurrent Features).md b/01_Archive/2026-04-20/React 동시성 기능 (Concurrent Features).md index f9277c95..d75798c0 100644 --- a/01_Archive/2026-04-20/React 동시성 기능 (Concurrent Features).md +++ b/01_Archive/2026-04-20/React 동시성 기능 (Concurrent Features).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-A689F7 -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - React 동시성 기능 (Concurrent Features)" --- -# [[React 동시성 기능 (Concurrent Features)]] +# [[React 동시성 기능 (Concurrent Features)|React 동시성 기능 (Concurrent Features)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - React 동시성 기능 (Concur ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/React 동시성 기능 (Concurrent Features).md]] +- Raw Source: 00_Raw/2026-04-20/React 동시성 기능 (Concurrent Features).md --- diff --git a/01_Archive/2026-04-20/React 및 Next.js 개발 환경.md b/01_Archive/2026-04-20/React 및 Next.js 개발 환경.md index 205afad7..083968be 100644 --- a/01_Archive/2026-04-20/React 및 Next.js 개발 환경.md +++ b/01_Archive/2026-04-20/React 및 Next.js 개발 환경.md @@ -1,4 +1,4 @@ -# [[React 및 Next.js 개발 환경]] +# [[React 및 Next.js 개발 환경|React 및 Next.js 개발 환경]] ## 📌 Brief Summary React 및 Next.js 개발 환경은 코드의 일관성과 품질을 유지하기 위해 정적 분석 도구와 포맷터를 적극적으로 활용하는 생태계이다 [1, 2]. 주로 ESLint를 통해 React 및 Next.js 특화 문법과 구조적 오류를 검사하고, Prettier를 통해 코드 스타일을 통일한다 [3, 4]. 대규모 프로젝트에서는 Turborepo와 같은 모노레포 도구와 Husky, lint-staged를 결합하여 개발 생산성을 높이고 효율적인 린팅 파이프라인을 구축한다 [5-7]. @@ -16,8 +16,8 @@ React 및 Next.js 개발 환경은 코드의 일관성과 품질을 유지하기 코드 저장소에 푸시되거나 커밋되기 전에 React 및 Next.js 코드 컨벤션이 강제되도록 `Husky`를 활용하여 Git 훅(pre-commit 등)을 설정한다 [19-21]. 여기에 `lint-staged`를 결합하면 변경되어 스테이징된 파일들에만 한정하여 ESLint와 Prettier를 실행하므로, 방대한 코드베이스에서도 1~2초 만에 검사를 완료하여 개발 흐름의 지연을 막을 수 있다 [6, 22]. ## 🔗 Knowledge Connections -- **Related Topics:** [[ESLint]], [[Prettier]], [[Turborepo]], [[Husky 및 lint-staged]] -- **Projects/Contexts:** [[Next.js 애플리케이션 및 모노레포 구축]], [[React 컴포넌트 개발 환경]] +- **Related Topics:** [[ESLint|ESLint]], [[Prettier|Prettier]], [[Turborepo|Turborepo]], Husky 및 lint-staged +- **Projects/Contexts:** Next.js 애플리케이션 및 모노레포 구축, React 컴포넌트 개발 환경 - **Contradictions/Notes:** ESLint와 Prettier를 함께 사용할 때 `eslint-plugin-prettier`를 사용하여 Prettier 규칙을 ESLint 내에서 실행하는 방식이 존재하나, 에디터상에 오류 밑줄이 과도하게 표시되거나 단독 실행보다 처리 속도가 느려지는 단점이 있어 Prettier 공식 문서 및 일부 실무 환경에서는 이를 지양하고 `eslint-config-prettier`만 적용할 것을 권장하기도 한다 [12, 23]. --- diff --git a/01_Archive/2026-04-20/React 및 Nextjs 개발 환경.md b/01_Archive/2026-04-20/React 및 Nextjs 개발 환경.md index b7193459..72ad64b4 100644 --- a/01_Archive/2026-04-20/React 및 Nextjs 개발 환경.md +++ b/01_Archive/2026-04-20/React 및 Nextjs 개발 환경.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-2C5A84 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - React 및 Nextjs 개발 환경" --- -# [[React 및 Nextjs 개발 환경]] +# [[React 및 Nextjs 개발 환경|React 및 Nextjs 개발 환경]] ## 📌 한 줄 통찰 (The Karpathy Summary) > React 및 Next.js 개발 환경은 코드의 일관성과 품질을 유지하기 위해 정적 분석 도구와 포맷터를 적극적으로 활용하는 생태계이다 [1, 2]. 주로 ESLint를 통해 React 및 Next.js 특화 문법과 구조적 오류를 검사하고, Prettier를 통해 코드 스타일을 통일한다 [3, 4]. 대규모 프로젝트에서는 Turborepo와 같은 모노레포 도구와 Husky, lint-staged를 결합하여 개발 생산성을 높이고 효율적인 린팅 파이프라인을 구축한다 [5-7]. @@ -29,11 +29,11 @@ github_commit: "[P-Reinforce] Continuous Worker - React 및 Nextjs 개발 환경 - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[ESLint]], [[Prettier]], [[Turborepo]], [[Husky 및 lint-staged]] -- **Projects/Contexts:** [[Next.js 애플리케이션 및 모노레포 구축]], [[React 컴포넌트 개발 환경]] +- **Related Topics:** [[ESLint|ESLint]], [[Prettier|Prettier]], [[Turborepo|Turborepo]], Husky 및 lint-staged +- **Projects/Contexts:** Next.js 애플리케이션 및 모노레포 구축, React 컴포넌트 개발 환경 - **Contradictions/Notes:** ESLint와 Prettier를 함께 사용할 때 `eslint-plugin-prettier`를 사용하여 Prettier 규칙을 ESLint 내에서 실행하는 방식이 존재하나, 에디터상에 오류 밑줄이 과도하게 표시되거나 단독 실행보다 처리 속도가 느려지는 단점이 있어 Prettier 공식 문서 및 일부 실무 환경에서는 이를 지양하고 `eslint-config-prettier`만 적용할 것을 권장하기도 한다 [12, 23]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/React 및 Next.js 개발 환경.md]] +- Raw Source: 00_Raw/2026-04-20/React 및 Next.js 개발 환경.md --- diff --git a/01_Archive/2026-04-20/React 상태 관리 (React State Management).md b/01_Archive/2026-04-20/React 상태 관리 (React State Management).md index 102ec073..6d0a0ae3 100644 --- a/01_Archive/2026-04-20/React 상태 관리 (React State Management).md +++ b/01_Archive/2026-04-20/React 상태 관리 (React State Management).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-3FAE48 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - React 상태 관리 (React State Management)" --- -# [[React 상태 관리 (React State Management)]] +# [[React 상태 관리 (React State Management)|React 상태 관리 (React State Management)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > React 상태 관리(React State Management)는 사용자 입력, API 응답, UI 설정 등 애플리케이션 내에서 시간에 따라 변화하는 데이터를 추적하고 유지하는 과정입니다 [1]. 타입스크립트 환경의 React에서는 구분된 유니언(Discriminated Unions)과 불변성(Immutability) 패턴을 활용하여 유효하지 않은 상태를 원천적으로 차단하는 것에 중점을 둡니다 [2-4]. 전반적인 React 자체의 상태 관리 메커니즘이나 라이브러리 생태계에 대해서는 소스에 관련 정보가 부족합니다. @@ -29,11 +29,11 @@ github_commit: "[P-Reinforce] Continuous Worker - React 상태 관리 (React Sta - **정책 변화:** Design & Experience 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Discriminated Unions]], [[Immutability]], [[State Machine Pattern]] -- **Projects/Contexts:** [[Redux-style Reducers]], [[Context API]] +- **Related Topics:** [[Discriminated Unions|Discriminated Unions]], [[불변성 (Immutability)|Immutability]], State Machine Pattern +- **Projects/Contexts:** Redux-style Reducers, [[Context API|Context API]] - **Contradictions/Notes:** 소스 문서는 React 프레임워크 자체의 상태 관리 동작 원리(예: Virtual DOM과의 관계, 훅의 내부 원리 등)를 깊이 있게 다루기보다는, TypeScript의 타입 시스템(구분된 유니언, 불변성 등)을 React 상태 관리에 어떻게 접목하여 안정성을 높이는지에 초점이 맞추어져 있습니다. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/React 상태 관리 (React State Management).md]] +- Raw Source: 00_Raw/2026-04-20/React 상태 관리 (React State Management).md --- diff --git a/01_Archive/2026-04-20/React 상태 관리 및 API 응답 처리.md b/01_Archive/2026-04-20/React 상태 관리 및 API 응답 처리.md index f5143aec..16a77477 100644 --- a/01_Archive/2026-04-20/React 상태 관리 및 API 응답 처리.md +++ b/01_Archive/2026-04-20/React 상태 관리 및 API 응답 처리.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-3E04B1 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - React 상태 관리 및 API 응답 처리" --- -# [[React 상태 관리 및 API 응답 처리]] +# [[React 상태 관리 및 API 응답 처리|React 상태 관리 및 API 응답 처리]] ## 📌 한 줄 통찰 (The Karpathy Summary) > React 애플리케이션에서 상태 관리 및 API 응답 처리를 다룰 때, TypeScript의 식별 가능한 유니온(Discriminated Unions) 패턴을 활용하면 매우 효과적입니다 [1, 2]. 이 패턴은 상태의 유효하지 않은 조합을 원천적으로 불가능하게 만들고 컴파일러를 통해 안전한 타입 좁히기를 제공합니다 [3, 4]. 결과적으로 비동기 로딩, 성공, 에러 등의 API 응답 상태와 복잡한 UI 상태를 철저하게 제어하고 예측 가능하게 만들어 줍니다 [2, 5]. @@ -24,11 +24,11 @@ github_commit: "[P-Reinforce] Continuous Worker - React 상태 관리 및 API - **정책 변화:** Design & Experience 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Discriminated Unions]], [[State Machine Pattern]], [[TypeScript]] -- **Projects/Contexts:** [[비동기 작업 패턴(Async Operations Pattern)]], [[Redux 스타일 리듀서(Redux-style reducers)]] +- **Related Topics:** [[Discriminated Unions|Discriminated Unions]], State Machine Pattern, [[TypeScript 라이브러리 타입 확장|TypeScript]] +- **Projects/Contexts:** 비동기 작업 패턴(Async Operations Pattern), Redux 스타일 리듀서(Redux-style reducers) - **Contradictions/Notes:** 소스에 관련 정보가 부족합니다. (React 상태 관리 및 API 응답 처리와 관련하여 소스 간의 상충되는 주장이 포함되어 있지 않습니다.) --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/React 상태 관리 및 API 응답 처리.md]] +- Raw Source: 00_Raw/2026-04-20/React 상태 관리 및 API 응답 처리.md --- diff --git a/01_Archive/2026-04-20/React 재조정 (Reconciliation) 최적화.md b/01_Archive/2026-04-20/React 재조정 (Reconciliation) 최적화.md index 516c711c..8bcafc76 100644 --- a/01_Archive/2026-04-20/React 재조정 (Reconciliation) 최적화.md +++ b/01_Archive/2026-04-20/React 재조정 (Reconciliation) 최적화.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-E6A358 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - React 재조정 (Reconciliation) 최적화" --- -# [[React 재조정 (Reconciliation) 최적화]] +# [[React 재조정 (Reconciliation) 최적화|React 재조정 (Reconciliation) 최적화]] ## 📌 한 줄 통찰 (The Karpathy Summary) > React 재조정(Reconciliation) 최적화는 React가 가상 DOM 트리를 비교(Diffing)하여 실제 DOM에 적용할 최소한의 변경 사항을 계산하는 과정에서 발생하는 CPU 오버헤드와 불필요한 렌더링을 줄여 애플리케이션의 성능과 반응성을 극대화하는 아키텍처 및 코딩 기법입니다. @@ -40,12 +40,12 @@ github_commit: "[P-Reinforce] Continuous Worker - React 재조정 (Reconciliatio - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[가상 DOM (Virtual DOM)]], [[React 19 Compiler]], [[불필요한 리렌더링 방지]], [[명령형 직접 조작 (Imperative Manipulation)]] -- **Projects/Contexts:** [[고성능 실시간 상호작용 시스템을 위한 React 기반 게임 엔진 아키텍처]], [[대규모 데이터 렌더링 및 가상화 최적화]] +- **Related Topics:** [[가상 DOM (Virtual DOM)|가상 DOM (Virtual DOM)]], [[React 19 Compiler|React 19 Compiler]], [[불필요한 리렌더링 방지|불필요한 리렌더링 방지]], [[명령형 직접 조작 (Imperative Manipulation)|명령형 직접 조작 (Imperative Manipulation)]] +- **Projects/Contexts:** [[고성능 실시간 상호작용 시스템을 위한 React 기반 게임 엔진 아키텍처|고성능 실시간 상호작용 시스템을 위한 React 기반 게임 엔진 아키텍처]], [[대규모 데이터 렌더링 및 가상화 최적화|대규모 데이터 렌더링 및 가상화 최적화]] - **Contradictions/Notes:** React 19의 컴파일러가 도입되면서 `useMemo`나 `useCallback`과 같은 수동 참조 안정화 작업의 대부분을 빌드 타임에 자동으로 처리해 줍니다. 하지만 이는 구조적으로 순수한 컴포넌트에서만 완벽히 동작하며, 거대한 컴포넌트 트리, 불안정한 Key 배열, 과도한 Context 사용과 같은 잘못된 아키텍처 설계 자체를 고쳐주지는 못하므로 여전히 개발자의 구조 최적화 역량이 중요합니다. --- _Last updated: 2026-04-15_ -- Raw Source: [[00_Raw/2026-04-20/React 재조정 (Reconciliation) 최적화.md]] +- Raw Source: 00_Raw/2026-04-20/React 재조정 (Reconciliation) 최적화.md --- diff --git a/01_Archive/2026-04-20/React 컴포넌트 Props 검증.md b/01_Archive/2026-04-20/React 컴포넌트 Props 검증.md index b5973ce4..50b74994 100644 --- a/01_Archive/2026-04-20/React 컴포넌트 Props 검증.md +++ b/01_Archive/2026-04-20/React 컴포넌트 Props 검증.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-F45907 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - React 컴포넌트 Props 검증" --- -# [[React 컴포넌트 Props 검증]] +# [[React 컴포넌트 Props 검증|React 컴포넌트 Props 검증]] ## 📌 한 줄 통찰 (The Karpathy Summary) > React 컴포넌트 Props 검증은 TypeScript를 활용하여 컴포넌트에 전달되는 속성(Props)의 타입 안전성을 보장하고, 유효하지 않은 상태 표현을 원천적으로 차단하는 과정입니다 [1, 2]. 컴파일 타임에는 식별 가능한 유니온(Discriminated Unions)과 초과 속성 검사 등의 기법으로 잘못된 Props 조합을 방지하며, 런타임에는 외부 데이터에 대한 추가적인 유효성 검사를 수행하여 안정성을 확보합니다 [3-5]. @@ -25,11 +25,11 @@ github_commit: "[P-Reinforce] Continuous Worker - React 컴포넌트 Props 검 - **정책 변화:** Design & Experience 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Discriminated Unions]], [[Exclusive Props]], [[Excess Property Checking]], [[Zod 런타임 검증]], [[satisfies 연산자]] -- **Projects/Contexts:** [[React 상태 및 Props 관리]], [[외부 API 데이터 연동 컴포넌트]] +- **Related Topics:** [[Discriminated Unions|Discriminated Unions]], Exclusive Props, [[Excess Property Checking|Excess Property Checking]], Zod 런타임 검증, [[satisfies 연산자|satisfies 연산자]] +- **Projects/Contexts:** React 상태 및 Props 관리, 외부 API 데이터 연동 컴포넌트 - **Contradictions/Notes:** TypeScript의 컴파일 타임 검사는 무결성을 보장하지만, 런타임에 외부(API, 설정 파일 등)에서 주입되는 잘못된 Props 데이터까지는 막아주지 못하므로 외부 데이터 연동 컴포넌트에서는 런타임 검증이 동반되어야 합니다 [4]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/React 컴포넌트 Props 검증.md]] +- Raw Source: 00_Raw/2026-04-20/React 컴포넌트 Props 검증.md --- diff --git a/01_Archive/2026-04-20/React 컴포넌트 Props 전달 및 상태 관리.md b/01_Archive/2026-04-20/React 컴포넌트 Props 전달 및 상태 관리.md index 4e893e5d..0e662888 100644 --- a/01_Archive/2026-04-20/React 컴포넌트 Props 전달 및 상태 관리.md +++ b/01_Archive/2026-04-20/React 컴포넌트 Props 전달 및 상태 관리.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-F29466 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - React 컴포넌트 Props 전달 및 상태 관리" --- -# [[React 컴포넌트 Props 전달 및 상태 관리]] +# [[React 컴포넌트 Props 전달 및 상태 관리|React 컴포넌트 Props 전달 및 상태 관리]] ## 📌 한 줄 통찰 (The Karpathy Summary) > React 컴포넌트의 Props 전달과 상태 관리는 애플리케이션의 동작을 제어하고 컴포넌트 간 데이터를 교환하는 핵심 메커니즘입니다 [1, 2]. 올바른 Props 설계는 초과 속성으로 인한 불필요한 리렌더링과 런타임 경고를 방지하며, 효과적인 상태 관리는 유효하지 않은 상태를 원천 차단하여 예측 불가능한 동작이나 버그를 예방합니다 [3, 4]. TypeScript의 식별 가능한 유니언(Discriminated Unions)과 초과 속성 검사(Excess Property Checking) 같은 기능을 활용하면 타입 안전성이 보장된 견고한 React 애플리케이션을 구축할 수 있습니다 [1, 4-6]. @@ -33,11 +33,11 @@ github_commit: "[P-Reinforce] Continuous Worker - React 컴포넌트 Props 전 - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Discriminated Unions]], [[Excess Property Checking]], [[Runtime Validation (Zod)]] -- **Projects/Contexts:** [[Redux-style Reducers]], [[React Component Library]] +- **Related Topics:** [[Discriminated Unions|Discriminated Unions]], [[Excess Property Checking|Excess Property Checking]], Runtime Validation (Zod) +- **Projects/Contexts:** Redux-style Reducers, React Component Library - **Contradictions/Notes:** React props 타입 정의 시 기본적인 사용에 있어 `interface`와 `type` 간의 실질적 큰 차이는 없으나, TypeScript는 캐싱과 성능 최적화 측면에서 교집합(&)보다는 `interface extends`의 사용을 권장합니다 [7, 8, 13]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/React 컴포넌트 Props 전달 및 상태 관리.md]] +- Raw Source: 00_Raw/2026-04-20/React 컴포넌트 Props 전달 및 상태 관리.md --- diff --git a/01_Archive/2026-04-20/Readonly Type.md b/01_Archive/2026-04-20/Readonly Type.md index b386e75f..3f2db17c 100644 --- a/01_Archive/2026-04-20/Readonly Type.md +++ b/01_Archive/2026-04-20/Readonly Type.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-EDA6A3 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Readonly Type" --- -# [[Readonly Type]] +# [[Readonly Type|Readonly Type]] ## 📌 한 줄 통찰 (The Karpathy Summary) > TypeScript의 `Readonly Type` (또는 `readonly` 수식어)은 객체의 속성, 배열 등이 초기화된 이후 수정되는 것을 방지하여 타입 수준에서 불변성(Immutability)을 강제하는 기능입니다[1, 2]. 이는 런타임 오버헤드 없이 컴파일 타임에 예기치 않은 데이터의 변이를 차단하며, 변수의 재할당을 막는 `const`나 런타임 동작인 `Object.freeze()`와 구별됩니다[3-5]. 주로 설정 객체, API 응답, 상태 관리 등 변경되지 않아야 하는 데이터 구조를 보호하는 데 사용됩니다[6, 7]. @@ -29,11 +29,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Readonly Type" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Immutability]], [[Utility Types]], [[DeepReadonly]], [[Object.freeze()]], [[Mapped Types]] -- **Projects/Contexts:** [[Functional Programming]], [[State Management]] +- **Related Topics:** [[불변성 (Immutability)|Immutability]], Utility Types, [[DeepReadonly|DeepReadonly]], Object.freeze(), [[Mapped-Types|Mapped Types]] +- **Projects/Contexts:** [[Functional Programming|Functional Programming]], [[상태 관리(State Management)|State Management]] - **Contradictions/Notes:** 자바스크립트의 `const`는 변수 자체의 재할당을 막고 객체 내부 속성의 변경은 허용하지만, TypeScript의 `readonly`는 객체 내부 속성의 변경을 막습니다[4, 19]. 또한 `Object.freeze()`는 런타임에 얕은 동결을 수행하지만, `readonly`는 런타임 성능 비용 없이 컴파일 타임에만 엄격하게 검사한다는 차이가 있습니다[5, 20, 21]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/Readonly Type.md]] +- Raw Source: 00_Raw/2026-04-20/Readonly Type.md --- diff --git a/01_Archive/2026-04-20/Readonly 유틸리티 타입.md b/01_Archive/2026-04-20/Readonly 유틸리티 타입.md index c358217b..eb8eeb45 100644 --- a/01_Archive/2026-04-20/Readonly 유틸리티 타입.md +++ b/01_Archive/2026-04-20/Readonly 유틸리티 타입.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-33C0BF -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Readonly 유틸리티 타입" --- -# [[Readonly 유틸리티 타입]] +# [[Readonly 유틸리티 타입|Readonly 유틸리티 타입]] ## 📌 한 줄 통찰 (The Karpathy Summary) > Readonly 유틸리티 타입(`Readonly`)은 TypeScript에서 특정 객체 타입의 모든 속성에 `readonly` 수식어를 추가하여 초기화 이후 값을 재할당할 수 없도록 변환하는 기능입니다[1, 2]. 이는 런타임 성능 저하 없이 컴파일 타임에만 엄격하게 불변성을 강제하여, 의도치 않은 데이터 변형으로 인한 버그를 사전에 차단합니다[3, 4]. 단, 최상위 속성에만 적용되는 얕은(shallow) 불변성만을 제공하므로, 중첩된 객체를 완전히 동결하려면 재귀적인 형태의 딥 리드온리(Deep Readonly) 패턴이 별도로 필요합니다[5, 6]. @@ -32,11 +32,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Readonly 유틸리티 타입" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[불변성(Immutability)]], [[매핑된 타입(Mapped Types)]], [[DeepReadonly]] +- **Related Topics:** [[불변성(Immutability)|불변성(Immutability)]], 매핑된 타입(Mapped Types), [[DeepReadonly|DeepReadonly]] - **Projects/Contexts:** 변경 불가한 외부 API 응답 데이터 모델링, 상태 관리 시스템(Redux 리듀서 등)의 데이터 무결성 보장, 그리고 애플리케이션의 전역 환경 설정(Configuration) 객체 보호 맥락에서 광범위하게 쓰입니다[8, 17]. - **Contradictions/Notes:** TypeScript의 에일리어싱 한계로 인해 `readonly` 데이터가 `mutable` 타입을 요구하는 함수로 전달되어 내부에서 값이 변경될 위험이 존재하므로, 완전한 불변성을 지키려면 함수 시그니처 전반에 걸쳐 읽기 전용 파라미터를 강제하거나 데이터의 복사본을 넘기는 설계가 필요합니다[18, 19]. 또한, 모든 `readonly` 속성을 다시 수정 가능하게 되돌려야 할 때는 `Mutable`이라는 커스텀 헬퍼 타입을 만들어 매핑 수식어를 제거(`-readonly`)하는 방식으로 해결할 수 있습니다[6]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/Readonly 유틸리티 타입.md]] +- Raw Source: 00_Raw/2026-04-20/Readonly 유틸리티 타입.md --- diff --git a/01_Archive/2026-04-20/Real User Monitoring (RUM).md b/01_Archive/2026-04-20/Real User Monitoring (RUM).md index 3acc4360..ed1850be 100644 --- a/01_Archive/2026-04-20/Real User Monitoring (RUM).md +++ b/01_Archive/2026-04-20/Real User Monitoring (RUM).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-AB3C97 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Real User Monitoring (RUM)" --- -# [[Real User Monitoring (RUM)]] +# [[Real User Monitoring (RUM)|Real User Monitoring (RUM)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 실제 사용자 모니터링(RUM)은 웹사이트가 실행되는 동안 실제 사용자가 경험하는 성능 데이터를 직접 수집하는 방법입니다 [1]. 이는 통제된 환경에서 측정하는 실험실(Lab) 데이터와 달리, 성능 에이전트를 사용하여 사용자의 생생한 현장 데이터(Field Data)를 포착합니다 [1, 2]. RUM은 코어 웹 바이탈(Core Web Vitals)과 같은 주요 사용자 경험 지표를 측정하고 시간에 따른 성능 추이를 파악하는 데 필수적으로 활용됩니다 [3, 4]. @@ -31,11 +31,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Real User Monitoring (RUM)" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Field Data]], [[Core Web Vitals]], [[Chrome User Experience Report (CrUX)]], [[Synthetic Testing]] -- **Projects/Contexts:** [[Request Metrics]], [[DebugBear]] +- **Related Topics:** Field Data, [[Core Web Vitals|Core Web Vitals]], [[Chrome User Experience Report (CrUX)|Chrome User Experience Report (CrUX)]], [[Synthetic Testing|Synthetic Testing]] +- **Projects/Contexts:** Request Metrics, DebugBear - **Contradictions/Notes:** 현장 데이터를 수집하는 대표적인 도구인 CrUX는 데이터가 월별로 업데이트되고 도메인 전체로 요약되어 제공되는 반면, Request Metrics와 같은 전문 RUM 서비스는 지연 없이 현재 시점(right now)의 실시간 성능 데이터를 제공한다는 차이점이 있습니다 [10, 13]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Real User Monitoring (RUM).md]] +- Raw Source: 00_Raw/2026-04-20/Real User Monitoring (RUM).md --- diff --git a/01_Archive/2026-04-20/Real-Time-Game-Engines.md b/01_Archive/2026-04-20/Real-Time-Game-Engines.md index 0ffdab01..124a8315 100644 --- a/01_Archive/2026-04-20/Real-Time-Game-Engines.md +++ b/01_Archive/2026-04-20/Real-Time-Game-Engines.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-9DBB1E -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Real-Time-Game-Engines" --- -# [[Real-Time-Game-Engines]] +# [[Real-Time-Game-Engines|Real-Time-Game-Engines]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Real-Time-Game-Engines" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Real-Time-Game-Engines.md]] +- Raw Source: 00_Raw/2026-04-20/Real-Time-Game-Engines.md --- diff --git a/01_Archive/2026-04-20/Redstone Engineering.md b/01_Archive/2026-04-20/Redstone Engineering.md index 3bb66b17..6b7dcb2a 100644 --- a/01_Archive/2026-04-20/Redstone Engineering.md +++ b/01_Archive/2026-04-20/Redstone Engineering.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-F36E08 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Redstone Engineering" --- -# [[Redstone Engineering]] +# [[Redstone Engineering|Redstone Engineering]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Redstone Engineering" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Redstone Engineering.md]] +- Raw Source: 00_Raw/2026-04-20/Redstone Engineering.md --- diff --git a/01_Archive/2026-04-20/Redux 등 상태 관리 (State Management).md b/01_Archive/2026-04-20/Redux 등 상태 관리 (State Management).md index cbc1adb4..f3425c08 100644 --- a/01_Archive/2026-04-20/Redux 등 상태 관리 (State Management).md +++ b/01_Archive/2026-04-20/Redux 등 상태 관리 (State Management).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-8514DD -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Redux 등 상태 관리 (State Management)" --- -# [[Redux 등 상태 관리 (State Management)]] +# [[Redux 등 상태 관리 (State Management)|Redux 등 상태 관리 (State Management)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 상태 관리는 사용자 입력, API 응답, 애플리케이션 설정 등 시간에 따라 변화하는 데이터를 추적하고 유지하는 방법론입니다 [1]. 상태 관리를 잘못하면 예측 불가능한 동작, 디버깅의 어려움, 기술 부채 축적 및 성능 문제(불필요한 리렌더링 등)가 발생할 수 있습니다 [2]. TypeScript 환경에서는 Redux 스타일의 리듀서와 액션을 안전하게 제어하기 위해 식별 가능한 유니온(Discriminated Unions)과 읽기 전용(Readonly) 타입을 활용한 불변성 유지가 상태 관리의 핵심 패턴으로 사용됩니다 [3-6]. @@ -22,11 +22,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Redux 등 상태 관리 (State - **정책 변화:** Design & Experience 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[식별 가능한 유니온 (Discriminated Unions)]], [[불변성 (Immutability)]], [[Readonly 타입]] -- **Projects/Contexts:** [[TypeScript 기반 React 애플리케이션의 Redux 스타일 리듀서 구현]] +- **Related Topics:** [[식별 가능한 유니온 (Discriminated Unions)|식별 가능한 유니온 (Discriminated Unions)]], [[불변성 (Immutability)|불변성 (Immutability)]], Readonly 타입 +- **Projects/Contexts:** TypeScript 기반 React 애플리케이션의 Redux 스타일 리듀서 구현 - **Contradictions/Notes:** 소스에서는 Redux 라이브러리 자체의 세부적인 API나 동작 원리보다는, TypeScript의 강력한 타입 시스템(식별 가능한 유니온, Readonly)을 결합하여 상태 관리의 복잡성과 부작용을 통제하는 아키텍처적 관점이 주로 강조되어 있습니다 [1, 3, 4, 7]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/Redux 등 상태 관리 (State Management).md]] +- Raw Source: 00_Raw/2026-04-20/Redux 등 상태 관리 (State Management).md --- diff --git a/01_Archive/2026-04-20/Redux 스타일 리듀서 및 액션 관리.md b/01_Archive/2026-04-20/Redux 스타일 리듀서 및 액션 관리.md index f0daa6cc..9d868b1c 100644 --- a/01_Archive/2026-04-20/Redux 스타일 리듀서 및 액션 관리.md +++ b/01_Archive/2026-04-20/Redux 스타일 리듀서 및 액션 관리.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-EFAFFE -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Redux 스타일 리듀서 및 액션 관리" --- -# [[Redux 스타일 리듀서 및 액션 관리]] +# [[Redux 스타일 리듀서 및 액션 관리|Redux 스타일 리듀서 및 액션 관리]] ## 📌 한 줄 통찰 (The Karpathy Summary) > Redux 스타일 리듀서 및 액션 관리는 TypeScript의 식별 가능한 유니언(Discriminated Unions) 패턴이 가장 효과적으로 적용되는 대표적인 사례 중 하나입니다 [1, 2]. 이 패턴을 통해 다양한 액션 객체들을 타입 안전하게 구분하고 상태를 처리할 수 있습니다. 다만, 제공된 소스에서는 이 주제가 식별 가능한 유니언의 단순 활용 예시로만 간략히 언급되어 있어 전반적인 Redux 아키텍처에 대해 논하기에는 소스에 관련 정보가 부족합니다. @@ -22,11 +22,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Redux 스타일 리듀서 및 - **정책 변화:** Design & Experience 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Discriminated Unions]], [[Type Narrowing]] -- **Projects/Contexts:** [[상태 관리 및 프레임워크의 액션 처리]] +- **Related Topics:** [[Discriminated Unions|Discriminated Unions]], [[Type Narrowing|Type Narrowing]] +- **Projects/Contexts:** 상태 관리 및 프레임워크의 액션 처리 - **Contradictions/Notes:** 소스에 관련 정보가 부족합니다. 소스는 Redux 자체에 대한 깊은 설명보다는 TypeScript의 타입 시스템을 설명하면서 그 예시로만 Redux를 간략하게 다루고 있습니다. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/Redux 스타일 리듀서 및 액션 관리.md]] +- Raw Source: 00_Raw/2026-04-20/Redux 스타일 리듀서 및 액션 관리.md --- diff --git a/01_Archive/2026-04-20/Redux-Reducer-Pattern.md b/01_Archive/2026-04-20/Redux-Reducer-Pattern.md index 0fc07bad..118c852a 100644 --- a/01_Archive/2026-04-20/Redux-Reducer-Pattern.md +++ b/01_Archive/2026-04-20/Redux-Reducer-Pattern.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-B7CB54 -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Redux-Reducer-Pattern" --- -# [[Redux-Reducer-Pattern]] +# [[Redux-Reducer-Pattern|Redux-Reducer-Pattern]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Redux-Reducer-Pattern" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Redux-Reducer-Pattern.md]] +- Raw Source: 00_Raw/2026-04-20/Redux-Reducer-Pattern.md --- diff --git a/01_Archive/2026-04-20/Redux-Reducers-Design.md b/01_Archive/2026-04-20/Redux-Reducers-Design.md index 9784b87c..807290cd 100644 --- a/01_Archive/2026-04-20/Redux-Reducers-Design.md +++ b/01_Archive/2026-04-20/Redux-Reducers-Design.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-4EB691 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Redux-Reducers-Design" --- -# [[Redux-Reducers-Design]] +# [[Redux-Reducers-Design|Redux-Reducers-Design]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Redux-Reducers-Design" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Redux-Reducers-Design.md]] +- Raw Source: 00_Raw/2026-04-20/Redux-Reducers-Design.md --- diff --git a/01_Archive/2026-04-20/Redux-Reducers.md b/01_Archive/2026-04-20/Redux-Reducers.md index 77a66dfa..aff1a797 100644 --- a/01_Archive/2026-04-20/Redux-Reducers.md +++ b/01_Archive/2026-04-20/Redux-Reducers.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-20A7B7 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Redux-Reducers" --- -# [[Redux-Reducers]] +# [[Redux-Reducers|Redux-Reducers]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Redux-Reducers" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Redux-Reducers.md]] +- Raw Source: 00_Raw/2026-04-20/Redux-Reducers.md --- diff --git a/01_Archive/2026-04-20/Redux-State-Management.md b/01_Archive/2026-04-20/Redux-State-Management.md index 962f9c3a..b7f14db1 100644 --- a/01_Archive/2026-04-20/Redux-State-Management.md +++ b/01_Archive/2026-04-20/Redux-State-Management.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-DBA4CB -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Redux-State-Management" --- -# [[Redux-State-Management]] +# [[Redux-State-Management|Redux-State-Management]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Redux-State-Management" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Redux-State-Management.md]] +- Raw Source: 00_Raw/2026-04-20/Redux-State-Management.md --- diff --git a/01_Archive/2026-04-20/Redux-Toolkit-Architecture.md b/01_Archive/2026-04-20/Redux-Toolkit-Architecture.md index 138d8750..65ae6d41 100644 --- a/01_Archive/2026-04-20/Redux-Toolkit-Architecture.md +++ b/01_Archive/2026-04-20/Redux-Toolkit-Architecture.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-5308B9 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Redux-Toolkit-Architecture" --- -# [[Redux-Toolkit-Architecture]] +# [[Redux-Toolkit-Architecture|Redux-Toolkit-Architecture]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Redux-Toolkit-Architecture" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Redux-Toolkit-Architecture.md]] +- Raw Source: 00_Raw/2026-04-20/Redux-Toolkit-Architecture.md --- diff --git a/01_Archive/2026-04-20/Regenerative Design.md b/01_Archive/2026-04-20/Regenerative Design.md index 8acaf1d5..6ec76e08 100644 --- a/01_Archive/2026-04-20/Regenerative Design.md +++ b/01_Archive/2026-04-20/Regenerative Design.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-6EFEA1 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Regenerative Design" --- -# [[Regenerative Design]] +# [[Regenerative Design|Regenerative Design]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Regenerative Design" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Regenerative Design.md]] +- Raw Source: 00_Raw/2026-04-20/Regenerative Design.md --- diff --git a/01_Archive/2026-04-20/Regenerative-Design.md b/01_Archive/2026-04-20/Regenerative-Design.md index c7affdd1..a9912da3 100644 --- a/01_Archive/2026-04-20/Regenerative-Design.md +++ b/01_Archive/2026-04-20/Regenerative-Design.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-9E754B -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Regenerative-Design" --- -# [[Regenerative-Design]] +# [[Regenerative-Design|Regenerative-Design]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Regenerative-Design" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Regenerative-Design.md]] +- Raw Source: 00_Raw/2026-04-20/Regenerative-Design.md --- diff --git a/01_Archive/2026-04-20/Rehabilitative-Medicine.md b/01_Archive/2026-04-20/Rehabilitative-Medicine.md index 471c45a5..18163239 100644 --- a/01_Archive/2026-04-20/Rehabilitative-Medicine.md +++ b/01_Archive/2026-04-20/Rehabilitative-Medicine.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-2E9085 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Rehabilitative-Medicine" --- -# [[Rehabilitative-Medicine]] +# [[Rehabilitative-Medicine|Rehabilitative-Medicine]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Rehabilitative-Medicine" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Rehabilitative-Medicine.md]] +- Raw Source: 00_Raw/2026-04-20/Rehabilitative-Medicine.md --- diff --git a/01_Archive/2026-04-20/Reinforcement Learning (RL).md b/01_Archive/2026-04-20/Reinforcement Learning (RL).md index 6ec2645e..ed7b262b 100644 --- a/01_Archive/2026-04-20/Reinforcement Learning (RL).md +++ b/01_Archive/2026-04-20/Reinforcement Learning (RL).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-81D53F -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Reinforcement Learning (RL)" --- -# [[Reinforcement Learning (RL)]] +# [[Reinforcement Learning (RL)|Reinforcement Learning (RL)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Reinforcement Learning (RL)" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Reinforcement Learning (RL).md]] +- Raw Source: 00_Raw/2026-04-20/Reinforcement Learning (RL).md --- diff --git a/01_Archive/2026-04-20/Reinforcement Learning Reward Shaping.md b/01_Archive/2026-04-20/Reinforcement Learning Reward Shaping.md index 8d8c5ee1..3f8437ec 100644 --- a/01_Archive/2026-04-20/Reinforcement Learning Reward Shaping.md +++ b/01_Archive/2026-04-20/Reinforcement Learning Reward Shaping.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-390731 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Reinforcement Learning Reward Shaping" --- -# [[Reinforcement Learning Reward Shaping]] +# [[Reinforcement Learning Reward Shaping|Reinforcement Learning Reward Shaping]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Reinforcement Learning Reward ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Reinforcement Learning Reward Shaping.md]] +- Raw Source: 00_Raw/2026-04-20/Reinforcement Learning Reward Shaping.md --- diff --git a/01_Archive/2026-04-20/Reinforcement Learning for Automated Playtesting.md b/01_Archive/2026-04-20/Reinforcement Learning for Automated Playtesting.md index 808eb5f3..a12c9f3a 100644 --- a/01_Archive/2026-04-20/Reinforcement Learning for Automated Playtesting.md +++ b/01_Archive/2026-04-20/Reinforcement Learning for Automated Playtesting.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-01F691 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Reinforcement Learning for Automated Playtesting" --- -# [[Reinforcement Learning for Automated Playtesting]] +# [[Reinforcement Learning for Automated Playtesting|Reinforcement Learning for Automated Playtesting]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Reinforcement Learning for Aut ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Reinforcement Learning for Automated Playtesting.md]] +- Raw Source: 00_Raw/2026-04-20/Reinforcement Learning for Automated Playtesting.md --- diff --git a/01_Archive/2026-04-20/Reinforcement Learning in Economics.md b/01_Archive/2026-04-20/Reinforcement Learning in Economics.md index b06c53f9..222d7584 100644 --- a/01_Archive/2026-04-20/Reinforcement Learning in Economics.md +++ b/01_Archive/2026-04-20/Reinforcement Learning in Economics.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-169C30 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Reinforcement Learning in Economics" --- -# [[Reinforcement Learning in Economics]] +# [[Reinforcement Learning in Economics|Reinforcement Learning in Economics]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Reinforcement Learning in Econ ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Reinforcement Learning in Economics.md]] +- Raw Source: 00_Raw/2026-04-20/Reinforcement Learning in Economics.md --- diff --git a/01_Archive/2026-04-20/Reinforcement Learning.md b/01_Archive/2026-04-20/Reinforcement Learning.md index b8c10a40..81d1525e 100644 --- a/01_Archive/2026-04-20/Reinforcement Learning.md +++ b/01_Archive/2026-04-20/Reinforcement Learning.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-AE51CB -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Reinforcement Learning" --- -# [[Reinforcement Learning]] +# [[Reinforcement Learning|Reinforcement Learning]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Reinforcement Learning" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Reinforcement Learning.md]] +- Raw Source: 00_Raw/2026-04-20/Reinforcement Learning.md --- diff --git a/01_Archive/2026-04-20/Reinforcement Schedules.md b/01_Archive/2026-04-20/Reinforcement Schedules.md index a5591a2f..e2ad7224 100644 --- a/01_Archive/2026-04-20/Reinforcement Schedules.md +++ b/01_Archive/2026-04-20/Reinforcement Schedules.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-8A0BA0 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Reinforcement Schedules" --- -# [[Reinforcement Schedules]] +# [[Reinforcement Schedules|Reinforcement Schedules]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Reinforcement Schedules" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Reinforcement Schedules.md]] +- Raw Source: 00_Raw/2026-04-20/Reinforcement Schedules.md --- diff --git a/01_Archive/2026-04-20/Render State.md b/01_Archive/2026-04-20/Render State.md index e38e2264..452359ee 100644 --- a/01_Archive/2026-04-20/Render State.md +++ b/01_Archive/2026-04-20/Render State.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-6A1728 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Render State" --- -# [[Render State]] +# [[Render State|Render State]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 렌더링 상태(Render State)란 드로우 콜을 실행하기 위해 CPU가 설정하는 GPU의 내부 설정 및 리소스 상태를 의미합니다 [1, 2]. 셰이더 프로그램 바인딩, 재질 변경, 정점 버퍼 할당 등 렌더 상태를 변경하는 작업은 그래픽 API가 수행하는 연산 중 가장 리소스를 많이 소모하는 작업입니다 [1, 2]. 따라서 드로우 콜과 렌더 상태 변경 횟수를 최소화하는 것은 전체 그래픽 렌더링 성능을 최적화하는 데 매우 중요합니다 [2, 3]. @@ -25,11 +25,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Render State" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Draw Call]], [[CPU]], [[GPU]] -- **Projects/Contexts:** [[Unity]], [[Real-time Rendering]] +- **Related Topics:** [[Draw Call|Draw Call]], CPU, [[GPU|GPU]] +- **Projects/Contexts:** [[Unity|Unity]], Real-time Rendering - **Contradictions/Notes:** 소스 내에서 렌더 상태에 관한 정보나 최적화 방향성에 대해 상충되는 주장은 존재하지 않습니다. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Render State.md]] +- Raw Source: 00_Raw/2026-04-20/Render State.md --- diff --git a/01_Archive/2026-04-20/Resilience Science.md b/01_Archive/2026-04-20/Resilience Science.md index 0f7a27c1..45050812 100644 --- a/01_Archive/2026-04-20/Resilience Science.md +++ b/01_Archive/2026-04-20/Resilience Science.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-06F1DA -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Resilience Science" --- -# [[Resilience Science]] +# [[Resilience Science|Resilience Science]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Resilience Science" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Resilience Science.md]] +- Raw Source: 00_Raw/2026-04-20/Resilience Science.md --- diff --git a/01_Archive/2026-04-20/Resilience-Engineering.md b/01_Archive/2026-04-20/Resilience-Engineering.md index ec2bebc1..e180bc83 100644 --- a/01_Archive/2026-04-20/Resilience-Engineering.md +++ b/01_Archive/2026-04-20/Resilience-Engineering.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-49D143 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Resilience-Engineering" --- -# [[Resilience-Engineering]] +# [[Resilience-Engineering|Resilience-Engineering]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Resilience-Engineering" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Resilience-Engineering.md]] +- Raw Source: 00_Raw/2026-04-20/Resilience-Engineering.md --- diff --git a/01_Archive/2026-04-20/Result Type.md b/01_Archive/2026-04-20/Result Type.md index 2a57e10f..0d90b08a 100644 --- a/01_Archive/2026-04-20/Result Type.md +++ b/01_Archive/2026-04-20/Result Type.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-ED64AE -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Result Type" --- -# [[Result Type]] +# [[Result Type|Result Type]] ## 📌 한 줄 통찰 (The Karpathy Summary) > Result Type(결과 타입)은 함수나 메서드의 반환 값으로 성공 데이터 또는 예상되는 실패(에러)를 명시적으로 함께 표현하는 타입 구조입니다 [1-3]. 예외(Exception)를 무분별하게 던지는 대신 결괏값을 직접 반환하여 프로그램의 실행 흐름이 임의로 끊기는 것을 방지하고 성능 오버헤드를 줄입니다 [4-6]. 개발자가 함수 시그니처만으로 발생 가능한 에러를 명확히 알 수 있게 하며, 컴파일 단계에서 모든 경우의 수에 대한 에러 처리를 강제하여 런타임 안정성을 높이는 데 활용됩니다 [7-9]. @@ -22,11 +22,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Result Type" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Discriminated Unions]], [[Exception Handling]] -- **Projects/Contexts:** [[neverthrow]], [[OneOf]], [[Railway Oriented Programming]] +- **Related Topics:** [[Discriminated Unions|Discriminated Unions]], Exception Handling +- **Projects/Contexts:** neverthrow, OneOf, Railway Oriented Programming - **Contradictions/Notes:** C# 생태계에서는 Result Type 도입을 둘러싼 논쟁이 존재합니다. 도입을 지지하는 쪽은 타입 안전성과 명확한 에러 파악을 장점으로 꼽지만, 반대하는 개발자들은 C#이 기본적으로 예외(Exception) 기반의 언어이므로 두 가지 에러 처리 방식이 섞이면 혼란을 야기할 수 있으며, 결괏값을 포장(Wrapping)하고 푸는 과정에서 보일러플레이트 코드가 증가해 오히려 가독성을 해칠 수 있다고 지적합니다 [2, 6, 19, 20]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/Result Type.md]] +- Raw Source: 00_Raw/2026-04-20/Result Type.md --- diff --git a/01_Archive/2026-04-20/Retainers(유지 경로).md b/01_Archive/2026-04-20/Retainers(유지 경로).md index 01d62ba6..95f165d9 100644 --- a/01_Archive/2026-04-20/Retainers(유지 경로).md +++ b/01_Archive/2026-04-20/Retainers(유지 경로).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-77A920 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Retainers(유지 경로)" --- -# [[Retainers(유지 경로)]] +# [[Retainers(유지 경로)|Retainers(유지 경로)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > Retainers(유지 경로)는 가비지 컬렉터(GC) 루트부터 특정 객체까지 연결된 참조 체인을 의미한다 [1, 2]. 이는 객체가 가비지 컬렉션의 대상이 되지 않고 메모리에 계속 남아있게 만드는 원인을 파악하는 데 사용된다 [1, 2]. 개발자는 Chrome DevTools나 IntelliJ IDEA와 같은 메모리 프로파일링 도구에서 제공하는 Retainers 패널을 통해 이 경로를 역추적하여 메모리 누수의 근본 원인을 식별하고 해결할 수 있다 [3-5]. @@ -30,11 +30,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Retainers(유지 경로)" - **정책 변화:** AI 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Garbage Collection(GC)]], [[Memory Leak]], [[Heap Snapshot]], [[GC Roots]] -- **Projects/Contexts:** [[Chrome DevTools Memory Panel]], [[V8 JavaScript Engine]], [[IntelliJ IDEA V8 CPU and Memory Profiling]] +- **Related Topics:** [[Garbage Collection (GC) 최적화|Garbage Collection(GC)]], [[Memory Leak|Memory Leak]], [[Heap Snapshot|Heap Snapshot]], GC Roots +- **Projects/Contexts:** [[Chrome DevTools Memory Panel|Chrome DevTools Memory Panel]], [[V8 JavaScript Engine|V8 JavaScript Engine]], IntelliJ IDEA V8 CPU and Memory Profiling - **Contradictions/Notes:** 소스에 관련 정보가 부족합니다. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Retainers(유지 경로).md]] +- Raw Source: 00_Raw/2026-04-20/Retainers(유지 경로).md --- diff --git a/01_Archive/2026-04-20/Retaining Path.md b/01_Archive/2026-04-20/Retaining Path.md index c260709b..2c6c7b29 100644 --- a/01_Archive/2026-04-20/Retaining Path.md +++ b/01_Archive/2026-04-20/Retaining Path.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-B5755B -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Retaining Path" --- -# [[Retaining Path]] +# [[Retaining Path|Retaining Path]] ## 📌 한 줄 통찰 (The Karpathy Summary) > Retaining Path(유지 경로)는 가비지 컬렉터가 객체를 메모리에서 해제하지 못하도록 계속 살아있게(live) 만드는 참조의 사슬(chain of references)을 의미합니다 [1, 2]. V8 엔진은 전역 객체나 활성 스택과 같은 GC 루트(GC root)로부터 포인터 사슬을 통해 도달할 수 있는 객체를 살아있는 것으로 판단합니다 [3]. 따라서 이 경로를 분석하는 것은 애플리케이션의 메모리 누수(memory leak) 원인을 식별하고 불필요한 참조를 제거하는 데 핵심적인 역할을 합니다 [4, 5]. @@ -29,11 +29,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Retaining Path" - **정책 변화:** AI 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Memory Leak]], [[Garbage Collection]], [[GC Root]], [[Heap Snapshot]] -- **Projects/Contexts:** [[Chrome DevTools]], [[V8 JavaScript Engine]] +- **Related Topics:** [[Memory Leak|Memory Leak]], [[Garbage Collection|Garbage Collection]], [[GC Root|GC Root]], [[Heap Snapshot|Heap Snapshot]] +- **Projects/Contexts:** [[Chrome DevTools|Chrome DevTools]], [[V8 JavaScript Engine|V8 JavaScript Engine]] - **Contradictions/Notes:** 소스 내에 모순된 주장은 존재하지 않습니다. 제공된 자료들은 모두 메모리 누수를 추적하고 V8 엔진에서 객체가 유지되는 이유를 파악하는 데 있어 Retaining Path의 중요성을 일관되게 강조하고 있습니다. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Retaining Path.md]] +- Raw Source: 00_Raw/2026-04-20/Retaining Path.md --- diff --git a/01_Archive/2026-04-20/Retrograde-Games.md b/01_Archive/2026-04-20/Retrograde-Games.md index 004442ed..0db57af4 100644 --- a/01_Archive/2026-04-20/Retrograde-Games.md +++ b/01_Archive/2026-04-20/Retrograde-Games.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-3F21E0 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Retrograde-Games" --- -# [[Retrograde-Games]] +# [[Retrograde-Games|Retrograde-Games]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Retrograde-Games" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Retrograde-Games.md]] +- Raw Source: 00_Raw/2026-04-20/Retrograde-Games.md --- diff --git a/01_Archive/2026-04-20/Revit glTF Export.md b/01_Archive/2026-04-20/Revit glTF Export.md index 5f21a562..be3f7b6d 100644 --- a/01_Archive/2026-04-20/Revit glTF Export.md +++ b/01_Archive/2026-04-20/Revit glTF Export.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-E2D208 -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Revit glTF Export" --- -# [[Revit glTF Export]] +# [[Revit glTF Export|Revit glTF Export]] ## 📌 한 줄 통찰 (The Karpathy Summary) > Revit glTF Export는 Revit에서 작성된 건축 및 건물 모델을 웹 3D 환경에서 효율적으로 렌더링하기 위해 glTF 형식으로 내보내는 과정입니다 [1, 2]. 이 과정에서는 성능 최적화를 위해 동일한 재질을 가진 메쉬를 병합하는 동시에, 병합된 모델 내에서도 개별 객체를 식별하고 제어하기 위해 특수한 glTF 확장 기능과 정점 데이터 속성을 함께 활용합니다 [3, 4]. @@ -22,11 +22,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Revit glTF Export" - **정책 변화:** Graphics & Performance 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[BatchedMesh]], [[glTF Extensions]], [[Three.js]] -- **Projects/Contexts:** [[건축 및 BIM(Building Information Modeling) 3D 뷰어 구현]] +- **Related Topics:** [[BatchedMesh|BatchedMesh]], glTF Extensions, [[Three.js|Three.js]] +- **Projects/Contexts:** 건축 및 BIM(Building Information Modeling) 3D 뷰어 구현 - **Contradictions/Notes:** Revit에서 내보낸 1,200만 개 이상의 삼각형과 1,600만 개 이상의 정점을 포함하는 거대한 glTF 모델을 다룰 때, 개별 객체 제어를 위해 `BatchedMesh`를 사용하면 단순히 병합된 일반 `Mesh`로 렌더링할 때보다 오히려 CPU 사용량이 40~60%까지 급증하고 프레임 속도(FPS)가 급격히 떨어지는 성능 저하 현상이 보고되고 있습니다 [1, 2, 6, 7]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Revit glTF Export.md]] +- Raw Source: 00_Raw/2026-04-20/Revit glTF Export.md --- diff --git a/01_Archive/2026-04-20/Revit 모델 렌더링.md b/01_Archive/2026-04-20/Revit 모델 렌더링.md index 12857f90..1edd72a4 100644 --- a/01_Archive/2026-04-20/Revit 모델 렌더링.md +++ b/01_Archive/2026-04-20/Revit 모델 렌더링.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-EC4298 -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Revit 모델 렌더링" --- -# [[Revit 모델 렌더링]] +# [[Revit 모델 렌더링|Revit 모델 렌더링]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 소스에 관련 정보가 부족합니다. 제공된 텍스트에서는 Revit 모델을 Three.js와 같은 웹 그래픽 환경으로 내보내어 렌더링하는 과정에서 발생한 특정 사용자의 워크플로우와 성능 병목 사례만이 제한적으로 언급되어 있습니다. @@ -24,11 +24,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Revit 모델 렌더링" - **정책 변화:** Graphics & Performance 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[BatchedMesh]], [[glTF]], [[Three.js]] -- **Projects/Contexts:** [[대규모 건축 모델의 웹 기반 시각화 및 최적화 테스트]] +- **Related Topics:** [[BatchedMesh|BatchedMesh]], glTF, [[Three.js|Three.js]] +- **Projects/Contexts:** 대규모 건축 모델의 웹 기반 시각화 및 최적화 테스트 - **Contradictions/Notes:** 소스에 관련 정보가 부족합니다. 한편 사례를 통해, 일반적인 렌더링 횟수를 줄이기 위해 도입하는 `BatchedMesh` 최적화 기법이 거대한 규모의 Revit 파생 모델(수천만 정점 및 수십만 지오메트리)에서는 막대한 CPU 오버헤드를 유발하여 오히려 렌더링 성능을 저하시키는 모순적인 결과를 낳는다는 것을 확인할 수 있습니다 [1, 8, 10]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Revit 모델 렌더링.md]] +- Raw Source: 00_Raw/2026-04-20/Revit 모델 렌더링.md --- diff --git a/01_Archive/2026-04-20/Reward Hacking (보상 해킹).md b/01_Archive/2026-04-20/Reward Hacking (보상 해킹).md index 0f3236b4..225c4a43 100644 --- a/01_Archive/2026-04-20/Reward Hacking (보상 해킹).md +++ b/01_Archive/2026-04-20/Reward Hacking (보상 해킹).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-7F2CC8 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Reward Hacking (보상 해킹)" --- -# [[Reward Hacking (보상 해킹)]] +# [[Reward Hacking (보상 해킹)|Reward Hacking (보상 해킹)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Reward Hacking (보상 해킹) ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Reward Hacking (보상 해킹).md]] +- Raw Source: 00_Raw/2026-04-20/Reward Hacking (보상 해킹).md --- diff --git a/01_Archive/2026-04-20/Reward Prediction Error.md b/01_Archive/2026-04-20/Reward Prediction Error.md index a8a92180..f000e70e 100644 --- a/01_Archive/2026-04-20/Reward Prediction Error.md +++ b/01_Archive/2026-04-20/Reward Prediction Error.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-08768A -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Reward Prediction Error" --- -# [[Reward Prediction Error]] +# [[Reward Prediction Error|Reward Prediction Error]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Reward Prediction Error" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Reward Prediction Error.md]] +- Raw Source: 00_Raw/2026-04-20/Reward Prediction Error.md --- diff --git a/01_Archive/2026-04-20/Reward Shaping (보상 설계).md b/01_Archive/2026-04-20/Reward Shaping (보상 설계).md index 4f47c588..e4741441 100644 --- a/01_Archive/2026-04-20/Reward Shaping (보상 설계).md +++ b/01_Archive/2026-04-20/Reward Shaping (보상 설계).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-1B82EC -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Reward Shaping (보상 설계)" --- -# [[Reward Shaping (보상 설계)]] +# [[Reward Shaping (보상 설계)|Reward Shaping (보상 설계)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Reward Shaping (보상 설계) ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Reward Shaping (보상 설계).md]] +- Raw Source: 00_Raw/2026-04-20/Reward Shaping (보상 설계).md --- diff --git a/01_Archive/2026-04-20/Risk Management in Finance.md b/01_Archive/2026-04-20/Risk Management in Finance.md index e8bf77fb..a7fa55e2 100644 --- a/01_Archive/2026-04-20/Risk Management in Finance.md +++ b/01_Archive/2026-04-20/Risk Management in Finance.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-5DD3BE -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Risk Management in Finance" --- -# [[Risk Management in Finance]] +# [[Risk Management in Finance|Risk Management in Finance]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Risk Management in Finance" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Risk Management in Finance.md]] +- Raw Source: 00_Raw/2026-04-20/Risk Management in Finance.md --- diff --git a/01_Archive/2026-04-20/Robotic Manipulation Control.md b/01_Archive/2026-04-20/Robotic Manipulation Control.md index d2cd6c09..d8777bab 100644 --- a/01_Archive/2026-04-20/Robotic Manipulation Control.md +++ b/01_Archive/2026-04-20/Robotic Manipulation Control.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-913A3C -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Robotic Manipulation Control" --- -# [[Robotic Manipulation Control]] +# [[Robotic Manipulation Control|Robotic Manipulation Control]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Robotic Manipulation Control" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Robotic Manipulation Control.md]] +- Raw Source: 00_Raw/2026-04-20/Robotic Manipulation Control.md --- diff --git a/01_Archive/2026-04-20/Robotic-Manipulator-Dynamics.md b/01_Archive/2026-04-20/Robotic-Manipulator-Dynamics.md index cbd22aec..1cf9ebae 100644 --- a/01_Archive/2026-04-20/Robotic-Manipulator-Dynamics.md +++ b/01_Archive/2026-04-20/Robotic-Manipulator-Dynamics.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-CA896D -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Robotic-Manipulator-Dynamics" --- -# [[Robotic-Manipulator-Dynamics]] +# [[Robotic-Manipulator-Dynamics|Robotic-Manipulator-Dynamics]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Robotic-Manipulator-Dynamics" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Robotic-Manipulator-Dynamics.md]] +- Raw Source: 00_Raw/2026-04-20/Robotic-Manipulator-Dynamics.md --- diff --git a/01_Archive/2026-04-20/Robotic-Prosthetics-Control-Systems.md b/01_Archive/2026-04-20/Robotic-Prosthetics-Control-Systems.md index 880bea42..59804e1a 100644 --- a/01_Archive/2026-04-20/Robotic-Prosthetics-Control-Systems.md +++ b/01_Archive/2026-04-20/Robotic-Prosthetics-Control-Systems.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-A360D1 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Robotic-Prosthetics-Control-Systems" --- -# [[Robotic-Prosthetics-Control-Systems]] +# [[Robotic-Prosthetics-Control-Systems|Robotic-Prosthetics-Control-Systems]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Robotic-Prosthetics-Control-Sy ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Robotic-Prosthetics-Control-Systems.md]] +- Raw Source: 00_Raw/2026-04-20/Robotic-Prosthetics-Control-Systems.md --- diff --git a/01_Archive/2026-04-20/Robotics-Control-Systems.md b/01_Archive/2026-04-20/Robotics-Control-Systems.md index 28a8bc81..523c5873 100644 --- a/01_Archive/2026-04-20/Robotics-Control-Systems.md +++ b/01_Archive/2026-04-20/Robotics-Control-Systems.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-A9830E -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Robotics-Control-Systems" --- -# [[Robotics-Control-Systems]] +# [[Robotics-Control-Systems|Robotics-Control-Systems]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Robotics-Control-Systems" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Robotics-Control-Systems.md]] +- Raw Source: 00_Raw/2026-04-20/Robotics-Control-Systems.md --- diff --git a/01_Archive/2026-04-20/Robust-GitHub-Sync-Pipeline.md b/01_Archive/2026-04-20/Robust-GitHub-Sync-Pipeline.md index f32a3e5f..f359191a 100644 --- a/01_Archive/2026-04-20/Robust-GitHub-Sync-Pipeline.md +++ b/01_Archive/2026-04-20/Robust-GitHub-Sync-Pipeline.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-CCD7BE -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Robust-GitHub-Sync-Pipeline" --- -# [[Robust-GitHub-Sync-Pipeline]] +# [[Robust-GitHub-Sync-Pipeline|Robust-GitHub-Sync-Pipeline]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 에이전트가 수집한 지식을 원격 위키 저장소에 안전하게 기록하는 최종 단계의 동기화 엔진입니다. 복잡한 저장소 URL 형식을 자동으로 파싱하고, 파일 부재(404)를 오류가 아닌 '신규 생성 기회'로 판단하는 지능형 예외 처리를 포함합니다. @@ -29,8 +29,8 @@ GitHub API를 이용한 자동 커밋은 파일 존재 여부에 따라 SHA 값 - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Ontology-Driven-Relevancy-Filtering]], [[Zustand-Based-Mission-Persistence]] -- **Projects/Contexts:** [[Knowledge-Base-Automation]] +- **Related Topics:** [[Ontology-Driven-Relevancy-Filtering|Ontology-Driven-Relevancy-Filtering]], [[Zustand-Based-Mission-Persistence|Zustand-Based-Mission-Persistence]] +- **Projects/Contexts:** Knowledge-Base-Automation - **Contradictions/Notes:** GitHub API의 Rate Limit(시간당 요청 제한)을 고려해야 하며, 대량의 커밋 성공 시 배치(Batch) 처리 방식을 검토할 수 있습니다. -- Raw Source: [[00_Raw/2026-04-20/Robust-GitHub-Sync-Pipeline.md]] +- Raw Source: 00_Raw/2026-04-20/Robust-GitHub-Sync-Pipeline.md --- diff --git a/01_Archive/2026-04-20/Robustness (강건성).md b/01_Archive/2026-04-20/Robustness (강건성).md index 977d25e3..42644436 100644 --- a/01_Archive/2026-04-20/Robustness (강건성).md +++ b/01_Archive/2026-04-20/Robustness (강건성).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-EB7908 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Robustness (강건성)" --- -# [[Robustness (강건성)]] +# [[Robustness (강건성)|Robustness (강건성)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Robustness (강건성)" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Robustness (강건성).md]] +- Raw Source: 00_Raw/2026-04-20/Robustness (강건성).md --- diff --git a/01_Archive/2026-04-20/Roguelike Procedural Generation.md b/01_Archive/2026-04-20/Roguelike Procedural Generation.md index 020d8e6c..f40a5507 100644 --- a/01_Archive/2026-04-20/Roguelike Procedural Generation.md +++ b/01_Archive/2026-04-20/Roguelike Procedural Generation.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-537B8F -category: "[[10_Wiki/💡 Topics/Game Design]]" +category: "10_Wiki/💡 Topics/Game Design" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Roguelike Procedural Generation" --- -# [[Roguelike Procedural Generation]] +# [[Roguelike Procedural Generation|Roguelike Procedural Generation]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Roguelike Procedural Generatio ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Roguelike Procedural Generation.md]] +- Raw Source: 00_Raw/2026-04-20/Roguelike Procedural Generation.md --- diff --git a/01_Archive/2026-04-20/Roguelike Subgenre.md b/01_Archive/2026-04-20/Roguelike Subgenre.md index 89befafc..18c38002 100644 --- a/01_Archive/2026-04-20/Roguelike Subgenre.md +++ b/01_Archive/2026-04-20/Roguelike Subgenre.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-3475FE -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Roguelike Subgenre" --- -# [[Roguelike Subgenre]] +# [[Roguelike Subgenre|Roguelike Subgenre]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Roguelike Subgenre" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Roguelike Subgenre.md]] +- Raw Source: 00_Raw/2026-04-20/Roguelike Subgenre.md --- diff --git a/01_Archive/2026-04-20/Role-Playing-Games (RPGs).md b/01_Archive/2026-04-20/Role-Playing-Games (RPGs).md index 58522c59..525bb0d5 100644 --- a/01_Archive/2026-04-20/Role-Playing-Games (RPGs).md +++ b/01_Archive/2026-04-20/Role-Playing-Games (RPGs).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-5C3932 -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Role-Playing-Games (RPGs)" --- -# [[Role-Playing-Games (RPGs)]] +# [[Role-Playing-Games (RPGs)|Role-Playing-Games (RPGs)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Role-Playing-Games (RPGs)" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Role-Playing-Games (RPGs).md]] +- Raw Source: 00_Raw/2026-04-20/Role-Playing-Games (RPGs).md --- diff --git a/01_Archive/2026-04-20/Rowhammer attack.md b/01_Archive/2026-04-20/Rowhammer attack.md index 9f413063..34098a0e 100644 --- a/01_Archive/2026-04-20/Rowhammer attack.md +++ b/01_Archive/2026-04-20/Rowhammer attack.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-80DA6E -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Rowhammer attack" --- -# [[Rowhammer attack]] +# [[Rowhammer attack|Rowhammer attack]] ## 📌 한 줄 통찰 (The Karpathy Summary) > Rowhammer 공격은 WebGL을 사용하여 GPU에서 실행되었던 심각한 보안 취약점 공격입니다 [1]. 이 공격은 고정밀 타임스탬프 쿼리를 활용하여 캐시 적중 실패율(cache miss rates)을 관찰하고, 이를 통해 GPU의 물리적 메모리 레이아웃을 파악합니다 [1]. 이후 파악된 메모리에서 특정 비트를 반전(flip)시켜 페이지 테이블을 조작하고 악의적인 작업을 수행하도록 유도합니다 [1]. 과거에는 막기 어려운 공격으로 보고되었으나, 현재는 최신 RAM에 적용된 완화(mitigations) 기술을 통해 방어할 수 있습니다 [1]. @@ -22,11 +22,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Rowhammer attack" - **정책 변화:** Graphics & Performance 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[WebGL]], [[GPU]], [[Timestamp queries]], [[TLB design]], [[Cache miss rates]] -- **Projects/Contexts:** WebGPU의 [[High Resolution Time spec]] 이슈 논의 과정 중, 고해상도 타임스탬프가 야기할 수 있는 심각한 보안 위협(타이밍 공격)의 과거 사례로 언급되었습니다 [1]. +- **Related Topics:** [[WebGL|WebGL]], [[GPU|GPU]], [[Timestamp Queries|Timestamp queries]], [[TLB design|TLB design]], [[Cache miss rates|Cache miss rates]] +- **Projects/Contexts:** WebGPU의 High Resolution Time spec 이슈 논의 과정 중, 고해상도 타임스탬프가 야기할 수 있는 심각한 보안 위협(타이밍 공격)의 과거 사례로 언급되었습니다 [1]. - **Contradictions/Notes:** 소스에 따르면 보고된 당시에는 막을 수 없는(couldn't plug) 공격이었으나, 현재는 하드웨어(최신 RAM)의 개선으로 인해 더 이상 유효하지 않은 것으로 보입니다 [1]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Rowhammer attack.md]] +- Raw Source: 00_Raw/2026-04-20/Rowhammer attack.md --- diff --git a/01_Archive/2026-04-20/Rowhammer.md b/01_Archive/2026-04-20/Rowhammer.md index 8b8427f5..9d3f51da 100644 --- a/01_Archive/2026-04-20/Rowhammer.md +++ b/01_Archive/2026-04-20/Rowhammer.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-13F9F1 -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Rowhammer" --- -# [[Rowhammer]] +# [[Rowhammer|Rowhammer]] ## 📌 한 줄 통찰 (The Karpathy Summary) > Rowhammer는 WebGL을 통해 GPU 상에서 실행되어 물리적 메모리의 특정 비트를 반전시키는 심각한 보안 공격 기법입니다 [1]. 이 공격은 고정밀 타임스탬프 쿼리를 이용해 캐시 미스율을 관찰하고 GPU의 물리적 메모리 레이아웃을 파악하는 방식으로 이루어집니다 [1]. 한때 막을 수 없었던 위협적인 공격이었으나, 특정 장치에만 국한되어 발생하며 최신 RAM의 방어 기술을 통해 완화되었습니다 [1]. @@ -22,11 +22,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Rowhammer" - **정책 변화:** Graphics & Performance 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[WebGL]], [[Timestamp Queries]], [[TLB (Translation Lookaside Buffer)]] -- **Projects/Contexts:** [[High Resolution Time spec 논의]] (GPU 타임스탬프 해상도를 제한(coarsen)하여 보안 취약점을 방지해야 한다는 논의 중, 고정밀 타임스탬프를 악용한 실제 공격 사례로 언급됨 [1]) +- **Related Topics:** [[WebGL|WebGL]], [[Timestamp Queries|Timestamp Queries]], TLB (Translation Lookaside Buffer) +- **Projects/Contexts:** High Resolution Time spec 논의 (GPU 타임스탬프 해상도를 제한(coarsen)하여 보안 취약점을 방지해야 한다는 논의 중, 고정밀 타임스탬프를 악용한 실제 공격 사례로 언급됨 [1]) - **Contradictions/Notes:** 소스에 따르면 Rowhammer는 초기에 "막을 수 없었던 최초의 실질적이고 심각한 공격(the first real, serious attack we couldn't plug)"으로 평가되었으나, 현재는 최신 RAM 하드웨어의 발전으로 회피가 가능해졌습니다 [1]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Rowhammer.md]] +- Raw Source: 00_Raw/2026-04-20/Rowhammer.md --- diff --git a/01_Archive/2026-04-20/Runtime-Type-Validation.md b/01_Archive/2026-04-20/Runtime-Type-Validation.md index 956dbfea..b7685448 100644 --- a/01_Archive/2026-04-20/Runtime-Type-Validation.md +++ b/01_Archive/2026-04-20/Runtime-Type-Validation.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-BFB695 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Runtime-Type-Validation" --- -# [[Runtime-Type-Validation]] +# [[Runtime-Type-Validation|Runtime-Type-Validation]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Runtime-Type-Validation" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Runtime-Type-Validation.md]] +- Raw Source: 00_Raw/2026-04-20/Runtime-Type-Validation.md --- diff --git a/01_Archive/2026-04-20/SAST (Static Application Security Testing).md b/01_Archive/2026-04-20/SAST (Static Application Security Testing).md index b2466e45..1c515f91 100644 --- a/01_Archive/2026-04-20/SAST (Static Application Security Testing).md +++ b/01_Archive/2026-04-20/SAST (Static Application Security Testing).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-DCCAB5 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - SAST (Static Application Security Testing)" --- -# [[SAST (Static Application Security Testing)]] +# [[SAST (Static Application Security Testing)|SAST (Static Application Security Testing)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > SAST(정적 애플리케이션 보안 테스트)는 애플리케이션을 실행하지 않고 소스 코드나 바이트코드를 정적으로 분석하여 잠재적인 보안 취약점을 식별하는 화이트박스 테스트(White-box testing) 기법입니다 [1]. 소프트웨어 개발 수명 주기(SDLC) 초기에 도입되어, 코드 결함이 배포되기 전에 수정할 수 있도록 개발 과정 중에 실시간으로 오류를 잡아냅니다 [1, 2]. 최근에는 단순한 규칙 기반 방식을 넘어 AI 모델과 결합하여, 문맥 기반의 비즈니스 로직 결함을 찾고 자동 수정(Auto-fix) 코드를 제안하는 형태로 발전하고 있습니다 [3, 4]. @@ -24,11 +24,11 @@ github_commit: "[P-Reinforce] Continuous Worker - SAST (Static Application Secur - **정책 변화:** AI 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[DAST (Dynamic Application Security Testing)]], [[SCA (Software Composition Analysis)]], [[Shift-Left Security]], [[False Positives]], [[Taint Analysis]] -- **Projects/Contexts:** [[Snyk Code]], [[Corgea]], [[SonarQube]], [[GitHub Advanced Security]], [[Checkmarx]], [[Semgrep]] +- **Related Topics:** [[DAST (Dynamic Application Security Testing)|DAST (Dynamic Application Security Testing)]], SCA (Software Composition Analysis), Shift-Left Security, False Positives, Taint Analysis +- **Projects/Contexts:** Snyk Code, [[Corgea|Corgea]], [[SonarQube|SonarQube]], GitHub Advanced Security, Checkmarx, Semgrep - **Contradictions/Notes:** 레거시 SAST 도구들은 엄격한 정적 규칙으로 인해 50-80%에 달하는 높은 오탐률(False Positives)을 보여 개발자에게 경고 피로(Alert fatigue)를 유발한다는 단점이 있었으나, 최신 AI 기반 SAST는 수백만 개의 오픈소스 커밋과 문맥을 학습하여 노이즈를 획기적으로 줄이고 실제 악용 가능한 취약점을 분류해 내는 방향으로 단점을 극복하고 있습니다 [9, 11, 17]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/SAST (Static Application Security Testing).md]] +- Raw Source: 00_Raw/2026-04-20/SAST (Static Application Security Testing).md --- diff --git a/01_Archive/2026-04-20/SAST (정적 애플리케이션 보안 테스트).md b/01_Archive/2026-04-20/SAST (정적 애플리케이션 보안 테스트).md index 23f8c11d..b1e417fa 100644 --- a/01_Archive/2026-04-20/SAST (정적 애플리케이션 보안 테스트).md +++ b/01_Archive/2026-04-20/SAST (정적 애플리케이션 보안 테스트).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-4C10C5 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - SAST (정적 애플리케이션 보안 테스트)" --- -# [[SAST (정적 애플리케이션 보안 테스트)]] +# [[SAST (정적 애플리케이션 보안 테스트)|SAST (정적 애플리케이션 보안 테스트)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > SAST(정적 애플리케이션 보안 테스트)는 애플리케이션을 실행하지 않고 소스 코드나 바이트코드 자체를 분석하여 잠재적인 보안 취약점을 찾아내는 화이트박스 테스트(White-box testing) 기법입니다 [1]. 소프트웨어 개발 수명 주기(SDLC)의 초기 단계에 통합되어 결함을 사전에 식별하고 조치함으로써 보안 문제를 빠르고 저렴하게 해결하는 '시프트 레프트(Shift-Left)' 접근법의 핵심입니다 [2-4]. 최근에는 전통적인 규칙 기반의 한계를 극복하기 위해 머신러닝과 LLM을 결합하여 코드의 문맥을 이해하고 오탐을 줄이는 AI 기반 SAST로 발전하고 있습니다 [5, 6]. @@ -30,11 +30,11 @@ github_commit: "[P-Reinforce] Continuous Worker - SAST (정적 애플리케이 - **정책 변화:** AI 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[DAST (동적 애플리케이션 보안 테스트)]], [[SCA (소프트웨어 구성 분석)]], [[시프트 레프트 (Shift-Left)]], [[오탐 (False Positive)]], [[코드 리뷰 (Code Review)]] -- **Projects/Contexts:** [[Snyk Code]], [[Corgea]], [[SonarQube]], [[소프트웨어 개발 수명 주기 (SDLC)]] +- **Related Topics:** [[DAST (동적 애플리케이션 보안 테스트)|DAST (동적 애플리케이션 보안 테스트)]], [[SCA (소프트웨어 구성 분석)|SCA (소프트웨어 구성 분석)]], [[시프트 레프트 (Shift-Left)|시프트 레프트 (Shift-Left)]], [[오탐 (False Positive)|오탐 (False Positive)]], [[코드 리뷰 (Code Review)|코드 리뷰 (Code Review)]] +- **Projects/Contexts:** Snyk Code, [[Corgea|Corgea]], [[SonarQube|SonarQube]], [[소프트웨어 개발 수명 주기 (SDLC)|소프트웨어 개발 수명 주기 (SDLC)]] - **Contradictions/Notes:** 소스에 따르면 수동 코드 리뷰는 문맥과 비즈니스 로직, 아키텍처를 깊이 이해하지만 속도가 느리고 비용이 큰 반면, 자동화된 SAST 도구는 매우 빠르고 일관적이지만 코드의 의도를 파악하지 못해 오탐이 발생한다는 뚜렷한 대비가 있습니다 [21-23]. 이에 따라 2025년의 모범 사례는 SAST와 같은 자동화 스캔 도구로 코드 스타일과 일반적인 보안 결함을 1차적으로 걸러내고, 인간 검토자는 자동화가 놓치는 핵심 로직 및 크로스 서비스 영향도 평가에 집중하는 '하이브리드 코드 리뷰' 모델을 채택하는 것입니다 [21, 24, 25]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/SAST (정적 애플리케이션 보안 테스트).md]] +- Raw Source: 00_Raw/2026-04-20/SAST (정적 애플리케이션 보안 테스트).md --- diff --git a/01_Archive/2026-04-20/SAST (정적 애플리케이션 보안 테스팅).md b/01_Archive/2026-04-20/SAST (정적 애플리케이션 보안 테스팅).md index e8d599e6..ae12dc5a 100644 --- a/01_Archive/2026-04-20/SAST (정적 애플리케이션 보안 테스팅).md +++ b/01_Archive/2026-04-20/SAST (정적 애플리케이션 보안 테스팅).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-8D39DE -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - SAST (정적 애플리케이션 보안 테스팅)" --- -# [[SAST (정적 애플리케이션 보안 테스팅)]] +# [[SAST (정적 애플리케이션 보안 테스팅)|SAST (정적 애플리케이션 보안 테스팅)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > SAST(정적 애플리케이션 보안 테스팅)는 애플리케이션을 실행하지 않고 소스 코드나 바이트코드를 정적으로 분석하여 보안 취약점을 찾아내는 '화이트박스 테스팅' 기법입니다 [1, 2]. 개발 초기 단계(CI/CD 파이프라인이나 IDE)에 통합되어 취약점이 프로덕션 환경에 도달하기 전에 예방하는 Shift-Left 보안을 실현합니다 [3, 4]. 최근에는 규칙 기반 패턴 매칭의 한계를 넘어, 대형 언어 모델(LLM)과 기계 학습(ML)을 결합하여 문맥을 이해하고 자동으로 코드를 수정해주는 AI 기반 SAST로 진화하고 있습니다 [5-7]. @@ -27,11 +27,11 @@ github_commit: "[P-Reinforce] Continuous Worker - SAST (정적 애플리케이 - **정책 변화:** AI 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[DAST (동적 애플리케이션 보안 테스팅)]], [[SCA (소프트웨어 구성 분석)]], [[AI-powered SAST]], [[수동 코드 리뷰 (Manual Code Review)]] -- **Projects/Contexts:** [[Shift-Left 보안]], [[CI/CD 및 IDE 통합]], [[OWASP Top 10]] +- **Related Topics:** DAST (동적 애플리케이션 보안 테스팅), [[SCA (소프트웨어 구성 분석)|SCA (소프트웨어 구성 분석)]], AI-powered SAST, [[수동 코드 리뷰 (Manual Code Review)|수동 코드 리뷰 (Manual Code Review)]] +- **Projects/Contexts:** Shift-Left 보안, CI/CD 및 IDE 통합, [[OWASP Top 10|OWASP Top 10]] - **Contradictions/Notes:** 자동화된 SAST는 매우 빠르고 일관되게 코드를 검사하지만 비즈니스 로직과 의도를 파악하는 데는 맹점이 존재하므로(Context Blindness), 런타임 환경을 분석하는 DAST 또는 설계와 맥락을 깊이 이해하는 수동 코드 리뷰(Manual Review)와 결합된 하이브리드 접근 방식이 권장됩니다 [15, 19, 20]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/SAST (정적 애플리케이션 보안 테스팅).md]] +- Raw Source: 00_Raw/2026-04-20/SAST (정적 애플리케이션 보안 테스팅).md --- diff --git a/01_Archive/2026-04-20/SAST.md b/01_Archive/2026-04-20/SAST.md index 611fd4cd..4f24a5d2 100644 --- a/01_Archive/2026-04-20/SAST.md +++ b/01_Archive/2026-04-20/SAST.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-205541 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - SAST" --- -# [[SAST]] +# [[SAST|SAST]] ## 📌 한 줄 통찰 (The Karpathy Summary) > SAST(Static Application Security Testing, 정적 애플리케이션 보안 테스트)는 애플리케이션을 실행하지 않고 소스 코드, 바이트코드 또는 바이너리를 정적으로 분석하여 보안 취약점을 찾아내는 화이트박스 테스트 기법입니다 [1-3]. 개발 초기 단계인 IDE나 CI/CD 파이프라인에 통합되어 결함을 사전에 해결하는 '시프트 레프트(Shift-left)' 보안 접근법의 핵심적인 역할을 수행합니다 [4-7]. 최근에는 높은 오탐률(False Positive)과 문맥 파악의 한계를 극복하기 위해 머신러닝(ML)과 대규모 언어 모델(LLM)을 결합한 AI 기반 SAST로 진화하여 더욱 정확한 탐지와 자동 수정(Auto-fix) 기능을 제공하고 있습니다 [8-10]. @@ -20,11 +20,11 @@ github_commit: "[P-Reinforce] Continuous Worker - SAST" - **정책 변화:** AI 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[DAST]], [[SCA]], [[IAST]], [[Shift-Left]], [[False Positives]] -- **Projects/Contexts:** [[CI/CD Pipeline Integration]], [[Snyk Code]], [[Corgea]], [[Checkmarx]], [[SonarQube]] +- **Related Topics:** [[DAST (동적 애플리케이션 보안 테스트)|DAST]], [[SCA (소프트웨어 구성 분석)|SCA]], IAST, [[시프트 레프트 (Shift-Left)|Shift-Left]], False Positives +- **Projects/Contexts:** CI/CD Pipeline Integration, Snyk Code, [[Corgea|Corgea]], Checkmarx, [[SonarQube|SonarQube]] - **Contradictions/Notes:** 자동화된 SAST 도구는 코드 기반의 패턴 매칭에 빠르고 일관되지만, 복잡한 비즈니스 로직과 아키텍처 트레이드오프를 이해하지 못하므로, 완벽한 보안과 코드 품질 확보를 위해서는 인간 개발자가 직접 수행하는 수동 코드 리뷰(Manual Code Review)를 반드시 병행해야 한다고 강조됩니다 [16, 26-28]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/SAST.md]] +- Raw Source: 00_Raw/2026-04-20/SAST.md --- diff --git a/01_Archive/2026-04-20/SCA (소프트웨어 구성 분석).md b/01_Archive/2026-04-20/SCA (소프트웨어 구성 분석).md index ef07c068..f7bf4499 100644 --- a/01_Archive/2026-04-20/SCA (소프트웨어 구성 분석).md +++ b/01_Archive/2026-04-20/SCA (소프트웨어 구성 분석).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-A04F7E -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - SCA (소프트웨어 구성 분석)" --- -# [[SCA (소프트웨어 구성 분석)]] +# [[SCA (소프트웨어 구성 분석)|SCA (소프트웨어 구성 분석)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > SCA(Software Composition Analysis)는 애플리케이션에 포함된 제3자(Third-party) 코드 및 오픈소스 라이브러리의 의존성(Dependencies)을 분석하는 보안 테스팅 기법입니다 [1, 2]. 주로 외부 컴포넌트에 이미 보고된 보안 취약점(CVE 등)과 라이선스 컴플라이언스 관련 리스크를 식별하는 데 사용됩니다 [1]. 오늘날 소프트웨어 개발에서 오픈소스 라이브러리 사용 비중이 매우 높기 때문에 소프트웨어 공급망 보안을 관리하는 데 있어 그 중요성이 커지고 있으며 [1, 2], 자체 코드를 검사하는 SAST와 함께 상호 보완적으로 활용됩니다 [3]. @@ -23,11 +23,11 @@ github_commit: "[P-Reinforce] Continuous Worker - SCA (소프트웨어 구성 - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[SAST (정적 애플리케이션 보안 테스팅)]], [[서플라이 체인 보안 (Supply Chain Security)]], [[오픈소스 컴포넌트 (Open Source Components)]], [[도달 가능성 분석 (Reachability Analysis)]] -- **Projects/Contexts:** [[데브섹옵스 (DevSecOps) 환경에서의 지속적인 보안 검사]], [[Snyk, Checkmarx, Endor Labs 등 종합 애플리케이션 보안 플랫폼]] +- **Related Topics:** [[SAST (정적 애플리케이션 보안 테스팅)|SAST (정적 애플리케이션 보안 테스팅)]], [[서플라이 체인 보안 (Supply Chain Security)|서플라이 체인 보안 (Supply Chain Security)]], [[오픈소스 컴포넌트 (Open Source Components)|오픈소스 컴포넌트 (Open Source Components)]], [[도달 가능성 분석 (Reachability Analysis)|도달 가능성 분석 (Reachability Analysis)]] +- **Projects/Contexts:** [[데브섹옵스 (DevSecOps) 환경에서의 지속적인 보안 검사|데브섹옵스 (DevSecOps) 환경에서의 지속적인 보안 검사]], [[Snyk, Checkmarx, Endor Labs 등 종합 애플리케이션 보안 플랫폼|Snyk, Checkmarx, Endor Labs 등 종합 애플리케이션 보안 플랫폼]] - **Contradictions/Notes:** 여러 소스에서 SCA와 SAST는 서로 대체하거나 경쟁하는 관계가 아니라는 점을 분명히 합니다. SAST는 자체 작성 코드의 논리 결함을, SCA는 서드파티 코드의 버전 이력 및 라이선스 문제를 잡아내기 때문에 각 도구의 약점을 보완하려면 이 둘을 결합하여 사용하는 것이 모범 사례로 강조됩니다 [1, 2]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/SCA (소프트웨어 구성 분석).md]] +- Raw Source: 00_Raw/2026-04-20/SCA (소프트웨어 구성 분석).md --- diff --git a/01_Archive/2026-04-20/SCADA.md b/01_Archive/2026-04-20/SCADA.md index ce72de7d..195ca981 100644 --- a/01_Archive/2026-04-20/SCADA.md +++ b/01_Archive/2026-04-20/SCADA.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-001 -category: "[[10_Wiki/💡 Topics/Automation]]" +category: "10_Wiki/💡 Topics/Automation" confidence_score: 0.90 tags: [automation, scada, industrial, control] last_reinforced: 2026-04-20 github_commit: "batch-reinforce-06" --- -# [[SCADA (Supervisory Control and Data Acquisition)]] +# SCADA (Supervisory Control and Data Acquisition) ## 📌 한 줄 통찰 (The Karpathy Summary) > 광범위한 산업 현장의 데이터를 실시간으로 수집하고 원격에서 제어함으로써 제조 지능화를 구현하는 중앙 통제 센터. @@ -24,6 +24,6 @@ github_commit: "batch-reinforce-06" - **정책 변화:** 구조적 연결성(w2) 관점에서 3D_Web_HMI 및 Digital_Twin과의 데이터 정합성 강조. ## 🔗 지식 연결 (Graph) -- **Parent:** [[10_Wiki/💡 Topics/Automation]] -- **Related:** [[3D_Web_HMI]], [[Digital_Twin]], [[Industrial-IoT]] -- **Raw Source:** [[00_Raw/2026-04-20/Industrial-Automation.md]] +- **Parent:** 10_Wiki/💡 Topics/Automation +- **Related:** [[3D_Web_HMI|3D_Web_HMI]], [[Digital_Twin|Digital_Twin]], Industrial-IoT +- **Raw Source:** 00_Raw/2026-04-20/Industrial-Automation.md diff --git a/01_Archive/2026-04-20/SDLC (소프트웨어 개발 수명 주기).md b/01_Archive/2026-04-20/SDLC (소프트웨어 개발 수명 주기).md index 9e5af0ed..494c4ad3 100644 --- a/01_Archive/2026-04-20/SDLC (소프트웨어 개발 수명 주기).md +++ b/01_Archive/2026-04-20/SDLC (소프트웨어 개발 수명 주기).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-9A0FE1 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - SDLC (소프트웨어 개발 수명 주기)" --- -# [[SDLC (소프트웨어 개발 수명 주기)]] +# [[SDLC (소프트웨어 개발 수명 주기)|SDLC (소프트웨어 개발 수명 주기)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > SDLC(소프트웨어 개발 수명 주기)는 소프트웨어를 개발하고 유지보수하기 위해 조직에서 사용하는 전체 프로세스입니다 [1, 2]. 현대의 SDLC는 코드 생성 및 디버깅을 돕는 AI 도구들이 필수적으로 통합되고 있으며, 이에 따라 초기 단계부터 보안 및 품질 검증을 수행하는 것이 매우 중요해졌습니다 [2, 3]. 특히 정적 분석(SAST) 및 자동화된 코드 리뷰 도구를 SDLC 전반에 통합하여 취약점과 결함을 조기에 발견하고 안전한 코드를 대규모로 배포하는 데 중점을 둡니다 [1, 4]. @@ -23,11 +23,11 @@ github_commit: "[P-Reinforce] Continuous Worker - SDLC (소프트웨어 개발 - **정책 변화:** AI 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[SAST (정적 애플리케이션 보안 테스트)]], [[Quality Gates (품질 게이트)]], [[SSDLC (안전한 소프트웨어 개발 수명 주기)]], [[AI Code Review (AI 코드 리뷰)]] -- **Projects/Contexts:** [[SonarQube]], [[Snyk]], [[GitHub Code Security]] +- **Related Topics:** [[SAST (정적 애플리케이션 보안 테스트)|SAST (정적 애플리케이션 보안 테스트)]], Quality Gates (품질 게이트), SSDLC (안전한 소프트웨어 개발 수명 주기), AI Code Review (AI 코드 리뷰) +- **Projects/Contexts:** [[SonarQube|SonarQube]], Snyk, GitHub Code Security - **Contradictions/Notes:** 소스에 따르면 SDLC에 AI 도구가 빠르게 도입되어 생산성이 혁신적으로 향상되고 있으나, 이를 뒷받침할 적절한 거버넌스와 보안 정책(SAST 도구 검사 등)이 동반되지 않을 경우 오히려 심각한 보안 취약점과 기술 부채의 증가를 초래할 수 있다고 경고합니다 [2]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/SDLC (소프트웨어 개발 수명 주기).md]] +- Raw Source: 00_Raw/2026-04-20/SDLC (소프트웨어 개발 수명 주기).md --- diff --git a/01_Archive/2026-04-20/SFT (Supervised Fine-Tuning).md b/01_Archive/2026-04-20/SFT (Supervised Fine-Tuning).md index befa3546..4a630411 100644 --- a/01_Archive/2026-04-20/SFT (Supervised Fine-Tuning).md +++ b/01_Archive/2026-04-20/SFT (Supervised Fine-Tuning).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-ACC5DA -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - SFT (Supervised Fine-Tuning)" --- -# [[SFT (Supervised Fine-Tuning)]] +# [[SFT (Supervised Fine-Tuning)|SFT (Supervised Fine-Tuning)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - SFT (Supervised Fine-Tuning)" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/SFT (Supervised Fine-Tuning).md]] +- Raw Source: 00_Raw/2026-04-20/SFT (Supervised Fine-Tuning).md --- diff --git a/01_Archive/2026-04-20/SHACL (Shapes Constraint Language).md b/01_Archive/2026-04-20/SHACL (Shapes Constraint Language).md index 4b9b4087..f40127c2 100644 --- a/01_Archive/2026-04-20/SHACL (Shapes Constraint Language).md +++ b/01_Archive/2026-04-20/SHACL (Shapes Constraint Language).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-B7C59C -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - SHACL (Shapes Constraint Language)" --- -# [[SHACL (Shapes Constraint Language)]] +# [[SHACL (Shapes Constraint Language)|SHACL (Shapes Constraint Language)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - SHACL (Shapes Constraint Langu ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/SHACL (Shapes Constraint Language).md]] +- Raw Source: 00_Raw/2026-04-20/SHACL (Shapes Constraint Language).md --- diff --git a/01_Archive/2026-04-20/SLA-Definition.md b/01_Archive/2026-04-20/SLA-Definition.md index 00fafdd3..628c57ba 100644 --- a/01_Archive/2026-04-20/SLA-Definition.md +++ b/01_Archive/2026-04-20/SLA-Definition.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-37BE33 -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - SLA-Definition" --- -# [[SLA-Definition]] +# [[SLA-Definition|SLA-Definition]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - SLA-Definition" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/SLA-Definition.md]] +- Raw Source: 00_Raw/2026-04-20/SLA-Definition.md --- diff --git a/01_Archive/2026-04-20/SOLID 원칙 (SOLID Principles).md b/01_Archive/2026-04-20/SOLID 원칙 (SOLID Principles).md index 5f4a70ee..b3de53f1 100644 --- a/01_Archive/2026-04-20/SOLID 원칙 (SOLID Principles).md +++ b/01_Archive/2026-04-20/SOLID 원칙 (SOLID Principles).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-D3B79D -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - SOLID 원칙 (SOLID Principles)" --- -# [[SOLID 원칙 (SOLID Principles)]] +# [[SOLID 원칙 (SOLID Principles)|SOLID 원칙 (SOLID Principles)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -36,11 +36,11 @@ github_commit: "[P-Reinforce] Continuous Worker - SOLID 원칙 (SOLID Principles - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[객체 지향 프로그래밍 (OOP)]], [[관심사의 분리 (Separation of Concerns)]], [[의존성 주입 (Dependency Injection)]] -- **Projects/Contexts:** [[엔터프라이즈 애플리케이션 및 점진적 리팩토링]], [[라이브러리 및 확장 가능한 코드베이스]] +- **Related Topics:** [[객체 지향 프로그래밍 (OOP)|객체 지향 프로그래밍 (OOP)]], [[관심사의 분리 (Separation of Concerns)|관심사의 분리 (Separation of Concerns)]], [[의존성 주입 (Dependency Injection)|의존성 주입 (Dependency Injection)]] +- **Projects/Contexts:** [[엔터프라이즈 애플리케이션 및 점진적 리팩토링|엔터프라이즈 애플리케이션 및 점진적 리팩토링]], [[라이브러리 및 확장 가능한 코드베이스|라이브러리 및 확장 가능한 코드베이스]] - **Contradictions/Notes:** 소스 내에서 상충하는 주장은 발견되지 않았습니다. 다만, 단일 책임 원칙(SRP)은 시스템을 고차원적인 수준에서 분리하는 '관심사의 분리(SoC)' 원칙과 종종 비교되며, SRP는 클래스나 모듈의 '책임'이라는 더 미시적인 수준을 다루는 것으로 설명됩니다 [9]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/SOLID 원칙 (SOLID Principles).md]] +- Raw Source: 00_Raw/2026-04-20/SOLID 원칙 (SOLID Principles).md --- diff --git a/01_Archive/2026-04-20/SOLID 원칙.md b/01_Archive/2026-04-20/SOLID 원칙.md index 42aef66e..bc272107 100644 --- a/01_Archive/2026-04-20/SOLID 원칙.md +++ b/01_Archive/2026-04-20/SOLID 원칙.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-FAB206 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - SOLID 원칙" --- -# [[SOLID 원칙]] +# [[SOLID 원칙|SOLID 원칙]] ## 📌 한 줄 통찰 (The Karpathy Summary) > SOLID 원칙은 객체 지향 프로그래밍에서 소프트웨어 설계를 더 이해하기 쉽고, 유연하며, 유지보수하기 좋게 만들기 위해 고안된 5가지 핵심 설계 원칙의 집합이다 [1]. 로버트 C. 마틴(Robert C. Martin)에 의해 대중화된 이 원칙들은 코드의 부패를 방지하고 견고한 기반을 구축하는 데 필수적인 지침으로 작용한다 [1]. 이 원칙들을 올바르게 적용하면 시스템 내 컴포넌트 간의 의존성이 줄어들어 한 부분의 변경이 다른 부분에 미치는 영향을 최소화할 수 있다 [1]. @@ -30,11 +30,11 @@ github_commit: "[P-Reinforce] Continuous Worker - SOLID 원칙" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[객체 지향 프로그래밍(OOP)]], [[관심사의 분리(SoC)]], [[의존성 주입(DI)]] -- **Projects/Contexts:** [[클린 아키텍처(Clean Architecture)]], [[소프트웨어 아키텍처 베스트 프랙티스]] +- **Related Topics:** [[객체 지향 프로그래밍(OOP)|객체 지향 프로그래밍(OOP)]], [[관심사의 분리(SoC)|관심사의 분리(SoC)]], [[의존성 주입(DI)|의존성 주입(DI)]] +- **Projects/Contexts:** [[클린 아키텍처(Clean Architecture)|클린 아키텍처(Clean Architecture)]], [[소프트웨어 아키텍처 베스트 프랙티스|소프트웨어 아키텍처 베스트 프랙티스]] - **Contradictions/Notes:** 소스 전반에 걸쳐 SOLID 원칙은 코드의 복잡성을 줄이고 유지보수성을 높이는 필수적인 기법으로 일관되게 강조되고 있으며, 서로 대립하거나 모순되는 주장은 존재하지 않습니다 [1, 3, 8]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/SOLID 원칙.md]] +- Raw Source: 00_Raw/2026-04-20/SOLID 원칙.md --- diff --git a/01_Archive/2026-04-20/SPA 라우트 전환 성능 최적화.md b/01_Archive/2026-04-20/SPA 라우트 전환 성능 최적화.md index eab233e1..821f9780 100644 --- a/01_Archive/2026-04-20/SPA 라우트 전환 성능 최적화.md +++ b/01_Archive/2026-04-20/SPA 라우트 전환 성능 최적화.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-A346D0 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - SPA 라우트 전환 성능 최적화" --- -# [[SPA 라우트 전환 성능 최적화]] +# [[SPA 라우트 전환 성능 최적화|SPA 라우트 전환 성능 최적화]] ## 📌 한 줄 통찰 (The Karpathy Summary) > SPA(Single Page Application) 라우트 전환은 현대 프론트엔드 애플리케이션에서 메모리 누수가 발생하는 가장 주요한 원인 중 하나입니다 [1]. 이전 라우트의 컴포넌트가 적절히 정리되지 않으면 애플리케이션의 세션 수명 동안 메모리에 지속적으로 누적되어 성능 저하를 유발합니다 [1]. 따라서 성공적인 라우트 전환 성능 최적화를 위해서는 사용되지 않는 리소스와 참조를 철저히 식별하고 해제하는 메모리 관리가 필수적입니다 [1, 2]. @@ -26,11 +26,11 @@ github_commit: "[P-Reinforce] Continuous Worker - SPA 라우트 전환 성능 - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[메모리 누수(Memory Leak)]], [[3-스냅샷 기법(Three-snapshot technique)]], [[가비지 컬렉션(Garbage Collection)]] -- **Projects/Contexts:** [[Browser Memory Leak Detection]] +- **Related Topics:** [[메모리 누수(Memory Leak)|메모리 누수(Memory Leak)]], 3-스냅샷 기법(Three-snapshot technique), [[가비지 컬렉션(Garbage Collection)|가비지 컬렉션(Garbage Collection)]] +- **Projects/Contexts:** [[브라우저 메모리 누수 탐지(Browser Memory Leak Detection)|Browser Memory Leak Detection]] - **Contradictions/Notes:** 소스에서는 SPA 라우트 전환 성능 최적화에 대한 전반적인 프론트엔드 렌더링 최적화 기술은 언급하지 않으며, 오직 컴포넌트 언마운트 시의 정리 실패로 인한 메모리 누수 문제와 그 진단법에만 집중하고 있습니다. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/SPA 라우트 전환 성능 최적화.md]] +- Raw Source: 00_Raw/2026-04-20/SPA 라우트 전환 성능 최적화.md --- diff --git a/01_Archive/2026-04-20/SPARQL (RDF 그래프 질의 언어).md b/01_Archive/2026-04-20/SPARQL (RDF 그래프 질의 언어).md index fd1af564..f6a33dc7 100644 --- a/01_Archive/2026-04-20/SPARQL (RDF 그래프 질의 언어).md +++ b/01_Archive/2026-04-20/SPARQL (RDF 그래프 질의 언어).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-6D75A5 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - SPARQL (RDF 그래프 질의 언어)" --- -# [[SPARQL (RDF 그래프 질의 언어)]] +# [[SPARQL (RDF 그래프 질의 언어)|SPARQL (RDF 그래프 질의 언어)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - SPARQL (RDF 그래프 질의 ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/SPARQL (RDF 그래프 질의 언어).md]] +- Raw Source: 00_Raw/2026-04-20/SPARQL (RDF 그래프 질의 언어).md --- diff --git a/01_Archive/2026-04-20/STEM Laboratory Virtualization.md b/01_Archive/2026-04-20/STEM Laboratory Virtualization.md index 24c6090f..f57a92fa 100644 --- a/01_Archive/2026-04-20/STEM Laboratory Virtualization.md +++ b/01_Archive/2026-04-20/STEM Laboratory Virtualization.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-E8F7C8 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - STEM Laboratory Virtualization" --- -# [[STEM Laboratory Virtualization]] +# [[STEM Laboratory Virtualization|STEM Laboratory Virtualization]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - STEM Laboratory Virtualization ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/STEM Laboratory Virtualization.md]] +- Raw Source: 00_Raw/2026-04-20/STEM Laboratory Virtualization.md --- diff --git a/01_Archive/2026-04-20/SaaS-Product-Management.md b/01_Archive/2026-04-20/SaaS-Product-Management.md index e2a29f00..086afdb8 100644 --- a/01_Archive/2026-04-20/SaaS-Product-Management.md +++ b/01_Archive/2026-04-20/SaaS-Product-Management.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-B72D67 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - SaaS-Product-Management" --- -# [[SaaS-Product-Management]] +# [[SaaS-Product-Management|SaaS-Product-Management]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - SaaS-Product-Management" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/SaaS-Product-Management.md]] +- Raw Source: 00_Raw/2026-04-20/SaaS-Product-Management.md --- diff --git a/01_Archive/2026-04-20/SaaS-Retention-Strategies.md b/01_Archive/2026-04-20/SaaS-Retention-Strategies.md index 0199383d..801ac978 100644 --- a/01_Archive/2026-04-20/SaaS-Retention-Strategies.md +++ b/01_Archive/2026-04-20/SaaS-Retention-Strategies.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-B5B823 -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - SaaS-Retention-Strategies" --- -# [[SaaS-Retention-Strategies]] +# [[SaaS-Retention-Strategies|SaaS-Retention-Strategies]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - SaaS-Retention-Strategies" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/SaaS-Retention-Strategies.md]] +- Raw Source: 00_Raw/2026-04-20/SaaS-Retention-Strategies.md --- diff --git a/01_Archive/2026-04-20/Sandbox Simulations (e.g., Minecraft, Dwarf Fortress).md b/01_Archive/2026-04-20/Sandbox Simulations (e.g., Minecraft, Dwarf Fortress).md index 6d61cb63..17ee43bc 100644 --- a/01_Archive/2026-04-20/Sandbox Simulations (e.g., Minecraft, Dwarf Fortress).md +++ b/01_Archive/2026-04-20/Sandbox Simulations (e.g., Minecraft, Dwarf Fortress).md @@ -1,4 +1,4 @@ -[[Sandbox Simulations (e.g., Minecraft, Dwarf Fortress)]] +[[Sandbox Simulations (e.g., Minecraft, Dwarf Fortress)|Sandbox Simulations (e.g., Minecraft, Dwarf Fortress)]] 📌 Brief Summary Sandbox simulations are a genre of interactive software characterized by emergent gameplay, high degrees of player agency, and the absence of predefined win-states or linear progression. These systems rely on complex underlying rule-sets—often involving cellular automata, procedural generation, and agent-based modeling—to create dynamic environments where complex behaviors emerge from simple local interactions. @@ -10,8 +10,8 @@ Sandbox simulations are a genre of interactive software characterized by emergen * **Computational Constraints and Optimization:** A significant research challenge in sandbox design is the "simulation bottleneck." Managing thousands of interacting entities requires sophisticated optimization techniques, such as spatial partitioning (Quadtrees/Octrees), multithreading, and chunk-based loading/unloading. Developers must balance the fidelity of the simulation (the depth of the rule-set) against the computational cost of maintaining a persistent, reactive state across a massive coordinate space. 🔗 Knowledge Connections -* Related Topics: [[Emergent Gameplay]], [[Procedural Content Generation (PCG)]], [[Agent-Based Modeling (ABM)]], [[Cellular Automata]] -* Projects/Contexts: [[Computational Ecology]], [[Artificial Life (ALife)]], [[Game Engine Architecture]], [[Digital Twins]] +* Related Topics: [[Emergent Gameplay|Emergent Gameplay]], [[Procedural Content Generation (PCG)|Procedural Content Generation (PCG)]], [[Agent-Based Modeling (ABM)|Agent-Based Modeling (ABM)]], [[Cellular Automata|Cellular Automata]] +* Projects/Contexts: [[Computational Ecology|Computational Ecology]], [[Artificial Life (ALife)|Artificial Life (ALife)]], [[Game Engine Architecture|Game Engine Architecture]], [[Digital Twins|Digital Twins]] * Contradictions/Notes: There is an ongoing tension in development between "Simulation Depth" and "Performance Scalability"; increasing the granularity of physical interactions (e.g., individual fluid molecules) exponentially increases computational complexity, often necessitating a move toward simplified approximations rather than true physics-based modeling. Last updated: 2026-04-16 \ No newline at end of file diff --git a/01_Archive/2026-04-20/Sandbox Simulations (eg Minecraft Dwarf Fortress).md b/01_Archive/2026-04-20/Sandbox Simulations (eg Minecraft Dwarf Fortress).md index 74a6b1eb..7f3f2b3f 100644 --- a/01_Archive/2026-04-20/Sandbox Simulations (eg Minecraft Dwarf Fortress).md +++ b/01_Archive/2026-04-20/Sandbox Simulations (eg Minecraft Dwarf Fortress).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-0DFB46 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Sandbox Simulations (eg Minecraft Dwarf Fortress)" --- -# [[Sandbox Simulations (eg Minecraft Dwarf Fortress)]] +# [[Sandbox Simulations (eg Minecraft Dwarf Fortress)|Sandbox Simulations (eg Minecraft Dwarf Fortress)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Sandbox Simulations (eg Minecr ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Sandbox Simulations (e.g., Minecraft, Dwarf Fortress).md]] +- Raw Source: 00_Raw/2026-04-20/Sandbox Simulations (e.g., Minecraft, Dwarf Fortress).md --- diff --git a/01_Archive/2026-04-20/Sandbox-Simulation.md b/01_Archive/2026-04-20/Sandbox-Simulation.md index e831c294..5db0c26b 100644 --- a/01_Archive/2026-04-20/Sandbox-Simulation.md +++ b/01_Archive/2026-04-20/Sandbox-Simulation.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-D0C092 -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Sandbox-Simulation" --- -# [[Sandbox-Simulation]] +# [[Sandbox-Simulation|Sandbox-Simulation]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Sandbox-Simulation" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Sandbox-Simulation.md]] +- Raw Source: 00_Raw/2026-04-20/Sandbox-Simulation.md --- diff --git a/01_Archive/2026-04-20/Santa Fe Institute.md b/01_Archive/2026-04-20/Santa Fe Institute.md index 2ee81df9..64375275 100644 --- a/01_Archive/2026-04-20/Santa Fe Institute.md +++ b/01_Archive/2026-04-20/Santa Fe Institute.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-6E6047 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Santa Fe Institute" --- -# [[Santa Fe Institute]] +# [[Santa Fe Institute|Santa Fe Institute]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Santa Fe Institute" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Santa Fe Institute.md]] +- Raw Source: 00_Raw/2026-04-20/Santa Fe Institute.md --- diff --git a/01_Archive/2026-04-20/Satisfiability-Problem-(SAT).md b/01_Archive/2026-04-20/Satisfiability-Problem-(SAT).md index 30bfaff1..e0d44056 100644 --- a/01_Archive/2026-04-20/Satisfiability-Problem-(SAT).md +++ b/01_Archive/2026-04-20/Satisfiability-Problem-(SAT).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-55CA55 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Satisfiability-Problem-(SAT)" --- -# [[Satisfiability-Problem-(SAT)]] +# [[Satisfiability-Problem-(SAT)|Satisfiability-Problem-(SAT)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Satisfiability-Problem-(SAT)" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Satisfiability-Problem-(SAT).md]] +- Raw Source: 00_Raw/2026-04-20/Satisfiability-Problem-(SAT).md --- diff --git a/01_Archive/2026-04-20/Satisfies Operator.md b/01_Archive/2026-04-20/Satisfies Operator.md index dbde3131..2164f31a 100644 --- a/01_Archive/2026-04-20/Satisfies Operator.md +++ b/01_Archive/2026-04-20/Satisfies Operator.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-B08904 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Satisfies Operator" --- -# [[Satisfies Operator]] +# [[Satisfies Operator|Satisfies Operator]] ## 📌 한 줄 통찰 (The Karpathy Summary) > `satisfies` 연산자는 TypeScript 4.9에 도입된 기능으로, 객체가 특정 타입의 형태를 준수하는지 검증하면서도 해당 객체의 구체적인 타입(리터럴 타입 등)을 넓히지(widening) 않고 그대로 유지하는 역할을 합니다 [1-3]. 기존의 타입 어노테이션(`:`)이 가진 타입 확장 문제와 타입 단언(`as`)이 가진 검증 누락 문제를 동시에 해결하여 엄격한 타입 검사와 정밀한 타입 추론을 모두 제공합니다 [1, 3, 4]. 이를 통해 컴파일 타임에 잉여 속성이나 오타를 잡아내어 코드의 안정성과 예측 가능성을 크게 높여줍니다 [3, 5]. @@ -28,11 +28,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Satisfies Operator" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Excess Property Checking]], [[Structural Typing]], [[Discriminated Unions]], [[Type Narrowing]] -- **Projects/Contexts:** [[설정 객체(Configuration Objects) 검증]], [[데이터 매핑 및 변환(Data Mapping & Transformation)]] +- **Related Topics:** [[Excess Property Checking|Excess Property Checking]], [[Structural Typing|Structural Typing]], [[Discriminated Unions|Discriminated Unions]], [[Type Narrowing|Type Narrowing]] +- **Projects/Contexts:** 설정 객체(Configuration Objects) 검증, 데이터 매핑 및 변환(Data Mapping & Transformation) - **Contradictions/Notes:** 타입 단언(`as`)은 대상 타입과 근본적으로 호환되지 않는 경우가 아니면 잉여 속성이 포함되어 있어도 타입 검사를 강제하지 않고 통과시켜 조용한 에러(silent errors)를 낳을 수 있지만, `satisfies`는 이를 허용하지 않고 컴파일 타임에 엄격히 잡아냅니다 [10]. 또한, `satisfies`는 본래 추가적인 잉여 속성을 허용하는 특성이 있으나, 만약 추가된 속성의 이름이 대상 타입의 속성 철자와 비슷하여 오타로 의심될 경우에는 잠재적 오류로 간주하고 경고를 발생시킵니다 [2, 14, 15]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/Satisfies Operator.md]] +- Raw Source: 00_Raw/2026-04-20/Satisfies Operator.md --- diff --git a/01_Archive/2026-04-20/Scaffolding (Instructional Technique).md b/01_Archive/2026-04-20/Scaffolding (Instructional Technique).md index fee5e97f..5a98603f 100644 --- a/01_Archive/2026-04-20/Scaffolding (Instructional Technique).md +++ b/01_Archive/2026-04-20/Scaffolding (Instructional Technique).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-B407CA -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Scaffolding (Instructional Technique)" --- -# [[Scaffolding (Instructional Technique)]] +# [[Scaffolding (Instructional Technique)|Scaffolding (Instructional Technique)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Scaffolding (Instructional Tec ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Scaffolding (Instructional Technique).md]] +- Raw Source: 00_Raw/2026-04-20/Scaffolding (Instructional Technique).md --- diff --git a/01_Archive/2026-04-20/Scavenge.md b/01_Archive/2026-04-20/Scavenge.md index 2f636397..1cd3fdd7 100644 --- a/01_Archive/2026-04-20/Scavenge.md +++ b/01_Archive/2026-04-20/Scavenge.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-E7007A -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Scavenge" --- -# [[Scavenge]] +# [[Scavenge|Scavenge]] ## 📌 한 줄 통찰 (The Karpathy Summary) > Scavenge(스캐빈지)는 V8 엔진을 비롯한 가비지 컬렉션(GC) 시스템에서 젊은 세대(Young Generation) 메모리를 정리하기 위해 수행되는 마이너 가비지 컬렉션(Minor GC) 주기입니다 [1, 2]. 주로 새로운 객체가 할당되는 '새로운 공간(New-space)'이 가득 차서 할당에 실패했을 때 트리거되며, 죽은 객체를 빠르게 제거하고 살아있는 객체를 보존합니다 [1, 2]. 애플리케이션 실행 중 매우 빈번하게 발생하기 때문에 성능에 미치는 영향을 최소화하도록 극히 빠른 속도로 동작하게 설계되었습니다 [3]. @@ -23,11 +23,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Scavenge" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Garbage Collection]], [[New-space (Young Generation)]], [[Old-space (Old Generation)]], [[Cheney's Algorithm]], [[Mark-Sweep-Compact]] -- **Projects/Contexts:** [[V8 JavaScript Engine]], [[Orinoco GC]], [[Eclipse OpenJ9]] +- **Related Topics:** [[Garbage Collection|Garbage Collection]], [[New Space(Young Generation)|New-space (Young Generation)]], [[Old Space(Old Generation)|Old-space (Old Generation)]], [[Cheney's Algorithm|Cheney's Algorithm]], [[Mark-Sweep-Compact|Mark-Sweep-Compact]] +- **Projects/Contexts:** [[V8 JavaScript Engine|V8 JavaScript Engine]], [[Orinoco GC|Orinoco GC]], Eclipse OpenJ9 - **Contradictions/Notes:** 소스 간의 뚜렷한 모순은 없으나, 스캐빈지가 발생하면 본래 메인 스레드가 정지하는 'Stop-the-world' 현상이 발생하지만 최신 V8 엔진(Orinoco)에서는 다수의 스레드를 동원한 병렬 처리(Parallel)를 적용하여 사용자가 느끼는 지연(Jank)을 획기적으로 줄였다고 명시하고 있습니다 [6, 10, 13]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Scavenge.md]] +- Raw Source: 00_Raw/2026-04-20/Scavenge.md --- diff --git a/01_Archive/2026-04-20/Scavenger 알고리즘.md b/01_Archive/2026-04-20/Scavenger 알고리즘.md index 553b8d95..f032860b 100644 --- a/01_Archive/2026-04-20/Scavenger 알고리즘.md +++ b/01_Archive/2026-04-20/Scavenger 알고리즘.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-04124F -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Scavenger 알고리즘" --- -# [[Scavenger 알고리즘]] +# [[Scavenger 알고리즘|Scavenger 알고리즘]] ## 📌 한 줄 통찰 (The Karpathy Summary) > Scavenger 알고리즘은 V8 JavaScript 엔진에서 새로운 객체가 주로 할당되는 '새로운 공간(New-space)'의 가비지를 수집하는 마이너 가비지 컬렉션(Minor GC) 알고리즘입니다 [1-3]. 이 알고리즘은 공간을 두 개의 동일한 크기(to-space와 from-space)로 나누고 살아남은 활성 객체만 새로운 공간으로 복사하여 압축하는 세미스페이스(semi-space) 방식을 통해 메모리 단편화를 방지하고 매우 빠르게 메모리를 회수합니다 [3-5]. 최근의 V8 엔진에서는 Orinoco 프로젝트를 통해 메인 스레드와 헬퍼 스레드에 작업을 분산시키는 병렬(Parallel) 방식으로 진화하여 메인 스레드의 일시 정지 시간을 획기적으로 단축시켰습니다 [6-8]. @@ -24,11 +24,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Scavenger 알고리즘" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Minor GC]], [[Young Generation]], [[Cheney's Algorithm]], [[Write Barriers]], [[Orinoco]] -- **Projects/Contexts:** [[V8 엔진 메모리 관리 (V8 Memory Management)]], [[가비지 컬렉션 최적화]] +- **Related Topics:** [[마이너 가비지 컬렉션(Minor GC)|Minor GC]], Young Generation, [[Cheney's Algorithm|Cheney's Algorithm]], Write Barriers, [[Orinoco|Orinoco]] +- **Projects/Contexts:** V8 엔진 메모리 관리 (V8 Memory Management), 가비지 컬렉션 최적화 - **Contradictions/Notes:** 과거 버전의 V8에서는 Scavenger가 단일 코어 환경에 적합한 완전한 동기식 Cheney 알고리즘을 구현했으나, 현재 크롬 및 Node.js의 멀티코어 환경 요구에 맞추어 메인 스레드와 워커 스레드가 동적으로 작업을 분배하는 병렬(Parallel) 복사 가비지 컬렉터로 진화했음이 기록되어 있습니다 [10, 20]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Scavenger 알고리즘.md]] +- Raw Source: 00_Raw/2026-04-20/Scavenger 알고리즘.md --- diff --git a/01_Archive/2026-04-20/Scavenger(Minor GC).md b/01_Archive/2026-04-20/Scavenger(Minor GC).md index 0381b89c..4ce05a64 100644 --- a/01_Archive/2026-04-20/Scavenger(Minor GC).md +++ b/01_Archive/2026-04-20/Scavenger(Minor GC).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-7DB27B -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Scavenger(Minor GC)" --- -# [[Scavenger(Minor GC)]] +# [[Scavenger(Minor GC)|Scavenger(Minor GC)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > Scavenger(Minor GC)는 V8 엔진에서 새로운 객체가 할당되는 '새로운 공간(New-space)' 또는 '젊은 세대(Young Generation)'의 메모리를 빠르고 효율적으로 정리하기 위해 사용되는 가비지 컬렉션 메커니즘입니다 [1-3]. 이 알고리즘은 **"대부분의 객체는 생성된 직후 죽는다"는 세대적 가설(Generational hypothesis)**을 바탕으로 짧은 수명의 객체들을 신속하게 제거합니다 [2, 4, 5]. 빈번하게 발생하는 만큼 실행 속도가 매우 빠르며, 객체를 복사하고 이동하는 과정을 통해 메모리 단편화를 방지하는 핵심적인 역할을 합니다 [6-8]. @@ -20,11 +20,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Scavenger(Minor GC)" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Young Generation]], [[Mark-Sweep/Mark-Compact(Major GC)]], [[Write Barriers]], [[Cheney's Algorithm]], [[Orinoco GC]] -- **Projects/Contexts:** [[V8 JavaScript Engine Memory Management]] +- **Related Topics:** Young Generation, Mark-Sweep/Mark-Compact(Major GC), Write Barriers, [[Cheney's Algorithm|Cheney's Algorithm]], [[Orinoco GC|Orinoco GC]] +- **Projects/Contexts:** V8 JavaScript Engine Memory Management - **Contradictions/Notes:** 과거 버전의 V8에서는 스캐빈저가 동기적인 Cheney's 알고리즘을 사용하였으나, V8 v6.2 이후부터는 다중 코어 환경의 이점을 살리기 위해 Halstead 알고리즘과 유사한 동적 작업 훔치기(work stealing) 기법을 사용하는 병렬 처리 구조로 진화했다는 점이 소스에 기록되어 있습니다 [22, 25]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Scavenger(Minor GC).md]] +- Raw Source: 00_Raw/2026-04-20/Scavenger(Minor GC).md --- diff --git a/01_Archive/2026-04-20/Scavenger(마이너 GC).md b/01_Archive/2026-04-20/Scavenger(마이너 GC).md index 61f90af3..ea46953b 100644 --- a/01_Archive/2026-04-20/Scavenger(마이너 GC).md +++ b/01_Archive/2026-04-20/Scavenger(마이너 GC).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-735166 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Scavenger(마이너 GC)" --- -# [[Scavenger(마이너 GC)]] +# [[Scavenger(마이너 GC)|Scavenger(마이너 GC)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -27,11 +27,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Scavenger(마이너 GC)" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[New Space(Young Generation)]], [[Cheney's Algorithm]], [[Promotion(승격)]], [[Major GC(Mark-Sweep/Mark-Compact)]] -- **Projects/Contexts:** [[V8 JavaScript Engine]], [[IBM SDK (gencon GC policy)]] +- **Related Topics:** [[New Space(Young Generation)|New Space(Young Generation)]], [[Cheney's Algorithm|Cheney's Algorithm]], Promotion(승격), Major GC(Mark-Sweep/Mark-Compact) +- **Projects/Contexts:** [[V8 JavaScript Engine|V8 JavaScript Engine]], IBM SDK (gencon GC policy) - **Contradictions/Notes:** 소스 간의 내용 모순은 발견되지 않았습니다. V8 엔진의 마이너 GC 메커니즘과 IBM SDK(gencon 정책)의 스캐빈지 작업은 구현 환경은 다르지만, 모두 '주로 새롭게 할당되는 작은 공간을 대상으로 하여 빠른 주기로 살아있는 객체를 복사 및 승격한다'는 공통된 역할을 성공적으로 수행하고 있습니다. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Scavenger(마이너 GC).md]] +- Raw Source: 00_Raw/2026-04-20/Scavenger(마이너 GC).md --- diff --git a/01_Archive/2026-04-20/Scheduler API.md b/01_Archive/2026-04-20/Scheduler API.md index 697113a4..8963de53 100644 --- a/01_Archive/2026-04-20/Scheduler API.md +++ b/01_Archive/2026-04-20/Scheduler API.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-6B64AB -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Scheduler API" --- -# [[Scheduler API]] +# [[Scheduler API|Scheduler API]] ## 📌 한 줄 통찰 (The Karpathy Summary) > Scheduler API는 개발자가 브라우저 내에서 다양한 처리 작업이 실행되는 시점을 더 쉽게 제어할 수 있도록 도와주는 기능입니다 [1]. 길게 실행되는 작업은 여러 개의 짧은 작업보다 상호작용 지연을 더 많이 유발하기 때문에, 이 API를 통해 작업을 분할하여 사용자 경험을 개선할 수 있습니다 [1]. 특히 작업 중간에 제어권을 브라우저에 양보함으로써 다른 중요한 상호작용이 지연 없이 우선적으로 처리될 수 있게 합니다 [1]. @@ -22,11 +22,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Scheduler API" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[scheduler.yield()]], [[Interaction to Next Paint (INP)]] -- **Projects/Contexts:** [[Web Performance Optimization]] +- **Related Topics:** scheduler.yield(), [[Interaction to Next Paint (INP)|Interaction to Next Paint (INP)]] +- **Projects/Contexts:** [[Web Performance Optimization|Web Performance Optimization]] - **Contradictions/Notes:** 소스 내에 상충하는 정보는 없습니다. 다만, Chrome(2024년)과 Firefox(2025년 8월)는 해당 API를 지원하지만 Safari는 아직 지원하지 않는다는 호환성 제약이 명시되어 있습니다 [2]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Scheduler API.md]] +- Raw Source: 00_Raw/2026-04-20/Scheduler API.md --- diff --git a/01_Archive/2026-04-20/Scheduling-and-Timetabling.md b/01_Archive/2026-04-20/Scheduling-and-Timetabling.md index 3c2d8903..9a463b52 100644 --- a/01_Archive/2026-04-20/Scheduling-and-Timetabling.md +++ b/01_Archive/2026-04-20/Scheduling-and-Timetabling.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-FEBDAB -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Scheduling-and-Timetabling" --- -# [[Scheduling-and-Timetabling]] +# [[Scheduling-and-Timetabling|Scheduling-and-Timetabling]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Scheduling-and-Timetabling" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Scheduling-and-Timetabling.md]] +- Raw Source: 00_Raw/2026-04-20/Scheduling-and-Timetabling.md --- diff --git a/01_Archive/2026-04-20/Schema-Driven-Development.md b/01_Archive/2026-04-20/Schema-Driven-Development.md index 69bf58c8..bde72aca 100644 --- a/01_Archive/2026-04-20/Schema-Driven-Development.md +++ b/01_Archive/2026-04-20/Schema-Driven-Development.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-DE27F0 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Schema-Driven-Development" --- -# [[Schema-Driven-Development]] +# [[Schema-Driven-Development|Schema-Driven-Development]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Schema-Driven-Development" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Schema-Driven-Development.md]] +- Raw Source: 00_Raw/2026-04-20/Schema-Driven-Development.md --- diff --git a/01_Archive/2026-04-20/Schema.org.md b/01_Archive/2026-04-20/Schema.org.md index 08303825..f8ebdb1b 100644 --- a/01_Archive/2026-04-20/Schema.org.md +++ b/01_Archive/2026-04-20/Schema.org.md @@ -1,4 +1,4 @@ -[[Schema.org]] +[[Schema.org|Schema.org]] 📌 Brief Summary Schema.org is a collaborative, community-driven initiative—managed by Google, Microsoft, Yahoo, and Yandex—to create a shared vocabulary of structured data markup. It provides a standardized set of microdatamarks (types, properties, and values) that allow search engines and other machines to interpret the semantic meaning of web content, facilitating the generation of rich results and knowledge graphs. @@ -13,8 +13,8 @@ Schema.org is a collaborative, community-driven initiative—managed by Google, * **Knowledge Graph Integration:** Beyond simple snippets, Schema.org serves as the foundational layer for Knowledge Graphs. Search engines use this structured data to populate entities in their databases, allowing them to answer complex natural language queries by understanding the relationship between disparate data points (e.g., linking an `Author` to a `Book` via a `Work` entity). 🔗 Knowledge Connections -* Related Topics: [[Semantic-Web]], [[JSON-LD]], [[Linked-Data]], [[Knowledge-Graph]], [[Microdata]] -* Projects/Contexts: [[Google-Search-Central]], [[W3C-Semantic-Web-Standards]], [[SEO-Optimization]] +* Related Topics: [[Semantic-Web|Semantic-Web]], JSON-LD, Linked-Data, [[Knowledge-Graph|Knowledge-Graph]], Microdata +* Projects/Contexts: Google-Search-Central, [[W3C-Semantic-Web-Standards|W3C-Semantic-Web-Standards]], SEO-Optimization * Contradictions/Notes: While Schema.org provides the vocabulary, search engines are not obligated to display rich results for all implemented types; implementation of "unsupported" or "non-documented" properties may result in no visible change in SERPs despite valid syntax. Last updated: 2026-04-16 \ No newline at end of file diff --git a/01_Archive/2026-04-20/Schemaorg.md b/01_Archive/2026-04-20/Schemaorg.md index b0d8b6d1..ac50c8de 100644 --- a/01_Archive/2026-04-20/Schemaorg.md +++ b/01_Archive/2026-04-20/Schemaorg.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-A3B261 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Schemaorg" --- -# [[Schemaorg]] +# [[Schemaorg|Schemaorg]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Schemaorg" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Schema.org.md]] +- Raw Source: 00_Raw/2026-04-20/Schema.org.md --- diff --git a/01_Archive/2026-04-20/SeL4-Microkernel.md b/01_Archive/2026-04-20/SeL4-Microkernel.md index c824e6f2..2ad6fa77 100644 --- a/01_Archive/2026-04-20/SeL4-Microkernel.md +++ b/01_Archive/2026-04-20/SeL4-Microkernel.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-0A0995 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - SeL4-Microkernel" --- -# [[SeL4-Microkernel]] +# [[SeL4-Microkernel|SeL4-Microkernel]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - SeL4-Microkernel" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/SeL4-Microkernel.md]] +- Raw Source: 00_Raw/2026-04-20/SeL4-Microkernel.md --- diff --git a/01_Archive/2026-04-20/Search-Based Procedural Content Generation (SBPCG).md b/01_Archive/2026-04-20/Search-Based Procedural Content Generation (SBPCG).md index 10473674..f7c8b0ad 100644 --- a/01_Archive/2026-04-20/Search-Based Procedural Content Generation (SBPCG).md +++ b/01_Archive/2026-04-20/Search-Based Procedural Content Generation (SBPCG).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-8371CD -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Search-Based Procedural Content Generation (SBPCG)" --- -# [[Search-Based Procedural Content Generation (SBPCG)]] +# [[Search-Based Procedural Content Generation (SBPCG)|Search-Based Procedural Content Generation (SBPCG)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Search-Based Procedural Conten ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Search-Based Procedural Content Generation (SBPCG).md]] +- Raw Source: 00_Raw/2026-04-20/Search-Based Procedural Content Generation (SBPCG).md --- diff --git a/01_Archive/2026-04-20/Section-508-Compliance.md b/01_Archive/2026-04-20/Section-508-Compliance.md index e6c1c5cd..37ce0f7d 100644 --- a/01_Archive/2026-04-20/Section-508-Compliance.md +++ b/01_Archive/2026-04-20/Section-508-Compliance.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-A56544 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Section-508-Compliance" --- -# [[Section-508-Compliance]] +# [[Section-508-Compliance|Section-508-Compliance]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Section-508-Compliance" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Section-508-Compliance.md]] +- Raw Source: 00_Raw/2026-04-20/Section-508-Compliance.md --- diff --git a/01_Archive/2026-04-20/Segments.ai.md b/01_Archive/2026-04-20/Segments.ai.md index 6c314674..447afcfe 100644 --- a/01_Archive/2026-04-20/Segments.ai.md +++ b/01_Archive/2026-04-20/Segments.ai.md @@ -1,4 +1,4 @@ -# [[Segments.ai]] +# [[Segments.ai|Segments.ai]] ## 📌 Brief Summary Segments.ai는 수백만 개의 3D 포인트와 원활하게 상호작용할 수 있는 기능을 제공하는 3D 분할(segmentation) 플랫폼이자 라이다(LiDAR) 포인트 클라우드 라벨링 도구입니다 [1, 2]. 2025년에서 2026년 사이에 렌더링 파이프라인을 WebGL에서 WebGPU로 성공적으로 전환하여 100배의 성능 향상을 달성했습니다 [1, 3]. 이 플랫폼은 깊은 그래픽스 전문 지식 없이도 Three.js를 활용하여 특화된 성능 최적화를 구현한 대표적인 사례입니다 [2]. @@ -10,8 +10,8 @@ Segments.ai는 수백만 개의 3D 포인트와 원활하게 상호작용할 수 * **대규모 데이터 처리의 효율성 확보:** 이러한 렌더링 성능 개선 덕분에 수백만 개의 점으로 구성된 방대한 데이터셋에서도 끊김 없이 부드럽고 원활한 상호작용(seamless interaction)이 가능해졌습니다 [1, 2]. ## 🔗 Knowledge Connections -- **Related Topics:** [[WebGPU]], [[Three.js]], [[WebGL]], [[LiDAR point cloud]] -- **Projects/Contexts:** [[Utsubo]], [[Three.js WebGPU 마이그레이션 사례]] +- **Related Topics:** [[WebGPU|WebGPU]], [[Three.js|Three.js]], [[WebGL|WebGL]], LiDAR point cloud +- **Projects/Contexts:** [[Utsubo|Utsubo]], Three.js WebGPU 마이그레이션 사례 - **Contradictions/Notes:** 소스에 관련하여 모순되는 정보는 없습니다. --- diff --git a/01_Archive/2026-04-20/Segmentsai.md b/01_Archive/2026-04-20/Segmentsai.md index 0866f322..b7ee6dd7 100644 --- a/01_Archive/2026-04-20/Segmentsai.md +++ b/01_Archive/2026-04-20/Segmentsai.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-A08DC7 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Segmentsai" --- -# [[Segmentsai]] +# [[Segmentsai|Segmentsai]] ## 📌 한 줄 통찰 (The Karpathy Summary) > Segments.ai는 수백만 개의 3D 포인트와 원활하게 상호작용할 수 있는 기능을 제공하는 3D 분할(segmentation) 플랫폼이자 라이다(LiDAR) 포인트 클라우드 라벨링 도구입니다 [1, 2]. 2025년에서 2026년 사이에 렌더링 파이프라인을 WebGL에서 WebGPU로 성공적으로 전환하여 100배의 성능 향상을 달성했습니다 [1, 3]. 이 플랫폼은 깊은 그래픽스 전문 지식 없이도 Three.js를 활용하여 특화된 성능 최적화를 구현한 대표적인 사례입니다 [2]. @@ -23,11 +23,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Segmentsai" - **정책 변화:** AI 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[WebGPU]], [[Three.js]], [[WebGL]], [[LiDAR point cloud]] -- **Projects/Contexts:** [[Utsubo]], [[Three.js WebGPU 마이그레이션 사례]] +- **Related Topics:** [[WebGPU|WebGPU]], [[Three.js|Three.js]], [[WebGL|WebGL]], LiDAR point cloud +- **Projects/Contexts:** [[Utsubo|Utsubo]], Three.js WebGPU 마이그레이션 사례 - **Contradictions/Notes:** 소스에 관련하여 모순되는 정보는 없습니다. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Segments.ai.md]] +- Raw Source: 00_Raw/2026-04-20/Segments.ai.md --- diff --git a/01_Archive/2026-04-20/Self-Consistency (자기 일관성 디코딩).md b/01_Archive/2026-04-20/Self-Consistency (자기 일관성 디코딩).md index 1cbae5eb..82713621 100644 --- a/01_Archive/2026-04-20/Self-Consistency (자기 일관성 디코딩).md +++ b/01_Archive/2026-04-20/Self-Consistency (자기 일관성 디코딩).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-E25B8B -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Self-Consistency (자기 일관성 디코딩)" --- -# [[Self-Consistency (자기 일관성 디코딩)]] +# [[Self-Consistency (자기 일관성 디코딩)|Self-Consistency (자기 일관성 디코딩)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Self-Consistency (자기 일 ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Self-Consistency (자기 일관성 디코딩).md]] +- Raw Source: 00_Raw/2026-04-20/Self-Consistency (자기 일관성 디코딩).md --- diff --git a/01_Archive/2026-04-20/Self-Determination Theory.md b/01_Archive/2026-04-20/Self-Determination Theory.md index 4b9aabf0..821dd690 100644 --- a/01_Archive/2026-04-20/Self-Determination Theory.md +++ b/01_Archive/2026-04-20/Self-Determination Theory.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-2C7B68 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Self-Determination Theory" --- -# [[Self-Determination Theory]] +# [[Self-Determination Theory|Self-Determination Theory]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Self-Determination Theory" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Self-Determination Theory.md]] +- Raw Source: 00_Raw/2026-04-20/Self-Determination Theory.md --- diff --git a/01_Archive/2026-04-20/Self-Determination-Theory.md b/01_Archive/2026-04-20/Self-Determination-Theory.md index 798ca219..860ed3ab 100644 --- a/01_Archive/2026-04-20/Self-Determination-Theory.md +++ b/01_Archive/2026-04-20/Self-Determination-Theory.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-576385 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Self-Determination-Theory" --- -# [[Self-Determination-Theory]] +# [[Self-Determination-Theory|Self-Determination-Theory]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Self-Determination-Theory" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Self-Determination-Theory.md]] +- Raw Source: 00_Raw/2026-04-20/Self-Determination-Theory.md --- diff --git a/01_Archive/2026-04-20/Self-Organized Criticality.md b/01_Archive/2026-04-20/Self-Organized Criticality.md index 69cb80dd..a1c99d65 100644 --- a/01_Archive/2026-04-20/Self-Organized Criticality.md +++ b/01_Archive/2026-04-20/Self-Organized Criticality.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-01E518 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Self-Organized Criticality" --- -# [[Self-Organized Criticality]] +# [[Self-Organized Criticality|Self-Organized Criticality]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Self-Organized Criticality" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Self-Organized Criticality.md]] +- Raw Source: 00_Raw/2026-04-20/Self-Organized Criticality.md --- diff --git a/01_Archive/2026-04-20/Self-Play (자기 대결 기반 강화학습).md b/01_Archive/2026-04-20/Self-Play (자기 대결 기반 강화학습).md index c72008ba..bf78ddd0 100644 --- a/01_Archive/2026-04-20/Self-Play (자기 대결 기반 강화학습).md +++ b/01_Archive/2026-04-20/Self-Play (자기 대결 기반 강화학습).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-4CE048 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Self-Play (자기 대결 기반 강화학습)" --- -# [[Self-Play (자기 대결 기반 강화학습)]] +# [[Self-Play (자기 대결 기반 강화학습)|Self-Play (자기 대결 기반 강화학습)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Self-Play (자기 대결 기 ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Self-Play (자기 대결 기반 강화학습).md]] +- Raw Source: 00_Raw/2026-04-20/Self-Play (자기 대결 기반 강화학습).md --- diff --git a/01_Archive/2026-04-20/Self-Regulation.md b/01_Archive/2026-04-20/Self-Regulation.md index 76a415f7..e20c0065 100644 --- a/01_Archive/2026-04-20/Self-Regulation.md +++ b/01_Archive/2026-04-20/Self-Regulation.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-70F3AC -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Self-Regulation" --- -# [[Self-Regulation]] +# [[Self-Regulation|Self-Regulation]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Self-Regulation" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Self-Regulation.md]] +- Raw Source: 00_Raw/2026-04-20/Self-Regulation.md --- diff --git a/01_Archive/2026-04-20/Semantic Grounding Provenance.md b/01_Archive/2026-04-20/Semantic Grounding Provenance.md index c5febfd4..afab7402 100644 --- a/01_Archive/2026-04-20/Semantic Grounding Provenance.md +++ b/01_Archive/2026-04-20/Semantic Grounding Provenance.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-479D8D -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Semantic Grounding Provenance" --- -# [[Semantic Grounding Provenance]] +# [[Semantic Grounding Provenance|Semantic Grounding Provenance]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Semantic Grounding Provenance ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Semantic Grounding & Provenance.md]] +- Raw Source: 00_Raw/2026-04-20/Semantic Grounding & Provenance.md --- diff --git a/01_Archive/2026-04-20/Semantic Grounding & Provenance.md b/01_Archive/2026-04-20/Semantic Grounding & Provenance.md index 4946bca9..3b6037d6 100644 --- a/01_Archive/2026-04-20/Semantic Grounding & Provenance.md +++ b/01_Archive/2026-04-20/Semantic Grounding & Provenance.md @@ -1,4 +1,4 @@ -[[Semantic Grounding (의미적 접지) & Provenance (출처 역추적)]] +Semantic Grounding (의미적 접지) & Provenance (출처 역추적) 📌 Brief Summary @@ -93,8 +93,8 @@ Provenance(출처 태깅) → 각 사실에 트리플 출처 URI 부착 🔗 Knowledge Connections -- **Related Topics:** [[LLM Hallucination (언어 모델 환각)]], [[RAG (검색 증강 생성)]], [[GraphRAG (그래프 기반 검색 증강 생성)]], [[RDF와 OWL]], [[RDF-star (RDF*)]], [[지식 그래프 (Knowledge Graph)]], [[온톨로지 (Ontology)]], [[Ontology-Guided Knowledge Extraction]] -- **Projects/Contexts:** [[온톨로지 지식 베이스]], [[AI 신뢰성·투명성]], [[LLM 환각 방지]] +- **Related Topics:** [[LLM Hallucination (언어 모델 환각)|LLM Hallucination (언어 모델 환각)]], [[RAG (검색 증강 생성)|RAG (검색 증강 생성)]], [[GraphRAG (그래프 기반 검색 증강 생성)|GraphRAG (그래프 기반 검색 증강 생성)]], [[RDF와 OWL|RDF와 OWL]], [[RDF-star (RDF 확장 사양)|RDF-star (RDF*)]], [[지식 그래프 (Knowledge Graph)|지식 그래프 (Knowledge Graph)]], [[온톨로지 (Ontology)|온톨로지 (Ontology)]], [[Ontology-Guided Knowledge Extraction|Ontology-Guided Knowledge Extraction]] +- **Projects/Contexts:** [[온톨로지 지식 베이스|온톨로지 지식 베이스]], AI 신뢰성·투명성, LLM 환각 방지 - **Contradictions/Notes:** - Grounding은 LLM 생성 품질을 높이지만, 지식 그래프 자체가 오래되거나 불완전하면 Grounding된 답변도 틀릴 수 있음 (Garbage In, Garbage Out). - Provenance를 완전히 구현하려면 RDF-star 또는 Named Graph 패턴 필요 → 기존 RDF Reification은 너무 장황. diff --git a/01_Archive/2026-04-20/Semantic Versioning (SemVer) in Type Safety.md b/01_Archive/2026-04-20/Semantic Versioning (SemVer) in Type Safety.md index 540d81e4..132c394a 100644 --- a/01_Archive/2026-04-20/Semantic Versioning (SemVer) in Type Safety.md +++ b/01_Archive/2026-04-20/Semantic Versioning (SemVer) in Type Safety.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-882353 -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Semantic Versioning (SemVer) in Type Safety" --- -# [[Semantic Versioning (SemVer) in Type Safety]] +# [[Semantic Versioning (SemVer) in Type Safety|Semantic Versioning (SemVer) in Type Safety]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Semantic Versioning (SemVer) i ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Semantic Versioning (SemVer) in Type Safety.md]] +- Raw Source: 00_Raw/2026-04-20/Semantic Versioning (SemVer) in Type Safety.md --- diff --git a/01_Archive/2026-04-20/Semantic-Web-Technologies.md b/01_Archive/2026-04-20/Semantic-Web-Technologies.md index 75026bcb..68fba7c5 100644 --- a/01_Archive/2026-04-20/Semantic-Web-Technologies.md +++ b/01_Archive/2026-04-20/Semantic-Web-Technologies.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-BB1892 -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Semantic-Web-Technologies" --- -# [[Semantic-Web-Technologies]] +# [[Semantic-Web-Technologies|Semantic-Web-Technologies]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Semantic-Web-Technologies" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Semantic-Web-Technologies.md]] +- Raw Source: 00_Raw/2026-04-20/Semantic-Web-Technologies.md --- diff --git a/01_Archive/2026-04-20/Semantic-Web.md b/01_Archive/2026-04-20/Semantic-Web.md index 10b2f189..ac17affb 100644 --- a/01_Archive/2026-04-20/Semantic-Web.md +++ b/01_Archive/2026-04-20/Semantic-Web.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-8C1755 -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Semantic-Web" --- -# [[Semantic-Web]] +# [[Semantic-Web|Semantic-Web]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Semantic-Web" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Semantic-Web.md]] +- Raw Source: 00_Raw/2026-04-20/Semantic-Web.md --- diff --git a/01_Archive/2026-04-20/Semgrep Assistant.md b/01_Archive/2026-04-20/Semgrep Assistant.md index 777c4e9f..ad0d5fca 100644 --- a/01_Archive/2026-04-20/Semgrep Assistant.md +++ b/01_Archive/2026-04-20/Semgrep Assistant.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-484EAB -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Semgrep Assistant" --- -# [[Semgrep Assistant]] +# [[Semgrep Assistant|Semgrep Assistant]] ## 📌 한 줄 통찰 (The Karpathy Summary) > Semgrep Assistant는 빠른 패턴 매칭 기반의 정적 분석 도구인 Semgrep에 대형 언어 모델(LLM)을 결합하여 코드 리뷰 및 보안 분석을 고도화한 솔루션입니다. 이 도구는 노이즈 필터링, 취약점 결과 설명, 그리고 Pull Request(PR) 워크플로우 내에서의 자동 수정(autofix) 제안 등의 AI 기반 기능을 제공합니다. 과거의 트리아지(triage) 결정을 재사용하고 상황적 맥락(context)을 이해함으로써 오탐지(False Positives)를 대폭 줄여주며, 결과적으로 보안 엔지니어와 개발 플랫폼 팀의 분석 병목 현상을 해소하는 데 적합합니다. @@ -31,11 +31,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Semgrep Assistant" - **정책 변화:** AI 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Static Application Security Testing (SAST)]], [[False Positive]], [[Pull Request (PR)]], [[LLM (Large Language Model)]] -- **Projects/Contexts:** [[DevSecOps Workflow]], [[AppSec (Application Security)]] +- **Related Topics:** [[Static Application Security Testing (SAST)|Static Application Security Testing (SAST)]], [[오탐 (False Positive)|False Positive]], [[Pull Request (PR)|Pull Request (PR)]], LLM (Large Language Model) +- **Projects/Contexts:** DevSecOps Workflow, AppSec (Application Security) - **Contradictions/Notes:** 소스 분석에 따르면 Semgrep Assistant는 독립된 테스트에서 OWASP 벤치마크 기준 오탐지(False Positives) 제로(0)를 기록할 만큼 강력한 신호(signal)를 제공하지만, 동시에 AI 기반의 노이즈 필터링 기능은 공식적으로 '베타(beta)' 상태이므로 엔터프라이즈 규모로 운영 시 이를 인지하고 적용해야 한다는 상충되는 주의 사항이 존재합니다. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/Semgrep Assistant.md]] +- Raw Source: 00_Raw/2026-04-20/Semgrep Assistant.md --- diff --git a/01_Archive/2026-04-20/Semiotics in Media.md b/01_Archive/2026-04-20/Semiotics in Media.md index 37a6c364..cacf6650 100644 --- a/01_Archive/2026-04-20/Semiotics in Media.md +++ b/01_Archive/2026-04-20/Semiotics in Media.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-A79FEB -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Semiotics in Media" --- -# [[Semiotics in Media]] +# [[Semiotics in Media|Semiotics in Media]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Semiotics in Media" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Semiotics in Media.md]] +- Raw Source: 00_Raw/2026-04-20/Semiotics in Media.md --- diff --git a/01_Archive/2026-04-20/Sensor Fusion.md b/01_Archive/2026-04-20/Sensor Fusion.md index 0f797fa5..badcf871 100644 --- a/01_Archive/2026-04-20/Sensor Fusion.md +++ b/01_Archive/2026-04-20/Sensor Fusion.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-AA5A99 -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Sensor Fusion" --- -# [[Sensor Fusion]] +# [[Sensor Fusion|Sensor Fusion]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Sensor Fusion" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Sensor Fusion.md]] +- Raw Source: 00_Raw/2026-04-20/Sensor Fusion.md --- diff --git a/01_Archive/2026-04-20/Sensorimotor-Integration.md b/01_Archive/2026-04-20/Sensorimotor-Integration.md index b8235935..782b6b9d 100644 --- a/01_Archive/2026-04-20/Sensorimotor-Integration.md +++ b/01_Archive/2026-04-20/Sensorimotor-Integration.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-F9E556 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Sensorimotor-Integration" --- -# [[Sensorimotor-Integration]] +# [[Sensorimotor-Integration|Sensorimotor-Integration]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Sensorimotor-Integration" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Sensorimotor-Integration.md]] +- Raw Source: 00_Raw/2026-04-20/Sensorimotor-Integration.md --- diff --git a/01_Archive/2026-04-20/Serious Games.md b/01_Archive/2026-04-20/Serious Games.md index 982269ee..e131b63b 100644 --- a/01_Archive/2026-04-20/Serious Games.md +++ b/01_Archive/2026-04-20/Serious Games.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-4A3ECC -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Serious Games" --- -# [[Serious Games]] +# [[Serious Games|Serious Games]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Serious Games" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Serious Games.md]] +- Raw Source: 00_Raw/2026-04-20/Serious Games.md --- diff --git a/01_Archive/2026-04-20/Server Architecture.md b/01_Archive/2026-04-20/Server Architecture.md index 2d79c9cc..098d5035 100644 --- a/01_Archive/2026-04-20/Server Architecture.md +++ b/01_Archive/2026-04-20/Server Architecture.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-F7D840 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Server Architecture" --- -# [[Server Architecture]] +# [[Server Architecture|Server Architecture]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 소스에 관련 정보가 부족합니다. @@ -26,5 +26,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Server Architecture" --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/Server Architecture.md]] +- Raw Source: 00_Raw/2026-04-20/Server Architecture.md --- diff --git a/01_Archive/2026-04-20/Service-Design-Blueprinting.md b/01_Archive/2026-04-20/Service-Design-Blueprinting.md index 8c277099..8e68b0c6 100644 --- a/01_Archive/2026-04-20/Service-Design-Blueprinting.md +++ b/01_Archive/2026-04-20/Service-Design-Blueprinting.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-07A1AA -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Service-Design-Blueprinting" --- -# [[Service-Design-Blueprinting]] +# [[Service-Design-Blueprinting|Service-Design-Blueprinting]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Service-Design-Blueprinting" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Service-Design-Blueprinting.md]] +- Raw Source: 00_Raw/2026-04-20/Service-Design-Blueprinting.md --- diff --git a/01_Archive/2026-04-20/Service-Design.md b/01_Archive/2026-04-20/Service-Design.md index 31a90400..22737881 100644 --- a/01_Archive/2026-04-20/Service-Design.md +++ b/01_Archive/2026-04-20/Service-Design.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-92A8B5 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Service-Design" --- -# [[Service-Design]] +# [[Service-Design|Service-Design]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Service-Design" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Service-Design.md]] +- Raw Source: 00_Raw/2026-04-20/Service-Design.md --- diff --git a/01_Archive/2026-04-20/Service-Dominant-Logic.md b/01_Archive/2026-04-20/Service-Dominant-Logic.md index 5e24b0cc..86355e66 100644 --- a/01_Archive/2026-04-20/Service-Dominant-Logic.md +++ b/01_Archive/2026-04-20/Service-Dominant-Logic.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-625B63 -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Service-Dominant-Logic" --- -# [[Service-Dominant-Logic]] +# [[Service-Dominant-Logic|Service-Dominant-Logic]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Service-Dominant-Logic" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Service-Dominant-Logic.md]] +- Raw Source: 00_Raw/2026-04-20/Service-Dominant-Logic.md --- diff --git a/01_Archive/2026-04-20/Shannon-Entropy.md b/01_Archive/2026-04-20/Shannon-Entropy.md index 45f65bc6..87fb408c 100644 --- a/01_Archive/2026-04-20/Shannon-Entropy.md +++ b/01_Archive/2026-04-20/Shannon-Entropy.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-2A9F66 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Shannon-Entropy" --- -# [[Shannon-Entropy]] +# [[Shannon-Entropy|Shannon-Entropy]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Shannon-Entropy" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Shannon-Entropy.md]] +- Raw Source: 00_Raw/2026-04-20/Shannon-Entropy.md --- diff --git a/01_Archive/2026-04-20/SharedArrayBuffer vs postMessage 성능 차이.md b/01_Archive/2026-04-20/SharedArrayBuffer vs postMessage 성능 차이.md index b46e45d1..69623a28 100644 --- a/01_Archive/2026-04-20/SharedArrayBuffer vs postMessage 성능 차이.md +++ b/01_Archive/2026-04-20/SharedArrayBuffer vs postMessage 성능 차이.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-1B42F5 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - SharedArrayBuffer vs postMessage 성능 차이" --- -# [[SharedArrayBuffer vs postMessage 성능 차이]] +# [[SharedArrayBuffer vs postMessage 성능 차이|SharedArrayBuffer vs postMessage 성능 차이]] ## 📌 한 줄 통찰 (The Karpathy Summary) > `postMessage`는 데이터를 직렬화 및 역직렬화하여 스레드 간에 전달하기 때문에 통신 오버헤드가 발생하는 반면, `SharedArrayBuffer`는 두 스레드가 동일한 메모리 영역을 공유하여 **데이터 복사 비용 없이 0의 오버헤드와 극도로 낮은 지연 시간**을 달성하는 기술입니다. @@ -38,12 +38,12 @@ github_commit: "[P-Reinforce] Continuous Worker - SharedArrayBuffer vs postMessa - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Web Worker]], [[직렬화(Serialization) 및 병목 현상]], [[Transferable Objects]], [[Data-Oriented Design (ECS)]], [[원자적 연산(Atomic Operations)]] -- **Projects/Contexts:** [[멀티스레드 기반 고성능 React 게임 엔진]], [[실시간 물리 시뮬레이션 동기화]] +- **Related Topics:** [[Web Worker (웹 워커)|Web Worker]], [[직렬화(Serialization) 및 병목 현상|직렬화(Serialization) 및 병목 현상]], Transferable Objects, Data-Oriented Design (ECS), 원자적 연산(Atomic Operations) +- **Projects/Contexts:** 멀티스레드 기반 고성능 React 게임 엔진, [[실시간 물리 시뮬레이션 동기화|실시간 물리 시뮬레이션 동기화]] - **Contradictions/Notes:** `postMessage`도 `ArrayBuffer` 등을 Transferable 객체로 전달하면 직렬화 오버헤드를 거의 0으로 만들 수 있습니다. 그러나 이는 '소유권 이전' 방식이므로 두 스레드가 "동시에 데이터를 읽고 쓰는" 양방향 공유(Shared)가 불가능하다는 점에서 `SharedArrayBuffer`와 결정적인 차이를 가집니다. --- _Last updated: 2026-04-14_ -- Raw Source: [[00_Raw/2026-04-20/SharedArrayBuffer vs postMessage 성능 차이.md]] +- Raw Source: 00_Raw/2026-04-20/SharedArrayBuffer vs postMessage 성능 차이.md --- diff --git a/01_Archive/2026-04-20/SharedArrayBuffer 동시성 문제 해결법.md b/01_Archive/2026-04-20/SharedArrayBuffer 동시성 문제 해결법.md index 71059279..d8694a95 100644 --- a/01_Archive/2026-04-20/SharedArrayBuffer 동시성 문제 해결법.md +++ b/01_Archive/2026-04-20/SharedArrayBuffer 동시성 문제 해결법.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-918534 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - SharedArrayBuffer 동시성 문제 해결법" --- -# [[SharedArrayBuffer 동시성 문제 해결법]] +# [[SharedArrayBuffer 동시성 문제 해결법|SharedArrayBuffer 동시성 문제 해결법]] ## 📌 한 줄 통찰 (The Karpathy Summary) > `SharedArrayBuffer`는 여러 스레드가 동일한 메모리 영역을 동시에 공유하기 때문에 데이터 경쟁 상태(Data Race)가 발생할 수 있으며, 이를 해결하기 위해 **원자적 연산(Atomic operations)** 지원을 활용하거나 **아키텍처 설계(ECS 등)**를 통해 스레드 간의 읽기/쓰기 역할을 명확히 분리해야 합니다. @@ -27,12 +27,12 @@ github_commit: "[P-Reinforce] Continuous Worker - SharedArrayBuffer 동시성 - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Web Worker]], [[Atomics API]], [[경쟁 상태 (Race Condition)]], [[Data-Oriented Design (ECS)]] -- **Projects/Contexts:** [[멀티스레드 React WebGL 애플리케이션]], [[고성능 실시간 상호작용 시스템]] +- **Related Topics:** [[Web Worker (웹 워커)|Web Worker]], Atomics API, 경쟁 상태 (Race Condition), Data-Oriented Design (ECS) +- **Projects/Contexts:** 멀티스레드 React WebGL 애플리케이션, 고성능 실시간 상호작용 시스템 - **Contradictions/Notes:** `SharedArrayBuffer`는 지연 시간을 극도로 낮추고 복사 비용을 '0'으로 만들지만, 로우 레벨의 이진 데이터 버퍼를 직접 다뤄야 하고 `Atomics`로 동시성을 관리해야 하므로 구현 복잡도가 매우 높습니다 [264, 895, 이전 대화 내용 참조]. 따라서 충돌 제어와 개발 편의성이 더 중요한 일반적인 경우에는 Valtio 등 프록시(Proxy)를 사용해 `BroadcastChannel`이나 `postMessage`로 변경점(Delta)만 동기화하는 메시지 기반 패턴이 더 직관적일 수 있습니다. --- _Last updated: 2026-04-14_ -- Raw Source: [[00_Raw/2026-04-20/SharedArrayBuffer 동시성 문제 해결법.md]] +- Raw Source: 00_Raw/2026-04-20/SharedArrayBuffer 동시성 문제 해결법.md --- diff --git a/01_Archive/2026-04-20/SharedArrayBuffer 보안 이슈와 Cross-Origin Isolation 설정법.md b/01_Archive/2026-04-20/SharedArrayBuffer 보안 이슈와 Cross-Origin Isolation 설정법.md index 024371d9..29d6e1a2 100644 --- a/01_Archive/2026-04-20/SharedArrayBuffer 보안 이슈와 Cross-Origin Isolation 설정법.md +++ b/01_Archive/2026-04-20/SharedArrayBuffer 보안 이슈와 Cross-Origin Isolation 설정법.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-3E2EC5 -category: "[[10_Wiki/💡 Topics/General Knowledge]]" +category: "10_Wiki/💡 Topics/General Knowledge" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - SharedArrayBuffer 보안 이슈와 Cross-Origin Isolation 설정법" --- -# [[SharedArrayBuffer 보안 이슈와 Cross-Origin Isolation 설정법]] +# [[SharedArrayBuffer 보안 이슈와 Cross-Origin Isolation 설정법|SharedArrayBuffer 보안 이슈와 Cross-Origin Isolation 설정법]] ## 📌 한 줄 통찰 (The Karpathy Summary) > `SharedArrayBuffer`는 멀티스레드 간 복사 비용 0으로 데이터를 공유할 수 있는 강력한 기능이지만, 타이밍 공격(Spectre 등)을 유발할 수 있는 보안 취약점이 존재하여 이를 안전하게 사용하려면 웹 서버에 **COOP 및 COEP HTTP 보안 헤더를 통한 Cross-Origin Isolation(교차 출처 격리)** 설정이 반드시 필요합니다. @@ -29,12 +29,12 @@ github_commit: "[P-Reinforce] Continuous Worker - SharedArrayBuffer 보안 이 - **정책 변화:** General Knowledge 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Spectre Vulnerability]], [[HTTP Security Headers (COOP/COEP)]], [[CORS (Cross-Origin Resource Sharing)]], [[Web Worker Multi-threading]] -- **Projects/Contexts:** [[보안이 강화된 멀티스레드 기반 React WebGL 게임 엔진 구축]] +- **Related Topics:** Spectre Vulnerability, HTTP Security Headers (COOP/COEP), CORS (Cross-Origin Resource Sharing), Web Worker Multi-threading +- **Projects/Contexts:** 보안이 강화된 멀티스레드 기반 React WebGL 게임 엔진 구축 - **Contradictions/Notes:** 제공된 소스에 따르면 `SharedArrayBuffer`는 성능과 속도 면에서 가장 이상적이지만 로우 레벨(Low-level)의 원시 이진 데이터를 다루어야 해서 구현이 까다롭습니다. 여기에 더해 COOP/COEP 보안 헤더까지 설정해야 하므로 인프라 구축 및 외부 리소스 관리의 복잡성이 급격히 증가한다는 점을 프로젝트 기획 단계에서 반드시 고려해야 합니다. --- _Last updated: 2026-04-14_ -- Raw Source: [[00_Raw/2026-04-20/SharedArrayBuffer 보안 이슈와 Cross-Origin Isolation 설정법.md]] +- Raw Source: 00_Raw/2026-04-20/SharedArrayBuffer 보안 이슈와 Cross-Origin Isolation 설정법.md --- diff --git a/01_Archive/2026-04-20/SharedArrayBuffer 보안 이슈와 Cross-Origin Isolation.md b/01_Archive/2026-04-20/SharedArrayBuffer 보안 이슈와 Cross-Origin Isolation.md index e45f235b..5743c6f2 100644 --- a/01_Archive/2026-04-20/SharedArrayBuffer 보안 이슈와 Cross-Origin Isolation.md +++ b/01_Archive/2026-04-20/SharedArrayBuffer 보안 이슈와 Cross-Origin Isolation.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-C3F189 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - SharedArrayBuffer 보안 이슈와 Cross-Origin Isolation" --- -# [[SharedArrayBuffer 보안 이슈와 Cross-Origin Isolation]] +# [[SharedArrayBuffer 보안 이슈와 Cross-Origin Isolation|SharedArrayBuffer 보안 이슈와 Cross-Origin Isolation]] ## 📌 한 줄 통찰 (The Karpathy Summary) > `SharedArrayBuffer`는 스펙터(Spectre)와 같은 CPU 취약점을 악용한 타이밍 공격(Timing Attack)의 위험이 있어 브라우저에서 사용이 제한되며, 이를 다시 활성화하려면 웹 서버에 **Cross-Origin Isolation(교차 출처 격리) 보안 헤더**를 명시적으로 설정하여 안전한 환경을 구축해야 합니다. @@ -29,12 +29,12 @@ github_commit: "[P-Reinforce] Continuous Worker - SharedArrayBuffer 보안 이 - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Spectre & Meltdown 취약점]], [[CORS (Cross-Origin Resource Sharing)]], [[HTTP Security Headers (COOP, COEP, CORP)]], [[Web Worker 멀티스레딩 통신]] -- **Projects/Contexts:** [[보안 격리 환경에서의 고성능 웹 게임 개발]], [[멀티스레드 기반 렌더링 파이프라인(React Three Fiber)]] +- **Related Topics:** Spectre & Meltdown 취약점, CORS (Cross-Origin Resource Sharing), HTTP Security Headers (COOP, COEP, CORP), Web Worker 멀티스레딩 통신 +- **Projects/Contexts:** 보안 격리 환경에서의 고성능 웹 게임 개발, 멀티스레드 기반 렌더링 파이프라인(React Three Fiber) - **Contradictions/Notes:** 로컬 개발 환경(`localhost` 또는 `127.0.0.1`)에서는 개발 편의상 Cross-Origin Isolation 헤더 없이도 `SharedArrayBuffer`가 임시로 동작할 수 있으나, 실제 프로덕션(HTTPS 환경)에 배포할 때는 반드시 헤더 설정이 필요합니다. --- _Last updated: 2026-04-14_ -- Raw Source: [[00_Raw/2026-04-20/SharedArrayBuffer 보안 이슈와 Cross-Origin Isolation.md]] +- Raw Source: 00_Raw/2026-04-20/SharedArrayBuffer 보안 이슈와 Cross-Origin Isolation.md --- diff --git a/01_Archive/2026-04-20/SharedArrayBuffer 보안을 위한 COOP COEP 헤더 설정.md b/01_Archive/2026-04-20/SharedArrayBuffer 보안을 위한 COOP COEP 헤더 설정.md index d203abf3..a229475c 100644 --- a/01_Archive/2026-04-20/SharedArrayBuffer 보안을 위한 COOP COEP 헤더 설정.md +++ b/01_Archive/2026-04-20/SharedArrayBuffer 보안을 위한 COOP COEP 헤더 설정.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-01AE3D -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - SharedArrayBuffer 보안을 위한 COOP COEP 헤더 설정" --- -# [[SharedArrayBuffer 보안을 위한 COOP COEP 헤더 설정]] +# [[SharedArrayBuffer 보안을 위한 COOP COEP 헤더 설정|SharedArrayBuffer 보안을 위한 COOP COEP 헤더 설정]] ## 📌 한 줄 통찰 (The Karpathy Summary) > `SharedArrayBuffer`의 보안 취약점을 방지하고 스레드 간 안전한 메모리 공유를 수행하기 위해, 웹 서버에서 응답 시 브라우저의 교차 출처 격리(Cross-Origin Isolation)를 활성화하는 필수 HTTP 보안 헤더 설정 기법입니다. @@ -29,12 +29,12 @@ _(안내: 제공된 소스 자료에서는 `SharedArrayBuffer`가 복사 비용 - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Cross-Origin Isolation (COI)]], [[HTTP Security Headers (COOP/COEP)]], [[Spectre 취약점 부채널 공격]], [[CORS 및 CORP 설정]] -- **Projects/Contexts:** [[보안이 강화된 고성능 WebGL/멀티스레드 게임 엔진 배포]] +- **Related Topics:** Cross-Origin Isolation (COI), HTTP Security Headers (COOP/COEP), Spectre 취약점 부채널 공격, CORS 및 CORP 설정 +- **Projects/Contexts:** 보안이 강화된 고성능 WebGL/멀티스레드 게임 엔진 배포 - **Contradictions/Notes:** COOP와 COEP 헤더를 적용하면 엔진의 성능을 최대로 끌어올릴 수 있지만, 반대급부로 기존에 제약 없이 로드되던 외부 CDN 이미지나 타사 분석 스크립트가 브라우저에 의해 렌더링 차단되는 심각한 부작용이 생길 수 있습니다. 이를 우회하려면 외부 리소스 태그에 `crossorigin="anonymous"` 속성을 달고, 리소스 제공 서버가 적절한 접근 제어 헤더를 함께 내려주어야 하는 인프라적 제약이 따릅니다. --- _Last updated: 2026-04-14_ -- Raw Source: [[00_Raw/2026-04-20/SharedArrayBuffer 보안을 위한 COOP, COEP 헤더 설정.md]] +- Raw Source: 00_Raw/2026-04-20/SharedArrayBuffer 보안을 위한 COOP, COEP 헤더 설정.md --- diff --git a/01_Archive/2026-04-20/SharedArrayBuffer 보안을 위한 COOP, COEP 헤더 설정.md b/01_Archive/2026-04-20/SharedArrayBuffer 보안을 위한 COOP, COEP 헤더 설정.md index 76769f85..e82a8d45 100644 --- a/01_Archive/2026-04-20/SharedArrayBuffer 보안을 위한 COOP, COEP 헤더 설정.md +++ b/01_Archive/2026-04-20/SharedArrayBuffer 보안을 위한 COOP, COEP 헤더 설정.md @@ -19,8 +19,8 @@ _(안내: 제공된 소스 자료에서는 `SharedArrayBuffer`가 복사 비용 ## 🔗 Knowledge Connections -- **Related Topics:** [[Cross-Origin Isolation (COI)]], [[HTTP Security Headers (COOP/COEP)]], [[Spectre 취약점 부채널 공격]], [[CORS 및 CORP 설정]] -- **Projects/Contexts:** [[보안이 강화된 고성능 WebGL/멀티스레드 게임 엔진 배포]] +- **Related Topics:** Cross-Origin Isolation (COI), HTTP Security Headers (COOP/COEP), Spectre 취약점 부채널 공격, CORS 및 CORP 설정 +- **Projects/Contexts:** 보안이 강화된 고성능 WebGL/멀티스레드 게임 엔진 배포 - **Contradictions/Notes:** COOP와 COEP 헤더를 적용하면 엔진의 성능을 최대로 끌어올릴 수 있지만, 반대급부로 기존에 제약 없이 로드되던 외부 CDN 이미지나 타사 분석 스크립트가 브라우저에 의해 렌더링 차단되는 심각한 부작용이 생길 수 있습니다. 이를 우회하려면 외부 리소스 태그에 `crossorigin="anonymous"` 속성을 달고, 리소스 제공 서버가 적절한 접근 제어 헤더를 함께 내려주어야 하는 인프라적 제약이 따릅니다. --- diff --git a/01_Archive/2026-04-20/SharedArrayBuffer 보안을 위한 Cross-Origin Isolation 서버 헤더 설정.md b/01_Archive/2026-04-20/SharedArrayBuffer 보안을 위한 Cross-Origin Isolation 서버 헤더 설정.md index b047cea0..af224cca 100644 --- a/01_Archive/2026-04-20/SharedArrayBuffer 보안을 위한 Cross-Origin Isolation 서버 헤더 설정.md +++ b/01_Archive/2026-04-20/SharedArrayBuffer 보안을 위한 Cross-Origin Isolation 서버 헤더 설정.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-32CC81 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - SharedArrayBuffer 보안을 위한 Cross-Origin Isolation 서버 헤더 설정" --- -# [[SharedArrayBuffer 보안을 위한 Cross-Origin Isolation 서버 헤더 설정]] +# [[SharedArrayBuffer 보안을 위한 Cross-Origin Isolation 서버 헤더 설정|SharedArrayBuffer 보안을 위한 Cross-Origin Isolation 서버 헤더 설정]] ## 📌 한 줄 통찰 (The Karpathy Summary) > `SharedArrayBuffer`의 스펙터(Spectre) 취약점을 악용한 메모리 유출 공격을 방지하기 위해, 웹 서버에서 응답 시 **COOP 및 COEP HTTP 보안 헤더**를 설정하여 브라우저의 교차 출처 격리(Cross-Origin Isolation) 상태를 활성화하는 서버 설정 방법입니다. @@ -32,12 +32,12 @@ github_commit: "[P-Reinforce] Continuous Worker - SharedArrayBuffer 보안을 - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Spectre 부채널 공격 (Side-Channel Attack)]], [[HTTP Security Headers (COOP/COEP/CORP)]], [[CORS (Cross-Origin Resource Sharing)]], [[Web Worker Multi-threading]] -- **Projects/Contexts:** [[보안이 강화된 고성능 WebGL/React 게임 엔진 배포 환경 구축]] +- **Related Topics:** Spectre 부채널 공격 (Side-Channel Attack), HTTP Security Headers (COOP/COEP/CORP), CORS (Cross-Origin Resource Sharing), Web Worker Multi-threading +- **Projects/Contexts:** 보안이 강화된 고성능 WebGL/React 게임 엔진 배포 환경 구축 - **Contradictions/Notes:** 로컬 개발 환경(`localhost` 또는 `127.0.0.1`)에서는 개발 편의를 위해 COOP/COEP 헤더 없이도 `SharedArrayBuffer`가 일시적으로 동작할 수 있습니다. 하지만 실제 도메인이 연결된 프로덕션(HTTPS) 환경으로 배포할 때는 서버 헤더 설정이 누락되면 즉시 앱이 중단되므로 인프라 수준에서의 꼼꼼한 설정이 필요합니다. --- _Last updated: 2026-04-14_ -- Raw Source: [[00_Raw/2026-04-20/SharedArrayBuffer 보안을 위한 Cross-Origin Isolation 서버 헤더 설정.md]] +- Raw Source: 00_Raw/2026-04-20/SharedArrayBuffer 보안을 위한 Cross-Origin Isolation 서버 헤더 설정.md --- diff --git a/01_Archive/2026-04-20/SharedArrayBuffer.md b/01_Archive/2026-04-20/SharedArrayBuffer.md index ac1fc23d..f54acdad 100644 --- a/01_Archive/2026-04-20/SharedArrayBuffer.md +++ b/01_Archive/2026-04-20/SharedArrayBuffer.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-C22BDF -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - SharedArrayBuffer" --- -# [[SharedArrayBuffer]] +# [[SharedArrayBuffer|SharedArrayBuffer]] ## 📌 한 줄 통찰 (The Karpathy Summary) > SharedArrayBuffer는 다중 스레드 환경에서 Web Worker와 메인 스레드 간에 데이터를 공유할 때 메모리 과부하를 방지하기 위해 사용되는 기술입니다 [1]. 전통적인 데이터 전달 방식과 달리 메모리를 복제하지 않는 제로 카피(Zero-copy) 아키텍처를 구현할 수 있게 해줍니다 [1]. 이를 통해 Electron과 같은 환경에서 대규모 3D 모델을 로드하고 파싱할 때 메모리 안정성을 획기적으로 유지할 수 있습니다 [1, 2]. @@ -20,11 +20,11 @@ github_commit: "[P-Reinforce] Continuous Worker - SharedArrayBuffer" - **정책 변화:** Graphics & Performance 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Web Worker]], [[Structured Cloning]], [[BufferAttribute]], [[Zero-copy architecture]] -- **Projects/Contexts:** [[Electron 기반 WebGL CAD 렌더링 최적화]] +- **Related Topics:** [[Web Worker (웹 워커)|Web Worker]], Structured Cloning, [[BufferAttribute|BufferAttribute]], Zero-copy architecture +- **Projects/Contexts:** Electron 기반 WebGL CAD 렌더링 최적화 - **Contradictions/Notes:** 소스에서는 워커를 활용할 때 기존의 Structured Cloning을 사용할 경우 데이터가 전체 복사되어 OOM이 발생할 위험이 크지만, SharedArrayBuffer를 사용하면 복사 과정을 없애(Zero-copy) 이러한 메모리 오버헤드를 완벽히 방지할 수 있다고 대조하여 설명합니다 [1]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/SharedArrayBuffer.md]] +- Raw Source: 00_Raw/2026-04-20/SharedArrayBuffer.md --- diff --git a/01_Archive/2026-04-20/SharedArrayBuffer로 스레드 간 메모리 공유 효율 높이기.md b/01_Archive/2026-04-20/SharedArrayBuffer로 스레드 간 메모리 공유 효율 높이기.md index cbf86a0a..35a7b3e6 100644 --- a/01_Archive/2026-04-20/SharedArrayBuffer로 스레드 간 메모리 공유 효율 높이기.md +++ b/01_Archive/2026-04-20/SharedArrayBuffer로 스레드 간 메모리 공유 효율 높이기.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-4A9AE0 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - SharedArrayBuffer로 스레드 간 메모리 공유 효율 높이기" --- -# [[SharedArrayBuffer로 스레드 간 메모리 공유 효율 높이기]] +# [[SharedArrayBuffer로 스레드 간 메모리 공유 효율 높이기|SharedArrayBuffer로 스레드 간 메모리 공유 효율 높이기]] ## 📌 한 줄 통찰 (The Karpathy Summary) > **SharedArrayBuffer**는 웹 워커(Web Worker)와 메인 스레드 간의 전통적인 통신 방식인 `postMessage`의 데이터 직렬화(Serialization) 및 복사 오버헤드를 제거하고, **두 스레드가 동일한 메모리 영역을 복사 없이(Zero-copy) 직접 접근하고 공유**할 수 있게 해주는 저수준(Low-level)의 고성능 최적화 기법입니다. @@ -33,5 +33,5 @@ github_commit: "[P-Reinforce] Continuous Worker - SharedArrayBuffer로 스레드 ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/SharedArrayBuffer로 스레드 간 메모리 공유 효율 높이기.md]] +- Raw Source: 00_Raw/2026-04-20/SharedArrayBuffer로 스레드 간 메모리 공유 효율 높이기.md --- diff --git a/01_Archive/2026-04-20/SharedArrayBuffer와 Atomics 구체적 활용법.md b/01_Archive/2026-04-20/SharedArrayBuffer와 Atomics 구체적 활용법.md index 8b80669c..851ccbc9 100644 --- a/01_Archive/2026-04-20/SharedArrayBuffer와 Atomics 구체적 활용법.md +++ b/01_Archive/2026-04-20/SharedArrayBuffer와 Atomics 구체적 활용법.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-0A2C98 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - SharedArrayBuffer와 Atomics 구체적 활용법" --- -# [[SharedArrayBuffer와 Atomics 구체적 활용법]] +# [[SharedArrayBuffer와 Atomics 구체적 활용법|SharedArrayBuffer와 Atomics 구체적 활용법]] ## 📌 한 줄 통찰 (The Karpathy Summary) > `SharedArrayBuffer`를 통해 다중 스레드에서 공유되는 메모리에 접근할 때 데이터 경쟁(Data Race)을 막기 위해, 자바스크립트 내장 객체인 `Atomics`의 정적 메서드들을 활용하여 안전하게 데이터를 읽고 쓰고 동기화하는 기법입니다. @@ -61,12 +61,12 @@ Atomics.notify(sharedArray, 3, 1); // 인덱스 3에서 대기 중인 스레드 - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[SharedArrayBuffer]], [[Web Worker]], [[Data Race (데이터 경쟁)]], [[Lock / Mutex 동기화 패턴]] -- **Projects/Contexts:** [[고성능 실시간 상호작용 시스템]], [[멀티스레드 React 게임 엔진 아키텍처]] +- **Related Topics:** [[SharedArrayBuffer|SharedArrayBuffer]], [[Web Worker (웹 워커)|Web Worker]], Data Race (데이터 경쟁), Lock / Mutex 동기화 패턴 +- **Projects/Contexts:** 고성능 실시간 상호작용 시스템, 멀티스레드 React 게임 엔진 아키텍처 - **Contradictions/Notes:** `SharedArrayBuffer`와 `Atomics`는 메모리 복사를 없애 지연 시간을 극도로 낮추는 최적의 수단이지만, 원시 이진 데이터를 직접 제어해야 하므로 구현 난이도가 매우 높습니다. 따라서 실무에서는 개발 편의성을 위해 직렬화 오버헤드를 어느 정도 감수하더라도 `Valtio` 같은 프록시 객체를 통한 메시지 패싱 방식을 선택하거나, 이진 데이터를 추상화해 둔 `bitECS` 같은 고성능 라이브러리를 활용하는 경우가 많습니다. --- _Last updated: 2026-04-14_ -- Raw Source: [[00_Raw/2026-04-20/SharedArrayBuffer와 Atomics 구체적 활용법.md]] +- Raw Source: 00_Raw/2026-04-20/SharedArrayBuffer와 Atomics 구체적 활용법.md --- diff --git a/01_Archive/2026-04-20/Side-channel Attack.md b/01_Archive/2026-04-20/Side-channel Attack.md index 86dc2309..f8a258de 100644 --- a/01_Archive/2026-04-20/Side-channel Attack.md +++ b/01_Archive/2026-04-20/Side-channel Attack.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-624D09 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Side-channel Attack" --- -# [[Side-channel Attack]] +# [[Side-channel Attack|Side-channel Attack]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 부채널 공격(Side-channel Attack)은 하드웨어의 투기적 실행(Speculative execution)이나 캐시 접근 시간과 같은 물리적 작동 특성에서 발생하는 정보 유출을 악용하는 보안 취약점입니다 [1-3]. 공격자는 고정밀 타이밍 측정을 통해 캐시 적중률이나 메모리 접근 패턴을 관찰하여, 본래 접근이 제한된 시스템의 비밀 메모리 영역을 유추하고 읽어낼 수 있습니다 [3-5]. 웹 브라우저 환경에서는 이러한 공격이 기존의 보안 검사(경계 및 타입 검사 등)를 우회할 수 있어, 브라우저 벤더들이 타이머 정밀도 감소 및 분기 없는 보안 검사 등의 방어책을 도입하게 되었습니다 [6-8]. @@ -23,11 +23,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Side-channel Attack" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Spectre]], [[Meltdown]], [[Speculative Execution]], [[Timing Attack]], [[Timer Quantization]], [[Rowhammer]] -- **Projects/Contexts:** [[WebKit]], [[JavaScriptCore]], [[Blink]], [[WebGPU timestamp queries]], [[EXT_disjoint_timer_query]] +- **Related Topics:** [[Spectre|Spectre]], [[Meltdown|Meltdown]], [[Speculative Execution|Speculative Execution]], [[Timing Attack|Timing Attack]], Timer Quantization, [[Rowhammer|Rowhammer]] +- **Projects/Contexts:** [[WebKit|WebKit]], [[JavaScriptCore|JavaScriptCore]], [[Blink|Blink]], [[WebGPU Timestamp Queries|WebGPU timestamp queries]], [[EXT_disjoint_timer_query|EXT_disjoint_timer_query]] - **Contradictions/Notes:** 고정밀 GPU 타임스탬프 기능의 경우, 성능 프로파일링을 위해 이 기능이 필수적이라는 개발자들의 요구(WebGPU 커뮤니티 등)와 캐시 부채널 공격(Timing attack)을 막아야 한다는 보안 요구가 충돌합니다. 이에 따라 브라우저 벤더들은 사이트 격리(Site isolation) 상태에 따라 타이머 해상도를 조대화(coarsening)하거나 양자화(quantization)를 강제하는 방식을 타협점으로 사용하고 있습니다 [4, 11, 15, 18]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Side-channel Attack.md]] +- Raw Source: 00_Raw/2026-04-20/Side-channel Attack.md --- diff --git a/01_Archive/2026-04-20/Side-channel attacks.md b/01_Archive/2026-04-20/Side-channel attacks.md index 3205f917..d8e209bc 100644 --- a/01_Archive/2026-04-20/Side-channel attacks.md +++ b/01_Archive/2026-04-20/Side-channel attacks.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-9A3E86 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Side-channel attacks" --- -# [[Side-channel attacks]] +# [[Side-channel attacks|Side-channel attacks]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -28,11 +28,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Side-channel attacks" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** `[[Spectre]]`, `[[Meltdown]]`, `[[Speculative execution]]`, `[[Timestamp quantization]]`, `[[Branchless security checks]]` -- **Projects/Contexts:** `[[WebKit]]`, `[[JavaScriptCore]]`, `[[WebGPU]]` +- **Related Topics:** `[[Spectre|Spectre]]`, `[[Meltdown|Meltdown]]`, `[[Speculative Execution|Speculative execution]]`, `[[Timestamp Quantization|Timestamp quantization]]`, `[[Branchless Security Checks|Branchless security checks]]` +- **Projects/Contexts:** `[[WebKit|WebKit]]`, `[[JavaScriptCore|JavaScriptCore]]`, `[[WebGPU|WebGPU]]` - **Contradictions/Notes:** WebGPU 스펙은 타이밍 공격의 위험성 때문에 타임스탬프 쿼리를 선택적(optional) 기능으로 명시하고 아예 노출을 제한할 수 있다고 규정합니다. 그러나 Chrome(Blink) 등의 구현체는 기능을 완전히 차단하는 대신, 사이트 격리(site isolation) 여부에 따라 타이머 해상도를 100 마이크로초로 양자화(quantization)하여 보안과 개발자 성능 측정 요구 사이의 타협점을 제공하고 있습니다 [12, 18, 19]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Side-channel attacks.md]] +- Raw Source: 00_Raw/2026-04-20/Side-channel attacks.md --- diff --git a/01_Archive/2026-04-20/Signal Processing.md b/01_Archive/2026-04-20/Signal Processing.md index dc24dfaf..5a92970f 100644 --- a/01_Archive/2026-04-20/Signal Processing.md +++ b/01_Archive/2026-04-20/Signal Processing.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-E8C536 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Signal Processing" --- -# [[Signal Processing]] +# [[Signal Processing|Signal Processing]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Signal Processing" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Signal Processing.md]] +- Raw Source: 00_Raw/2026-04-20/Signal Processing.md --- diff --git a/01_Archive/2026-04-20/SimCity (as a model of systemic interaction).md b/01_Archive/2026-04-20/SimCity (as a model of systemic interaction).md index 8bdfa7d4..a7552e39 100644 --- a/01_Archive/2026-04-20/SimCity (as a model of systemic interaction).md +++ b/01_Archive/2026-04-20/SimCity (as a model of systemic interaction).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-10C76A -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - SimCity (as a model of systemic interaction)" --- -# [[SimCity (as a model of systemic interaction)]] +# [[SimCity (as a model of systemic interaction)|SimCity (as a model of systemic interaction)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - SimCity (as a model of systemi ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/SimCity (as a model of systemic interaction).md]] +- Raw Source: 00_Raw/2026-04-20/SimCity (as a model of systemic interaction).md --- diff --git a/01_Archive/2026-04-20/SimCity-Series.md b/01_Archive/2026-04-20/SimCity-Series.md index 207aa0f4..13db5ffd 100644 --- a/01_Archive/2026-04-20/SimCity-Series.md +++ b/01_Archive/2026-04-20/SimCity-Series.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-5D71A8 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - SimCity-Series" --- -# [[SimCity-Series]] +# [[SimCity-Series|SimCity-Series]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - SimCity-Series" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/SimCity-Series.md]] +- Raw Source: 00_Raw/2026-04-20/SimCity-Series.md --- diff --git a/01_Archive/2026-04-20/Simulated History.md b/01_Archive/2026-04-20/Simulated History.md index cec80aef..37ca7c6d 100644 --- a/01_Archive/2026-04-20/Simulated History.md +++ b/01_Archive/2026-04-20/Simulated History.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-DEC9B0 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Simulated History" --- -# [[Simulated History]] +# [[Simulated History|Simulated History]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Simulated History" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Simulated History.md]] +- Raw Source: 00_Raw/2026-04-20/Simulated History.md --- diff --git a/01_Archive/2026-04-20/Simulation Theory.md b/01_Archive/2026-04-20/Simulation Theory.md index af9fb541..c2519866 100644 --- a/01_Archive/2026-04-20/Simulation Theory.md +++ b/01_Archive/2026-04-20/Simulation Theory.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-5A1ACA -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Simulation Theory" --- -# [[Simulation Theory]] +# [[Simulation Theory|Simulation Theory]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Simulation Theory" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Simulation Theory.md]] +- Raw Source: 00_Raw/2026-04-20/Simulation Theory.md --- diff --git a/01_Archive/2026-04-20/Simulations of Social Systems.md b/01_Archive/2026-04-20/Simulations of Social Systems.md index e1ba8ec5..6380d75d 100644 --- a/01_Archive/2026-04-20/Simulations of Social Systems.md +++ b/01_Archive/2026-04-20/Simulations of Social Systems.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-6349BA -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Simulations of Social Systems" --- -# [[Simulations of Social Systems]] +# [[Simulations of Social Systems|Simulations of Social Systems]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Simulations of Social Systems" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Simulations of Social Systems.md]] +- Raw Source: 00_Raw/2026-04-20/Simulations of Social Systems.md --- diff --git a/01_Archive/2026-04-20/Simulator Sickness Questionnaire (SSQ).md b/01_Archive/2026-04-20/Simulator Sickness Questionnaire (SSQ).md index 6a3fef07..9db0d664 100644 --- a/01_Archive/2026-04-20/Simulator Sickness Questionnaire (SSQ).md +++ b/01_Archive/2026-04-20/Simulator Sickness Questionnaire (SSQ).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-73720A -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Simulator Sickness Questionnaire (SSQ)" --- -# [[Simulator Sickness Questionnaire (SSQ)]] +# [[Simulator Sickness Questionnaire (SSQ)|Simulator Sickness Questionnaire (SSQ)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 시뮬레이터 멀미 설문지(Simulator Sickness Questionnaire, SSQ)는 가상현실(VR) 및 시뮬레이터 연구에서 가상현실 멀미 증상을 자가 보고 방식으로 측정하기 위해 가장 널리 사용되는 도구입니다 [1]. 16개의 증상 목록을 바탕으로 0(없음)에서 3(심각함)까지의 4점 척도로 평가하며, 측정된 증상은 크게 메스꺼움, 안구 운동, 방향 감각 상실의 세 가지 하위 범주로 분류됩니다 [1]. @@ -26,11 +26,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Simulator Sickness Questionnai - **정책 변화:** AI 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Virtual Reality Sickness]], [[Nausea]], [[Oculomotor]], [[Disorientation]] -- **Projects/Contexts:** [[Beat Saber Exergaming Study]] +- **Related Topics:** Virtual Reality Sickness, Nausea, Oculomotor, Disorientation +- **Projects/Contexts:** Beat Saber Exergaming Study - **Contradictions/Notes:** 연구에 따르면 SSQ 점수가 20점 이상일 경우 문제가 있는 시뮬레이터로 판단하지만, 이러한 높은 SSQ 점수가 사용자의 실제 일상생활 수행 능력 저하와 어떻게 연결되는지에 대해서는 아직 명확히 밝혀지지 않았으며 이는 향후 VR의 안전한 사용을 위해 해결해야 할 지식의 공백으로 남아있습니다 [3]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Simulator Sickness Questionnaire (SSQ).md]] +- Raw Source: 00_Raw/2026-04-20/Simulator Sickness Questionnaire (SSQ).md --- diff --git a/01_Archive/2026-04-20/Simultaneous Localization and Mapping (SLAM).md b/01_Archive/2026-04-20/Simultaneous Localization and Mapping (SLAM).md index c6b628ae..3092ee53 100644 --- a/01_Archive/2026-04-20/Simultaneous Localization and Mapping (SLAM).md +++ b/01_Archive/2026-04-20/Simultaneous Localization and Mapping (SLAM).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-72B40F -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Simultaneous Localization and Mapping (SLAM)" --- -# [[Simultaneous Localization and Mapping (SLAM)]] +# [[Simultaneous Localization and Mapping (SLAM)|Simultaneous Localization and Mapping (SLAM)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Simultaneous Localization and ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Simultaneous Localization and Mapping (SLAM).md]] +- Raw Source: 00_Raw/2026-04-20/Simultaneous Localization and Mapping (SLAM).md --- diff --git a/01_Archive/2026-04-20/Single Page Applications (SPA).md b/01_Archive/2026-04-20/Single Page Applications (SPA).md index 7aa13b35..5c5921af 100644 --- a/01_Archive/2026-04-20/Single Page Applications (SPA).md +++ b/01_Archive/2026-04-20/Single Page Applications (SPA).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-D50C28 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Single Page Applications (SPA)" --- -# [[Single Page Applications (SPA)]] +# [[Single Page Applications (SPA)|Single Page Applications (SPA)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 소스에 관련 정보가 부족합니다. 제공된 소스에는 Single Page Applications (SPA)에 대한 명확한 정의나 개요가 포함되어 있지 않으며, 브라우저 메모리 누수의 문맥에서 단편적으로만 언급되어 있습니다 [1]. @@ -23,11 +23,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Single Page Applications (SPA) - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Memory Leaks]], [[Garbage Collection]] -- **Projects/Contexts:** [[Browser Memory Leak Detection]] +- **Related Topics:** [[Memory Leaks|Memory Leaks]], [[Garbage Collection|Garbage Collection]] +- **Projects/Contexts:** [[브라우저 메모리 누수 탐지(Browser Memory Leak Detection)|Browser Memory Leak Detection]] - **Contradictions/Notes:** 소스에 관련 정보가 부족합니다. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Single Page Applications (SPA).md]] +- Raw Source: 00_Raw/2026-04-20/Single Page Applications (SPA).md --- diff --git a/01_Archive/2026-04-20/Single-Responsibility-Principle.md b/01_Archive/2026-04-20/Single-Responsibility-Principle.md index 0b5f1677..6f1bfdbf 100644 --- a/01_Archive/2026-04-20/Single-Responsibility-Principle.md +++ b/01_Archive/2026-04-20/Single-Responsibility-Principle.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-91F776 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Single-Responsibility-Principle" --- -# [[Single-Responsibility-Principle]] +# [[Single-Responsibility-Principle|Single-Responsibility-Principle]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Single-Responsibility-Principl ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Single-Responsibility-Principle.md]] +- Raw Source: 00_Raw/2026-04-20/Single-Responsibility-Principle.md --- diff --git a/01_Archive/2026-04-20/Single-Source-of-Truth-Principle.md b/01_Archive/2026-04-20/Single-Source-of-Truth-Principle.md index ee988ef3..dac84e9a 100644 --- a/01_Archive/2026-04-20/Single-Source-of-Truth-Principle.md +++ b/01_Archive/2026-04-20/Single-Source-of-Truth-Principle.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-A292A4 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Single-Source-of-Truth-Principle" --- -# [[Single-Source-of-Truth-Principle]] +# [[Single-Source-of-Truth-Principle|Single-Source-of-Truth-Principle]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Single-Source-of-Truth-Princip ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Single-Source-of-Truth-Principle.md]] +- Raw Source: 00_Raw/2026-04-20/Single-Source-of-Truth-Principle.md --- diff --git a/01_Archive/2026-04-20/Single-Source-of-Truth.md b/01_Archive/2026-04-20/Single-Source-of-Truth.md index 713f6863..d48db01c 100644 --- a/01_Archive/2026-04-20/Single-Source-of-Truth.md +++ b/01_Archive/2026-04-20/Single-Source-of-Truth.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-9158CA -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Single-Source-of-Truth" --- -# [[Single-Source-of-Truth]] +# [[Single-Source-of-Truth|Single-Source-of-Truth]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Single-Source-of-Truth" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Single-Source-of-Truth.md]] +- Raw Source: 00_Raw/2026-04-20/Single-Source-of-Truth.md --- diff --git a/01_Archive/2026-04-20/Singularity (기술적 특이점).md b/01_Archive/2026-04-20/Singularity (기술적 특이점).md index ed90d836..d7b15ddb 100644 --- a/01_Archive/2026-04-20/Singularity (기술적 특이점).md +++ b/01_Archive/2026-04-20/Singularity (기술적 특이점).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-04DB11 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Singularity (기술적 특이점)" --- -# [[Singularity (기술적 특이점)]] +# [[Singularity (기술적 특이점)|Singularity (기술적 특이점)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Singularity (기술적 특이 ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Singularity (기술적 특이점).md]] +- Raw Source: 00_Raw/2026-04-20/Singularity (기술적 특이점).md --- diff --git a/01_Archive/2026-04-20/SkinnedMesh.md b/01_Archive/2026-04-20/SkinnedMesh.md index 6f412f89..7fcf27be 100644 --- a/01_Archive/2026-04-20/SkinnedMesh.md +++ b/01_Archive/2026-04-20/SkinnedMesh.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-1189F7 -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - SkinnedMesh" --- -# [[SkinnedMesh]] +# [[SkinnedMesh|SkinnedMesh]] ## 📌 한 줄 통찰 (The Karpathy Summary) > SkinnedMesh는 뼈대(Bone) 계층 구조를 기반으로 한 애니메이션(예: 캐릭터의 얼굴 뼈대나 손가락 움직임 등)을 구현할 때 사용되는 3D 객체 타입입니다 [1-3]. 단일 객체로는 원활하게 동작하지만 대량으로 렌더링할 경우 심각한 CPU 병목 현상을 유발하며 [4], 정점이 다수의 본 행렬에 영향을 받는 특성상 대규모 렌더링 최적화 기법인 InstancedMesh와 기본적으로 호환되지 않는 물리적 한계를 지닙니다 [3]. @@ -32,11 +32,11 @@ github_commit: "[P-Reinforce] Continuous Worker - SkinnedMesh" - **정책 변화:** Graphics & Performance 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[InstancedMesh]], [[InstancedMesh2]], [[AnimationMixer]], [[Bone Texture]], [[Level of Detail (LOD)]] -- **Projects/Contexts:** [[Three.js 엔진의 대규모 군중 렌더링 및 애니메이션 처리]] +- **Related Topics:** [[InstancedMesh|InstancedMesh]], [[InstancedMesh2|InstancedMesh2]], AnimationMixer, Bone Texture, [[Level of Detail (LOD)|Level of Detail (LOD)]] +- **Projects/Contexts:** Three.js 엔진의 대규모 군중 렌더링 및 애니메이션 처리 - **Contradictions/Notes:** 엔진의 공식 기능 상으로는 데이터 전송량의 기하급수적 증가 및 `AnimationMixer`와의 아키텍처 충돌 문제로 스킨드 메쉬의 대규모 인스턴싱이 불가능하다고 지적되지만 [3], 개발자들은 본 텍스처를 활용한 셰이더 커스터마이징이나 `InstancedMesh2` 라이브러리를 적용하여 각기 다른 애니메이션을 가진 수만 개의 SkinnedMesh를 단일 혹은 최소한의 드로우 콜로 최적화하여 렌더링하는 데 성공하고 있습니다 [3, 6, 12]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/SkinnedMesh.md]] +- Raw Source: 00_Raw/2026-04-20/SkinnedMesh.md --- diff --git a/01_Archive/2026-04-20/Skybound Protocol 개발자 확장 가이드 및 아키텍처 리뷰.md b/01_Archive/2026-04-20/Skybound Protocol 개발자 확장 가이드 및 아키텍처 리뷰.md index 2ffe7475..e789e4b9 100644 --- a/01_Archive/2026-04-20/Skybound Protocol 개발자 확장 가이드 및 아키텍처 리뷰.md +++ b/01_Archive/2026-04-20/Skybound Protocol 개발자 확장 가이드 및 아키텍처 리뷰.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-271BCA -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Skybound Protocol 개발자 확장 가이드 및 아키텍처 리뷰" --- -# [[Skybound Protocol 개발자 확장 가이드 및 아키텍처 리뷰]] +# [[Skybound Protocol 개발자 확장 가이드 및 아키텍처 리뷰|Skybound Protocol 개발자 확장 가이드 및 아키텍처 리뷰]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Skybound Protocol 개발자 ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Skybound Protocol 개발자 확장 가이드 및 아키텍처 리뷰.md]] +- Raw Source: 00_Raw/2026-04-20/Skybound Protocol 개발자 확장 가이드 및 아키텍처 리뷰.md --- diff --git a/01_Archive/2026-04-20/Skybound Protocol 구조 및 의존성 분석 (Dependency Mapping).md b/01_Archive/2026-04-20/Skybound Protocol 구조 및 의존성 분석 (Dependency Mapping).md index 006cd5f6..6c1d4321 100644 --- a/01_Archive/2026-04-20/Skybound Protocol 구조 및 의존성 분석 (Dependency Mapping).md +++ b/01_Archive/2026-04-20/Skybound Protocol 구조 및 의존성 분석 (Dependency Mapping).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-A04161 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Skybound Protocol 구조 및 의존성 분석 (Dependency Mapping)" --- -# [[Skybound Protocol 구조 및 의존성 분석 (Dependency Mapping)]] +# [[Skybound Protocol 구조 및 의존성 분석 (Dependency Mapping)|Skybound Protocol 구조 및 의존성 분석 (Dependency Mapping)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Skybound Protocol 구조 및 ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Skybound Protocol 구조 및 의존성 분석 (Dependency Mapping).md]] +- Raw Source: 00_Raw/2026-04-20/Skybound Protocol 구조 및 의존성 분석 (Dependency Mapping).md --- diff --git a/01_Archive/2026-04-20/Skybound Protocol 기술 메뉴얼 및 개발자 가이드.md b/01_Archive/2026-04-20/Skybound Protocol 기술 메뉴얼 및 개발자 가이드.md index ece37881..6068400a 100644 --- a/01_Archive/2026-04-20/Skybound Protocol 기술 메뉴얼 및 개발자 가이드.md +++ b/01_Archive/2026-04-20/Skybound Protocol 기술 메뉴얼 및 개발자 가이드.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-19F4EF -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Skybound Protocol 기술 메뉴얼 및 개발자 가이드" --- -# [[Skybound Protocol 기술 메뉴얼 및 개발자 가이드]] +# [[Skybound Protocol 기술 메뉴얼 및 개발자 가이드|Skybound Protocol 기술 메뉴얼 및 개발자 가이드]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Skybound Protocol 기술 메 ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Skybound Protocol 기술 메뉴얼 및 개발자 가이드.md]] +- Raw Source: 00_Raw/2026-04-20/Skybound Protocol 기술 메뉴얼 및 개발자 가이드.md --- diff --git a/01_Archive/2026-04-20/Skybound Protocol 데이터 및 제어 흐름 (Control Flow).md b/01_Archive/2026-04-20/Skybound Protocol 데이터 및 제어 흐름 (Control Flow).md index 3ddfbb82..4c6f7d5c 100644 --- a/01_Archive/2026-04-20/Skybound Protocol 데이터 및 제어 흐름 (Control Flow).md +++ b/01_Archive/2026-04-20/Skybound Protocol 데이터 및 제어 흐름 (Control Flow).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-1B8F72 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Skybound Protocol 데이터 및 제어 흐름 (Control Flow)" --- -# [[Skybound Protocol 데이터 및 제어 흐름 (Control Flow)]] +# [[Skybound Protocol 데이터 및 제어 흐름 (Control Flow)|Skybound Protocol 데이터 및 제어 흐름 (Control Flow)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Skybound Protocol 데이터 ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Skybound Protocol 데이터 및 제어 흐름 (Control Flow).md]] +- Raw Source: 00_Raw/2026-04-20/Skybound Protocol 데이터 및 제어 흐름 (Control Flow).md --- diff --git a/01_Archive/2026-04-20/Skybound Protocol 시스템 아키텍처 및 데이터 흐름 분석.md b/01_Archive/2026-04-20/Skybound Protocol 시스템 아키텍처 및 데이터 흐름 분석.md index 547b5dff..0270bb52 100644 --- a/01_Archive/2026-04-20/Skybound Protocol 시스템 아키텍처 및 데이터 흐름 분석.md +++ b/01_Archive/2026-04-20/Skybound Protocol 시스템 아키텍처 및 데이터 흐름 분석.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-ADF455 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Skybound Protocol 시스템 아키텍처 및 데이터 흐름 분석" --- -# [[Skybound Protocol 시스템 아키텍처 및 데이터 흐름 분석]] +# [[Skybound Protocol 시스템 아키텍처 및 데이터 흐름 분석|Skybound Protocol 시스템 아키텍처 및 데이터 흐름 분석]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Skybound Protocol 시스템 ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Skybound Protocol 시스템 아키텍처 및 데이터 흐름 분석.md]] +- Raw Source: 00_Raw/2026-04-20/Skybound Protocol 시스템 아키텍처 및 데이터 흐름 분석.md --- diff --git a/01_Archive/2026-04-20/Skybound Protocol 코드리뷰.md b/01_Archive/2026-04-20/Skybound Protocol 코드리뷰.md index 60250a11..bf745d6f 100644 --- a/01_Archive/2026-04-20/Skybound Protocol 코드리뷰.md +++ b/01_Archive/2026-04-20/Skybound Protocol 코드리뷰.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-274080 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Skybound Protocol 코드리뷰" --- -# [[Skybound Protocol 코드리뷰]] +# [[Skybound Protocol 코드리뷰|Skybound Protocol 코드리뷰]] ## 📌 한 줄 통찰 (The Karpathy Summary) > **Skybound Protocol**은 React와 TypeScript로 구현된 고성능 아카이브 스타일 슈팅 게임 엔진입니다. "Code-as-Data" 원칙에 따라 모든 게임 밸런스와 AI 행동 양식을 상수화하여 관리하며, 수만 개의 파티클과 복잡한 탄막 패턴을 웹 브라우저에서 60FPS로 유지하도록 최적화되어 있습니다. @@ -20,8 +20,8 @@ github_commit: "[P-Reinforce] Continuous Worker - Skybound Protocol 코드리뷰 - **정책 변화:** AI 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[React Game Development]], [[Entity Component System (ECS)]], [[Canvas Physics]], [[Data-Driven Design]] -- **Projects/Contexts:** [[Antigravity Games]], [[Technical Bible Project]] +- **Related Topics:** React Game Development, [[Entity Component System (ECS)|Entity Component System (ECS)]], Canvas Physics, [[데이터 기반 설계 (Data-Driven Design)|Data-Driven Design]] +- **Projects/Contexts:** Antigravity Games, Technical Bible Project - **Contradictions/Notes:** - **연산 최적화:** 현재 모든 거리 계산에 `Math.hypot`을 사용 중이나, 개체가 수천 개로 늘어날 경우 제곱근 연산 부하를 줄이기 위해 제곱 거리 비교(`dx*dx + dy*dy`) 방식 도입이 필요할 수 있습니다. - **상태 관리:** React 환경임에도 불구하고 실시간 성능을 위해 가변(Mutable) 객체와 `ctx`를 통한 직접 수정을 혼용하고 있습니다. @@ -33,5 +33,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Skybound Protocol 코드리뷰 --- # 🕵️ Skybound Protocol 코드 리뷰 리포트 -- Raw Source: [[00_Raw/2026-04-20/Skybound Protocol 코드리뷰.md]] +- Raw Source: 00_Raw/2026-04-20/Skybound Protocol 코드리뷰.md --- diff --git a/01_Archive/2026-04-20/Smart City Digital Twins.md b/01_Archive/2026-04-20/Smart City Digital Twins.md index a8c92edc..26da0359 100644 --- a/01_Archive/2026-04-20/Smart City Digital Twins.md +++ b/01_Archive/2026-04-20/Smart City Digital Twins.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-888FC9 -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Smart City Digital Twins" --- -# [[Smart City Digital Twins]] +# [[Smart City Digital Twins|Smart City Digital Twins]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Smart City Digital Twins" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Smart City Digital Twins.md]] +- Raw Source: 00_Raw/2026-04-20/Smart City Digital Twins.md --- diff --git a/01_Archive/2026-04-20/Smart-City-Frameworks.md b/01_Archive/2026-04-20/Smart-City-Frameworks.md index 8cb59abb..54e39986 100644 --- a/01_Archive/2026-04-20/Smart-City-Frameworks.md +++ b/01_Archive/2026-04-20/Smart-City-Frameworks.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-28F252 -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Smart-City-Frameworks" --- -# [[Smart-City-Frameworks]] +# [[Smart-City-Frameworks|Smart-City-Frameworks]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Smart-City-Frameworks" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Smart-City-Frameworks.md]] +- Raw Source: 00_Raw/2026-04-20/Smart-City-Frameworks.md --- diff --git a/01_Archive/2026-04-20/Smithsonian-Digital-Repository.md b/01_Archive/2026-04-20/Smithsonian-Digital-Repository.md index eef31f89..d85b4dd2 100644 --- a/01_Archive/2026-04-20/Smithsonian-Digital-Repository.md +++ b/01_Archive/2026-04-20/Smithsonian-Digital-Repository.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-F0CD87 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Smithsonian-Digital-Repository" --- -# [[Smithsonian-Digital-Repository]] +# [[Smithsonian-Digital-Repository|Smithsonian-Digital-Repository]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Smithsonian-Digital-Repository ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Smithsonian-Digital-Repository.md]] +- Raw Source: 00_Raw/2026-04-20/Smithsonian-Digital-Repository.md --- diff --git a/01_Archive/2026-04-20/Snyk Checkmarx Endor Labs 등 종합 애플리케이션 보안 플랫폼.md b/01_Archive/2026-04-20/Snyk Checkmarx Endor Labs 등 종합 애플리케이션 보안 플랫폼.md index b6ccdec2..ef58beb8 100644 --- a/01_Archive/2026-04-20/Snyk Checkmarx Endor Labs 등 종합 애플리케이션 보안 플랫폼.md +++ b/01_Archive/2026-04-20/Snyk Checkmarx Endor Labs 등 종합 애플리케이션 보안 플랫폼.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-1D1222 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Snyk Checkmarx Endor Labs 등 종합 애플리케이션 보안 플랫폼" --- -# [[Snyk Checkmarx Endor Labs 등 종합 애플리케이션 보안 플랫폼]] +# [[Snyk Checkmarx Endor Labs 등 종합 애플리케이션 보안 플랫폼|Snyk Checkmarx Endor Labs 등 종합 애플리케이션 보안 플랫폼]] ## 📌 한 줄 통찰 (The Karpathy Summary) > Snyk, Checkmarx, Endor Labs 등은 소프트웨어 개발 수명 주기(SDLC) 전반에 걸쳐 코드의 취약점을 탐지하고 수정을 지원하는 종합 애플리케이션 보안 플랫폼입니다 [1-4]. 이들 플랫폼은 정적 애플리케이션 보안 테스트(SAST), 소프트웨어 구성 분석(SCA), 컨테이너 및 IaC(코드형 인프라) 스캔 등 다양한 보안 영역을 제공하며, '시프트 레프트(Shift-Left)' 전략을 통해 개발 초기 단계에서 보안 이슈를 해결하도록 돕습니다 [2, 3, 5, 6]. 최근에는 인공지능(AI)과 머신러닝 기술을 결합하여 오탐율을 줄이고 실시간 자동 수정 제안을 제공하는 형태로 고도화되고 있습니다 [7, 8]. @@ -23,11 +23,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Snyk Checkmarx Endor Labs 등 - **정책 변화:** AI 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Static Application Security Testing (SAST)]], [[Software Composition Analysis (SCA)]], [[DevSecOps]] -- **Projects/Contexts:** [[Shift-Left Security]], [[Reachability Analysis]], [[AI-powered Remediation]] +- **Related Topics:** [[Static Application Security Testing (SAST)|Static Application Security Testing (SAST)]], [[Software Composition Analysis (SCA)|Software Composition Analysis (SCA)]], [[DevSecOps|DevSecOps]] +- **Projects/Contexts:** Shift-Left Security, [[Reachability Analysis|Reachability Analysis]], AI-powered Remediation - **Contradictions/Notes:** 소스에 따르면 각 플랫폼은 명확한 타겟층과 상충되는 트레이드오프를 가집니다. Checkmarx는 엔터프라이즈 수준의 맞춤 설정과 거버넌스에 강력하지만 소규모 팀에게는 무거울 수 있습니다 [12]. 반면 Snyk은 빠른 IDE 통합과 채택률로 개발자 경험에 탁월하지만, 언어 지원 범위가 타 엔터프라이즈 벤더보다 다소 좁을 수 있습니다 [16, 17]. 또한, Endor Labs는 강력한 도달 가능성 분석을 자랑하지만 전용 SAST 도구에 비해 SAST 룰 커버리지나 언어 지원 확장이 아직 진행 중이라는 한계가 있습니다 [13]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/Snyk, Checkmarx, Endor Labs 등 종합 애플리케이션 보안 플랫폼.md]] +- Raw Source: 00_Raw/2026-04-20/Snyk, Checkmarx, Endor Labs 등 종합 애플리케이션 보안 플랫폼.md --- diff --git a/01_Archive/2026-04-20/Snyk Open Source.md b/01_Archive/2026-04-20/Snyk Open Source.md index c55d60c8..78e9f044 100644 --- a/01_Archive/2026-04-20/Snyk Open Source.md +++ b/01_Archive/2026-04-20/Snyk Open Source.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-F26CB3 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Snyk Open Source" --- -# [[Snyk Open Source]] +# [[Snyk Open Source|Snyk Open Source]] ## 📌 한 줄 통찰 (The Karpathy Summary) > Snyk Open Source는 애플리케이션을 구성하는 서드파티 종속성(third-party dependencies)을 스캔하여 알려진 보안 취약점을 탐지하는 소프트웨어 구성 분석(SCA, Software Composition Analysis) 도구입니다 [1, 2]. 이 도구는 `package.json`, `pom.xml`, `requirements.txt`와 같은 매니페스트 파일을 검사하고 Snyk의 엄선된 취약점 데이터베이스와 대조하여 위험 요소를 식별합니다 [3]. 또한, 취약한 패키지를 안전한 버전으로 업그레이드할 수 있도록 풀 리퀘스트(Pull Request)를 자동으로 생성하는 기능을 제공하여 신속한 보안 패치를 돕습니다 [3]. @@ -22,11 +22,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Snyk Open Source" - **정책 변화:** Design & Experience 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[SCA (Software Composition Analysis)]], [[Snyk Code]], [[서드파티 종속성 (Third-party dependencies)]], [[CVE (Common Vulnerabilities and Exposures)]] -- **Projects/Contexts:** [[Snyk Security Platform]] +- **Related Topics:** SCA (Software Composition Analysis), Snyk Code, 서드파티 종속성 (Third-party dependencies), CVE (Common Vulnerabilities and Exposures) +- **Projects/Contexts:** Snyk Security Platform - **Contradictions/Notes:** 소스의 내용 간에 특별한 모순은 발견되지 않았습니다. 소스는 Snyk Open Source(SCA)와 Snyk Code(SAST)가 경쟁 관계가 아니라 완전히 다른 영역을 검사하며, 강력한 보안 태세를 위해 상호 보완적으로 사용되어야 한다는 점을 거듭 강조합니다 [2, 3, 5]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Snyk Open Source.md]] +- Raw Source: 00_Raw/2026-04-20/Snyk Open Source.md --- diff --git a/01_Archive/2026-04-20/Snyk, Checkmarx, Endor Labs 등 종합 애플리케이션 보안 플랫폼.md b/01_Archive/2026-04-20/Snyk, Checkmarx, Endor Labs 등 종합 애플리케이션 보안 플랫폼.md index 4e88604e..35d92320 100644 --- a/01_Archive/2026-04-20/Snyk, Checkmarx, Endor Labs 등 종합 애플리케이션 보안 플랫폼.md +++ b/01_Archive/2026-04-20/Snyk, Checkmarx, Endor Labs 등 종합 애플리케이션 보안 플랫폼.md @@ -1,4 +1,4 @@ -# [[Snyk, Checkmarx, Endor Labs 등 종합 애플리케이션 보안 플랫폼]] +# [[Snyk, Checkmarx, Endor Labs 등 종합 애플리케이션 보안 플랫폼|Snyk, Checkmarx, Endor Labs 등 종합 애플리케이션 보안 플랫폼]] ## 📌 Brief Summary Snyk, Checkmarx, Endor Labs 등은 소프트웨어 개발 수명 주기(SDLC) 전반에 걸쳐 코드의 취약점을 탐지하고 수정을 지원하는 종합 애플리케이션 보안 플랫폼입니다 [1-4]. 이들 플랫폼은 정적 애플리케이션 보안 테스트(SAST), 소프트웨어 구성 분석(SCA), 컨테이너 및 IaC(코드형 인프라) 스캔 등 다양한 보안 영역을 제공하며, '시프트 레프트(Shift-Left)' 전략을 통해 개발 초기 단계에서 보안 이슈를 해결하도록 돕습니다 [2, 3, 5, 6]. 최근에는 인공지능(AI)과 머신러닝 기술을 결합하여 오탐율을 줄이고 실시간 자동 수정 제안을 제공하는 형태로 고도화되고 있습니다 [7, 8]. @@ -10,8 +10,8 @@ Snyk, Checkmarx, Endor Labs 등은 소프트웨어 개발 수명 주기(SDLC) - **AI 기반 탐지 및 수정 자동화**: 기존의 단순 규칙 및 패턴 매칭 기반 도구의 한계(비즈니스 로직 이해 부족 및 높은 오탐률)를 극복하기 위해, 이들 플랫폼은 AI-Native 구조를 채택하여 코드의 문맥과 데이터 흐름(Data flow)을 심층 분석하고, 취약점의 우선순위를 평가하여 개발자에게 실행 가능한(Actionable) 패치 코드를 즉시 제안합니다 [2, 6-8, 15]. ## 🔗 Knowledge Connections -- **Related Topics:** [[Static Application Security Testing (SAST)]], [[Software Composition Analysis (SCA)]], [[DevSecOps]] -- **Projects/Contexts:** [[Shift-Left Security]], [[Reachability Analysis]], [[AI-powered Remediation]] +- **Related Topics:** [[Static Application Security Testing (SAST)|Static Application Security Testing (SAST)]], [[Software Composition Analysis (SCA)|Software Composition Analysis (SCA)]], [[DevSecOps|DevSecOps]] +- **Projects/Contexts:** Shift-Left Security, [[Reachability Analysis|Reachability Analysis]], AI-powered Remediation - **Contradictions/Notes:** 소스에 따르면 각 플랫폼은 명확한 타겟층과 상충되는 트레이드오프를 가집니다. Checkmarx는 엔터프라이즈 수준의 맞춤 설정과 거버넌스에 강력하지만 소규모 팀에게는 무거울 수 있습니다 [12]. 반면 Snyk은 빠른 IDE 통합과 채택률로 개발자 경험에 탁월하지만, 언어 지원 범위가 타 엔터프라이즈 벤더보다 다소 좁을 수 있습니다 [16, 17]. 또한, Endor Labs는 강력한 도달 가능성 분석을 자랑하지만 전용 SAST 도구에 비해 SAST 룰 커버리지나 언어 지원 확장이 아직 진행 중이라는 한계가 있습니다 [13]. --- diff --git a/01_Archive/2026-04-20/Social Constructivism.md b/01_Archive/2026-04-20/Social Constructivism.md index dd0b1ebc..2f51da54 100644 --- a/01_Archive/2026-04-20/Social Constructivism.md +++ b/01_Archive/2026-04-20/Social Constructivism.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-A416E7 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Social Constructivism" --- -# [[Social Constructivism]] +# [[Social Constructivism|Social Constructivism]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Social Constructivism" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Social Constructivism.md]] +- Raw Source: 00_Raw/2026-04-20/Social Constructivism.md --- diff --git a/01_Archive/2026-04-20/Social Learning Theory.md b/01_Archive/2026-04-20/Social Learning Theory.md index f8266839..d46ef4cc 100644 --- a/01_Archive/2026-04-20/Social Learning Theory.md +++ b/01_Archive/2026-04-20/Social Learning Theory.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-26C0EB -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Social Learning Theory" --- -# [[Social Learning Theory]] +# [[Social Learning Theory|Social Learning Theory]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Social Learning Theory" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Social Learning Theory.md]] +- Raw Source: 00_Raw/2026-04-20/Social Learning Theory.md --- diff --git a/01_Archive/2026-04-20/Social Systems Theory.md b/01_Archive/2026-04-20/Social Systems Theory.md index 88566ee4..9eb98401 100644 --- a/01_Archive/2026-04-20/Social Systems Theory.md +++ b/01_Archive/2026-04-20/Social Systems Theory.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-700A72 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Social Systems Theory" --- -# [[Social Systems Theory]] +# [[Social Systems Theory|Social Systems Theory]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Social Systems Theory" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Social Systems Theory.md]] +- Raw Source: 00_Raw/2026-04-20/Social Systems Theory.md --- diff --git a/01_Archive/2026-04-20/Socially Assistive Robotics (SAR).md b/01_Archive/2026-04-20/Socially Assistive Robotics (SAR).md index 3d5c1bf1..7e722ee1 100644 --- a/01_Archive/2026-04-20/Socially Assistive Robotics (SAR).md +++ b/01_Archive/2026-04-20/Socially Assistive Robotics (SAR).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-22DA21 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Socially Assistive Robotics (SAR)" --- -# [[Socially Assistive Robotics (SAR)]] +# [[Socially Assistive Robotics (SAR)|Socially Assistive Robotics (SAR)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Socially Assistive Robotics (S ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Socially Assistive Robotics (SAR).md]] +- Raw Source: 00_Raw/2026-04-20/Socially Assistive Robotics (SAR).md --- diff --git a/01_Archive/2026-04-20/Soft Navigation.md b/01_Archive/2026-04-20/Soft Navigation.md index e3628305..00b5a573 100644 --- a/01_Archive/2026-04-20/Soft Navigation.md +++ b/01_Archive/2026-04-20/Soft Navigation.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-A5364E -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Soft Navigation" --- -# [[Soft Navigation]] +# [[Soft Navigation|Soft Navigation]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 소프트 내비게이션(Soft Navigation)은 단일 페이지 자바스크립트 애플리케이션(SPA)에서 URL이 변경될 때 웹사이트 전체를 다시 로드하지 않고 콘텐츠를 전환하는 방식을 의미합니다 [1]. 기존의 성능 지표인 최대 콘텐츠 풀 페인트(Largest Contentful Paint, LCP)는 초기 내비게이션의 로드 시간만 측정하기 때문에, 후속 탐색 성능을 파악하는 데 큰 사각지대가 존재해 왔습니다 [2]. 이를 해결하기 위해 Chrome은 소프트 내비게이션 발생을 감지하고 상호작용에 따른 DOM 수정 사항을 관찰하여 개별 로드 시간을 측정할 수 있는 새로운 API를 테스트하고 있습니다 [2]. @@ -22,11 +22,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Soft Navigation" - **정책 변화:** AI 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Single-Page JavaScript Applications]], [[Largest Contentful Paint]], [[Origin Trials]] -- **Projects/Contexts:** [[Chrome 2025 Soft Navigations Origin Trial]] +- **Related Topics:** Single-Page JavaScript Applications, Largest Contentful Paint, Origin Trials +- **Projects/Contexts:** Chrome 2025 Soft Navigations Origin Trial - **Contradictions/Notes:** 소스 내에 상충하는 정보는 없습니다. 다만, 단일 페이지 앱이 '더 빠른 후속 탐색'을 제공한다는 약속을 실제로 이행하고 있는지 여부를 알기 위해서는 Chrome에 소프트 내비게이션 성능 측정 지원이 반드시 도입되어야 한다는 점이 개발자들의 더 나은 의사결정을 위한 핵심 과제로 지적되고 있습니다 [3]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Soft Navigation.md]] +- Raw Source: 00_Raw/2026-04-20/Soft Navigation.md --- diff --git a/01_Archive/2026-04-20/Software Architecture API Contract Design.md b/01_Archive/2026-04-20/Software Architecture API Contract Design.md index 6b92d06f..7189eebb 100644 --- a/01_Archive/2026-04-20/Software Architecture API Contract Design.md +++ b/01_Archive/2026-04-20/Software Architecture API Contract Design.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-A7EF2F -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Software Architecture API Contract Design" --- -# [[Software Architecture API Contract Design]] +# [[Software Architecture API Contract Design|Software Architecture API Contract Design]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Software Architecture API Con ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Software Architecture & API Contract Design.md]] +- Raw Source: 00_Raw/2026-04-20/Software Architecture & API Contract Design.md --- diff --git a/01_Archive/2026-04-20/Software Architecture & API Contract Design.md b/01_Archive/2026-04-20/Software Architecture & API Contract Design.md index 51826fe8..aa870eae 100644 --- a/01_Archive/2026-04-20/Software Architecture & API Contract Design.md +++ b/01_Archive/2026-04-20/Software Architecture & API Contract Design.md @@ -1,4 +1,4 @@ -[[Software Architecture & API Contract Design]] +[[Software Architecture & API Contract Design|Software Architecture & API Contract Design]] 📌 Brief Summary Software Architecture and API Contract Design refers to the formal definition of boundaries, data structures, and behavioral expectations between decoupled system components. In the context of TypeScript, this involves utilizing the type system to enforce structural integrity, ensuring that both producers and consumers adhere to a shared, verifiable schema that minimizes runtime errors and integration friction. @@ -10,8 +10,8 @@ Software Architecture and API Contract Design refers to the formal definition of * **Abstraction via Generics**: To create reusable and scalable architectures, API contracts often employ Generics (``). This allows for the definition of standardized response envelopes (e.g., `ApiResponse`) where the metadata (status, timestamp) is fixed by the architecture, but the payload remains flexible, maintaining type safety across diverse data entities. 🔗 Knowledge Connections -* Related Topics: [[Structural Typing]], [[Discriminated Unions]], [[Runtime Type Validation]] -* Projects/Contexts: [[Microservices Communication]], [[Full-stack Type Safety (End-to-end Type Safety)]] +* Related Topics: [[Structural Typing|Structural Typing]], [[Discriminated Unions|Discriminated Unions]], [[Runtime-Type-Validation|Runtime Type Validation]] +* Projects/Contexts: Microservices Communication, Full-stack Type Safety (End-to-end Type Safety) * Contradictions/Notes: While `interface` is preferred for declaration merging and performance in large scales, `type` aliases are necessary for complex intersections and unions; the choice depends on whether the contract needs to be extensible or strictly defined. Last updated: 2026-04-17 \ No newline at end of file diff --git a/01_Archive/2026-04-20/Software-Contract-Enforcement.md b/01_Archive/2026-04-20/Software-Contract-Enforcement.md index ec2a7f99..ece210a0 100644 --- a/01_Archive/2026-04-20/Software-Contract-Enforcement.md +++ b/01_Archive/2026-04-20/Software-Contract-Enforcement.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-B29206 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Software-Contract-Enforcement" --- -# [[Software-Contract-Enforcement]] +# [[Software-Contract-Enforcement|Software-Contract-Enforcement]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Software-Contract-Enforcement" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Software-Contract-Enforcement.md]] +- Raw Source: 00_Raw/2026-04-20/Software-Contract-Enforcement.md --- diff --git a/01_Archive/2026-04-20/Software-Product-Management.md b/01_Archive/2026-04-20/Software-Product-Management.md index 00183a34..993875fc 100644 --- a/01_Archive/2026-04-20/Software-Product-Management.md +++ b/01_Archive/2026-04-20/Software-Product-Management.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-7094F5 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Software-Product-Management" --- -# [[Software-Product-Management]] +# [[Software-Product-Management|Software-Product-Management]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Software-Product-Management" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Software-Product-Management.md]] +- Raw Source: 00_Raw/2026-04-20/Software-Product-Management.md --- diff --git a/01_Archive/2026-04-20/SonarQube.md b/01_Archive/2026-04-20/SonarQube.md index 8dd469fb..7df35c62 100644 --- a/01_Archive/2026-04-20/SonarQube.md +++ b/01_Archive/2026-04-20/SonarQube.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-0785CD -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - SonarQube" --- -# [[SonarQube]] +# [[SonarQube|SonarQube]] ## 📌 한 줄 통찰 (The Karpathy Summary) > SonarQube는 소프트웨어의 품질, 보안, 유지보수성을 보장하기 위해 설계된 강력한 정적 애플리케이션 보안 테스트(SAST) 및 자동화된 코드 리뷰 플랫폼이다 [1-3]. 결정론적인 정적 분석 엔진과 AI 기능을 활용하여 사람이 작성한 코드뿐만 아니라 AI가 생성한 코드의 결함, 보안 취약점, 코드 스멜을 자동으로 식별한다 [3-5]. 개발자의 IDE부터 CI/CD 파이프라인, 풀 리퀘스트(PR) 워크플로우에 원활하게 통합되어 코드가 릴리스되기 전에 일관된 품질 표준과 규정 준수를 강제한다 [6-8]. @@ -23,11 +23,11 @@ github_commit: "[P-Reinforce] Continuous Worker - SonarQube" - **정책 변화:** AI 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[SAST]], [[Quality Gates]], [[Model Context Protocol (MCP)]], [[Clean as You Code]] -- **Projects/Contexts:** [[CI/CD 및 Pull Request 자동화 리뷰]], [[AI 생성 코드 검증(AI Code Assurance)]] +- **Related Topics:** [[SAST|SAST]], [[Quality Gates|Quality Gates]], [[Model Context Protocol (MCP)|Model Context Protocol (MCP)]], [[Clean as You Code|Clean as You Code]] +- **Projects/Contexts:** [[CI_CD 및 Pull Request 자동화 리뷰|CI/CD 및 Pull Request 자동화 리뷰]], [[AI 생성 코드 검증(AI Code Assurance)|AI 생성 코드 검증(AI Code Assurance)]] - **Contradictions/Notes:** SonarQube는 코드 품질과 보안을 통합적으로 제공하는 매우 강력한 플랫폼이지만, 취약점 탐지 방식이 주로 규칙(Rule) 및 패턴에 의존하고 있다. 따라서 컨텍스트와 비즈니스 로직을 자체적으로 이해해야 하는 새로운 형태의 결함이나 취약점을 탐지하는 데는 최신 AI 네이티브 기반 스캐너에 비해 덜 효과적일 수 있다는 한계가 지적된다 [3, 19]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/SonarQube.md]] +- Raw Source: 00_Raw/2026-04-20/SonarQube.md --- diff --git a/01_Archive/2026-04-20/Sorting.md b/01_Archive/2026-04-20/Sorting.md index beef0248..c11b2ac3 100644 --- a/01_Archive/2026-04-20/Sorting.md +++ b/01_Archive/2026-04-20/Sorting.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-9C6ABB -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Sorting" --- -# [[Sorting]] +# [[Sorting|Sorting]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 3D 렌더링 환경에서 정렬(Sorting)은 카메라와의 거리를 기준으로 객체의 렌더링 순서를 결정하는 핵심 프로세스입니다. 불투명한 객체는 앞에서 뒤로(Front-to-Back) 정렬하여 오버드로우를 최소화하고, 투명한 객체는 뒤에서 앞으로(Back-to-Front) 정렬하여 알파 블렌딩(Alpha Blending)을 올바르게 표현하기 위해 필수적입니다. 그러나 수많은 객체를 다루는 인스턴싱 환경에서는 매 프레임 정렬을 계산하고 버퍼를 재배열하는 과정이 심각한 CPU 병목 현상을 유발할 수 있습니다 [1, 2]. @@ -32,11 +32,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Sorting" - **정책 변화:** Graphics & Performance 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[InstancedMesh]], [[BatchedMesh]], [[Overdraw]], [[Alpha Blending]], [[Frustum Culling]], [[Radix Sort]] -- **Projects/Contexts:** [[Three.js]], [[InstancedMesh2]] +- **Related Topics:** [[InstancedMesh|InstancedMesh]], [[BatchedMesh|BatchedMesh]], [[Overdraw|Overdraw]], [[Alpha Blending|Alpha Blending]], [[Frustum Culling|Frustum Culling]], [[Radix Sort|Radix Sort]] +- **Projects/Contexts:** [[Three.js|Three.js]], [[InstancedMesh2|InstancedMesh2]] - **Contradictions/Notes:** 투명도 및 오버드로우 해결을 위해 정렬이 필수적이지만, 정렬 연산 자체(버퍼 재배열 등)가 CPU에 큰 부하를 가하기 때문에 오히려 전체 프레임 레이트를 떨어뜨리는 역설적인 결과를 낳을 수 있습니다. 이는 GPU 압박과 CPU 병목 사이의 가혹한 절충안을 요구합니다 [1, 2, 7, 8]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Sorting.md]] +- Raw Source: 00_Raw/2026-04-20/Sorting.md --- diff --git a/01_Archive/2026-04-20/Sparse Autoencoder (SAE).md b/01_Archive/2026-04-20/Sparse Autoencoder (SAE).md index 342d2ec6..3a729c0f 100644 --- a/01_Archive/2026-04-20/Sparse Autoencoder (SAE).md +++ b/01_Archive/2026-04-20/Sparse Autoencoder (SAE).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-A11EAF -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Sparse Autoencoder (SAE)" --- -# [[Sparse Autoencoder (SAE)]] +# [[Sparse Autoencoder (SAE)|Sparse Autoencoder (SAE)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Sparse Autoencoder (SAE)" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Sparse Autoencoder (SAE).md]] +- Raw Source: 00_Raw/2026-04-20/Sparse Autoencoder (SAE).md --- diff --git a/01_Archive/2026-04-20/Spatial Cognition.md b/01_Archive/2026-04-20/Spatial Cognition.md index 284b54a3..af62d810 100644 --- a/01_Archive/2026-04-20/Spatial Cognition.md +++ b/01_Archive/2026-04-20/Spatial Cognition.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-06C479 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Spatial Cognition" --- -# [[Spatial Cognition]] +# [[Spatial Cognition|Spatial Cognition]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Spatial Cognition" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Spatial Cognition.md]] +- Raw Source: 00_Raw/2026-04-20/Spatial Cognition.md --- diff --git a/01_Archive/2026-04-20/Spatial Computing.md b/01_Archive/2026-04-20/Spatial Computing.md index a69b4fba..7a3c70a4 100644 --- a/01_Archive/2026-04-20/Spatial Computing.md +++ b/01_Archive/2026-04-20/Spatial Computing.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-C2600F -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Spatial Computing" --- -# [[Spatial Computing]] +# [[Spatial Computing|Spatial Computing]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Spatial Computing" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Spatial Computing.md]] +- Raw Source: 00_Raw/2026-04-20/Spatial Computing.md --- diff --git a/01_Archive/2026-04-20/Spatial Partitioning.md b/01_Archive/2026-04-20/Spatial Partitioning.md index 4665462b..cbd4fba9 100644 --- a/01_Archive/2026-04-20/Spatial Partitioning.md +++ b/01_Archive/2026-04-20/Spatial Partitioning.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-1BF809 -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Spatial Partitioning" --- -# [[Spatial Partitioning]] +# [[Spatial Partitioning|Spatial Partitioning]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 공간 분할(Spatial Partitioning)은 3D 그래픽스에서 대규모 씬(Scene)의 수많은 객체나 복잡한 기하학적 구조를 효율적으로 렌더링하고 관리하기 위한 최적화 기법입니다. 3D 공간을 BVH(Bounding Volume Hierarchy)나 옥트리(Octree)와 같은 계층적 인덱스 자료구조로 분할하여 관리함으로써, 시스템이 시야 밖의 객체를 조기에 연산에서 제외(Culling)할 수 있게 합니다 [1]. 이를 통해 광선 추적(Raycasting) 상호작용의 속도를 높이고, 프러스텀 컬링의 효율성을 극대화하여 CPU 및 GPU의 과부하를 방지하는 핵심적인 역할을 수행합니다 [1-3]. @@ -23,11 +23,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Spatial Partitioning" - **정책 변화:** Graphics & Performance 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Frustum Culling]], [[BVH (Bounding Volume Hierarchy)]], [[Octree]], [[InstancedMesh]], [[Raycasting]] -- **Projects/Contexts:** [[three-mesh-bvh]], [[Tesseract Engine]] +- **Related Topics:** [[Frustum Culling|Frustum Culling]], BVH (Bounding Volume Hierarchy), Octree, [[InstancedMesh|InstancedMesh]], [[Raycasting|Raycasting]] +- **Projects/Contexts:** [[three-mesh-bvh|three-mesh-bvh]], Tesseract Engine - **Contradictions/Notes:** 대규모 환경에서 레이캐스팅 및 렌더링 최적화를 위해 공간 인덱스(Spatial index)를 활용하는 것은 명확한 성능 향상을 제공하지만, 이러한 공간 분할 자료구조를 구축하고 유지하는 데에는 상당한 복잡성(non-trivial complexity)이 수반되며 구현 난이도가 높다는 개발자들의 논의가 존재합니다 [6, 9]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Spatial Partitioning.md]] +- Raw Source: 00_Raw/2026-04-20/Spatial Partitioning.md --- diff --git a/01_Archive/2026-04-20/Spatial UI.md b/01_Archive/2026-04-20/Spatial UI.md index a96e39d0..8d98bd81 100644 --- a/01_Archive/2026-04-20/Spatial UI.md +++ b/01_Archive/2026-04-20/Spatial UI.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-E02F81 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Spatial UI" --- -# [[Spatial UI]] +# [[Spatial UI|Spatial UI]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Spatial UI" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Spatial UI.md]] +- Raw Source: 00_Raw/2026-04-20/Spatial UI.md --- diff --git a/01_Archive/2026-04-20/Spatial-Syntax.md b/01_Archive/2026-04-20/Spatial-Syntax.md index 8d5ed614..6332589e 100644 --- a/01_Archive/2026-04-20/Spatial-Syntax.md +++ b/01_Archive/2026-04-20/Spatial-Syntax.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-9BAC11 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Spatial-Syntax" --- -# [[Spatial-Syntax]] +# [[Spatial-Syntax|Spatial-Syntax]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Spatial-Syntax" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Spatial-Syntax.md]] +- Raw Source: 00_Raw/2026-04-20/Spatial-Syntax.md --- diff --git a/01_Archive/2026-04-20/Spatial_Computing.md b/01_Archive/2026-04-20/Spatial_Computing.md index 7ff81a59..2f78db34 100644 --- a/01_Archive/2026-04-20/Spatial_Computing.md +++ b/01_Archive/2026-04-20/Spatial_Computing.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-METAVERSE-002 -category: "[[10_Wiki/💡 Topics/Metaverse]]" +category: "10_Wiki/💡 Topics/Metaverse" confidence_score: 0.94 tags: [metaverse, spatial-computing, ar, vr, xr] last_reinforced: 2026-04-20 github_commit: "batch-reinforce-04" --- -# [[Spatial Computing]] +# [[Spatial Computing|Spatial Computing]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 화면 속에 갇혀 있던 디지털 정보를 우리가 발 딛고 서 있는 물리적 공간으로 끌어내어 확장하는 계산 패러다임. @@ -24,6 +24,6 @@ github_commit: "batch-reinforce-04" - **정책 변화:** 사용자 만족도(w3) 피드백에 따라 공간 피로도 감소를 위한 설계 지침 비중 상향. ## 🔗 지식 연결 (Graph) -- **Parent:** [[10_Wiki/💡 Topics/Metaverse]] -- **Related:** [[Architecture]], [[MR]], [[SLAM]] -- **Raw Source:** [[00_Raw/2026-04-20/Spatial Computing.md]] +- **Parent:** 10_Wiki/💡 Topics/Metaverse +- **Related:** [[Architecture|Architecture]], MR, SLAM +- **Raw Source:** 00_Raw/2026-04-20/Spatial Computing.md diff --git a/01_Archive/2026-04-20/Special Education Interventions.md b/01_Archive/2026-04-20/Special Education Interventions.md index 03dc19fc..ffe0983d 100644 --- a/01_Archive/2026-04-20/Special Education Interventions.md +++ b/01_Archive/2026-04-20/Special Education Interventions.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-B2C5F1 -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Special Education Interventions" --- -# [[Special Education Interventions]] +# [[Special Education Interventions|Special Education Interventions]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Special Education Intervention ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Special Education Interventions.md]] +- Raw Source: 00_Raw/2026-04-20/Special Education Interventions.md --- diff --git a/01_Archive/2026-04-20/Specification Gaming (명세 우회).md b/01_Archive/2026-04-20/Specification Gaming (명세 우회).md index 991b6984..c6cb6a6d 100644 --- a/01_Archive/2026-04-20/Specification Gaming (명세 우회).md +++ b/01_Archive/2026-04-20/Specification Gaming (명세 우회).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-1BD229 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Specification Gaming (명세 우회)" --- -# [[Specification Gaming (명세 우회)]] +# [[Specification Gaming (명세 우회)|Specification Gaming (명세 우회)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Specification Gaming (명세 ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Specification Gaming (명세 우회).md]] +- Raw Source: 00_Raw/2026-04-20/Specification Gaming (명세 우회).md --- diff --git a/01_Archive/2026-04-20/Spectre and Meltdown.md b/01_Archive/2026-04-20/Spectre and Meltdown.md index 97697a61..fa7f7b5a 100644 --- a/01_Archive/2026-04-20/Spectre and Meltdown.md +++ b/01_Archive/2026-04-20/Spectre and Meltdown.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-8FCA7F -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Spectre and Meltdown" --- -# [[Spectre and Meltdown]] +# [[Spectre and Meltdown|Spectre and Meltdown]] ## 📌 한 줄 통찰 (The Karpathy Summary) > Spectre와 Meltdown은 현대 프로세서의 투기적 실행(speculative execution) 과정에서 발생하는 취약점을 악용하여, 공격자가 접근 권한이 없는 메모리 영역의 비밀 데이터를 읽을 수 있게 하는 보안 결함이다 [1, 2]. 웹 브라우저 환경에서는 캐시 적중률과 메모리 접근 패턴의 미세한 시간 차이를 측정하는 타이밍 공격을 통해 이 취약점이 실행될 수 있다 [3-6]. 이를 방지하기 위해 브라우저 엔진들은 타이머의 정밀도를 낮추고 분기 없는 보안 검사를 도입하였으며, 이는 결과적으로 GPU 및 WebGL 파이프라인 연산의 미세 지연(micro-latency)을 소폭 증가시켰다 [7-9]. @@ -30,11 +30,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Spectre and Meltdown" - **정책 변화:** Graphics & Performance 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[EXT_disjoint_timer_query]], [[Timestamp Queries Quantization]], [[Branchless Security Checks]] -- **Projects/Contexts:** [[WebKit Security Mitigations]], [[WebGPU / WebGL Timing API Security]] +- **Related Topics:** [[EXT_disjoint_timer_query|EXT_disjoint_timer_query]], [[Timestamp Queries Quantization|Timestamp Queries Quantization]], [[Branchless Security Checks|Branchless Security Checks]] +- **Projects/Contexts:** [[WebKit Security Mitigations|WebKit Security Mitigations]], [[WebGPU _ WebGL Timing API Security|WebGPU / WebGL Timing API Security]] - **Contradictions/Notes:** 소스에는 Spectre 및 Meltdown 취약점으로 인해 도입된 브라우저 엔진의 보안 조치(타이머 정밀도 하향, 분기 없는 보안 검사 추가 등)가 그래픽스 파이프라인의 전반적인 미세 지연을 증가시킨다는 사실은 설명되어 있으나 [8], 루트 주제에서 명시한 '브라우저 메모리 할당 시점별' 미세 지연의 변화를 직접적으로 측정한 구체적인 실험 사례나 수치에 대해서는 소스에 관련 정보가 부족합니다. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Spectre and Meltdown.md]] +- Raw Source: 00_Raw/2026-04-20/Spectre and Meltdown.md --- diff --git a/01_Archive/2026-04-20/Spectre.md b/01_Archive/2026-04-20/Spectre.md index a77849fc..df503e1f 100644 --- a/01_Archive/2026-04-20/Spectre.md +++ b/01_Archive/2026-04-20/Spectre.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-6C2AC3 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Spectre" --- -# [[Spectre]] +# [[Spectre|Spectre]] ## 📌 한 줄 통찰 (The Karpathy Summary) > Spectre는 최신 프로세서에 공통적으로 존재하는 보안 취약점으로, CPU의 **추측 실행(Speculative Execution)과 분기 예측(Branch Prediction)을 악용하여 비밀 메모리 영역에 대한 읽기 권한을 탈취**하는 공격입니다 [1-3]. 웹 브라우저 환경에서는 신뢰할 수 없는 JavaScript 등의 코드가 고해상도 타이머를 이용해 캐시 지연 시간을 측정하는 방식(타이밍 공격)으로 시스템 메모리를 유출할 수 있는 치명적인 위험을 초래했습니다 [4-6]. @@ -23,11 +23,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Spectre" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Speculative Execution]], [[Branch Prediction]], [[Meltdown]], [[Timing Attacks]], [[Branchless Security Checks]] -- **Projects/Contexts:** [[WebKit]], [[JavaScriptCore]], [[WebGL]], [[WebGPU]] +- **Related Topics:** [[Speculative Execution|Speculative Execution]], [[Branch Prediction|Branch Prediction]], [[Meltdown|Meltdown]], [[Timing Attacks|Timing Attacks]], [[Branchless Security Checks|Branchless Security Checks]] +- **Projects/Contexts:** [[WebKit|WebKit]], [[JavaScriptCore|JavaScriptCore]], [[WebGL|WebGL]], [[WebGPU|WebGPU]] - **Contradictions/Notes:** 그래픽스 및 성능 최적화 개발자들은 마이크로 레이턴시 측정을 위해 WebGPU/WebGL 환경에서 나노초 단위의 정밀한 타이머를 필요로 하지만, 브라우저 벤더들은 Spectre와 같은 사이드 채널 공격을 방지하기 위해 이 타이머의 정밀도를 의도적으로 제한해야 하는 보안과 성능 분석 기능 간의 상충 관계(Trade-off)가 발생합니다 [12-14, 19]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Spectre.md]] +- Raw Source: 00_Raw/2026-04-20/Spectre.md --- diff --git a/01_Archive/2026-04-20/Speculative Biology.md b/01_Archive/2026-04-20/Speculative Biology.md index e1ce2dab..cd4d6790 100644 --- a/01_Archive/2026-04-20/Speculative Biology.md +++ b/01_Archive/2026-04-20/Speculative Biology.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-FF5504 -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Speculative Biology" --- -# [[Speculative Biology]] +# [[Speculative Biology|Speculative Biology]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Speculative Biology" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Speculative Biology.md]] +- Raw Source: 00_Raw/2026-04-20/Speculative Biology.md --- diff --git a/01_Archive/2026-04-20/Speculative Execution.md b/01_Archive/2026-04-20/Speculative Execution.md index b7cf853f..68242de1 100644 --- a/01_Archive/2026-04-20/Speculative Execution.md +++ b/01_Archive/2026-04-20/Speculative Execution.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-CCED4D -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Speculative Execution" --- -# [[Speculative Execution]] +# [[Speculative Execution|Speculative Execution]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 추측 실행(Speculative Execution)은 현대 CPU가 성능 최적화를 위해 분기(branch)의 실제 결과가 확인되기 전에 미리 명령어를 실행하는 기법입니다 [1]. 예측이 틀린 것으로 판명될 경우 CPU는 실행을 롤백(roll back)하여 변경 사항을 취소할 수 있습니다 [1]. 하지만 이 과정에서 L1 캐시로 미리 가져온 데이터는 롤백 시 취소되지 않으며, 이러한 구조적 특성은 타이밍 기반의 정보 유출을 유발하여 **Spectre**와 같은 보안 취약점 공격에 악용될 수 있습니다 [1, 2]. @@ -23,11 +23,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Speculative Execution" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Spectre]], [[Meltdown]], [[Branch Prediction]], [[L1 Cache]] -- **Projects/Contexts:** [[WebKit]], [[JavaScriptCore]] +- **Related Topics:** [[Spectre|Spectre]], [[Meltdown|Meltdown]], [[Branch Prediction|Branch Prediction]], L1 Cache +- **Projects/Contexts:** [[WebKit|WebKit]], [[JavaScriptCore|JavaScriptCore]] - **Contradictions/Notes:** 소스 내에서 상충되는 주장은 발견되지 않았습니다. 다만, 이와 관련하여 WebKit 프로젝트는 추측 실행을 악용한 공격을 방어하기 위해 타이머(performance.now 등)의 정밀도를 낮추고, 분기 명령어에 의존하지 않는 보안 검사(branchless security checks) 및 포인터 포이즈닝(pointer poisoning)을 도입하는 방식으로 대응하고 있습니다 [7-9]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Speculative Execution.md]] +- Raw Source: 00_Raw/2026-04-20/Speculative Execution.md --- diff --git a/01_Archive/2026-04-20/Sports Management Theory.md b/01_Archive/2026-04-20/Sports Management Theory.md index 8548cc68..43f1a077 100644 --- a/01_Archive/2026-04-20/Sports Management Theory.md +++ b/01_Archive/2026-04-20/Sports Management Theory.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-B81B6E -category: "[[10_Wiki/💡 Topics/Software Architecture]]" +category: "10_Wiki/💡 Topics/Software Architecture" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Sports Management Theory" --- -# [[Sports Management Theory]] +# [[Sports Management Theory|Sports Management Theory]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Sports Management Theory" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Sports Management Theory.md]] +- Raw Source: 00_Raw/2026-04-20/Sports Management Theory.md --- diff --git a/01_Archive/2026-04-20/Sports Neuroscience.md b/01_Archive/2026-04-20/Sports Neuroscience.md index 06440731..a606a85f 100644 --- a/01_Archive/2026-04-20/Sports Neuroscience.md +++ b/01_Archive/2026-04-20/Sports Neuroscience.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-80CF35 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Sports Neuroscience" --- -# [[Sports Neuroscience]] +# [[Sports Neuroscience|Sports Neuroscience]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Sports Neuroscience" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Sports Neuroscience.md]] +- Raw Source: 00_Raw/2026-04-20/Sports Neuroscience.md --- diff --git a/01_Archive/2026-04-20/Sports-Medicine-Rehabilitation.md b/01_Archive/2026-04-20/Sports-Medicine-Rehabilitation.md index fcd57b04..54c3389e 100644 --- a/01_Archive/2026-04-20/Sports-Medicine-Rehabilitation.md +++ b/01_Archive/2026-04-20/Sports-Medicine-Rehabilitation.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-727225 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Sports-Medicine-Rehabilitation" --- -# [[Sports-Medicine-Rehabilitation]] +# [[Sports-Medicine-Rehabilitation|Sports-Medicine-Rehabilitation]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Sports-Medicine-Rehabilitation ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Sports-Medicine-Rehabilitation.md]] +- Raw Source: 00_Raw/2026-04-20/Sports-Medicine-Rehabilitation.md --- diff --git a/01_Archive/2026-04-20/Sports-Performance-Optimization.md b/01_Archive/2026-04-20/Sports-Performance-Optimization.md index 0a82981e..5f9031f1 100644 --- a/01_Archive/2026-04-20/Sports-Performance-Optimization.md +++ b/01_Archive/2026-04-20/Sports-Performance-Optimization.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-FEEFC9 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Sports-Performance-Optimization" --- -# [[Sports-Performance-Optimization]] +# [[Sports-Performance-Optimization|Sports-Performance-Optimization]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Sports-Performance-Optimizatio ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Sports-Performance-Optimization.md]] +- Raw Source: 00_Raw/2026-04-20/Sports-Performance-Optimization.md --- diff --git a/01_Archive/2026-04-20/Sports-Psychology.md b/01_Archive/2026-04-20/Sports-Psychology.md index 460ce457..60d8a52a 100644 --- a/01_Archive/2026-04-20/Sports-Psychology.md +++ b/01_Archive/2026-04-20/Sports-Psychology.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-D4C5E8 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Sports-Psychology" --- -# [[Sports-Psychology]] +# [[Sports-Psychology|Sports-Psychology]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Sports-Psychology" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Sports-Psychology.md]] +- Raw Source: 00_Raw/2026-04-20/Sports-Psychology.md --- diff --git a/01_Archive/2026-04-20/Sports-Science-Training.md b/01_Archive/2026-04-20/Sports-Science-Training.md index 038b4bb7..2b977217 100644 --- a/01_Archive/2026-04-20/Sports-Science-Training.md +++ b/01_Archive/2026-04-20/Sports-Science-Training.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-9A7390 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Sports-Science-Training" --- -# [[Sports-Science-Training]] +# [[Sports-Science-Training|Sports-Science-Training]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Sports-Science-Training" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Sports-Science-Training.md]] +- Raw Source: 00_Raw/2026-04-20/Sports-Science-Training.md --- diff --git a/01_Archive/2026-04-20/Sprague-Grundy Theorem.md b/01_Archive/2026-04-20/Sprague-Grundy Theorem.md index 6a305e3b..beb7228d 100644 --- a/01_Archive/2026-04-20/Sprague-Grundy Theorem.md +++ b/01_Archive/2026-04-20/Sprague-Grundy Theorem.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-3D42A2 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Sprague-Grundy Theorem" --- -# [[Sprague-Grundy Theorem]] +# [[Sprague-Grundy Theorem|Sprague-Grundy Theorem]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Sprague-Grundy Theorem" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Sprague-Grundy Theorem.md]] +- Raw Source: 00_Raw/2026-04-20/Sprague-Grundy Theorem.md --- diff --git a/01_Archive/2026-04-20/Spring Framework.md b/01_Archive/2026-04-20/Spring Framework.md index c27ab742..f30a8049 100644 --- a/01_Archive/2026-04-20/Spring Framework.md +++ b/01_Archive/2026-04-20/Spring Framework.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-C45BD6 -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Spring Framework" --- -# [[Spring Framework]] +# [[Spring Framework|Spring Framework]] ## 📌 한 줄 통찰 (The Karpathy Summary) > Spring Framework는 자바(Java) 환경에서 사용되는 프레임워크로, 주로 내장된 DI(의존성 주입) 컨테이너를 통해 컴포넌트 간의 결합도를 낮추는 역할을 합니다 [1]. 또한 런타임 시점에 적용되는 Spring AOP를 지원하여 트랜잭션 관리 및 캐시 처리와 같은 횡단 관심사의 모듈화를 돕습니다 [2, 3]. 다만 제공된 문헌에는 Spring Framework의 전반적인 아키텍처나 생태계 전반을 다루는 내용이 없어, 소스에 관련 정보가 부족합니다. @@ -28,11 +28,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Spring Framework" - **정책 변화:** Graphics & Performance 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Dependency Injection (DI)]], [[Aspect-Oriented Programming (AOP)]] -- **Projects/Contexts:** [[SOLID Principles]], [[객체 지향 프로그래밍 (OOP)]] +- **Related Topics:** [[Dependency Injection (DI)|Dependency Injection (DI)]], Aspect-Oriented Programming (AOP) +- **Projects/Contexts:** [[SOLID Principles|SOLID Principles]], [[객체 지향 프로그래밍 (OOP)|객체 지향 프로그래밍 (OOP)]] - **Contradictions/Notes:** 소스에 따르면 Spring AOP는 런타임에 적용되어 유용한 모듈화를 제공하지만, 오직 메서드 실행 시점의 조인 포인트만 지원하는 한계가 있어 더 정밀한 제어를 원할 경우 AspectJ 사용이 권장됩니다 [4, 5]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/Spring Framework.md]] +- Raw Source: 00_Raw/2026-04-20/Spring Framework.md --- diff --git a/01_Archive/2026-04-20/State-Machine-Implementation.md b/01_Archive/2026-04-20/State-Machine-Implementation.md index 224da0ad..317c7b95 100644 --- a/01_Archive/2026-04-20/State-Machine-Implementation.md +++ b/01_Archive/2026-04-20/State-Machine-Implementation.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-CB6F5B -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - State-Machine-Implementation" --- -# [[State-Machine-Implementation]] +# [[State-Machine-Implementation|State-Machine-Implementation]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - State-Machine-Implementation" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/State-Machine-Implementation.md]] +- Raw Source: 00_Raw/2026-04-20/State-Machine-Implementation.md --- diff --git a/01_Archive/2026-04-20/Static Application Security Testing (SAST).md b/01_Archive/2026-04-20/Static Application Security Testing (SAST).md index 58bbf095..4c59bb33 100644 --- a/01_Archive/2026-04-20/Static Application Security Testing (SAST).md +++ b/01_Archive/2026-04-20/Static Application Security Testing (SAST).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-95EC02 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Static Application Security Testing (SAST)" --- -# [[Static Application Security Testing (SAST)]] +# [[Static Application Security Testing (SAST)|Static Application Security Testing (SAST)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > Static Application Security Testing(SAST)는 애플리케이션을 직접 실행하지 않고 소스 코드나 바이트코드를 분석하여 잠재적인 보안 취약점과 결함을 찾아내는 화이트박스 테스트(white-box testing) 기법입니다 [1, 2]. 이 방식은 소프트웨어 개발 수명 주기(SDLC)의 초기 단계에 적용되어 코드가 배포되기 전에 문제를 식별하고 수정할 수 있게 해줍니다 [1, 3, 4]. 최근에는 인공지능(AI)과 기계 학습(ML) 기술이 결합되어 전통적인 규칙 기반 탐지의 한계를 넘어 코드의 문맥을 이해하고, 자동으로 수정 코드를 제안하는 수준으로 진화하고 있습니다 [5-7]. @@ -24,11 +24,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Static Application Security Te - **정책 변화:** AI 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Dynamic Application Security Testing (DAST)]], [[Software Composition Analysis (SCA)]], [[Shift-Left]], [[False Positives]], [[Artificial Intelligence (AI) Code Review]] -- **Projects/Contexts:** 소프트웨어 개발 수명 주기(SDLC) 내에서 보안을 강화하기 위해 CI/CD 파이프라인, IDE 플러그인, Pull Request 등에 연동하여 사용되는 맥락을 가집니다. 대표적인 도구로는 [[Snyk Code]], [[Corgea]], [[SonarQube]], [[Checkmarx]], [[Semgrep]], [[Veracode]], [[GitHub Advanced Security]] 등이 널리 사용되고 있습니다 [7, 18, 22, 27, 34-38]. +- **Related Topics:** Dynamic Application Security Testing (DAST), [[Software Composition Analysis (SCA)|Software Composition Analysis (SCA)]], [[시프트 레프트 (Shift-Left)|Shift-Left]], False Positives, Artificial Intelligence (AI) Code Review +- **Projects/Contexts:** 소프트웨어 개발 수명 주기(SDLC) 내에서 보안을 강화하기 위해 CI/CD 파이프라인, IDE 플러그인, Pull Request 등에 연동하여 사용되는 맥락을 가집니다. 대표적인 도구로는 Snyk Code, [[Corgea|Corgea]], [[SonarQube|SonarQube]], Checkmarx, Semgrep, Veracode, GitHub Advanced Security 등이 널리 사용되고 있습니다 [7, 18, 22, 27, 34-38]. - **Contradictions/Notes:** 전통적인 정적 분석(SAST)은 빠르고 일관된 검사를 제공하지만, 비즈니스 로직에 대한 문맥 이해 부족과 높은 오탐률(False Positives)이라는 한계가 지적됩니다 [23, 24]. 이를 해결하기 위해 최근에는 사람이 판단을 내리는 수동 코드 리뷰(Manual Code Review)와 AI가 결합된 정적 분석을 혼합하여 사용하는 하이브리드(Hybrid) 접근 방식이 필수적인 보안 검토의 모범 사례로 권장되고 있습니다 [39-41]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Static Application Security Testing (SAST).md]] +- Raw Source: 00_Raw/2026-04-20/Static Application Security Testing (SAST).md --- diff --git a/01_Archive/2026-04-20/Static Type Checking Systems.md b/01_Archive/2026-04-20/Static Type Checking Systems.md index b69a0ea6..96bb9b16 100644 --- a/01_Archive/2026-04-20/Static Type Checking Systems.md +++ b/01_Archive/2026-04-20/Static Type Checking Systems.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-AB0264 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Static Type Checking Systems" --- -# [[Static Type Checking Systems]] +# [[Static Type Checking Systems|Static Type Checking Systems]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Static Type Checking Systems" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Static Type Checking Systems.md]] +- Raw Source: 00_Raw/2026-04-20/Static Type Checking Systems.md --- diff --git a/01_Archive/2026-04-20/Static-Analysis-in-JavaScript-Ecosystem.md b/01_Archive/2026-04-20/Static-Analysis-in-JavaScript-Ecosystem.md index 02e33980..e51317c6 100644 --- a/01_Archive/2026-04-20/Static-Analysis-in-JavaScript-Ecosystem.md +++ b/01_Archive/2026-04-20/Static-Analysis-in-JavaScript-Ecosystem.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-6BE2FD -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Static-Analysis-in-JavaScript-Ecosystem" --- -# [[Static-Analysis-in-JavaScript-Ecosystem]] +# [[Static-Analysis-in-JavaScript-Ecosystem|Static-Analysis-in-JavaScript-Ecosystem]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Static-Analysis-in-JavaScript- ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Static-Analysis-in-JavaScript-Ecosystem.md]] +- Raw Source: 00_Raw/2026-04-20/Static-Analysis-in-JavaScript-Ecosystem.md --- diff --git a/01_Archive/2026-04-20/Static-Analysis-in-JavaScript.md b/01_Archive/2026-04-20/Static-Analysis-in-JavaScript.md index 1026c06c..f80c5739 100644 --- a/01_Archive/2026-04-20/Static-Analysis-in-JavaScript.md +++ b/01_Archive/2026-04-20/Static-Analysis-in-JavaScript.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-AC87D9 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Static-Analysis-in-JavaScript" --- -# [[Static-Analysis-in-JavaScript]] +# [[Static-Analysis-in-JavaScript|Static-Analysis-in-JavaScript]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Static-Analysis-in-JavaScript" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Static-Analysis-in-JavaScript.md]] +- Raw Source: 00_Raw/2026-04-20/Static-Analysis-in-JavaScript.md --- diff --git a/01_Archive/2026-04-20/Static-Analysis-in-Software-Engineering.md b/01_Archive/2026-04-20/Static-Analysis-in-Software-Engineering.md index af2bb74a..6a4a2f02 100644 --- a/01_Archive/2026-04-20/Static-Analysis-in-Software-Engineering.md +++ b/01_Archive/2026-04-20/Static-Analysis-in-Software-Engineering.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-97FE65 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Static-Analysis-in-Software-Engineering" --- -# [[Static-Analysis-in-Software-Engineering]] +# [[Static-Analysis-in-Software-Engineering|Static-Analysis-in-Software-Engineering]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Static-Analysis-in-Software-En ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Static-Analysis-in-Software-Engineering.md]] +- Raw Source: 00_Raw/2026-04-20/Static-Analysis-in-Software-Engineering.md --- diff --git a/01_Archive/2026-04-20/Static-Analysis-of-Interfaces.md b/01_Archive/2026-04-20/Static-Analysis-of-Interfaces.md index b0e98dd7..e8ae4d72 100644 --- a/01_Archive/2026-04-20/Static-Analysis-of-Interfaces.md +++ b/01_Archive/2026-04-20/Static-Analysis-of-Interfaces.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-FCF0B0 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Static-Analysis-of-Interfaces" --- -# [[Static-Analysis-of-Interfaces]] +# [[Static-Analysis-of-Interfaces|Static-Analysis-of-Interfaces]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Static-Analysis-of-Interfaces" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Static-Analysis-of-Interfaces.md]] +- Raw Source: 00_Raw/2026-04-20/Static-Analysis-of-Interfaces.md --- diff --git a/01_Archive/2026-04-20/Static-Program-Analysis.md b/01_Archive/2026-04-20/Static-Program-Analysis.md index 17f1e86e..f0a8b177 100644 --- a/01_Archive/2026-04-20/Static-Program-Analysis.md +++ b/01_Archive/2026-04-20/Static-Program-Analysis.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-295D6F -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Static-Program-Analysis" --- -# [[Static-Program-Analysis]] +# [[Static-Program-Analysis|Static-Program-Analysis]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Static-Program-Analysis" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Static-Program-Analysis.md]] +- Raw Source: 00_Raw/2026-04-20/Static-Program-Analysis.md --- diff --git a/01_Archive/2026-04-20/Static-Type-Inference.md b/01_Archive/2026-04-20/Static-Type-Inference.md index 86507eca..5263d183 100644 --- a/01_Archive/2026-04-20/Static-Type-Inference.md +++ b/01_Archive/2026-04-20/Static-Type-Inference.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-262D9E -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Static-Type-Inference" --- -# [[Static-Type-Inference]] +# [[Static-Type-Inference|Static-Type-Inference]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Static-Type-Inference" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Static-Type-Inference.md]] +- Raw Source: 00_Raw/2026-04-20/Static-Type-Inference.md --- diff --git a/01_Archive/2026-04-20/Statistical Mechanics.md b/01_Archive/2026-04-20/Statistical Mechanics.md index 270071cc..242d412a 100644 --- a/01_Archive/2026-04-20/Statistical Mechanics.md +++ b/01_Archive/2026-04-20/Statistical Mechanics.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-9E33B1 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Statistical Mechanics" --- -# [[Statistical Mechanics]] +# [[Statistical Mechanics|Statistical Mechanics]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Statistical Mechanics" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Statistical Mechanics.md]] +- Raw Source: 00_Raw/2026-04-20/Statistical Mechanics.md --- diff --git a/01_Archive/2026-04-20/Stochastic Processes.md b/01_Archive/2026-04-20/Stochastic Processes.md index 52d69fb0..3e36e0e0 100644 --- a/01_Archive/2026-04-20/Stochastic Processes.md +++ b/01_Archive/2026-04-20/Stochastic Processes.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-71E76D -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Stochastic Processes" --- -# [[Stochastic Processes]] +# [[Stochastic Processes|Stochastic Processes]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Stochastic Processes" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Stochastic Processes.md]] +- Raw Source: 00_Raw/2026-04-20/Stochastic Processes.md --- diff --git a/01_Archive/2026-04-20/Stochastic-Games.md b/01_Archive/2026-04-20/Stochastic-Games.md index 3817d518..4f94f86c 100644 --- a/01_Archive/2026-04-20/Stochastic-Games.md +++ b/01_Archive/2026-04-20/Stochastic-Games.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-4892A4 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Stochastic-Games" --- -# [[Stochastic-Games]] +# [[Stochastic-Games|Stochastic-Games]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Stochastic-Games" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Stochastic-Games.md]] +- Raw Source: 00_Raw/2026-04-20/Stochastic-Games.md --- diff --git a/01_Archive/2026-04-20/Stop-the-world.md b/01_Archive/2026-04-20/Stop-the-world.md index 5698d1a9..4357bad7 100644 --- a/01_Archive/2026-04-20/Stop-the-world.md +++ b/01_Archive/2026-04-20/Stop-the-world.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-D2D9B2 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Stop-the-world" --- -# [[Stop-the-world]] +# [[Stop-the-world|Stop-the-world]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 'Stop-the-world'(STW)는 가비지 컬렉션(GC)이 실행되는 동안 메모리를 정리하기 위해 애플리케이션의 실행이 일시적으로 완전히 중단되는 현상을 의미합니다 [1, 2]. 가비지 컬렉터가 힙(Heap) 메모리에 대한 배타적 접근 권한을 얻어야 하므로 애플리케이션 스레드가 멈추게 됩니다 [1, 3]. 이로 인해 발생하는 지연(Latency)과 화면 끊김(Jank)을 줄이기 위해 현대의 GC 알고리즘들은 STW 시간을 최소화하거나 회피하는 병렬 및 동시 처리 방식으로 발전하고 있습니다 [2, 4, 5]. @@ -33,11 +33,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Stop-the-world" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Garbage Collection]], [[Heap Memory]], [[Orinoco]], [[Mark-Sweep]] -- **Projects/Contexts:** [[V8 JavaScript Engine]], [[IBM Java Virtual Machine (VM)]] +- **Related Topics:** [[Garbage Collection|Garbage Collection]], [[힙 메모리(Heap Memory)|Heap Memory]], [[Orinoco|Orinoco]], [[Mark-Sweep|Mark-Sweep]] +- **Projects/Contexts:** [[V8 JavaScript Engine|V8 JavaScript Engine]], IBM Java Virtual Machine (VM) - **Contradictions/Notes:** 제공된 소스들 사이에서 내용 상의 모순은 없으며, V8 엔진과 IBM JVM 환경 모두에서 가비지 컬렉션 중 발생하는 'Stop-the-world'의 기본 개념과 이를 최적화(병렬, 동시, 점진적 처리)하여 일시 정지 시간을 줄이려는 공통된 발전 방향을 보여줍니다 [3-5, 8]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Stop-the-world.md]] +- Raw Source: 00_Raw/2026-04-20/Stop-the-world.md --- diff --git a/01_Archive/2026-04-20/Structural Type System.md b/01_Archive/2026-04-20/Structural Type System.md index 635221a0..36a9f4d6 100644 --- a/01_Archive/2026-04-20/Structural Type System.md +++ b/01_Archive/2026-04-20/Structural Type System.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-8CDABA -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Structural Type System" --- -# [[Structural Type System]] +# [[Structural Type System|Structural Type System]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Structural Type System" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Structural Type System.md]] +- Raw Source: 00_Raw/2026-04-20/Structural Type System.md --- diff --git a/01_Archive/2026-04-20/Structural Typing.md b/01_Archive/2026-04-20/Structural Typing.md index a7e56030..f847b8a2 100644 --- a/01_Archive/2026-04-20/Structural Typing.md +++ b/01_Archive/2026-04-20/Structural Typing.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-8C150A -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Structural Typing" --- -# [[Structural Typing]] +# [[Structural Typing|Structural Typing]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 구조적 타이핑(Structural Typing)은 명시적인 타입 선언이나 이름이 아닌, 객체가 가진 실제 형태와 구조(속성 및 메서드)를 기준으로 타입 호환성을 결정하는 시스템이다[1, 2]. "오리처럼 걷고 갉갉거리면 오리다"라는 '덕 타이핑(Duck Typing)' 원리와 동일한 맥락을 가지며, 대상 타입이 요구하는 최소한의 멤버(속성)를 모두 포함하고 있다면 호환되는 것으로 간주한다[2, 3]. 이는 타입의 이름이 일치해야만 호환성을 인정하는 명목적 타이핑(Nominal Typing)과 대비되는 TypeScript의 핵심 설계 철학이다[2]. @@ -33,11 +33,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Structural Typing" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Duck Typing]], [[Nominal Typing]], [[Excess Property Checking]], [[Branded Types]], [[satisfies Operator]] -- **Projects/Contexts:** [[TypeScript Type System]] +- **Related Topics:** [[Duck-Typing|Duck Typing]], [[Nominal Typing|Nominal Typing]], [[Excess Property Checking|Excess Property Checking]], [[Branded Types|Branded Types]], [[Satisfies Operator|satisfies Operator]] +- **Projects/Contexts:** [[TypeScript-Type-System|TypeScript Type System]] - **Contradictions/Notes:** 구조적 타이핑은 기본적으로 대상 객체가 추가적인 속성을 가지는 것을 허용하여 유연한 호환성을 부여하지만[4], 객체 리터럴을 직접 할당할 때는 이러한 유연성 대신 '초과 속성 검사(Excess Property Checking)'가 개입하여 선언되지 않은 속성의 존재를 엄격하게 에러로 처리한다는 상반된 동작 규칙이 공존한다[6, 11, 12]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/Structural Typing.md]] +- Raw Source: 00_Raw/2026-04-20/Structural Typing.md --- diff --git a/01_Archive/2026-04-20/Structural-Subtyping.md b/01_Archive/2026-04-20/Structural-Subtyping.md index bfd8b65c..8789b75b 100644 --- a/01_Archive/2026-04-20/Structural-Subtyping.md +++ b/01_Archive/2026-04-20/Structural-Subtyping.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-ED919D -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Structural-Subtyping" --- -# [[Structural-Subtyping]] +# [[Structural-Subtyping|Structural-Subtyping]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Structural-Subtyping" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Structural-Subtyping.md]] +- Raw Source: 00_Raw/2026-04-20/Structural-Subtyping.md --- diff --git a/01_Archive/2026-04-20/Structural-Type-System.md b/01_Archive/2026-04-20/Structural-Type-System.md index 2bb3304f..a414ba26 100644 --- a/01_Archive/2026-04-20/Structural-Type-System.md +++ b/01_Archive/2026-04-20/Structural-Type-System.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-51BF6C -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Structural-Type-System" --- -# [[Structural-Type-System]] +# [[Structural-Type-System|Structural-Type-System]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Structural-Type-System" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Structural-Type-System.md]] +- Raw Source: 00_Raw/2026-04-20/Structural-Type-System.md --- diff --git a/01_Archive/2026-04-20/Structural-Typing-Analysis.md b/01_Archive/2026-04-20/Structural-Typing-Analysis.md index 9b1c80cd..dffdaabd 100644 --- a/01_Archive/2026-04-20/Structural-Typing-Analysis.md +++ b/01_Archive/2026-04-20/Structural-Typing-Analysis.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-7B4F4E -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Structural-Typing-Analysis" --- -# [[Structural-Typing-Analysis]] +# [[Structural-Typing-Analysis|Structural-Typing-Analysis]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Structural-Typing-Analysis" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Structural-Typing-Analysis.md]] +- Raw Source: 00_Raw/2026-04-20/Structural-Typing-Analysis.md --- diff --git a/01_Archive/2026-04-20/Structural-Typing-Compatibility.md b/01_Archive/2026-04-20/Structural-Typing-Compatibility.md index 484f5a11..7c917625 100644 --- a/01_Archive/2026-04-20/Structural-Typing-Compatibility.md +++ b/01_Archive/2026-04-20/Structural-Typing-Compatibility.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-61CE6C -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Structural-Typing-Compatibility" --- -# [[Structural-Typing-Compatibility]] +# [[Structural-Typing-Compatibility|Structural-Typing-Compatibility]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Structural-Typing-Compatibilit ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Structural-Typing-Compatibility.md]] +- Raw Source: 00_Raw/2026-04-20/Structural-Typing-Compatibility.md --- diff --git a/01_Archive/2026-04-20/Structural-Typing-Mechanics.md b/01_Archive/2026-04-20/Structural-Typing-Mechanics.md index 7942f8ae..c6c512d1 100644 --- a/01_Archive/2026-04-20/Structural-Typing-Mechanics.md +++ b/01_Archive/2026-04-20/Structural-Typing-Mechanics.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-472330 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Structural-Typing-Mechanics" --- -# [[Structural-Typing-Mechanics]] +# [[Structural-Typing-Mechanics|Structural-Typing-Mechanics]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Structural-Typing-Mechanics" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Structural-Typing-Mechanics.md]] +- Raw Source: 00_Raw/2026-04-20/Structural-Typing-Mechanics.md --- diff --git a/01_Archive/2026-04-20/Structural-Typing-Mechanisms.md b/01_Archive/2026-04-20/Structural-Typing-Mechanisms.md index e6b0eddb..ead064b4 100644 --- a/01_Archive/2026-04-20/Structural-Typing-Mechanisms.md +++ b/01_Archive/2026-04-20/Structural-Typing-Mechanisms.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-88EAEF -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Structural-Typing-Mechanisms" --- -# [[Structural-Typing-Mechanisms]] +# [[Structural-Typing-Mechanisms|Structural-Typing-Mechanisms]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Structural-Typing-Mechanisms" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Structural-Typing-Mechanisms.md]] +- Raw Source: 00_Raw/2026-04-20/Structural-Typing-Mechanisms.md --- diff --git a/01_Archive/2026-04-20/Structural-Typing-System.md b/01_Archive/2026-04-20/Structural-Typing-System.md index 5c6454ec..8a3d83ef 100644 --- a/01_Archive/2026-04-20/Structural-Typing-System.md +++ b/01_Archive/2026-04-20/Structural-Typing-System.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-CB5A39 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Structural-Typing-System" --- -# [[Structural-Typing-System]] +# [[Structural-Typing-System|Structural-Typing-System]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Structural-Typing-System" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Structural-Typing-System.md]] +- Raw Source: 00_Raw/2026-04-20/Structural-Typing-System.md --- diff --git a/01_Archive/2026-04-20/Structural-Typing-and-Compatibility.md b/01_Archive/2026-04-20/Structural-Typing-and-Compatibility.md index 76ee5c69..78227d3f 100644 --- a/01_Archive/2026-04-20/Structural-Typing-and-Compatibility.md +++ b/01_Archive/2026-04-20/Structural-Typing-and-Compatibility.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-8A9CF7 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Structural-Typing-and-Compatibility" --- -# [[Structural-Typing-and-Compatibility]] +# [[Structural-Typing-and-Compatibility|Structural-Typing-and-Compatibility]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Structural-Typing-and-Compatib ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Structural-Typing-and-Compatibility.md]] +- Raw Source: 00_Raw/2026-04-20/Structural-Typing-and-Compatibility.md --- diff --git a/01_Archive/2026-04-20/Structural-Typing-vs-Nominal-Typing.md b/01_Archive/2026-04-20/Structural-Typing-vs-Nominal-Typing.md index e972cea5..a5de4392 100644 --- a/01_Archive/2026-04-20/Structural-Typing-vs-Nominal-Typing.md +++ b/01_Archive/2026-04-20/Structural-Typing-vs-Nominal-Typing.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-AA252C -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Structural-Typing-vs-Nominal-Typing" --- -# [[Structural-Typing-vs-Nominal-Typing]] +# [[Structural-Typing-vs-Nominal-Typing|Structural-Typing-vs-Nominal-Typing]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Structural-Typing-vs-Nominal-T ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Structural-Typing-vs-Nominal-Typing.md]] +- Raw Source: 00_Raw/2026-04-20/Structural-Typing-vs-Nominal-Typing.md --- diff --git a/01_Archive/2026-04-20/Structural-Typing.md b/01_Archive/2026-04-20/Structural-Typing.md index 4d9e9cf6..f7720827 100644 --- a/01_Archive/2026-04-20/Structural-Typing.md +++ b/01_Archive/2026-04-20/Structural-Typing.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-65A250 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Structural-Typing" --- -# [[Structural-Typing]] +# [[Structural-Typing|Structural-Typing]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Structural-Typing" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Structural-Typing.md]] +- Raw Source: 00_Raw/2026-04-20/Structural-Typing.md --- diff --git a/01_Archive/2026-04-20/Structural-vs-Nominal-Typing-in-TS.md b/01_Archive/2026-04-20/Structural-vs-Nominal-Typing-in-TS.md index 77f71efc..9b4e23bf 100644 --- a/01_Archive/2026-04-20/Structural-vs-Nominal-Typing-in-TS.md +++ b/01_Archive/2026-04-20/Structural-vs-Nominal-Typing-in-TS.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-1623C6 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Structural-vs-Nominal-Typing-in-TS" --- -# [[Structural-vs-Nominal-Typing-in-TS]] +# [[Structural-vs-Nominal-Typing-in-TS|Structural-vs-Nominal-Typing-in-TS]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Structural-vs-Nominal-Typing-i ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Structural-vs-Nominal-Typing-in-TS.md]] +- Raw Source: 00_Raw/2026-04-20/Structural-vs-Nominal-Typing-in-TS.md --- diff --git a/01_Archive/2026-04-20/Structural-vs-Nominal-Typing.md b/01_Archive/2026-04-20/Structural-vs-Nominal-Typing.md index e551e47b..97029094 100644 --- a/01_Archive/2026-04-20/Structural-vs-Nominal-Typing.md +++ b/01_Archive/2026-04-20/Structural-vs-Nominal-Typing.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-AD6E98 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Structural-vs-Nominal-Typing" --- -# [[Structural-vs-Nominal-Typing]] +# [[Structural-vs-Nominal-Typing|Structural-vs-Nominal-Typing]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Structural-vs-Nominal-Typing" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Structural-vs-Nominal-Typing.md]] +- Raw Source: 00_Raw/2026-04-20/Structural-vs-Nominal-Typing.md --- diff --git a/01_Archive/2026-04-20/Structuralism.md b/01_Archive/2026-04-20/Structuralism.md index f2492510..135b2f8c 100644 --- a/01_Archive/2026-04-20/Structuralism.md +++ b/01_Archive/2026-04-20/Structuralism.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-569BE2 -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Structuralism" --- -# [[Structuralism]] +# [[Structuralism|Structuralism]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Structuralism" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Structuralism.md]] +- Raw Source: 00_Raw/2026-04-20/Structuralism.md --- diff --git a/01_Archive/2026-04-20/StyleCounsel.md b/01_Archive/2026-04-20/StyleCounsel.md index e9f5f28e..1b263522 100644 --- a/01_Archive/2026-04-20/StyleCounsel.md +++ b/01_Archive/2026-04-20/StyleCounsel.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-761709 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - StyleCounsel" --- -# [[StyleCounsel]] +# [[StyleCounsel|StyleCounsel]] ## 📌 한 줄 통찰 (The Karpathy Summary) > StyleCounsel은 프로그래머가 자신의 고유한 코딩 스타일을 난독화(obfuscate)하고 다른 특정 프로그래머의 스타일을 모방(mimic)할 수 있도록 지원하여 신원을 보호하는 프라이버시 강화 도구입니다. 대중적인 오픈소스 IDE인 Eclipse의 플러그인 형태로 개발되었으며, Weka 머신러닝 시스템의 랜덤 포레스트(Random Forest) 알고리즘을 내장하고 있습니다. 이 도구는 사용자의 코드를 평가한 후, 타겟 작성자로 오분류를 유도하기 위해 어떤 부분을 수정해야 하는지 구체적인 변경 사항을 조언(counsel)하는 'Human-in-the-loop' 방식으로 동작합니다. @@ -29,11 +29,11 @@ github_commit: "[P-Reinforce] Continuous Worker - StyleCounsel" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Code Stylometry]], [[Authorship Attribution]], [[Random Forest]], [[Adversarial Imitation]] -- **Projects/Contexts:** [[Eclipse IDE]], [[Weka Machine Learning]] +- **Related Topics:** [[Code Stylometry (코드 문체론)|Code Stylometry]], [[Authorship Attribution|Authorship Attribution]], Random Forest, Adversarial Imitation +- **Projects/Contexts:** Eclipse IDE, Weka Machine Learning - **Contradictions/Notes:** 사용자 연구에 따르면, StyleCounsel의 지속적이고 자동화된 피드백은 수동으로 코드를 분석하는 시간을 획기적으로 줄여준다는 긍정적인 평가를 받았습니다. 반면, 추천된 변경 사항 중 일부는 가독성 유지나 기능적 결함 발생을 우려하게 만들어 실제 코드에 적용하기 까다롭다는 점이 상충하는 한계로 지적되었습니다. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/StyleCounsel.md]] +- Raw Source: 00_Raw/2026-04-20/StyleCounsel.md --- diff --git a/01_Archive/2026-04-20/Submodules.md b/01_Archive/2026-04-20/Submodules.md index 7763e4e6..e6d49d47 100644 --- a/01_Archive/2026-04-20/Submodules.md +++ b/01_Archive/2026-04-20/Submodules.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-A6EDEA -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Submodules" --- -# [[Submodules]] +# [[Submodules|Submodules]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 서브모듈(Submodules)은 부모 애플리케이션 내에 존재하더라도 자체적인 컨텍스트를 가지기 때문에 Husky, lint-staged, ESLint와 같은 코드 품질 도구들과 기본적으로 원활하게 연동되지 않습니다. 따라서 이러한 도구들이 정상적으로 작동하여 코딩 표준을 강제할 수 있도록, 서브모듈 루트 내에 개별적인 패키지 설치 및 부모 설정을 확장(extend)하는 구성 작업이 필수적으로 요구됩니다 [1, 2]. @@ -24,11 +24,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Submodules" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Husky]], [[lint-staged]], [[ESLint]], [[TypeScript]] -- **Projects/Contexts:** [[팀 코딩 표준 강제 (Enforcing coding standards)]] +- **Related Topics:** [[Husky|Husky]], [[lint-staged|lint-staged]], [[ESLint|ESLint]], [[TypeScript 라이브러리 타입 확장|TypeScript]] +- **Projects/Contexts:** 팀 코딩 표준 강제 (Enforcing coding standards) - **Contradictions/Notes:** 서브모듈은 부모 디렉터리에 도구들이 설치 및 설정되어 있더라도 이를 자동으로 공유하지 않습니다. 따라서 부모 애플리케이션의 린트 및 포맷팅 자동화를 서브모듈에도 동일하게 적용하려면 각각 독립적인 훅과 확장 설정이 강제됩니다 [1, 2]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Submodules.md]] +- Raw Source: 00_Raw/2026-04-20/Submodules.md --- diff --git a/01_Archive/2026-04-20/Subtyping-Relations.md b/01_Archive/2026-04-20/Subtyping-Relations.md index 39e58f79..bcd8c746 100644 --- a/01_Archive/2026-04-20/Subtyping-Relations.md +++ b/01_Archive/2026-04-20/Subtyping-Relations.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-4C9B28 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Subtyping-Relations" --- -# [[Subtyping-Relations]] +# [[Subtyping-Relations|Subtyping-Relations]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Subtyping-Relations" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Subtyping-Relations.md]] +- Raw Source: 00_Raw/2026-04-20/Subtyping-Relations.md --- diff --git a/01_Archive/2026-04-20/Subtyping-Rules.md b/01_Archive/2026-04-20/Subtyping-Rules.md index 358c3596..5fa0870f 100644 --- a/01_Archive/2026-04-20/Subtyping-Rules.md +++ b/01_Archive/2026-04-20/Subtyping-Rules.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-FFBE65 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Subtyping-Rules" --- -# [[Subtyping-Rules]] +# [[Subtyping-Rules|Subtyping-Rules]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Subtyping-Rules" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Subtyping-Rules.md]] +- Raw Source: 00_Raw/2026-04-20/Subtyping-Rules.md --- diff --git a/01_Archive/2026-04-20/Subtyping-and-Variance.md b/01_Archive/2026-04-20/Subtyping-and-Variance.md index 7407aa19..b18fc524 100644 --- a/01_Archive/2026-04-20/Subtyping-and-Variance.md +++ b/01_Archive/2026-04-20/Subtyping-and-Variance.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-B1CA51 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Subtyping-and-Variance" --- -# [[Subtyping-and-Variance]] +# [[Subtyping-and-Variance|Subtyping-and-Variance]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Subtyping-and-Variance" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Subtyping-and-Variance.md]] +- Raw Source: 00_Raw/2026-04-20/Subtyping-and-Variance.md --- diff --git a/01_Archive/2026-04-20/Sum-Types.md b/01_Archive/2026-04-20/Sum-Types.md index d7a13309..bbf96be5 100644 --- a/01_Archive/2026-04-20/Sum-Types.md +++ b/01_Archive/2026-04-20/Sum-Types.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-BDFB36 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Sum-Types" --- -# [[Sum-Types]] +# [[Sum-Types|Sum-Types]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Sum-Types" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Sum-Types.md]] +- Raw Source: 00_Raw/2026-04-20/Sum-Types.md --- diff --git a/01_Archive/2026-04-20/Superposition (중첩).md b/01_Archive/2026-04-20/Superposition (중첩).md index 3fe1778c..8b343916 100644 --- a/01_Archive/2026-04-20/Superposition (중첩).md +++ b/01_Archive/2026-04-20/Superposition (중첩).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-1840DD -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Superposition (중첩)" --- -# [[Superposition (중첩)]] +# [[Superposition (중첩)|Superposition (중첩)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Superposition (중첩)" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Superposition (중첩).md]] +- Raw Source: 00_Raw/2026-04-20/Superposition (중첩).md --- diff --git a/01_Archive/2026-04-20/Supply-Chain-Management.md b/01_Archive/2026-04-20/Supply-Chain-Management.md index 35dc7d38..c327b9f6 100644 --- a/01_Archive/2026-04-20/Supply-Chain-Management.md +++ b/01_Archive/2026-04-20/Supply-Chain-Management.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-58899C -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Supply-Chain-Management" --- -# [[Supply-Chain-Management]] +# [[Supply-Chain-Management|Supply-Chain-Management]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Supply-Chain-Management" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Supply-Chain-Management.md]] +- Raw Source: 00_Raw/2026-04-20/Supply-Chain-Management.md --- diff --git a/01_Archive/2026-04-20/Surgical-Robotics.md b/01_Archive/2026-04-20/Surgical-Robotics.md index 0bf6770e..0bc4ceed 100644 --- a/01_Archive/2026-04-20/Surgical-Robotics.md +++ b/01_Archive/2026-04-20/Surgical-Robotics.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-C5C20D -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Surgical-Robotics" --- -# [[Surgical-Robotics]] +# [[Surgical-Robotics|Surgical-Robotics]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Surgical-Robotics" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Surgical-Robotics.md]] +- Raw Source: 00_Raw/2026-04-20/Surgical-Robotics.md --- diff --git a/01_Archive/2026-04-20/Surreal Numbers.md b/01_Archive/2026-04-20/Surreal Numbers.md index 2a574be5..66e6dbfe 100644 --- a/01_Archive/2026-04-20/Surreal Numbers.md +++ b/01_Archive/2026-04-20/Surreal Numbers.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-785AE1 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Surreal Numbers" --- -# [[Surreal Numbers]] +# [[Surreal Numbers|Surreal Numbers]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Surreal Numbers" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Surreal Numbers.md]] +- Raw Source: 00_Raw/2026-04-20/Surreal Numbers.md --- diff --git a/01_Archive/2026-04-20/Survival Horror Genre.md b/01_Archive/2026-04-20/Survival Horror Genre.md index c761fbf5..539b972d 100644 --- a/01_Archive/2026-04-20/Survival Horror Genre.md +++ b/01_Archive/2026-04-20/Survival Horror Genre.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-2AE52E -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Survival Horror Genre" --- -# [[Survival Horror Genre]] +# [[Survival Horror Genre|Survival Horror Genre]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Survival Horror Genre" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Survival Horror Genre.md]] +- Raw Source: 00_Raw/2026-04-20/Survival Horror Genre.md --- diff --git a/01_Archive/2026-04-20/Sustainable Development Goals (SDGs).md b/01_Archive/2026-04-20/Sustainable Development Goals (SDGs).md index 65255e96..3cf6f0ae 100644 --- a/01_Archive/2026-04-20/Sustainable Development Goals (SDGs).md +++ b/01_Archive/2026-04-20/Sustainable Development Goals (SDGs).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-189E36 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Sustainable Development Goals (SDGs)" --- -# [[Sustainable Development Goals (SDGs)]] +# [[Sustainable Development Goals (SDGs)|Sustainable Development Goals (SDGs)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Sustainable Development Goals ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Sustainable Development Goals (SDGs).md]] +- Raw Source: 00_Raw/2026-04-20/Sustainable Development Goals (SDGs).md --- diff --git a/01_Archive/2026-04-20/Sustainable-Development-Goals (SDGs).md b/01_Archive/2026-04-20/Sustainable-Development-Goals (SDGs).md index 96b46bc8..cfa36cfa 100644 --- a/01_Archive/2026-04-20/Sustainable-Development-Goals (SDGs).md +++ b/01_Archive/2026-04-20/Sustainable-Development-Goals (SDGs).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-C74AAC -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Sustainable-Development-Goals (SDGs)" --- -# [[Sustainable-Development-Goals (SDGs)]] +# [[Sustainable-Development-Goals (SDGs)|Sustainable-Development-Goals (SDGs)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Sustainable-Development-Goals ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Sustainable-Development-Goals (SDGs).md]] +- Raw Source: 00_Raw/2026-04-20/Sustainable-Development-Goals (SDGs).md --- diff --git a/01_Archive/2026-04-20/Sycophancy (LLM 아첨 문제).md b/01_Archive/2026-04-20/Sycophancy (LLM 아첨 문제).md index 87611aa9..46e7035a 100644 --- a/01_Archive/2026-04-20/Sycophancy (LLM 아첨 문제).md +++ b/01_Archive/2026-04-20/Sycophancy (LLM 아첨 문제).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-0AA310 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Sycophancy (LLM 아첨 문제)" --- -# [[Sycophancy (LLM 아첨 문제)]] +# [[Sycophancy (LLM 아첨 문제)|Sycophancy (LLM 아첨 문제)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Sycophancy (LLM 아첨 문제) ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Sycophancy (LLM 아첨 문제).md]] +- Raw Source: 00_Raw/2026-04-20/Sycophancy (LLM 아첨 문제).md --- diff --git a/01_Archive/2026-04-20/Symbolic-Logic.md b/01_Archive/2026-04-20/Symbolic-Logic.md index d5de31a8..7f521e39 100644 --- a/01_Archive/2026-04-20/Symbolic-Logic.md +++ b/01_Archive/2026-04-20/Symbolic-Logic.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-5793E0 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Symbolic-Logic" --- -# [[Symbolic-Logic]] +# [[Symbolic-Logic|Symbolic-Logic]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Symbolic-Logic" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Symbolic-Logic.md]] +- Raw Source: 00_Raw/2026-04-20/Symbolic-Logic.md --- diff --git a/01_Archive/2026-04-20/Synaptic Plasticity.md b/01_Archive/2026-04-20/Synaptic Plasticity.md index 39785997..e2345244 100644 --- a/01_Archive/2026-04-20/Synaptic Plasticity.md +++ b/01_Archive/2026-04-20/Synaptic Plasticity.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-DC2DA0 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Synaptic Plasticity" --- -# [[Synaptic Plasticity]] +# [[Synaptic Plasticity|Synaptic Plasticity]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Synaptic Plasticity" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Synaptic Plasticity.md]] +- Raw Source: 00_Raw/2026-04-20/Synaptic Plasticity.md --- diff --git a/01_Archive/2026-04-20/SynthID (구글 AI 식별 기술).md b/01_Archive/2026-04-20/SynthID (구글 AI 식별 기술).md index b33b1360..110cea0a 100644 --- a/01_Archive/2026-04-20/SynthID (구글 AI 식별 기술).md +++ b/01_Archive/2026-04-20/SynthID (구글 AI 식별 기술).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-A89657 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - SynthID (구글 AI 식별 기술)" --- -# [[SynthID (구글 AI 식별 기술)]] +# [[SynthID (구글 AI 식별 기술)|SynthID (구글 AI 식별 기술)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - SynthID (구글 AI 식별 기 ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/SynthID (구글 AI 식별 기술).md]] +- Raw Source: 00_Raw/2026-04-20/SynthID (구글 AI 식별 기술).md --- diff --git a/01_Archive/2026-04-20/Synthetic Data (합성 데이터).md b/01_Archive/2026-04-20/Synthetic Data (합성 데이터).md index d779d41f..5dc75872 100644 --- a/01_Archive/2026-04-20/Synthetic Data (합성 데이터).md +++ b/01_Archive/2026-04-20/Synthetic Data (합성 데이터).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-532E5E -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Synthetic Data (합성 데이터)" --- -# [[Synthetic Data (합성 데이터)]] +# [[Synthetic Data (합성 데이터)|Synthetic Data (합성 데이터)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Synthetic Data (합성 데이 ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Synthetic Data (합성 데이터).md]] +- Raw Source: 00_Raw/2026-04-20/Synthetic Data (합성 데이터).md --- diff --git a/01_Archive/2026-04-20/Synthetic Testing.md b/01_Archive/2026-04-20/Synthetic Testing.md index 95c81381..6fac40a0 100644 --- a/01_Archive/2026-04-20/Synthetic Testing.md +++ b/01_Archive/2026-04-20/Synthetic Testing.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-DE0BE9 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Synthetic Testing" --- -# [[Synthetic Testing]] +# [[Synthetic Testing|Synthetic Testing]] ## 📌 한 줄 통찰 (The Karpathy Summary) > Synthetic Testing(합성 테스트)은 네트워크에 연결된 알려진 기기 및 통제된 실험실(Lab) 환경에서 웹사이트의 성능을 측정하는 방법입니다 [1, 2]. 이는 실제 사용자가 겪는 성능을 직접 측정하는 것이 아니라, 향후 성능이 어떨지 추정(estimate)하기 위해 사용됩니다 [2]. 주로 Google Lighthouse, WebPageTest, DebugBear 같은 도구를 사용하여 사용자 상호작용을 시뮬레이션하고 성능 메트릭을 평가하는 데 활용됩니다 [1, 3, 4]. @@ -26,11 +26,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Synthetic Testing" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Lab Data]], [[Field Data]], [[Real User Monitoring]], [[Core Web Vitals]] -- **Projects/Contexts:** [[웹 성능 모니터링 및 최적화]], [[Google Lighthouse]], [[WebPageTest]] +- **Related Topics:** Lab Data, Field Data, Real User Monitoring, [[Core Web Vitals|Core Web Vitals]] +- **Projects/Contexts:** 웹 성능 모니터링 및 최적화, [[Google Lighthouse|Google Lighthouse]], WebPageTest - **Contradictions/Notes:** Synthetic Testing(합성 테스트)은 통제된 환경에서의 성능 추정에는 매우 유용하지만, 실제 사용자의 상호작용을 완벽하게 재현할 수 없다는 한계를 가집니다. 따라서 이를 보완하기 위해 실제 환경의 성능을 반영하는 Field Data(Real User Monitoring)가 필수적으로 요구된다고 소스들은 강조합니다 [1, 2]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Synthetic Testing.md]] +- Raw Source: 00_Raw/2026-04-20/Synthetic Testing.md --- diff --git a/01_Archive/2026-04-20/System Dynamics.md b/01_Archive/2026-04-20/System Dynamics.md index a2fe9262..639068c7 100644 --- a/01_Archive/2026-04-20/System Dynamics.md +++ b/01_Archive/2026-04-20/System Dynamics.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-282998 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - System Dynamics" --- -# [[System Dynamics]] +# [[System Dynamics|System Dynamics]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - System Dynamics" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/System Dynamics.md]] +- Raw Source: 00_Raw/2026-04-20/System Dynamics.md --- diff --git a/01_Archive/2026-04-20/System Prompt (시스템 프롬프트).md b/01_Archive/2026-04-20/System Prompt (시스템 프롬프트).md index 31349567..fdbf0513 100644 --- a/01_Archive/2026-04-20/System Prompt (시스템 프롬프트).md +++ b/01_Archive/2026-04-20/System Prompt (시스템 프롬프트).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-BEA248 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - System Prompt (시스템 프롬프트)" --- -# [[System Prompt (시스템 프롬프트)]] +# [[System Prompt (시스템 프롬프트)|System Prompt (시스템 프롬프트)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - System Prompt (시스템 프 ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/System Prompt (시스템 프롬프트).md]] +- Raw Source: 00_Raw/2026-04-20/System Prompt (시스템 프롬프트).md --- diff --git a/01_Archive/2026-04-20/Systemic Design.md b/01_Archive/2026-04-20/Systemic Design.md index 3f861d93..a536c3b8 100644 --- a/01_Archive/2026-04-20/Systemic Design.md +++ b/01_Archive/2026-04-20/Systemic Design.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-0B8492 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Systemic Design" --- -# [[Systemic Design]] +# [[Systemic Design|Systemic Design]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Systemic Design" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Systemic Design.md]] +- Raw Source: 00_Raw/2026-04-20/Systemic Design.md --- diff --git a/01_Archive/2026-04-20/Systemic Game Design.md b/01_Archive/2026-04-20/Systemic Game Design.md index d8c474d1..f2817b99 100644 --- a/01_Archive/2026-04-20/Systemic Game Design.md +++ b/01_Archive/2026-04-20/Systemic Game Design.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-364762 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Systemic Game Design" --- -# [[Systemic Game Design]] +# [[Systemic Game Design|Systemic Game Design]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Systemic Game Design" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Systemic Game Design.md]] +- Raw Source: 00_Raw/2026-04-20/Systemic Game Design.md --- diff --git a/01_Archive/2026-04-20/Systemic-Cohesion.md b/01_Archive/2026-04-20/Systemic-Cohesion.md index 10b43a27..d4523fec 100644 --- a/01_Archive/2026-04-20/Systemic-Cohesion.md +++ b/01_Archive/2026-04-20/Systemic-Cohesion.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-E0B412 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Systemic-Cohesion" --- -# [[Systemic-Cohesion]] +# [[Systemic-Cohesion|Systemic-Cohesion]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Systemic-Cohesion" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Systemic-Cohesion.md]] +- Raw Source: 00_Raw/2026-04-20/Systemic-Cohesion.md --- diff --git a/01_Archive/2026-04-20/Systemic-Design-Frameworks.md b/01_Archive/2026-04-20/Systemic-Design-Frameworks.md index ba86633b..89b36eb5 100644 --- a/01_Archive/2026-04-20/Systemic-Design-Frameworks.md +++ b/01_Archive/2026-04-20/Systemic-Design-Frameworks.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-3308A5 -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Systemic-Design-Frameworks" --- -# [[Systemic-Design-Frameworks]] +# [[Systemic-Design-Frameworks|Systemic-Design-Frameworks]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Systemic-Design-Frameworks" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Systemic-Design-Frameworks.md]] +- Raw Source: 00_Raw/2026-04-20/Systemic-Design-Frameworks.md --- diff --git a/01_Archive/2026-04-20/Systemic-Design.md b/01_Archive/2026-04-20/Systemic-Design.md index bbf33a6d..6f8aa647 100644 --- a/01_Archive/2026-04-20/Systemic-Design.md +++ b/01_Archive/2026-04-20/Systemic-Design.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-9123E5 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Systemic-Design" --- -# [[Systemic-Design]] +# [[Systemic-Design|Systemic-Design]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Systemic-Design" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Systemic-Design.md]] +- Raw Source: 00_Raw/2026-04-20/Systemic-Design.md --- diff --git a/01_Archive/2026-04-20/Systems Biology.md b/01_Archive/2026-04-20/Systems Biology.md index e8669e34..b738a35a 100644 --- a/01_Archive/2026-04-20/Systems Biology.md +++ b/01_Archive/2026-04-20/Systems Biology.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-2A4288 -category: "[[10_Wiki/💡 Topics/Game Design]]" +category: "10_Wiki/💡 Topics/Game Design" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Systems Biology" --- -# [[Systems Biology]] +# [[Systems Biology|Systems Biology]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Systems Biology" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Systems Biology.md]] +- Raw Source: 00_Raw/2026-04-20/Systems Biology.md --- diff --git a/01_Archive/2026-04-20/Systems Dynamics.md b/01_Archive/2026-04-20/Systems Dynamics.md index 95466b5a..ef0551d9 100644 --- a/01_Archive/2026-04-20/Systems Dynamics.md +++ b/01_Archive/2026-04-20/Systems Dynamics.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-A319BE -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Systems Dynamics" --- -# [[Systems Dynamics]] +# [[Systems Dynamics|Systems Dynamics]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Systems Dynamics" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Systems Dynamics.md]] +- Raw Source: 00_Raw/2026-04-20/Systems Dynamics.md --- diff --git a/01_Archive/2026-04-20/Systems Theory.md b/01_Archive/2026-04-20/Systems Theory.md index 9e83912d..b92845a9 100644 --- a/01_Archive/2026-04-20/Systems Theory.md +++ b/01_Archive/2026-04-20/Systems Theory.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-B5E5CB -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Systems Theory" --- -# [[Systems Theory]] +# [[Systems Theory|Systems Theory]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Systems Theory" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Systems Theory.md]] +- Raw Source: 00_Raw/2026-04-20/Systems Theory.md --- diff --git a/01_Archive/2026-04-20/Systems Thinking in Management.md b/01_Archive/2026-04-20/Systems Thinking in Management.md index 9e4936c1..0620dd5c 100644 --- a/01_Archive/2026-04-20/Systems Thinking in Management.md +++ b/01_Archive/2026-04-20/Systems Thinking in Management.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-8B0A69 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Systems Thinking in Management" --- -# [[Systems Thinking in Management]] +# [[Systems Thinking in Management|Systems Thinking in Management]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Systems Thinking in Management ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Systems Thinking in Management.md]] +- Raw Source: 00_Raw/2026-04-20/Systems Thinking in Management.md --- diff --git a/01_Archive/2026-04-20/Systems Thinking.md b/01_Archive/2026-04-20/Systems Thinking.md index 96cfd529..2133c5e6 100644 --- a/01_Archive/2026-04-20/Systems Thinking.md +++ b/01_Archive/2026-04-20/Systems Thinking.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-6EBBC9 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Systems Thinking" --- -# [[Systems Thinking]] +# [[Systems Thinking|Systems Thinking]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Systems Thinking" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Systems Thinking.md]] +- Raw Source: 00_Raw/2026-04-20/Systems Thinking.md --- diff --git a/01_Archive/2026-04-20/Systems-Thinking.md b/01_Archive/2026-04-20/Systems-Thinking.md index 2b756aa7..650ddd0a 100644 --- a/01_Archive/2026-04-20/Systems-Thinking.md +++ b/01_Archive/2026-04-20/Systems-Thinking.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-2028E0 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Systems-Thinking" --- -# [[Systems-Thinking]] +# [[Systems-Thinking|Systems-Thinking]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Systems-Thinking" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Systems-Thinking.md]] +- Raw Source: 00_Raw/2026-04-20/Systems-Thinking.md --- diff --git a/01_Archive/2026-04-20/TLB design.md b/01_Archive/2026-04-20/TLB design.md index 4ca8a5a8..a19a4d30 100644 --- a/01_Archive/2026-04-20/TLB design.md +++ b/01_Archive/2026-04-20/TLB design.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-3CAF83 -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - TLB design" --- -# [[TLB design]] +# [[TLB design|TLB design]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 소스에 관련 정보가 부족합니다. 제공된 문헌에는 TLB design(Translation Lookaside Buffer 설계)에 대한 직접적이고 구체적인 정의나 기술적 설명이 포함되어 있지 않습니다. @@ -26,11 +26,11 @@ github_commit: "[P-Reinforce] Continuous Worker - TLB design" - **정책 변화:** Graphics & Performance 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Rowhammer]], [[WebGL]] -- **Projects/Contexts:** [[WebGPU High Resolution Time Spec]] +- **Related Topics:** [[Rowhammer|Rowhammer]], [[WebGL|WebGL]] +- **Projects/Contexts:** WebGPU High Resolution Time Spec - **Contradictions/Notes:** 소스에 관련 정보가 부족합니다. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/TLB design.md]] +- Raw Source: 00_Raw/2026-04-20/TLB design.md --- diff --git a/01_Archive/2026-04-20/TSL (Three Shader Language).md b/01_Archive/2026-04-20/TSL (Three Shader Language).md index 7336f19b..19676495 100644 --- a/01_Archive/2026-04-20/TSL (Three Shader Language).md +++ b/01_Archive/2026-04-20/TSL (Three Shader Language).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-C8966B -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - TSL (Three Shader Language)" --- -# [[TSL (Three Shader Language)]] +# [[TSL (Three Shader Language)|TSL (Three Shader Language)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > TSL (Three Shader Language)은 Three.js의 노드 기반 머티리얼 시스템입니다 [1]. 셰이더를 한 번 작성하면 WebGPU용 WGSL과 WebGL용 GLSL로 자동 컴파일되어 실행될 수 있게 해줍니다 [1, 2]. 로우 레벨(Raw) 셰이더를 직접 작성하는 것을 대체하며, 향후 Three.js에서 커스텀 셰이더를 구현하기 위한 권장 방식입니다 [1, 3]. @@ -24,11 +24,11 @@ github_commit: "[P-Reinforce] Continuous Worker - TSL (Three Shader Language)" - **정책 변화:** Graphics & Performance 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[WebGPU]], [[WebGL]], [[WGSL]], [[GLSL]], [[Node Material]] -- **Projects/Contexts:** [[Three.js]] +- **Related Topics:** [[WebGPU|WebGPU]], [[WebGL|WebGL]], WGSL, GLSL, Node Material +- **Projects/Contexts:** [[Three.js|Three.js]] - **Contradictions/Notes:** 소스 간의 모순점은 없으나, 이전의 렌더링 방식과 달리 별도의 GLSL/WGSL 코드를 직접 작성하는 것보다 TSL을 사용하는 것이 코드 유지보수 및 교차 호환성 측면에서 명백히 우월하다고 강조하고 있습니다 [3]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/TSL (Three Shader Language).md]] +- Raw Source: 00_Raw/2026-04-20/TSL (Three Shader Language).md --- diff --git a/01_Archive/2026-04-20/Taxonomy-and-Ontology.md b/01_Archive/2026-04-20/Taxonomy-and-Ontology.md index 1c051f5b..fb43308e 100644 --- a/01_Archive/2026-04-20/Taxonomy-and-Ontology.md +++ b/01_Archive/2026-04-20/Taxonomy-and-Ontology.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-93E139 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Taxonomy-and-Ontology" --- -# [[Taxonomy-and-Ontology]] +# [[Taxonomy-and-Ontology|Taxonomy-and-Ontology]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Taxonomy-and-Ontology" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Taxonomy-and-Ontology.md]] +- Raw Source: 00_Raw/2026-04-20/Taxonomy-and-Ontology.md --- diff --git a/01_Archive/2026-04-20/TeamCity.md b/01_Archive/2026-04-20/TeamCity.md index ad6a3b25..49237e76 100644 --- a/01_Archive/2026-04-20/TeamCity.md +++ b/01_Archive/2026-04-20/TeamCity.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-63B068 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - TeamCity" --- -# [[TeamCity]] +# [[TeamCity|TeamCity]] ## 📌 한 줄 통찰 (The Karpathy Summary) > TeamCity는 개봉 즉시 사용 가능한(out of the box) 강력한 지속적 통합(Continuous Integration) 도구입니다 [1, 2]. 이 도구는 팀을 위한 CI/CD 서버로 기능하며, 소프트웨어 빌드 프로세스 내에서 핵심적인 역할을 수행합니다 [3, 4]. 특히 정적 코드 분석 도구와 원활하게 통합되어 저품질의 코드가 프로덕션 환경에 배포되는 것을 사전에 차단할 수 있게 돕습니다 [4]. @@ -23,11 +23,11 @@ github_commit: "[P-Reinforce] Continuous Worker - TeamCity" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Continuous Integration]], [[Qodana]], [[CI/CD]] -- **Projects/Contexts:** [[정적 코드 분석 및 소프트웨어 빌드 자동화]] +- **Related Topics:** Continuous Integration, Qodana, [[CI_CD|CI/CD]] +- **Projects/Contexts:** 정적 코드 분석 및 소프트웨어 빌드 자동화 - **Contradictions/Notes:** 소스에는 TeamCity가 CI/CD 서버로서 Qodana와 통합되어 빌드 프로세스를 돕는다는 사실 외에 구체적인 기능이나 상세한 원리에 대한 설명은 없으므로, 전반적으로 소스에 관련 정보가 부족합니다. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/TeamCity.md]] +- Raw Source: 00_Raw/2026-04-20/TeamCity.md --- diff --git a/01_Archive/2026-04-20/Template-Literal-Types.md b/01_Archive/2026-04-20/Template-Literal-Types.md index 9aac9d74..24d686e2 100644 --- a/01_Archive/2026-04-20/Template-Literal-Types.md +++ b/01_Archive/2026-04-20/Template-Literal-Types.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-CBED64 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Template-Literal-Types" --- -# [[Template-Literal-Types]] +# [[Template-Literal-Types|Template-Literal-Types]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Template-Literal-Types" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Template-Literal-Types.md]] +- Raw Source: 00_Raw/2026-04-20/Template-Literal-Types.md --- diff --git a/01_Archive/2026-04-20/Temporal Difference Learning.md b/01_Archive/2026-04-20/Temporal Difference Learning.md index 0b58a573..7f395b40 100644 --- a/01_Archive/2026-04-20/Temporal Difference Learning.md +++ b/01_Archive/2026-04-20/Temporal Difference Learning.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-92B6E9 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Temporal Difference Learning" --- -# [[Temporal Difference Learning]] +# [[Temporal Difference Learning|Temporal Difference Learning]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Temporal Difference Learning" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Temporal Difference Learning.md]] +- Raw Source: 00_Raw/2026-04-20/Temporal Difference Learning.md --- diff --git a/01_Archive/2026-04-20/Temporal-Logic.md b/01_Archive/2026-04-20/Temporal-Logic.md index 614f1891..367ec266 100644 --- a/01_Archive/2026-04-20/Temporal-Logic.md +++ b/01_Archive/2026-04-20/Temporal-Logic.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-8C33E2 -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Temporal-Logic" --- -# [[Temporal-Logic]] +# [[Temporal-Logic|Temporal-Logic]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Temporal-Logic" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Temporal-Logic.md]] +- Raw Source: 00_Raw/2026-04-20/Temporal-Logic.md --- diff --git a/01_Archive/2026-04-20/Test-Time Compute Scaling (추론 시간 계산 스케일링).md b/01_Archive/2026-04-20/Test-Time Compute Scaling (추론 시간 계산 스케일링).md index e8f261a6..d83716b3 100644 --- a/01_Archive/2026-04-20/Test-Time Compute Scaling (추론 시간 계산 스케일링).md +++ b/01_Archive/2026-04-20/Test-Time Compute Scaling (추론 시간 계산 스케일링).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-E16EB6 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Test-Time Compute Scaling (추론 시간 계산 스케일링)" --- -# [[Test-Time Compute Scaling (추론 시간 계산 스케일링)]] +# [[Test-Time Compute Scaling (추론 시간 계산 스케일링)|Test-Time Compute Scaling (추론 시간 계산 스케일링)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Test-Time Compute Scaling (추 ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Test-Time Compute Scaling (추론 시간 계산 스케일링).md]] +- Raw Source: 00_Raw/2026-04-20/Test-Time Compute Scaling (추론 시간 계산 스케일링).md --- diff --git a/01_Archive/2026-04-20/Texture Atlas.md b/01_Archive/2026-04-20/Texture Atlas.md index 1332da92..9275826a 100644 --- a/01_Archive/2026-04-20/Texture Atlas.md +++ b/01_Archive/2026-04-20/Texture Atlas.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-71CA1F -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Texture Atlas" --- -# [[Texture Atlas]] +# [[Texture Atlas|Texture Atlas]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 텍스처 아틀라스(Texture Atlas)는 여러 개의 개별 텍스처 이미지를 하나의 커다란 텍스처 시트(Texture Sheet)로 병합하여 사용하는 렌더링 최적화 기법이다. `InstancedMesh` 환경에서 모든 인스턴스가 동일한 재질을 공유해야 하는 한계를 극복하고, 개별 인스턴스마다 다른 텍스처를 적용하기 위한 필수적인 우회 기법으로 활용된다. 이를 통해 텍스처 바인딩 횟수를 줄이고 드로우 콜(Draw Call)을 최소화하여 성능을 크게 향상시킬 수 있다. @@ -30,11 +30,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Texture Atlas" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[InstancedMesh]], [[Draw Call]], [[UV Offset]], [[Edge Bleeding]], [[Data Array Textures]], [[BatchedMesh]] -- **Projects/Contexts:** [[Three.js 렌더링 최적화]], [[WebGL 모바일 GPU 성능 관리]] +- **Related Topics:** [[InstancedMesh|InstancedMesh]], [[Draw Call|Draw Call]], [[UV Offset|UV Offset]], [[Edge Bleeding|Edge Bleeding]], [[Data Array Textures|Data Array Textures]], [[BatchedMesh|BatchedMesh]] +- **Projects/Contexts:** [[Three.js 렌더링 최적화|Three.js 렌더링 최적화]], [[WebGL 모바일 GPU 성능 관리|WebGL 모바일 GPU 성능 관리]] - **Contradictions/Notes:** 소스 문헌들은 텍스처 아틀라스가 드로우 콜을 획기적으로 줄여주는 필수 최적화 기법임을 인정하면서도, 경계선 블리딩(Edge Bleeding) 방지를 위한 패딩으로 인한 메모리 낭비와 UV 연산 복잡성 증가라는 명확한 단점을 지적한다. 그 대안으로 배열 텍스처(Array Textures)가 추천되지만, 다양한 해상도의 텍스처를 혼합해 써야 할 경우에는 여전히 텍스처 아틀라스를 사용해야 한다는 트레이드오프가 존재한다 [2, 5, 9]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Texture Atlas.md]] +- Raw Source: 00_Raw/2026-04-20/Texture Atlas.md --- diff --git a/01_Archive/2026-04-20/Texture Compression.md b/01_Archive/2026-04-20/Texture Compression.md index 4383bb5d..da5673f5 100644 --- a/01_Archive/2026-04-20/Texture Compression.md +++ b/01_Archive/2026-04-20/Texture Compression.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-B90AAF -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Texture Compression" --- -# [[Texture Compression]] +# [[Texture Compression|Texture Compression]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 텍스처 압축(Texture Compression)은 웹 기반 3D 애플리케이션(예: Three.js)에서 GPU 메모리(VRAM) 소비와 파일 다운로드 크기를 획기적으로 줄이기 위한 필수 최적화 기술입니다 [1-3]. PNG나 JPEG와 같은 일반적인 이미지 포맷이 GPU 메모리 내에서 압축이 완전히 풀리는 것과 달리, KTX2나 Basis Universal 같은 포맷은 GPU 상에서도 압축된 상태를 유지하여 하드웨어 가속 압축 해제를 지원합니다 [1, 3]. 이를 통해 메모리 대역폭 요구량을 줄이고 저사양 기기에서의 브라우저 크래시나 프레임 저하를 방지할 수 있습니다 [2, 3]. @@ -29,11 +29,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Texture Compression" - **정책 변화:** Graphics & Performance 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[KTX2]], [[Basis Universal]], [[UASTC]], [[ETC1S]], [[VRAM]] -- **Projects/Contexts:** [[Three.js]], [[WebGL]], [[gltf-compressor]] +- **Related Topics:** KTX2, Basis Universal, UASTC, ETC1S, VRAM +- **Projects/Contexts:** [[Three.js|Three.js]], [[WebGL|WebGL]], gltf-compressor - **Contradictions/Notes:** 소스에 내용 충돌은 없으며, PNG/JPEG 포맷은 파일 크기(예: 200KB)가 작더라도 GPU 메모리에 올라갈 때 압축이 해제되어 막대한 VRAM(예: 20MB+)을 소모하므로 KTX2와 같은 전용 텍스처 압축 기술이 필수적이라고 일관되게 강조하고 있습니다 [1]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Texture Compression.md]] +- Raw Source: 00_Raw/2026-04-20/Texture Compression.md --- diff --git a/01_Archive/2026-04-20/Texture-Synthesis.md b/01_Archive/2026-04-20/Texture-Synthesis.md index a12c2351..4cc552f7 100644 --- a/01_Archive/2026-04-20/Texture-Synthesis.md +++ b/01_Archive/2026-04-20/Texture-Synthesis.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-197D49 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Texture-Synthesis" --- -# [[Texture-Synthesis]] +# [[Texture-Synthesis|Texture-Synthesis]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Texture-Synthesis" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Texture-Synthesis.md]] +- Raw Source: 00_Raw/2026-04-20/Texture-Synthesis.md --- diff --git a/01_Archive/2026-04-20/The 'Immersive Sim' Taxonomy Debate.md b/01_Archive/2026-04-20/The 'Immersive Sim' Taxonomy Debate.md index b2e25a6d..95989ee9 100644 --- a/01_Archive/2026-04-20/The 'Immersive Sim' Taxonomy Debate.md +++ b/01_Archive/2026-04-20/The 'Immersive Sim' Taxonomy Debate.md @@ -1,4 +1,4 @@ -[[The 'Immersive Sim' Taxonomy Debate]] +[[The 'Immersive Sim' Taxonomy Debate|The 'Immersive Sim' Taxonomy Debate]] 📌 Brief Summary The "Immersive Sim" taxonomy debate centers on whether the genre should be defined by specific mechanical constraints (systemic agency and emergent gameplay) or by a particular aesthetic and narrative atmosphere (environmental storytelling and player presence). This ontological conflict pits a formalist approach, focusing on rule-based interaction, against a phenomenological approach, focusing on the player's subjective experience of "immersion." @@ -13,8 +13,8 @@ The debate is fundamentally an architectural disagreement over what constitutes The debate is further complicated by the "Scope Creep" problem: as developers integrate more systemic elements into traditional RPGs or stealth games, the boundaries of the taxonomy blur. This leads to the critical question of whether "Immersive Sim" is a functional genre (a set of tools) or an aesthetic genre (a way of presenting a world). 🔗 Knowledge Connections -* Related Topics: [[Emergent Gameplay]], [[Ludonarrative Dissonance]], [[Systemic Design]], [[Environmental Storytelling]] -* Projects/Contexts: [[Looking Glass Studios Legacy]], [[The Looking Glass School of Design]], [[Systemic Interaction Theory]] +* Related Topics: [[Emergent Gameplay|Emergent Gameplay]], [[Ludonarrative Dissonance|Ludonarrative Dissonance]], [[Systemic Design|Systemic Design]], [[Environmental Storytelling|Environmental Storytelling]] +* Projects/Contexts: Looking Glass Studios Legacy, The Looking Glass School of Design, Systemic Interaction Theory * Contradictions/Notes: There is a significant tension between "Hard Systemic" purists (who exclude games with scripted sequences) and "Atmospheric" theorists (who include games that prioritize narrative immersion over mechanical unpredictability). Last updated: 2026-04-16 \ No newline at end of file diff --git a/01_Archive/2026-04-20/The Emergence Theory in Game Design.md b/01_Archive/2026-04-20/The Emergence Theory in Game Design.md index c01715b0..c4788869 100644 --- a/01_Archive/2026-04-20/The Emergence Theory in Game Design.md +++ b/01_Archive/2026-04-20/The Emergence Theory in Game Design.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-A4804A -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - The Emergence Theory in Game Design" --- -# [[The Emergence Theory in Game Design]] +# [[The Emergence Theory in Game Design|The Emergence Theory in Game Design]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - The Emergence Theory in Game D ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/The Emergence Theory in Game Design.md]] +- Raw Source: 00_Raw/2026-04-20/The Emergence Theory in Game Design.md --- diff --git a/01_Archive/2026-04-20/The Immersive Sim Taxonomy Debate.md b/01_Archive/2026-04-20/The Immersive Sim Taxonomy Debate.md index 858d5746..863f2267 100644 --- a/01_Archive/2026-04-20/The Immersive Sim Taxonomy Debate.md +++ b/01_Archive/2026-04-20/The Immersive Sim Taxonomy Debate.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-4613F1 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - The Immersive Sim Taxonomy Debate" --- -# [[The Immersive Sim Taxonomy Debate]] +# [[The Immersive Sim Taxonomy Debate|The Immersive Sim Taxonomy Debate]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - The Immersive Sim Taxonomy Deb ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/The 'Immersive Sim' Taxonomy Debate.md]] +- Raw Source: 00_Raw/2026-04-20/The 'Immersive Sim' Taxonomy Debate.md --- diff --git a/01_Archive/2026-04-20/The Last of Us (Resource Scarcity and Character Bond).md b/01_Archive/2026-04-20/The Last of Us (Resource Scarcity and Character Bond).md index df00de73..065814b7 100644 --- a/01_Archive/2026-04-20/The Last of Us (Resource Scarcity and Character Bond).md +++ b/01_Archive/2026-04-20/The Last of Us (Resource Scarcity and Character Bond).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-B7E710 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - The Last of Us (Resource Scarcity and Character Bond)" --- -# [[The Last of Us (Resource Scarcity and Character Bond)]] +# [[The Last of Us (Resource Scarcity and Character Bond)|The Last of Us (Resource Scarcity and Character Bond)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - The Last of Us (Resource Scarc ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/The Last of Us (Resource Scarcity and Character Bond).md]] +- Raw Source: 00_Raw/2026-04-20/The Last of Us (Resource Scarcity and Character Bond).md --- diff --git a/01_Archive/2026-04-20/The Last of Us Series.md b/01_Archive/2026-04-20/The Last of Us Series.md index ff05119e..9ae4fc9a 100644 --- a/01_Archive/2026-04-20/The Last of Us Series.md +++ b/01_Archive/2026-04-20/The Last of Us Series.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-2121F1 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - The Last of Us Series" --- -# [[The Last of Us Series]] +# [[The Last of Us Series|The Last of Us Series]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - The Last of Us Series" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/The Last of Us Series.md]] +- Raw Source: 00_Raw/2026-04-20/The Last of Us Series.md --- diff --git a/01_Archive/2026-04-20/The Overwatch League Case Study.md b/01_Archive/2026-04-20/The Overwatch League Case Study.md index 2960c83d..ee5e73fe 100644 --- a/01_Archive/2026-04-20/The Overwatch League Case Study.md +++ b/01_Archive/2026-04-20/The Overwatch League Case Study.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-B644A1 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - The Overwatch League Case Study" --- -# [[The Overwatch League Case Study]] +# [[The Overwatch League Case Study|The Overwatch League Case Study]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - The Overwatch League Case Stud ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/The Overwatch League Case Study.md]] +- Raw Source: 00_Raw/2026-04-20/The Overwatch League Case Study.md --- diff --git a/01_Archive/2026-04-20/The Rapture Setting.md b/01_Archive/2026-04-20/The Rapture Setting.md index cd931f18..a9a087d1 100644 --- a/01_Archive/2026-04-20/The Rapture Setting.md +++ b/01_Archive/2026-04-20/The Rapture Setting.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-180DD3 -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - The Rapture Setting" --- -# [[The Rapture Setting]] +# [[The Rapture Setting|The Rapture Setting]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - The Rapture Setting" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/The Rapture Setting.md]] +- Raw Source: 00_Raw/2026-04-20/The Rapture Setting.md --- diff --git a/01_Archive/2026-04-20/The Science of Well-Being (Yale).md b/01_Archive/2026-04-20/The Science of Well-Being (Yale).md index 159c2a95..cc2a6700 100644 --- a/01_Archive/2026-04-20/The Science of Well-Being (Yale).md +++ b/01_Archive/2026-04-20/The Science of Well-Being (Yale).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-C3C1C2 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - The Science of Well-Being (Yale)" --- -# [[The Science of Well-Being (Yale)]] +# [[The Science of Well-Being (Yale)|The Science of Well-Being (Yale)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - The Science of Well-Being (Yal ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/The Science of Well-Being (Yale).md]] +- Raw Source: 00_Raw/2026-04-20/The Science of Well-Being (Yale).md --- diff --git a/01_Archive/2026-04-20/The-Collapse-of-Utopian-Ideologies.md b/01_Archive/2026-04-20/The-Collapse-of-Utopian-Ideologies.md index 324d452b..44017fbd 100644 --- a/01_Archive/2026-04-20/The-Collapse-of-Utopian-Ideologies.md +++ b/01_Archive/2026-04-20/The-Collapse-of-Utopian-Ideologies.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-12C4DD -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - The-Collapse-of-Utopian-Ideologies" --- -# [[The-Collapse-of-Utopian-Ideologies]] +# [[The-Collapse-of-Utopian-Ideologies|The-Collapse-of-Utopian-Ideologies]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - The-Collapse-of-Utopian-Ideolo ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/The-Collapse-of-Utopian-Ideologies.md]] +- Raw Source: 00_Raw/2026-04-20/The-Collapse-of-Utopian-Ideologies.md --- diff --git a/01_Archive/2026-04-20/The-Space-Syntax-Laboratory.md b/01_Archive/2026-04-20/The-Space-Syntax-Laboratory.md index fea0bce1..021a9385 100644 --- a/01_Archive/2026-04-20/The-Space-Syntax-Laboratory.md +++ b/01_Archive/2026-04-20/The-Space-Syntax-Laboratory.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-64715F -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - The-Space-Syntax-Laboratory" --- -# [[The-Space-Syntax-Laboratory]] +# [[The-Space-Syntax-Laboratory|The-Space-Syntax-Laboratory]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - The-Space-Syntax-Laboratory" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/The-Space-Syntax-Laboratory.md]] +- Raw Source: 00_Raw/2026-04-20/The-Space-Syntax-Laboratory.md --- diff --git a/01_Archive/2026-04-20/Themework-Integration.md b/01_Archive/2026-04-20/Themework-Integration.md index fdd0e2a8..d0bfc75e 100644 --- a/01_Archive/2026-04-20/Themework-Integration.md +++ b/01_Archive/2026-04-20/Themework-Integration.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-159F6C -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Themework-Integration" --- -# [[Themework-Integration]] +# [[Themework-Integration|Themework-Integration]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Themework-Integration" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Themework-Integration.md]] +- Raw Source: 00_Raw/2026-04-20/Themework-Integration.md --- diff --git a/01_Archive/2026-04-20/Three Shader Language (TSL).md b/01_Archive/2026-04-20/Three Shader Language (TSL).md index 377ecb42..67ad4b8f 100644 --- a/01_Archive/2026-04-20/Three Shader Language (TSL).md +++ b/01_Archive/2026-04-20/Three Shader Language (TSL).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-1AF9EB -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Three Shader Language (TSL)" --- -# [[Three Shader Language (TSL)]] +# [[Three Shader Language (TSL)|Three Shader Language (TSL)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > TSL(Three Shader Language)은 WebGPU의 WGSL과 WebGL의 GLSL로 모두 컴파일될 수 있는 Three.js의 노드 기반 머티리얼 및 셰이더 시스템입니다 [1]. 개발자가 셰이더 코드를 한 번만 작성하면 여러 플랫폼에서 실행 가능하도록 자동 교차 컴파일을 지원하여 코드 중복을 방지합니다 [1-3]. 유니폼 및 속성 관리를 자동으로 처리해주며, 향후 Three.js에서 커스텀 셰이더를 개발하기 위한 권장 방식으로 평가받고 있습니다 [1, 2, 4]. @@ -23,11 +23,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Three Shader Language (TSL)" - **정책 변화:** Graphics & Performance 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[WebGPU]], [[WebGL]], [[WGSL]], [[GLSL]], [[Node Material]] -- **Projects/Contexts:** [[Three.js 크로스 플랫폼 커스텀 셰이더 및 포스트 프로세싱 개발]] +- **Related Topics:** [[WebGPU|WebGPU]], [[WebGL|WebGL]], WGSL, GLSL, Node Material +- **Projects/Contexts:** Three.js 크로스 플랫폼 커스텀 셰이더 및 포스트 프로세싱 개발 - **Contradictions/Notes:** 기존 WebGL 프로젝트에서는 외부 라이브러리인 `pmndrs/postprocessing`이 여전히 훌륭한 선택지로 평가되지만, WebGPU 프로젝트 환경에서는 TSL 노드 기반의 Three.js 네이티브 포스트 프로세싱을 사용하는 것으로 개발 방식이 전환될 것을 권장하고 있습니다 [7]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Three Shader Language (TSL).md]] +- Raw Source: 00_Raw/2026-04-20/Three Shader Language (TSL).md --- diff --git a/01_Archive/2026-04-20/Three.js WebGL Rendering Optimization.md b/01_Archive/2026-04-20/Three.js WebGL Rendering Optimization.md index 61d26209..31d026f0 100644 --- a/01_Archive/2026-04-20/Three.js WebGL Rendering Optimization.md +++ b/01_Archive/2026-04-20/Three.js WebGL Rendering Optimization.md @@ -1,4 +1,4 @@ -# [[Three.js WebGL Rendering Optimization]] +# [[Three.js WebGL Rendering Optimization|Three.js WebGL Rendering Optimization]] ## 📌 Brief Summary Three.js WebGL 렌더링 최적화는 3D 웹 애플리케이션의 프레임 속도를 향상시키고 메모리 사용량을 줄이기 위한 기술적 접근 방식을 의미합니다 [1, 2]. 이 최적화의 핵심은 CPU와 GPU 간의 병목 현상을 유발하는 드로우 콜(Draw Call) 횟수를 최소화하고, 메모리 대역폭을 효율적으로 관리하는 것입니다 [3, 4]. 이를 위해 `InstancedMesh`, `BatchedMesh`, 기하학 병합(Geometry Merging), 텍스처 압축, 그리고 시야 절두체 컬링(Frustum Culling)과 같은 다양한 기법이 활용되며, 2026년 도입된 WebGPU 기술은 컴퓨트 셰이더를 통해 렌더링 한계를 더욱 확장시켰습니다 [3, 5-8]. @@ -27,8 +27,8 @@ Three.js WebGL 렌더링 최적화는 3D 웹 애플리케이션의 프레임 속 * 2026년 기준, WebGL에서 WebGPU(`WebGPURenderer`)로 전환하면 컴퓨트 셰이더(Compute Shaders)를 활용하여 CPU가 처리하던 대규모 파티클 시스템 업데이트, 물리 시뮬레이션 연산 등을 GPU 병렬 처리로 넘겨 비약적인 성능 향상(최대 100배)을 이룰 수 있습니다 [7, 42-45]. ## 🔗 Knowledge Connections -- **Related Topics:** [[Draw Call]], [[InstancedMesh]], [[BatchedMesh]], [[Level of Detail (LOD)]], [[Frustum Culling]], [[WebGPU]] -- **Projects/Contexts:** [[Segments.ai WebGPU Migration]], [[InstancedMesh2 Library]], [[Three.js WebGPURenderer (r171+)]] +- **Related Topics:** [[Draw Call|Draw Call]], [[InstancedMesh|InstancedMesh]], [[BatchedMesh|BatchedMesh]], [[Level of Detail (LOD)|Level of Detail (LOD)]], [[Frustum Culling|Frustum Culling]], [[WebGPU|WebGPU]] +- **Projects/Contexts:** Segments.ai WebGPU Migration, [[InstancedMesh2 library|InstancedMesh2 Library]], Three.js WebGPURenderer (r171+) - **Contradictions/Notes:** - `BatchedMesh`는 다수의 고유 기하학 객체를 단일 드로우 콜로 묶어주는 훌륭한 최적화 도구이지만 [5, 16], 20만 개가 넘는 수준의 과도하게 많은 지오메트리에 적용할 경우 버퍼의 draw "starts" 및 "counts" 데이터를 매 프레임 업데이트해야 하는 오버헤드로 인해 오히려 CPU 사용률이 폭증하고 기존의 Merged Mesh 방식보다 성능이 크게 저하되는 현상이 발생할 수 있습니다 [46-49]. - `InstancedMesh`는 드로우 콜을 혁신적으로 줄여주지만, 인스턴스들이 정렬되지 않아 막대한 오버드로우를 유발하므로, 객체가 겹치는 씬의 경우 여러 개의 개별 Mesh를 공유 속성으로 렌더링하는 것보다 오히려 프레임 속도가 더 떨어지는 역설적인 상황이 발생할 수 있습니다 [30, 31, 50]. diff --git a/01_Archive/2026-04-20/Three.js WebGL 렌더링 최적화.md b/01_Archive/2026-04-20/Three.js WebGL 렌더링 최적화.md index 47fa7d87..6dd87d19 100644 --- a/01_Archive/2026-04-20/Three.js WebGL 렌더링 최적화.md +++ b/01_Archive/2026-04-20/Three.js WebGL 렌더링 최적화.md @@ -1,4 +1,4 @@ -# [[Three.js WebGL 렌더링 최적화]] +# [[Three.js WebGL 렌더링 최적화|Three.js WebGL 렌더링 최적화]] ## 📌 Brief Summary Three.js WebGL 렌더링 최적화는 주로 CPU와 GPU 간의 통신 병목 현상을 유발하는 드로우 콜(Draw Call)을 줄이고, 메모리 및 렌더링 연산 효율을 극대화하는 일련의 과정입니다 [1-6]. 이를 위해 인스턴싱(Instancing), 배칭(Batching), 기하학적 병합, 텍스처/모델 압축 및 LOD(Level of Detail)와 같은 다양한 기법이 복합적으로 적용됩니다 [7-12]. 최적화를 통해 렌더링 프레임 속도를 방어할 수 있으나, 각 기법은 절두체 컬링(Frustum Culling) 정밀도 저하나 오버드로우(Overdraw) 유발과 같은 구조적 한계와 트레이드오프를 가지므로 씬(Scene)의 특성에 맞는 전략적 접근이 필수적입니다 [13-17]. @@ -22,8 +22,8 @@ Three.js WebGL 렌더링 최적화는 주로 CPU와 GPU 간의 통신 병목 현 * 정적 씬에서는 라이트맵과 그림자를 런타임 이전에 베이크(Bake)하여 실시간 연산을 피하는 것이 좋습니다 [49]. ## 🔗 Knowledge Connections -- **Related Topics:** [[드로우 콜 (Draw Call)]], [[InstancedMesh]], [[BatchedMesh]], [[LOD (Level of Detail)]], [[Frustum Culling]], [[Draco 압축]], [[Texture Atlas]], [[WebGPU]] -- **Projects/Contexts:** [[Utsubo Three.js Optimization Tips (2026)]], [[InstancedMesh2 라이브러리]], [[Threedium Image-To-3D WebGL 파이프라인]], [[Three.js Roadmap: Draw Calls]] +- **Related Topics:** 드로우 콜 (Draw Call), [[InstancedMesh|InstancedMesh]], [[BatchedMesh|BatchedMesh]], [[가변적 LOD(Level of Detail) 시스템|LOD (Level of Detail)]], [[Frustum Culling|Frustum Culling]], Draco 압축, [[Texture Atlas|Texture Atlas]], [[WebGPU|WebGPU]] +- **Projects/Contexts:** Utsubo Three.js Optimization Tips (2026), InstancedMesh2 라이브러리, Threedium Image-To-3D WebGL 파이프라인, Three.js Roadmap: Draw Calls - **Contradictions/Notes:** - `InstancedMesh`는 드로우 콜을 혁신적으로 줄여주지만, 자동 정렬 기능이 없고 전체를 렌더링하는 특성 때문에 씬 내 객체들이 중첩될 경우 막대한 오버드로우 연산이 발생하여, 1회 드로우 콜임에도 다수의 개별 메쉬를 렌더링할 때보다 오히려 프레임률(FPS)이 낮아지는 기현상이 발생할 수 있습니다 [13-16, 50]. - `BatchedMesh`는 여러 지오메트리를 하나의 드로우 콜로 모아주어 효율적인 것으로 소개되나, 객체의 가시성을 확인하고 렌더링 순서를 정렬하는 연산 비용이 커 특정 다량의 객체 렌더링 씬에서는 병합 메쉬(Merged Mesh)를 사용할 때보다 CPU 사용량을 치솟게 만들고 30~50% 더 낮은 FPS를 기록하는 성능 병목 현상이 보고되고 있습니다 [28-30, 51, 52]. diff --git a/01_Archive/2026-04-20/Three.js WebGPU 파티클 예제.md b/01_Archive/2026-04-20/Three.js WebGPU 파티클 예제.md index cd51f03f..f424b89e 100644 --- a/01_Archive/2026-04-20/Three.js WebGPU 파티클 예제.md +++ b/01_Archive/2026-04-20/Three.js WebGPU 파티클 예제.md @@ -1,4 +1,4 @@ -# [[Three.js WebGPU 파티클 예제]] +# [[Three.js WebGPU 파티클 예제|Three.js WebGPU 파티클 예제]] ## 📌 Brief Summary Three.js에서 전통적인 CPU 기반의 파티클 업데이트는 약 5만 개 수준에서 병목 현상이 발생하지만, WebGPU 컴퓨트 셰이더를 활용하면 이를 수백만 개 단위로 확장할 수 있습니다 [1]. WebGPU 파티클 예제들은 `instancedArray`와 같은 GPU 영구 버퍼를 사용하여 CPU와 GPU 간의 데이터 전송 부하를 제거하는 방식을 보여줍니다 [1]. 이러한 최적화 기술은 Expo 2025 Osaka와 같은 실제 프로젝트에서 100만 개의 파티클을 지연 없이 실시간으로 렌더링하는 데 성공적으로 적용되었습니다 [2, 3]. @@ -10,8 +10,8 @@ Three.js에서 전통적인 CPU 기반의 파티클 업데이트는 약 5만 개 * **컴퓨트 셰이더의 연산 확장성:** 파티클 렌더링 외에도 물리 연산, 충돌 감지, 실시간 데이터 필터링 등 연산 집약적인 작업들은 WebGPU 컴퓨트 셰이더를 통해 수천 개의 GPU 코어에서 병렬로 처리될 수 있습니다 [4, 5]. ## 🔗 Knowledge Connections -- **Related Topics:** [[WebGPU Compute Shaders]], [[instancedArray]] -- **Projects/Contexts:** [[Expo 2025 Osaka]], [[Waves of Connection]] +- **Related Topics:** [[WebGPU Compute Shaders|WebGPU Compute Shaders]], [[instancedArray|instancedArray]] +- **Projects/Contexts:** [[Expo 2025 Osaka|Expo 2025 Osaka]], [[Waves of Connection|Waves of Connection]] - **Contradictions/Notes:** 소스 내용에 따르면, WebGPU 파티클 예제는 WebGL 기반의 단일 스레드 CPU 처리 한계(약 5만 개)를 극복하기 위해 컴퓨트 셰이더 연산과 영구적인 GPU 데이터 할당 구조를 결합하여 수십 배 이상의 파티클을 렌더링할 수 있는 방향으로 발전하고 있습니다 [1, 5, 6]. --- diff --git a/01_Archive/2026-04-20/Three.js WebGPURenderer.md b/01_Archive/2026-04-20/Three.js WebGPURenderer.md index bcbb8046..b2dcdaf4 100644 --- a/01_Archive/2026-04-20/Three.js WebGPURenderer.md +++ b/01_Archive/2026-04-20/Three.js WebGPURenderer.md @@ -1,4 +1,4 @@ -# [[Three.js WebGPURenderer]] +# [[Three.js WebGPURenderer|Three.js WebGPURenderer]] ## 📌 Brief Summary Three.js WebGPURenderer는 2025년 r171 버전부터 프로덕션 환경에 도입된 그래픽 렌더러로, 브라우저가 3D 그래픽을 처리하는 방식에 근본적인 전환을 가져왔습니다 [1-3]. 복잡한 설정 없이 `three/webgpu`에서 모듈을 불러와 사용할 수 있으며, 브라우저가 WebGPU를 지원하지 않을 경우 자동으로 WebGL 2로 대체(fallback)되는 기능을 제공합니다 [2, 4, 5]. 드로우 콜(Draw call)이 많은 장면이나 컴퓨트 셰이더(Compute Shader)가 필요한 복잡한 효과에서 기존 대비 2~10배 이상의 성능 향상을 가능하게 합니다 [5, 6]. @@ -14,8 +14,8 @@ Three.js WebGPURenderer는 2025년 r171 버전부터 프로덕션 환경에 도 WebGPURenderer는 렌더 루프 과정에서 불필요한 객체 할당을 제거하여 가비지 컬렉터 부하를 방지하고, 리소스를 바인드 그룹(Bind group)으로 묶어 배치(Batch) 처리하는 구조를 채택하여 성능을 최적화했습니다 [11, 16]. 실제로 3D 데이터 플랫폼인 Segments.ai는 이 렌더러로 마이그레이션하여 수백만 개의 포인트 클라우드를 렌더링할 때 100배의 성능 향상을 거두었습니다 [17, 18]. ## 🔗 Knowledge Connections -- **Related Topics:** [[TSL (Three Shader Language)]], [[Compute Shaders]], [[WebGL 2 fallback]] -- **Projects/Contexts:** [[Segments.ai]], [[Expo 2025 Osaka]] +- **Related Topics:** [[TSL (Three Shader Language)|TSL (Three Shader Language)]], [[Compute Shaders|Compute Shaders]], WebGL 2 fallback +- **Projects/Contexts:** [[Segments.ai|Segments.ai]], [[Expo 2025 Osaka|Expo 2025 Osaka]] - **Contradictions/Notes:** 소스는 WebGPU가 분명한 성능 우위를 제공하지만, 기존의 WebGL 기반 프로젝트가 이미 60fps로 부드럽게 실행되고 있으며 성능 한계에 부딪히지 않았다면 무리해서 시급히 마이그레이션할 필요는 없다고 조언합니다 [9, 19, 20]. --- diff --git a/01_Archive/2026-04-20/Three.js 대규모 렌더링 최적화 파이프라인.md b/01_Archive/2026-04-20/Three.js 대규모 렌더링 최적화 파이프라인.md index 2c5affa7..aae98d19 100644 --- a/01_Archive/2026-04-20/Three.js 대규모 렌더링 최적화 파이프라인.md +++ b/01_Archive/2026-04-20/Three.js 대규모 렌더링 최적화 파이프라인.md @@ -1,4 +1,4 @@ -# [[Three.js 대규모 렌더링 최적화 파이프라인]] +# [[Three.js 대규모 렌더링 최적화 파이프라인|Three.js 대규모 렌더링 최적화 파이프라인]] ## 📌 Brief Summary Three.js 대규모 렌더링 최적화 파이프라인은 수많은 3D 객체를 브라우저 환경에서 매끄럽게 렌더링하기 위해 CPU와 GPU 간의 통신 오버헤드, 즉 드로우 콜(Draw Call)과 메모리 병목 현상을 극복하는 일련의 기술적 아키텍처입니다 [1, 2]. 주로 InstancedMesh와 BatchedMesh를 통한 드로우 콜 최소화, Draco 및 KTX2 등을 이용한 에셋 압축, 절두체 컬링(Frustum Culling) 및 LOD 시스템을 활용하여 그래픽 자원의 낭비를 줄입니다 [3-6]. 최근에는 WebGPU와 컴퓨트 셰이더(Compute Shader)가 도입되어 렌더링 제어 및 가시성 판단 연산을 GPU로 대거 이관함으로써, 더욱 막대한 규모의 씬을 유연하게 처리할 수 있는 차세대 파이프라인으로 진화하고 있습니다 [7-9]. @@ -10,8 +10,8 @@ Three.js 대규모 렌더링 최적화 파이프라인은 수많은 3D 객체를 - **WebGPU 기반 차세대 렌더링 파이프라인:** 2026년 기준, Three.js(r171 이상)의 `WebGPURenderer` 및 TSL(Three Shader Language) 도입으로 대규모 렌더링 구조가 혁신적으로 변화했습니다 [7, 30]. 일반적인 CPU 한계를 초과하던 100만 개 이상의 파티클 연산, 물리 시뮬레이션, 복잡한 군중 애니메이션 등을 컴퓨트 셰이더(Compute Shader)를 통한 GPU-driven Rendering으로 병렬 처리할 수 있게 되었습니다 [31-34]. Native WebGPU 수준에서는 `GPURenderBundles` 및 Indirect Drawing 기술을 통해 500MB 이상의 초대형 건설/BIM 데이터셋에서도 강력한 성능 향상을 이끌어냅니다 [35, 36]. ## 🔗 Knowledge Connections -- **Related Topics:** `[[InstancedMesh]]`, `[[BatchedMesh]]`, `[[WebGPU]]`, `[[Draw Call (드로우 콜)]]`, `[[Frustum Culling (절두체 컬링)]]`, `[[LOD (Level of Detail)]]`, `[[Overdraw (오버드로우)]]`, `[[Compute Shader (컴퓨트 셰이더)]]` -- **Projects/Contexts:** `[[InstancedMesh2 (agargaro)]]`, `[[Three.js r171 WebGPURenderer]]`, `[[Segments.ai]]`, `[[Fragment (IFC.js)]]` +- **Related Topics:** `[[InstancedMesh|InstancedMesh]]`, `[[BatchedMesh|BatchedMesh]]`, `[[WebGPU|WebGPU]]`, `Draw Call (드로우 콜)`, `Frustum Culling (절두체 컬링)`, `[[가변적 LOD(Level of Detail) 시스템|LOD (Level of Detail)]]`, `Overdraw (오버드로우)`, `Compute Shader (컴퓨트 셰이더)` +- **Projects/Contexts:** `InstancedMesh2 (agargaro)`, `Three.js r171 WebGPURenderer`, `[[Segments.ai|Segments.ai]]`, `Fragment (IFC.js)` - **Contradictions/Notes:** - `InstancedMesh`는 드로우 콜을 줄여 성능을 크게 향상시키도록 설계되었으나, 불투명도 및 복잡한 셰이더 환경에서는 인스턴스 정렬 부재로 인한 심각한 오버드로우(Overdraw)를 유발해 일반 개별 Mesh(Shared attributes)를 사용할 때보다 프레임 레이트(FPS)가 오히려 낮아지는 역설적인 사례가 보고되고 있습니다 [18, 19]. - `BatchedMesh` 역시 다수의 기하학적 구조를 통합하는 유용한 기술이지만, 약 20만 개 수준의 대량 지오메트리에 적용할 시 버퍼 데이터 업로드 등의 이유로 CPU 사용량이 30~50% 급증하며 병합된 기하학(Merged Geometry)보다 현저히 성능이 하락하는 구조적 병목이 제기되고 있습니다 [37-39]. diff --git a/01_Archive/2026-04-20/Three.js 렌더링 성능 최적화.md b/01_Archive/2026-04-20/Three.js 렌더링 성능 최적화.md index decf1e2f..b1c296b6 100644 --- a/01_Archive/2026-04-20/Three.js 렌더링 성능 최적화.md +++ b/01_Archive/2026-04-20/Three.js 렌더링 성능 최적화.md @@ -1,4 +1,4 @@ -# [[Three.js 렌더링 성능 최적화]] +# [[Three.js 렌더링 성능 최적화|Three.js 렌더링 성능 최적화]] ## 📌 Brief Summary Three.js 렌더링 성능 최적화는 브라우저 환경에서 3D 씬을 부드럽게 렌더링하기 위해 CPU와 GPU 간의 병목 현상을 줄이고 하드웨어 자원의 효율성을 극대화하는 일련의 기법을 의미합니다. 가장 핵심적인 목표는 CPU 오버헤드를 유발하는 드로우 콜(Draw Call) 횟수를 프레임당 100회 미만으로 유지하는 것이며, 이를 위해 인스턴싱(Instancing)과 배칭(Batching) 같은 기술이 필수적으로 사용됩니다 [1-5]. 또한, 에셋 압축, 메모리 관리, 셰이더 및 시야 절두체 컬링(Frustum Culling) 조정, WebGPU와 컴퓨트 셰이더의 도입 등을 통해 전반적인 연산 부하를 다각도로 최적화합니다 [1, 6-8]. @@ -23,8 +23,8 @@ Three.js 렌더링 성능 최적화는 브라우저 환경에서 3D 씬을 부 * TSL (Three Shader Language)을 사용하면 WGSL(WebGPU)과 GLSL(WebGL) 양쪽 모두에서 호환되는 크로스 플랫폼 커스텀 셰이더를 구축할 수 있습니다 [50, 51]. ## 🔗 Knowledge Connections -- **Related Topics:** [[드로우 콜 (Draw Call)]], [[InstancedMesh]], [[BatchedMesh]], [[LOD (Level of Detail)]], [[WebGPU]] -- **Projects/Contexts:** [[Three.js r171 WebGPU 도입]], [[IFC.js Fragment 아키텍처]], [[InstancedMesh2 라이브러리]] +- **Related Topics:** 드로우 콜 (Draw Call), [[InstancedMesh|InstancedMesh]], [[BatchedMesh|BatchedMesh]], [[가변적 LOD(Level of Detail) 시스템|LOD (Level of Detail)]], [[WebGPU|WebGPU]] +- **Projects/Contexts:** Three.js r171 WebGPU 도입, IFC.js Fragment 아키텍처, InstancedMesh2 라이브러리 - **Contradictions/Notes:** 다양한 지오메트리를 한 번에 렌더링하기 위해 제안된 `BatchedMesh`는 드로우 콜 최적화의 훌륭한 대안으로 소개되지만[18], 다른 소스에서는 1,000만 개가 넘는 트라이앵글 환경에서 인스턴싱 또는 일반 `Merged Mesh`보다 CPU 점유율을 비정상적으로 높이고 프레임률을 크게 떨어뜨리는 심각한 구조적 오버헤드가 있음을 상반되게 지적하고 있습니다[19-22]. 또한 `InstancedMesh` 역시 만능이 아니며 정렬의 부재로 인해 발생하는 심각한 오버드로우(Overdraw) 때문에 일반 메쉬 렌더링보다 느려지는 병목 사례가 보고되고 있습니다[13, 14]. --- diff --git a/01_Archive/2026-04-20/Three.js 렌더링 최적화.md b/01_Archive/2026-04-20/Three.js 렌더링 최적화.md index 8496b87d..12c1edbb 100644 --- a/01_Archive/2026-04-20/Three.js 렌더링 최적화.md +++ b/01_Archive/2026-04-20/Three.js 렌더링 최적화.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AI-046 -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.97 tags: [three.js, webgl, rendering, optimization] last_reinforced: 2026-06-XX github_commit: "[P-Reinforce] Processed Three.js WebGL 렌더링 최적화." --- -# [[Three.js 렌더링 최적화]] (이전 배치와 동일한 내용) +# [[Three.js 렌더링 최적화|Three.js 렌더링 최적화]] (이전 배치와 동일한 내용) ## 📌 한 줄 통찰 (The Karpathy Summary) > 대규모 웹 환경에서 WebGL 기반 3D 씬을 구현할 때, 단순한 모델 로딩 이상의 관점에서 드로우 콜 감소, 자원 재활용, 그리고 GPU/CPU 부하 분산을 통해 성능 병목을 해결하는 것이 핵심이다. @@ -23,7 +23,7 @@ github_commit: "[P-Reinforce] Processed Three.js WebGL 렌더링 최적화." - **정책 변화:** WebGPU의 도입은 기존 WebGL의 한계를 뛰어넘는 가장 중요한 패러다임 전환점이며, 이를 활용한 컴퓨팅 기능(Compute Shader)이 핵심 트렌드로 부상 중이다. ## 🔗 지식 연결 (Graph) -- Parent: [[WebGL Optimization]] -- Related: [[InstancedMesh]] , [[Draw Call Optimization]] , [[WebGPU]] -- Raw Source: [[00_Raw/Three.js WebGL 렌더링 최적화.md]] +- Parent: [[WebGL Optimization|WebGL Optimization]] +- Related: [[InstancedMesh|InstancedMesh]] , [[Draw Call Optimization|Draw Call Optimization]] , [[WebGPU|WebGPU]] +- Raw Source: 00_Raw/Three.js WebGL 렌더링 최적화.md --- \ No newline at end of file diff --git a/01_Archive/2026-04-20/Three.js 모바일 렌더링 최적화.md b/01_Archive/2026-04-20/Three.js 모바일 렌더링 최적화.md index 0c79e006..26005a3c 100644 --- a/01_Archive/2026-04-20/Three.js 모바일 렌더링 최적화.md +++ b/01_Archive/2026-04-20/Three.js 모바일 렌더링 최적화.md @@ -1,4 +1,4 @@ -# [[Three.js 모바일 렌더링 최적화]] +# [[Three.js 모바일 렌더링 최적화|Three.js 모바일 렌더링 최적화]] ## 📌 Brief Summary Three.js 모바일 렌더링 최적화는 제한된 컴퓨팅 파워, 메모리 대역폭 및 배터리 용량을 가진 모바일 기기 환경에서 3D 장면을 원활하게 구동하기 위한 일련의 기술적 접근이다. 이 최적화는 셰이더 정밀도 조절, 텍스처 및 폴리곤 수 제한, 드로우 콜(Draw Call) 감소, 배터리 절약을 위한 렌더링 루프 제어 등을 포함한다 [1-4]. 이를 통해 모바일 브라우저에서도 60fps의 안정적인 프레임 속도를 유지하고 메모리 한계로 인한 애플리케이션 크래시를 방지할 수 있다 [5, 6]. @@ -26,8 +26,8 @@ Three.js 모바일 렌더링 최적화는 제한된 컴퓨팅 파워, 메모리 * 모바일 환경에서는 WebGL 컨텍스트 손실(Context lost)이 발생할 수 있으므로, 리스너(`webglcontextlost`)를 등록하여 이를 감지하고 우아하게 복구하는(gracefully recover) 예외 처리가 필수적이다 [11]. ## 🔗 Knowledge Connections -- **Related Topics:** [[드로우 콜 최적화 (Draw Call Optimization)]], [[텍스처 압축 (Texture Compression)]], [[셰이더 정밀도 (Shader Precision)]], [[가비지 컬렉션 (Garbage Collection)]] -- **Projects/Contexts:** [[React Three Fiber (R3F)]], [[Basis Universal / KTX2]] +- **Related Topics:** 드로우 콜 최적화 (Draw Call Optimization), 텍스처 압축 (Texture Compression), 셰이더 정밀도 (Shader Precision), [[가비지 컬렉션 (Garbage Collection)|가비지 컬렉션 (Garbage Collection)]] +- **Projects/Contexts:** [[React Three Fiber (R3F)|React Three Fiber (R3F)]], Basis Universal / KTX2 - **Contradictions/Notes:** 소스에서는 모바일 환경 구현 시 시각적 품질과 성능 간의 직접적인 타협(trade-off)을 강조한다. 데스크톱 환경에서는 다중 텍스처 파일과 MSAA, 4096 크기의 섀도우 맵 활용이 가능하지만, 모바일 기기에서는 동일한 구성을 유지할 경우 프레임 속도 저하와 발열, 메모리 부족으로 인한 강제 종료를 유발할 수 있으므로 극단적인 간소화(FXAA, 아틀라스 텍스처, 512~1024 섀도우 등)를 필수적으로 도입해야 함을 명시한다 [5, 6, 10]. --- diff --git a/01_Archive/2026-04-20/Three.js 성능 최적화.md b/01_Archive/2026-04-20/Three.js 성능 최적화.md index b1fee080..034f4a52 100644 --- a/01_Archive/2026-04-20/Three.js 성능 최적화.md +++ b/01_Archive/2026-04-20/Three.js 성능 최적화.md @@ -1,4 +1,4 @@ -# [[Three.js 성능 최적화]] +# [[Three.js 성능 최적화|Three.js 성능 최적화]] ## 📌 Brief Summary Three.js 성능 최적화는 CPU와 GPU 간의 통신 병목 현상을 유발하는 드로우 콜(Draw Call)을 줄이고 렌더링 파이프라인의 효율을 극대화하여 높은 프레임 속도를 유지하는 과정이다 [1-3]. 주로 `InstancedMesh` 및 `BatchedMesh`를 활용한 인스턴싱/배칭 기법, 텍스처와 지오메트리 압축, 프러스텀 컬링(Frustum Culling) 및 LOD(Level of Detail) 기법이 핵심적으로 사용된다 [4-9]. 최근에는 WebGL의 구조적 한계를 극복하기 위해 WebGPU와 컴퓨트 셰이더를 기반으로 한 GPU 주도 렌더링(GPU-driven Rendering) 기술로 발전하고 있다 [10, 11]. @@ -27,8 +27,8 @@ Three.js 성능 최적화는 CPU와 GPU 간의 통신 병목 현상을 유발하 * 컴퓨트 셰이더를 활용하면 CPU에서 처리하던 충돌 감지, 지형 생성, 수백만 개의 파티클 업데이트 및 컬링을 GPU에서 병렬로 직접 수행할 수 있어 극적인 성능 향상을 이룰 수 있다 [35-37]. ## 🔗 Knowledge Connections -- **Related Topics:** [[InstancedMesh]], [[BatchedMesh]], [[WebGPU]], [[드로우 콜 (Draw Call)]], [[LOD (Level of Detail)]] -- **Projects/Contexts:** [[Utsubo의 WebGPU 도입 (Segments.ai 등)]], [[InstancedMesh2 라이브러리]], [[Three.js r171 WebGPURenderer]] +- **Related Topics:** [[InstancedMesh|InstancedMesh]], [[BatchedMesh|BatchedMesh]], [[WebGPU|WebGPU]], 드로우 콜 (Draw Call), [[가변적 LOD(Level of Detail) 시스템|LOD (Level of Detail)]] +- **Projects/Contexts:** Utsubo의 WebGPU 도입 (Segments.ai 등), InstancedMesh2 라이브러리, Three.js r171 WebGPURenderer - **Contradictions/Notes:** 드로우 콜을 줄이기 위해 `InstancedMesh`나 `BatchedMesh`를 도입하더라도 항상 성능이 향상되는 것은 아니다. `InstancedMesh`는 개별 컬링의 부재와 오버드로우로 인해 오히려 개별 렌더링보다 GPU FPS를 떨어뜨릴 수 있다는 점이 지적된다 [27, 30, 38]. 또한 `BatchedMesh`의 경우에도 천만 개 이상의 많은 폴리곤과 지오메트리를 처리할 때는 내부적인 다중 그리기(multi-draw) 버퍼 업로드 및 패킹 오버헤드로 인해 CPU 점유율이 40~60%까지 치솟고 프레임이 급감하는 현상이 보고되어, 상황에 따른 벤치마킹이 필수적이다 [39-43]. --- diff --git a/01_Archive/2026-04-20/Three.js.md b/01_Archive/2026-04-20/Three.js.md index a0ec80a2..30b743c3 100644 --- a/01_Archive/2026-04-20/Three.js.md +++ b/01_Archive/2026-04-20/Three.js.md @@ -1,4 +1,4 @@ -# [[Three.js]] +# [[Three.js|Three.js]] ## 📌 Brief Summary Three.js는 WebGL 및 WebGPU를 사용하여 웹 브라우저에서 애니메이션 3D 컴퓨터 그래픽스를 생성하고 표시할 수 있도록 지원하는 크로스 브라우저 자바스크립트 라이브러리이자 API이다 [1, 2]. 브라우저, GPU, 자바스크립트 간의 복잡한 상호작용을 추상화하여 개발자가 고성능의 3D 환경을 쉽게 구축할 수 있도록 돕는다 [3]. 2026년을 기점으로 프로덕션 수준의 WebGPU 렌더러와 TSL(Three Shader Language)이 도입되면서, 단순한 시각화를 넘어 수백만 개의 파티클 연산이나 대규모 CAD 모델 처리까지 가능한 고성능 플랫폼으로 진화했다 [4-7]. @@ -17,8 +17,8 @@ Three.js는 WebGL 및 WebGPU를 사용하여 웹 브라우저에서 애니메이 사용자의 마우스나 터치 입력을 통한 화면 상의 3D 객체 선택(피킹)은 `Raycaster` 객체를 통해 수행된다 [35, 36]. 하지만 `InstancedMesh`에서 개별 인스턴스의 행렬(위치/회전/축척)을 동적으로 변경할 경우, 레이캐스팅이 정상 작동하려면 변경 직후 반드시 `.computeBoundingSphere()` 및 `.computeBoundingBox()`를 호출하여 바운딩 볼륨을 갱신해야 한다 [37, 38]. 다량의 인스턴스가 존재하는 환경에서 충돌 및 선택의 속도를 높이려면 `three-mesh-bvh` 같은 공간 분할(Spatial Indexing) 라이브러리를 활용하는 것이 권장된다 [39, 40]. ## 🔗 Knowledge Connections -- **Related Topics:** [[WebGPU]], [[InstancedMesh]], [[BatchedMesh]], [[TSL (Three Shader Language)]], [[Raycaster]], [[LOD (Level of Detail)]] -- **Projects/Contexts:** [[React Three Fiber (R3F)]], [[IFC.js]], [[InstancedMesh2]] +- **Related Topics:** [[WebGPU|WebGPU]], [[InstancedMesh|InstancedMesh]], [[BatchedMesh|BatchedMesh]], [[TSL (Three Shader Language)|TSL (Three Shader Language)]], [[Raycaster|Raycaster]], [[가변적 LOD(Level of Detail) 시스템|LOD (Level of Detail)]] +- **Projects/Contexts:** [[React Three Fiber (R3F)|React Three Fiber (R3F)]], [[IFC.js|IFC.js]], [[InstancedMesh2|InstancedMesh2]] - **Contradictions/Notes:** 일반적으로 `InstancedMesh`는 드로우 콜을 1회로 줄여 렌더링 성능을 획기적으로 높인다고 알려져 있으나, 인스턴스의 자동 정렬 기능이 없어 오버드로우(Overdraw)가 빈번하게 발생할 경우 단일 메쉬를 분할하여 그릴 때보다 오히려 프레임 속도(FPS)가 급락할 수 있습니다 [4, 31-33]. 또한 여러 다른 지오메트리를 하나의 렌더 호출로 묶어주는 `BatchedMesh` 역시, 지나치게 많은 수의 정점과 데이터를 렌더링할 경우 패킹 및 컬링 연산 때문에 극심한 CPU 과부하와 성능 저하를 야기할 수 있다는 한계가 보고되고 있습니다 [41, 42]. --- diff --git a/01_Archive/2026-04-20/Threejs WebGL Rendering Optimization.md b/01_Archive/2026-04-20/Threejs WebGL Rendering Optimization.md index a5099969..9ec4c6b4 100644 --- a/01_Archive/2026-04-20/Threejs WebGL Rendering Optimization.md +++ b/01_Archive/2026-04-20/Threejs WebGL Rendering Optimization.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-46187E -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Threejs WebGL Rendering Optimization" --- -# [[Threejs WebGL Rendering Optimization]] +# [[Threejs WebGL Rendering Optimization|Threejs WebGL Rendering Optimization]] ## 📌 한 줄 통찰 (The Karpathy Summary) > Three.js WebGL 렌더링 최적화는 3D 웹 애플리케이션의 프레임 속도를 향상시키고 메모리 사용량을 줄이기 위한 기술적 접근 방식을 의미합니다 [1, 2]. 이 최적화의 핵심은 CPU와 GPU 간의 병목 현상을 유발하는 드로우 콜(Draw Call) 횟수를 최소화하고, 메모리 대역폭을 효율적으로 관리하는 것입니다 [3, 4]. 이를 위해 `InstancedMesh`, `BatchedMesh`, 기하학 병합(Geometry Merging), 텍스처 압축, 그리고 시야 절두체 컬링(Frustum Culling)과 같은 다양한 기법이 활용되며, 2026년 도입된 WebGPU 기술은 컴퓨트 셰이더를 통해 렌더링 한계를 더욱 확장시켰습니다 [3, 5-8]. @@ -39,13 +39,13 @@ github_commit: "[P-Reinforce] Continuous Worker - Threejs WebGL Rendering Optimi - **정책 변화:** Graphics & Performance 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Draw Call]], [[InstancedMesh]], [[BatchedMesh]], [[Level of Detail (LOD)]], [[Frustum Culling]], [[WebGPU]] -- **Projects/Contexts:** [[Segments.ai WebGPU Migration]], [[InstancedMesh2 Library]], [[Three.js WebGPURenderer (r171+)]] +- **Related Topics:** [[Draw Call|Draw Call]], [[InstancedMesh|InstancedMesh]], [[BatchedMesh|BatchedMesh]], [[Level of Detail (LOD)|Level of Detail (LOD)]], [[Frustum Culling|Frustum Culling]], [[WebGPU|WebGPU]] +- **Projects/Contexts:** Segments.ai WebGPU Migration, [[InstancedMesh2 library|InstancedMesh2 Library]], Three.js WebGPURenderer (r171+) - **Contradictions/Notes:** - `BatchedMesh`는 다수의 고유 기하학 객체를 단일 드로우 콜로 묶어주는 훌륭한 최적화 도구이지만 [5, 16], 20만 개가 넘는 수준의 과도하게 많은 지오메트리에 적용할 경우 버퍼의 draw "starts" 및 "counts" 데이터를 매 프레임 업데이트해야 하는 오버헤드로 인해 오히려 CPU 사용률이 폭증하고 기존의 Merged Mesh 방식보다 성능이 크게 저하되는 현상이 발생할 수 있습니다 [46-49]. - `InstancedMesh`는 드로우 콜을 혁신적으로 줄여주지만, 인스턴스들이 정렬되지 않아 막대한 오버드로우를 유발하므로, 객체가 겹치는 씬의 경우 여러 개의 개별 Mesh를 공유 속성으로 렌더링하는 것보다 오히려 프레임 속도가 더 떨어지는 역설적인 상황이 발생할 수 있습니다 [30, 31, 50]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Three.js WebGL Rendering Optimization.md]] +- Raw Source: 00_Raw/2026-04-20/Three.js WebGL Rendering Optimization.md --- diff --git a/01_Archive/2026-04-20/Threejs WebGL 렌더링 최적화.md b/01_Archive/2026-04-20/Threejs WebGL 렌더링 최적화.md index d65c7bb0..46eee419 100644 --- a/01_Archive/2026-04-20/Threejs WebGL 렌더링 최적화.md +++ b/01_Archive/2026-04-20/Threejs WebGL 렌더링 최적화.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-FE50FB -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Threejs WebGL 렌더링 최적화" --- -# [[Threejs WebGL 렌더링 최적화]] +# [[Threejs WebGL 렌더링 최적화|Threejs WebGL 렌더링 최적화]] ## 📌 한 줄 통찰 (The Karpathy Summary) > Three.js WebGL 렌더링 최적화는 주로 CPU와 GPU 간의 통신 병목 현상을 유발하는 드로우 콜(Draw Call)을 줄이고, 메모리 및 렌더링 연산 효율을 극대화하는 일련의 과정입니다 [1-6]. 이를 위해 인스턴싱(Instancing), 배칭(Batching), 기하학적 병합, 텍스처/모델 압축 및 LOD(Level of Detail)와 같은 다양한 기법이 복합적으로 적용됩니다 [7-12]. 최적화를 통해 렌더링 프레임 속도를 방어할 수 있으나, 각 기법은 절두체 컬링(Frustum Culling) 정밀도 저하나 오버드로우(Overdraw) 유발과 같은 구조적 한계와 트레이드오프를 가지므로 씬(Scene)의 특성에 맞는 전략적 접근이 필수적입니다 [13-17]. @@ -35,13 +35,13 @@ github_commit: "[P-Reinforce] Continuous Worker - Threejs WebGL 렌더링 최적 - **정책 변화:** AI 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[드로우 콜 (Draw Call)]], [[InstancedMesh]], [[BatchedMesh]], [[LOD (Level of Detail)]], [[Frustum Culling]], [[Draco 압축]], [[Texture Atlas]], [[WebGPU]] -- **Projects/Contexts:** [[Utsubo Three.js Optimization Tips (2026)]], [[InstancedMesh2 라이브러리]], [[Threedium Image-To-3D WebGL 파이프라인]], [[Three.js Roadmap: Draw Calls]] +- **Related Topics:** 드로우 콜 (Draw Call), [[InstancedMesh|InstancedMesh]], [[BatchedMesh|BatchedMesh]], [[가변적 LOD(Level of Detail) 시스템|LOD (Level of Detail)]], [[Frustum Culling|Frustum Culling]], Draco 압축, [[Texture Atlas|Texture Atlas]], [[WebGPU|WebGPU]] +- **Projects/Contexts:** Utsubo Three.js Optimization Tips (2026), InstancedMesh2 라이브러리, Threedium Image-To-3D WebGL 파이프라인, Three.js Roadmap: Draw Calls - **Contradictions/Notes:** - `InstancedMesh`는 드로우 콜을 혁신적으로 줄여주지만, 자동 정렬 기능이 없고 전체를 렌더링하는 특성 때문에 씬 내 객체들이 중첩될 경우 막대한 오버드로우 연산이 발생하여, 1회 드로우 콜임에도 다수의 개별 메쉬를 렌더링할 때보다 오히려 프레임률(FPS)이 낮아지는 기현상이 발생할 수 있습니다 [13-16, 50]. - `BatchedMesh`는 여러 지오메트리를 하나의 드로우 콜로 모아주어 효율적인 것으로 소개되나, 객체의 가시성을 확인하고 렌더링 순서를 정렬하는 연산 비용이 커 특정 다량의 객체 렌더링 씬에서는 병합 메쉬(Merged Mesh)를 사용할 때보다 CPU 사용량을 치솟게 만들고 30~50% 더 낮은 FPS를 기록하는 성능 병목 현상이 보고되고 있습니다 [28-30, 51, 52]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Three.js WebGL 렌더링 최적화.md]] +- Raw Source: 00_Raw/2026-04-20/Three.js WebGL 렌더링 최적화.md --- diff --git a/01_Archive/2026-04-20/Threejs WebGPU 파티클 예제.md b/01_Archive/2026-04-20/Threejs WebGPU 파티클 예제.md index 42b4651d..b9684be6 100644 --- a/01_Archive/2026-04-20/Threejs WebGPU 파티클 예제.md +++ b/01_Archive/2026-04-20/Threejs WebGPU 파티클 예제.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-A9D3D4 -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Threejs WebGPU 파티클 예제" --- -# [[Threejs WebGPU 파티클 예제]] +# [[Threejs WebGPU 파티클 예제|Threejs WebGPU 파티클 예제]] ## 📌 한 줄 통찰 (The Karpathy Summary) > Three.js에서 전통적인 CPU 기반의 파티클 업데이트는 약 5만 개 수준에서 병목 현상이 발생하지만, WebGPU 컴퓨트 셰이더를 활용하면 이를 수백만 개 단위로 확장할 수 있습니다 [1]. WebGPU 파티클 예제들은 `instancedArray`와 같은 GPU 영구 버퍼를 사용하여 CPU와 GPU 간의 데이터 전송 부하를 제거하는 방식을 보여줍니다 [1]. 이러한 최적화 기술은 Expo 2025 Osaka와 같은 실제 프로젝트에서 100만 개의 파티클을 지연 없이 실시간으로 렌더링하는 데 성공적으로 적용되었습니다 [2, 3]. @@ -23,11 +23,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Threejs WebGPU 파티클 예 - **정책 변화:** Graphics & Performance 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[WebGPU Compute Shaders]], [[instancedArray]] -- **Projects/Contexts:** [[Expo 2025 Osaka]], [[Waves of Connection]] +- **Related Topics:** [[WebGPU Compute Shaders|WebGPU Compute Shaders]], [[instancedArray|instancedArray]] +- **Projects/Contexts:** [[Expo 2025 Osaka|Expo 2025 Osaka]], [[Waves of Connection|Waves of Connection]] - **Contradictions/Notes:** 소스 내용에 따르면, WebGPU 파티클 예제는 WebGL 기반의 단일 스레드 CPU 처리 한계(약 5만 개)를 극복하기 위해 컴퓨트 셰이더 연산과 영구적인 GPU 데이터 할당 구조를 결합하여 수십 배 이상의 파티클을 렌더링할 수 있는 방향으로 발전하고 있습니다 [1, 5, 6]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Three.js WebGPU 파티클 예제.md]] +- Raw Source: 00_Raw/2026-04-20/Three.js WebGPU 파티클 예제.md --- diff --git a/01_Archive/2026-04-20/Threejs WebGPURenderer.md b/01_Archive/2026-04-20/Threejs WebGPURenderer.md index 92cb20e2..02a8af82 100644 --- a/01_Archive/2026-04-20/Threejs WebGPURenderer.md +++ b/01_Archive/2026-04-20/Threejs WebGPURenderer.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-2EFC4E -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Threejs WebGPURenderer" --- -# [[Threejs WebGPURenderer]] +# [[Threejs WebGPURenderer|Threejs WebGPURenderer]] ## 📌 한 줄 통찰 (The Karpathy Summary) > Three.js WebGPURenderer는 2025년 r171 버전부터 프로덕션 환경에 도입된 그래픽 렌더러로, 브라우저가 3D 그래픽을 처리하는 방식에 근본적인 전환을 가져왔습니다 [1-3]. 복잡한 설정 없이 `three/webgpu`에서 모듈을 불러와 사용할 수 있으며, 브라우저가 WebGPU를 지원하지 않을 경우 자동으로 WebGL 2로 대체(fallback)되는 기능을 제공합니다 [2, 4, 5]. 드로우 콜(Draw call)이 많은 장면이나 컴퓨트 셰이더(Compute Shader)가 필요한 복잡한 효과에서 기존 대비 2~10배 이상의 성능 향상을 가능하게 합니다 [5, 6]. @@ -27,11 +27,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Threejs WebGPURenderer" - **정책 변화:** AI 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[TSL (Three Shader Language)]], [[Compute Shaders]], [[WebGL 2 fallback]] -- **Projects/Contexts:** [[Segments.ai]], [[Expo 2025 Osaka]] +- **Related Topics:** [[TSL (Three Shader Language)|TSL (Three Shader Language)]], [[Compute Shaders|Compute Shaders]], WebGL 2 fallback +- **Projects/Contexts:** [[Segments.ai|Segments.ai]], [[Expo 2025 Osaka|Expo 2025 Osaka]] - **Contradictions/Notes:** 소스는 WebGPU가 분명한 성능 우위를 제공하지만, 기존의 WebGL 기반 프로젝트가 이미 60fps로 부드럽게 실행되고 있으며 성능 한계에 부딪히지 않았다면 무리해서 시급히 마이그레이션할 필요는 없다고 조언합니다 [9, 19, 20]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Three.js WebGPURenderer.md]] +- Raw Source: 00_Raw/2026-04-20/Three.js WebGPURenderer.md --- diff --git a/01_Archive/2026-04-20/Threejs 대규모 렌더링 최적화 파이프라인.md b/01_Archive/2026-04-20/Threejs 대규모 렌더링 최적화 파이프라인.md index 2c1c069a..7191bfa1 100644 --- a/01_Archive/2026-04-20/Threejs 대규모 렌더링 최적화 파이프라인.md +++ b/01_Archive/2026-04-20/Threejs 대규모 렌더링 최적화 파이프라인.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-8E841B -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Threejs 대규모 렌더링 최적화 파이프라인" --- -# [[Threejs 대규모 렌더링 최적화 파이프라인]] +# [[Threejs 대규모 렌더링 최적화 파이프라인|Threejs 대규모 렌더링 최적화 파이프라인]] ## 📌 한 줄 통찰 (The Karpathy Summary) > Three.js 대규모 렌더링 최적화 파이프라인은 수많은 3D 객체를 브라우저 환경에서 매끄럽게 렌더링하기 위해 CPU와 GPU 간의 통신 오버헤드, 즉 드로우 콜(Draw Call)과 메모리 병목 현상을 극복하는 일련의 기술적 아키텍처입니다 [1, 2]. 주로 InstancedMesh와 BatchedMesh를 통한 드로우 콜 최소화, Draco 및 KTX2 등을 이용한 에셋 압축, 절두체 컬링(Frustum Culling) 및 LOD 시스템을 활용하여 그래픽 자원의 낭비를 줄입니다 [3-6]. 최근에는 WebGPU와 컴퓨트 셰이더(Compute Shader)가 도입되어 렌더링 제어 및 가시성 판단 연산을 GPU로 대거 이관함으로써, 더욱 막대한 규모의 씬을 유연하게 처리할 수 있는 차세대 파이프라인으로 진화하고 있습니다 [7-9]. @@ -23,13 +23,13 @@ github_commit: "[P-Reinforce] Continuous Worker - Threejs 대규모 렌더링 - **정책 변화:** Graphics & Performance 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** `[[InstancedMesh]]`, `[[BatchedMesh]]`, `[[WebGPU]]`, `[[Draw Call (드로우 콜)]]`, `[[Frustum Culling (절두체 컬링)]]`, `[[LOD (Level of Detail)]]`, `[[Overdraw (오버드로우)]]`, `[[Compute Shader (컴퓨트 셰이더)]]` -- **Projects/Contexts:** `[[InstancedMesh2 (agargaro)]]`, `[[Three.js r171 WebGPURenderer]]`, `[[Segments.ai]]`, `[[Fragment (IFC.js)]]` +- **Related Topics:** `[[InstancedMesh|InstancedMesh]]`, `[[BatchedMesh|BatchedMesh]]`, `[[WebGPU|WebGPU]]`, `Draw Call (드로우 콜)`, `Frustum Culling (절두체 컬링)`, `[[가변적 LOD(Level of Detail) 시스템|LOD (Level of Detail)]]`, `Overdraw (오버드로우)`, `Compute Shader (컴퓨트 셰이더)` +- **Projects/Contexts:** `InstancedMesh2 (agargaro)`, `Three.js r171 WebGPURenderer`, `[[Segments.ai|Segments.ai]]`, `Fragment (IFC.js)` - **Contradictions/Notes:** - `InstancedMesh`는 드로우 콜을 줄여 성능을 크게 향상시키도록 설계되었으나, 불투명도 및 복잡한 셰이더 환경에서는 인스턴스 정렬 부재로 인한 심각한 오버드로우(Overdraw)를 유발해 일반 개별 Mesh(Shared attributes)를 사용할 때보다 프레임 레이트(FPS)가 오히려 낮아지는 역설적인 사례가 보고되고 있습니다 [18, 19]. - `BatchedMesh` 역시 다수의 기하학적 구조를 통합하는 유용한 기술이지만, 약 20만 개 수준의 대량 지오메트리에 적용할 시 버퍼 데이터 업로드 등의 이유로 CPU 사용량이 30~50% 급증하며 병합된 기하학(Merged Geometry)보다 현저히 성능이 하락하는 구조적 병목이 제기되고 있습니다 [37-39]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Three.js 대규모 렌더링 최적화 파이프라인.md]] +- Raw Source: 00_Raw/2026-04-20/Three.js 대규모 렌더링 최적화 파이프라인.md --- diff --git a/01_Archive/2026-04-20/Threejs 렌더링 성능 최적화.md b/01_Archive/2026-04-20/Threejs 렌더링 성능 최적화.md index 47bc9add..7eee3da7 100644 --- a/01_Archive/2026-04-20/Threejs 렌더링 성능 최적화.md +++ b/01_Archive/2026-04-20/Threejs 렌더링 성능 최적화.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-4EE7A9 -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Threejs 렌더링 성능 최적화" --- -# [[Threejs 렌더링 성능 최적화]] +# [[Threejs 렌더링 성능 최적화|Threejs 렌더링 성능 최적화]] ## 📌 한 줄 통찰 (The Karpathy Summary) > Three.js 렌더링 성능 최적화는 브라우저 환경에서 3D 씬을 부드럽게 렌더링하기 위해 CPU와 GPU 간의 병목 현상을 줄이고 하드웨어 자원의 효율성을 극대화하는 일련의 기법을 의미합니다. 가장 핵심적인 목표는 CPU 오버헤드를 유발하는 드로우 콜(Draw Call) 횟수를 프레임당 100회 미만으로 유지하는 것이며, 이를 위해 인스턴싱(Instancing)과 배칭(Batching) 같은 기술이 필수적으로 사용됩니다 [1-5]. 또한, 에셋 압축, 메모리 관리, 셰이더 및 시야 절두체 컬링(Frustum Culling) 조정, WebGPU와 컴퓨트 셰이더의 도입 등을 통해 전반적인 연산 부하를 다각도로 최적화합니다 [1, 6-8]. @@ -36,11 +36,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Threejs 렌더링 성능 최 - **정책 변화:** Graphics & Performance 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[드로우 콜 (Draw Call)]], [[InstancedMesh]], [[BatchedMesh]], [[LOD (Level of Detail)]], [[WebGPU]] -- **Projects/Contexts:** [[Three.js r171 WebGPU 도입]], [[IFC.js Fragment 아키텍처]], [[InstancedMesh2 라이브러리]] +- **Related Topics:** 드로우 콜 (Draw Call), [[InstancedMesh|InstancedMesh]], [[BatchedMesh|BatchedMesh]], [[가변적 LOD(Level of Detail) 시스템|LOD (Level of Detail)]], [[WebGPU|WebGPU]] +- **Projects/Contexts:** Three.js r171 WebGPU 도입, IFC.js Fragment 아키텍처, InstancedMesh2 라이브러리 - **Contradictions/Notes:** 다양한 지오메트리를 한 번에 렌더링하기 위해 제안된 `BatchedMesh`는 드로우 콜 최적화의 훌륭한 대안으로 소개되지만[18], 다른 소스에서는 1,000만 개가 넘는 트라이앵글 환경에서 인스턴싱 또는 일반 `Merged Mesh`보다 CPU 점유율을 비정상적으로 높이고 프레임률을 크게 떨어뜨리는 심각한 구조적 오버헤드가 있음을 상반되게 지적하고 있습니다[19-22]. 또한 `InstancedMesh` 역시 만능이 아니며 정렬의 부재로 인해 발생하는 심각한 오버드로우(Overdraw) 때문에 일반 메쉬 렌더링보다 느려지는 병목 사례가 보고되고 있습니다[13, 14]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Three.js 렌더링 성능 최적화.md]] +- Raw Source: 00_Raw/2026-04-20/Three.js 렌더링 성능 최적화.md --- diff --git a/01_Archive/2026-04-20/Threejs 렌더링 최적화.md b/01_Archive/2026-04-20/Threejs 렌더링 최적화.md index 445a6b75..5c029e4e 100644 --- a/01_Archive/2026-04-20/Threejs 렌더링 최적화.md +++ b/01_Archive/2026-04-20/Threejs 렌더링 최적화.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-13670A -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Threejs 렌더링 최적화" --- -# [[Threejs 렌더링 최적화]] +# [[Threejs 렌더링 최적화|Threejs 렌더링 최적화]] ## 📌 한 줄 통찰 (The Karpathy Summary) > Three.js 렌더링 최적화는 웹 환경에서 3D 그래픽을 부드럽고 효율적으로 구동하기 위해 CPU와 GPU 간의 병목 현상을 해소하는 일련의 기술적 과정입니다 [1-3]. 핵심 목표는 초당 프레임 수(FPS)를 안정적으로 유지하기 위해 드로우 콜(Draw Call) 횟수를 최소화하고, 메모리 대역폭을 효율적으로 관리하는 것입니다 [4-7]. 이를 위해 인스턴싱(Instancing), 배칭(Batching), 에셋 압축, 디테일 수준(LOD) 조절 및 최신 WebGPU API의 도입이 필수적으로 요구됩니다 [4, 8-10]. @@ -24,11 +24,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Threejs 렌더링 최적화" - **정책 변화:** Graphics & Performance 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Draw Call]], [[InstancedMesh]], [[BatchedMesh]], [[WebGPU]], [[Level of Detail (LOD)]], [[Texture Compression]] -- **Projects/Contexts:** [[Utsubo]], [[Segments.ai]], [[InstancedMesh2 library]] +- **Related Topics:** [[Draw Call|Draw Call]], [[InstancedMesh|InstancedMesh]], [[BatchedMesh|BatchedMesh]], [[WebGPU|WebGPU]], [[Level of Detail (LOD)|Level of Detail (LOD)]], [[Texture Compression|Texture Compression]] +- **Projects/Contexts:** [[Utsubo|Utsubo]], [[Segments.ai|Segments.ai]], [[InstancedMesh2 library|InstancedMesh2 library]] - **Contradictions/Notes:** `InstancedMesh`는 드로우 콜을 획기적으로 줄여주지만, 엔진 수준에서 개별 인스턴스에 대한 절두체 컬링과 깊이 정렬(Sorting)이 불가능하여 오버드로우(Overdraw)가 유발됩니다. 이로 인해 픽셀 연산이 무거운 씬에서는 오히려 일반 메쉬 방식보다 프레임 레이트가 하락할 수 있다는 한계가 지적됩니다 [41-44]. 대안으로 꼽히는 `BatchedMesh` 역시 수십만 개 단위의 복잡한 기하학적 데이터와 인스턴스를 처리할 때는 심각한 CPU 병목 현상 및 성능 저하를 야기할 수 있습니다 [20, 45-48]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Three.js 렌더링 최적화.md]] +- Raw Source: 00_Raw/2026-04-20/Three.js 렌더링 최적화.md --- diff --git a/01_Archive/2026-04-20/Threejs 모바일 렌더링 최적화.md b/01_Archive/2026-04-20/Threejs 모바일 렌더링 최적화.md index bdefe553..90873c94 100644 --- a/01_Archive/2026-04-20/Threejs 모바일 렌더링 최적화.md +++ b/01_Archive/2026-04-20/Threejs 모바일 렌더링 최적화.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-E3AAE4 -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Threejs 모바일 렌더링 최적화" --- -# [[Threejs 모바일 렌더링 최적화]] +# [[Threejs 모바일 렌더링 최적화|Threejs 모바일 렌더링 최적화]] ## 📌 한 줄 통찰 (The Karpathy Summary) > Three.js 모바일 렌더링 최적화는 제한된 컴퓨팅 파워, 메모리 대역폭 및 배터리 용량을 가진 모바일 기기 환경에서 3D 장면을 원활하게 구동하기 위한 일련의 기술적 접근이다. 이 최적화는 셰이더 정밀도 조절, 텍스처 및 폴리곤 수 제한, 드로우 콜(Draw Call) 감소, 배터리 절약을 위한 렌더링 루프 제어 등을 포함한다 [1-4]. 이를 통해 모바일 브라우저에서도 60fps의 안정적인 프레임 속도를 유지하고 메모리 한계로 인한 애플리케이션 크래시를 방지할 수 있다 [5, 6]. @@ -39,11 +39,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Threejs 모바일 렌더링 - **정책 변화:** Graphics & Performance 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[드로우 콜 최적화 (Draw Call Optimization)]], [[텍스처 압축 (Texture Compression)]], [[셰이더 정밀도 (Shader Precision)]], [[가비지 컬렉션 (Garbage Collection)]] -- **Projects/Contexts:** [[React Three Fiber (R3F)]], [[Basis Universal / KTX2]] +- **Related Topics:** 드로우 콜 최적화 (Draw Call Optimization), 텍스처 압축 (Texture Compression), 셰이더 정밀도 (Shader Precision), [[가비지 컬렉션 (Garbage Collection)|가비지 컬렉션 (Garbage Collection)]] +- **Projects/Contexts:** [[React Three Fiber (R3F)|React Three Fiber (R3F)]], Basis Universal / KTX2 - **Contradictions/Notes:** 소스에서는 모바일 환경 구현 시 시각적 품질과 성능 간의 직접적인 타협(trade-off)을 강조한다. 데스크톱 환경에서는 다중 텍스처 파일과 MSAA, 4096 크기의 섀도우 맵 활용이 가능하지만, 모바일 기기에서는 동일한 구성을 유지할 경우 프레임 속도 저하와 발열, 메모리 부족으로 인한 강제 종료를 유발할 수 있으므로 극단적인 간소화(FXAA, 아틀라스 텍스처, 512~1024 섀도우 등)를 필수적으로 도입해야 함을 명시한다 [5, 6, 10]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Three.js 모바일 렌더링 최적화.md]] +- Raw Source: 00_Raw/2026-04-20/Three.js 모바일 렌더링 최적화.md --- diff --git a/01_Archive/2026-04-20/Threejs 성능 최적화.md b/01_Archive/2026-04-20/Threejs 성능 최적화.md index 51af4e6b..04e31df6 100644 --- a/01_Archive/2026-04-20/Threejs 성능 최적화.md +++ b/01_Archive/2026-04-20/Threejs 성능 최적화.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-965BAB -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Threejs 성능 최적화" --- -# [[Threejs 성능 최적화]] +# [[Threejs 성능 최적화|Threejs 성능 최적화]] ## 📌 한 줄 통찰 (The Karpathy Summary) > Three.js 성능 최적화는 CPU와 GPU 간의 통신 병목 현상을 유발하는 드로우 콜(Draw Call)을 줄이고 렌더링 파이프라인의 효율을 극대화하여 높은 프레임 속도를 유지하는 과정이다 [1-3]. 주로 `InstancedMesh` 및 `BatchedMesh`를 활용한 인스턴싱/배칭 기법, 텍스처와 지오메트리 압축, 프러스텀 컬링(Frustum Culling) 및 LOD(Level of Detail) 기법이 핵심적으로 사용된다 [4-9]. 최근에는 WebGL의 구조적 한계를 극복하기 위해 WebGPU와 컴퓨트 셰이더를 기반으로 한 GPU 주도 렌더링(GPU-driven Rendering) 기술로 발전하고 있다 [10, 11]. @@ -39,11 +39,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Threejs 성능 최적화" - **정책 변화:** AI 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[InstancedMesh]], [[BatchedMesh]], [[WebGPU]], [[드로우 콜 (Draw Call)]], [[LOD (Level of Detail)]] -- **Projects/Contexts:** [[Utsubo의 WebGPU 도입 (Segments.ai 등)]], [[InstancedMesh2 라이브러리]], [[Three.js r171 WebGPURenderer]] +- **Related Topics:** [[InstancedMesh|InstancedMesh]], [[BatchedMesh|BatchedMesh]], [[WebGPU|WebGPU]], 드로우 콜 (Draw Call), [[가변적 LOD(Level of Detail) 시스템|LOD (Level of Detail)]] +- **Projects/Contexts:** Utsubo의 WebGPU 도입 (Segments.ai 등), InstancedMesh2 라이브러리, Three.js r171 WebGPURenderer - **Contradictions/Notes:** 드로우 콜을 줄이기 위해 `InstancedMesh`나 `BatchedMesh`를 도입하더라도 항상 성능이 향상되는 것은 아니다. `InstancedMesh`는 개별 컬링의 부재와 오버드로우로 인해 오히려 개별 렌더링보다 GPU FPS를 떨어뜨릴 수 있다는 점이 지적된다 [27, 30, 38]. 또한 `BatchedMesh`의 경우에도 천만 개 이상의 많은 폴리곤과 지오메트리를 처리할 때는 내부적인 다중 그리기(multi-draw) 버퍼 업로드 및 패킹 오버헤드로 인해 CPU 점유율이 40~60%까지 치솟고 프레임이 급감하는 현상이 보고되어, 상황에 따른 벤치마킹이 필수적이다 [39-43]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Three.js 성능 최적화.md]] +- Raw Source: 00_Raw/2026-04-20/Three.js 성능 최적화.md --- diff --git a/01_Archive/2026-04-20/Threejs 자원 해제 (Dispose).md b/01_Archive/2026-04-20/Threejs 자원 해제 (Dispose).md index a3707f54..5f3e5c36 100644 --- a/01_Archive/2026-04-20/Threejs 자원 해제 (Dispose).md +++ b/01_Archive/2026-04-20/Threejs 자원 해제 (Dispose).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-5ED3CA -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Threejs 자원 해제 (Dispose)" --- -# [[Threejs 자원 해제 (Dispose)]] +# [[Threejs 자원 해제 (Dispose)|Threejs 자원 해제 (Dispose)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Threejs 자원 해제 (Dispose ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Three.js 자원 해제 (Dispose).md]] +- Raw Source: 00_Raw/2026-04-20/Three.js 자원 해제 (Dispose).md --- diff --git a/01_Archive/2026-04-20/Threejs.md b/01_Archive/2026-04-20/Threejs.md index 50f1b223..1e92da88 100644 --- a/01_Archive/2026-04-20/Threejs.md +++ b/01_Archive/2026-04-20/Threejs.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-A5498B -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Threejs" --- -# [[Threejs]] +# [[Threejs|Threejs]] ## 📌 한 줄 통찰 (The Karpathy Summary) > Three.js는 WebGL 및 WebGPU를 사용하여 웹 브라우저에서 애니메이션 3D 컴퓨터 그래픽스를 생성하고 표시할 수 있도록 지원하는 크로스 브라우저 자바스크립트 라이브러리이자 API이다 [1, 2]. 브라우저, GPU, 자바스크립트 간의 복잡한 상호작용을 추상화하여 개발자가 고성능의 3D 환경을 쉽게 구축할 수 있도록 돕는다 [3]. 2026년을 기점으로 프로덕션 수준의 WebGPU 렌더러와 TSL(Three Shader Language)이 도입되면서, 단순한 시각화를 넘어 수백만 개의 파티클 연산이나 대규모 CAD 모델 처리까지 가능한 고성능 플랫폼으로 진화했다 [4-7]. @@ -29,11 +29,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Threejs" - **정책 변화:** Graphics & Performance 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[WebGPU]], [[InstancedMesh]], [[BatchedMesh]], [[TSL (Three Shader Language)]], [[Raycaster]], [[LOD (Level of Detail)]] -- **Projects/Contexts:** [[React Three Fiber (R3F)]], [[IFC.js]], [[InstancedMesh2]] +- **Related Topics:** [[WebGPU|WebGPU]], [[InstancedMesh|InstancedMesh]], [[BatchedMesh|BatchedMesh]], [[TSL (Three Shader Language)|TSL (Three Shader Language)]], [[Raycaster|Raycaster]], [[가변적 LOD(Level of Detail) 시스템|LOD (Level of Detail)]] +- **Projects/Contexts:** [[React Three Fiber (R3F)|React Three Fiber (R3F)]], [[IFC.js|IFC.js]], [[InstancedMesh2|InstancedMesh2]] - **Contradictions/Notes:** 일반적으로 `InstancedMesh`는 드로우 콜을 1회로 줄여 렌더링 성능을 획기적으로 높인다고 알려져 있으나, 인스턴스의 자동 정렬 기능이 없어 오버드로우(Overdraw)가 빈번하게 발생할 경우 단일 메쉬를 분할하여 그릴 때보다 오히려 프레임 속도(FPS)가 급락할 수 있습니다 [4, 31-33]. 또한 여러 다른 지오메트리를 하나의 렌더 호출로 묶어주는 `BatchedMesh` 역시, 지나치게 많은 수의 정점과 데이터를 렌더링할 경우 패킹 및 컬링 연산 때문에 극심한 CPU 과부하와 성능 저하를 야기할 수 있다는 한계가 보고되고 있습니다 [41, 42]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Three.js.md]] +- Raw Source: 00_Raw/2026-04-20/Three.js.md --- diff --git a/01_Archive/2026-04-20/Throttling Debouncing (스로틀링과 디바운싱).md b/01_Archive/2026-04-20/Throttling Debouncing (스로틀링과 디바운싱).md index 667e12b3..2143280f 100644 --- a/01_Archive/2026-04-20/Throttling Debouncing (스로틀링과 디바운싱).md +++ b/01_Archive/2026-04-20/Throttling Debouncing (스로틀링과 디바운싱).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-A0A08A -category: "[[10_Wiki/💡 Topics/Software Architecture]]" +category: "10_Wiki/💡 Topics/Software Architecture" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Throttling Debouncing (스로틀링과 디바운싱)" --- -# [[Throttling Debouncing (스로틀링과 디바운싱)]] +# [[Throttling Debouncing (스로틀링과 디바운싱)|Throttling Debouncing (스로틀링과 디바운싱)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Throttling Debouncing (스로 ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Throttling & Debouncing (스로틀링과 디바운싱).md]] +- Raw Source: 00_Raw/2026-04-20/Throttling & Debouncing (스로틀링과 디바운싱).md --- diff --git a/01_Archive/2026-04-20/Throttling Debouncing.md b/01_Archive/2026-04-20/Throttling Debouncing.md index 7257af8c..3b627f12 100644 --- a/01_Archive/2026-04-20/Throttling Debouncing.md +++ b/01_Archive/2026-04-20/Throttling Debouncing.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-92BBDE -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Throttling Debouncing" --- -# [[Throttling Debouncing]] +# [[Throttling Debouncing|Throttling Debouncing]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 스크롤, 화면 크기 조절(Resize), 타이핑 등 짧은 시간 동안 과도하게 발생하는 사용자 이벤트의 실행 빈도를 제어하여 애플리케이션의 성능 병목 현상을 방지하는 최적화 기법입니다. @@ -26,12 +26,12 @@ github_commit: "[P-Reinforce] Continuous Worker - Throttling Debouncing" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[React Performance Optimization]], [[Tree Shaking (번들 크기 최적화)]], [[이벤트 포워딩 (Event Forwarding)]], [[불필요한 리렌더링 방지]] -- **Projects/Contexts:** [[실시간 검색 입력(Typing) 지연 처리]], [[반응형 윈도우 리사이즈(Resize) 이벤트 처리]], [[웹 워커 통신 지연 최소화]] +- **Related Topics:** [[React Performance Optimization|React Performance Optimization]], [[Tree Shaking (번들 크기 최적화)|Tree Shaking (번들 크기 최적화)]], [[이벤트 포워딩(Event Forwarding)|이벤트 포워딩 (Event Forwarding)]], [[불필요한 리렌더링 방지|불필요한 리렌더링 방지]] +- **Projects/Contexts:** 실시간 검색 입력(Typing) 지연 처리, [[반응형 윈도우 리사이즈(Resize) 이벤트 처리|반응형 윈도우 리사이즈(Resize) 이벤트 처리]], 웹 워커 통신 지연 최소화 - **Contradictions/Notes:** 스로틀링과 디바운싱은 무거운 연산을 줄이고 프레임 드랍을 막아주지만, 설정한 대기 시간이 너무 길면 화면 업데이트가 늦어져 사용자에게 끊기는 느낌을 줄 수 있습니다. 따라서 작업의 성격(예: 즉각 반응이 필요한 드래그, 멈춘 후 반응해도 되는 윈도우 리사이즈)에 맞추어 적절한 지연 시간을 타협하는 것이 중요합니다. --- _Last updated: 2026-04-14_ -- Raw Source: [[00_Raw/2026-04-20/Throttling & Debouncing.md]] +- Raw Source: 00_Raw/2026-04-20/Throttling & Debouncing.md --- diff --git a/01_Archive/2026-04-20/Throttling & Debouncing.md b/01_Archive/2026-04-20/Throttling & Debouncing.md index 342984b6..6fffe21d 100644 --- a/01_Archive/2026-04-20/Throttling & Debouncing.md +++ b/01_Archive/2026-04-20/Throttling & Debouncing.md @@ -1,4 +1,4 @@ -# [[Throttling & Debouncing (스로틀링과 디바운싱)]] +# [[Throttling & Debouncing (스로틀링과 디바운싱)|Throttling & Debouncing (스로틀링과 디바운싱)]] ## 📌 Brief Summary @@ -16,8 +16,8 @@ ## 🔗 Knowledge Connections -- **Related Topics:** [[React Performance Optimization]], [[Tree Shaking (번들 크기 최적화)]], [[이벤트 포워딩 (Event Forwarding)]], [[불필요한 리렌더링 방지]] -- **Projects/Contexts:** [[실시간 검색 입력(Typing) 지연 처리]], [[반응형 윈도우 리사이즈(Resize) 이벤트 처리]], [[웹 워커 통신 지연 최소화]] +- **Related Topics:** [[React Performance Optimization|React Performance Optimization]], [[Tree Shaking (번들 크기 최적화)|Tree Shaking (번들 크기 최적화)]], [[이벤트 포워딩(Event Forwarding)|이벤트 포워딩 (Event Forwarding)]], [[불필요한 리렌더링 방지|불필요한 리렌더링 방지]] +- **Projects/Contexts:** 실시간 검색 입력(Typing) 지연 처리, [[반응형 윈도우 리사이즈(Resize) 이벤트 처리|반응형 윈도우 리사이즈(Resize) 이벤트 처리]], 웹 워커 통신 지연 최소화 - **Contradictions/Notes:** 스로틀링과 디바운싱은 무거운 연산을 줄이고 프레임 드랍을 막아주지만, 설정한 대기 시간이 너무 길면 화면 업데이트가 늦어져 사용자에게 끊기는 느낌을 줄 수 있습니다. 따라서 작업의 성격(예: 즉각 반응이 필요한 드래그, 멈춘 후 반응해도 되는 윈도우 리사이즈)에 맞추어 적절한 지연 시간을 타협하는 것이 중요합니다. --- diff --git a/01_Archive/2026-04-20/Time Series Analysis.md b/01_Archive/2026-04-20/Time Series Analysis.md index e4bbe742..512377a2 100644 --- a/01_Archive/2026-04-20/Time Series Analysis.md +++ b/01_Archive/2026-04-20/Time Series Analysis.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-D84BD7 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Time Series Analysis" --- -# [[Time Series Analysis]] +# [[Time Series Analysis|Time Series Analysis]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Time Series Analysis" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Time Series Analysis.md]] +- Raw Source: 00_Raw/2026-04-20/Time Series Analysis.md --- diff --git a/01_Archive/2026-04-20/Time to Interactive (TTI).md b/01_Archive/2026-04-20/Time to Interactive (TTI).md index 0d2efe79..43c16e29 100644 --- a/01_Archive/2026-04-20/Time to Interactive (TTI).md +++ b/01_Archive/2026-04-20/Time to Interactive (TTI).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-8492DF -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Time to Interactive (TTI)" --- -# [[Time to Interactive (TTI)]] +# [[Time to Interactive (TTI)|Time to Interactive (TTI)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > Time to Interactive (TTI)는 Chrome Lighthouse에서 주로 사용되는 웹 성능 측정 지표입니다 [1]. 이는 페이지 렌더링이 완료되고, JavaScript 실행이 끝나며, 브라우저의 백그라운드 작업이 완료되어 페이지가 완전히 상호작용 가능한 상태(fully interactive)가 될 때까지 걸리는 시간을 측정합니다 [1]. @@ -20,11 +20,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Time to Interactive (TTI)" - **정책 변화:** AI 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Largest Contentful Paint (LCP)]], [[First Input Delay (FID)]] -- **Projects/Contexts:** [[Chrome Lighthouse]] +- **Related Topics:** [[Largest Contentful Paint (LCP)|Largest Contentful Paint (LCP)]], [[First Input Delay (FID)|First Input Delay (FID)]] +- **Projects/Contexts:** Chrome Lighthouse - **Contradictions/Notes:** 소스에 관련 정보가 부족합니다. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Time to Interactive (TTI).md]] +- Raw Source: 00_Raw/2026-04-20/Time to Interactive (TTI).md --- diff --git a/01_Archive/2026-04-20/Timestamp Quantization.md b/01_Archive/2026-04-20/Timestamp Quantization.md index fe097b1c..5135d6a1 100644 --- a/01_Archive/2026-04-20/Timestamp Quantization.md +++ b/01_Archive/2026-04-20/Timestamp Quantization.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-B27B31 -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Timestamp Quantization" --- -# [[Timestamp Quantization]] +# [[Timestamp Quantization|Timestamp Quantization]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 타임스탬프 양자화(Timestamp Quantization)는 WebGPU 등 웹 그래픽 API에서 발생할 수 있는 타이밍 공격(Timing Attack) 및 기기 핑거프린팅을 방지하기 위해, 타이머 쿼리의 해상도를 의도적으로 조대화(coarsening)하여 낮추는 보안 메커니즘입니다 [1-3]. 고정밀 타이밍 정보가 캐시 사이드 채널 공격이나 Rowhammer 공격 등에 악용되는 것을 막기 위해 브라우저 엔진은 타임스탬프의 측정 해상도를 100 마이크로초(µs)와 같은 표준 단위로 제한합니다 [1, 4-6]. @@ -22,11 +22,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Timestamp Quantization" - **정책 변화:** Graphics & Performance 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[WebGPU]], [[Timing Attack]], [[Side-channel Attack]], [[Spectre]], [[Rowhammer]], [[High Resolution Time]] -- **Projects/Contexts:** [[Chrome (Blink/Dawn)]], [[GPU for the Web Community Group]] +- **Related Topics:** [[WebGPU|WebGPU]], [[Timing Attack|Timing Attack]], [[Side-channel Attack|Side-channel Attack]], [[Spectre|Spectre]], [[Rowhammer|Rowhammer]], [[High Resolution Time|High Resolution Time]] +- **Projects/Contexts:** [[Chrome (Blink_Dawn)|Chrome (Blink/Dawn)]], [[GPU for the Web Community Group|GPU for the Web Community Group]] - **Contradictions/Notes:** Chrome의 초기 제안에서는 교차 출처 격리(cross-origin isolated) 상태에 따라 격리된 컨텍스트에서는 100µs 해상도를 제공하고 비격리 컨텍스트에서는 타임스탬프를 아예 노출하지 않으려 했습니다 [3, 13]. 그러나 상호운용성(interoperability) 문제와 모호한 사양에 대한 지적이 제기되었고, 최종적으로는 사이트 격리 상태와 무관하게 항상 100µs 해상도로 타임스탬프를 허용하는 방안이 합의되었습니다 [5, 11, 14]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Timestamp Quantization.md]] +- Raw Source: 00_Raw/2026-04-20/Timestamp Quantization.md --- diff --git a/01_Archive/2026-04-20/Timestamp Queries Quantization.md b/01_Archive/2026-04-20/Timestamp Queries Quantization.md index abf01f46..4706d1e6 100644 --- a/01_Archive/2026-04-20/Timestamp Queries Quantization.md +++ b/01_Archive/2026-04-20/Timestamp Queries Quantization.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-788E1E -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Timestamp Queries Quantization" --- -# [[Timestamp Queries Quantization]] +# [[Timestamp Queries Quantization|Timestamp Queries Quantization]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 타임스탬프 쿼리 양자화(Timestamp Queries Quantization)는 WebGPU 애플리케이션에서 GPU 명령의 실행 시간을 측정할 때 그 정밀도를 의도적으로 낮추는 보안 메커니즘입니다 [1], [2], [3], [4]. 개발자는 타임스탬프 쿼리를 통해 나노초 단위의 정밀한 데이터를 얻을 수 있지만, 이는 Spectre나 Rowhammer와 같은 캐시 기반 타이밍 공격(Timing attack)에 악용될 수 있습니다 [5], [1], [2], [6]. 이를 방지하기 위해 브라우저 엔진은 반환되는 타이머의 해상도를 100 마이크로초(µs) 수준으로 낮추어 보안과 성능 분석의 균형을 맞춥니다 [1], [7], [3], [4]. @@ -22,11 +22,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Timestamp Queries Quantization - **정책 변화:** Graphics & Performance 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[WebGPU]], [[Timing Attack]], [[Spectre]], [[EXT_disjoint_timer_query]] -- **Projects/Contexts:** [[High Resolution Time Spec]], [[Chrome DevTools]] +- **Related Topics:** [[WebGPU|WebGPU]], [[Timing Attack|Timing Attack]], [[Spectre|Spectre]], [[EXT_disjoint_timer_query|EXT_disjoint_timer_query]] +- **Projects/Contexts:** High Resolution Time Spec, [[Chrome DevTools|Chrome DevTools]] - **Contradictions/Notes:** 초기 WebGPU 사양 제안에서는 사이트 격리(Site isolation) 여부에 따라 타임스탬프 쿼리 제공 여부를 차등 적용(비격리 시 완전히 미노출)하려 했으나 [3], 이후 표준화 논의 과정에서 상호 운용성을 위해 모든 컨텍스트에 대해 100 마이크로초의 해상도를 일괄 제공하도록 정책이 변경되었습니다 [10], [11]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Timestamp Queries Quantization.md]] +- Raw Source: 00_Raw/2026-04-20/Timestamp Queries Quantization.md --- diff --git a/01_Archive/2026-04-20/Timestamp Queries.md b/01_Archive/2026-04-20/Timestamp Queries.md index 6d351fd3..0289d6f0 100644 --- a/01_Archive/2026-04-20/Timestamp Queries.md +++ b/01_Archive/2026-04-20/Timestamp Queries.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-77D993 -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Timestamp Queries" --- -# [[Timestamp Queries]] +# [[Timestamp Queries|Timestamp Queries]] ## 📌 한 줄 통찰 (The Karpathy Summary) > Timestamp Queries(타임스탬프 쿼리)는 WebGL 및 WebGPU와 같은 웹 그래픽 파이프라인에서 GPU 명령 세트의 경과 시간을 나노초 단위까지 정밀하게 측정할 수 있게 해주는 기능입니다 [1-3]. 렌더링 파이프라인을 지연시키지 않으면서 GPU 작업 부하의 성능과 동작에 대한 깊은 통찰력을 제공하는 데 필수적입니다 [3, 4]. 그러나 고정밀 타이머가 사이드 채널 공격(예: Spectre 및 Meltdown)에 악용될 수 있다는 보안 취약점 때문에, 최신 브라우저 환경에서는 타이머의 정밀도를 의도적으로 낮추는 양자화(Quantization) 기법이 적용됩니다 [2, 5, 6]. @@ -29,11 +29,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Timestamp Queries" - **정책 변화:** Graphics & Performance 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[WebGL Timer Queries]], [[Spectre and Meltdown]], [[WebGPU]], [[Timestamp Quantization]] -- **Projects/Contexts:** [[EXT_disjoint_timer_query]], [[High Resolution Time Spec]] +- **Related Topics:** WebGL Timer Queries, [[Spectre and Meltdown|Spectre and Meltdown]], [[WebGPU|WebGPU]], [[Timestamp Quantization|Timestamp Quantization]] +- **Projects/Contexts:** [[EXT_disjoint_timer_query|EXT_disjoint_timer_query]], High Resolution Time Spec - **Contradictions/Notes:** 초기 WebGPU 구현 제안에서는 사이트 격리 상태에 따라 타임스탬프 쿼리의 노출 여부와 해상도를 다르게 적용하려고 했으나(격리 시 100µs, 비격리 시 미노출) [5], 브라우저 간의 상호 운용성 부족 및 GPU의 격리 한계를 이유로 격리 상태와 관계없이 모든 GPU 작업에 대해 일괄적으로 100µs 해상도를 적용하도록 사양이 수정되었습니다 [6, 9]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Timestamp Queries.md]] +- Raw Source: 00_Raw/2026-04-20/Timestamp Queries.md --- diff --git a/01_Archive/2026-04-20/Timing Attack.md b/01_Archive/2026-04-20/Timing Attack.md index e362bb5e..b488ead0 100644 --- a/01_Archive/2026-04-20/Timing Attack.md +++ b/01_Archive/2026-04-20/Timing Attack.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-392C3B -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Timing Attack" --- -# [[Timing Attack]] +# [[Timing Attack|Timing Attack]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 타이밍 공격(Timing Attack)은 캐시 적중률이나 메모리 접근 패턴 등 시스템의 작업 수행 시간을 극도로 정밀하게 측정함으로써 의도치 않은 정보를 유출하거나 보안 경계를 우회하는 부채널 공격(Side-channel Attack)의 일종입니다 [1-3]. 스펙터(Spectre)와 멜트다운(Meltdown)이 대표적인 예로, CPU의 추측 실행(Speculative Execution) 기능을 악용하여 L1 캐시와 메인 메모리 간의 접근 지연 시간 차이를 관찰함으로써 데이터를 탈취합니다 [3-5]. 웹 환경에서 이러한 공격은 신뢰할 수 없는 JavaScript나 WebAssembly 코드가 호스트 프로세스의 메모리를 읽을 수 있게 하므로, 브라우저 차원의 타이머 정밀도 저하 및 분기 없는 보안 검사(Branchless Security Checks) 등의 방어 기법이 필수적입니다 [6-8]. @@ -25,11 +25,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Timing Attack" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Side-channel Attack]], [[Spectre and Meltdown]], [[Speculative Execution]], [[Timestamp Quantization]], [[Branchless Security Checks]] -- **Projects/Contexts:** [[WebKit]], [[WebGL]], [[WebGPU]] +- **Related Topics:** [[Side-channel Attack|Side-channel Attack]], [[Spectre and Meltdown|Spectre and Meltdown]], [[Speculative Execution|Speculative Execution]], [[Timestamp Quantization|Timestamp Quantization]], [[Branchless Security Checks|Branchless Security Checks]] +- **Projects/Contexts:** [[WebKit|WebKit]], [[WebGL|WebGL]], [[WebGPU|WebGPU]] - **Contradictions/Notes:** 소스 내에서 특별한 모순점은 발견되지 않았습니다. 개발자들의 성능 분석 요구와 타이밍 공격(보안)이라는 상충하는 두 가지 목표를 해결하기 위해, WebGPU 표준에서는 타임스탬프 쿼리를 전면 차단하는 대신 '정밀도 양자화(Quantization)'를 절충안으로 도입하는 데 합의했습니다 [1, 10, 11]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Timing Attack.md]] +- Raw Source: 00_Raw/2026-04-20/Timing Attack.md --- diff --git a/01_Archive/2026-04-20/Timing Attacks (Spectre_Meltdown).md b/01_Archive/2026-04-20/Timing Attacks (Spectre_Meltdown).md index 1edcf860..17a83cf1 100644 --- a/01_Archive/2026-04-20/Timing Attacks (Spectre_Meltdown).md +++ b/01_Archive/2026-04-20/Timing Attacks (Spectre_Meltdown).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-09FCC7 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Timing Attacks (Spectre_Meltdown)" --- -# [[Timing Attacks (Spectre_Meltdown)]] +# [[Timing Attacks (Spectre_Meltdown)|Timing Attacks (Spectre_Meltdown)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > Spectre와 Meltdown은 최신 프로세서의 투기적 실행(speculative execution) 기능과 캐시 지연 시간의 차이를 악용하여 보호된 메모리 영역을 무단으로 읽어내는 보안 취약점입니다 [1, 2]. 이러한 타이밍 공격(Timing Attacks)은 고해상도 타이머를 사용해 L1 캐시와 메인 메모리 간의 지연 시간 차이를 관찰함으로써 달성되며, 브라우저 환경에서 신뢰할 수 없는 JavaScript나 WebAssembly 코드가 실행될 때 악용될 수 있습니다 [1, 3]. 이를 방지하기 위해 웹 생태계에서는 타이머의 정밀도를 의도적으로 낮추고, 분기 명령어(branch)에 의존하지 않는 보안 검사를 도입하는 등의 방어 체계를 구축했습니다 [4, 5]. @@ -20,11 +20,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Timing Attacks (Spectre_Meltdo - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Speculative Execution]], [[EXT_disjoint_timer_query]], [[WebGPU Timestamp Queries]], [[Branchless Security Checks]] -- **Projects/Contexts:** [[WebKit]], [[Blink]] +- **Related Topics:** [[Speculative Execution|Speculative Execution]], [[EXT_disjoint_timer_query|EXT_disjoint_timer_query]], [[WebGPU Timestamp Queries|WebGPU Timestamp Queries]], [[Branchless Security Checks|Branchless Security Checks]] +- **Projects/Contexts:** [[WebKit|WebKit]], [[Blink|Blink]] - **Contradictions/Notes:** WebGPU 명세에서 타임스탬프 쿼리 기능은 타이밍 공격의 우려로 인해 선택적(optional)인 기능으로 정의되어 있으나, 성능 최적화를 위한 개발자들의 요구가 커서 해상도를 100 마이크로초로 낮추는 양자화(quantization)를 적용하는 절충안을 통해 기능을 제공하고 있습니다 [7, 13, 16]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Timing Attacks (Spectre_Meltdown).md]] +- Raw Source: 00_Raw/2026-04-20/Timing Attacks (Spectre_Meltdown).md --- diff --git a/01_Archive/2026-04-20/Timing Attacks.md b/01_Archive/2026-04-20/Timing Attacks.md index a4798871..317f2348 100644 --- a/01_Archive/2026-04-20/Timing Attacks.md +++ b/01_Archive/2026-04-20/Timing Attacks.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-59075E -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Timing Attacks" --- -# [[Timing Attacks]] +# [[Timing Attacks|Timing Attacks]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 타이밍 공격(Timing Attacks)은 CPU나 GPU의 연산 처리, 캐시 적중률, 메모리 접근에 소요되는 미세한 시간 차이를 고정밀 타이머로 측정하여 시스템의 기밀 정보를 유출시키는 부채널 공격(Side-channel attacks)의 일종입니다 [1-3]. 웹 환경에서는 신뢰할 수 없는 JavaScript나 WebAssembly 코드가 실행될 때, 분기 예측과 추측 실행(Speculative execution) 과정에서 발생하는 타이밍 차이를 악용하여 스펙터(Spectre) 및 멜트다운(Meltdown) 취약점을 유발합니다 [2, 4, 5]. 이를 방지하기 위해 웹 브라우저들은 타이머의 정밀도를 고의로 낮추거나 타이밍 조작을 방지하는 다양한 완화(Mitigation) 정책을 적용하고 있습니다 [6, 7]. @@ -23,11 +23,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Timing Attacks" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Spectre]], [[Meltdown]], [[Speculative Execution]], [[Timestamp Queries]], [[Side-channel Attacks]] -- **Projects/Contexts:** [[WebKit]], [[WebGPU]], [[WebGL]] +- **Related Topics:** [[Spectre|Spectre]], [[Meltdown|Meltdown]], [[Speculative Execution|Speculative Execution]], [[Timestamp Queries|Timestamp Queries]], [[Side-channel attacks|Side-channel Attacks]] +- **Projects/Contexts:** [[WebKit|WebKit]], [[WebGPU|WebGPU]], [[WebGL|WebGL]] - **Contradictions/Notes:** 소스에 따르면 WebGPU 및 WebGL의 고정밀 타임스탬프 쿼리 기능은 개발자의 성능 최적화(Profiling)를 위해 반드시 필요하지만, 타이밍 공격에 악용될 수 있는 치명적인 위험성을 동시에 안고 있습니다. 이 때문에 표준화 그룹과 브라우저 벤더들은 성능 분석 기능 제공과 보안 유지 사이에서 타협점(예: 사이트 격리 상태에 따른 타이머 해상도 축소 및 비활성화)을 찾아야만 했습니다 [8, 14]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Timing Attacks.md]] +- Raw Source: 00_Raw/2026-04-20/Timing Attacks.md --- diff --git a/01_Archive/2026-04-20/To-Space와 From-Space.md b/01_Archive/2026-04-20/To-Space와 From-Space.md index f84cfaf6..33996367 100644 --- a/01_Archive/2026-04-20/To-Space와 From-Space.md +++ b/01_Archive/2026-04-20/To-Space와 From-Space.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-3F32E9 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - To-Space와 From-Space" --- -# [[To-Space와 From-Space]] +# [[To-Space와 From-Space|To-Space와 From-Space]] ## 📌 한 줄 통찰 (The Karpathy Summary) > To-Space와 From-Space는 V8 자바스크립트 엔진의 가비지 컬렉션(GC) 과정에서 사용되는 'New Space(새로운 세대)' 내의 동일한 크기를 가진 두 개의 반공간(semi-space)입니다 [1-3]. 이 두 공간은 Cheney의 알고리즘을 기반으로 한 Scavenge(마이너 GC) 과정에서 메모리 단편화를 제거하고 살아남은 활성 객체를 효율적으로 복사 및 대피시키는 데 핵심적인 역할을 합니다 [1, 2, 4]. 공간이 가득 차면 활성 객체를 한 공간에서 다른 공간으로 복사한 뒤 두 공간의 역할을 맞바꾸는(swap) 방식으로 메모리를 관리합니다 [1, 4, 5]. @@ -27,11 +27,11 @@ github_commit: "[P-Reinforce] Continuous Worker - To-Space와 From-Space" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[New Space]], [[Scavenger]], [[Cheney's Algorithm]], [[Garbage Collection]] -- **Projects/Contexts:** [[V8 JavaScript Engine Memory Management]], [[Orinoco Garbage Collector]] +- **Related Topics:** [[New Space|New Space]], [[Scavenger 알고리즘|Scavenger]], [[Cheney's Algorithm|Cheney's Algorithm]], [[Garbage Collection|Garbage Collection]] +- **Projects/Contexts:** V8 JavaScript Engine Memory Management, Orinoco Garbage Collector - **Contradictions/Notes:** 소스 간에 새 객체가 최초로 할당되는 기본 공간의 명칭에 대해 설명이 엇갈립니다. 소스 [1, 14]는 새 객체가 'To-Space'에 할당되고 공간이 가득 차면 두 공간을 바꾼 후 From-Space에서 To-Space로 활성 객체를 복사한다고 설명합니다. 반면, 소스 [5, 6, 9]는 새 객체가 'From-Space'에 할당되며, 마이너 GC 발생 시 활성 객체를 비어있는 To-Space로 복사한 뒤 두 공간의 역할을 맞바꾸어 다시 비워진 From-Space에 새로운 할당을 진행한다고 상반되게 설명하고 있습니다. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/To-Space와 From-Space.md]] +- Raw Source: 00_Raw/2026-04-20/To-Space와 From-Space.md --- diff --git a/01_Archive/2026-04-20/Tokenomics.md b/01_Archive/2026-04-20/Tokenomics.md index 9008567b..1a919c85 100644 --- a/01_Archive/2026-04-20/Tokenomics.md +++ b/01_Archive/2026-04-20/Tokenomics.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-84C772 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Tokenomics" --- -# [[Tokenomics]] +# [[Tokenomics|Tokenomics]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Tokenomics" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Tokenomics.md]] +- Raw Source: 00_Raw/2026-04-20/Tokenomics.md --- diff --git a/01_Archive/2026-04-20/Topological-Sorting.md b/01_Archive/2026-04-20/Topological-Sorting.md index 202354fd..1f006b60 100644 --- a/01_Archive/2026-04-20/Topological-Sorting.md +++ b/01_Archive/2026-04-20/Topological-Sorting.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-2CF8FE -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Topological-Sorting" --- -# [[Topological-Sorting]] +# [[Topological-Sorting|Topological-Sorting]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Topological-Sorting" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Topological-Sorting.md]] +- Raw Source: 00_Raw/2026-04-20/Topological-Sorting.md --- diff --git a/01_Archive/2026-04-20/Topology-of-Strategy-Spaces.md b/01_Archive/2026-04-20/Topology-of-Strategy-Spaces.md index a1df60fd..23217042 100644 --- a/01_Archive/2026-04-20/Topology-of-Strategy-Spaces.md +++ b/01_Archive/2026-04-20/Topology-of-Strategy-Spaces.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-2D6874 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Topology-of-Strategy-Spaces" --- -# [[Topology-of-Strategy-Spaces]] +# [[Topology-of-Strategy-Spaces|Topology-of-Strategy-Spaces]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Topology-of-Strategy-Spaces" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Topology-of-Strategy-Spaces.md]] +- Raw Source: 00_Raw/2026-04-20/Topology-of-Strategy-Spaces.md --- diff --git a/01_Archive/2026-04-20/Toss Front SDK 기반 외부 연동사 플러그인 개발 생태계 구축.md b/01_Archive/2026-04-20/Toss Front SDK 기반 외부 연동사 플러그인 개발 생태계 구축.md index 7864aa8c..30994bff 100644 --- a/01_Archive/2026-04-20/Toss Front SDK 기반 외부 연동사 플러그인 개발 생태계 구축.md +++ b/01_Archive/2026-04-20/Toss Front SDK 기반 외부 연동사 플러그인 개발 생태계 구축.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-C43BEF -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Toss Front SDK 기반 외부 연동사 플러그인 개발 생태계 구축" --- -# [[Toss Front SDK 기반 외부 연동사 플러그인 개발 생태계 구축]] +# [[Toss Front SDK 기반 외부 연동사 플러그인 개발 생태계 구축|Toss Front SDK 기반 외부 연동사 플러그인 개발 생태계 구축]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 토스플레이스는 자체 개발한 결제 단말기인 'Toss Front(프론트)'에서 동작하는 플러그인 앱을 외부 연동사가 개발할 수 있도록 돕는 SDK를 개발하고 있습니다 [1]. 이는 내부 개발에만 의존하지 않고 서드파티(3rd-party)의 참여를 통해 단말기 생태계를 무한히 확장하기 위한 구조입니다 [1]. 외부 연동사의 휴먼 에러를 방지하고 안정적인 생태계를 구축하기 위해, 토스는 퍼사드(Facade) 패턴을 활용하여 사용자의 의도(Intent)에 맞춘 직관적이고 안전한 SDK 인터페이스를 설계하는 데 집중하고 있습니다 [2, 3]. @@ -24,11 +24,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Toss Front SDK 기반 외부 - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Toss Front SDK]], [[Facade 패턴]], [[Single Responsibility Principle (SRP)]], [[Escape Hatch (탈출구)]] -- **Projects/Contexts:** [[토스플레이스 결제 단말기 생태계 확장]] +- **Related Topics:** [[Toss Front SDK 기반 외부 연동사 플러그인 개발 생태계 구축|Toss Front SDK]], Facade 패턴, [[Single Responsibility Principle (SRP)|Single Responsibility Principle (SRP)]], [[Escape Hatch (탈출구)|Escape Hatch (탈출구)]] +- **Projects/Contexts:** 토스플레이스 결제 단말기 생태계 확장 - **Contradictions/Notes:** 소스 내에 관련된 모순점이나 반대 의견은 존재하지 않습니다. 소스는 Toss Front SDK의 개발자 경험(DX)을 개선하고, 안정성을 확보하며, 휴먼 에러를 구조적으로 방지하기 위해 퍼사드 패턴과 책임 분리를 적용해야 한다는 일관된 주장을 펼치고 있습니다 [1, 3, 8]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/Toss Front SDK 기반 외부 연동사 플러그인 개발 생태계 구축.md]] +- Raw Source: 00_Raw/2026-04-20/Toss Front SDK 기반 외부 연동사 플러그인 개발 생태계 구축.md --- diff --git a/01_Archive/2026-04-20/Toss Front SDK의 Facade 패턴 적용 사례.md b/01_Archive/2026-04-20/Toss Front SDK의 Facade 패턴 적용 사례.md index 8d9c9b36..13d5ff1c 100644 --- a/01_Archive/2026-04-20/Toss Front SDK의 Facade 패턴 적용 사례.md +++ b/01_Archive/2026-04-20/Toss Front SDK의 Facade 패턴 적용 사례.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-E2FE05 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Toss Front SDK의 Facade 패턴 적용 사례" --- -# [[Toss Front SDK의 Facade 패턴 적용 사례]] +# [[Toss Front SDK의 Facade 패턴 적용 사례|Toss Front SDK의 Facade 패턴 적용 사례]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 토스플레이스(Tossplace)에서 자체 개발한 결제 단말기인 Toss Front의 외부 연동 SDK는 사용자의 개발 경험을 향상시키고 휴먼 에러를 방지하기 위해 Facade 패턴을 적용했습니다. [1, 2] 이 패턴은 단순히 내부 기능을 숨기는 것을 넘어, 인증이나 상태 관리 같은 복잡한 내부 구현을 사용자의 '의도(Intent)'를 기준으로 재구성하여 직관적인 인터페이스를 제공하는 데 목적이 있습니다. [3] 결과적으로 80%의 일반적인 사용 사례를 위한 고수준(High-level) 인터페이스와 20%의 세밀한 제어를 위한 저수준(Low-level) 탈출구를 함께 제공하여 편의성과 유연성의 균형을 맞추었습니다. [4, 5] @@ -33,11 +33,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Toss Front SDK의 Facade 패 - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Facade 패턴]], [[단일 책임 원칙(SRP)]], [[Escape Hatch (탈출구)]] -- **Projects/Contexts:** [[Toss Front]], [[토스플레이스 결제 단말기 SDK]] +- **Related Topics:** Facade 패턴, [[단일 책임 원칙(SRP)|단일 책임 원칙(SRP)]], [[Escape Hatch (탈출구)|Escape Hatch (탈출구)]] +- **Projects/Contexts:** Toss Front, 토스플레이스 결제 단말기 SDK - **Contradictions/Notes:** 소스에서는 Facade 패턴이 모든 문제의 정답은 아니며, 추상화 수준이 높아질수록 세밀한 제어가 제한되는 트레이드오프가 발생한다고 지적합니다. 이를 해결하기 위해 편리한 고수준 API에만 안주하지 않고, 언제든 저수준 인터페이스로 내려가 조작할 수 있는 '탈출구(Escape Hatch)'를 제공하여 설계의 균형을 잡아야 한다고 강조합니다. [5, 7] --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/Toss Front SDK의 Facade 패턴 적용 사례.md]] +- Raw Source: 00_Raw/2026-04-20/Toss Front SDK의 Facade 패턴 적용 사례.md --- diff --git a/01_Archive/2026-04-20/Toss SDK의 퍼사드(Facade) 패턴 설계와 인터페이스 전략.md b/01_Archive/2026-04-20/Toss SDK의 퍼사드(Facade) 패턴 설계와 인터페이스 전략.md index 3ff96ab3..64a4da66 100644 --- a/01_Archive/2026-04-20/Toss SDK의 퍼사드(Facade) 패턴 설계와 인터페이스 전략.md +++ b/01_Archive/2026-04-20/Toss SDK의 퍼사드(Facade) 패턴 설계와 인터페이스 전략.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-E3649D -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Toss SDK의 퍼사드(Facade) 패턴 설계와 인터페이스 전략" --- -# [[Toss SDK의 퍼사드(Facade) 패턴 설계와 인터페이스 전략]] +# [[Toss SDK의 퍼사드(Facade) 패턴 설계와 인터페이스 전략|Toss SDK의 퍼사드(Facade) 패턴 설계와 인터페이스 전략]] ## 📌 한 줄 통찰 (The Karpathy Summary) > Toss Front SDK는 외부 연동사가 직관적으로 연동 앱을 개발할 수 있도록 퍼사드(Facade) 패턴을 적용하여 인터페이스를 설계했습니다. 이 설계의 핵심은 단순히 내부 기능을 숨기는 것이 아니라, 복잡한 로직을 사용자의 '의도(Intent)'를 기준으로 재구성하여 제공하는 것입니다. 흔하게 쓰이는 80%의 작업은 고수준 인터페이스로 제공해 편의성을 높이고, 20%의 특수한 상황을 위해 저수준 인터페이스를 탈출구(Escape Hatch)로 남겨두어 편의성과 유연성의 균형을 맞추고 개발자의 인지 부하를 크게 줄입니다. @@ -20,11 +20,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Toss SDK의 퍼사드(Facade) - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Facade Pattern (퍼사드 패턴)]], [[단일 책임 원칙(SRP)]], [[Escape Hatch (탈출구)]] -- **Projects/Contexts:** [[Toss Front SDK 기반 외부 연동사 플러그인 개발 생태계 구축]] +- **Related Topics:** [[Facade Pattern (퍼사드 패턴)|Facade Pattern (퍼사드 패턴)]], [[단일 책임 원칙(SRP)|단일 책임 원칙(SRP)]], [[Escape Hatch (탈출구)|Escape Hatch (탈출구)]] +- **Projects/Contexts:** [[Toss Front SDK 기반 외부 연동사 플러그인 개발 생태계 구축|Toss Front SDK 기반 외부 연동사 플러그인 개발 생태계 구축]] - **Contradictions/Notes:** 내용 간의 상충되는 주장은 존재하지 않습니다. 다만 고수준으로 추상화된 퍼사드 패턴이 사용자 경험(DX)을 극대화하는 반면, SDK 내부적으로는 오케스트레이션 로직의 유지 비용과 복잡성을 심화시킨다는 명확한 트레이드오프가 존재함을 지적하고 있습니다 [6]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/Toss SDK의 퍼사드(Facade) 패턴 설계와 인터페이스 전략.md]] +- Raw Source: 00_Raw/2026-04-20/Toss SDK의 퍼사드(Facade) 패턴 설계와 인터페이스 전략.md --- diff --git a/01_Archive/2026-04-20/Touchpoint-Analysis.md b/01_Archive/2026-04-20/Touchpoint-Analysis.md index 7b302892..29e62fe6 100644 --- a/01_Archive/2026-04-20/Touchpoint-Analysis.md +++ b/01_Archive/2026-04-20/Touchpoint-Analysis.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-5E6FFB -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Touchpoint-Analysis" --- -# [[Touchpoint-Analysis]] +# [[Touchpoint-Analysis|Touchpoint-Analysis]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Touchpoint-Analysis" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Touchpoint-Analysis.md]] +- Raw Source: 00_Raw/2026-04-20/Touchpoint-Analysis.md --- diff --git a/01_Archive/2026-04-20/Trajectory-Planning.md b/01_Archive/2026-04-20/Trajectory-Planning.md index 9a885658..906a4988 100644 --- a/01_Archive/2026-04-20/Trajectory-Planning.md +++ b/01_Archive/2026-04-20/Trajectory-Planning.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-A39C55 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Trajectory-Planning" --- -# [[Trajectory-Planning]] +# [[Trajectory-Planning|Trajectory-Planning]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Trajectory-Planning" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Trajectory-Planning.md]] +- Raw Source: 00_Raw/2026-04-20/Trajectory-Planning.md --- diff --git a/01_Archive/2026-04-20/Transhumanism.md b/01_Archive/2026-04-20/Transhumanism.md index 159822f8..29cfb1e0 100644 --- a/01_Archive/2026-04-20/Transhumanism.md +++ b/01_Archive/2026-04-20/Transhumanism.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-B576FD -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Transhumanism" --- -# [[Transhumanism]] +# [[Transhumanism|Transhumanism]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Transhumanism" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Transhumanism.md]] +- Raw Source: 00_Raw/2026-04-20/Transhumanism.md --- diff --git a/01_Archive/2026-04-20/Transient Hypofrontality.md b/01_Archive/2026-04-20/Transient Hypofrontality.md index dcc75aad..fa5c8925 100644 --- a/01_Archive/2026-04-20/Transient Hypofrontality.md +++ b/01_Archive/2026-04-20/Transient Hypofrontality.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-DFE168 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Transient Hypofrontality" --- -# [[Transient Hypofrontality]] +# [[Transient Hypofrontality|Transient Hypofrontality]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Transient Hypofrontality" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Transient Hypofrontality.md]] +- Raw Source: 00_Raw/2026-04-20/Transient Hypofrontality.md --- diff --git a/01_Archive/2026-04-20/Transient-Hypofrontality.md b/01_Archive/2026-04-20/Transient-Hypofrontality.md index fd44afb6..b7150cc3 100644 --- a/01_Archive/2026-04-20/Transient-Hypofrontality.md +++ b/01_Archive/2026-04-20/Transient-Hypofrontality.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-18B59B -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Transient-Hypofrontality" --- -# [[Transient-Hypofrontality]] +# [[Transient-Hypofrontality|Transient-Hypofrontality]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Transient-Hypofrontality" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Transient-Hypofrontality.md]] +- Raw Source: 00_Raw/2026-04-20/Transient-Hypofrontality.md --- diff --git a/01_Archive/2026-04-20/Transit-Oriented-Development (TOD).md b/01_Archive/2026-04-20/Transit-Oriented-Development (TOD).md index 0d6b7a09..255d644e 100644 --- a/01_Archive/2026-04-20/Transit-Oriented-Development (TOD).md +++ b/01_Archive/2026-04-20/Transit-Oriented-Development (TOD).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-50DD5F -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Transit-Oriented-Development (TOD)" --- -# [[Transit-Oriented-Development (TOD)]] +# [[Transit-Oriented-Development (TOD)|Transit-Oriented-Development (TOD)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Transit-Oriented-Development ( ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Transit-Oriented-Development (TOD).md]] +- Raw Source: 00_Raw/2026-04-20/Transit-Oriented-Development (TOD).md --- diff --git a/01_Archive/2026-04-20/Tree Shaking (번들 크기 최적화).md b/01_Archive/2026-04-20/Tree Shaking (번들 크기 최적화).md index 26cda4d5..a434ba81 100644 --- a/01_Archive/2026-04-20/Tree Shaking (번들 크기 최적화).md +++ b/01_Archive/2026-04-20/Tree Shaking (번들 크기 최적화).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-5A7457 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Tree Shaking (번들 크기 최적화)" --- -# [[Tree Shaking (번들 크기 최적화)]] +# [[Tree Shaking (번들 크기 최적화)|Tree Shaking (번들 크기 최적화)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 최신 모듈 번들러(Webpack, Vite 등)를 사용하여 애플리케이션의 최종 프로덕션 번들에서 사용되지 않는 '죽은 코드(Dead Code)'를 제거함으로써, 전체 자바스크립트 파일 크기를 최적화하는 기법입니다. @@ -31,12 +31,12 @@ github_commit: "[P-Reinforce] Continuous Worker - Tree Shaking (번들 크기 - **정책 변화:** Design & Experience 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Code Splitting & Lazy Loading]], [[React Performance Optimization]], [[Webpack 번들 분석기 (webpack-bundle-analyzer)]], [[First Contentful Paint (FCP) 개선]] -- **Projects/Contexts:** [[대규모 React 프론트엔드 최적화]], [[모바일 웹 성능 향상 프로젝트]] +- **Related Topics:** Code Splitting & Lazy Loading, [[React Performance Optimization|React Performance Optimization]], Webpack 번들 분석기 (webpack-bundle-analyzer), First Contentful Paint (FCP) 개선 +- **Projects/Contexts:** [[대규모 React 프론트엔드 최적화|대규모 React 프론트엔드 최적화]], 모바일 웹 성능 향상 프로젝트 - **Contradictions/Notes:** 모듈을 가져올 때 구조 분해 할당(예: `import { debounce } from 'lodash'`)을 하더라도 해당 라이브러리가 본래 ES6 모듈 기반으로 작성되지 않았다면 전체 코드가 번들에 포함될 수 있습니다. 따라서 `lodash` 대신 Tree Shaking이 지원되는 `lodash-es`를 사용하는 등, 종속성을 추가할 때 라이브러리 자체의 지원 여부를 확인하는 것이 매우 중요합니다. --- _Last updated: 2026-04-14_ -- Raw Source: [[00_Raw/2026-04-20/Tree Shaking (번들 크기 최적화).md]] +- Raw Source: 00_Raw/2026-04-20/Tree Shaking (번들 크기 최적화).md --- diff --git a/01_Archive/2026-04-20/Tree-of-Thought (ToT 사고 트리).md b/01_Archive/2026-04-20/Tree-of-Thought (ToT 사고 트리).md index 14f2e74a..279694f5 100644 --- a/01_Archive/2026-04-20/Tree-of-Thought (ToT 사고 트리).md +++ b/01_Archive/2026-04-20/Tree-of-Thought (ToT 사고 트리).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-E38A5C -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Tree-of-Thought (ToT 사고 트리)" --- -# [[Tree-of-Thought (ToT 사고 트리)]] +# [[Tree-of-Thought (ToT 사고 트리)|Tree-of-Thought (ToT 사고 트리)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Tree-of-Thought (ToT 사고 ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Tree-of-Thought (ToT, 사고 트리).md]] +- Raw Source: 00_Raw/2026-04-20/Tree-of-Thought (ToT, 사고 트리).md --- diff --git a/01_Archive/2026-04-20/Tree-of-Thought (ToT, 사고 트리).md b/01_Archive/2026-04-20/Tree-of-Thought (ToT, 사고 트리).md index 7b8a8662..7c1ea0d0 100644 --- a/01_Archive/2026-04-20/Tree-of-Thought (ToT, 사고 트리).md +++ b/01_Archive/2026-04-20/Tree-of-Thought (ToT, 사고 트리).md @@ -1,4 +1,4 @@ -[[Tree-of-Thought (ToT, 사고 트리)]] +[[Tree-of-Thought (ToT, 사고 트리)|Tree-of-Thought (ToT, 사고 트리)]] 📌 Brief Summary @@ -92,8 +92,8 @@ Tree-of-Thought(ToT)는 LLM이 문제를 선형 단계(Chain-of-Thought)가 아 🔗 Knowledge Connections -- **Related Topics:** [[Chain-of-Thought (CoT, 사고 사슬)]], [[ReAct (Reasoning + Acting)]], [[강화학습 (Reinforcement Learning)]], [[GRPO (Group Relative Policy Optimization)]], [[Multi-Hop Reasoning (다중 홉 추론)]], [[Self-Consistency (자기 일관성)]] -- **Projects/Contexts:** [[AI 추론 시스템]] +- **Related Topics:** [[Chain-of-Thought (CoT, 사고 사슬)|Chain-of-Thought (CoT, 사고 사슬)]], [[ReAct (Reasoning + Acting)|ReAct (Reasoning + Acting)]], [[강화학습 (Reinforcement Learning)|강화학습 (Reinforcement Learning)]], [[GRPO (Group Relative Policy Optimization)|GRPO (Group Relative Policy Optimization)]], [[Multi-Hop Reasoning (다중 홉 추론)|Multi-Hop Reasoning (다중 홉 추론)]], Self-Consistency (자기 일관성) +- **Projects/Contexts:** AI 추론 시스템 - **Contradictions/Notes:** - ToT는 비용 대비 성능 트레이드오프가 극단적 → 실시간 서비스보다 오프라인 배치·연구용으로 적합. - **신규 키워드**: `MCTS (몬테카를로 트리 탐색)`, `Self-Evaluation`, `Backtracking` → 탐색 큐 추가. diff --git a/01_Archive/2026-04-20/Turborepo 기반 모노레포 워크플로우.md b/01_Archive/2026-04-20/Turborepo 기반 모노레포 워크플로우.md index c29737de..79fd607f 100644 --- a/01_Archive/2026-04-20/Turborepo 기반 모노레포 워크플로우.md +++ b/01_Archive/2026-04-20/Turborepo 기반 모노레포 워크플로우.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-5397E2 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Turborepo 기반 모노레포 워크플로우" --- -# [[Turborepo 기반 모노레포 워크플로우]] +# [[Turborepo 기반 모노레포 워크플로우|Turborepo 기반 모노레포 워크플로우]] ## 📌 한 줄 통찰 (The Karpathy Summary) > Turborepo 기반 모노레포 워크플로우는 여러 패키지와 애플리케이션을 단일 저장소에서 효율적으로 관리하기 위해 린팅(ESLint) 및 포매팅(Prettier) 설정의 중복을 줄이고 실행 속도를 최적화하는 개발 프로세스입니다 [1], [2], [3]. 중앙 집중식 설정 패키지와 루트 오케스트레이션(Root Orchestration) 구성을 활용해 각 패키지의 자율성을 보장하면서도 변경된 파일에 대한 부분 검사와 Turborepo의 캐싱 이점을 극대화합니다 [4], [5], [6]. @@ -24,11 +24,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Turborepo 기반 모노레포 - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[ESLint]], [[Prettier]], [[Husky]], [[Lint-staged]] -- **Projects/Contexts:** [[Next.js 애플리케이션]], [[공유 라이브러리(Library) 환경]] +- **Related Topics:** [[ESLint|ESLint]], [[Prettier|Prettier]], [[Husky|Husky]], [[lint-staged|Lint-staged]] +- **Projects/Contexts:** Next.js 애플리케이션, 공유 라이브러리(Library) 환경 - **Contradictions/Notes:** 소스에 상충하는 내용이나 관련 정보가 부족합니다. 다만 기존의 중복되고 분산된 설정 방식과, 중앙 집중화 및 루트 오케스트레이션을 도입한 현대적 방식 간의 개발자 경험(DX) 차이가 극적으로 향상됨을 강조합니다 [1], [9]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Turborepo 기반 모노레포 워크플로우.md]] +- Raw Source: 00_Raw/2026-04-20/Turborepo 기반 모노레포 워크플로우.md --- diff --git a/01_Archive/2026-04-20/Turborepo 환경 구성.md b/01_Archive/2026-04-20/Turborepo 환경 구성.md index 60512cfb..adf36890 100644 --- a/01_Archive/2026-04-20/Turborepo 환경 구성.md +++ b/01_Archive/2026-04-20/Turborepo 환경 구성.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-C5884C -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Turborepo 환경 구성" --- -# [[Turborepo 환경 구성]] +# [[Turborepo 환경 구성|Turborepo 환경 구성]] ## 📌 한 줄 통찰 (The Karpathy Summary) > Turborepo 모노레포 환경에서 ESLint, Prettier, lint-staged를 효율적으로 관리하기 위한 구성 방법입니다 [1]. 여러 패키지에 분산된 중복 설정과 규칙의 불일치 문제를 해결하기 위해 고안되었습니다 [1, 2]. 중앙 집중식 설정 패키지와 루트 오케스트레이션(Root Orchestration)을 결합하여, 각 패키지의 규칙을 존중하면서도 빠르고 확장 가능한 린팅 환경을 제공합니다 [3, 4]. @@ -24,11 +24,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Turborepo 환경 구성" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[ESLint]], [[Prettier]], [[lint-staged]], [[Husky]], [[Monorepo]] -- **Projects/Contexts:** [[Turborepo 기반 다중 패키지 프로젝트의 린팅 및 코드 포매팅 자동화 파이프라인 구축]] +- **Related Topics:** [[ESLint|ESLint]], [[Prettier|Prettier]], [[lint-staged|lint-staged]], [[Husky|Husky]], [[Monorepo|Monorepo]] +- **Projects/Contexts:** Turborepo 기반 다중 패키지 프로젝트의 린팅 및 코드 포매팅 자동화 파이프라인 구축 - **Contradictions/Notes:** 소스는 ESLint 9의 평면 구성 형식을 기준으로 최적의 환경 구성법을 제안하고 있습니다. 만약 ESLint 8 환경을 이용할 경우에는 `eslint.config.mjs` 대신 `.eslintrc.js`를 사용하고 ES 모듈 대신 CommonJS를 사용해야 하는 등 이전 형식에 맞춘 구조적 조정이 별도로 필요합니다 [11]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Turborepo 환경 구성.md]] +- Raw Source: 00_Raw/2026-04-20/Turborepo 환경 구성.md --- diff --git a/01_Archive/2026-04-20/Turborepo-Orchestration.md b/01_Archive/2026-04-20/Turborepo-Orchestration.md index d888bd38..640cf08b 100644 --- a/01_Archive/2026-04-20/Turborepo-Orchestration.md +++ b/01_Archive/2026-04-20/Turborepo-Orchestration.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-05096A -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Turborepo-Orchestration" --- -# [[Turborepo-Orchestration]] +# [[Turborepo-Orchestration|Turborepo-Orchestration]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Turborepo-Orchestration" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Turborepo-Orchestration.md]] +- Raw Source: 00_Raw/2026-04-20/Turborepo-Orchestration.md --- diff --git a/01_Archive/2026-04-20/Turborepo.md b/01_Archive/2026-04-20/Turborepo.md index 486a3bd2..2e35c053 100644 --- a/01_Archive/2026-04-20/Turborepo.md +++ b/01_Archive/2026-04-20/Turborepo.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-9E8212 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Turborepo" --- -# [[Turborepo]] +# [[Turborepo|Turborepo]] ## 📌 한 줄 통찰 (The Karpathy Summary) > Turborepo는 여러 애플리케이션과 라이브러리 패키지를 하나의 저장소에서 관리하는 모노레포(Monorepo) 환경을 위한 빌드 도구입니다 [1, 2]. 작업 결과를 저장하고 재사용하는 캐싱(Caching) 기능을 지원하여 개발 워크플로우와 커밋 속도를 크게 향상시킵니다 [3, 4]. Nx, Bazel, Lerna 등과 함께 대표적인 모노레포 관리 솔루션 중 하나로 꼽힙니다 [5]. @@ -22,11 +22,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Turborepo" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Monorepo]], [[ESLint]], [[Prettier]] -- **Projects/Contexts:** [[Next.js]], [[Husky]], [[lint-staged]] +- **Related Topics:** [[Monorepo|Monorepo]], [[ESLint|ESLint]], [[Prettier|Prettier]] +- **Projects/Contexts:** [[Next.js|Next.js]], [[Husky|Husky]], [[lint-staged|lint-staged]] - **Contradictions/Notes:** 소스에 관련 정보가 부족합니다. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Turborepo.md]] +- Raw Source: 00_Raw/2026-04-20/Turborepo.md --- diff --git a/01_Archive/2026-04-20/Turborepo를 활용한 다중 애플리케이션 및 라이브러리 통합 관리.md b/01_Archive/2026-04-20/Turborepo를 활용한 다중 애플리케이션 및 라이브러리 통합 관리.md index cf03490d..87fe61b8 100644 --- a/01_Archive/2026-04-20/Turborepo를 활용한 다중 애플리케이션 및 라이브러리 통합 관리.md +++ b/01_Archive/2026-04-20/Turborepo를 활용한 다중 애플리케이션 및 라이브러리 통합 관리.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-F2D6B7 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Turborepo를 활용한 다중 애플리케이션 및 라이브러리 통합 관리" --- -# [[Turborepo를 활용한 다중 애플리케이션 및 라이브러리 통합 관리]] +# [[Turborepo를 활용한 다중 애플리케이션 및 라이브러리 통합 관리|Turborepo를 활용한 다중 애플리케이션 및 라이브러리 통합 관리]] ## 📌 한 줄 통찰 (The Karpathy Summary) > Turborepo를 활용한 모노레포(Monorepo) 환경에서 다중 애플리케이션(Next.js 등) 및 공유 라이브러리의 린팅(ESLint)과 포매팅(Prettier)을 효율적으로 통합 관리하는 아키텍처에 대한 내용입니다. 중앙 집중식 설정 패키지와 루트 오케스트레이션(Root Orchestration) 기법을 도입함으로써, 패키지별 설정 중복을 방지하고 각 프로젝트의 자율성을 보장하면서도 일관되고 빠른 코드 품질 관리를 달성할 수 있습니다. @@ -30,11 +30,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Turborepo를 활용한 다중 - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[모노레포(Monorepo)]], [[ESLint 및 Prettier 통합]], [[lint-staged와 Husky]] -- **Projects/Contexts:** [[Turborepo 기반의 확장 가능한 프론트엔드 환경 구축 및 중앙 집중형 코드 거버넌스]] +- **Related Topics:** 모노레포(Monorepo), ESLint 및 Prettier 통합, lint-staged와 Husky +- **Projects/Contexts:** Turborepo 기반의 확장 가능한 프론트엔드 환경 구축 및 중앙 집중형 코드 거버넌스 - **Contradictions/Notes:** 모노레포 내 각 패키지마다 독립된 설정과 의존성을 중복해서 유지하는 전통적인 방식에 반대하며, 단일 진실 공급원(Single source of truth) 역할을 하는 전용 설정 패키지를 구축하여 루트에서 일괄 오케스트레이션하는 현대적이고 통합적인 관리 체계를 지향합니다 [2, 6, 10]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Turborepo를 활용한 다중 애플리케이션 및 라이브러리 통합 관리.md]] +- Raw Source: 00_Raw/2026-04-20/Turborepo를 활용한 다중 애플리케이션 및 라이브러리 통합 관리.md --- diff --git a/01_Archive/2026-04-20/Turtle-Graphics.md b/01_Archive/2026-04-20/Turtle-Graphics.md index ddc4a9dc..1ef28ccc 100644 --- a/01_Archive/2026-04-20/Turtle-Graphics.md +++ b/01_Archive/2026-04-20/Turtle-Graphics.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-51C40D -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Turtle-Graphics" --- -# [[Turtle-Graphics]] +# [[Turtle-Graphics|Turtle-Graphics]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Turtle-Graphics" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Turtle-Graphics.md]] +- Raw Source: 00_Raw/2026-04-20/Turtle-Graphics.md --- diff --git a/01_Archive/2026-04-20/Type Alias.md b/01_Archive/2026-04-20/Type Alias.md index fca16223..4c39ac90 100644 --- a/01_Archive/2026-04-20/Type Alias.md +++ b/01_Archive/2026-04-20/Type Alias.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-D2A4B8 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Type Alias" --- -# [[Type Alias]] +# [[Type Alias|Type Alias]] ## 📌 한 줄 통찰 (The Karpathy Summary) > Type Alias(타입 별칭)는 기존 타입에 새로운 이름을 부여하는 TypeScript의 타입 정의 방식이다 [1]. 인터페이스(Interface)와 유사하게 객체의 형태를 정의할 수 있지만, 이에 국한되지 않고 원시 타입(primitives), 유니온(unions), 튜플(tuples) 등 복잡한 타입 구성에도 이름을 지정할 수 있다 [1]. 동일한 이름으로 재선언 시 병합되지 않고 에러를 발생시키므로, 예기치 않은 타입 확장을 방지하는 엄격한 코드 관리에 유용하다 [2, 3]. @@ -22,11 +22,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Type Alias" - **정책 변화:** Design & Experience 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Interface]], [[Union Types]], [[Intersection Types]] -- **Projects/Contexts:** [[TypeScript Type System 설계]], [[대규모 애플리케이션의 도메인 모델링]] +- **Related Topics:** [[인터페이스 (Interface)|Interface]], [[Union Types|Union Types]], [[교집합 타입 (Intersection Types)|Intersection Types]] +- **Projects/Contexts:** TypeScript Type System 설계, 대규모 애플리케이션의 도메인 모델링 - **Contradictions/Notes:** 소스 내 개발자 커뮤니티에서는 Type Alias와 Interface의 사용을 두고 뚜렷한 논쟁이 존재한다. 일부 개발자들은 선언 병합으로 인한 잠재적 오류를 피하고 일관성을 유지하기 위해 전적으로 Type Alias만 사용할 것을 주장한다 [2, 4, 11]. 반면, TypeScript 공식 가이드 및 다른 개발자들은 컴파일러 캐싱에 따른 성능 최적화와 에러 메시지의 직관성(불투명한 이름 표시)을 이유로 Interface를 기본으로 사용해야 한다고 반론한다 [7, 12-15]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/Type Alias.md]] +- Raw Source: 00_Raw/2026-04-20/Type Alias.md --- diff --git a/01_Archive/2026-04-20/Type Branding.md b/01_Archive/2026-04-20/Type Branding.md index cfb884a1..fa61435c 100644 --- a/01_Archive/2026-04-20/Type Branding.md +++ b/01_Archive/2026-04-20/Type Branding.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-62F9F5 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Type Branding" --- -# [[Type Branding]] +# [[Type Branding|Type Branding]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Type Branding" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Type Branding.md]] +- Raw Source: 00_Raw/2026-04-20/Type Branding.md --- diff --git a/01_Archive/2026-04-20/Type Casting.md b/01_Archive/2026-04-20/Type Casting.md index 5300bf9e..a6298b15 100644 --- a/01_Archive/2026-04-20/Type Casting.md +++ b/01_Archive/2026-04-20/Type Casting.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-2B5557 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Type Casting" --- -# [[Type Casting]] +# [[Type Casting|Type Casting]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 타입 캐스팅(Type Casting) 또는 타입 단언(Type Assertion)은 개발자가 TypeScript 컴파일러보다 값의 타입에 대해 더 잘 알고 있을 때, 컴파일러에게 특정 값의 타입을 지정하도록 강제하는 방법입니다 [1]. 다른 언어의 타입 캐스트와 유사하지만 데이터의 구조를 재구성(restructuring)하거나 특별한 검사를 수행하지 않으며, 런타임 동작에 아무런 영향을 주지 않습니다 [1]. 이는 오로지 컴파일러에 의해서만 소비되며, 개발자가 값의 타입을 확신할 때 예외적으로 사용해야 합니다 [1, 2]. @@ -23,11 +23,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Type Casting" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Type Assertion]], [[Type Guards]], [[Satisfies Operator]], [[Branded Types]], [[unknown]] -- **Projects/Contexts:** [[DOM Manipulation]], [[Type System Design]] +- **Related Topics:** [[타입 단언(Type Assertion)|Type Assertion]], [[타입 가드 (Type Guards)|Type Guards]], [[Satisfies Operator|Satisfies Operator]], [[Branded Types|Branded Types]], unknown +- **Projects/Contexts:** DOM Manipulation, Type System Design - **Contradictions/Notes:** 소스에서는 `as` 키워드를 사용한 타입 캐스팅이 타입 에러를 우회하는 강력한 수단이지만, 초과 속성 검사를 건너뛰어 안전성을 훼손하므로, 구조적 엄격함을 유지해야 하는 데이터 변환 및 매핑 상황에서는 캐스팅보다 `satisfies` 키워드를 사용하는 것을 우선적으로 권장합니다 [8, 9]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/Type Casting.md]] +- Raw Source: 00_Raw/2026-04-20/Type Casting.md --- diff --git a/01_Archive/2026-04-20/Type Declaration.md b/01_Archive/2026-04-20/Type Declaration.md index b26ab9fe..76c854cf 100644 --- a/01_Archive/2026-04-20/Type Declaration.md +++ b/01_Archive/2026-04-20/Type Declaration.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-D3F069 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Type Declaration" --- -# [[Type Declaration]] +# [[Type Declaration|Type Declaration]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 타입 선언(Type Declaration)은 TypeScript에서 변수, 함수, 객체 등의 데이터 형태와 규칙을 명시적으로 정의하여 시스템의 예측 가능성을 높이는 과정이다[1, 2]. 주로 `type` 별칭(Type Alias)이나 `interface` 키워드를 사용하여 정의하며, 외부 자바스크립트 라이브러리 사용 시에는 구현부 없이 타입 정보만 제공하는 `.d.ts` 선언 파일을 통해 활용된다[3]. 타입 단언(Type Assertion) 방식과 달리, 명시적인 타입 선언을 활용하면 컴파일러의 엄격한 구조적 타입 검사를 통해 런타임 에러를 사전에 방지할 수 있다[1]. @@ -23,11 +23,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Type Declaration" - **정책 변화:** Design & Experience 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Type Alias]], [[Interface]], [[Type Assertion]], [[Declaration Merging]], [[Type Inference]] -- **Projects/Contexts:** [[TypeScript Type System]], [[TypeScript Best Practices]] +- **Related Topics:** [[Type Alias|Type Alias]], [[인터페이스 (Interface)|Interface]], [[타입 단언(Type Assertion)|Type Assertion]], [[Declaration Merging|Declaration Merging]], [[Type Inference|Type Inference]] +- **Projects/Contexts:** [[TypeScript-Type-System|TypeScript Type System]], TypeScript Best Practices - **Contradictions/Notes:** 객체 타입을 선언할 때 `interface`와 `type` 중 어느 것을 사용할지에 대한 개발자 간의 선호도 논쟁이 존재한다. 일부는 선언 병합의 이점과 성능 최적화를 위해 `interface`를 선호하지만[8-10], 다른 진영에서는 의도치 않은 선언 병합에 의한 오작동을 막고 오류를 명확히 잡기 위해 `type` 선언을 엄격히 사용하는 것을 지향한다[6, 11]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/Type Declaration.md]] +- Raw Source: 00_Raw/2026-04-20/Type Declaration.md --- diff --git a/01_Archive/2026-04-20/Type Definition Files (DefinitelyTyped).md b/01_Archive/2026-04-20/Type Definition Files (DefinitelyTyped).md index 177483ee..c9e03764 100644 --- a/01_Archive/2026-04-20/Type Definition Files (DefinitelyTyped).md +++ b/01_Archive/2026-04-20/Type Definition Files (DefinitelyTyped).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-CF3F9B -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Type Definition Files (DefinitelyTyped)" --- -# [[Type Definition Files (DefinitelyTyped)]] +# [[Type Definition Files (DefinitelyTyped)|Type Definition Files (DefinitelyTyped)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Type Definition Files (Definit ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Type Definition Files (DefinitelyTyped).md]] +- Raw Source: 00_Raw/2026-04-20/Type Definition Files (DefinitelyTyped).md --- diff --git a/01_Archive/2026-04-20/Type Inference.md b/01_Archive/2026-04-20/Type Inference.md index 341b178e..88222f1e 100644 --- a/01_Archive/2026-04-20/Type Inference.md +++ b/01_Archive/2026-04-20/Type Inference.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-75C521 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Type Inference" --- -# [[Type Inference]] +# [[Type Inference|Type Inference]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Type Inference" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Type Inference.md]] +- Raw Source: 00_Raw/2026-04-20/Type Inference.md --- diff --git a/01_Archive/2026-04-20/Type Narrowing.md b/01_Archive/2026-04-20/Type Narrowing.md index 08b5946d..59cffe94 100644 --- a/01_Archive/2026-04-20/Type Narrowing.md +++ b/01_Archive/2026-04-20/Type Narrowing.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-325DC7 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Type Narrowing" --- -# [[Type Narrowing]] +# [[Type Narrowing|Type Narrowing]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -33,11 +33,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Type Narrowing" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Type Guards]], [[Discriminated Unions]], [[Union Types]], [[Type Predicates]] +- **Related Topics:** [[타입 가드 (Type Guards)|Type Guards]], [[Discriminated Unions|Discriminated Unions]], [[Union Types|Union Types]], [[Type Predicates|Type Predicates]] - **Projects/Contexts:** 알 수 없는 외부 데이터를 수신하는 상황(`unknown` 타입 처리), API 응답 상태(loading/success/error), Redux 리듀서 액션, 또는 다단계 폼 및 라우터 상태 등 다형성 데이터를 구별하여 안전하게 처리해야 하는 구조적 맥락에서 빈번하게 사용됩니다 [3, 12, 13]. - **Contradictions/Notes:** 컴파일러에게 개발자가 직접 타입을 가정하도록 강제하는 타입 단언(Type Assertions, `as` 키워드 사용)과 달리, 타입 좁히기(Type Narrowing)는 코드의 제어 흐름과 타입 가드를 기반으로 타입스크립트가 스스로 안전하게 타입을 추론하고 좁힌다는 점에서 안전성 면에서 큰 차이가 있습니다 [3, 9, 14, 15]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/Type Narrowing.md]] +- Raw Source: 00_Raw/2026-04-20/Type Narrowing.md --- diff --git a/01_Archive/2026-04-20/Type Predicates.md b/01_Archive/2026-04-20/Type Predicates.md index 86ef9e96..54a6c530 100644 --- a/01_Archive/2026-04-20/Type Predicates.md +++ b/01_Archive/2026-04-20/Type Predicates.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-1D7E99 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Type Predicates" --- -# [[Type Predicates]] +# [[Type Predicates|Type Predicates]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Type Predicates" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Type Predicates.md]] +- Raw Source: 00_Raw/2026-04-20/Type Predicates.md --- diff --git a/01_Archive/2026-04-20/Type Theory.md b/01_Archive/2026-04-20/Type Theory.md index 4d1c1b5c..3e4d92a4 100644 --- a/01_Archive/2026-04-20/Type Theory.md +++ b/01_Archive/2026-04-20/Type Theory.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AI-054 -category: "[[10_Wiki/💡 Topics/Programming & Formal Methods]]" +category: "10_Wiki/💡 Topics/Programming & Formal Methods" confidence_score: 0.96 tags: [type theory, formal verification, type system, compiler] last_reinforced: 2026-06-XX github_commit: "[P-Reinforce] Processed Type Theory." --- -# [[Type Theory]] (타입 이론) +# [[Type Theory|Type Theory]] (타입 이론) ## 📌 한 줄 통찰 (The Karpathy Summary) > 프로그래밍 언어의 타입 시스템을 수학적 공리(Axiom)와 논리학에 기반하여 분석하고, 프로그램의 안전성과 정확성을 컴파일 타임에 증명하는 학문이다. @@ -24,7 +24,7 @@ github_commit: "[P-Reinforce] Processed Type Theory." - **정책 변화:** 타입 시스템은 언어 차원의 기능뿐만 아니라, 도메인 모델링(DDD)의 규칙을 코드로 강제하는 도구로 활용되어 그 가치가 극대화되고 있다. ## 🔗 지식 연결 (Graph) -- Parent: [[Type Safety]] -- Related: [[Formal Methods in Software Engineering]] , [[Algebraic-Data-Types]] , [[TypeScript Type System]] -- Raw Source: [[00_Raw/Type Theory.md]] +- Parent: [[Type-Safety|Type Safety]] +- Related: [[Formal-Methods-in-Software-Engineering|Formal Methods in Software Engineering]] , [[Algebraic-Data-Types|Algebraic-Data-Types]] , [[TypeScript-Type-System|TypeScript Type System]] +- Raw Source: 00_Raw/Type Theory.md --- \ No newline at end of file diff --git a/01_Archive/2026-04-20/Type-Assertion.md b/01_Archive/2026-04-20/Type-Assertion.md index 1b87f742..676b1139 100644 --- a/01_Archive/2026-04-20/Type-Assertion.md +++ b/01_Archive/2026-04-20/Type-Assertion.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-1404CE -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Type-Assertion" --- -# [[Type-Assertion]] +# [[Type-Assertion|Type-Assertion]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Type-Assertion" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Type-Assertion.md]] +- Raw Source: 00_Raw/2026-04-20/Type-Assertion.md --- diff --git a/01_Archive/2026-04-20/Type-Aware-Linting.md b/01_Archive/2026-04-20/Type-Aware-Linting.md index 1ace3b43..e7cb0958 100644 --- a/01_Archive/2026-04-20/Type-Aware-Linting.md +++ b/01_Archive/2026-04-20/Type-Aware-Linting.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-CAD7C2 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Type-Aware-Linting" --- -# [[Type-Aware-Linting]] +# [[Type-Aware-Linting|Type-Aware-Linting]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Type-Aware-Linting" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Type-Aware-Linting.md]] +- Raw Source: 00_Raw/2026-04-20/Type-Aware-Linting.md --- diff --git a/01_Archive/2026-04-20/Type-Compatibility-Rules.md b/01_Archive/2026-04-20/Type-Compatibility-Rules.md index e875d1c6..28377dd6 100644 --- a/01_Archive/2026-04-20/Type-Compatibility-Rules.md +++ b/01_Archive/2026-04-20/Type-Compatibility-Rules.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-A6932F -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Type-Compatibility-Rules" --- -# [[Type-Compatibility-Rules]] +# [[Type-Compatibility-Rules|Type-Compatibility-Rules]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Type-Compatibility-Rules" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Type-Compatibility-Rules.md]] +- Raw Source: 00_Raw/2026-04-20/Type-Compatibility-Rules.md --- diff --git a/01_Archive/2026-04-20/Type-Compatibility-and-Subtyping.md b/01_Archive/2026-04-20/Type-Compatibility-and-Subtyping.md index 5d870cf8..68e6b112 100644 --- a/01_Archive/2026-04-20/Type-Compatibility-and-Subtyping.md +++ b/01_Archive/2026-04-20/Type-Compatibility-and-Subtyping.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-DAF93E -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Type-Compatibility-and-Subtyping" --- -# [[Type-Compatibility-and-Subtyping]] +# [[Type-Compatibility-and-Subtyping|Type-Compatibility-and-Subtyping]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Type-Compatibility-and-Subtypi ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Type-Compatibility-and-Subtyping.md]] +- Raw Source: 00_Raw/2026-04-20/Type-Compatibility-and-Subtyping.md --- diff --git a/01_Archive/2026-04-20/Type-Compatibility.md b/01_Archive/2026-04-20/Type-Compatibility.md index 9d97f169..f046d80e 100644 --- a/01_Archive/2026-04-20/Type-Compatibility.md +++ b/01_Archive/2026-04-20/Type-Compatibility.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-BEFC96 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Type-Compatibility" --- -# [[Type-Compatibility]] +# [[Type-Compatibility|Type-Compatibility]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Type-Compatibility" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Type-Compatibility.md]] +- Raw Source: 00_Raw/2026-04-20/Type-Compatibility.md --- diff --git a/01_Archive/2026-04-20/Type-Composition-via-Intersection-Types.md b/01_Archive/2026-04-20/Type-Composition-via-Intersection-Types.md index a81ee9bc..16b3bed1 100644 --- a/01_Archive/2026-04-20/Type-Composition-via-Intersection-Types.md +++ b/01_Archive/2026-04-20/Type-Composition-via-Intersection-Types.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-FBAE38 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Type-Composition-via-Intersection-Types" --- -# [[Type-Composition-via-Intersection-Types]] +# [[Type-Composition-via-Intersection-Types|Type-Composition-via-Intersection-Types]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Type-Composition-via-Intersect ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Type-Composition-via-Intersection-Types.md]] +- Raw Source: 00_Raw/2026-04-20/Type-Composition-via-Intersection-Types.md --- diff --git a/01_Archive/2026-04-20/Type-Composition-via-Intersections.md b/01_Archive/2026-04-20/Type-Composition-via-Intersections.md index d5102adb..105473fc 100644 --- a/01_Archive/2026-04-20/Type-Composition-via-Intersections.md +++ b/01_Archive/2026-04-20/Type-Composition-via-Intersections.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-F4AFF9 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Type-Composition-via-Intersections" --- -# [[Type-Composition-via-Intersections]] +# [[Type-Composition-via-Intersections|Type-Composition-via-Intersections]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Type-Composition-via-Intersect ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Type-Composition-via-Intersections.md]] +- Raw Source: 00_Raw/2026-04-20/Type-Composition-via-Intersections.md --- diff --git a/01_Archive/2026-04-20/Type-Driven-Development.md b/01_Archive/2026-04-20/Type-Driven-Development.md index b4d6cd20..c551c112 100644 --- a/01_Archive/2026-04-20/Type-Driven-Development.md +++ b/01_Archive/2026-04-20/Type-Driven-Development.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-1CC60F -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Type-Driven-Development" --- -# [[Type-Driven-Development]] +# [[Type-Driven-Development|Type-Driven-Development]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Type-Driven-Development" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Type-Driven-Development.md]] +- Raw Source: 00_Raw/2026-04-20/Type-Driven-Development.md --- diff --git a/01_Archive/2026-04-20/Type-Erasure-and-Runtime-Behavior.md b/01_Archive/2026-04-20/Type-Erasure-and-Runtime-Behavior.md index 8b70ad22..7584cd4f 100644 --- a/01_Archive/2026-04-20/Type-Erasure-and-Runtime-Behavior.md +++ b/01_Archive/2026-04-20/Type-Erasure-and-Runtime-Behavior.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-BD9DA5 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Type-Erasure-and-Runtime-Behavior" --- -# [[Type-Erasure-and-Runtime-Behavior]] +# [[Type-Erasure-and-Runtime-Behavior|Type-Erasure-and-Runtime-Behavior]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Type-Erasure-and-Runtime-Behav ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Type-Erasure-and-Runtime-Behavior.md]] +- Raw Source: 00_Raw/2026-04-20/Type-Erasure-and-Runtime-Behavior.md --- diff --git a/01_Archive/2026-04-20/Type-Erasure.md b/01_Archive/2026-04-20/Type-Erasure.md index 0497a966..a462b239 100644 --- a/01_Archive/2026-04-20/Type-Erasure.md +++ b/01_Archive/2026-04-20/Type-Erasure.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-565E28 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Type-Erasure" --- -# [[Type-Erasure]] +# [[Type-Erasure|Type-Erasure]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Type-Erasure" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Type-Erasure.md]] +- Raw Source: 00_Raw/2026-04-20/Type-Erasure.md --- diff --git a/01_Archive/2026-04-20/Type-Guards-and-Narrowing.md b/01_Archive/2026-04-20/Type-Guards-and-Narrowing.md index 489013fb..c990da2a 100644 --- a/01_Archive/2026-04-20/Type-Guards-and-Narrowing.md +++ b/01_Archive/2026-04-20/Type-Guards-and-Narrowing.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-9DB0ED -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Type-Guards-and-Narrowing" --- -# [[Type-Guards-and-Narrowing]] +# [[Type-Guards-and-Narrowing|Type-Guards-and-Narrowing]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Type-Guards-and-Narrowing" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Type-Guards-and-Narrowing.md]] +- Raw Source: 00_Raw/2026-04-20/Type-Guards-and-Narrowing.md --- diff --git a/01_Archive/2026-04-20/Type-Guards.md b/01_Archive/2026-04-20/Type-Guards.md index 0ac69c2e..26cb2fb1 100644 --- a/01_Archive/2026-04-20/Type-Guards.md +++ b/01_Archive/2026-04-20/Type-Guards.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-1B3627 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Type-Guards" --- -# [[Type-Guards]] +# [[Type-Guards|Type-Guards]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Type-Guards" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Type-Guards.md]] +- Raw Source: 00_Raw/2026-04-20/Type-Guards.md --- diff --git a/01_Archive/2026-04-20/Type-Inference-Algorithms.md b/01_Archive/2026-04-20/Type-Inference-Algorithms.md index e58d9840..fd2c7b6e 100644 --- a/01_Archive/2026-04-20/Type-Inference-Algorithms.md +++ b/01_Archive/2026-04-20/Type-Inference-Algorithms.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-0EC835 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Type-Inference-Algorithms" --- -# [[Type-Inference-Algorithms]] +# [[Type-Inference-Algorithms|Type-Inference-Algorithms]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Type-Inference-Algorithms" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Type-Inference-Algorithms.md]] +- Raw Source: 00_Raw/2026-04-20/Type-Inference-Algorithms.md --- diff --git a/01_Archive/2026-04-20/Type-Inference.md b/01_Archive/2026-04-20/Type-Inference.md index d8503fd1..af1acbf7 100644 --- a/01_Archive/2026-04-20/Type-Inference.md +++ b/01_Archive/2026-04-20/Type-Inference.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-37FB9B -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Type-Inference" --- -# [[Type-Inference]] +# [[Type-Inference|Type-Inference]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Type-Inference" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Type-Inference.md]] +- Raw Source: 00_Raw/2026-04-20/Type-Inference.md --- diff --git a/01_Archive/2026-04-20/Type-Intersection.md b/01_Archive/2026-04-20/Type-Intersection.md index 0e5645db..9f25fd54 100644 --- a/01_Archive/2026-04-20/Type-Intersection.md +++ b/01_Archive/2026-04-20/Type-Intersection.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-D16150 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Type-Intersection" --- -# [[Type-Intersection]] +# [[Type-Intersection|Type-Intersection]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Type-Intersection" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Type-Intersection.md]] +- Raw Source: 00_Raw/2026-04-20/Type-Intersection.md --- diff --git a/01_Archive/2026-04-20/Type-Narrowing-Mechanisms.md b/01_Archive/2026-04-20/Type-Narrowing-Mechanisms.md index 2a096030..0f88ada2 100644 --- a/01_Archive/2026-04-20/Type-Narrowing-Mechanisms.md +++ b/01_Archive/2026-04-20/Type-Narrowing-Mechanisms.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-8D1630 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Type-Narrowing-Mechanisms" --- -# [[Type-Narrowing-Mechanisms]] +# [[Type-Narrowing-Mechanisms|Type-Narrowing-Mechanisms]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Type-Narrowing-Mechanisms" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Type-Narrowing-Mechanisms.md]] +- Raw Source: 00_Raw/2026-04-20/Type-Narrowing-Mechanisms.md --- diff --git a/01_Archive/2026-04-20/Type-Narrowing-and-Control-Flow-Analysis.md b/01_Archive/2026-04-20/Type-Narrowing-and-Control-Flow-Analysis.md index d786c7fb..71f7c7bf 100644 --- a/01_Archive/2026-04-20/Type-Narrowing-and-Control-Flow-Analysis.md +++ b/01_Archive/2026-04-20/Type-Narrowing-and-Control-Flow-Analysis.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-DD413B -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Type-Narrowing-and-Control-Flow-Analysis" --- -# [[Type-Narrowing-and-Control-Flow-Analysis]] +# [[Type-Narrowing-and-Control-Flow-Analysis|Type-Narrowing-and-Control-Flow-Analysis]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Type-Narrowing-and-Control-Flo ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Type-Narrowing-and-Control-Flow-Analysis.md]] +- Raw Source: 00_Raw/2026-04-20/Type-Narrowing-and-Control-Flow-Analysis.md --- diff --git a/01_Archive/2026-04-20/Type-Narrowing-and-Guards.md b/01_Archive/2026-04-20/Type-Narrowing-and-Guards.md index ee3d32a3..7e807d4c 100644 --- a/01_Archive/2026-04-20/Type-Narrowing-and-Guards.md +++ b/01_Archive/2026-04-20/Type-Narrowing-and-Guards.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-D8EC83 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Type-Narrowing-and-Guards" --- -# [[Type-Narrowing-and-Guards]] +# [[Type-Narrowing-and-Guards|Type-Narrowing-and-Guards]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Type-Narrowing-and-Guards" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Type-Narrowing-and-Guards.md]] +- Raw Source: 00_Raw/2026-04-20/Type-Narrowing-and-Guards.md --- diff --git a/01_Archive/2026-04-20/Type-Narrowing.md b/01_Archive/2026-04-20/Type-Narrowing.md index 76080a5e..cec16cf4 100644 --- a/01_Archive/2026-04-20/Type-Narrowing.md +++ b/01_Archive/2026-04-20/Type-Narrowing.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-60D972 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Type-Narrowing" --- -# [[Type-Narrowing]] +# [[Type-Narrowing|Type-Narrowing]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Type-Narrowing" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Type-Narrowing.md]] +- Raw Source: 00_Raw/2026-04-20/Type-Narrowing.md --- diff --git a/01_Archive/2026-04-20/Type-Predicates.md b/01_Archive/2026-04-20/Type-Predicates.md index 6d1f306a..8d03847b 100644 --- a/01_Archive/2026-04-20/Type-Predicates.md +++ b/01_Archive/2026-04-20/Type-Predicates.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-62E7D2 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Type-Predicates" --- -# [[Type-Predicates]] +# [[Type-Predicates|Type-Predicates]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Type-Predicates" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Type-Predicates.md]] +- Raw Source: 00_Raw/2026-04-20/Type-Predicates.md --- diff --git a/01_Archive/2026-04-20/Type-Safe-API-Design.md b/01_Archive/2026-04-20/Type-Safe-API-Design.md index dbc9786f..e5b6d45e 100644 --- a/01_Archive/2026-04-20/Type-Safe-API-Design.md +++ b/01_Archive/2026-04-20/Type-Safe-API-Design.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-BDDBAD -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Type-Safe-API-Design" --- -# [[Type-Safe-API-Design]] +# [[Type-Safe-API-Design|Type-Safe-API-Design]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Type-Safe-API-Design" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Type-Safe-API-Design.md]] +- Raw Source: 00_Raw/2026-04-20/Type-Safe-API-Design.md --- diff --git a/01_Archive/2026-04-20/Type-Safety-and-Exhaustiveness-Checking.md b/01_Archive/2026-04-20/Type-Safety-and-Exhaustiveness-Checking.md index e4868c9f..984c51f3 100644 --- a/01_Archive/2026-04-20/Type-Safety-and-Exhaustiveness-Checking.md +++ b/01_Archive/2026-04-20/Type-Safety-and-Exhaustiveness-Checking.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-5C9108 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Type-Safety-and-Exhaustiveness-Checking" --- -# [[Type-Safety-and-Exhaustiveness-Checking]] +# [[Type-Safety-and-Exhaustiveness-Checking|Type-Safety-and-Exhaustiveness-Checking]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Type-Safety-and-Exhaustiveness ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Type-Safety-and-Exhaustiveness-Checking.md]] +- Raw Source: 00_Raw/2026-04-20/Type-Safety-and-Exhaustiveness-Checking.md --- diff --git a/01_Archive/2026-04-20/Type-Safety-in-Distributed-Systems.md b/01_Archive/2026-04-20/Type-Safety-in-Distributed-Systems.md index 86cb59ed..303682f5 100644 --- a/01_Archive/2026-04-20/Type-Safety-in-Distributed-Systems.md +++ b/01_Archive/2026-04-20/Type-Safety-in-Distributed-Systems.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-D64613 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Type-Safety-in-Distributed-Systems" --- -# [[Type-Safety-in-Distributed-Systems]] +# [[Type-Safety-in-Distributed-Systems|Type-Safety-in-Distributed-Systems]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Type-Safety-in-Distributed-Sys ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Type-Safety-in-Distributed-Systems.md]] +- Raw Source: 00_Raw/2026-04-20/Type-Safety-in-Distributed-Systems.md --- diff --git a/01_Archive/2026-04-20/Type-Safety-in-Domain-Driven-Design.md b/01_Archive/2026-04-20/Type-Safety-in-Domain-Driven-Design.md index 8be9bee6..ef432c32 100644 --- a/01_Archive/2026-04-20/Type-Safety-in-Domain-Driven-Design.md +++ b/01_Archive/2026-04-20/Type-Safety-in-Domain-Driven-Design.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-C88D89 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Type-Safety-in-Domain-Driven-Design" --- -# [[Type-Safety-in-Domain-Driven-Design]] +# [[Type-Safety-in-Domain-Driven-Design|Type-Safety-in-Domain-Driven-Design]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Type-Safety-in-Domain-Driven-D ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Type-Safety-in-Domain-Driven-Design.md]] +- Raw Source: 00_Raw/2026-04-20/Type-Safety-in-Domain-Driven-Design.md --- diff --git a/01_Archive/2026-04-20/Type-Safety-in-Generics.md b/01_Archive/2026-04-20/Type-Safety-in-Generics.md index a530c1b2..c5335e9b 100644 --- a/01_Archive/2026-04-20/Type-Safety-in-Generics.md +++ b/01_Archive/2026-04-20/Type-Safety-in-Generics.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-D5AEC1 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Type-Safety-in-Generics" --- -# [[Type-Safety-in-Generics]] +# [[Type-Safety-in-Generics|Type-Safety-in-Generics]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Type-Safety-in-Generics" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Type-Safety-in-Generics.md]] +- Raw Source: 00_Raw/2026-04-20/Type-Safety-in-Generics.md --- diff --git a/01_Archive/2026-04-20/Type-Safety.md b/01_Archive/2026-04-20/Type-Safety.md index 74099882..0f14ce7d 100644 --- a/01_Archive/2026-04-20/Type-Safety.md +++ b/01_Archive/2026-04-20/Type-Safety.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-0FE004 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Type-Safety" --- -# [[Type-Safety]] +# [[Type-Safety|Type-Safety]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Type-Safety" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Type-Safety.md]] +- Raw Source: 00_Raw/2026-04-20/Type-Safety.md --- diff --git a/01_Archive/2026-04-20/Type-Soundness.md b/01_Archive/2026-04-20/Type-Soundness.md index 9358beb3..4fbde709 100644 --- a/01_Archive/2026-04-20/Type-Soundness.md +++ b/01_Archive/2026-04-20/Type-Soundness.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-9C23CB -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Type-Soundness" --- -# [[Type-Soundness]] +# [[Type-Soundness|Type-Soundness]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Type-Soundness" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Type-Soundness.md]] +- Raw Source: 00_Raw/2026-04-20/Type-Soundness.md --- diff --git a/01_Archive/2026-04-20/Type-Theory.md b/01_Archive/2026-04-20/Type-Theory.md index bcc8d1db..07780141 100644 --- a/01_Archive/2026-04-20/Type-Theory.md +++ b/01_Archive/2026-04-20/Type-Theory.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-3E115A -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Type-Theory" --- -# [[Type-Theory]] +# [[Type-Theory|Type-Theory]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Type-Theory" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Type-Theory.md]] +- Raw Source: 00_Raw/2026-04-20/Type-Theory.md --- diff --git a/01_Archive/2026-04-20/Type-Unification.md b/01_Archive/2026-04-20/Type-Unification.md index 187972c5..41cd2dd5 100644 --- a/01_Archive/2026-04-20/Type-Unification.md +++ b/01_Archive/2026-04-20/Type-Unification.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-190EA7 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Type-Unification" --- -# [[Type-Unification]] +# [[Type-Unification|Type-Unification]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Type-Unification" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Type-Unification.md]] +- Raw Source: 00_Raw/2026-04-20/Type-Unification.md --- diff --git a/01_Archive/2026-04-20/Type-Variance-in-TypeScript.md b/01_Archive/2026-04-20/Type-Variance-in-TypeScript.md index 9a63f635..bd55ac7d 100644 --- a/01_Archive/2026-04-20/Type-Variance-in-TypeScript.md +++ b/01_Archive/2026-04-20/Type-Variance-in-TypeScript.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-E14411 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Type-Variance-in-TypeScript" --- -# [[Type-Variance-in-TypeScript]] +# [[Type-Variance-in-TypeScript|Type-Variance-in-TypeScript]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Type-Variance-in-TypeScript" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Type-Variance-in-TypeScript.md]] +- Raw Source: 00_Raw/2026-04-20/Type-Variance-in-TypeScript.md --- diff --git a/01_Archive/2026-04-20/Type-safe Error Handling Exhaustiveness Checking.md b/01_Archive/2026-04-20/Type-safe Error Handling Exhaustiveness Checking.md index faf59873..305c9197 100644 --- a/01_Archive/2026-04-20/Type-safe Error Handling Exhaustiveness Checking.md +++ b/01_Archive/2026-04-20/Type-safe Error Handling Exhaustiveness Checking.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-E20F27 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Type-safe Error Handling Exhaustiveness Checking" --- -# [[Type-safe Error Handling Exhaustiveness Checking]] +# [[Type-safe Error Handling Exhaustiveness Checking|Type-safe Error Handling Exhaustiveness Checking]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 타입 안전한 에러 처리(Type-safe Error Handling)와 철저함 검사(Exhaustiveness Checking)는 타입 시스템을 활용하여 예상 가능한 에러와 상태 변화를 컴파일 타임에 제어하는 기법입니다. 예외(Exception)를 무분별하게 던지는 대신 반환 타입(예: Result 타입이나 식별 가능한 유니온)에 에러를 명시하여, 함수의 시그니처만으로도 발생 가능한 실패를 미리 파악하고 대응하게 만듭니다 [1, 2]. 이에 더해 철저함 검사는 제어문(switch 등)에서 에러나 유니온 타입의 모든 가능한 케이스가 누락 없이 처리되었는지를 컴파일러가 강제로 확인하게 하여 런타임 에러를 방지합니다 [3, 4]. @@ -23,11 +23,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Type-safe Error Handling Exha - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Discriminated Unions]], [[The never Type]], [[Result Type]] -- **Projects/Contexts:** [[neverthrow 라이브러리]], [[ts-pattern 라이브러리]] +- **Related Topics:** [[Discriminated Unions|Discriminated Unions]], The never Type, [[Result Type|Result Type]] +- **Projects/Contexts:** neverthrow 라이브러리, ts-pattern 라이브러리 - **Contradictions/Notes:** 분기 처리 시 `ts-pattern` 라이브러리의 `.exhaustive()`를 사용하여 철저함 검사를 손쉽게 수행할 수 있으나, 네이티브 `if/else`나 `switch` 문에 `satisfies never`를 결합하는 방식에 비해 패턴 매칭 연산 성능이 99% 이상 떨어질 수 있어 오버엔지니어링을 경계해야 한다는 지적이 있습니다 [20-22]. 또한, 일부 언어(예: C#) 생태계에서는 예외 처리가 언어 표준 프레임워크 설계에 더 부합한다는 이유로 Result 타입을 과도한 보일러플레이트로 간주하는 비판적 의견도 존재합니다 [23, 24]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/Type-safe Error Handling & Exhaustiveness Checking.md]] +- Raw Source: 00_Raw/2026-04-20/Type-safe Error Handling & Exhaustiveness Checking.md --- diff --git a/01_Archive/2026-04-20/Type-safe Error Handling & Exhaustiveness Checking.md b/01_Archive/2026-04-20/Type-safe Error Handling & Exhaustiveness Checking.md index ffa144a6..08b57130 100644 --- a/01_Archive/2026-04-20/Type-safe Error Handling & Exhaustiveness Checking.md +++ b/01_Archive/2026-04-20/Type-safe Error Handling & Exhaustiveness Checking.md @@ -1,4 +1,4 @@ -# [[Type-safe Error Handling & Exhaustiveness Checking]] +# [[Type-safe Error Handling & Exhaustiveness Checking|Type-safe Error Handling & Exhaustiveness Checking]] ## 📌 Brief Summary 타입 안전한 에러 처리(Type-safe Error Handling)와 철저함 검사(Exhaustiveness Checking)는 타입 시스템을 활용하여 예상 가능한 에러와 상태 변화를 컴파일 타임에 제어하는 기법입니다. 예외(Exception)를 무분별하게 던지는 대신 반환 타입(예: Result 타입이나 식별 가능한 유니온)에 에러를 명시하여, 함수의 시그니처만으로도 발생 가능한 실패를 미리 파악하고 대응하게 만듭니다 [1, 2]. 이에 더해 철저함 검사는 제어문(switch 등)에서 에러나 유니온 타입의 모든 가능한 케이스가 누락 없이 처리되었는지를 컴파일러가 강제로 확인하게 하여 런타임 에러를 방지합니다 [3, 4]. @@ -10,8 +10,8 @@ - **`never` 타입을 활용한 검사 구현:** 가장 흔한 네이티브 철저함 검사 방식은 모든 케이스를 처리한 후 남는 `default` 블록에서 값을 `never` 타입에 할당하거나 전용 검사 함수(`assertNever`)로 전달하는 것입니다 [18, 19]. 분기에서 누락된 케이스가 있다면 해당 값은 실제 타입을 가지므로 `never` 타입에 할당될 수 없어 컴파일 타입 에러(예: `Type 'Pentagon' is not assignable to type 'never'`)를 냅니다 [4, 19, 20]. ## 🔗 Knowledge Connections -- **Related Topics:** [[Discriminated Unions]], [[The never Type]], [[Result Type]] -- **Projects/Contexts:** [[neverthrow 라이브러리]], [[ts-pattern 라이브러리]] +- **Related Topics:** [[Discriminated Unions|Discriminated Unions]], The never Type, [[Result Type|Result Type]] +- **Projects/Contexts:** neverthrow 라이브러리, ts-pattern 라이브러리 - **Contradictions/Notes:** 분기 처리 시 `ts-pattern` 라이브러리의 `.exhaustive()`를 사용하여 철저함 검사를 손쉽게 수행할 수 있으나, 네이티브 `if/else`나 `switch` 문에 `satisfies never`를 결합하는 방식에 비해 패턴 매칭 연산 성능이 99% 이상 떨어질 수 있어 오버엔지니어링을 경계해야 한다는 지적이 있습니다 [20-22]. 또한, 일부 언어(예: C#) 생태계에서는 예외 처리가 언어 표준 프레임워크 설계에 더 부합한다는 이유로 Result 타입을 과도한 보일러플레이트로 간주하는 비판적 의견도 존재합니다 [23, 24]. --- diff --git a/01_Archive/2026-04-20/TypeScript 4.9.md b/01_Archive/2026-04-20/TypeScript 4.9.md index f333dc75..c2961c51 100644 --- a/01_Archive/2026-04-20/TypeScript 4.9.md +++ b/01_Archive/2026-04-20/TypeScript 4.9.md @@ -1,4 +1,4 @@ -# [[TypeScript 4.9]] +# [[TypeScript 4.9|TypeScript 4.9]] ## 📌 Brief Summary TypeScript 4.9는 객체의 구조 검증과 구체적인 타입(literal types) 유지 사이의 딜레마를 해결하기 위해 `satisfies` 연산자를 새롭게 도입한 주요 릴리스입니다 [1, 2]. 이 버전을 통해 개발자는 타입 추론의 정확성을 잃지 않으면서도 엄격한 타입 안정성을 강제할 수 있게 되었습니다 [1, 3]. @@ -10,8 +10,8 @@ TypeScript 4.9는 객체의 구조 검증과 구체적인 타입(literal types) - **고급 패턴과의 결합**: 이 연산자는 식별 가능한 유니온(Discriminated Unions)에서 판별자의 리터럴 타입을 보존해 타입 좁히기(Type narrowing)를 가능하게 합니다 [7]. 또한 `as const`와 결합하여 검증과 불변성(Immutability)을 동시에 만족시키는 객체를 생성할 수 있도록 지원합니다 [8]. ## 🔗 Knowledge Connections -- **Related Topics:** [[satisfies Operator]], [[Excess Property Checking]], [[Structural Typing]], [[Type Narrowing]] -- **Projects/Contexts:** [[Type Safety Verification]], [[Object Structure Validation]] +- **Related Topics:** [[Satisfies Operator|satisfies Operator]], [[Excess Property Checking|Excess Property Checking]], [[Structural Typing|Structural Typing]], [[Type Narrowing|Type Narrowing]] +- **Projects/Contexts:** Type Safety Verification, Object Structure Validation - **Contradictions/Notes:** 주어진 소스 내에서 TypeScript 4.9와 관련된 설명은 전적으로 `satisfies` 연산자의 도입과 그로 인한 타입 검증 시스템의 변화에 집중되어 있으며, 그 외 TypeScript 4.9의 다른 기능 업데이트에 대해서는 소스에 관련 정보가 부족합니다. --- diff --git a/01_Archive/2026-04-20/TypeScript 49.md b/01_Archive/2026-04-20/TypeScript 49.md index afba6201..053764dc 100644 --- a/01_Archive/2026-04-20/TypeScript 49.md +++ b/01_Archive/2026-04-20/TypeScript 49.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-33CE04 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - TypeScript 49" --- -# [[TypeScript 49]] +# [[TypeScript 49|TypeScript 49]] ## 📌 한 줄 통찰 (The Karpathy Summary) > TypeScript 4.9는 객체의 구조 검증과 구체적인 타입(literal types) 유지 사이의 딜레마를 해결하기 위해 `satisfies` 연산자를 새롭게 도입한 주요 릴리스입니다 [1, 2]. 이 버전을 통해 개발자는 타입 추론의 정확성을 잃지 않으면서도 엄격한 타입 안정성을 강제할 수 있게 되었습니다 [1, 3]. @@ -23,11 +23,11 @@ github_commit: "[P-Reinforce] Continuous Worker - TypeScript 49" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[satisfies Operator]], [[Excess Property Checking]], [[Structural Typing]], [[Type Narrowing]] -- **Projects/Contexts:** [[Type Safety Verification]], [[Object Structure Validation]] +- **Related Topics:** [[Satisfies Operator|satisfies Operator]], [[Excess Property Checking|Excess Property Checking]], [[Structural Typing|Structural Typing]], [[Type Narrowing|Type Narrowing]] +- **Projects/Contexts:** Type Safety Verification, Object Structure Validation - **Contradictions/Notes:** 주어진 소스 내에서 TypeScript 4.9와 관련된 설명은 전적으로 `satisfies` 연산자의 도입과 그로 인한 타입 검증 시스템의 변화에 집중되어 있으며, 그 외 TypeScript 4.9의 다른 기능 업데이트에 대해서는 소스에 관련 정보가 부족합니다. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/TypeScript 4.9.md]] +- Raw Source: 00_Raw/2026-04-20/TypeScript 4.9.md --- diff --git a/01_Archive/2026-04-20/TypeScript API Development.md b/01_Archive/2026-04-20/TypeScript API Development.md index 32a8c179..1bf4e47d 100644 --- a/01_Archive/2026-04-20/TypeScript API Development.md +++ b/01_Archive/2026-04-20/TypeScript API Development.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-7B86BE -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - TypeScript API Development" --- -# [[TypeScript API Development]] +# [[TypeScript API Development|TypeScript API Development]] ## 📌 한 줄 통찰 (The Karpathy Summary) > TypeScript API 개발은 강력한 타입 시스템을 활용하여 시스템 경계에서 데이터를 안전하게 검증하고, 예측 가능한 에러 모델을 구축하며, 클라이언트와 서버 간의 견고한 인터페이스를 설계하는 과정입니다 [1-3]. 이를 통해 런타임 에러를 방지하고 안정적인 데이터 통신 계약(Contract)을 확립할 수 있습니다 [1, 4]. @@ -33,11 +33,11 @@ github_commit: "[P-Reinforce] Continuous Worker - TypeScript API Development" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Parse, don't validate]], [[Discriminated Unions]], [[Branded Types]], [[Facade Pattern]] -- **Projects/Contexts:** [[Toss Front SDK]], [[Zod Validation]] +- **Related Topics:** [[Parse, don't validate|Parse, don't validate]], [[Discriminated Unions|Discriminated Unions]], [[Branded Types|Branded Types]], [[Facade Pattern (퍼사드 패턴)|Facade Pattern]] +- **Projects/Contexts:** [[Toss Front SDK 기반 외부 연동사 플러그인 개발 생태계 구축|Toss Front SDK]], Zod Validation - **Contradictions/Notes:** API의 에러 처리에 관하여, 모든 에러를 글로벌 예외 처리기(Global Exception Handler)로 넘기고 컨트롤러 로직을 짧게 가져가는 것이 더 깔끔하다는 전통적인 객체 지향 및 웹 프레임워크의 관점과, 예측 가능한 에러는 예외(Exception)가 아닌 명시적인 유니온 타입이나 Result 객체로 반환해야 제어 흐름이 투명해진다는 함수형 타입 시스템 관점이 서로 팽팽하게 대립하기도 합니다 [8, 19-21]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/TypeScript API Development.md]] +- Raw Source: 00_Raw/2026-04-20/TypeScript API Development.md --- diff --git a/01_Archive/2026-04-20/TypeScript Advanced Type System.md b/01_Archive/2026-04-20/TypeScript Advanced Type System.md index 614e9409..c6931def 100644 --- a/01_Archive/2026-04-20/TypeScript Advanced Type System.md +++ b/01_Archive/2026-04-20/TypeScript Advanced Type System.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-A211EA -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - TypeScript Advanced Type System" --- -# [[TypeScript Advanced Type System]] +# [[TypeScript Advanced Type System|TypeScript Advanced Type System]] ## 📌 한 줄 통찰 (The Karpathy Summary) > TypeScript의 고급 타입 시스템은 구조적 타이핑(Structural Typing)을 기반으로 하면서도, 개발자가 코드의 예측 가능성과 안정성을 극대화할 수 있도록 돕는 강력한 도구 모음입니다 [1-3]. 이 시스템은 집합론에 기반하여 타입을 값들의 집합으로 다루며, 컴파일 시점에 런타임 에러를 방지합니다 [3-5]. 식별 가능한 유니온, 브랜디드 타입, `readonly` 수식어, 그리고 `satisfies` 연산자 등의 고급 기능을 통해 복잡한 비즈니스 로직을 안전하게 모델링할 수 있습니다 [6-10]. @@ -25,11 +25,11 @@ github_commit: "[P-Reinforce] Continuous Worker - TypeScript Advanced Type Syste - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Structural Typing]], [[Discriminated Unions]], [[Branded Types]], [[Readonly Modifier]], [[Satisfies Operator]] -- **Projects/Contexts:** [[Large-scale Application Architecture]], [[Domain-Driven Design (DDD)]] +- **Related Topics:** [[Structural Typing|Structural Typing]], [[Discriminated Unions|Discriminated Unions]], [[Branded Types|Branded Types]], Readonly Modifier, [[Satisfies Operator|Satisfies Operator]] +- **Projects/Contexts:** Large-scale Application Architecture, [[Domain-Driven Design (DDD)|Domain-Driven Design (DDD)]] - **Contradictions/Notes:** 인터페이스(Interface)와 타입 별칭(Type Alias)의 사용 기준에 대해 개발자 간 선호도 차이가 있습니다. 일부는 일관성을 위해 Type만을 선호하기도 하지만 [44], TypeScript 공식 성능 가이드와 주요 문헌에서는 타입 관계 캐싱 및 선언 병합(Declaration Merging)의 장점 때문에 객체 구조를 확장할 때는 인터페이스(`extends`)를 우선적으로 사용할 것을 권장합니다 [45-49]. 또한, 복잡한 타입 분기 처리를 돕는 외부 라이브러리(ts-pattern 등)의 도입을 두고 단순한 제어문(`if`, `switch`) 대비 성능 오버헤드와 가독성 측면에서 의견 대립이 존재합니다 [50-52]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/TypeScript Advanced Type System.md]] +- Raw Source: 00_Raw/2026-04-20/TypeScript Advanced Type System.md --- diff --git a/01_Archive/2026-04-20/TypeScript Compiler (tsc).md b/01_Archive/2026-04-20/TypeScript Compiler (tsc).md index 861f2e6d..12f4984b 100644 --- a/01_Archive/2026-04-20/TypeScript Compiler (tsc).md +++ b/01_Archive/2026-04-20/TypeScript Compiler (tsc).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-E23D67 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - TypeScript Compiler (tsc)" --- -# [[TypeScript Compiler (tsc)]] +# [[TypeScript Compiler (tsc)|TypeScript Compiler (tsc)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - TypeScript Compiler (tsc)" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/TypeScript Compiler (tsc).md]] +- Raw Source: 00_Raw/2026-04-20/TypeScript Compiler (tsc).md --- diff --git a/01_Archive/2026-04-20/TypeScript Compiler API.md b/01_Archive/2026-04-20/TypeScript Compiler API.md index a195183b..fc2f79b1 100644 --- a/01_Archive/2026-04-20/TypeScript Compiler API.md +++ b/01_Archive/2026-04-20/TypeScript Compiler API.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-A553B6 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - TypeScript Compiler API" --- -# [[TypeScript Compiler API]] +# [[TypeScript Compiler API|TypeScript Compiler API]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - TypeScript Compiler API" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/TypeScript Compiler API.md]] +- Raw Source: 00_Raw/2026-04-20/TypeScript Compiler API.md --- diff --git a/01_Archive/2026-04-20/TypeScript Declaration Files (.d.ts) Design.md b/01_Archive/2026-04-20/TypeScript Declaration Files (.d.ts) Design.md index df466cd6..400c6b15 100644 --- a/01_Archive/2026-04-20/TypeScript Declaration Files (.d.ts) Design.md +++ b/01_Archive/2026-04-20/TypeScript Declaration Files (.d.ts) Design.md @@ -1,4 +1,4 @@ -[[TypeScript Declaration Files (.d.ts) Design]] +[[TypeScript Declaration Files (.d.ts) Design|TypeScript Declaration Files (.d.ts) Design]] 📌 Brief Summary TypeScript declaration files (`.d.ts`) serve as the structural blueprint for type information in a JavaScript ecosystem, providing ambient declarations that describe the shape of existing code without containing implementation logic. Designing these files requires a sophisticated approach to "Ambient Type Definition," focusing on maintaining type safety across module boundaries while managing the complexity of declaration merging and global scope pollution. @@ -13,8 +13,8 @@ The design of `.d.ts` files is centered around the concept of **Ambient Declarat * **Handling Side Effects and Ambient Imports**: Professional `.d.ts` design must account for files that contain top-level `import` or `export` statements. Once a file contains an `import`, it becomes a module, and all declarations within it are no longer global unless explicitly wrapped in `declare global`. This distinction is critical when designing type definitions for polyfills or environment-specific globals (like `window` or `process`). 🔗 Knowledge Connections -* Related Topics: [[Declaration Merging]], [[Module Augmentation]], [[Ambient Contexts]] -* Projects/Contexts: [[DefinitelyTyped]], [[TypeScript Compiler API]] +* Related Topics: [[Declaration Merging|Declaration Merging]], [[Module Augmentation|Module Augmentation]], [[Ambient Contexts|Ambient Contexts]] +* Projects/Contexts: [[DefinitelyTyped|DefinitelyTyped]], [[TypeScript Compiler API|TypeScript Compiler API]] * Contradictions/Notes: While declaration merging provides flexibility, it can lead to "hidden" type changes that make debugging difficult; therefore, architectural preference is given to explicit interface extensions over implicit global overrides. Last updated: 2026-04-17 \ No newline at end of file diff --git a/01_Archive/2026-04-20/TypeScript Declaration Files (dts) Design.md b/01_Archive/2026-04-20/TypeScript Declaration Files (dts) Design.md index 6ea7e836..272159ed 100644 --- a/01_Archive/2026-04-20/TypeScript Declaration Files (dts) Design.md +++ b/01_Archive/2026-04-20/TypeScript Declaration Files (dts) Design.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-EE6A06 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - TypeScript Declaration Files (dts) Design" --- -# [[TypeScript Declaration Files (dts) Design]] +# [[TypeScript Declaration Files (dts) Design|TypeScript Declaration Files (dts) Design]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - TypeScript Declaration Files ( ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/TypeScript Declaration Files (.d.ts) Design.md]] +- Raw Source: 00_Raw/2026-04-20/TypeScript Declaration Files (.d.ts) Design.md --- diff --git a/01_Archive/2026-04-20/TypeScript Interface Design.md b/01_Archive/2026-04-20/TypeScript Interface Design.md index fd9506be..39e6942c 100644 --- a/01_Archive/2026-04-20/TypeScript Interface Design.md +++ b/01_Archive/2026-04-20/TypeScript Interface Design.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-2B3B7E -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - TypeScript Interface Design" --- -# [[TypeScript Interface Design]] +# [[TypeScript Interface Design|TypeScript Interface Design]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - TypeScript Interface Design" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/TypeScript Interface Design.md]] +- Raw Source: 00_Raw/2026-04-20/TypeScript Interface Design.md --- diff --git a/01_Archive/2026-04-20/TypeScript Type System (Interface Design).md b/01_Archive/2026-04-20/TypeScript Type System (Interface Design).md index c65ad3de..373f6d96 100644 --- a/01_Archive/2026-04-20/TypeScript Type System (Interface Design).md +++ b/01_Archive/2026-04-20/TypeScript Type System (Interface Design).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-FE2C59 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - TypeScript Type System (Interface Design)" --- -# [[TypeScript Type System (Interface Design)]] +# [[TypeScript Type System (Interface Design)|TypeScript Type System (Interface Design)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - TypeScript Type System (Interf ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/TypeScript Type System (Interface Design).md]] +- Raw Source: 00_Raw/2026-04-20/TypeScript Type System (Interface Design).md --- diff --git a/01_Archive/2026-04-20/TypeScript Type System Design.md b/01_Archive/2026-04-20/TypeScript Type System Design.md index 7761a326..a28fcbf8 100644 --- a/01_Archive/2026-04-20/TypeScript Type System Design.md +++ b/01_Archive/2026-04-20/TypeScript Type System Design.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-616782 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - TypeScript Type System Design" --- -# [[TypeScript Type System Design]] +# [[TypeScript Type System Design|TypeScript Type System Design]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - TypeScript Type System Design" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/TypeScript Type System Design.md]] +- Raw Source: 00_Raw/2026-04-20/TypeScript Type System Design.md --- diff --git a/01_Archive/2026-04-20/TypeScript Utility Types (Record Readonly).md b/01_Archive/2026-04-20/TypeScript Utility Types (Record Readonly).md index cad24eaa..e0b28a11 100644 --- a/01_Archive/2026-04-20/TypeScript Utility Types (Record Readonly).md +++ b/01_Archive/2026-04-20/TypeScript Utility Types (Record Readonly).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-523973 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - TypeScript Utility Types (Record Readonly)" --- -# [[TypeScript Utility Types (Record Readonly)]] +# [[TypeScript Utility Types (Record Readonly)|TypeScript Utility Types (Record Readonly)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > TypeScript의 유틸리티 타입인 `Readonly`와 `Record`는 타입 안전성을 높이고 데이터 구조를 효과적으로 모델링하는 데 사용됩니다. `Readonly`는 주어진 객체 타입의 모든 속성을 읽기 전용으로 변환하여 컴파일 타임에 의도치 않은 상태 변경(돌연변이)을 방지합니다 [1, 2]. `Record`는 키와 값의 타입을 지정하여 객체(사전) 구조를 안전하게 정의하는 데 쓰이며, 이 둘을 결합하면 불변의 키-값 맵을 구축할 수 있습니다 [3, 4]. @@ -30,11 +30,11 @@ github_commit: "[P-Reinforce] Continuous Worker - TypeScript Utility Types (Reco - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[DeepReadonly]], [[TypeScript Structural Typing]], [[Utility Types]] +- **Related Topics:** [[DeepReadonly|DeepReadonly]], TypeScript Structural Typing, Utility Types - **Projects/Contexts:** `Readonly`는 앱의 설정(Configuration) 객체를 고정하거나 [13, 14], 상태 관리(Reducer) 시 불변성을 강제하고 [14], API로부터 받아온 응답 데이터가 로직 내에서 우발적으로 변조되는 것을 막는 컨텍스트에 널리 활용됩니다 [14]. - **Contradictions/Notes:** TypeScript의 `Readonly`는 런타임에 데이터를 얕게 동결시키는 자바스크립트의 `Object.freeze()`나 변수 자체의 재할당을 막는 `const`와 구별됩니다. `Readonly`는 런타임 비용이 전혀 없으며 컴파일 타임에만 엄격하게 속성 재할당을 검사합니다 [1, 15, 16]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/TypeScript Utility Types (Record, Readonly).md]] +- Raw Source: 00_Raw/2026-04-20/TypeScript Utility Types (Record, Readonly).md --- diff --git a/01_Archive/2026-04-20/TypeScript Utility Types (Record, Readonly).md b/01_Archive/2026-04-20/TypeScript Utility Types (Record, Readonly).md index 5b8c9220..5a5d447b 100644 --- a/01_Archive/2026-04-20/TypeScript Utility Types (Record, Readonly).md +++ b/01_Archive/2026-04-20/TypeScript Utility Types (Record, Readonly).md @@ -1,4 +1,4 @@ -# [[TypeScript Utility Types (Record, Readonly)]] +# [[TypeScript Utility Types (Record, Readonly)|TypeScript Utility Types (Record, Readonly)]] ## 📌 Brief Summary TypeScript의 유틸리티 타입인 `Readonly`와 `Record`는 타입 안전성을 높이고 데이터 구조를 효과적으로 모델링하는 데 사용됩니다. `Readonly`는 주어진 객체 타입의 모든 속성을 읽기 전용으로 변환하여 컴파일 타임에 의도치 않은 상태 변경(돌연변이)을 방지합니다 [1, 2]. `Record`는 키와 값의 타입을 지정하여 객체(사전) 구조를 안전하게 정의하는 데 쓰이며, 이 둘을 결합하면 불변의 키-값 맵을 구축할 수 있습니다 [3, 4]. @@ -17,7 +17,7 @@ TypeScript의 유틸리티 타입인 `Readonly`와 `Record`는 타입 안전성 - 두 유틸리티 타입을 결합(`Readonly>`)하면 속성이 절대 변하지 않는 불변의 키-값 맵(Immutable key-value map)을 구성할 수 있습니다 [3]. 이는 애플리케이션 전반에서 변하지 않아야 하는 정적인 사전(Static dictionaries)을 선언할 때 권장되는 패턴입니다 [3]. ## 🔗 Knowledge Connections -- **Related Topics:** [[DeepReadonly]], [[TypeScript Structural Typing]], [[Utility Types]] +- **Related Topics:** [[DeepReadonly|DeepReadonly]], TypeScript Structural Typing, Utility Types - **Projects/Contexts:** `Readonly`는 앱의 설정(Configuration) 객체를 고정하거나 [13, 14], 상태 관리(Reducer) 시 불변성을 강제하고 [14], API로부터 받아온 응답 데이터가 로직 내에서 우발적으로 변조되는 것을 막는 컨텍스트에 널리 활용됩니다 [14]. - **Contradictions/Notes:** TypeScript의 `Readonly`는 런타임에 데이터를 얕게 동결시키는 자바스크립트의 `Object.freeze()`나 변수 자체의 재할당을 막는 `const`와 구별됩니다. `Readonly`는 런타임 비용이 전혀 없으며 컴파일 타임에만 엄격하게 속성 재할당을 검사합니다 [1, 15, 16]. diff --git a/01_Archive/2026-04-20/TypeScript 라이브러리 타입 확장.md b/01_Archive/2026-04-20/TypeScript 라이브러리 타입 확장.md index a2f4d89c..b1b4d657 100644 --- a/01_Archive/2026-04-20/TypeScript 라이브러리 타입 확장.md +++ b/01_Archive/2026-04-20/TypeScript 라이브러리 타입 확장.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-BF50D4 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - TypeScript 라이브러리 타입 확장" --- -# [[TypeScript 라이브러리 타입 확장]] +# [[TypeScript 라이브러리 타입 확장|TypeScript 라이브러리 타입 확장]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -23,11 +23,11 @@ github_commit: "[P-Reinforce] Continuous Worker - TypeScript 라이브러리 타 - **정책 변화:** Design & Experience 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[선언 병합(Declaration Merging)]], [[Interface]], [[Type Alias]], [[교집합 타입(Intersection Type)]] -- **Projects/Contexts:** [[외부 라이브러리 API 설계]], [[TypeScript 컴파일러 캐싱 최적화]], [[선언 파일(.d.ts)]] +- **Related Topics:** [[선언 병합(Declaration Merging)|선언 병합(Declaration Merging)]], [[인터페이스 (Interface)|Interface]], [[Type Alias|Type Alias]], [[교집합 타입(Intersection Type)|교집합 타입(Intersection Type)]] +- **Projects/Contexts:** [[외부 라이브러리 API 설계|외부 라이브러리 API 설계]], [[TypeScript 컴파일러 캐싱 최적화|TypeScript 컴파일러 캐싱 최적화]], [[선언 파일(.d.ts)|선언 파일(.d.ts)]] - **Contradictions/Notes:** 애플리케이션 내부 코드의 경우, 인터페이스의 확장성을 '의도치 않은 속성 병합(Bad Thing)'으로 간주하여 타입 별칭(Type Alias)의 사용을 선호하는 실무적 의견이 다수 존재합니다 [4, 10-12]. 하지만 외부 패키지나 라이브러리 생태계에서는 여전히 사용자에게 타입 확장을 허용하기 위해 인터페이스를 채택하는 것이 정석으로 평가받고 있습니다 [2, 3]. 또한, 객체를 확장할 때 교집합(`&`) 방식은 유연해 보이지만, 성능 이슈와 충돌 검사 한계로 인해 `interface extends` 방식에 비해 상대적으로 지양됩니다 [5, 7, 13]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/TypeScript 라이브러리 타입 확장.md]] +- Raw Source: 00_Raw/2026-04-20/TypeScript 라이브러리 타입 확장.md --- diff --git a/01_Archive/2026-04-20/TypeScript 인터페이스 및 시스템 보호 아키텍처 설계.md b/01_Archive/2026-04-20/TypeScript 인터페이스 및 시스템 보호 아키텍처 설계.md index b202c2f8..80b17957 100644 --- a/01_Archive/2026-04-20/TypeScript 인터페이스 및 시스템 보호 아키텍처 설계.md +++ b/01_Archive/2026-04-20/TypeScript 인터페이스 및 시스템 보호 아키텍처 설계.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-6ECC4D -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - TypeScript 인터페이스 및 시스템 보호 아키텍처 설계" --- -# [[TypeScript 인터페이스 및 시스템 보호 아키텍처 설계]] +# [[TypeScript 인터페이스 및 시스템 보호 아키텍처 설계|TypeScript 인터페이스 및 시스템 보호 아키텍처 설계]] ## 📌 한 줄 통찰 (The Karpathy Summary) > TypeScript의 타입 시스템은 구조적 타이핑을 기반으로 하여 복잡한 비즈니스 로직을 보호하고 개발자의 의도를 명확히 규정하는 아키텍처적 도구이다 [1]. 인터페이스(Interface)와 타입 별칭(Type Alias)을 전략적으로 선택하여 컴파일 성능과 확장성을 최적화하며, `readonly` 수식어와 `satisfies` 연산자 등을 통해 예기치 않은 데이터 오염과 상태 변경을 원천적으로 차단한다 [2-4]. 이러한 견고한 인터페이스 설계는 시스템의 결합도를 낮추고 예측 가능성을 극대화하여 대규모 애플리케이션에서 철벽과 같은 수비 체계를 구축한다 [5, 6]. @@ -30,11 +30,11 @@ github_commit: "[P-Reinforce] Continuous Worker - TypeScript 인터페이스 및 - **정책 변화:** Design & Experience 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[구조적 타이핑 (Structural Typing)]], [[과잉 속성 체크 (Excess Property Checking)]], [[재귀적 불변성 (DeepReadonly)]], [[식별 가능한 유니온 (Discriminated Unions)]], [[브랜디드 타입 (Branded Types)]], [[SOLID 원칙]] -- **Projects/Contexts:** [[Toss Front SDK의 Facade 패턴 적용 사례]] +- **Related Topics:** [[구조적 타이핑 (Structural Typing)|구조적 타이핑 (Structural Typing)]], [[과잉 속성 체크 (Excess Property Checking)|과잉 속성 체크 (Excess Property Checking)]], [[재귀적 불변성 (DeepReadonly)|재귀적 불변성 (DeepReadonly)]], [[식별 가능한 유니온 (Discriminated Unions)|식별 가능한 유니온 (Discriminated Unions)]], [[브랜디드 타입 (Branded Types)|브랜디드 타입 (Branded Types)]], [[SOLID 원칙|SOLID 원칙]] +- **Projects/Contexts:** [[Toss Front SDK의 Facade 패턴 적용 사례|Toss Front SDK의 Facade 패턴 적용 사례]] - **Contradictions/Notes:** TypeScript의 구조적 타이핑은 최소 요건만 충족하면 호환성을 허용하므로 매우 유연하지만, 이메일 주소와 이름이 같은 `string`으로 취급되는 등 "기본 타입에의 집착(Primitive Obsession)" 문제를 야기한다 [11]. 이를 방어하기 위해 컴파일 시점에만 존재하는 고유 속성을 부여하는 브랜디드 타입(Branded Types)을 사용하여 데이터의 무분별한 혼용을 차단해야 한다 [10, 11]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/TypeScript 인터페이스 및 시스템 보호 아키텍처 설계.md]] +- Raw Source: 00_Raw/2026-04-20/TypeScript 인터페이스 및 시스템 보호 아키텍처 설계.md --- diff --git a/01_Archive/2026-04-20/TypeScript 컴파일러 캐싱 최적화.md b/01_Archive/2026-04-20/TypeScript 컴파일러 캐싱 최적화.md index 42e355ef..2800b457 100644 --- a/01_Archive/2026-04-20/TypeScript 컴파일러 캐싱 최적화.md +++ b/01_Archive/2026-04-20/TypeScript 컴파일러 캐싱 최적화.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-3D0990 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - TypeScript 컴파일러 캐싱 최적화" --- -# [[TypeScript 컴파일러 캐싱 최적화]] +# [[TypeScript 컴파일러 캐싱 최적화|TypeScript 컴파일러 캐싱 최적화]] ## 📌 한 줄 통찰 (The Karpathy Summary) > TypeScript 컴파일러는 타입 검사 속도와 IDE 응답성을 향상시키기 위해 타입 관계를 캐싱하는 최적화 메커니즘을 사용합니다. 이 캐싱 메커니즘은 객체를 확장할 때 주로 `interface extends`를 사용할 경우 해당 이름을 기준으로 효과적으로 작동하며, 타입 검사 성능을 향상시키는 핵심적인 역할을 합니다 [1-3]. @@ -22,11 +22,11 @@ github_commit: "[P-Reinforce] Continuous Worker - TypeScript 컴파일러 캐싱 - **정책 변화:** Design & Experience 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[인터페이스 확장(Interface Extends)]], [[교집합 타입(Intersection Types)]] -- **Projects/Contexts:** [[TypeScript Performance Guide]] +- **Related Topics:** 인터페이스 확장(Interface Extends), [[교집합 타입 (Intersection Types)|교집합 타입(Intersection Types)]] +- **Projects/Contexts:** TypeScript Performance Guide - **Contradictions/Notes:** 인터페이스 간의 타입 관계는 이름 기반으로 캐싱되어 성능상 이점을 제공하지만, 교집합 타입은 전체가 캐싱되지 않고 사용할 때마다 평탄화 및 재계산을 거쳐야 한다는 구조적 차이가 존재합니다 [3]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/TypeScript 컴파일러 캐싱 최적화.md]] +- Raw Source: 00_Raw/2026-04-20/TypeScript 컴파일러 캐싱 최적화.md --- diff --git a/01_Archive/2026-04-20/TypeScript 타입 시스템 (TypeScript Type System).md b/01_Archive/2026-04-20/TypeScript 타입 시스템 (TypeScript Type System).md index f2812567..0c93a5b2 100644 --- a/01_Archive/2026-04-20/TypeScript 타입 시스템 (TypeScript Type System).md +++ b/01_Archive/2026-04-20/TypeScript 타입 시스템 (TypeScript Type System).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-5C8A49 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - TypeScript 타입 시스템 (TypeScript Type System)" --- -# [[TypeScript 타입 시스템 (TypeScript Type System)]] +# [[TypeScript 타입 시스템 (TypeScript Type System)|TypeScript 타입 시스템 (TypeScript Type System)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > TypeScript의 타입 시스템은 구조적 타이핑(Structural Typing)을 기반으로 하여, 객체의 실제 형태가 일치하면 호환성을 인정하는 유연성을 제공한다[1, 2]. 동시에 과잉 속성 체크(Excess Property Checking)나 `satisfies` 연산자와 같은 방어 기제를 통해 런타임 에러와 의도치 않은 데이터 유입을 컴파일 시점에 차단한다[3-6]. 이는 집합론(Set Theory)적 관점에서 타입을 정의하고 평가하며, 궁극적으로 복잡한 비즈니스 로직을 보호하고 견고한 인터페이스 설계를 가능하게 하는 아키텍처적 도구로 기능한다[2, 7-9]. @@ -24,11 +24,11 @@ github_commit: "[P-Reinforce] Continuous Worker - TypeScript 타입 시스템 (T - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[구조적 타이핑 (Structural Typing)]], [[식별 가능한 유니온 (Discriminated Unions)]], [[브랜디드 타입 (Branded Types)]], [[과잉 속성 체크 (Excess Property Checking)]], [[satisfies 연산자]], [[불변성 (Immutability)]] -- **Projects/Contexts:** [[대규모 애플리케이션 개발]], [[SOLID 원칙 기반 인터페이스 설계]], [[Toss Front SDK 설계]] +- **Related Topics:** [[구조적 타이핑 (Structural Typing)|구조적 타이핑 (Structural Typing)]], [[식별 가능한 유니온 (Discriminated Unions)|식별 가능한 유니온 (Discriminated Unions)]], [[브랜디드 타입 (Branded Types)|브랜디드 타입 (Branded Types)]], [[과잉 속성 체크 (Excess Property Checking)|과잉 속성 체크 (Excess Property Checking)]], [[satisfies 연산자|satisfies 연산자]], [[불변성 (Immutability)|불변성 (Immutability)]] +- **Projects/Contexts:** [[대규모 애플리케이션 개발|대규모 애플리케이션 개발]], SOLID 원칙 기반 인터페이스 설계, Toss Front SDK 설계 - **Contradictions/Notes:** 인터페이스(`interface`)와 타입 별칭(`type`)의 선택과 관련하여, 선언 병합으로 인한 예기치 않은 구조 오버라이딩을 피하기 위해 오직 `type`만을 엄격하게 사용하는 팀 문화가 존재하는 반면[30, 31], 컴파일러 캐싱 최적화 관점에서는 객체 상속 시 `interface`를 우선할 것을 강력히 권고하는 이견이 존재한다[25, 26, 28]. 또한 `ts-pattern` 라이브러리는 철저한 타입 추론과 가독성을 주지만 네이티브 `if/switch` 구문에 비해 성능이 현저히 떨어지므로(초당 연산 횟수 기준 99% 저하 등), 간단한 분기문에 남용할 경우 불필요한 런타임 오버헤드를 유발할 수 있다는 비판적 견해가 있다[32-34]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/TypeScript 타입 시스템 (TypeScript Type System).md]] +- Raw Source: 00_Raw/2026-04-20/TypeScript 타입 시스템 (TypeScript Type System).md --- diff --git a/01_Archive/2026-04-20/TypeScript 타입 시스템 (인터페이스 설계).md b/01_Archive/2026-04-20/TypeScript 타입 시스템 (인터페이스 설계).md index 453a19b5..fc214ddf 100644 --- a/01_Archive/2026-04-20/TypeScript 타입 시스템 (인터페이스 설계).md +++ b/01_Archive/2026-04-20/TypeScript 타입 시스템 (인터페이스 설계).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-411D87 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - TypeScript 타입 시스템 (인터페이스 설계)" --- -# [[TypeScript 타입 시스템 (인터페이스 설계)]] +# [[TypeScript 타입 시스템 (인터페이스 설계)|TypeScript 타입 시스템 (인터페이스 설계)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - TypeScript 타입 시스템 ( ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/TypeScript 타입 시스템 (인터페이스 설계).md]] +- Raw Source: 00_Raw/2026-04-20/TypeScript 타입 시스템 (인터페이스 설계).md --- diff --git a/01_Archive/2026-04-20/TypeScript 타입 시스템 및 인터페이스 설계.md b/01_Archive/2026-04-20/TypeScript 타입 시스템 및 인터페이스 설계.md index bef3bfaa..890eb96b 100644 --- a/01_Archive/2026-04-20/TypeScript 타입 시스템 및 인터페이스 설계.md +++ b/01_Archive/2026-04-20/TypeScript 타입 시스템 및 인터페이스 설계.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-9DE40A -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - TypeScript 타입 시스템 및 인터페이스 설계" --- -# [[TypeScript 타입 시스템 및 인터페이스 설계]] +# [[TypeScript 타입 시스템 및 인터페이스 설계|TypeScript 타입 시스템 및 인터페이스 설계]] ## 📌 한 줄 통찰 (The Karpathy Summary) > TypeScript의 타입 시스템은 객체의 실제 형태와 구조를 기준으로 호환성을 판단하는 구조적 타이핑(Structural Typing)을 근간으로 합니다 [1, 2]. 개발자는 시스템 설계 시 인터페이스와 타입 별칭을 전략적으로 선택하여 타입의 확장성과 컴파일러 성능을 최적화할 수 있습니다 [3-5]. 또한, 식별 가능한 유니온, 브랜디드 타입(Branded Types), `readonly` 및 `satisfies` 연산자 등의 고급 기능을 적극적으로 활용하여 런타임 에러를 방지하고 견고한 소프트웨어 아키텍처를 구축할 수 있습니다 [6-10]. @@ -33,11 +33,11 @@ github_commit: "[P-Reinforce] Continuous Worker - TypeScript 타입 시스템 - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[구조적 타이핑 (Structural Typing)]], [[식별 가능한 유니온 (Discriminated Unions)]], [[Branded Types]], [[satisfies 연산자]] -- **Projects/Contexts:** [[도메인 기반 설계 (DDD)]], [[SOLID 원칙 및 인터페이스 분리 원칙 (ISP)]] +- **Related Topics:** [[구조적 타이핑 (Structural Typing)|구조적 타이핑 (Structural Typing)]], [[식별 가능한 유니온 (Discriminated Unions)|식별 가능한 유니온 (Discriminated Unions)]], [[Branded Types|Branded Types]], [[satisfies 연산자|satisfies 연산자]] +- **Projects/Contexts:** [[도메인 기반 설계 (DDD)|도메인 기반 설계 (DDD)]], SOLID 원칙 및 인터페이스 분리 원칙 (ISP) - **Contradictions/Notes:** TypeScript 공식 문서와 성능 가이드는 컴파일 최적화를 위해 상속 시 `interface extends`를 권장합니다[16-18]. 하지만 일부 개발 팀들은 인터페이스 선언 병합(Declaration Merging)으로 인한 예기치 않은 부작용을 원천 차단하기 위해 모든 객체 정의에 대해 `Type` 별칭(alias)만 사용하도록 규칙을 강제하기도 합니다[19, 39, 40]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/TypeScript 타입 시스템 및 인터페이스 설계.md]] +- Raw Source: 00_Raw/2026-04-20/TypeScript 타입 시스템 및 인터페이스 설계.md --- diff --git a/01_Archive/2026-04-20/TypeScript 타입 시스템 아키텍처 및 도메인 기반 설계(DDD).md b/01_Archive/2026-04-20/TypeScript 타입 시스템 아키텍처 및 도메인 기반 설계(DDD).md index 3a9a649d..7e4cad60 100644 --- a/01_Archive/2026-04-20/TypeScript 타입 시스템 아키텍처 및 도메인 기반 설계(DDD).md +++ b/01_Archive/2026-04-20/TypeScript 타입 시스템 아키텍처 및 도메인 기반 설계(DDD).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-176A7F -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - TypeScript 타입 시스템 아키텍처 및 도메인 기반 설계(DDD)" --- -# [[TypeScript 타입 시스템 아키텍처 및 도메인 기반 설계(DDD)]] +# [[TypeScript 타입 시스템 아키텍처 및 도메인 기반 설계(DDD)|TypeScript 타입 시스템 아키텍처 및 도메인 기반 설계(DDD)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -36,11 +36,11 @@ github_commit: "[P-Reinforce] Continuous Worker - TypeScript 타입 시스템 - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[브랜디드 타입(Branded Types)]], [[식별 가능한 유니온(Discriminated Unions)]], [[구조적 타이핑(Structural Typing)]], [[Parse, Don't Validate]], [[완전성 검사(Exhaustiveness Checking)]] -- **Projects/Contexts:** [[Zod 유효성 검사 라이브러리 연동]], [[프론트엔드 상태 머신(State Machine) 구현]] +- **Related Topics:** [[브랜디드 타입(Branded Types)|브랜디드 타입(Branded Types)]], [[식별 가능한 유니온(Discriminated Unions)|식별 가능한 유니온(Discriminated Unions)]], [[구조적 타이핑(Structural Typing)|구조적 타이핑(Structural Typing)]], [[Parse dont validate|Parse, Don't Validate]], [[완전성 검사(Exhaustiveness Checking)|완전성 검사(Exhaustiveness Checking)]] +- **Projects/Contexts:** Zod 유효성 검사 라이브러리 연동, 프론트엔드 상태 머신(State Machine) 구현 - **Contradictions/Notes:** TypeScript는 본래 Java나 C#과 달리 명목적 타이핑(Nominal Typing)을 네이티브로 지원하지 않고 구조적 타이핑으로 동작합니다. 따라서 엄격한 도메인 설계를 구축하려면, 컴파일러를 속이는 방식(가짜 속성 추가 등)인 브랜디드 타입과 같은 우회 전략을 인위적으로 도입해야만 명목적 타이핑의 효과를 얻을 수 있습니다. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/TypeScript 타입 시스템 아키텍처 및 도메인 기반 설계(DDD).md]] +- Raw Source: 00_Raw/2026-04-20/TypeScript 타입 시스템 아키텍처 및 도메인 기반 설계(DDD).md --- diff --git a/01_Archive/2026-04-20/TypeScript 타입 시스템을 활용한 내부 로직 보호 및 데이터 검증.md b/01_Archive/2026-04-20/TypeScript 타입 시스템을 활용한 내부 로직 보호 및 데이터 검증.md index 3366943d..9075d4cd 100644 --- a/01_Archive/2026-04-20/TypeScript 타입 시스템을 활용한 내부 로직 보호 및 데이터 검증.md +++ b/01_Archive/2026-04-20/TypeScript 타입 시스템을 활용한 내부 로직 보호 및 데이터 검증.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-2609F8 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - TypeScript 타입 시스템을 활용한 내부 로직 보호 및 데이터 검증" --- -# [[TypeScript 타입 시스템을 활용한 내부 로직 보호 및 데이터 검증]] +# [[TypeScript 타입 시스템을 활용한 내부 로직 보호 및 데이터 검증|TypeScript 타입 시스템을 활용한 내부 로직 보호 및 데이터 검증]] ## 📌 한 줄 통찰 (The Karpathy Summary) > TypeScript의 타입 시스템은 컴파일 시점에 내부 로직을 보호하고 데이터 무결성을 검증하는 강력한 수비 기제를 제공합니다. 구조적 타이핑의 유연성에서 오는 한계점을 과잉 속성 체크(Excess Property Checking)와 `satisfies` 연산자로 보완하며, 브랜디드 타입(Branded Types)과 식별 가능한 유니온(Discriminated Unions)을 활용하여 잘못된 상태와 데이터 오염을 원천 차단합니다. 또한, 시스템 경계에서 "검증하지 말고 파싱하라(Parse, don't validate)" 원칙을 적용함으로써 런타임 환경에서도 예측 가능하고 견고한 애플리케이션 구조를 확립할 수 있습니다. @@ -33,11 +33,11 @@ github_commit: "[P-Reinforce] Continuous Worker - TypeScript 타입 시스템을 - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[구조적 타이핑 (Structural Typing)]], [[식별 가능한 유니온 (Discriminated Unions)]], [[브랜디드 타입 (Branded Types)]], [[satisfies 연산자]], [[Parse, Don't Validate]] -- **Projects/Contexts:** [[Zod를 활용한 런타임 데이터 파싱 및 검증]], [[Toss Front SDK의 Facade 패턴 설계 및 안전성 확보]] +- **Related Topics:** [[구조적 타이핑 (Structural Typing)|구조적 타이핑 (Structural Typing)]], [[식별 가능한 유니온 (Discriminated Unions)|식별 가능한 유니온 (Discriminated Unions)]], [[브랜디드 타입 (Branded Types)|브랜디드 타입 (Branded Types)]], [[satisfies 연산자|satisfies 연산자]], [[Parse dont validate|Parse, Don't Validate]] +- **Projects/Contexts:** Zod를 활용한 런타임 데이터 파싱 및 검증, Toss Front SDK의 Facade 패턴 설계 및 안전성 확보 - **Contradictions/Notes:** TypeScript의 구조적 타이핑은 매우 유연하여 덕 타이핑의 이점을 제공하지만, "의도하지 않은 초과 데이터의 유입"이라는 치명적인 보안적 허점을 만듭니다 [4, 21]. 이를 방어하기 위해 개발자들은 오히려 구조적 타이핑의 반대 개념인 명목적 타이핑(Nominal Typing) 특성을 강제로 모방한 브랜디드 타입을 사용하여 데이터를 격리해야 하는 역설적이지만 필수적인 설계 패턴을 따르게 됩니다 [21, 34, 35]. 또한, `any` 타입의 사용은 이러한 모든 타입 시스템의 보호막을 무력화시키므로 지양해야 하며, 출처를 알 수 없는 외부 데이터는 반드시 `unknown` 타입으로 선언 후 타입 가드를 거치도록 강제해야 합니다 [36-38]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/TypeScript 타입 시스템을 활용한 내부 로직 보호 및 데이터 검증.md]] +- Raw Source: 00_Raw/2026-04-20/TypeScript 타입 시스템을 활용한 내부 로직 보호 및 데이터 검증.md --- diff --git a/01_Archive/2026-04-20/TypeScript-Advanced-Type-System-Design.md b/01_Archive/2026-04-20/TypeScript-Advanced-Type-System-Design.md index 11afb726..ebcded44 100644 --- a/01_Archive/2026-04-20/TypeScript-Advanced-Type-System-Design.md +++ b/01_Archive/2026-04-20/TypeScript-Advanced-Type-System-Design.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-3E5992 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - TypeScript-Advanced-Type-System-Design" --- -# [[TypeScript-Advanced-Type-System-Design]] +# [[TypeScript-Advanced-Type-System-Design|TypeScript-Advanced-Type-System-Design]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - TypeScript-Advanced-Type-Syste ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/TypeScript-Advanced-Type-System-Design.md]] +- Raw Source: 00_Raw/2026-04-20/TypeScript-Advanced-Type-System-Design.md --- diff --git a/01_Archive/2026-04-20/TypeScript-Compiler-API-Design.md b/01_Archive/2026-04-20/TypeScript-Compiler-API-Design.md index 1e0d4773..6fcfab51 100644 --- a/01_Archive/2026-04-20/TypeScript-Compiler-API-Design.md +++ b/01_Archive/2026-04-20/TypeScript-Compiler-API-Design.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-D06F7B -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - TypeScript-Compiler-API-Design" --- -# [[TypeScript-Compiler-API-Design]] +# [[TypeScript-Compiler-API-Design|TypeScript-Compiler-API-Design]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - TypeScript-Compiler-API-Design ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/TypeScript-Compiler-API-Design.md]] +- Raw Source: 00_Raw/2026-04-20/TypeScript-Compiler-API-Design.md --- diff --git a/01_Archive/2026-04-20/TypeScript-Compiler-API-Integration.md b/01_Archive/2026-04-20/TypeScript-Compiler-API-Integration.md index 604d403d..a23b2556 100644 --- a/01_Archive/2026-04-20/TypeScript-Compiler-API-Integration.md +++ b/01_Archive/2026-04-20/TypeScript-Compiler-API-Integration.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-C996EE -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - TypeScript-Compiler-API-Integration" --- -# [[TypeScript-Compiler-API-Integration]] +# [[TypeScript-Compiler-API-Integration|TypeScript-Compiler-API-Integration]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - TypeScript-Compiler-API-Integr ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/TypeScript-Compiler-API-Integration.md]] +- Raw Source: 00_Raw/2026-04-20/TypeScript-Compiler-API-Integration.md --- diff --git a/01_Archive/2026-04-20/TypeScript-Compiler-API.md b/01_Archive/2026-04-20/TypeScript-Compiler-API.md index 8237d687..73407057 100644 --- a/01_Archive/2026-04-20/TypeScript-Compiler-API.md +++ b/01_Archive/2026-04-20/TypeScript-Compiler-API.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-9F7F6E -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - TypeScript-Compiler-API" --- -# [[TypeScript-Compiler-API]] +# [[TypeScript-Compiler-API|TypeScript-Compiler-API]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - TypeScript-Compiler-API" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/TypeScript-Compiler-API.md]] +- Raw Source: 00_Raw/2026-04-20/TypeScript-Compiler-API.md --- diff --git a/01_Archive/2026-04-20/TypeScript-Compiler-Architecture.md b/01_Archive/2026-04-20/TypeScript-Compiler-Architecture.md index 0f86439f..87598baa 100644 --- a/01_Archive/2026-04-20/TypeScript-Compiler-Architecture.md +++ b/01_Archive/2026-04-20/TypeScript-Compiler-Architecture.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-98247B -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - TypeScript-Compiler-Architecture" --- -# [[TypeScript-Compiler-Architecture]] +# [[TypeScript-Compiler-Architecture|TypeScript-Compiler-Architecture]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - TypeScript-Compiler-Architectu ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/TypeScript-Compiler-Architecture.md]] +- Raw Source: 00_Raw/2026-04-20/TypeScript-Compiler-Architecture.md --- diff --git a/01_Archive/2026-04-20/TypeScript-Domain-Driven-Design.md b/01_Archive/2026-04-20/TypeScript-Domain-Driven-Design.md index 918341be..18eb1ffa 100644 --- a/01_Archive/2026-04-20/TypeScript-Domain-Driven-Design.md +++ b/01_Archive/2026-04-20/TypeScript-Domain-Driven-Design.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-1EE94B -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - TypeScript-Domain-Driven-Design" --- -# [[TypeScript-Domain-Driven-Design]] +# [[TypeScript-Domain-Driven-Design|TypeScript-Domain-Driven-Design]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - TypeScript-Domain-Driven-Desig ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/TypeScript-Domain-Driven-Design.md]] +- Raw Source: 00_Raw/2026-04-20/TypeScript-Domain-Driven-Design.md --- diff --git a/01_Archive/2026-04-20/TypeScript-Interface-Design.md b/01_Archive/2026-04-20/TypeScript-Interface-Design.md index 3de67588..ee9e97c2 100644 --- a/01_Archive/2026-04-20/TypeScript-Interface-Design.md +++ b/01_Archive/2026-04-20/TypeScript-Interface-Design.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-8A42E4 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - TypeScript-Interface-Design" --- -# [[TypeScript-Interface-Design]] +# [[TypeScript-Interface-Design|TypeScript-Interface-Design]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - TypeScript-Interface-Design" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/TypeScript-Interface-Design.md]] +- Raw Source: 00_Raw/2026-04-20/TypeScript-Interface-Design.md --- diff --git a/01_Archive/2026-04-20/TypeScript-Language-Service-API.md b/01_Archive/2026-04-20/TypeScript-Language-Service-API.md index 04eba6ce..d7559dbd 100644 --- a/01_Archive/2026-04-20/TypeScript-Language-Service-API.md +++ b/01_Archive/2026-04-20/TypeScript-Language-Service-API.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-C7C758 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - TypeScript-Language-Service-API" --- -# [[TypeScript-Language-Service-API]] +# [[TypeScript-Language-Service-API|TypeScript-Language-Service-API]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - TypeScript-Language-Service-AP ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/TypeScript-Language-Service-API.md]] +- Raw Source: 00_Raw/2026-04-20/TypeScript-Language-Service-API.md --- diff --git a/01_Archive/2026-04-20/TypeScript-Language-Service.md b/01_Archive/2026-04-20/TypeScript-Language-Service.md index e2a9398c..8a055233 100644 --- a/01_Archive/2026-04-20/TypeScript-Language-Service.md +++ b/01_Archive/2026-04-20/TypeScript-Language-Service.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-90F4A8 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - TypeScript-Language-Service" --- -# [[TypeScript-Language-Service]] +# [[TypeScript-Language-Service|TypeScript-Language-Service]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - TypeScript-Language-Service" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/TypeScript-Language-Service.md]] +- Raw Source: 00_Raw/2026-04-20/TypeScript-Language-Service.md --- diff --git a/01_Archive/2026-04-20/TypeScript-Project-References.md b/01_Archive/2026-04-20/TypeScript-Project-References.md index 000e6e4a..e7837422 100644 --- a/01_Archive/2026-04-20/TypeScript-Project-References.md +++ b/01_Archive/2026-04-20/TypeScript-Project-References.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-E852BD -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - TypeScript-Project-References" --- -# [[TypeScript-Project-References]] +# [[TypeScript-Project-References|TypeScript-Project-References]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - TypeScript-Project-References" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/TypeScript-Project-References.md]] +- Raw Source: 00_Raw/2026-04-20/TypeScript-Project-References.md --- diff --git a/01_Archive/2026-04-20/TypeScript-Type-System-Architecture.md b/01_Archive/2026-04-20/TypeScript-Type-System-Architecture.md index 30caeb9d..7ac1b90a 100644 --- a/01_Archive/2026-04-20/TypeScript-Type-System-Architecture.md +++ b/01_Archive/2026-04-20/TypeScript-Type-System-Architecture.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-82C949 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - TypeScript-Type-System-Architecture" --- -# [[TypeScript-Type-System-Architecture]] +# [[TypeScript-Type-System-Architecture|TypeScript-Type-System-Architecture]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - TypeScript-Type-System-Archite ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/TypeScript-Type-System-Architecture.md]] +- Raw Source: 00_Raw/2026-04-20/TypeScript-Type-System-Architecture.md --- diff --git a/01_Archive/2026-04-20/TypeScript-Type-System-Design.md b/01_Archive/2026-04-20/TypeScript-Type-System-Design.md index 1eadf4b1..8c783d70 100644 --- a/01_Archive/2026-04-20/TypeScript-Type-System-Design.md +++ b/01_Archive/2026-04-20/TypeScript-Type-System-Design.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-F844F1 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - TypeScript-Type-System-Design" --- -# [[TypeScript-Type-System-Design]] +# [[TypeScript-Type-System-Design|TypeScript-Type-System-Design]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - TypeScript-Type-System-Design" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/TypeScript-Type-System-Design.md]] +- Raw Source: 00_Raw/2026-04-20/TypeScript-Type-System-Design.md --- diff --git a/01_Archive/2026-04-20/TypeScript-Type-System-Interface-Design.md b/01_Archive/2026-04-20/TypeScript-Type-System-Interface-Design.md index 313458af..b9d0fac3 100644 --- a/01_Archive/2026-04-20/TypeScript-Type-System-Interface-Design.md +++ b/01_Archive/2026-04-20/TypeScript-Type-System-Interface-Design.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-9A759D -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - TypeScript-Type-System-Interface-Design" --- -# [[TypeScript-Type-System-Interface-Design]] +# [[TypeScript-Type-System-Interface-Design|TypeScript-Type-System-Interface-Design]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - TypeScript-Type-System-Interfa ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/TypeScript-Type-System-Interface-Design.md]] +- Raw Source: 00_Raw/2026-04-20/TypeScript-Type-System-Interface-Design.md --- diff --git a/01_Archive/2026-04-20/TypeScript-Type-System.md b/01_Archive/2026-04-20/TypeScript-Type-System.md index 1c6f3276..96736235 100644 --- a/01_Archive/2026-04-20/TypeScript-Type-System.md +++ b/01_Archive/2026-04-20/TypeScript-Type-System.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-6060FE -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - TypeScript-Type-System" --- -# [[TypeScript-Type-System]] +# [[TypeScript-Type-System|TypeScript-Type-System]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - TypeScript-Type-System" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/TypeScript-Type-System.md]] +- Raw Source: 00_Raw/2026-04-20/TypeScript-Type-System.md --- diff --git a/01_Archive/2026-04-20/TypeScript의 안전한 인터페이스 설계.md b/01_Archive/2026-04-20/TypeScript의 안전한 인터페이스 설계.md index ea4987b5..9cbcaa5e 100644 --- a/01_Archive/2026-04-20/TypeScript의 안전한 인터페이스 설계.md +++ b/01_Archive/2026-04-20/TypeScript의 안전한 인터페이스 설계.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-08AE3A -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - TypeScript의 안전한 인터페이스 설계" --- -# [[TypeScript의 안전한 인터페이스 설계]] +# [[TypeScript의 안전한 인터페이스 설계|TypeScript의 안전한 인터페이스 설계]] ## 📌 한 줄 통찰 (The Karpathy Summary) > TypeScript의 인터페이스 설계는 언어의 근본적인 특성인 구조적 타이핑(Structural Typing)의 유연성을 수용하면서도, 의도치 않은 데이터 유입과 런타임 에러를 방어하는 것을 핵심으로 합니다 [1-3]. 이를 위해 개발자는 `interface`와 `type alias`를 전략적으로 선택하고, `readonly`를 통한 불변성 확보, 식별 가능한 유니온을 활용한 상태 관리, 그리고 `satisfies` 연산자나 브랜디드 타입(Branded Types) 같은 고급 기법을 동원해야 합니다 [4-8]. 결과적으로 안전한 인터페이스 설계는 시스템의 예측 가능성을 높이고 변경에 따른 부작용을 최소화하는 견고한 아키텍처적 도구로 작용합니다 [9]. @@ -36,11 +36,11 @@ github_commit: "[P-Reinforce] Continuous Worker - TypeScript의 안전한 인터 - **정책 변화:** Design & Experience 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[구조적 타이핑]], [[과잉 속성 체크(EPC)]], [[식별 가능한 유니온]], [[브랜디드 타입]], [[불변성(Immutability)]] -- **Projects/Contexts:** [[대규모 애플리케이션 개발]], [[프론트엔드 아키텍처 및 SDK 설계]] +- **Related Topics:** [[구조적 타이핑|구조적 타이핑]], [[과잉 속성 체크(EPC)|과잉 속성 체크(EPC)]], [[식별 가능한 유니온|식별 가능한 유니온]], [[브랜디드 타입|브랜디드 타입]], [[불변성(Immutability)|불변성(Immutability)]] +- **Projects/Contexts:** [[대규모 애플리케이션 개발|대규모 애플리케이션 개발]], 프론트엔드 아키텍처 및 SDK 설계 - **Contradictions/Notes:** `type`과 `interface`의 사용 지침과 관련하여, TypeScript 성능과 캐싱을 고려해 객체 확장에 `interface extends`를 권장하는 측면과 [4, 14], 선언 병합(Declaration Merging)으로 인한 의도치 않은 타입 변경을 방지하기 위해 보다 엄격한 `type`의 사용을 선호하는 개발자들의 의견이 대립하는 사례가 존재합니다 [15, 17, 34, 35]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/TypeScript의 안전한 인터페이스 설계.md]] +- Raw Source: 00_Raw/2026-04-20/TypeScript의 안전한 인터페이스 설계.md --- diff --git a/01_Archive/2026-04-20/TypeScript의 인터페이스 및 객체 타입 설계.md b/01_Archive/2026-04-20/TypeScript의 인터페이스 및 객체 타입 설계.md index 1af6b310..bcc522ec 100644 --- a/01_Archive/2026-04-20/TypeScript의 인터페이스 및 객체 타입 설계.md +++ b/01_Archive/2026-04-20/TypeScript의 인터페이스 및 객체 타입 설계.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-844A65 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - TypeScript의 인터페이스 및 객체 타입 설계" --- -# [[TypeScript의 인터페이스 및 객체 타입 설계]] +# [[TypeScript의 인터페이스 및 객체 타입 설계|TypeScript의 인터페이스 및 객체 타입 설계]] ## 📌 한 줄 통찰 (The Karpathy Summary) > TypeScript의 인터페이스와 객체 타입 설계는 명시적인 이름이 아닌 객체의 실제 형태와 속성을 기준으로 타입 호환성을 결정하는 구조적 타이핑(Structural Typing)을 근간으로 합니다. 확장성과 컴파일 성능을 고려하여 인터페이스(Interface)와 타입 별칭(Type Alias)을 전략적으로 선택해야 하며, `readonly` 수식어, 초과 속성 검사(Excess Property Checking), `satisfies` 연산자 등의 도구를 활용해 런타임 오류를 방지하고 견고하고 예측 가능한 객체 경계를 구축하는 것이 설계의 핵심입니다. @@ -37,11 +37,11 @@ TypeScript의 객체 타입은 명목적 타이핑(Nominal Typing)과 달리 명 - **정책 변화:** Design & Experience 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[구조적 타이핑 (Structural Typing)]], [[초과 속성 검사 (Excess Property Checking)]], [[선언 병합 (Declaration Merging)]], [[satisfies 연산자]] -- **Projects/Contexts:** [[대규모 TypeScript 애플리케이션 아키텍처 구축]], [[SOLID 원칙 기반의 타입 시스템 설계]] +- **Related Topics:** [[구조적 타이핑 (Structural Typing)|구조적 타이핑 (Structural Typing)]], [[초과 속성 검사 (Excess Property Checking)|초과 속성 검사 (Excess Property Checking)]], [[선언 병합 (Declaration Merging)|선언 병합 (Declaration Merging)]], [[satisfies 연산자|satisfies 연산자]] +- **Projects/Contexts:** 대규모 TypeScript 애플리케이션 아키텍처 구축, SOLID 원칙 기반의 타입 시스템 설계 - **Contradictions/Notes:** 소스 간 의견 대립이 존재합니다. 일부 개발자(소스 52, 138, 141)는 캐싱 성능 최적화와 외부 확장을 위한 선언 병합 기능 때문에 '인터페이스(Interface) 우선 사용'을 강력히 주장하지만, 또 다른 현업 개발자(소스 138, 140, 147)는 의도치 않은 선언 병합으로 인해 런타임 로직이 오염될 위험과 일관된 문법을 이유로 '모든 상황에서 타입 별칭(Type)만을 사용하는 규칙'을 조직 내에 강제하는 것이 장기 유지보수에 유리하다고 반박합니다. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/TypeScript의 인터페이스 및 객체 타입 설계.md]] +- Raw Source: 00_Raw/2026-04-20/TypeScript의 인터페이스 및 객체 타입 설계.md --- diff --git a/01_Archive/2026-04-20/TypeScript의 제어 흐름 분석 및 상태 관리 패턴.md b/01_Archive/2026-04-20/TypeScript의 제어 흐름 분석 및 상태 관리 패턴.md index cadb5fa7..da8022b0 100644 --- a/01_Archive/2026-04-20/TypeScript의 제어 흐름 분석 및 상태 관리 패턴.md +++ b/01_Archive/2026-04-20/TypeScript의 제어 흐름 분석 및 상태 관리 패턴.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-348B57 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - TypeScript의 제어 흐름 분석 및 상태 관리 패턴" --- -# [[TypeScript의 제어 흐름 분석 및 상태 관리 패턴]] +# [[TypeScript의 제어 흐름 분석 및 상태 관리 패턴|TypeScript의 제어 흐름 분석 및 상태 관리 패턴]] ## 📌 한 줄 통찰 (The Karpathy Summary) > TypeScript의 제어 흐름 분석과 상태 관리 패턴은 컴파일러가 런타임의 코드 흐름을 추론하여 타입을 안전하고 구체적으로 좁혀나가는(Narrowing) 메커니즘을 핵심으로 합니다 [1, 2]. 특히 '식별 가능한 유니온(Discriminated Unions)' 패턴을 활용하면 복잡한 조건부 분기를 간결하게 처리하고, 유효하지 않은 상태(Invalid state)가 발생하는 것을 원천적으로 방지할 수 있습니다 [3-5]. 이 패턴은 완전성 검사(Exhaustiveness Checking)와 결합되어 복잡한 상태 머신 모델링이나 React 애플리케이션 등에서 시스템의 아키텍처적 안정성을 크게 높이는 데 기여합니다 [4, 6, 7]. @@ -33,11 +33,11 @@ github_commit: "[P-Reinforce] Continuous Worker - TypeScript의 제어 흐름 - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Type Narrowing]], [[Discriminated Unions]], [[Exhaustiveness Checking]], [[State Machine Pattern]], [[ts-pattern]] -- **Projects/Contexts:** [[React State Management]], [[API Response Handling]], [[Form Handling]] +- **Related Topics:** [[Type Narrowing|Type Narrowing]], [[Discriminated Unions|Discriminated Unions]], [[Exhaustiveness-Checking|Exhaustiveness Checking]], State Machine Pattern, [[ts-pattern|ts-pattern]] +- **Projects/Contexts:** React State Management, API Response Handling, Form Handling - **Contradictions/Notes:** 복잡한 조건부 분기를 처리할 때 `ts-pattern` 라이브러리는 훌륭한 타입 안전성과 완전성 검사를 제공하지만, 기존의 `if/else`나 `switch` 제어문에 비해 성능 오버헤드가 발생할 수 있으므로, 성능이 중요한 상황이거나 복잡도가 낮은 분기에서는 기본 제어 구조나 Early return을 활용하는 것이 더 효율적일 수 있습니다 [17-19]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/TypeScript의 제어 흐름 분석 및 상태 관리 패턴.md]] +- Raw Source: 00_Raw/2026-04-20/TypeScript의 제어 흐름 분석 및 상태 관리 패턴.md --- diff --git a/01_Archive/2026-04-20/TypedArray.md b/01_Archive/2026-04-20/TypedArray.md index 1cf82548..7868ce47 100644 --- a/01_Archive/2026-04-20/TypedArray.md +++ b/01_Archive/2026-04-20/TypedArray.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-DEE006 -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - TypedArray" --- -# [[TypedArray]] +# [[TypedArray|TypedArray]] ## 📌 한 줄 통찰 (The Karpathy Summary) > TypedArray는 Three.js 등의 WebGL 렌더링 환경에서 정점 데이터나 인스턴스의 속성값(예: `Float32Array`를 통한 UV 오프셋 등)을 저장하고 GPU로 전달하기 위해 사용되는 자바스크립트의 데이터 구조입니다 [1, 2]. 대규모 그래픽 데이터를 처리하는 데 사용되지만, 동적 환경에서 잦은 할당 및 해제는 성능 저하를 일으킬 수 있습니다 [3]. 다만 본 문서의 전반적인 작동 원리나 세부 명세에 대해서는 **소스에 관련 정보가 부족합니다.** @@ -22,11 +22,11 @@ github_commit: "[P-Reinforce] Continuous Worker - TypedArray" - **정책 변화:** Graphics & Performance 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[InstancedMesh]], [[InstancedBufferAttribute]], [[Garbage Collection]] -- **Projects/Contexts:** [[Three.js 메모리 관리 및 렌더링 최적화]] +- **Related Topics:** [[InstancedMesh|InstancedMesh]], InstancedBufferAttribute, [[Garbage Collection|Garbage Collection]] +- **Projects/Contexts:** Three.js 메모리 관리 및 렌더링 최적화 - **Contradictions/Notes:** 제공된 소스는 TypedArray 자체의 기능적 설명보다는, 이를 활용한 대규모 인스턴스 환경에서 동적 버퍼 확장이 유발하는 메모리 해제와 생성의 위험성(프레임 드랍)을 경고하는 데 초점을 맞추고 있습니다 [3]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/TypedArray.md]] +- Raw Source: 00_Raw/2026-04-20/TypedArray.md --- diff --git a/01_Archive/2026-04-20/UNESCO-Memory-of-the-World.md b/01_Archive/2026-04-20/UNESCO-Memory-of-the-World.md index c0129d5e..c2789ee8 100644 --- a/01_Archive/2026-04-20/UNESCO-Memory-of-the-World.md +++ b/01_Archive/2026-04-20/UNESCO-Memory-of-the-World.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-8CC54C -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - UNESCO-Memory-of-the-World" --- -# [[UNESCO-Memory-of-the-World]] +# [[UNESCO-Memory-of-the-World|UNESCO-Memory-of-the-World]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - UNESCO-Memory-of-the-World" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/UNESCO-Memory-of-the-World.md]] +- Raw Source: 00_Raw/2026-04-20/UNESCO-Memory-of-the-World.md --- diff --git a/01_Archive/2026-04-20/USD - Universal Scene Description.md b/01_Archive/2026-04-20/USD - Universal Scene Description.md index 75f47a9f..b8f819ac 100644 --- a/01_Archive/2026-04-20/USD - Universal Scene Description.md +++ b/01_Archive/2026-04-20/USD - Universal Scene Description.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-B0E0B6 -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - USD - Universal Scene Description" --- -# [[USD - Universal Scene Description]] +# [[USD - Universal Scene Description|USD - Universal Scene Description]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - USD - Universal Scene Descript ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/USD - Universal Scene Description.md]] +- Raw Source: 00_Raw/2026-04-20/USD - Universal Scene Description.md --- diff --git a/01_Archive/2026-04-20/UV Offset.md b/01_Archive/2026-04-20/UV Offset.md index 73780076..f87d2709 100644 --- a/01_Archive/2026-04-20/UV Offset.md +++ b/01_Archive/2026-04-20/UV Offset.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-FF2C8C -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - UV Offset" --- -# [[UV Offset]] +# [[UV Offset|UV Offset]] ## 📌 한 줄 통찰 (The Karpathy Summary) > UV Offset(UV 오프셋)은 3D 모델에 텍스처의 특정 영역을 매핑하기 위해 UV 좌표를 조정하거나 계산하는 기법입니다 [1, 2]. 실시간 렌더링 최적화 환경에서는 여러 텍스처를 하나로 합친 텍스처 아틀라스(Texture Atlas)와 함께 주로 사용됩니다 [3, 4]. 특히 수많은 인스턴스를 렌더링할 때 각 인스턴스의 속성으로 UV 오프셋을 전달함으로써, 단일 드로우 콜(Draw Call) 내에서 개별 인스턴스마다 다른 텍스처 이미지를 적용할 수 있게 해줍니다 [5, 6]. @@ -22,11 +22,11 @@ github_commit: "[P-Reinforce] Continuous Worker - UV Offset" - **정책 변화:** Graphics & Performance 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Texture Atlas]], [[InstancedMesh]], [[BufferAttribute]] -- **Projects/Contexts:** [[Three.js]], [[WebGL Optimization]] +- **Related Topics:** [[Texture Atlas|Texture Atlas]], [[InstancedMesh|InstancedMesh]], [[BufferAttribute|BufferAttribute]] +- **Projects/Contexts:** [[Three.js|Three.js]], [[WebGL Optimization|WebGL Optimization]] - **Contradictions/Notes:** 텍스처 아틀라스와 UV 오프셋의 조합은 인스턴싱 최적화를 위해 필수적이지만 UV 연산의 복잡성과 경계선 블리딩(Edge Bleeding)이라는 한계를 가지며, 소스에 따르면 이를 완전히 회피하기 위한 대안으로 데이터 배열 텍스처(Data Array Textures)의 사용이 제안됩니다 [2, 11]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/UV Offset.md]] +- Raw Source: 00_Raw/2026-04-20/UV Offset.md --- diff --git a/01_Archive/2026-04-20/UX Design Gamification.md b/01_Archive/2026-04-20/UX Design Gamification.md index f8bfd08d..2e347001 100644 --- a/01_Archive/2026-04-20/UX Design Gamification.md +++ b/01_Archive/2026-04-20/UX Design Gamification.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-C3544E -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - UX Design Gamification" --- -# [[UX Design Gamification]] +# [[UX Design Gamification|UX Design Gamification]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - UX Design Gamification" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/UX Design & Gamification.md]] +- Raw Source: 00_Raw/2026-04-20/UX Design & Gamification.md --- diff --git a/01_Archive/2026-04-20/UX Design & Gamification.md b/01_Archive/2026-04-20/UX Design & Gamification.md index 6e7b0244..e9185309 100644 --- a/01_Archive/2026-04-20/UX Design & Gamification.md +++ b/01_Archive/2026-04-20/UX Design & Gamification.md @@ -1,4 +1,4 @@ -[[UX Design & Gamification]] +[[UX Design & Gamification|UX Design & Gamification]] 📌 Brief Summary UX Design and Gamification is the strategic integration of game mechanics, aesthetics, and ludic elements into non-game user interfaces to enhance user engagement, motivation, and retention. It leverages psychological frameworks—such as Self-Determination Theory (SDT)—to transform functional tasks into rewarding experiences by optimizing the balance between challenge and skill. @@ -24,8 +24,8 @@ The intersection of UX Design and Gamification moves beyond superficial "points * A significant area of academic scrutiny involves "Dark Gamification," where mechanics are used to manipulate users into addictive behaviors or unintended financial expenditures (e.g., loot boxes, predatory microtransactions), violating the core UX principle of user-centricity and well-being. 🔗 Knowledge Connections -* Related Topics: [[Self-Determination Theory]], [[Behavioral Economics]], [[Human-Computer Interaction (HCI)]], [[Dopaminergic Reward Systems]] -* Projects/Contexts: [[Duolingo (Language Learning)], [Fitness Tracking Apps (Strava/Fitbit)], [EdTech Gamification], [FinTech Engagement Strategies]] +* Related Topics: [[Self-Determination Theory|Self-Determination Theory]], [[Behavioral Economics|Behavioral Economics]], [[Human-Computer Interaction (HCI)|Human-Computer Interaction (HCI)]], [[Dopaminergic Reward Systems|Dopaminergic Reward Systems]] +* Projects/Contexts: [[Duolingo (Language Learning)] [Fitness Tracking Apps (Strava_Fitbit)] [EdTech Gamification] [FinTech Engagement Strategies|Duolingo (Language Learning)], [Fitness Tracking Apps (Strava/Fitbit)], [EdTech Gamification], [FinTech Engagement Strategies]] * Contradictions/Notes: There is an active debate regarding "Extrinsic Crowding-Out," where the introduction of external rewards (points/badges) may inadvertently decrease a user's pre-existing intrinsic interest in a task. Last updated: 2026-04-16 \ No newline at end of file diff --git a/01_Archive/2026-04-20/UX-Design-Architecture.md b/01_Archive/2026-04-20/UX-Design-Architecture.md index 0dc5a16b..4a089439 100644 --- a/01_Archive/2026-04-20/UX-Design-Architecture.md +++ b/01_Archive/2026-04-20/UX-Design-Architecture.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-6A1026 -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - UX-Design-Architecture" --- -# [[UX-Design-Architecture]] +# [[UX-Design-Architecture|UX-Design-Architecture]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - UX-Design-Architecture" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/UX-Design-Architecture.md]] +- Raw Source: 00_Raw/2026-04-20/UX-Design-Architecture.md --- diff --git a/01_Archive/2026-04-20/UX-Design-and-Engagement.md b/01_Archive/2026-04-20/UX-Design-and-Engagement.md index d5ea0967..3f0d3907 100644 --- a/01_Archive/2026-04-20/UX-Design-and-Engagement.md +++ b/01_Archive/2026-04-20/UX-Design-and-Engagement.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-6D50AA -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - UX-Design-and-Engagement" --- -# [[UX-Design-and-Engagement]] +# [[UX-Design-and-Engagement|UX-Design-and-Engagement]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - UX-Design-and-Engagement" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/UX-Design-and-Engagement.md]] +- Raw Source: 00_Raw/2026-04-20/UX-Design-and-Engagement.md --- diff --git a/01_Archive/2026-04-20/UX-Gamification.md b/01_Archive/2026-04-20/UX-Gamification.md index a13b4115..399fc89a 100644 --- a/01_Archive/2026-04-20/UX-Gamification.md +++ b/01_Archive/2026-04-20/UX-Gamification.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AI-042 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.95 tags: [ux, gamification, design, psychology] last_reinforced: 2026-06-XX github_commit: "[P-Reinforce] Processed UX_Gamification.md" --- -# [[UX - Gamification]] (사용자 경험 및 게이미피케이션) +# [[UX-Gamification|UX - Gamification]] (사용자 경험 및 게이미피케이션) ## 📌 한 줄 통찰 (The Karpathy Summary) > 게임 메커니즘을 활용해 사용자의 동기를 유발하고 지속적인 참여를 설계하는 것은, 사용자 경험(UX)의 목표와 행동 심리학적 원리를 결합한 필수 전략이다. @@ -28,7 +28,7 @@ github_commit: "[P-Reinforce] Processed UX_Gamification.md" - **정책 변화:** 게이미피케이션의 남용은 '보상의 역효과 (Overjustification Effect)'를 초래할 수 있으므로, 보상이 학습 자체를 방해하지 않도록 신중하게 설계해야 한다. ## 🔗 지식 연결 (Graph) -- Parent: [[User Experience (UX) Design]] -- Related: [[Self-Determination Theory]] , [[Behavioral Economics]] , [[Gamification-Design]] -- Raw Source: [[00_Raw/UX_Gamification.md]] +- Parent: [[User Experience (UX) Design|User Experience (UX) Design]] +- Related: [[Self-Determination Theory|Self-Determination Theory]] , [[Behavioral Economics|Behavioral Economics]] , [[Gamification-Design|Gamification-Design]] +- Raw Source: 00_Raw/UX_Gamification.md --- \ No newline at end of file diff --git a/01_Archive/2026-04-20/UX-Research-Methodologies.md b/01_Archive/2026-04-20/UX-Research-Methodologies.md index d4310520..0d826064 100644 --- a/01_Archive/2026-04-20/UX-Research-Methodologies.md +++ b/01_Archive/2026-04-20/UX-Research-Methodologies.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-037092 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - UX-Research-Methodologies" --- -# [[UX-Research-Methodologies]] +# [[UX-Research-Methodologies|UX-Research-Methodologies]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - UX-Research-Methodologies" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/UX-Research-Methodologies.md]] +- Raw Source: 00_Raw/2026-04-20/UX-Research-Methodologies.md --- diff --git a/01_Archive/2026-04-20/UX_UI in Interactive Media.md b/01_Archive/2026-04-20/UX_UI in Interactive Media.md index c1b4db6a..8d6e1e81 100644 --- a/01_Archive/2026-04-20/UX_UI in Interactive Media.md +++ b/01_Archive/2026-04-20/UX_UI in Interactive Media.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-8F3CFA -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - UX_UI in Interactive Media" --- -# [[UX_UI in Interactive Media]] +# [[UX_UI in Interactive Media|UX_UI in Interactive Media]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - UX_UI in Interactive Media" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/UX_UI in Interactive Media.md]] +- Raw Source: 00_Raw/2026-04-20/UX_UI in Interactive Media.md --- diff --git a/01_Archive/2026-04-20/Ubiquitous Computing Paradigm.md b/01_Archive/2026-04-20/Ubiquitous Computing Paradigm.md index bd90d979..d4f187a1 100644 --- a/01_Archive/2026-04-20/Ubiquitous Computing Paradigm.md +++ b/01_Archive/2026-04-20/Ubiquitous Computing Paradigm.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-C59CA1 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Ubiquitous Computing Paradigm" --- -# [[Ubiquitous Computing Paradigm]] +# [[Ubiquitous Computing Paradigm|Ubiquitous Computing Paradigm]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Ubiquitous Computing Paradigm" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Ubiquitous Computing Paradigm.md]] +- Raw Source: 00_Raw/2026-04-20/Ubiquitous Computing Paradigm.md --- diff --git a/01_Archive/2026-04-20/Ubiquitous Computing.md b/01_Archive/2026-04-20/Ubiquitous Computing.md index f842b465..1d9073cb 100644 --- a/01_Archive/2026-04-20/Ubiquitous Computing.md +++ b/01_Archive/2026-04-20/Ubiquitous Computing.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-8C0151 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Ubiquitous Computing" --- -# [[Ubiquitous Computing]] +# [[Ubiquitous Computing|Ubiquitous Computing]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Ubiquitous Computing" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Ubiquitous Computing.md]] +- Raw Source: 00_Raw/2026-04-20/Ubiquitous Computing.md --- diff --git a/01_Archive/2026-04-20/Ubiquitous-Computing.md b/01_Archive/2026-04-20/Ubiquitous-Computing.md index 66f4f900..87d1baee 100644 --- a/01_Archive/2026-04-20/Ubiquitous-Computing.md +++ b/01_Archive/2026-04-20/Ubiquitous-Computing.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-6333BB -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Ubiquitous-Computing" --- -# [[Ubiquitous-Computing]] +# [[Ubiquitous-Computing|Ubiquitous-Computing]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Ubiquitous-Computing" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Ubiquitous-Computing.md]] +- Raw Source: 00_Raw/2026-04-20/Ubiquitous-Computing.md --- diff --git a/01_Archive/2026-04-20/Ubiquitous-Language-Encoding.md b/01_Archive/2026-04-20/Ubiquitous-Language-Encoding.md index 2792dc21..b1db3d39 100644 --- a/01_Archive/2026-04-20/Ubiquitous-Language-Encoding.md +++ b/01_Archive/2026-04-20/Ubiquitous-Language-Encoding.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-3B5892 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Ubiquitous-Language-Encoding" --- -# [[Ubiquitous-Language-Encoding]] +# [[Ubiquitous-Language-Encoding|Ubiquitous-Language-Encoding]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Ubiquitous-Language-Encoding" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Ubiquitous-Language-Encoding.md]] +- Raw Source: 00_Raw/2026-04-20/Ubiquitous-Language-Encoding.md --- diff --git a/01_Archive/2026-04-20/Unified-User-Experience.md b/01_Archive/2026-04-20/Unified-User-Experience.md index b2030c37..9ea95fd5 100644 --- a/01_Archive/2026-04-20/Unified-User-Experience.md +++ b/01_Archive/2026-04-20/Unified-User-Experience.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-0A5862 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Unified-User-Experience" --- -# [[Unified-User-Experience]] +# [[Unified-User-Experience|Unified-User-Experience]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Unified-User-Experience" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Unified-User-Experience.md]] +- Raw Source: 00_Raw/2026-04-20/Unified-User-Experience.md --- diff --git a/01_Archive/2026-04-20/Union Types.md b/01_Archive/2026-04-20/Union Types.md index 1d6fae3f..37fc2305 100644 --- a/01_Archive/2026-04-20/Union Types.md +++ b/01_Archive/2026-04-20/Union Types.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-696914 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Union Types" --- -# [[Union Types]] +# [[Union Types|Union Types]] ## 📌 한 줄 통찰 (The Karpathy Summary) > Union Types는 TypeScript에서 하나의 값이 여러 타입 중 하나를 가질 수 있음을 나타내는 기능입니다 [1, 2]. 수직선(`|`) 기호를 사용하여 타입들을 연결하며(예: `string | number`), `any` 타입을 사용하는 것보다 타입 안전성을 유지하면서도 유연한 코드를 작성할 수 있게 해줍니다 [1-3]. 집합론적 관점에서는 두 개 이상의 타입 집합을 합친 합집합(Union)으로 기능합니다 [4, 5]. @@ -24,11 +24,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Union Types" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Intersection Types]], [[Discriminated Unions]], [[Type Narrowing]], [[Set Theory]] -- **Projects/Contexts:** [[TypeScript Type System]], [[State Management]] +- **Related Topics:** [[교집합 타입 (Intersection Types)|Intersection Types]], [[Discriminated Unions|Discriminated Unions]], [[Type Narrowing|Type Narrowing]], [[집합론 (Set Theory)|Set Theory]] +- **Projects/Contexts:** [[TypeScript-Type-System|TypeScript Type System]], [[상태 관리(State Management)|State Management]] - **Contradictions/Notes:** Union Types는 값의 유연성을 보장(`A` 혹은 `B` 중 하나 허용)하지만, 객체 속성에 접근할 때는 유니온의 모든 타입에 공통으로 존재하는 속성(교집합 형태)만 접근할 수 있는 엄격함이 있으므로 이를 다룰 때는 항상 타입 좁히기(Type Narrowing)가 선행되어야 합니다 [2, 8]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/Union Types.md]] +- Raw Source: 00_Raw/2026-04-20/Union Types.md --- diff --git a/01_Archive/2026-04-20/Union-Types-vs-Overloading.md b/01_Archive/2026-04-20/Union-Types-vs-Overloading.md index 39e5bcda..cf163e65 100644 --- a/01_Archive/2026-04-20/Union-Types-vs-Overloading.md +++ b/01_Archive/2026-04-20/Union-Types-vs-Overloading.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-13D0FE -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Union-Types-vs-Overloading" --- -# [[Union-Types-vs-Overloading]] +# [[Union-Types-vs-Overloading|Union-Types-vs-Overloading]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Union-Types-vs-Overloading" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Union-Types-vs-Overloading.md]] +- Raw Source: 00_Raw/2026-04-20/Union-Types-vs-Overloading.md --- diff --git a/01_Archive/2026-04-20/Union-Types.md b/01_Archive/2026-04-20/Union-Types.md index afc5641c..1d13db6b 100644 --- a/01_Archive/2026-04-20/Union-Types.md +++ b/01_Archive/2026-04-20/Union-Types.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-A21B05 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Union-Types" --- -# [[Union-Types]] +# [[Union-Types|Union-Types]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Union-Types" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Union-Types.md]] +- Raw Source: 00_Raw/2026-04-20/Union-Types.md --- diff --git a/01_Archive/2026-04-20/Unity.md b/01_Archive/2026-04-20/Unity.md index 93df94a9..2e221f18 100644 --- a/01_Archive/2026-04-20/Unity.md +++ b/01_Archive/2026-04-20/Unity.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-6033D2 -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Unity" --- -# [[Unity]] +# [[Unity|Unity]] ## 📌 한 줄 통찰 (The Karpathy Summary) > Unity는 2D 및 3D 프로젝트를 개발할 수 있는 소프트웨어 엔진 및 플랫폼입니다 [1]. 그래픽 렌더링 파이프라인, 물리 시스템, 씬(Scene) 및 게임 오브젝트(GameObject) 구성을 지원하며, 높은 그래픽 성능을 달성하기 위한 다양한 도구를 제공합니다 [1, 2]. 특히 화면에 기하학적 구조를 그리기 위해 그래픽 API에 명령을 내리는 드로우 콜(Draw call)과 렌더 상태 변경(Render-state changes)을 최적화하는 아키텍처가 핵심적으로 다뤄집니다 [3, 4]. @@ -34,11 +34,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Unity" - **정책 변화:** Graphics & Performance 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[GPU Instancing]], [[Draw Call Batching]], [[Scriptable Render Pipeline (SRP)]], [[GameObject]] -- **Projects/Contexts:** [[Needle Engine]], [[Optimizing draw calls]] +- **Related Topics:** GPU Instancing, Draw Call Batching, Scriptable Render Pipeline (SRP), GameObject +- **Projects/Contexts:** [[Needle Engine|Needle Engine]], Optimizing draw calls - **Contradictions/Notes:** Unity는 여러 드로우 콜 최적화 옵션을 지원하지만 기법 간에 충돌이 발생할 수 있습니다. 렌더러가 인스턴싱 셰이더를 사용하더라도 정적 배칭(Static batching)이 적용되는 경우 Unity는 자동으로 GPU 인스턴싱을 비활성화하며, 인스펙터(Inspector) 창에 정적 배칭을 끄라는 경고 메시지를 표시합니다 [7]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Unity.md]] +- Raw Source: 00_Raw/2026-04-20/Unity.md --- diff --git a/01_Archive/2026-04-20/Universal-Design-Principles.md b/01_Archive/2026-04-20/Universal-Design-Principles.md index c655002d..9569e048 100644 --- a/01_Archive/2026-04-20/Universal-Design-Principles.md +++ b/01_Archive/2026-04-20/Universal-Design-Principles.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-701DFC -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Universal-Design-Principles" --- -# [[Universal-Design-Principles]] +# [[Universal-Design-Principles|Universal-Design-Principles]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Universal-Design-Principles" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Universal-Design-Principles.md]] +- Raw Source: 00_Raw/2026-04-20/Universal-Design-Principles.md --- diff --git a/01_Archive/2026-04-20/Urban Planning Simulation.md b/01_Archive/2026-04-20/Urban Planning Simulation.md index 3f9a678f..ebf0ca5e 100644 --- a/01_Archive/2026-04-20/Urban Planning Simulation.md +++ b/01_Archive/2026-04-20/Urban Planning Simulation.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-E9E18A -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Urban Planning Simulation" --- -# [[Urban Planning Simulation]] +# [[Urban Planning Simulation|Urban Planning Simulation]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Urban Planning Simulation" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Urban Planning Simulation.md]] +- Raw Source: 00_Raw/2026-04-20/Urban Planning Simulation.md --- diff --git a/01_Archive/2026-04-20/Urban Resilience Strategies.md b/01_Archive/2026-04-20/Urban Resilience Strategies.md index a6ef41ab..0041164d 100644 --- a/01_Archive/2026-04-20/Urban Resilience Strategies.md +++ b/01_Archive/2026-04-20/Urban Resilience Strategies.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-C3A9D0 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Urban Resilience Strategies" --- -# [[Urban Resilience Strategies]] +# [[Urban Resilience Strategies|Urban Resilience Strategies]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Urban Resilience Strategies" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Urban Resilience Strategies.md]] +- Raw Source: 00_Raw/2026-04-20/Urban Resilience Strategies.md --- diff --git a/01_Archive/2026-04-20/Urban-Morphology.md b/01_Archive/2026-04-20/Urban-Morphology.md index 9d0c3d18..ba8acab6 100644 --- a/01_Archive/2026-04-20/Urban-Morphology.md +++ b/01_Archive/2026-04-20/Urban-Morphology.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-27741A -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Urban-Morphology" --- -# [[Urban-Morphology]] +# [[Urban-Morphology|Urban-Morphology]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Urban-Morphology" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Urban-Morphology.md]] +- Raw Source: 00_Raw/2026-04-20/Urban-Morphology.md --- diff --git a/01_Archive/2026-04-20/Urban-Planning-Simulations.md b/01_Archive/2026-04-20/Urban-Planning-Simulations.md index dc07ff82..bb914f78 100644 --- a/01_Archive/2026-04-20/Urban-Planning-Simulations.md +++ b/01_Archive/2026-04-20/Urban-Planning-Simulations.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-F27EBE -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Urban-Planning-Simulations" --- -# [[Urban-Planning-Simulations]] +# [[Urban-Planning-Simulations|Urban-Planning-Simulations]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Urban-Planning-Simulations" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Urban-Planning-Simulations.md]] +- Raw Source: 00_Raw/2026-04-20/Urban-Planning-Simulations.md --- diff --git a/01_Archive/2026-04-20/Urban-Planning.md b/01_Archive/2026-04-20/Urban-Planning.md index 0916ab65..2f443a2b 100644 --- a/01_Archive/2026-04-20/Urban-Planning.md +++ b/01_Archive/2026-04-20/Urban-Planning.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-A67C66 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Urban-Planning" --- -# [[Urban-Planning]] +# [[Urban-Planning|Urban-Planning]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Urban-Planning" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Urban-Planning.md]] +- Raw Source: 00_Raw/2026-04-20/Urban-Planning.md --- diff --git a/01_Archive/2026-04-20/Urban-Resilience-Planning.md b/01_Archive/2026-04-20/Urban-Resilience-Planning.md index e34c8b3e..a2aca5ae 100644 --- a/01_Archive/2026-04-20/Urban-Resilience-Planning.md +++ b/01_Archive/2026-04-20/Urban-Resilience-Planning.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-D2E4D4 -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Urban-Resilience-Planning" --- -# [[Urban-Resilience-Planning]] +# [[Urban-Resilience-Planning|Urban-Resilience-Planning]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Urban-Resilience-Planning" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Urban-Resilience-Planning.md]] +- Raw Source: 00_Raw/2026-04-20/Urban-Resilience-Planning.md --- diff --git a/01_Archive/2026-04-20/User Experience (UX) Design.md b/01_Archive/2026-04-20/User Experience (UX) Design.md index a322a496..6830f090 100644 --- a/01_Archive/2026-04-20/User Experience (UX) Design.md +++ b/01_Archive/2026-04-20/User Experience (UX) Design.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-A613D6 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - User Experience (UX) Design" --- -# [[User Experience (UX) Design]] +# [[User Experience (UX) Design|User Experience (UX) Design]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - User Experience (UX) Design" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/User Experience (UX) Design.md]] +- Raw Source: 00_Raw/2026-04-20/User Experience (UX) Design.md --- diff --git a/01_Archive/2026-04-20/User Experience (UX) in Game Design.md b/01_Archive/2026-04-20/User Experience (UX) in Game Design.md index 6b55c693..591192d4 100644 --- a/01_Archive/2026-04-20/User Experience (UX) in Game Design.md +++ b/01_Archive/2026-04-20/User Experience (UX) in Game Design.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-94EC93 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - User Experience (UX) in Game Design" --- -# [[User Experience (UX) in Game Design]] +# [[User Experience (UX) in Game Design|User Experience (UX) in Game Design]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - User Experience (UX) in Game D ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/User Experience (UX) in Game Design.md]] +- Raw Source: 00_Raw/2026-04-20/User Experience (UX) in Game Design.md --- diff --git a/01_Archive/2026-04-20/User-Experience-Design.md b/01_Archive/2026-04-20/User-Experience-Design.md index dd2b2867..c663b59c 100644 --- a/01_Archive/2026-04-20/User-Experience-Design.md +++ b/01_Archive/2026-04-20/User-Experience-Design.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-41A69F -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - User-Experience-Design" --- -# [[User-Experience-Design]] +# [[User-Experience-Design|User-Experience-Design]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - User-Experience-Design" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/User-Experience-Design.md]] +- Raw Source: 00_Raw/2026-04-20/User-Experience-Design.md --- diff --git a/01_Archive/2026-04-20/User-Story-Mapping.md b/01_Archive/2026-04-20/User-Story-Mapping.md index 90b68f1f..6a46f586 100644 --- a/01_Archive/2026-04-20/User-Story-Mapping.md +++ b/01_Archive/2026-04-20/User-Story-Mapping.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-1AFDC8 -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - User-Story-Mapping" --- -# [[User-Story-Mapping]] +# [[User-Story-Mapping|User-Story-Mapping]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - User-Story-Mapping" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/User-Story-Mapping.md]] +- Raw Source: 00_Raw/2026-04-20/User-Story-Mapping.md --- diff --git a/01_Archive/2026-04-20/Utility Theory.md b/01_Archive/2026-04-20/Utility Theory.md index 2c196da9..dde9dd22 100644 --- a/01_Archive/2026-04-20/Utility Theory.md +++ b/01_Archive/2026-04-20/Utility Theory.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-D4C836 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Utility Theory" --- -# [[Utility Theory]] +# [[Utility Theory|Utility Theory]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Utility Theory" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Utility Theory.md]] +- Raw Source: 00_Raw/2026-04-20/Utility Theory.md --- diff --git a/01_Archive/2026-04-20/Utsubo.md b/01_Archive/2026-04-20/Utsubo.md index aa2b1dd8..70fd1bc4 100644 --- a/01_Archive/2026-04-20/Utsubo.md +++ b/01_Archive/2026-04-20/Utsubo.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-468135 -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Utsubo" --- -# [[Utsubo]] +# [[Utsubo|Utsubo]] ## 📌 한 줄 통찰 (The Karpathy Summary) > Utsubo는 브랜드 웹사이트부터 물리적 설치물에 이르기까지 Three.js 개발을 전문으로 하는 기술 중심의 인터랙티브 크리에이티브 스튜디오이다 [1, 2]. 이들은 2024년 초에 최초의 프로덕션 WebGPU Three.js 환경 중 하나를 구축하여 출시했으며, WebGPU 성능 모니터링을 위한 `stats-gl`과 같은 도구를 개발하는 등 Three.js 생태계 발전에 적극적으로 기여하고 있다 [1]. @@ -27,11 +27,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Utsubo" - **정책 변화:** Graphics & Performance 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Three.js]], [[WebGPU]], [[stats-gl]] -- **Projects/Contexts:** [[Expo 2025 Osaka]], [[Segments.ai]] +- **Related Topics:** [[Three.js|Three.js]], [[WebGPU|WebGPU]], stats-gl +- **Projects/Contexts:** [[Expo 2025 Osaka|Expo 2025 Osaka]], [[Segments.ai|Segments.ai]] - **Contradictions/Notes:** 소스에 관련된 모순 정보나 반대 주장이 부족합니다. (제공된 소스는 모두 Utsubo의 성과와 기술적 기여를 일관되게 긍정적으로 설명하고 있습니다.) --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Utsubo.md]] +- Raw Source: 00_Raw/2026-04-20/Utsubo.md --- diff --git a/01_Archive/2026-04-20/V8 Engine Heap Management.md b/01_Archive/2026-04-20/V8 Engine Heap Management.md index f5b905e8..cdca5756 100644 --- a/01_Archive/2026-04-20/V8 Engine Heap Management.md +++ b/01_Archive/2026-04-20/V8 Engine Heap Management.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-27C7BF -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - V8 Engine Heap Management" --- -# [[V8 Engine Heap Management]] +# [[V8 Engine Heap Management|V8 Engine Heap Management]] ## 📌 한 줄 통찰 (The Karpathy Summary) > V8 엔진의 힙 관리는 자바스크립트 애플리케이션의 동적 데이터를 효율적으로 할당하고 회수하기 위한 자동 메모리 관리 시스템이다 [1, 2]. 이 시스템은 대부분의 객체가 생성 직후 쓸모없어진다는 세대 가설(Generational Hypothesis)을 바탕으로 메모리를 여러 세대와 공간으로 분할하여 관리한다 [3-6]. 최신 V8 엔진은 오리노코(Orinoco) 프로젝트를 통해 병렬(Parallel), 점진적(Incremental), 동시(Concurrent) 가비지 컬렉션 기술을 적용하여 애플리케이션의 멈춤 현상(Stop-the-world)을 크게 줄였다 [7-9]. @@ -34,11 +34,11 @@ github_commit: "[P-Reinforce] Continuous Worker - V8 Engine Heap Management" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Garbage Collection]], [[Generational Hypothesis]], [[Mark-Sweep-Compact]], [[Scavenge]], [[Orinoco]], [[Pointer Compression]] -- **Projects/Contexts:** [[Node.js Memory Tuning]], [[Chrome DevTools Memory Profiling]], [[V8 Memory Cage]] +- **Related Topics:** [[Garbage Collection|Garbage Collection]], [[Generational Hypothesis|Generational Hypothesis]], [[Mark-Sweep-Compact|Mark-Sweep-Compact]], [[Scavenge|Scavenge]], [[Orinoco|Orinoco]], [[Pointer Compression|Pointer Compression]] +- **Projects/Contexts:** [[Node.js Memory Tuning|Node.js Memory Tuning]], [[Chrome DevTools Memory Profiling|Chrome DevTools Memory Profiling]], [[V8 Memory Cage|V8 Memory Cage]] - **Contradictions/Notes:** 자바스크립트는 언어 스펙상 프로그래머가 가비지 컬렉터의 메모리 관리에 직접적으로 개입하거나 제어할 수 없는 것이 원칙이다 [34]. 하지만 Node.js 구동 환경에서는 예외적으로 `--expose-gc` 플래그를 사용하여 프로그램 코드 내부에서 `global.gc()`를 호출해 수동으로 가비지 컬렉션을 강제 실행할 수 있는 우회 방법을 제공한다 [35, 36]. 또한, 전통적으로 힙의 각 페이지(Page) 크기는 1MB로 할당된다고 알려져 있으나 [37], 최근 저사양 기기 최적화 및 단편화 개선을 위해 페이지 크기가 512KB로 축소 적용되는 등 구조적 변화가 일어나고 있다 [38, 39]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/V8 Engine Heap Management.md]] +- Raw Source: 00_Raw/2026-04-20/V8 Engine Heap Management.md --- diff --git a/01_Archive/2026-04-20/V8 Engine.md b/01_Archive/2026-04-20/V8 Engine.md index 283d85d5..767133d3 100644 --- a/01_Archive/2026-04-20/V8 Engine.md +++ b/01_Archive/2026-04-20/V8 Engine.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-7D181E -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - V8 Engine" --- -# [[V8 Engine]] +# [[V8 Engine|V8 Engine]] ## 📌 한 줄 통찰 (The Karpathy Summary) > V8 Engine은 구글이 C++로 개발한 고성능 자바스크립트 및 웹어셈블리 엔진이다 [1]. 이 엔진은 대부분의 객체가 생성 후 곧바로 소멸한다는 '세대 가설(Generational Hypothesis)'에 기반한 정교한 가비지 컬렉션(GC) 시스템을 통해 메모리를 자동으로 관리한다 [2, 3]. 최신 GC 아키텍처인 오리노코(Orinoco)와 V8 메모리 케이지(Memory Cage) 같은 최적화 및 보안 기법을 적극적으로 도입하여, 메모리 효율성과 애플리케이션의 실행 성능, 안전성을 동시에 보장한다 [4, 5]. @@ -35,11 +35,11 @@ github_commit: "[P-Reinforce] Continuous Worker - V8 Engine" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Garbage Collection]], [[Orinoco]], [[Pointer Compression]], [[V8 Memory Cage]] -- **Projects/Contexts:** [[Node.js]], [[Chrome]], [[Electron]] +- **Related Topics:** [[Garbage Collection|Garbage Collection]], [[Orinoco|Orinoco]], [[Pointer Compression|Pointer Compression]], [[V8 Memory Cage|V8 Memory Cage]] +- **Projects/Contexts:** [[Node.js|Node.js]], [[Chrome|Chrome]], [[Electron|Electron]] - **Contradictions/Notes:** 컴팩션(Compaction)은 단편화를 해결하는 데 매우 유용하지만, 살아있는 큰 객체들을 다른 위치로 복사하고 포인터를 모두 업데이트해야 하므로 비용이 매우 비쌉니다. 따라서 Major GC는 Old Space의 모든 페이지를 매번 압축하지 않고 단편화 정도가 심한 페이지에 대해서만 선택적으로 압축을 수행합니다 [18, 41, 42]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/V8 Engine.md]] +- Raw Source: 00_Raw/2026-04-20/V8 Engine.md --- diff --git a/01_Archive/2026-04-20/V8 Heap Architecture.md b/01_Archive/2026-04-20/V8 Heap Architecture.md index 3f76d54f..90060bcd 100644 --- a/01_Archive/2026-04-20/V8 Heap Architecture.md +++ b/01_Archive/2026-04-20/V8 Heap Architecture.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-0C14B5 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - V8 Heap Architecture" --- -# [[V8 Heap Architecture]] +# [[V8 Heap Architecture|V8 Heap Architecture]] ## 📌 한 줄 통찰 (The Karpathy Summary) > V8 엔진의 힙(Heap) 아키텍처는 자바스크립트 런타임에 동적으로 할당되는 데이터와 객체를 저장하기 위해 구조화된 메모리 영역이다 [1]. V8은 메모리 할당 속도를 높이고 가비지 컬렉션(GC)의 오버헤드를 줄이기 위해, 객체의 수명 주기에 기반한 '세대별 가설(Generational Hypothesis)'을 적용하여 힙을 여러 특수 공간(Space)으로 분할한다 [2, 3]. 이를 통해 각기 다른 메모리 영역의 특성에 맞는 최적화된 메모리 회수 알고리즘을 적용할 수 있다 [2]. @@ -37,11 +37,11 @@ V8의 힙은 객체의 특성과 수명에 따라 여러 개의 고유한 공간 - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Garbage Collection]], [[Generational Hypothesis]], [[V8 Memory Cage]], [[Pointer Compression]] -- **Projects/Contexts:** [[Google Chrome]], [[Node.js]], [[Electron]] +- **Related Topics:** [[Garbage Collection|Garbage Collection]], [[Generational Hypothesis|Generational Hypothesis]], [[V8 Memory Cage|V8 Memory Cage]], [[Pointer Compression|Pointer Compression]] +- **Projects/Contexts:** [[Google Chrome|Google Chrome]], [[Node.js|Node.js]], [[Electron|Electron]] - **Contradictions/Notes:** 일반적으로 V8 페이지의 크기는 1MB로 알려져 있으나 [12], 모바일 장치나 데스크탑 환경에서의 메모리 단편화 개선 및 사용량 최적화를 위해 512KB로 축소 적용되기도 하였다 [13, 14]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/V8 Heap Architecture.md]] +- Raw Source: 00_Raw/2026-04-20/V8 Heap Architecture.md --- diff --git a/01_Archive/2026-04-20/V8 JavaScript Engine 메모리 관리 및 가비지 컬렉션.md b/01_Archive/2026-04-20/V8 JavaScript Engine 메모리 관리 및 가비지 컬렉션.md index ede2f90b..f691ec7d 100644 --- a/01_Archive/2026-04-20/V8 JavaScript Engine 메모리 관리 및 가비지 컬렉션.md +++ b/01_Archive/2026-04-20/V8 JavaScript Engine 메모리 관리 및 가비지 컬렉션.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-44DD69 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - V8 JavaScript Engine 메모리 관리 및 가비지 컬렉션" --- -# [[V8 JavaScript Engine 메모리 관리 및 가비지 컬렉션]] +# [[V8 JavaScript Engine 메모리 관리 및 가비지 컬렉션|V8 JavaScript Engine 메모리 관리 및 가비지 컬렉션]] ## 📌 한 줄 통찰 (The Karpathy Summary) > V8 엔진은 동적인 데이터를 관리하기 위해 메모리를 힙(Heap)과 스택(Stack)으로 구분하며, 가비지 컬렉션(GC)을 통해 더 이상 참조되지 않는 메모리를 자동으로 회수한다 [1-3]. V8은 대다수 객체의 수명이 짧다는 '세대적 가설(Generational Hypothesis)'을 기반으로 힙 영역을 여러 세대 공간으로 나누어 관리하고, 각기 다른 GC 알고리즘(Scavenge, Mark-Sweep-Compact 등)을 적용해 성능을 최적화한다 [4-7]. 근래에는 'Orinoco' 프로젝트를 통해 메인 스레드의 실행을 멈추는 'Stop-the-world' 현상을 최소화하기 위해 병렬(Parallel), 점진적(Incremental), 동시(Concurrent) 방식의 GC 기법을 도입하여 애플리케이션의 지연 시간(Latency)을 크게 개선했다 [6, 8, 9]. @@ -20,11 +20,11 @@ github_commit: "[P-Reinforce] Continuous Worker - V8 JavaScript Engine 메모리 - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** `[[Garbage Collection]]`, `[[Cheney's Algorithm]]`, `[[Mark-Sweep-Compact]]`, `[[Orinoco GC]]`, `[[Pointer Compression]]`, `[[Generational Hypothesis]]` -- **Projects/Contexts:** `[[Node.js Memory Management]]`, `[[Chrome V8 Heap Analysis]]`, `[[Electron V8 Memory Cage]]` +- **Related Topics:** `[[Garbage Collection|Garbage Collection]]`, `[[Cheney's Algorithm|Cheney's Algorithm]]`, `[[Mark-Sweep-Compact|Mark-Sweep-Compact]]`, `[[Orinoco GC|Orinoco GC]]`, `[[Pointer Compression|Pointer Compression]]`, `[[Generational Hypothesis|Generational Hypothesis]]` +- **Projects/Contexts:** `[[Node.js Memory Management|Node.js Memory Management]]`, `[[Chrome V8 Heap Analysis|Chrome V8 Heap Analysis]]`, `[[Electron V8 Memory Cage|Electron V8 Memory Cage]]` - **Contradictions/Notes:** Minor GC(Scavenger)에서 살아남은 객체를 지속적으로 다른 메모리 공간으로 복사(Evacuate/Copy)하는 방식은 얼핏 보기에 비용이 매우 큰 작업처럼 보인다. 그러나 '대다수의 객체가 곧바로 죽는다'는 세대적 가설(Generational Hypothesis) 덕분에 실제로 복사되는 객체는 아주 소수에 불과하며, 오히려 살아남은 것들만 모아주어 나머지 공간 전체를 즉시 재사용할 수 있게 하므로 전체적인 할당 속도와 단편화 관리에 훨씬 유리하다 [5, 14, 50]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/V8 JavaScript Engine 메모리 관리 및 가비지 컬렉션.md]] +- Raw Source: 00_Raw/2026-04-20/V8 JavaScript Engine 메모리 관리 및 가비지 컬렉션.md --- diff --git a/01_Archive/2026-04-20/V8 JavaScript Engine.md b/01_Archive/2026-04-20/V8 JavaScript Engine.md index 74ebf2e0..a8944c62 100644 --- a/01_Archive/2026-04-20/V8 JavaScript Engine.md +++ b/01_Archive/2026-04-20/V8 JavaScript Engine.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-E8BF09 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - V8 JavaScript Engine" --- -# [[V8 JavaScript Engine]] +# [[V8 JavaScript Engine|V8 JavaScript Engine]] ## 📌 한 줄 통찰 (The Karpathy Summary) > V8 JavaScript Engine은 자바스크립트를 해석하고 네이티브 기계어로 컴파일하는 고성능 자바스크립트 및 WebAssembly 엔진이다 [1]. 애플리케이션 실행 시 스택(Stack)과 힙(Heap)으로 구분되는 '레지던트 세트(Resident Set)' 메모리 구조를 기반으로 작동한다 [2, 3]. 특히 세대별 가설(Generational Hypothesis)을 적용한 고급 가비지 컬렉션(GC) 시스템과 최신 동시성 처리 기법을 활용하여 성능 저하 없이 효율적이고 안전하게 메모리를 관리하는 것이 특징이다 [4-6]. @@ -28,11 +28,11 @@ V8 JavaScript Engine은 성능과 메모리 효율을 극대화하기 위해 복 - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Garbage Collection]], [[Resident Set]], [[Orinoco Project]], [[Memory Cage]], [[Pointer Compression]] -- **Projects/Contexts:** [[Node.js]], [[Google Chrome]], [[Electron]] +- **Related Topics:** [[Garbage Collection|Garbage Collection]], Resident Set, Orinoco Project, Memory Cage, [[Pointer Compression|Pointer Compression]] +- **Projects/Contexts:** [[Node.js|Node.js]], [[Google Chrome|Google Chrome]], [[Electron|Electron]] - **Contradictions/Notes:** 가비지 컬렉터를 통해 V8 엔진이 메모리를 자동으로 관리하여 편리함을 제공하지만, 자바스크립트(ECMAScript) 사양 자체는 개발자가 가비지 컬렉터를 직접 측정하거나 제어할 수 있는 공식적인 인터페이스를 제공하지 않는다는 한계가 존재한다 [41]. 또한 수명이 짧은 객체를 다루는 Minor GC는 객체를 새 공간으로 '복사(Copy)'하여 할당 속도를 높이는 방식을 취하지만, 수명이 긴 객체가 모인 Major GC 영역에서는 복사 비용이 비효율적이므로 주로 'Mark-Sweep'을 수행하고 예외적인 상황에서만 압축(Compact)을 진행하는 전략적 차이를 보인다 [14, 20, 21]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/V8 JavaScript Engine.md]] +- Raw Source: 00_Raw/2026-04-20/V8 JavaScript Engine.md --- diff --git a/01_Archive/2026-04-20/V8 JavaScript 엔진.md b/01_Archive/2026-04-20/V8 JavaScript 엔진.md index ffe91caf..fcfc65b5 100644 --- a/01_Archive/2026-04-20/V8 JavaScript 엔진.md +++ b/01_Archive/2026-04-20/V8 JavaScript 엔진.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-383B09 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - V8 JavaScript 엔진" --- -# [[V8 JavaScript 엔진]] +# [[V8 JavaScript 엔진|V8 JavaScript 엔진]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -36,11 +36,11 @@ V8은 객체와 포인터를 빠르게 식별하기 위해 단어의 마지막 - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Garbage Collection]], [[Orinoco]], [[Pointer Compression]], [[V8 Memory Cage]], [[Scavenger]], [[Generational Hypothesis]] -- **Projects/Contexts:** [[Node.js]], [[Chrome]], [[Electron]] +- **Related Topics:** [[Garbage Collection|Garbage Collection]], [[Orinoco|Orinoco]], [[Pointer Compression|Pointer Compression]], [[V8 Memory Cage|V8 Memory Cage]], [[Scavenger 알고리즘|Scavenger]], [[Generational Hypothesis|Generational Hypothesis]] +- **Projects/Contexts:** [[Node.js|Node.js]], [[Chrome|Chrome]], [[Electron|Electron]] - **Contradictions/Notes:** 모바일 같은 저메모리 디바이스에서는 V8이 가비지 컬렉션의 지연 시간이나 처리량보다는 메모리 소비를 줄이기 위해 GC를 더 자주 실행하도록 휴리스틱을 엄격하게 조정합니다. 이로 인해 메모리는 절약되지만 GC 비용(빈도)이 증가하는 트레이드오프가 존재합니다 [39, 40]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/V8 JavaScript 엔진.md]] +- Raw Source: 00_Raw/2026-04-20/V8 JavaScript 엔진.md --- diff --git a/01_Archive/2026-04-20/V8 Memory Cage.md b/01_Archive/2026-04-20/V8 Memory Cage.md index ddf70d8d..31d91c41 100644 --- a/01_Archive/2026-04-20/V8 Memory Cage.md +++ b/01_Archive/2026-04-20/V8 Memory Cage.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-BEAD76 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - V8 Memory Cage" --- -# [[V8 Memory Cage]] +# [[V8 Memory Cage|V8 Memory Cage]] ## 📌 한 줄 통찰 (The Karpathy Summary) > V8 Memory Cage(또는 V8 Sandbox)는 V8 JavaScript 엔진의 힙 객체들을 제한된 연속 메모리 영역(일반적으로 4GB) 내에 격리하는 보안 및 최적화 아키텍처입니다 [1, 2]. 이 구조는 메모리 내에 실제 포인터 대신 기준 주소로부터의 오프셋(offset)을 저장하여, 공격자가 취약점을 이용해 프로세스의 임의 메모리를 읽고 쓰는 것을 방지합니다 [3]. 포인터 압축을 통해 메모리 사용량을 줄이고 성능을 향상시키지만, 힙 외부(off-heap) 메모리를 직접 참조하는 ArrayBuffer 생성이 제한된다는 단점이 있습니다 [4, 5]. @@ -20,11 +20,11 @@ github_commit: "[P-Reinforce] Continuous Worker - V8 Memory Cage" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Pointer Compression]], [[ArrayBuffer]], [[Type Confusion]], [[V8 Heap]] -- **Projects/Contexts:** [[Electron 21+]], [[Chromium 103+]], [[Node.js Native Modules]] +- **Related Topics:** [[Pointer Compression|Pointer Compression]], [[ArrayBuffer|ArrayBuffer]], Type Confusion, [[V8 힙(Heap)|V8 Heap]] +- **Projects/Contexts:** Electron 21+, Chromium 103+, Node.js Native Modules - **Contradictions/Notes:** V8 메모리 케이지는 보안과 전반적인 성능 측면에서 이점이 크지만, V8 힙 용량이 4GB로 제한된다는 분명한 단점이 있습니다 [4, 5]. 대용량 메모리가 필수적인 앱의 경우 자식 프로세스로 워크로드를 분리하거나 포인터 압축이 비활성화된 사용자 지정 빌드를 사용해야 하는 워크어라운드가 필요합니다 [11]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/V8 Memory Cage.md]] +- Raw Source: 00_Raw/2026-04-20/V8 Memory Cage.md --- diff --git a/01_Archive/2026-04-20/V8 가비지 컬렉션(Garbage Collection).md b/01_Archive/2026-04-20/V8 가비지 컬렉션(Garbage Collection).md index eb765eda..cc05a82a 100644 --- a/01_Archive/2026-04-20/V8 가비지 컬렉션(Garbage Collection).md +++ b/01_Archive/2026-04-20/V8 가비지 컬렉션(Garbage Collection).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-488812 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - V8 가비지 컬렉션(Garbage Collection)" --- -# [[V8 가비지 컬렉션(Garbage Collection)]] +# [[V8 가비지 컬렉션(Garbage Collection)|V8 가비지 컬렉션(Garbage Collection)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > V8 가비지 컬렉션은 애플리케이션의 메모리를 자동으로 관리하기 위해 더 이상 사용되지 않는 죽은 메모리 영역을 식별하고 운영체제로 반환하거나 재사용하는 프로세스입니다 [1]. 가비지 컬렉터는 루트(Root) 객체에서 시작하는 포인터 체인을 통해 도달할 수 없는 객체를 죽은 객체(가비지)로 간주하여 처리합니다 [1, 2]. V8은 대다수의 객체가 일찍 죽는다는 특성을 활용하여 힙 메모리를 세대별로 분할하고, 각 공간에 최적화된 마이너 GC(Minor GC)와 메이저 GC(Major GC)를 수행합니다 [3, 4]. @@ -39,11 +39,11 @@ V8은 힙을 객체의 생존 기간 및 용도에 따라 여러 공간으로 - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[세대별 가설(Generational Hypothesis)]], [[마크-스위프-컴팩트(Mark-Sweep-Compact)]], [[마이너 GC(Scavenge)]], [[Orinoco 가비지 컬렉터]] -- **Projects/Contexts:** [[Node.js]], [[Chrome V8 엔진]], [[Orinoco 프로젝트]] +- **Related Topics:** [[세대별 가설(Generational Hypothesis)|세대별 가설(Generational Hypothesis)]], [[마크-스위프-컴팩트(Mark-Sweep-Compact)|마크-스위프-컴팩트(Mark-Sweep-Compact)]], 마이너 GC(Scavenge), [[Orinoco 가비지 컬렉터|Orinoco 가비지 컬렉터]] +- **Projects/Contexts:** [[Node.js|Node.js]], Chrome V8 엔진, [[Orinoco 프로젝트|Orinoco 프로젝트]] - **Contradictions/Notes:** 소스에 따르면 과거의 Scavenge 알고리즘은 동기식(Synchronous)인 체니(Cheney) 알고리즘을 구현하였으나, Chrome과 Node.js가 구동되는 현대의 멀티코어 환경에 발맞추어 현재의 V8은 다중 스레드를 활용해 동적으로 작업을 분배하는 병렬(Parallel) Scavenger로 진화했습니다 [28, 29]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/V8 가비지 컬렉션(Garbage Collection).md]] +- Raw Source: 00_Raw/2026-04-20/V8 가비지 컬렉션(Garbage Collection).md --- diff --git a/01_Archive/2026-04-20/V8 메모리 케이지(V8 Memory Cage).md b/01_Archive/2026-04-20/V8 메모리 케이지(V8 Memory Cage).md index fad6c869..83d720c6 100644 --- a/01_Archive/2026-04-20/V8 메모리 케이지(V8 Memory Cage).md +++ b/01_Archive/2026-04-20/V8 메모리 케이지(V8 Memory Cage).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-F23E51 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - V8 메모리 케이지(V8 Memory Cage)" --- -# [[V8 메모리 케이지(V8 Memory Cage)]] +# [[V8 메모리 케이지(V8 Memory Cage)|V8 메모리 케이지(V8 Memory Cage)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > V8 메모리 케이지(V8 Memory Cage)는 V8 힙 내부에 메모리 포인터를 직접 저장하지 않고, 예약된 특정 영역의 시작점을 기준으로 한 오프셋(Offset)만을 저장하여 메모리를 격리하는 보안 기술입니다 [1]. 이 기술은 JIT 엔진의 타입 혼동 버그 등을 악용하여 공격자가 V8 힙 영역을 벗어난 프로세스 메모리를 임의로 읽고 쓰는 것을 원천적으로 차단하기 위해 고안되었습니다 [1, 2]. 64비트 플랫폼에서 포인터 압축(Pointer Compression) 기술과 결합하여 작동하며, 모든 V8 힙 객체를 4GB 크기의 연속된 '케이지(Cage)' 영역 내에 강제로 제한합니다 [3]. @@ -26,11 +26,11 @@ github_commit: "[P-Reinforce] Continuous Worker - V8 메모리 케이지(V8 Memo - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[포인터 압축(Pointer Compression)]], [[ArrayBuffer]], [[가비지 컬렉션(Garbage Collection)]] -- **Projects/Contexts:** [[Electron]], [[Chromium]], [[Node.js Native Modules]] +- **Related Topics:** [[포인터 압축(Pointer Compression)|포인터 압축(Pointer Compression)]], [[ArrayBuffer|ArrayBuffer]], [[가비지 컬렉션(Garbage Collection)|가비지 컬렉션(Garbage Collection)]] +- **Projects/Contexts:** [[Electron|Electron]], [[Chromium|Chromium]], Node.js Native Modules - **Contradictions/Notes:** 소스 문헌들은 메모리 케이지 및 포인터 압축이 성능(CPU 및 GC)을 5%~10% 향상시키고 보안을 강화한다고 설명하지만, 이로 인해 외부 메모리 버퍼를 지원하지 않아 네이티브 모듈에서 호환성 문제가 생기고 힙 크기가 4GB로 제한되는 명확한 트레이드오프(Trade-off)가 있음을 함께 강조합니다 [5, 10]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/V8 메모리 케이지(V8 Memory Cage).md]] +- Raw Source: 00_Raw/2026-04-20/V8 메모리 케이지(V8 Memory Cage).md --- diff --git a/01_Archive/2026-04-20/V8 엔진 (V8 Engine).md b/01_Archive/2026-04-20/V8 엔진 (V8 Engine).md index ba37598d..7a1cf980 100644 --- a/01_Archive/2026-04-20/V8 엔진 (V8 Engine).md +++ b/01_Archive/2026-04-20/V8 엔진 (V8 Engine).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-D6DB20 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - V8 엔진 (V8 Engine)" --- -# [[V8 엔진 (V8 Engine)]] +# [[V8 엔진 (V8 Engine)|V8 엔진 (V8 Engine)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -35,11 +35,11 @@ V8의 메모리 관리는 "대부분의 객체는 생성된 직후 금방 죽는 - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** `[[Orinoco GC]]`, `[[Generational Hypothesis]]`, `[[Mark-Sweep-Compact]]`, `[[V8 Memory Cage]]` -- **Projects/Contexts:** `[[Node.js]]`, `[[Google Chrome]]`, `[[Electron]]`, `[[WebAssembly]]` +- **Related Topics:** `[[Orinoco GC|Orinoco GC]]`, `[[Generational Hypothesis|Generational Hypothesis]]`, `[[Mark-Sweep-Compact|Mark-Sweep-Compact]]`, `[[V8 Memory Cage|V8 Memory Cage]]` +- **Projects/Contexts:** `[[Node.js|Node.js]]`, `[[Google Chrome|Google Chrome]]`, `[[Electron|Electron]]`, `[[WebAssembly|WebAssembly]]` - **Contradictions/Notes:** V8에 도입된 포인터 압축 기술(Pointer Compression)은 V8 힙 메모리 크기를 최대 40% 감소시키고 CPU 및 GC 성능을 5~10% 향상시키는 장점이 있지만, 그로 인해 V8 힙 크기가 최대 4GB로 제한된다는 단점 또한 명확히 존재합니다 [38, 45]. 추가로, V8 환경에서 프로그래머가 직접 가비지 컬렉션(GC)을 통제하거나 개입하는 것은 불가능하게 설계되어 있으나(`ECMAScript` 사양에 GC 제어 인터페이스가 없음), `--expose-gc`와 같은 특수 커맨드라인 플래그나 크롬 브라우저의 'Idle-time GC' 메커니즘을 이용하면 외부(Embedder)에서 유휴 시간을 이용해 수동으로 GC를 유도하는 것은 가능합니다 [46-48]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/V8 엔진 (V8 Engine).md]] +- Raw Source: 00_Raw/2026-04-20/V8 엔진 (V8 Engine).md --- diff --git a/01_Archive/2026-04-20/V8 엔진 메모리 구조.md b/01_Archive/2026-04-20/V8 엔진 메모리 구조.md index bd6193cc..849775f3 100644 --- a/01_Archive/2026-04-20/V8 엔진 메모리 구조.md +++ b/01_Archive/2026-04-20/V8 엔진 메모리 구조.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-3C3331 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - V8 엔진 메모리 구조" --- -# [[V8 엔진 메모리 구조]] +# [[V8 엔진 메모리 구조|V8 엔진 메모리 구조]] ## 📌 한 줄 통찰 (The Karpathy Summary) > V8 엔진의 메모리 구조는 실행 중인 프로그램에 할당되는 상주 집합(Resident Set)을 기반으로 하며, 크게 정적 데이터를 다루는 스택(Stack) 영역과 동적 데이터를 관리하는 힙(Heap) 영역으로 나뉜다 [1, 2]. 힙 메모리는 가비지 컬렉터(GC)가 객체의 생명주기와 특성에 맞춰 효율적으로 메모리를 회수할 수 있도록 세대별 가설(Generational hypothesis)에 기반하여 여러 공간(Space)으로 세분화된다 [3-5]. 최신 아키텍처에서는 메모리 단편화 방지와 보안 강화를 위해 오프힙 존(Zone) 메모리 활용, 512KB로 축소된 페이지(Page) 단위 관리, 그리고 4GB 제한을 가지는 포인터 압축(Pointer Compression) 및 메모리 케이지(Memory Cage) 기술이 적용되어 있다 [4, 6-8]. @@ -20,11 +20,11 @@ github_commit: "[P-Reinforce] Continuous Worker - V8 엔진 메모리 구조" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[가비지 컬렉터(Garbage Collection)]], [[포인터 압축(Pointer Compression)]], [[세대별 가설(Generational Hypothesis)]] -- **Projects/Contexts:** [[Node.js 및 웹 브라우저 런타임 최적화]], [[V8 보안 및 샌드박싱 모델(Memory Cage)]] +- **Related Topics:** 가비지 컬렉터(Garbage Collection), [[포인터 압축(Pointer Compression)|포인터 압축(Pointer Compression)]], [[세대별 가설(Generational Hypothesis)|세대별 가설(Generational Hypothesis)]] +- **Projects/Contexts:** Node.js 및 웹 브라우저 런타임 최적화, V8 보안 및 샌드박싱 모델(Memory Cage) - **Contradictions/Notes:** 소스에 관련 정보가 부족합니다. (특별한 모순점은 없으나, V8의 힙 페이지 크기가 기기와 버전에 따라 1MB에서 512KB로 유동적으로 최적화되었다는 변화 기록만 존재합니다 [4, 24, 25].) --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/V8 엔진 메모리 구조.md]] +- Raw Source: 00_Raw/2026-04-20/V8 엔진 메모리 구조.md --- diff --git a/01_Archive/2026-04-20/V8 엔진 힙 아키텍처 및 로그 분석.md b/01_Archive/2026-04-20/V8 엔진 힙 아키텍처 및 로그 분석.md index b7b86736..e571878d 100644 --- a/01_Archive/2026-04-20/V8 엔진 힙 아키텍처 및 로그 분석.md +++ b/01_Archive/2026-04-20/V8 엔진 힙 아키텍처 및 로그 분석.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-18F9C4 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - V8 엔진 힙 아키텍처 및 로그 분석" --- -# [[V8 엔진 힙 아키텍처 및 로그 분석]] +# [[V8 엔진 힙 아키텍처 및 로그 분석|V8 엔진 힙 아키텍처 및 로그 분석]] ## 📌 한 줄 통찰 (The Karpathy Summary) > V8 엔진 힙 아키텍처는 효율적인 메모리 할당과 빠른 가비지 컬렉션(GC)을 위해 물리적 메모리를 세대와 용도별 여러 공간으로 세분화하여 관리하는 구조입니다. 이 시스템은 대부분의 객체가 짧은 시간 안에 소멸한다는 '세대 가설(Generational hypothesis)'을 바탕으로 설계되어 젊은 세대와 오래된 세대에 각각 다른 알고리즘을 적용합니다. 런타임 로그 분석은 `--trace-gc` 등의 플래그를 활용해 메모리 할당 실패 원인, 수집에 소요된 시간, 힙의 생존 객체 크기 변화를 추적함으로써 메모리 누수와 성능 병목을 진단하는 핵심 기술입니다. @@ -35,11 +35,11 @@ github_commit: "[P-Reinforce] Continuous Worker - V8 엔진 힙 아키텍처 및 - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[세대 가설(Generational Hypothesis)]], [[Scavenger(마이너 GC)]], [[Mark-Sweep-Compact(메이저 GC)]], [[오리노코(Orinoco) 프로젝트]], [[포인터 압축(Pointer Compression)]] -- **Projects/Contexts:** [[Node.js 프로덕션 메모리 누수 진단]], [[Chrome 렌더러 프로세스 V8 샌드박스 보안]] +- **Related Topics:** [[세대 가설(Generational Hypothesis)|세대 가설(Generational Hypothesis)]], [[Scavenger(마이너 GC)|Scavenger(마이너 GC)]], [[Mark-Sweep-Compact(메이저 GC)|Mark-Sweep-Compact(메이저 GC)]], [[오리노코(Orinoco) 프로젝트|오리노코(Orinoco) 프로젝트]], [[포인터 압축(Pointer Compression)|포인터 압축(Pointer Compression)]] +- **Projects/Contexts:** [[Node.js 프로덕션 메모리 누수 진단|Node.js 프로덕션 메모리 누수 진단]], [[Chrome 렌더러 프로세스 V8 샌드박스 보안|Chrome 렌더러 프로세스 V8 샌드박스 보안]] - **Contradictions/Notes:** 소스 [37-56]에서는 gencon, balanced 등 IBM Eclipse OpenJ9의 GC 정책에 대한 내용을 깊이 다루고 있으나, 이는 V8 엔진 고유의 구조가 아니므로 본 V8 아키텍처 중심 분석에서는 배제하였습니다. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/V8 엔진 힙 아키텍처 및 로그 분석.md]] +- Raw Source: 00_Raw/2026-04-20/V8 엔진 힙 아키텍처 및 로그 분석.md --- diff --git a/01_Archive/2026-04-20/V8 엔진 힙 아키텍처(V8 Engine Heap Architecture).md b/01_Archive/2026-04-20/V8 엔진 힙 아키텍처(V8 Engine Heap Architecture).md index 85712998..976cf444 100644 --- a/01_Archive/2026-04-20/V8 엔진 힙 아키텍처(V8 Engine Heap Architecture).md +++ b/01_Archive/2026-04-20/V8 엔진 힙 아키텍처(V8 Engine Heap Architecture).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-FEC38C -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - V8 엔진 힙 아키텍처(V8 Engine Heap Architecture)" --- -# [[V8 엔진 힙 아키텍처(V8 Engine Heap Architecture)]] +# [[V8 엔진 힙 아키텍처(V8 Engine Heap Architecture)|V8 엔진 힙 아키텍처(V8 Engine Heap Architecture)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > V8 엔진의 힙 아키텍처는 동적 데이터와 런타임에 크기 및 수명이 결정되는 객체들을 저장하고 관리하는 메모리 영역입니다 [1, 2]. V8은 대부분의 객체가 일찍 죽는다는 '세대적 가설(Generational Hypothesis)'을 바탕으로 힙을 여러 세대와 특수한 목적의 공간(Space)으로 분할하여 관리합니다 [3-5]. 이를 통해 할당 속도를 극대화하고 가비지 컬렉션(GC)의 오버헤드 및 지연 시간을 줄여 효율적인 메모리 회수와 프로그램 실행 성능을 보장합니다 [4, 6]. @@ -20,11 +20,11 @@ github_commit: "[P-Reinforce] Continuous Worker - V8 엔진 힙 아키텍처(V8 - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Generational Hypothesis]], [[Garbage Collection (Minor GC / Major GC)]], [[V8 Memory Cage]], [[Pointer Compression]] -- **Projects/Contexts:** [[Node.js]], [[Chrome Browser]], [[Electron]], [[Deno]] +- **Related Topics:** [[Generational Hypothesis|Generational Hypothesis]], Garbage Collection (Minor GC / Major GC), [[V8 Memory Cage|V8 Memory Cage]], [[Pointer Compression|Pointer Compression]] +- **Projects/Contexts:** [[Node.js|Node.js]], Chrome Browser, [[Electron|Electron]], Deno - **Contradictions/Notes:** V8 힙의 페이지 크기는 전통적으로 1MB로 설명되지만, 소스에 따르면 저메모리 기기의 메모리 최적화와 메모리 파편화를 줄이기 위해 512KB로 크기가 축소되는 최적화가 적용되었습니다 [4, 17, 19, 20]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/V8 엔진 힙 아키텍처(V8 Engine Heap Architecture).md]] +- Raw Source: 00_Raw/2026-04-20/V8 엔진 힙 아키텍처(V8 Engine Heap Architecture).md --- diff --git a/01_Archive/2026-04-20/V8 엔진 힙 아키텍처.md b/01_Archive/2026-04-20/V8 엔진 힙 아키텍처.md index 3ac524dc..11f16e8e 100644 --- a/01_Archive/2026-04-20/V8 엔진 힙 아키텍처.md +++ b/01_Archive/2026-04-20/V8 엔진 힙 아키텍처.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-221751 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - V8 엔진 힙 아키텍처" --- -# [[V8 엔진 힙 아키텍처]] +# [[V8 엔진 힙 아키텍처|V8 엔진 힙 아키텍처]] ## 📌 한 줄 통찰 (The Karpathy Summary) > V8 엔진의 힙 아키텍처는 런타임 시 크기나 수명을 미리 알 수 없는 동적 데이터와 자바스크립트 객체들을 저장하고 관리하기 위해 구성된 메모리 구조입니다 [1-3]. 효율적인 가비지 컬렉션을 위해 대부분의 객체가 생성 직후 죽는다는 '세대적 가설(Generational Hypothesis)'을 기반으로 설계되었습니다 [4-6]. 이를 위해 힙은 객체의 수명과 특성에 따라 여러 개의 특수 공간(Space)으로 나뉘며, 각 공간은 페이지(Pages) 단위로 나뉘어 메모리 할당 및 회수에 최적화된 고유의 방식으로 관리됩니다 [7-10]. @@ -37,11 +37,11 @@ github_commit: "[P-Reinforce] Continuous Worker - V8 엔진 힙 아키텍처" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[가비지 컬렉션(Garbage Collection)]], [[세대적 가설(Generational Hypothesis)]], [[스캐빈저(Scavenger)]], [[Mark-Sweep-Compact]], [[포인터 압축(Pointer Compression)]] -- **Projects/Contexts:** [[Node.js 성능 최적화]], [[Google Chrome 브라우저 메모리 관리]], [[Orinoco 가비지 컬렉터]] +- **Related Topics:** [[가비지 컬렉션(Garbage Collection)|가비지 컬렉션(Garbage Collection)]], 세대적 가설(Generational Hypothesis), [[스캐빈저(Scavenger)|스캐빈저(Scavenger)]], [[Mark-Sweep-Compact|Mark-Sweep-Compact]], [[포인터 압축(Pointer Compression)|포인터 압축(Pointer Compression)]] +- **Projects/Contexts:** Node.js 성능 최적화, Google Chrome 브라우저 메모리 관리, [[Orinoco 가비지 컬렉터|Orinoco 가비지 컬렉터]] - **Contradictions/Notes:** V8은 일반적으로 1MB 단위의 페이지 크기를 사용해 왔으나, 최신 최적화 동향에 따라 메모리 단편화를 줄이고 병렬 압축(Compaction) 효율을 높이기 위해 페이지 크기를 512KB로 축소 조정하는 방식을 병행하여 사용합니다 [5, 8, 18]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/V8 엔진 힙 아키텍처.md]] +- Raw Source: 00_Raw/2026-04-20/V8 엔진 힙 아키텍처.md --- diff --git a/01_Archive/2026-04-20/V8 엔진(V8 Engine).md b/01_Archive/2026-04-20/V8 엔진(V8 Engine).md index 9143aca6..8bb3116b 100644 --- a/01_Archive/2026-04-20/V8 엔진(V8 Engine).md +++ b/01_Archive/2026-04-20/V8 엔진(V8 Engine).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-F107AC -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - V8 엔진(V8 Engine)" --- -# [[V8 엔진(V8 Engine)]] +# [[V8 엔진(V8 Engine)|V8 엔진(V8 Engine)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -25,11 +25,11 @@ github_commit: "[P-Reinforce] Continuous Worker - V8 엔진(V8 Engine)" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Garbage Collection (GC)]], [[Orinoco]], [[Generational Hypothesis]], [[Pointer Compression]], [[Heap Space]] -- **Projects/Contexts:** [[Google Chrome]], [[Node.js]], [[Electron]], [[Deno]] +- **Related Topics:** [[Garbage Collection (GC)|Garbage Collection (GC)]], [[Orinoco|Orinoco]], [[Generational Hypothesis|Generational Hypothesis]], [[Pointer Compression|Pointer Compression]], Heap Space +- **Projects/Contexts:** [[Google Chrome|Google Chrome]], [[Node.js|Node.js]], [[Electron|Electron]], Deno - **Contradictions/Notes:** 과거의 V8 스캐빈저(Scavenger)는 단일 스레드 기반의 Cheney 알고리즘을 사용했으나, 최신 버전에서는 멀티코어 환경에 맞춰 Halstead 방식과 유사한 동적 작업 훔치기(Work stealing) 기반의 병렬 스캐빈저를 도입하여 성능을 개선한 변화가 존재합니다 [35, 36]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/V8 엔진(V8 Engine).md]] +- Raw Source: 00_Raw/2026-04-20/V8 엔진(V8 Engine).md --- diff --git a/01_Archive/2026-04-20/V8 엔진의 메모리 관리 아키텍처 및 Orinoco 프로젝트.md b/01_Archive/2026-04-20/V8 엔진의 메모리 관리 아키텍처 및 Orinoco 프로젝트.md index bc3973c3..d6b57149 100644 --- a/01_Archive/2026-04-20/V8 엔진의 메모리 관리 아키텍처 및 Orinoco 프로젝트.md +++ b/01_Archive/2026-04-20/V8 엔진의 메모리 관리 아키텍처 및 Orinoco 프로젝트.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-C4468D -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - V8 엔진의 메모리 관리 아키텍처 및 Orinoco 프로젝트" --- -# [[V8 엔진의 메모리 관리 아키텍처 및 Orinoco 프로젝트]] +# [[V8 엔진의 메모리 관리 아키텍처 및 Orinoco 프로젝트|V8 엔진의 메모리 관리 아키텍처 및 Orinoco 프로젝트]] ## 📌 한 줄 통찰 (The Karpathy Summary) > V8 엔진의 메모리 관리 아키텍처는 객체의 예상 수명에 따라 메모리 공간을 분할하는 세대별 힙(Generational Heap) 모델을 기반으로 설계되었습니다. 이를 통해 수명이 짧은 객체와 긴 객체에 각각 다른 알고리즘을 적용하여 가비지 컬렉션(GC)의 효율성을 극대화합니다. Orinoco 프로젝트는 V8의 가비지 컬렉터를 혁신하기 위한 이니셔티브로, 기존의 순차적이고 메인 스레드를 멈추게 하던(Stop-the-world) 방식에서 벗어나 병렬(Parallel), 동시성(Concurrent), 점진적(Incremental) 기법을 도입함으로써 애플리케이션의 응답성과 처리량을 크게 향상시켰습니다. @@ -37,11 +37,11 @@ Orinoco는 메인 스레드의 멈춤 시간(Pause time)을 줄이기 위해 최 - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[가비지 컬렉션(Garbage Collection)]], [[세대별 가설(Generational Hypothesis)]], [[포인터 압축(Pointer Compression)]], [[Mark-Sweep-Compact 알고리즘]], [[Scavenger 알고리즘]] -- **Projects/Contexts:** [[V8 JavaScript 엔진]], [[Node.js 메모리 최적화]], [[Chrome 브라우저 렌더링 성능]] +- **Related Topics:** [[가비지 컬렉션(Garbage Collection)|가비지 컬렉션(Garbage Collection)]], [[세대별 가설(Generational Hypothesis)|세대별 가설(Generational Hypothesis)]], [[포인터 압축(Pointer Compression)|포인터 압축(Pointer Compression)]], [[Mark-Sweep-Compact 알고리즘|Mark-Sweep-Compact 알고리즘]], [[Scavenger 알고리즘|Scavenger 알고리즘]] +- **Projects/Contexts:** [[V8 JavaScript 엔진|V8 JavaScript 엔진]], [[Node.js 메모리 최적화|Node.js 메모리 최적화]], [[Chrome 브라우저 렌더링 성능|Chrome 브라우저 렌더링 성능]] - **Contradictions/Notes:** 과거 버전의 V8에서는 단일 스레드 기반의 동기식 Cheney 알고리즘을 Scavenger에 사용했으나, 멀티 코어 환경이 보편화됨에 따라 Orinoco 프로젝트를 기점으로 동적 작업 훔치기(Dynamic work stealing) 방식을 활용하는 병렬 스캐빈저(Parallel Scavenger)로 진화했습니다 [30, 40]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/V8 엔진의 메모리 관리 아키텍처 및 Orinoco 프로젝트.md]] +- Raw Source: 00_Raw/2026-04-20/V8 엔진의 메모리 관리 아키텍처 및 Orinoco 프로젝트.md --- diff --git a/01_Archive/2026-04-20/V8 자바스크립트 엔진.md b/01_Archive/2026-04-20/V8 자바스크립트 엔진.md index 68af32cf..01f202fe 100644 --- a/01_Archive/2026-04-20/V8 자바스크립트 엔진.md +++ b/01_Archive/2026-04-20/V8 자바스크립트 엔진.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-4AC7A0 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - V8 자바스크립트 엔진" --- -# [[V8 자바스크립트 엔진]] +# [[V8 자바스크립트 엔진|V8 자바스크립트 엔진]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -36,11 +36,11 @@ V8은 객체 대부분이 일찍 죽는다는 '세대별 가설(Generational hyp - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[가비지 컬렉션(Garbage Collection)]], [[Orinoco 가비지 컬렉터]], [[세대별 가설(Generational Hypothesis)]], [[포인터 압축(Pointer Compression)]], [[V8 메모리 케이지(Memory Cage)]] +- **Related Topics:** [[가비지 컬렉션(Garbage Collection)|가비지 컬렉션(Garbage Collection)]], [[Orinoco 가비지 컬렉터|Orinoco 가비지 컬렉터]], [[세대별 가설(Generational Hypothesis)|세대별 가설(Generational Hypothesis)]], [[포인터 압축(Pointer Compression)|포인터 압축(Pointer Compression)]], V8 메모리 케이지(Memory Cage) - **Projects/Contexts:** Node.js, Deno, Electron, Chrome 브라우저 등에서 핵심 자바스크립트 및 WebAssembly 실행 환경으로 채택되어 사용됩니다 [31, 36-39]. 애플리케이션의 메모리 누수 분석 및 성능 모니터링 시 V8의 `--trace-gc`, `--heap-prof` 등 다양한 런타임 플래그와 크롬 개발자 도구의 힙 스냅샷 기능을 주로 활용합니다 [40-43]. - **Contradictions/Notes:** 자바스크립트는 언어 스펙상 가비지 컬렉터에 대해 프로그래머가 직접 제어할 수 있는 인터페이스를 제공하지 않는 것이 원칙이나 [44], Node.js 환경에서 구동되는 V8은 예외적으로 `--max-old-space-size` 및 `--expose-gc` (코드 내에서 `global.gc()` 호출 지원) 등의 커맨드라인 플래그를 통해 개발자가 직접 힙 크기를 튜닝하고 수동으로 컬렉션을 유도할 수 있도록 허용합니다 [45-47]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/V8 자바스크립트 엔진.md]] +- Raw Source: 00_Raw/2026-04-20/V8 자바스크립트 엔진.md --- diff --git a/01_Archive/2026-04-20/V8 힙 공간(V8 Heap Spaces).md b/01_Archive/2026-04-20/V8 힙 공간(V8 Heap Spaces).md index 0a1a0b00..8fd0f226 100644 --- a/01_Archive/2026-04-20/V8 힙 공간(V8 Heap Spaces).md +++ b/01_Archive/2026-04-20/V8 힙 공간(V8 Heap Spaces).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-438240 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - V8 힙 공간(V8 Heap Spaces)" --- -# [[V8 힙 공간(V8 Heap Spaces)]] +# [[V8 힙 공간(V8 Heap Spaces)|V8 힙 공간(V8 Heap Spaces)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > V8 엔진은 동적으로 할당되는 데이터와 객체를 저장하기 위해 힙(Heap) 메모리를 사용하며, 효율적인 메모리 관리를 위해 이를 여러 개의 특화된 공간(Space)으로 나눕니다 [1, 2]. 객체의 예상 수명과 크기, 내부 포인터의 유무에 따라 신규 공간(New Space), 올드 공간(Old Space), 대형 객체 공간(Large Object Space) 등으로 분리됩니다 [2-4]. 이러한 공간 분할은 가비지 컬렉터(GC)가 각 메모리 영역의 특성에 맞는 최적화된 수집 알고리즘을 적용할 수 있게 하여 애플리케이션의 성능을 향상시킵니다 [2]. 또한 최신 V8에서는 보안과 성능을 위해 포인터 압축 기술을 사용하여 전체 힙 공간을 4GB 크기의 메모리 케이지(Memory Cage) 내에 제한합니다 [5, 6]. @@ -44,11 +44,11 @@ V8 힙은 각기 다른 생명주기를 가진 객체를 관리하기 위해 여 - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[가비지 컬렉션(Garbage Collection)]], [[스캐빈저(Scavenger)]], [[마크-스위프-컴팩트(Mark-Sweep-Compact)]] -- **Projects/Contexts:** [[Orinoco 프로젝트]], [[V8 메모리 케이지(V8 Memory Cage)]] +- **Related Topics:** [[가비지 컬렉션(Garbage Collection)|가비지 컬렉션(Garbage Collection)]], [[스캐빈저(Scavenger)|스캐빈저(Scavenger)]], [[마크-스위프-컴팩트(Mark-Sweep-Compact)|마크-스위프-컴팩트(Mark-Sweep-Compact)]] +- **Projects/Contexts:** [[Orinoco 프로젝트|Orinoco 프로젝트]], [[V8 메모리 케이지(V8 Memory Cage)|V8 메모리 케이지(V8 Memory Cage)]] - **Contradictions/Notes:** 전통적으로 V8 힙을 구성하는 단위인 각 '페이지(Page)'의 크기는 1MB였으나, 최근 저사양 모바일 기기를 위한 메모리 절감 및 파편화 감소 최적화의 일환으로 512KB 크기의 페이지로 축소 변경되기도 하였습니다 [7, 8, 19, 20]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/V8 힙 공간(V8 Heap Spaces).md]] +- Raw Source: 00_Raw/2026-04-20/V8 힙 공간(V8 Heap Spaces).md --- diff --git a/01_Archive/2026-04-20/V8 힙(Heap).md b/01_Archive/2026-04-20/V8 힙(Heap).md index e5b30dba..b7505dd9 100644 --- a/01_Archive/2026-04-20/V8 힙(Heap).md +++ b/01_Archive/2026-04-20/V8 힙(Heap).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-326FC1 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - V8 힙(Heap)" --- -# [[V8 힙(Heap)]] +# [[V8 힙(Heap)|V8 힙(Heap)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > V8 힙(Heap)은 자바스크립트 프로그램 실행 시 동적 데이터와 컴파일 타임에 크기나 수명 등을 결정할 수 없는 객체들이 저장되는 메모리 영역입니다 [1, 2]. 이 메모리 공간은 수동으로 관리할 필요 없이 V8 엔진의 가비지 컬렉터(Garbage Collector)에 의해 자동으로 재활용됩니다 [3, 4]. 효율적인 메모리 관리를 위해 V8은 객체의 예상 수명에 따라 힙을 '새로운 세대(Young Generation)'와 '오래된 세대(Old Generation)' 등 여러 특수한 공간(Space)으로 나누어 구성합니다 [5-7]. @@ -35,11 +35,11 @@ V8 엔진은 "대부분의 객체는 일찍 죽는다"는 세대 가설(Generati - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[가비지 컬렉션(Garbage Collection)]], [[세대 가설(Generational Hypothesis)]], [[포인터 압축(Pointer Compression)]], [[Scavenger(Minor GC)]], [[Mark-Sweep-Compact(Major GC)]] -- **Projects/Contexts:** [[Node.js]], [[Google Chrome]], [[Orinoco(V8 GC 프로젝트)]] +- **Related Topics:** [[가비지 컬렉션(Garbage Collection)|가비지 컬렉션(Garbage Collection)]], [[세대 가설(Generational Hypothesis)|세대 가설(Generational Hypothesis)]], [[포인터 압축(Pointer Compression)|포인터 압축(Pointer Compression)]], [[Scavenger(Minor GC)|Scavenger(Minor GC)]], Mark-Sweep-Compact(Major GC) +- **Projects/Contexts:** [[Node.js|Node.js]], [[Google Chrome|Google Chrome]], [[Orinoco(V8 GC 프로젝트)|Orinoco(V8 GC 프로젝트)]] - **Contradictions/Notes:** 소스 간의 본질적 모순은 없으나, V8 엔진의 지속적인 진화로 인해 페이지 크기가 1MB에서 512KB로 변경되는 등 시간의 흐름과 메모리 한계에 따른 구조 최적화 변화가 소스에 혼재되어 나타납니다. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/V8 힙(Heap).md]] +- Raw Source: 00_Raw/2026-04-20/V8 힙(Heap).md --- diff --git a/01_Archive/2026-04-20/VIA Institute on Character.md b/01_Archive/2026-04-20/VIA Institute on Character.md index c4749b5c..c95fd216 100644 --- a/01_Archive/2026-04-20/VIA Institute on Character.md +++ b/01_Archive/2026-04-20/VIA Institute on Character.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-4C752E -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - VIA Institute on Character" --- -# [[VIA Institute on Character]] +# [[VIA Institute on Character|VIA Institute on Character]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - VIA Institute on Character" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/VIA Institute on Character.md]] +- Raw Source: 00_Raw/2026-04-20/VIA Institute on Character.md --- diff --git a/01_Archive/2026-04-20/VIA-Classification.md b/01_Archive/2026-04-20/VIA-Classification.md index 30808914..9e27f8f7 100644 --- a/01_Archive/2026-04-20/VIA-Classification.md +++ b/01_Archive/2026-04-20/VIA-Classification.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-19F48C -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - VIA-Classification" --- -# [[VIA-Classification]] +# [[VIA-Classification|VIA-Classification]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - VIA-Classification" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/VIA-Classification.md]] +- Raw Source: 00_Raw/2026-04-20/VIA-Classification.md --- diff --git a/01_Archive/2026-04-20/VPS_NeRF.md b/01_Archive/2026-04-20/VPS_NeRF.md index ac6d1276..5c930cbc 100644 --- a/01_Archive/2026-04-20/VPS_NeRF.md +++ b/01_Archive/2026-04-20/VPS_NeRF.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-GRAPHICS-005 -category: "[[10_Wiki/💡 Topics/Graphics]]" +category: "10_Wiki/💡 Topics/Graphics" confidence_score: 0.94 tags: [graphics, nerf, vps, navigation] last_reinforced: 2026-04-20 github_commit: "batch-reinforce-05" --- -# [[VPS & NeRF (Visual Positioning System)]] +# VPS & NeRF (Visual Positioning System) ## 📌 한 줄 통찰 (The Karpathy Summary) > 이미지 기반의 정밀 위치 측정 기술과 신경망 기반 공간 재구성을 결합하여 현실 세계를 완벽한 디지털 좌표계로 변환하다. @@ -24,6 +24,6 @@ github_commit: "batch-reinforce-05" - **정책 변화:** 기술적 가중치(w1)를 높게 설정하여 메타버스 카테고리의 핵심 브리지 지식으로 배치. ## 🔗 지식 연결 (Graph) -- **Parent:** [[10_Wiki/💡 Topics/Graphics]] -- **Related:** [[CV_Synthesis]], [[3D_Gaussian_Splatting]], [[SLAM]] -- **Raw Source:** [[00_Raw/2026-04-20/Visual Positioning Systems (VPS).md]] +- **Parent:** 10_Wiki/💡 Topics/Graphics +- **Related:** [[CV_Synthesis|CV_Synthesis]], [[3D_Gaussian_Splatting|3D_Gaussian_Splatting]], SLAM +- **Raw Source:** 00_Raw/2026-04-20/Visual Positioning Systems (VPS).md diff --git a/01_Archive/2026-04-20/VR Sickness.md b/01_Archive/2026-04-20/VR Sickness.md index 69aecec8..11ff356e 100644 --- a/01_Archive/2026-04-20/VR Sickness.md +++ b/01_Archive/2026-04-20/VR Sickness.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-7B9E16 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - VR Sickness" --- -# [[VR Sickness]] +# [[VR Sickness|VR Sickness]] ## 📌 한 줄 통찰 (The Karpathy Summary) > VR 멀미(VR Sickness, 또는 모션 병, 사이버 멀미)는 헤드마운트 디스플레이(HMD)를 비롯한 가상현실 기기를 사용할 때 발생하는 메스꺼움, 방향 감각 상실, 시각적 장애 등의 부작용을 의미합니다 [1], [2]. 이는 주로 시각적 경험과 신체적 전정 감각 간의 충돌로 인해 발생하며 [3], 사용자의 실재감(Presence)을 저해하고 작업 수행 능력과 즐거움을 크게 감소시키는 주요 요인입니다 [2]. @@ -23,11 +23,11 @@ github_commit: "[P-Reinforce] Continuous Worker - VR Sickness" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Visual-Vestibular Conflict]], [[Vergence-Accommodation Conflict]], [[Presence]], [[Head-Mounted Displays (HMD)]] -- **Projects/Contexts:** [[VR Exergaming]] (예: Beat Saber를 활용한 VR 노출 시간 및 후유증 연구 [13], [14]) +- **Related Topics:** [[시각-전정 갈등 (Visual-Vestibular Conflict)|Visual-Vestibular Conflict]], [[수렴-조절 불일치(Vergence-Accommodation Conflict)|Vergence-Accommodation Conflict]], [[몰입감 (Presence)|Presence]], Head-Mounted Displays (HMD) +- **Projects/Contexts:** VR Exergaming (예: Beat Saber를 활용한 VR 노출 시간 및 후유증 연구 [13], [14]) - **Contradictions/Notes:** 일반적으로 VR 노출 시간이 길어질수록 증상이 심해진다고 알려져 있으나, 한 연구 검토에서는 10~20분 노출된 경우보다 20분 이상 노출된 연구에서 평균적으로 덜 심각한 증상이 보고되기도 했습니다. 이는 노출 시간 자체의 문제라기보다는 각 연구에 사용된 VR 콘텐츠의 유형(예: 360도 비디오, 게임, 정적 풍경 등) 분포 차이로 인한 결과일 수 있습니다 [10]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/VR Sickness.md]] +- Raw Source: 00_Raw/2026-04-20/VR Sickness.md --- diff --git a/01_Archive/2026-04-20/VR 멀미 (VR Sickness).md b/01_Archive/2026-04-20/VR 멀미 (VR Sickness).md index a828899e..1a45be07 100644 --- a/01_Archive/2026-04-20/VR 멀미 (VR Sickness).md +++ b/01_Archive/2026-04-20/VR 멀미 (VR Sickness).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-BD2336 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - VR 멀미 (VR Sickness)" --- -# [[VR 멀미 (VR Sickness)]] +# [[VR 멀미 (VR Sickness)|VR 멀미 (VR Sickness)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > VR 멀미(VR Sickness 또는 Cybersickness)는 헤드마운트 디스플레이(HMD)를 사용하는 가상현실(VR) 경험 중 다수의 사용자가 겪는 부정적인 상태로, 메스꺼움, 방향 감각 상실, 시각적 장애 등의 증상을 동반합니다 [1, 2]. 이러한 멀미 증상은 가상현실에서의 몰입감(presence), 동기 부여, 즐거움 및 과제 수행 능력을 저하시키며, 결과적으로 평균 15.6%의 높은 중도 포기율(dropout rate)을 초래하는 주요 원인이 됩니다 [2]. @@ -25,11 +25,11 @@ github_commit: "[P-Reinforce] Continuous Worker - VR 멀미 (VR Sickness)" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[시각-전정 갈등 (Visual-Vestibular Conflict)]], [[폭주-조절 갈등 (Vergence-Accommodation Conflict)]], [[몰입감 (Presence)]], [[헤드마운트 디스플레이 (HMD)]] -- **Projects/Contexts:** [[VR 엑서게임 (VR Exergaming)]] +- **Related Topics:** [[시각-전정 갈등 (Visual-Vestibular Conflict)|시각-전정 갈등 (Visual-Vestibular Conflict)]], [[폭주-조절 갈등 (Vergence-Accommodation Conflict)|폭주-조절 갈등 (Vergence-Accommodation Conflict)]], [[몰입감 (Presence)|몰입감 (Presence)]], [[헤드마운트 디스플레이 (HMD)|헤드마운트 디스플레이 (HMD)]] +- **Projects/Contexts:** [[VR 엑서게임 (VR Exergaming)|VR 엑서게임 (VR Exergaming)]] - **Contradictions/Notes:** VR 멀미의 정확한 발병 원인(etiology)에 대해서는 학계 내에서 여전히 일치된 합의가 없습니다 [3, 4]. 덧붙여, VR 엑서게임 환경에서는 멀미 증상이 격렬한 신체 운동으로 인해 유발되는 자연스러운 신체 반응과 중복되기 때문에 정확한 멀미를 식별해 내는 것이 까다로울 수 있습니다 [6]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/VR 멀미 (VR Sickness).md]] +- Raw Source: 00_Raw/2026-04-20/VR 멀미 (VR Sickness).md --- diff --git a/01_Archive/2026-04-20/VR 멀미(VR sickness).md b/01_Archive/2026-04-20/VR 멀미(VR sickness).md index 1064d43f..4c1baa21 100644 --- a/01_Archive/2026-04-20/VR 멀미(VR sickness).md +++ b/01_Archive/2026-04-20/VR 멀미(VR sickness).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-926D42 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - VR 멀미(VR sickness)" --- -# [[VR 멀미(VR sickness)]] +# [[VR 멀미(VR sickness)|VR 멀미(VR sickness)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > VR 멀미(VR sickness)는 헤드 마운트 디스플레이(HMD) 사용 시 발생하는 부정적인 부작용으로, 주로 메스꺼움, 방향 감각 상실, 안구 피로 및 시각적 장애와 같은 증상으로 나타납니다 [1, 2]. 가상 세계의 시각적 경험과 실제 신체의 감각이 일치하지 않을 때 발생하는 시각-전정 감각의 충돌(visual-vestibular conflict)이 주요 원인으로 지목됩니다 [3]. 이러한 멀미 증상은 사용자의 몰입감(presence)을 떨어뜨리고, 게임이나 작업의 동기 부여와 즐거움을 감소시키며, 종국에는 수행 능력을 저하시키는 원인이 됩니다 [2]. @@ -32,11 +32,11 @@ github_commit: "[P-Reinforce] Continuous Worker - VR 멀미(VR sickness)" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[시각-전정 감각 충돌(Visual-Vestibular Conflict)]], [[폭주-조절 불일치(Vergence-Accommodation Conflict)]], [[시뮬레이터 멀미 설문지(SSQ)]], [[몰입감(Presence)]] -- **Projects/Contexts:** [[비트 세이버(Beat Saber) 엑서게이밍 연구]] (10분 및 50분의 VR 노출이 사용자의 시각, 인지 및 자기 보고된 멀미 후유증에 미치는 영향을 조사한 연구 [14, 15]). +- **Related Topics:** [[시각-전정 감각 충돌(Visual-Vestibular Conflict)|시각-전정 감각 충돌(Visual-Vestibular Conflict)]], [[폭주-조절 불일치(Vergence-accommodation conflict)|폭주-조절 불일치(Vergence-Accommodation Conflict)]], [[시뮬레이터 멀미 설문지(SSQ)|시뮬레이터 멀미 설문지(SSQ)]], [[몰입감 (Presence)|몰입감(Presence)]] +- **Projects/Contexts:** 비트 세이버(Beat Saber) 엑서게이밍 연구 (10분 및 50분의 VR 노출이 사용자의 시각, 인지 및 자기 보고된 멀미 후유증에 미치는 영향을 조사한 연구 [14, 15]). - **Contradictions/Notes:** 고강도 신체 활동을 동반하는 VR 엑서게임(Exergame)을 수행할 경우, 피로, 방향 감각 상실, 땀 흘림, 메스꺼움 등 격렬한 유산소 운동으로 인한 생리적 증상과 VR 멀미 증상이 겹치게 됩니다. 이로 인해 운동 중 순수한 VR 멀미 증상만을 명확히 구분해 내는 데에는 어려움이 따릅니다 [16]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/VR 멀미(VR sickness).md]] +- Raw Source: 00_Raw/2026-04-20/VR 멀미(VR sickness).md --- diff --git a/01_Archive/2026-04-20/VR 엑서게임 (VR Exergaming).md b/01_Archive/2026-04-20/VR 엑서게임 (VR Exergaming).md index 2840eb88..838938f6 100644 --- a/01_Archive/2026-04-20/VR 엑서게임 (VR Exergaming).md +++ b/01_Archive/2026-04-20/VR 엑서게임 (VR Exergaming).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-E1E503 -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - VR 엑서게임 (VR Exergaming)" --- -# [[VR 엑서게임 (VR Exergaming)]] +# [[VR 엑서게임 (VR Exergaming)|VR 엑서게임 (VR Exergaming)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > VR 엑서게임(VR Exergaming)은 운동(Exercise)과 게임 플레이(Gameplay)를 3D 가상 환경에 결합하여 신체 활동을 촉진하고 사람들의 좌식 생활 습관을 개선하는 활동을 말합니다 [1, 2]. 사용자에게 360도 공간과 신체 추적 기능을 제공하여 높은 몰입감을 유도하며, 이를 통해 운동에 수반되는 육체적 피로를 잊게 만들고 지속적인 참여 동기를 부여합니다 [2]. 대표적인 예시로 '비트 세이버(Beat Saber)'가 있으며, 실제 테니스와 맞먹는 에너지를 소모할 정도로 신체적, 심리적 이점을 모두 제공하는 도구로 주목받고 있습니다 [3]. @@ -23,11 +23,11 @@ github_commit: "[P-Reinforce] Continuous Worker - VR 엑서게임 (VR Exergaming - **정책 변화:** Graphics & Performance 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Flow State]], [[VR 멀미 (VR Sickness)]] -- **Projects/Contexts:** [[Beat Saber]] +- **Related Topics:** [[Flow State|Flow State]], [[VR 멀미 (VR Sickness)|VR 멀미 (VR Sickness)]] +- **Projects/Contexts:** [[Beat Saber|Beat Saber]] - **Contradictions/Notes:** 평균적인 그룹 데이터로는 VR 엑서게임 종료 40분 후 멀미 증상이 모두 회복되는 것으로 나타나지만, 개별 데이터에 따르면 50분 플레이 후 약 14%의 사용자는 40분 뒤에도 여전히 높은 수준의 멀미를 겪고 있어 심각한 개인차가 존재함을 알 수 있습니다 [12]. 또한, 문헌에 따라 VR 노출이 사용자의 반응 시간(Reaction time)에 미치는 영향이 긍정적이라는 연구와 부정적이라는 연구가 혼재되어 있습니다 [13]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/VR 엑서게임 (VR Exergaming).md]] +- Raw Source: 00_Raw/2026-04-20/VR 엑서게임 (VR Exergaming).md --- diff --git a/01_Archive/2026-04-20/Value Object Pattern.md b/01_Archive/2026-04-20/Value Object Pattern.md index 8a9ba032..800665df 100644 --- a/01_Archive/2026-04-20/Value Object Pattern.md +++ b/01_Archive/2026-04-20/Value Object Pattern.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-314692 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Value Object Pattern" --- -# [[Value Object Pattern]] +# [[Value Object Pattern|Value Object Pattern]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Value Object Pattern" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Value Object Pattern.md]] +- Raw Source: 00_Raw/2026-04-20/Value Object Pattern.md --- diff --git a/01_Archive/2026-04-20/Value-Objects.md b/01_Archive/2026-04-20/Value-Objects.md index 86709d91..4b523675 100644 --- a/01_Archive/2026-04-20/Value-Objects.md +++ b/01_Archive/2026-04-20/Value-Objects.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-038FBF -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Value-Objects" --- -# [[Value-Objects]] +# [[Value-Objects|Value-Objects]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Value-Objects" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Value-Objects.md]] +- Raw Source: 00_Raw/2026-04-20/Value-Objects.md --- diff --git a/01_Archive/2026-04-20/Variable Ratio Reinforcement.md b/01_Archive/2026-04-20/Variable Ratio Reinforcement.md index bfbc6e82..5d52ac92 100644 --- a/01_Archive/2026-04-20/Variable Ratio Reinforcement.md +++ b/01_Archive/2026-04-20/Variable Ratio Reinforcement.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-1B19EF -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Variable Ratio Reinforcement" --- -# [[Variable Ratio Reinforcement]] +# [[Variable Ratio Reinforcement|Variable Ratio Reinforcement]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Variable Ratio Reinforcement" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Variable Ratio Reinforcement.md]] +- Raw Source: 00_Raw/2026-04-20/Variable Ratio Reinforcement.md --- diff --git a/01_Archive/2026-04-20/Variance (Covariance Contravariance Invariance).md b/01_Archive/2026-04-20/Variance (Covariance Contravariance Invariance).md index a600cb20..5df9223e 100644 --- a/01_Archive/2026-04-20/Variance (Covariance Contravariance Invariance).md +++ b/01_Archive/2026-04-20/Variance (Covariance Contravariance Invariance).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-372429 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Variance (Covariance Contravariance Invariance)" --- -# [[Variance (Covariance Contravariance Invariance)]] +# [[Variance (Covariance Contravariance Invariance)|Variance (Covariance Contravariance Invariance)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Variance (Covariance Contravar ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Variance (Covariance, Contravariance, Invariance).md]] +- Raw Source: 00_Raw/2026-04-20/Variance (Covariance, Contravariance, Invariance).md --- diff --git a/01_Archive/2026-04-20/Variance (Covariance, Contravariance, Invariance).md b/01_Archive/2026-04-20/Variance (Covariance, Contravariance, Invariance).md index dcc6a4ee..2c4870c7 100644 --- a/01_Archive/2026-04-20/Variance (Covariance, Contravariance, Invariance).md +++ b/01_Archive/2026-04-20/Variance (Covariance, Contravariance, Invariance).md @@ -1,4 +1,4 @@ -[[Variance (Covariance, Contravariance, Invariance)]] +[[Variance (Covariance, Contravariance, Invariance)|Variance (Covariance, Contravariance, Invariance)]] 📌 Brief Summary Variance describes how the subtyping relationship between complex types (such as functions or generics) relates to the subtyping relationship of their component types. In TypeScript's type system, understanding variance is critical for designing safe interfaces, as it determines whether a subtype can be substituted for a supertype without violating type safety. @@ -21,8 +21,8 @@ In the context of TypeScript interface design, variance defines the rules for "s When designing interfaces, developers must decide the variance of generic parameters. Using `in` (contravariant) and `out` (covariant) annotations (though primarily a feature of languages like C# or Scala, the logic applies to how TypeScript infers compatibility) allows for more flexible and reusable API designs. 🔗 Knowledge Connections -* Related Topics: [[Liskov Substitution Principle]], [[Function Type Compatibility]] -* Projects/Contexts: [[TypeScript Structural Type System]] +* Related Topics: [[Liskov-Substitution-Principle|Liskov Substitution Principle]], Function Type Compatibility +* Projects/Contexts: TypeScript Structural Type System * Contradictions/Notes: Note that TypeScript's type system is "structural," meaning variance is determined by the shape of the object rather than explicit declarations, which can sometimes lead to unexpected compatibility in complex nested generics. Last updated: 2026-04-17 \ No newline at end of file diff --git a/01_Archive/2026-04-20/Variance-(Covariance-Contravariance-Invariance).md b/01_Archive/2026-04-20/Variance-(Covariance-Contravariance-Invariance).md index 818208fa..f1d2b0a7 100644 --- a/01_Archive/2026-04-20/Variance-(Covariance-Contravariance-Invariance).md +++ b/01_Archive/2026-04-20/Variance-(Covariance-Contravariance-Invariance).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-84D6F1 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Variance-(Covariance-Contravariance-Invariance)" --- -# [[Variance-(Covariance-Contravariance-Invariance)]] +# [[Variance-(Covariance-Contravariance-Invariance)|Variance-(Covariance-Contravariance-Invariance)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Variance-(Covariance-Contravar ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Variance-(Covariance-Contravariance-Invariance).md]] +- Raw Source: 00_Raw/2026-04-20/Variance-(Covariance-Contravariance-Invariance).md --- diff --git a/01_Archive/2026-04-20/Variance-Covariance-Contravariance.md b/01_Archive/2026-04-20/Variance-Covariance-Contravariance.md index a17ca64c..40a1bc43 100644 --- a/01_Archive/2026-04-20/Variance-Covariance-Contravariance.md +++ b/01_Archive/2026-04-20/Variance-Covariance-Contravariance.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-429958 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Variance-Covariance-Contravariance" --- -# [[Variance-Covariance-Contravariance]] +# [[Variance-Covariance-Contravariance|Variance-Covariance-Contravariance]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Variance-Covariance-Contravari ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Variance-Covariance-Contravariance.md]] +- Raw Source: 00_Raw/2026-04-20/Variance-Covariance-Contravariance.md --- diff --git a/01_Archive/2026-04-20/Variance-Covariance-and-Contravariance.md b/01_Archive/2026-04-20/Variance-Covariance-and-Contravariance.md index ceda6bf8..a0cbd0de 100644 --- a/01_Archive/2026-04-20/Variance-Covariance-and-Contravariance.md +++ b/01_Archive/2026-04-20/Variance-Covariance-and-Contravariance.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-B7957E -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Variance-Covariance-and-Contravariance" --- -# [[Variance-Covariance-and-Contravariance]] +# [[Variance-Covariance-and-Contravariance|Variance-Covariance-and-Contravariance]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Variance-Covariance-and-Contra ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Variance-Covariance-and-Contravariance.md]] +- Raw Source: 00_Raw/2026-04-20/Variance-Covariance-and-Contravariance.md --- diff --git a/01_Archive/2026-04-20/Variance-Rules.md b/01_Archive/2026-04-20/Variance-Rules.md index 10886599..2c62c56b 100644 --- a/01_Archive/2026-04-20/Variance-Rules.md +++ b/01_Archive/2026-04-20/Variance-Rules.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-85151B -category: "[[10_Wiki/💡 Topics/General Knowledge]]" +category: "10_Wiki/💡 Topics/General Knowledge" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Variance-Rules" --- -# [[Variance-Rules]] +# [[Variance-Rules|Variance-Rules]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Variance-Rules" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Variance-Rules.md]] +- Raw Source: 00_Raw/2026-04-20/Variance-Rules.md --- diff --git a/01_Archive/2026-04-20/Variance-in-TypeScript.md b/01_Archive/2026-04-20/Variance-in-TypeScript.md index e788c008..4e28160c 100644 --- a/01_Archive/2026-04-20/Variance-in-TypeScript.md +++ b/01_Archive/2026-04-20/Variance-in-TypeScript.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-E0D3BE -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Variance-in-TypeScript" --- -# [[Variance-in-TypeScript]] +# [[Variance-in-TypeScript|Variance-in-TypeScript]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Variance-in-TypeScript" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Variance-in-TypeScript.md]] +- Raw Source: 00_Raw/2026-04-20/Variance-in-TypeScript.md --- diff --git a/01_Archive/2026-04-20/Variational-Autoencoders.md b/01_Archive/2026-04-20/Variational-Autoencoders.md index aea9d8dd..81eac063 100644 --- a/01_Archive/2026-04-20/Variational-Autoencoders.md +++ b/01_Archive/2026-04-20/Variational-Autoencoders.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-92A652 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Variational-Autoencoders" --- -# [[Variational-Autoencoders]] +# [[Variational-Autoencoders|Variational-Autoencoders]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Variational-Autoencoders" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Variational-Autoencoders.md]] +- Raw Source: 00_Raw/2026-04-20/Variational-Autoencoders.md --- diff --git a/01_Archive/2026-04-20/Varying Variables.md b/01_Archive/2026-04-20/Varying Variables.md index 2d525a55..660641ec 100644 --- a/01_Archive/2026-04-20/Varying Variables.md +++ b/01_Archive/2026-04-20/Varying Variables.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-9ED1C2 -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Varying Variables" --- -# [[Varying Variables]] +# [[Varying Variables|Varying Variables]] ## 📌 한 줄 통찰 (The Karpathy Summary) > Varying Variables(베어링 변수)는 3D 그래픽 파이프라인에서 버텍스 셰이더(vertex shaders)와 프래그먼트 셰이더(fragment shaders) 간에 데이터를 전송하는 역할을 하는 변수입니다 [1]. 모바일 기기에서의 렌더링 성능을 위해 사용량을 최소화해야 하는 셰이더 최적화 대상 중 하나입니다 [1]. @@ -23,11 +23,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Varying Variables" - **정책 변화:** Graphics & Performance 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Vertex Shader]], [[Fragment Shader]], [[Mobile GPU]] -- **Projects/Contexts:** [[Three.js Performance Optimization]] (Shaders & Materials 최적화 팁) +- **Related Topics:** [[Vertex Shader|Vertex Shader]], Fragment Shader, Mobile GPU +- **Projects/Contexts:** Three.js Performance Optimization (Shaders & Materials 최적화 팁) - **Contradictions/Notes:** 소스에 관련 정보가 부족합니다. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Varying Variables.md]] +- Raw Source: 00_Raw/2026-04-20/Varying Variables.md --- diff --git a/01_Archive/2026-04-20/Vergence-Accommodation Conflicts.md b/01_Archive/2026-04-20/Vergence-Accommodation Conflicts.md index bd4b19f1..c3675a83 100644 --- a/01_Archive/2026-04-20/Vergence-Accommodation Conflicts.md +++ b/01_Archive/2026-04-20/Vergence-Accommodation Conflicts.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-122E42 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Vergence-Accommodation Conflicts" --- -# [[Vergence-Accommodation Conflicts]] +# [[Vergence-Accommodation Conflicts|Vergence-Accommodation Conflicts]] ## 📌 한 줄 통찰 (The Karpathy Summary) > Vergence-Accommodation Conflicts(양안 폭주-초점 조절 불일치)는 주로 헤드마운트 디스플레이(HMD) 사용 시 발생하는 현상으로, 자연스러운 시각 환경에서 피드백 루프를 통해 함께 작동하는 안구 운동 기능인 '양안 폭주(Vergence)'와 '초점 조절(Accommodation)'이 서로 분리될 때 발생합니다 [1, 2]. 이 충돌은 깊이 지각을 위한 망막 단서에 불확실성을 초래하여 두통, 눈의 통증, 피로, 복시 등의 안구 운동 증상을 유발할 수 있습니다 [1, 2]. 이러한 불일치가 가상현실(VR) 멀미를 유발하는 직접적인 원인인지, 아니면 단순히 멀미 증상을 악화시키는 요인인지는 아직 명확하게 밝혀지지 않았습니다 [3]. @@ -23,11 +23,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Vergence-Accommodation Conflic - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Oculomotor Functions]], [[Head-Mounted Displays (HMDs)]], [[VR Sickness]], [[Depth Perception]] -- **Projects/Contexts:** [[Virtual Reality (VR) Exergaming]] +- **Related Topics:** [[안구 운동 기능 (Oculomotor Functions)|Oculomotor Functions]], Head-Mounted Displays (HMDs), [[VR Sickness|VR Sickness]], [[깊이 지각 (Depth Perception)|Depth Perception]] +- **Projects/Contexts:** Virtual Reality (VR) Exergaming - **Contradictions/Notes:** 소스에 따르면 Vergence-Accommodation Conflicts가 특정 사용자에게서 나타나는 VR 멀미(VR sickness)의 직접적인 발병 원인인지, 혹은 멀미 증상을 악화시키는 보조 요인인지에 대한 인과관계는 아직 명확하지 않다고 언급되어 있습니다 [3]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Vergence-Accommodation Conflicts.md]] +- Raw Source: 00_Raw/2026-04-20/Vergence-Accommodation Conflicts.md --- diff --git a/01_Archive/2026-04-20/Vertex Shader.md b/01_Archive/2026-04-20/Vertex Shader.md index 91a294b6..a1c68add 100644 --- a/01_Archive/2026-04-20/Vertex Shader.md +++ b/01_Archive/2026-04-20/Vertex Shader.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-E201D0 -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Vertex Shader" --- -# [[Vertex Shader]] +# [[Vertex Shader|Vertex Shader]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 버텍스 셰이더(Vertex Shader)는 렌더링 파이프라인에서 정점(Vertex)의 연산을 처리하는 셰이더 단계입니다 [1, 2]. 주로 인스턴스화된 메쉬(Instanced Mesh) 기반의 애니메이션을 처리하거나, 메쉬 데이터의 복제 없이 무작위 축척 및 회전 등을 절차적으로 변형하는 데 사용됩니다 [3, 4]. 계산된 데이터는 Varying 변수를 통해 프래그먼트 셰이더(Fragment Shader)로 전달됩니다 [1]. @@ -22,11 +22,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Vertex Shader" - **정책 변화:** Graphics & Performance 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Fragment Shader]], [[Instancing]], [[Varying Variables]] -- **Projects/Contexts:** [[대규모 인스턴스 렌더링 최적화]], [[모바일 GPU 셰이더 성능 관리]] +- **Related Topics:** Fragment Shader, [[Instancing|Instancing]], [[Varying Variables|Varying Variables]] +- **Projects/Contexts:** 대규모 인스턴스 렌더링 최적화, 모바일 GPU 셰이더 성능 관리 - **Contradictions/Notes:** 소스에 관련 정보가 부족합니다. (버텍스 셰이더 자체의 구체적인 내부 문법이나 근본적인 그래픽스 파이프라인 원리에 대한 상세한 설명은 제공된 소스에 포함되어 있지 않습니다.) --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Vertex Shader.md]] +- Raw Source: 00_Raw/2026-04-20/Vertex Shader.md --- diff --git a/01_Archive/2026-04-20/Video Game Design.md b/01_Archive/2026-04-20/Video Game Design.md index abcdb1d6..f0851ff9 100644 --- a/01_Archive/2026-04-20/Video Game Design.md +++ b/01_Archive/2026-04-20/Video Game Design.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-FE3DA6 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Video Game Design" --- -# [[Video Game Design]] +# [[Video Game Design|Video Game Design]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Video Game Design" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Video Game Design.md]] +- Raw Source: 00_Raw/2026-04-20/Video Game Design.md --- diff --git a/01_Archive/2026-04-20/Virtual Reality (VR) Storytelling.md b/01_Archive/2026-04-20/Virtual Reality (VR) Storytelling.md index 2daa3111..e02b4bc7 100644 --- a/01_Archive/2026-04-20/Virtual Reality (VR) Storytelling.md +++ b/01_Archive/2026-04-20/Virtual Reality (VR) Storytelling.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-C15945 -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Virtual Reality (VR) Storytelling" --- -# [[Virtual Reality (VR) Storytelling]] +# [[Virtual Reality (VR) Storytelling|Virtual Reality (VR) Storytelling]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Virtual Reality (VR) Storytell ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Virtual Reality (VR) Storytelling.md]] +- Raw Source: 00_Raw/2026-04-20/Virtual Reality (VR) Storytelling.md --- diff --git a/01_Archive/2026-04-20/Visual Positioning Systems (VPS).md b/01_Archive/2026-04-20/Visual Positioning Systems (VPS).md index 9d8b2464..1ca7b5bc 100644 --- a/01_Archive/2026-04-20/Visual Positioning Systems (VPS).md +++ b/01_Archive/2026-04-20/Visual Positioning Systems (VPS).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-5B3EE3 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Visual Positioning Systems (VPS)" --- -# [[Visual Positioning Systems (VPS)]] +# [[Visual Positioning Systems (VPS)|Visual Positioning Systems (VPS)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Visual Positioning Systems (VP ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Visual Positioning Systems (VPS).md]] +- Raw Source: 00_Raw/2026-04-20/Visual Positioning Systems (VPS).md --- diff --git a/01_Archive/2026-04-20/Visual-Hierarchy-in-Game-Design.md b/01_Archive/2026-04-20/Visual-Hierarchy-in-Game-Design.md index cd1b1fa7..3fa4e986 100644 --- a/01_Archive/2026-04-20/Visual-Hierarchy-in-Game-Design.md +++ b/01_Archive/2026-04-20/Visual-Hierarchy-in-Game-Design.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-827C0B -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Visual-Hierarchy-in-Game-Design" --- -# [[Visual-Hierarchy-in-Game-Design]] +# [[Visual-Hierarchy-in-Game-Design|Visual-Hierarchy-in-Game-Design]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Visual-Hierarchy-in-Game-Desig ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Visual-Hierarchy-in-Game-Design.md]] +- Raw Source: 00_Raw/2026-04-20/Visual-Hierarchy-in-Game-Design.md --- diff --git a/01_Archive/2026-04-20/Von Neumann-Morgenstern Axioms.md b/01_Archive/2026-04-20/Von Neumann-Morgenstern Axioms.md index 4bd8bec6..b95ba30f 100644 --- a/01_Archive/2026-04-20/Von Neumann-Morgenstern Axioms.md +++ b/01_Archive/2026-04-20/Von Neumann-Morgenstern Axioms.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-E77B4E -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Von Neumann-Morgenstern Axioms" --- -# [[Von Neumann-Morgenstern Axioms]] +# [[Von Neumann-Morgenstern Axioms|Von Neumann-Morgenstern Axioms]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Von Neumann-Morgenstern Axioms ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Von Neumann-Morgenstern Axioms.md]] +- Raw Source: 00_Raw/2026-04-20/Von Neumann-Morgenstern Axioms.md --- diff --git a/01_Archive/2026-04-20/Voxel-based Rendering.md b/01_Archive/2026-04-20/Voxel-based Rendering.md index ed841921..0e766242 100644 --- a/01_Archive/2026-04-20/Voxel-based Rendering.md +++ b/01_Archive/2026-04-20/Voxel-based Rendering.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-89D12F -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Voxel-based Rendering" --- -# [[Voxel-based Rendering]] +# [[Voxel-based Rendering|Voxel-based Rendering]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Voxel-based Rendering" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Voxel-based Rendering.md]] +- Raw Source: 00_Raw/2026-04-20/Voxel-based Rendering.md --- diff --git a/01_Archive/2026-04-20/Vulkan.md b/01_Archive/2026-04-20/Vulkan.md index 13014750..79308dbc 100644 --- a/01_Archive/2026-04-20/Vulkan.md +++ b/01_Archive/2026-04-20/Vulkan.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-DDC386 -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Vulkan" --- -# [[Vulkan]] +# [[Vulkan|Vulkan]] ## 📌 한 줄 통찰 (The Karpathy Summary) > Vulkan은 Metal, Direct3D 12와 함께 WebGPU 설계의 기반이 된 현대적인 그래픽스 API입니다 [1]. 단일 스레드와 상태 저장(Stateful)에 의존하는 WebGL이나 d3d9 같은 구형 API와 달리, 드로우 콜(Draw call) 오버헤드 처리에 훨씬 효율적인 아키텍처를 가집니다 [1, 2]. 조건부 렌더링(Conditional Rendering)이나 간접 그리기(Indirect drawing) 등 최신 렌더링 파이프라인을 구현하는 데 강력한 성능을 제공합니다 [3, 4]. @@ -25,11 +25,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Vulkan" - **정책 변화:** Graphics & Performance 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[WebGPU]], [[Direct3D 12]], [[Metal]], [[Conditional Rendering]] -- **Projects/Contexts:** [[Vulkan Forward+ Renderer]], [[Vulkan Pathtracer]] +- **Related Topics:** [[WebGPU|WebGPU]], Direct3D 12, [[Metal|Metal]], Conditional Rendering +- **Projects/Contexts:** Vulkan Forward+ Renderer, Vulkan Pathtracer - **Contradictions/Notes:** 소스에 관련 정보가 부족합니다. Vulkan 기술 자체를 깊이 있게 다루는 문헌은 없으며, 대부분 WebGPU의 성능을 설명하기 위한 비교 대상이나 그래픽스 개발자들의 프로젝트 제목 및 질의응답 속에서 단편적으로만 등장합니다. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Vulkan.md]] +- Raw Source: 00_Raw/2026-04-20/Vulkan.md --- diff --git a/01_Archive/2026-04-20/W3C-Semantic-Web-Standards.md b/01_Archive/2026-04-20/W3C-Semantic-Web-Standards.md index 993cfd07..764623e8 100644 --- a/01_Archive/2026-04-20/W3C-Semantic-Web-Standards.md +++ b/01_Archive/2026-04-20/W3C-Semantic-Web-Standards.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-CEA1E7 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - W3C-Semantic-Web-Standards" --- -# [[W3C-Semantic-Web-Standards]] +# [[W3C-Semantic-Web-Standards|W3C-Semantic-Web-Standards]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - W3C-Semantic-Web-Standards" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/W3C-Semantic-Web-Standards.md]] +- Raw Source: 00_Raw/2026-04-20/W3C-Semantic-Web-Standards.md --- diff --git a/01_Archive/2026-04-20/WAI-ARIA-Accessible-Rich-Internet-Applications.md b/01_Archive/2026-04-20/WAI-ARIA-Accessible-Rich-Internet-Applications.md index 40b1fce2..0262da5f 100644 --- a/01_Archive/2026-04-20/WAI-ARIA-Accessible-Rich-Internet-Applications.md +++ b/01_Archive/2026-04-20/WAI-ARIA-Accessible-Rich-Internet-Applications.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-6F7B37 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - WAI-ARIA-Accessible-Rich-Internet-Applications" --- -# [[WAI-ARIA-Accessible-Rich-Internet-Applications]] +# [[WAI-ARIA-Accessible-Rich-Internet-Applications|WAI-ARIA-Accessible-Rich-Internet-Applications]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - WAI-ARIA-Accessible-Rich-Inter ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/WAI-ARIA-Accessible-Rich-Internet-Applications.md]] +- Raw Source: 00_Raw/2026-04-20/WAI-ARIA-Accessible-Rich-Internet-Applications.md --- diff --git a/01_Archive/2026-04-20/WEBGL_multi_draw.md b/01_Archive/2026-04-20/WEBGL_multi_draw.md index cef37257..559ef248 100644 --- a/01_Archive/2026-04-20/WEBGL_multi_draw.md +++ b/01_Archive/2026-04-20/WEBGL_multi_draw.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-C71621 -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - WEBGL_multi_draw" --- -# [[WEBGL_multi_draw]] +# [[WEBGL_multi_draw|WEBGL_multi_draw]] ## 📌 한 줄 통찰 (The Karpathy Summary) > `WEBGL_multi_draw`는 한 번의 드로우 콜(Draw Call)로 정렬된 다수의 드로우 요청을 한꺼번에 제출할 수 있게 해주는 WebGL 확장 기능(Extension)입니다 [1, 2]. Three.js에서는 `BatchedMesh`가 이 API를 활용하여 동일한 재질을 공유하지만 각기 다른 기하학적 구조(Geometry)를 가진 여러 객체들을 묶어 렌더링하는 데 사용됩니다 [3-5]. 다양한 고유 객체들을 처리할 때 기존의 개별 호출 방식에 비해 엄청난 성능 향상을 제공하지만, 브라우저 호환성 문제와 대규모 씬에서의 오버헤드 한계를 동시에 안고 있습니다 [6, 7]. @@ -29,11 +29,11 @@ github_commit: "[P-Reinforce] Continuous Worker - WEBGL_multi_draw" - **정책 변화:** Graphics & Performance 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[BatchedMesh]], [[InstancedMesh]], [[Draw Call]] -- **Projects/Contexts:** [[Three.js]], [[WebGL]] +- **Related Topics:** [[BatchedMesh|BatchedMesh]], [[InstancedMesh|InstancedMesh]], [[Draw Call|Draw Call]] +- **Projects/Contexts:** [[Three.js|Three.js]], [[WebGL|WebGL]] - **Contradictions/Notes:** `WEBGL_multi_draw`는 다수의 고유 객체를 그릴 때 CPU의 드로우 콜 병목을 해소하기 위해 설계되었으나 [1, 9], 역설적으로 특정 임계치(예: 수십만 단위)를 넘어서면 관련 버퍼 업로드 및 GPU 텍스처 업데이트 비용 때문에 오히려 병합된 지오메트리(Merged Geometry) 방식보다 성능이 30~50% 더 악화되는 실증적 모순이 관찰되었습니다 [7, 17, 18]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/WEBGL_multi_draw.md]] +- Raw Source: 00_Raw/2026-04-20/WEBGL_multi_draw.md --- diff --git a/01_Archive/2026-04-20/Wang-Tiles.md b/01_Archive/2026-04-20/Wang-Tiles.md index 582422c3..0081f873 100644 --- a/01_Archive/2026-04-20/Wang-Tiles.md +++ b/01_Archive/2026-04-20/Wang-Tiles.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-1C2064 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Wang-Tiles" --- -# [[Wang-Tiles]] +# [[Wang-Tiles|Wang-Tiles]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Wang-Tiles" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Wang-Tiles.md]] +- Raw Source: 00_Raw/2026-04-20/Wang-Tiles.md --- diff --git a/01_Archive/2026-04-20/Watermarking (AI 워터마킹).md b/01_Archive/2026-04-20/Watermarking (AI 워터마킹).md index fa75ccda..79c5e81a 100644 --- a/01_Archive/2026-04-20/Watermarking (AI 워터마킹).md +++ b/01_Archive/2026-04-20/Watermarking (AI 워터마킹).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-948507 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Watermarking (AI 워터마킹)" --- -# [[Watermarking (AI 워터마킹)]] +# [[Watermarking (AI 워터마킹)|Watermarking (AI 워터마킹)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Watermarking (AI 워터마킹) ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Watermarking (AI 워터마킹).md]] +- Raw Source: 00_Raw/2026-04-20/Watermarking (AI 워터마킹).md --- diff --git a/01_Archive/2026-04-20/Wavefunction-Collapse-Algorithm.md b/01_Archive/2026-04-20/Wavefunction-Collapse-Algorithm.md index 9a1e0b1e..087264ce 100644 --- a/01_Archive/2026-04-20/Wavefunction-Collapse-Algorithm.md +++ b/01_Archive/2026-04-20/Wavefunction-Collapse-Algorithm.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-E0FD1F -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Wavefunction-Collapse-Algorithm" --- -# [[Wavefunction-Collapse-Algorithm]] +# [[Wavefunction-Collapse-Algorithm|Wavefunction-Collapse-Algorithm]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Wavefunction-Collapse-Algorith ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Wavefunction-Collapse-Algorithm.md]] +- Raw Source: 00_Raw/2026-04-20/Wavefunction-Collapse-Algorithm.md --- diff --git a/01_Archive/2026-04-20/Waves of Connection.md b/01_Archive/2026-04-20/Waves of Connection.md index 1fcc67b8..5bf18d8f 100644 --- a/01_Archive/2026-04-20/Waves of Connection.md +++ b/01_Archive/2026-04-20/Waves of Connection.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-74AA0F -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Waves of Connection" --- -# [[Waves of Connection]] +# [[Waves of Connection|Waves of Connection]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 'Waves of Connection'은 2025년 오사카 엑스포(Expo 2025 Osaka)에서 전시된 설치 작품입니다 [1]. 이 프로젝트는 Three.js WebGPU를 활용하여 98인치 4K 디스플레이 상에 100만 개의 파티클을 실시간으로 렌더링했습니다 [1]. 특히 눈에 띄는 지연(lag) 없이 다수의 사람의 움직임을 추적하는 다인원 바디 트래킹(multi-person body tracking) 기술을 구현하여 WebGPU의 뛰어난 성능을 입증한 사례로 꼽힙니다 [1]. @@ -20,11 +20,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Waves of Connection" - **정책 변화:** Graphics & Performance 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Three.js WebGPU]], [[Particle System]] -- **Projects/Contexts:** [[Expo 2025 Osaka]] +- **Related Topics:** [[Threejs WebGPU 파티클 예제|Three.js WebGPU]], Particle System +- **Projects/Contexts:** [[Expo 2025 Osaka|Expo 2025 Osaka]] - **Contradictions/Notes:** 소스 내에서 'Waves of Connection'에 대한 정보는 Three.js WebGPU와 Native WebGPU의 성능을 비교하며 WebGPU의 압도적인 렌더링 성능 향상(100만 개 파티클 실시간 처리)을 보여주기 위한 단편적인 사례로만 언급되었습니다. 그 외의 배경지식이나 세부 내용은 소스에 관련 정보가 부족합니다. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Waves of Connection.md]] +- Raw Source: 00_Raw/2026-04-20/Waves of Connection.md --- diff --git a/01_Archive/2026-04-20/Wayfinding-Design.md b/01_Archive/2026-04-20/Wayfinding-Design.md index 86fa91fa..7c3f536a 100644 --- a/01_Archive/2026-04-20/Wayfinding-Design.md +++ b/01_Archive/2026-04-20/Wayfinding-Design.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-9E4F37 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Wayfinding-Design" --- -# [[Wayfinding-Design]] +# [[Wayfinding-Design|Wayfinding-Design]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Wayfinding-Design" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Wayfinding-Design.md]] +- Raw Source: 00_Raw/2026-04-20/Wayfinding-Design.md --- diff --git a/01_Archive/2026-04-20/Web Performance Optimization.md b/01_Archive/2026-04-20/Web Performance Optimization.md index c01493f0..5e041024 100644 --- a/01_Archive/2026-04-20/Web Performance Optimization.md +++ b/01_Archive/2026-04-20/Web Performance Optimization.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-3862CA -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Web Performance Optimization" --- -# [[Web Performance Optimization]] +# [[Web Performance Optimization|Web Performance Optimization]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 웹 성능 최적화(Web Performance Optimization)는 웹사이트가 사용자에게 얼마나 빠르게 느껴지는지(인지된 성능)를 측정하고 개선하는 과정이다 [1]. 느린 웹사이트는 사용자의 좌절감을 유발하고 이탈률을 높이며 검색 엔진 순위(SEO)에도 악영향을 미치므로, 코어 웹 바이탈(Core Web Vitals)과 같은 표준화된 지표를 바탕으로 로딩 속도, 상호작용성, 시각적 안정성을 최적화하는 것이 필수적이다 [1-5]. @@ -37,11 +37,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Web Performance Optimization" - **정책 변화:** AI 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Core Web Vitals]], [[Largest Contentful Paint]], [[Interaction to Next Paint]], [[Cumulative Layout Shift]], [[WebGPU]], [[WebGL]] -- **Projects/Contexts:** [[Chrome DevTools]], [[Lighthouse]], [[Chrome User Experience Report]], [[WebPageTest]] +- **Related Topics:** [[Core Web Vitals|Core Web Vitals]], Largest Contentful Paint, Interaction to Next Paint, Cumulative Layout Shift, [[WebGPU|WebGPU]], [[WebGL|WebGL]] +- **Projects/Contexts:** [[Chrome DevTools|Chrome DevTools]], [[Lighthouse|Lighthouse]], Chrome User Experience Report, WebPageTest - **Contradictions/Notes:** FID(First Input Delay)는 사용자의 첫 번째 상호작용 지연 시간만을 측정하는 한계가 있어, 페이지 생명주기 전체의 모든 상호작용 응답성을 추적하는 INP로 대체되었다 [7-10]. 또한, WebGL은 단일 스레드 명령 제출 구조로 인해 GPU가 유휴 상태임에도 CPU 병목이 발생하는 한계가 있었으나, WebGPU는 다중 스레드 명령 생성과 컴퓨트 셰이더를 통해 이러한 아키텍처적 한계를 해결한다 [44, 45, 56-59]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Web Performance Optimization.md]] +- Raw Source: 00_Raw/2026-04-20/Web Performance Optimization.md --- diff --git a/01_Archive/2026-04-20/Web Worker (웹 워커).md b/01_Archive/2026-04-20/Web Worker (웹 워커).md index 65bef19f..6999da35 100644 --- a/01_Archive/2026-04-20/Web Worker (웹 워커).md +++ b/01_Archive/2026-04-20/Web Worker (웹 워커).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AI-049 -category: "[[10_Wiki/💡 Topics/Frontend & Concurrency]]" +category: "10_Wiki/💡 Topics/Frontend & Concurrency" confidence_score: 0.98 tags: [webworker, concurrency, javascript, performance] last_reinforced: 2026-06-XX github_commit: "[P-Reinforce] Processed Web Worker (웹 워커)." --- -# [[Web Worker (웹 워커)]] +# [[Web Worker (웹 워커)|Web Worker (웹 워커)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 웹 브라우저의 메인 스레드(Main Thread)가 UI 및 사용자 입력 처리라는 중요한 임무를 수행할 수 있도록, 무겁고 시간이 오래 걸리는 계산 작업을 별도의 백그라운드 스레드에서 분리 실행하는 기술이다. @@ -24,7 +24,7 @@ github_commit: "[P-Reinforce] Processed Web Worker (웹 워커)." - **정책 변화:** 고성능 컴퓨팅이 요구되는 환경에서는 `SharedArrayBuffer`와 같은 고급 메모리 공유 기법과 함께, 웹 워커를 활용하여 병목 현상을 근본적으로 해결하는 아키텍처 설계가 표준화되고 있다. ## 🔗 지식 연결 (Graph) -- Parent: [[Web Worker (웹 워커)]] -- Related: [[Concurrency]] , [[JavaScript 메모리 관리(JavaScript Memory Management)]] , [[SharedArrayBuffer]] -- Raw Source: [[00_Raw/Web Worker (웹 워커).md]] +- Parent: [[Web Worker (웹 워커)|Web Worker (웹 워커)]] +- Related: Concurrency , [[JavaScript 메모리 관리(JavaScript Memory Management)|JavaScript 메모리 관리(JavaScript Memory Management)]] , [[SharedArrayBuffer|SharedArrayBuffer]] +- Raw Source: 00_Raw/Web Worker (웹 워커).md --- \ No newline at end of file diff --git a/01_Archive/2026-04-20/Web Worker와 SharedArrayBuffer를 이용한 실제 고부하 병렬 처리 구현체 (실패_성공 포함).md b/01_Archive/2026-04-20/Web Worker와 SharedArrayBuffer를 이용한 실제 고부하 병렬 처리 구현체 (실패_성공 포함).md index dc41d369..1932e8ff 100644 --- a/01_Archive/2026-04-20/Web Worker와 SharedArrayBuffer를 이용한 실제 고부하 병렬 처리 구현체 (실패_성공 포함).md +++ b/01_Archive/2026-04-20/Web Worker와 SharedArrayBuffer를 이용한 실제 고부하 병렬 처리 구현체 (실패_성공 포함).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-EBB42F -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Web Worker와 SharedArrayBuffer를 이용한 실제 고부하 병렬 처리 구현체 (실패_성공 포함)" --- -# [[Web Worker와 SharedArrayBuffer를 이용한 실제 고부하 병렬 처리 구현체 (실패_성공 포함)]] +# [[Web Worker와 SharedArrayBuffer를 이용한 실제 고부하 병렬 처리 구현체 (실패_성공 포함)|Web Worker와 SharedArrayBuffer를 이용한 실제 고부하 병렬 처리 구현체 (실패_성공 포함)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 소스에 관련 정보가 부족합니다. @@ -26,5 +26,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Web Worker와 SharedArrayBuffe --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Web Worker와 SharedArrayBuffer를 이용한 실제 고부하 병렬 처리 구현체 (실패_성공 포함).md]] +- Raw Source: 00_Raw/2026-04-20/Web Worker와 SharedArrayBuffer를 이용한 실제 고부하 병렬 처리 구현체 (실패_성공 포함).md --- diff --git a/01_Archive/2026-04-20/Web-Content-Accessibility-Guidelines-WCAG.md b/01_Archive/2026-04-20/Web-Content-Accessibility-Guidelines-WCAG.md index 6e26e524..0b5090b7 100644 --- a/01_Archive/2026-04-20/Web-Content-Accessibility-Guidelines-WCAG.md +++ b/01_Archive/2026-04-20/Web-Content-Accessibility-Guidelines-WCAG.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-52EA66 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Web-Content-Accessibility-Guidelines-WCAG" --- -# [[Web-Content-Accessibility-Guidelines-WCAG]] +# [[Web-Content-Accessibility-Guidelines-WCAG|Web-Content-Accessibility-Guidelines-WCAG]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Web-Content-Accessibility-Guid ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Web-Content-Accessibility-Guidelines-WCAG.md]] +- Raw Source: 00_Raw/2026-04-20/Web-Content-Accessibility-Guidelines-WCAG.md --- diff --git a/01_Archive/2026-04-20/Web3 Infrastructure.md b/01_Archive/2026-04-20/Web3 Infrastructure.md index 80a99d1c..a5f1f30e 100644 --- a/01_Archive/2026-04-20/Web3 Infrastructure.md +++ b/01_Archive/2026-04-20/Web3 Infrastructure.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-7551CC -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Web3 Infrastructure" --- -# [[Web3 Infrastructure]] +# [[Web3 Infrastructure|Web3 Infrastructure]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Web3 Infrastructure" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Web3 Infrastructure.md]] +- Raw Source: 00_Raw/2026-04-20/Web3 Infrastructure.md --- diff --git a/01_Archive/2026-04-20/WebAssembly.md b/01_Archive/2026-04-20/WebAssembly.md index 09de59d0..be505463 100644 --- a/01_Archive/2026-04-20/WebAssembly.md +++ b/01_Archive/2026-04-20/WebAssembly.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-E798C0 -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - WebAssembly" --- -# [[WebAssembly]] +# [[WebAssembly|WebAssembly]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 소스에 관련 정보가 부족합니다. 제공된 소스에서 WebAssembly(Wasm)에 대한 근본적인 정의나 포괄적인 설명은 찾을 수 없습니다. 다만, 웹 브라우저 환경에서 JavaScript와 함께 실행되어 CPU 기반의 복잡한 연산을 보조하거나, C/C++ 등의 언어로 작성된 코드를 웹에서 디버깅 및 구동할 수 있게 해주는 기술로 단편적으로 확인됩니다 [1-3]. @@ -24,11 +24,11 @@ github_commit: "[P-Reinforce] Continuous Worker - WebAssembly" - **정책 변화:** Graphics & Performance 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[WebGL]], [[JavaScript]], [[Spectre]] -- **Projects/Contexts:** [[3D Gaussian Splatting]], [[Chrome DevTools]], [[WebKit]] +- **Related Topics:** [[WebGL|WebGL]], [[JavaScript|JavaScript]], [[Spectre|Spectre]] +- **Projects/Contexts:** [[3D_Gaussian_Splatting|3D Gaussian Splatting]], [[Chrome DevTools|Chrome DevTools]], [[WebKit|WebKit]] - **Contradictions/Notes:** 소스에 WebAssembly의 구체적인 설계 구조나 동작 원리에 대한 포괄적인 정보가 부족합니다. 제공된 문헌들은 주로 WebGL의 연산 한계를 설명할 때의 대안(CPU 오프로딩 수단)이나 브라우저 보안 및 디버깅 툴을 설명하는 맥락에서만 WebAssembly를 부가적으로 언급하고 있습니다. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/WebAssembly.md]] +- Raw Source: 00_Raw/2026-04-20/WebAssembly.md --- diff --git a/01_Archive/2026-04-20/WebGL 2.0.md b/01_Archive/2026-04-20/WebGL 2.0.md index 50f69caa..92f45a8f 100644 --- a/01_Archive/2026-04-20/WebGL 2.0.md +++ b/01_Archive/2026-04-20/WebGL 2.0.md @@ -1,4 +1,4 @@ -# [[WebGL 2.0]] +# [[WebGL 2.0|WebGL 2.0]] ## 📌 Brief Summary WebGL 2.0은 웹 브라우저 환경에서 3D 그래픽을 렌더링하기 위한 API로, 브라우저가 WebGPU를 지원하지 않는 환경에서 WebGPURenderer가 자동으로 사용하는 대체(Fallback) 렌더러 역할을 합니다 [1, 2]. 최신 Three.js 개발 환경에서는 TSL(Three Shader Language)을 통해 WebGPU와 WebGL에서 모두 작동하는 크로스 플랫폼 셰이더를 작성할 수 있습니다 [1-3]. WebGL 2.0은 텍스처 배열(Data Array Textures)과 BatchedMesh 같은 기능을 지원하여 전통적인 WebGL 1.0의 한계를 극복하고 렌더링 성능을 높일 수 있는 강력한 기반을 제공합니다 [4, 5]. @@ -10,8 +10,8 @@ WebGL 2.0은 웹 브라우저 환경에서 3D 그래픽을 렌더링하기 위 * **셰이더 파이프라인의 통합:** TSL(Three Shader Language) 시스템의 도입으로, 개발자는 기존처럼 GLSL(WebGL)과 WGSL(WebGPU)의 두 가지 셰이더 코드베이스를 이중으로 유지할 필요가 없어졌습니다 [3, 15]. 하나의 TSL 코드가 각 백엔드에 맞게 자동 컴파일을 지원합니다 [3]. 포스트 프로세싱(Post-processing)의 경우, WebGL 프로젝트에서는 여전히 `pmndrs/postprocessing` 라이브러리가 가장 우수한 성능을 발휘하지만, TSL 기반 포스트 프로세싱도 혼용이 가능해졌습니다 [16]. ## 🔗 Knowledge Connections -- **Related Topics:** [[WebGPU]], [[Three.js]], [[Draw Calls]], [[BatchedMesh]], [[TSL (Three Shader Language)]] -- **Projects/Contexts:** [[WebGPURenderer Fallback]] +- **Related Topics:** [[WebGPU|WebGPU]], [[Three.js|Three.js]], Draw Calls, [[BatchedMesh|BatchedMesh]], [[TSL (Three Shader Language)|TSL (Three Shader Language)]] +- **Projects/Contexts:** WebGPURenderer Fallback - **Contradictions/Notes:** 소스에 따르면 WebGPU는 멀티스레드 명령 생성과 Compute Shader 연산을 통해 복잡한 시뮬레이션 및 데이터 처리가 가능하지만, WebGL은 싱글 스레드 및 상태 기반 접근 방식을 취하고 있어 1,000~2,000회 이상의 빈번한 드로우 콜 발생 시 CPU에서 극심한 렌더링 성능 병목(Bottleneck) 현상이 발생한다는 뚜렷한 대비가 관찰됩니다 [10, 17, 18]. --- diff --git a/01_Archive/2026-04-20/WebGL 20.md b/01_Archive/2026-04-20/WebGL 20.md index 746f54b9..12a0408f 100644 --- a/01_Archive/2026-04-20/WebGL 20.md +++ b/01_Archive/2026-04-20/WebGL 20.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-DDA796 -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - WebGL 20" --- -# [[WebGL 20]] +# [[WebGL 20|WebGL 20]] ## 📌 한 줄 통찰 (The Karpathy Summary) > WebGL 2.0은 웹 브라우저 환경에서 3D 그래픽을 렌더링하기 위한 API로, 브라우저가 WebGPU를 지원하지 않는 환경에서 WebGPURenderer가 자동으로 사용하는 대체(Fallback) 렌더러 역할을 합니다 [1, 2]. 최신 Three.js 개발 환경에서는 TSL(Three Shader Language)을 통해 WebGPU와 WebGL에서 모두 작동하는 크로스 플랫폼 셰이더를 작성할 수 있습니다 [1-3]. WebGL 2.0은 텍스처 배열(Data Array Textures)과 BatchedMesh 같은 기능을 지원하여 전통적인 WebGL 1.0의 한계를 극복하고 렌더링 성능을 높일 수 있는 강력한 기반을 제공합니다 [4, 5]. @@ -23,11 +23,11 @@ github_commit: "[P-Reinforce] Continuous Worker - WebGL 20" - **정책 변화:** Graphics & Performance 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[WebGPU]], [[Three.js]], [[Draw Calls]], [[BatchedMesh]], [[TSL (Three Shader Language)]] -- **Projects/Contexts:** [[WebGPURenderer Fallback]] +- **Related Topics:** [[WebGPU|WebGPU]], [[Three.js|Three.js]], Draw Calls, [[BatchedMesh|BatchedMesh]], [[TSL (Three Shader Language)|TSL (Three Shader Language)]] +- **Projects/Contexts:** WebGPURenderer Fallback - **Contradictions/Notes:** 소스에 따르면 WebGPU는 멀티스레드 명령 생성과 Compute Shader 연산을 통해 복잡한 시뮬레이션 및 데이터 처리가 가능하지만, WebGL은 싱글 스레드 및 상태 기반 접근 방식을 취하고 있어 1,000~2,000회 이상의 빈번한 드로우 콜 발생 시 CPU에서 극심한 렌더링 성능 병목(Bottleneck) 현상이 발생한다는 뚜렷한 대비가 관찰됩니다 [10, 17, 18]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/WebGL 2.0.md]] +- Raw Source: 00_Raw/2026-04-20/WebGL 2.0.md --- diff --git a/01_Archive/2026-04-20/WebGL API.md b/01_Archive/2026-04-20/WebGL API.md index 635240b9..552a960c 100644 --- a/01_Archive/2026-04-20/WebGL API.md +++ b/01_Archive/2026-04-20/WebGL API.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-32752F -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - WebGL API" --- -# [[WebGL API]] +# [[WebGL API|WebGL API]] ## 📌 한 줄 통찰 (The Karpathy Summary) > WebGL(Web Graphics Library)은 웹 브라우저의 HTML5 `` 요소 내에서 하드웨어 가속을 통해 실시간 3D 및 2D 그래픽을 렌더링하기 위한 저수준(low-level) 크로스 플랫폼 애플리케이션 프로그래밍 인터페이스(API)입니다 [1-3]. OpenGL ES 2.0을 기반으로 구축되었으며, 자바스크립트(JavaScript) 코드를 GPU 명령어로 변환하여 그래픽 처리 장치(GPU)에서 직접 실행되도록 설계되었습니다 [2, 4]. 2011년에 도입된 이후 웹 기반 3D 그래픽의 핵심 기반으로 사용되어 왔으나, 단일 스레드 실행 및 전역 상태 머신 모델과 같은 아키텍처의 한계로 인해 CPU 병목 현상이 발생하는 등 최신 하드웨어 성능을 온전히 끌어내기에는 제약이 존재합니다 [4-7]. @@ -27,11 +27,11 @@ WebGL의 핵심적인 문제는 기반이 되는 아키텍처가 2011년 GPU 설 - **정책 변화:** Graphics & Performance 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[OpenGL ES 2.0]], [[GPU]], [[HTML5 Canvas]], [[WebGPU]], [[JavaScript]] -- **Projects/Contexts:** [[Three.js]], [[WebGLRenderingContext]] +- **Related Topics:** [[OpenGL ES 2.0|OpenGL ES 2.0]], [[GPU|GPU]], [[HTML5 Canvas|HTML5 Canvas]], [[WebGPU|WebGPU]], [[JavaScript|JavaScript]] +- **Projects/Contexts:** [[Three.js|Three.js]], [[WebGLRenderingContext|WebGLRenderingContext]] - **Contradictions/Notes:** 소스에 따르면 WebGL은 단일 스레드 실행과 컴퓨트 셰이더 미지원 등의 구조적 단점 때문에 성능에 민감하고 대규모 연산이 필요한 최신 3D 경험에서는 한계가 명확하여 WebGPU로 대체되고 있습니다 [7, 19, 23]. 하지만 보편적이고 폭넓은 브라우저 호환성이 필요한 프로덕션 환경(모든 기기에서 동작해야 하는 경우)에서는 WebGPU의 지원이 아직 완벽하지 않기 때문에 여전히 WebGL이 가장 안전하고 적절한 선택(또는 폴백)으로 간주됩니다 [24-26]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/WebGL API.md]] +- Raw Source: 00_Raw/2026-04-20/WebGL API.md --- diff --git a/01_Archive/2026-04-20/WebGL Optimization.md b/01_Archive/2026-04-20/WebGL Optimization.md index f5eacea4..767bd790 100644 --- a/01_Archive/2026-04-20/WebGL Optimization.md +++ b/01_Archive/2026-04-20/WebGL Optimization.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-655682 -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - WebGL Optimization" --- -# [[WebGL Optimization]] +# [[WebGL Optimization|WebGL Optimization]] ## 📌 한 줄 통찰 (The Karpathy Summary) > WebGL 최적화는 웹 브라우저 환경에서 3D 그래픽스의 렌더링 속도와 메모리 효율성을 향상시키기 위한 체계적인 기술과 방법론을 의미합니다 [1, 2]. 주된 목적은 CPU와 GPU 간의 통신 오버헤드를 유발하는 드로우 콜(Draw Call)을 최소화하여 안정적인 60 FPS 프레임 레이트를 유지하는 것입니다 [2, 3]. 이를 위해 기하학적 구조 인스턴싱(Instancing), 텍스처 압축, 디테일 수준(LOD) 제어, 그리고 브라우저 메모리 한계를 고려한 자원 해제 등의 최적화 기법이 복합적으로 적용됩니다 [4-6]. @@ -23,13 +23,13 @@ github_commit: "[P-Reinforce] Continuous Worker - WebGL Optimization" - **정책 변화:** Graphics & Performance 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Draw Call]], [[InstancedMesh]], [[BatchedMesh]], [[Frustum Culling]], [[Level of Detail (LOD)]] -- **Projects/Contexts:** [[Three.js]] +- **Related Topics:** [[Draw Call|Draw Call]], [[InstancedMesh|InstancedMesh]], [[BatchedMesh|BatchedMesh]], [[Frustum Culling|Frustum Culling]], [[Level of Detail (LOD)|Level of Detail (LOD)]] +- **Projects/Contexts:** [[Three.js|Three.js]] - **Contradictions/Notes:** - `InstancedMesh`는 드로우 콜을 1회로 줄여주어 강력하지만, 단일 엔진 객체로 취급되기 때문에 인스턴스 각각에 대한 시야 절두체 컬링(Frustum Culling)이 개별 적용되지 않는 한계가 있습니다 [29]. 따라서 화면에 하나의 인스턴스만 걸쳐 있어도 보이지 않는 나머지 인스턴스의 정점 연산까지 수행해야 하는 GPU 낭비가 발생할 수 있습니다 [29]. - 오버드로우(Overdraw) 관점에서도 `InstancedMesh`는 자동 정렬(Sorting) 기능을 지원하지 않아 뒤에 있는 객체가 덮어 씌워지면서 픽셀 처리에 병목을 일으킬 수 있으므로, 상황에 따라서는 오히려 개별 메쉬나 정적 지오메트리 병합(Merging)을 활용하는 것이 더 높은 FPS를 제공할 수 있다고 지적합니다 [30-32]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/WebGL Optimization.md]] +- Raw Source: 00_Raw/2026-04-20/WebGL Optimization.md --- diff --git a/01_Archive/2026-04-20/WebGL 모바일 GPU 성능 관리.md b/01_Archive/2026-04-20/WebGL 모바일 GPU 성능 관리.md index efe2a670..7e04fe3a 100644 --- a/01_Archive/2026-04-20/WebGL 모바일 GPU 성능 관리.md +++ b/01_Archive/2026-04-20/WebGL 모바일 GPU 성능 관리.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-3EE85A -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - WebGL 모바일 GPU 성능 관리" --- -# [[WebGL 모바일 GPU 성능 관리]] +# [[WebGL 모바일 GPU 성능 관리|WebGL 모바일 GPU 성능 관리]] ## 📌 한 줄 통찰 (The Karpathy Summary) > WebGL 모바일 GPU 성능 관리는 처리 능력과 메모리 용량이 제한적인 모바일 디바이스 환경에서 3D 애플리케이션이 부드럽게 구동될 수 있도록 렌더링 부하를 줄이는 기술적 과정입니다. 모바일 브라우저는 처리 가능한 폴리곤 수와 드로우 콜(Draw Call)에 뚜렷한 한계가 있으며, 이를 극복하기 위해 셰이더 정밀도 조절, 텍스처 압축, 배터리 소모 관리 등의 다각적인 최적화가 요구됩니다 [1-4]. @@ -29,11 +29,11 @@ github_commit: "[P-Reinforce] Continuous Worker - WebGL 모바일 GPU 성능 관 - **정책 변화:** Graphics & Performance 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Draw Calls]], [[Texture Atlas]], [[셰이더 정밀도 (Mediump/Highp)]], [[Varying Variables]], [[FXAA]] -- **Projects/Contexts:** [[Three.js 모바일 렌더링 최적화]], [[모바일 기반 WebGL 애플리케이션 개발]] +- **Related Topics:** Draw Calls, [[Texture Atlas|Texture Atlas]], [[셰이더 정밀도 (Mediump_Highp)|셰이더 정밀도 (Mediump/Highp)]], [[Varying Variables|Varying Variables]], [[FXAA|FXAA]] +- **Projects/Contexts:** [[Three.js 모바일 렌더링 최적화|Three.js 모바일 렌더링 최적화]], [[모바일 기반 WebGL 애플리케이션 개발|모바일 기반 WebGL 애플리케이션 개발]] - **Contradictions/Notes:** 모바일 환경 최적화를 위해 다양한 기법을 동원하더라도, 텍스처 메모리를 500MB 이하로 통제하지 않으면 가비지 컬렉션(GC) 멈춤 현상으로 최적화 효과가 상쇄될 수 있으므로 메모리 사용량에 대한 엄격한 제한이 우선되어야 합니다 [4]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/WebGL 모바일 GPU 성능 관리.md]] +- Raw Source: 00_Raw/2026-04-20/WebGL 모바일 GPU 성능 관리.md --- diff --git a/01_Archive/2026-04-20/WebGL.md b/01_Archive/2026-04-20/WebGL.md index 6cf38599..ccb43cfc 100644 --- a/01_Archive/2026-04-20/WebGL.md +++ b/01_Archive/2026-04-20/WebGL.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-7B2955 -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - WebGL" --- -# [[WebGL]] +# [[WebGL|WebGL]] ## 📌 한 줄 통찰 (The Karpathy Summary) > **WebGL**은 플러그인 없이 웹 브라우저에서 2D 및 3D 그래픽을 렌더링하기 위한 저수준(Low-level) JavaScript API입니다. 원시 WebGL은 직접 다루기 매우 복잡하고 장황하지만, **Three.js**나 **React Three Fiber(R3F)** 같은 라이브러리를 통해 추상화되어 현대 웹의 고성능 3D 인터랙티브 그래픽과 게임 엔진을 구현하는 핵심 기반 기술로 사용됩니다. @@ -28,8 +28,8 @@ github_commit: "[P-Reinforce] Continuous Worker - WebGL" - **정책 변화:** Graphics & Performance 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Three.js]], [[React Three Fiber (R3F)]], [[WebGPU Compute Shaders]], [[OffscreenCanvas]], [[InstancedMesh (드로우 콜 최적화)]], [[Memory Leak Prevention (메모리 누수 방지)]] -- **Projects/Contexts:** [[브라우저 기반 3D 데이터 시각화 및 디지털 트윈]], [[멀티스레드 기반 고성능 웹 게임 엔진]] +- **Related Topics:** [[Three.js|Three.js]], [[React Three Fiber (R3F)|React Three Fiber (R3F)]], [[WebGPU Compute Shaders|WebGPU Compute Shaders]], [[OffscreenCanvas|OffscreenCanvas]], [[InstancedMesh (드로우 콜 최적화)|InstancedMesh (드로우 콜 최적화)]], [[Memory Leak Prevention 메모리 누수 방지|Memory Leak Prevention (메모리 누수 방지)]] +- **Projects/Contexts:** 브라우저 기반 3D 데이터 시각화 및 디지털 트윈, 멀티스레드 기반 고성능 웹 게임 엔진 - **Contradictions/Notes:** WebGL 파이프라인에서 `EffectComposer` 등을 활용해 커스텀 후처리(Post-processing)를 적용할 경우, WebGL의 내장 안티앨리어싱(AA) 기능이 무효화되는 제약이 있습니다. 이를 해결하려면 파이프라인 마지막 단계에 SMAA나 FXAA 효과 패스를 수동으로 추가해 주어야 시각적 품질을 유지할 수 있습니다. -- Raw Source: [[00_Raw/2026-04-20/WebGL.md]] +- Raw Source: 00_Raw/2026-04-20/WebGL.md --- diff --git a/01_Archive/2026-04-20/WebGL2.md b/01_Archive/2026-04-20/WebGL2.md index 28be87ba..6a898db5 100644 --- a/01_Archive/2026-04-20/WebGL2.md +++ b/01_Archive/2026-04-20/WebGL2.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-208D23 -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - WebGL2" --- -# [[WebGL2]] +# [[WebGL2|WebGL2]] ## 📌 한 줄 통찰 (The Karpathy Summary) > WebGL2는 웹 브라우저 환경에서 3D 그래픽스를 렌더링하기 위해 사용되는 그래픽 API입니다 [1, 2]. 최신 Three.js 생태계에서는 차세대 API인 WebGPU로의 전환이 이루어지고 있으나, WebGPU를 지원하지 않는 브라우저에서는 WebGL 2가 자동 대체(Fallback) 수단으로서 핵심적인 역할을 수행합니다 [3, 4]. WebGL1과 비교했을 때 데이터 배열 텍스처(Data Array Textures)를 지원하고 텍스처 아틀라스의 블리딩(Bleeding) 현상을 더 쉽게 제어할 수 있는 등 진보된 기능을 제공하지만, WebGPU와 달리 컴퓨트 셰이더(Compute Shaders)를 지원하지 않는 한계가 있습니다 [1, 5, 6]. @@ -25,11 +25,11 @@ github_commit: "[P-Reinforce] Continuous Worker - WebGL2" - **정책 변화:** Graphics & Performance 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[WebGPU]], [[Three.js]], [[Data Array Textures]], [[Compute Shaders]] -- **Projects/Contexts:** [[Three.js WebGPURenderer 자동 폴백 지원]], [[BatchedMesh 및 드로우 콜 최적화 파이프라인]] +- **Related Topics:** [[WebGPU|WebGPU]], [[Three.js|Three.js]], [[Data Array Textures|Data Array Textures]], [[Compute Shaders|Compute Shaders]] +- **Projects/Contexts:** Three.js WebGPURenderer 자동 폴백 지원, BatchedMesh 및 드로우 콜 최적화 파이프라인 - **Contradictions/Notes:** 소스에 따르면 WebGL 2는 현재 널리 지원되는 강력한 그래픽 API이지만, 컴퓨트 셰이더를 통한 GPU 기반의 병렬 가시성 연산(Compute Culling)이나 대규모 간접 드로우(Indirect Draw) 부재로 인해 렌더링 성능 최적화의 기술적 한계점에 도달해 있습니다 [2, 5, 11]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/WebGL2.md]] +- Raw Source: 00_Raw/2026-04-20/WebGL2.md --- diff --git a/01_Archive/2026-04-20/WebGLRenderingContext.md b/01_Archive/2026-04-20/WebGLRenderingContext.md index 181904e3..82995800 100644 --- a/01_Archive/2026-04-20/WebGLRenderingContext.md +++ b/01_Archive/2026-04-20/WebGLRenderingContext.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-47CDF1 -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - WebGLRenderingContext" --- -# [[WebGLRenderingContext]] +# [[WebGLRenderingContext|WebGLRenderingContext]] ## 📌 한 줄 통찰 (The Karpathy Summary) > WebGLRenderingContext는 HTML 캔버스(canvas) 요소에 대한 WebGL 컨텍스트를 보유하는 자바스크립트 객체입니다 [1, 2]. 개발자들 사이에서 일반적으로 `gl`이라고 명명되며, 애플리케이션은 이 객체를 통해 하드웨어 그래픽 파이프라인의 모든 WebGL 기능(API)에 접근하고 제어합니다 [1, 2]. 이 컨텍스트를 생성하는 작업은 브라우저가 동기적으로 OpenGL 컨텍스트를 생성하도록 강제하므로 운영 체제나 시스템 환경에 따라 속도가 느려질 수 있습니다 [3]. @@ -22,11 +22,11 @@ github_commit: "[P-Reinforce] Continuous Worker - WebGLRenderingContext" - **정책 변화:** Graphics & Performance 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[WebGL]], [[OpenGL]], [[GPU]] -- **Projects/Contexts:** [[Modernizr]], [[LearnWebGL]] +- **Related Topics:** [[WebGL|WebGL]], OpenGL, [[GPU|GPU]] +- **Projects/Contexts:** Modernizr, LearnWebGL - **Contradictions/Notes:** 소스 간의 모순된 내용은 없으나, WebGLRenderingContext 생성에 따른 성능 지연 문제와 관련해 페이지 로드 시 불필요하게 컨텍스트를 생성하지 않아야 한다는 점이 강조됩니다 [3, 7]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/WebGLRenderingContext.md]] +- Raw Source: 00_Raw/2026-04-20/WebGLRenderingContext.md --- diff --git a/01_Archive/2026-04-20/WebGPU Compute Shader.md b/01_Archive/2026-04-20/WebGPU Compute Shader.md index 2b633cf9..05b8a44b 100644 --- a/01_Archive/2026-04-20/WebGPU Compute Shader.md +++ b/01_Archive/2026-04-20/WebGPU Compute Shader.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-B03C61 -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - WebGPU Compute Shader" --- -# [[WebGPU Compute Shader]] +# [[WebGPU Compute Shader|WebGPU Compute Shader]] ## 📌 한 줄 통찰 (The Karpathy Summary) > WebGPU Compute Shader는 범용 GPU 연산을 수행하여 메인 스레드(CPU)의 과중한 작업을 GPU 코어로 분산시키는 렌더링 기술이다 [1, 2]. InstancedMesh를 사용할 때 발생하는 가시성 판단(컬링) 및 데이터 전송 병목 현상을 극복하기 위해 GPU 주도 렌더링(GPU-driven Rendering)을 구현하는 데 핵심적인 역할을 한다 [2]. 이를 통해 수백만 개의 파티클이나 대규모 인스턴스의 물리 연산 및 컬링을 CPU 개입 없이 GPU 내부에서 병렬로 직접 처리할 수 있다 [1-3]. @@ -23,11 +23,11 @@ github_commit: "[P-Reinforce] Continuous Worker - WebGPU Compute Shader" - **정책 변화:** Graphics & Performance 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[GPU-driven Rendering]], [[Indirect Draw]], [[Frustum Culling]], [[Draw Call]] -- **Projects/Contexts:** [[대규모 건축물 및 지형 뷰어(BIM)]], [[Three.js WebGPU 파티클 예제]], [[실시간 물리 및 유체 시뮬레이션]] +- **Related Topics:** [[GPU-driven Rendering|GPU-driven Rendering]], [[Indirect Draw|Indirect Draw]], [[Frustum Culling|Frustum Culling]], [[Draw Call|Draw Call]] +- **Projects/Contexts:** [[대규모 건축물 및 지형 뷰어(BIM)|대규모 건축물 및 지형 뷰어(BIM)]], [[Three.js WebGPU 파티클 예제|Three.js WebGPU 파티클 예제]], [[실시간 물리 및 유체 시뮬레이션|실시간 물리 및 유체 시뮬레이션]] - **Contradictions/Notes:** 컴퓨트 셰이더를 통해 GPU 단에서 컬링 및 피킹 처리를 최적화할 수 있으나, 다른 인스턴스에 의해 가려진 객체들을 포함하여 올가미(Lasso) 그룹 선택을 하는 것과 같은 복잡한 상호작용은 컴퓨트 셰이더만으로는 간단히 해결되지 않으며, 깊이 벗기기(depth-peeling)와 같은 추가적인 셰이더 작업이나 웹 워커가 필요할 수 있다 [10]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/WebGPU Compute Shader.md]] +- Raw Source: 00_Raw/2026-04-20/WebGPU Compute Shader.md --- diff --git a/01_Archive/2026-04-20/WebGPU Compute Shaders.md b/01_Archive/2026-04-20/WebGPU Compute Shaders.md index 1a789a27..7b9db8f2 100644 --- a/01_Archive/2026-04-20/WebGPU Compute Shaders.md +++ b/01_Archive/2026-04-20/WebGPU Compute Shaders.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-1903E0 -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - WebGPU Compute Shaders" --- -# [[WebGPU Compute Shaders]] +# [[WebGPU Compute Shaders|WebGPU Compute Shaders]] ## 📌 한 줄 통찰 (The Karpathy Summary) > WebGPU Compute Shader는 JavaScript의 메인 스레드에서 수행되던 무거운 범용 연산을 수많은 GPU 코어를 활용해 병렬로 처리할 수 있게 해주는 기능입니다 [1]. CPU 기반 연산의 병목 현상을 해소하여 수백만 개의 파티클이나 대규모 복잡한 시뮬레이션을 실시간으로 처리할 수 있도록 돕습니다 [2, 3]. Three.js와 같은 라이브러리를 통해 접근성이 크게 향상되었으며, 대규모 데이터 필터링, 물리 시뮬레이션, GPU 주도 렌더링 등 고성능이 요구되는 작업에 필수적으로 사용됩니다 [1, 4]. @@ -24,11 +24,11 @@ github_commit: "[P-Reinforce] Continuous Worker - WebGPU Compute Shaders" - **정책 변화:** Graphics & Performance 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Storage Textures]], [[Indirect Draws]], [[TSL (Three Shader Language)]], [[Compute Skinning]] -- **Projects/Contexts:** [[Three.js r171+]] (WebGPURenderer 도입 및 TSL 통합으로 컴퓨트 셰이더 지원 [13-17]), [[BIM Datasets]] (대규모 데이터 필터링 및 병렬 처리 적용 맥락 [3]), [[Expo 2025 Osaka]] (100만 개 파티클 유체 시뮬레이션 적용 사례 [18, 19]) +- **Related Topics:** [[스토리지 텍스처(Storage Textures)|Storage Textures]], Indirect Draws, [[TSL (Three Shader Language)|TSL (Three Shader Language)]], Compute Skinning +- **Projects/Contexts:** Three.js r171+ (WebGPURenderer 도입 및 TSL 통합으로 컴퓨트 셰이더 지원 [13-17]), BIM Datasets (대규모 데이터 필터링 및 병렬 처리 적용 맥락 [3]), [[Expo 2025 Osaka|Expo 2025 Osaka]] (100만 개 파티클 유체 시뮬레이션 적용 사례 [18, 19]) - **Contradictions/Notes:** WebGL이나 WebGL2 환경에서는 컴퓨트 셰이더가 지원되지 않으며 WebGPU 환경에서만 동작합니다 [20]. Three.js의 TSL과 렌더러를 사용하면 비교적 쉽게 컴퓨트 셰이더를 구현할 수 있지만, 네이티브 WebGPU를 사용할 경우 더 세밀한 직접 제어 및 다중 패스 물리 연산 등이 가능한 대신 그래픽스 파이프라인에 대한 매우 높은 기술적 숙련도가 요구된다는 트레이드오프가 존재합니다 [1, 4, 10]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/WebGPU Compute Shaders.md]] +- Raw Source: 00_Raw/2026-04-20/WebGPU Compute Shaders.md --- diff --git a/01_Archive/2026-04-20/WebGPU Performance Profiling.md b/01_Archive/2026-04-20/WebGPU Performance Profiling.md index 1180e184..912cfe31 100644 --- a/01_Archive/2026-04-20/WebGPU Performance Profiling.md +++ b/01_Archive/2026-04-20/WebGPU Performance Profiling.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-A8AA46 -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - WebGPU Performance Profiling" --- -# [[WebGPU Performance Profiling]] +# [[WebGPU Performance Profiling|WebGPU Performance Profiling]] ## 📌 한 줄 통찰 (The Karpathy Summary) > WebGPU Performance Profiling은 WebGPU API를 활용하는 웹 애플리케이션에서 컴퓨트 및 렌더 패스 경계에서의 GPU 명령 실행 시간을 정밀하게 측정하고 분석하는 과정입니다 [1, 2]. 개발자는 이를 통해 성능 병목 현상을 식별하고 최적화할 수 있으나, 타이밍 기반의 보안 공격을 방지하기 위해 타임스탬프의 정밀도가 의도적으로 낮춰져(Quantization) 제공됩니다 [1, 3, 4]. 하드웨어 수준의 타이머 접근이 제한될 경우, 개발자는 브라우저 내부의 트레이싱 도구를 활용하여 시스템 수준의 프로파일링을 수행할 수 있습니다 [5, 6]. @@ -30,11 +30,11 @@ github_commit: "[P-Reinforce] Continuous Worker - WebGPU Performance Profiling" - **정책 변화:** Graphics & Performance 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Timestamp Queries]], [[Timing Attacks]], [[Chrome DevTools]] -- **Projects/Contexts:** [[High Resolution Time Spec]], [[Chromium WebGPU Implementation]] +- **Related Topics:** [[Timestamp Queries|Timestamp Queries]], [[Timing Attacks|Timing Attacks]], [[Chrome DevTools|Chrome DevTools]] +- **Projects/Contexts:** High Resolution Time Spec, [[Chromium WebGPU Implementation|Chromium WebGPU Implementation]] - **Contradictions/Notes:** WebGPU 사양 원문에서는 타이밍 공격에 대한 우려로 인해 타임스탬프 쿼리를 선택적(optional) 기능으로 명시하고 신뢰할 수 있는 환경으로 노출을 제한할 수 있다고 규정했습니다 [4, 16]. 하지만, GPU for the Web 커뮤니티 그룹은 개발자의 성능 프로파일링 요구를 충족하면서도 보안을 유지하기 위해, 해상도를 100 마이크로초로 낮추는 조건 하에 사이트 격리(site isolation) 여부와 상관없이 타임스탬프 쿼리를 허용하기로 합의했습니다 [9, 10]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/WebGPU Performance Profiling.md]] +- Raw Source: 00_Raw/2026-04-20/WebGPU Performance Profiling.md --- diff --git a/01_Archive/2026-04-20/WebGPU Timestamp Queries.md b/01_Archive/2026-04-20/WebGPU Timestamp Queries.md index fd1cbb57..962d9dcd 100644 --- a/01_Archive/2026-04-20/WebGPU Timestamp Queries.md +++ b/01_Archive/2026-04-20/WebGPU Timestamp Queries.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-1F8BE6 -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - WebGPU Timestamp Queries" --- -# [[WebGPU Timestamp Queries]] +# [[WebGPU Timestamp Queries|WebGPU Timestamp Queries]] ## 📌 한 줄 통찰 (The Karpathy Summary) > WebGPU Timestamp Queries는 WebGPU 애플리케이션이 컴퓨트(Compute) 및 렌더(Render) 패스의 경계 등에서 GPU 명령이 실행되는 데 걸리는 시간을 나노초 단위까지 정밀하게 측정할 수 있도록 지원하는 API 기능입니다 [1, 2]. 고해상도 타이머를 악용한 캐시 사이드 채널 공격(예: Spectre)을 방지하기 위해 브라우저 환경에서는 일반적으로 해상도를 100마이크로초로 제한하는 타임스탬프 양자화(Timestamp Quantization)가 적용됩니다 [3, 4]. 한편, 루트 주제인 '브라우저 메모리 할당 시점별 미세 지연 측정 사례'와 관련하여, 타임스탬프 쿼리를 직접적으로 메모리 할당 시점과 연계하여 측정한 구체적인 사례는 소스에 관련 정보가 부족합니다. @@ -20,11 +20,11 @@ github_commit: "[P-Reinforce] Continuous Worker - WebGPU Timestamp Queries" - **정책 변화:** Graphics & Performance 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Micro-latency]], [[Timestamp Quantization]], [[Timing Attacks (Spectre/Meltdown)]] -- **Projects/Contexts:** [[WebGPU Performance Profiling]], [[Browser Security Mitigations]] +- **Related Topics:** [[Micro-latency|Micro-latency]], [[Timestamp Quantization|Timestamp Quantization]], [[Timing Attacks (Spectre_Meltdown)|Timing Attacks (Spectre/Meltdown)]] +- **Projects/Contexts:** [[WebGPU Performance Profiling|WebGPU Performance Profiling]], [[Browser Security Mitigations|Browser Security Mitigations]] - **Contradictions/Notes:** 소스 [5]에서는 보안을 위해 비격리 컨텍스트(Non-isolated contexts)에서 타임스탬프 쿼리 기능을 아예 노출하지 않는 방향을 주장하지만, 소스 [6]에서는 GPU for the Web Community Group의 추후 합의를 통해 사이트 격리 여부와 무관하게 100마이크로초 해상도로 기능을 항상 허용하는 것으로 변경되었음을 보여줍니다. 또한 루트 주제에서 요구한 '브라우저 메모리 할당 시점별' 구체적 지연 측정 사례에 대해서는 소스에 관련 정보가 부족합니다. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/WebGPU Timestamp Queries.md]] +- Raw Source: 00_Raw/2026-04-20/WebGPU Timestamp Queries.md --- diff --git a/01_Archive/2026-04-20/WebGPU _ WebGL Timing API Security.md b/01_Archive/2026-04-20/WebGPU _ WebGL Timing API Security.md index 96883ddb..26e1b4d2 100644 --- a/01_Archive/2026-04-20/WebGPU _ WebGL Timing API Security.md +++ b/01_Archive/2026-04-20/WebGPU _ WebGL Timing API Security.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-B3C1E7 -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - WebGPU _ WebGL Timing API Security" --- -# [[WebGPU _ WebGL Timing API Security]] +# [[WebGPU _ WebGL Timing API Security|WebGPU _ WebGL Timing API Security]] ## 📌 한 줄 통찰 (The Karpathy Summary) > WebGPU와 WebGL의 타이밍 API는 GPU 명령어의 실행 시간을 측정하는 도구이지만, 높은 정밀도의 타이밍 데이터가 보안 취약점으로 악용될 수 있어 엄격한 보안 모델이 적용됩니다 [1-3]. 과거 WebGL의 `EXT_disjoint_timer_query`와 같은 확장 기능은 캐시 적중률 및 메모리 접근 패턴을 노출시켜 Spectre, Meltdown, Rowhammer 등의 부채널 공격(Side-channel attack)에 악용되었습니다 [2, 4, 5]. 이에 대응하여 브라우저 벤더들은 고정밀 타이머를 비활성화하거나, 시간의 정밀도를 의도적으로 낮추는 '양자화(Quantization)' 기법을 도입하여 보안과 성능 분석 간의 균형을 맞추고 있습니다 [2, 6, 7]. @@ -23,11 +23,11 @@ github_commit: "[P-Reinforce] Continuous Worker - WebGPU _ WebGL Timing API Secu - **정책 변화:** Graphics & Performance 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Spectre and Meltdown]], [[Cache Side-Channel Attack]], [[Timestamp Quantization]], [[Rowhammer Attack]] -- **Projects/Contexts:** [[Chrome / Blink WebGPU Implementation]], [[WebKit Security Mitigations]] +- **Related Topics:** [[Spectre and Meltdown|Spectre and Meltdown]], [[Cache Side-Channel Attack|Cache Side-Channel Attack]], [[Timestamp Quantization|Timestamp Quantization]], [[Rowhammer attack|Rowhammer Attack]] +- **Projects/Contexts:** [[Chrome _ Blink WebGPU Implementation|Chrome / Blink WebGPU Implementation]], [[WebKit Security Mitigations|WebKit Security Mitigations]] - **Contradictions/Notes:** 초기 WebGPU 보안 모델의 제안에서는 사이트 격리(Site Isolation) 여부에 따라 타임스탬프 노출 및 정밀도를 다르게 적용할 계획이었습니다(격리 컨텍스트에서는 100µs 해상도를 제공하고, 비격리 컨텍스트에서는 노출하지 않음) [3]. 그러나 브라우저 간 상호 운용성(Interop) 문제를 해결하기 위해, GPU for the Web 커뮤니티 그룹은 사이트 격리 여부와 무관하게 모든 상황에서 100 마이크로초(100µs) 해상도로 통일하여 허용하는 것으로 최종 합의를 변경했습니다 [17]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/WebGPU _ WebGL Timing API Security.md]] +- Raw Source: 00_Raw/2026-04-20/WebGPU _ WebGL Timing API Security.md --- diff --git a/01_Archive/2026-04-20/WebGPU 대규모 건설 뷰어.md b/01_Archive/2026-04-20/WebGPU 대규모 건설 뷰어.md index 5cea4648..e8d63f7e 100644 --- a/01_Archive/2026-04-20/WebGPU 대규모 건설 뷰어.md +++ b/01_Archive/2026-04-20/WebGPU 대규모 건설 뷰어.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-BF6C28 -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - WebGPU 대규모 건설 뷰어" --- -# [[WebGPU 대규모 건설 뷰어]] +# [[WebGPU 대규모 건설 뷰어|WebGPU 대규모 건설 뷰어]] ## 📌 한 줄 통찰 (The Karpathy Summary) > WebGPU 대규모 건설 뷰어는 WebGPU 기술을 활용하여 거대한 건축, 엔지니어링 및 건설 데이터(BIM 모델, LiDAR 포인트 클라우드 등)를 브라우저에서 실시간으로 렌더링하는 플랫폼입니다. 2026년 기준 500MB 미만의 모델이나 빠른 프로토타이핑에는 접근성이 높은 Three.js의 WebGPU가 주로 사용되며, 500MB를 초과하는 초대형 병원 캠퍼스, 공항 터미널 또는 복잡한 구조 시뮬레이션에는 강력한 제어력과 렌더 번들 기능을 갖춘 네이티브 WebGPU가 권장됩니다. 이 기술은 컴퓨트 셰이더 등을 통해 기존 WebGL 대비 드로우 콜 오버헤드를 획기적으로 줄이고 최대 100배 이상의 성능 향상을 제공합니다. @@ -25,11 +25,11 @@ github_commit: "[P-Reinforce] Continuous Worker - WebGPU 대규모 건설 뷰어 - **정책 변화:** Graphics & Performance 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Three.js WebGPU]], [[Native WebGPU]], [[BIM (Building Information Modeling)]], [[LiDAR Point Cloud]], [[Compute Shaders]], [[GPURenderBundles]] -- **Projects/Contexts:** [[Segments.ai]] (LiDAR 포인트 클라우드 레이블링 도구를 WebGPU로 전환하여 100배 성능 향상), [[Expo 2025 Osaka]] ("Waves of Connection" 설치물에서 4K 디스플레이에 100만 개 파티클을 지연 없이 실시간 렌더링) +- **Related Topics:** [[Threejs WebGPU 파티클 예제|Three.js WebGPU]], Native WebGPU, BIM (Building Information Modeling), LiDAR Point Cloud, [[Compute Shaders|Compute Shaders]], [[GPURenderBundles|GPURenderBundles]] +- **Projects/Contexts:** [[Segments.ai|Segments.ai]] (LiDAR 포인트 클라우드 레이블링 도구를 WebGPU로 전환하여 100배 성능 향상), [[Expo 2025 Osaka|Expo 2025 Osaka]] ("Waves of Connection" 설치물에서 4K 디스플레이에 100만 개 파티클을 지연 없이 실시간 렌더링) - **Contradictions/Notes:** Three.js의 WebGPU는 추상화 레이어를 통해 빠르고 쉬운 뷰어 개발을 가능하게 하지만, 고유한 객체가 10,000~20,000개를 초과할 경우 UBO(Uniform Buffer Object) 바인딩 오버헤드로 인해 프레임 저하(예: 15 FPS)가 발생할 수 있습니다. 반면 네이티브 WebGPU는 막대한 데이터도 원활하게 처리할 수 있으나, 파이프라인 및 셰이더에 대한 깊은 지식이 요구되어 개발 속도가 상대적으로 느립니다. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/WebGPU 대규모 건설 뷰어.md]] +- Raw Source: 00_Raw/2026-04-20/WebGPU 대규모 건설 뷰어.md --- diff --git a/01_Archive/2026-04-20/WebGPU.md b/01_Archive/2026-04-20/WebGPU.md index bddae76f..5f688c1d 100644 --- a/01_Archive/2026-04-20/WebGPU.md +++ b/01_Archive/2026-04-20/WebGPU.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-C06372 -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - WebGPU" --- -# [[WebGPU]] +# [[WebGPU|WebGPU]] ## 📌 한 줄 통찰 (The Karpathy Summary) > WebGPU는 웹 브라우저 환경에서 고성능 3D 그래픽 및 연산을 처리하기 위해 설계된 차세대 그래픽 API이다 [1]. 기존 WebGL의 한계를 극복하고 컴퓨트 셰이더(Compute Shaders), 직접적인 메모리 관리, 멀티스레딩 등 최신 하드웨어 기능을 웹에서 사용할 수 있게 해준다 [2, 3]. Three.js와 같은 라이브러리를 통해 쉽게 도입할 수 있으며, 특히 드로우 콜(Draw Call)이 집중된 씬이나 대규모 물리 연산에서 기존 WebGL 대비 비약적인 성능 향상을 제공한다 [4-6]. @@ -27,11 +27,11 @@ github_commit: "[P-Reinforce] Continuous Worker - WebGPU" - **정책 변화:** Graphics & Performance 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[WebGL]], [[Compute Shaders]], [[Three Shader Language (TSL)]], [[GPURenderBundles]], [[Draw Call]] -- **Projects/Contexts:** [[Three.js]], [[Segments.ai]], [[Expo 2025 Osaka]] +- **Related Topics:** [[WebGL|WebGL]], [[Compute Shaders|Compute Shaders]], [[Three Shader Language (TSL)|Three Shader Language (TSL)]], [[GPURenderBundles|GPURenderBundles]], [[Draw Call|Draw Call]] +- **Projects/Contexts:** [[Three.js|Three.js]], [[Segments.ai|Segments.ai]], [[Expo 2025 Osaka|Expo 2025 Osaka]] - **Contradictions/Notes:** Three.js의 WebGPU 렌더러는 개발 속도를 비약적으로 높여주고 사용이 쉽지만, 수만 개의 고유 객체를 처리할 때 발생하는 UBO(Uniform Buffer Object) 바인딩 오버헤드와 메타데이터 메모리 소비로 인해 초대규모 데이터셋(500MB 이상)에서는 Native WebGPU 성능에 미치지 못한다는 벤치마크 결과가 있다 [18-21]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/WebGPU.md]] +- Raw Source: 00_Raw/2026-04-20/WebGPU.md --- diff --git a/01_Archive/2026-04-20/WebKit Security Mitigations.md b/01_Archive/2026-04-20/WebKit Security Mitigations.md index 2226442b..db06fd87 100644 --- a/01_Archive/2026-04-20/WebKit Security Mitigations.md +++ b/01_Archive/2026-04-20/WebKit Security Mitigations.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-78AFAF -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - WebKit Security Mitigations" --- -# [[WebKit Security Mitigations]] +# [[WebKit Security Mitigations|WebKit Security Mitigations]] ## 📌 한 줄 통찰 (The Karpathy Summary) > WebKit Security Mitigations는 Spectre 및 Meltdown과 같은 CPU 추측 실행(Speculative Execution) 취약점으로부터 사용자를 보호하기 위해 WebKit 엔진에 도입된 보안 방어 전략입니다 [1], [2]. WebKit은 신뢰할 수 없는 JavaScript 코드를 실행해야 하므로 이러한 공격에 노출될 수 있으며, 이를 방지하기 위해 WebKit은 타이머 정밀도를 낮추고 분기 없는(Branchless) 보안 검사를 도입하는 두 가지 주요 방어 계층을 구축했습니다 [1], [3]. @@ -27,11 +27,11 @@ github_commit: "[P-Reinforce] Continuous Worker - WebKit Security Mitigations" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Spectre]], [[Meltdown]], [[Speculative Execution]], [[Branch Prediction]] -- **Projects/Contexts:** [[JavaScriptCore]], [[WebAssembly]] +- **Related Topics:** [[Spectre|Spectre]], [[Meltdown|Meltdown]], [[Speculative Execution|Speculative Execution]], [[Branch Prediction|Branch Prediction]] +- **Projects/Contexts:** [[JavaScriptCore|JavaScriptCore]], [[WebAssembly|WebAssembly]] - **Contradictions/Notes:** 제공된 소스 내에서 상충하는 주장이나 모순되는 정보는 발견되지 않았습니다. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/WebKit Security Mitigations.md]] +- Raw Source: 00_Raw/2026-04-20/WebKit Security Mitigations.md --- diff --git a/01_Archive/2026-04-20/WebKit.md b/01_Archive/2026-04-20/WebKit.md index c025ac2a..ebba7970 100644 --- a/01_Archive/2026-04-20/WebKit.md +++ b/01_Archive/2026-04-20/WebKit.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-84FEA9 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - WebKit" --- -# [[WebKit]] +# [[WebKit|WebKit]] ## 📌 한 줄 통찰 (The Karpathy Summary) > WebKit은 최신 웹사이트를 렌더링하기 위해 사용자의 프로세서에서 신뢰할 수 없는 JavaScript 및 WebAssembly 코드를 실행하도록 설계된 웹 브라우저 엔진입니다 [1]. 기존에는 신뢰할 수 없는 코드의 작업을 제어하고 보안 속성을 강제하기 위해 분기(branch) 명령에 크게 의존했습니다 [2]. 그러나 Spectre와 Meltdown 같은 프로세서 취약점이 발견되면서 기존의 분기 기반 보안 검사가 무력화되었고, 이에 대응하기 위해 방어 체계의 대대적인 개편을 진행하게 되었습니다 [1, 2]. @@ -26,11 +26,11 @@ github_commit: "[P-Reinforce] Continuous Worker - WebKit" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Spectre]], [[Meltdown]], [[JavaScriptCore]], [[Speculative execution]] -- **Projects/Contexts:** [[WebKit 취약점 완화(Security Mitigations)]] +- **Related Topics:** [[Spectre|Spectre]], [[Meltdown|Meltdown]], [[JavaScriptCore|JavaScriptCore]], [[Speculative Execution|Speculative execution]] +- **Projects/Contexts:** WebKit 취약점 완화(Security Mitigations) - **Contradictions/Notes:** 초기 도입된 인덱스 마스킹 기법은 길이를 다음 2의 거듭제곱으로 반올림해 마스크를 계산하는 방식을 사용하므로, 임의의 메모리 접근은 막지만 여전히 제한적인 범위 외(out-of-bounds) 읽기를 허용하는 한계가 존재합니다 [11]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/WebKit.md]] +- Raw Source: 00_Raw/2026-04-20/WebKit.md --- diff --git a/01_Archive/2026-04-20/WebSplatter (3D Gaussian Splatting).md b/01_Archive/2026-04-20/WebSplatter (3D Gaussian Splatting).md index 8d000a9a..07d116f7 100644 --- a/01_Archive/2026-04-20/WebSplatter (3D Gaussian Splatting).md +++ b/01_Archive/2026-04-20/WebSplatter (3D Gaussian Splatting).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-166181 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - WebSplatter (3D Gaussian Splatting)" --- -# [[WebSplatter (3D Gaussian Splatting)]] +# [[WebSplatter (3D Gaussian Splatting)|WebSplatter (3D Gaussian Splatting)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > WebSplatter는 이기종 웹 생태계를 위해 WebGPU를 기반으로 설계된 엔드투엔드(end-to-end) 3D 가우시안 스플래팅(3D Gaussian Splatting, 3DGS) 렌더링 파이프라인입니다. 기존 WebGL 기반 방식이 겪는 CPU 정렬의 병목 현상을 해결하기 위해 깊이 정렬과 뷰 적응형 평가를 모두 GPU 컴퓨트 셰이더로 이동시켰습니다. 글로벌 원자성(global atomics)이 부족한 WebGPU의 한계를 우회하는 '대기 없는 계층적 기수 정렬(wait-free hierarchical radix sort)'과 불투명도 인식 기하학 컬링을 도입하여 기존 웹 뷰어 대비 1.18배에서 4.5배의 렌더링 속도 향상과 뛰어난 메모리 효율성을 달성했습니다 [1-3]. @@ -30,11 +30,11 @@ github_commit: "[P-Reinforce] Continuous Worker - WebSplatter (3D Gaussian Splat - **정책 변화:** AI 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[WebGPU]], [[3D Gaussian Splatting]], [[Compute Shaders]], [[Radix Sort]] -- **Projects/Contexts:** [[Web-Based 3D Rendering]], [[Generative 3D Modeling]] +- **Related Topics:** [[WebGPU|WebGPU]], [[3D_Gaussian_Splatting|3D Gaussian Splatting]], [[Compute Shaders|Compute Shaders]], [[Radix Sort|Radix Sort]] +- **Projects/Contexts:** Web-Based 3D Rendering, Generative 3D Modeling - **Contradictions/Notes:** 소스에 따르면 기존 WebGL 뷰어는 CPU 정렬로 인해 대규모 장면에서 병목이 발생하고, 단순 네이티브 GPU 포팅 방식의 WebGPU 뷰어들은 '스핀 대기(spin-wait)' 구현으로 인해 스케줄링 순서가 보장되지 않는 하드웨어(예: Apple M1)에서 매우 심각한 성능 저하(busy-wait)를 겪습니다. WebSplatter는 자체적인 '대기 없는 기수 정렬(wait-free radix sort)' 알고리즘을 적용하여 이 문제를 완벽히 회피하였으며, 동일한 환경에서 기존 WebGPU 대비 4.5배 이상의 속도 향상을 입증했습니다 [22, 25]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/WebSplatter (3D Gaussian Splatting).md]] +- Raw Source: 00_Raw/2026-04-20/WebSplatter (3D Gaussian Splatting).md --- diff --git a/01_Archive/2026-04-20/Wellbeing-Science.md b/01_Archive/2026-04-20/Wellbeing-Science.md index 29bb11c4..72f73502 100644 --- a/01_Archive/2026-04-20/Wellbeing-Science.md +++ b/01_Archive/2026-04-20/Wellbeing-Science.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-59A0A3 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Wellbeing-Science" --- -# [[Wellbeing-Science]] +# [[Wellbeing-Science|Wellbeing-Science]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Wellbeing-Science" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Wellbeing-Science.md]] +- Raw Source: 00_Raw/2026-04-20/Wellbeing-Science.md --- diff --git a/01_Archive/2026-04-20/Wicked-Problems.md b/01_Archive/2026-04-20/Wicked-Problems.md index 5a9a6689..4c5bca70 100644 --- a/01_Archive/2026-04-20/Wicked-Problems.md +++ b/01_Archive/2026-04-20/Wicked-Problems.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-9805C7 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Wicked-Problems" --- -# [[Wicked-Problems]] +# [[Wicked-Problems|Wicked-Problems]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Wicked-Problems" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Wicked-Problems.md]] +- Raw Source: 00_Raw/2026-04-20/Wicked-Problems.md --- diff --git a/01_Archive/2026-04-20/Width-Subtyping.md b/01_Archive/2026-04-20/Width-Subtyping.md index a10c74f8..32590149 100644 --- a/01_Archive/2026-04-20/Width-Subtyping.md +++ b/01_Archive/2026-04-20/Width-Subtyping.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-20758B -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Width-Subtyping" --- -# [[Width-Subtyping]] +# [[Width-Subtyping|Width-Subtyping]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Width-Subtyping" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Width-Subtyping.md]] +- Raw Source: 00_Raw/2026-04-20/Width-Subtyping.md --- diff --git a/01_Archive/2026-04-20/Width-and-Depth-Subtyping.md b/01_Archive/2026-04-20/Width-and-Depth-Subtyping.md index a1fdf8ab..467cc7fb 100644 --- a/01_Archive/2026-04-20/Width-and-Depth-Subtyping.md +++ b/01_Archive/2026-04-20/Width-and-Depth-Subtyping.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-B088E5 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Width-and-Depth-Subtyping" --- -# [[Width-and-Depth-Subtyping]] +# [[Width-and-Depth-Subtyping|Width-and-Depth-Subtyping]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Width-and-Depth-Subtyping" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Width-and-Depth-Subtyping.md]] +- Raw Source: 00_Raw/2026-04-20/Width-and-Depth-Subtyping.md --- diff --git a/01_Archive/2026-04-20/Wikidata.md b/01_Archive/2026-04-20/Wikidata.md index 3ddcba17..b095bb1d 100644 --- a/01_Archive/2026-04-20/Wikidata.md +++ b/01_Archive/2026-04-20/Wikidata.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-244AE9 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Wikidata" --- -# [[Wikidata]] +# [[Wikidata|Wikidata]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Wikidata" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Wikidata.md]] +- Raw Source: 00_Raw/2026-04-20/Wikidata.md --- diff --git a/01_Archive/2026-04-20/Winning Ways for your Mathematical Plays.md b/01_Archive/2026-04-20/Winning Ways for your Mathematical Plays.md index c33aa248..7b106f0b 100644 --- a/01_Archive/2026-04-20/Winning Ways for your Mathematical Plays.md +++ b/01_Archive/2026-04-20/Winning Ways for your Mathematical Plays.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-A3A3FC -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Winning Ways for your Mathematical Plays" --- -# [[Winning Ways for your Mathematical Plays]] +# [[Winning Ways for your Mathematical Plays|Winning Ways for your Mathematical Plays]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Winning Ways for your Mathemat ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Winning Ways for your Mathematical Plays.md]] +- Raw Source: 00_Raw/2026-04-20/Winning Ways for your Mathematical Plays.md --- diff --git a/01_Archive/2026-04-20/Wonderland Engine.md b/01_Archive/2026-04-20/Wonderland Engine.md index 5eb9c9d4..d9a9e756 100644 --- a/01_Archive/2026-04-20/Wonderland Engine.md +++ b/01_Archive/2026-04-20/Wonderland Engine.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-F85BEF -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Wonderland Engine" --- -# [[Wonderland Engine]] +# [[Wonderland Engine|Wonderland Engine]] ## 📌 한 줄 통찰 (The Karpathy Summary) > Wonderland Engine(원더랜드 엔진)은 웹 환경을 위한 차세대 고성능 3D 엔진입니다 [1]. 이 엔진은 프로덕션 수준의 성능으로 제품 구성기, 시각화 및 대화형 3D 경험을 구축할 수 있도록 설계되었습니다 [1]. WebGL 성능 최적화 원칙을 극한으로 적용하여, 개발자가 성능 병목 현상을 고민하지 않고 프로젝트 자체에만 집중할 수 있는 환경을 제공합니다 [2]. @@ -23,11 +23,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Wonderland Engine" - **정책 변화:** Graphics & Performance 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[WebGL]], [[WebXR]], [[Draw Calls]], [[Batching]] -- **Projects/Contexts:** [[Interactive 3D Experiences]] +- **Related Topics:** [[WebGL|WebGL]], WebXR, Draw Calls, [[Batching|Batching]] +- **Projects/Contexts:** Interactive 3D Experiences - **Contradictions/Notes:** 소스에 모순되는 내용은 없으나, WebGL이 복잡한 3D 그래픽을 렌더링하기에 느리다는 개발자들의 일반적인 오해와 달리, Wonderland Engine은 극한의 엔진 최적화(드로우 콜 최소화 등)를 통해 웹에서도 압도적인 3D 렌더링 성능을 낼 수 있음을 보여줍니다 [4, 9]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Wonderland Engine.md]] +- Raw Source: 00_Raw/2026-04-20/Wonderland Engine.md --- diff --git a/01_Archive/2026-04-20/Work-Engagement-Models.md b/01_Archive/2026-04-20/Work-Engagement-Models.md index d528ac7b..60288cc6 100644 --- a/01_Archive/2026-04-20/Work-Engagement-Models.md +++ b/01_Archive/2026-04-20/Work-Engagement-Models.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-CBB42F -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Work-Engagement-Models" --- -# [[Work-Engagement-Models]] +# [[Work-Engagement-Models|Work-Engagement-Models]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Work-Engagement-Models" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Work-Engagement-Models.md]] +- Raw Source: 00_Raw/2026-04-20/Work-Engagement-Models.md --- diff --git a/01_Archive/2026-04-20/World of Warcraft (Gold Sink Mechanics).md b/01_Archive/2026-04-20/World of Warcraft (Gold Sink Mechanics).md index bb57531a..4d763a16 100644 --- a/01_Archive/2026-04-20/World of Warcraft (Gold Sink Mechanics).md +++ b/01_Archive/2026-04-20/World of Warcraft (Gold Sink Mechanics).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-DA62AF -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - World of Warcraft (Gold Sink Mechanics)" --- -# [[World of Warcraft (Gold Sink Mechanics)]] +# [[World of Warcraft (Gold Sink Mechanics)|World of Warcraft (Gold Sink Mechanics)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - World of Warcraft (Gold Sink M ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/World of Warcraft (Gold Sink Mechanics).md]] +- Raw Source: 00_Raw/2026-04-20/World of Warcraft (Gold Sink Mechanics).md --- diff --git a/01_Archive/2026-04-20/Write Barrier.md b/01_Archive/2026-04-20/Write Barrier.md index c87ace90..202af3fb 100644 --- a/01_Archive/2026-04-20/Write Barrier.md +++ b/01_Archive/2026-04-20/Write Barrier.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-2240C5 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Write Barrier" --- -# [[Write Barrier]] +# [[Write Barrier|Write Barrier]] ## 📌 한 줄 통찰 (The Karpathy Summary) > Write Barrier(쓰기 장벽)는 가비지 컬렉션(GC) 시스템에서 객체에 새로운 포인터(참조)가 저장될 때마다 이를 감지하고 기록하기 위해 실행되는 짧은 코드 조각입니다 [1]. 주로 구 세대(Old-space) 객체가 신규 세대(New-space) 객체를 참조하는 것을 추적하거나, 점진적/동시성 마킹(Incremental/Concurrent marking) 중에 변경된 객체 그래프를 추적하는 데 필수적으로 사용됩니다 [1-3]. 이를 통해 가비지 컬렉터가 메모리 힙 전체를 무거운 비용으로 스캔하지 않고도 살아있는 객체를 정확하고 빠르게 식별할 수 있도록 돕습니다 [4, 5]. @@ -22,11 +22,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Write Barrier" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Garbage Collection]], [[Store Buffer]], [[Incremental Marking]], [[Concurrent Marking]], [[Scavenge]] -- **Projects/Contexts:** [[V8 JavaScript Engine]], [[IBM Eclipse OpenJ9]] +- **Related Topics:** [[Garbage Collection|Garbage Collection]], Store Buffer, [[Incremental Marking|Incremental Marking]], Concurrent Marking, [[Scavenge|Scavenge]] +- **Projects/Contexts:** [[V8 JavaScript Engine|V8 JavaScript Engine]], IBM Eclipse OpenJ9 - **Contradictions/Notes:** 소스에 관련 정보가 부족합니다. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/Write Barrier.md]] +- Raw Source: 00_Raw/2026-04-20/Write Barrier.md --- diff --git a/01_Archive/2026-04-20/XState-Library.md b/01_Archive/2026-04-20/XState-Library.md index 620aa913..25a77cbc 100644 --- a/01_Archive/2026-04-20/XState-Library.md +++ b/01_Archive/2026-04-20/XState-Library.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-7C6A30 -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - XState-Library" --- -# [[XState-Library]] +# [[XState-Library|XState-Library]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - XState-Library" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/XState-Library.md]] +- Raw Source: 00_Raw/2026-04-20/XState-Library.md --- diff --git a/01_Archive/2026-04-20/Zod 런타임 유효성 검사 통합.md b/01_Archive/2026-04-20/Zod 런타임 유효성 검사 통합.md index 1abd9c70..229c4785 100644 --- a/01_Archive/2026-04-20/Zod 런타임 유효성 검사 통합.md +++ b/01_Archive/2026-04-20/Zod 런타임 유효성 검사 통합.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-FD8703 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Zod 런타임 유효성 검사 통합" --- -# [[Zod 런타임 유효성 검사 통합]] +# [[Zod 런타임 유효성 검사 통합|Zod 런타임 유효성 검사 통합]] ## 📌 한 줄 통찰 (The Karpathy Summary) > Zod는 TypeScript 환경에서 런타임 유효성 검사를 수행하여 시스템의 데이터 무결성을 보장하는 데 사용되는 검증 라이브러리입니다. 컴파일 타임에만 동작하는 TypeScript의 한계를 보완하여, API 응답이나 외부 설정 파일과 같이 타입을 강제할 수 없는 외부 데이터를 안전하게 처리합니다. 주로 '검증하지 말고 파싱하라(Parse, don't validate)'는 철학을 바탕으로, 알 수 없는(unknown) 데이터를 시스템 경계에서 신뢰할 수 있는 타입으로 파싱하는 역할을 합니다. @@ -27,11 +27,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Zod 런타임 유효성 검사 - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Parse, don't validate]], [[브랜디드 타입(Branded Types)]], [[식별 가능한 유니온(Discriminated Unions)]] -- **Projects/Contexts:** [[외부 API 응답 및 설정 파일 처리]], [[런타임 상태 및 데이터 무결성 검증]] +- **Related Topics:** [[Parse, don't validate|Parse, don't validate]], [[브랜디드 타입(Branded Types)|브랜디드 타입(Branded Types)]], [[식별 가능한 유니온(Discriminated Unions)|식별 가능한 유니온(Discriminated Unions)]] +- **Projects/Contexts:** 외부 API 응답 및 설정 파일 처리, 런타임 상태 및 데이터 무결성 검증 - **Contradictions/Notes:** Zod 유효성 검사 도입 시 발생할 수 있는 구체적인 성능 저하 수치나 이와 대립되는 다른 라이브러리(예: Joi, Yup 등)와의 직접적인 비교에 대해서는 소스에 관련 정보가 부족합니다. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/Zod 런타임 유효성 검사 통합.md]] +- Raw Source: 00_Raw/2026-04-20/Zod 런타임 유효성 검사 통합.md --- diff --git a/01_Archive/2026-04-20/Zod 파싱과 브랜디드 타입을 결합한 런타임 데이터 검증.md b/01_Archive/2026-04-20/Zod 파싱과 브랜디드 타입을 결합한 런타임 데이터 검증.md index 30802a10..41f2b921 100644 --- a/01_Archive/2026-04-20/Zod 파싱과 브랜디드 타입을 결합한 런타임 데이터 검증.md +++ b/01_Archive/2026-04-20/Zod 파싱과 브랜디드 타입을 결합한 런타임 데이터 검증.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-725C86 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Zod 파싱과 브랜디드 타입을 결합한 런타임 데이터 검증" --- -# [[Zod 파싱과 브랜디드 타입을 결합한 런타임 데이터 검증]] +# [[Zod 파싱과 브랜디드 타입을 결합한 런타임 데이터 검증|Zod 파싱과 브랜디드 타입을 결합한 런타임 데이터 검증]] ## 📌 한 줄 통찰 (The Karpathy Summary) > Zod 파싱과 브랜디드 타입을 결합한 런타임 데이터 검증은 시스템 경계에서 신뢰할 수 없는 데이터를 안전하고 구체적인 타입으로 변환하는 강력한 설계 기법입니다 [1-3]. 이 기법은 "검증하지 말고 파싱하라(Parse, Don't Validate)"는 철학을 바탕으로, Zod를 통해 런타임에 데이터를 검증함과 동시에 컴파일 타임의 고유한 브랜디드 타입을 부여합니다 [4]. 이를 통해 런타임 환경의 구조적 무결성과 컴파일 타임의 엄격한 타입 안전성을 한 번에 확보할 수 있습니다 [3-5]. @@ -24,11 +24,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Zod 파싱과 브랜디드 타 - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Parse, don't validate]], [[Branded Types]], [[Opaque Types]], [[Zod]] +- **Related Topics:** [[Parse, don't validate|Parse, don't validate]], [[Branded Types|Branded Types]], [[Opaque Types|Opaque Types]], [[Zod|Zod]] - **Projects/Contexts:** 도메인 기반 설계(DDD)에서의 데이터 오염 방지(예: UserId와 OrderId의 엄격한 분리), 외부 API 응답 및 사용자 입력 등 시스템 경계면에서의 런타임 검증 [3, 4, 8, 10] - **Contradictions/Notes:** Zod와의 결합을 반대하는 내용은 없으나, 브랜디드 타입과 같은 타입 시스템 기능은 코드 작업에 개념적 복잡성을 추가하므로, 개발자가 애플리케이션에서 직면한 실제 문제에 실질적인 이점을 제공하는지 먼저 신중히 평가한 뒤 도입해야 합니다 [11, 12]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/Zod 파싱과 브랜디드 타입을 결합한 런타임 데이터 검증.md]] +- Raw Source: 00_Raw/2026-04-20/Zod 파싱과 브랜디드 타입을 결합한 런타임 데이터 검증.md --- diff --git a/01_Archive/2026-04-20/Zod-Runtime-Validation.md b/01_Archive/2026-04-20/Zod-Runtime-Validation.md index 063a2214..1718a8e4 100644 --- a/01_Archive/2026-04-20/Zod-Runtime-Validation.md +++ b/01_Archive/2026-04-20/Zod-Runtime-Validation.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-869303 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Zod-Runtime-Validation" --- -# [[Zod-Runtime-Validation]] +# [[Zod-Runtime-Validation|Zod-Runtime-Validation]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Zod-Runtime-Validation" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Zod-Runtime-Validation.md]] +- Raw Source: 00_Raw/2026-04-20/Zod-Runtime-Validation.md --- diff --git a/01_Archive/2026-04-20/Zod-Schema-Validation.md b/01_Archive/2026-04-20/Zod-Schema-Validation.md index ffbe16b3..c77378f3 100644 --- a/01_Archive/2026-04-20/Zod-Schema-Validation.md +++ b/01_Archive/2026-04-20/Zod-Schema-Validation.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-1B08D2 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Zod-Schema-Validation" --- -# [[Zod-Schema-Validation]] +# [[Zod-Schema-Validation|Zod-Schema-Validation]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - Zod-Schema-Validation" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/Zod-Schema-Validation.md]] +- Raw Source: 00_Raw/2026-04-20/Zod-Schema-Validation.md --- diff --git a/01_Archive/2026-04-20/Zod.md b/01_Archive/2026-04-20/Zod.md index 607eda95..e360936e 100644 --- a/01_Archive/2026-04-20/Zod.md +++ b/01_Archive/2026-04-20/Zod.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-DB4331 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Zod" --- -# [[Zod]] +# [[Zod|Zod]] ## 📌 한 줄 통찰 (The Karpathy Summary) > Zod는 TypeScript 및 JavaScript 환경에서 런타임 검증(Runtime validation)을 수행하기 위해 널리 사용되는 인기 있는 유효성 검사 라이브러리입니다 [1, 2]. API 응답이나 외부 구성 파일처럼 TypeScript의 정적 타입 시스템이 런타임에 도움을 줄 수 없는 외부 데이터를 다룰 때, 타입 안정성을 확보하는 데 핵심적인 역할을 합니다 [1]. 단순히 유효성을 검사하는 것에 그치지 않고, 알 수 없는 데이터를 잘 정의된 타입으로 '파싱(Parsing)'하여 시스템 내부를 안전하게 보호하는 도구로 활용됩니다 [3, 4]. @@ -23,11 +23,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Zod" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Runtime Validation]], [[Branded Types]], [[Discriminated Unions]], [[Parse, don't validate]] -- **Projects/Contexts:** [[External Data Handling]], [[TypeScript Type Safety]] +- **Related Topics:** [[런타임 상태 검증(Runtime Validation)|Runtime Validation]], [[Branded Types|Branded Types]], [[Discriminated Unions|Discriminated Unions]], [[Parse, don't validate|Parse, don't validate]] +- **Projects/Contexts:** External Data Handling, [[TypeScript_Type_Safety|TypeScript Type Safety]] - **Contradictions/Notes:** 소스 내에서 Zod에 대한 모순된 주장은 발견되지 않습니다. 대신, 정적 타입 언어인 TypeScript가 갖는 런타임 데이터 검증의 사각지대를 보완하는 매우 효과적이고 권장되는 라이브러리로 일관되게 소개됩니다 [1-4]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/Zod.md]] +- Raw Source: 00_Raw/2026-04-20/Zod.md --- diff --git a/01_Archive/2026-04-20/Zod를 활용한 런타임 데이터 파싱.md b/01_Archive/2026-04-20/Zod를 활용한 런타임 데이터 파싱.md index bae479da..2f20bddc 100644 --- a/01_Archive/2026-04-20/Zod를 활용한 런타임 데이터 파싱.md +++ b/01_Archive/2026-04-20/Zod를 활용한 런타임 데이터 파싱.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-4215D8 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Zod를 활용한 런타임 데이터 파싱" --- -# [[Zod를 활용한 런타임 데이터 파싱]] +# [[Zod를 활용한 런타임 데이터 파싱|Zod를 활용한 런타임 데이터 파싱]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -30,11 +30,11 @@ github_commit: "[P-Reinforce] Continuous Worker - Zod를 활용한 런타임 데 - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Parse, don't validate]], [[브랜디드 타입(Branded Types)]], [[식별 가능한 유니온(Discriminated Unions)]] -- **Projects/Contexts:** [[외부 API 데이터 및 설정 파일 처리]], [[런타임 상태 검증(Runtime Validation)]] +- **Related Topics:** [[Parse, don't validate|Parse, don't validate]], [[브랜디드 타입(Branded Types)|브랜디드 타입(Branded Types)]], [[식별 가능한 유니온(Discriminated Unions)|식별 가능한 유니온(Discriminated Unions)]] +- **Projects/Contexts:** [[외부 API 데이터 및 설정 파일 처리|외부 API 데이터 및 설정 파일 처리]], [[런타임 상태 검증(Runtime Validation)|런타임 상태 검증(Runtime Validation)]] - **Contradictions/Notes:** 소스에 관련 정보가 부족합니다. (제공된 소스 내에서 Zod 활용에 대한 상충되는 의견이나 모순점은 발견되지 않았습니다.) --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/Zod를 활용한 런타임 데이터 파싱.md]] +- Raw Source: 00_Raw/2026-04-20/Zod를 활용한 런타임 데이터 파싱.md --- diff --git a/01_Archive/2026-04-20/Zustand-Based-Mission-Persistence.md b/01_Archive/2026-04-20/Zustand-Based-Mission-Persistence.md index 097ef8fd..afc788d8 100644 --- a/01_Archive/2026-04-20/Zustand-Based-Mission-Persistence.md +++ b/01_Archive/2026-04-20/Zustand-Based-Mission-Persistence.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-E45B33 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - Zustand-Based-Mission-Persistence" --- -# [[Zustand-Based-Mission-Persistence]] +# [[Zustand-Based-Mission-Persistence|Zustand-Based-Mission-Persistence]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 장시간 지속되는 지식 탐사 미션의 안정성을 보장하기 위해 도입된 상태 유지 로직입니다. Zustand 라이브러리와 로컬 스토리지를 활용하여, 브라우저 종료나 네트워크 장애 시에도 현재의 작업 큐, 완료 목록, 그리고 진행 중인 NotebookLM 태스크 정보를 즉시 복구합니다. @@ -30,8 +30,8 @@ github_commit: "[P-Reinforce] Continuous Worker - Zustand-Based-Mission-Persiste - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Autonomous-Loop-State-Machine]], [[NotebookLM-Automated-Authentication-CLI]] -- **Projects/Contexts:** [[P-Reinforce-Agent-v2.6]] +- **Related Topics:** Autonomous-Loop-State-Machine, [[NotebookLM-Automated-Authentication-CLI|NotebookLM-Automated-Authentication-CLI]] +- **Projects/Contexts:** P-Reinforce-Agent-v2.6 - **Contradictions/Notes:** 로컬 스토리지의 용량 제한(약 5MB)에 유의해야 하며, 큐가 수만 개로 늘어날 경우 별도의 DB 연동을 고려해야 합니다. -- Raw Source: [[00_Raw/2026-04-20/Zustand-Based-Mission-Persistence.md]] +- Raw Source: 00_Raw/2026-04-20/Zustand-Based-Mission-Persistence.md --- diff --git a/01_Archive/2026-04-20/[[Cluster A b/01_Archive/2026-04-20/[[Cluster A deleted file mode 100644 index e69de29b..00000000 diff --git a/01_Archive/2026-04-20/[[Cluster E b/01_Archive/2026-04-20/[[Cluster E deleted file mode 100644 index e69de29b..00000000 diff --git a/01_Archive/2026-04-20/_뇌와 팔다리의 분리_ - 관심사의 분리 (Separation of Concerns).md b/01_Archive/2026-04-20/_뇌와 팔다리의 분리_ - 관심사의 분리 (Separation of Concerns).md index 16099af8..d780851b 100644 --- a/01_Archive/2026-04-20/_뇌와 팔다리의 분리_ - 관심사의 분리 (Separation of Concerns).md +++ b/01_Archive/2026-04-20/_뇌와 팔다리의 분리_ - 관심사의 분리 (Separation of Concerns).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-53B106 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - _뇌와 팔다리의 분리_ - 관심사의 분리 (Separation of Concerns)" --- -# [[_뇌와 팔다리의 분리_ - 관심사의 분리 (Separation of Concerns)]] +# [[_뇌와 팔다리의 분리_ - 관심사의 분리 (Separation of Concerns)|_뇌와 팔다리의 분리_ - 관심사의 분리 (Separation of Concerns)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -38,11 +38,11 @@ github_commit: "[P-Reinforce] Continuous Worker - _뇌와 팔다리의 분리_ - - **정책 변화:** AI 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[관심사의 분리 (Separation of Concerns)]], [[단일 책임 원칙 (SRP)]], [[의존성 역전 (Dependency Inversion)]] -- **Projects/Contexts:** [[클린 아키텍처 (Clean Architecture)]], [[계층화 아키텍처 (Layered Architecture)]], [[도메인 주도 설계 (DDD)]] +- **Related Topics:** [[관심사의 분리 (Separation of Concerns)|관심사의 분리 (Separation of Concerns)]], [[단일 책임 원칙 (SRP)|단일 책임 원칙 (SRP)]], [[의존성 역전 (Dependency Inversion)|의존성 역전 (Dependency Inversion)]] +- **Projects/Contexts:** [[클린 아키텍처 (Clean Architecture)|클린 아키텍처 (Clean Architecture)]], [[계층화 아키텍처 (Layered Architecture)|계층화 아키텍처 (Layered Architecture)]], [[도메인 주도 설계 (DDD)|도메인 주도 설계 (DDD)]] - **Contradictions/Notes:** 소스에 명시적인 모순점은 없으나, "뇌와 팔다리의 분리"와 같은 관심사의 분리 원칙을 맹목적으로 추구할 경우 함수 호출의 뎁스가 깊어지고 성능 오버헤드나 통신 비용이 증가할 수 있다고 경고합니다 [5]. 너무 많은 레이어와 추상화는 개발자를 미궁에 빠뜨리는 오버엔지니어링이 될 수 있으므로, 응집도와 결합도를 잣대로 최적의 분리 지점을 모색하는 절제가 필요합니다 [6, 7]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/_뇌와 팔다리의 분리_ - 관심사의 분리 (Separation of Concerns).md]] +- Raw Source: 00_Raw/2026-04-20/_뇌와 팔다리의 분리_ - 관심사의 분리 (Separation of Concerns).md --- diff --git a/01_Archive/2026-04-20/agargaro의 오픈 소스 라이브러리.md b/01_Archive/2026-04-20/agargaro의 오픈 소스 라이브러리.md index 89e7f7fb..a5fbdbc0 100644 --- a/01_Archive/2026-04-20/agargaro의 오픈 소스 라이브러리.md +++ b/01_Archive/2026-04-20/agargaro의 오픈 소스 라이브러리.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-B271A4 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - agargaro의 오픈 소스 라이브러리" --- -# [[agargaro의 오픈 소스 라이브러리]] +# [[agargaro의 오픈 소스 라이브러리|agargaro의 오픈 소스 라이브러리]] ## 📌 한 줄 통찰 (The Karpathy Summary) > agargaro가 개발한 오픈 소스 라이브러리는 주로 Three.js의 기본 `InstancedMesh` 성능과 기능을 획기적으로 확장한 `InstancedMesh2`를 지칭합니다 [1, 2]. 이 라이브러리는 개별 인스턴스 단위의 절두체 컬링(Frustum Culling), LOD(Level of Detail), 가시성(Visibility) 관리 및 BVH를 활용한 빠른 레이캐스팅 기능을 제공하여 대규모 3D 렌더링 성능을 최적화합니다 [2, 3]. 이 밖에도 `BatchedMesh`를 위한 확장 라이브러리인 `batched-mesh-extensions`를 제공하여 오픈 월드 수준의 환경 구현을 돕고 있습니다 [4, 5]. @@ -34,11 +34,11 @@ github_commit: "[P-Reinforce] Continuous Worker - agargaro의 오픈 소스 라 - **정책 변화:** AI 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[InstancedMesh2]], [[Frustum Culling]], [[LOD(Level of Detail)]], [[BVH(Bounding Volume Hierarchy)]], [[BatchedMesh]] -- **Projects/Contexts:** [[20k skinned instances 데모]], [[batched-mesh-extensions]] +- **Related Topics:** [[InstancedMesh2|InstancedMesh2]], [[Frustum Culling|Frustum Culling]], [[가변적 LOD(Level of Detail) 시스템|LOD(Level of Detail)]], BVH(Bounding Volume Hierarchy), [[BatchedMesh|BatchedMesh]] +- **Projects/Contexts:** 20k skinned instances 데모, batched-mesh-extensions - **Contradictions/Notes:** 애니메이션 최적화 기법 중 뼈대 텍스처(Bone texture)의 부분 업데이트 기능이 있으나, 일부 모바일 기기 및 Firefox 브라우저에서는 해당 연산이 오히려 느리게 동작하여(이중 버퍼링 구현 필요) 기본적으로 비활성화해 두는 등 플랫폼 간 성능 편차가 존재합니다 [1, 13]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/agargaro의 오픈 소스 라이브러리.md]] +- Raw Source: 00_Raw/2026-04-20/agargaro의 오픈 소스 라이브러리.md --- diff --git a/01_Archive/2026-04-20/as const Assertion.md b/01_Archive/2026-04-20/as const Assertion.md index 1007a180..d170c17c 100644 --- a/01_Archive/2026-04-20/as const Assertion.md +++ b/01_Archive/2026-04-20/as const Assertion.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-CAF879 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.95 tags: [] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Mega Batch 2 - Wikified as const Assertion" --- -# [[as const Assertion]] +# [[as const Assertion|as const Assertion]] ## 📌 한 줄 통찰 (The Karpathy Summary) > `as const` Assertion은 TypeScript에서 값을 깊은 읽기 전용(deeply readonly) 상태로 만들고 타입을 해당 리터럴 값으로 좁히는(narrow) 기능입니다 [1]. 이를 통해 객체나 배열이 변경되지 않도록 컴파일 타임에 보장하며, 더 정확한 타입 추론을 가능하게 합니다 [1, 2]. 주로 절대 변경되어서는 안 되는 구성(configuration) 객체나 조회 테이블(lookup tables)을 정의할 때 유용하게 사용됩니다 [2]. @@ -22,11 +22,11 @@ github_commit: "[P-Reinforce] Mega Batch 2 - Wikified as const Assertion" - **정책 변화:** Programming & Language 카테고리의 전문성 확보 및 링크 밀도 최적화. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Readonly]], [[Literal Types]], [[Satisfies Operator]] -- **Projects/Contexts:** [[Configuration Objects]], [[Lookup Tables]] +- **Related Topics:** [[Readonly 유틸리티 타입|Readonly]], [[리터럴 타입 (Literal Types)|Literal Types]], [[Satisfies Operator|Satisfies Operator]] +- **Projects/Contexts:** Configuration Objects, Lookup Tables - **Contradictions/Notes:** 제공된 소스에서 `as const`에 대한 단독 설명은 다소 간략하며 정보가 부족한 편이지만, `satisfies` 연산자와 결합할 때 불변의 타입 안전 객체(immutable, type-safe objects)를 생성하는 핵심적인 역할을 한다는 점이 뚜렷하게 강조됩니다 [1-3]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/as const Assertion.md]] +- Raw Source: 00_Raw/2026-04-20/as const Assertion.md --- diff --git a/01_Archive/2026-04-20/as const.md b/01_Archive/2026-04-20/as const.md index a858cb9e..83481b7d 100644 --- a/01_Archive/2026-04-20/as const.md +++ b/01_Archive/2026-04-20/as const.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-701C2F -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - as const" --- -# [[as const]] +# [[as const|as const]] ## 📌 한 줄 통찰 (The Karpathy Summary) > `as const`는 TypeScript에서 값을 깊은 수준의 읽기 전용(deeply readonly)으로 만들고, 해당 타입을 구체적인 리터럴 값으로 좁히는(narrows types to their literal values) 데 사용되는 단언(assertion) 문법입니다 [1]. 객체나 배열 등이 변경되지 않도록 컴파일 타임 검증과 런타임 불변성을 동시에 확보할 때 유용하게 쓰입니다 [2]. 특히 구성(configuration) 객체나 룩업 테이블을 정의할 때 다른 연산자와 결합하여 매우 강력하고 안전한 타입 패턴을 형성합니다 [2, 3]. @@ -30,11 +30,11 @@ github_commit: "[P-Reinforce] Continuous Worker - as const" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[satisfies]], [[readonly]], [[Literal Types]], [[Type Narrowing]] -- **Projects/Contexts:** [[TypeScript 구성(configuration) 객체 및 룩업 테이블 모델링]], [[불변성(Immutability) 보장 패턴]] +- **Related Topics:** [[satisfies 연산자|satisfies]], [[readonly|readonly]], [[리터럴 타입 (Literal Types)|Literal Types]], [[Type Narrowing|Type Narrowing]] +- **Projects/Contexts:** TypeScript 구성(configuration) 객체 및 룩업 테이블 모델링, 불변성(Immutability) 보장 패턴 - **Contradictions/Notes:** 소스 상에 명시적인 모순은 없으나, 타입 추론과 타입 가드를 위해 관행적으로 `as const`를 붙여 쓰던 것을 특정 패턴 도입을 통해 생략할 수도 있다는 개발자 커뮤니티의 코멘트가 존재합니다 [5]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/as const.md]] +- Raw Source: 00_Raw/2026-04-20/as const.md --- diff --git a/01_Archive/2026-04-20/bitECS와 SharedArrayBuffer를 결합한 멀티스레드 고성능 아키텍처.md b/01_Archive/2026-04-20/bitECS와 SharedArrayBuffer를 결합한 멀티스레드 고성능 아키텍처.md index e8312863..c3075665 100644 --- a/01_Archive/2026-04-20/bitECS와 SharedArrayBuffer를 결합한 멀티스레드 고성능 아키텍처.md +++ b/01_Archive/2026-04-20/bitECS와 SharedArrayBuffer를 결합한 멀티스레드 고성능 아키텍처.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-33DDD3 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - bitECS와 SharedArrayBuffer를 결합한 멀티스레드 고성능 아키텍처" --- -# [[bitECS와 SharedArrayBuffer를 결합한 멀티스레드 고성능 아키텍처]] +# [[bitECS와 SharedArrayBuffer를 결합한 멀티스레드 고성능 아키텍처|bitECS와 SharedArrayBuffer를 결합한 멀티스레드 고성능 아키텍처]] ## 📌 한 줄 통찰 (The Karpathy Summary) > `bitECS`의 데이터 지향 설계(SoA) 구조와 `SharedArrayBuffer`의 무복사(Zero-Copy) 메모리 공유 기능을 결합하여, 메인 스레드의 렌더링 블로킹 없이 웹 워커에서 수만 개의 엔티티를 병렬 연산하고 실시간으로 동기화하는 초고성능 웹 게임 엔진 아키텍처입니다. @@ -29,12 +29,12 @@ github_commit: "[P-Reinforce] Continuous Worker - bitECS와 SharedArrayBuffer를 - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Data-Oriented Design (DOD)]], [[Structure of Arrays (SoA)]], [[Web Worker 멀티스레딩]], [[React Three Fiber (R3F) 최적화]], [[메모리 파편화 방지 및 객체 풀링]] -- **Projects/Contexts:** [[브라우저 기반 AAA급 멀티스레드 3D 게임]], [[수만 개의 엔티티가 존재하는 실시간 물리 시뮬레이션]] +- **Related Topics:** Data-Oriented Design (DOD), Structure of Arrays (SoA), Web Worker 멀티스레딩, React Three Fiber (R3F) 최적화, 메모리 파편화 방지 및 객체 풀링 +- **Projects/Contexts:** 브라우저 기반 AAA급 멀티스레드 3D 게임, 수만 개의 엔티티가 존재하는 실시간 물리 시뮬레이션 - **Contradictions/Notes:** 원시 이진 데이터인 `SharedArrayBuffer`를 직접 다루는 것은 로우 레벨 개발 지식이 필요해 매우 까다롭습니다. 하지만 `bitECS`를 프록시 구조로 활용하면, 개발자는 익숙한 자바스크립트 배열이나 객체를 다루는 듯한 편의성을 누리면서도 내부적으로는 C++ 엔진에 필적하는 메모리 공유 성능을 얻을 수 있다는 강력한 장점이 있습니다. --- _Last updated: 2026-04-14_ -- Raw Source: [[00_Raw/2026-04-20/bitECS와 SharedArrayBuffer를 결합한 멀티스레드 고성능 아키텍처.md]] +- Raw Source: 00_Raw/2026-04-20/bitECS와 SharedArrayBuffer를 결합한 멀티스레드 고성능 아키텍처.md --- diff --git a/01_Archive/2026-04-20/bitECS와 SharedArrayBuffer의 실제 코드 통합.md b/01_Archive/2026-04-20/bitECS와 SharedArrayBuffer의 실제 코드 통합.md index b8d3e10f..6be766a6 100644 --- a/01_Archive/2026-04-20/bitECS와 SharedArrayBuffer의 실제 코드 통합.md +++ b/01_Archive/2026-04-20/bitECS와 SharedArrayBuffer의 실제 코드 통합.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-6AB6C6 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - bitECS와 SharedArrayBuffer의 실제 코드 통합" --- -# [[bitECS와 SharedArrayBuffer의 실제 코드 통합]] +# [[bitECS와 SharedArrayBuffer의 실제 코드 통합|bitECS와 SharedArrayBuffer의 실제 코드 통합]] ## 📌 한 줄 통찰 (The Karpathy Summary) > `bitECS`의 데이터 지향 컴포넌트(SoA) 구조에 기본 자바스크립트 배열 대신 `SharedArrayBuffer` 기반의 `TypedArray(Float32Array 등)`를 매핑하여, 멀티스레드 환경에서 복사 오버헤드 없이 실시간으로 데이터를 읽고 쓰는 구현 방식입니다. @@ -62,12 +62,12 @@ Velocity.y[eid] = 1.23; - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Structure of Arrays (SoA)]], [[TypedArray (Float32Array)]], [[Web Worker postMessage 통신]], [[메모리 제로 복사 (Zero-Copy)]] -- **Projects/Contexts:** [[멀티스레드 기반 웹 게임 물리 엔진 구현]], [[초대규모 파티클 및 엔티티 시뮬레이션 (React Three Fiber)]] +- **Related Topics:** Structure of Arrays (SoA), TypedArray (Float32Array), Web Worker postMessage 통신, 메모리 제로 복사 (Zero-Copy) +- **Projects/Contexts:** 멀티스레드 기반 웹 게임 물리 엔진 구현, 초대규모 파티클 및 엔티티 시뮬레이션 (React Three Fiber) - **Contradictions/Notes:** `bitECS`와 같은 프록시 객체를 사용하면 원시 메모리를 다루는 로우 레벨 프로그래밍을 자바스크립트 객체 배열(JS objects) 다루듯 쉽게 접근할 수 있게 해줍니다. 하지만 이렇게 최적화를 하더라도, 개발자가 일반적으로 즐겨 사용하는 유연한 JSON 구조의 객체 데이터 포맷과는 여전히 거리가 멀고 데이터의 형태가 고정되어야 한다는 설계적 제약이 따릅니다. --- _Last updated: 2026-04-14_ -- Raw Source: [[00_Raw/2026-04-20/bitECS와 SharedArrayBuffer의 실제 코드 통합.md]] +- Raw Source: 00_Raw/2026-04-20/bitECS와 SharedArrayBuffer의 실제 코드 통합.md --- diff --git a/01_Archive/2026-04-20/clinic.js.md b/01_Archive/2026-04-20/clinic.js.md index 3a00a2ce..7f6850b7 100644 --- a/01_Archive/2026-04-20/clinic.js.md +++ b/01_Archive/2026-04-20/clinic.js.md @@ -1,4 +1,4 @@ -# [[clinic.js]] +# [[clinic.js|clinic.js]] ## 📌 Brief Summary `clinic.js`는 Node.js 개발 환경에서 메모리 누수(Memory Leak)의 원인을 빠르고 자동화된 방식으로 분석하기 위해 사용하는 도구입니다 [1, 2]. 힙(Heap) 시각화 기능을 제공하여 애플리케이션 내 어떤 함수가 많은 메모리를 점유하고 있는지 식별하도록 돕습니다 [2]. 터미널에서 `clinic doctor -- node app.js`와 같은 명령어 형태로 실행되어 자동 분석을 수행합니다 [1]. @@ -10,8 +10,8 @@ - *참고: 도구의 구체적인 내부 작동 원리 등 그 외 상세 내용에 대해서는 소스에 관련 정보가 부족합니다.* ## 🔗 Knowledge Connections -- **Related Topics:** [[Memory Leak]], [[Heap Visualization]], [[Garbage Collection]] -- **Projects/Contexts:** [[Node.js Performance Debugging]] +- **Related Topics:** [[Memory Leak|Memory Leak]], Heap Visualization, [[Garbage Collection|Garbage Collection]] +- **Projects/Contexts:** Node.js Performance Debugging - **Contradictions/Notes:** 소스에는 `clinic.js`의 목적과 명령어 사용법 위주의 정보만 간략히 등장하므로, 세부 아키텍처나 추가 프로파일링 기능에 대해서는 소스에 관련 정보가 부족합니다. --- diff --git a/01_Archive/2026-04-20/clinicjs.md b/01_Archive/2026-04-20/clinicjs.md index 26832f64..3b03303d 100644 --- a/01_Archive/2026-04-20/clinicjs.md +++ b/01_Archive/2026-04-20/clinicjs.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-B7F89C -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - clinicjs" --- -# [[clinicjs]] +# [[clinicjs|clinicjs]] ## 📌 한 줄 통찰 (The Karpathy Summary) > `clinic.js`는 Node.js 개발 환경에서 메모리 누수(Memory Leak)의 원인을 빠르고 자동화된 방식으로 분석하기 위해 사용하는 도구입니다 [1, 2]. 힙(Heap) 시각화 기능을 제공하여 애플리케이션 내 어떤 함수가 많은 메모리를 점유하고 있는지 식별하도록 돕습니다 [2]. 터미널에서 `clinic doctor -- node app.js`와 같은 명령어 형태로 실행되어 자동 분석을 수행합니다 [1]. @@ -23,11 +23,11 @@ github_commit: "[P-Reinforce] Continuous Worker - clinicjs" - **정책 변화:** AI 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Memory Leak]], [[Heap Visualization]], [[Garbage Collection]] -- **Projects/Contexts:** [[Node.js Performance Debugging]] +- **Related Topics:** [[Memory Leak|Memory Leak]], Heap Visualization, [[Garbage Collection|Garbage Collection]] +- **Projects/Contexts:** Node.js Performance Debugging - **Contradictions/Notes:** 소스에는 `clinic.js`의 목적과 명령어 사용법 위주의 정보만 간략히 등장하므로, 세부 아키텍처나 추가 프로파일링 기능에 대해서는 소스에 관련 정보가 부족합니다. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/clinic.js.md]] +- Raw Source: 00_Raw/2026-04-20/clinic.js.md --- diff --git a/01_Archive/2026-04-20/eSports Performance Psychology.md b/01_Archive/2026-04-20/eSports Performance Psychology.md index e1c7cad9..c16609f0 100644 --- a/01_Archive/2026-04-20/eSports Performance Psychology.md +++ b/01_Archive/2026-04-20/eSports Performance Psychology.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-29AB4C -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - eSports Performance Psychology" --- -# [[eSports Performance Psychology]] +# [[eSports Performance Psychology|eSports Performance Psychology]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - eSports Performance Psychology ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/eSports Performance Psychology.md]] +- Raw Source: 00_Raw/2026-04-20/eSports Performance Psychology.md --- diff --git a/01_Archive/2026-04-20/eslint-config-prettier.md b/01_Archive/2026-04-20/eslint-config-prettier.md index 0a9261e5..f2d31a97 100644 --- a/01_Archive/2026-04-20/eslint-config-prettier.md +++ b/01_Archive/2026-04-20/eslint-config-prettier.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-7BFB20 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - eslint-config-prettier" --- -# [[eslint-config-prettier]] +# [[eslint-config-prettier|eslint-config-prettier]] ## 📌 한 줄 통찰 (The Karpathy Summary) > `eslint-config-prettier`는 코드 스타일을 포맷팅하는 도구인 Prettier와 코드 품질을 검사하는 정적 분석 도구인 ESLint를 함께 사용할 때 발생하는 규칙 충돌을 해결하기 위해 사용하는 npm 패키지입니다 [1, 2]. 이 설정은 ESLint의 규칙 중 Prettier의 포맷팅과 겹치거나 충돌할 수 있는 스타일 관련 규칙들을 모두 꺼주는(off) 역할을 합니다 [1, 3]. 주로 로컬 IDE 및 CI 파이프라인 환경에서 개발 전용(dev-only) 의존성으로 설치되어 사용됩니다 [4, 5]. @@ -33,11 +33,11 @@ github_commit: "[P-Reinforce] Continuous Worker - eslint-config-prettier" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[ESLint]], [[Prettier]], [[Supply Chain Attack]] -- **Projects/Contexts:** [[JavaScript Development Environment]], [[CVE-2025-54313]] +- **Related Topics:** [[ESLint|ESLint]], [[Prettier|Prettier]], [[공급망 공격 (Supply Chain Attack)|Supply Chain Attack]] +- **Projects/Contexts:** JavaScript Development Environment, CVE-2025-54313 - **Contradictions/Notes:** 소스들에 따르면 `eslint-plugin-prettier`나 `prettier-eslint`와 같은 대안 패키지도 존재하지만, 이들은 속도가 느려지거나 에디터에서 불필요한 빨간 밑줄을 너무 많이 발생시키는 단점이 있어 공식적으로 `eslint-config-prettier`의 단독 사용이 가장 권장됩니다 [7, 19]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/eslint-config-prettier.md]] +- Raw Source: 00_Raw/2026-04-20/eslint-config-prettier.md --- diff --git a/01_Archive/2026-04-20/eslint-plugin-prettier.md b/01_Archive/2026-04-20/eslint-plugin-prettier.md index 7f7c87f9..6529b5ee 100644 --- a/01_Archive/2026-04-20/eslint-plugin-prettier.md +++ b/01_Archive/2026-04-20/eslint-plugin-prettier.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-4555A7 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - eslint-plugin-prettier" --- -# [[eslint-plugin-prettier]] +# [[eslint-plugin-prettier|eslint-plugin-prettier]] ## 📌 한 줄 통찰 (The Karpathy Summary) > `eslint-plugin-prettier`는 코드 포맷터인 Prettier를 정적 분석 도구인 ESLint의 규칙으로 실행시켜주는 플러그인 패키지입니다 [1, 2]. 이 도구를 사용하면 Prettier가 인식하는 코드 스타일 및 포맷 오류를 ESLint의 에러나 경고로 출력하게 됩니다 [2, 3]. 결과적으로 개발자는 두 도구의 기능을 통합하여 코드 문법과 포맷팅을 한 번에 관리할 수 있습니다 [4, 5]. @@ -28,11 +28,11 @@ github_commit: "[P-Reinforce] Continuous Worker - eslint-plugin-prettier" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[ESLint]], [[Prettier]], [[eslint-config-prettier]] -- **Projects/Contexts:** [[CVE-2025-54313 (공급망 공격)]], [[웹 프론트엔드 개발 환경 설정]] +- **Related Topics:** [[ESLint|ESLint]], [[Prettier|Prettier]], [[eslint-config-prettier|eslint-config-prettier]] +- **Projects/Contexts:** CVE-2025-54313 (공급망 공격), 웹 프론트엔드 개발 환경 설정 - **Contradictions/Notes:** Prettier 공식 문서 및 여러 개발자들은 `eslint-plugin-prettier`를 사용할 때 발생하는 속도 저하와 과도한 에러 표시 문제 때문에 이 방법보다는 포맷팅 충돌 규칙만 꺼주는 `eslint-config-prettier`의 단독 사용을 가장 추천하고 있습니다 [1, 6, 8]. 그러나 설정의 중앙화와 단일 수정 명령어(`eslint --fix`)의 편리함을 이유로 이를 선호하는 실무자들도 존재합니다 [4]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/eslint-plugin-prettier.md]] +- Raw Source: 00_Raw/2026-04-20/eslint-plugin-prettier.md --- diff --git a/01_Archive/2026-04-20/e스포츠 인지 상태 및 성과 위험 평가.md b/01_Archive/2026-04-20/e스포츠 인지 상태 및 성과 위험 평가.md index fb0f4a30..97fb02de 100644 --- a/01_Archive/2026-04-20/e스포츠 인지 상태 및 성과 위험 평가.md +++ b/01_Archive/2026-04-20/e스포츠 인지 상태 및 성과 위험 평가.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-52CDF0 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - e스포츠 인지 상태 및 성과 위험 평가" --- -# [[e스포츠 인지 상태 및 성과 위험 평가]] +# [[e스포츠 인지 상태 및 성과 위험 평가|e스포츠 인지 상태 및 성과 위험 평가]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -30,11 +30,11 @@ github_commit: "[P-Reinforce] Continuous Worker - e스포츠 인지 상태 및 - **정책 변화:** AI 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[기계 학습(Machine Learning)]], [[생체 신호(Physiological Signals)]], [[심박 변이도(HRV)]], [[틸트(Tilt)]], [[몰입(Flow State)]] +- **Related Topics:** 기계 학습(Machine Learning), 생체 신호(Physiological Signals), 심박 변이도(HRV), 틸트(Tilt), 몰입(Flow State) - **Projects/Contexts:** 웨어러블 센서(EEG, EDA, 시선 추적기 등)를 기반으로 한 기계 학습 모델을 통해 e스포츠 선수의 실시간 인지 상태(작업 부하, 인지적 피로)를 감지하고 성과 하락(틸트)을 예측하기 위한 프레임워크 연구 [15], [12]. - **Contradictions/Notes:** HRV 수치는 인지적 요구와 스트레스가 높은 압박 상황에서는 감소하지만, 플레이어가 고도의 집중과 기술적 균형을 이루는 '몰입(Flow)'에 진입했을 때는 반대로 증가하므로 측정 당시의 게임 문맥에 따른 세심한 해석이 필수적입니다 [7], [8]. 동공 크기 역시 단기적인 인지적 노력의 증가에는 확장되지만, 2시간 이상의 장기적인 인지적 피로 상태에서는 수축하는 상반된 반응을 보입니다 [5], [6]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/e스포츠 인지 상태 및 성과 위험 평가.md]] +- Raw Source: 00_Raw/2026-04-20/e스포츠 인지 상태 및 성과 위험 평가.md --- diff --git a/01_Archive/2026-04-20/instancedArray.md b/01_Archive/2026-04-20/instancedArray.md index 3e697e68..e23f411e 100644 --- a/01_Archive/2026-04-20/instancedArray.md +++ b/01_Archive/2026-04-20/instancedArray.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-FF8159 -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - instancedArray" --- -# [[instancedArray]] +# [[instancedArray|instancedArray]] ## 📌 한 줄 통찰 (The Karpathy Summary) > `instancedArray`는 렌더링 프레임 간에도 유지되는 영구적인 GPU 버퍼(GPU-persistent buffers)를 생성하는 기능입니다 [1]. 이 기능을 활용하면 기존 파티클 시스템 등에서 성능 저하의 주원인으로 꼽히는 CPU와 GPU 간의 데이터 전송을 제거할 수 있습니다 [1]. 특히 매 프레임마다 업데이트되는 파티클 데이터에 적용하여, 비용이 많이 드는 WebGPU 버퍼 쓰기 작업을 최소화하는 데 핵심적인 역할을 합니다 [2]. @@ -23,11 +23,11 @@ github_commit: "[P-Reinforce] Continuous Worker - instancedArray" - **정책 변화:** Graphics & Performance 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[WebGPU]], [[TSL]], [[Particle Systems]] -- **Projects/Contexts:** [[Three.js 성능 최적화 (Utsubo의 2026 가이드)]] +- **Related Topics:** [[WebGPU|WebGPU]], TSL, [[입자 시스템(Particle Systems)|Particle Systems]] +- **Projects/Contexts:** Three.js 성능 최적화 (Utsubo의 2026 가이드) - **Contradictions/Notes:** 소스 내에 이 주제와 관련하여 상충하는 주장이나 반대 의견은 존재하지 않습니다. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/instancedArray.md]] +- Raw Source: 00_Raw/2026-04-20/instancedArray.md --- diff --git a/01_Archive/2026-04-20/lint-staged.md b/01_Archive/2026-04-20/lint-staged.md index 23c3bcc7..9109920a 100644 --- a/01_Archive/2026-04-20/lint-staged.md +++ b/01_Archive/2026-04-20/lint-staged.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-D0626D -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - lint-staged" --- -# [[lint-staged]] +# [[lint-staged|lint-staged]] ## 📌 한 줄 통찰 (The Karpathy Summary) > `lint-staged`는 Git의 커밋 전 단계(pre-commit)에서 스테이징된(staged) 파일들에 대해서만 린터(Linter)나 포매터(Formatter) 등의 특정 명령어를 실행하도록 도와주는 도구입니다 [1, 2]. 전체 코드베이스 대신 변경된 파일만 검사하므로 실행 시간을 대폭 단축시켜 줍니다 [2, 3]. 주로 Husky와 같은 Git 훅(Hook) 관리 도구와 함께 사용되어, 커밋 전에 코드의 품질을 검사하고 문제를 자동으로 수정하여 오류 없는 깔끔한 코드만 저장소에 반영되도록 보장합니다 [4, 5]. @@ -33,11 +33,11 @@ github_commit: "[P-Reinforce] Continuous Worker - lint-staged" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Husky]], [[ESLint]], [[Prettier]], [[Git Hooks]] -- **Projects/Contexts:** [[CI/CD 파이프라인 자동화]], [[모노레포(Monorepo) 아키텍처 설정]], [[Turborepo 환경 구성]] +- **Related Topics:** [[Husky|Husky]], [[ESLint|ESLint]], [[Prettier|Prettier]], [[Git Hooks|Git Hooks]] +- **Projects/Contexts:** [[CI_CD 파이프라인 자동화|CI/CD 파이프라인 자동화]], [[모노레포(Monorepo) 아키텍처 설정|모노레포(Monorepo) 아키텍처 설정]], [[Turborepo 환경 구성|Turborepo 환경 구성]] - **Contradictions/Notes:** 소스에 따르면 `lint-staged`의 명령어 목록에 `git add`를 수동으로 포함하는 것은 피해야 합니다. v10 이후부터는 여러 작업이 동일한 파일을 편집할 때 발생하는 경쟁 상태를 방지하기 위해 도구 자체가 수정 사항을 자동으로 스테이징 처리하기 때문입니다 [9, 18]. 또한, 전체 프로젝트를 검사하도록 설계된 도구(예: `ng lint` 또는 `tsc --noEmit`)를 `lint-staged`를 통해 실행하는 것은 구조적으로 맞지 않으며 지양해야 한다고 명시되어 있습니다 [13, 18]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/lint-staged.md]] +- Raw Source: 00_Raw/2026-04-20/lint-staged.md --- diff --git a/01_Archive/2026-04-20/never 타입(never type).md b/01_Archive/2026-04-20/never 타입(never type).md index e86ee437..4f2cbf0a 100644 --- a/01_Archive/2026-04-20/never 타입(never type).md +++ b/01_Archive/2026-04-20/never 타입(never type).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-F56CC2 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - never 타입(never type)" --- -# [[never 타입(never type)]] +# [[never 타입(never type)|never 타입(never type)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > `never` 타입은 타입스크립트에서 절대 발생하지 않는 값의 타입을 의미하며, 집합론적으로는 어떠한 값도 포함하지 않는 '공집합(empty set)'으로 기능한다 [1, 2]. 주로 모든 케이스가 처리되었는지 확인하는 철저함 검사(exhaustiveness checking), 오류를 발생시키거나 절대 반환하지 않는 함수의 반환 타입, 그리고 양립할 수 없는 타입들을 교차했을 때 발생하는 타입으로 활용된다 [3-6]. 다른 모든 타입에 할당될 수는 있지만, `never` 자신 외에는 어떤 타입도 `never`에 할당할 수 없는 특성을 지닌다 [7, 8]. @@ -24,11 +24,11 @@ github_commit: "[P-Reinforce] Continuous Worker - never 타입(never type)" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[식별 가능한 유니온(Discriminated Unions)]], [[초과 속성 검사(Excess Property Checking)]], [[구조적 타이핑(Structural Typing)]] -- **Projects/Contexts:** [[switch문 완전성 검사(Exhaustiveness checking)]], [[에러 핸들링 및 무한 루프 함수 설계]], [[상호 배타적 속성(Exclusive Props) 패턴]] +- **Related Topics:** [[식별 가능한 유니온(Discriminated Unions)|식별 가능한 유니온(Discriminated Unions)]], [[초과 속성 검사 (Excess Property Checking)|초과 속성 검사(Excess Property Checking)]], [[구조적 타이핑(Structural Typing)|구조적 타이핑(Structural Typing)]] +- **Projects/Contexts:** switch문 완전성 검사(Exhaustiveness checking), 에러 핸들링 및 무한 루프 함수 설계, 상호 배타적 속성(Exclusive Props) 패턴 - **Contradictions/Notes:** 종료 후 반환값이 없는 함수는 `undefined`를 반환하는 것이므로 `void` 타입을 지정해야 하며, `never` 타입은 절대 정상 종료되지 않는 함수에만 사용해야 한다 [5]. 또한 모든 타입의 상위 집합인 `any` 타입과 비교 시, `any extends never`는 `0 | 1`로 평가되어 `any` 타입이 공집합일 가능성도 내포하고 있는 패러독스(역설)적인 성질을 보인다 [17]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/never 타입(never type).md]] +- Raw Source: 00_Raw/2026-04-20/never 타입(never type).md --- diff --git a/01_Archive/2026-04-20/never 타입.md b/01_Archive/2026-04-20/never 타입.md index e718901d..9916dcdb 100644 --- a/01_Archive/2026-04-20/never 타입.md +++ b/01_Archive/2026-04-20/never 타입.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-5297D4 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - never 타입" --- -# [[never 타입]] +# [[never 타입|never 타입]] ## 📌 한 줄 통찰 (The Karpathy Summary) > `never` 타입은 TypeScript에서 결코 발생할 수 없는 값이나 완료되지 않는 상태를 의미하는 타입이다 [1, 2]. 주로 무한 루프나 예외를 던지는 함수의 반환 타입으로 쓰이며, 집합론적으로 '빈 집합'을 나타내어 컴파일러의 완전성 검사(Exhaustiveness checking) 및 엄격한 타입 통제를 구현하는 데 핵심적으로 사용된다 [3, 4]. @@ -23,11 +23,11 @@ github_commit: "[P-Reinforce] Continuous Worker - never 타입" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[유니온 타입 (Union Types)]], [[식별 가능한 유니온 (Discriminated Unions)]], [[집합론 (Set Theory)]], [[초과 속성 검사 (Excess Property Checking)]] -- **Projects/Contexts:** [[TypeScript 상태 관리 및 에러 처리 방어 (State Management and Defensive Error Handling)]] +- **Related Topics:** [[유니온 타입 (Union Types)|유니온 타입 (Union Types)]], [[식별 가능한 유니온 (Discriminated Unions)|식별 가능한 유니온 (Discriminated Unions)]], [[집합론 (Set Theory)|집합론 (Set Theory)]], [[초과 속성 검사 (Excess Property Checking)|초과 속성 검사 (Excess Property Checking)]] +- **Projects/Contexts:** TypeScript 상태 관리 및 에러 처리 방어 (State Management and Defensive Error Handling) - **Contradictions/Notes:** `never`와 `void`는 기능적으로 다르다. 함수가 정상적으로 실행을 마치고 아무 값도 반환하지 않는 경우(실제로는 `undefined`를 반환)에는 `void`를 써야 하며, 예외를 던지거나 영원히 종료되지 않아 실행 흐름이 끝에 도달하지 못하는 경우에만 `never`를 사용해야 한다 [2, 14]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/never 타입.md]] +- Raw Source: 00_Raw/2026-04-20/never 타입.md --- diff --git a/01_Archive/2026-04-20/readonly 수식어.md b/01_Archive/2026-04-20/readonly 수식어.md index 8f0c010f..d8464de2 100644 --- a/01_Archive/2026-04-20/readonly 수식어.md +++ b/01_Archive/2026-04-20/readonly 수식어.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-E98170 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - readonly 수식어" --- -# [[readonly 수식어]] +# [[readonly 수식어|readonly 수식어]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -34,11 +34,11 @@ github_commit: "[P-Reinforce] Continuous Worker - readonly 수식어" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** `[[불변성(Immutability)]]`, `[[ReadonlyArray]]`, `[[Utility Types]]`, `[[구조적 타이핑(Structural Typing)]]` -- **Projects/Contexts:** `[[상태 관리(State Management) 및 리듀서(Reducers)]]`, `[[API 응답 및 환경 설정 모델링]]` +- **Related Topics:** `[[불변성(Immutability)|불변성(Immutability)]]`, `ReadonlyArray`, `Utility Types`, `[[구조적 타이핑(Structural Typing)|구조적 타이핑(Structural Typing)]]` +- **Projects/Contexts:** `상태 관리(State Management) 및 리듀서(Reducers)`, `API 응답 및 환경 설정 모델링` - **Contradictions/Notes:** `readonly`는 타입 레벨에서 완벽한 불변성을 보장하는 것처럼 보이지만, TypeScript의 타입 호환성(별칭 문제)으로 인해 파라미터로 넘겨진 곳에서 의도치 않게 값이 변경되는 구멍이 발생할 수 있다 [21]. 또한 중첩된 객체를 기본적으로 보호하지 않으므로 구조가 복잡할 때는 사용자 정의 `DeepReadonly`가 필수적으로 요구된다 [18]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/readonly 수식어.md]] +- Raw Source: 00_Raw/2026-04-20/readonly 수식어.md --- diff --git a/01_Archive/2026-04-20/readonly.md b/01_Archive/2026-04-20/readonly.md index 0037113a..d151b74c 100644 --- a/01_Archive/2026-04-20/readonly.md +++ b/01_Archive/2026-04-20/readonly.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-92E2DD -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - readonly" --- -# [[readonly]] +# [[readonly|readonly]] ## 📌 한 줄 통찰 (The Karpathy Summary) > `readonly`는 TypeScript에서 객체의 속성이나 배열, 튜플이 초기화된 이후에 수정되지 않도록 방지하는 수식어이자 유틸리티 타입입니다 [1-3]. 변수의 재할당을 막는 `const`와 달리 객체 내부 구조의 불변성을 제어하며, 런타임 오버헤드 없이 컴파일 타임에 오류를 잡아내어 코드의 안정성과 예측 가능성을 높입니다 [2, 4, 5]. @@ -35,11 +35,11 @@ github_commit: "[P-Reinforce] Continuous Worker - readonly" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[const]], [[Object.freeze()]], [[ReadonlyArray]], [[DeepReadonly]], [[Utility Types]] -- **Projects/Contexts:** [[State Management]], [[Configuration Objects]], [[API Responses]] +- **Related Topics:** const, Object.freeze(), ReadonlyArray, [[DeepReadonly|DeepReadonly]], Utility Types +- **Projects/Contexts:** [[상태 관리(State Management)|State Management]], Configuration Objects, API Responses - **Contradictions/Notes:** `readonly`는 데이터 변경을 막는 훌륭한 타입 제어 장치지만, 컴파일러는 `readonly` 데이터를 변경 가능(mutable)한 매개변수를 받는 함수에 전달하는 것(Aliasing)을 허용하므로 이로 인한 우회적 변이(mutation)가 발생할 수 있다는 구조적 맹점을 주의해야 합니다 [20, 21]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/readonly.md]] +- Raw Source: 00_Raw/2026-04-20/readonly.md --- diff --git a/01_Archive/2026-04-20/satisfies Keyword.md b/01_Archive/2026-04-20/satisfies Keyword.md index 9f90132f..354f97a2 100644 --- a/01_Archive/2026-04-20/satisfies Keyword.md +++ b/01_Archive/2026-04-20/satisfies Keyword.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-5B3851 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - satisfies Keyword" --- -# [[satisfies Keyword]] +# [[satisfies Keyword|satisfies Keyword]] ## 📌 한 줄 통찰 (The Karpathy Summary) > `satisfies` 키워드는 TypeScript 4.9에 도입된 기능으로, 객체가 특정 타입의 구조적 요구 사항을 준수하는지 검증하면서도 해당 객체 속성들의 구체적인 리터럴 타입(Literal Type)을 그대로 보존하는 역할을 합니다[1-3]. 기존의 타입 어노테이션(`:`)이 구체적인 타입을 일반적인 타입으로 넓혀(Widening) 정밀도를 떨어뜨리거나, 타입 단언(`as`)이 컴파일러의 검증을 우회하여 런타임 에러를 유발할 수 있는 단점들을 모두 해결합니다[4-6]. 이를 통해 개발자는 엄격한 타입 검사와 정밀한 타입 추론의 이점을 동시에 누릴 수 있습니다[1, 7]. @@ -25,11 +25,11 @@ github_commit: "[P-Reinforce] Continuous Worker - satisfies Keyword" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Type Annotation]], [[Type Assertion]], [[Excess Property Checking]], [[Discriminated Unions]], [[Literal Type]], [[Structural Typing]] -- **Projects/Contexts:** [[TypeScript 4.9]], [[Data Mapping and Transformation]] +- **Related Topics:** Type Annotation, [[타입 단언(Type Assertion)|Type Assertion]], [[Excess Property Checking|Excess Property Checking]], [[Discriminated Unions|Discriminated Unions]], Literal Type, [[Structural Typing|Structural Typing]] +- **Projects/Contexts:** [[TypeScript 4.9|TypeScript 4.9]], Data Mapping and Transformation - **Contradictions/Notes:** TypeScript의 타입 단언(`as`)은 초과 속성이나 잘못된 매핑에 대한 검사를 수행하지 않아 조용한 런타임 에러를 유발할 수 있지만, `satisfies` 키워드는 구조적 타이핑의 유연성을 허용하면서도 지정된 타입에 대해 엄격한 검증(Excess property checks 등)을 수행하므로 타입 캐스팅의 훌륭한 대안이 됩니다[3, 9, 14]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/satisfies Keyword.md]] +- Raw Source: 00_Raw/2026-04-20/satisfies Keyword.md --- diff --git a/01_Archive/2026-04-20/satisfies 연산자.md b/01_Archive/2026-04-20/satisfies 연산자.md index 1e3ccd74..b245cb87 100644 --- a/01_Archive/2026-04-20/satisfies 연산자.md +++ b/01_Archive/2026-04-20/satisfies 연산자.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-9EE666 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - satisfies 연산자" --- -# [[satisfies 연산자]] +# [[satisfies 연산자|satisfies 연산자]] ## 📌 한 줄 통찰 (The Karpathy Summary) > `satisfies` 연산자는 TypeScript 4.9에 도입된 기능으로, 값의 구체적인 타입(예: 리터럴 타입)을 더 넓은 타입으로 잃지 않으면서(widening 방지) 특정 대상 타입의 요구사항을 충족하는지 검증하는 도구이다 [1-3]. 기존의 타입 어노테이션(`:`)과 타입 단언(`as`) 사이의 딜레마를 해결하여, 엄격한 구조적 유효성 검사와 정밀한 타입 추론이라는 두 가지 이점을 동시에 제공한다 [1, 3]. 이를 통해 런타임 에러를 사전에 방지하고 인터페이스 계약을 안전하게 보호하는 '철벽 수비대'의 핵심 기제로 작동한다 [3, 4]. @@ -25,11 +25,11 @@ github_commit: "[P-Reinforce] Continuous Worker - satisfies 연산자" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** `[[구조적 타이핑(Structural Typing)]]`, `[[과잉 속성 체크(Excess Property Checking)]]`, `[[타입 단언(Type Assertions)]]`, `[[식별 가능한 유니온(Discriminated Unions)]]`, `[[타입 좁히기(Type Narrowing)]]` -- **Projects/Contexts:** `[[설정 객체 및 룩업 테이블 설계(Configuration Objects and Lookup Tables)]]`, `[[백엔드-프론트엔드 데이터 변환(Data Transformation between Backend and Frontend)]]` +- **Related Topics:** `[[구조적 타이핑(Structural Typing)|구조적 타이핑(Structural Typing)]]`, `[[과잉 속성 체크(Excess Property Checking)|과잉 속성 체크(Excess Property Checking)]]`, `[[타입 단언(Type Assertions)|타입 단언(Type Assertions)]]`, `[[식별 가능한 유니온(Discriminated Unions)|식별 가능한 유니온(Discriminated Unions)]]`, `[[타입 좁히기(Type Narrowing)|타입 좁히기(Type Narrowing)]]` +- **Projects/Contexts:** `[[설정 객체 및 룩업 테이블 설계(Configuration Objects and Lookup Tables)|설정 객체 및 룩업 테이블 설계(Configuration Objects and Lookup Tables)]]`, `[[백엔드-프론트엔드 데이터 변환(Data Transformation between Backend and Frontend)|백엔드-프론트엔드 데이터 변환(Data Transformation between Backend and Frontend)]]` - **Contradictions/Notes:** 타입 단언(`as`) 기법은 컴파일러의 과잉 속성 검사를 우회해버리므로 초과 속성이 포함되는 것을 방어하지 못하는 반면, `satisfies` 연산자는 객체 구조에 일치하지 않는 속성이나 오타가 발생한 경우 이를 놓치지 않고 컴파일 에러로 차단한다는 점에서 수비적 안정성의 차이가 극명히 대비된다 [3, 12]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/satisfies 연산자.md]] +- Raw Source: 00_Raw/2026-04-20/satisfies 연산자.md --- diff --git a/01_Archive/2026-04-20/three-mesh-bvh.md b/01_Archive/2026-04-20/three-mesh-bvh.md index 03f0e467..7e2832da 100644 --- a/01_Archive/2026-04-20/three-mesh-bvh.md +++ b/01_Archive/2026-04-20/three-mesh-bvh.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-150C10 -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - three-mesh-bvh" --- -# [[three-mesh-bvh]] +# [[three-mesh-bvh|three-mesh-bvh]] ## 📌 한 줄 통찰 (The Karpathy Summary) > three-mesh-bvh는 Three.js 메시에 대한 광선 투사(Raycasting) 속도를 높이고 공간 쿼리를 가능하게 하는 BVH(Bounding Volume Hierarchy) 구현 라이브러리입니다 [1]. 초당 60프레임(60fps) 환경에서 8만 개 이상의 다각형(polygon)에 대한 빠른 광선 투사를 지원합니다 [2]. 복잡한 기하학적 구조를 가진 대화형 3D 씬(scene)의 상호작용 성능을 최적화하는 데 필수적인 도구로 활용됩니다 [2]. @@ -23,11 +23,11 @@ github_commit: "[P-Reinforce] Continuous Worker - three-mesh-bvh" - **정책 변화:** Graphics & Performance 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Raycasting]], [[InstancedMesh]], [[Bounding Volume Hierarchy (BVH)]] -- **Projects/Contexts:** [[Three.js Performance Optimization]], [[InstancedMesh2]] +- **Related Topics:** [[Raycasting|Raycasting]], [[InstancedMesh|InstancedMesh]], [[Bounding Volume Hierarchy (BVH)|Bounding Volume Hierarchy (BVH)]] +- **Projects/Contexts:** Three.js Performance Optimization, [[InstancedMesh2|InstancedMesh2]] - **Contradictions/Notes:** 소스에 따르면 구버전에서 사용되던 시각화 클래스인 `MeshBVHVisualizer`는 현재 지원이 중단(deprecated)되었으므로, 사용자는 `MeshBVHHelper`로 교체하여 사용해야 합니다 [4]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/three-mesh-bvh.md]] +- Raw Source: 00_Raw/2026-04-20/three-mesh-bvh.md --- diff --git a/01_Archive/2026-04-20/three.js Issue _30352.md b/01_Archive/2026-04-20/three.js Issue _30352.md index e74c5f41..05bec2a9 100644 --- a/01_Archive/2026-04-20/three.js Issue _30352.md +++ b/01_Archive/2026-04-20/three.js Issue _30352.md @@ -1,4 +1,4 @@ -# [[three.js Issue #30352]] +# [[threejs Issue _30352|three.js Issue]] ## 📌 Brief Summary three.js Issue #30352는 공유 속성을 가진 여러 개의 일반 `Mesh` 객체를 렌더링할 때보다 `InstancedMesh`를 사용할 때 성능이 오히려 크게 저하되는 현상을 보고한 이슈입니다 [1, 2]. 이 현상의 주요 원인은 `InstancedMesh`가 내부 인스턴스들을 렌더링할 때 앞뒤로 자동 정렬(Sorting)하지 않아 발생하는 막대한 오버드로우(Overdraw) 비용 때문입니다 [3, 4]. 즉, 단일 드로우 콜로 인한 CPU 연산 감소 이득보다 불필요한 픽셀 처리 부하가 더 커지면서 씬이 프래그먼트 바운드(Fragment-bound) 상태에 빠지는 구조적 한계를 보여주는 사례입니다 [5]. @@ -17,8 +17,8 @@ three.js Issue #30352는 공유 속성을 가진 여러 개의 일반 `Mesh` 객 기여자들은 정렬 기능이 없는 `InstancedMesh` 대신, 인스턴스의 정렬(Sorting)을 지원하는 `BatchedMesh`를 사용해 볼 것을 대안으로 권장했습니다 [4]. 해당 이슈는 특정 기기의 버그가 아니라 정렬 부재와 오버드로우로 인한 정상적인 하드웨어 한계 지점임이 확인되어 2025년 1월 23일에 종결(Closed)되었습니다 [4, 6]. ## 🔗 Knowledge Connections -- **Related Topics:** [[InstancedMesh]], [[Overdraw]], [[BatchedMesh]], [[Fragment-bound]] -- **Projects/Contexts:** [[three.js]] +- **Related Topics:** [[InstancedMesh|InstancedMesh]], [[Overdraw|Overdraw]], [[BatchedMesh|BatchedMesh]], [[Fragment-bound|Fragment-bound]] +- **Projects/Contexts:** [[Threejs 성능 최적화|three.js]] - **Contradictions/Notes:** 이론적으로 `InstancedMesh`는 드로우 콜 횟수를 1회로 줄여주어 렌더링 성능을 향상시켜야 하지만, 이슈 #30352의 사례에서는 개별 정렬 부재로 인한 오버드로우 비용 때문에 오히려 개별 드로우 콜(5,000회)을 수행하는 일반 `Mesh` 방식보다 성능이 떨어지는 모순적인 결과를 보여줍니다 [1, 2, 5]. --- diff --git a/01_Archive/2026-04-20/threejs Issue _30352.md b/01_Archive/2026-04-20/threejs Issue _30352.md index d1c6088e..34d259b9 100644 --- a/01_Archive/2026-04-20/threejs Issue _30352.md +++ b/01_Archive/2026-04-20/threejs Issue _30352.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-AE68EC -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - threejs Issue _30352" --- -# [[threejs Issue _30352]] +# [[threejs Issue _30352|threejs Issue _30352]] ## 📌 한 줄 통찰 (The Karpathy Summary) > three.js Issue #30352는 공유 속성을 가진 여러 개의 일반 `Mesh` 객체를 렌더링할 때보다 `InstancedMesh`를 사용할 때 성능이 오히려 크게 저하되는 현상을 보고한 이슈입니다 [1, 2]. 이 현상의 주요 원인은 `InstancedMesh`가 내부 인스턴스들을 렌더링할 때 앞뒤로 자동 정렬(Sorting)하지 않아 발생하는 막대한 오버드로우(Overdraw) 비용 때문입니다 [3, 4]. 즉, 단일 드로우 콜로 인한 CPU 연산 감소 이득보다 불필요한 픽셀 처리 부하가 더 커지면서 씬이 프래그먼트 바운드(Fragment-bound) 상태에 빠지는 구조적 한계를 보여주는 사례입니다 [5]. @@ -20,11 +20,11 @@ github_commit: "[P-Reinforce] Continuous Worker - threejs Issue _30352" - **정책 변화:** Graphics & Performance 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[InstancedMesh]], [[Overdraw]], [[BatchedMesh]], [[Fragment-bound]] -- **Projects/Contexts:** [[three.js]] +- **Related Topics:** [[InstancedMesh|InstancedMesh]], [[Overdraw|Overdraw]], [[BatchedMesh|BatchedMesh]], [[Fragment-bound|Fragment-bound]] +- **Projects/Contexts:** [[Threejs 성능 최적화|three.js]] - **Contradictions/Notes:** 이론적으로 `InstancedMesh`는 드로우 콜 횟수를 1회로 줄여주어 렌더링 성능을 향상시켜야 하지만, 이슈 #30352의 사례에서는 개별 정렬 부재로 인한 오버드로우 비용 때문에 오히려 개별 드로우 콜(5,000회)을 수행하는 일반 `Mesh` 방식보다 성능이 떨어지는 모순적인 결과를 보여줍니다 [1, 2, 5]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/three.js Issue _30352.md]] +- Raw Source: 00_Raw/2026-04-20/three.js Issue _30352.md --- diff --git a/01_Archive/2026-04-20/ts-brand.md b/01_Archive/2026-04-20/ts-brand.md index fecb5e84..2150c127 100644 --- a/01_Archive/2026-04-20/ts-brand.md +++ b/01_Archive/2026-04-20/ts-brand.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-7A0150 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - ts-brand" --- -# [[ts-brand]] +# [[ts-brand|ts-brand]] ## 📌 한 줄 통찰 (The Karpathy Summary) > `ts-brand`는 타입스크립트(TypeScript)에서 브랜디드 타입(Branded Types, 불투명 타입)을 보다 쉽게 생성하고 사용할 수 있도록 돕는 커뮤니티 기반의 유틸리티 패키지입니다 [1, 2]. 이 라이브러리는 타입 브랜드 구성을 위해 미리 작성된 코드를 제공하여, 개발자들이 구조적으로 동일하지만 의미가 다른 타입들을 안전하게 구분할 수 있도록 지원합니다 [2]. 제네릭 `Brand` 타입을 내보내어 브랜딩을 위한 보다 고급화된 기능을 제공하는 것이 특징입니다 [1, 2]. @@ -22,11 +22,11 @@ github_commit: "[P-Reinforce] Continuous Worker - ts-brand" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Branded Types]], [[Opaque Types]], [[Structural Typing]], [[Effect TS]] -- **Projects/Contexts:** [[TypeScript Community Libraries]], [[Type Safety Optimization]] +- **Related Topics:** [[Branded Types|Branded Types]], [[Opaque Types|Opaque Types]], [[Structural Typing|Structural Typing]], [[Effect TS|Effect TS]] +- **Projects/Contexts:** TypeScript Community Libraries, Type Safety Optimization - **Contradictions/Notes:** `ts-brand`를 활용한 브랜디드 타입 패턴은 프로그램의 타입 안정성을 높여주지만, 동시에 코드의 개념적 복잡성을 증가시키는 단점이 있습니다 [5, 6]. 따라서 단순한 유니언(Union), 열거형(Enum) 등 덜 복잡한 대안으로도 요구사항을 충족할 수 있는지 도입 전 트레이드오프(trade-off)를 신중히 고려해야 합니다 [5-7]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/ts-brand.md]] +- Raw Source: 00_Raw/2026-04-20/ts-brand.md --- diff --git a/01_Archive/2026-04-20/ts-pattern.md b/01_Archive/2026-04-20/ts-pattern.md index acedd5a1..fd5d124e 100644 --- a/01_Archive/2026-04-20/ts-pattern.md +++ b/01_Archive/2026-04-20/ts-pattern.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-ED6DC8 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - ts-pattern" --- -# [[ts-pattern]] +# [[ts-pattern|ts-pattern]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -22,11 +22,11 @@ github_commit: "[P-Reinforce] Continuous Worker - ts-pattern" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Pattern Matching]], [[Type Inference]], [[TC39]], [[Discriminated Unions]] -- **Projects/Contexts:** [[TypeScript 조건부 분기 처리 및 상태 관리]] +- **Related Topics:** Pattern Matching, [[Type Inference|Type Inference]], TC39, [[Discriminated Unions|Discriminated Unions]] +- **Projects/Contexts:** TypeScript 조건부 분기 처리 및 상태 관리 - **Contradictions/Notes:** 일부 벤치마크는 `ts-pattern`이 `if/else`보다 약 99% 느리다고 주장하지만 [2], 개발자 커뮤니티(댓글)에서는 이 벤치마크가 순수한 `ts-pattern` 성능이 아닌 외부의 객체 생성 시간(Object Creation Time)을 포함했거나, 벤치마크 툴 자체의 메모리 간섭 문제로 인해 차이가 크게 과장되었다는 반론을 제기합니다. 실제로는 1~2배 수준의 차이에 불과하여, 납득할 수 있는 성능 차이이므로 가독성과 타입 안정성을 위해 충분히 사용할 만하다는 상반된 의견이 존재합니다 [6, 7]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/ts-pattern.md]] +- Raw Source: 00_Raw/2026-04-20/ts-pattern.md --- diff --git a/01_Archive/2026-04-20/useEffect 클린업(Cleanup).md b/01_Archive/2026-04-20/useEffect 클린업(Cleanup).md index 70c2852e..7f15ea71 100644 --- a/01_Archive/2026-04-20/useEffect 클린업(Cleanup).md +++ b/01_Archive/2026-04-20/useEffect 클린업(Cleanup).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-55865D -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - useEffect 클린업(Cleanup)" --- -# [[useEffect 클린업(Cleanup)]] +# [[useEffect 클린업(Cleanup)|useEffect 클린업(Cleanup)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > `useEffect` 훅 내부에서 반환(return)하는 클린업 함수는 컴포넌트가 화면에서 사라질 때(Unmount) 또는 다음 이펙트가 실행되기 전에 호출되어, 불필요하게 남아있는 백그라운드 작업이나 자원 점유를 해제함으로써 **애플리케이션의 메모리 누수(Memory Leak)를 방지하는 핵심 메커니즘**입니다. @@ -28,8 +28,8 @@ github_commit: "[P-Reinforce] Continuous Worker - useEffect 클린업(Cleanup)" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Memory Leak Prevention (메모리 누수 방지)]], [[반응형 윈도우 리사이즈(Resize) 이벤트 처리]], [[웹 워커(Web Worker)]], [[Three.js 자원 해제 (Dispose)]] -- **Projects/Contexts:** [[고성능 실시간 상호작용 시스템]], [[멀티스레드 기반 웹 애플리케이션]] +- **Related Topics:** [[Memory Leak Prevention 메모리 누수 방지|Memory Leak Prevention (메모리 누수 방지)]], [[반응형 윈도우 리사이즈(Resize) 이벤트 처리|반응형 윈도우 리사이즈(Resize) 이벤트 처리]], 웹 워커(Web Worker), [[Three.js 자원 해제 (Dispose)|Three.js 자원 해제 (Dispose)]] +- **Projects/Contexts:** 고성능 실시간 상호작용 시스템, 멀티스레드 기반 웹 애플리케이션 - **Contradictions/Notes:** React 18의 Strict Mode(개발 환경)에서는 컴포넌트가 의도적으로 한 번 더 마운트/언마운트되는 과정을 거칩니다. 이 과정에서 클린업 함수가 제대로 구현되어 있지 않으면 예기치 않은 이중 실행(예: 두 번 연결되는 웹소켓 등) 버그를 조기에 발견할 수 있으므로, 정확한 클린업 작성은 안정적인 React 앱 설계의 필수 조건입니다. -- Raw Source: [[00_Raw/2026-04-20/useEffect 클린업(Cleanup).md]] +- Raw Source: 00_Raw/2026-04-20/useEffect 클린업(Cleanup).md --- diff --git a/01_Archive/2026-04-20/가비지 컬렉션 (Garbage Collection).md b/01_Archive/2026-04-20/가비지 컬렉션 (Garbage Collection).md index db85d805..bd48b3ba 100644 --- a/01_Archive/2026-04-20/가비지 컬렉션 (Garbage Collection).md +++ b/01_Archive/2026-04-20/가비지 컬렉션 (Garbage Collection).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-51196C -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 가비지 컬렉션 (Garbage Collection)" --- -# [[가비지 컬렉션 (Garbage Collection)]] +# [[가비지 컬렉션 (Garbage Collection)|가비지 컬렉션 (Garbage Collection)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 가비지 컬렉션(GC)은 애플리케이션에서 더 이상 필요하지 않거나 도달할 수 없는 객체가 차지한 메모리 영역을 식별하고 자동으로 회수하여 재사용할 수 있도록 하는 메모리 관리 프로세스입니다 [1, 2]. 프로그래머가 직접 메모리를 할당하고 해제해야 하는 복잡성을 줄여주고 메모리 누수와 같은 오류를 방지하는 데 도움을 줍니다 [3]. 하지만 메모리 관리에 대한 통제권을 잃게 되며, 시스템 실행을 멈추게 하는 예측 불가능한 일시 정지(Stop-The-World)를 유발할 수 있는 양날의 검과 같은 특성을 가집니다 [2-4]. @@ -36,11 +36,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 가비지 컬렉션 (Garbage C - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[메모리 누수 (Memory Leak)]], [[힙 메모리 (Heap Memory)]], [[V8 엔진 (V8 Engine)]], [[Stop-The-World]] -- **Projects/Contexts:** [[V8 Orinoco 프로젝트]], [[Node.js]], [[IBM Eclipse OpenJ9]] +- **Related Topics:** [[메모리 누수(Memory Leak)|메모리 누수 (Memory Leak)]], [[힙 메모리(Heap Memory)|힙 메모리 (Heap Memory)]], [[V8 엔진 (V8 Engine)|V8 엔진 (V8 Engine)]], [[Stop-the-world|Stop-The-World]] +- **Projects/Contexts:** V8 Orinoco 프로젝트, [[Node.js|Node.js]], IBM Eclipse OpenJ9 - **Contradictions/Notes:** 가비지 컬렉션은 프로그래머에게서 수동 메모리 관리에 대한 부담을 덜어주어 대규모 애플리케이션의 메모리 누수나 오류를 획기적으로 줄여주는 장점이 있지만, 메모리 관리 시점에 대한 제어권을 잃게 되며 C/C++ 같은 언어와 비교할 때 포인터를 식별하고 마킹하는 등 런타임 오버헤드를 발생시킨다는 단점도 공존합니다 [3, 4]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/가비지 컬렉션 (Garbage Collection).md]] +- Raw Source: 00_Raw/2026-04-20/가비지 컬렉션 (Garbage Collection).md --- diff --git a/01_Archive/2026-04-20/가비지 컬렉션(Garbage Collection).md b/01_Archive/2026-04-20/가비지 컬렉션(Garbage Collection).md index dcbf7b56..35bb10b0 100644 --- a/01_Archive/2026-04-20/가비지 컬렉션(Garbage Collection).md +++ b/01_Archive/2026-04-20/가비지 컬렉션(Garbage Collection).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-F0509C -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 가비지 컬렉션(Garbage Collection)" --- -# [[가비지 컬렉션(Garbage Collection)]] +# [[가비지 컬렉션(Garbage Collection)|가비지 컬렉션(Garbage Collection)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 가비지 컬렉션(GC)은 프로그램에서 더 이상 참조되거나 도달할 수 없는 객체가 차지하는 메모리 영역을 식별하고 이를 자동으로 회수하는 메모리 관리 프로세스입니다 [1-3]. V8과 같은 모던 자바스크립트 엔진에서 GC는 스택 변수나 글로벌 객체와 같은 루트 노드로부터 도달 가능성(reachability)을 기준으로 살아있는 객체를 판별합니다 [1, 4]. 프로그래머의 명시적인 메모리 관리 부담을 덜어주지만, 메모리 할당 실패 시점과 힙의 상태 변화가 GC 로그를 통해 기록되므로 이를 분석하는 것은 애플리케이션의 메모리 누수 방지 및 성능 최적화에 필수적입니다 [5-7]. @@ -20,11 +20,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 가비지 컬렉션(Garbage Co - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[새로운 공간(New Space)]], [[오래된 공간(Old Space)]], [[스캐빈저(Scavenger)]], [[마크-스위프(Mark-Sweep)]], [[메모리 누수(Memory Leak)]], [[할당 타임라인(Allocation Timeline)]], [[오리노코(Orinoco GC)]] -- **Projects/Contexts:** [[V8 엔진의 메모리 관리 아키텍처 및 Orinoco 프로젝트]], [[Chrome DevTools 메모리 프로파일링 및 힙 스냅샷 분석]] +- **Related Topics:** [[새로운 공간(New Space)|새로운 공간(New Space)]], [[오래된 공간(Old Space)|오래된 공간(Old Space)]], [[스캐빈저(Scavenger)|스캐빈저(Scavenger)]], [[마크-스위프(Mark-Sweep)|마크-스위프(Mark-Sweep)]], [[메모리 누수(Memory Leak)|메모리 누수(Memory Leak)]], [[할당 타임라인(Allocation Timeline)|할당 타임라인(Allocation Timeline)]], [[오리노코(Orinoco GC)|오리노코(Orinoco GC)]] +- **Projects/Contexts:** [[V8 엔진의 메모리 관리 아키텍처 및 Orinoco 프로젝트|V8 엔진의 메모리 관리 아키텍처 및 Orinoco 프로젝트]], [[Chrome DevTools 메모리 프로파일링 및 힙 스냅샷 분석|Chrome DevTools 메모리 프로파일링 및 힙 스냅샷 분석]] - **Contradictions/Notes:** 과거 전통적인 가비지 컬렉터는 'Stop-the-world' 방식의 순차적 처리를 사용하여 메인 스레드를 멈추고 지연을 발생시켰으나, 최신 V8의 Orinoco 가비지 컬렉터는 동시적(Concurrent), 병렬적(Parallel) 작업을 도입하여 애플리케이션(자바스크립트) 실행을 차단하지 않고 백그라운드에서 마킹과 스위핑을 수행하도록 개선되었습니다 [18, 33-35]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/가비지 컬렉션(Garbage Collection).md]] +- Raw Source: 00_Raw/2026-04-20/가비지 컬렉션(Garbage Collection).md --- diff --git a/01_Archive/2026-04-20/가비지 컬렉터(Garbage Collector).md b/01_Archive/2026-04-20/가비지 컬렉터(Garbage Collector).md index 386bf51d..c2e7bd42 100644 --- a/01_Archive/2026-04-20/가비지 컬렉터(Garbage Collector).md +++ b/01_Archive/2026-04-20/가비지 컬렉터(Garbage Collector).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-A11817 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 가비지 컬렉터(Garbage Collector)" --- -# [[가비지 컬렉터(Garbage Collector)]] +# [[가비지 컬렉터(Garbage Collector)|가비지 컬렉터(Garbage Collector)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 가비지 컬렉터(Garbage Collector, GC)는 프로그램에서 더 이상 사용되지 않는 메모리(Dead regions)를 자동으로 식별하여 운영체제나 새로운 객체 할당을 위해 재사용하도록 수거하는 메모리 관리 메커니즘입니다 [1, 2]. 스택 변수나 전역 객체와 같은 '루트(Root) 객체'에서부터 포인터 체인을 통해 도달할 수 있는 객체는 '활성(Live)' 상태로 간주하고, 도달할 수 없는 모든 객체는 가비지로 판단합니다 [1, 3, 4]. 개발자가 메모리를 명시적으로 관리할 필요성을 덜어주는 장점이 있지만, 메모리 관리에 대한 제어권을 잃게 되고 실행을 멈추게 하는 예측 불가능한 지연(Pause)을 유발할 수 있는 양날의 검과 같습니다 [5, 6]. @@ -32,11 +32,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 가비지 컬렉터(Garbage Co - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Generational Hypothesis]], [[Mark-Sweep-Compact]], [[Scavenge]], [[Stop-the-world]] -- **Projects/Contexts:** [[V8 Engine]], [[Orinoco Garbage Collector]], [[IBM Eclipse OpenJ9]] +- **Related Topics:** [[Generational Hypothesis|Generational Hypothesis]], [[Mark-Sweep-Compact|Mark-Sweep-Compact]], [[Scavenge|Scavenge]], [[Stop-the-world|Stop-the-world]] +- **Projects/Contexts:** [[V8 Engine|V8 Engine]], Orinoco Garbage Collector, IBM Eclipse OpenJ9 - **Contradictions/Notes:** 소스에 따르면 V8 엔진은 메모리 효율을 높이기 위해 포인터 압축(Pointer compression) 기술을 도입했는데, 이는 메모리와 성능 최적화에는 크게 기여하지만 64비트 시스템 환경에서도 V8의 최대 힙 크기를 4GB로 제한하게 만드는 부작용(Downside)을 초래합니다 [29, 30]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/가비지 컬렉터(Garbage Collector).md]] +- Raw Source: 00_Raw/2026-04-20/가비지 컬렉터(Garbage Collector).md --- diff --git a/01_Archive/2026-04-20/가상 DOM (Virtual DOM).md b/01_Archive/2026-04-20/가상 DOM (Virtual DOM).md index 29f895f4..736fd8b5 100644 --- a/01_Archive/2026-04-20/가상 DOM (Virtual DOM).md +++ b/01_Archive/2026-04-20/가상 DOM (Virtual DOM).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-181AC7 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 가상 DOM (Virtual DOM)" --- -# [[가상 DOM (Virtual DOM)]] +# [[가상 DOM (Virtual DOM)|가상 DOM (Virtual DOM)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 실제 DOM을 매번 직접 조작하는 대신, 메모리 상에 UI의 가상 표현을 구축한 뒤 이전 상태와 비교(Diffing)하여 실제 변경이 필요한 최소한의 부분만 DOM에 반영함으로써 렌더링 성능을 최적화하는 React의 핵심 아키텍처입니다. @@ -29,12 +29,12 @@ github_commit: "[P-Reinforce] Continuous Worker - 가상 DOM (Virtual DOM)" - **정책 변화:** Design & Experience 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[재조정 (Reconciliation)]], [[React Performance Optimization]], [[불필요한 리렌더링 방지]] -- **Projects/Contexts:** [[대규모 데이터 렌더링 및 가상화 최적화]], [[고성능 실시간 상호작용 시스템을 위한 React 기반 게임 엔진 아키텍처]] +- **Related Topics:** [[재조정 (Reconciliation)|재조정 (Reconciliation)]], [[React Performance Optimization|React Performance Optimization]], [[불필요한 리렌더링 방지|불필요한 리렌더링 방지]] +- **Projects/Contexts:** [[대규모 데이터 렌더링 및 가상화 최적화|대규모 데이터 렌더링 및 가상화 최적화]], [[고성능 실시간 상호작용 시스템을 위한 React 기반 게임 엔진 아키텍처|고성능 실시간 상호작용 시스템을 위한 React 기반 게임 엔진 아키텍처]] - **Contradictions/Notes:** 가상 DOM과 재조정 알고리즘은 일반적인 웹 애플리케이션의 선언적 UI 관리에는 압도적으로 훌륭하지만, 매 프레임 수만 개의 속성이 변해야 하는 3D 게임이나 무거운 애니메이션 환경에서는 오히려 가상 DOM을 비교하는 $O(n)$ 연산 자체가 프레임 저하(Lag)를 유발하는 치명적인 원인이 됩니다. 이러한 특수 환경에서는 가상 DOM을 우회하여 참조(`ref`)를 통한 **명령형 직접 조작(Imperative Manipulation)**을 사용해야만 60FPS를 달성할 수 있습니다. --- _Last updated: 2026-04-15_ -- Raw Source: [[00_Raw/2026-04-20/가상 DOM (Virtual DOM).md]] +- Raw Source: 00_Raw/2026-04-20/가상 DOM (Virtual DOM).md --- diff --git a/01_Archive/2026-04-20/가상현실 멀미 (VR Sickness).md b/01_Archive/2026-04-20/가상현실 멀미 (VR Sickness).md index c7289924..0eabd45e 100644 --- a/01_Archive/2026-04-20/가상현실 멀미 (VR Sickness).md +++ b/01_Archive/2026-04-20/가상현실 멀미 (VR Sickness).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-9DED54 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 가상현실 멀미 (VR Sickness)" --- -# [[가상현실 멀미 (VR Sickness)]] +# [[가상현실 멀미 (VR Sickness)|가상현실 멀미 (VR Sickness)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 가상현실 멀미(VR Sickness)는 헤드마운트 디스플레이(HMD)와 같은 가상현실 기기를 사용할 때 다수의 사용자가 경험하는 메스꺼움, 방향 감각 상실, 시각적 장애 등의 부작용을 의미합니다 [1, 2]. 이 현상의 정확한 발병 원인에 대해서는 학계의 완전한 합의가 이루어지지 않았으나, 가상 환경과 실제 신체 경험 간의 시각-전정 감각 충돌(visual-vestibular conflict)이 주요 원인으로 지목되고 있습니다 [3]. 가상현실 멀미는 사용자의 몰입감과 즐거움을 저하시키고 과제 수행 능력에 부정적인 영향을 미칩니다 [2]. @@ -26,11 +26,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 가상현실 멀미 (VR Sickne - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[시각-전정 감각 충돌 (Visual-Vestibular Conflict)]], [[양안 수렴-조절 불일치 (Vergence-Accommodation Conflict)]] -- **Projects/Contexts:** [[엑서게임 (Exergaming)]], [[헤드마운트 디스플레이 (HMD)]] +- **Related Topics:** [[시각-전정 감각 충돌(Visual-Vestibular Conflict)|시각-전정 감각 충돌 (Visual-Vestibular Conflict)]], 양안 수렴-조절 불일치 (Vergence-Accommodation Conflict) +- **Projects/Contexts:** [[엑서게임(Exergaming)|엑서게임 (Exergaming)]], [[헤드마운트 디스플레이 (HMD)|헤드마운트 디스플레이 (HMD)]] - **Contradictions/Notes:** 가상현실 멀미의 발병 원인(etiology)에 대해 아직 학계의 완전한 합의(consensus)는 존재하지 않습니다 [3]. 또한, 노출 시간과 멀미 심각도의 관계가 항상 선형적이지는 않다는 점도 관찰됩니다. 10분 미만 노출보다 10~20분 노출에서 증상이 더 심하게 나타나지만, 20분 이상 노출된 연구에서는 오히려 10~20분 노출보다 증상이 덜 심각하게 보고되는 상반된 양상이 발견되기도 합니다(이는 360도 비디오, 게임, 정적 풍경 등 연구에 사용된 콘텐츠 유형의 분포 차이에 기인한 것으로 추정됩니다) [8]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/가상현실 멀미 (VR Sickness).md]] +- Raw Source: 00_Raw/2026-04-20/가상현실 멀미 (VR Sickness).md --- diff --git a/01_Archive/2026-04-20/가상현실 멀미(VR Sickness).md b/01_Archive/2026-04-20/가상현실 멀미(VR Sickness).md index 7f60062f..34425b10 100644 --- a/01_Archive/2026-04-20/가상현실 멀미(VR Sickness).md +++ b/01_Archive/2026-04-20/가상현실 멀미(VR Sickness).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-DE69FA -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 가상현실 멀미(VR Sickness)" --- -# [[가상현실 멀미(VR Sickness)]] +# [[가상현실 멀미(VR Sickness)|가상현실 멀미(VR Sickness)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -30,11 +30,11 @@ HMD 기기의 특성상 발생하는 폭주-조절 불일치(vergence-accommodat - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[시각-전정 충돌(Visual-vestibular conflict)]], [[폭주-조절 불일치(Vergence-accommodation conflict)]], [[깊이 지각(Depth perception)]], [[반응 시간(Reaction time)]] -- **Projects/Contexts:** [[Beat Saber를 활용한 VR 엑서게임 후유증 연구(VR Exergaming Aftereffects)]] +- **Related Topics:** [[시각-전정 충돌(Visual-vestibular conflict)|시각-전정 충돌(Visual-vestibular conflict)]], [[폭주-조절 불일치(Vergence-accommodation conflict)|폭주-조절 불일치(Vergence-accommodation conflict)]], [[깊이 지각(Depth perception)|깊이 지각(Depth perception)]], [[반응 시간(Reaction Time)|반응 시간(Reaction time)]] +- **Projects/Contexts:** [[Beat Saber를 활용한 VR 엑서게임 후유증 연구(VR Exergaming Aftereffects)|Beat Saber를 활용한 VR 엑서게임 후유증 연구(VR Exergaming Aftereffects)]] - **Contradictions/Notes:** VR 노출이 사용자의 '반응 시간(Reaction time)'에 미치는 직접적인 영향에 대해 기존 문헌들은 매우 일관되지 않은(highly inconsistent) 결과를 보이고 있습니다. 일부 연구에서는 가상현실 멀미로 인해 반응 시간이 부정적으로 지연된다고 보고하는 반면, 다른 연구에서는 긍정적으로 반응 속도가 빨라진다고 주장합니다 [13]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/가상현실 멀미(VR Sickness).md]] +- Raw Source: 00_Raw/2026-04-20/가상현실 멀미(VR Sickness).md --- diff --git a/01_Archive/2026-04-20/가상현실 사후 효과 연구(Virtual Reality Aftereffects Study).md b/01_Archive/2026-04-20/가상현실 사후 효과 연구(Virtual Reality Aftereffects Study).md index 139366a5..8cffbca6 100644 --- a/01_Archive/2026-04-20/가상현실 사후 효과 연구(Virtual Reality Aftereffects Study).md +++ b/01_Archive/2026-04-20/가상현실 사후 효과 연구(Virtual Reality Aftereffects Study).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-52C04C -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 가상현실 사후 효과 연구(Virtual Reality Aftereffects Study)" --- -# [[가상현실 사후 효과 연구(Virtual Reality Aftereffects Study)]] +# [[가상현실 사후 효과 연구(Virtual Reality Aftereffects Study)|가상현실 사후 효과 연구(Virtual Reality Aftereffects Study)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 가상현실 사후 효과 연구는 사용자가 가상현실(VR) 환경, 특히 엑서게임(Exergame) 등을 체험한 후 겪게 되는 시각적, 인지적 변화와 VR 멀미(VR sickness) 증상을 분석하는 연구입니다 [1]. 노출 시간(예: 10분 대 50분)에 따른 눈의 조절(accommodation) 및 폭주(convergence), 인지 반응 속도, 주관적 멀미 증상의 발생과 회복 양상을 측정합니다 [1]. 연구 결과, 대부분의 사후 효과는 VR 종료 후 40분 이내에 기저 수준으로 회복되지만, 노출 시간의 길이와 개인의 민감도에 따라 증상의 강도와 지속 시간이 크게 달라질 수 있음이 확인되었습니다 [2, 3]. @@ -23,11 +23,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 가상현실 사후 효과 연 - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[VR Sickness (가상현실 멀미)]], [[Vergence-Accommodation Conflict (폭주-조절 불일치)]], [[Exergaming (엑서게이밍)]] -- **Projects/Contexts:** [[Beat Saber (비트 세이버)를 활용한 가상현실 사후 효과 분석]] +- **Related Topics:** VR Sickness (가상현실 멀미), Vergence-Accommodation Conflict (폭주-조절 불일치), Exergaming (엑서게이밍) +- **Projects/Contexts:** Beat Saber (비트 세이버)를 활용한 가상현실 사후 효과 분석 - **Contradictions/Notes:** 연구 결과에서 그룹 평균적으로는 VR 노출 40분 후 모든 시각적 및 멀미 증상이 기저 수준으로 회복되었다고 나타나지만, 50분 노출군 중 약 14%의 사용자는 40분 후에도 여전히 높은 수준의 멀미를 경험하여 '평균적 회복 양상'과 '개인별 실제 회복' 사이에 모순적인 괴리가 존재합니다 [8, 10]. 또한, 인지적 반응 시간에 대한 기존 문헌들은 VR이 부정적인 영향을 미친다는 결과와 오히려 긍정적인 영향을 미친다는 결과가 혼재되어 일관성이 부족하나, 본 연구에서는 인지 능력에 유의미한 영향이 없는 것으로 나타났습니다 [6, 12]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/가상현실 사후 효과 연구(Virtual Reality Aftereffects Study).md]] +- Raw Source: 00_Raw/2026-04-20/가상현실 사후 효과 연구(Virtual Reality Aftereffects Study).md --- diff --git a/01_Archive/2026-04-20/가상현실 엑서게임 후유증 연구(VR Exergaming Aftereffects Study).md b/01_Archive/2026-04-20/가상현실 엑서게임 후유증 연구(VR Exergaming Aftereffects Study).md index 2888fdd3..8fb4e1da 100644 --- a/01_Archive/2026-04-20/가상현실 엑서게임 후유증 연구(VR Exergaming Aftereffects Study).md +++ b/01_Archive/2026-04-20/가상현실 엑서게임 후유증 연구(VR Exergaming Aftereffects Study).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-DE15F3 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 가상현실 엑서게임 후유증 연구(VR Exergaming Aftereffects Study)" --- -# [[가상현실 엑서게임 후유증 연구(VR Exergaming Aftereffects Study)]] +# [[가상현실 엑서게임 후유증 연구(VR Exergaming Aftereffects Study)|가상현실 엑서게임 후유증 연구(VR Exergaming Aftereffects Study)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 가상현실(VR) 엑서게임 후유증 연구는 인기 VR 게임인 '비트 세이버(Beat Saber)'를 활용하여 단기 및 장기 VR 노출이 사용자의 시각, 인지, 주관적 웰빙에 미치는 영향을 분석한 연구입니다 [1], [2]. 연구 결과, VR 직후에 시각적 변화와 멀미 증상이 발생하지만 그룹 평균적으로는 40분 후에 기저 수준으로 회복됨을 확인했습니다 [3]. 그러나 멀미 회복에 있어 개인 편차가 뚜렷하게 나타남을 입증하여, 향후 안전한 VR 엑서게임 사용을 위해 노출 전후의 관리 가이드라인을 제시하고 있습니다 [3], [4]. @@ -28,11 +28,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 가상현실 엑서게임 후 - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[가상현실 멀미(VR Sickness)]], [[폭주-조절 불일치(Vergence-accommodation conflict)]], [[시뮬레이터 멀미 설문(SSQ)]] -- **Projects/Contexts:** [[비트 세이버(Beat Saber)를 활용한 엑서게임 실험]] +- **Related Topics:** [[가상현실 멀미(VR Sickness)|가상현실 멀미(VR Sickness)]], [[폭주-조절 불일치(Vergence-accommodation conflict)|폭주-조절 불일치(Vergence-accommodation conflict)]], 시뮬레이터 멀미 설문(SSQ) +- **Projects/Contexts:** 비트 세이버(Beat Saber)를 활용한 엑서게임 실험 - **Contradictions/Notes:** 통계적으로 그룹의 평균적인 시각적 변화 및 멀미 증상은 VR 종료 40분 후 기저 수준으로 회복된다고 나타나지만, 개별 데이터에 따르면 참가자의 약 14%는 40분 후에도 여전히 심각한 수준의 멀미 증상을 경험하는 모순적(개인 편차) 결과가 존재합니다 [3], [14]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/가상현실 엑서게임 후유증 연구(VR Exergaming Aftereffects Study).md]] +- Raw Source: 00_Raw/2026-04-20/가상현실 엑서게임 후유증 연구(VR Exergaming Aftereffects Study).md --- diff --git a/01_Archive/2026-04-20/가상현실 엑서게임 후유증 연구(Virtual reality exergaming aftereffects research).md b/01_Archive/2026-04-20/가상현실 엑서게임 후유증 연구(Virtual reality exergaming aftereffects research).md index 83030509..9c9ece7a 100644 --- a/01_Archive/2026-04-20/가상현실 엑서게임 후유증 연구(Virtual reality exergaming aftereffects research).md +++ b/01_Archive/2026-04-20/가상현실 엑서게임 후유증 연구(Virtual reality exergaming aftereffects research).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-EE39A3 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 가상현실 엑서게임 후유증 연구(Virtual reality exergaming aftereffects research)" --- -# [[가상현실 엑서게임 후유증 연구(Virtual reality exergaming aftereffects research)]] +# [[가상현실 엑서게임 후유증 연구(Virtual reality exergaming aftereffects research)|가상현실 엑서게임 후유증 연구(Virtual reality exergaming aftereffects research)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 가상현실(VR) 엑서게임 후유증 연구는 사용자가 헤드마운트 디스플레이(HMD)를 착용하고 신체 활동을 동반하는 게임(예: 비트 세이버)을 수행한 후 경험하는 시각적, 인지적 변화와 주관적인 사이버 멀미(VR sickness) 증상을 조사하는 분야입니다 [1, 2]. 이 연구는 짧은 노출(10분)과 긴 노출(50분) 등 게임 시간에 따른 후유증의 발생 정도 및 회복 시간을 분석하여, VR 엑서게임의 안전성과 지속적인 활용 가능성을 평가하는 것을 목적으로 합니다 [1, 3]. 연구 결과에 따르면 대부분의 시각적 변화 및 멀미 증상은 게임 직후 악화되지만, 일정 시간의 휴식 후에는 대체로 기저 수준(baseline)으로 회복되는 것으로 나타났습니다 [4-6]. @@ -24,11 +24,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 가상현실 엑서게임 후 - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[사이버 멀미(VR sickness)]], [[수렴-조절 불일치(Vergence-accommodation conflicts)]], [[시뮬레이터 멀미 설문지(Simulator Sickness Questionnaire, SSQ)]], [[헤드마운트 디스플레이(HMD)]] -- **Projects/Contexts:** [[비트 세이버 엑서게임 연구(Beat Saber exergame study)]] +- **Related Topics:** 사이버 멀미(VR sickness), 수렴-조절 불일치(Vergence-accommodation conflicts), 시뮬레이터 멀미 설문지(Simulator Sickness Questionnaire, SSQ), [[헤드 마운트 디스플레이(HMD)|헤드마운트 디스플레이(HMD)]] +- **Projects/Contexts:** 비트 세이버 엑서게임 연구(Beat Saber exergame study) - **Contradictions/Notes:** 그룹 전체의 평균 데이터를 보면 VR 노출 후 40분이 지나면 증상이 완전히 기저 수준으로 회복됨을 시사하지만, 개별 데이터를 심층적으로 보면 일부 사용자(약 14%)가 50분 노출 후 40분이 지나도 여전히 높은 수준의 멀미를 보고한다는 점에서 평균값과 개인차 간의 상반된 양상을 주의해야 합니다 [11]. 또한 멀미나 피로로 인해 인지 속도가 저하될 것이라는 일반적 우려와 달리, 실제 엑서게임 직후에는 오히려 운동 반응 속도가 일시적으로 향상되는 모순된/긍정적인 결과가 관찰되기도 했습니다 [9]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/가상현실 엑서게임 후유증 연구(Virtual reality exergaming aftereffects research).md]] +- Raw Source: 00_Raw/2026-04-20/가상현실 엑서게임 후유증 연구(Virtual reality exergaming aftereffects research).md --- diff --git a/01_Archive/2026-04-20/가상현실 엑서게임(Exergaming) 후유증 연구.md b/01_Archive/2026-04-20/가상현실 엑서게임(Exergaming) 후유증 연구.md index b95371ba..7651813a 100644 --- a/01_Archive/2026-04-20/가상현실 엑서게임(Exergaming) 후유증 연구.md +++ b/01_Archive/2026-04-20/가상현실 엑서게임(Exergaming) 후유증 연구.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-9CAC35 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 가상현실 엑서게임(Exergaming) 후유증 연구" --- -# [[가상현실 엑서게임(Exergaming) 후유증 연구]] +# [[가상현실 엑서게임(Exergaming) 후유증 연구|가상현실 엑서게임(Exergaming) 후유증 연구]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 가상현실(VR) 엑서게임은 몰입감을 통해 신체적 노력에 대한 부담을 잊게 하고 좌식 행동을 개선할 수 있는 유망한 도구이지만, 헤드 마운트 디스플레이(HMD) 사용은 시각적 불일치나 VR 멀미(VR Sickness) 등의 후유증을 유발할 수 있습니다 [1]. 인기 VR 엑서게임인 '비트 세이버(Beat Saber)'를 활용한 실험 결과에 따르면, 노출 직후 사용자의 안구 조절 및 폭주 기능의 변화와 주관적인 멀미 증상이 나타나며, 특히 긴 시간(50분) 노출 시 그 증상이 더욱 심해지는 것으로 나타났습니다 [2, 3]. 대다수의 사용자는 VR 종료 40분 후 기저 수준으로 회복되지만 일부는 장기적인 멀미를 겪을 수 있어, VR 엑서게임 후에는 운전 등의 위험한 활동을 피하고 충분한 휴식 시간을 갖는 것이 필수적입니다 [4, 5]. @@ -20,11 +20,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 가상현실 엑서게임(Exer - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[가상현실 멀미(VR Sickness)]], [[폭주-조절 불일치(Vergence-Accommodation Conflicts)]], [[시뮬레이터 멀미 설문지(SSQ)]] -- **Projects/Contexts:** [[비트 세이버(Beat Saber) 실험]] +- **Related Topics:** [[가상현실 멀미(VR Sickness)|가상현실 멀미(VR Sickness)]], [[폭주-조절 불일치(Vergence-Accommodation Conflicts)|폭주-조절 불일치(Vergence-Accommodation Conflicts)]], [[시뮬레이터 멀미 설문지(SSQ)|시뮬레이터 멀미 설문지(SSQ)]] +- **Projects/Contexts:** [[비트 세이버(Beat Saber) 실험|비트 세이버(Beat Saber) 실험]] - **Contradictions/Notes:** 연구 결과에서 그룹 전체 평균으로는 VR 엑서게임 종료 40분 후 모든 시각적 변화와 멀미가 기저 수준으로 회복된다고 나타났지만, 개별 데이터 확인 시 50분 플레이어의 약 14%는 회복되지 않고 여전히 심각한 멀미를 앓고 있어 평균이 개인의 완전한 회복을 담보하지 않는다는 점에 주의해야 합니다 [4]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/가상현실 엑서게임(Exergaming) 후유증 연구.md]] +- Raw Source: 00_Raw/2026-04-20/가상현실 엑서게임(Exergaming) 후유증 연구.md --- diff --git a/01_Archive/2026-04-20/가상현실 후유증 (Virtual Reality Aftereffects).md b/01_Archive/2026-04-20/가상현실 후유증 (Virtual Reality Aftereffects).md index c9a90961..7b22763f 100644 --- a/01_Archive/2026-04-20/가상현실 후유증 (Virtual Reality Aftereffects).md +++ b/01_Archive/2026-04-20/가상현실 후유증 (Virtual Reality Aftereffects).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-167F08 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 가상현실 후유증 (Virtual Reality Aftereffects)" --- -# [[가상현실 후유증 (Virtual Reality Aftereffects)]] +# [[가상현실 후유증 (Virtual Reality Aftereffects)|가상현실 후유증 (Virtual Reality Aftereffects)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 가상현실(VR) 후유증은 사용자가 헤드 마운트 디스플레이(HMD)를 사용하여 VR 환경(예: 엑서게임 등)을 체험할 때 겪는 메스꺼움, 방향 감각 상실, 시각적 장애 등의 멀미(VR sickness) 증상과 그로 인한 신체적·인지적 영향을 의미합니다 [1, 2]. 이는 가상 환경에서의 시각적 경험과 실제 신체적 경험 간의 감각적 불일치로 인해 발생하며, 깊이 지각(depth perception)과 인지 능력에도 부정적인 영향을 미칠 수 있습니다 [1-3]. 대다수의 즉각적인 시각 및 인지적 후유증은 기기 사용 종료 후 일정 시간(약 40분)이 지나면 기준선으로 회복되지만, 개인의 민감도나 초기 증상의 심각성에 따라 회복 시간에 큰 편차가 존재합니다 [4-6]. @@ -30,11 +30,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 가상현실 후유증 (Virtua - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[가상현실 멀미 (VR Sickness / Cybersickness)]], [[시각-전정 감각 충돌 (Visual-Vestibular Conflict)]], [[폭주-조절 불일치 (Vergence-Accommodation Conflict)]] -- **Projects/Contexts:** [[비트 세이버(Beat Saber)를 활용한 엑서게임 후유증 연구]] +- **Related Topics:** 가상현실 멀미 (VR Sickness / Cybersickness), [[시각-전정 감각 충돌(Visual-Vestibular Conflict)|시각-전정 감각 충돌 (Visual-Vestibular Conflict)]], [[폭주-조절 불일치(Vergence-accommodation conflict)|폭주-조절 불일치 (Vergence-Accommodation Conflict)]] +- **Projects/Contexts:** 비트 세이버(Beat Saber)를 활용한 엑서게임 후유증 연구 - **Contradictions/Notes:** 소스에 따르면 그룹 평균적으로는 VR 노출 후 40분 이내에 증상이 기준선으로 회복되는 것으로 나타났으나, 이는 모든 개인에게 일괄 적용되는 것은 아닙니다. 실제로 50분간 게임을 플레이한 참가자 중 약 14%는 40분이 지난 후에도 여전히 심각한 수준의 VR 멀미를 보고하여, 후유증의 회복에는 큰 개인차가 존재함이 강조됩니다 [4, 10]. 또한, 잦은 휴식이나 짧은 반복 노출을 통한 습관화(habituation)가 일부 사용자의 증상을 완화할 수 있다는 증거가 있지만, 이 역시 모든 사람에게 효과가 있는 전략은 아니라고 지적합니다 [8]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/가상현실 후유증 (Virtual Reality Aftereffects).md]] +- Raw Source: 00_Raw/2026-04-20/가상현실 후유증 (Virtual Reality Aftereffects).md --- diff --git a/01_Archive/2026-04-20/가상현실 후유증(VR Aftereffects).md b/01_Archive/2026-04-20/가상현실 후유증(VR Aftereffects).md index 3c64d6a3..b57c574c 100644 --- a/01_Archive/2026-04-20/가상현실 후유증(VR Aftereffects).md +++ b/01_Archive/2026-04-20/가상현실 후유증(VR Aftereffects).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-4280D4 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 가상현실 후유증(VR Aftereffects)" --- -# [[가상현실 후유증(VR Aftereffects)]] +# [[가상현실 후유증(VR Aftereffects)|가상현실 후유증(VR Aftereffects)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 가상현실 후유증(VR Aftereffects)은 사용자가 헤드마운트 디스플레이(HMD) 등을 통해 가상현실 환경을 경험한 후 겪게 되는 멀미, 방향 감각 상실, 시각적 장애 등의 부정적인 신체적, 인지적 증상을 의미합니다 [1, 2]. 이러한 현상은 가상 세계의 시각적 정보와 실제 신체의 전정 감각 간의 충돌이나, HMD 기기가 유발하는 눈의 폭주-조절 불일치 등으로 인해 발생합니다 [3, 4]. 후유증은 사용자의 가상현실에 대한 몰입감을 떨어뜨리고, 즐거움을 저하시키며, 작업 수행 능력에 악영향을 미칠 수 있기 때문에 VR 기술의 지속적인 활용을 제한하는 주요 요인으로 꼽힙니다 [2]. @@ -30,11 +30,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 가상현실 후유증(VR Afte - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[가상현실 멀미(VR Sickness)]], [[시각-전정 감각 충돌(Visual-Vestibular Conflict)]], [[폭주-조절 불일치(Vergence-Accommodation Conflict)]] -- **Projects/Contexts:** [[비트 세이버(Beat Saber) 엑서게임 연구]] +- **Related Topics:** [[가상현실 멀미(VR Sickness)|가상현실 멀미(VR Sickness)]], [[시각-전정 감각 충돌(Visual-Vestibular Conflict)|시각-전정 감각 충돌(Visual-Vestibular Conflict)]], [[폭주-조절 불일치(Vergence-accommodation conflict)|폭주-조절 불일치(Vergence-Accommodation Conflict)]] +- **Projects/Contexts:** [[비트 세이버(Beat Saber) 엑서게임 연구|비트 세이버(Beat Saber) 엑서게임 연구]] - **Contradictions/Notes:** 일반적으로 VR 노출 시간이 길어질수록 후유증 증상이 증가하지만, 일부 문헌에서는 10~20분 노출된 연구보다 20분 이상 노출된 연구에서 오히려 평균 증상이 더 낮게 나타나는 등 비선형적인 양상을 보고하기도 합니다. 이는 포함된 VR 콘텐츠의 유형(360도 비디오, 게임 등) 차이에서 기인했을 가능성이 큽니다 [7]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/가상현실 후유증(VR Aftereffects).md]] +- Raw Source: 00_Raw/2026-04-20/가상현실 후유증(VR Aftereffects).md --- diff --git a/01_Archive/2026-04-20/가상현실(VR) 엑서게임 인지 사후 효과 분석(CANTAB 5-choice RTI).md b/01_Archive/2026-04-20/가상현실(VR) 엑서게임 인지 사후 효과 분석(CANTAB 5-choice RTI).md index 2aa05fca..b9c0771d 100644 --- a/01_Archive/2026-04-20/가상현실(VR) 엑서게임 인지 사후 효과 분석(CANTAB 5-choice RTI).md +++ b/01_Archive/2026-04-20/가상현실(VR) 엑서게임 인지 사후 효과 분석(CANTAB 5-choice RTI).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-2EC87D -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 가상현실(VR) 엑서게임 인지 사후 효과 분석(CANTAB 5-choice RTI)" --- -# [[가상현실(VR) 엑서게임 인지 사후 효과 분석(CANTAB 5-choice RTI)]] +# [[가상현실(VR) 엑서게임 인지 사후 효과 분석(CANTAB 5-choice RTI)|가상현실(VR) 엑서게임 인지 사후 효과 분석(CANTAB 5-choice RTI)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 본 주제는 가상현실(VR) 엑서게임(예: Beat Saber) 플레이가 사용자의 인지 능력과 반응 속도에 미치는 사후 효과를 분석한 내용입니다 [1-3]. 인지적 요인과 운동적 요인을 분리하여 측정하기 위해 CANTAB 5-choice 반응 시간(RTI) 과제가 활용되었습니다 [3]. 평가 결과, VR 엑서게임 노출 후 의사 결정 속도와 운동 속도에서 우려할 만한 부정적인 인지 사후 효과는 나타나지 않았으며, 단기적으로 운동 속도가 약간 향상되는 등 안전한 수준으로 확인되었습니다 [4]. @@ -24,11 +24,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 가상현실(VR) 엑서게임 - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[엑서게임(Exergaming)]], [[반응 시간(Reaction Time)]], [[가상현실 멀미(VR Sickness)]] -- **Projects/Contexts:** [[Beat Saber VR 엑서게임 실험]] +- **Related Topics:** [[엑서게임(Exergaming)|엑서게임(Exergaming)]], [[반응 시간(Reaction Time)|반응 시간(Reaction Time)]], [[가상현실 멀미(VR Sickness)|가상현실 멀미(VR Sickness)]] +- **Projects/Contexts:** Beat Saber VR 엑서게임 실험 - **Contradictions/Notes:** 소스에 따르면, 가상현실 노출이 반응 속도에 미치는 즉각적인 영향에 대해 기존 문헌들은 매우 일관되지 않은 결과를 보입니다. 일부 연구는 부정적인 사후 효과(반응 속도 지연 등)를 보고한 반면, 본 연구 결과를 포함한 다른 연구들은 반응 시간이 오히려 빨라지는 긍정적인 효과를 발견하기도 했습니다 [8]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/가상현실(VR) 엑서게임 인지 사후 효과 분석(CANTAB 5-choice RTI).md]] +- Raw Source: 00_Raw/2026-04-20/가상현실(VR) 엑서게임 인지 사후 효과 분석(CANTAB 5-choice RTI).md --- diff --git a/01_Archive/2026-04-20/가상현실(VR) 자전거 시뮬레이터.md b/01_Archive/2026-04-20/가상현실(VR) 자전거 시뮬레이터.md index a7658c51..982126aa 100644 --- a/01_Archive/2026-04-20/가상현실(VR) 자전거 시뮬레이터.md +++ b/01_Archive/2026-04-20/가상현실(VR) 자전거 시뮬레이터.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-807F75 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 가상현실(VR) 자전거 시뮬레이터" --- -# [[가상현실(VR) 자전거 시뮬레이터]] +# [[가상현실(VR) 자전거 시뮬레이터|가상현실(VR) 자전거 시뮬레이터]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 가상현실(VR) 자전거 시뮬레이터는 사용자의 신체적 활동과 가상 환경을 결합한 엑스어게임(Exergame) 연구에서 활용되는 시뮬레이션 시스템 중 하나입니다 [1]. 이 시스템은 헤드마운트 디스플레이(HMD)나 대형 스크린과 결합되어 가상현실 멀미(Cybersickness)와 같은 부작용이나 몰입도를 평가하는 데 주로 쓰입니다 [1]. 소스 데이터 내에서는 주로 가상현실 환경에서의 시뮬레이션된 움직임과 디스플레이 유형이 사용자에게 미치는 영향을 분석하는 단일 연구 사례의 맥락으로만 간략히 등장합니다 [1]. @@ -26,11 +26,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 가상현실(VR) 자전거 시 - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[엑스어게임(Exergames)]], [[사이버 멀미(Cybersickness)]], [[헤드마운트 디스플레이(HMD)]] -- **Projects/Contexts:** [[디스플레이 유형과 모션 제어가 가상 자전거 시뮬레이터 멀미에 미치는 영향 연구]] +- **Related Topics:** 엑스어게임(Exergames), 사이버 멀미(Cybersickness), [[헤드 마운트 디스플레이(HMD)|헤드마운트 디스플레이(HMD)]] +- **Projects/Contexts:** 디스플레이 유형과 모션 제어가 가상 자전거 시뮬레이터 멀미에 미치는 영향 연구 - **Contradictions/Notes:** 소스에 가상현실(VR) 자전거 시뮬레이터에 대한 전반적이고 상세한 정보가 부족합니다. 다만 HMD 기반의 시뮬레이터가 몰입도를 높이는 장점이 있음에도 불구하고, 스크린 기반 게임에 비해 멀미를 더 많이 유발할 수 있다는 점이 지적됩니다 [1]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/가상현실(VR) 자전거 시뮬레이터.md]] +- Raw Source: 00_Raw/2026-04-20/가상현실(VR) 자전거 시뮬레이터.md --- diff --git a/01_Archive/2026-04-20/가상현실(VR).md b/01_Archive/2026-04-20/가상현실(VR).md index 72d10585..61003922 100644 --- a/01_Archive/2026-04-20/가상현실(VR).md +++ b/01_Archive/2026-04-20/가상현실(VR).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-13DD7A -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 가상현실(VR)" --- -# [[가상현실(VR)]] +# [[가상현실(VR)|가상현실(VR)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 가상현실(VR)은 헤드마운트 디스플레이(HMD)와 신체 추적 기술 등을 통해 사용자가 가상 세계에 실제로 존재하는 것처럼 느끼게 하는 컴퓨터 생성 3D 환경입니다 [1-3]. 이 기술은 교육, 의료, 게임, 군사 훈련 등 다양한 분야에서 몰입형 상호작용과 시뮬레이션을 제공하는 데 활용됩니다 [3, 4]. 하지만 감각 정보의 불일치로 인한 VR 멀미(VR Sickness)와 복잡한 인터페이스로 인한 높은 인지 부하(Cognitive Load) 등의 부작용이 사용자 경험을 저해하는 주요 과제로 남아 있습니다 [5-7]. @@ -23,11 +23,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 가상현실(VR)" - **정책 변화:** Graphics & Performance 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[현존감(Presence)]], [[인지 부하(Cognitive Load)]], [[VR 멀미(VR Sickness)]], [[몰입(Flow State)]] -- **Projects/Contexts:** [[교육용 몰입형 시뮬레이션(Educational Immersive Simulations)]], [[기능성 게임(Serious Games)]], [[엑서게임(Exergaming)]] +- **Related Topics:** 현존감(Presence), 인지 부하(Cognitive Load), [[VR 멀미 (VR Sickness)|VR 멀미(VR Sickness)]], 몰입(Flow State) +- **Projects/Contexts:** 교육용 몰입형 시뮬레이션(Educational Immersive Simulations), 기능성 게임(Serious Games), [[엑서게임(Exergaming)|엑서게임(Exergaming)]] - **Contradictions/Notes:** 일반적으로 가상현실 인터페이스가 실제 현실의 감각(Fidelity)을 완벽하게 재현할수록 사용자 몰입과 성과가 향상될 것이라 가정하지만, 연구 결과에 따르면 장비의 기술적 복잡성과 물리적 제약이 오히려 사용자의 주의를 분산시켜 인지적 과부하를 초래하는 '충실도 패러독스(Fidelity Paradox)'가 존재함이 확인되었습니다 [13, 14, 19, 20]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/가상현실(VR).md]] +- Raw Source: 00_Raw/2026-04-20/가상현실(VR).md --- diff --git a/01_Archive/2026-04-20/가상화 (Virtualization).md b/01_Archive/2026-04-20/가상화 (Virtualization).md index 2e4fb06b..3b96fd2e 100644 --- a/01_Archive/2026-04-20/가상화 (Virtualization).md +++ b/01_Archive/2026-04-20/가상화 (Virtualization).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-9E9923 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 가상화 (Virtualization)" --- -# [[가상화 (Virtualization)]] +# [[가상화 (Virtualization)|가상화 (Virtualization)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - 가상화 (Virtualization)" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/가상화 (Virtualization).md]] +- Raw Source: 00_Raw/2026-04-20/가상화 (Virtualization).md --- diff --git a/01_Archive/2026-04-20/감각 통합(Sensory integration).md b/01_Archive/2026-04-20/감각 통합(Sensory integration).md index 375410c7..418efdbe 100644 --- a/01_Archive/2026-04-20/감각 통합(Sensory integration).md +++ b/01_Archive/2026-04-20/감각 통합(Sensory integration).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-22B9B4 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 감각 통합(Sensory integration)" --- -# [[감각 통합(Sensory integration)]] +# [[감각 통합(Sensory integration)|감각 통합(Sensory integration)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 감각 통합(Sensory integration)은 개인이 환경 내에서 이동하고 상호작용하는 능력에 근본적인 역할을 하는 감각 처리 과정이다 [1]. 특히 시각적 감각과 전정(신체적) 감각의 통합을 포함하며, 이들 감각 사이에 불일치가 발생할 경우 감각 통합에 교란이 일어난다 [1]. 이러한 감각 통합의 교란은 주로 가상현실(VR) 환경 등에서 메스꺼움이나 방향 상실과 같은 멀미 증상을 유발하는 원인으로 작용한다 [1]. 이 외에 감각 통합의 일반적인 의학적/신경학적 정의에 대해서는 소스에 관련 정보가 부족합니다. @@ -23,11 +23,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 감각 통합(Sensory integrat - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[가상현실 멀미(VR Sickness)]], [[시각-전정 충돌(Visual-vestibular conflict)]] -- **Projects/Contexts:** [[가상현실 엑서게임(Beat Saber) 시각 및 인지적 후유증 연구]] +- **Related Topics:** [[가상현실 멀미(VR Sickness)|가상현실 멀미(VR Sickness)]], [[시각-전정 충돌(Visual-vestibular conflict)|시각-전정 충돌(Visual-vestibular conflict)]] +- **Projects/Contexts:** 가상현실 엑서게임(Beat Saber) 시각 및 인지적 후유증 연구 - **Contradictions/Notes:** 제공된 소스에서는 감각 통합을 주로 VR 환경에서의 멀미 유발 원인(시각과 전정 감각의 충돌)이라는 매우 제한적인 맥락에서만 다루고 있으며, 그 외의 정보에 대해서는 소스에 관련 정보가 부족합니다. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/감각 통합(Sensory integration).md]] +- Raw Source: 00_Raw/2026-04-20/감각 통합(Sensory integration).md --- diff --git a/01_Archive/2026-04-20/강화 계획.md b/01_Archive/2026-04-20/강화 계획.md index 6840d2cf..58f4a845 100644 --- a/01_Archive/2026-04-20/강화 계획.md +++ b/01_Archive/2026-04-20/강화 계획.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-6EDEB4 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 강화 계획" --- -# [[강화 계획]] +# [[강화 계획|강화 계획]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - 강화 계획" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/강화 계획.md]] +- Raw Source: 00_Raw/2026-04-20/강화 계획.md --- diff --git a/01_Archive/2026-04-20/강화 학습(Reinforcement Learning) 알고리즘.md b/01_Archive/2026-04-20/강화 학습(Reinforcement Learning) 알고리즘.md index 2c4c29ba..54fc9ef4 100644 --- a/01_Archive/2026-04-20/강화 학습(Reinforcement Learning) 알고리즘.md +++ b/01_Archive/2026-04-20/강화 학습(Reinforcement Learning) 알고리즘.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-B4CA68 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 강화 학습(Reinforcement Learning) 알고리즘" --- -# [[강화 학습(Reinforcement Learning) 알고리즘]] +# [[강화 학습(Reinforcement Learning) 알고리즘|강화 학습(Reinforcement Learning) 알고리즘]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - 강화 학습(Reinforcement Le ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/강화 학습(Reinforcement Learning) 알고리즘.md]] +- Raw Source: 00_Raw/2026-04-20/강화 학습(Reinforcement Learning) 알고리즘.md --- diff --git a/01_Archive/2026-04-20/강화학습 (Reinforcement Learning).md b/01_Archive/2026-04-20/강화학습 (Reinforcement Learning).md index 0eb47e3f..db51a80d 100644 --- a/01_Archive/2026-04-20/강화학습 (Reinforcement Learning).md +++ b/01_Archive/2026-04-20/강화학습 (Reinforcement Learning).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-FE1230 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 강화학습 (Reinforcement Learning)" --- -# [[강화학습 (Reinforcement Learning)]] +# [[강화학습 (Reinforcement Learning)|강화학습 (Reinforcement Learning)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - 강화학습 (Reinforcement Le ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/강화학습 (Reinforcement Learning).md]] +- Raw Source: 00_Raw/2026-04-20/강화학습 (Reinforcement Learning).md --- diff --git a/01_Archive/2026-04-20/개발자 경험(DX).md b/01_Archive/2026-04-20/개발자 경험(DX).md index 6c6a49aa..53a69984 100644 --- a/01_Archive/2026-04-20/개발자 경험(DX).md +++ b/01_Archive/2026-04-20/개발자 경험(DX).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-C2C2F8 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 개발자 경험(DX)" --- -# [[개발자 경험(DX)]] +# [[개발자 경험(DX)|개발자 경험(DX)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 개발자 경험(DX, Developer Experience)은 개발자가 소프트웨어 도구, API, 또는 SDK 등을 사용할 때 겪는 전반적인 사용 편의성과 만족도를 의미합니다 [1, 2]. 훌륭한 DX는 복잡한 내부 로직을 숨기고 직관적인 인터페이스를 제공하여 개발자의 인지 부하를 줄이며, 휴먼 에러를 구조적으로 방지합니다 [2-4]. 이는 단기적인 개발 편의성을 넘어 시스템의 성능, 안정성, 그리고 장기적인 확장성을 지켜내는 핵심 요소입니다 [5, 6]. @@ -24,11 +24,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 개발자 경험(DX)" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Facade 패턴]], [[탈출구(Escape Hatch)]], [[파레토 법칙]], [[단일 책임 원칙(SRP)]] -- **Projects/Contexts:** [[Toss Front SDK 개발]], [[AWS CDK]], [[Effective TypeScript Principles]] +- **Related Topics:** Facade 패턴, 탈출구(Escape Hatch), 파레토 법칙, [[단일 책임 원칙(SRP)|단일 책임 원칙(SRP)]] +- **Projects/Contexts:** Toss Front SDK 개발, AWS CDK, Effective TypeScript Principles - **Contradictions/Notes:** 추상화 수준이 높아져 DX가 개선될수록 세밀한 제어가 어려워지고 내부 오케스트레이션 로직의 유지 비용이 증가하는 트레이드오프가 발생합니다 [7]. 따라서 고수준의 편의성에만 안주하지 않고 저수준 API와의 공존을 통해 균형을 잡는 것이 필수적입니다 [8]. 또한, 개발자 경험을 핑계로 AI 도구에 전적으로 의존하고 제어권을 넘기는 것은 오히려 복잡성을 키울 수 있으므로 지양해야 합니다 [10]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/개발자 경험(DX).md]] +- Raw Source: 00_Raw/2026-04-20/개발자 경험(DX).md --- diff --git a/01_Archive/2026-04-20/객체 지향 소프트웨어 아키텍처 설계.md b/01_Archive/2026-04-20/객체 지향 소프트웨어 아키텍처 설계.md index cd512397..c9e3369d 100644 --- a/01_Archive/2026-04-20/객체 지향 소프트웨어 아키텍처 설계.md +++ b/01_Archive/2026-04-20/객체 지향 소프트웨어 아키텍처 설계.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-B40B56 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 객체 지향 소프트웨어 아키텍처 설계" --- -# [[객체 지향 소프트웨어 아키텍처 설계]] +# [[객체 지향 소프트웨어 아키텍처 설계|객체 지향 소프트웨어 아키텍처 설계]] ## 📌 한 줄 통찰 (The Karpathy Summary) > **객체 지향 소프트웨어 아키텍처 설계**는 데이터와 행동을 객체(Object) 내에 캡슐화하여 복잡한 시스템을 더 작고 관리하기 쉬운 단위로 구성하는 패러다임입니다 [1, 2]. 이는 코드의 의존성을 줄이고 재사용성을 높여 소프트웨어를 더 이해하기 쉽고, 유연하며, 유지보수가 가능하도록 만드는 것을 핵심 목표로 합니다 [3, 4]. @@ -23,11 +23,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 객체 지향 소프트웨어 - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[SOLID 원칙]], [[관심사의 분리(SoC)]], [[AOP(관점 지향 프로그래밍)]] -- **Projects/Contexts:** [[소프트웨어 모듈화 및 컴포넌트 설계]], [[의존성 관리와 횡단 관심사 처리]] +- **Related Topics:** [[SOLID 원칙|SOLID 원칙]], [[관심사의 분리(SoC)|관심사의 분리(SoC)]], AOP(관점 지향 프로그래밍) +- **Projects/Contexts:** 소프트웨어 모듈화 및 컴포넌트 설계, 의존성 관리와 횡단 관심사 처리 - **Contradictions/Notes:** 소스에서는 횡단 관심사를 처리할 때 객체 지향 프로그래밍의 다형성과 디자인 패턴(전략 패턴 등)을 통해 확장 가능하도록 설계할 수 있다고 설명하지만 [8], 동시에 OOP가 갖는 수직적 분리의 한계 때문에 코드의 복잡성을 낮추고 중복을 제거하려면 AOP(관점 지향 프로그래밍)를 통한 수평적 분리로 시스템을 보완해야 한다는 점을 함께 지적합니다 [10, 11]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/객체 지향 소프트웨어 아키텍처 설계.md]] +- Raw Source: 00_Raw/2026-04-20/객체 지향 소프트웨어 아키텍처 설계.md --- diff --git a/01_Archive/2026-04-20/객체 지향 프로그래밍 (OOP).md b/01_Archive/2026-04-20/객체 지향 프로그래밍 (OOP).md index f417ea41..e768e257 100644 --- a/01_Archive/2026-04-20/객체 지향 프로그래밍 (OOP).md +++ b/01_Archive/2026-04-20/객체 지향 프로그래밍 (OOP).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-4772F3 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 객체 지향 프로그래밍 (OOP)" --- -# [[객체 지향 프로그래밍 (OOP)]] +# [[객체 지향 프로그래밍 (OOP)|객체 지향 프로그래밍 (OOP)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 객체 지향 프로그래밍(OOP)은 데이터와 그 데이터를 다루는 동작(behavior)을 객체(object)라는 단위 안에 캡슐화하여 소프트웨어의 복잡성을 관리하는 프로그래밍 패러다임입니다 [1, 2]. 클래스와 상속 구조를 통해 코드 중복을 방지하고 재사용성을 높일 수 있습니다 [3]. 주로 단일 책임 원칙(SRP)을 포함한 SOLID 설계 원칙과 함께 적용되어 유지보수가 용이하고 유연한 소프트웨어 아키텍처를 구축하는 데 핵심적인 역할을 합니다 [1, 4]. @@ -23,11 +23,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 객체 지향 프로그래밍 - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[관심사의 분리 (SoC)]], [[SOLID 원칙]], [[관점 지향 프로그래밍 (AOP)]] -- **Projects/Contexts:** [[소프트웨어 시스템 설계 및 아키텍처 구축]] +- **Related Topics:** [[관심사의 분리 (SoC)|관심사의 분리 (SoC)]], [[SOLID 원칙|SOLID 원칙]], [[관점 지향 프로그래밍 (AOP)|관점 지향 프로그래밍 (AOP)]] +- **Projects/Contexts:** [[소프트웨어 시스템 설계 및 아키텍처 구축|소프트웨어 시스템 설계 및 아키텍처 구축]] - **Contradictions/Notes:** 소스에 따르면 OOP는 객체 간 책임을 분리하고 기능 단위의 수직적 분리를 달성하는 데 탁월하지만, 시스템 전반에 걸친 공통 기능(횡단 관심사)을 분리하는 데는 단점이 존재하며 이는 AOP 방식을 통해 반대/보완적으로 해결될 수 있다고 설명합니다 [6, 7]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/객체 지향 프로그래밍 (OOP).md]] +- Raw Source: 00_Raw/2026-04-20/객체 지향 프로그래밍 (OOP).md --- diff --git a/01_Archive/2026-04-20/객체 지향 프로그래밍 (Object-Oriented Programming).md b/01_Archive/2026-04-20/객체 지향 프로그래밍 (Object-Oriented Programming).md index dd0120ba..71fa13da 100644 --- a/01_Archive/2026-04-20/객체 지향 프로그래밍 (Object-Oriented Programming).md +++ b/01_Archive/2026-04-20/객체 지향 프로그래밍 (Object-Oriented Programming).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-D7D274 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 객체 지향 프로그래밍 (Object-Oriented Programming)" --- -# [[객체 지향 프로그래밍 (Object-Oriented Programming)]] +# [[객체 지향 프로그래밍 (Object-Oriented Programming)|객체 지향 프로그래밍 (Object-Oriented Programming)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 객체 지향 프로그래밍(OOP)은 1980년대에 부상하여 데이터와 행위를 객체(Object) 내에 캡슐화하는 개념을 도입한 프로그래밍 패러다임입니다 [1, 2]. 이 방식은 시스템을 기능 단위로 수직적 분리를 이루게 하며, 객체 간의 책임을 나누어 클래스를 설계합니다 [3]. 캡슐화, 상속, 다형성 등의 원칙을 활용하여 소프트웨어의 복잡성을 관리하고 '관심사의 분리(SoC)'를 촉진하는 데 중점을 둡니다 [2]. @@ -23,11 +23,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 객체 지향 프로그래밍 - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[SOLID Principles]], [[Separation of Concerns (SoC)]], [[Aspect-Oriented Programming (AOP)]], [[Encapsulation]], [[Inheritance]], [[Polymorphism]] -- **Projects/Contexts:** [[소프트웨어 아키텍처 및 시스템 설계]], [[유지보수 및 확장성 관리를 위한 엔터프라이즈 애플리케이션]] +- **Related Topics:** [[SOLID Principles|SOLID Principles]], [[관심사의 분리 (Separation of Concerns SoC)|Separation of Concerns (SoC)]], Aspect-Oriented Programming (AOP), Encapsulation, Inheritance, Polymorphism +- **Projects/Contexts:** 소프트웨어 아키텍처 및 시스템 설계, 유지보수 및 확장성 관리를 위한 엔터프라이즈 애플리케이션 - **Contradictions/Notes:** 소스에 따르면 OOP는 객체 간 책임 분리와 기능 단위의 모듈화에 뛰어난 강점을 보이지만 모든 관심사 분리에 완벽한 것은 아닙니다. 시스템 전체에 퍼져 있는 공통 로직(횡단 관심사)을 효율적으로 분리하기 위해서는 AOP(관점 지향 프로그래밍)의 수평적 분리 접근 방식을 혼합하여 단점을 보완해야 합니다 [3]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/객체 지향 프로그래밍 (Object-Oriented Programming).md]] +- Raw Source: 00_Raw/2026-04-20/객체 지향 프로그래밍 (Object-Oriented Programming).md --- diff --git a/01_Archive/2026-04-20/객체 지향 프로그래밍(OOP).md b/01_Archive/2026-04-20/객체 지향 프로그래밍(OOP).md index c5fd52f3..76e637b3 100644 --- a/01_Archive/2026-04-20/객체 지향 프로그래밍(OOP).md +++ b/01_Archive/2026-04-20/객체 지향 프로그래밍(OOP).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-9FB550 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 객체 지향 프로그래밍(OOP)" --- -# [[객체 지향 프로그래밍(OOP)]] +# [[객체 지향 프로그래밍(OOP)|객체 지향 프로그래밍(OOP)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 객체 지향 프로그래밍(OOP)은 데이터와 그 동작(behavior)을 하나의 '객체(Object)' 내에 캡슐화하여 코드를 구성하는 프로그래밍 패러다임입니다 [1, 2]. 이 방식은 각 객체가 특정 기능이나 관심사에 대한 책임을 지도록 설계함으로써 관심사의 분리(Separation of Concerns)를 자연스럽게 이끌어냅니다 [1, 2]. 주로 기능 단위의 수직적 분리를 통해 객체 간의 책임을 나누며, 소프트웨어 설계를 더욱 이해하기 쉽고 유연하며 유지보수하기 좋게 만듭니다 [3-5]. @@ -23,11 +23,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 객체 지향 프로그래밍( - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[SOLID Principles]], [[Separation of Concerns (SoC)]], [[Aspect-Oriented Programming (AOP)]], [[캡슐화(Encapsulation)]], [[상속(Inheritance)]] +- **Related Topics:** [[SOLID Principles|SOLID Principles]], [[관심사의 분리 (Separation of Concerns SoC)|Separation of Concerns (SoC)]], Aspect-Oriented Programming (AOP), 캡슐화(Encapsulation), 상속(Inheritance) - **Projects/Contexts:** 확장 가능하고 모듈화된 시스템 아키텍처 및 라이브러리 설계의 기본 바탕이 되며, 실무 기술 면접에서도 소프트웨어 설계 철학을 확인하기 위한 단골 질문으로 다루어집니다 [1, 8, 9]. - **Contradictions/Notes:** 소스 간의 직접적인 의견 대립이나 모순에 대한 정보는 부족합니다. 다만 참고 사항으로, OOP 고유의 수직적 책임 분리만으로는 중복을 완벽히 제거하기 힘든 횡단 관심사가 존재하며, 소스에서는 이를 해결하기 위해 AOP 기법이 보완적으로 적용된다는 점을 강조하고 있습니다 [4, 5]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/객체 지향 프로그래밍(OOP).md]] +- Raw Source: 00_Raw/2026-04-20/객체 지향 프로그래밍(OOP).md --- diff --git a/01_Archive/2026-04-20/건강 심리학.md b/01_Archive/2026-04-20/건강 심리학.md index 1e85917e..868eb8db 100644 --- a/01_Archive/2026-04-20/건강 심리학.md +++ b/01_Archive/2026-04-20/건강 심리학.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-801A0D -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 건강 심리학" --- -# [[건강 심리학]] +# [[건강 심리학|건강 심리학]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - 건강 심리학" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/건강 심리학.md]] +- Raw Source: 00_Raw/2026-04-20/건강 심리학.md --- diff --git a/01_Archive/2026-04-20/건강 행동 변화 모델.md b/01_Archive/2026-04-20/건강 행동 변화 모델.md index b97b4ac0..7ecb1c4f 100644 --- a/01_Archive/2026-04-20/건강 행동 변화 모델.md +++ b/01_Archive/2026-04-20/건강 행동 변화 모델.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-77EB30 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 건강 행동 변화 모델" --- -# [[건강 행동 변화 모델]] +# [[건강 행동 변화 모델|건강 행동 변화 모델]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - 건강 행동 변화 모델" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/건강 행동 변화 모델.md]] +- Raw Source: 00_Raw/2026-04-20/건강 행동 변화 모델.md --- diff --git a/01_Archive/2026-04-20/게임 디자인 이론 및 구조론.md b/01_Archive/2026-04-20/게임 디자인 이론 및 구조론.md index a6d7f0f0..01662641 100644 --- a/01_Archive/2026-04-20/게임 디자인 이론 및 구조론.md +++ b/01_Archive/2026-04-20/게임 디자인 이론 및 구조론.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-D69C13 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 게임 디자인 이론 및 구조론" --- -# [[게임 디자인 이론 및 구조론]] +# [[게임 디자인 이론 및 구조론|게임 디자인 이론 및 구조론]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - 게임 디자인 이론 및 ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/게임 디자인 이론 및 구조론.md]] +- Raw Source: 00_Raw/2026-04-20/게임 디자인 이론 및 구조론.md --- diff --git a/01_Archive/2026-04-20/게임 디자인의 보상 루프(Reward Loop) 설계.md b/01_Archive/2026-04-20/게임 디자인의 보상 루프(Reward Loop) 설계.md index 54c178aa..fe380ed6 100644 --- a/01_Archive/2026-04-20/게임 디자인의 보상 루프(Reward Loop) 설계.md +++ b/01_Archive/2026-04-20/게임 디자인의 보상 루프(Reward Loop) 설계.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-A6178D -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 게임 디자인의 보상 루프(Reward Loop) 설계" --- -# [[게임 디자인의 보상 루프(Reward Loop) 설계]] +# [[게임 디자인의 보상 루프(Reward Loop) 설계|게임 디자인의 보상 루프(Reward Loop) 설계]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - 게임 디자인의 보상 루 ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/게임 디자인의 보상 루프(Reward Loop) 설계.md]] +- Raw Source: 00_Raw/2026-04-20/게임 디자인의 보상 루프(Reward Loop) 설계.md --- diff --git a/01_Archive/2026-04-20/게임 루프 설계.md b/01_Archive/2026-04-20/게임 루프 설계.md index ba4b8096..3431337a 100644 --- a/01_Archive/2026-04-20/게임 루프 설계.md +++ b/01_Archive/2026-04-20/게임 루프 설계.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-59E3A9 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 게임 루프 설계" --- -# [[게임 루프 설계]] +# [[게임 루프 설계|게임 루프 설계]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - 게임 루프 설계" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/게임 루프 설계.md]] +- Raw Source: 00_Raw/2026-04-20/게임 루프 설계.md --- diff --git a/01_Archive/2026-04-20/게임 행동 심리학.md b/01_Archive/2026-04-20/게임 행동 심리학.md index 43257746..2c80d198 100644 --- a/01_Archive/2026-04-20/게임 행동 심리학.md +++ b/01_Archive/2026-04-20/게임 행동 심리학.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-BB80E3 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 게임 행동 심리학" --- -# [[게임 행동 심리학]] +# [[게임 행동 심리학|게임 행동 심리학]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - 게임 행동 심리학" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/게임 행동 심리학.md]] +- Raw Source: 00_Raw/2026-04-20/게임 행동 심리학.md --- diff --git a/01_Archive/2026-04-20/게임학(Ludology) vs 서사학(Narratology) 논쟁.md b/01_Archive/2026-04-20/게임학(Ludology) vs 서사학(Narratology) 논쟁.md index 04de56e4..1a10c3f8 100644 --- a/01_Archive/2026-04-20/게임학(Ludology) vs 서사학(Narratology) 논쟁.md +++ b/01_Archive/2026-04-20/게임학(Ludology) vs 서사학(Narratology) 논쟁.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-1A5F45 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 게임학(Ludology) vs 서사학(Narratology) 논쟁" --- -# [[게임학(Ludology) vs 서사학(Narratology) 논쟁]] +# [[게임학(Ludology) vs 서사학(Narratology) 논쟁|게임학(Ludology) vs 서사학(Narratology) 논쟁]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - 게임학(Ludology) vs 서사 ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/게임학(Ludology) vs 서사학(Narratology) 논쟁.md]] +- Raw Source: 00_Raw/2026-04-20/게임학(Ludology) vs 서사학(Narratology) 논쟁.md --- diff --git a/01_Archive/2026-04-20/견고한 도메인 모델 및 API 계약 설계.md b/01_Archive/2026-04-20/견고한 도메인 모델 및 API 계약 설계.md index 33d86227..9fe2cd9c 100644 --- a/01_Archive/2026-04-20/견고한 도메인 모델 및 API 계약 설계.md +++ b/01_Archive/2026-04-20/견고한 도메인 모델 및 API 계약 설계.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-E5BF95 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 견고한 도메인 모델 및 API 계약 설계" --- -# [[견고한 도메인 모델 및 API 계약 설계]] +# [[견고한 도메인 모델 및 API 계약 설계|견고한 도메인 모델 및 API 계약 설계]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 견고한 도메인 모델 및 API 계약 설계는 TypeScript의 정적 타입 시스템을 활용하여 유효하지 않은 상태를 원천 차단하고 예측 가능한 애플리케이션 구조를 만드는 과정입니다. 이를 위해 식별 가능한 유니온, 브랜디드 타입, 불변성 제약, 그리고 "검증하지 말고 파싱하라"와 같은 설계 철학을 결합하여, 경계면에서부터 데이터의 무결성을 보장하는 안전한 계약을 수립합니다. @@ -25,11 +25,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 견고한 도메인 모델 및 - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Parse, don't validate]], [[식별 가능한 유니온 (Discriminated Unions)]], [[브랜디드 타입 (Branded Types)]], [[Satisfies 연산자]], [[불변성 (Immutability)]], [[Result 타입]] -- **Projects/Contexts:** [[Zod를 활용한 런타임 데이터 검증]], [[API 응답 처리 및 상태 머신 모델링]] +- **Related Topics:** [[Parse, don't validate|Parse, don't validate]], [[식별 가능한 유니온 (Discriminated Unions)|식별 가능한 유니온 (Discriminated Unions)]], [[브랜디드 타입 (Branded Types)|브랜디드 타입 (Branded Types)]], [[satisfies 연산자|Satisfies 연산자]], [[불변성 (Immutability)|불변성 (Immutability)]], Result 타입 +- **Projects/Contexts:** Zod를 활용한 런타임 데이터 검증, API 응답 처리 및 상태 머신 모델링 - **Contradictions/Notes:** 소스에 따르면 교집합(`&`)과 타입 별칭(`type`)만으로도 객체를 조합할 수 있지만, 대규모 프로젝트의 성능과 컴파일러 캐싱 최적화를 고려할 때 핵심 도메인 객체 선언에는 인터페이스 상속(`interface extends`)을 우선시하는 것이 권장됩니다 [32-34]. 또한 비즈니스 흐름 제어를 위해 전통적인 예외(`Exception`) 투척보다는 `Result` 패턴을 활용하는 방식이 더욱 안전한 설계로 제시됩니다 [28, 30, 35]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/견고한 도메인 모델 및 API 계약 설계.md]] +- Raw Source: 00_Raw/2026-04-20/견고한 도메인 모델 및 API 계약 설계.md --- diff --git a/01_Archive/2026-04-20/결정 속도(Decision Speed).md b/01_Archive/2026-04-20/결정 속도(Decision Speed).md index c1bdda45..1572debb 100644 --- a/01_Archive/2026-04-20/결정 속도(Decision Speed).md +++ b/01_Archive/2026-04-20/결정 속도(Decision Speed).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-527675 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 결정 속도(Decision Speed)" --- -# [[결정 속도(Decision Speed)]] +# [[결정 속도(Decision Speed)|결정 속도(Decision Speed)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 결정 속도(Decision Speed)는 목표 자극이 나타난 순간부터 사용자가 판단을 내리고 행동을 개시하기까지 걸린 시간을 나타내는 인지적 측정 지표입니다 [1]. 이는 주로 전체 반응 시간(Reaction Time)을 구성하는 핵심 요소 중 하나로, 물리적인 동작 속도(Movement Speed)와는 구별되는 개념입니다 [1]. 가상현실(VR) 엑서게임(Exergaming)의 인지적 사후 효과를 측정하거나, 고도의 인지적 통제력과 빠른 판단력이 요구되는 e스포츠에서 선수의 수행 능력을 평가하는 맥락에서 중요한 변수로 다뤄집니다 [1, 2]. @@ -20,11 +20,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 결정 속도(Decision Speed)" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[반응 시간(Reaction Time)]], [[동작 속도(Movement Speed)]] -- **Projects/Contexts:** [[가상현실(VR) 엑서게임 인지 사후 효과 분석(CANTAB 5-choice RTI)]], [[e스포츠 인지 상태 및 성과 위험 평가]] +- **Related Topics:** [[반응 시간(Reaction Time)|반응 시간(Reaction Time)]], [[동작 속도(Movement Speed)|동작 속도(Movement Speed)]] +- **Projects/Contexts:** [[가상현실(VR) 엑서게임 인지 사후 효과 분석(CANTAB 5-choice RTI)|가상현실(VR) 엑서게임 인지 사후 효과 분석(CANTAB 5-choice RTI)]], [[e스포츠 인지 상태 및 성과 위험 평가|e스포츠 인지 상태 및 성과 위험 평가]] - **Contradictions/Notes:** 소스 내에서 직접적인 모순은 없으나, VR 노출이 반응 및 결정 속도에 미치는 영향에 대한 기존 학계 문헌들은 긍정적 효과(반응 속도 증가)와 부정적 효과(반응 속도 감소)가 혼재되어 있어 매우 일관되지 않은(highly inconsistent) 결과를 보인다는 점이 언급되어 있습니다 [6]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/결정 속도(Decision Speed).md]] +- Raw Source: 00_Raw/2026-04-20/결정 속도(Decision Speed).md --- diff --git a/01_Archive/2026-04-20/결합도 (Coupling).md b/01_Archive/2026-04-20/결합도 (Coupling).md index cc876059..0edbe58f 100644 --- a/01_Archive/2026-04-20/결합도 (Coupling).md +++ b/01_Archive/2026-04-20/결합도 (Coupling).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-1DFEC5 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 결합도 (Coupling)" --- -# [[결합도 (Coupling)]] +# [[결합도 (Coupling)|결합도 (Coupling)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 결합도(Coupling)는 소프트웨어 설계에서 모듈 간의 상호 의존성 정도를 나타내는 척도입니다 [1, 2]. 결합도가 낮다는 것은 모듈 간의 의존성이 적어 각 모듈이 독립적으로 동작할 수 있음을 의미하며, 반대로 결합도가 높으면 하나의 모듈을 변경할 때 다른 모듈에도 연쇄적인 영향을 미치게 됩니다 [2]. 성공적인 소프트웨어 아키텍처를 구현하기 위해서는 시스템의 복잡성을 줄이고 유지보수성을 높일 수 있도록 낮은 결합도를 지향해야 합니다 [2, 3]. @@ -36,11 +36,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 결합도 (Coupling)" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[응집도 (Cohesion)]], [[관심사의 분리 (Separation of Concerns)]], [[의존성 주입 (Dependency Injection)]], [[단일 책임 원칙 (Single Responsibility Principle)]] -- **Projects/Contexts:** [[소프트웨어 아키텍처 설계]], [[마이크로서비스 아키텍처]], [[이벤트 기반 아키텍처]] +- **Related Topics:** [[응집도 (Cohesion)|응집도 (Cohesion)]], [[관심사의 분리 (Separation of Concerns)|관심사의 분리 (Separation of Concerns)]], [[의존성 주입 (Dependency Injection)|의존성 주입 (Dependency Injection)]], [[단일 책임 원칙 (Single Responsibility Principle)|단일 책임 원칙 (Single Responsibility Principle)]] +- **Projects/Contexts:** [[소프트웨어 아키텍처 설계|소프트웨어 아키텍처 설계]], [[마이크로서비스 아키텍처|마이크로서비스 아키텍처]], 이벤트 기반 아키텍처 - **Contradictions/Notes:** 모듈 간 결합도를 낮추기 위해 관심사를 엄격하게 분리하는 것은 유지보수성을 크게 향상하지만, 추상화 레이어가 지나치게 많아지면 시스템 내 구성요소 간의 상호작용을 파악하기 힘들어지거나 통신 오버헤드가 발생하여 전체적인 시스템의 복잡성이 오히려 증가할 수 있다는 단점도 수반됩니다 [6, 7]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/결합도 (Coupling).md]] +- Raw Source: 00_Raw/2026-04-20/결합도 (Coupling).md --- diff --git a/01_Archive/2026-04-20/경고 피로 (Alert Fatigue).md b/01_Archive/2026-04-20/경고 피로 (Alert Fatigue).md index 6add8c0e..5bfb4f1c 100644 --- a/01_Archive/2026-04-20/경고 피로 (Alert Fatigue).md +++ b/01_Archive/2026-04-20/경고 피로 (Alert Fatigue).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-642AF9 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 경고 피로 (Alert Fatigue)" --- -# [[경고 피로 (Alert Fatigue)]] +# [[경고 피로 (Alert Fatigue)|경고 피로 (Alert Fatigue)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 경고 피로(Alert Fatigue)는 자동화된 코드 리뷰나 보안 스캐닝 도구가 사소한 문제나 오탐지(False Positives)를 포함한 수많은 경고를 개발자에게 과도하게 쏟아낼 때 발생하는 현상입니다 [1, 2]. 개발자가 쏟아지는 알림(노이즈)에 압도되면 결국 도구의 출력 결과를 무시하게 되며, 이로 인해 실제로 중요한 보안 취약점이나 치명적인 경고조차 놓치게 됩니다 [2, 3]. 따라서 보안 도구의 효과를 유지하기 위해서는 경고 피로를 세심하게 관리하는 것이 필수적입니다 [1]. @@ -28,11 +28,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 경고 피로 (Alert Fatigue)" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[오탐지 (False Positives)]], [[자동화된 코드 리뷰 (Automated Code Review)]], [[정적 애플리케이션 보안 테스트 (SAST)]] -- **Projects/Contexts:** [[Endor Labs]], [[JetBrains Qodana]] +- **Related Topics:** 오탐지 (False Positives), 자동화된 코드 리뷰 (Automated Code Review), [[정적 애플리케이션 보안 테스트 (SAST)|정적 애플리케이션 보안 테스트 (SAST)]] +- **Projects/Contexts:** Endor Labs, JetBrains Qodana - **Contradictions/Notes:** 소스 전반에서 자동화된 코드 분석 도구가 빠르고 일관적이라는 큰 장점을 제공한다고 주장하지만, 동시에 문맥 이해 부족에서 기인하는 과도한 오탐지가 '경고 피로'를 유발하여 도구의 효용성을 떨어뜨린다는 한계점을 공통적으로 지적하고 있습니다 [1, 2]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/경고 피로 (Alert Fatigue).md]] +- Raw Source: 00_Raw/2026-04-20/경고 피로 (Alert Fatigue).md --- diff --git a/01_Archive/2026-04-20/계층형 아키텍처 (Layered Architecture).md b/01_Archive/2026-04-20/계층형 아키텍처 (Layered Architecture).md index cd0a6b99..3b4ff234 100644 --- a/01_Archive/2026-04-20/계층형 아키텍처 (Layered Architecture).md +++ b/01_Archive/2026-04-20/계층형 아키텍처 (Layered Architecture).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-28439B -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 계층형 아키텍처 (Layered Architecture)" --- -# [[계층형 아키텍처 (Layered Architecture)]] +# [[계층형 아키텍처 (Layered Architecture)|계층형 아키텍처 (Layered Architecture)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 계층형 아키텍처(Layered Architecture), 또는 n-tier 아키텍처는 시스템을 수평적인 계층(Layer)들로 나누어 구성하는 전통적이고 영향력 있는 소프트웨어 설계 패턴입니다 [1, 2]. 각 계층은 특정한 책임을 가지며, 인접한 하위 계층하고만 소통하도록 통신을 제한하여 엄격한 관심사의 분리(Separation of Concerns)를 강제합니다 [2, 3]. 이 아키텍처의 주된 목표는 시스템을 명확히 구조화하여 개발, 테스트, 유지보수성을 단순화하고 모듈성을 향상시키는 것입니다 [2, 4]. @@ -31,11 +31,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 계층형 아키텍처 (Layere - **정책 변화:** Design & Experience 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[관심사의 분리 (Separation of Concerns)]], [[N-Tier 아키텍처 (N-Tier Architecture)]], [[의존성 주입 (Dependency Injection)]], [[단일 책임 원칙 (SRP)]] -- **Projects/Contexts:** [[엔터프라이즈 애플리케이션]], [[웹 애플리케이션 3계층 시스템 (3-Tier Systems)]] +- **Related Topics:** [[관심사의 분리 (Separation of Concerns)|관심사의 분리 (Separation of Concerns)]], N-Tier 아키텍처 (N-Tier Architecture), [[의존성 주입 (Dependency Injection)|의존성 주입 (Dependency Injection)]], [[단일 책임 원칙 (SRP)|단일 책임 원칙 (SRP)]] +- **Projects/Contexts:** 엔터프라이즈 애플리케이션, 웹 애플리케이션 3계층 시스템 (3-Tier Systems) - **Contradictions/Notes:** 소스에 따르면, 계층형 아키텍처는 명확한 분리를 제공해 주지만 레이어를 무겁게 만들면 오히려 시스템 관리가 비효율적일 수 있으므로, 계층을 얇게 유지(Keep layers thin)하고 인터페이스와 의존성 주입을 적극 활용하여 경계를 명확히 보호할 것을 권장하고 있습니다 [8, 9]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/계층형 아키텍처 (Layered Architecture).md]] +- Raw Source: 00_Raw/2026-04-20/계층형 아키텍처 (Layered Architecture).md --- diff --git a/01_Archive/2026-04-20/계층화 아키텍처 (Layered Architecture).md b/01_Archive/2026-04-20/계층화 아키텍처 (Layered Architecture).md index bd25b4b7..d049fec8 100644 --- a/01_Archive/2026-04-20/계층화 아키텍처 (Layered Architecture).md +++ b/01_Archive/2026-04-20/계층화 아키텍처 (Layered Architecture).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-1EAECE -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 계층화 아키텍처 (Layered Architecture)" --- -# [[계층화 아키텍처 (Layered Architecture)]] +# [[계층화 아키텍처 (Layered Architecture)|계층화 아키텍처 (Layered Architecture)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 계층화 아키텍처(Layered Architecture)는 시스템을 특정 책임을 가진 여러 수평적 계층(Layer)으로 나누어 구성하는 전통적이고 영향력 있는 소프트웨어 설계 패턴입니다 [1]. 각 계층은 사용자 인터페이스, 비즈니스 로직, 데이터 접근 등 특정 관심사(Concern)만을 전담하여 엄격한 관심사의 분리(SoC)를 강제합니다 [1, 2]. 이를 통해 각 계층은 주로 인접한 계층과만 소통하게 되며, 결과적으로 시스템의 결합도를 낮추고 유지보수성, 확장성 및 테스트 용이성을 크게 향상시키는 것을 목표로 합니다 [1, 3]. @@ -28,11 +28,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 계층화 아키텍처 (Layere - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[응집도와 결합도 (Cohesion and Coupling)]], [[단일 책임 원칙 (SRP)]], [[의존성 역전 원칙 (DIP)]], [[클린 아키텍처 (Clean Architecture)]] -- **Projects/Contexts:** [[웹 애플리케이션의 3계층 구조]], [[엔터프라이즈 애플리케이션 설계]] +- **Related Topics:** [[응집도와 결합도 (Cohesion and Coupling)|응집도와 결합도 (Cohesion and Coupling)]], [[단일 책임 원칙 (SRP)|단일 책임 원칙 (SRP)]], [[의존성 역전 원칙 (DIP)|의존성 역전 원칙 (DIP)]], [[클린 아키텍처 (Clean Architecture)|클린 아키텍처 (Clean Architecture)]] +- **Projects/Contexts:** [[웹 애플리케이션의 3계층 구조|웹 애플리케이션의 3계층 구조]], [[엔터프라이즈 애플리케이션 설계|엔터프라이즈 애플리케이션 설계]] - **Contradictions/Notes:** 소스는 계층화 아키텍처가 시스템의 복잡성을 줄이고 관심사를 성공적으로 격리한다고 긍정적으로 평가하지만, 동시에 지나친 관심사 분리(과도한 계층화 및 추상화)는 여러 계층을 거쳐야 하는 성능 오버헤드를 유발하거나, 오히려 코드를 추적하기 어렵게 만드는 '인디렉션의 저주(Curse of Indirection)'를 발생시킬 수 있다고 경고합니다 [11-13]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/계층화 아키텍처 (Layered Architecture).md]] +- Raw Source: 00_Raw/2026-04-20/계층화 아키텍처 (Layered Architecture).md --- diff --git a/01_Archive/2026-04-20/고성능 3D WebGL 게임 렌더링 엔진.md b/01_Archive/2026-04-20/고성능 3D WebGL 게임 렌더링 엔진.md index fd85a31e..8ddda779 100644 --- a/01_Archive/2026-04-20/고성능 3D WebGL 게임 렌더링 엔진.md +++ b/01_Archive/2026-04-20/고성능 3D WebGL 게임 렌더링 엔진.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-BD05D2 -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 고성능 3D WebGL 게임 렌더링 엔진" --- -# [[고성능 3D WebGL 게임 렌더링 엔진]] +# [[고성능 3D WebGL 게임 렌더링 엔진|고성능 3D WebGL 게임 렌더링 엔진]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - 고성능 3D WebGL 게임 렌 ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/고성능 3D WebGL 게임 렌더링 엔진.md]] +- Raw Source: 00_Raw/2026-04-20/고성능 3D WebGL 게임 렌더링 엔진.md --- diff --git a/01_Archive/2026-04-20/고성능 멀티스레드 React 앱 아키텍처.md b/01_Archive/2026-04-20/고성능 멀티스레드 React 앱 아키텍처.md index cf926c8d..c581e925 100644 --- a/01_Archive/2026-04-20/고성능 멀티스레드 React 앱 아키텍처.md +++ b/01_Archive/2026-04-20/고성능 멀티스레드 React 앱 아키텍처.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-87DB97 -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 고성능 멀티스레드 React 앱 아키텍처" --- -# [[고성능 멀티스레드 React 앱 아키텍처]] +# [[고성능 멀티스레드 React 앱 아키텍처|고성능 멀티스레드 React 앱 아키텍처]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 자바스크립트의 단일 스레드(Single-thread) 제약을 극복하기 위해 웹 워커(Web Worker)와 OffscreenCanvas를 활용하여 무거운 CPU 연산이나 3D 그래픽 렌더링을 백그라운드로 분리하고, 메인 스레드와 고효율로 상태를 동기화하여 초당 60프레임(FPS)의 매끄러운 반응성을 보장하는 진보된 애플리케이션 설계 패턴입니다. @@ -31,12 +31,12 @@ github_commit: "[P-Reinforce] Continuous Worker - 고성능 멀티스레드 Reac - **정책 변화:** Graphics & Performance 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Web Worker (웹 워커)]], [[OffscreenCanvas]], [[SharedArrayBuffer]], [[Valtio (Proxy State 관리)]], [[Event Forwarding (이벤트 포워딩)]] -- **Projects/Contexts:** [[대규모 데이터 분석 및 시각화 대시보드]], [[고성능 실시간 WebGL 게임 엔진]], [[서드파티 스크립트가 많은 엔터프라이즈 앱 성능 개선]] +- **Related Topics:** [[Web Worker (웹 워커)|Web Worker (웹 워커)]], [[OffscreenCanvas|OffscreenCanvas]], [[SharedArrayBuffer|SharedArrayBuffer]], Valtio (Proxy State 관리), Event Forwarding (이벤트 포워딩) +- **Projects/Contexts:** 대규모 데이터 분석 및 시각화 대시보드, 고성능 실시간 WebGL 게임 엔진, 서드파티 스크립트가 많은 엔터프라이즈 앱 성능 개선 - **Contradictions/Notes:** 멀티스레딩이 무조건적인 성능 향상을 가져오지는 않습니다. 스레드 간에 메시지를 주고받는 과정(Message passing)에는 직렬화로 인한 오버헤드(약 5~10ms)가 수반됩니다. 연산 시간이 50ms 미만인 비교적 가벼운 작업을 워커로 분리하면 오히려 통신 비용이 연산 시간보다 커져 성능이 하락할 수 있으므로 철저한 프로파일링을 기반으로 병목 구간에만 선택적으로 적용해야 합니다. --- _Last updated: 2026-04-15_ -- Raw Source: [[00_Raw/2026-04-20/고성능 멀티스레드 React 앱 아키텍처.md]] +- Raw Source: 00_Raw/2026-04-20/고성능 멀티스레드 React 앱 아키텍처.md --- diff --git a/01_Archive/2026-04-20/고성능 실시간 상호작용 시스템을 위한 React 기반 게임 엔진 아키텍처.md b/01_Archive/2026-04-20/고성능 실시간 상호작용 시스템을 위한 React 기반 게임 엔진 아키텍처.md index df8384c4..5601e122 100644 --- a/01_Archive/2026-04-20/고성능 실시간 상호작용 시스템을 위한 React 기반 게임 엔진 아키텍처.md +++ b/01_Archive/2026-04-20/고성능 실시간 상호작용 시스템을 위한 React 기반 게임 엔진 아키텍처.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-416C0F -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 고성능 실시간 상호작용 시스템을 위한 React 기반 게임 엔진 아키텍처" --- -# [[고성능 실시간 상호작용 시스템을 위한 React 기반 게임 엔진 아키텍처]] +# [[고성능 실시간 상호작용 시스템을 위한 React 기반 게임 엔진 아키텍처|고성능 실시간 상호작용 시스템을 위한 React 기반 게임 엔진 아키텍처]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - 고성능 실시간 상호작 ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/고성능 실시간 상호작용 시스템을 위한 React 기반 게임 엔진 아키텍처.md]] +- Raw Source: 00_Raw/2026-04-20/고성능 실시간 상호작용 시스템을 위한 React 기반 게임 엔진 아키텍처.md --- diff --git a/01_Archive/2026-04-20/고전적 조건 형성.md b/01_Archive/2026-04-20/고전적 조건 형성.md index d69b1d71..35f9caa9 100644 --- a/01_Archive/2026-04-20/고전적 조건 형성.md +++ b/01_Archive/2026-04-20/고전적 조건 형성.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-46AEE6 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 고전적 조건 형성" --- -# [[고전적 조건 형성]] +# [[고전적 조건 형성|고전적 조건 형성]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - 고전적 조건 형성" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/고전적 조건 형성.md]] +- Raw Source: 00_Raw/2026-04-20/고전적 조건 형성.md --- diff --git a/01_Archive/2026-04-20/공급망 공격 (Supply Chain Attack).md b/01_Archive/2026-04-20/공급망 공격 (Supply Chain Attack).md index c7cb3f13..99cbd091 100644 --- a/01_Archive/2026-04-20/공급망 공격 (Supply Chain Attack).md +++ b/01_Archive/2026-04-20/공급망 공격 (Supply Chain Attack).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-2BF446 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 공급망 공격 (Supply Chain Attack)" --- -# [[공급망 공격 (Supply Chain Attack)]] +# [[공급망 공격 (Supply Chain Attack)|공급망 공격 (Supply Chain Attack)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 공급망 공격(Supply Chain Attack)은 오픈소스 파이프라인이 상호 신뢰를 바탕으로 운영된다는 점을 악용하여, 널리 사용되는 합법적인 패키지나 개발 도구의 유지보수자 계정을 탈취해 악성 코드를 다운스트림 환경에 유포하는 공격 방식입니다 [1]. 한 명의 유지보수자 계정이나 단일 패키지가 손상되는 것만으로도 수천만 건의 설치로 피해가 파급될 수 있어 소프트웨어 생태계 전반에 대규모 위험을 초래합니다 [1, 2]. 코드 품질과 안전을 보장하기 위해 사용하는 도구 자체가 개발자를 공격하는 무기로 돌변할 수 있다는 점에서 현대 소프트웨어 개발의 중대한 위협으로 꼽힙니다 [2]. @@ -30,11 +30,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 공급망 공격 (Supply Chain - **정책 변화:** AI 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[CVE-2025-54313]], [[Software Composition Analysis (SCA)]], [[eslint-config-prettier]] -- **Projects/Contexts:** [[npm registry]], [[Open Source Security]] +- **Related Topics:** CVE-2025-54313, [[Software Composition Analysis (SCA)|Software Composition Analysis (SCA)]], [[eslint-config-prettier|eslint-config-prettier]] +- **Projects/Contexts:** npm registry, Open Source Security - **Contradictions/Notes:** 소스에 관련된 모순점은 발견되지 않았습니다. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/공급망 공격 (Supply Chain Attack).md]] +- Raw Source: 00_Raw/2026-04-20/공급망 공격 (Supply Chain Attack).md --- diff --git a/01_Archive/2026-04-20/공존 질환 (Comorbidity).md b/01_Archive/2026-04-20/공존 질환 (Comorbidity).md index 93006dfa..ac4e8c9a 100644 --- a/01_Archive/2026-04-20/공존 질환 (Comorbidity).md +++ b/01_Archive/2026-04-20/공존 질환 (Comorbidity).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-ACDF2F -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 공존 질환 (Comorbidity)" --- -# [[공존 질환 (Comorbidity)]] +# [[공존 질환 (Comorbidity)|공존 질환 (Comorbidity)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - 공존 질환 (Comorbidity)" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/공존 질환 (Comorbidity).md]] +- Raw Source: 00_Raw/2026-04-20/공존 질환 (Comorbidity).md --- diff --git a/01_Archive/2026-04-20/과잉 속성 체크 (Excess Property Checking).md b/01_Archive/2026-04-20/과잉 속성 체크 (Excess Property Checking).md index 20b1f451..097f37a5 100644 --- a/01_Archive/2026-04-20/과잉 속성 체크 (Excess Property Checking).md +++ b/01_Archive/2026-04-20/과잉 속성 체크 (Excess Property Checking).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-9B5810 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 과잉 속성 체크 (Excess Property Checking)" --- -# [[과잉 속성 체크 (Excess Property Checking)]] +# [[과잉 속성 체크 (Excess Property Checking)|과잉 속성 체크 (Excess Property Checking)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > TypeScript의 과잉 속성 체크(Excess Property Checking, EPC)는 객체 리터럴이 다른 변수에 직접 할당되거나 함수의 인자로 전달될 때, 대상 타입에 정의되지 않은 속성이 포함되어 있는지를 엄격하게 검사하는 기능이다[1-4]. 이는 구조적 타이핑(Structural Typing)의 유연함으로 인해 속성 이름의 오타나 잘못된 데이터가 유입되어 발생하는 런타임 오류를 컴파일 시점에 방지하는TypeScript의 핵심 방어 기제로 작동한다[5-7]. @@ -23,11 +23,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 과잉 속성 체크 (Excess P - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[구조적 타이핑 (Structural Typing)]], [[satisfies 연산자]], [[타입 캐스팅 (Type Casting)]], [[약한 타입 탐지 (Weak Type Detection)]] -- **Projects/Contexts:** [[철벽 수비대" - TypeScript 타입 시스템 (인터페이스 설계)]], [[React 컴포넌트 Props 검증]] +- **Related Topics:** [[구조적 타이핑 (Structural Typing)|구조적 타이핑 (Structural Typing)]], [[satisfies 연산자|satisfies 연산자]], [[타입 캐스팅 (Type Casting)|타입 캐스팅 (Type Casting)]], [[약한 타입 탐지 (Weak Type Detection)|약한 타입 탐지 (Weak Type Detection)]] +- **Projects/Contexts:** [[철벽 수비대_ - TypeScript 타입 시스템 (인터페이스 설계)|철벽 수비대" - TypeScript 타입 시스템 (인터페이스 설계)]], [[React 컴포넌트 Props 검증|React 컴포넌트 Props 검증]] - **Contradictions/Notes:** 객체 리터럴을 직접 할당할 때는 과잉 속성 체크가 발동되어 에러를 반환하지만, 중간 변수를 통해 간접 할당될 때는 구조적 타이핑 원칙이 적용되어 과잉 속성이 존재해도 에러가 발생하지 않는 모순적 동작을 보인다[1, 3, 5, 12]. 또한 `as` 연산자는 과잉 속성을 무시하고 할당을 허용하지만, `satisfies` 연산자는 초과된 속성에 대해 엄격한 검증을 강제한다[16, 21]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/과잉 속성 체크 (Excess Property Checking).md]] +- Raw Source: 00_Raw/2026-04-20/과잉 속성 체크 (Excess Property Checking).md --- diff --git a/01_Archive/2026-04-20/과잉 속성 체크(EPC).md b/01_Archive/2026-04-20/과잉 속성 체크(EPC).md index 2f9979a2..161fcc4c 100644 --- a/01_Archive/2026-04-20/과잉 속성 체크(EPC).md +++ b/01_Archive/2026-04-20/과잉 속성 체크(EPC).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-13C5F5 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 과잉 속성 체크(EPC)" --- -# [[과잉 속성 체크(EPC)]] +# [[과잉 속성 체크(EPC)|과잉 속성 체크(EPC)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 과잉 속성 체크(EPC, Excess Property Checking)는 객체 리터럴을 변수에 직접 할당하거나 함수의 인수로 전달할 때, 예상치 못한(정의되지 않은) 속성이 포함되어 있는지 감지하여 에러를 발생시키는 TypeScript의 검사 기능입니다 [1], [2], [3]. 이는 속성명의 오타와 같은 개발자의 실수를 컴파일 시점에 방지하여 의도치 않은 런타임 버그를 예방하는 데 목적이 있습니다 [4], [5], [6]. @@ -30,11 +30,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 과잉 속성 체크(EPC)" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[구조적 타이핑(Structural Typing)]], [[satisfies 연산자]], [[객체 리터럴(Object Literals)]] -- **Projects/Contexts:** [[TypeScript 타입 검사 시스템]], [[React 컴포넌트 Props 검사]] +- **Related Topics:** [[구조적 타이핑(Structural Typing)|구조적 타이핑(Structural Typing)]], [[satisfies 연산자|satisfies 연산자]], 객체 리터럴(Object Literals) +- **Projects/Contexts:** TypeScript 타입 검사 시스템, React 컴포넌트 Props 검사 - **Contradictions/Notes:** 과잉 속성이 실제 버그를 유발하는 빈도에 대해서는 시각차가 존재합니다. 일부는 초과 속성이 런타임 이슈(리렌더링, 보안 문제)를 야기한다고 경고하지만 [12], [10], TypeScript-eslint 저장소의 일부 논의에서는 객체의 키나 값 세트에 대한 직접적인 연산이 없는 한 과잉 속성 자체가 실제로 버그를 유발하는 경우는 드물다고 주장합니다 [17]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/과잉 속성 체크(EPC).md]] +- Raw Source: 00_Raw/2026-04-20/과잉 속성 체크(EPC).md --- diff --git a/01_Archive/2026-04-20/과잉 속성 체크(Excess Property Checking).md b/01_Archive/2026-04-20/과잉 속성 체크(Excess Property Checking).md index 372e70ee..bc280e95 100644 --- a/01_Archive/2026-04-20/과잉 속성 체크(Excess Property Checking).md +++ b/01_Archive/2026-04-20/과잉 속성 체크(Excess Property Checking).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-7ED2D3 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 과잉 속성 체크(Excess Property Checking)" --- -# [[과잉 속성 체크(Excess Property Checking)]] +# [[과잉 속성 체크(Excess Property Checking)|과잉 속성 체크(Excess Property Checking)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 과잉 속성 체크(Excess Property Checking)는 TypeScript에서 객체 리터럴을 다른 변수에 직접 할당하거나 함수의 인자로 전달할 때, 예상치 못한(정의되지 않은) 잉여 속성이 포함되어 있는지 엄격하게 검사하여 에러를 발생시키는 기능입니다 [1-4]. 구조적 타이핑의 유연성 속에서 발생할 수 있는 오타나 잘못된 속성 전달 실수를 컴파일 시점에 포착하여 런타임 오류를 방지하는 첫 번째 방어선 역할을 합니다 [5-7]. @@ -22,11 +22,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 과잉 속성 체크(Excess Pr - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[구조적 타이핑(Structural Typing)]], [[satisfies 연산자]], [[약한 타입 검사(Weak Type Detection)]] -- **Projects/Contexts:** [[TypeScript의 인터페이스 및 객체 타입 설계]], [[React 컴포넌트 Props 전달 및 상태 관리]] +- **Related Topics:** [[구조적 타이핑(Structural Typing)|구조적 타이핑(Structural Typing)]], [[satisfies 연산자|satisfies 연산자]], [[약한 타입 검사(Weak Type Detection)|약한 타입 검사(Weak Type Detection)]] +- **Projects/Contexts:** [[TypeScript의 인터페이스 및 객체 타입 설계|TypeScript의 인터페이스 및 객체 타입 설계]], [[React 컴포넌트 Props 전달 및 상태 관리|React 컴포넌트 Props 전달 및 상태 관리]] - **Contradictions/Notes:** TypeScript는 구조적 타이핑을 핵심 철학으로 삼지만, "객체 리터럴"에 대해서만 과잉 속성 체크라는 예외적으로 엄격한 잣대를 적용합니다. 이로 인해 값을 직접 전달할 때와 중간 변수를 거쳐 전달할 때의 타입 검사 결과가 달라지는 동작 방식의 차이가 존재합니다 [3, 5, 11]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/과잉 속성 체크(Excess Property Checking).md]] +- Raw Source: 00_Raw/2026-04-20/과잉 속성 체크(Excess Property Checking).md --- diff --git a/01_Archive/2026-04-20/과잉 정당화 효과 (Overjustification Effect).md b/01_Archive/2026-04-20/과잉 정당화 효과 (Overjustification Effect).md index 49934c37..eed3da61 100644 --- a/01_Archive/2026-04-20/과잉 정당화 효과 (Overjustification Effect).md +++ b/01_Archive/2026-04-20/과잉 정당화 효과 (Overjustification Effect).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-CB8555 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 과잉 정당화 효과 (Overjustification Effect)" --- -# [[과잉 정당화 효과 (Overjustification Effect)]] +# [[과잉 정당화 효과 (Overjustification Effect)|과잉 정당화 효과 (Overjustification Effect)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - 과잉 정당화 효과 (Overj ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/과잉 정당화 효과 (Overjustification Effect).md]] +- Raw Source: 00_Raw/2026-04-20/과잉 정당화 효과 (Overjustification Effect).md --- diff --git a/01_Archive/2026-04-20/관심사의 분리 (Separation of Concerns SoC).md b/01_Archive/2026-04-20/관심사의 분리 (Separation of Concerns SoC).md index d82e962e..1f2ee4f7 100644 --- a/01_Archive/2026-04-20/관심사의 분리 (Separation of Concerns SoC).md +++ b/01_Archive/2026-04-20/관심사의 분리 (Separation of Concerns SoC).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-CE39CC -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 관심사의 분리 (Separation of Concerns SoC)" --- -# [[관심사의 분리 (Separation of Concerns SoC)]] +# [[관심사의 분리 (Separation of Concerns SoC)|관심사의 분리 (Separation of Concerns SoC)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 관심사의 분리(SoC)는 복잡한 소프트웨어 시스템을 더 작고 관리하기 쉬운 부분으로 나누어, 각 모듈이 단일한 관심사(기능이나 책임)만을 다루도록 설계하는 소프트웨어 공학의 근본적인 원칙이다 [1-3]. 1974년 에츠허르 데이크스트라(Edsger W. Dijkstra)가 처음 제안한 이 개념은 한 번에 모든 측면을 다루는 대신 특정 측면에 집중하여 복잡성을 통제하는 것을 목표로 한다 [4-6]. 이 원칙을 통해 시스템의 모듈성, 유지보수성, 재사용성 및 테스트 가능성을 획기적으로 향상시킬 수 있다 [1, 7, 8]. @@ -33,11 +33,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 관심사의 분리 (Separatio - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[단일 책임 원칙 (Single Responsibility Principle, SRP)]], [[응집도 (Cohesion)]], [[결합도 (Coupling)]], [[계층화 아키텍처 (Layered Architecture)]], [[마이크로서비스 아키텍처 (Microservices Architecture)]] -- **Projects/Contexts:** [[넷플릭스 코스모스 플랫폼 (Netflix Cosmos Platform)]] (마이크로서비스, 워크플로우, 서버리스 함수로 논리적 계층을 엄격히 분리하여 병목 현상을 해결한 사례 [34-36]), [[스포티파이 마이크로 프론트엔드 (Spotify Micro Frontends)]] (스쿼드 조직 모델과 프론트엔드의 관심사를 분리하여 독립적 개발과 배포를 가능하게 한 사례 [22]). +- **Related Topics:** 단일 책임 원칙 (Single Responsibility Principle, SRP), [[응집도 (Cohesion)|응집도 (Cohesion)]], [[결합도 (Coupling)|결합도 (Coupling)]], [[계층화 아키텍처 (Layered Architecture)|계층화 아키텍처 (Layered Architecture)]], [[마이크로서비스 아키텍처 (Microservices Architecture)|마이크로서비스 아키텍처 (Microservices Architecture)]] +- **Projects/Contexts:** [[넷플릭스 코스모스 플랫폼 (Netflix Cosmos Platform)|넷플릭스 코스모스 플랫폼 (Netflix Cosmos Platform)]] (마이크로서비스, 워크플로우, 서버리스 함수로 논리적 계층을 엄격히 분리하여 병목 현상을 해결한 사례 [34-36]), 스포티파이 마이크로 프론트엔드 (Spotify Micro Frontends) (스쿼드 조직 모델과 프론트엔드의 관심사를 분리하여 독립적 개발과 배포를 가능하게 한 사례 [22]). - **Contradictions/Notes:** 관심사의 분리는 훌륭한 설계 지침이지만, 개발 초기 단계부터 모든 것을 선제적으로 추측하여 분리하려 하면 '오버엔지니어링'이나 '성급한 추상화(Premature Abstraction)'가 발생할 수 있다. 이는 인지적 부하를 줄이려는 SoC의 본래 목적과 정반대의 결과를 낳을 수 있으므로, 실제 중복과 복잡성이 확인되는 임계점에서 점진적으로 분리를 수행해야 한다는 실무자들의 지적이 있다 [29, 30, 33, 37]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/관심사의 분리 (Separation of Concerns, SoC).md]] +- Raw Source: 00_Raw/2026-04-20/관심사의 분리 (Separation of Concerns, SoC).md --- diff --git a/01_Archive/2026-04-20/관심사의 분리 (Separation of Concerns).md b/01_Archive/2026-04-20/관심사의 분리 (Separation of Concerns).md index 7c10d4b0..5ecb9771 100644 --- a/01_Archive/2026-04-20/관심사의 분리 (Separation of Concerns).md +++ b/01_Archive/2026-04-20/관심사의 분리 (Separation of Concerns).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-FE2B8D -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 관심사의 분리 (Separation of Concerns)" --- -# [[관심사의 분리 (Separation of Concerns)]] +# [[관심사의 분리 (Separation of Concerns)|관심사의 분리 (Separation of Concerns)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 관심사의 분리(SoC)는 소프트웨어 설계에서 프로그램의 각 부분이 서로 다른 고유한 기능이나 특정 관심사에만 집중하도록 시스템을 논리적 단위로 나누는 근본적인 원칙입니다 [1-3]. 1974년 에츠허르 데이크스트라(Edsger W. Dijkstra)가 인간의 지적 한계로 인한 복잡성을 통제하기 위해 제안한 개념으로, 시스템을 관리하기 쉬운 조각으로 분해하여 모듈성, 유지보수성, 재사용성 및 확장성을 극대화하는 것을 목표로 합니다 [1, 3-6]. 시스템의 핵심 비즈니스 로직과 기술적 세부 사항을 명확히 격리함으로써, 변화에 유연하게 대응하고 진화할 수 있는 견고한 아키텍처를 구축하는 데 필수적인 철학입니다 [7-9]. @@ -35,11 +35,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 관심사의 분리 (Separatio - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[응집도와 결합도 (Cohesion and Coupling)]], [[클린 아키텍처 (Clean Architecture)]], [[단일 책임 원칙 (Single Responsibility Principle)]], [[의존성 규칙 (Dependency Rule)]] -- **Projects/Contexts:** [[넷플릭스 코스모스 플랫폼 (Netflix Cosmos Platform)]], [[스포티파이 자율적 분대 모델 및 마이크로 프론트엔드 (Spotify Squads and Micro Frontends)]], [[화신산 병원 모듈러 통합 건설 (Huoshenshan Hospital Modular Construction)]] +- **Related Topics:** [[응집도와 결합도 (Cohesion and Coupling)|응집도와 결합도 (Cohesion and Coupling)]], [[클린 아키텍처 (Clean Architecture)|클린 아키텍처 (Clean Architecture)]], [[단일 책임 원칙 (Single Responsibility Principle)|단일 책임 원칙 (Single Responsibility Principle)]], [[의존성 규칙 (Dependency Rule)|의존성 규칙 (Dependency Rule)]] +- **Projects/Contexts:** [[넷플릭스 코스모스 플랫폼 (Netflix Cosmos Platform)|넷플릭스 코스모스 플랫폼 (Netflix Cosmos Platform)]], [[스포티파이 자율적 분대 모델 및 마이크로 프론트엔드 (Spotify Squads and Micro Frontends)|스포티파이 자율적 분대 모델 및 마이크로 프론트엔드 (Spotify Squads and Micro Frontends)]], 화신산 병원 모듈러 통합 건설 (Huoshenshan Hospital Modular Construction) - **Contradictions/Notes:** 관심사의 분리는 시스템의 복잡성을 낮추지만, 맹목적으로 추구하여 과도하게 분리할 경우 함수 호출의 깊이 증가, 네트워크 지연, 데이터 변환 오버헤드 등 성능 저하를 초래할 수 있습니다 [30]. 또한 지나친 추상화는 개발자를 미궁에 빠뜨려 가독성을 저하시키는 '오버엔지니어링'의 부작용을 낳을 수 있으므로, 유사 코드가 최소 3번 이상 중복될 때 추상화를 고려하는 "Rule of Three"를 참고하여 실무적인 분리의 임계점을 찾아야 합니다 [31, 32]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/관심사의 분리 (Separation of Concerns).md]] +- Raw Source: 00_Raw/2026-04-20/관심사의 분리 (Separation of Concerns).md --- diff --git a/01_Archive/2026-04-20/관심사의 분리 (Separation of Concerns, SoC).md b/01_Archive/2026-04-20/관심사의 분리 (Separation of Concerns, SoC).md index 06908ab5..bb7d34c7 100644 --- a/01_Archive/2026-04-20/관심사의 분리 (Separation of Concerns, SoC).md +++ b/01_Archive/2026-04-20/관심사의 분리 (Separation of Concerns, SoC).md @@ -1,4 +1,4 @@ -# [[관심사의 분리 (Separation of Concerns, SoC)]] +# [[관심사의 분리 (Separation of Concerns, SoC)|관심사의 분리 (Separation of Concerns, SoC)]] ## 📌 Brief Summary 관심사의 분리(SoC)는 복잡한 소프트웨어 시스템을 더 작고 관리하기 쉬운 부분으로 나누어, 각 모듈이 단일한 관심사(기능이나 책임)만을 다루도록 설계하는 소프트웨어 공학의 근본적인 원칙이다 [1-3]. 1974년 에츠허르 데이크스트라(Edsger W. Dijkstra)가 처음 제안한 이 개념은 한 번에 모든 측면을 다루는 대신 특정 측면에 집중하여 복잡성을 통제하는 것을 목표로 한다 [4-6]. 이 원칙을 통해 시스템의 모듈성, 유지보수성, 재사용성 및 테스트 가능성을 획기적으로 향상시킬 수 있다 [1, 7, 8]. @@ -20,8 +20,8 @@ * **한계(오버헤드):** 완벽한 분리를 맹목적으로 추구하면 불필요한 레이어와 인디렉션(Indirection)이 추가되어 오히려 코드 추적과 디버깅을 어렵게 만들 수 있다 [29, 30]. 또한 분산 환경에서는 계층 간 데이터 변환 및 통신 오버헤드에 따른 성능 저하가 발생할 수 있다 [31]. 이를 방지하기 위해 코드 중복이 세 번 이상 발견될 때 비로소 추상화와 분리를 고려하는 "Rule of Three"와 같은 실무적 지침이 권장된다 [30, 32, 33]. ## 🔗 Knowledge Connections -- **Related Topics:** [[단일 책임 원칙 (Single Responsibility Principle, SRP)]], [[응집도 (Cohesion)]], [[결합도 (Coupling)]], [[계층화 아키텍처 (Layered Architecture)]], [[마이크로서비스 아키텍처 (Microservices Architecture)]] -- **Projects/Contexts:** [[넷플릭스 코스모스 플랫폼 (Netflix Cosmos Platform)]] (마이크로서비스, 워크플로우, 서버리스 함수로 논리적 계층을 엄격히 분리하여 병목 현상을 해결한 사례 [34-36]), [[스포티파이 마이크로 프론트엔드 (Spotify Micro Frontends)]] (스쿼드 조직 모델과 프론트엔드의 관심사를 분리하여 독립적 개발과 배포를 가능하게 한 사례 [22]). +- **Related Topics:** 단일 책임 원칙 (Single Responsibility Principle, SRP), [[응집도 (Cohesion)|응집도 (Cohesion)]], [[결합도 (Coupling)|결합도 (Coupling)]], [[계층화 아키텍처 (Layered Architecture)|계층화 아키텍처 (Layered Architecture)]], [[마이크로서비스 아키텍처 (Microservices Architecture)|마이크로서비스 아키텍처 (Microservices Architecture)]] +- **Projects/Contexts:** [[넷플릭스 코스모스 플랫폼 (Netflix Cosmos Platform)|넷플릭스 코스모스 플랫폼 (Netflix Cosmos Platform)]] (마이크로서비스, 워크플로우, 서버리스 함수로 논리적 계층을 엄격히 분리하여 병목 현상을 해결한 사례 [34-36]), 스포티파이 마이크로 프론트엔드 (Spotify Micro Frontends) (스쿼드 조직 모델과 프론트엔드의 관심사를 분리하여 독립적 개발과 배포를 가능하게 한 사례 [22]). - **Contradictions/Notes:** 관심사의 분리는 훌륭한 설계 지침이지만, 개발 초기 단계부터 모든 것을 선제적으로 추측하여 분리하려 하면 '오버엔지니어링'이나 '성급한 추상화(Premature Abstraction)'가 발생할 수 있다. 이는 인지적 부하를 줄이려는 SoC의 본래 목적과 정반대의 결과를 낳을 수 있으므로, 실제 중복과 복잡성이 확인되는 임계점에서 점진적으로 분리를 수행해야 한다는 실무자들의 지적이 있다 [29, 30, 33, 37]. --- diff --git a/01_Archive/2026-04-20/관심사의 분리 (SoC).md b/01_Archive/2026-04-20/관심사의 분리 (SoC).md index d4f4a6fd..984a37d0 100644 --- a/01_Archive/2026-04-20/관심사의 분리 (SoC).md +++ b/01_Archive/2026-04-20/관심사의 분리 (SoC).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-441E04 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 관심사의 분리 (SoC)" --- -# [[관심사의 분리 (SoC)]] +# [[관심사의 분리 (SoC)|관심사의 분리 (SoC)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 관심사의 분리(SoC)는 시스템을 구성하는 요소를 서로 겹치지 않는 독립적인 모듈로 나누어, 각 부분이 특정 기능이나 목적(관심사)에만 집중하도록 설계하는 소프트웨어 공학의 핵심 원칙이다 [1, 2]. 1974년 에츠허르 데이크스트라가 제안한 이 개념은 복잡한 문제를 해결할 때 인간의 인지적 한계를 고려해 한 번에 하나의 측면에만 집중할 것을 강조한다 [3, 4]. 특히 아키텍처 관점에서 "뇌와 팔다리의 분리"라는 비유로 설명되며, 시스템의 본질인 핵심 비즈니스 로직(뇌)과 이를 외부에 연결하는 기술적 인프라(팔다리)를 격리하여 유지보수성과 재사용성을 극대화하는 것을 목표로 한다 [5, 6]. @@ -35,11 +35,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 관심사의 분리 (SoC)" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[단일 책임 원칙 (SRP)]], [[응집도와 결합도]], [[클린 아키텍처 (Clean Architecture)]] -- **Projects/Contexts:** [[넷플릭스 코스모스 플랫폼 (Netflix Cosmos)]], [[스포티파이 자율적 분대 모델 (Spotify Squad)]], [[모듈러 통합 건설 (MiC)]] +- **Related Topics:** [[단일 책임 원칙 (SRP)|단일 책임 원칙 (SRP)]], [[응집도와 결합도|응집도와 결합도]], [[클린 아키텍처 (Clean Architecture)|클린 아키텍처 (Clean Architecture)]] +- **Projects/Contexts:** [[넷플릭스 코스모스 플랫폼 (Netflix Cosmos)|넷플릭스 코스모스 플랫폼 (Netflix Cosmos)]], [[스포티파이 자율적 분대 모델 (Spotify Squad)|스포티파이 자율적 분대 모델 (Spotify Squad)]], [[모듈러 통합 건설 (MiC)|모듈러 통합 건설 (MiC)]] - **Contradictions/Notes:** 관심사의 분리는 시스템의 가독성, 테스트 가능성, 재사용성을 비약적으로 향상시키지만 [25-27], 이를 맹목적으로 추구하여 과도하게 분리할 경우 함수 호출의 뎁스를 깊게 만들거나 간접 참조가 늘어나 오히려 인지적 부하와 성능 오버헤드(Overengineering)를 유발할 수 있다 [28-30]. 따라서 실무에서는 성급한 추상화를 피하고, 동일한 패턴이 세 번 반복될 때 비로소 분리를 고려하는 "Rule of Three"와 같이 실용적인 임계점을 찾아 균형을 맞추어야 한다 [30]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/관심사의 분리 (SoC).md]] +- Raw Source: 00_Raw/2026-04-20/관심사의 분리 (SoC).md --- diff --git a/01_Archive/2026-04-20/관심사의 분리(Separation of Concerns).md b/01_Archive/2026-04-20/관심사의 분리(Separation of Concerns).md index 520cd923..215b415d 100644 --- a/01_Archive/2026-04-20/관심사의 분리(Separation of Concerns).md +++ b/01_Archive/2026-04-20/관심사의 분리(Separation of Concerns).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-55088F -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 관심사의 분리(Separation of Concerns)" --- -# [[관심사의 분리(Separation of Concerns)]] +# [[관심사의 분리(Separation of Concerns)|관심사의 분리(Separation of Concerns)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 관심사의 분리(Separation of Concerns, SoC)는 복잡한 소프트웨어 시스템을 작고 관리하기 쉬운 개별 부분으로 나누어, 각 부분이 단일한 기능적 측면이나 '관심사'만을 처리하도록 설계하는 핵심 소프트웨어 공학 원칙입니다 [1-3]. 1974년 에츠허르 데이크스트라(Edsger W. Dijkstra)가 인간의 인지적 한계를 극복하고 복잡성을 제어하기 위해 처음 제안한 철학에 기원을 두고 있습니다 [4-6]. 이 원칙은 모듈 내의 응집도(Cohesion)를 높이고 모듈 간의 결합도(Coupling)를 낮추어 시스템의 유지보수성, 재사용성, 테스트 가능성 및 확장성을 극대화하는 것을 목표로 합니다 [7-10]. @@ -33,11 +33,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 관심사의 분리(Separation - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[단일 책임 원칙(SRP)]], [[응집도(Cohesion)와 결합도(Coupling)]], [[계층화 아키텍처(Layered Architecture)]] -- **Projects/Contexts:** [[넷플릭스(Netflix)의 코스모스(Cosmos) 플랫폼과 마이크로서비스 전환]], [[스포티파이(Spotify)의 마이크로 프론트엔드 및 스쿼드 모델]], [[HTML, CSS, JavaScript의 웹 표준 3요소 분리]] +- **Related Topics:** [[단일 책임 원칙(SRP)|단일 책임 원칙(SRP)]], 응집도(Cohesion)와 결합도(Coupling), [[계층화 아키텍처 (Layered Architecture)|계층화 아키텍처(Layered Architecture)]] +- **Projects/Contexts:** 넷플릭스(Netflix)의 코스모스(Cosmos) 플랫폼과 마이크로서비스 전환, 스포티파이(Spotify)의 마이크로 프론트엔드 및 스쿼드 모델, HTML, CSS, JavaScript의 웹 표준 3요소 분리 - **Contradictions/Notes:** 많은 개발 가이드라인은 관심사의 분리를 선제적으로 엄격히 설계할 것을 권장하지만, 일부 전문가들은 코드 작성 초기부터 완벽하게 관심사를 예측하여 분리하는 것은 불가능하다고 주장합니다 [34, 35]. 대신, 유사한 코드가 3번 이상 반복될 때 추출하는 'Rule of Three'처럼, 반복되는 패턴을 확인한 뒤에 경험적으로 사후에 분리하는 실용적이고 점진적인 접근(DRY 원칙과 병행)을 강조합니다 [31, 35, 36]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/관심사의 분리(Separation of Concerns).md]] +- Raw Source: 00_Raw/2026-04-20/관심사의 분리(Separation of Concerns).md --- diff --git a/01_Archive/2026-04-20/관심사의 분리(SoC).md b/01_Archive/2026-04-20/관심사의 분리(SoC).md index c3a1a288..f2796752 100644 --- a/01_Archive/2026-04-20/관심사의 분리(SoC).md +++ b/01_Archive/2026-04-20/관심사의 분리(SoC).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-1BA61A -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 관심사의 분리(SoC)" --- -# [[관심사의 분리(SoC)]] +# [[관심사의 분리(SoC)|관심사의 분리(SoC)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 관심사의 분리(SoC, Separation of Concerns)는 소프트웨어 시스템을 각기 다른 기능이나 책임(관심사)에만 집중하는 작고 관리하기 쉬운 독립적인 모듈로 나누는 소프트웨어 엔지니어링의 핵심 설계 원칙이다 [1-5]. 1974년 에츠허르 데이크스트라(Edsger W. Dijkstra)가 처음 제안한 개념으로, 복잡성을 통제하고 코드의 모듈성, 가독성, 유지보수성, 확장성 및 재사용성을 크게 향상시키는 것을 목표로 한다 [3, 4, 6, 7]. 이 철학은 객체 지향 설계의 단일 책임 원칙(SRP)과 인터페이스 분리 원칙(ISP) 등 현대 아키텍처 패턴이 탄생하는 직접적인 근간이 되었다 [5, 8-10]. @@ -32,13 +32,13 @@ github_commit: "[P-Reinforce] Continuous Worker - 관심사의 분리(SoC)" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[단일 책임 원칙(SRP)]], [[응집도(Cohesion)와 결합도(Coupling)]], [[계층화 아키텍처(Layered Architecture)]], [[모델-뷰-컨트롤러(MVC)]], [[관점 지향 프로그래밍(AOP)]] -- **Projects/Contexts:** [[넷플릭스 코스모스(Cosmos) 플랫폼]], [[스포티파이 스쿼드(Squad) 및 마이크로 프론트엔드]], [[화신산(Huoshen Mountain) 병원 모듈러 통합 건설(MiC)]] +- **Related Topics:** [[단일 책임 원칙(SRP)|단일 책임 원칙(SRP)]], 응집도(Cohesion)와 결합도(Coupling), [[계층화 아키텍처 (Layered Architecture)|계층화 아키텍처(Layered Architecture)]], 모델-뷰-컨트롤러(MVC), [[관점 지향 프로그래밍(AOP)|관점 지향 프로그래밍(AOP)]] +- **Projects/Contexts:** 넷플릭스 코스모스(Cosmos) 플랫폼, 스포티파이 스쿼드(Squad) 및 마이크로 프론트엔드, 화신산(Huoshen Mountain) 병원 모듈러 통합 건설(MiC) - **Contradictions/Notes:** * "SoC를 도입하면 유지보수와 모듈성이 향상된다"는 원칙이 일반적이나, "지나친 관심사 분리와 추상화는 간접 참조를 늘리고 런타임 성능 저하 및 코드 추적의 어려움을 유발하여 실무적 복잡성을 오히려 가중시킨다"는 경고와 상충하는 지점이 있다 [42-45]. * 관심사의 선제적인 도출이 필수적이라는 견해가 있는 반면, 다른 실무자들은 초기에 관심사를 미리 예측해 분리하는 것은 불가능에 가까우며, 코드가 중복되어 나타날 때(Rule of Three) 사후적으로 리팩토링을 통해 분리하는 것(DRY 관점)이 현실적이라는 상반된 주장을 한다 [45, 46]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/관심사의 분리(SoC).md]] +- Raw Source: 00_Raw/2026-04-20/관심사의 분리(SoC).md --- diff --git a/01_Archive/2026-04-20/관점 지향 프로그래밍 (AOP).md b/01_Archive/2026-04-20/관점 지향 프로그래밍 (AOP).md index b2310600..82635121 100644 --- a/01_Archive/2026-04-20/관점 지향 프로그래밍 (AOP).md +++ b/01_Archive/2026-04-20/관점 지향 프로그래밍 (AOP).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-A9FD39 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 관점 지향 프로그래밍 (AOP)" --- -# [[관점 지향 프로그래밍 (AOP)]] +# [[관점 지향 프로그래밍 (AOP)|관점 지향 프로그래밍 (AOP)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 관점 지향 프로그래밍(Aspect-Oriented Programming, AOP)은 소프트웨어 개발에서 시스템 전체에 흩어져 있는 횡단 관심사(Cross-Cutting Concerns)를 주요 비즈니스 로직과 분리하여 모듈화하는 프로그래밍 기법입니다 [1]. 이는 객체 지향 프로그래밍(OOP)의 단점을 보완하여 코드 중복을 최소화하고 가독성 및 유지보수성을 향상시키는 역할을 합니다 [1, 2]. 로깅, 보안, 트랜잭션 관리 등 여러 모듈에 공통으로 쓰이는 기능들을 중앙에서 효과적으로 관리할 때 주로 도입됩니다 [3, 4]. @@ -35,5 +35,5 @@ github_commit: "[P-Reinforce] Continuous Worker - 관점 지향 프로그래밍 ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/관점 지향 프로그래밍 (AOP).md]] +- Raw Source: 00_Raw/2026-04-20/관점 지향 프로그래밍 (AOP).md --- diff --git a/01_Archive/2026-04-20/관점 지향 프로그래밍(AOP).md b/01_Archive/2026-04-20/관점 지향 프로그래밍(AOP).md index f6c1853d..d1155a25 100644 --- a/01_Archive/2026-04-20/관점 지향 프로그래밍(AOP).md +++ b/01_Archive/2026-04-20/관점 지향 프로그래밍(AOP).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-B943FA -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 관점 지향 프로그래밍(AOP)" --- -# [[관점 지향 프로그래밍(AOP)]] +# [[관점 지향 프로그래밍(AOP)|관점 지향 프로그래밍(AOP)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 관점 지향 프로그래밍(AOP, Aspect-Oriented Programming)은 소프트웨어 개발 시 로깅, 보안 등 시스템 전체에 공통으로 사용되는 횡단 관심사(Cross-Cutting Concerns)를 주요 비즈니스 로직으로부터 분리하여 모듈화하는 프로그래밍 기법이다 [1-3]. 이는 객체 지향 프로그래밍(OOP)의 단점을 보완하며, 공통된 기능을 수평적으로 분리해 코드의 단순화와 명확한 역할 분리를 돕는다 [1, 2]. 결과적으로 AOP를 도입하면 코드의 중복을 제거할 수 있고, 가독성과 유지보수성이 크게 향상되는 이점을 얻을 수 있다 [2]. @@ -35,11 +35,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 관점 지향 프로그래밍( - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[객체 지향 프로그래밍(OOP)]], [[횡단 관심사(Cross-Cutting Concerns)]], [[관심사의 분리(SoC)]] -- **Projects/Contexts:** [[Spring AOP]], [[AspectJ]] +- **Related Topics:** [[객체 지향 프로그래밍(OOP)|객체 지향 프로그래밍(OOP)]], 횡단 관심사(Cross-Cutting Concerns), [[관심사의 분리(SoC)|관심사의 분리(SoC)]] +- **Projects/Contexts:** Spring AOP, AspectJ - **Contradictions/Notes:** 소스들 간에 직접적인 모순은 없으나, AOP 도입에 대한 명확한 트레이드오프(Trade-off)가 강조된다. AOP는 횡단 관심사를 분리하여 코드 품질과 유지보수성을 높이는 훌륭한 해결책이지만, 과도하게 사용할 경우 런타임 코드 추적을 어렵게 만들고 오히려 복잡도를 증가시킬 수 있다는 점을 주의해야 한다 [6]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/관점 지향 프로그래밍(AOP).md]] +- Raw Source: 00_Raw/2026-04-20/관점 지향 프로그래밍(AOP).md --- diff --git a/01_Archive/2026-04-20/광범위한 신경과학적 연합 기제.md b/01_Archive/2026-04-20/광범위한 신경과학적 연합 기제.md index 981b894e..46e06dd1 100644 --- a/01_Archive/2026-04-20/광범위한 신경과학적 연합 기제.md +++ b/01_Archive/2026-04-20/광범위한 신경과학적 연합 기제.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-2AE4FF -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 광범위한 신경과학적 연합 기제" --- -# [[광범위한 신경과학적 연합 기제]] +# [[광범위한 신경과학적 연합 기제|광범위한 신경과학적 연합 기제]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - 광범위한 신경과학적 ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/광범위한 신경과학적 연합 기제.md]] +- Raw Source: 00_Raw/2026-04-20/광범위한 신경과학적 연합 기제.md --- diff --git a/01_Archive/2026-04-20/교육 심리학 및 교수법 설계.md b/01_Archive/2026-04-20/교육 심리학 및 교수법 설계.md index 724f12b2..6196dc85 100644 --- a/01_Archive/2026-04-20/교육 심리학 및 교수법 설계.md +++ b/01_Archive/2026-04-20/교육 심리학 및 교수법 설계.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-5D01FE -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 교육 심리학 및 교수법 설계" --- -# [[교육 심리학 및 교수법 설계]] +# [[교육 심리학 및 교수법 설계|교육 심리학 및 교수법 설계]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - 교육 심리학 및 교수법 ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/교육 심리학 및 교수법 설계.md]] +- Raw Source: 00_Raw/2026-04-20/교육 심리학 및 교수법 설계.md --- diff --git a/01_Archive/2026-04-20/교육 심리학에서의 보상 설계.md b/01_Archive/2026-04-20/교육 심리학에서의 보상 설계.md index a2234e31..f886247c 100644 --- a/01_Archive/2026-04-20/교육 심리학에서의 보상 설계.md +++ b/01_Archive/2026-04-20/교육 심리학에서의 보상 설계.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-DD5110 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 교육 심리학에서의 보상 설계" --- -# [[교육 심리학에서의 보상 설계]] +# [[교육 심리학에서의 보상 설계|교육 심리학에서의 보상 설계]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - 교육 심리학에서의 보 ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/교육 심리학에서의 보상 설계.md]] +- Raw Source: 00_Raw/2026-04-20/교육 심리학에서의 보상 설계.md --- diff --git a/01_Archive/2026-04-20/교육 심리학에서의 학습 동기 유도.md b/01_Archive/2026-04-20/교육 심리학에서의 학습 동기 유도.md index 1baebe32..070c8dca 100644 --- a/01_Archive/2026-04-20/교육 심리학에서의 학습 동기 유도.md +++ b/01_Archive/2026-04-20/교육 심리학에서의 학습 동기 유도.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-C63490 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 교육 심리학에서의 학습 동기 유도" --- -# [[교육 심리학에서의 학습 동기 유도]] +# [[교육 심리학에서의 학습 동기 유도|교육 심리학에서의 학습 동기 유도]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - 교육 심리학에서의 학 ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/교육 심리학에서의 학습 동기 유도.md]] +- Raw Source: 00_Raw/2026-04-20/교육 심리학에서의 학습 동기 유도.md --- diff --git a/01_Archive/2026-04-20/교육 심리학에서의 학습 동기 유발.md b/01_Archive/2026-04-20/교육 심리학에서의 학습 동기 유발.md index 1475fcdb..dd5e614b 100644 --- a/01_Archive/2026-04-20/교육 심리학에서의 학습 동기 유발.md +++ b/01_Archive/2026-04-20/교육 심리학에서의 학습 동기 유발.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-A6A206 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 교육 심리학에서의 학습 동기 유발" --- -# [[교육 심리학에서의 학습 동기 유발]] +# [[교육 심리학에서의 학습 동기 유발|교육 심리학에서의 학습 동기 유발]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - 교육 심리학에서의 학 ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/교육 심리학에서의 학습 동기 유발.md]] +- Raw Source: 00_Raw/2026-04-20/교육 심리학에서의 학습 동기 유발.md --- diff --git a/01_Archive/2026-04-20/교육학의 모델링 전략.md b/01_Archive/2026-04-20/교육학의 모델링 전략.md index 24593bf4..39e72bdd 100644 --- a/01_Archive/2026-04-20/교육학의 모델링 전략.md +++ b/01_Archive/2026-04-20/교육학의 모델링 전략.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-8413FB -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 교육학의 모델링 전략" --- -# [[교육학의 모델링 전략]] +# [[교육학의 모델링 전략|교육학의 모델링 전략]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - 교육학의 모델링 전략" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/교육학의 모델링 전략.md]] +- Raw Source: 00_Raw/2026-04-20/교육학의 모델링 전략.md --- diff --git a/01_Archive/2026-04-20/교집합 타입 (Intersection Types).md b/01_Archive/2026-04-20/교집합 타입 (Intersection Types).md index 76041f1e..5393f83d 100644 --- a/01_Archive/2026-04-20/교집합 타입 (Intersection Types).md +++ b/01_Archive/2026-04-20/교집합 타입 (Intersection Types).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-795BA0 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 교집합 타입 (Intersection Types)" --- -# [[교집합 타입 (Intersection Types)]] +# [[교집합 타입 (Intersection Types)|교집합 타입 (Intersection Types)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -23,11 +23,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 교집합 타입 (Intersection - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[유니언 타입 (Union Types)]], [[인터페이스 (Interfaces)]], [[구조적 타이핑 (Structural Typing)]] -- **Projects/Contexts:** [[TypeScript 컴파일러 성능 최적화]], [[객체 타입 조합 및 확장]] +- **Related Topics:** 유니언 타입 (Union Types), 인터페이스 (Interfaces), [[구조적 타이핑 (Structural Typing)|구조적 타이핑 (Structural Typing)]] +- **Projects/Contexts:** TypeScript 컴파일러 성능 최적화, 객체 타입 조합 및 확장 - **Contradictions/Notes:** 교집합 타입(`&`)은 유연하게 여러 객체를 결합할 수 있는 수단이지만, 성능 최적화와 명시적 충돌 에러 감지의 이점 때문에 TypeScript 공식 가이드나 성능 가이드라인에서는 가능한 경우 인터페이스 확장(`extends`)을 더 우선적으로 사용할 것을 권장합니다 [6, 7, 9]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/교집합 타입 (Intersection Types).md]] +- Raw Source: 00_Raw/2026-04-20/교집합 타입 (Intersection Types).md --- diff --git a/01_Archive/2026-04-20/교집합 타입(Intersection Type).md b/01_Archive/2026-04-20/교집합 타입(Intersection Type).md index 1efecc69..6a50be11 100644 --- a/01_Archive/2026-04-20/교집합 타입(Intersection Type).md +++ b/01_Archive/2026-04-20/교집합 타입(Intersection Type).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-4ECB5E -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 교집합 타입(Intersection Type)" --- -# [[교집합 타입(Intersection Type)]] +# [[교집합 타입(Intersection Type)|교집합 타입(Intersection Type)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 교집합 타입(Intersection Type)은 여러 개의 타입을 결합하여 필요한 모든 기능을 갖춘 단일 타입을 생성하는 TypeScript의 타입 구성 문법입니다 [1]. `&` 연산자를 사용하여 정의하며, 결합된 모든 구성 타입의 제약 조건과 속성을 동시에 만족(A AND B)해야 합니다 [2, 3]. 이를 통해 기존에 정의된 여러 객체의 구조나 기능을 재사용하여 복잡하고 확장된 타입을 유연하게 만들 수 있습니다 [1, 4]. @@ -34,11 +34,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 교집합 타입(Intersection - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[유니언 타입(Union Type)]], [[인터페이스(Interface)]], [[집합론(Set Theory)]] -- **Projects/Contexts:** [[API 도메인 모델 구조화 및 설정 객체(Configuration Objects) 관리]], [[TypeScript 컴파일 성능 최적화]] +- **Related Topics:** 유니언 타입(Union Type), [[인터페이스 (Interface)|인터페이스(Interface)]], [[집합론(Set Theory)|집합론(Set Theory)]] +- **Projects/Contexts:** API 도메인 모델 구조화 및 설정 객체(Configuration Objects) 관리, TypeScript 컴파일 성능 최적화 - **Contradictions/Notes:** 여러 타입을 합칠 때 교집합 타입(`&`)이 흔히 사용되지만, TypeScript 공식 성능 가이드와 개발 커뮤니티에서는 객체를 확장할 경우 컴파일 캐싱 및 성능 이점, 에러 방지를 위해 교집합 타입보다 `interface extends`의 사용을 적극적으로 권장합니다 [12, 13, 17]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/교집합 타입(Intersection Type).md]] +- Raw Source: 00_Raw/2026-04-20/교집합 타입(Intersection Type).md --- diff --git a/01_Archive/2026-04-20/구조적 타이핑 (Structural Typing).md b/01_Archive/2026-04-20/구조적 타이핑 (Structural Typing).md index 73673ee0..a0c8f33b 100644 --- a/01_Archive/2026-04-20/구조적 타이핑 (Structural Typing).md +++ b/01_Archive/2026-04-20/구조적 타이핑 (Structural Typing).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-66BE32 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 구조적 타이핑 (Structural Typing)" --- -# [[구조적 타이핑 (Structural Typing)]] +# [[구조적 타이핑 (Structural Typing)|구조적 타이핑 (Structural Typing)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -31,11 +31,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 구조적 타이핑 (Structura - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[명목적 타이핑 (Nominal Typing)]], [[덕 타이핑 (Duck Typing)]], [[과잉 속성 체크 (Excess Property Checking)]], [[브랜디드 타입 (Branded Types)]] -- **Projects/Contexts:** [[TypeScript 인터페이스 및 시스템 보호 아키텍처 설계]] +- **Related Topics:** [[명목적 타이핑 (Nominal Typing)|명목적 타이핑 (Nominal Typing)]], [[덕 타이핑 (Duck Typing)|덕 타이핑 (Duck Typing)]], [[과잉 속성 체크 (Excess Property Checking)|과잉 속성 체크 (Excess Property Checking)]], [[브랜디드 타입 (Branded Types)|브랜디드 타입 (Branded Types)]] +- **Projects/Contexts:** [[TypeScript 인터페이스 및 시스템 보호 아키텍처 설계|TypeScript 인터페이스 및 시스템 보호 아키텍처 설계]] - **Contradictions/Notes:** TypeScript는 기본적으로 구조적 타이핑을 따르지만, 객체 리터럴을 직접 할당할 때에 한해서는 잉여 속성을 허용하지 않는 엄격한 "과잉 속성 체크(Excess Property Checking)"를 수행하여 유연성과 안전성의 균형을 맞춘다 [1, 5, 10]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/구조적 타이핑 (Structural Typing).md]] +- Raw Source: 00_Raw/2026-04-20/구조적 타이핑 (Structural Typing).md --- diff --git a/01_Archive/2026-04-20/구조적 타이핑(Structural Typing).md b/01_Archive/2026-04-20/구조적 타이핑(Structural Typing).md index 5a7900ad..37b3d1ad 100644 --- a/01_Archive/2026-04-20/구조적 타이핑(Structural Typing).md +++ b/01_Archive/2026-04-20/구조적 타이핑(Structural Typing).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-25EFF5 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 구조적 타이핑(Structural Typing)" --- -# [[구조적 타이핑(Structural Typing)]] +# [[구조적 타이핑(Structural Typing)|구조적 타이핑(Structural Typing)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 구조적 타이핑은 TypeScript 타입 시스템의 근본적인 원칙으로, 타입의 이름이나 명시적 선언이 아닌 객체의 실제 형태(구조)에 기반하여 타입 호환성을 결정하는 방식입니다 [1, 2]. 이는 "만약 어떤 것이 오리처럼 걷고 갉갉거리면 그것은 오리다"라는 '덕 타이핑(Duck Typing)' 개념으로도 불리며, 대상 타입이 요구하는 최소한의 속성과 메서드를 갖추고 있다면 잉여 속성이 있더라도 호환되는 것으로 간주합니다 [1-3]. 이 시스템은 유연성을 제공하지만, 의미론적 구분이 필요한 상황에서는 한계를 보일 수 있어 이를 보완하는 다양한 기법들이 함께 사용됩니다 [4-6]. @@ -33,11 +33,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 구조적 타이핑(Structural - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[덕 타이핑(Duck Typing)]], [[명목적 타이핑(Nominal Typing)]], [[과잉 속성 체크(Excess Property Checking)]], [[브랜디드 타입(Branded Types)]], [[satisfies 연산자]] -- **Projects/Contexts:** [[TypeScript 타입 시스템 아키텍처 및 도메인 기반 설계(DDD)]] +- **Related Topics:** [[덕 타이핑(Duck Typing)|덕 타이핑(Duck Typing)]], [[명목적 타이핑(Nominal Typing)|명목적 타이핑(Nominal Typing)]], [[과잉 속성 체크(Excess Property Checking)|과잉 속성 체크(Excess Property Checking)]], [[브랜디드 타입(Branded Types)|브랜디드 타입(Branded Types)]], [[satisfies 연산자|satisfies 연산자]] +- **Projects/Contexts:** [[TypeScript 타입 시스템 아키텍처 및 도메인 기반 설계(DDD)|TypeScript 타입 시스템 아키텍처 및 도메인 기반 설계(DDD)]] - **Contradictions/Notes:** 객체 리터럴을 직접 할당하거나 인자로 넘길 때는 예기치 않은 잉여 속성에 대해 엄격한 에러를 발생시키는 반면, 값을 미리 변수에 선언한 뒤 간접적으로 할당할 때는 최소 요건만 충족하면 잉여 속성을 무시하고 할당을 허용하는 동작 방식의 차이가 존재합니다 [8, 10, 17, 18]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/구조적 타이핑(Structural Typing).md]] +- Raw Source: 00_Raw/2026-04-20/구조적 타이핑(Structural Typing).md --- diff --git a/01_Archive/2026-04-20/구조적 타이핑.md b/01_Archive/2026-04-20/구조적 타이핑.md index f7d87c16..de77cb97 100644 --- a/01_Archive/2026-04-20/구조적 타이핑.md +++ b/01_Archive/2026-04-20/구조적 타이핑.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-E8243F -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 구조적 타이핑" --- -# [[구조적 타이핑]] +# [[구조적 타이핑|구조적 타이핑]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 구조적 타이핑(Structural Typing)은 객체의 명시적인 이름이나 선언 대신, 객체가 가진 실제 형태와 구조(속성과 메서드)가 일치하면 타입 간의 호환성을 인정하는 타입 시스템입니다[1-3]. 이는 "어떤 것이 오리처럼 걷고 소리를 낸다면 오리다"라는 이른바 '덕 타이핑(Duck typing)' 원칙에 기반하며 TypeScript 타입 검사의 핵심 철학입니다[2, 4, 5]. 타입의 이름이 일치해야만 호환되는 Java나 C#의 명목적 타이핑(Nominal Typing)과는 대비되는 유연한 접근 방식입니다[2]. @@ -22,11 +22,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 구조적 타이핑" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[명목적 타이핑]], [[덕 타이핑]], [[과잉 속성 체크]], [[브랜디드 타입]] -- **Projects/Contexts:** [[TypeScript 타입 시스템 설계]], [[도메인 기반 설계(DDD)]] +- **Related Topics:** 명목적 타이핑, 덕 타이핑, 과잉 속성 체크, [[브랜디드 타입|브랜디드 타입]] +- **Projects/Contexts:** TypeScript 타입 시스템 설계, [[도메인 기반 설계(DDD)|도메인 기반 설계(DDD)]] - **Contradictions/Notes:** 소스에 따르면 구조적 타이핑은 TypeScript에 강력한 유연성을 부여하는 근간이지만, 동시에 의미론적으로 다른 데이터를 구별하지 못하거나 불필요한 속성이 섞여 들어오는 구조적 취약점을 지니기 때문에 과잉 속성 체크나 브랜디드 타입과 같은 추가적인 방어 전략이 반드시 동반되어야 합니다[1, 3, 9]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/구조적 타이핑.md]] +- Raw Source: 00_Raw/2026-04-20/구조적 타이핑.md --- diff --git a/01_Archive/2026-04-20/기본 타입에의 집착 (Primitive Obsession).md b/01_Archive/2026-04-20/기본 타입에의 집착 (Primitive Obsession).md index baa0b954..6cfc1067 100644 --- a/01_Archive/2026-04-20/기본 타입에의 집착 (Primitive Obsession).md +++ b/01_Archive/2026-04-20/기본 타입에의 집착 (Primitive Obsession).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-29E29A -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 기본 타입에의 집착 (Primitive Obsession)" --- -# [[기본 타입에의 집착 (Primitive Obsession)]] +# [[기본 타입에의 집착 (Primitive Obsession)|기본 타입에의 집착 (Primitive Obsession)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > '기본 타입에의 집착(Primitive Obsession)'은 서로 다른 의미와 맥락을 지닌 데이터를 구별하지 않고 범용적인 원시 기본 타입(예: `string`, `number`)만 사용하여 코드를 작성하려는 안티 패턴을 의미합니다 [1, 2]. TypeScript와 같은 구조적 타이핑 환경에서는 이메일 주소와 이름이 모두 `string`으로 취급되어, 의도치 않은 잘못된 값이 전달되더라도 컴파일러가 오류를 잡아내지 못하는 취약점을 발생시킵니다 [2]. 이를 방지하고 타입의 의미적 경계를 명확히 하기 위해, 런타임에는 동일한 원시 값이지만 컴파일 단계에서는 서로 다르게 구별되도록 강제하는 브랜디드 타입(Branded Types)이나 오패크 타입(Opaque Types) 기법이 해결책으로 활용됩니다 [2, 3]. @@ -31,11 +31,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 기본 타입에의 집착 (Pr - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[구조적 타이핑 (Structural Typing)]], [[명목적 타이핑 (Nominal Typing)]], [[브랜디드 타입 (Branded Types)]], [[오패크 타입 (Opaque Types)]] -- **Projects/Contexts:** [[도메인 기반 설계 (DDD)]], [[마스 클라이메이트 오비터 (Mars Climate Orbiter)]] +- **Related Topics:** [[구조적 타이핑 (Structural Typing)|구조적 타이핑 (Structural Typing)]], [[명목적 타이핑 (Nominal Typing)|명목적 타이핑 (Nominal Typing)]], [[브랜디드 타입 (Branded Types)|브랜디드 타입 (Branded Types)]], 오패크 타입 (Opaque Types) +- **Projects/Contexts:** [[도메인 기반 설계 (DDD)|도메인 기반 설계 (DDD)]], 마스 클라이메이트 오비터 (Mars Climate Orbiter) - **Contradictions/Notes:** 브랜디드 타입과 같은 해결책은 프로그램의 안전성을 높이고 '기본 타입에의 집착'을 해소해 주지만, 추가적인 타입 작성 및 개념적 복잡성이 증가하는 단점(비용)이 수반됩니다. 따라서 개발팀은 애플리케이션에서 실제로 직면할 가능성이 높은 문제인지 득실을 판단하여 도입해야 한다고 조언합니다 [9, 10]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/기본 타입에의 집착 (Primitive Obsession).md]] +- Raw Source: 00_Raw/2026-04-20/기본 타입에의 집착 (Primitive Obsession).md --- diff --git a/01_Archive/2026-04-20/기본 타입에의 집착(Primitive Obsession).md b/01_Archive/2026-04-20/기본 타입에의 집착(Primitive Obsession).md index afb3bbfe..7790d205 100644 --- a/01_Archive/2026-04-20/기본 타입에의 집착(Primitive Obsession).md +++ b/01_Archive/2026-04-20/기본 타입에의 집착(Primitive Obsession).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-5462C7 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 기본 타입에의 집착(Primitive Obsession)" --- -# [[기본 타입에의 집착(Primitive Obsession)]] +# [[기본 타입에의 집착(Primitive Obsession)|기본 타입에의 집착(Primitive Obsession)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > '기본 타입에의 집착(Primitive Obsession)'은 이메일 주소, 이름, 식별자, 통화 등 의미적으로 서로 다른 데이터를 `string`이나 `number` 같은 단일한 기본(원시) 타입으로만 취급하여 표현하려는 문제를 뜻한다[1, 2]. TypeScript와 같이 구조적 타이핑(Structural Typing)을 사용하는 언어에서는 컴파일러가 이러한 데이터들의 의미적 차이를 구분하지 못해 의도치 않은 데이터 혼용 실수를 방지할 수 없다[2, 3]. 이 문제를 해결하기 위해 고유한 표식을 부여하는 브랜디드 타입(Branded Types)이나 불투명 타입(Opaque Types) 같은 기법이 해결책으로 사용된다[2-4]. @@ -27,11 +27,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 기본 타입에의 집착(Pri - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[구조적 타이핑(Structural Typing)]], [[브랜디드 타입(Branded Types)]], [[불투명 타입(Opaque Types)]], [[도메인 기반 설계(DDD)]] -- **Projects/Contexts:** [[TypeScript 타입 시스템]], [[Mars Climate Orbiter 사례]] +- **Related Topics:** [[구조적 타이핑(Structural Typing)|구조적 타이핑(Structural Typing)]], [[브랜디드 타입(Branded Types)|브랜디드 타입(Branded Types)]], 불투명 타입(Opaque Types), [[도메인 기반 설계(DDD)|도메인 기반 설계(DDD)]] +- **Projects/Contexts:** TypeScript 타입 시스템, Mars Climate Orbiter 사례 - **Contradictions/Notes:** 소스에 따르면 타입 브랜딩은 프로그램의 안전성을 극대화하지만, 코드의 개념적 복잡성을 증가시키고 작성해야 할 타이핑 량이 많아진다는 단점이 있다. 따라서 일부 소스에서는 값이 0이 아님이 개발자에 의해 명확히 인지되는 등의 특정 상황에서는 브랜디드 타입의 강박적 사용을 피하고 단순한 원시 타입과 단일 예외 처리(어설션)를 사용하는 것이 코드를 더 간결하고 읽기 쉽게 만들 수 있다고 조언한다[12-14]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/기본 타입에의 집착(Primitive Obsession).md]] +- Raw Source: 00_Raw/2026-04-20/기본 타입에의 집착(Primitive Obsession).md --- diff --git a/01_Archive/2026-04-20/기업 문화 진단 및 개선.md b/01_Archive/2026-04-20/기업 문화 진단 및 개선.md index eb764fd7..1710979c 100644 --- a/01_Archive/2026-04-20/기업 문화 진단 및 개선.md +++ b/01_Archive/2026-04-20/기업 문화 진단 및 개선.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-7FF20D -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 기업 문화 진단 및 개선" --- -# [[기업 문화 진단 및 개선]] +# [[기업 문화 진단 및 개선|기업 문화 진단 및 개선]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - 기업 문화 진단 및 개 ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/기업 문화 진단 및 개선.md]] +- Raw Source: 00_Raw/2026-04-20/기업 문화 진단 및 개선.md --- diff --git a/01_Archive/2026-04-20/깊이 지각 (Depth Perception).md b/01_Archive/2026-04-20/깊이 지각 (Depth Perception).md index 4bd80e54..fee9ba7b 100644 --- a/01_Archive/2026-04-20/깊이 지각 (Depth Perception).md +++ b/01_Archive/2026-04-20/깊이 지각 (Depth Perception).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-F049E9 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 깊이 지각 (Depth Perception)" --- -# [[깊이 지각 (Depth Perception)]] +# [[깊이 지각 (Depth Perception)|깊이 지각 (Depth Perception)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 깊이 지각(Depth Perception)은 가까운 물체에 대해 단일하고 명확한 초점을 맞추기 위해 망막의 단서들을 활용하는 시각적 기능이다 [1]. 자연스러운 환경에서는 흐림(blur)과 양안 부등(disparity) 같은 단서를 바탕으로 눈모음(vergence)과 조절(accommodation) 메커니즘이 상호작용하여 깊이를 지각한다 [1]. 그러나 가상현실(VR)과 같은 머리 착용 디스플레이(HMD) 환경에서는 이러한 안구 운동 기능 간의 충돌이나 분리가 발생하여 깊이 지각에 불확실성과 악영향을 초래할 수 있다 [1, 2]. @@ -22,11 +22,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 깊이 지각 (Depth Perceptio - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[눈모음-조절 충돌(Vergence-Accommodation Conflict)]], [[VR 멀미(VR Sickness)]] -- **Projects/Contexts:** [[가상현실(VR) 환경에서의 안구 운동 및 시각 후유증 연구]] +- **Related Topics:** 눈모음-조절 충돌(Vergence-Accommodation Conflict), [[VR 멀미 (VR Sickness)|VR 멀미(VR Sickness)]] +- **Projects/Contexts:** 가상현실(VR) 환경에서의 안구 운동 및 시각 후유증 연구 - **Contradictions/Notes:** 소스에 관련 정보가 부족합니다. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/깊이 지각 (Depth Perception).md]] +- Raw Source: 00_Raw/2026-04-20/깊이 지각 (Depth Perception).md --- diff --git a/01_Archive/2026-04-20/깊이 지각(Depth perception).md b/01_Archive/2026-04-20/깊이 지각(Depth perception).md index cb97bb3c..82e084dc 100644 --- a/01_Archive/2026-04-20/깊이 지각(Depth perception).md +++ b/01_Archive/2026-04-20/깊이 지각(Depth perception).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-889755 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 깊이 지각(Depth perception)" --- -# [[깊이 지각(Depth perception)]] +# [[깊이 지각(Depth perception)|깊이 지각(Depth perception)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 깊이 지각은 인간이 흐림(blur)과 양안 시차(disparity) 같은 망막의 단서를 활용하여 가까운 물체에 정확하게 시선을 고정할 수 있도록 돕는 시각적 기능입니다 [1]. 특히 머리 장착형 디스플레이(HMD) 기반의 가상현실(VR) 환경에서는 사용자가 VR 멀미를 겪을 때 깊이 지각 능력과 인지 능력이 부정적인 영향을 받을 수 있습니다 [2]. VR 사용 후 발생하는 안구 운동의 변화는 현실 세계에서의 깊이 지각 능력에도 영향을 미칠 수 있습니다 [1]. @@ -24,11 +24,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 깊이 지각(Depth perception - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[VR 멀미(VR Sickness)]], [[눈모음-조절 충돌(Vergence-accommodation conflicts)]] -- **Projects/Contexts:** [[머리 장착형 디스플레이(HMD) 환경의 시각적 후유증 연구]] +- **Related Topics:** [[VR 멀미 (VR Sickness)|VR 멀미(VR Sickness)]], [[눈모음-조절 충돌(Vergence-accommodation conflicts)|눈모음-조절 충돌(Vergence-accommodation conflicts)]] +- **Projects/Contexts:** [[머리 장착형 디스플레이(HMD) 환경의 시각적 후유증 연구|머리 장착형 디스플레이(HMD) 환경의 시각적 후유증 연구]] - **Contradictions/Notes:** 소스에 깊이 지각의 기초적인 원리 등에 대한 관련 정보가 부족합니다. 현재 소스는 깊이 지각을 온전히 설명하기보다는, VR 게임(예: Beat Saber) 및 HMD 노출이 안구의 눈모음·조절 기능에 미치는 부작용 측면에 집중하여 서술하고 있습니다. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/깊이 지각(Depth perception).md]] +- Raw Source: 00_Raw/2026-04-20/깊이 지각(Depth perception).md --- diff --git a/01_Archive/2026-04-20/내재적 동기 (Intrinsic Motivation).md b/01_Archive/2026-04-20/내재적 동기 (Intrinsic Motivation).md index 6c1f45c6..e86b5167 100644 --- a/01_Archive/2026-04-20/내재적 동기 (Intrinsic Motivation).md +++ b/01_Archive/2026-04-20/내재적 동기 (Intrinsic Motivation).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-88E0B9 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 내재적 동기 (Intrinsic Motivation)" --- -# [[내재적 동기 (Intrinsic Motivation)]] +# [[내재적 동기 (Intrinsic Motivation)|내재적 동기 (Intrinsic Motivation)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - 내재적 동기 (Intrinsic Mo ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/내재적 동기 (Intrinsic Motivation).md]] +- Raw Source: 00_Raw/2026-04-20/내재적 동기 (Intrinsic Motivation).md --- diff --git a/01_Archive/2026-04-20/내재적 동기 vs 외재적 동기.md b/01_Archive/2026-04-20/내재적 동기 vs 외재적 동기.md index 2923fb9a..85a15c11 100644 --- a/01_Archive/2026-04-20/내재적 동기 vs 외재적 동기.md +++ b/01_Archive/2026-04-20/내재적 동기 vs 외재적 동기.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-AA8345 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 내재적 동기 vs 외재적 동기" --- -# [[내재적 동기 vs 외재적 동기]] +# [[내재적 동기 vs 외재적 동기|내재적 동기 vs 외재적 동기]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - 내재적 동기 vs 외재적 ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/내재적 동기 vs 외재적 동기.md]] +- Raw Source: 00_Raw/2026-04-20/내재적 동기 vs 외재적 동기.md --- diff --git a/01_Archive/2026-04-20/네버 타입 (never type).md b/01_Archive/2026-04-20/네버 타입 (never type).md index 9868f029..ccb09ab8 100644 --- a/01_Archive/2026-04-20/네버 타입 (never type).md +++ b/01_Archive/2026-04-20/네버 타입 (never type).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-90D699 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 네버 타입 (never type)" --- -# [[네버 타입 (never type)]] +# [[네버 타입 (never type)|네버 타입 (never type)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -33,11 +33,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 네버 타입 (never type)" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[식별 가능한 유니온 (Discriminated Unions)]], [[집합론 (Set Theory)]], [[초과 속성 검사 (Excess Property Checking)]], [[구조적 타이핑 (Structural Typing)]] -- **Projects/Contexts:** [[Type-safe Error Handling & Exhaustiveness Checking]], [[TypeScript Advanced Type System]] +- **Related Topics:** [[식별 가능한 유니온 (Discriminated Unions)|식별 가능한 유니온 (Discriminated Unions)]], [[집합론 (Set Theory)|집합론 (Set Theory)]], [[초과 속성 검사 (Excess Property Checking)|초과 속성 검사 (Excess Property Checking)]], [[구조적 타이핑 (Structural Typing)|구조적 타이핑 (Structural Typing)]] +- **Projects/Contexts:** [[Type-safe Error Handling & Exhaustiveness Checking|Type-safe Error Handling & Exhaustiveness Checking]], [[TypeScript Advanced Type System|TypeScript Advanced Type System]] - **Contradictions/Notes:** 소스에서는 `never`와 `void`, `any`, `unknown`을 엄격하게 구분합니다. `void`는 정상적으로 완료되나 반환값이 없는 경우인 반면, `never`는 결코 도달할 수 없거나 완료되지 않는 값이라는 차이를 지적합니다 [5]. 또한 `any`는 타입 시스템을 우회하지만, `never`는 빈 집합으로서 타입 시스템 내에서 엄격한 논리적 제어를 돕는다는 상반된 특성을 지닙니다 [13, 14]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/네버 타입 (never type).md]] +- Raw Source: 00_Raw/2026-04-20/네버 타입 (never type).md --- diff --git a/01_Archive/2026-04-20/넷플릭스 (Netflix) 마이크로서비스 도입 사례.md b/01_Archive/2026-04-20/넷플릭스 (Netflix) 마이크로서비스 도입 사례.md index cc45d305..b61c0385 100644 --- a/01_Archive/2026-04-20/넷플릭스 (Netflix) 마이크로서비스 도입 사례.md +++ b/01_Archive/2026-04-20/넷플릭스 (Netflix) 마이크로서비스 도입 사례.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-E41C28 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 넷플릭스 (Netflix) 마이크로서비스 도입 사례" --- -# [[넷플릭스 (Netflix) 마이크로서비스 도입 사례]] +# [[넷플릭스 (Netflix) 마이크로서비스 도입 사례|넷플릭스 (Netflix) 마이크로서비스 도입 사례]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 넷플릭스는 초기 데이터 센터의 모놀리식(Monolithic) 아키텍처가 가진 확장 및 혁신의 한계를 극복하기 위해 약 7년에 걸쳐 마이크로서비스 아키텍처로의 대대적인 전환을 단행했습니다. 느슨한 결합(Loose coupling)을 통해 각 개발 팀이 개발, 테스트, 배포에 대한 엔드투엔드(End-to-End) 소유권을 가지게 됨으로써 시스템 복원력과 배포 속도가 극대화되었습니다. 이후 미디어 처리 분야에서도 마이크로서비스에 비동기 워크플로와 서버리스 컴퓨팅을 결합한 'Cosmos' 플랫폼을 개발하는 등, 비즈니스 성장에 맞춰 아키텍처를 지속적으로 고도화하고 있습니다. @@ -20,11 +20,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 넷플릭스 (Netflix) 마이 - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Microservices Architecture]], [[Separation of Concerns]], [[Serverless Computing]], [[Chaos Engineering]], [[Micro Frontends]] -- **Projects/Contexts:** [[Simian Army]], [[Apache Cassandra]], [[Cosmos Platform]], [[Reloaded]] +- **Related Topics:** [[마이크로서비스 아키텍처 (Microservices Architecture)|Microservices Architecture]], [[_뇌와 팔다리의 분리_ - 관심사의 분리 (Separation of Concerns)|Separation of Concerns]], [[서버리스 컴퓨팅(Serverless Computing)|Serverless Computing]], Chaos Engineering, [[마이크로 프론트엔드 (Micro Frontends)|Micro Frontends]] +- **Projects/Contexts:** Simian Army, Apache Cassandra, Cosmos Platform, [[리로디드(Reloaded)|Reloaded]] - **Contradictions/Notes:** 넷플릭스의 마이크로서비스 도입은 개발 속도, 혁신, 가용성 측면에서 엄청난 이점을 가져다주었지만, 소스에 따르면 분산 시스템 관리에 따른 운영의 복잡성 증가와 개별 VM/JVM 운영으로 인한 막대한 메모리 소모라는 명확한 기술적 트레이드오프(단점)도 수반했습니다. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/넷플릭스 (Netflix) 마이크로서비스 도입 사례.md]] +- Raw Source: 00_Raw/2026-04-20/넷플릭스 (Netflix) 마이크로서비스 도입 사례.md --- diff --git a/01_Archive/2026-04-20/넷플릭스 비디오 인코딩 파이프라인 (Netflix Video Encoding Pipeline).md b/01_Archive/2026-04-20/넷플릭스 비디오 인코딩 파이프라인 (Netflix Video Encoding Pipeline).md index 322d1b8a..3266a6b5 100644 --- a/01_Archive/2026-04-20/넷플릭스 비디오 인코딩 파이프라인 (Netflix Video Encoding Pipeline).md +++ b/01_Archive/2026-04-20/넷플릭스 비디오 인코딩 파이프라인 (Netflix Video Encoding Pipeline).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-9616B9 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 넷플릭스 비디오 인코딩 파이프라인 (Netflix Video Encoding Pipeline)" --- -# [[넷플릭스 비디오 인코딩 파이프라인 (Netflix Video Encoding Pipeline)]] +# [[넷플릭스 비디오 인코딩 파이프라인 (Netflix Video Encoding Pipeline)|넷플릭스 비디오 인코딩 파이프라인 (Netflix Video Encoding Pipeline)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 넷플릭스의 비디오 인코딩 파이프라인은 파트너와 스튜디오로부터 유입되는 미디어 파일을 처리하여 모든 기기에서 재생할 수 있도록 변환하는 핵심 시스템입니다 [1]. 초기 모놀리식 아키텍처였던 'Reloaded' 시스템의 한계를 극복하기 위해, 현재는 마이크로서비스, 비동기 워크플로우, 서버리스 함수를 결합한 '코스모스(Cosmos)' 플랫폼을 기반으로 운영됩니다 [1-3]. 이 파이프라인은 대규모의 컴퓨팅 리소스를 활용하여 비디오를 여러 청크로 분할한 뒤 병렬로 인코딩하고 조립하는 고도의 오케스트레이션 과정을 거칩니다 [4-6]. @@ -31,11 +31,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 넷플릭스 비디오 인코 - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[마이크로서비스 아키텍처 (Microservices Architecture)]], [[관심사의 분리 (Separation of Concerns)]], [[서버리스 컴퓨팅 (Serverless Computing)]] -- **Projects/Contexts:** [[코스모스 플랫폼 (Cosmos Platform)]], [[Reloaded 시스템]], [[Tapas 서비스]] +- **Related Topics:** [[마이크로서비스 아키텍처 (Microservices Architecture)|마이크로서비스 아키텍처 (Microservices Architecture)]], [[관심사의 분리 (Separation of Concerns)|관심사의 분리 (Separation of Concerns)]], [[서버리스 컴퓨팅(Serverless Computing)|서버리스 컴퓨팅 (Serverless Computing)]] +- **Projects/Contexts:** 코스모스 플랫폼 (Cosmos Platform), Reloaded 시스템, Tapas 서비스 - **Contradictions/Notes:** 넷플릭스의 기존 'Reloaded' 시스템은 7년간 안정적이고 대규모 스케일링이 가능했지만, 단일 모놀리식 데이터 모델과 강한 결합도로 인해 기술적 부채와 배포 지연의 원인이 되었습니다 [1, 7]. 또한 코스모스 서비스에 구현된 모델은 상태가 없는 비즈니스 로직을 API로 제공하는 전형적인 마이크로서비스와는 달리, 다단계 워크플로우와 연산 집약적인 비동기 서버리스 함수가 결합된 형태라는 점에서 구별됩니다 [12]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/넷플릭스 비디오 인코딩 파이프라인 (Netflix Video Encoding Pipeline).md]] +- Raw Source: 00_Raw/2026-04-20/넷플릭스 비디오 인코딩 파이프라인 (Netflix Video Encoding Pipeline).md --- diff --git a/01_Archive/2026-04-20/넷플릭스 코스모스 플랫폼 (Netflix Cosmos Platform).md b/01_Archive/2026-04-20/넷플릭스 코스모스 플랫폼 (Netflix Cosmos Platform).md index 6a83a406..af505a10 100644 --- a/01_Archive/2026-04-20/넷플릭스 코스모스 플랫폼 (Netflix Cosmos Platform).md +++ b/01_Archive/2026-04-20/넷플릭스 코스모스 플랫폼 (Netflix Cosmos Platform).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-E3ABA1 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 넷플릭스 코스모스 플랫폼 (Netflix Cosmos Platform)" --- -# [[넷플릭스 코스모스 플랫폼 (Netflix Cosmos Platform)]] +# [[넷플릭스 코스모스 플랫폼 (Netflix Cosmos Platform)|넷플릭스 코스모스 플랫폼 (Netflix Cosmos Platform)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -30,11 +30,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 넷플릭스 코스모스 플 - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[관심사의 분리 (Separation of Concerns)]], [[마이크로서비스 아키텍처 (Microservices Architecture)]], [[응집도와 결합도 (Cohesion and Coupling)]] -- **Projects/Contexts:** [[넷플릭스 비디오 인코딩 파이프라인 (Netflix Video Encoding Pipeline)]] +- **Related Topics:** [[관심사의 분리 (Separation of Concerns)|관심사의 분리 (Separation of Concerns)]], [[마이크로서비스 아키텍처 (Microservices Architecture)|마이크로서비스 아키텍처 (Microservices Architecture)]], [[응집도와 결합도 (Cohesion and Coupling)|응집도와 결합도 (Cohesion and Coupling)]] +- **Projects/Contexts:** [[넷플릭스 비디오 인코딩 파이프라인 (Netflix Video Encoding Pipeline)|넷플릭스 비디오 인코딩 파이프라인 (Netflix Video Encoding Pipeline)]] - **Contradictions/Notes:** 넷플릭스는 코스모스 플랫폼 도입과 마이크로서비스로의 분리를 통해 혁신과 독립적 배포의 유연성을 얻었으나, 관심사를 고도로 분리하는 분산 시스템을 구축하는 과정에서 서비스 간 통신 메커니즘을 직접 구현해야 하고 독립적인 서버 공간 유지로 인해 관리 복잡성과 비용 상승이라는 대가가 뒤따랐음을 지적하고 있습니다 [10], [7]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/넷플릭스 코스모스 플랫폼 (Netflix Cosmos Platform).md]] +- Raw Source: 00_Raw/2026-04-20/넷플릭스 코스모스 플랫폼 (Netflix Cosmos Platform).md --- diff --git a/01_Archive/2026-04-20/넷플릭스 코스모스 플랫폼 (Netflix Cosmos).md b/01_Archive/2026-04-20/넷플릭스 코스모스 플랫폼 (Netflix Cosmos).md index 1281ef23..c678aea4 100644 --- a/01_Archive/2026-04-20/넷플릭스 코스모스 플랫폼 (Netflix Cosmos).md +++ b/01_Archive/2026-04-20/넷플릭스 코스모스 플랫폼 (Netflix Cosmos).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-F16810 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 넷플릭스 코스모스 플랫폼 (Netflix Cosmos)" --- -# [[넷플릭스 코스모스 플랫폼 (Netflix Cosmos)]] +# [[넷플릭스 코스모스 플랫폼 (Netflix Cosmos)|넷플릭스 코스모스 플랫폼 (Netflix Cosmos)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 넷플릭스 코스모스 플랫폼(Netflix Cosmos)은 마이크로서비스의 장점과 비동기 워크플로우 및 서버리스 함수를 결합한 컴퓨팅 플랫폼이다 [1]. 이 플랫폼은 주로 수 분에서 수 년까지 지속될 수 있는 복잡하고 계층적인 워크플로우를 통해 조정되는 자원 집약적 알고리즘을 처리하는 데 사용된다 [1]. 기존의 모놀리식 아키텍처인 '리로디드(Reloaded)'의 한계를 극복하고 관찰성, 모듈성, 생산성, 자동화된 전송 능력을 향상시키기 위해 개발되었다 [2-4]. @@ -29,11 +29,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 넷플릭스 코스모스 플 - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[마이크로서비스 (Microservices)]], [[관심사의 분리 (Separation of Concerns)]], [[서버리스 컴퓨팅 (Serverless Computing)]] -- **Projects/Contexts:** [[리로디드 (Reloaded)]], [[타파스 (Tapas)]], [[사간 (Sagan)]], [[스트랭글러 피그 패턴 (Strangler fig pattern)]] +- **Related Topics:** 마이크로서비스 (Microservices), [[관심사의 분리 (Separation of Concerns)|관심사의 분리 (Separation of Concerns)]], [[서버리스 컴퓨팅(Serverless Computing)|서버리스 컴퓨팅 (Serverless Computing)]] +- **Projects/Contexts:** [[리로디드(Reloaded)|리로디드 (Reloaded)]], [[타파스(Tapas)|타파스 (Tapas)]], 사간 (Sagan), [[스트랭글러 피그 패턴(Strangler Fig Pattern)|스트랭글러 피그 패턴 (Strangler fig pattern)]] - **Contradictions/Notes:** 소스에 따르면, 코스모스 서비스는 전형적인 마이크로서비스와 유사한 점이 있으나 완전히 같지는 않다. 일반적인 마이크로서비스가 무상태 비즈니스 로직을 가진 API로 요청 부하에 따라 자동 확장되는 반면, 코스모스는 다단계 워크플로우와 컴퓨팅 집약적인 비동기 서버리스 함수를 결합하고 있으며 큐(queue)의 크기에 따라 확장된다는 차이가 존재한다 [14]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/넷플릭스 코스모스 플랫폼 (Netflix Cosmos).md]] +- Raw Source: 00_Raw/2026-04-20/넷플릭스 코스모스 플랫폼 (Netflix Cosmos).md --- diff --git a/01_Archive/2026-04-20/넷플릭스(Netflix)의 마이크로서비스 및 코스모스 플랫폼 전환.md b/01_Archive/2026-04-20/넷플릭스(Netflix)의 마이크로서비스 및 코스모스 플랫폼 전환.md index 174020ba..7d313f1e 100644 --- a/01_Archive/2026-04-20/넷플릭스(Netflix)의 마이크로서비스 및 코스모스 플랫폼 전환.md +++ b/01_Archive/2026-04-20/넷플릭스(Netflix)의 마이크로서비스 및 코스모스 플랫폼 전환.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-AC1C1C -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 넷플릭스(Netflix)의 마이크로서비스 및 코스모스 플랫폼 전환" --- -# [[넷플릭스(Netflix)의 마이크로서비스 및 코스모스 플랫폼 전환]] +# [[넷플릭스(Netflix)의 마이크로서비스 및 코스모스 플랫폼 전환|넷플릭스(Netflix)의 마이크로서비스 및 코스모스 플랫폼 전환]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 넷플릭스(Netflix)는 비즈니스 혁신과 안정성을 위해 기존의 RDBMS 기반 모놀리식 아키텍처를 독립적인 마이크로서비스로 전환하여 뛰어난 확장성과 가용성을 확보했습니다 [1, 2]. 이후 비디오 및 오디오 처리와 같은 미디어 중심의 비동기식 대규모 워크플로우에서 발생하는 병목 현상을 해결하기 위해 마이크로서비스, 워크플로우, 서버리스 함수를 결합한 '코스모스(Cosmos)' 플랫폼을 새롭게 도입했습니다 [3, 4]. 코스모스 플랫폼은 다차원적인 관심사 분리를 통해 인프라와 애플리케이션 코드를 격리하고 시스템의 모듈성 및 생산성을 비약적으로 향상시켰습니다 [4, 5]. @@ -36,11 +36,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 넷플릭스(Netflix)의 마 - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Microservices Architecture]], [[Separation of Concerns]], [[Serverless Functions]], [[Asynchronous Workflows]], [[Chaos Monkey]] -- **Projects/Contexts:** [[Reloaded]], [[Tapas]], [[Sagan]], [[Strangler Fig Pattern]] +- **Related Topics:** [[마이크로서비스 아키텍처 (Microservices Architecture)|Microservices Architecture]], [[_뇌와 팔다리의 분리_ - 관심사의 분리 (Separation of Concerns)|Separation of Concerns]], Serverless Functions, Asynchronous Workflows, [[카오스 몽키(Chaos Monkey)|Chaos Monkey]] +- **Projects/Contexts:** [[리로디드(Reloaded)|Reloaded]], [[타파스(Tapas)|Tapas]], Sagan, [[스트랭글러 피그 패턴(Strangler Fig Pattern)|Strangler Fig Pattern]] - **Contradictions/Notes:** 마이크로서비스 전환과 코스모스와 같은 분산 플랫폼의 구축은 혁신과 확장성 측면에서 큰 이점을 제공하지만, 그 대가로 분산 시스템의 통신 메커니즘을 직접 구현해야 하는 설계적 복잡성을 증가시킵니다 [15, 16]. 또한 여러 서비스 인스턴스를 독립적으로 실행하고 배포해야 하므로, 메모리 소비가 증가하고 운영 비용이 상승하는 단점이 존재합니다 [16-18]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/넷플릭스(Netflix)의 마이크로서비스 및 코스모스 플랫폼 전환.md]] +- Raw Source: 00_Raw/2026-04-20/넷플릭스(Netflix)의 마이크로서비스 및 코스모스 플랫폼 전환.md --- diff --git a/01_Archive/2026-04-20/넷플릭스의 코스모스 플랫폼 및 마이크로서비스 전환.md b/01_Archive/2026-04-20/넷플릭스의 코스모스 플랫폼 및 마이크로서비스 전환.md index d371ab0c..dbf84238 100644 --- a/01_Archive/2026-04-20/넷플릭스의 코스모스 플랫폼 및 마이크로서비스 전환.md +++ b/01_Archive/2026-04-20/넷플릭스의 코스모스 플랫폼 및 마이크로서비스 전환.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-6271CF -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 넷플릭스의 코스모스 플랫폼 및 마이크로서비스 전환" --- -# [[넷플릭스의 코스모스 플랫폼 및 마이크로서비스 전환]] +# [[넷플릭스의 코스모스 플랫폼 및 마이크로서비스 전환|넷플릭스의 코스모스 플랫폼 및 마이크로서비스 전환]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 넷플릭스는 시스템 확장성과 혁신 속도를 높이기 위해 7년에 걸쳐 기존 모놀리식 데이터센터 환경을 마이크로서비스 아키텍처로 성공적으로 전환했습니다 [1, 2]. 이어 미디어 파일 처리 파이프라인인 '리로디드(Reloaded)' 시스템의 운영 복잡성 한계를 극복하기 위해, '코스모스(Cosmos)' 플랫폼을 도입했습니다 [3-5]. 코스모스는 마이크로서비스에 비동기 워크플로우와 서버리스 함수를 결합한 혁신적인 플랫폼으로, API, 워크플로우, 서버리스 계층을 명확히 분할하는 '관심사의 분리(Separation of Concerns)'를 구현하여 개발 생산성과 시스템 안정성을 대폭 향상시켰습니다 [6-8]. @@ -34,11 +34,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 넷플릭스의 코스모스 - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[마이크로서비스 아키텍처(Microservices Architecture)]], [[관심사의 분리(Separation of Concerns)]], [[서버리스 컴퓨팅(Serverless Computing)]], [[카오스 몽키(Chaos Monkey)]], [[카산드라(Cassandra)]] -- **Projects/Contexts:** [[리로디드(Reloaded)]], [[코스모스(Cosmos)]], [[타파스(Tapas)]], [[스트랭글러 피그 패턴(Strangler Fig Pattern)]] +- **Related Topics:** [[마이크로서비스 아키텍처 (Microservices Architecture)|마이크로서비스 아키텍처(Microservices Architecture)]], [[관심사의 분리(Separation of Concerns)|관심사의 분리(Separation of Concerns)]], [[서버리스 컴퓨팅(Serverless Computing)|서버리스 컴퓨팅(Serverless Computing)]], [[카오스 몽키(Chaos Monkey)|카오스 몽키(Chaos Monkey)]], [[카산드라(Cassandra)|카산드라(Cassandra)]] +- **Projects/Contexts:** [[리로디드(Reloaded)|리로디드(Reloaded)]], [[코스모스(Cosmos)|코스모스(Cosmos)]], [[타파스(Tapas)|타파스(Tapas)]], [[스트랭글러 피그 패턴(Strangler Fig Pattern)|스트랭글러 피그 패턴(Strangler Fig Pattern)]] - **Contradictions/Notes:** 마이크로서비스 전환은 넷플릭스에 조직적 민첩성과 신뢰성을 가져다주었지만, 개발자가 분산 시스템 내 서비스 통신을 직접 구현해야 하는 복잡성이 증가하고 N개의 모놀리식 앱이 N*M개의 서비스로 확장되면서 막대한 메모리 및 JVM 오버헤드가 발생한다는 단점도 보고되었습니다 [20-23]. 이러한 한계를 극복하고자 넷플릭스는 단순한 API 호출 방식을 넘어, "마이크로서비스가 워크플로우를 트리거하고, 서버리스 함수를 오케스트레이션하는" 방식으로 플랫폼 아키텍처(코스모스)를 진화시켰습니다 [24]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/넷플릭스의 코스모스 플랫폼 및 마이크로서비스 전환.md]] +- Raw Source: 00_Raw/2026-04-20/넷플릭스의 코스모스 플랫폼 및 마이크로서비스 전환.md --- diff --git a/01_Archive/2026-04-20/뇌 가소성 (Neuroplasticity).md b/01_Archive/2026-04-20/뇌 가소성 (Neuroplasticity).md index 233a6ea2..6bd35851 100644 --- a/01_Archive/2026-04-20/뇌 가소성 (Neuroplasticity).md +++ b/01_Archive/2026-04-20/뇌 가소성 (Neuroplasticity).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-63C048 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 뇌 가소성 (Neuroplasticity)" --- -# [[뇌 가소성 (Neuroplasticity)]] +# [[뇌 가소성 (Neuroplasticity)|뇌 가소성 (Neuroplasticity)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - 뇌 가소성 (Neuroplasticity ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/뇌 가소성 (Neuroplasticity).md]] +- Raw Source: 00_Raw/2026-04-20/뇌 가소성 (Neuroplasticity).md --- diff --git a/01_Archive/2026-04-20/뇌과학 기반 중독 재활 프로그램.md b/01_Archive/2026-04-20/뇌과학 기반 중독 재활 프로그램.md index 1d5927dc..9935ef7d 100644 --- a/01_Archive/2026-04-20/뇌과학 기반 중독 재활 프로그램.md +++ b/01_Archive/2026-04-20/뇌과학 기반 중독 재활 프로그램.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-563E3F -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 뇌과학 기반 중독 재활 프로그램" --- -# [[뇌과학 기반 중독 재활 프로그램]] +# [[뇌과학 기반 중독 재활 프로그램|뇌과학 기반 중독 재활 프로그램]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - 뇌과학 기반 중독 재활 ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/뇌과학 기반 중독 재활 프로그램.md]] +- Raw Source: 00_Raw/2026-04-20/뇌과학 기반 중독 재활 프로그램.md --- diff --git a/01_Archive/2026-04-20/눈모음-조절 충돌(Vergence-accommodation conflicts).md b/01_Archive/2026-04-20/눈모음-조절 충돌(Vergence-accommodation conflicts).md index 30ae02bd..46b24d8d 100644 --- a/01_Archive/2026-04-20/눈모음-조절 충돌(Vergence-accommodation conflicts).md +++ b/01_Archive/2026-04-20/눈모음-조절 충돌(Vergence-accommodation conflicts).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-93D7DA -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 눈모음-조절 충돌(Vergence-accommodation conflicts)" --- -# [[눈모음-조절 충돌(Vergence-accommodation conflicts)]] +# [[눈모음-조절 충돌(Vergence-accommodation conflicts)|눈모음-조절 충돌(Vergence-accommodation conflicts)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 눈모음-조절 충돌(Vergence-accommodation conflicts)은 주로 헤드마운트 디스플레이(HMD)와 같은 가상현실(VR) 환경에서 상충되는 깊이 단서로 인해 눈모음(vergence)과 조절(accommodation) 기능이 분리되면서 발생하는 현상입니다 [1]. 자연스러운 시각 환경에서는 이 두 기능이 피드백 루프를 통해 함께 작동하지만, VR 기기에서는 이 연결이 끊어져 깊이 지각의 불확실성을 초래합니다 [1]. 이 충돌은 시각적 성능을 저하시키고 피로를 유발하며, 다양한 안구 운동 관련 증상과 가상현실 멀미(VR sickness)를 동반할 수 있습니다 [1, 2]. @@ -23,11 +23,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 눈모음-조절 충돌(Vergen - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[가상현실 멀미(VR sickness)]], [[헤드마운트 디스플레이(HMD)]], [[안구 운동 기능(Oculomotor functions)]], [[깊이 지각(Depth perception)]] -- **Projects/Contexts:** [[VR 엑서게임(비트 세이버) 후유증 조사 연구(Investigation of Virtual Reality Aftereffects)]] +- **Related Topics:** [[가상현실 멀미 (VR Sickness)|가상현실 멀미(VR sickness)]], [[헤드 마운트 디스플레이(HMD)|헤드마운트 디스플레이(HMD)]], [[안구 운동 기능(Oculomotor functions)|안구 운동 기능(Oculomotor functions)]], [[깊이 지각(Depth perception)|깊이 지각(Depth perception)]] +- **Projects/Contexts:** VR 엑서게임(비트 세이버) 후유증 조사 연구(Investigation of Virtual Reality Aftereffects) - **Contradictions/Notes:** 눈모음-조절 충돌이 특정 개인들에게 가상현실 멀미(VR sickness)를 발생시키는 직접적인 원인인지, 아니면 멀미 증상의 심각성을 가중시키는 요인인지는 소스 상에서 아직 명확히 밝혀지지 않았습니다 [2]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/눈모음-조절 충돌(Vergence-accommodation conflicts).md]] +- Raw Source: 00_Raw/2026-04-20/눈모음-조절 충돌(Vergence-accommodation conflicts).md --- diff --git a/01_Archive/2026-04-20/느슨한 결합 (Loose Coupling).md b/01_Archive/2026-04-20/느슨한 결합 (Loose Coupling).md index 6d17cfb8..7b003e0c 100644 --- a/01_Archive/2026-04-20/느슨한 결합 (Loose Coupling).md +++ b/01_Archive/2026-04-20/느슨한 결합 (Loose Coupling).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-50EE48 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 느슨한 결합 (Loose Coupling)" --- -# [[느슨한 결합 (Loose Coupling)]] +# [[느슨한 결합 (Loose Coupling)|느슨한 결합 (Loose Coupling)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 느슨한 결합(Loose Coupling)은 소프트웨어 시스템에서 모듈이나 컴포넌트 간의 상호 의존성을 최소화하여 각 부분이 독립적으로 동작할 수 있도록 설계하는 원칙입니다 [1-3]. 이를 통해 한 모듈의 변경이 다른 모듈에 미치는 영향을 최소화하고, 시스템의 유지보수성과 확장성을 크게 향상시킬 수 있습니다 [4-6]. 종종 '높은 응집도(High Cohesion)'와 함께 언급되며, 소프트웨어 품질을 높이는 가장 핵심적인 척도 중 하나로 작용합니다 [5, 7]. @@ -32,11 +32,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 느슨한 결합 (Loose Coupli - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[관심사의 분리 (Separation of Concerns)]], [[응집도 (Cohesion)]], [[의존성 주입 (Dependency Injection)]], [[이벤트 기반 아키텍처 (Event-Driven Architecture)]], [[단일 책임 원칙 (SRP)]] -- **Projects/Contexts:** [[마이크로서비스 아키텍처 (Microservices Architecture)]], [[클린 아키텍처 (Clean Architecture)]], [[계층화 아키텍처 (Layered Architecture)]] +- **Related Topics:** [[관심사의 분리 (Separation of Concerns)|관심사의 분리 (Separation of Concerns)]], [[응집도 (Cohesion)|응집도 (Cohesion)]], [[의존성 주입 (Dependency Injection)|의존성 주입 (Dependency Injection)]], [[이벤트 기반 아키텍처 (Event-Driven Architecture)|이벤트 기반 아키텍처 (Event-Driven Architecture)]], [[단일 책임 원칙 (SRP)|단일 책임 원칙 (SRP)]] +- **Projects/Contexts:** [[마이크로서비스 아키텍처 (Microservices Architecture)|마이크로서비스 아키텍처 (Microservices Architecture)]], [[클린 아키텍처 (Clean Architecture)|클린 아키텍처 (Clean Architecture)]], [[계층화 아키텍처 (Layered Architecture)|계층화 아키텍처 (Layered Architecture)]] - **Contradictions/Notes:** 단순히 시스템을 마이크로서비스로 나눈다고 해서 결합이 완벽히 분리되는 것은 아니며, 네트워크상의 공유 자원이나 공통 데이터 구조에 의해 간접적으로 강하게 결합되는 '결합 분리의 오류'가 발생할 수 있습니다 [21]. 또한, 과도하게 세분화된 분리는 오히려 성능 오버헤드, 네트워크 통신 비용 증가 및 코드 추적의 복잡성을 초래할 수 있으므로 상황에 맞는 적절한 균형이 필요합니다 [22, 23]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/느슨한 결합 (Loose Coupling).md]] +- Raw Source: 00_Raw/2026-04-20/느슨한 결합 (Loose Coupling).md --- diff --git a/01_Archive/2026-04-20/단일 책임 원칙 (SRP).md b/01_Archive/2026-04-20/단일 책임 원칙 (SRP).md index 9a35723c..f50865fe 100644 --- a/01_Archive/2026-04-20/단일 책임 원칙 (SRP).md +++ b/01_Archive/2026-04-20/단일 책임 원칙 (SRP).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-B343BD -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 단일 책임 원칙 (SRP)" --- -# [[단일 책임 원칙 (SRP)]] +# [[단일 책임 원칙 (SRP)|단일 책임 원칙 (SRP)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 단일 책임 원칙(Single Responsibility Principle, SRP)은 클래스, 모듈 또는 함수가 오직 하나의 역할(책임)만을 수행해야 하며, 코드의 변경을 요구하는 이유 또한 단 하나여야 한다는 소프트웨어 설계 원칙입니다 [1, 2]. 이는 객체 지향 프로그래밍의 핵심인 SOLID 원칙 중 하나로, 더 높은 추상화 수준의 개념인 '관심사의 분리(SoC)'를 개별 클래스나 모듈 단위에서 구체화한 것입니다 [3-6]. SRP를 준수하면 코드의 응집도를 높이고 복잡성을 줄여, 가독성과 유지보수성이 뛰어난 시스템을 구축할 수 있습니다 [2, 7]. @@ -24,11 +24,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 단일 책임 원칙 (SRP)" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[관심사의 분리 (SoC)]], [[SOLID 원칙]], [[객체 지향 프로그래밍 (OOP)]], [[응집도 (Cohesion)]] -- **Projects/Contexts:** [[프론트엔드 컴포넌트 구조화]], [[소프트웨어 아키텍처 설계]] +- **Related Topics:** [[관심사의 분리 (SoC)|관심사의 분리 (SoC)]], [[SOLID 원칙|SOLID 원칙]], [[객체 지향 프로그래밍 (OOP)|객체 지향 프로그래밍 (OOP)]], [[응집도 (Cohesion)|응집도 (Cohesion)]] +- **Projects/Contexts:** [[프론트엔드 컴포넌트 구조화|프론트엔드 컴포넌트 구조화]], [[소프트웨어 아키텍처 설계|소프트웨어 아키텍처 설계]] - **Contradictions/Notes:** 소스에 따르면 SoC와 SRP는 서로 대립하는 개념이 아닙니다. 두 원칙 모두 소프트웨어의 모듈성을 높이는 데 기여하지만, SoC는 기능적 측면에서 코드를 구성하는 큰 그림(높은 추상화)을 다루고, SRP는 변경의 이유라는 관점에서 개별 클래스나 모듈의 단일 책임에 집중한다는 범위(Scope)와 초점의 차이가 있습니다 [4, 7]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/단일 책임 원칙 (SRP).md]] +- Raw Source: 00_Raw/2026-04-20/단일 책임 원칙 (SRP).md --- diff --git a/01_Archive/2026-04-20/단일 책임 원칙 (Single Responsibility Principle).md b/01_Archive/2026-04-20/단일 책임 원칙 (Single Responsibility Principle).md index 60f6debf..108aae61 100644 --- a/01_Archive/2026-04-20/단일 책임 원칙 (Single Responsibility Principle).md +++ b/01_Archive/2026-04-20/단일 책임 원칙 (Single Responsibility Principle).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-B860D8 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 단일 책임 원칙 (Single Responsibility Principle)" --- -# [[단일 책임 원칙 (Single Responsibility Principle)]] +# [[단일 책임 원칙 (Single Responsibility Principle)|단일 책임 원칙 (Single Responsibility Principle)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 단일 책임 원칙(SRP)은 클래스, 모듈 또는 함수가 단 하나의 작업이나 책임만을 가져야 하며, 그 코드가 변경되어야 할 이유도 단 하나여야 한다는 객체 지향 설계의 핵심 원칙입니다 [1-3]. 이 원칙은 복잡한 시스템을 모듈화하고 유지보수성을 높이기 위한 '관심사의 분리(SoC)' 개념을 개별 클래스나 함수 수준에서 극대화한 것으로 볼 수 있습니다 [3-5]. 이를 적용하면 코드의 목적이 명확해지고, 하나의 변경 사항이 시스템의 다른 부분에 미치는 영향을 최소화하여 버그 발생 가능성을 줄일 수 있습니다 [6]. @@ -32,11 +32,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 단일 책임 원칙 (Single R - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[객체 지향 프로그래밍(OOP)]], [[SOLID 원칙]], [[응집도(Cohesion)]] -- **Projects/Contexts:** [[프론트엔드 컴포넌트 설계]], [[객체 지향 소프트웨어 아키텍처 설계]] +- **Related Topics:** [[객체 지향 프로그래밍(OOP)|객체 지향 프로그래밍(OOP)]], [[SOLID 원칙|SOLID 원칙]], [[응집도 (Cohesion)|응집도(Cohesion)]] +- **Projects/Contexts:** [[프론트엔드 컴포넌트 설계|프론트엔드 컴포넌트 설계]], [[객체 지향 소프트웨어 아키텍처 설계|객체 지향 소프트웨어 아키텍처 설계]] - **Contradictions/Notes:** 단일 책임 원칙(SRP)과 관심사의 분리(SoC)는 종종 같은 의미로 혼용되거나 비교되지만, 적용되는 추상화 수준에서 차이가 있습니다. SoC는 더 넓은 의미의 기능적 관심사를 모듈이나 아키텍처 계층 수준에서 분리하는 것에 초점을 맞추는 반면, SRP는 가장 작은 단위인 개별 클래스나 함수가 가지는 책임과 변경의 이유를 하나로 제한하는 데 집중합니다 [3]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/단일 책임 원칙 (Single Responsibility Principle).md]] +- Raw Source: 00_Raw/2026-04-20/단일 책임 원칙 (Single Responsibility Principle).md --- diff --git a/01_Archive/2026-04-20/단일 책임 원칙(SRP).md b/01_Archive/2026-04-20/단일 책임 원칙(SRP).md index 5a81a2ef..0c756201 100644 --- a/01_Archive/2026-04-20/단일 책임 원칙(SRP).md +++ b/01_Archive/2026-04-20/단일 책임 원칙(SRP).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-F57735 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 단일 책임 원칙(SRP)" --- -# [[단일 책임 원칙(SRP)]] +# [[단일 책임 원칙(SRP)|단일 책임 원칙(SRP)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 단일 책임 원칙(SRP, Single Responsibility Principle)은 클래스나 모듈이 단 하나의 변경 이유만 가져야 한다는 소프트웨어 설계 원칙입니다 [1, 2]. 하나의 모듈에 영속성, 데이터 처리, 알림 등 여러 책임이 섞이면 코드가 불안정해지고 조그만 수정에도 예기치 않은 문제가 발생할 위험이 커집니다 [2]. 이 원칙을 준수하면 각 모듈이 한 가지 명확한 역할만 수행하게 되어, 한 영역의 코드를 수정할 때 다른 무관한 로직에 영향을 미치지 않고 안전하게 변경할 수 있습니다 [2, 3]. @@ -26,11 +26,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 단일 책임 원칙(SRP)" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[SOLID]], [[인터페이스 분리 원칙(ISP)]], [[퍼사드(Facade) 패턴]] -- **Projects/Contexts:** [[Toss Front SDK]], [[Strapi]] +- **Related Topics:** [[SOLID 원칙|SOLID]], 인터페이스 분리 원칙(ISP), 퍼사드(Facade) 패턴 +- **Projects/Contexts:** [[Toss Front SDK 기반 외부 연동사 플러그인 개발 생태계 구축|Toss Front SDK]], Strapi - **Contradictions/Notes:** 소스 내에서 단일 책임 원칙에 대한 모순점은 없으며, 제공된 모든 소스에서 모듈의 결합도를 낮추고 예측 가능성을 높이는 핵심 아키텍처 원칙으로 일관되게 강조하고 있습니다. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/단일 책임 원칙(SRP).md]] +- Raw Source: 00_Raw/2026-04-20/단일 책임 원칙(SRP).md --- diff --git a/01_Archive/2026-04-20/대규모 3D 건축 모델(BIM) 시각화.md b/01_Archive/2026-04-20/대규모 3D 건축 모델(BIM) 시각화.md index d88b07f7..56fc3c89 100644 --- a/01_Archive/2026-04-20/대규모 3D 건축 모델(BIM) 시각화.md +++ b/01_Archive/2026-04-20/대규모 3D 건축 모델(BIM) 시각화.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-750154 -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 대규모 3D 건축 모델(BIM) 시각화" --- -# [[대규모 3D 건축 모델(BIM) 시각화]] +# [[대규모 3D 건축 모델(BIM) 시각화|대규모 3D 건축 모델(BIM) 시각화]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 대규모 3D 건축 모델(BIM) 시각화는 수십만에서 수백만 개의 개별 컴포넌트로 구성된 복잡한 건축 및 산업 환경을 웹 브라우저 등에서 실시간으로 렌더링하는 기술을 의미합니다 [1-3]. 이를 원활하게 처리하기 위해서는 드로우 콜(Draw Call) 병목 현상과 메모리 한계를 극복해야 하며, 객체의 고유성 여부에 따라 형상 병합(Batching)과 인스턴싱(Instancing)을 혼합하는 하이브리드 최적화 및 WebGPU의 컴퓨트 셰이더와 같은 최신 그래픽 API 기술이 필수적으로 요구됩니다 [4-7]. @@ -23,11 +23,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 대규모 3D 건축 모델(BIM - **정책 변화:** Graphics & Performance 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[InstancedMesh]], [[BatchedMesh]], [[WebGPU]], [[Compute Shader]], [[Draw Call]], [[Occlusion Culling]], [[Level of Detail (LOD)]] -- **Projects/Contexts:** [[IFC.js (Fragment)]], [[Revit glTF Export]] +- **Related Topics:** [[InstancedMesh|InstancedMesh]], [[BatchedMesh|BatchedMesh]], [[WebGPU|WebGPU]], [[Compute Shader|Compute Shader]], [[Draw Call|Draw Call]], [[Occlusion Culling|Occlusion Culling]], [[Level of Detail (LOD)|Level of Detail (LOD)]] +- **Projects/Contexts:** [[IFC.js (Fragment)|IFC.js (Fragment)]], [[Revit glTF Export|Revit glTF Export]] - **Contradictions/Notes:** 성능 최적화 기법으로 흔히 권장되는 `THREE.LOD` (Level of Detail)는 방대하고 동적으로 생성/변경되는 산업용 플랜트나 BIM 씬에서는 적합하지 않을 수 있습니다. 모든 LOD 단계의 메쉬를 GPU 메모리에 유지해야 하고, 런타임에 동적으로 지오메트리 단순화 버전을 생성하는 오버헤드가 커서 오히려 성능을 저하시킬 수 있기 때문입니다. 이러한 환경에서는 드로우 콜을 줄이는 배칭(Batching)이나 인스턴싱이 우선적으로 고려되어야 합니다 [3, 23-26]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/대규모 3D 건축 모델(BIM) 시각화.md]] +- Raw Source: 00_Raw/2026-04-20/대규모 3D 건축 모델(BIM) 시각화.md --- diff --git a/01_Archive/2026-04-20/대규모 React 프론트엔드 최적화.md b/01_Archive/2026-04-20/대규모 React 프론트엔드 최적화.md index 722de782..2c9cd856 100644 --- a/01_Archive/2026-04-20/대규모 React 프론트엔드 최적화.md +++ b/01_Archive/2026-04-20/대규모 React 프론트엔드 최적화.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-FAAB3D -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 대규모 React 프론트엔드 최적화" --- -# [[대규모 React 프론트엔드 최적화]] +# [[대규모 React 프론트엔드 최적화|대규모 React 프론트엔드 최적화]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - 대규모 React 프론트엔 ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/대규모 React 프론트엔드 최적화.md]] +- Raw Source: 00_Raw/2026-04-20/대규모 React 프론트엔드 최적화.md --- diff --git a/01_Archive/2026-04-20/대규모 TypeScript 애플리케이션 아키텍처 설계.md b/01_Archive/2026-04-20/대규모 TypeScript 애플리케이션 아키텍처 설계.md index 6f0b443a..c99b9657 100644 --- a/01_Archive/2026-04-20/대규모 TypeScript 애플리케이션 아키텍처 설계.md +++ b/01_Archive/2026-04-20/대규모 TypeScript 애플리케이션 아키텍처 설계.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-00FB6C -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 대규모 TypeScript 애플리케이션 아키텍처 설계" --- -# [[대규모 TypeScript 애플리케이션 아키텍처 설계]] +# [[대규모 TypeScript 애플리케이션 아키텍처 설계|대규모 TypeScript 애플리케이션 아키텍처 설계]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 대규모 TypeScript 애플리케이션 아키텍처 설계는 언어의 강력한 정적 타입 시스템과 객체 지향 및 함수형 설계 원칙(SOLID 등)을 결합하여 예측 가능하고 유지보수 가능한 시스템을 구축하는 과정입니다 [1, 2]. 불변성 강제, 식별 가능한 유니온, 도메인 에러의 타입화 등을 통해 런타임 에러를 방지하고 논리적으로 잘못된 상태를 표현할 수 없도록 원천 차단합니다 [3-5]. 또한 무분별한 추상화를 피하고 퍼사드 패턴이나 객체 합성을 통해 모듈 간 결합도를 낮추는 것을 핵심 목표로 삼습니다 [6, 7]. @@ -31,11 +31,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 대규모 TypeScript 애플리 - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[SOLID 원칙]], [[식별 가능한 유니온 (Discriminated Unions)]], [[브랜디드 타입 (Branded Types)]], [[퍼사드 패턴 (Facade Pattern)]], [[Parse, don't validate]], [[구조적 타이핑 (Structural Typing)]] -- **Projects/Contexts:** [[토스(Toss) Front SDK 개발 환경]], [[엔터프라이즈급 대규모 상태 관리 시스템]] +- **Related Topics:** [[SOLID 원칙|SOLID 원칙]], [[식별 가능한 유니온 (Discriminated Unions)|식별 가능한 유니온 (Discriminated Unions)]], [[브랜디드 타입 (Branded Types)|브랜디드 타입 (Branded Types)]], 퍼사드 패턴 (Facade Pattern), [[Parse, don't validate|Parse, don't validate]], [[구조적 타이핑 (Structural Typing)|구조적 타이핑 (Structural Typing)]] +- **Projects/Contexts:** 토스(Toss) Front SDK 개발 환경, 엔터프라이즈급 대규모 상태 관리 시스템 - **Contradictions/Notes:** TypeScript 커뮤니티 내에서는 객체 구조 정의 시 `type`과 `interface`의 선택 기준에 대한 논쟁이 존재합니다. 캐싱을 통한 컴파일 성능 향상과 선언 병합(Declaration Merging)의 이점 때문에 `interface`를 선호하는 관점이 있는 반면 [9-11], 의도치 않은 선언 병합을 방지하고 보다 엄격한 관리를 위해 애플리케이션 내부에서는 `type`만을 일관되게 사용해야 한다는 개발팀의 실무적 주장도 강하게 대립합니다 [13, 37, 38]. 또한, 함수형 프로그래밍에서 유래한 `Result` 타입 반환 패턴 역시 명확한 에러 흐름 제어로 호평받지만, 코드의 보일러플레이트를 증가시켜 가독성을 해칠 수 있다는 비판적 시각도 존재합니다 [39-41]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/대규모 TypeScript 애플리케이션 아키텍처 설계.md]] +- Raw Source: 00_Raw/2026-04-20/대규모 TypeScript 애플리케이션 아키텍처 설계.md --- diff --git a/01_Archive/2026-04-20/대규모 TypeScript 프로젝트의 컴파일 성능 최적화.md b/01_Archive/2026-04-20/대규모 TypeScript 프로젝트의 컴파일 성능 최적화.md index 16aa235e..c412921f 100644 --- a/01_Archive/2026-04-20/대규모 TypeScript 프로젝트의 컴파일 성능 최적화.md +++ b/01_Archive/2026-04-20/대규모 TypeScript 프로젝트의 컴파일 성능 최적화.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-C4763A -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 대규모 TypeScript 프로젝트의 컴파일 성능 최적화" --- -# [[대규모 TypeScript 프로젝트의 컴파일 성능 최적화]] +# [[대규모 TypeScript 프로젝트의 컴파일 성능 최적화|대규모 TypeScript 프로젝트의 컴파일 성능 최적화]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 대규모 TypeScript 프로젝트의 컴파일 성능을 최적화하려면 복잡한 타입 연산을 줄이고 컴파일러의 캐싱 능력을 극대화해야 합니다 [1-3]. 특히 구조를 매번 재평가해야 하는 교집합(`&`) 타입 대신 인터페이스 확장(`extends`)을 우선적으로 사용하여 평탄화(flattening) 오버헤드를 방지하는 것이 가장 핵심적인 성능 향상 전략입니다 [3, 4]. 더불어 과도하게 복잡한 유니온 타입이나, 호출 시점마다 부가 정보를 추적하는 제네릭 타입의 사용을 최소화하여 컴파일 속도 저하를 막아야 합니다 [5, 6]. @@ -22,11 +22,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 대규모 TypeScript 프로젝 - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[인터페이스 확장 (Interface Extends)]], [[교집합 타입 (Intersection Types)]], [[타입 캐싱 (Type Caching)]], [[판별 가능한 유니온 (Discriminated Unions)]] -- **Projects/Contexts:** [[대규모 코드베이스 (Large Codebases)]], [[타입 검사 및 IDE 성능 최적화 (Type Checking and IDE Performance)]] +- **Related Topics:** 인터페이스 확장 (Interface Extends), [[교집합 타입 (Intersection Types)|교집합 타입 (Intersection Types)]], 타입 캐싱 (Type Caching), 판별 가능한 유니온 (Discriminated Unions) +- **Projects/Contexts:** 대규모 코드베이스 (Large Codebases), 타입 검사 및 IDE 성능 최적화 (Type Checking and IDE Performance) - **Contradictions/Notes:** 의도치 않은 선언 병합(Declaration Merging)의 위험성 때문에 많은 실무 팀들이 인터페이스 대신 `type`만을 사용하는 컨벤션을 선호하기도 하지만 [10], TypeScript의 컴파일 및 성능 가이드라인 측면에서는 교집합(`&`) 대신 인터페이스 확장(`extends`)을 사용하는 것이 권장되고 있습니다 [3, 4]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/대규모 TypeScript 프로젝트의 컴파일 성능 최적화.md]] +- Raw Source: 00_Raw/2026-04-20/대규모 TypeScript 프로젝트의 컴파일 성능 최적화.md --- diff --git a/01_Archive/2026-04-20/대규모 건설 뷰어(Construction Viewers).md b/01_Archive/2026-04-20/대규모 건설 뷰어(Construction Viewers).md index 12441a2d..ef6ddb07 100644 --- a/01_Archive/2026-04-20/대규모 건설 뷰어(Construction Viewers).md +++ b/01_Archive/2026-04-20/대규모 건설 뷰어(Construction Viewers).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-9E35B0 -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 대규모 건설 뷰어(Construction Viewers)" --- -# [[대규모 건설 뷰어(Construction Viewers)]] +# [[대규모 건설 뷰어(Construction Viewers)|대규모 건설 뷰어(Construction Viewers)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 대규모 건설 뷰어(Construction Viewers)는 수천에서 수백만 개의 객체로 구성된 거대한 BIM(Building Information Modeling) 및 CAD 데이터를 웹 브라우저 환경 등에서 실시간으로 렌더링하고 시각화하는 플랫폼이다 [1-3]. 복잡한 기하학적 구조, 고유한 형태의 벽체나 배관, 반복되는 가구 등을 효율적으로 처리하고 사용자와의 상호작용을 지원하기 위해 Three.js, WebGPU, 그리고 다양한 렌더링 최적화 기법이 필수적으로 요구된다 [4-6]. @@ -22,11 +22,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 대규모 건설 뷰어(Constr - **정책 변화:** Graphics & Performance 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[BIM(Building Information Modeling)]], [[WebGPU]], [[BatchedMesh]], [[InstancedMesh]] -- **Projects/Contexts:** [[IFC.js]], [[Revit]], [[Segments.ai]] +- **Related Topics:** BIM(Building Information Modeling), [[WebGPU|WebGPU]], [[BatchedMesh|BatchedMesh]], [[InstancedMesh|InstancedMesh]] +- **Projects/Contexts:** [[IFC.js|IFC.js]], [[Revit 모델 렌더링|Revit]], [[Segments.ai|Segments.ai]] - **Contradictions/Notes:** 동일한 재질의 객체를 묶어 가시성을 개별 관리하기 위해 `BatchedMesh`가 유용하게 쓰일 수 있지만, 수백만 개의 삼각형과 수십만 개의 고유 형상이 포함된 복잡한 Revit 추출 모델 등에서는 `BatchedMesh`를 사용했을 때 CPU 사용량이 급증하고 프레임률(FPS)이 오히려 크게 하락하는 심각한 성능 병목 현상이 보고되기도 한다 [20-23]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/대규모 건설 뷰어(Construction Viewers).md]] +- Raw Source: 00_Raw/2026-04-20/대규모 건설 뷰어(Construction Viewers).md --- diff --git a/01_Archive/2026-04-20/대규모 건축물 및 지형 뷰어(BIM).md b/01_Archive/2026-04-20/대규모 건축물 및 지형 뷰어(BIM).md index d29aa004..578e2f22 100644 --- a/01_Archive/2026-04-20/대규모 건축물 및 지형 뷰어(BIM).md +++ b/01_Archive/2026-04-20/대규모 건축물 및 지형 뷰어(BIM).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-73ED53 -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 대규모 건축물 및 지형 뷰어(BIM)" --- -# [[대규모 건축물 및 지형 뷰어(BIM)]] +# [[대규모 건축물 및 지형 뷰어(BIM)|대규모 건축물 및 지형 뷰어(BIM)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 대규모 건축물 및 지형 뷰어(BIM)는 병원 캠퍼스, 공항 터미널, 도시 규모의 디지털 트윈 등 500MB를 초과하는 방대한 규모의 3D 모델을 실시간으로 시각화하는 시스템이다 [1, 2]. 이러한 모델은 보, 기둥, HVAC 시스템과 같이 수십만 개의 개별 구성 요소로 이루어져 있어 막대한 렌더링 부하를 유발한다 [3]. 이를 원활하게 렌더링하고 시각적 상호작용을 지원하기 위해서는 WebGPU, BatchedMesh, 공간 분할 알고리즘 등 드로우 콜(Draw Call)을 최소화하고 메모리를 관리하는 고도의 최적화 기술이 필수적으로 요구된다 [3-5]. @@ -23,11 +23,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 대규모 건축물 및 지형 - **정책 변화:** Graphics & Performance 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[WebGPU]], [[BatchedMesh]], [[InstancedMesh]], [[Compute Shader]], [[Draw Call]], [[Frustum Culling]] -- **Projects/Contexts:** [[Three.js]], [[IFC.js]], [[Cesium]] +- **Related Topics:** [[WebGPU|WebGPU]], [[BatchedMesh|BatchedMesh]], [[InstancedMesh|InstancedMesh]], [[Compute Shader|Compute Shader]], [[Draw Call|Draw Call]], [[Frustum Culling|Frustum Culling]] +- **Projects/Contexts:** [[Three.js|Three.js]], [[IFC.js|IFC.js]], [[Cesium|Cesium]] - **Contradictions/Notes:** 소스에 따르면 `BatchedMesh`는 BIM 모델처럼 다양한 기하학적 객체를 통합하는 데 필수적이라고 평가받지만 [4], 1,000만 개 이상의 정점과 다수의 고유 기하학을 포함하는 환경에서 정렬(Sort) 및 개별 절두체 컬링(perObjectFrustumCulled) 기능을 활성화할 경우, 도리어 단순 병합 메쉬(Merged Mesh)보다 30~50% 더 심각한 CPU 성능 저하를 일으킬 수 있다는 실증적 한계가 보고되고 있습니다 [21-26]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/대규모 건축물 및 지형 뷰어(BIM).md]] +- Raw Source: 00_Raw/2026-04-20/대규모 건축물 및 지형 뷰어(BIM).md --- diff --git a/01_Archive/2026-04-20/대규모 데이터 렌더링 및 가상화 최적화.md b/01_Archive/2026-04-20/대규모 데이터 렌더링 및 가상화 최적화.md index 40edc607..88ff2385 100644 --- a/01_Archive/2026-04-20/대규모 데이터 렌더링 및 가상화 최적화.md +++ b/01_Archive/2026-04-20/대규모 데이터 렌더링 및 가상화 최적화.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-BB908E -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 대규모 데이터 렌더링 및 가상화 최적화" --- -# [[대규모 데이터 렌더링 및 가상화 최적화]] +# [[대규모 데이터 렌더링 및 가상화 최적화|대규모 데이터 렌더링 및 가상화 최적화]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 대규모 리스트나 테이블을 렌더링할 때 발생하는 DOM 노드 폭증과 메모리 부족, 프레임 저하 현상을 방지하기 위해, 전체 데이터 중 현재 화면(Viewport)에 보이는 항목과 약간의 여분(Buffer)만을 동적으로 마운트하여 렌더링하는 성능 최적화 기법입니다. @@ -35,9 +35,9 @@ github_commit: "[P-Reinforce] Continuous Worker - 대규모 데이터 렌더링 - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[React Performance Optimization]], [[재조정 (Reconciliation)]], [[불필요한 리렌더링 방지]] +- **Related Topics:** [[React Performance Optimization|React Performance Optimization]], [[재조정 (Reconciliation)|재조정 (Reconciliation)]], [[불필요한 리렌더링 방지|불필요한 리렌더링 방지]] -- **Projects/Contexts:** [[장기 실행되는 실시간 데이터 대시보드 최적화]], [[대규모 로그 뷰어 및 데이터 테이블 구현]], [[이커머스 무한 스크롤 상품 리스트]] +- **Projects/Contexts:** [[장기 실행되는 실시간 데이터 대시보드 최적화|장기 실행되는 실시간 데이터 대시보드 최적화]], [[대규모 로그 뷰어 및 데이터 테이블 구현|대규모 로그 뷰어 및 데이터 테이블 구현]], 이커머스 무한 스크롤 상품 리스트 - **Contradictions/Notes:** 50~100개 이상의 대규모 리스트나 무한 스크롤 환경에서는 가상화가 필수적이지만, 항목의 높이가 제각각인 가변 높이 항목(Variable height items)을 렌더링할 때는 렌더링 전 각 항목의 크기를 측정(Measurement)하는 단계가 필요하여 구현이 훨씬 복잡해집니다. 따라서 가급적 리스트 항목의 높이를 일정하게 설계하는 것이 성능과 구현 측면에서 훨씬 유리합니다. @@ -45,5 +45,5 @@ github_commit: "[P-Reinforce] Continuous Worker - 대규모 데이터 렌더링 --- _Last updated: 2026-04-15_ -- Raw Source: [[00_Raw/2026-04-20/대규모 데이터 렌더링 및 가상화 최적화.md]] +- Raw Source: 00_Raw/2026-04-20/대규모 데이터 렌더링 및 가상화 최적화.md --- diff --git a/01_Archive/2026-04-20/대규모 로그 뷰어 및 데이터 테이블 구현.md b/01_Archive/2026-04-20/대규모 로그 뷰어 및 데이터 테이블 구현.md index 0a8b2dff..a0edf5a5 100644 --- a/01_Archive/2026-04-20/대규모 로그 뷰어 및 데이터 테이블 구현.md +++ b/01_Archive/2026-04-20/대규모 로그 뷰어 및 데이터 테이블 구현.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-7D1621 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 대규모 로그 뷰어 및 데이터 테이블 구현" --- -# [[대규모 로그 뷰어 및 데이터 테이블 구현]] +# [[대규모 로그 뷰어 및 데이터 테이블 구현|대규모 로그 뷰어 및 데이터 테이블 구현]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - 대규모 로그 뷰어 및 ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/대규모 로그 뷰어 및 데이터 테이블 구현.md]] +- Raw Source: 00_Raw/2026-04-20/대규모 로그 뷰어 및 데이터 테이블 구현.md --- diff --git a/01_Archive/2026-04-20/대규모 모노레포(Turborepo) 환경에서의 린트 오케스트레이션.md b/01_Archive/2026-04-20/대규모 모노레포(Turborepo) 환경에서의 린트 오케스트레이션.md index 1f97a1ab..ca1467b0 100644 --- a/01_Archive/2026-04-20/대규모 모노레포(Turborepo) 환경에서의 린트 오케스트레이션.md +++ b/01_Archive/2026-04-20/대규모 모노레포(Turborepo) 환경에서의 린트 오케스트레이션.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-873405 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 대규모 모노레포(Turborepo) 환경에서의 린트 오케스트레이션" --- -# [[대규모 모노레포(Turborepo) 환경에서의 린트 오케스트레이션]] +# [[대규모 모노레포(Turborepo) 환경에서의 린트 오케스트레이션|대규모 모노레포(Turborepo) 환경에서의 린트 오케스트레이션]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 대규모 모노레포(Turborepo) 환경에서는 여러 패키지가 혼재하여 린트(ESLint, Prettier) 설정이 중복되고 일관성이 떨어지며 모노레포 루트에서 `lint-staged`를 실행하기 까다로운 문제가 발생합니다 [1-3]. 이를 해결하기 위해 중앙 집중식 설정 패키지를 구성하고, 모노레포 루트에서 파일 패턴을 기반으로 적절한 프리셋을 매핑하는 오케스트레이션 구성을 도입합니다 [3, 4]. 이 아키텍처는 패키지별 자율성을 유지하면서도 Husky 및 lint-staged와 결합하여 변경된 파일만 효율적으로 검사할 수 있도록 지원합니다 [5, 6]. @@ -24,11 +24,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 대규모 모노레포(Turbore - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[ESLint]], [[Prettier]], [[Husky]], [[lint-staged]] -- **Projects/Contexts:** [[Turborepo를 활용한 다중 애플리케이션 및 라이브러리 통합 관리]] +- **Related Topics:** [[ESLint|ESLint]], [[Prettier|Prettier]], [[Husky|Husky]], [[lint-staged|lint-staged]] +- **Projects/Contexts:** [[Turborepo를 활용한 다중 애플리케이션 및 라이브러리 통합 관리|Turborepo를 활용한 다중 애플리케이션 및 라이브러리 통합 관리]] - **Contradictions/Notes:** 분산된 린트 구성 방식은 개별 패키지의 제어력을 높여줄 것 같지만 실제로는 심각한 중복과 유지보수 문제를 야기합니다. 소스는 오히려 중앙 집중식 설정과 루트 오케스트레이션을 결합하는 방식이 종속성 중복을 줄이고(package-lock.json 축소), 전체적인 코드 라인 수를 감소시키면서도 패키지별 자율성을 보장할 수 있다고 강조합니다 [5, 8, 9]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/대규모 모노레포(Turborepo) 환경에서의 린트 오케스트레이션.md]] +- Raw Source: 00_Raw/2026-04-20/대규모 모노레포(Turborepo) 환경에서의 린트 오케스트레이션.md --- diff --git a/01_Archive/2026-04-20/대규모 애플리케이션 개발.md b/01_Archive/2026-04-20/대규모 애플리케이션 개발.md index 11cdd114..8a13dc05 100644 --- a/01_Archive/2026-04-20/대규모 애플리케이션 개발.md +++ b/01_Archive/2026-04-20/대규모 애플리케이션 개발.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-0D36D4 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 대규모 애플리케이션 개발" --- -# [[대규모 애플리케이션 개발]] +# [[대규모 애플리케이션 개발|대규모 애플리케이션 개발]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -36,11 +36,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 대규모 애플리케이션 - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[구조적 타이핑(Structural Typing)]], [[식별 가능한 유니온(Discriminated Unions)]], [[브랜디드 타입(Branded Types)]], [[불변성(Immutability)]], [[satisfies 연산자]] -- **Projects/Contexts:** [[토스(Toss) Front SDK 퍼사드 패턴 적용]], [[Zod 파싱과 브랜디드 타입을 결합한 런타임 데이터 검증]] +- **Related Topics:** [[구조적 타이핑(Structural Typing)|구조적 타이핑(Structural Typing)]], [[식별 가능한 유니온(Discriminated Unions)|식별 가능한 유니온(Discriminated Unions)]], [[브랜디드 타입(Branded Types)|브랜디드 타입(Branded Types)]], [[불변성(Immutability)|불변성(Immutability)]], [[satisfies 연산자|satisfies 연산자]] +- **Projects/Contexts:** [[토스(Toss) Front SDK 퍼사드 패턴 적용|토스(Toss) Front SDK 퍼사드 패턴 적용]], [[Zod 파싱과 브랜디드 타입을 결합한 런타임 데이터 검증|Zod 파싱과 브랜디드 타입을 결합한 런타임 데이터 검증]] - **Contradictions/Notes:** 소스에 따르면 "상속(Inheritance)"보다 "합성(Composition)"을 선호하는 것이 TypeScript 인터페이스 설계의 핵심 원칙 중 하나라고 주장합니다. 클래스 기반 상속은 구조를 경직시키고 결합도를 높이므로, 작은 인터페이스들의 조합을 통해 유연한 수비력을 제공해야 한다고 강조합니다 [8, 12]. 또한 구조적 타이핑의 유연성은 개발의 편의를 주지만, 이로 인한 '기본 타입에의 집착'과 같은 취약점은 브랜디드 타입이라는 인위적인 명목적 타이핑 우회로를 통해 보완해야 한다고 지적합니다 [6, 11]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/대규모 애플리케이션 개발.md]] +- Raw Source: 00_Raw/2026-04-20/대규모 애플리케이션 개발.md --- diff --git a/01_Archive/2026-04-20/대규모 웹 그래픽스 프로젝트.md b/01_Archive/2026-04-20/대규모 웹 그래픽스 프로젝트.md index e5f570b4..5fd21d08 100644 --- a/01_Archive/2026-04-20/대규모 웹 그래픽스 프로젝트.md +++ b/01_Archive/2026-04-20/대규모 웹 그래픽스 프로젝트.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-F01D3F -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 대규모 웹 그래픽스 프로젝트" --- -# [[대규모 웹 그래픽스 프로젝트]] +# [[대규모 웹 그래픽스 프로젝트|대규모 웹 그래픽스 프로젝트]] ## 📌 한 줄 통찰 (The Karpathy Summary) > InstancedMesh는 동일한 기하학적 구조와 재질을 가진 수많은 객체를 단 한 번의 드로우 콜(Draw Call)로 처리하여 CPU 병목을 획기적으로 줄여주는 실시간 웹 그래픽스 렌더링 최적화 기술입니다[1-4]. 그러나 이러한 드로우 콜 최적화는 시야 절두체 컬링(Frustum Culling)의 비효율성, 개별 객체 정렬 부재로 인한 오버드로우(Overdraw), 메모리 대역폭 한계, 그리고 애니메이션 및 상호작용 구현의 어려움 등 다양한 구조적 한계와 새로운 성능 병목 현상을 유발하는 것으로 나타났습니다[5, 6]. @@ -33,12 +33,12 @@ github_commit: "[P-Reinforce] Continuous Worker - 대규모 웹 그래픽스 프 - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[InstancedMesh]], [[BatchedMesh]], [[Frustum Culling]], [[Overdraw]], [[Draw Call]] -- **Projects/Contexts:** [[WebGPU]], [[InstancedMesh2]] +- **Related Topics:** [[InstancedMesh|InstancedMesh]], [[BatchedMesh|BatchedMesh]], [[Frustum Culling|Frustum Culling]], [[Overdraw|Overdraw]], [[Draw Call|Draw Call]] +- **Projects/Contexts:** [[WebGPU|WebGPU]], [[InstancedMesh2|InstancedMesh2]] - **Contradictions/Notes:** 드로우 콜을 1회로 극적으로 줄이는 InstancedMesh가 무조건적인 성능 향상을 보장하지는 않습니다. 개별 인스턴스에 대한 시야 절두체 컬링과 깊이 정렬(Depth Sorting)이 지원되지 않기 때문에, 조명 연산이 복잡한 `MeshStandardMaterial` 등을 사용할 경우 발생하는 심각한 오버드로우로 인해 드로우 콜이 5,000회인 일반 Mesh 방식보다 InstancedMesh 방식의 FPS가 오히려 더 낮게 측정되는 모순적인 병목 현상이 실증적으로 보고되었습니다[6, 12, 13]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/대규모 웹 그래픽스 프로젝트.md]] +- Raw Source: 00_Raw/2026-04-20/대규모 웹 그래픽스 프로젝트.md --- diff --git a/01_Archive/2026-04-20/대규모 웹 애플리케이션의 조직 및 기술적 확장성 확보.md b/01_Archive/2026-04-20/대규모 웹 애플리케이션의 조직 및 기술적 확장성 확보.md index b9d955c6..4af092b5 100644 --- a/01_Archive/2026-04-20/대규모 웹 애플리케이션의 조직 및 기술적 확장성 확보.md +++ b/01_Archive/2026-04-20/대규모 웹 애플리케이션의 조직 및 기술적 확장성 확보.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-714552 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 대규모 웹 애플리케이션의 조직 및 기술적 확장성 확보" --- -# [[대규모 웹 애플리케이션의 조직 및 기술적 확장성 확보]] +# [[대규모 웹 애플리케이션의 조직 및 기술적 확장성 확보|대규모 웹 애플리케이션의 조직 및 기술적 확장성 확보]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 대규모 웹 애플리케이션에서 기술적, 조직적 확장성을 동시에 확보하기 위해서는 모놀리식 구조를 탈피하고 시스템을 독립적으로 관리 가능한 작은 단위로 분할해야 합니다 [1, 2]. 이를 위해 마이크로서비스 아키텍처(MSA) 및 마이크로 프론트엔드와 같은 기술적 접근 방식이 사용되며, 이는 기술적 결합도를 낮추고 유연한 시스템 확장을 가능하게 합니다 [1, 3]. 동시에 이렇게 분리된 모듈들을 소규모 전담 팀이 독립적으로 책임지고 개발, 테스트, 배포하게 함으로써, 병렬적 업무 수행을 통한 조직적 확장성과 혁신 속도를 높일 수 있습니다 [4, 5]. @@ -32,11 +32,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 대규모 웹 애플리케이 - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Microservices Architecture]], [[Micro Frontends]], [[Separation of Concerns]], [[API-First Architecture]], [[Cloud-Native Architecture]] -- **Projects/Contexts:** [[Netflix Cosmos Platform]], [[Spotify Squad Model]] +- **Related Topics:** [[마이크로서비스 아키텍처 (Microservices Architecture)|Microservices Architecture]], [[마이크로 프론트엔드 (Micro Frontends)|Micro Frontends]], [[_뇌와 팔다리의 분리_ - 관심사의 분리 (Separation of Concerns)|Separation of Concerns]], [[API-First Architecture|API-First Architecture]], Cloud-Native Architecture +- **Projects/Contexts:** [[넷플릭스 코스모스 플랫폼 (Netflix Cosmos Platform)|Netflix Cosmos Platform]], Spotify Squad Model - **Contradictions/Notes:** 조직 및 기술적 확장성을 위해 마이크로서비스 등을 도입하면 높은 유연성과 병렬성을 얻지만, 반대로 분산 시스템 구축으로 인한 컴포넌트 간 통신 메커니즘 구현의 어려움, 다중 서비스 배포 및 운영 관리의 복잡성 증가, 메모리 및 서버 인프라 유지 비용 상승 등의 새로운 문제와 트레이드오프가 필연적으로 발생합니다 [26-29]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/대규모 웹 애플리케이션의 조직 및 기술적 확장성 확보.md]] +- Raw Source: 00_Raw/2026-04-20/대규모 웹 애플리케이션의 조직 및 기술적 확장성 확보.md --- diff --git a/01_Archive/2026-04-20/대규모 인스턴스 렌더링 및 투명도 처리.md b/01_Archive/2026-04-20/대규모 인스턴스 렌더링 및 투명도 처리.md index 6a6cf1a6..6db6570e 100644 --- a/01_Archive/2026-04-20/대규모 인스턴스 렌더링 및 투명도 처리.md +++ b/01_Archive/2026-04-20/대규모 인스턴스 렌더링 및 투명도 처리.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-3EBBAF -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 대규모 인스턴스 렌더링 및 투명도 처리" --- -# [[대규모 인스턴스 렌더링 및 투명도 처리]] +# [[대규모 인스턴스 렌더링 및 투명도 처리|대규모 인스턴스 렌더링 및 투명도 처리]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 대규모 인스턴스 렌더링(InstancedMesh)은 동일한 기하학적 구조와 재질을 가진 수많은 객체를 단일 드로우 콜로 처리하여 CPU 병목을 줄이는 렌더링 최적화 기술이다[1, 2]. 하지만 인스턴스 간의 자동 정렬 기능이 없어 투명도 처리를 위한 알파 블렌딩(Alpha Blending) 시 치명적인 시각적 오류를 유발할 수 있다[3]. 이를 해결하기 위해 매 프레임 수동으로 객체를 정렬하면 막대한 CPU 오버헤드가 발생하므로, 대규모 투명 객체 렌더링 시에는 성능과 품질 사이의 철저한 타협이 요구된다[3]. @@ -20,11 +20,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 대규모 인스턴스 렌더 - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[InstancedMesh]], [[Alpha Blending]], [[Overdraw]], [[Draw Call]], [[Frustum Culling]] -- **Projects/Contexts:** [[Three.js 대규모 렌더링 최적화 파이프라인]], [[BatchedMesh 및 InstancedMesh 성능 벤치마크]] +- **Related Topics:** [[InstancedMesh|InstancedMesh]], [[Alpha Blending|Alpha Blending]], [[Overdraw|Overdraw]], [[Draw Call|Draw Call]], [[Frustum Culling|Frustum Culling]] +- **Projects/Contexts:** [[Three.js 대규모 렌더링 최적화 파이프라인|Three.js 대규모 렌더링 최적화 파이프라인]], [[BatchedMesh 및 InstancedMesh 성능 벤치마크|BatchedMesh 및 InstancedMesh 성능 벤치마크]] - **Contradictions/Notes:** CPU의 드로우 콜 오버헤드를 줄이기 위해 InstancedMesh를 도입하지만, 투명도 오류를 해결하기 위해 수동으로 카메라 거리 계산 및 인스턴스 정렬을 시도할 경우 도리어 막대한 CPU 병목을 유발하는 구조적 모순이 발생한다[3]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/대규모 인스턴스 렌더링 및 투명도 처리.md]] +- Raw Source: 00_Raw/2026-04-20/대규모 인스턴스 렌더링 및 투명도 처리.md --- diff --git a/01_Archive/2026-04-20/대규모 파티클 시스템 최적화.md b/01_Archive/2026-04-20/대규모 파티클 시스템 최적화.md index cd91254c..bb3a775c 100644 --- a/01_Archive/2026-04-20/대규모 파티클 시스템 최적화.md +++ b/01_Archive/2026-04-20/대규모 파티클 시스템 최적화.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-A0A931 -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 대규모 파티클 시스템 최적화" --- -# [[대규모 파티클 시스템 최적화]] +# [[대규모 파티클 시스템 최적화|대규모 파티클 시스템 최적화]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 대규모 파티클 시스템을 최적화하려면 CPU 연산 병목과 메모리 할당으로 인한 가비지 컬렉션(GC) 스파이크를 방지하는 것이 핵심입니다. 이를 위해 **WebGPU 연산 셰이더(Compute Shaders)**, **InstancedMesh**, **오브젝트 풀링(Object Pooling)**, 그리고 **데이터 지향 설계(ECS/SoA)**를 종합적으로 활용해야 합니다. @@ -28,12 +28,12 @@ github_commit: "[P-Reinforce] Continuous Worker - 대규모 파티클 시스템 - **정책 변화:** Graphics & Performance 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[WebGPU Compute Shaders]], [[InstancedMesh (드로우 콜 최적화)]], [[Object Pooling (오브젝트 풀링)]], [[Garbage Collection (GC) 최적화]], [[Data-Oriented Design (bitECS)]] -- **Projects/Contexts:** [[초대규모 파티클 및 엔티티 시뮬레이션 (React Three Fiber)]], [[고성능 실시간 상호작용 웹 게임 아키텍처]] +- **Related Topics:** [[WebGPU Compute Shaders|WebGPU Compute Shaders]], [[InstancedMesh (드로우 콜 최적화)|InstancedMesh (드로우 콜 최적화)]], [[Object Pooling (오브젝트 풀링)|Object Pooling (오브젝트 풀링)]], [[Garbage Collection (GC) 최적화|Garbage Collection (GC) 최적화]], Data-Oriented Design (bitECS) +- **Projects/Contexts:** 초대규모 파티클 및 엔티티 시뮬레이션 (React Three Fiber), 고성능 실시간 상호작용 웹 게임 아키텍처 - **Contradictions/Notes:** 연산 셰이더와 영구 GPU 버퍼를 사용해 수백만 개의 파티클을 제어하는 방식이 압도적으로 빠르지만, 이는 WebGPU 환경에서만 온전히 동작하며 WebGL 환경으로 폴백(Fallback)될 경우 이 수준의 동시성을 기대하기 어렵다는 제약이 있습니다. --- _Last updated: 2026-04-14_ -- Raw Source: [[00_Raw/2026-04-20/대규모 파티클 시스템 최적화.md]] +- Raw Source: 00_Raw/2026-04-20/대규모 파티클 시스템 최적화.md --- diff --git a/01_Archive/2026-04-20/대규모 프론트엔드 웹 프로젝트 폴더 구조화.md b/01_Archive/2026-04-20/대규모 프론트엔드 웹 프로젝트 폴더 구조화.md index c97f6368..0a4e5993 100644 --- a/01_Archive/2026-04-20/대규모 프론트엔드 웹 프로젝트 폴더 구조화.md +++ b/01_Archive/2026-04-20/대규모 프론트엔드 웹 프로젝트 폴더 구조화.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-71F406 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 대규모 프론트엔드 웹 프로젝트 폴더 구조화" --- -# [[대규모 프론트엔드 웹 프로젝트 폴더 구조화]] +# [[대규모 프론트엔드 웹 프로젝트 폴더 구조화|대규모 프론트엔드 웹 프로젝트 폴더 구조화]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 대규모 프론트엔드 웹 프로젝트의 폴더 구조화는 프로젝트의 규모와 복잡성이 증가함에 따라 관심사를 효과적으로 분리하여 유지보수성과 확장성을 높이는 설계 과정이다 [1, 2]. 초기에는 개발의 속도를 높일 수 있는 역할 중심의 폴더 구조가 주로 사용되지만, 프로젝트가 성장함에 따라 관련 파일을 하나의 단위로 묶어 관리하는 기능 중심의 구조(예: Feature-Sliced Design 아키텍처)로 진화하게 된다 [1, 3, 4]. 이는 데이터와 화면 간의 의존성을 줄이고 컴포넌트 및 기능의 결합도를 낮추어 코드 관리를 용이하게 하기 위한 필수적인 원칙이다 [5, 6]. @@ -33,11 +33,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 대규모 프론트엔드 웹 - **정책 변화:** Design & Experience 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[관심사의 분리 (Separation of Concerns)]], [[Feature-Sliced Design (FSD)]], [[마이크로 프론트엔드 (Micro Frontends)]] -- **Projects/Contexts:** [[항해 DEV LAB 미니 학술회]] (FSD와 프론트엔드 관심사 분리에 관한 시각과 발표 내용이 논의된 맥락 [16]), [[스포티파이 (Spotify)]] (자율적인 기능 단위 '스쿼드' 모델과 프론트엔드를 분리하는 마이크로 프론트엔드를 결합하여 대규모 웹 앱 개발의 확장성을 획기적으로 개선한 실제 기업 사례 [17, 18]) +- **Related Topics:** [[관심사의 분리 (Separation of Concerns)|관심사의 분리 (Separation of Concerns)]], [[Feature-Sliced Design (FSD)|Feature-Sliced Design (FSD)]], [[마이크로 프론트엔드 (Micro Frontends)|마이크로 프론트엔드 (Micro Frontends)]] +- **Projects/Contexts:** 항해 DEV LAB 미니 학술회 (FSD와 프론트엔드 관심사 분리에 관한 시각과 발표 내용이 논의된 맥락 [16]), 스포티파이 (Spotify) (자율적인 기능 단위 '스쿼드' 모델과 프론트엔드를 분리하는 마이크로 프론트엔드를 결합하여 대규모 웹 앱 개발의 확장성을 획기적으로 개선한 실제 기업 사례 [17, 18]) - **Contradictions/Notes:** 소스에 따르면 폴더 구조 설계에 있어서 절대적으로 "이것이 정답"이라고 할 수 있는 완벽한 구조는 존재하지 않는다. 프로젝트의 특성과 규모, 팀의 요구사항, 그리고 시기에 따라 기능 중심, 역할 중심, 혹은 도메인 중심 등으로 유연하게 폴더 구조를 진화시키고 균형을 맞추는 것이 핵심이라고 조언한다 [11, 19]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/대규모 프론트엔드 웹 프로젝트 폴더 구조화.md]] +- Raw Source: 00_Raw/2026-04-20/대규모 프론트엔드 웹 프로젝트 폴더 구조화.md --- diff --git a/01_Archive/2026-04-20/덕 타이핑 (Duck Typing).md b/01_Archive/2026-04-20/덕 타이핑 (Duck Typing).md index c41eb495..9bfd5a11 100644 --- a/01_Archive/2026-04-20/덕 타이핑 (Duck Typing).md +++ b/01_Archive/2026-04-20/덕 타이핑 (Duck Typing).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-EFC438 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 덕 타이핑 (Duck Typing)" --- -# [[덕 타이핑 (Duck Typing)]] +# [[덕 타이핑 (Duck Typing)|덕 타이핑 (Duck Typing)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 덕 타이핑(Duck Typing)은 TypeScript의 근본적인 타입 시스템인 '구조적 타이핑(Structural Typing)'을 일컫는 또 다른 용어로, "만약 어떤 것이 오리처럼 걷고 오리처럼 꽥꽥거리면 그것은 오리다"라는 격언에서 유래했습니다 [1, 2]. 이 시스템에서는 명시적인 타입의 이름이나 선언이 일치할 필요 없이, 객체의 실제 형태나 요구되는 속성(구조)을 최소한으로 포함하고 있다면 동일한 타입 혹은 호환되는 타입으로 간주합니다 [1, 3]. 이는 자바스크립트의 유연성을 살려주지만, 의도하지 않은 잉여 속성의 유입이나 의미적으로 다른 데이터를 구별하지 못하는 보안적 허점을 유발할 수 있어 TypeScript 내의 다양한 보완적 방어 기제와 함께 사용됩니다 [4, 5]. @@ -20,11 +20,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 덕 타이핑 (Duck Typing)" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[구조적 타이핑 (Structural Typing)]], [[명목적 타이핑 (Nominal Typing)]], [[과잉 속성 체크 (Excess Property Checking)]], [[satisfies 연산자]], [[브랜디드 타입 (Branded Types)]] -- **Projects/Contexts:** [[철벽 수비대: TypeScript 타입 시스템과 견고한 인터페이스 설계의 정수]] +- **Related Topics:** [[구조적 타이핑 (Structural Typing)|구조적 타이핑 (Structural Typing)]], [[명목적 타이핑 (Nominal Typing)|명목적 타이핑 (Nominal Typing)]], [[과잉 속성 체크 (Excess Property Checking)|과잉 속성 체크 (Excess Property Checking)]], [[satisfies 연산자|satisfies 연산자]], [[브랜디드 타입 (Branded Types)|브랜디드 타입 (Branded Types)]] +- **Projects/Contexts:** [[철벽 수비대_ TypeScript 타입 시스템과 견고한 인터페이스 설계의 정수|철벽 수비대: TypeScript 타입 시스템과 견고한 인터페이스 설계의 정수]] - **Contradictions/Notes:** 덕 타이핑은 자바스크립트 고유의 동적인 유연성을 잘 살려주지만, 구조만 같으면 모든 호환을 허용하므로 시스템 경계에서 오염된 데이터를 완벽히 걸러내지 못합니다. 따라서 견고한 인터페이스 설계를 위해서는 과잉 속성 체크나 satisfies 연산자, 브랜디드 타입 같은 "엄격한 수비 장치"들과의 결합이 필수적으로 요구됩니다 [4, 5, 8, 11]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/덕 타이핑 (Duck Typing).md]] +- Raw Source: 00_Raw/2026-04-20/덕 타이핑 (Duck Typing).md --- diff --git a/01_Archive/2026-04-20/덕 타이핑(Duck Typing).md b/01_Archive/2026-04-20/덕 타이핑(Duck Typing).md index 26028569..7b757b54 100644 --- a/01_Archive/2026-04-20/덕 타이핑(Duck Typing).md +++ b/01_Archive/2026-04-20/덕 타이핑(Duck Typing).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-5164C3 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 덕 타이핑(Duck Typing)" --- -# [[덕 타이핑(Duck Typing)]] +# [[덕 타이핑(Duck Typing)|덕 타이핑(Duck Typing)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 덕 타이핑(Duck Typing)은 객체의 실제 형태나 구조에 기반하여 타입을 결정하는 방식을 의미합니다 [1-3]. "만약 어떤 것이 오리처럼 걷고 오리처럼 갉갉거리면 그것은 오리다"라는 개념에 바탕을 둡니다 [1, 3]. 타입스크립트와 자바스크립트의 핵심적인 타입 시스템 특징으로, 명시적인 타입 이름의 선언 없이도 멤버(속성과 메서드)의 형태가 일치하면 호환성을 인정하는 구조적 타이핑(Structural Typing)과 동일한 의미로 불립니다 [1-3]. @@ -22,11 +22,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 덕 타이핑(Duck Typing)" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[구조적 타이핑(Structural Typing)]], [[명목적 타이핑(Nominal Typing)]], [[오파크 타입(Opaque Types)]] -- **Projects/Contexts:** [[타입스크립트(TypeScript) 타입 시스템 및 호환성 평가]] +- **Related Topics:** [[구조적 타이핑(Structural Typing)|구조적 타이핑(Structural Typing)]], [[명목적 타이핑(Nominal Typing)|명목적 타이핑(Nominal Typing)]], 오파크 타입(Opaque Types) +- **Projects/Contexts:** 타입스크립트(TypeScript) 타입 시스템 및 호환성 평가 - **Contradictions/Notes:** 덕 타이핑은 높은 코드 유연성을 제공하지만, 그로 인해 구조가 같은 다른 의미의 데이터를 원천적으로 구별하기 어렵다는 단점이 있습니다. 따라서 이 문제를 해결하기 위해 오파크 타입(Opaque Types) 등의 별도 기법이 요구됩니다 [4]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/덕 타이핑(Duck Typing).md]] +- Raw Source: 00_Raw/2026-04-20/덕 타이핑(Duck Typing).md --- diff --git a/01_Archive/2026-04-20/데브섹옵스 (DevSecOps) 환경에서의 지속적인 보안 검사.md b/01_Archive/2026-04-20/데브섹옵스 (DevSecOps) 환경에서의 지속적인 보안 검사.md index 9296bb9e..1c86024c 100644 --- a/01_Archive/2026-04-20/데브섹옵스 (DevSecOps) 환경에서의 지속적인 보안 검사.md +++ b/01_Archive/2026-04-20/데브섹옵스 (DevSecOps) 환경에서의 지속적인 보안 검사.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-DF816E -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 데브섹옵스 (DevSecOps) 환경에서의 지속적인 보안 검사" --- -# [[데브섹옵스 (DevSecOps) 환경에서의 지속적인 보안 검사]] +# [[데브섹옵스 (DevSecOps) 환경에서의 지속적인 보안 검사|데브섹옵스 (DevSecOps) 환경에서의 지속적인 보안 검사]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 데브섹옵스(DevSecOps) 환경에서의 지속적인 보안 검사는 소프트웨어 개발 수명 주기(SDLC)의 모든 단계에 보안을 내재화하여 실시간으로 취약점을 식별하고 해결하는 과정을 의미합니다 [1, 2]. 이는 CI/CD 파이프라인이나 IDE에 정적 애플리케이션 보안 테스트(SAST), 소프트웨어 구성 분석(SCA) 등 자동화된 도구를 통합함으로써 코드가 작성되거나 풀 리퀘스트(PR)가 생성될 때 즉각적인 피드백을 제공합니다 [3-5]. 결과적으로 개발 초기 단계부터 보안 문제를 차단하는 '시프트 레프트(Shift-Left)' 전략을 통해 개발 속도를 늦추지 않으면서도 높은 보안 품질을 유지하게 합니다 [5, 6]. @@ -33,11 +33,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 데브섹옵스 (DevSecOps) - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[SAST (Static Application Security Testing)]], [[시프트 레프트 (Shift-Left)]], [[CI/CD 파이프라인]], [[하이브리드 코드 리뷰]], [[오픈소스 컴포지션 분석 (SCA)]] -- **Projects/Contexts:** [[GitHub Code Security 워크플로우]], [[Snyk의 개발자 우선(Developer-First) 보안 통합]], [[SonarQube의 파이프라인 품질 게이트]] +- **Related Topics:** [[SAST (Static Application Security Testing)|SAST (Static Application Security Testing)]], [[시프트 레프트 (Shift-Left)|시프트 레프트 (Shift-Left)]], [[CI_CD 파이프라인|CI/CD 파이프라인]], [[하이브리드 코드 리뷰|하이브리드 코드 리뷰]], 오픈소스 컴포지션 분석 (SCA) +- **Projects/Contexts:** GitHub Code Security 워크플로우, Snyk의 개발자 우선(Developer-First) 보안 통합, SonarQube의 파이프라인 품질 게이트 - **Contradictions/Notes:** 자동화된 정적 애플리케이션 보안 테스트(SAST)는 코드베이스 전체에 걸쳐 알려진 보안 결함을 빠르고 일관되게 감지하는 데 탁월하지만 [12], 코드의 기저에 깔린 비즈니스 로직을 이해하지 못하는 한계(Context Blindness)가 있습니다 [13]. 여러 연구들은 특정 자동화 도구 단일로는 실제 취약점의 약 22%를 놓치거나 높은 오탐지율(False Positives)을 기록할 수 있음을 지적하며, 효과적인 보안 보장을 위해 인간 리뷰어의 맥락 판단을 결합하는 '하이브리드 리뷰'의 당위성을 주장합니다 [28, 29]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/데브섹옵스 (DevSecOps) 환경에서의 지속적인 보안 검사.md]] +- Raw Source: 00_Raw/2026-04-20/데브섹옵스 (DevSecOps) 환경에서의 지속적인 보안 검사.md --- diff --git a/01_Archive/2026-04-20/데이터 거버넌스 (Data Governance).md b/01_Archive/2026-04-20/데이터 거버넌스 (Data Governance).md index 21bb228f..adbeebdc 100644 --- a/01_Archive/2026-04-20/데이터 거버넌스 (Data Governance).md +++ b/01_Archive/2026-04-20/데이터 거버넌스 (Data Governance).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-1F9ACB -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 데이터 거버넌스 (Data Governance)" --- -# [[데이터 거버넌스 (Data Governance)]] +# [[데이터 거버넌스 (Data Governance)|데이터 거버넌스 (Data Governance)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 데이터 거버넌스(Data Governance)는 확장 가능한 데이터 아키텍처 내에서 데이터 자산을 관리하기 위한 정책 및 프로세스의 프레임워크입니다 [1]. 이 관행은 데이터를 하나의 제품으로 취급하여 규칙, 소유권, 그리고 명확한 카탈로그를 요구합니다 [1]. 강력한 데이터 거버넌스를 구축하지 않으면 조직은 규정 준수 위반, 신뢰할 수 없는 데이터에 기반한 잘못된 의사 결정, 엔지니어링 노력의 중복과 같은 중대한 위험에 직면하게 됩니다 [1]. @@ -27,11 +27,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 데이터 거버넌스 (Data G - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[메타데이터 관리 (Metadata Management)]], [[데이터 리니지 (Data Lineage)]], [[데이터 수명 주기 관리 (Data Lifecycle Management)]] -- **Projects/Contexts:** [[확장 가능한 데이터 시스템을 구축하기 위한 데이터 엔지니어링 모범 사례]] +- **Related Topics:** 메타데이터 관리 (Metadata Management), 데이터 리니지 (Data Lineage), 데이터 수명 주기 관리 (Data Lifecycle Management) +- **Projects/Contexts:** 확장 가능한 데이터 시스템을 구축하기 위한 데이터 엔지니어링 모범 사례 - **Contradictions/Notes:** 소스 X는 이를 주장하지만, 소스 Y는 반대합니다와 같은 의견 대립이나 모순점은 소스에 관련 정보가 부족합니다. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/데이터 거버넌스 (Data Governance).md]] +- Raw Source: 00_Raw/2026-04-20/데이터 거버넌스 (Data Governance).md --- diff --git a/01_Archive/2026-04-20/데이터 지향 설계 (Data-Oriented Design).md b/01_Archive/2026-04-20/데이터 지향 설계 (Data-Oriented Design).md index 801de48b..d47be7fd 100644 --- a/01_Archive/2026-04-20/데이터 지향 설계 (Data-Oriented Design).md +++ b/01_Archive/2026-04-20/데이터 지향 설계 (Data-Oriented Design).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-D9E964 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 데이터 지향 설계 (Data-Oriented Design)" --- -# [[데이터 지향 설계 (Data-Oriented Design)]] +# [[데이터 지향 설계 (Data-Oriented Design)|데이터 지향 설계 (Data-Oriented Design)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - 데이터 지향 설계 (Data- ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/데이터 지향 설계 (Data-Oriented Design).md]] +- Raw Source: 00_Raw/2026-04-20/데이터 지향 설계 (Data-Oriented Design).md --- diff --git a/01_Archive/2026-04-20/도달 가능성 분석 (Reachability Analysis).md b/01_Archive/2026-04-20/도달 가능성 분석 (Reachability Analysis).md index e1ea3479..bfc33dc0 100644 --- a/01_Archive/2026-04-20/도달 가능성 분석 (Reachability Analysis).md +++ b/01_Archive/2026-04-20/도달 가능성 분석 (Reachability Analysis).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-03E8DE -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 도달 가능성 분석 (Reachability Analysis)" --- -# [[도달 가능성 분석 (Reachability Analysis)]] +# [[도달 가능성 분석 (Reachability Analysis)|도달 가능성 분석 (Reachability Analysis)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 도달 가능성 분석(Reachability Analysis)은 소스 코드 내의 데이터 흐름이나 호출 그래프(Call Graph)를 추적하여 특정 취약점이 실제 프로덕션 환경이나 실행 경로에서 도달 가능한지를 판별하는 보안 분석 기법입니다 [1, 2]. 이를 통해 신뢰할 수 없는 오염된 데이터가 민감한 싱크(sink)나 취약한 함수에 도달할 수 있는지 검증합니다 [3]. 결과적으로 실제 실행되지 않는 경로의 취약점을 필터링하여 경고 피로(alert fatigue)를 줄이고 보안 취약점 해결의 우선순위를 명확히 지정하는 데 핵심적인 역할을 합니다 [2, 4]. @@ -26,11 +26,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 도달 가능성 분석 (Reach - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[정적 애플리케이션 보안 테스트 (SAST)]], [[소프트웨어 구성 분석 (SCA)]], [[데이터 흐름 분석 (Data Flow Analysis)]], [[호출 그래프 (Call Graph)]] -- **Projects/Contexts:** [[Endor Labs]], [[Veracode]], [[Corgea]], [[Qwiet AI]] +- **Related Topics:** [[정적 애플리케이션 보안 테스트 (SAST)|정적 애플리케이션 보안 테스트 (SAST)]], [[소프트웨어 구성 분석(SCA)|소프트웨어 구성 분석 (SCA)]], 데이터 흐름 분석 (Data Flow Analysis), 호출 그래프 (Call Graph) +- **Projects/Contexts:** Endor Labs, Veracode, [[Corgea|Corgea]], Qwiet AI - **Contradictions/Notes:** 단순 규칙이나 패턴 기반의 전통적인 정적 분석 도구는 문맥 파악의 한계로 인해 오탐을 다수 발생시킬 수 있으나, 도달 가능성 분석이 결합된 최신 분석 도구들은 도달 불가능한 경로의 노이즈를 필터링하여 실제 문제 해결 효율을 크게 높여줍니다 [4, 7]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/도달 가능성 분석 (Reachability Analysis).md]] +- Raw Source: 00_Raw/2026-04-20/도달 가능성 분석 (Reachability Analysis).md --- diff --git a/01_Archive/2026-04-20/도메인 기반 설계 (DDD) 및 데이터 오염 방지.md b/01_Archive/2026-04-20/도메인 기반 설계 (DDD) 및 데이터 오염 방지.md index 6488795f..cdff4dd5 100644 --- a/01_Archive/2026-04-20/도메인 기반 설계 (DDD) 및 데이터 오염 방지.md +++ b/01_Archive/2026-04-20/도메인 기반 설계 (DDD) 및 데이터 오염 방지.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-9B5D9F -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 도메인 기반 설계 (DDD) 및 데이터 오염 방지" --- -# [[도메인 기반 설계 (DDD) 및 데이터 오염 방지]] +# [[도메인 기반 설계 (DDD) 및 데이터 오염 방지|도메인 기반 설계 (DDD) 및 데이터 오염 방지]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 도메인 기반 설계(DDD)에서 데이터 오염 방지는 TypeScript의 구조적 타이핑 한계로 인해 발생하는 '기본 타입에의 집착(Primitive Obsession)' 문제를 해결하기 위한 필수적인 방어 기제입니다 [1]. 브랜디드 타입(Branded Types) 또는 불투명 타입(Opaque Types)을 활용해 구조가 동일한 기본 타입 데이터에 고유한 가상의 식별자를 부여하여 의미가 다른 데이터를 엄격하게 분리합니다 [1]. 이를 통해 오직 사전에 검증된 안전한 데이터만이 시스템의 핵심 비즈니스 로직으로 진입하도록 강제하여 데이터가 섞이거나 오염되는 것을 원천 차단합니다 [2]. @@ -30,11 +30,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 도메인 기반 설계 (DDD) - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[브랜디드 타입 (Branded Types)]], [[기본 타입에의 집착 (Primitive Obsession)]], [[구조적 타이핑 (Structural Typing)]], [[Parse, Don't Validate]] -- **Projects/Contexts:** [[UserId와 OrderId의 엄격한 분리 모델링]], [[Zod 라이브러리를 활용한 런타임 데이터 파싱]] +- **Related Topics:** [[브랜디드 타입 (Branded Types)|브랜디드 타입 (Branded Types)]], [[기본 타입에의 집착 (Primitive Obsession)|기본 타입에의 집착 (Primitive Obsession)]], [[구조적 타이핑 (Structural Typing)|구조적 타이핑 (Structural Typing)]], [[Parse dont validate|Parse, Don't Validate]] +- **Projects/Contexts:** UserId와 OrderId의 엄격한 분리 모델링, Zod 라이브러리를 활용한 런타임 데이터 파싱 - **Contradictions/Notes:** TypeScript 자체는 형태를 기준으로 하는 구조적 타이핑 언어이지만, 도메인 주도 설계에서 데이터 오염을 완벽히 차단하기 위해서는 오히려 명목적 타이핑(Nominal Typing)의 특성을 브랜디드 타입이라는 우회적 방법론으로 모방하여 사용해야 합니다 [1, 4]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/도메인 기반 설계 (DDD) 및 데이터 오염 방지.md]] +- Raw Source: 00_Raw/2026-04-20/도메인 기반 설계 (DDD) 및 데이터 오염 방지.md --- diff --git a/01_Archive/2026-04-20/도메인 기반 설계 (DDD).md b/01_Archive/2026-04-20/도메인 기반 설계 (DDD).md index 364f8090..8ab2159c 100644 --- a/01_Archive/2026-04-20/도메인 기반 설계 (DDD).md +++ b/01_Archive/2026-04-20/도메인 기반 설계 (DDD).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-F2DA4C -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 도메인 기반 설계 (DDD)" --- -# [[도메인 기반 설계 (DDD)]] +# [[도메인 기반 설계 (DDD)|도메인 기반 설계 (DDD)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 도메인 기반 설계(DDD)는 비즈니스 도메인에 맞춰 소프트웨어를 모델링하는 설계 접근법으로, TypeScript의 타입 시스템에서는 의미적으로 다른 데이터를 엄격하게 분리하여 시스템의 무결성을 보호하는 데 활용됩니다 [1]. 특히 브랜디드 타입(Branded Types)과 불변성(Immutability)을 통해 도메인 모델 내에서 데이터가 무분별하게 섞이거나 오염되는 것을 방지하여 예측 가능성을 극대화합니다 [1-3]. @@ -23,11 +23,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 도메인 기반 설계 (DDD)" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[브랜디드 타입 (Branded Types)]], [[불변성 (Immutability)]], [[구조적 타이핑 (Structural Typing)]] -- **Projects/Contexts:** [[TypeScript 타입 시스템을 활용한 내부 로직 보호 및 데이터 검증]] +- **Related Topics:** [[브랜디드 타입 (Branded Types)|브랜디드 타입 (Branded Types)]], [[불변성 (Immutability)|불변성 (Immutability)]], [[구조적 타이핑 (Structural Typing)|구조적 타이핑 (Structural Typing)]] +- **Projects/Contexts:** [[TypeScript 타입 시스템을 활용한 내부 로직 보호 및 데이터 검증|TypeScript 타입 시스템을 활용한 내부 로직 보호 및 데이터 검증]] - **Contradictions/Notes:** 예외(Exception) 처리에 대해, 도메인 비즈니스 흐름을 단순히 제어할 목적(if-else를 대체하는 용도)으로 예외를 남용하는 것은 지양해야 하지만, 예기치 않은 상황이나 검증 실패 시 도메인 에러를 발생시키고 이를 전역 미들웨어에서 처리하도록 위임하는 방어적 프로그래밍 패턴은 적절한 수비 전략으로 권장됩니다 [6, 7]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/도메인 기반 설계 (DDD).md]] +- Raw Source: 00_Raw/2026-04-20/도메인 기반 설계 (DDD).md --- diff --git a/01_Archive/2026-04-20/도메인 기반 설계(DDD).md b/01_Archive/2026-04-20/도메인 기반 설계(DDD).md index 38c04728..4e86ca86 100644 --- a/01_Archive/2026-04-20/도메인 기반 설계(DDD).md +++ b/01_Archive/2026-04-20/도메인 기반 설계(DDD).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-9C55A9 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 도메인 기반 설계(DDD)" --- -# [[도메인 기반 설계(DDD)]] +# [[도메인 기반 설계(DDD)|도메인 기반 설계(DDD)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 도메인 기반 설계(DDD)에 대한 전반적인 정의는 소스에 관련 정보가 부족합니다. 제공된 자료에 따르면, 도메인 기반 설계(DDD)는 브랜디드 타입(Branded Types)과 결합하여 의미적으로 다른 데이터를 엄격히 분리하고 검증된 데이터만 시스템 내부로 진입하도록 강제하는 데 유용하게 쓰이는 설계 접근법입니다 [1]. @@ -24,11 +24,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 도메인 기반 설계(DDD)" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[브랜디드 타입(Branded Types)]] +- **Related Topics:** [[브랜디드 타입(Branded Types)|브랜디드 타입(Branded Types)]] - **Projects/Contexts:** 소스에 관련 정보가 부족합니다. - **Contradictions/Notes:** 소스에 관련 정보가 부족합니다. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/도메인 기반 설계(DDD).md]] +- Raw Source: 00_Raw/2026-04-20/도메인 기반 설계(DDD).md --- diff --git a/01_Archive/2026-04-20/도메인 기반 설계(DDD)의 데이터 검증.md b/01_Archive/2026-04-20/도메인 기반 설계(DDD)의 데이터 검증.md index 8e4754bf..f41341d1 100644 --- a/01_Archive/2026-04-20/도메인 기반 설계(DDD)의 데이터 검증.md +++ b/01_Archive/2026-04-20/도메인 기반 설계(DDD)의 데이터 검증.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-DDDB06 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 도메인 기반 설계(DDD)의 데이터 검증" --- -# [[도메인 기반 설계(DDD)의 데이터 검증]] +# [[도메인 기반 설계(DDD)의 데이터 검증|도메인 기반 설계(DDD)의 데이터 검증]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 도메인 기반 설계(DDD)에서 데이터 검증은 단순한 유효성 확인을 넘어, 신뢰할 수 있는 데이터를 도메인 객체로 변환하여 시스템 내부를 보호하는 아키텍처적 과정입니다 [1, 2]. 주로 브랜디드 타입(Branded Types)과 "검증하지 말고 파싱하라(Parse, Don't Validate)"라는 철학을 결합하여, 시스템 경계에서 불확실한 데이터를 명확하게 타입화된 구체적 객체로 변환합니다 [1-4]. 이를 통해 잘못된 데이터의 유입을 원천 차단하고 예측 가능한 비즈니스 로직을 구현합니다 [4, 5]. @@ -22,11 +22,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 도메인 기반 설계(DDD) - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[브랜디드 타입(Branded Types)]], [[Parse, Don't Validate]] -- **Projects/Contexts:** [[Zod를 활용한 런타임 데이터 유효성 검사]], [[TypeScript 구조적 타이핑의 한계 극복]] +- **Related Topics:** [[브랜디드 타입(Branded Types)|브랜디드 타입(Branded Types)]], [[Parse dont validate|Parse, Don't Validate]] +- **Projects/Contexts:** Zod를 활용한 런타임 데이터 유효성 검사, TypeScript 구조적 타이핑의 한계 극복 - **Contradictions/Notes:** 도메인 기반 설계(DDD)의 데이터 검증 방식에 대한 상반된 주장이나 모순점에 대해서는 소스에 관련 정보가 부족합니다. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/도메인 기반 설계(DDD)의 데이터 검증.md]] +- Raw Source: 00_Raw/2026-04-20/도메인 기반 설계(DDD)의 데이터 검증.md --- diff --git a/01_Archive/2026-04-20/도메인 기반 설계(DDD)의 식별자 분리.md b/01_Archive/2026-04-20/도메인 기반 설계(DDD)의 식별자 분리.md index 7d9a6870..f2f28f37 100644 --- a/01_Archive/2026-04-20/도메인 기반 설계(DDD)의 식별자 분리.md +++ b/01_Archive/2026-04-20/도메인 기반 설계(DDD)의 식별자 분리.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-5D91AB -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 도메인 기반 설계(DDD)의 식별자 분리" --- -# [[도메인 기반 설계(DDD)의 식별자 분리]] +# [[도메인 기반 설계(DDD)의 식별자 분리|도메인 기반 설계(DDD)의 식별자 분리]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -27,11 +27,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 도메인 기반 설계(DDD) - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[브랜디드 타입(Branded Types)]], [[오파크 타입(Opaque Types)]], [[기본 타입에의 집착(Primitive Obsession)]], [[구조적 타이핑(Structural Typing)]] -- **Projects/Contexts:** [[TypeScript의 안전한 도메인 모델링]], [[데이터 오염 방지 및 무결성 보호 체계]] +- **Related Topics:** [[브랜디드 타입(Branded Types)|브랜디드 타입(Branded Types)]], 오파크 타입(Opaque Types), [[기본 타입에의 집착(Primitive Obsession)|기본 타입에의 집착(Primitive Obsession)]], [[구조적 타이핑(Structural Typing)|구조적 타이핑(Structural Typing)]] +- **Projects/Contexts:** TypeScript의 안전한 도메인 모델링, 데이터 오염 방지 및 무결성 보호 체계 - **Contradictions/Notes:** 소스에 따르면 TypeScript의 구조적 타이핑은 매우 편리하지만 식별자처럼 고유성이 필요한 데이터를 구별하지 못하는 허점이 존재합니다. 이를 명목적 타이핑(Nominal Typing)과 유사한 효과를 내는 브랜디드 타입으로 보완해야만 도메인 식별자를 엄격히 분리할 수 있다는 점이 일관되게 강조되고 있습니다 [1, 5, 8]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/도메인 기반 설계(DDD)의 식별자 분리.md]] +- Raw Source: 00_Raw/2026-04-20/도메인 기반 설계(DDD)의 식별자 분리.md --- diff --git a/01_Archive/2026-04-20/도메인 주도 설계 (DDD).md b/01_Archive/2026-04-20/도메인 주도 설계 (DDD).md index dcb307f5..b1425138 100644 --- a/01_Archive/2026-04-20/도메인 주도 설계 (DDD).md +++ b/01_Archive/2026-04-20/도메인 주도 설계 (DDD).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-ADBB0E -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 도메인 주도 설계 (DDD)" --- -# [[도메인 주도 설계 (DDD)]] +# [[도메인 주도 설계 (DDD)|도메인 주도 설계 (DDD)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 도메인 주도 설계(DDD)는 비즈니스 도메인에 대한 깊은 이해를 중심으로 소프트웨어 개발 프로세스를 진행하는 설계 접근법입니다 [1]. 이 방식은 핵심 비즈니스 로직(뇌)을 데이터베이스나 UI 프레임워크와 같은 인프라스트럭처 관심사(팔다리)로부터 철저히 격리하여 깨끗하고 테스트 가능한 도메인 모델을 구축하는 것을 목표로 합니다 [2]. 결과적으로 DDD는 전통적인 기술 중심의 계층화를 넘어 '비즈니스 역량 중심'의 수직적 분리로 관심사의 분리(SoC) 원칙의 지평을 크게 넓혔습니다 [3]. @@ -24,11 +24,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 도메인 주도 설계 (DDD)" - **정책 변화:** Design & Experience 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[바운디드 컨텍스트 (Bounded Context)]], [[유비쿼터스 언어 (Ubiquitous Language)]], [[관심사의 분리 (Separation of Concerns)]], [[애그리거트 (Aggregates)]] -- **Projects/Contexts:** [[마이크로서비스 아키텍처 (MSA)]], [[복잡한 비즈니스 도메인 (금융, 헬스케어, 이커머스 등)]] +- **Related Topics:** [[바운디드 컨텍스트 (Bounded Context)|바운디드 컨텍스트 (Bounded Context)]], [[유비쿼터스 언어 (Ubiquitous Language)|유비쿼터스 언어 (Ubiquitous Language)]], [[관심사의 분리 (Separation of Concerns)|관심사의 분리 (Separation of Concerns)]], [[애그리거트 (Aggregates)|애그리거트 (Aggregates)]] +- **Projects/Contexts:** [[마이크로서비스 아키텍처 (MSA)|마이크로서비스 아키텍처 (MSA)]], [[복잡한 비즈니스 도메인 (금융, 헬스케어, 이커머스 등)|복잡한 비즈니스 도메인 (금융, 헬스케어, 이커머스 등)]] - **Contradictions/Notes:** 소스 내용 간의 모순점은 발견되지 않았습니다. 다만, 도메인 주도 설계(DDD)는 비즈니스와 강하게 결합된 명확한 모델을 도출하는 데 큰 장점이 있지만, 도메인 전문가와의 긴밀한 협업과 깊은 모델링 분석 시간이 필요하여 구현 복잡도와 리소스 요구량이 높다는 특징이 있습니다 [5]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/도메인 주도 설계 (DDD).md]] +- Raw Source: 00_Raw/2026-04-20/도메인 주도 설계 (DDD).md --- diff --git a/01_Archive/2026-04-20/도메인 주도 설계 (Domain-Driven Design DDD).md b/01_Archive/2026-04-20/도메인 주도 설계 (Domain-Driven Design DDD).md index 17be026d..af802baa 100644 --- a/01_Archive/2026-04-20/도메인 주도 설계 (Domain-Driven Design DDD).md +++ b/01_Archive/2026-04-20/도메인 주도 설계 (Domain-Driven Design DDD).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-B7F6A8 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 도메인 주도 설계 (Domain-Driven Design DDD)" --- -# [[도메인 주도 설계 (Domain-Driven Design DDD)]] +# [[도메인 주도 설계 (Domain-Driven Design DDD)|도메인 주도 설계 (Domain-Driven Design DDD)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 도메인 주도 설계(DDD)는 비즈니스 도메인에 대한 깊은 이해를 중심으로 소프트웨어 개발 프로세스를 구성하는 설계 접근 방식입니다 [1]. 기술 팀과 도메인 전문가 간의 긴밀한 협력을 바탕으로 현실 세계의 비즈니스 프로세스를 정확하게 반영하는 소프트웨어 모델을 생성하는 것을 목표로 합니다 [1]. 이를 통해 시스템의 복잡성을 해결하고 개발자와 비즈니스 이해관계자 간의 의사소통 격차를 해소하여, 결과적으로 소프트웨어가 올바른 문제를 해결할 수 있도록 보장합니다 [1]. @@ -30,11 +30,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 도메인 주도 설계 (Domai - **정책 변화:** AI 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[유비쿼터스 언어(Ubiquitous Language)]], [[제한된 컨텍스트(Bounded Contexts)]], [[애그리게잇(Aggregates)]], [[관심사의 분리(Separation of Concerns)]] -- **Projects/Contexts:** [[복잡한 비즈니스 도메인(금융, 의료, 이커머스 등)을 다루는 대규모 시스템 개발 프로젝트]] +- **Related Topics:** [[유비쿼터스 언어 (Ubiquitous Language)|유비쿼터스 언어(Ubiquitous Language)]], 제한된 컨텍스트(Bounded Contexts), 애그리게잇(Aggregates), [[관심사의 분리(Separation of Concerns)|관심사의 분리(Separation of Concerns)]] +- **Projects/Contexts:** 복잡한 비즈니스 도메인(금융, 의료, 이커머스 등)을 다루는 대규모 시스템 개발 프로젝트 - **Contradictions/Notes:** 소스 내에서 상충하는 주장은 발견되지 않으나, DDD는 비즈니스 구조와의 강력한 일치와 명확한 도메인 모델을 제공하는 큰 장점이 있는 반면, 도입 시 도메인 전문가와의 심도 있는 협업 모델링이 필요하여 중간에서 높음(Medium-High) 수준의 복잡성과 리소스가 요구된다는 점이 주의사항으로 지적됩니다 [6]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/도메인 주도 설계 (Domain-Driven Design, DDD).md]] +- Raw Source: 00_Raw/2026-04-20/도메인 주도 설계 (Domain-Driven Design, DDD).md --- diff --git a/01_Archive/2026-04-20/도메인 주도 설계 (Domain-Driven Design, DDD).md b/01_Archive/2026-04-20/도메인 주도 설계 (Domain-Driven Design, DDD).md index 37992239..41153418 100644 --- a/01_Archive/2026-04-20/도메인 주도 설계 (Domain-Driven Design, DDD).md +++ b/01_Archive/2026-04-20/도메인 주도 설계 (Domain-Driven Design, DDD).md @@ -1,4 +1,4 @@ -# [[도메인 주도 설계 (Domain-Driven Design, DDD)]] +# [[도메인 주도 설계 (Domain-Driven Design, DDD)|도메인 주도 설계 (Domain-Driven Design, DDD)]] ## 📌 Brief Summary 도메인 주도 설계(DDD)는 비즈니스 도메인에 대한 깊은 이해를 중심으로 소프트웨어 개발 프로세스를 구성하는 설계 접근 방식입니다 [1]. 기술 팀과 도메인 전문가 간의 긴밀한 협력을 바탕으로 현실 세계의 비즈니스 프로세스를 정확하게 반영하는 소프트웨어 모델을 생성하는 것을 목표로 합니다 [1]. 이를 통해 시스템의 복잡성을 해결하고 개발자와 비즈니스 이해관계자 간의 의사소통 격차를 해소하여, 결과적으로 소프트웨어가 올바른 문제를 해결할 수 있도록 보장합니다 [1]. @@ -17,8 +17,8 @@ DDD는 깊은 도메인 모델링과 이해관계자의 지속적인 협업이 필수적이므로 초기 구현 복잡도와 리소스 요구 사항(분석 시간, 도메인 전문가 참여 등)이 상대적으로 높은 편입니다 [6]. 따라서 단순한 시스템보다는 금융, 의료, 이커머스와 같이 비즈니스 도메인이 매우 복잡한 엔터프라이즈 시스템 구축에 가장 이상적인 아키텍처 베스트 프랙티스입니다 [6]. ## 🔗 Knowledge Connections -- **Related Topics:** [[유비쿼터스 언어(Ubiquitous Language)]], [[제한된 컨텍스트(Bounded Contexts)]], [[애그리게잇(Aggregates)]], [[관심사의 분리(Separation of Concerns)]] -- **Projects/Contexts:** [[복잡한 비즈니스 도메인(금융, 의료, 이커머스 등)을 다루는 대규모 시스템 개발 프로젝트]] +- **Related Topics:** [[유비쿼터스 언어 (Ubiquitous Language)|유비쿼터스 언어(Ubiquitous Language)]], 제한된 컨텍스트(Bounded Contexts), 애그리게잇(Aggregates), [[관심사의 분리(Separation of Concerns)|관심사의 분리(Separation of Concerns)]] +- **Projects/Contexts:** 복잡한 비즈니스 도메인(금융, 의료, 이커머스 등)을 다루는 대규모 시스템 개발 프로젝트 - **Contradictions/Notes:** 소스 내에서 상충하는 주장은 발견되지 않으나, DDD는 비즈니스 구조와의 강력한 일치와 명확한 도메인 모델을 제공하는 큰 장점이 있는 반면, 도입 시 도메인 전문가와의 심도 있는 협업 모델링이 필요하여 중간에서 높음(Medium-High) 수준의 복잡성과 리소스가 요구된다는 점이 주의사항으로 지적됩니다 [6]. --- diff --git a/01_Archive/2026-04-20/도메인 주도 설계(DDD).md b/01_Archive/2026-04-20/도메인 주도 설계(DDD).md index 52becd14..c5963b07 100644 --- a/01_Archive/2026-04-20/도메인 주도 설계(DDD).md +++ b/01_Archive/2026-04-20/도메인 주도 설계(DDD).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-4DC206 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 도메인 주도 설계(DDD)" --- -# [[도메인 주도 설계(DDD)]] +# [[도메인 주도 설계(DDD)|도메인 주도 설계(DDD)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 도메인 주도 설계(DDD)는 비즈니스 도메인에 대한 깊은 이해를 중심으로 소프트웨어 개발 프로세스를 구성하는 설계 방식입니다 [1]. 이 접근법은 복잡한 비즈니스 로직을 애플리케이션의 핵심에 두고, 개발팀과 비즈니스 이해관계자 간의 긴밀한 협력을 통해 현실 세계의 비즈니스 프로세스를 정확히 반영하는 모델을 생성합니다 [1]. 결과적으로 DDD는 기술 중심의 분리에서 벗어나 비즈니스 역량 중심의 관심사 분리를 가능하게 합니다 [2]. @@ -26,11 +26,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 도메인 주도 설계(DDD)" - **정책 변화:** Design & Experience 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[보편적 언어(Ubiquitous Language)]], [[제한된 문맥(Bounded Contexts)]], [[마이크로서비스 아키텍처(MSA)]], [[관심사의 분리(SoC)]] -- **Projects/Contexts:** [[이벤트 스토밍(Event Storming)]], [[복잡한 비즈니스 도메인(금융, 의료, 이커머스 등)]] +- **Related Topics:** [[보편적 언어 (Ubiquitous Language)|보편적 언어(Ubiquitous Language)]], 제한된 문맥(Bounded Contexts), [[마이크로서비스 아키텍처 (MSA)|마이크로서비스 아키텍처(MSA)]], [[관심사의 분리(SoC)|관심사의 분리(SoC)]] +- **Projects/Contexts:** 이벤트 스토밍(Event Storming), 복잡한 비즈니스 도메인(금융, 의료, 이커머스 등) - **Contradictions/Notes:** 도메인 주도 설계는 비즈니스 도메인을 명확하게 반영하고 강력한 기반을 제공하지만, 깊은 수준의 모델링과 조직적 협력이 필요하므로 구현 복잡성이 높고 상당한 리소스(도메인 전문가, 분석 시간 등)가 요구된다는 제약이 있습니다 [6]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/도메인 주도 설계(DDD).md]] +- Raw Source: 00_Raw/2026-04-20/도메인 주도 설계(DDD).md --- diff --git a/01_Archive/2026-04-20/도파민 보상 체계 (Dopaminergic Reward System).md b/01_Archive/2026-04-20/도파민 보상 체계 (Dopaminergic Reward System).md index 6511532f..a2fab083 100644 --- a/01_Archive/2026-04-20/도파민 보상 체계 (Dopaminergic Reward System).md +++ b/01_Archive/2026-04-20/도파민 보상 체계 (Dopaminergic Reward System).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-90ACEA -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 도파민 보상 체계 (Dopaminergic Reward System)" --- -# [[도파민 보상 체계 (Dopaminergic Reward System)]] +# [[도파민 보상 체계 (Dopaminergic Reward System)|도파민 보상 체계 (Dopaminergic Reward System)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - 도파민 보상 체계 (Dopam ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/도파민 보상 체계 (Dopaminergic Reward System).md]] +- Raw Source: 00_Raw/2026-04-20/도파민 보상 체계 (Dopaminergic Reward System).md --- diff --git a/01_Archive/2026-04-20/도파민 보상 체계.md b/01_Archive/2026-04-20/도파민 보상 체계.md index 342e0042..7365f3d6 100644 --- a/01_Archive/2026-04-20/도파민 보상 체계.md +++ b/01_Archive/2026-04-20/도파민 보상 체계.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-19D38E -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 도파민 보상 체계" --- -# [[도파민 보상 체계]] +# [[도파민 보상 체계|도파민 보상 체계]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - 도파민 보상 체계" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/도파민 보상 체계.md]] +- Raw Source: 00_Raw/2026-04-20/도파민 보상 체계.md --- diff --git a/01_Archive/2026-04-20/동기강화 상담(Motivational Interviewing).md b/01_Archive/2026-04-20/동기강화 상담(Motivational Interviewing).md index 6d2df2d7..15961611 100644 --- a/01_Archive/2026-04-20/동기강화 상담(Motivational Interviewing).md +++ b/01_Archive/2026-04-20/동기강화 상담(Motivational Interviewing).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-981A52 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 동기강화 상담(Motivational Interviewing)" --- -# [[동기강화 상담(Motivational Interviewing)]] +# [[동기강화 상담(Motivational Interviewing)|동기강화 상담(Motivational Interviewing)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - 동기강화 상담(Motivation ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/동기강화 상담(Motivational Interviewing).md]] +- Raw Source: 00_Raw/2026-04-20/동기강화 상담(Motivational Interviewing).md --- diff --git a/01_Archive/2026-04-20/동시성 및 점진적 마킹(Concurrent Incremental Marking).md b/01_Archive/2026-04-20/동시성 및 점진적 마킹(Concurrent Incremental Marking).md index 92809210..d9c19d10 100644 --- a/01_Archive/2026-04-20/동시성 및 점진적 마킹(Concurrent Incremental Marking).md +++ b/01_Archive/2026-04-20/동시성 및 점진적 마킹(Concurrent Incremental Marking).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-BDF67C -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 동시성 및 점진적 마킹(Concurrent Incremental Marking)" --- -# [[동시성 및 점진적 마킹(Concurrent Incremental Marking)]] +# [[동시성 및 점진적 마킹(Concurrent Incremental Marking)|동시성 및 점진적 마킹(Concurrent Incremental Marking)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 동시성 및 점진적 마킹은 가비지 컬렉션(GC) 수행 시 애플리케이션의 'Stop-The-World' 일시 정지 시간을 최소화하기 위해 고안된 고도화된 메모리 관리 기법이다 [1-3]. 동시성 마킹(Concurrent Marking)은 메인 스레드가 애플리케이션 코드를 실행하는 동안 백그라운드 도우미 스레드를 활용해 객체의 도달 가능성을 추적하는 방식이다 [4, 5]. 반면 점진적 마킹(Incremental Marking)은 전체 마킹 작업을 짧은 단위(예: 5~10ms)로 쪼개어 메인 스레드의 애플리케이션 실행과 교차로 수행하는 방식이다 [6, 7]. @@ -30,11 +30,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 동시성 및 점진적 마킹 - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[가비지 컬렉션(Garbage Collection)]], [[마크-스윕(Mark-Sweep)]], [[쓰기 장벽(Write Barrier)]], [[삼색 마킹(Tri-color Marking)]] -- **Projects/Contexts:** [[V8 자바스크립트 엔진(V8 JavaScript Engine)]], [[Orinoco 가비지 컬렉터]], [[IBM Eclipse OpenJ9]] +- **Related Topics:** [[가비지 컬렉션(Garbage Collection)|가비지 컬렉션(Garbage Collection)]], [[마크-스윕(Mark-Sweep)|마크-스윕(Mark-Sweep)]], [[쓰기 장벽(Write Barrier)|쓰기 장벽(Write Barrier)]], 삼색 마킹(Tri-color Marking) +- **Projects/Contexts:** V8 자바스크립트 엔진(V8 JavaScript Engine), [[Orinoco 가비지 컬렉터|Orinoco 가비지 컬렉터]], IBM Eclipse OpenJ9 - **Contradictions/Notes:** 점진적 마킹은 개별 일시 정지 시간은 짧게 분산시키지만 메인 스레드가 마킹에 소요하는 총합 시간은 오히려 약간 증가시킬 수 있는 반면, 동시성 마킹은 메인 스레드를 온전히 해방시키는 대신 백그라운드 스레드와의 동기화 비용(Overhead)이 추가로 발생한다는 차이점이 있다 [3, 5]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/동시성 및 점진적 마킹(Concurrent & Incremental Marking).md]] +- Raw Source: 00_Raw/2026-04-20/동시성 및 점진적 마킹(Concurrent & Incremental Marking).md --- diff --git a/01_Archive/2026-04-20/동시성 및 점진적 마킹(Concurrent & Incremental Marking).md b/01_Archive/2026-04-20/동시성 및 점진적 마킹(Concurrent & Incremental Marking).md index 1e3ad094..b8ce0235 100644 --- a/01_Archive/2026-04-20/동시성 및 점진적 마킹(Concurrent & Incremental Marking).md +++ b/01_Archive/2026-04-20/동시성 및 점진적 마킹(Concurrent & Incremental Marking).md @@ -1,4 +1,4 @@ -# [[동시성 및 점진적 마킹(Concurrent & Incremental Marking)]] +# [[동시성 및 점진적 마킹(Concurrent & Incremental Marking)|동시성 및 점진적 마킹(Concurrent & Incremental Marking)]] ## 📌 Brief Summary 동시성 및 점진적 마킹은 가비지 컬렉션(GC) 수행 시 애플리케이션의 'Stop-The-World' 일시 정지 시간을 최소화하기 위해 고안된 고도화된 메모리 관리 기법이다 [1-3]. 동시성 마킹(Concurrent Marking)은 메인 스레드가 애플리케이션 코드를 실행하는 동안 백그라운드 도우미 스레드를 활용해 객체의 도달 가능성을 추적하는 방식이다 [4, 5]. 반면 점진적 마킹(Incremental Marking)은 전체 마킹 작업을 짧은 단위(예: 5~10ms)로 쪼개어 메인 스레드의 애플리케이션 실행과 교차로 수행하는 방식이다 [6, 7]. @@ -17,8 +17,8 @@ 이 두 기법은 모바일 기기나 대규모 데이터 처리 환경에서 500~1000ms에 달하던 극단적인 가비지 컬렉션 일시 정지를 획기적으로 줄이는 데 기여한다 [6, 12]. 특히 사용자의 입력에 응답하거나 애니메이션을 부드럽게 렌더링해야 하는 인터랙티브 환경에서 버벅거림(Jank)과 지연율을 줄이는 핵심 역할을 한다 [3, 6, 13]. ## 🔗 Knowledge Connections -- **Related Topics:** [[가비지 컬렉션(Garbage Collection)]], [[마크-스윕(Mark-Sweep)]], [[쓰기 장벽(Write Barrier)]], [[삼색 마킹(Tri-color Marking)]] -- **Projects/Contexts:** [[V8 자바스크립트 엔진(V8 JavaScript Engine)]], [[Orinoco 가비지 컬렉터]], [[IBM Eclipse OpenJ9]] +- **Related Topics:** [[가비지 컬렉션(Garbage Collection)|가비지 컬렉션(Garbage Collection)]], [[마크-스윕(Mark-Sweep)|마크-스윕(Mark-Sweep)]], [[쓰기 장벽(Write Barrier)|쓰기 장벽(Write Barrier)]], 삼색 마킹(Tri-color Marking) +- **Projects/Contexts:** V8 자바스크립트 엔진(V8 JavaScript Engine), [[Orinoco 가비지 컬렉터|Orinoco 가비지 컬렉터]], IBM Eclipse OpenJ9 - **Contradictions/Notes:** 점진적 마킹은 개별 일시 정지 시간은 짧게 분산시키지만 메인 스레드가 마킹에 소요하는 총합 시간은 오히려 약간 증가시킬 수 있는 반면, 동시성 마킹은 메인 스레드를 온전히 해방시키는 대신 백그라운드 스레드와의 동기화 비용(Overhead)이 추가로 발생한다는 차이점이 있다 [3, 5]. --- diff --git a/01_Archive/2026-04-20/동작 속도(Movement Speed).md b/01_Archive/2026-04-20/동작 속도(Movement Speed).md index 7b27cc55..5f1599e9 100644 --- a/01_Archive/2026-04-20/동작 속도(Movement Speed).md +++ b/01_Archive/2026-04-20/동작 속도(Movement Speed).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-8D64FF -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 동작 속도(Movement Speed)" --- -# [[동작 속도(Movement Speed)]] +# [[동작 속도(Movement Speed)|동작 속도(Movement Speed)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 동작 속도(Movement Speed)는 사용자가 특정 자극에 반응하여 물리적인 움직임을 수행하는 데 소요되는 시간이나 속도를 의미합니다 [1]. 반응 시간 측정 시 인지적 요인인 결정 속도와 분리되어 순수한 운동적 요소로 평가되며, 버튼에서 손을 떼어 목표물을 터치할 때까지의 시간 등으로 계산됩니다 [1]. 가상현실(VR) 엑서게임(Exergame) 플레이 전후의 단기적 신체 능력 변화를 측정하거나, 비디오 게임 내 플레이어의 이동 속도를 분석하는 지표로 활용되지만, 동작 속도의 생리학적 메커니즘 전반에 대해서는 소스에 관련 정보가 부족합니다 [2], [3]. @@ -22,11 +22,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 동작 속도(Movement Speed)" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[반응 시간(Reaction Time)]], [[결정 속도(Decision Speed)]] -- **Projects/Contexts:** [[CANTAB 5-choice RTI task]], [[가상현실 엑서게임(VR Exergaming)]] +- **Related Topics:** [[반응 시간(Reaction Time)|반응 시간(Reaction Time)]], [[결정 속도(Decision Speed)|결정 속도(Decision Speed)]] +- **Projects/Contexts:** CANTAB 5-choice RTI task, 가상현실 엑서게임(VR Exergaming) - **Contradictions/Notes:** 소스에 따르면 단기간의 VR 엑서게임 플레이 직후 동작 속도의 일시적 향상이 확인되었으나, 반복적이고 장기적인 플레이가 동작 속도에 미치는 인지적/신체적 영향에 대해서는 소스에 관련 정보가 부족합니다 [2]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/동작 속도(Movement Speed).md]] +- Raw Source: 00_Raw/2026-04-20/동작 속도(Movement Speed).md --- diff --git a/01_Archive/2026-04-20/동적 애플리케이션 보안 테스트(DAST).md b/01_Archive/2026-04-20/동적 애플리케이션 보안 테스트(DAST).md index 75681e8e..8f3e5cdb 100644 --- a/01_Archive/2026-04-20/동적 애플리케이션 보안 테스트(DAST).md +++ b/01_Archive/2026-04-20/동적 애플리케이션 보안 테스트(DAST).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-93CA9B -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 동적 애플리케이션 보안 테스트(DAST)" --- -# [[동적 애플리케이션 보안 테스트(DAST)]] +# [[동적 애플리케이션 보안 테스트(DAST)|동적 애플리케이션 보안 테스트(DAST)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 동적 애플리케이션 보안 테스트(DAST)는 실행 중인 애플리케이션을 외부에서 테스트하여 취약점을 찾는 블랙박스(Black-box) 보안 테스트 기법입니다 [1, 2]. 소스 코드를 정적으로 분석하는 SAST와 달리, DAST는 런타임 동작, 구성 오류(configuration issues) 및 노출된 공격 표면을 관찰합니다 [1, 2]. 주로 스테이징이나 프로덕션과 같은 소프트웨어 개발 수명 주기(SDLC)의 후반부에 적용되어 실제 배포 환경에서의 런타임 보안을 검증하는 데 사용됩니다 [2]. @@ -23,11 +23,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 동적 애플리케이션 보 - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[정적 애플리케이션 보안 테스트(SAST)]], [[블랙박스 테스트]], [[퍼징(Fuzzing)]] -- **Projects/Contexts:** [[소프트웨어 개발 수명 주기(SDLC)]], [[CI/CD 파이프라인]] +- **Related Topics:** [[정적 애플리케이션 보안 테스트(SAST)|정적 애플리케이션 보안 테스트(SAST)]], 블랙박스 테스트, 퍼징(Fuzzing) +- **Projects/Contexts:** [[소프트웨어 개발 수명 주기 (SDLC)|소프트웨어 개발 수명 주기(SDLC)]], [[CI_CD 파이프라인|CI/CD 파이프라인]] - **Contradictions/Notes:** 소스에 명시적인 모순점은 없으나, 주의할 점으로 DAST와 SAST의 명확한 역할 차이가 강조됩니다. SAST는 소스 코드를 볼 수 있는 화이트박스 테스트인 반면 DAST는 코드를 보지 않고 외부에서 공격을 시도하는 블랙박스 테스트이므로, 두 방법은 경쟁 관계가 아닌 상호보완적으로 사용해야 가장 효과적이라고 설명됩니다 [1-3]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/동적 애플리케이션 보안 테스트(DAST).md]] +- Raw Source: 00_Raw/2026-04-20/동적 애플리케이션 보안 테스트(DAST).md --- diff --git a/01_Archive/2026-04-20/디자인 시스템 (Design Systems).md b/01_Archive/2026-04-20/디자인 시스템 (Design Systems).md index 76c25be9..93b69950 100644 --- a/01_Archive/2026-04-20/디자인 시스템 (Design Systems).md +++ b/01_Archive/2026-04-20/디자인 시스템 (Design Systems).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-891E2B -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 디자인 시스템 (Design Systems)" --- -# [[디자인 시스템 (Design Systems)]] +# [[디자인 시스템 (Design Systems)|디자인 시스템 (Design Systems)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - 디자인 시스템 (Design Sy ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/디자인 시스템 (Design Systems).md]] +- Raw Source: 00_Raw/2026-04-20/디자인 시스템 (Design Systems).md --- diff --git a/01_Archive/2026-04-20/디지털 미학(Digital Aesthetics).md b/01_Archive/2026-04-20/디지털 미학(Digital Aesthetics).md index 945d6e50..267c77ed 100644 --- a/01_Archive/2026-04-20/디지털 미학(Digital Aesthetics).md +++ b/01_Archive/2026-04-20/디지털 미학(Digital Aesthetics).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-276C6F -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 디지털 미학(Digital Aesthetics)" --- -# [[디지털 미학(Digital Aesthetics)]] +# [[디지털 미학(Digital Aesthetics)|디지털 미학(Digital Aesthetics)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - 디지털 미학(Digital Aesth ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/디지털 미학(Digital Aesthetics).md]] +- Raw Source: 00_Raw/2026-04-20/디지털 미학(Digital Aesthetics).md --- diff --git a/01_Archive/2026-04-20/라이브러리 및 확장 가능한 코드베이스.md b/01_Archive/2026-04-20/라이브러리 및 확장 가능한 코드베이스.md index aabf45cf..ef2e815c 100644 --- a/01_Archive/2026-04-20/라이브러리 및 확장 가능한 코드베이스.md +++ b/01_Archive/2026-04-20/라이브러리 및 확장 가능한 코드베이스.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-BBBC83 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 라이브러리 및 확장 가능한 코드베이스" --- -# [[라이브러리 및 확장 가능한 코드베이스]] +# [[라이브러리 및 확장 가능한 코드베이스|라이브러리 및 확장 가능한 코드베이스]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 라이브러리 및 확장 가능한 코드베이스는 중복되는 로직이나 공통 기능을 추상화하여 재사용 가능한 모듈과 공유 라이브러리로 구축함으로써, 시스템이 커지더라도 유연하고 유지보수 가능하게 만드는 소프트웨어 설계 방식을 의미합니다. DRY(Don't Repeat Yourself)와 관심사의 분리(SoC) 같은 소프트웨어 공학 원칙을 바탕으로 코드를 조직화하여, 기능이 추가되거나 다수의 팀이 병렬로 개발하더라도 안정적으로 시스템을 확장할 수 있는 토대를 제공합니다. @@ -24,11 +24,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 라이브러리 및 확장 가 - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[DRY 원칙 (Don't Repeat Yourself)]], [[관심사의 분리 (Separation of Concerns)]], [[마이크로 프론트엔드 (Micro Frontends)]], [[클린 아키텍처 (Clean Architecture)]] -- **Projects/Contexts:** [[대규모 프론트엔드 웹 개발 프로젝트]], [[모던 데이터 아키텍처 파이프라인]], [[복잡한 확장성(Scalability)을 요구하는 엔터프라이즈 시스템]] +- **Related Topics:** DRY 원칙 (Don't Repeat Yourself), [[관심사의 분리 (Separation of Concerns)|관심사의 분리 (Separation of Concerns)]], [[마이크로 프론트엔드 (Micro Frontends)|마이크로 프론트엔드 (Micro Frontends)]], [[클린 아키텍처 (Clean Architecture)|클린 아키텍처 (Clean Architecture)]] +- **Projects/Contexts:** 대규모 프론트엔드 웹 개발 프로젝트, 모던 데이터 아키텍처 파이프라인, 복잡한 확장성(Scalability)을 요구하는 엔터프라이즈 시스템 - **Contradictions/Notes:** 소스에 따르면, 코드를 공유 라이브러리로 추상화하는 것은 유용하지만 너무 이른 추상화(Premature abstraction)는 불필요한 복잡성을 추가할 수 있으므로 동일한 코드가 최소 두 번 이상 복제된 후에 추상화해야 한다고 권장합니다 [3]. 또한, 마이크로 프론트엔드 아키텍처 등에서 서로 다른 모듈 간에 공유 라이브러리의 버전 불일치(Version Mismatch)가 발생하면 런타임 충돌로 이어질 수 있다는 문제점이 있습니다 [12]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/라이브러리 및 확장 가능한 코드베이스.md]] +- Raw Source: 00_Raw/2026-04-20/라이브러리 및 확장 가능한 코드베이스.md --- diff --git a/01_Archive/2026-04-20/라이브러리 타입 선언 (d.ts) 확장.md b/01_Archive/2026-04-20/라이브러리 타입 선언 (d.ts) 확장.md index 79d3ac29..719c8463 100644 --- a/01_Archive/2026-04-20/라이브러리 타입 선언 (d.ts) 확장.md +++ b/01_Archive/2026-04-20/라이브러리 타입 선언 (d.ts) 확장.md @@ -1,4 +1,4 @@ -# [[라이브러리 타입 선언 (d.ts) 확장]] +# [[라이브러리 타입 선언 (d.ts) 확장|라이브러리 타입 선언 (d.ts) 확장]] ## 📌 Brief Summary 라이브러리 타입 선언(.d.ts) 확장은 타입스크립트 환경에서 외부 자바스크립트 라이브러리의 타입 정보를 제공, 패치(patch) 또는 연장하기 위해 수행하는 작업입니다 [1-3]. 주로 인터페이스(Interface)의 '선언 병합(Declaration Merging)' 기능을 활용하여, 기존 라이브러리 코드의 수정 없이 소비자가 필요한 타입 선언을 유연하게 추가할 수 있도록 지원합니다 [2, 4, 5]. @@ -14,8 +14,8 @@ *(참고: 구체적인 글로벌(Global) 환경에서의 모듈 수정 템플릿이나, d.ts 파일을 직접 생성하고 퍼블리싱하는 상세한 코드 작성 문법에 대해서는 소스에 관련 정보가 부족합니다 [8].)* ## 🔗 Knowledge Connections -- **Related Topics:** [[인터페이스(Interface)]], [[선언 병합(Declaration Merging)]], [[타입 별칭(Type Alias)]] -- **Projects/Contexts:** [[TypeScript 라이브러리 생태계 및 DefinitelyTyped]] +- **Related Topics:** [[인터페이스 (Interface)|인터페이스(Interface)]], [[선언 병합(Declaration Merging)|선언 병합(Declaration Merging)]], [[타입 별칭 (Type Alias)|타입 별칭(Type Alias)]] +- **Projects/Contexts:** TypeScript 라이브러리 생태계 및 DefinitelyTyped - **Contradictions/Notes:** 소스에 따르면, 일반적인 애플리케이션 코드 작성 시에는 엄격한 관리가 가능한 타입 별칭(Type)을 선호하는 실무 의견이 많지만, 외부 라이브러리 사용자가 타입을 확장해야 하는 특수한 상황에서는 선언 병합이 가능한 인터페이스(Interface)가 절대적으로 더 적합하다는 뚜렷한 용도 차이를 보입니다 [1, 2, 5, 7]. --- diff --git a/01_Archive/2026-04-20/라이브러리 타입 선언 (dts) 확장.md b/01_Archive/2026-04-20/라이브러리 타입 선언 (dts) 확장.md index e5bbd9e5..60daa761 100644 --- a/01_Archive/2026-04-20/라이브러리 타입 선언 (dts) 확장.md +++ b/01_Archive/2026-04-20/라이브러리 타입 선언 (dts) 확장.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-73EE30 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 라이브러리 타입 선언 (dts) 확장" --- -# [[라이브러리 타입 선언 (dts) 확장]] +# [[라이브러리 타입 선언 (dts) 확장|라이브러리 타입 선언 (dts) 확장]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 라이브러리 타입 선언(.d.ts) 확장은 타입스크립트 환경에서 외부 자바스크립트 라이브러리의 타입 정보를 제공, 패치(patch) 또는 연장하기 위해 수행하는 작업입니다 [1-3]. 주로 인터페이스(Interface)의 '선언 병합(Declaration Merging)' 기능을 활용하여, 기존 라이브러리 코드의 수정 없이 소비자가 필요한 타입 선언을 유연하게 추가할 수 있도록 지원합니다 [2, 4, 5]. @@ -27,11 +27,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 라이브러리 타입 선언 - **정책 변화:** Design & Experience 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[인터페이스(Interface)]], [[선언 병합(Declaration Merging)]], [[타입 별칭(Type Alias)]] -- **Projects/Contexts:** [[TypeScript 라이브러리 생태계 및 DefinitelyTyped]] +- **Related Topics:** [[인터페이스 (Interface)|인터페이스(Interface)]], [[선언 병합(Declaration Merging)|선언 병합(Declaration Merging)]], [[타입 별칭 (Type Alias)|타입 별칭(Type Alias)]] +- **Projects/Contexts:** TypeScript 라이브러리 생태계 및 DefinitelyTyped - **Contradictions/Notes:** 소스에 따르면, 일반적인 애플리케이션 코드 작성 시에는 엄격한 관리가 가능한 타입 별칭(Type)을 선호하는 실무 의견이 많지만, 외부 라이브러리 사용자가 타입을 확장해야 하는 특수한 상황에서는 선언 병합이 가능한 인터페이스(Interface)가 절대적으로 더 적합하다는 뚜렷한 용도 차이를 보입니다 [1, 2, 5, 7]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/라이브러리 타입 선언 (d.ts) 확장.md]] +- Raw Source: 00_Raw/2026-04-20/라이브러리 타입 선언 (d.ts) 확장.md --- diff --git a/01_Archive/2026-04-20/런타임 상태 검증(Runtime Validation).md b/01_Archive/2026-04-20/런타임 상태 검증(Runtime Validation).md index c06eaae6..dbf3e12d 100644 --- a/01_Archive/2026-04-20/런타임 상태 검증(Runtime Validation).md +++ b/01_Archive/2026-04-20/런타임 상태 검증(Runtime Validation).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-1A43C0 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 런타임 상태 검증(Runtime Validation)" --- -# [[런타임 상태 검증(Runtime Validation)]] +# [[런타임 상태 검증(Runtime Validation)|런타임 상태 검증(Runtime Validation)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 런타임 상태 검증(Runtime Validation)은 애플리케이션 실행 중 외부에서 유입되는 데이터가 예상된 타입과 비즈니스 규칙을 충족하는지 확인하는 기법입니다. TypeScript의 정적 타입 시스템은 컴파일 시점에만 존재하여 런타임 시 외부 데이터의 무결성을 보장할 수 없기 때문에, 이 간극을 메우기 위해 사용됩니다[1, 2]. 주로 Zod와 같은 라이브러리를 활용하여 시스템 경계에서 데이터를 파싱하고 검증함으로써 코드베이스 전반의 타입 안전성을 극대화합니다[3, 4]. @@ -23,11 +23,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 런타임 상태 검증(Runtim - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Parse, don't validate]], [[Zod]], [[Branded Types]], [[Discriminated Unions]] +- **Related Topics:** [[Parse, don't validate|Parse, don't validate]], [[Zod|Zod]], [[Branded Types|Branded Types]], [[Discriminated Unions|Discriminated Unions]] - **Projects/Contexts:** 외부 API 응답 데이터 처리 및 파싱[1, 5], 외부 설정 파일 유효성 검사[1, 5], 외부에서 소비되는 컴포넌트 라이브러리 구축[5]. - **Contradictions/Notes:** TypeScript의 순수 타입 검사는 런타임 오버헤드를 전혀 추가하지 않지만, 런타임 검증(Runtime Validation)은 실제 실행 비용이 발생하므로 강력한 안전성을 제공하는 대신 성능과의 트레이드오프(Trade-off)를 고려하여 적절히 배치해야 합니다[2]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/런타임 상태 검증(Runtime Validation).md]] +- Raw Source: 00_Raw/2026-04-20/런타임 상태 검증(Runtime Validation).md --- diff --git a/01_Archive/2026-04-20/루도-내러티브 부조화(Ludonarrative Dissonance).md b/01_Archive/2026-04-20/루도-내러티브 부조화(Ludonarrative Dissonance).md index a6b18036..7bd18f41 100644 --- a/01_Archive/2026-04-20/루도-내러티브 부조화(Ludonarrative Dissonance).md +++ b/01_Archive/2026-04-20/루도-내러티브 부조화(Ludonarrative Dissonance).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-CBF7DE -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 루도-내러티브 부조화(Ludonarrative Dissonance)" --- -# [[루도-내러티브 부조화(Ludonarrative Dissonance)]] +# [[루도-내러티브 부조화(Ludonarrative Dissonance)|루도-내러티브 부조화(Ludonarrative Dissonance)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - 루도-내러티브 부조화( ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/루도-내러티브 부조화(Ludonarrative Dissonance).md]] +- Raw Source: 00_Raw/2026-04-20/루도-내러티브 부조화(Ludonarrative Dissonance).md --- diff --git a/01_Archive/2026-04-20/리로디드(Reloaded).md b/01_Archive/2026-04-20/리로디드(Reloaded).md index 2100bab3..85d5b192 100644 --- a/01_Archive/2026-04-20/리로디드(Reloaded).md +++ b/01_Archive/2026-04-20/리로디드(Reloaded).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-CF4C61 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 리로디드(Reloaded)" --- -# [[리로디드(Reloaded)]] +# [[리로디드(Reloaded)|리로디드(Reloaded)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 리로디드(Reloaded)는 파트너와 스튜디오로부터 유입되는 미디어 파일을 처리하여 모든 기기에서 재생할 수 있도록 변환하는 넷플릭스(Netflix)의 3세대 비디오/오디오 처리 파이프라인 시스템입니다 [1]. 약 7년 동안 운영되며 안정성과 대규모 확장성을 입증했으나, 비즈니스 성장과 함께 모놀리틱 아키텍처의 한계가 명확히 드러나게 되었습니다 [1]. 결과적으로 이 크고 복잡한 레거시 시스템은 마이크로서비스 기반의 새로운 '코스모스(Cosmos)' 플랫폼으로 점진적으로 대체되고 있습니다 [2-4]. @@ -22,11 +22,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 리로디드(Reloaded)" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[모놀리틱 아키텍처(Monolithic Architecture)]], [[코스모스(Cosmos)]], [[스트랭글러 피그 패턴(Strangler Fig Pattern)]] -- **Projects/Contexts:** [[넷플릭스 미디어 클라우드 엔지니어링(Netflix Media Cloud Engineering)]] +- **Related Topics:** 모놀리틱 아키텍처(Monolithic Architecture), [[코스모스(Cosmos)|코스모스(Cosmos)]], [[스트랭글러 피그 패턴(Strangler Fig Pattern)|스트랭글러 피그 패턴(Strangler Fig Pattern)]] +- **Projects/Contexts:** 넷플릭스 미디어 클라우드 엔지니어링(Netflix Media Cloud Engineering) - **Contradictions/Notes:** 리로디드는 구축 후 약 7년 동안 매우 안정적이고 대규모 확장이 가능한(stable and massively scalable) 시스템으로 기능했지만, 조직 규모와 요구사항의 폭발적 성장에 직면하면서 유용했던 중앙 집중식 모델이 역으로 큰 한계를 드러내는 모순적인 기술 생명주기를 보여줍니다 [1]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/리로디드(Reloaded).md]] +- Raw Source: 00_Raw/2026-04-20/리로디드(Reloaded).md --- diff --git a/01_Archive/2026-04-20/리터럴 타입 (Literal Types).md b/01_Archive/2026-04-20/리터럴 타입 (Literal Types).md index 81066f7e..0629a376 100644 --- a/01_Archive/2026-04-20/리터럴 타입 (Literal Types).md +++ b/01_Archive/2026-04-20/리터럴 타입 (Literal Types).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-B0B7AB -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 리터럴 타입 (Literal Types)" --- -# [[리터럴 타입 (Literal Types)]] +# [[리터럴 타입 (Literal Types)|리터럴 타입 (Literal Types)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 리터럴 타입(Literal Types)은 `string`이나 `number`와 같은 범용적인 원시 타입 대신, 개발자가 미리 정의한 정확하고 구체적인 값(예: 특정 문자열, 특정 숫자 등)만을 허용하는 타입입니다. 단일 값으로 구성되는 이 타입은 주로 유니온 타입(Union Types)과 결합되어 허용되는 값의 범위를 엄격하게 제한하는 데 사용됩니다. 특히 식별 가능한 유니온(Discriminated Unions) 패턴의 핵심 요소로 작용하여, 컴파일러가 타입의 범위를 안전하게 좁히고(Narrowing) 예측 가능한 코드를 작성할 수 있도록 돕습니다. @@ -28,11 +28,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 리터럴 타입 (Literal Type - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[유니온 타입 (Union Types)]], [[식별 가능한 유니온 (Discriminated Unions)]], [[타입 좁히기 (Type Narrowing)]], [[satisfies 연산자]], [[as const 단언]] -- **Projects/Contexts:** [[네트워크 응답 상태 모델링 (loading, success, failed 상태 구분)]], [[Redux 액션 및 API 응답 처리 패턴]] +- **Related Topics:** [[유니온 타입 (Union Types)|유니온 타입 (Union Types)]], [[식별 가능한 유니온 (Discriminated Unions)|식별 가능한 유니온 (Discriminated Unions)]], [[타입 좁히기 (Type Narrowing)|타입 좁히기 (Type Narrowing)]], [[satisfies 연산자|satisfies 연산자]], as const 단언 +- **Projects/Contexts:** 네트워크 응답 상태 모델링 (loading, success, failed 상태 구분), Redux 액션 및 API 응답 처리 패턴 - **Contradictions/Notes:** 리터럴 타입 자체는 단일한 값만을 허용하기에 그 자체로만 쓰이면 제한적이지만, 유니온 타입 및 `satisfies`, `as const` 와 같은 TypeScript의 고급 기능들과 결합할 때 비로소 예측 불가능한 런타임 오류를 막아주고 자동 완성(IntelliSense)을 극대화하는 컴파일 타임의 핵심 안전장치로 작동합니다. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/리터럴 타입 (Literal Types).md]] +- Raw Source: 00_Raw/2026-04-20/리터럴 타입 (Literal Types).md --- diff --git a/01_Archive/2026-04-20/린터 (Linter).md b/01_Archive/2026-04-20/린터 (Linter).md index 51f1e5b2..32b2b3d3 100644 --- a/01_Archive/2026-04-20/린터 (Linter).md +++ b/01_Archive/2026-04-20/린터 (Linter).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-D02DB7 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 린터 (Linter)" --- -# [[린터 (Linter)]] +# [[린터 (Linter)|린터 (Linter)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -27,11 +27,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 린터 (Linter)" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[정적 분석 (Static Analysis)]], [[포매터 (Formatter)]], [[ESLint]] -- **Projects/Contexts:** [[통합 개발 환경 (IDE)]], [[CI/CD 파이프라인]], [[코드 리뷰 (Code Review)]] +- **Related Topics:** [[정적 분석(Static Analysis)|정적 분석 (Static Analysis)]], 포매터 (Formatter), [[ESLint|ESLint]] +- **Projects/Contexts:** 통합 개발 환경 (IDE), [[CI_CD 파이프라인|CI/CD 파이프라인]], [[코드 리뷰 (Code Review)|코드 리뷰 (Code Review)]] - **Contradictions/Notes:** 린터(Linter)는 코드 품질 보장과 오류 검출에 중점을 두는 반면, 포매터(Formatter)는 코드를 깔끔하게 정렬하는 데 특화되어 있다 [17]. 그러나 린터(예: ESLint)에도 코드 포매팅 기능이 포함되어 있어 Prettier와 같은 전용 포매터와 함께 사용할 경우 스타일 규칙 충돌이 발생할 수 있으므로, 린터의 포매팅 기능을 끄고 문법 검사 기능만 사용하도록 설정(예: `eslint-config-prettier` 사용)하는 것이 권장된다 [18, 19]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/린터 (Linter).md]] +- Raw Source: 00_Raw/2026-04-20/린터 (Linter).md --- diff --git a/01_Archive/2026-04-20/마이너 가비지 컬렉션(Minor GC).md b/01_Archive/2026-04-20/마이너 가비지 컬렉션(Minor GC).md index b78bd12f..ae251afe 100644 --- a/01_Archive/2026-04-20/마이너 가비지 컬렉션(Minor GC).md +++ b/01_Archive/2026-04-20/마이너 가비지 컬렉션(Minor GC).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-4E47A6 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 마이너 가비지 컬렉션(Minor GC)" --- -# [[마이너 가비지 컬렉션(Minor GC)]] +# [[마이너 가비지 컬렉션(Minor GC)|마이너 가비지 컬렉션(Minor GC)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -31,11 +31,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 마이너 가비지 컬렉션( - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[새로운 공간(New Space)]], [[구세대(Old Space)]], [[세대별 가설(Generational Hypothesis)]], [[스캐빈저(Scavenger)]], [[쓰기 장벽(Write Barrier)]] -- **Projects/Contexts:** [[V8 JavaScript Engine]], [[Orinoco Garbage Collector]] +- **Related Topics:** [[새로운 공간(New Space)|새로운 공간(New Space)]], 구세대(Old Space), [[세대별 가설(Generational Hypothesis)|세대별 가설(Generational Hypothesis)]], [[스캐빈저(Scavenger)|스캐빈저(Scavenger)]], [[쓰기 장벽(Write Barrier)|쓰기 장벽(Write Barrier)]] +- **Projects/Contexts:** [[V8 JavaScript Engine|V8 JavaScript Engine]], Orinoco Garbage Collector - **Contradictions/Notes:** 초기 V8 버전에서는 마이너 GC를 위해 단일 스레드로 동작하는 동기식 체니 알고리즘(Cheney's algorithm)을 사용했지만, 최신 버전에서는 멀티코어 환경에 맞춰 작업 훔치기(work stealing) 기법을 활용하는 병렬 스캐빈저(Parallel Scavenger)로 발전했습니다 [7, 13]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/마이너 가비지 컬렉션(Minor GC).md]] +- Raw Source: 00_Raw/2026-04-20/마이너 가비지 컬렉션(Minor GC).md --- diff --git a/01_Archive/2026-04-20/마이크로 프론트엔드 (Micro Frontends).md b/01_Archive/2026-04-20/마이크로 프론트엔드 (Micro Frontends).md index 20e3c23d..a06685e6 100644 --- a/01_Archive/2026-04-20/마이크로 프론트엔드 (Micro Frontends).md +++ b/01_Archive/2026-04-20/마이크로 프론트엔드 (Micro Frontends).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-039AAE -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 마이크로 프론트엔드 (Micro Frontends)" --- -# [[마이크로 프론트엔드 (Micro Frontends)]] +# [[마이크로 프론트엔드 (Micro Frontends)|마이크로 프론트엔드 (Micro Frontends)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 마이크로 프론트엔드(Micro Frontends)는 백엔드의 마이크로서비스 아키텍처와 유사하게, 방대하고 복잡한 프론트엔드 애플리케이션을 작고 독립적인 여러 모듈로 나누어 개발하는 접근 방식이다 [1]. 이 아키텍처는 비즈니스 기능에 따라 프론트엔드를 분할하여, 각 부분을 전담 팀이 독립적으로 개발, 테스트, 배포할 수 있도록 지원한다 [1]. 기존 모놀리식 구조의 한계를 극복하여 팀의 자율성, 확장성, 유지보수성을 크게 향상시키는 현대 웹 개발의 솔루션이다 [1-3]. @@ -20,11 +20,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 마이크로 프론트엔드 ( - **정책 변화:** Design & Experience 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[마이크로서비스 아키텍처 (Microservices Architecture)]], [[모놀리식 아키텍처 (Monolithic Architecture)]], [[관심사의 분리 (Separation of Concerns)]], [[웹 컴포넌트 (Web Components)]], [[모듈 페더레이션 (Module federation)]] -- **Projects/Contexts:** [[Spotify의 마이크로 프론트엔드 도입 (스쿼드 모델)]], [[Netflix의 레거시 현대화 및 대시보드]], [[Zalando의 이커머스 모듈 분리]], [[IKEA와 Amazon의 독립적 UX 커스터마이징]] +- **Related Topics:** [[마이크로서비스 아키텍처 (Microservices Architecture)|마이크로서비스 아키텍처 (Microservices Architecture)]], [[모놀리식 아키텍처 (Monolithic Architecture)|모놀리식 아키텍처 (Monolithic Architecture)]], [[관심사의 분리 (Separation of Concerns)|관심사의 분리 (Separation of Concerns)]], 웹 컴포넌트 (Web Components), 모듈 페더레이션 (Module federation) +- **Projects/Contexts:** Spotify의 마이크로 프론트엔드 도입 (스쿼드 모델), Netflix의 레거시 현대화 및 대시보드, Zalando의 이커머스 모듈 분리, IKEA와 Amazon의 독립적 UX 커스터마이징 - **Contradictions/Notes:** 소스에 따르면 마이크로 프론트엔드는 팀의 자율성과 시스템의 유지보수성을 비약적으로 높여주지만, 동시에 여러 마이크로 프론트엔드 번들이 로드되면서 초기 로딩 성능에 오버헤드(Performance Overhead)가 발생하고, 스타일이나 버전 충돌 등 새로운 복잡성이 추가될 수 있다는 단점(과제)을 명확히 동반한다 [5, 9]. 따라서 소규모 프로젝트나 적절한 DevOps 기반이 없는 환경에서는 오버헤드가 장점을 상쇄하므로 피해야 한다고 경고한다 [11]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/마이크로 프론트엔드 (Micro Frontends).md]] +- Raw Source: 00_Raw/2026-04-20/마이크로 프론트엔드 (Micro Frontends).md --- diff --git a/01_Archive/2026-04-20/마이크로 프론트엔드.md b/01_Archive/2026-04-20/마이크로 프론트엔드.md index f54332c3..da470890 100644 --- a/01_Archive/2026-04-20/마이크로 프론트엔드.md +++ b/01_Archive/2026-04-20/마이크로 프론트엔드.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-E74AFF -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 마이크로 프론트엔드" --- -# [[마이크로 프론트엔드]] +# [[마이크로 프론트엔드|마이크로 프론트엔드]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 마이크로 프론트엔드는 거대하고 복잡한 프론트엔드 애플리케이션을 백엔드의 마이크로서비스처럼 작고 독립적인 여러 조각으로 나누어 개발하는 아키텍처 접근 방식입니다 [1]. 이 방식을 통해 각 비즈니스 기능별로 전담 팀이 구성되어 선호하는 기술 스택을 활용해 독립적으로 모듈을 개발, 테스트 및 배포할 수 있습니다 [1-3]. 전통적인 모놀리식 프론트엔드 구조의 한계를 극복하고 팀의 자율성, 애플리케이션의 확장성 및 유지보수성을 향상시키는 데 목적이 있습니다 [2, 4]. @@ -24,11 +24,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 마이크로 프론트엔드" - **정책 변화:** Graphics & Performance 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[마이크로서비스 아키텍처]], [[모놀리식 프론트엔드]], [[관심사의 분리(SoC)]], [[모듈 페더레이션(Module Federation)]], [[웹 컴포넌트(Web Components)]] -- **Projects/Contexts:** [[Spotify의 스쿼드(Squad) 모델 및 웹 플레이어]], [[Netflix의 대시보드 및 도구 현대화]], [[Zalando와 Amazon의 이커머스 모듈화]] +- **Related Topics:** [[마이크로서비스 아키텍처|마이크로서비스 아키텍처]], 모놀리식 프론트엔드, [[관심사의 분리(SoC)|관심사의 분리(SoC)]], 모듈 페더레이션(Module Federation), 웹 컴포넌트(Web Components) +- **Projects/Contexts:** Spotify의 스쿼드(Squad) 모델 및 웹 플레이어, Netflix의 대시보드 및 도구 현대화, Zalando와 Amazon의 이커머스 모듈화 - **Contradictions/Notes:** 마이크로 프론트엔드는 팀 간 의존성을 줄이고 자율성과 확장성을 높여주지만, 동시에 초기 로딩 성능 저하 및 빌드/배포 파이프라인의 복잡성 증가라는 뚜렷한 트레이드오프(Trade-off)를 수반합니다 [3, 8]. 소규모 프로젝트의 경우 오히려 관리 부담이 가중될 수 있어 권장되지 않습니다 [11]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/마이크로 프론트엔드.md]] +- Raw Source: 00_Raw/2026-04-20/마이크로 프론트엔드.md --- diff --git a/01_Archive/2026-04-20/마이크로서비스 아키텍처 (MSA).md b/01_Archive/2026-04-20/마이크로서비스 아키텍처 (MSA).md index e74a379f..10a1a847 100644 --- a/01_Archive/2026-04-20/마이크로서비스 아키텍처 (MSA).md +++ b/01_Archive/2026-04-20/마이크로서비스 아키텍처 (MSA).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-6DFA0C -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 마이크로서비스 아키텍처 (MSA)" --- -# [[마이크로서비스 아키텍처 (MSA)]] +# [[마이크로서비스 아키텍처 (MSA)|마이크로서비스 아키텍처 (MSA)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 마이크로서비스 아키텍처(MSA)는 단일 애플리케이션을 비즈니스 도메인을 중심으로 모델링된 작고 자율적이며 독립적으로 배포 가능한 서비스들의 모음으로 구성하는 소프트웨어 설계 접근 방식입니다 [1-3]. 이는 기존의 모놀리식(Monolithic) 아키텍처와 대비되며, 각 서비스는 자체 프로세스에서 실행되고 HTTP REST나 비동기 메시징 큐와 같은 가벼운 메커니즘을 통해 통신합니다 [1, 2, 4]. 이 아키텍처는 조직의 민첩성을 높이고 기술적 이질성을 수용하며 복잡한 시스템의 확장성을 향상시킵니다 [1, 4-6]. @@ -43,11 +43,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 마이크로서비스 아키 - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[관심사의 분리 (Separation of Concerns)]], [[모놀리식 아키텍처 (Monolithic Architecture)]], [[단일 책임 원칙 (SRP)]], [[클린 아키텍처 (Clean Architecture)]] -- **Projects/Contexts:** [[넷플릭스 (Netflix) 마이크로서비스 도입 사례]], [[Cosmos 플랫폼 (Netflix)]] +- **Related Topics:** [[관심사의 분리 (Separation of Concerns)|관심사의 분리 (Separation of Concerns)]], [[모놀리식 아키텍처 (Monolithic Architecture)|모놀리식 아키텍처 (Monolithic Architecture)]], [[단일 책임 원칙 (SRP)|단일 책임 원칙 (SRP)]], [[클린 아키텍처 (Clean Architecture)|클린 아키텍처 (Clean Architecture)]] +- **Projects/Contexts:** [[넷플릭스 (Netflix) 마이크로서비스 도입 사례|넷플릭스 (Netflix) 마이크로서비스 도입 사례]], [[Cosmos 플랫폼 (Netflix)|Cosmos 플랫폼 (Netflix)]] - **Contradictions/Notes:** 소스에 따르면 MSA는 배포 독립성, 빠른 릴리스, 확장성이라는 분명한 장점을 지니지만 [1, 3, 12], 분산 시스템으로 인한 복잡성(네트워크 지연, 부분적 실패, 테스트의 어려움) 및 많은 수의 가상 머신(VM)/JVM 런타임 운영에 따른 메모리 오버헤드와 비용 폭증이라는 상충 관계(Trade-off)를 명확히 가집니다 [9-11, 13]. 따라서 단순한 소규모 프로젝트보다는 빠르고 복잡하게 확장하는 대규모 시스템에 적합한 아키텍처입니다 [12]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/마이크로서비스 아키텍처 (MSA).md]] +- Raw Source: 00_Raw/2026-04-20/마이크로서비스 아키텍처 (MSA).md --- diff --git a/01_Archive/2026-04-20/마이크로서비스 아키텍처 (Microservices Architecture).md b/01_Archive/2026-04-20/마이크로서비스 아키텍처 (Microservices Architecture).md index 16169ed4..52bccf6b 100644 --- a/01_Archive/2026-04-20/마이크로서비스 아키텍처 (Microservices Architecture).md +++ b/01_Archive/2026-04-20/마이크로서비스 아키텍처 (Microservices Architecture).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-303610 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 마이크로서비스 아키텍처 (Microservices Architecture)" --- -# [[마이크로서비스 아키텍처 (Microservices Architecture)]] +# [[마이크로서비스 아키텍처 (Microservices Architecture)|마이크로서비스 아키텍처 (Microservices Architecture)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 마이크로서비스 아키텍처(MSA)는 크고 복잡한 단일 애플리케이션을 비즈니스 도메인(Business Domain)을 중심으로 작고 독립적이며 자율적인 서비스들의 집합으로 구조화하는 소프트웨어 개발 접근 방식입니다 [1-3]. 각 마이크로서비스는 자체 프로세스에서 실행되며 주로 HTTP/REST API나 비동기 메시징 큐와 같은 경량화된 네트워크 메커니즘을 통해 통신합니다 [3, 4]. 이 아키텍처는 개별 서비스의 독립적인 개발, 배포 및 확장을 가능하게 하여 시스템의 유지보수성, 유연성 및 장애 복원력을 크게 향상시킵니다 [1, 5]. @@ -36,11 +36,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 마이크로서비스 아키 - **정책 변화:** AI 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[단일 애플리케이션 아키텍처 (Monolithic Architecture)]], [[관심사의 분리 (Separation of Concerns)]], [[도메인 주도 설계 (Domain-Driven Design)]], [[컨테이너 및 오케스트레이션 (Containers and Orchestration)]] -- **Projects/Contexts:** [[넷플릭스 코스모스 플랫폼 (Netflix Cosmos Platform)]], [[스포티파이 스쿼드 모델 (Spotify Squad Model)]] +- **Related Topics:** 단일 애플리케이션 아키텍처 (Monolithic Architecture), [[관심사의 분리 (Separation of Concerns)|관심사의 분리 (Separation of Concerns)]], 도메인 주도 설계 (Domain-Driven Design), 컨테이너 및 오케스트레이션 (Containers and Orchestration) +- **Projects/Contexts:** [[넷플릭스 코스모스 플랫폼 (Netflix Cosmos Platform)|넷플릭스 코스모스 플랫폼 (Netflix Cosmos Platform)]], 스포티파이 스쿼드 모델 (Spotify Squad Model) - **Contradictions/Notes:** 일반적으로 마이크로서비스는 완벽한 모듈의 결합 분리와 배포 독립성을 가져다주는 것으로 간주되지만, 실제로는 시스템이 횡단 관심사(Cross-cutting concerns)나 공유 데이터 모델에 얽혀있을 경우 여러 서비스가 강하게 결합되는 '결합 분리의 오류' 및 '개발 및 배포 독립성의 오류'가 발생할 수 있습니다. 즉 서비스 간의 단순 물리적 분리만으로는 충분치 않으며, 서비스 내부의 아키텍처 경계와 의존성 규칙이 제대로 설계되어야 진정한 독립성을 확보할 수 있습니다 [21-24]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/마이크로서비스 아키텍처 (Microservices Architecture).md]] +- Raw Source: 00_Raw/2026-04-20/마이크로서비스 아키텍처 (Microservices Architecture).md --- diff --git a/01_Archive/2026-04-20/마이크로서비스 아키텍처.md b/01_Archive/2026-04-20/마이크로서비스 아키텍처.md index 5f4639c3..7de141dd 100644 --- a/01_Archive/2026-04-20/마이크로서비스 아키텍처.md +++ b/01_Archive/2026-04-20/마이크로서비스 아키텍처.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-6067F4 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 마이크로서비스 아키텍처" --- -# [[마이크로서비스 아키텍처]] +# [[마이크로서비스 아키텍처|마이크로서비스 아키텍처]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -34,11 +34,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 마이크로서비스 아키 - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[모놀리식 아키텍처]], [[서비스 지향 아키텍처(SOA)]], [[도메인 주도 설계(DDD)]], [[컨테이너 및 클라우드 네이티브 아키텍처]] -- **Projects/Contexts:** [[넷플릭스(Netflix) 마이크로서비스 도입 사례]], [[넷플릭스 코스모스(Cosmos) 플랫폼]], [[스포티파이(Spotify)의 컨테이너화된 마이크로서비스]] +- **Related Topics:** 모놀리식 아키텍처, 서비스 지향 아키텍처(SOA), [[도메인 주도 설계(DDD)|도메인 주도 설계(DDD)]], 컨테이너 및 클라우드 네이티브 아키텍처 +- **Projects/Contexts:** [[넷플릭스 (Netflix) 마이크로서비스 도입 사례|넷플릭스(Netflix) 마이크로서비스 도입 사례]], 넷플릭스 코스모스(Cosmos) 플랫폼, 스포티파이(Spotify)의 컨테이너화된 마이크로서비스 - **Contradictions/Notes:** 소스에 명시적인 모순은 없으나, 마이크로서비스 아키텍처는 극대화된 유지보수성과 유연성을 가져다주는 반면, 개발 초기의 분산 시스템 복잡성 및 배포 운영 난이도가 급격히 상승한다는 명확한 '트레이드오프(Trade-off)'를 갖는다고 강조합니다. 따라서 규모가 작고 단순한 환경에서는 모놀리식 구조에 비해 과도한 설계(Over-engineering)가 될 수 있습니다. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/마이크로서비스 아키텍처.md]] +- Raw Source: 00_Raw/2026-04-20/마이크로서비스 아키텍처.md --- diff --git a/01_Archive/2026-04-20/마크-스위프(Mark-Sweep).md b/01_Archive/2026-04-20/마크-스위프(Mark-Sweep).md index edd8945f..d0b7c08e 100644 --- a/01_Archive/2026-04-20/마크-스위프(Mark-Sweep).md +++ b/01_Archive/2026-04-20/마크-스위프(Mark-Sweep).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-C80E5C -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 마크-스위프(Mark-Sweep)" --- -# [[마크-스위프(Mark-Sweep)]] +# [[마크-스위프(Mark-Sweep)|마크-스위프(Mark-Sweep)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 마크-스위프(Mark-Sweep)는 가비지 컬렉터(GC)가 더 이상 사용되지 않는 메모리 영역을 식별하고 회수하여 재사용할 수 있도록 하는 가비지 컬렉션 알고리즘입니다 [1]. 루트(Root) 객체부터 도달 가능한 라이브(Live) 객체를 식별하여 표시하는 '마킹(Mark)' 단계와, 마킹되지 않은 데드(Dead) 객체를 메모리에서 지워 빈 공간(Free space)으로 전환하는 '스위핑(Sweep)' 단계로 구성됩니다 [2, 3]. 주로 자바스크립트 V8 엔진이나 IBM 가비지 컬렉터에서 비교적 오래 살아남은 객체가 모인 구 세대(Old Generation/Space)의 메모리를 정리하는 데 사용됩니다 [4, 5]. @@ -20,11 +20,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 마크-스위프(Mark-Sweep)" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[가비지 컬렉션(Garbage Collection)]], [[마크-컴팩트(Mark-Compact)]], [[Old Space (구 세대 공간)]], [[점진적 마킹(Incremental marking)]] -- **Projects/Contexts:** [[V8 자바스크립트 엔진]], [[Orinoco 프로젝트]], [[IBM 가비지 컬렉션]] +- **Related Topics:** [[가비지 컬렉션(Garbage Collection)|가비지 컬렉션(Garbage Collection)]], [[마크-컴팩트(Mark-Compact)|마크-컴팩트(Mark-Compact)]], [[Old Space (구 세대 공간)|Old Space (구 세대 공간)]], [[점진적 마킹(Incremental marking)|점진적 마킹(Incremental marking)]] +- **Projects/Contexts:** [[V8 자바스크립트 엔진|V8 자바스크립트 엔진]], [[Orinoco 프로젝트|Orinoco 프로젝트]], [[IBM 가비지 컬렉션|IBM 가비지 컬렉션]] - **Contradictions/Notes:** 마크-컴팩트는 단편화를 제거해주지만, 모든 생존 객체를 복사하고 메모리 포인터를 업데이트해야 하므로 비용이 매우 비쌉니다. 따라서 V8 엔진은 모든 페이지를 컴팩트하지 않고, 일부는 스위핑(Sweep)만 수행하며 필요한 파편화 페이지에 한해서만 압축(Compact)을 진행하는 전략을 취합니다 [17, 24]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/마크-스위프(Mark-Sweep).md]] +- Raw Source: 00_Raw/2026-04-20/마크-스위프(Mark-Sweep).md --- diff --git a/01_Archive/2026-04-20/마크-스위프-컴팩트(Mark-Sweep-Compact).md b/01_Archive/2026-04-20/마크-스위프-컴팩트(Mark-Sweep-Compact).md index 49ff4761..c0197e5d 100644 --- a/01_Archive/2026-04-20/마크-스위프-컴팩트(Mark-Sweep-Compact).md +++ b/01_Archive/2026-04-20/마크-스위프-컴팩트(Mark-Sweep-Compact).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-F94637 -category: "[[10_Wiki/💡 Topics/General Knowledge]]" +category: "10_Wiki/💡 Topics/General Knowledge" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 마크-스위프-컴팩트(Mark-Sweep-Compact)" --- -# [[마크-스위프-컴팩트(Mark-Sweep-Compact)]] +# [[마크-스위프-컴팩트(Mark-Sweep-Compact)|마크-스위프-컴팩트(Mark-Sweep-Compact)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -30,11 +30,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 마크-스위프-컴팩트(Mar - **정책 변화:** General Knowledge 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[가비지 컬렉션(Garbage Collection)]], [[이전 세대(Old Generation/Space)]], [[스캐빈저(Scavenger)]], [[동시성 및 점진적 마킹(Concurrent & Incremental Marking)]] -- **Projects/Contexts:** [[V8 자바스크립트 엔진]], [[자바 가상 머신(JVM)]], [[Orinoco 프로젝트]] +- **Related Topics:** [[가비지 컬렉션(Garbage Collection)|가비지 컬렉션(Garbage Collection)]], [[이전 세대(Old Generation_Space)|이전 세대(Old Generation/Space)]], [[스캐빈저(Scavenger)|스캐빈저(Scavenger)]], [[동시성 및 점진적 마킹(Concurrent & Incremental Marking)|동시성 및 점진적 마킹(Concurrent & Incremental Marking)]] +- **Projects/Contexts:** [[V8 자바스크립트 엔진|V8 자바스크립트 엔진]], [[자바 가상 머신(JVM)|자바 가상 머신(JVM)]], [[Orinoco 프로젝트|Orinoco 프로젝트]] - **Contradictions/Notes:** 소스 전반에서 마크-스위프-컴팩트의 기본 원리에는 차이가 없으나, 작동 환경(예: V8 엔진 대 IBM JVM)에 따라 이 알고리즘을 트리거하는 조건이나 조정 가능한 커맨드라인 옵션(`-Xcompactgc`, `--trace-gc` 등)은 구체적인 구현체에 따라 각기 다르게 제어된다는 점이 확인된다 [18, 22]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/마크-스위프-컴팩트(Mark-Sweep-Compact).md]] +- Raw Source: 00_Raw/2026-04-20/마크-스위프-컴팩트(Mark-Sweep-Compact).md --- diff --git a/01_Archive/2026-04-20/마크-스윕(Mark-Sweep).md b/01_Archive/2026-04-20/마크-스윕(Mark-Sweep).md index 38c5a4e0..e9883f35 100644 --- a/01_Archive/2026-04-20/마크-스윕(Mark-Sweep).md +++ b/01_Archive/2026-04-20/마크-스윕(Mark-Sweep).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-A62B31 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 마크-스윕(Mark-Sweep)" --- -# [[마크-스윕(Mark-Sweep)]] +# [[마크-스윕(Mark-Sweep)|마크-스윕(Mark-Sweep)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 마크-스윕(Mark-Sweep)은 V8 엔진 및 자바 가상 머신(JVM) 등에서 더 이상 필요하지 않은 객체의 메모리를 회수하기 위해 사용하는 주요 가비지 컬렉션(Major GC) 알고리즘입니다 [1-3]. 이 알고리즘은 힙을 순회하며 활성 상태인 객체를 식별하는 '마크(Mark)' 단계와, 표시되지 않은 객체를 제거하여 메모리를 확보하는 '스윕(Sweep)' 단계로 나뉘어 동작합니다 [2, 4, 5]. 주로 수십에서 수백 메가바이트의 데이터를 포함할 수 있는 대용량 메모리 영역인 구공간(Old Space)을 관리하는 데 필수적으로 사용됩니다 [4, 6]. @@ -26,11 +26,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 마크-스윕(Mark-Sweep)" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[가비지 컬렉션(Garbage Collection)]], [[구공간(Old Space)]], [[마크-컴팩트(Mark-Compact)]], [[점진적 마킹(Incremental Marking)]], [[스캐빈지(Scavenge)]] -- **Projects/Contexts:** [[V8 엔진(V8 Engine)]], [[오리노코(Orinoco)]], [[자바 가상 머신(JVM)]] +- **Related Topics:** [[가비지 컬렉션(Garbage Collection)|가비지 컬렉션(Garbage Collection)]], 구공간(Old Space), [[마크-컴팩트(Mark-Compact)|마크-컴팩트(Mark-Compact)]], [[점진적 마킹(Incremental marking)|점진적 마킹(Incremental Marking)]], 스캐빈지(Scavenge) +- **Projects/Contexts:** [[V8 엔진(V8 Engine)|V8 엔진(V8 Engine)]], 오리노코(Orinoco), [[자바 가상 머신(JVM)|자바 가상 머신(JVM)]] - **Contradictions/Notes:** 소스의 설명에 따르면, 스캐빈지(Scavenge) 알고리즘은 투-스페이스(to-space)와 프롬-스페이스(from-space)를 사용하는 물리적 메모리 오버헤드가 크기 때문에 신공간(New Space)에서만 유용하게 쓰이며, 반면 마크-스윕은 메모리 오버헤드는 적지만 실행 시간이 오래 걸릴 수 있어 구공간(Old Space) 관리에 사용된다는 명확한 역할 분담이 존재합니다 [4, 6]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/마크-스윕(Mark-Sweep).md]] +- Raw Source: 00_Raw/2026-04-20/마크-스윕(Mark-Sweep).md --- diff --git a/01_Archive/2026-04-20/마크-컴팩트(Mark-Compact).md b/01_Archive/2026-04-20/마크-컴팩트(Mark-Compact).md index f2126713..7603b1d5 100644 --- a/01_Archive/2026-04-20/마크-컴팩트(Mark-Compact).md +++ b/01_Archive/2026-04-20/마크-컴팩트(Mark-Compact).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-5617F2 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 마크-컴팩트(Mark-Compact)" --- -# [[마크-컴팩트(Mark-Compact)]] +# [[마크-컴팩트(Mark-Compact)|마크-컴팩트(Mark-Compact)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -30,11 +30,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 마크-컴팩트(Mark-Compact) - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[가비지 컬렉션(Garbage Collection)]], [[마크-스윕(Mark-Sweep)]], [[단편화(Fragmentation)]] -- **Projects/Contexts:** [[V8 JavaScript Engine]], [[IBM SDK/Eclipse OpenJ9]] +- **Related Topics:** [[가비지 컬렉션(Garbage Collection)|가비지 컬렉션(Garbage Collection)]], [[마크-스윕(Mark-Sweep)|마크-스윕(Mark-Sweep)]], 단편화(Fragmentation) +- **Projects/Contexts:** [[V8 JavaScript Engine|V8 JavaScript Engine]], IBM SDK/Eclipse OpenJ9 - **Contradictions/Notes:** 소스 상에서 마크-컴팩트 알고리즘의 개념에 대한 모순은 없습니다. 다만 V8(자바스크립트)에서는 주로 'Old Space'를 정리하기 위해 설계된 메이저 가비지 컬렉션의 핵심 메커니즘으로 소개되며 [1, 2], IBM OpenJ9(자바) 환경에서는 고비용 오퍼레이션이라는 이유로 기본적으로는 발생하지 않되, 공간 고갈이나 명시적 옵션 적용 시 발생하는 조건부 동작으로 자세히 묘사됩니다 [7, 12]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/마크-컴팩트(Mark-Compact).md]] +- Raw Source: 00_Raw/2026-04-20/마크-컴팩트(Mark-Compact).md --- diff --git a/01_Archive/2026-04-20/만성 질환 행동 수정 개입.md b/01_Archive/2026-04-20/만성 질환 행동 수정 개입.md index b6e1c5eb..c9e1731a 100644 --- a/01_Archive/2026-04-20/만성 질환 행동 수정 개입.md +++ b/01_Archive/2026-04-20/만성 질환 행동 수정 개입.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-2F0833 -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 만성 질환 행동 수정 개입" --- -# [[만성 질환 행동 수정 개입]] +# [[만성 질환 행동 수정 개입|만성 질환 행동 수정 개입]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - 만성 질환 행동 수정 ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/만성 질환 행동 수정 개입.md]] +- Raw Source: 00_Raw/2026-04-20/만성 질환 행동 수정 개입.md --- diff --git a/01_Archive/2026-04-20/맞춤형 개별화 학습 설계.md b/01_Archive/2026-04-20/맞춤형 개별화 학습 설계.md index 16456e84..55e2ba32 100644 --- a/01_Archive/2026-04-20/맞춤형 개별화 학습 설계.md +++ b/01_Archive/2026-04-20/맞춤형 개별화 학습 설계.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-6B106E -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 맞춤형 개별화 학습 설계" --- -# [[맞춤형 개별화 학습 설계]] +# [[맞춤형 개별화 학습 설계|맞춤형 개별화 학습 설계]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - 맞춤형 개별화 학습 설 ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/맞춤형 개별화 학습 설계.md]] +- Raw Source: 00_Raw/2026-04-20/맞춤형 개별화 학습 설계.md --- diff --git a/01_Archive/2026-04-20/머리 장착형 디스플레이(HMD) 환경의 시각적 후유증 연구.md b/01_Archive/2026-04-20/머리 장착형 디스플레이(HMD) 환경의 시각적 후유증 연구.md index 210b8c13..288adba1 100644 --- a/01_Archive/2026-04-20/머리 장착형 디스플레이(HMD) 환경의 시각적 후유증 연구.md +++ b/01_Archive/2026-04-20/머리 장착형 디스플레이(HMD) 환경의 시각적 후유증 연구.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-439852 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 머리 장착형 디스플레이(HMD) 환경의 시각적 후유증 연구" --- -# [[머리 장착형 디스플레이(HMD) 환경의 시각적 후유증 연구]] +# [[머리 장착형 디스플레이(HMD) 환경의 시각적 후유증 연구|머리 장착형 디스플레이(HMD) 환경의 시각적 후유증 연구]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 머리 장착형 디스플레이(HMD)를 사용하는 가상현실(VR) 환경은 사용자에게 메스꺼움이나 방향 감각 상실뿐만 아니라 깊이 인지와 관련된 시각적 후유증을 유발할 수 있습니다 [1, 2]. 특히 HMD 환경에서는 가까운 물체에 명확한 초점을 맞추는 데 필수적인 안구 운동인 폭주(convergence)와 조절(accommodation) 간의 충돌이 발생하여 시각적 불편함이 초래됩니다 [3, 4]. 관련 연구에 따르면 HMD 사용 직후 이러한 조절 및 폭주의 유의미한 변화가 나타나지만, 이는 VR 노출 시간(10분 및 50분)과는 무관하며 기기 사용 종료 후 40분이 지나면 기준치로 회복되는 비교적 단기적인 현상으로 확인되었습니다 [4-6]. @@ -22,11 +22,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 머리 장착형 디스플레 - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[폭주-조절 충돌(Vergence-Accommodation Conflict)]], [[VR 멀미(VR Sickness)]], [[깊이 지각(Depth Perception)]] -- **Projects/Contexts:** [[Beat Saber를 활용한 VR 엑서게임의 시각적 및 인지적 후유증 조사 연구]] +- **Related Topics:** [[폭주-조절 충돌(Vergence-accommodation conflict)|폭주-조절 충돌(Vergence-Accommodation Conflict)]], [[VR 멀미 (VR Sickness)|VR 멀미(VR Sickness)]], [[깊이 지각 (Depth Perception)|깊이 지각(Depth Perception)]] +- **Projects/Contexts:** Beat Saber를 활용한 VR 엑서게임의 시각적 및 인지적 후유증 조사 연구 - **Contradictions/Notes:** 소스에 따르면 HMD 사용 직후 사용자의 조절과 폭주 등 안구 운동 기능에 큰 변화가 발생하여 피로와 복시 등을 유발할 수 있지만, 이러한 시각적 후유증의 크기는 VR 노출 시간(10분 노출과 50분 노출)에 영향을 받지 않았으며 기기 사용 종료 후 40분 이내에 사용 전 상태로 회복되는 것으로 나타났습니다 [4-6]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/머리 장착형 디스플레이(HMD) 환경의 시각적 후유증 연구.md]] +- Raw Source: 00_Raw/2026-04-20/머리 장착형 디스플레이(HMD) 환경의 시각적 후유증 연구.md --- diff --git a/01_Archive/2026-04-20/머리 착용 디스플레이(HMD) 시각 연구.md b/01_Archive/2026-04-20/머리 착용 디스플레이(HMD) 시각 연구.md index 806dac25..642bbb6f 100644 --- a/01_Archive/2026-04-20/머리 착용 디스플레이(HMD) 시각 연구.md +++ b/01_Archive/2026-04-20/머리 착용 디스플레이(HMD) 시각 연구.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-C33D02 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 머리 착용 디스플레이(HMD) 시각 연구" --- -# [[머리 착용 디스플레이(HMD) 시각 연구]] +# [[머리 착용 디스플레이(HMD) 시각 연구|머리 착용 디스플레이(HMD) 시각 연구]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -24,11 +24,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 머리 착용 디스플레이( - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[수렴-조절 불일치(Vergence-Accommodation Conflict)]], [[VR 멀미(VR Sickness)]], [[깊이 지각(Depth Perception)]], [[안구 운동 기능(Oculomotor Functions)]] -- **Projects/Contexts:** [[비트 세이버(Beat Saber) VR 엑서게임 연구]] +- **Related Topics:** [[수렴-조절 불일치(Vergence-Accommodation Conflict)|수렴-조절 불일치(Vergence-Accommodation Conflict)]], [[VR 멀미 (VR Sickness)|VR 멀미(VR Sickness)]], [[깊이 지각 (Depth Perception)|깊이 지각(Depth Perception)]], [[안구 운동 기능 (Oculomotor Functions)|안구 운동 기능(Oculomotor Functions)]] +- **Projects/Contexts:** [[비트 세이버(Beat Saber) VR 엑서게임 연구|비트 세이버(Beat Saber) VR 엑서게임 연구]] - **Contradictions/Notes:** 소스에 따르면 HMD 사용 시간에 비례하여 시각적 후유증이 계속 증가할 것이라는 직관적 예상과 달리, 노출 시간(10분 vs 50분)은 조절 및 수렴 척도 변화 크기에 유의미한 영향을 미치지 않았으며 변화는 초기 10분 내에 이루어짐을 보여줍니다 [3]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/머리 착용 디스플레이(HMD) 시각 연구.md]] +- Raw Source: 00_Raw/2026-04-20/머리 착용 디스플레이(HMD) 시각 연구.md --- diff --git a/01_Archive/2026-04-20/메모리 누수(Memory Leak).md b/01_Archive/2026-04-20/메모리 누수(Memory Leak).md index 3f5f4c92..7de91195 100644 --- a/01_Archive/2026-04-20/메모리 누수(Memory Leak).md +++ b/01_Archive/2026-04-20/메모리 누수(Memory Leak).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-80BFE5 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 메모리 누수(Memory Leak)" --- -# [[메모리 누수(Memory Leak)]] +# [[메모리 누수(Memory Leak)|메모리 누수(Memory Leak)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 메모리 누수(Memory Leak)는 더 이상 필요하지 않은 객체가 가비지 컬렉션(GC) 루트(예: 전역 객체, 클로저, 이벤트 리스너 등)로부터 지속적으로 참조되어 시스템이 메모리를 회수할 수 없는 상태를 의미합니다 [1-3]. 애플리케이션이 장시간 실행되면서 가용 메모리가 점진적으로 고갈되며 성능 저하, 긴 GC 일시 정지(Pause), 그리고 결국 OOM(Out of Memory) 충돌을 일으키게 됩니다 [2, 4, 5]. V8과 같은 엔진은 자동으로 메모리를 관리하지만, 개발자가 의도치 않게 남겨둔 참조로 인해 메모리 누수가 발생하므로 힙 스냅샷이나 할당 타임라인(Allocation Timeline) 등의 프로파일링 도구를 통해 세밀하게 추적해야 합니다 [1, 3, 6, 7]. @@ -20,11 +20,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 메모리 누수(Memory Leak)" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[가비지 컬렉션(Garbage Collection)]], [[할당 타임라인(Allocation Timeline)]], [[힙 스냅샷(Heap Snapshot)]], [[Old Space]] -- **Projects/Contexts:** [[Chrome DevTools 메모리 분석 및 성능 최적화]], [[V8 엔진 힙 아키텍처 및 로그 분석]] +- **Related Topics:** [[가비지 컬렉션(Garbage Collection)|가비지 컬렉션(Garbage Collection)]], [[할당 타임라인(Allocation Timeline)|할당 타임라인(Allocation Timeline)]], [[힙 스냅샷(Heap Snapshot)|힙 스냅샷(Heap Snapshot)]], [[Old Space|Old Space]] +- **Projects/Contexts:** [[Chrome DevTools 메모리 분석 및 성능 최적화|Chrome DevTools 메모리 분석 및 성능 최적화]], [[V8 엔진 힙 아키텍처 및 로그 분석|V8 엔진 힙 아키텍처 및 로그 분석]] - **Contradictions/Notes:** `WeakRef` 및 `FinalizationRegistry`는 누수 방지를 위한 모던 도구이지만, GC의 실행 시점이 비결정적이므로 적절한 생명주기 관리를 완전히 대체할 수는 없습니다 [11]. 또한, 크기가 계속 커지는 모든 메모리 그래프가 누수인 것은 아니며, 캐시나 가상화된 리스트 버퍼 등 의도적인 데이터 보존(Intentional retention)과 구별해야 합니다 [26]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/메모리 누수(Memory Leak).md]] +- Raw Source: 00_Raw/2026-04-20/메모리 누수(Memory Leak).md --- diff --git a/01_Archive/2026-04-20/메모리 누수(Memory Leaks).md b/01_Archive/2026-04-20/메모리 누수(Memory Leaks).md index 886234be..53df756d 100644 --- a/01_Archive/2026-04-20/메모리 누수(Memory Leaks).md +++ b/01_Archive/2026-04-20/메모리 누수(Memory Leaks).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-2F9E62 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 메모리 누수(Memory Leaks)" --- -# [[메모리 누수(Memory Leaks)]] +# [[메모리 누수(Memory Leaks)|메모리 누수(Memory Leaks)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 가비지 컬렉션 환경에서의 메모리 누수는 개발자가 더 이상 필요로 하지 않는 객체들이 가비지 컬렉션(GC) 루트로부터 여전히 참조되고 있어 메모리가 해제되지 않는 현상을 의미한다 [1-4]. 이러한 현상은 애플리케이션의 메모리 사용량을 점진적으로 증가시키며, 결과적으로 잦은 GC 실행에 따른 성능 저하와 메모리 부족(OOM) 크래시를 유발한다 [5, 6]. 일반적인 메모리 유실과 달리, 자바스크립트에서의 메모리 누수는 기본적으로 코드 어딘가에 남아있는 원치 않는 참조 때문에 발생한다 [1, 4]. @@ -31,11 +31,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 메모리 누수(Memory Leaks) - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[가비지 컬렉션(Garbage Collection)]], [[V8 Heap Architecture]], [[힙 스냅샷(Heap Snapshot)]], [[클로저(Closure)]] -- **Projects/Contexts:** [[Node.js Memory Leaks in Production]], [[Browser Memory Leak Detection]] +- **Related Topics:** [[가비지 컬렉션(Garbage Collection)|가비지 컬렉션(Garbage Collection)]], [[V8 Heap Architecture|V8 Heap Architecture]], [[힙 스냅샷(Heap Snapshot)|힙 스냅샷(Heap Snapshot)]], 클로저(Closure) +- **Projects/Contexts:** Node.js Memory Leaks in Production, [[브라우저 메모리 누수 탐지(Browser Memory Leak Detection)|Browser Memory Leak Detection]] - **Contradictions/Notes:** C/C++ 프로그램 등에 사용되는 컴파일러 지원이 없는 보수적(Conservative) 가비지 컬렉터의 경우, 포인터처럼 보이는 일반 정수 데이터로 인해 거대한 객체 서브그래프가 유지되는 독특한 형태의 메모리 누수를 유발할 가능성이 존재한다고 소스에서 지적한다 [32]. 또한 프론트엔드 최신 도구인 `WeakRef`와 `FinalizationRegistry`를 사용해 누수에 강한 패턴을 작성할 수 있으나, 가비지 컬렉터는 자체 일정에 따라 실행되어 결정론적이지 않으므로 적절한 객체 수명 주기 관리를 완벽히 대체할 수는 없음에 유의해야 한다 [12]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/메모리 누수(Memory Leaks).md]] +- Raw Source: 00_Raw/2026-04-20/메모리 누수(Memory Leaks).md --- diff --git a/01_Archive/2026-04-20/메모리 단편화(Fragmentation).md b/01_Archive/2026-04-20/메모리 단편화(Fragmentation).md index 9aeb9512..eef59ce8 100644 --- a/01_Archive/2026-04-20/메모리 단편화(Fragmentation).md +++ b/01_Archive/2026-04-20/메모리 단편화(Fragmentation).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-4BA757 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 메모리 단편화(Fragmentation)" --- -# [[메모리 단편화(Fragmentation)]] +# [[메모리 단편화(Fragmentation)|메모리 단편화(Fragmentation)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -25,11 +25,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 메모리 단편화(Fragmentat - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[가비지 컬렉션(Garbage Collection)]], [[메모리 압축(Compaction)]] -- **Projects/Contexts:** [[V8 자바스크립트 엔진(V8 JavaScript Engine)]], [[Eclipse OpenJ9]] +- **Related Topics:** [[가비지 컬렉션(Garbage Collection)|가비지 컬렉션(Garbage Collection)]], 메모리 압축(Compaction) +- **Projects/Contexts:** V8 자바스크립트 엔진(V8 JavaScript Engine), Eclipse OpenJ9 - **Contradictions/Notes:** 소스 전반에서 압축(Compaction)은 메모리 단편화를 해결하는 가장 확실한 방법으로 묘사되나, 그에 수반되는 참조 포인터 업데이트 연산 때문에 성능 오버헤드가 큰 비싼 작업(expensive operation)임이 일관되게 강조되고 있습니다[3, 6]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/메모리 단편화(Fragmentation).md]] +- Raw Source: 00_Raw/2026-04-20/메모리 단편화(Fragmentation).md --- diff --git a/01_Archive/2026-04-20/메모리 파편화 방지 및 객체 풀링 (Object Pooling).md b/01_Archive/2026-04-20/메모리 파편화 방지 및 객체 풀링 (Object Pooling).md index 652eb423..16e93feb 100644 --- a/01_Archive/2026-04-20/메모리 파편화 방지 및 객체 풀링 (Object Pooling).md +++ b/01_Archive/2026-04-20/메모리 파편화 방지 및 객체 풀링 (Object Pooling).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-4FD94E -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 메모리 파편화 방지 및 객체 풀링 (Object Pooling)" --- -# [[메모리 파편화 방지 및 객체 풀링 (Object Pooling)]] +# [[메모리 파편화 방지 및 객체 풀링 (Object Pooling)|메모리 파편화 방지 및 객체 풀링 (Object Pooling)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - 메모리 파편화 방지 및 ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/메모리 파편화 방지 및 객체 풀링 (Object Pooling).md]] +- Raw Source: 00_Raw/2026-04-20/메모리 파편화 방지 및 객체 풀링 (Object Pooling).md --- diff --git a/01_Archive/2026-04-20/명령형 직접 조작 (Imperative Manipulation).md b/01_Archive/2026-04-20/명령형 직접 조작 (Imperative Manipulation).md index 3196719b..9d2c86e6 100644 --- a/01_Archive/2026-04-20/명령형 직접 조작 (Imperative Manipulation).md +++ b/01_Archive/2026-04-20/명령형 직접 조작 (Imperative Manipulation).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-2E3155 -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 명령형 직접 조작 (Imperative Manipulation)" --- -# [[명령형 직접 조작 (Imperative Manipulation)]] +# [[명령형 직접 조작 (Imperative Manipulation)|명령형 직접 조작 (Imperative Manipulation)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - 명령형 직접 조작 (Imper ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/명령형 직접 조작 (Imperative Manipulation).md]] +- Raw Source: 00_Raw/2026-04-20/명령형 직접 조작 (Imperative Manipulation).md --- diff --git a/01_Archive/2026-04-20/명목적 타이핑 (Nominal Typing).md b/01_Archive/2026-04-20/명목적 타이핑 (Nominal Typing).md index 7c5b6ebb..d8d44789 100644 --- a/01_Archive/2026-04-20/명목적 타이핑 (Nominal Typing).md +++ b/01_Archive/2026-04-20/명목적 타이핑 (Nominal Typing).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-129F01 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 명목적 타이핑 (Nominal Typing)" --- -# [[명목적 타이핑 (Nominal Typing)]] +# [[명목적 타이핑 (Nominal Typing)|명목적 타이핑 (Nominal Typing)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 명목적 타이핑(Nominal Typing)은 객체의 실제 형태나 구조와 상관없이 타입의 이름이나 명시적 선언이 일치해야만 호환성을 인정하는 타입 시스템 방식이다 [1, 2]. TypeScript는 기본적으로 구조적 타이핑을 사용하기 때문에 명목적 타이핑을 내장 기능으로 지원하지 않지만, Java나 C# 같은 전통적인 객체 지향 언어에서는 기본 방식으로 사용된다 [1-3]. TypeScript 환경에서는 의미적으로 다른 데이터를 안전하게 구분하기 위해 '브랜디드 타입(Branded Types)' 패턴을 사용하여 명목적 타이핑의 효과를 흉내 낸다 [3-5]. @@ -27,11 +27,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 명목적 타이핑 (Nominal T - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[구조적 타이핑 (Structural Typing)]], [[브랜디드 타입 (Branded Types)]], [[기본 타입에의 집착 (Primitive Obsession)]] -- **Projects/Contexts:** [[도메인 기반 설계 (DDD) 및 데이터 오염 방지]], [[TypeScript의 안전한 인터페이스 설계]] +- **Related Topics:** [[구조적 타이핑 (Structural Typing)|구조적 타이핑 (Structural Typing)]], [[브랜디드 타입 (Branded Types)|브랜디드 타입 (Branded Types)]], [[기본 타입에의 집착 (Primitive Obsession)|기본 타입에의 집착 (Primitive Obsession)]] +- **Projects/Contexts:** [[도메인 기반 설계 (DDD) 및 데이터 오염 방지|도메인 기반 설계 (DDD) 및 데이터 오염 방지]], [[TypeScript의 안전한 인터페이스 설계|TypeScript의 안전한 인터페이스 설계]] - **Contradictions/Notes:** Java나 C#과 같은 언어는 명목적 타이핑을 기본 언어 차원에서 제공하지만, TypeScript는 이를 내장하고 있지 않으므로 [1-3], 명목적 타이핑의 이점을 누리기 위해서는 개발자가 교집합 타입(`&`)이나 `unique symbol` 등을 활용하여 인위적인 패턴(브랜디드 타입)을 구현해야만 한다 [7, 8]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/명목적 타이핑 (Nominal Typing).md]] +- Raw Source: 00_Raw/2026-04-20/명목적 타이핑 (Nominal Typing).md --- diff --git a/01_Archive/2026-04-20/명목적 타이핑(Nominal Typing).md b/01_Archive/2026-04-20/명목적 타이핑(Nominal Typing).md index ca6812fb..6fd12098 100644 --- a/01_Archive/2026-04-20/명목적 타이핑(Nominal Typing).md +++ b/01_Archive/2026-04-20/명목적 타이핑(Nominal Typing).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-DCF544 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 명목적 타이핑(Nominal Typing)" --- -# [[명목적 타이핑(Nominal Typing)]] +# [[명목적 타이핑(Nominal Typing)|명목적 타이핑(Nominal Typing)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 명목적 타이핑(Nominal Typing)은 타입의 이름이나 명시적 선언이 일치해야만 호환성을 인정하는 타입 시스템 방식입니다 [1, 2]. 이는 객체의 실제 형태나 구조를 기준으로 타입을 결정하는 구조적 타이핑(Structural Typing)과 대비되는 개념으로, Java나 C#과 같은 전통적인 객체 지향 언어에서 주로 사용됩니다 [1, 2]. TypeScript는 구조적 타이핑을 따르지만, 명목적 타이핑의 엄격한 데이터 구분 효과를 얻기 위해 '브랜디드 타입(Branded Types)' 또는 '불투명 타입(Opaque Types)'과 같은 패턴을 활용합니다 [3-5]. @@ -23,11 +23,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 명목적 타이핑(Nominal Ty - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[구조적 타이핑(Structural Typing)]], [[브랜디드 타입(Branded Types)]], [[불투명 타입(Opaque Types)]] -- **Projects/Contexts:** [[도메인 기반 설계(DDD)]], [[Effect TS]] +- **Related Topics:** [[구조적 타이핑(Structural Typing)|구조적 타이핑(Structural Typing)]], [[브랜디드 타입(Branded Types)|브랜디드 타입(Branded Types)]], 불투명 타입(Opaque Types) +- **Projects/Contexts:** [[도메인 기반 설계(DDD)|도메인 기반 설계(DDD)]], [[Effect TS|Effect TS]] - **Contradictions/Notes:** TypeScript 커뮤니티에서 명목적(비구조적) 타입 매칭을 네이티브로 지원하는 것에 대한 논의가 2014년부터 꾸준히 있었으나 아직 완전한 합의나 내장 기능이 추가되지는 않았으며, 대신 개발자들은 고유 심볼(unique symbol)이나 런타임 유효성 검사(Zod 등)를 결합하여 이를 우회적으로 달성하고 있습니다 [3, 13, 14]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/명목적 타이핑(Nominal Typing).md]] +- Raw Source: 00_Raw/2026-04-20/명목적 타이핑(Nominal Typing).md --- diff --git a/01_Archive/2026-04-20/모노레포(Monorepo) 기반 구성 중앙화.md b/01_Archive/2026-04-20/모노레포(Monorepo) 기반 구성 중앙화.md index 9bb0035f..e7d6132b 100644 --- a/01_Archive/2026-04-20/모노레포(Monorepo) 기반 구성 중앙화.md +++ b/01_Archive/2026-04-20/모노레포(Monorepo) 기반 구성 중앙화.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-796BD7 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 모노레포(Monorepo) 기반 구성 중앙화" --- -# [[모노레포(Monorepo) 기반 구성 중앙화]] +# [[모노레포(Monorepo) 기반 구성 중앙화|모노레포(Monorepo) 기반 구성 중앙화]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 모노레포(Monorepo) 기반 구성 중앙화란 다수의 애플리케이션과 라이브러리가 존재하는 대규모 저장소에서 ESLint나 Prettier와 같은 도구의 설정 파일 중복을 제거하고 단일 진실 공급원(Single source of truth)을 마련하는 아키텍처 패턴입니다 [1], [2]. 중앙화된 설정 패키지를 구축하고 이를 루트 레벨에서 오케스트레이션하여 공통 규칙을 전역적으로 관리함과 동시에 패키지 고유의 자율성을 유지합니다 [3]. 이를 통해 코드의 유지보수성을 극대화하고 개발 환경의 일관성 및 검사 속도를 크게 향상시킵니다 [4]. @@ -28,11 +28,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 모노레포(Monorepo) 기반 - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[ESLint]], [[Prettier]], [[lint-staged]], [[Turborepo]] -- **Projects/Contexts:** [[대규모 모노레포 환경의 린팅 및 포매팅 설정 현대화 프로젝트]] +- **Related Topics:** [[ESLint|ESLint]], [[Prettier|Prettier]], [[lint-staged|lint-staged]], [[Turborepo|Turborepo]] +- **Projects/Contexts:** 대규모 모노레포 환경의 린팅 및 포매팅 설정 현대화 프로젝트 - **Contradictions/Notes:** 공식적인 `lint-staged` 모노레포 가이드에서는 최상위에 `lint-staged`를 설치하고 각 패키지마다 별도의 구성 파일을 두어 고립되게 처리하라고 안내하며 루트 설정이 하위 설정을 자동으로 채워주지 않는다고 명시하지만 [11], 루트 오케스트레이션 구성을 도입하면 최상위에서 실행하면서도 패턴 매핑을 통해 각 패키지의 규칙을 성공적으로 병합·제어할 수 있습니다 [8], [12]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/모노레포(Monorepo) 기반 구성 중앙화.md]] +- Raw Source: 00_Raw/2026-04-20/모노레포(Monorepo) 기반 구성 중앙화.md --- diff --git a/01_Archive/2026-04-20/모노레포(Monorepo) 설정 중앙화.md b/01_Archive/2026-04-20/모노레포(Monorepo) 설정 중앙화.md index bc8273d4..99fb89d4 100644 --- a/01_Archive/2026-04-20/모노레포(Monorepo) 설정 중앙화.md +++ b/01_Archive/2026-04-20/모노레포(Monorepo) 설정 중앙화.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-19D53A -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 모노레포(Monorepo) 설정 중앙화" --- -# [[모노레포(Monorepo) 설정 중앙화]] +# [[모노레포(Monorepo) 설정 중앙화|모노레포(Monorepo) 설정 중앙화]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 모노레포(Monorepo) 설정 중앙화는 대규모 프로젝트 내 여러 패키지에 분산되어 있는 코드 컨벤션(ESLint, Prettier 등) 설정을 단일 핵심 패키지로 통합하고 관리하는 아키텍처입니다 [1-3]. 이를 통해 조직 내 코드 품질 규칙의 단일 진실 공급원(Single Source of Truth)을 구축하여 설정 파편화를 방지합니다 [3, 4]. 결과적으로 전역적인 규칙 업데이트를 용이하게 하고, 중복을 제거하여 린팅 검사 및 유지보수 효율을 극대화합니다 [3, 5]. @@ -36,11 +36,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 모노레포(Monorepo) 설정 - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[ESLint]], [[Prettier]], [[Turborepo]], [[Husky]], [[lint-staged]] -- **Projects/Contexts:** [[대규모 모노레포(Monorepo) 프로젝트]], [[다중 패키지 관리 환경]] +- **Related Topics:** [[ESLint|ESLint]], [[Prettier|Prettier]], [[Turborepo|Turborepo]], [[Husky|Husky]], [[lint-staged|lint-staged]] +- **Projects/Contexts:** 대규모 모노레포(Monorepo) 프로젝트, 다중 패키지 관리 환경 - **Contradictions/Notes:** 모노레포 환경에서 `lint-staged`를 적용하는 구조와 관련하여 다른 관점이 존재합니다. 일반적인 가이드에서는 패키지 간의 격리성 확보를 위해 각 패키지별로 독립된 설정 파일을 둘 것을 권장하지만 [14, 15], Turborepo를 활용하는 모노레포 환경에서는 최상위에서 '루트 오케스트레이션(Root Orchestration)'을 통해 파일 패턴으로 린팅을 중앙 제어하는 것이 중복 제거와 일관성 면에서 더 효과적인 해결책으로 제시되고 있습니다 [6, 9, 16]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/모노레포(Monorepo) 설정 중앙화.md]] +- Raw Source: 00_Raw/2026-04-20/모노레포(Monorepo) 설정 중앙화.md --- diff --git a/01_Archive/2026-04-20/모노레포(Monorepo) 아키텍처 설정.md b/01_Archive/2026-04-20/모노레포(Monorepo) 아키텍처 설정.md index 841baa1a..519c8549 100644 --- a/01_Archive/2026-04-20/모노레포(Monorepo) 아키텍처 설정.md +++ b/01_Archive/2026-04-20/모노레포(Monorepo) 아키텍처 설정.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-671D24 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 모노레포(Monorepo) 아키텍처 설정" --- -# [[모노레포(Monorepo) 아키텍처 설정]] +# [[모노레포(Monorepo) 아키텍처 설정|모노레포(Monorepo) 아키텍처 설정]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 모노레포(Monorepo) 아키텍처 설정은 여러 애플리케이션과 라이브러리가 공존하는 대규모 프로젝트 환경에서 ESLint, Prettier, Husky, lint-staged 등의 도구들을 효율적으로 구성하고 관리하는 방법론입니다 [1-3]. 중복된 설정 파일로 인한 관리의 어려움을 피하기 위해 중앙 집중식 설정 패키지와 루트 오케스트레이션(Root Orchestration)을 도입하여 단일 진실 공급원(Single source of truth)을 형성합니다 [2-4]. 이를 통해 패키지별 자율성을 유지하면서도 전역적인 코드 품질 규칙을 일관되고 빠르게 강제할 수 있습니다 [4, 5]. @@ -32,11 +32,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 모노레포(Monorepo) 아키 - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Turborepo]], [[ESLint]], [[Prettier]], [[Husky]], [[lint-staged]] -- **Projects/Contexts:** [[Next.js 애플리케이션 및 라이브러리 관리]], [[모노레포 린트 자동화]] +- **Related Topics:** [[Turborepo|Turborepo]], [[ESLint|ESLint]], [[Prettier|Prettier]], [[Husky|Husky]], [[lint-staged|lint-staged]] +- **Projects/Contexts:** Next.js 애플리케이션 및 라이브러리 관리, 모노레포 린트 자동화 - **Contradictions/Notes:** 소스 [10]에 따르면 `lint-staged`의 공식 지침은 여러 하위 패키지의 구성 파일을 상호 격리된 상태로 취급하여 가장 가까운 파일을 적용하라고 설명하지만, 소스 [3, 8, 12]에서는 단일 진실 공급원을 기반으로 루트에서 파일 패턴을 매핑해주는 루트 오케스트레이션(Root Orchestration) 방식이 유지보수와 실행 속도 면에서 모노레포에 더 뛰어난 해결책이라고 주장합니다. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/모노레포(Monorepo) 아키텍처 설정.md]] +- Raw Source: 00_Raw/2026-04-20/모노레포(Monorepo) 아키텍처 설정.md --- diff --git a/01_Archive/2026-04-20/모놀리식 아키텍처 (Monolithic Architecture).md b/01_Archive/2026-04-20/모놀리식 아키텍처 (Monolithic Architecture).md index e8d0bd3b..b783ed0f 100644 --- a/01_Archive/2026-04-20/모놀리식 아키텍처 (Monolithic Architecture).md +++ b/01_Archive/2026-04-20/모놀리식 아키텍처 (Monolithic Architecture).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-C46007 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 모놀리식 아키텍처 (Monolithic Architecture)" --- -# [[모놀리식 아키텍처 (Monolithic Architecture)]] +# [[모놀리식 아키텍처 (Monolithic Architecture)|모놀리식 아키텍처 (Monolithic Architecture)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 모놀리식 아키텍처는 애플리케이션의 모든 기능이 단일하고 강하게 결합된 단위로 구축되는 전통적인 소프트웨어 설계 방식입니다 [1]. 개발자 팀이 소규모일 경우 협의를 통해 채택하기 적합한 구조이며, 대규모 엔터프라이즈 시스템을 구축하는 데에도 역사적으로 널리 사용되어 왔습니다 [2, 3]. 그러나 시스템 규모가 커짐에 따라 새로운 기능의 배포가 지연되고 유지보수가 어려워지는 한계가 있어, 현대에는 마이크로서비스 아키텍처 등으로 전환되는 추세입니다 [1, 4, 5]. @@ -23,11 +23,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 모놀리식 아키텍처 (Mon - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[마이크로서비스 아키텍처 (Microservices Architecture)]], [[X축 스케일링 (X-Axis Scaling)]] -- **Projects/Contexts:** [[넷플릭스 (Netflix)]], [[스포티파이 (Spotify)]] +- **Related Topics:** [[마이크로서비스 아키텍처 (Microservices Architecture)|마이크로서비스 아키텍처 (Microservices Architecture)]], X축 스케일링 (X-Axis Scaling) +- **Projects/Contexts:** 넷플릭스 (Netflix), 스포티파이 (Spotify) - **Contradictions/Notes:** 소스에 따르면 대규모 엔터프라이즈 시스템을 모놀리식 구조로 구축하는 것이 가능하다고 증명되어 있지만 [3], 실제 급격히 성장하는 기업(넷플릭스 등)의 사례에서는 규모 확장에 따른 기능 전달 지연 및 유지보수 문제를 해결하기 위해 모놀리식 아키텍처를 포기하고 마이크로서비스 아키텍처로 전환(Migration)하는 한계를 보입니다 [4, 5]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/모놀리식 아키텍처 (Monolithic Architecture).md]] +- Raw Source: 00_Raw/2026-04-20/모놀리식 아키텍처 (Monolithic Architecture).md --- diff --git a/01_Archive/2026-04-20/모듈러 통합 건설 (MiC).md b/01_Archive/2026-04-20/모듈러 통합 건설 (MiC).md index 9567de14..aacfa9c5 100644 --- a/01_Archive/2026-04-20/모듈러 통합 건설 (MiC).md +++ b/01_Archive/2026-04-20/모듈러 통합 건설 (MiC).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-FE2B8A -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 모듈러 통합 건설 (MiC)" --- -# [[모듈러 통합 건설 (MiC)]] +# [[모듈러 통합 건설 (MiC)|모듈러 통합 건설 (MiC)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 모듈러 통합 건설(MiC)은 전통적인 현장 시공 방식에서 벗어나, 건축물을 독립적인 모듈로 나누어 공장에서 사전 제작한 뒤 현장에서 조립하는 혁신적인 건설 기술입니다[1]. 이 방식은 통제된 공장 환경에서 제작이 이루어지므로 기존 건설 방식에 비해 더 안전하고 환경에 미치는 영향이 적으며, 품질 제어 및 공기 단축에 매우 유리합니다[1, 2]. 건설 산업 내 숙련된 노동력 부족 문제를 해결하고 지속 가능한 발전을 지원하는 게임 체인저로 평가받고 있습니다[1, 2]. @@ -24,11 +24,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 모듈러 통합 건설 (MiC)" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[관심사의 분리 (SoC)]], [[모듈러 철골 건물 (MSB)]] -- **Projects/Contexts:** [[화신산 병원 (Huoshen Mountain Hospital)]] (코로나19 팬데믹 당시 모듈러 설계 및 조립 기술을 활용하여 단기간에 고품질로 구축된 응급 병원 프로젝트[1, 4]) +- **Related Topics:** [[관심사의 분리 (SoC)|관심사의 분리 (SoC)]], 모듈러 철골 건물 (MSB) +- **Projects/Contexts:** 화신산 병원 (Huoshen Mountain Hospital) (코로나19 팬데믹 당시 모듈러 설계 및 조립 기술을 활용하여 단기간에 고품질로 구축된 응급 병원 프로젝트[1, 4]) - **Contradictions/Notes:** 소스에 관련 정보가 부족합니다. (제공된 소스 내에서 모듈러 통합 건설에 대한 상반된 주장이나 모순점은 발견되지 않습니다.) --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/모듈러 통합 건설 (MiC).md]] +- Raw Source: 00_Raw/2026-04-20/모듈러 통합 건설 (MiC).md --- diff --git a/01_Archive/2026-04-20/모듈화 및 아키텍처 경계 설정.md b/01_Archive/2026-04-20/모듈화 및 아키텍처 경계 설정.md index 2e68fb0d..a3f13ae3 100644 --- a/01_Archive/2026-04-20/모듈화 및 아키텍처 경계 설정.md +++ b/01_Archive/2026-04-20/모듈화 및 아키텍처 경계 설정.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-1ED3D4 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 모듈화 및 아키텍처 경계 설정" --- -# [[모듈화 및 아키텍처 경계 설정]] +# [[모듈화 및 아키텍처 경계 설정|모듈화 및 아키텍처 경계 설정]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 모듈화는 복잡한 소프트웨어 시스템을 작고 독립적이며 관리가 용이한 부분(모듈)으로 나누는 설계 기법이다 [1]. 아키텍처 경계 설정은 이러한 모듈 간의 책임과 상호작용을 통제하기 위해 명확한 선을 긋는 과정으로, 핵심 비즈니스 로직과 외부 세부 사항을 격리하는 역할을 한다 [2, 3]. 이를 통해 시스템은 높은 응집도와 낮은 결합도를 유지하게 되며, 특정 요소의 변경이 다른 부분에 미치는 영향을 최소화하여 유지보수성, 재사용성 및 테스트 용이성을 크게 향상시킬 수 있다 [1, 4, 5]. @@ -30,11 +30,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 모듈화 및 아키텍처 경 - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[관심사의 분리(SoC)]], [[클린 아키텍처(Clean Architecture)]], [[응집도와 결합도]], [[의존성 역전 원칙(DIP)]], [[단일 책임 원칙(SRP)]] -- **Projects/Contexts:** [[넷플릭스 코스모스(Netflix Cosmos) 플랫폼]], [[마이크로 프론트엔드(Micro Frontends)]], [[스포티파이 스쿼드(Spotify Squad) 모델]], [[모듈러 통합 건설(MiC)]] +- **Related Topics:** [[관심사의 분리(SoC)|관심사의 분리(SoC)]], [[클린 아키텍처(Clean Architecture)|클린 아키텍처(Clean Architecture)]], [[응집도와 결합도|응집도와 결합도]], [[의존성 역전 원칙 (DIP)|의존성 역전 원칙(DIP)]], [[단일 책임 원칙(SRP)|단일 책임 원칙(SRP)]] +- **Projects/Contexts:** 넷플릭스 코스모스(Netflix Cosmos) 플랫폼, [[마이크로 프론트엔드 (Micro Frontends)|마이크로 프론트엔드(Micro Frontends)]], 스포티파이 스쿼드(Spotify Squad) 모델, [[모듈러 통합 건설 (MiC)|모듈러 통합 건설(MiC)]] - **Contradictions/Notes:** 완벽한 아키텍처 경계를 선행적으로 구축하는 것은 상당한 노력과 비용이 들기 때문에, 당장 필요하지 않은 오버 엔지니어링(YAGNI 원칙 위배)으로 간주되어 일부 개발자들의 거부감을 일으킬 수 있다. 하지만 경계가 없는 상태에서 나중에 횡단 관심사 문제를 겪고 나서야 뒤늦게 경계를 추가하려고 하면, 훨씬 더 높은 비용과 위험을 감수해야 한다는 딜레마가 존재한다 [19, 23]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/모듈화 및 아키텍처 경계 설정.md]] +- Raw Source: 00_Raw/2026-04-20/모듈화 및 아키텍처 경계 설정.md --- diff --git a/01_Archive/2026-04-20/모바일 기반 WebGL 애플리케이션 개발.md b/01_Archive/2026-04-20/모바일 기반 WebGL 애플리케이션 개발.md index 97afdd1f..6ae109b8 100644 --- a/01_Archive/2026-04-20/모바일 기반 WebGL 애플리케이션 개발.md +++ b/01_Archive/2026-04-20/모바일 기반 WebGL 애플리케이션 개발.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-18A5BC -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 모바일 기반 WebGL 애플리케이션 개발" --- -# [[모바일 기반 WebGL 애플리케이션 개발]] +# [[모바일 기반 WebGL 애플리케이션 개발|모바일 기반 WebGL 애플리케이션 개발]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 모바일 기반 WebGL 애플리케이션 개발은 상대적으로 부족한 시스템 메모리와 프로세서 성능을 지닌 모바일 브라우저 환경에서 매끄러운 3D 렌더링(60fps)을 구현하고 배터리 소모를 최소화하는 데 중점을 두는 기술적 접근입니다. 제한된 하드웨어 리소스를 극복하기 위해 엄격한 폴리곤 수 및 드로우 콜(Draw Call) 제한, 텍스처 메모리 압축, 셰이더 정밀도 하향, 그리고 디바이스 특성을 고려한 전원 및 컨텍스트 관리 기법이 복합적으로 동원됩니다. @@ -37,11 +37,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 모바일 기반 WebGL 애플 - **정책 변화:** Graphics & Performance 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[드로우 콜 최적화(Draw Call Optimization)]], [[텍스처 압축 및 아틀라스(Texture Compression & Atlas)]], [[셰이더 정밀도 최적화(Shader Precision Optimization)]], [[가비지 컬렉션 관리(Garbage Collection Management)]] -- **Projects/Contexts:** [[Three.js WebGL 렌더링]], [[모바일 환경의 메모리 병목]] +- **Related Topics:** 드로우 콜 최적화(Draw Call Optimization), 텍스처 압축 및 아틀라스(Texture Compression & Atlas), 셰이더 정밀도 최적화(Shader Precision Optimization), 가비지 컬렉션 관리(Garbage Collection Management) +- **Projects/Contexts:** Three.js WebGL 렌더링, 모바일 환경의 메모리 병목 - **Contradictions/Notes:** 뼈대 텍스처의 부분 업데이트(partial texture updates)와 같은 특정 세부 렌더링 최적화 기법은 일부 모바일 기기와 Firefox 브라우저 환경에서는 오히려 속도를 느리게 만드는 부작용(역효과)이 보고되었습니다 [11, 12]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/모바일 기반 WebGL 애플리케이션 개발.md]] +- Raw Source: 00_Raw/2026-04-20/모바일 기반 WebGL 애플리케이션 개발.md --- diff --git a/01_Archive/2026-04-20/모바일 앱 및 웹 인터페이스 설계.md b/01_Archive/2026-04-20/모바일 앱 및 웹 인터페이스 설계.md index 7f6ed961..ae2b8329 100644 --- a/01_Archive/2026-04-20/모바일 앱 및 웹 인터페이스 설계.md +++ b/01_Archive/2026-04-20/모바일 앱 및 웹 인터페이스 설계.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-B1EC47 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 모바일 앱 및 웹 인터페이스 설계" --- -# [[모바일 앱 및 웹 인터페이스 설계]] +# [[모바일 앱 및 웹 인터페이스 설계|모바일 앱 및 웹 인터페이스 설계]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - 모바일 앱 및 웹 인터 ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/모바일 앱 및 웹 인터페이스 설계.md]] +- Raw Source: 00_Raw/2026-04-20/모바일 앱 및 웹 인터페이스 설계.md --- diff --git a/01_Archive/2026-04-20/몰입 (Flow Theory).md b/01_Archive/2026-04-20/몰입 (Flow Theory).md index 5c4d58c0..7918804f 100644 --- a/01_Archive/2026-04-20/몰입 (Flow Theory).md +++ b/01_Archive/2026-04-20/몰입 (Flow Theory).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-7D7420 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 몰입 (Flow Theory)" --- -# [[몰입 (Flow Theory)]] +# [[몰입 (Flow Theory)|몰입 (Flow Theory)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - 몰입 (Flow Theory)" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/몰입 (Flow Theory).md]] +- Raw Source: 00_Raw/2026-04-20/몰입 (Flow Theory).md --- diff --git a/01_Archive/2026-04-20/몰입감 (Presence).md b/01_Archive/2026-04-20/몰입감 (Presence).md index e552e2b2..fa2143e9 100644 --- a/01_Archive/2026-04-20/몰입감 (Presence).md +++ b/01_Archive/2026-04-20/몰입감 (Presence).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-589F08 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 몰입감 (Presence)" --- -# [[몰입감 (Presence)]] +# [[몰입감 (Presence)|몰입감 (Presence)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 몰입감(Presence)은 사용자가 가상 현실이나 전자 환경을 현실 세계보다 우선적으로 수용하여, 비물리적 세계에 실제로 "존재하는 것(being there)"처럼 느끼는 심리적 상태를 의미합니다 [1, 2]. 이는 가상현실(VR) 및 혼합현실(MR) 경험의 성공을 결정짓는 핵심 요소로, 사용자의 참여도, 몰입(Immersion), 그리고 학습 성과를 향상시킵니다 [3, 4]. 그러나 고도의 몰입감을 유지하는 것은 인지 부하(Cognitive Load)를 증가시킬 수 있으며, 사이버 멀미(VR sickness)와 같은 요인에 의해 쉽게 파괴될 수 있습니다 [3, 5]. @@ -30,11 +30,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 몰입감 (Presence)" - **정책 변화:** Design & Experience 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Flow State]], [[Cognitive Load]], [[Immersion]], [[Virtual Reality (VR)]] -- **Projects/Contexts:** [[Mixed Reality (MR) Tasks]], [[VR Exergaming]] +- **Related Topics:** [[Flow State|Flow State]], [[Cognitive_Load|Cognitive Load]], Immersion, Virtual Reality (VR) +- **Projects/Contexts:** Mixed Reality (MR) Tasks, VR Exergaming - **Contradictions/Notes:** 소스에 따르면 높은 수준의 가상 몰입감(Virtual Presence)은 학습 성과와 참여도를 긍정적으로 향상시키지만, 가상 콘텐츠를 처리하기 위한 정신적 노력이 요구되어 필연적으로 인지 부하(Cognitive Load)를 증가시킨다는 이중적 특성을 지닙니다 [3, 10]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/몰입감 (Presence).md]] +- Raw Source: 00_Raw/2026-04-20/몰입감 (Presence).md --- diff --git a/01_Archive/2026-04-20/무제.md b/01_Archive/2026-04-20/무제.md index afe88b10..4403ed2d 100644 --- a/01_Archive/2026-04-20/무제.md +++ b/01_Archive/2026-04-20/무제.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-D69A80 -category: "[[10_Wiki/💡 Topics/General Knowledge]]" +category: "10_Wiki/💡 Topics/General Knowledge" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 무제" --- -# [[무제]] +# [[무제|무제]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - 무제" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/무제.md]] +- Raw Source: 00_Raw/2026-04-20/무제.md --- diff --git a/01_Archive/2026-04-20/미디어 폭력과 공격성 연구.md b/01_Archive/2026-04-20/미디어 폭력과 공격성 연구.md index fab8f9a0..92073ea0 100644 --- a/01_Archive/2026-04-20/미디어 폭력과 공격성 연구.md +++ b/01_Archive/2026-04-20/미디어 폭력과 공격성 연구.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-7FB7BB -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 미디어 폭력과 공격성 연구" --- -# [[미디어 폭력과 공격성 연구]] +# [[미디어 폭력과 공격성 연구|미디어 폭력과 공격성 연구]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - 미디어 폭력과 공격성 ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/미디어 폭력과 공격성 연구.md]] +- Raw Source: 00_Raw/2026-04-20/미디어 폭력과 공격성 연구.md --- diff --git a/01_Archive/2026-04-20/바운디드 컨텍스트 (Bounded Context).md b/01_Archive/2026-04-20/바운디드 컨텍스트 (Bounded Context).md index 84ea82f6..41d78fd9 100644 --- a/01_Archive/2026-04-20/바운디드 컨텍스트 (Bounded Context).md +++ b/01_Archive/2026-04-20/바운디드 컨텍스트 (Bounded Context).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-7B2713 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 바운디드 컨텍스트 (Bounded Context)" --- -# [[바운디드 컨텍스트 (Bounded Context)]] +# [[바운디드 컨텍스트 (Bounded Context)|바운디드 컨텍스트 (Bounded Context)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 바운디드 컨텍스트(Bounded Context)는 도메인 주도 설계(DDD)에서 크고 복잡한 비즈니스 도메인을 더 작고 관리하기 쉬운 하위 도메인으로 분할한 단위를 의미합니다 [1, 2]. 각 컨텍스트는 고유한 소프트웨어 모델과 보편적 언어(Ubiquitous Language)를 가지며, 도메인의 논리를 캡슐화하여 서로 다른 책임 영역 간의 명확한 경계를 정의합니다 [1, 3]. 이를 통해 소프트웨어 모델을 순수하고 기능에 집중된 상태로 유지하며, 시스템의 복잡성을 효과적으로 관리할 수 있게 돕습니다 [1, 3]. @@ -23,11 +23,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 바운디드 컨텍스트 (Bou - **정책 변화:** Design & Experience 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[도메인 주도 설계 (Domain-Driven Design, DDD)]], [[보편적 언어 (Ubiquitous Language)]], [[마이크로서비스 아키텍처 (Microservices Architecture)]], [[관심사의 분리 (Separation of Concerns, SoC)]] +- **Related Topics:** [[도메인 주도 설계 (Domain-Driven Design, DDD)|도메인 주도 설계 (Domain-Driven Design, DDD)]], [[보편적 언어 (Ubiquitous Language)|보편적 언어 (Ubiquitous Language)]], [[마이크로서비스 아키텍처 (Microservices Architecture)|마이크로서비스 아키텍처 (Microservices Architecture)]], [[관심사의 분리 (Separation of Concerns, SoC)|관심사의 분리 (Separation of Concerns, SoC)]] - **Projects/Contexts:** 복잡한 비즈니스 도메인 모델링 [1], 객체 지향 및 모듈러 소프트웨어 시스템 설계 [3, 5], 마이크로서비스로의 서비스 분리 및 마이그레이션 [2] - **Contradictions/Notes:** 소스 내에 바운디드 컨텍스트의 효용이나 개념에 대한 상반된 주장은 존재하지 않으며, 일관되게 시스템 복잡성 완화와 마이크로서비스 확장을 위한 핵심 기반으로 설명되고 있습니다. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/바운디드 컨텍스트 (Bounded Context).md]] +- Raw Source: 00_Raw/2026-04-20/바운디드 컨텍스트 (Bounded Context).md --- diff --git a/01_Archive/2026-04-20/반응 시간(Reaction Time).md b/01_Archive/2026-04-20/반응 시간(Reaction Time).md index 7891a112..184c8d27 100644 --- a/01_Archive/2026-04-20/반응 시간(Reaction Time).md +++ b/01_Archive/2026-04-20/반응 시간(Reaction Time).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-9738CF -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 반응 시간(Reaction Time)" --- -# [[반응 시간(Reaction Time)]] +# [[반응 시간(Reaction Time)|반응 시간(Reaction Time)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 반응 시간(Reaction Time)은 특정 자극이 나타난 후 사용자가 이에 반응하여 움직임을 개시하고 목표를 터치하기까지 소요되는 시간을 의미합니다 [1]. 시각 및 인지적 후유증 연구에서 가상현실(VR) 노출이 사용자의 자극에 대한 빠른 반응 능력에 미치는 영향을 평가하는 핵심 지표로 활용됩니다 [2]. 일반적으로 인지적 요인인 결정 속도와 운동 요인인 이동 속도로 구분되어 분석되며, VR 경험이 반응 시간에 미치는 변화는 통상 50ms 미만으로 나타납니다 [1, 3]. @@ -22,11 +22,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 반응 시간(Reaction Time)" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[결정 속도(Decision Speed)]], [[가상현실 후유증(VR Aftereffects)]] -- **Projects/Contexts:** [[Beat Saber 엑서게임 연구(Beat Saber Exergaming Study)]], [[CANTAB 5-선택 반응 시간 과제(CANTAB 5-choice RTI)]] +- **Related Topics:** [[결정 속도(Decision Speed)|결정 속도(Decision Speed)]], [[가상현실 후유증(VR Aftereffects)|가상현실 후유증(VR Aftereffects)]] +- **Projects/Contexts:** [[Beat Saber 엑서게임 연구(Beat Saber Exergaming Study)|Beat Saber 엑서게임 연구(Beat Saber Exergaming Study)]], [[CANTAB 5-선택 반응 시간 과제(CANTAB 5-choice RTI)|CANTAB 5-선택 반응 시간 과제(CANTAB 5-choice RTI)]] - **Contradictions/Notes:** 가상현실 노출이 반응 시간에 미치는 즉각적인 영향에 대해 연구자마다 부정적인 후유증이 발생한다고 주장하는 연구와 오히려 긍정적인(빠른) 효과를 가져온다고 주장하는 연구가 혼재되어 문헌 간 일관성이 부족합니다 [3]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/반응 시간(Reaction Time).md]] +- Raw Source: 00_Raw/2026-04-20/반응 시간(Reaction Time).md --- diff --git a/01_Archive/2026-04-20/반응형 윈도우 리사이즈(Resize) 이벤트 처리.md b/01_Archive/2026-04-20/반응형 윈도우 리사이즈(Resize) 이벤트 처리.md index 8a5f4d8a..e78cf7b0 100644 --- a/01_Archive/2026-04-20/반응형 윈도우 리사이즈(Resize) 이벤트 처리.md +++ b/01_Archive/2026-04-20/반응형 윈도우 리사이즈(Resize) 이벤트 처리.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-DC2EFA -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 반응형 윈도우 리사이즈(Resize) 이벤트 처리" --- -# [[반응형 윈도우 리사이즈(Resize) 이벤트 처리]] +# [[반응형 윈도우 리사이즈(Resize) 이벤트 처리|반응형 윈도우 리사이즈(Resize) 이벤트 처리]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 윈도우 창 크기 조절 시 초당 수십 번씩 발생하는 `resize` 이벤트로 인한 UI 렌더링 병목 현상을 방지하기 위해, 디바운싱(Debouncing) 적용 및 이벤트 리스너 해제(Cleanup)를 통해 브라우저 과부하와 메모리 누수를 막는 성능 최적화 기법입니다. @@ -29,12 +29,12 @@ github_commit: "[P-Reinforce] Continuous Worker - 반응형 윈도우 리사이 - **정책 변화:** Design & Experience 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Throttling & Debouncing]], [[React Performance Optimization]], [[Memory Leak Prevention (메모리 누수 방지)]], [[useEffect 클린업(Cleanup)]] -- **Projects/Contexts:** [[반응형 3D 캔버스(Three.js/R3F) 크기 최적화]], [[실시간 데이터 대시보드 레이아웃 조절 시스템]] +- **Related Topics:** [[Throttling & Debouncing|Throttling & Debouncing]], [[React Performance Optimization|React Performance Optimization]], [[Memory Leak Prevention 메모리 누수 방지|Memory Leak Prevention (메모리 누수 방지)]], [[useEffect 클린업(Cleanup)|useEffect 클린업(Cleanup)]] +- **Projects/Contexts:** 반응형 3D 캔버스(Three.js/R3F) 크기 최적화, [[실시간 데이터 대시보드 레이아웃 조절 시스템|실시간 데이터 대시보드 레이아웃 조절 시스템]] - **Contradictions/Notes:** 단순히 윈도우 크기에 맞춰 CSS 요소의 크기나 배치를 조정하는 것이 목적이라면, 자바스크립트의 `resize` 이벤트를 아예 사용하지 않고 CSS의 미디어 쿼리(Media Queries)나 상대 단위(`vw`, `vh`, `100%`)를 사용하는 것이 렌더링 파이프라인 성능 측면에서 가장 비용이 낮고 완벽한 방법입니다. 자바스크립트 이벤트는 캔버스 렌더러 리사이즈나 복잡한 가상화 리스트(Virtualization) 재계산 등 CSS만으로 해결할 수 없는 경우에만 제한적으로 사용해야 합니다. --- _Last updated: 2026-04-14_ -- Raw Source: [[00_Raw/2026-04-20/반응형 윈도우 리사이즈(Resize) 이벤트 처리.md]] +- Raw Source: 00_Raw/2026-04-20/반응형 윈도우 리사이즈(Resize) 이벤트 처리.md --- diff --git a/01_Archive/2026-04-20/백엔드-프론트엔드 데이터 변환(Data Transformation between Backend and Frontend).md b/01_Archive/2026-04-20/백엔드-프론트엔드 데이터 변환(Data Transformation between Backend and Frontend).md index 4d168ab1..f7ec469c 100644 --- a/01_Archive/2026-04-20/백엔드-프론트엔드 데이터 변환(Data Transformation between Backend and Frontend).md +++ b/01_Archive/2026-04-20/백엔드-프론트엔드 데이터 변환(Data Transformation between Backend and Frontend).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-6AC944 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 백엔드-프론트엔드 데이터 변환(Data Transformation between Backend and Frontend)" --- -# [[백엔드-프론트엔드 데이터 변환(Data Transformation between Backend and Frontend)]] +# [[백엔드-프론트엔드 데이터 변환(Data Transformation between Backend and Frontend)|백엔드-프론트엔드 데이터 변환(Data Transformation between Backend and Frontend)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 백엔드-프론트엔드 데이터 변환은 외부 서버(백엔드)에서 수신한 데이터를 프론트엔드 애플리케이션의 모델 구조에 맞게 매핑하고 파싱하는 과정입니다 [1-3]. 이 과정에서 타입스크립트의 `satisfies` 키워드나 파싱(Parsing) 패턴을 활용하면 오타, 초과 속성 할당 등의 구조적 불일치를 사전에 방지하고 견고한 타입 안전성을 확보할 수 있습니다 [3-5]. @@ -24,11 +24,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 백엔드-프론트엔드 데 - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[satisfies Keyword]], [[Parse, don't validate]], [[Excess Property Checking]], [[Structural Typing]] -- **Projects/Contexts:** [[Inventory Management Example]] (외부 백엔드 응답을 프론트엔드의 `InventoryItem` 타입으로 매핑할 때 오류를 방지하는 실제 사용 시나리오 [2, 3]) +- **Related Topics:** [[satisfies Keyword|satisfies Keyword]], [[Parse, don't validate|Parse, don't validate]], [[Excess Property Checking|Excess Property Checking]], [[Structural Typing|Structural Typing]] +- **Projects/Contexts:** [[Inventory Management Example|Inventory Management Example]] (외부 백엔드 응답을 프론트엔드의 `InventoryItem` 타입으로 매핑할 때 오류를 방지하는 실제 사용 시나리오 [2, 3]) - **Contradictions/Notes:** 소스 데이터에 따르면 데이터 변환 과정에서 강제 타입 단언(type casting, `as`)을 사용하여 타입을 덮어씌우는 것은 잉여 속성을 걸러내지 못하므로 안전하지 않으며, 이를 보완하기 위해 런타임 오류 가능성을 원천 차단하는 `satisfies` 연산자의 사용이 권장됩니다 [5, 8]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/백엔드-프론트엔드 데이터 변환(Data Transformation between Backend and Frontend).md]] +- Raw Source: 00_Raw/2026-04-20/백엔드-프론트엔드 데이터 변환(Data Transformation between Backend and Frontend).md --- diff --git a/01_Archive/2026-04-20/번아웃 및 직무 스트레스.md b/01_Archive/2026-04-20/번아웃 및 직무 스트레스.md index 12477ae8..b051891f 100644 --- a/01_Archive/2026-04-20/번아웃 및 직무 스트레스.md +++ b/01_Archive/2026-04-20/번아웃 및 직무 스트레스.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-4FD551 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 번아웃 및 직무 스트레스" --- -# [[번아웃 및 직무 스트레스]] +# [[번아웃 및 직무 스트레스|번아웃 및 직무 스트레스]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - 번아웃 및 직무 스트레 ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/번아웃 및 직무 스트레스.md]] +- Raw Source: 00_Raw/2026-04-20/번아웃 및 직무 스트레스.md --- diff --git a/01_Archive/2026-04-20/범이론적 모델(Transtheoretical Model).md b/01_Archive/2026-04-20/범이론적 모델(Transtheoretical Model).md index 5825213d..eaf4c425 100644 --- a/01_Archive/2026-04-20/범이론적 모델(Transtheoretical Model).md +++ b/01_Archive/2026-04-20/범이론적 모델(Transtheoretical Model).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-8B5019 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 범이론적 모델(Transtheoretical Model)" --- -# [[범이론적 모델(Transtheoretical Model)]] +# [[범이론적 모델(Transtheoretical Model)|범이론적 모델(Transtheoretical Model)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - 범이론적 모델(Transtheor ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/범이론적 모델(Transtheoretical Model).md]] +- Raw Source: 00_Raw/2026-04-20/범이론적 모델(Transtheoretical Model).md --- diff --git a/01_Archive/2026-04-20/벡터 데이터베이스 (Vector Database).md b/01_Archive/2026-04-20/벡터 데이터베이스 (Vector Database).md index f23cafd4..7c4f498d 100644 --- a/01_Archive/2026-04-20/벡터 데이터베이스 (Vector Database).md +++ b/01_Archive/2026-04-20/벡터 데이터베이스 (Vector Database).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-A4C204 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 벡터 데이터베이스 (Vector Database)" --- -# [[벡터 데이터베이스 (Vector Database)]] +# [[벡터 데이터베이스 (Vector Database)|벡터 데이터베이스 (Vector Database)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - 벡터 데이터베이스 (Vec ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/벡터 데이터베이스 (Vector Database).md]] +- Raw Source: 00_Raw/2026-04-20/벡터 데이터베이스 (Vector Database).md --- diff --git a/01_Archive/2026-04-20/보상 예측 오류 (Reward Prediction Error).md b/01_Archive/2026-04-20/보상 예측 오류 (Reward Prediction Error).md index 15513f2c..3d2a6fa7 100644 --- a/01_Archive/2026-04-20/보상 예측 오류 (Reward Prediction Error).md +++ b/01_Archive/2026-04-20/보상 예측 오류 (Reward Prediction Error).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-F58C26 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 보상 예측 오류 (Reward Prediction Error)" --- -# [[보상 예측 오류 (Reward Prediction Error)]] +# [[보상 예측 오류 (Reward Prediction Error)|보상 예측 오류 (Reward Prediction Error)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - 보상 예측 오류 (Reward P ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/보상 예측 오류 (Reward Prediction Error).md]] +- Raw Source: 00_Raw/2026-04-20/보상 예측 오류 (Reward Prediction Error).md --- diff --git a/01_Archive/2026-04-20/보상의 역효과 (Overjustification Effect).md b/01_Archive/2026-04-20/보상의 역효과 (Overjustification Effect).md index 23a9acc8..14b93092 100644 --- a/01_Archive/2026-04-20/보상의 역효과 (Overjustification Effect).md +++ b/01_Archive/2026-04-20/보상의 역효과 (Overjustification Effect).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-0B61E9 -category: "[[10_Wiki/💡 Topics/Psychology & Behavior]]" +category: "10_Wiki/💡 Topics/Psychology & Behavior" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 보상의 역효과 (Overjustification Effect)" --- -# [[보상의 역효과 (Overjustification Effect)]] +# [[보상의 역효과 (Overjustification Effect)|보상의 역효과 (Overjustification Effect)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - 보상의 역효과 (Overjusti ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/보상의 역효과 (Overjustification Effect).md]] +- Raw Source: 00_Raw/2026-04-20/보상의 역효과 (Overjustification Effect).md --- diff --git a/01_Archive/2026-04-20/보조 공학 (Assistive Technology).md b/01_Archive/2026-04-20/보조 공학 (Assistive Technology).md index dfe5a273..954ab88e 100644 --- a/01_Archive/2026-04-20/보조 공학 (Assistive Technology).md +++ b/01_Archive/2026-04-20/보조 공학 (Assistive Technology).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-34AA37 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 보조 공학 (Assistive Technology)" --- -# [[보조 공학 (Assistive Technology)]] +# [[보조 공학 (Assistive Technology)|보조 공학 (Assistive Technology)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - 보조 공학 (Assistive Techn ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/보조 공학 (Assistive Technology).md]] +- Raw Source: 00_Raw/2026-04-20/보조 공학 (Assistive Technology).md --- diff --git a/01_Archive/2026-04-20/보존 경로(Retaining Path).md b/01_Archive/2026-04-20/보존 경로(Retaining Path).md index c8efb674..29983cf5 100644 --- a/01_Archive/2026-04-20/보존 경로(Retaining Path).md +++ b/01_Archive/2026-04-20/보존 경로(Retaining Path).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-97AEC6 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 보존 경로(Retaining Path)" --- -# [[보존 경로(Retaining Path)]] +# [[보존 경로(Retaining Path)|보존 경로(Retaining Path)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 보존 경로(Retaining Path)는 메모리 누수를 조사할 때 특정 객체가 가비지 컬렉션(GC)에 의해 수거되지 않고 살아남게 만드는 참조 체인(chain of references)을 의미합니다 [1, 2]. V8 엔진은 전역 창(window) 객체나 활성 스택의 로컬 변수와 같은 루트 객체(GC Root)로부터 포인터 체인을 통해 도달 가능한 객체를 메모리에 유지해야 할 객체로 간주합니다 [3]. 개발자는 힙 스냅샷 도구나 특수 디버깅 플래그를 사용하여 이러한 보존 경로를 역추적하고 불필요한 참조를 식별하여 메모리 누수 문제를 해결할 수 있습니다 [2-4]. @@ -23,11 +23,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 보존 경로(Retaining Path)" - **정책 변화:** AI 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Garbage Collection]], [[Heap Snapshot]], [[GC Root]], [[Memory Leak]] -- **Projects/Contexts:** [[V8 Engine]], [[Chrome DevTools]], [[Node.js Memory Management]] +- **Related Topics:** [[Garbage Collection|Garbage Collection]], [[Heap Snapshot|Heap Snapshot]], [[GC Root|GC Root]], [[Memory Leak|Memory Leak]] +- **Projects/Contexts:** [[V8 Engine|V8 Engine]], [[Chrome DevTools|Chrome DevTools]], [[Node.js Memory Management|Node.js Memory Management]] - **Contradictions/Notes:** 소스 내에 상충되는 내용은 없습니다. 보존 경로는 개념적으로 루트(Root) 객체로부터 시작되는 포인터의 체인이지만, DevTools 등의 분석 도구에서는 누수된 객체에서 루트로 올라가는 역순(reverse)으로 경로를 시각화하여 디버깅을 돕습니다 [3]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/보존 경로(Retaining Path).md]] +- Raw Source: 00_Raw/2026-04-20/보존 경로(Retaining Path).md --- diff --git a/01_Archive/2026-04-20/보편적 언어 (Ubiquitous Language).md b/01_Archive/2026-04-20/보편적 언어 (Ubiquitous Language).md index 3e05d30e..9a015bbd 100644 --- a/01_Archive/2026-04-20/보편적 언어 (Ubiquitous Language).md +++ b/01_Archive/2026-04-20/보편적 언어 (Ubiquitous Language).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-560AB4 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 보편적 언어 (Ubiquitous Language)" --- -# [[보편적 언어 (Ubiquitous Language)]] +# [[보편적 언어 (Ubiquitous Language)|보편적 언어 (Ubiquitous Language)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 보편적 언어(Ubiquitous Language)는 도메인 주도 설계(Domain-Driven Design)에서 복잡성을 해결하기 위해 프로젝트의 모든 참여자가 공통으로 사용하는 공유 언어입니다 [1]. 이는 개발자와 비즈니스 이해관계자 간의 의사소통 격차를 해소하는 공통 어휘 역할을 합니다 [1]. 궁극적으로 소프트웨어가 올바른 비즈니스 문제를 해결하도록 보장하는 데 핵심적인 목적이 있습니다 [1]. @@ -22,11 +22,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 보편적 언어 (Ubiquitous L - **정책 변화:** AI 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Domain-Driven Design (DDD)]], [[Bounded Contexts]] -- **Projects/Contexts:** [[소프트웨어 아키텍처 설계]] +- **Related Topics:** [[Domain-Driven Design (DDD)|Domain-Driven Design (DDD)]], [[Bounded Contexts|Bounded Contexts]] +- **Projects/Contexts:** [[소프트웨어 아키텍처 설계|소프트웨어 아키텍처 설계]] - **Contradictions/Notes:** 소스에 관련 정보가 부족합니다. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/보편적 언어 (Ubiquitous Language).md]] +- Raw Source: 00_Raw/2026-04-20/보편적 언어 (Ubiquitous Language).md --- diff --git a/01_Archive/2026-04-20/복잡한 비즈니스 도메인 (금융 헬스케어 이커머스 등).md b/01_Archive/2026-04-20/복잡한 비즈니스 도메인 (금융 헬스케어 이커머스 등).md index 411161e8..474b0326 100644 --- a/01_Archive/2026-04-20/복잡한 비즈니스 도메인 (금융 헬스케어 이커머스 등).md +++ b/01_Archive/2026-04-20/복잡한 비즈니스 도메인 (금융 헬스케어 이커머스 등).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-AD3BC6 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 복잡한 비즈니스 도메인 (금융 헬스케어 이커머스 등)" --- -# [[복잡한 비즈니스 도메인 (금융 헬스케어 이커머스 등)]] +# [[복잡한 비즈니스 도메인 (금융 헬스케어 이커머스 등)|복잡한 비즈니스 도메인 (금융 헬스케어 이커머스 등)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 복잡한 비즈니스 도메인(금융, 헬스케어, 이커머스 등)은 방대하고 민감한 데이터 처리, 고도의 보안 및 엄격한 규제 준수, 그리고 복잡한 비즈니스 로직을 특징으로 하는 산업 분야입니다 [1-4]. 이러한 도메인의 내재된 복잡성을 통제하고 현실의 비즈니스 프로세스를 소프트웨어로 정확히 반영하기 위해 도메인 주도 설계(DDD)와 같은 아키텍처 원칙이 필수적으로 활용됩니다 [4-6]. 이를 통해 조직은 기술적 부채를 최소화하고 변화하는 비즈니스 요구에 맞춰 확장 가능하며 유지보수가 용이한 시스템을 구축할 수 있습니다 [5, 7]. @@ -30,11 +30,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 복잡한 비즈니스 도메 - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[도메인 주도 설계 (DDD)]], [[바운디드 컨텍스트 (Bounded Context)]], [[마이크로서비스 아키텍처 (Microservices Architecture)]], [[이벤트 기반 아키텍처 (Event-Driven Architecture)]], [[데이터 거버넌스 (Data Governance)]] -- **Projects/Contexts:** [[핀테크의 실시간 사기 탐지]], [[이커머스의 실시간 재고 관리]], [[헬스케어의 민감 데이터(PII/PCI) 보안 규제 준수]] +- **Related Topics:** [[도메인 주도 설계 (DDD)|도메인 주도 설계 (DDD)]], [[바운디드 컨텍스트 (Bounded Context)|바운디드 컨텍스트 (Bounded Context)]], [[마이크로서비스 아키텍처 (Microservices Architecture)|마이크로서비스 아키텍처 (Microservices Architecture)]], [[이벤트 기반 아키텍처 (Event-Driven Architecture)|이벤트 기반 아키텍처 (Event-Driven Architecture)]], [[데이터 거버넌스 (Data Governance)|데이터 거버넌스 (Data Governance)]] +- **Projects/Contexts:** [[핀테크의 실시간 사기 탐지|핀테크의 실시간 사기 탐지]], [[이커머스의 실시간 재고 관리|이커머스의 실시간 재고 관리]], [[헬스케어의 민감 데이터(PII_PCI) 보안 규제 준수|헬스케어의 민감 데이터(PII/PCI) 보안 규제 준수]] - **Contradictions/Notes:** 소스 문헌들은 복잡한 비즈니스 도메인 구축 시 기술적인 관점으로만 시스템을 나누는 것(예: 단순 계층형 아키텍처)보다, 비즈니스 현실을 중심에 두고 비즈니스 역량과 도메인 모델을 기준으로 시스템을 세분화하는 도메인 주도 설계(DDD)나 마이크로서비스 아키텍처가 훨씬 더 높은 확장성과 유지보수성을 제공한다고 강조합니다 [5, 6, 15]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/복잡한 비즈니스 도메인 (금융, 헬스케어, 이커머스 등).md]] +- Raw Source: 00_Raw/2026-04-20/복잡한 비즈니스 도메인 (금융, 헬스케어, 이커머스 등).md --- diff --git a/01_Archive/2026-04-20/복잡한 비즈니스 도메인 (금융, 헬스케어, 이커머스 등).md b/01_Archive/2026-04-20/복잡한 비즈니스 도메인 (금융, 헬스케어, 이커머스 등).md index 07c382a1..755d91af 100644 --- a/01_Archive/2026-04-20/복잡한 비즈니스 도메인 (금융, 헬스케어, 이커머스 등).md +++ b/01_Archive/2026-04-20/복잡한 비즈니스 도메인 (금융, 헬스케어, 이커머스 등).md @@ -1,4 +1,4 @@ -# [[복잡한 비즈니스 도메인 (금융, 헬스케어, 이커머스 등)]] +# [[복잡한 비즈니스 도메인 (금융, 헬스케어, 이커머스 등)|복잡한 비즈니스 도메인 (금융, 헬스케어, 이커머스 등)]] ## 📌 Brief Summary 복잡한 비즈니스 도메인(금융, 헬스케어, 이커머스 등)은 방대하고 민감한 데이터 처리, 고도의 보안 및 엄격한 규제 준수, 그리고 복잡한 비즈니스 로직을 특징으로 하는 산업 분야입니다 [1-4]. 이러한 도메인의 내재된 복잡성을 통제하고 현실의 비즈니스 프로세스를 소프트웨어로 정확히 반영하기 위해 도메인 주도 설계(DDD)와 같은 아키텍처 원칙이 필수적으로 활용됩니다 [4-6]. 이를 통해 조직은 기술적 부채를 최소화하고 변화하는 비즈니스 요구에 맞춰 확장 가능하며 유지보수가 용이한 시스템을 구축할 수 있습니다 [5, 7]. @@ -17,8 +17,8 @@ 복잡한 비즈니스 도메인의 핵심 규칙은 클린 아키텍처(Clean Architecture) 원칙에 따라 데이터베이스나 웹 프레임워크와 같은 외부 인프라의 변동으로부터 완벽히 보호(격리)되어야 합니다 [12, 13]. 나아가 마이크로서비스 아키텍처를 도입하여 거대한 시스템을 특정 비즈니스 도메인 기능에 맞춰 세분화된 독립 서비스로 나누면, 각 팀이 자율적으로 배포 및 확장을 수행할 수 있어 복잡한 시스템 환경에서도 비즈니스 민첩성을 확보할 수 있습니다 [6, 14]. ## 🔗 Knowledge Connections -- **Related Topics:** [[도메인 주도 설계 (DDD)]], [[바운디드 컨텍스트 (Bounded Context)]], [[마이크로서비스 아키텍처 (Microservices Architecture)]], [[이벤트 기반 아키텍처 (Event-Driven Architecture)]], [[데이터 거버넌스 (Data Governance)]] -- **Projects/Contexts:** [[핀테크의 실시간 사기 탐지]], [[이커머스의 실시간 재고 관리]], [[헬스케어의 민감 데이터(PII/PCI) 보안 규제 준수]] +- **Related Topics:** [[도메인 주도 설계 (DDD)|도메인 주도 설계 (DDD)]], [[바운디드 컨텍스트 (Bounded Context)|바운디드 컨텍스트 (Bounded Context)]], [[마이크로서비스 아키텍처 (Microservices Architecture)|마이크로서비스 아키텍처 (Microservices Architecture)]], [[이벤트 기반 아키텍처 (Event-Driven Architecture)|이벤트 기반 아키텍처 (Event-Driven Architecture)]], [[데이터 거버넌스 (Data Governance)|데이터 거버넌스 (Data Governance)]] +- **Projects/Contexts:** [[핀테크의 실시간 사기 탐지|핀테크의 실시간 사기 탐지]], [[이커머스의 실시간 재고 관리|이커머스의 실시간 재고 관리]], [[헬스케어의 민감 데이터(PII_PCI) 보안 규제 준수|헬스케어의 민감 데이터(PII/PCI) 보안 규제 준수]] - **Contradictions/Notes:** 소스 문헌들은 복잡한 비즈니스 도메인 구축 시 기술적인 관점으로만 시스템을 나누는 것(예: 단순 계층형 아키텍처)보다, 비즈니스 현실을 중심에 두고 비즈니스 역량과 도메인 모델을 기준으로 시스템을 세분화하는 도메인 주도 설계(DDD)나 마이크로서비스 아키텍처가 훨씬 더 높은 확장성과 유지보수성을 제공한다고 강조합니다 [5, 6, 15]. --- diff --git a/01_Archive/2026-04-20/불변성 (Immutability).md b/01_Archive/2026-04-20/불변성 (Immutability).md index 40498a25..84f7265d 100644 --- a/01_Archive/2026-04-20/불변성 (Immutability).md +++ b/01_Archive/2026-04-20/불변성 (Immutability).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-07CB26 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 불변성 (Immutability)" --- -# [[불변성 (Immutability)]] +# [[불변성 (Immutability)|불변성 (Immutability)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > TypeScript에서 불변성(Immutability)은 주로 `readonly` 수식어와 `Readonly` 유틸리티 타입을 통해 컴파일 타임에 데이터가 의도치 않게 변경되는 것을 방지하는 핵심 개념입니다 [1-3]. 이를 통해 객체의 속성이나 배열 요소가 초기화된 이후에 수정되는 것을 엄격히 차단하여 부작용을 줄이고 함수형 프로그래밍 패턴을 지원합니다 [1, 4]. 런타임에 성능 오버헤드를 유발하는 `Object.freeze()`와 달리 컴파일 시점에만 작동하므로, 제로 런타임 비용으로 데이터의 무결성을 보장하는 것이 특징입니다 [1, 3, 5]. @@ -33,11 +33,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 불변성 (Immutability)" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[readonly 수식어]], [[Readonly 유틸리티 타입]], [[DeepReadonly (재귀적 불변성)]], [[에일리어싱 (Aliasing)]], [[구조적 타이핑 (Structural Typing)]] -- **Projects/Contexts:** [[Redux 등 상태 관리 (State Management)]], [[API 응답 데이터 모델링]], [[글로벌 설정 객체 (Configuration Objects) 보호]] +- **Related Topics:** [[readonly 수식어|readonly 수식어]], [[Readonly 유틸리티 타입|Readonly 유틸리티 타입]], DeepReadonly (재귀적 불변성), [[에일리어싱 (Aliasing)|에일리어싱 (Aliasing)]], [[구조적 타이핑 (Structural Typing)|구조적 타이핑 (Structural Typing)]] +- **Projects/Contexts:** [[Redux 등 상태 관리 (State Management)|Redux 등 상태 관리 (State Management)]], API 응답 데이터 모델링, 글로벌 설정 객체 (Configuration Objects) 보호 - **Contradictions/Notes:** TypeScript의 `readonly`는 완벽한 런타임 불변성을 제공하지 않습니다. 컴파일 타임에만 유효하며 컴파일 후 자바스크립트 코드에서는 해당 제약이 사라집니다 [1]. 또한, 에일리어싱을 통해 `readonly` 배열이 일반 배열 타입으로 취급될 경우 타입 시스템을 우회하여 변이가 일어날 수 있으므로 함수 시그니처 설계 시 주의해야 합니다 [14, 15]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/불변성 (Immutability).md]] +- Raw Source: 00_Raw/2026-04-20/불변성 (Immutability).md --- diff --git a/01_Archive/2026-04-20/불변성(Immutability).md b/01_Archive/2026-04-20/불변성(Immutability).md index 5d30f261..ec28c9f7 100644 --- a/01_Archive/2026-04-20/불변성(Immutability).md +++ b/01_Archive/2026-04-20/불변성(Immutability).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-647D86 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 불변성(Immutability)" --- -# [[불변성(Immutability)]] +# [[불변성(Immutability)|불변성(Immutability)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 불변성(Immutability)은 초기화 이후 객체의 속성이나 배열 요소와 같은 데이터가 예기치 않게 수정되는 것을 방지하는 개념이다 [1, 2]. TypeScript에서는 주로 `readonly` 수식어를 사용하여 런타임 오버헤드 없이 컴파일 타임에 선언적으로 불변성을 강제한다 [2-4]. 이는 의도치 않은 상태 변경이나 데이터 오염을 사전에 방지하여 코드의 예측 가능성을 높이고 버그를 줄이는 데 필수적인 역할을 한다 [4, 5]. @@ -29,11 +29,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 불변성(Immutability)" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[readonly]], [[DeepReadonly]], [[as const]], [[구조적 타이핑(Structural Typing)]] -- **Projects/Contexts:** [[상태 관리(State Management)]], [[TypeScript 타입 시스템 및 인터페이스 설계]] +- **Related Topics:** [[readonly|readonly]], [[DeepReadonly|DeepReadonly]], [[as const|as const]], [[구조적 타이핑(Structural Typing)|구조적 타이핑(Structural Typing)]] +- **Projects/Contexts:** [[상태 관리(State Management)|상태 관리(State Management)]], [[TypeScript 타입 시스템 및 인터페이스 설계|TypeScript 타입 시스템 및 인터페이스 설계]] - **Contradictions/Notes:** 자바스크립트의 `Object.freeze()`는 런타임에 직접 객체를 동결하여 보호하지만 성능 저하가 동반되는 반면, TypeScript의 `readonly`는 런타임 성능 저하는 없으나 타입 호환성을 악용한 우회(Aliasing) 변형까지는 완벽히 차단하지 못한다는 한계를 지닌다 [4, 6, 15, 18]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/불변성(Immutability).md]] +- Raw Source: 00_Raw/2026-04-20/불변성(Immutability).md --- diff --git a/01_Archive/2026-04-20/불필요한 리렌더링 방지.md b/01_Archive/2026-04-20/불필요한 리렌더링 방지.md index 5dca1d0a..5c9b4eae 100644 --- a/01_Archive/2026-04-20/불필요한 리렌더링 방지.md +++ b/01_Archive/2026-04-20/불필요한 리렌더링 방지.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-B13B4D -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 불필요한 리렌더링 방지" --- -# [[불필요한 리렌더링 방지]] +# [[불필요한 리렌더링 방지|불필요한 리렌더링 방지]] ## 📌 한 줄 통찰 (The Karpathy Summary) > React 애플리케이션에서 성능 저하를 막기 위해 컴포넌트의 프롭스(Props), 상태(State), 컨텍스트(Context) 변경으로 인한 연쇄적인 렌더링을 제어하고 최적화하는 기법입니다. @@ -35,12 +35,12 @@ github_commit: "[P-Reinforce] Continuous Worker - 불필요한 리렌더링 방 - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[React Performance Optimization]], [[React 19 Compiler]], [[상태 관리 최적화 (Zustand, Jotai, Valtio)]], [[재조정 (Reconciliation)]], [[Virtualization (리스트 가상화)]] -- **Projects/Contexts:** [[대규모 프론트엔드 아키텍처 설계]], [[고빈도 업데이트를 처리하는 실시간 대시보드]] +- **Related Topics:** [[React Performance Optimization|React Performance Optimization]], [[React 19 Compiler|React 19 Compiler]], [[상태 관리 최적화 (Zustand, Jotai, Valtio)|상태 관리 최적화 (Zustand, Jotai, Valtio)]], [[재조정 (Reconciliation)|재조정 (Reconciliation)]], Virtualization (리스트 가상화) +- **Projects/Contexts:** 대규모 프론트엔드 아키텍처 설계, 고빈도 업데이트를 처리하는 실시간 대시보드 - **Contradictions/Notes:** 많은 개발자들이 컴포넌트가 느려지면 습관적으로 조기 메모이제이션(Premature Memoization)을 적용하려 하지만, 비교 연산 자체의 오버헤드로 인해 컴포넌트가 작고 빠르다면 오히려 성능이 하락할 수 있습니다. 항상 React DevTools Profiler 등으로 측정(Measure)한 후 최적화를 적용해야 합니다. --- _Last updated: 2026-04-14_ -- Raw Source: [[00_Raw/2026-04-20/불필요한 리렌더링 방지.md]] +- Raw Source: 00_Raw/2026-04-20/불필요한 리렌더링 방지.md --- diff --git a/01_Archive/2026-04-20/브라우저 DOM 누수 탐지 및 렌더링 최적화.md b/01_Archive/2026-04-20/브라우저 DOM 누수 탐지 및 렌더링 최적화.md index 9bd34c20..75fd8d6b 100644 --- a/01_Archive/2026-04-20/브라우저 DOM 누수 탐지 및 렌더링 최적화.md +++ b/01_Archive/2026-04-20/브라우저 DOM 누수 탐지 및 렌더링 최적화.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-590D6E -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 브라우저 DOM 누수 탐지 및 렌더링 최적화" --- -# [[브라우저 DOM 누수 탐지 및 렌더링 최적화]] +# [[브라우저 DOM 누수 탐지 및 렌더링 최적화|브라우저 DOM 누수 탐지 및 렌더링 최적화]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -34,11 +34,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 브라우저 DOM 누수 탐지 - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Garbage Collection (GC)]], [[Chrome DevTools]], [[Detached DOM nodes]], [[Heap Snapshot]], [[Orinoco GC]] -- **Projects/Contexts:** [[V8 JavaScript Engine]], [[Single Page Applications (SPA)]] +- **Related Topics:** [[Garbage Collection (GC)|Garbage Collection (GC)]], [[Chrome DevTools|Chrome DevTools]], Detached DOM nodes, [[Heap Snapshot|Heap Snapshot]], [[Orinoco GC|Orinoco GC]] +- **Projects/Contexts:** [[V8 JavaScript Engine|V8 JavaScript Engine]], [[Single Page Applications (SPA)|Single Page Applications (SPA)]] - **Contradictions/Notes:** 소스에는 브라우저 메모리 누수 탐지 방법과 V8 엔진의 가비지 컬렉터 동작 원리에 대한 정보는 매우 상세하게 설명되어 있으나, 레이아웃 연산, 페인팅 규칙, CSS 최적화 등 브라우저의 순수 '렌더링 파이프라인 최적화'와 관련된 직접적인 소스에 관련 정보가 부족합니다. 따라서 렌더링 최적화는 주로 '메모리 누수 방지를 통한 GC Pause(Jank) 최소화'의 관점에서만 다루어졌습니다. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/브라우저 DOM 누수 탐지 및 렌더링 최적화.md]] +- Raw Source: 00_Raw/2026-04-20/브라우저 DOM 누수 탐지 및 렌더링 최적화.md --- diff --git a/01_Archive/2026-04-20/브라우저 그래픽 렌더링 백엔드.md b/01_Archive/2026-04-20/브라우저 그래픽 렌더링 백엔드.md index 455b55b5..83157918 100644 --- a/01_Archive/2026-04-20/브라우저 그래픽 렌더링 백엔드.md +++ b/01_Archive/2026-04-20/브라우저 그래픽 렌더링 백엔드.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-102878 -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 브라우저 그래픽 렌더링 백엔드" --- -# [[브라우저 그래픽 렌더링 백엔드]] +# [[브라우저 그래픽 렌더링 백엔드|브라우저 그래픽 렌더링 백엔드]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 브라우저 그래픽 렌더링 백엔드는 WebGL이나 WebGPU와 같은 웹 그래픽 API의 명령을 물리적 GPU가 실행할 수 있는 명령어로 변환하고 전달하는 기반 시스템입니다 [1, 2]. Windows 환경에서는 ANGLE과 같은 브라우저 추상화 계층을 사용하여 OpenGL ES 호출을 Direct3D로 변환하는 역할을 수행합니다 [1, 3]. 최근의 WebGPU 환경에서는 Dawn과 같은 백엔드를 통해 Vulkan, Metal, Direct3D 12 등 차세대 네이티브 GPU API와 직접적으로 상호작용하여 렌더링 성능을 극대화합니다 [2, 4, 5]. @@ -20,11 +20,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 브라우저 그래픽 렌더 - **정책 변화:** Graphics & Performance 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[WebGL]], [[WebGPU]], [[ANGLE]], [[Dawn]], [[마이크로 레이턴시(Micro-latency)]] -- **Projects/Contexts:** [[Google Chrome]], [[Mozilla Firefox]] +- **Related Topics:** [[WebGL|WebGL]], [[WebGPU|WebGPU]], [[ANGLE|ANGLE]], Dawn, 마이크로 레이턴시(Micro-latency) +- **Projects/Contexts:** [[Google Chrome|Google Chrome]], Mozilla Firefox - **Contradictions/Notes:** Windows 환경의 ANGLE 백엔드는 WebGL 호환성을 훌륭하게 제공하지만, OpenGL ES를 Direct3D로 변환하는 과정에서 본질적인 오버헤드를 동반합니다. 수천 개의 드로우 콜이 발생하는 복잡한 씬에서는 GPU가 유휴 상태임에도 불구하고 CPU 병목 현상과 마이크로 레이턴시가 누적되어 성능 저하를 일으킬 수 있습니다 [6]. 이를 우회하여 네이티브 OpenGL 구현을 테스트하기 위해 Chrome에서 `--use-gl=desktop` 플래그를 사용하기도 합니다 [3]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/브라우저 그래픽 렌더링 백엔드.md]] +- Raw Source: 00_Raw/2026-04-20/브라우저 그래픽 렌더링 백엔드.md --- diff --git a/01_Archive/2026-04-20/브라우저 메모리 관리 및 최적화.md b/01_Archive/2026-04-20/브라우저 메모리 관리 및 최적화.md index 8c363995..c2a645d1 100644 --- a/01_Archive/2026-04-20/브라우저 메모리 관리 및 최적화.md +++ b/01_Archive/2026-04-20/브라우저 메모리 관리 및 최적화.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-F4D557 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 브라우저 메모리 관리 및 최적화" --- -# [[브라우저 메모리 관리 및 최적화]] +# [[브라우저 메모리 관리 및 최적화|브라우저 메모리 관리 및 최적화]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 브라우저 메모리 관리는 더 이상 필요하지 않은 객체의 메모리를 자동으로 회수하여 애플리케이션의 성능 저하나 충돌을 방지하는 핵심 과정이다 [1-3]. V8 자바스크립트 엔진은 힙(Heap) 공간을 여러 세대로 나누고 가비지 컬렉션(GC)을 통해 동적으로 메모리를 관리한다 [4-6]. 브라우저에서 발생하는 주요 메모리 누수는 개발자가 실수로 남겨둔 참조(DOM 노드, 이벤트 리스너, 클로저 등) 때문에 발생하며, 이를 최적화하기 위해 Chrome DevTools의 힙 스냅샷 및 할당 타임라인 도구를 사용하여 누수 원인을 식별하고 해결해야 한다 [2, 7-9]. @@ -30,11 +30,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 브라우저 메모리 관리 - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[가비지 컬렉션 (Garbage Collection)]], [[V8 JavaScript Engine]], [[Chrome DevTools]], [[메모리 누수 (Memory Leak)]] -- **Projects/Contexts:** [[Orinoco 프로젝트]], [[Chrome Allocation Timeline]], [[Three-snapshot technique]], [[V8 Memory Cage]] +- **Related Topics:** [[가비지 컬렉션 (Garbage Collection)|가비지 컬렉션 (Garbage Collection)]], [[V8 JavaScript Engine|V8 JavaScript Engine]], [[Chrome DevTools|Chrome DevTools]], [[메모리 누수(Memory Leak)|메모리 누수 (Memory Leak)]] +- **Projects/Contexts:** [[Orinoco 프로젝트|Orinoco 프로젝트]], Chrome Allocation Timeline, Three-snapshot technique, [[V8 Memory Cage|V8 Memory Cage]] - **Contradictions/Notes:** 가비지 컬렉션 시스템의 성능이 관리되지 않는(unmanaged) 언어(예: C/C++)에 비해 절대적으로 우수하거나 나쁜 것은 아니다. 관리되는 언어는 메모리 할당이 단순 포인터 증가만으로 이루어져 매우 빠르지만, 메모리가 부족하여 가비지 컬렉터가 실행될 때는 예기치 않은 성능 비용(지연 및 멈춤)을 필연적으로 지불해야 한다 [44]. 또한 포인터 압축(Pointer compression)은 V8 힙 크기를 최대 40%까지 줄이고 성능을 5~10% 향상시키지만, 힙의 최대 크기를 4GB로 엄격히 제한한다는 트레이드오프가 존재한다 [42, 45]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/브라우저 메모리 관리 및 최적화.md]] +- Raw Source: 00_Raw/2026-04-20/브라우저 메모리 관리 및 최적화.md --- diff --git a/01_Archive/2026-04-20/브라우저 메모리 누수 탐지(Browser Memory Leak Detection).md b/01_Archive/2026-04-20/브라우저 메모리 누수 탐지(Browser Memory Leak Detection).md index 8b6b3a29..ca09f902 100644 --- a/01_Archive/2026-04-20/브라우저 메모리 누수 탐지(Browser Memory Leak Detection).md +++ b/01_Archive/2026-04-20/브라우저 메모리 누수 탐지(Browser Memory Leak Detection).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-CC0FCE -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 브라우저 메모리 누수 탐지(Browser Memory Leak Detection)" --- -# [[브라우저 메모리 누수 탐지(Browser Memory Leak Detection)]] +# [[브라우저 메모리 누수 탐지(Browser Memory Leak Detection)|브라우저 메모리 누수 탐지(Browser Memory Leak Detection)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 브라우저 메모리 누수는 가비지 컬렉션(GC) 대상이 되어야 할 객체들이 Window, 클로저, 이벤트 리스너 등의 GC 루트(Roots)에 의해 계속 참조되어 메모리에서 해제되지 않는 현상이다 [1]. 이를 탐지하고 원인을 파악하기 위해 주로 Chrome DevTools의 힙 스냅샷(Heap snapshot)과 할당 타임라인(Allocation timeline) 도구가 사용된다 [1, 2]. 이러한 도구들을 활용하면 메모리에 남아 있는 객체의 참조 체인(Retainers)과 할당된 스택 트레이스를 분석하여 애플리케이션의 메모리 누수 근본 원인을 식별할 수 있다 [2]. @@ -30,11 +30,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 브라우저 메모리 누수 - **정책 변화:** AI 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[가비지 컬렉션(Garbage Collection)]], [[힙 스냅샷(Heap Snapshot)]], [[클로저(Closures)]], [[V8 엔진(V8 Engine)]] -- **Projects/Contexts:** [[Chrome DevTools]], [[Single Page Applications (SPA)]] +- **Related Topics:** [[가비지 컬렉션(Garbage Collection)|가비지 컬렉션(Garbage Collection)]], [[힙 스냅샷(Heap Snapshot)|힙 스냅샷(Heap Snapshot)]], [[클로저(Closures)|클로저(Closures)]], [[V8 엔진(V8 Engine)|V8 엔진(V8 Engine)]] +- **Projects/Contexts:** [[Chrome DevTools|Chrome DevTools]], [[Single Page Applications (SPA)|Single Page Applications (SPA)]] - **Contradictions/Notes:** 메모리 사용량 그래프가 증가한다고 해서 모두 누수는 아니다. 캐시, 실행 취소 내역, 가상화된 리스트 버퍼 등은 의도적으로 데이터를 유지하는 것이므로, 의도적인 보존(Intentional retention)과 우발적인 누수(Accidental retention)를 반드시 구별해야 한다 [6]. 또한, `WeakRef`와 `FinalizationRegistry`를 사용해 누수에 강한 패턴을 작성할 수는 있으나, GC의 실행 시점은 비결정적이므로 이를 적절한 생명주기 관리의 대체재로 사용해서는 안 된다 [5]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/브라우저 메모리 누수 탐지(Browser Memory Leak Detection).md]] +- Raw Source: 00_Raw/2026-04-20/브라우저 메모리 누수 탐지(Browser Memory Leak Detection).md --- diff --git a/01_Archive/2026-04-20/브라우저 메모리 할당 시점별 힙(Heap) 동작 상세 로그.md b/01_Archive/2026-04-20/브라우저 메모리 할당 시점별 힙(Heap) 동작 상세 로그.md index e342c2e2..90d6c5c8 100644 --- a/01_Archive/2026-04-20/브라우저 메모리 할당 시점별 힙(Heap) 동작 상세 로그.md +++ b/01_Archive/2026-04-20/브라우저 메모리 할당 시점별 힙(Heap) 동작 상세 로그.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-CAF78B -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 브라우저 메모리 할당 시점별 힙(Heap) 동작 상세 로그" --- -# [[브라우저 메모리 할당 시점별 힙(Heap) 동작 상세 로그]] +# [[브라우저 메모리 할당 시점별 힙(Heap) 동작 상세 로그|브라우저 메모리 할당 시점별 힙(Heap) 동작 상세 로그]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -30,11 +30,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 브라우저 메모리 할당 - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[가비지 컬렉션(Garbage Collection)]], [[V8 힙 공간(V8 Heap Spaces)]], [[메모리 누수(Memory Leak)]], [[힙 스냅샷(Heap Snapshot)]] -- **Projects/Contexts:** [[Chrome DevTools 메모리 프로파일링]], [[Node.js 성능 최적화 및 디버깅]] +- **Related Topics:** [[가비지 컬렉션(Garbage Collection)|가비지 컬렉션(Garbage Collection)]], [[V8 힙 공간(V8 Heap Spaces)|V8 힙 공간(V8 Heap Spaces)]], [[메모리 누수(Memory Leak)|메모리 누수(Memory Leak)]], [[힙 스냅샷(Heap Snapshot)|힙 스냅샷(Heap Snapshot)]] +- **Projects/Contexts:** [[Chrome DevTools 메모리 프로파일링|Chrome DevTools 메모리 프로파일링]], [[Node.js 성능 최적화 및 디버깅|Node.js 성능 최적화 및 디버깅]] - **Contradictions/Notes:** 소스에 관련 정보가 부족합니다. (본 주제에 관하여 제공된 소스들 내에서 명시적인 주장 대립이나 모순점은 발견되지 않았습니다.) --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/브라우저 메모리 할당 시점별 힙(Heap) 동작 상세 로그.md]] +- Raw Source: 00_Raw/2026-04-20/브라우저 메모리 할당 시점별 힙(Heap) 동작 상세 로그.md --- diff --git a/01_Archive/2026-04-20/브라우저 및 Node.js 메모리 튜닝.md b/01_Archive/2026-04-20/브라우저 및 Node.js 메모리 튜닝.md index 1f37b6c6..d0427e60 100644 --- a/01_Archive/2026-04-20/브라우저 및 Node.js 메모리 튜닝.md +++ b/01_Archive/2026-04-20/브라우저 및 Node.js 메모리 튜닝.md @@ -1,4 +1,4 @@ -# [[브라우저 및 Node.js 메모리 튜닝]] +# [[브라우저 및 Node.js 메모리 튜닝|브라우저 및 Node.js 메모리 튜닝]] ## 📌 Brief Summary 브라우저와 Node.js의 메모리 튜닝은 V8 엔진의 메모리 사용량을 모니터링하고 가비지 컬렉션(GC)을 최적화하며, 메모리 누수를 해결하는 과정이다 [1, 2]. 애플리케이션의 메모리가 해제되지 않고 누적되는 현상을 탐지하기 위해 힙 스냅샷(Heap snapshot)과 타임라인 할당 추적(Allocation timeline) 등의 도구를 활용하여 원인을 분석한다 [3-6]. 또한 커맨드라인 플래그를 통한 힙 메모리 크기 조정과 V8의 세대별(Generational) 메모리 관리 구조를 깊이 이해함으로써 Out-Of-Memory (OOM) 크래시를 방지하고 성능을 극대화할 수 있다 [2, 7, 8]. @@ -17,8 +17,8 @@ 최신 프론트엔드 및 Node.js 애플리케이션의 7대 주요 누수 패턴으로는 화면에서 제거된 후에도 JavaScript 변수에 묶여있는 DOM 노드(Detached DOM nodes) [35, 36], 무한정 커지는 인메모리 캐시 [37], 삭제되지 않은 이벤트 리스너(Event Listener Accumulation) [34, 38], 정리되지 않은 setInterval 등의 타이머 및 옵저버 [37, 39, 40], 클로저(Closure) 내부 변수의 과도한 수명 연장 현상 등이 있다 [37, 38]. ## 🔗 Knowledge Connections -- **Related Topics:** `[[V8 Engine Heap Architecture]]`, `[[Orinoco Garbage Collector]]`, `[[Heap Snapshot & Allocation Timeline]]`, `[[Generational GC Hypothesis]]` -- **Projects/Contexts:** `[[Node.js Production Monitoring]]`, `[[Chrome DevTools Profiling]]`, `[[Electron Memory Cage]]` +- **Related Topics:** `V8 Engine Heap Architecture`, `Orinoco Garbage Collector`, `Heap Snapshot & Allocation Timeline`, `Generational GC Hypothesis` +- **Projects/Contexts:** `[[Node.js Production Monitoring|Node.js Production Monitoring]]`, `Chrome DevTools Profiling`, `Electron Memory Cage` - **Contradictions/Notes:** 가비지 컬렉션 시 살아남은 객체를 새로운 메모리 페이지로 복사(Copy)하는 방식은 비용이 크게 느껴질 수 있으나, 소스에 따르면 '대부분의 객체는 매우 짧은 시간 안에 버려진다(Generational Hypothesis)'는 통계적 근거 덕분에, 적은 수의 생존 객체만 복사하는 것이 전체 메모리 스캔 비용보다 훨씬 저렴하여 성능 상 이점이 크다고 설명한다 [41]. 또한, 포인터 압축(Pointer Compression) 기술은 메모리 사용량을 대폭 절감하지만, V8 힙을 최대 4GB로 제한하는 구조적 한계를 낳아 Electron과 같은 특수 환경에서 큰 ArrayBuffer를 다루는 네이티브 모듈에 리팩토링 부담을 주는 트레이드오프가 있다 [42-45]. --- diff --git a/01_Archive/2026-04-20/브라우저 및 Nodejs 메모리 튜닝.md b/01_Archive/2026-04-20/브라우저 및 Nodejs 메모리 튜닝.md index 1aa44e8e..98907f12 100644 --- a/01_Archive/2026-04-20/브라우저 및 Nodejs 메모리 튜닝.md +++ b/01_Archive/2026-04-20/브라우저 및 Nodejs 메모리 튜닝.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-D511AE -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 브라우저 및 Nodejs 메모리 튜닝" --- -# [[브라우저 및 Nodejs 메모리 튜닝]] +# [[브라우저 및 Nodejs 메모리 튜닝|브라우저 및 Nodejs 메모리 튜닝]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 브라우저와 Node.js의 메모리 튜닝은 V8 엔진의 메모리 사용량을 모니터링하고 가비지 컬렉션(GC)을 최적화하며, 메모리 누수를 해결하는 과정이다 [1, 2]. 애플리케이션의 메모리가 해제되지 않고 누적되는 현상을 탐지하기 위해 힙 스냅샷(Heap snapshot)과 타임라인 할당 추적(Allocation timeline) 등의 도구를 활용하여 원인을 분석한다 [3-6]. 또한 커맨드라인 플래그를 통한 힙 메모리 크기 조정과 V8의 세대별(Generational) 메모리 관리 구조를 깊이 이해함으로써 Out-Of-Memory (OOM) 크래시를 방지하고 성능을 극대화할 수 있다 [2, 7, 8]. @@ -30,11 +30,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 브라우저 및 Nodejs 메모 - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** `[[V8 Engine Heap Architecture]]`, `[[Orinoco Garbage Collector]]`, `[[Heap Snapshot & Allocation Timeline]]`, `[[Generational GC Hypothesis]]` -- **Projects/Contexts:** `[[Node.js Production Monitoring]]`, `[[Chrome DevTools Profiling]]`, `[[Electron Memory Cage]]` +- **Related Topics:** `V8 Engine Heap Architecture`, `Orinoco Garbage Collector`, `Heap Snapshot & Allocation Timeline`, `Generational GC Hypothesis` +- **Projects/Contexts:** `[[Node.js Production Monitoring|Node.js Production Monitoring]]`, `Chrome DevTools Profiling`, `Electron Memory Cage` - **Contradictions/Notes:** 가비지 컬렉션 시 살아남은 객체를 새로운 메모리 페이지로 복사(Copy)하는 방식은 비용이 크게 느껴질 수 있으나, 소스에 따르면 '대부분의 객체는 매우 짧은 시간 안에 버려진다(Generational Hypothesis)'는 통계적 근거 덕분에, 적은 수의 생존 객체만 복사하는 것이 전체 메모리 스캔 비용보다 훨씬 저렴하여 성능 상 이점이 크다고 설명한다 [41]. 또한, 포인터 압축(Pointer Compression) 기술은 메모리 사용량을 대폭 절감하지만, V8 힙을 최대 4GB로 제한하는 구조적 한계를 낳아 Electron과 같은 특수 환경에서 큰 ArrayBuffer를 다루는 네이티브 모듈에 리팩토링 부담을 주는 트레이드오프가 있다 [42-45]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/브라우저 및 Node.js 메모리 튜닝.md]] +- Raw Source: 00_Raw/2026-04-20/브라우저 및 Node.js 메모리 튜닝.md --- diff --git a/01_Archive/2026-04-20/브랜디드 타입 (Branded Types).md b/01_Archive/2026-04-20/브랜디드 타입 (Branded Types).md index c5252055..040fc327 100644 --- a/01_Archive/2026-04-20/브랜디드 타입 (Branded Types).md +++ b/01_Archive/2026-04-20/브랜디드 타입 (Branded Types).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-2095A1 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 브랜디드 타입 (Branded Types)" --- -# [[브랜디드 타입 (Branded Types)]] +# [[브랜디드 타입 (Branded Types)|브랜디드 타입 (Branded Types)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 브랜디드 타입(Branded Types) 또는 오파크 타입(Opaque Types)은 TypeScript의 구조적 타이핑(Structural Typing) 시스템 내에서 발생할 수 있는 의미론적 오류를 방지하기 위해 사용되는 디자인 패턴이다 [1, 2]. 컴파일 시점에만 존재하는 고유한 가상 속성이나 심볼을 타입에 부여하여, 런타임 구조가 동일한 타입이라도 명목적 타이핑(Nominal Typing) 효과를 내며 엄격히 구분되도록 강제한다 [2-4]. 이를 통해 사용자 ID와 주문 ID처럼 형태는 같지만 의미가 전혀 다른 데이터의 혼용을 막고, 시스템 내 데이터의 무결성을 안전하게 보호한다 [4-6]. @@ -36,11 +36,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 브랜디드 타입 (Branded T - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[구조적 타이핑 (Structural Typing)]], [[타입 단언 (Type Assertions)]], [[타입 가드 (Type Predicates)]] -- **Projects/Contexts:** [[도메인 주도 설계 (DDD)]], [[Zod를 활용한 런타임 데이터 파싱]] +- **Related Topics:** [[구조적 타이핑 (Structural Typing)|구조적 타이핑 (Structural Typing)]], [[타입 단언 (Type Assertions)|타입 단언 (Type Assertions)]], [[타입 가드 (Type Predicates)|타입 가드 (Type Predicates)]] +- **Projects/Contexts:** [[도메인 주도 설계 (DDD)|도메인 주도 설계 (DDD)]], [[Zod를 활용한 런타임 데이터 파싱|Zod를 활용한 런타임 데이터 파싱]] - **Contradictions/Notes:** 별도의 래퍼(Wrapper) 클래스를 만들어 기본 타입을 객체지향적으로 감싸는 방식도 무결성을 챙길 수 있는 대안으로 언급되나, 이는 브랜디드 타입(런타임 오버헤드가 없음)과 달리 매 생성마다 런타임 메모리와 성능 오버헤드를 유발하므로 극도의 안정성이 필요한 경우에만 제한적으로 사용해야 함을 소스는 경고하고 있습니다 [3, 26, 27]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/브랜디드 타입 (Branded Types).md]] +- Raw Source: 00_Raw/2026-04-20/브랜디드 타입 (Branded Types).md --- diff --git a/01_Archive/2026-04-20/브랜디드 타입(Branded Types).md b/01_Archive/2026-04-20/브랜디드 타입(Branded Types).md index 05afc7bb..0a231a6d 100644 --- a/01_Archive/2026-04-20/브랜디드 타입(Branded Types).md +++ b/01_Archive/2026-04-20/브랜디드 타입(Branded Types).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-D05100 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 브랜디드 타입(Branded Types)" --- -# [[브랜디드 타입(Branded Types)]] +# [[브랜디드 타입(Branded Types)|브랜디드 타입(Branded Types)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -38,11 +38,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 브랜디드 타입(Branded Ty - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[구조적 타이핑(Structural Typing)]], [[명목적 타이핑(Nominal Typing)]], [[기본 타입에의 집착(Primitive Obsession)]], [[타입 조건자(Type Predicates)]] -- **Projects/Contexts:** [[도메인 기반 설계(DDD)의 식별자 분리]], [[Zod 런타임 유효성 검사 통합]], [[Effect TS 및 ts-brand 라이브러리 활용]] +- **Related Topics:** [[구조적 타이핑(Structural Typing)|구조적 타이핑(Structural Typing)]], [[명목적 타이핑(Nominal Typing)|명목적 타이핑(Nominal Typing)]], [[기본 타입에의 집착(Primitive Obsession)|기본 타입에의 집착(Primitive Obsession)]], [[타입 조건자(Type Predicates)|타입 조건자(Type Predicates)]] +- **Projects/Contexts:** [[도메인 기반 설계(DDD)의 식별자 분리|도메인 기반 설계(DDD)의 식별자 분리]], [[Zod 런타임 유효성 검사 통합|Zod 런타임 유효성 검사 통합]], [[Effect TS 및 ts-brand 라이브러리 활용|Effect TS 및 ts-brand 라이브러리 활용]] - **Contradictions/Notes:** 브랜디드 타입은 훌륭한 타입 안정성을 제공하지만, 코드의 개념적 복잡성을 증가시킨다는 단점이 있습니다. 소스 자료에서는 브랜디드 타입을 무분별하게 도입하기 전에 유니온(Unions) 타입, 열거형(Enums), 템플릿 리터럴 타입(Template Literal Types)과 같은 더 단순한 대안으로 문제를 해결할 수 있는지 먼저 고려할 것을 권장합니다. 또한, 서로 다른 브랜디드 숫자 타입 간의 이항 연산(더하기 등)을 수행할 때는 타입 에러가 발생하지 않으므로 사용 시 주의가 필요합니다. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/브랜디드 타입(Branded Types).md]] +- Raw Source: 00_Raw/2026-04-20/브랜디드 타입(Branded Types).md --- diff --git a/01_Archive/2026-04-20/브랜디드 타입.md b/01_Archive/2026-04-20/브랜디드 타입.md index efceb0cd..eaef5b7e 100644 --- a/01_Archive/2026-04-20/브랜디드 타입.md +++ b/01_Archive/2026-04-20/브랜디드 타입.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-94A8AB -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 브랜디드 타입" --- -# [[브랜디드 타입]] +# [[브랜디드 타입|브랜디드 타입]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -29,11 +29,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 브랜디드 타입" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[구조적 타이핑]], [[명목적 타이핑]], [[Opaque Types]] -- **Projects/Contexts:** [[도메인 기반 설계(DDD)]], [[런타임 유효성 검사(Zod)]] +- **Related Topics:** [[구조적 타이핑|구조적 타이핑]], 명목적 타이핑, [[Opaque Types|Opaque Types]] +- **Projects/Contexts:** [[도메인 기반 설계(DDD)|도메인 기반 설계(DDD)]], 런타임 유효성 검사(Zod) - **Contradictions/Notes:** TypeScript에서 공식적으로 브랜디드 타입(명목적 타이핑)을 내장 기능으로 지원하지는 않으며, 개발자가 `&` 연산자와 가상 속성을 이용해 우회적으로 구현하는 방식입니다 [6, 8]. 또한, 이 기법은 코드의 정밀성을 높여주지만 복잡성 역시 증가시키므로, 실제 이점이 단점을 상회하는지 신중히 판단하고 대안(예: 단순 Union이나 Enum)을 사용하는 방법도 함께 고려해야 합니다 [22, 26]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/브랜디드 타입.md]] +- Raw Source: 00_Raw/2026-04-20/브랜디드 타입.md --- diff --git a/01_Archive/2026-04-20/비동기 데이터 패칭 (Async Operations Pattern).md b/01_Archive/2026-04-20/비동기 데이터 패칭 (Async Operations Pattern).md index bdf06d92..5155e209 100644 --- a/01_Archive/2026-04-20/비동기 데이터 패칭 (Async Operations Pattern).md +++ b/01_Archive/2026-04-20/비동기 데이터 패칭 (Async Operations Pattern).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-C7F096 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 비동기 데이터 패칭 (Async Operations Pattern)" --- -# [[비동기 데이터 패칭 (Async Operations Pattern)]] +# [[비동기 데이터 패칭 (Async Operations Pattern)|비동기 데이터 패칭 (Async Operations Pattern)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 비동기 데이터 패칭(Async Operations Pattern)은 API 요청과 같은 비동기 작업 및 UI 상태를 안전하게 관리하기 위한 재사용 가능한 아키텍처 패턴입니다. 주로 식별 가능한 유니온(Discriminated Unions)을 활용하여 로딩, 성공, 실패와 같은 다양한 상태를 모델링하며, 런타임 및 컴파일 단계에서 유효하지 않은 상태가 발생하는 것을 원천적으로 차단합니다. 이를 통해 애플리케이션의 상태 전환을 예측 가능하고 타입 안전(Type-safe)하게 만듭니다 [1-3]. @@ -22,11 +22,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 비동기 데이터 패칭 (As - **정책 변화:** Design & Experience 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[식별 가능한 유니온 (Discriminated Unions)]], [[상태 머신 (State Machine Pattern)]], [[런타임 유효성 검사 (Runtime Validation)]] -- **Projects/Contexts:** [[API 응답 처리 (API Response Handling)]], [[비동기 UI 상태 관리 (Async UI State)]] +- **Related Topics:** [[식별 가능한 유니온 (Discriminated Unions)|식별 가능한 유니온 (Discriminated Unions)]], 상태 머신 (State Machine Pattern), 런타임 유효성 검사 (Runtime Validation) +- **Projects/Contexts:** API 응답 처리 (API Response Handling), 비동기 UI 상태 관리 (Async UI State) - **Contradictions/Notes:** 소스 내에서 비동기 데이터 패칭 패턴 자체에 대한 상충되는 의견은 없으나, 타입스크립트의 구조적 타이핑 특성상 컴파일 타임의 에러 방지만으로는 외부 비동기 데이터의 무결성을 완벽히 보장할 수 없다는 한계가 존재합니다. 따라서 외부 API나 설정 파일에서 전달받는 비동기 상태 데이터는 반드시 런타임 유효성 검사를 병행해야 한다고 강조하고 있습니다 [6, 7]. (소스에 비동기 데이터 패칭의 구체적인 코드 구현 예시 정보는 일부 누락되어 있어 관련 정보가 부족합니다.) --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/비동기 데이터 패칭 (Async Operations Pattern).md]] +- Raw Source: 00_Raw/2026-04-20/비동기 데이터 패칭 (Async Operations Pattern).md --- diff --git a/01_Archive/2026-04-20/비즈니스 도메인 모델링 (Business Domain Modeling).md b/01_Archive/2026-04-20/비즈니스 도메인 모델링 (Business Domain Modeling).md index 7e9b0cf2..e536e0c9 100644 --- a/01_Archive/2026-04-20/비즈니스 도메인 모델링 (Business Domain Modeling).md +++ b/01_Archive/2026-04-20/비즈니스 도메인 모델링 (Business Domain Modeling).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-980499 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 비즈니스 도메인 모델링 (Business Domain Modeling)" --- -# [[비즈니스 도메인 모델링 (Business Domain Modeling)]] +# [[비즈니스 도메인 모델링 (Business Domain Modeling)|비즈니스 도메인 모델링 (Business Domain Modeling)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 비즈니스 도메인 모델링은 기술 팀과 도메인 전문가가 긴밀히 협력하여 실제 비즈니스 프로세스를 정확하게 반영하는 소프트웨어 모델을 구축하는 접근 방식입니다 [1]. 이 모델링 과정은 복잡한 비즈니스 로직을 부차적인 것으로 취급하지 않고 애플리케이션의 핵심으로 삼으며, 개발자와 비즈니스 이해관계자 간의 의사소통 격차를 줄이는 '보편적 언어(Ubiquitous Language)'를 생성하여 시스템의 복잡성을 해결하는 것을 목표로 합니다 [1]. 이를 통해 크고 복잡한 비즈니스 도메인을 작고 관리하기 쉬운 하위 도메인으로 나누어 체계적으로 구조화할 수 있습니다 [2]. @@ -29,11 +29,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 비즈니스 도메인 모델 - **정책 변화:** AI 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Domain-Driven Design (DDD)]], [[Bounded Contexts]], [[Ubiquitous Language]], [[Entities]], [[Clean Architecture]] -- **Projects/Contexts:** [[마이크로서비스 아키텍처 (Microservices Architecture)]] (비즈니스 도메인 역량을 중심으로 세분화된 작고 자율적인 서비스 집합으로 시스템을 구축할 때 주요하게 활용됩니다 [8]), [[복잡한 비즈니스 도메인 프로젝트]] (금융, 의료, 이커머스 등 비즈니스 규칙이 방대하고 복잡한 엔터프라이즈 시스템 구축에 특히 이상적입니다 [9]). +- **Related Topics:** [[Domain-Driven Design (DDD)|Domain-Driven Design (DDD)]], [[Bounded Contexts|Bounded Contexts]], [[보편적 언어 (Ubiquitous Language)|Ubiquitous Language]], [[엔티티 (Entities)|Entities]], [[Clean Architecture|Clean Architecture]] +- **Projects/Contexts:** [[마이크로서비스 아키텍처 (Microservices Architecture)|마이크로서비스 아키텍처 (Microservices Architecture)]] (비즈니스 도메인 역량을 중심으로 세분화된 작고 자율적인 서비스 집합으로 시스템을 구축할 때 주요하게 활용됩니다 [8]), 복잡한 비즈니스 도메인 프로젝트 (금융, 의료, 이커머스 등 비즈니스 규칙이 방대하고 복잡한 엔터프라이즈 시스템 구축에 특히 이상적입니다 [9]). - **Contradictions/Notes:** 관련 주제 및 구현 방식에 있어서 소스 간 직접적인 모순은 없으나, 도메인 중심 모델링은 심층적인 도메인 분석과 도메인 전문가와의 지속적인 협력이 요구되므로 구현 복잡성(Implementation Complexity)이 매우 높습니다 [9]. 따라서 단순한 시스템보다는 비즈니스 로직이 핵심인 장기적이고 중대한(Mission-critical) 시스템에 적용하는 것이 권장됩니다 [7, 9]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/비즈니스 도메인 모델링 (Business Domain Modeling).md]] +- Raw Source: 00_Raw/2026-04-20/비즈니스 도메인 모델링 (Business Domain Modeling).md --- diff --git a/01_Archive/2026-04-20/비트 세이버 엑서게임 후유증 평가(Beat Saber Exergaming Aftereffects).md b/01_Archive/2026-04-20/비트 세이버 엑서게임 후유증 평가(Beat Saber Exergaming Aftereffects).md index 1ef4bc01..f3130565 100644 --- a/01_Archive/2026-04-20/비트 세이버 엑서게임 후유증 평가(Beat Saber Exergaming Aftereffects).md +++ b/01_Archive/2026-04-20/비트 세이버 엑서게임 후유증 평가(Beat Saber Exergaming Aftereffects).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-B4568F -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 비트 세이버 엑서게임 후유증 평가(Beat Saber Exergaming Aftereffects)" --- -# [[비트 세이버 엑서게임 후유증 평가(Beat Saber Exergaming Aftereffects)]] +# [[비트 세이버 엑서게임 후유증 평가(Beat Saber Exergaming Aftereffects)|비트 세이버 엑서게임 후유증 평가(Beat Saber Exergaming Aftereffects)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 비트 세이버 엑서게임 후유증 평가는 인기 있는 VR 엑서게임인 '비트 세이버(Beat Saber)'를 단기(10분) 및 장기(50분) 동안 플레이한 후 시각, 인지, 그리고 자가 보고된 VR 멀미에 미치는 후유증을 조사한 연구입니다 [1]. 전반적으로 대부분의 시각 및 인지적 후유증과 멀미 증상은 VR 종료 40분 후에 기준선으로 회복되었으나, 노출 시간과 개인의 민감도에 따라 회복 정도에 개인차가 존재하는 것으로 나타났습니다 [2]. @@ -23,11 +23,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 비트 세이버 엑서게임 - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[VR 멀미 (VR Sickness)]], [[조절-폭주 불일치 (Vergence-Accommodation Conflict)]] -- **Projects/Contexts:** [[HMD(Head-Mounted Display) 기반 엑서게임 환경]] +- **Related Topics:** [[VR 멀미 (VR Sickness)|VR 멀미 (VR Sickness)]], [[조절-폭주 불일치 (Vergence-Accommodation Conflict)|조절-폭주 불일치 (Vergence-Accommodation Conflict)]] +- **Projects/Contexts:** [[HMD(Head-Mounted Display) 기반 엑서게임 환경|HMD(Head-Mounted Display) 기반 엑서게임 환경]] - **Contradictions/Notes:** 소스에 따르면 그룹 전체의 평균을 냈을 때는 VR 종료 40분 후 멀미 증상이 기준선으로 회복된 것으로 나타나 문제없어 보이지만, 개별 데이터를 살펴보면 50분 플레이어의 약 14%는 여전히 높은 수준의 멀미를 경험하고 있어 그룹 평균이 개인의 후유증 지속성을 완벽히 대변하지는 못한다는 한계를 지적합니다 [7]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/비트 세이버 엑서게임 후유증 평가(Beat Saber Exergaming Aftereffects).md]] +- Raw Source: 00_Raw/2026-04-20/비트 세이버 엑서게임 후유증 평가(Beat Saber Exergaming Aftereffects).md --- diff --git a/01_Archive/2026-04-20/비트 세이버(Beat Saber) VR 엑서게임 연구.md b/01_Archive/2026-04-20/비트 세이버(Beat Saber) VR 엑서게임 연구.md index 2569fac8..29967375 100644 --- a/01_Archive/2026-04-20/비트 세이버(Beat Saber) VR 엑서게임 연구.md +++ b/01_Archive/2026-04-20/비트 세이버(Beat Saber) VR 엑서게임 연구.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-6BEB16 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 비트 세이버(Beat Saber) VR 엑서게임 연구" --- -# [[비트 세이버(Beat Saber) VR 엑서게임 연구]] +# [[비트 세이버(Beat Saber) VR 엑서게임 연구|비트 세이버(Beat Saber) VR 엑서게임 연구]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -33,11 +33,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 비트 세이버(Beat Saber) V - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[VR 멀미(VR sickness)]], [[엑서게임(Exergaming)]], [[시뮬레이터 멀미 설문지(SSQ)]], [[몰입(Flow)]], [[수렴-조절 불일치(Vergence-accommodation conflict)]] -- **Projects/Contexts:** [[비트 세이버 VR 엑서게임 후유증 실험]] +- **Related Topics:** [[VR 멀미(VR sickness)|VR 멀미(VR sickness)]], [[엑서게임(Exergaming)|엑서게임(Exergaming)]], [[시뮬레이터 멀미 설문지(SSQ)|시뮬레이터 멀미 설문지(SSQ)]], 몰입(Flow), [[수렴-조절 불일치(Vergence-Accommodation Conflict)|수렴-조절 불일치(Vergence-accommodation conflict)]] +- **Projects/Contexts:** 비트 세이버 VR 엑서게임 후유증 실험 - **Contradictions/Notes:** 소스는 집단 평균적으로 볼 때 VR 종료 40분 후 멀미 증상이 기저치로 돌아온다고 밝히고 있지만, 개별 데이터에서는 50분 노출자 중 약 14%가 40분 후에도 여전히 심각한 수준의 멀미(High SSQ score)를 겪었다고 모순된 양상을 지적합니다. 따라서 그룹 평균 회복력이 모든 개인의 안전을 보장하는 지표로 쓰일 수는 없음에 주의해야 합니다 [6]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/비트 세이버(Beat Saber) VR 엑서게임 연구.md]] +- Raw Source: 00_Raw/2026-04-20/비트 세이버(Beat Saber) VR 엑서게임 연구.md --- diff --git a/01_Archive/2026-04-20/비트 세이버(Beat Saber) 실험.md b/01_Archive/2026-04-20/비트 세이버(Beat Saber) 실험.md index 27608f70..e9a3f609 100644 --- a/01_Archive/2026-04-20/비트 세이버(Beat Saber) 실험.md +++ b/01_Archive/2026-04-20/비트 세이버(Beat Saber) 실험.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-A4020A -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 비트 세이버(Beat Saber) 실험" --- -# [[비트 세이버(Beat Saber) 실험]] +# [[비트 세이버(Beat Saber) 실험|비트 세이버(Beat Saber) 실험]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 비트 세이버(Beat Saber) 실험은 널리 알려진 가상현실(VR) 엑서게임(exergame)인 '비트 세이버'를 활용하여 VR 노출 시간이 사용자의 시각, 인지 및 사이버스멀미(VR sickness)에 미치는 후유증을 조사한 연구입니다 [1]. 36명의 참가자를 대상으로 10분(단기) 및 50분(장기) 동안 게임을 플레이하게 한 후, VR 사용 전, 직후, 그리고 40분 후의 상태 변화를 측정했습니다 [1]. 이 실험은 VR 엑서게임의 잠재적 이점을 고려할 때 지속적인 사용을 제한하는 부작용을 식별하고 안전한 사용 환경을 이해하는 데 중점을 두었습니다 [1]. @@ -24,11 +24,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 비트 세이버(Beat Saber) - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[사이버스멀미(VR Sickness)]], [[엑서게임(Exergaming)]], [[시뮬레이터 멀미 설문지(SSQ)]] -- **Projects/Contexts:** [[가상현실 엑서게임 후유증 조사(Investigation of Virtual Reality Aftereffects)]] +- **Related Topics:** 사이버스멀미(VR Sickness), [[엑서게임(Exergaming)|엑서게임(Exergaming)]], [[시뮬레이터 멀미 설문지(SSQ)|시뮬레이터 멀미 설문지(SSQ)]] +- **Projects/Contexts:** 가상현실 엑서게임 후유증 조사(Investigation of Virtual Reality Aftereffects) - **Contradictions/Notes:** 연구 결과에서 그룹 평균적으로는 50분간의 VR 노출 후 40분이 지나면 멀미 증상이 기준치로 돌아온다고 보고하지만, 개별 참가자 데이터를 분석하면 약 14%의 인원은 40분 후에도 여전히 높은 수준의 멀미를 경험한다는 점에서 그룹 평균과 개인별 회복 양상 간에 뚜렷한 차이가 존재함을 지적합니다 [5], [10], [11]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/비트 세이버(Beat Saber) 실험.md]] +- Raw Source: 00_Raw/2026-04-20/비트 세이버(Beat Saber) 실험.md --- diff --git a/01_Archive/2026-04-20/비트 세이버(Beat Saber) 엑서게임 연구.md b/01_Archive/2026-04-20/비트 세이버(Beat Saber) 엑서게임 연구.md index 1edc0908..5a2dacd4 100644 --- a/01_Archive/2026-04-20/비트 세이버(Beat Saber) 엑서게임 연구.md +++ b/01_Archive/2026-04-20/비트 세이버(Beat Saber) 엑서게임 연구.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-1C6F5C -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 비트 세이버(Beat Saber) 엑서게임 연구" --- -# [[비트 세이버(Beat Saber) 엑서게임 연구]] +# [[비트 세이버(Beat Saber) 엑서게임 연구|비트 세이버(Beat Saber) 엑서게임 연구]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 이 연구는 전 세계적으로 인기 있는 가상현실(VR) 엑서게임인 '비트 세이버(Beat Saber)'를 플레이한 후 사용자에게 나타나는 시각적, 인지적, 신체적 사후 영향(Aftereffects)을 조사한 결과입니다 [1, 2]. 참가자들이 10분(단기) 및 50분(장기) 동안 게임을 플레이한 후 조절력, 수렴력, 인지 반응 속도, VR 멀미 수준이 어떻게 변화하는지 측정했습니다 [3]. 연구 결과 게임 플레이로 인한 대부분의 부작용은 일시적이었으나, 장시간 플레이할 경우 VR 멀미 증상이 유의미하게 증가하며 일부 사용자는 회복에 긴 시간이 필요한 것으로 나타났습니다 [4]. @@ -24,11 +24,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 비트 세이버(Beat Saber) - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[VR 멀미(VR Sickness)]], [[엑서게임(Exergaming)]], [[시뮬레이터 멀미 설문지(SSQ)]] -- **Projects/Contexts:** [[비트 세이버(Beat Saber) VR 사후 영향 조사 연구]] +- **Related Topics:** [[VR 멀미 (VR Sickness)|VR 멀미(VR Sickness)]], [[엑서게임(Exergaming)|엑서게임(Exergaming)]], [[시뮬레이터 멀미 설문지(SSQ)|시뮬레이터 멀미 설문지(SSQ)]] +- **Projects/Contexts:** 비트 세이버(Beat Saber) VR 사후 영향 조사 연구 - **Contradictions/Notes:** 연구 결과에서 엑서게임 직후의 멀미 증상은 그룹 평균치로 보았을 때 40분 이내에 완전히 회복되는 것으로 나타났으나, 개인차를 고려할 때 50분 장기 플레이를 한 참가자의 약 14%는 40분 후에도 회복되지 않은 높은 수준의 증상을 보인다는 점을 유의해야 합니다 [15]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/비트 세이버(Beat Saber) 엑서게임 연구.md]] +- Raw Source: 00_Raw/2026-04-20/비트 세이버(Beat Saber) 엑서게임 연구.md --- diff --git a/01_Archive/2026-04-20/비트 세이버(Beat Saber).md b/01_Archive/2026-04-20/비트 세이버(Beat Saber).md index 15e180d6..bb5d39b0 100644 --- a/01_Archive/2026-04-20/비트 세이버(Beat Saber).md +++ b/01_Archive/2026-04-20/비트 세이버(Beat Saber).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-4E9962 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 비트 세이버(Beat Saber)" --- -# [[비트 세이버(Beat Saber)]] +# [[비트 세이버(Beat Saber)|비트 세이버(Beat Saber)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 비트 세이버(Beat Saber)는 비트 게임즈(Beat Games)에서 개발한 상업용 가상 현실(VR) 리듬 운동 게임(exergame)으로, 전 세계적으로 200만 장 이상 판매된 가장 성공적인 게임 중 하나입니다 [1, 2]. 이 게임은 모션 트래킹 기술을 활용하여 핸드헬드 컨트롤러를 광선검처럼 시뮬레이션하며, 사용자는 음악의 비트에 맞춰 날아오는 목표물을 베고 장애물을 적극적으로 피해야 합니다 [2]. 또한 햅틱, 청각 및 성과 피드백을 결합하여 높은 몰입감을 선사하며, 실제 테니스를 치는 것과 비슷한 수준의 에너지를 소모하게 하는 특징이 있습니다 [1, 2]. @@ -22,11 +22,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 비트 세이버(Beat Saber)" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[운동 게임(Exergame)]], [[몰입 상태(Flow State)]], [[가상 현실 멀미(VR Sickness)]] -- **Projects/Contexts:** [[가상 현실 후유증 조사(Investigation of Virtual Reality Aftereffects)]] +- **Related Topics:** 운동 게임(Exergame), 몰입 상태(Flow State), [[가상현실 멀미 (VR Sickness)|가상 현실 멀미(VR Sickness)]] +- **Projects/Contexts:** 가상 현실 후유증 조사(Investigation of Virtual Reality Aftereffects) - **Contradictions/Notes:** 소스에 관련 정보가 부족합니다. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/비트 세이버(Beat Saber).md]] +- Raw Source: 00_Raw/2026-04-20/비트 세이버(Beat Saber).md --- diff --git a/01_Archive/2026-04-20/비트 세이버를 활용한 가상현실 엑서게임 후유증 연구(Exergaming With Beat Saber_ An Investigation of Virtual Reality Aftereffects).md b/01_Archive/2026-04-20/비트 세이버를 활용한 가상현실 엑서게임 후유증 연구(Exergaming With Beat Saber_ An Investigation of Virtual Reality Aftereffects).md index da46aa80..679ecfad 100644 --- a/01_Archive/2026-04-20/비트 세이버를 활용한 가상현실 엑서게임 후유증 연구(Exergaming With Beat Saber_ An Investigation of Virtual Reality Aftereffects).md +++ b/01_Archive/2026-04-20/비트 세이버를 활용한 가상현실 엑서게임 후유증 연구(Exergaming With Beat Saber_ An Investigation of Virtual Reality Aftereffects).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-F5F82B -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 비트 세이버를 활용한 가상현실 엑서게임 후유증 연구(Exergaming With Beat Saber_ An Investigation of Virtual Reality Aftereffects)" --- -# [[비트 세이버를 활용한 가상현실 엑서게임 후유증 연구(Exergaming With Beat Saber_ An Investigation of Virtual Reality Aftereffects)]] +# [[비트 세이버를 활용한 가상현실 엑서게임 후유증 연구(Exergaming With Beat Saber_ An Investigation of Virtual Reality Aftereffects)|비트 세이버를 활용한 가상현실 엑서게임 후유증 연구(Exergaming With Beat Saber_ An Investigation of Virtual Reality Aftereffects)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 본 연구는 인기 있는 가상현실(VR) 엑서게임인 '비트 세이버(Beat Saber)'를 단기(10분) 및 장기(50분) 동안 플레이한 후 시각, 인지 및 주관적 VR 멀미(VR sickness)에 미치는 후유증을 조사한 것입니다 [1]. 36명의 참가자를 대상으로 VR 노출 전, 노출 직후, 그리고 노출 40분 후(지연 측정)의 상태를 반복적으로 평가했습니다 [1]. 연구 결과 게임은 전반적으로 잘 수용되었으며 대부분의 후유증은 단기적이었으나, 일부 참가자들에게서는 40분 이후에도 멀미 증상이 지속되는 등 개인차가 존재함이 확인되었습니다 [2]. @@ -23,11 +23,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 비트 세이버를 활용한 - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[가상현실 멀미(VR sickness)]], [[엑서게임(Exergaming)]], [[시뮬레이터 멀미 설문지(Simulator Sickness Questionnaire, SSQ)]], [[조절과 수렴(Accommodation and Convergence)]] -- **Projects/Contexts:** [[Journal of Medical Internet Research (JMIR) 게재 연구]], [[비트 세이버(Beat Saber) 사용자 실험]] +- **Related Topics:** [[가상현실 멀미 (VR Sickness)|가상현실 멀미(VR sickness)]], [[엑서게임(Exergaming)|엑서게임(Exergaming)]], 시뮬레이터 멀미 설문지(Simulator Sickness Questionnaire, SSQ), 조절과 수렴(Accommodation and Convergence) +- **Projects/Contexts:** Journal of Medical Internet Research (JMIR) 게재 연구, 비트 세이버(Beat Saber) 사용자 실험 - **Contradictions/Notes:** 소스에 따르면, 그룹 전체의 통계적 평균을 기준으로 보았을 때는 VR 종료 40분 후 참가자들의 멀미 증상이 기준치 수준으로 회복된 것으로 나타납니다. 하지만 개별 데이터를 확인했을 때 50분 플레이한 참가자의 약 14%는 40분이 지난 후에도 여전히 '높은 수준'의 멀미를 경험하고 있어, 통계적 평균과 개인의 실제 회복 경험 사이에는 차이와 예외가 존재합니다 [2], [8]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/비트 세이버를 활용한 가상현실 엑서게임 후유증 연구(Exergaming With Beat Saber_ An Investigation of Virtual Reality Aftereffects).md]] +- Raw Source: 00_Raw/2026-04-20/비트 세이버를 활용한 가상현실 엑서게임 후유증 연구(Exergaming With Beat Saber_ An Investigation of Virtual Reality Aftereffects).md --- diff --git a/01_Archive/2026-04-20/빌보드 임포스터(Billboard Impostors).md b/01_Archive/2026-04-20/빌보드 임포스터(Billboard Impostors).md index 2eba1e4c..d73baab5 100644 --- a/01_Archive/2026-04-20/빌보드 임포스터(Billboard Impostors).md +++ b/01_Archive/2026-04-20/빌보드 임포스터(Billboard Impostors).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-143607 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 빌보드 임포스터(Billboard Impostors)" --- -# [[빌보드 임포스터(Billboard Impostors)]] +# [[빌보드 임포스터(Billboard Impostors)|빌보드 임포스터(Billboard Impostors)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 빌보드 임포스터(Billboard Impostor)는 카메라에서 멀리 떨어진 복잡한 3D 지오메트리를 미리 렌더링된 이미지가 맵핑된 카메라를 향하는 2D 평면(Quad)으로 대체하는 렌더링 최적화 기법입니다 [1]. 모델을 여러 각도(보통 8~16개)에서 캡처한 이미지를 사용하여 3D 객체와 같은 착시를 만들어냅니다 [1]. 렌더링에 필요한 폴리곤 수를 단 2개로 줄여 GPU 리소스 소모를 99.9%까지 감소시키며, 배경 캐릭터나 식생, 먼 거리의 환경 디테일을 표현하는 데 매우 효과적입니다 [1, 2]. @@ -22,11 +22,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 빌보드 임포스터(Billboa - **정책 변화:** AI 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Level of Detail (LOD)]], [[Texture Atlas/Array]], [[Draw Call Optimization]] -- **Projects/Contexts:** [[대규모 3D 환경 렌더링(Large-scale environments)]], [[Three.js 성능 최적화]], [[Tesseract 엔진(Tesseract Engine)]] +- **Related Topics:** [[Level of Detail (LOD)|Level of Detail (LOD)]], Texture Atlas/Array, [[Draw Call Optimization|Draw Call Optimization]] +- **Projects/Contexts:** 대규모 3D 환경 렌더링(Large-scale environments), [[Three.js 성능 최적화|Three.js 성능 최적화]], Tesseract 엔진(Tesseract Engine) - **Contradictions/Notes:** 소스에 따르면 빌보드 임포스터는 GPU 연산량을 획기적으로 줄여주지만, 다각도의 텍스처를 유지해야 하는 메모리 비용 부담이 따르며 각도 전환 시 시각적인 '팝핑(Popping)' 결함이 발생할 수 있습니다 [4]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/빌보드 임포스터(Billboard Impostors).md]] +- Raw Source: 00_Raw/2026-04-20/빌보드 임포스터(Billboard Impostors).md --- diff --git a/01_Archive/2026-04-20/사용성 공학 (Usability Engineering).md b/01_Archive/2026-04-20/사용성 공학 (Usability Engineering).md index d51d4df4..f4f6a0e8 100644 --- a/01_Archive/2026-04-20/사용성 공학 (Usability Engineering).md +++ b/01_Archive/2026-04-20/사용성 공학 (Usability Engineering).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-5E0332 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 사용성 공학 (Usability Engineering)" --- -# [[사용성 공학 (Usability Engineering)]] +# [[사용성 공학 (Usability Engineering)|사용성 공학 (Usability Engineering)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - 사용성 공학 (Usability En ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/사용성 공학 (Usability Engineering).md]] +- Raw Source: 00_Raw/2026-04-20/사용성 공학 (Usability Engineering).md --- diff --git a/01_Archive/2026-04-20/사용자 경험 (UX) 디자인.md b/01_Archive/2026-04-20/사용자 경험 (UX) 디자인.md index 7e17747a..17437639 100644 --- a/01_Archive/2026-04-20/사용자 경험 (UX) 디자인.md +++ b/01_Archive/2026-04-20/사용자 경험 (UX) 디자인.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-A602EE -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 사용자 경험 (UX) 디자인" --- -# [[사용자 경험 (UX) 디자인]] +# [[사용자 경험 (UX) 디자인|사용자 경험 (UX) 디자인]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - 사용자 경험 (UX) 디자 ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/사용자 경험 (UX) 디자인.md]] +- Raw Source: 00_Raw/2026-04-20/사용자 경험 (UX) 디자인.md --- diff --git a/01_Archive/2026-04-20/사용자 경험 (UX).md b/01_Archive/2026-04-20/사용자 경험 (UX).md index 4bb8c014..4251e754 100644 --- a/01_Archive/2026-04-20/사용자 경험 (UX).md +++ b/01_Archive/2026-04-20/사용자 경험 (UX).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-121347 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 사용자 경험 (UX)" --- -# [[사용자 경험 (UX)]] +# [[사용자 경험 (UX)|사용자 경험 (UX)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - 사용자 경험 (UX)" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/사용자 경험 (UX).md]] +- Raw Source: 00_Raw/2026-04-20/사용자 경험 (UX).md --- diff --git a/01_Archive/2026-04-20/사용자 경험 디자인 (UX Design).md b/01_Archive/2026-04-20/사용자 경험 디자인 (UX Design).md index 873b71d8..7a904813 100644 --- a/01_Archive/2026-04-20/사용자 경험 디자인 (UX Design).md +++ b/01_Archive/2026-04-20/사용자 경험 디자인 (UX Design).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-EA48D7 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 사용자 경험 디자인 (UX Design)" --- -# [[사용자 경험 디자인 (UX Design)]] +# [[사용자 경험 디자인 (UX Design)|사용자 경험 디자인 (UX Design)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - 사용자 경험 디자인 (UX ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/사용자 경험 디자인 (UX Design).md]] +- Raw Source: 00_Raw/2026-04-20/사용자 경험 디자인 (UX Design).md --- diff --git a/01_Archive/2026-04-20/사회 인지 이론(Social Cognitive Theory).md b/01_Archive/2026-04-20/사회 인지 이론(Social Cognitive Theory).md index 4c6af097..478d8bb1 100644 --- a/01_Archive/2026-04-20/사회 인지 이론(Social Cognitive Theory).md +++ b/01_Archive/2026-04-20/사회 인지 이론(Social Cognitive Theory).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-091F7D -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 사회 인지 이론(Social Cognitive Theory)" --- -# [[사회 인지 이론(Social Cognitive Theory)]] +# [[사회 인지 이론(Social Cognitive Theory)|사회 인지 이론(Social Cognitive Theory)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - 사회 인지 이론(Social Co ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/사회 인지 이론(Social Cognitive Theory).md]] +- Raw Source: 00_Raw/2026-04-20/사회 인지 이론(Social Cognitive Theory).md --- diff --git a/01_Archive/2026-04-20/사회 학습 이론.md b/01_Archive/2026-04-20/사회 학습 이론.md index e8dcb4ba..688ac53c 100644 --- a/01_Archive/2026-04-20/사회 학습 이론.md +++ b/01_Archive/2026-04-20/사회 학습 이론.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-D860B8 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 사회 학습 이론" --- -# [[사회 학습 이론]] +# [[사회 학습 이론|사회 학습 이론]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - 사회 학습 이론" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/사회 학습 이론.md]] +- Raw Source: 00_Raw/2026-04-20/사회 학습 이론.md --- diff --git a/01_Archive/2026-04-20/사회학습이론.md b/01_Archive/2026-04-20/사회학습이론.md index a1fa5607..c7d6e5c9 100644 --- a/01_Archive/2026-04-20/사회학습이론.md +++ b/01_Archive/2026-04-20/사회학습이론.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-4EE4B7 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 사회학습이론" --- -# [[사회학습이론]] +# [[사회 학습 이론|사회학습이론]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - 사회학습이론" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/사회학습이론.md]] +- Raw Source: 00_Raw/2026-04-20/사회학습이론.md --- diff --git a/01_Archive/2026-04-20/상태 관리 및 API 응답 모델링(State Management and API Response Modeling).md b/01_Archive/2026-04-20/상태 관리 및 API 응답 모델링(State Management and API Response Modeling).md index 48523436..a2b42d75 100644 --- a/01_Archive/2026-04-20/상태 관리 및 API 응답 모델링(State Management and API Response Modeling).md +++ b/01_Archive/2026-04-20/상태 관리 및 API 응답 모델링(State Management and API Response Modeling).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-397C6D -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 상태 관리 및 API 응답 모델링(State Management and API Response Modeling)" --- -# [[상태 관리 및 API 응답 모델링(State Management and API Response Modeling)]] +# [[상태 관리 및 API 응답 모델링(State Management and API Response Modeling)|상태 관리 및 API 응답 모델링(State Management and API Response Modeling)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 상태 관리 및 API 응답 모델링은 애플리케이션의 데이터 변화 및 네트워크 통신 결과를 타입 안전하게 구조화하는 기법입니다. 주로 식별 가능한 유니온(Discriminated Unions)을 활용하여 잘못된 상태 조합을 원천 차단하고, 완전성 검사(Exhaustiveness checking)를 통해 모든 가능한 응답 및 상태 케이스를 안전하게 처리하도록 강제합니다. 이를 통해 예측 불가능한 동작을 방지하고 코드의 유지보수성을 극대화할 수 있습니다. @@ -24,11 +24,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 상태 관리 및 API 응답 - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[식별 가능한 유니온(Discriminated Unions)]], [[완전성 검사(Exhaustiveness Checking)]], [[Satisfies 연산자]] -- **Projects/Contexts:** [[React의 상태 관리 및 비동기 UI 처리]], [[네트워크 요청 상태 머신(NetworkState)]] +- **Related Topics:** [[식별 가능한 유니온(Discriminated Unions)|식별 가능한 유니온(Discriminated Unions)]], [[완전성 검사(Exhaustiveness Checking)|완전성 검사(Exhaustiveness Checking)]], [[satisfies 연산자|Satisfies 연산자]] +- **Projects/Contexts:** React의 상태 관리 및 비동기 UI 처리, 네트워크 요청 상태 머신(NetworkState) - **Contradictions/Notes:** 상태나 로직의 실패를 다룰 때 C# 등의 전통적인 환경에서는 예외(Exception)를 발생시키고 글로벌 핸들러로 잡아내는 방식이 흔히 사용되나, 상태 모델링의 명확성 관점에서는 반환형 자체에 실패 상태(Result 객체 등)를 명시하여 제어 흐름과 예상 결과를 호출자가 즉시 파악할 수 있도록 설계하는 방식(Railway oriented programming)이 더 우수하다는 주장이 존재합니다 [20-26]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/상태 관리 및 API 응답 모델링(State Management and API Response Modeling).md]] +- Raw Source: 00_Raw/2026-04-20/상태 관리 및 API 응답 모델링(State Management and API Response Modeling).md --- diff --git a/01_Archive/2026-04-20/상태 관리 최적화 (Zustand Jotai Valtio).md b/01_Archive/2026-04-20/상태 관리 최적화 (Zustand Jotai Valtio).md index b933142b..9e659591 100644 --- a/01_Archive/2026-04-20/상태 관리 최적화 (Zustand Jotai Valtio).md +++ b/01_Archive/2026-04-20/상태 관리 최적화 (Zustand Jotai Valtio).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-5B0AFD -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 상태 관리 최적화 (Zustand Jotai Valtio)" --- -# [[상태 관리 최적화 (Zustand Jotai Valtio)]] +# [[상태 관리 최적화 (Zustand Jotai Valtio)|상태 관리 최적화 (Zustand Jotai Valtio)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > React의 기본 Context API가 유발하는 불필요한 연쇄 리렌더링 문제를 극복하기 위해, 상태 업데이트 빈도와 아키텍처에 맞춰 각기 다른 철학(Flux, Atomic, Proxy)을 가진 최신 경량 상태 관리 라이브러리를 도입하여 필요한 컴포넌트만 정밀하게 렌더링(Fine-grained reactivity)하는 성능 최적화 기법입니다. @@ -37,12 +37,12 @@ github_commit: "[P-Reinforce] Continuous Worker - 상태 관리 최적화 (Zusta - **정책 변화:** AI 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[불필요한 리렌더링 방지]], [[React Context API 한계]], [[React Performance Optimization]], [[가변 프록시(Mutable Proxy) 상태]] -- **Projects/Contexts:** [[장기 실행되는 실시간 데이터 대시보드 최적화]], [[고성능 실시간 상호작용 시스템을 위한 React 기반 게임 엔진 아키텍처]] +- **Related Topics:** [[불필요한 리렌더링 방지|불필요한 리렌더링 방지]], React Context API 한계, [[React Performance Optimization|React Performance Optimization]], 가변 프록시(Mutable Proxy) 상태 +- **Projects/Contexts:** [[장기 실행되는 실시간 데이터 대시보드 최적화|장기 실행되는 실시간 데이터 대시보드 최적화]], [[고성능 실시간 상호작용 시스템을 위한 React 기반 게임 엔진 아키텍처|고성능 실시간 상호작용 시스템을 위한 React 기반 게임 엔진 아키텍처]] - **Contradictions/Notes:** 많은 개발자들이 Zustand를 도입하기만 하면 성능이 좋아질 것이라 오해하지만, 컴포넌트에서 전체 상태를 가져오거나 셀렉터에서 파생 객체를 무분별하게 반환하면 오히려 성능이 악화될 수 있습니다. 최적의 성능을 위해서는 사용 패턴에 대한 정확한 이해(수동 셀렉터 분리)가 동반되어야 합니다. --- _Last updated: 2026-04-15_ -- Raw Source: [[00_Raw/2026-04-20/상태 관리 최적화 (Zustand, Jotai, Valtio).md]] +- Raw Source: 00_Raw/2026-04-20/상태 관리 최적화 (Zustand, Jotai, Valtio).md --- diff --git a/01_Archive/2026-04-20/상태 관리 최적화 (Zustand Valtio).md b/01_Archive/2026-04-20/상태 관리 최적화 (Zustand Valtio).md index 11a8ee4e..c3ff3294 100644 --- a/01_Archive/2026-04-20/상태 관리 최적화 (Zustand Valtio).md +++ b/01_Archive/2026-04-20/상태 관리 최적화 (Zustand Valtio).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-C69D47 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 상태 관리 최적화 (Zustand Valtio)" --- -# [[상태 관리 최적화 (Zustand Valtio)]] +# [[상태 관리 최적화 (Zustand Valtio)|상태 관리 최적화 (Zustand Valtio)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - 상태 관리 최적화 (Zusta ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/상태 관리 최적화 (Zustand, Valtio).md]] +- Raw Source: 00_Raw/2026-04-20/상태 관리 최적화 (Zustand, Valtio).md --- diff --git a/01_Archive/2026-04-20/상태 관리 최적화 (Zustand, Jotai, Valtio).md b/01_Archive/2026-04-20/상태 관리 최적화 (Zustand, Jotai, Valtio).md index 5e478372..a0f4e3b8 100644 --- a/01_Archive/2026-04-20/상태 관리 최적화 (Zustand, Jotai, Valtio).md +++ b/01_Archive/2026-04-20/상태 관리 최적화 (Zustand, Jotai, Valtio).md @@ -1,4 +1,4 @@ -[[상태 관리 최적화 (Zustand, Jotai, Valtio)]] +[[상태 관리 최적화 (Zustand, Jotai, Valtio)|상태 관리 최적화 (Zustand, Jotai, Valtio)]] ## 📌 Brief Summary @@ -27,8 +27,8 @@ React의 기본 Context API가 유발하는 불필요한 연쇄 리렌더링 문 ## 🔗 Knowledge Connections -- **Related Topics:** [[불필요한 리렌더링 방지]], [[React Context API 한계]], [[React Performance Optimization]], [[가변 프록시(Mutable Proxy) 상태]] -- **Projects/Contexts:** [[장기 실행되는 실시간 데이터 대시보드 최적화]], [[고성능 실시간 상호작용 시스템을 위한 React 기반 게임 엔진 아키텍처]] +- **Related Topics:** [[불필요한 리렌더링 방지|불필요한 리렌더링 방지]], React Context API 한계, [[React Performance Optimization|React Performance Optimization]], 가변 프록시(Mutable Proxy) 상태 +- **Projects/Contexts:** [[장기 실행되는 실시간 데이터 대시보드 최적화|장기 실행되는 실시간 데이터 대시보드 최적화]], [[고성능 실시간 상호작용 시스템을 위한 React 기반 게임 엔진 아키텍처|고성능 실시간 상호작용 시스템을 위한 React 기반 게임 엔진 아키텍처]] - **Contradictions/Notes:** 많은 개발자들이 Zustand를 도입하기만 하면 성능이 좋아질 것이라 오해하지만, 컴포넌트에서 전체 상태를 가져오거나 셀렉터에서 파생 객체를 무분별하게 반환하면 오히려 성능이 악화될 수 있습니다. 최적의 성능을 위해서는 사용 패턴에 대한 정확한 이해(수동 셀렉터 분리)가 동반되어야 합니다. --- diff --git a/01_Archive/2026-04-20/상태 관리 최적화 (Zustand, Valtio).md b/01_Archive/2026-04-20/상태 관리 최적화 (Zustand, Valtio).md index d2b6a8e9..3d16ffe5 100644 --- a/01_Archive/2026-04-20/상태 관리 최적화 (Zustand, Valtio).md +++ b/01_Archive/2026-04-20/상태 관리 최적화 (Zustand, Valtio).md @@ -1,4 +1,4 @@ -[[상태 관리 최적화 (Zustand, Valtio)]] +[[상태 관리 최적화 (Zustand, Valtio)|상태 관리 최적화 (Zustand, Valtio)]] 📌 Brief Summary Optimizing state management involves choosing the right tool for the specific reactivity needs of the application. Libraries like Zustand (Action-based) and Valtio (Proxy-based) offer different paradigms to reduce boilerplate and minimize re-renders compared to traditional solutions like Redux or React Context. @@ -18,8 +18,8 @@ Optimizing state management involves choosing the right tool for the specific re * **Transient Updates:** Updating store values without triggering a React render (reading directly via `api.getState()`). 🔗 Knowledge Connections -* Related Topics: [[React 상태 관리 (React State Management)]], [[Redux 등 상태 관리 (State Management)]], [[Reactive-Programming]] -* Projects/Contexts: [[Skybound Protocol UI]], [[Skybound Mission Persistence]] +* Related Topics: [[React 상태 관리 (React State Management)|React 상태 관리 (React State Management)]], [[Redux 등 상태 관리 (State Management)|Redux 등 상태 관리 (State Management)]], [[Reactive-Programming|Reactive-Programming]] +* Projects/Contexts: Skybound Protocol UI, Skybound Mission Persistence * Contradictions/Notes: Proxy-based state (Valtio) can sometimes hide where updates are coming from, making debugging harder in large teams if strict conventions aren't followed. Last updated: 2026-04-18 diff --git a/01_Archive/2026-04-20/상태 관리(State Management).md b/01_Archive/2026-04-20/상태 관리(State Management).md index b92fecbe..2f9b1a5e 100644 --- a/01_Archive/2026-04-20/상태 관리(State Management).md +++ b/01_Archive/2026-04-20/상태 관리(State Management).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-58EC09 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 상태 관리(State Management)" --- -# [[상태 관리(State Management)]] +# [[상태 관리(State Management)|상태 관리(State Management)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 상태 관리(State Management)는 사용자 입력, API 응답, UI 구성 및 애플리케이션 설정 등 시간이 지남에 따라 변경되는 데이터를 추적하고 유지하는 방법론입니다 [1]. 상태 흐름을 명확하게 관리하지 못하면 애플리케이션의 동작을 예측할 수 없게 되고 디버깅이 심각하게 어려워지며, 기술 부채와 성능 문제(불필요한 리렌더링, 메모리 누수 등)를 유발합니다 [2]. TypeScript 환경에서는 식별 가능한 유니온(Discriminated Unions)과 불변성(Immutability) 강제를 통해 무효한 상태를 원천 차단하고 안전하게 상태를 제어할 수 있습니다 [3-5]. @@ -22,11 +22,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 상태 관리(State Management - **정책 변화:** Design & Experience 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[식별 가능한 유니온(Discriminated Unions)]], [[불변성(Immutability)]], [[상태 기계(State Machine)]], [[리듀서(Reducer)]] -- **Projects/Contexts:** [[React 프론트엔드 개발]], [[Redux 아키텍처]] +- **Related Topics:** [[식별 가능한 유니온(Discriminated Unions)|식별 가능한 유니온(Discriminated Unions)]], [[불변성(Immutability)|불변성(Immutability)]], 상태 기계(State Machine), 리듀서(Reducer) +- **Projects/Contexts:** React 프론트엔드 개발, Redux 아키텍처 - **Contradictions/Notes:** 소스 전반에 걸쳐 상태 관리에 있어 불변성 유지(`readonly` 활용)와 타입 시스템(Discriminated Unions)을 통한 엄격한 상태 제어의 중요성에 동의하고 있으며, 상태 관리에 대한 상반된 주장이나 모순점은 발견되지 않았습니다. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/상태 관리(State Management).md]] +- Raw Source: 00_Raw/2026-04-20/상태 관리(State Management).md --- diff --git a/01_Archive/2026-04-20/상태 머신 (State Machine) 모델링 및 Redux 액션_리듀서 설계.md b/01_Archive/2026-04-20/상태 머신 (State Machine) 모델링 및 Redux 액션_리듀서 설계.md index b46bbdb7..bf2dca15 100644 --- a/01_Archive/2026-04-20/상태 머신 (State Machine) 모델링 및 Redux 액션_리듀서 설계.md +++ b/01_Archive/2026-04-20/상태 머신 (State Machine) 모델링 및 Redux 액션_리듀서 설계.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-D423C6 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 상태 머신 (State Machine) 모델링 및 Redux 액션_리듀서 설계" --- -# [[상태 머신 (State Machine) 모델링 및 Redux 액션_리듀서 설계]] +# [[상태 머신 (State Machine) 모델링 및 Redux 액션_리듀서 설계|상태 머신 (State Machine) 모델링 및 Redux 액션_리듀서 설계]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 상태 머신(State Machine) 모델링과 Redux 액션/리듀서 설계는 애플리케이션의 복잡한 상태 전이를 명확하게 정의하고 관리하기 위한 구조적 접근법입니다. 타입스크립트(TypeScript) 환경에서는 주로 식별 가능한 유니온(Discriminated Unions) 패턴을 활용하여 이러한 상태 및 액션들을 안전하고 완벽하게 구현할 수 있습니다 [1-3]. 다만, 제공된 소스에는 이를 구체적으로 설계하는 세부 방법론이나 코드 레벨의 상세한 정보가 부족합니다. @@ -24,11 +24,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 상태 머신 (State Machine) - **정책 변화:** Design & Experience 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[식별 가능한 유니온 (Discriminated Unions)]], [[타입 안전성 (Type Safety)]] -- **Projects/Contexts:** [[React 상태 관리 (React State Management)]], [[비동기 데이터 패칭 (Async Operations Pattern)]] +- **Related Topics:** [[식별 가능한 유니온 (Discriminated Unions)|식별 가능한 유니온 (Discriminated Unions)]], [[타입 안전성 (Type Safety)|타입 안전성 (Type Safety)]] +- **Projects/Contexts:** [[React 상태 관리 (React State Management)|React 상태 관리 (React State Management)]], [[비동기 데이터 패칭 (Async Operations Pattern)|비동기 데이터 패칭 (Async Operations Pattern)]] - **Contradictions/Notes:** 소스에 관련 정보가 부족합니다. 상태 머신 및 Redux 패턴 설계 지침을 다루기보다는, 타입스크립트의 '식별 가능한 유니온'이 활용되기 좋은 대표적인 사례(Use Case) 중 하나로서만 간략히 소개되어 있습니다. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/상태 머신 (State Machine) 모델링 및 Redux 액션_리듀서 설계.md]] +- Raw Source: 00_Raw/2026-04-20/상태 머신 (State Machine) 모델링 및 Redux 액션_리듀서 설계.md --- diff --git a/01_Archive/2026-04-20/상태 머신(State Machine) 설계.md b/01_Archive/2026-04-20/상태 머신(State Machine) 설계.md index b8347314..11d45f99 100644 --- a/01_Archive/2026-04-20/상태 머신(State Machine) 설계.md +++ b/01_Archive/2026-04-20/상태 머신(State Machine) 설계.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-C8AC26 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 상태 머신(State Machine) 설계" --- -# [[상태 머신(State Machine) 설계]] +# [[상태 머신(State Machine) 설계|상태 머신(State Machine) 설계]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 상태 머신(State Machine) 설계는 시스템이 가질 수 있는 다양한 상태와 그 상태 간의 전환을 명확히 정의하는 모델링 기법입니다 [1]. TypeScript에서는 구분된 유니언(Discriminated Unions)을 활용하여 상태 머신을 완벽하게 구현하고 타입 안전성을 보장할 수 있습니다 [1, 2]. 다만, 제공된 소스에는 TypeScript 패턴으로서의 간략한 적용 사례 외에 상태 머신 설계 자체에 대한 심층적인 정보는 부족합니다. @@ -23,11 +23,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 상태 머신(State Machine) - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Discriminated Unions]], [[Exhaustiveness Checking]] -- **Projects/Contexts:** [[API Response Handling]] +- **Related Topics:** [[Discriminated Unions|Discriminated Unions]], [[Exhaustiveness-Checking|Exhaustiveness Checking]] +- **Projects/Contexts:** API Response Handling - **Contradictions/Notes:** 소스에 관련 정보가 부족합니다. 상태 머신의 일반적인 아키텍처나 다양한 설계 패턴에 대한 상세한 이론적 배경은 제공되지 않으며, 오직 TypeScript의 구분된 유니언을 이용한 상태 모델링의 맥락에서만 짧게 언급됩니다 [1, 2]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/상태 머신(State Machine) 설계.md]] +- Raw Source: 00_Raw/2026-04-20/상태 머신(State Machine) 설계.md --- diff --git a/01_Archive/2026-04-20/상태 모델링 (State Modeling).md b/01_Archive/2026-04-20/상태 모델링 (State Modeling).md index b38dca11..81ae30d9 100644 --- a/01_Archive/2026-04-20/상태 모델링 (State Modeling).md +++ b/01_Archive/2026-04-20/상태 모델링 (State Modeling).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-BC8C33 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 상태 모델링 (State Modeling)" --- -# [[상태 모델링 (State Modeling)]] +# [[상태 모델링 (State Modeling)|상태 모델링 (State Modeling)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 상태 모델링은 애플리케이션에서 시간에 따라 변화하는 데이터(사용자 입력, API 응답, UI 설정 등)를 구조화하고 추적하는 과정입니다 [1]. 잘못된 상태 관리는 예측 불가능한 동작과 디버깅의 어려움 등 기술 부채를 초래하므로, 견고한 모델링이 필수적입니다 [2]. TypeScript에서는 주로 식별 가능한 유니온(Discriminated Unions)을 활용하여 "유효하지 않은 상태를 원천적으로 불가능하게 만드는" 상태 머신 패턴을 통해 안전하고 명확하게 상태를 모델링합니다 [3-5]. @@ -24,11 +24,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 상태 모델링 (State Modeli - **정책 변화:** Design & Experience 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[식별 가능한 유니온 (Discriminated Unions)]], [[완전성 검사 (Exhaustiveness Checking)]], [[상태 머신 (State Machine)]] -- **Projects/Contexts:** [[API 응답 처리 (API Response Handling)]], [[폼 제출 워크플로우 (Form Submission Workflow)]] +- **Related Topics:** [[식별 가능한 유니온 (Discriminated Unions)|식별 가능한 유니온 (Discriminated Unions)]], [[완전성 검사 (Exhaustiveness Checking)|완전성 검사 (Exhaustiveness Checking)]], 상태 머신 (State Machine) +- **Projects/Contexts:** API 응답 처리 (API Response Handling), 폼 제출 워크플로우 (Form Submission Workflow) - **Contradictions/Notes:** 소스에 관련 정보가 부족합니다. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/상태 모델링 (State Modeling).md]] +- Raw Source: 00_Raw/2026-04-20/상태 모델링 (State Modeling).md --- diff --git a/01_Archive/2026-04-20/새로운 공간(New Space).md b/01_Archive/2026-04-20/새로운 공간(New Space).md index ca9d103d..0a24ae91 100644 --- a/01_Archive/2026-04-20/새로운 공간(New Space).md +++ b/01_Archive/2026-04-20/새로운 공간(New Space).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-B1F49A -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 새로운 공간(New Space)" --- -# [[새로운 공간(New Space)]] +# [[새로운 공간(New Space)|새로운 공간(New Space)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 새로운 공간(New Space)은 V8 엔진의 힙(Heap) 메모리 구조에서 대부분의 새로운 객체가 최초로 할당되는 작고 빠른 영역입니다 [1, 2]. '젊은 세대(Young Generation)'라고도 불리며, 대부분의 객체가 생성 후 곧바로 소멸한다는 '세대 가설(Generational Hypothesis)'을 바탕으로 설계되었습니다 [3-5]. 이 공간은 다른 힙 공간들과 독립적으로 매우 빠르고 빈번하게 가비지 컬렉션(Garbage Collection)이 수행되도록 최적화되어 있습니다 [1, 6]. @@ -20,11 +20,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 새로운 공간(New Space)" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[스캐빈저(Scavenger) / 마이너 GC]], [[오래된 공간(Old Space)]], [[To-Space와 From-Space]], [[쓰기 장벽(Write Barrier)]] -- **Projects/Contexts:** [[V8 가비지 컬렉션(Garbage Collection)]], [[브라우저 메모리 관리 및 최적화]] +- **Related Topics:** [[스캐빈저(Scavenger) _ 마이너 GC|스캐빈저(Scavenger) / 마이너 GC]], [[오래된 공간(Old Space)|오래된 공간(Old Space)]], [[To-Space와 From-Space|To-Space와 From-Space]], [[쓰기 장벽(Write Barrier)|쓰기 장벽(Write Barrier)]] +- **Projects/Contexts:** [[V8 가비지 컬렉션(Garbage Collection)|V8 가비지 컬렉션(Garbage Collection)]], [[브라우저 메모리 관리 및 최적화|브라우저 메모리 관리 및 최적화]] - **Contradictions/Notes:** 소스 [2]에서는 새로운 공간의 크기를 휴리스틱에 따라 1~8MB로 설명하지만, 소스 [7]에서는 1~64MB로 언급합니다. 이는 V8 엔진의 버전이나 실행 환경, 동적 메모리 할당 정책에 따라 새로운 공간의 최대 한도가 다르게 적용될 수 있음을 보여줍니다. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/새로운 공간(New Space).md]] +- Raw Source: 00_Raw/2026-04-20/새로운 공간(New Space).md --- diff --git a/01_Archive/2026-04-20/생물학적 학습 이론.md b/01_Archive/2026-04-20/생물학적 학습 이론.md index 8a05acc4..851d95f6 100644 --- a/01_Archive/2026-04-20/생물학적 학습 이론.md +++ b/01_Archive/2026-04-20/생물학적 학습 이론.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-A4487C -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 생물학적 학습 이론" --- -# [[생물학적 학습 이론]] +# [[생물학적 학습 이론|생물학적 학습 이론]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - 생물학적 학습 이론" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/생물학적 학습 이론.md]] +- Raw Source: 00_Raw/2026-04-20/생물학적 학습 이론.md --- diff --git a/01_Archive/2026-04-20/서드파티 라이브러리 및 API 연동.md b/01_Archive/2026-04-20/서드파티 라이브러리 및 API 연동.md index 3d023bfe..496380c8 100644 --- a/01_Archive/2026-04-20/서드파티 라이브러리 및 API 연동.md +++ b/01_Archive/2026-04-20/서드파티 라이브러리 및 API 연동.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-ACB5DA -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 서드파티 라이브러리 및 API 연동" --- -# [[서드파티 라이브러리 및 API 연동]] +# [[서드파티 라이브러리 및 API 연동|서드파티 라이브러리 및 API 연동]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 서드파티 라이브러리 및 API 연동은 애플리케이션이 외부 시스템, 패키지, 또는 외부 연동사의 앱과 안전하고 효율적으로 데이터를 교환하고 상호작용하도록 설계하는 과정입니다. TypeScript 생태계에서는 외부에서 유입되는 알 수 없는 데이터를 런타임 및 컴파일 타임에 검증하여 시스템 내부를 보호하는 방어적 설계가 매우 중요합니다. 또한 외부 연동사를 위해 SDK를 제공할 때는 내부의 복잡한 로직을 은닉하고 사용자의 의도에 맞춘 직관적인 인터페이스를 제공하여 구조적으로 휴먼 에러를 방지해야 합니다. @@ -30,11 +30,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 서드파티 라이브러리 - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Parse, Don't Validate]], [[Facade 패턴]], [[식별 가능한 유니온 (Discriminated Unions)]], [[Zod]], [[satisfies 연산자]] -- **Projects/Contexts:** [[Toss Front SDK 연동 설계]], [[OpenAPI 스펙 기반 SDK 자동 생성]], [[Zod를 활용한 런타임 API 데이터 검증]] +- **Related Topics:** [[Parse dont validate|Parse, Don't Validate]], Facade 패턴, [[식별 가능한 유니온 (Discriminated Unions)|식별 가능한 유니온 (Discriminated Unions)]], [[Zod|Zod]], [[satisfies 연산자|satisfies 연산자]] +- **Projects/Contexts:** Toss Front SDK 연동 설계, OpenAPI 스펙 기반 SDK 자동 생성, Zod를 활용한 런타임 API 데이터 검증 - **Contradictions/Notes:** 소스에 따르면 `ts-pattern`과 같은 패턴 매칭 및 복잡한 분기 처리용 서드파티 라이브러리는 타입 안전성에는 도움을 주지만, 내부적인 클래스 및 함수 체이닝 구현 방식으로 인해 자바스크립트의 기본 제어 구조(`if/else`, `switch`)보다 성능이 현저히 떨어질 수 있으므로 무조건적인 도입보다는 상황과 성능 요구치를 고려해 사용해야 합니다 [17-19]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/서드파티 라이브러리 및 API 연동.md]] +- Raw Source: 00_Raw/2026-04-20/서드파티 라이브러리 및 API 연동.md --- diff --git a/01_Archive/2026-04-20/서버리스 컴퓨팅(Serverless Computing).md b/01_Archive/2026-04-20/서버리스 컴퓨팅(Serverless Computing).md index 241f9e76..0b1997ad 100644 --- a/01_Archive/2026-04-20/서버리스 컴퓨팅(Serverless Computing).md +++ b/01_Archive/2026-04-20/서버리스 컴퓨팅(Serverless Computing).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-DE9274 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 서버리스 컴퓨팅(Serverless Computing)" --- -# [[서버리스 컴퓨팅(Serverless Computing)]] +# [[서버리스 컴퓨팅(Serverless Computing)|서버리스 컴퓨팅(Serverless Computing)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -23,11 +23,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 서버리스 컴퓨팅(Serverl - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[클라우드 네이티브 아키텍처(Cloud-Native Architecture)]], [[마이크로서비스 아키텍처(Microservices Architecture)]], [[비동기 워크플로우(Asynchronous Workflows)]] -- **Projects/Contexts:** [[구글 클라우드 런(Google Cloud Run)]], [[넷플릭스 코스모스(Netflix Cosmos)]] +- **Related Topics:** 클라우드 네이티브 아키텍처(Cloud-Native Architecture), [[마이크로서비스 아키텍처 (Microservices Architecture)|마이크로서비스 아키텍처(Microservices Architecture)]], 비동기 워크플로우(Asynchronous Workflows) +- **Projects/Contexts:** 구글 클라우드 런(Google Cloud Run), 넷플릭스 코스모스(Netflix Cosmos) - **Contradictions/Notes:** 소스에 관련 정보가 부족합니다. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/서버리스 컴퓨팅(Serverless Computing).md]] +- Raw Source: 00_Raw/2026-04-20/서버리스 컴퓨팅(Serverless Computing).md --- diff --git a/01_Archive/2026-04-20/서비스 디자인 (Service Design).md b/01_Archive/2026-04-20/서비스 디자인 (Service Design).md index c0cf9fdc..8dc7347c 100644 --- a/01_Archive/2026-04-20/서비스 디자인 (Service Design).md +++ b/01_Archive/2026-04-20/서비스 디자인 (Service Design).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-DB809B -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 서비스 디자인 (Service Design)" --- -# [[서비스 디자인 (Service Design)]] +# [[서비스 디자인 (Service Design)|서비스 디자인 (Service Design)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - 서비스 디자인 (Service D ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/서비스 디자인 (Service Design).md]] +- Raw Source: 00_Raw/2026-04-20/서비스 디자인 (Service Design).md --- diff --git a/01_Archive/2026-04-20/서플라이 체인 보안 (Supply Chain Security).md b/01_Archive/2026-04-20/서플라이 체인 보안 (Supply Chain Security).md index 022b0dfe..3ed86db2 100644 --- a/01_Archive/2026-04-20/서플라이 체인 보안 (Supply Chain Security).md +++ b/01_Archive/2026-04-20/서플라이 체인 보안 (Supply Chain Security).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-E85988 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 서플라이 체인 보안 (Supply Chain Security)" --- -# [[서플라이 체인 보안 (Supply Chain Security)]] +# [[서플라이 체인 보안 (Supply Chain Security)|서플라이 체인 보안 (Supply Chain Security)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 서플라이 체인 보안(Supply Chain Security)은 소프트웨어 공급망, 특히 애플리케이션에 통합되는 오픈소스 종속성 및 서드파티 컴포넌트와 관련된 위험을 완화하는 데 중점을 두는 보안 영역입니다 [1, 2]. 이는 합법적인 패키지가 손상되거나 메인테이너 계정이 탈취되어 악성 코드가 배포되는 공급망 공격으로부터 소프트웨어 개발 파이프라인을 보호하는 과정을 포함합니다 [3-5]. 이러한 공급망 위험을 관리하고 라이선스 정책 등을 강제하기 위해 SCA(소프트웨어 구성 분석) 도구와 SBOM(소프트웨어 자재 명세서) 활용이 필수적입니다 [1, 2]. @@ -29,11 +29,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 서플라이 체인 보안 (Su - **정책 변화:** AI 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Software Composition Analysis (SCA)]], [[SBOM (Software Bill of Materials)]], [[오픈소스 보안]] -- **Projects/Contexts:** [[CVE-2025-54313 (`eslint-config-prettier` 공격)]], [[`tj-actions/changed-files` 공격]] +- **Related Topics:** [[Software Composition Analysis (SCA)|Software Composition Analysis (SCA)]], SBOM (Software Bill of Materials), 오픈소스 보안 +- **Projects/Contexts:** CVE-2025-54313 (`eslint-config-prettier` 공격), `tj-actions/changed-files` 공격 - **Contradictions/Notes:** 소스에 따르면 오픈소스 생태계는 '신뢰'에 극도로 의존하여 운영되고 있으나, 바로 이러한 신뢰 모델 때문에 한 명의 개발자 계정에 대한 피싱 공격이 거대한 소프트웨어 서플라이 체인 전체를 위험에 빠뜨리는 구조적 취약점이 됨을 경고하고 있습니다 [4]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/서플라이 체인 보안 (Supply Chain Security).md]] +- Raw Source: 00_Raw/2026-04-20/서플라이 체인 보안 (Supply Chain Security).md --- diff --git a/01_Archive/2026-04-20/선언 병합 (Declaration Merging).md b/01_Archive/2026-04-20/선언 병합 (Declaration Merging).md index 24a49fe2..a2689964 100644 --- a/01_Archive/2026-04-20/선언 병합 (Declaration Merging).md +++ b/01_Archive/2026-04-20/선언 병합 (Declaration Merging).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-6C2D93 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 선언 병합 (Declaration Merging)" --- -# [[선언 병합 (Declaration Merging)]] +# [[선언 병합 (Declaration Merging)|선언 병합 (Declaration Merging)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 선언 병합(Declaration Merging)은 TypeScript에서 동일한 이름을 가진 인터페이스를 여러 번 선언할 경우, 컴파일러가 이를 자동으로 합쳐서 하나의 인터페이스로 정의해 주는 고유한 기능입니다 [1, 2]. 이 기능은 타입 별칭(Type Alias)에는 존재하지 않으며, 주로 라이브러리 제작자가 사용자에게 타입 확장 지점을 제공하기 위해 사용됩니다 [2-4]. 그러나 의도치 않은 타입 병합으로 인한 오류 발생 가능성 때문에 프로젝트 성격에 따라 사용을 지양하는 경우도 존재합니다 [5-7]. @@ -20,11 +20,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 선언 병합 (Declaration Mer - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[인터페이스 (Interface)]], [[타입 별칭 (Type Alias)]] -- **Projects/Contexts:** [[TypeScript 라이브러리 타입 확장]], [[철벽 수비대 인터페이스 설계 전략]] +- **Related Topics:** [[인터페이스 (Interface)|인터페이스 (Interface)]], [[타입 별칭 (Type Alias)|타입 별칭 (Type Alias)]] +- **Projects/Contexts:** [[TypeScript 라이브러리 타입 확장|TypeScript 라이브러리 타입 확장]], [[철벽 수비대 인터페이스 설계 전략|철벽 수비대 인터페이스 설계 전략]] - **Contradictions/Notes:** 소스 [2-4]는 라이브러리 작성 시 소비자에게 타입 확장 지점을 제공한다는 측면에서 선언 병합의 강력한 유용성을 주장하지만, 소스 [5-7]은 개발자의 실수로 인한 의도치 않은 병합의 위험성을 지적하며 선언 병합 기능을 피하고 엄격한 에러를 뱉는 타입 별칭(Type Alias)을 사용하는 것이 바람직하다고 반대합니다. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/선언 병합 (Declaration Merging).md]] +- Raw Source: 00_Raw/2026-04-20/선언 병합 (Declaration Merging).md --- diff --git a/01_Archive/2026-04-20/선언 병합(Declaration Merging).md b/01_Archive/2026-04-20/선언 병합(Declaration Merging).md index 715e0a6c..c1397936 100644 --- a/01_Archive/2026-04-20/선언 병합(Declaration Merging).md +++ b/01_Archive/2026-04-20/선언 병합(Declaration Merging).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-18CC73 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 선언 병합(Declaration Merging)" --- -# [[선언 병합(Declaration Merging)]] +# [[선언 병합(Declaration Merging)|선언 병합(Declaration Merging)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 선언 병합(Declaration Merging)은 TypeScript에서 동일한 이름을 가진 여러 개의 인터페이스를 선언할 경우, 컴파일러가 이를 자동으로 하나의 단일 인터페이스로 합치는 고유한 기능입니다 [1]. 주로 라이브러리 제작자가 사용자에게 타입 확장 지점을 제공하거나 패치할 때 유용하게 사용되지만, 일반 애플리케이션 코드에서는 의도치 않은 타입 병합을 막기 위해 사용을 지양하는 경우도 많습니다 [2-4]. @@ -23,11 +23,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 선언 병합(Declaration Merg - **정책 변화:** Design & Experience 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[인터페이스(Interface)]], [[타입 별칭(Type Alias)]] -- **Projects/Contexts:** [[라이브러리 코드 작성]], [[TypeScript 타입 시스템]] +- **Related Topics:** [[인터페이스 (Interface)|인터페이스(Interface)]], [[타입 별칭 (Type Alias)|타입 별칭(Type Alias)]] +- **Projects/Contexts:** 라이브러리 코드 작성, TypeScript 타입 시스템 - **Contradictions/Notes:** 소스에 따르면 라이브러리 제작 관점에서는 소비자에게 확장을 허용하는 매우 유용한 기능으로 평가받지만 [1, 4], 애플리케이션 개발 팀 관점에서는 의도치 않은 병합 버그를 유발할 수 있어 피해야 할 기능으로 강하게 반대되기도 합니다 [2, 8]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/선언 병합(Declaration Merging).md]] +- Raw Source: 00_Raw/2026-04-20/선언 병합(Declaration Merging).md --- diff --git a/01_Archive/2026-04-20/선언 파일(.d.ts).md b/01_Archive/2026-04-20/선언 파일(.d.ts).md index 83613144..2f94685a 100644 --- a/01_Archive/2026-04-20/선언 파일(.d.ts).md +++ b/01_Archive/2026-04-20/선언 파일(.d.ts).md @@ -1,4 +1,4 @@ -# [[선언 파일(.d.ts)]] +# [[선언 파일(.d.ts)|선언 파일(.d.ts)]] ## 📌 Brief Summary 선언 파일(.d.ts)은 타입스크립트(TypeScript) 환경에서 자바스크립트(JavaScript) 라이브러리를 사용할 때 필요한 타입 정의를 제공하는 파일입니다 [1]. 이 파일은 실제 코드가 구현되어 있지 않으며, 순수하게 타입 정보만을 제공하는 데 목적이 있습니다 [1]. 주어진 소스에는 선언 파일의 구체적인 문법이나 심도 있는 활용법 등에 대한 정보가 전반적으로 부족합니다. @@ -12,7 +12,7 @@ - **에러 억제 기능:** 라이브러리에 대한 타입이 전혀 존재하지 않는 특수한 상황에서는, 임의로 모듈을 선언(declare)하여 타입스크립트 컴파일러가 뱉어내는 에러를 억제할 수 있습니다 [2]. ## 🔗 Knowledge Connections -- **Related Topics:** [[JavaScript Libraries]], [[DefinitelyTyped]], [[Type Definitions]] +- **Related Topics:** JavaScript Libraries, [[DefinitelyTyped|DefinitelyTyped]], Type Definitions - **Projects/Contexts:** 타입스크립트 환경에서 순수 자바스크립트로 작성된 외부 라이브러리를 가져와 사용할 때 발생할 수 있는 타입 에러를 방지하고, IDE의 자동 완성 등 타입 안정성을 확보하기 위한 맥락에서 사용됩니다 [1, 2]. - **Contradictions/Notes:** 제공된 여러 소스의 목차(Table of Contents)에서 선언 파일이 간략히 언급되기는 하나[3, 4], 실제 작동 원리나 세부 작성법을 설명한 본문 내용은 소스에 포함되어 있지 않아 정보를 깊이 있게 확장하는 데 한계가 있습니다. diff --git a/01_Archive/2026-04-20/선언 파일(dts).md b/01_Archive/2026-04-20/선언 파일(dts).md index 7e8f35e8..fcee8358 100644 --- a/01_Archive/2026-04-20/선언 파일(dts).md +++ b/01_Archive/2026-04-20/선언 파일(dts).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-239012 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 선언 파일(dts)" --- -# [[선언 파일(dts)]] +# [[선언 파일(dts)|선언 파일(dts)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 선언 파일(.d.ts)은 타입스크립트(TypeScript) 환경에서 자바스크립트(JavaScript) 라이브러리를 사용할 때 필요한 타입 정의를 제공하는 파일입니다 [1]. 이 파일은 실제 코드가 구현되어 있지 않으며, 순수하게 타입 정보만을 제공하는 데 목적이 있습니다 [1]. 주어진 소스에는 선언 파일의 구체적인 문법이나 심도 있는 활용법 등에 대한 정보가 전반적으로 부족합니다. @@ -25,11 +25,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 선언 파일(dts)" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[JavaScript Libraries]], [[DefinitelyTyped]], [[Type Definitions]] +- **Related Topics:** JavaScript Libraries, [[DefinitelyTyped|DefinitelyTyped]], Type Definitions - **Projects/Contexts:** 타입스크립트 환경에서 순수 자바스크립트로 작성된 외부 라이브러리를 가져와 사용할 때 발생할 수 있는 타입 에러를 방지하고, IDE의 자동 완성 등 타입 안정성을 확보하기 위한 맥락에서 사용됩니다 [1, 2]. - **Contradictions/Notes:** 제공된 여러 소스의 목차(Table of Contents)에서 선언 파일이 간략히 언급되기는 하나[3, 4], 실제 작동 원리나 세부 작성법을 설명한 본문 내용은 소스에 포함되어 있지 않아 정보를 깊이 있게 확장하는 데 한계가 있습니다. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/선언 파일(.d.ts).md]] +- Raw Source: 00_Raw/2026-04-20/선언 파일(.d.ts).md --- diff --git a/01_Archive/2026-04-20/설정 객체 및 룩업 테이블 설계(Configuration Objects and Lookup Tables).md b/01_Archive/2026-04-20/설정 객체 및 룩업 테이블 설계(Configuration Objects and Lookup Tables).md index a96924e6..5e36465b 100644 --- a/01_Archive/2026-04-20/설정 객체 및 룩업 테이블 설계(Configuration Objects and Lookup Tables).md +++ b/01_Archive/2026-04-20/설정 객체 및 룩업 테이블 설계(Configuration Objects and Lookup Tables).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-53A6E9 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 설정 객체 및 룩업 테이블 설계(Configuration Objects and Lookup Tables)" --- -# [[설정 객체 및 룩업 테이블 설계(Configuration Objects and Lookup Tables)]] +# [[설정 객체 및 룩업 테이블 설계(Configuration Objects and Lookup Tables)|설정 객체 및 룩업 테이블 설계(Configuration Objects and Lookup Tables)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 설정 객체(Configuration Objects)와 룩업 테이블(Lookup Tables)은 애플리케이션 내에서 변경되지 않아야 하는 고정된 상태 데이터, 매핑 정보 또는 환경 설정을 정의하기 위한 구조입니다. TypeScript에서는 이러한 객체가 런타임에 의도치 않게 수정되는 것을 방지하고 타입의 정밀도를 유지하기 위해 `readonly`, `Record`, `as const`, `satisfies`와 같은 타입 시스템의 기능들을 조합하여 설계합니다. 이를 통해 개발자는 런타임의 불변성(Immutability)과 컴파일 타임의 강력한 타입 유효성 검사를 동시에 확보할 수 있습니다. @@ -32,11 +32,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 설정 객체 및 룩업 테 - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Readonly Type]], [[Satisfies 연산자]], [[as const Assertion]], [[TypeScript Utility Types (Record, Readonly)]] -- **Projects/Contexts:** [[안전한 TypeScript 데이터 모델링 및 설정 관리 구축]] +- **Related Topics:** [[Readonly Type|Readonly Type]], [[satisfies 연산자|Satisfies 연산자]], [[as const Assertion|as const Assertion]], [[TypeScript Utility Types (Record, Readonly)|TypeScript Utility Types (Record, Readonly)]] +- **Projects/Contexts:** [[안전한 TypeScript 데이터 모델링 및 설정 관리 구축|안전한 TypeScript 데이터 모델링 및 설정 관리 구축]] - **Contradictions/Notes:** TypeScript에 내장된 `Readonly` 유틸리티 타입은 객체의 깊은 불변성까지는 강제하지 못하므로, 복잡한 설정 객체의 완벽한 런타임 무결성을 보장하기 위해서는 개발자가 직접 재귀형 `DeepReadonly` 유틸리티 타입을 구현하거나 외부 라이브러리에 의존해야 합니다 [7, 17]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/설정 객체 및 룩업 테이블 설계(Configuration Objects and Lookup Tables).md]] +- Raw Source: 00_Raw/2026-04-20/설정 객체 및 룩업 테이블 설계(Configuration Objects and Lookup Tables).md --- diff --git a/01_Archive/2026-04-20/성장 마인드셋 (Growth Mindset).md b/01_Archive/2026-04-20/성장 마인드셋 (Growth Mindset).md index 794e0855..fc9ad910 100644 --- a/01_Archive/2026-04-20/성장 마인드셋 (Growth Mindset).md +++ b/01_Archive/2026-04-20/성장 마인드셋 (Growth Mindset).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-56F98F -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 성장 마인드셋 (Growth Mindset)" --- -# [[성장 마인드셋 (Growth Mindset)]] +# [[성장 마인드셋 (Growth Mindset)|성장 마인드셋 (Growth Mindset)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - 성장 마인드셋 (Growth Mi ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/성장 마인드셋 (Growth Mindset).md]] +- Raw Source: 00_Raw/2026-04-20/성장 마인드셋 (Growth Mindset).md --- diff --git a/01_Archive/2026-04-20/성장 마인드셋(Growth Mindset).md b/01_Archive/2026-04-20/성장 마인드셋(Growth Mindset).md index b7ce76f9..55a61aaa 100644 --- a/01_Archive/2026-04-20/성장 마인드셋(Growth Mindset).md +++ b/01_Archive/2026-04-20/성장 마인드셋(Growth Mindset).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-A73E81 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 성장 마인드셋(Growth Mindset)" --- -# [[성장 마인드셋(Growth Mindset)]] +# [[성장 마인드셋(Growth Mindset)|성장 마인드셋(Growth Mindset)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - 성장 마인드셋(Growth Min ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/성장 마인드셋(Growth Mindset).md]] +- Raw Source: 00_Raw/2026-04-20/성장 마인드셋(Growth Mindset).md --- diff --git a/01_Archive/2026-04-20/세대 가설(Generational Hypothesis).md b/01_Archive/2026-04-20/세대 가설(Generational Hypothesis).md index 0474d103..69ce4c03 100644 --- a/01_Archive/2026-04-20/세대 가설(Generational Hypothesis).md +++ b/01_Archive/2026-04-20/세대 가설(Generational Hypothesis).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-3D4CF3 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 세대 가설(Generational Hypothesis)" --- -# [[세대 가설(Generational Hypothesis)]] +# [[세대 가설(Generational Hypothesis)|세대 가설(Generational Hypothesis)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 세대 가설(Generational Hypothesis)은 프로그램에서 생성된 대부분의 객체가 생성 직후 곧바로 도달할 수 없는 상태(죽은 상태)가 된다는 경험적 관찰을 의미합니다 [1-3]. 이 가설은 자바스크립트(JavaScript)뿐만 아니라 대부분의 동적 언어에 적용되는 중요한 가비지 컬렉션(Garbage Collection) 개념입니다 [2]. V8 엔진은 이 특성을 적극적으로 활용하여 힙(Heap) 메모리를 '젊은 세대(young generation)'와 '오래된 세대(old generation)'로 분리하고, 이를 통해 메모리 정리 작업을 최적화합니다 [1-4]. @@ -31,11 +31,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 세대 가설(Generational Hyp - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Garbage Collection (GC)]], [[V8 Engine]], [[Young Generation (New Space)]], [[Old Generation (Old Space)]], [[Scavenger (Minor GC)]] -- **Projects/Contexts:** [[V8 Memory Management]], [[Node.js Performance Optimization]] +- **Related Topics:** [[Garbage Collection (GC)|Garbage Collection (GC)]], [[V8 Engine|V8 Engine]], Young Generation (New Space), Old Generation (Old Space), [[Scavenger(Minor GC)|Scavenger (Minor GC)]] +- **Projects/Contexts:** V8 Memory Management, Node.js Performance Optimization - **Contradictions/Notes:** 소스에 관련 정보가 부족합니다. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/세대 가설(Generational Hypothesis).md]] +- Raw Source: 00_Raw/2026-04-20/세대 가설(Generational Hypothesis).md --- diff --git a/01_Archive/2026-04-20/세대별 가설(Generational Hypothesis).md b/01_Archive/2026-04-20/세대별 가설(Generational Hypothesis).md index a37d86e4..ac7802b9 100644 --- a/01_Archive/2026-04-20/세대별 가설(Generational Hypothesis).md +++ b/01_Archive/2026-04-20/세대별 가설(Generational Hypothesis).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-A34D6C -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 세대별 가설(Generational Hypothesis)" --- -# [[세대별 가설(Generational Hypothesis)]] +# [[세대별 가설(Generational Hypothesis)|세대별 가설(Generational Hypothesis)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -25,11 +25,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 세대별 가설(Generational - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[가비지 컬렉션(Garbage Collection)]], [[V8 엔진(V8 Engine)]], [[젊은 세대(Young Generation/New Space)]], [[늙은 세대(Old Generation/Old Space)]], [[스캐빈저(Scavenger/Minor GC)]] -- **Projects/Contexts:** [[V8 자바스크립트 엔진 메모리 관리(V8 JavaScript Engine Memory Management)]], [[오리노코 가비지 컬렉터(Orinoco Garbage Collector)]] +- **Related Topics:** [[가비지 컬렉션(Garbage Collection)|가비지 컬렉션(Garbage Collection)]], [[V8 엔진(V8 Engine)|V8 엔진(V8 Engine)]], 젊은 세대(Young Generation/New Space), 늙은 세대(Old Generation/Old Space), 스캐빈저(Scavenger/Minor GC) +- **Projects/Contexts:** V8 자바스크립트 엔진 메모리 관리(V8 JavaScript Engine Memory Management), 오리노코 가비지 컬렉터(Orinoco Garbage Collector) - **Contradictions/Notes:** 소스에 제공된 정보들 사이에서 모순은 발견되지 않으며, 모든 소스가 공통으로 세대별 가설이 V8의 메모리 공간 분할 및 가비지 컬렉션 효율화의 핵심 이론적 기반이라고 설명하고 있습니다. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/세대별 가설(Generational Hypothesis).md]] +- Raw Source: 00_Raw/2026-04-20/세대별 가설(Generational Hypothesis).md --- diff --git a/01_Archive/2026-04-20/셰이더 정밀도 (Mediump_Highp).md b/01_Archive/2026-04-20/셰이더 정밀도 (Mediump_Highp).md index 72c354cc..5e5567d9 100644 --- a/01_Archive/2026-04-20/셰이더 정밀도 (Mediump_Highp).md +++ b/01_Archive/2026-04-20/셰이더 정밀도 (Mediump_Highp).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-B2C911 -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 셰이더 정밀도 (Mediump_Highp)" --- -# [[셰이더 정밀도 (Mediump_Highp)]] +# [[셰이더 정밀도 (Mediump_Highp)|셰이더 정밀도 (Mediump_Highp)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 셰이더 정밀도(Mediump/Highp)는 3D 그래픽스의 셰이더 연산에서 변수의 데이터 정확도를 결정하는 설정입니다. 모바일 GPU 환경에서 `mediump`(중간 정밀도)는 `highp`(고정밀도)보다 약 2배 빠른 속도로 처리됩니다 [1]. 따라서 깊이 계산이나 위치 연산과 같이 높은 정밀도가 반드시 필요한 경우에만 `highp`를 사용하고, 그 외에는 `mediump`를 사용하는 것이 모바일 성능 최적화의 핵심입니다 [1]. @@ -22,11 +22,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 셰이더 정밀도 (Mediump_H - **정책 변화:** Graphics & Performance 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[셰이더 최적화]], [[깊이 계산 (Depth Calculations)]] -- **Projects/Contexts:** [[Three.js 모바일 성능 최적화]] +- **Related Topics:** 셰이더 최적화, 깊이 계산 (Depth Calculations) +- **Projects/Contexts:** Three.js 모바일 성능 최적화 - **Contradictions/Notes:** 소스에 관련 정보가 제한적이며, 주어진 자료 내에서 셰이더 정밀도에 대한 이견이나 추가적인 구체적 작동 원리에 대한 소스에 관련 정보가 부족합니다 [1]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/셰이더 정밀도 (Mediump_Highp).md]] +- Raw Source: 00_Raw/2026-04-20/셰이더 정밀도 (Mediump_Highp).md --- diff --git a/01_Archive/2026-04-20/소프트웨어 개발 수명 주기 (SDLC).md b/01_Archive/2026-04-20/소프트웨어 개발 수명 주기 (SDLC).md index 00ebed66..bfb07dbc 100644 --- a/01_Archive/2026-04-20/소프트웨어 개발 수명 주기 (SDLC).md +++ b/01_Archive/2026-04-20/소프트웨어 개발 수명 주기 (SDLC).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-C931C8 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 소프트웨어 개발 수명 주기 (SDLC)" --- -# [[소프트웨어 개발 수명 주기 (SDLC)]] +# [[소프트웨어 개발 수명 주기 (SDLC)|소프트웨어 개발 수명 주기 (SDLC)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 소프트웨어 개발 수명 주기(SDLC)는 소프트웨어를 개발하고 유지보수하는 전체 과정을 의미합니다. 현대의 SDLC는 정적 분석(SAST)과 AI 도구를 초기 단계부터 통합하여 취약점을 조기에 발견하고 수정하는 '시프트 레프트(Shift-Left)' 접근법을 강조합니다 [1-3]. 이를 통해 조직은 개발 수명 주기 내내 AI가 생성한 코드를 포함한 모든 소프트웨어의 보안, 유지보수성, 품질을 효율적으로 관리할 수 있습니다 [1, 4, 5]. @@ -23,11 +23,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 소프트웨어 개발 수명 - **정책 변화:** AI 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[시프트 레프트 (Shift-Left)]], [[정적 애플리케이션 보안 테스트 (SAST)]], [[DevSecOps]] -- **Projects/Contexts:** [[AI 코드 리뷰]], [[풀 리퀘스트 워크플로우]] +- **Related Topics:** [[시프트 레프트 (Shift-Left)|시프트 레프트 (Shift-Left)]], [[정적 애플리케이션 보안 테스트 (SAST)|정적 애플리케이션 보안 테스트 (SAST)]], [[DevSecOps|DevSecOps]] +- **Projects/Contexts:** [[AI 코드 리뷰|AI 코드 리뷰]], [[풀 리퀘스트 워크플로우|풀 리퀘스트 워크플로우]] - **Contradictions/Notes:** 소스 간의 명백한 모순은 존재하지 않으며, 모든 소스가 공통적으로 SDLC 전반(특히 초기 단계)에 걸친 보안 스캔 자동화 및 AI 도구 도입의 중요성을 일관되게 강조하고 있습니다. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/소프트웨어 개발 수명 주기 (SDLC).md]] +- Raw Source: 00_Raw/2026-04-20/소프트웨어 개발 수명 주기 (SDLC).md --- diff --git a/01_Archive/2026-04-20/소프트웨어 구성 분석(SCA).md b/01_Archive/2026-04-20/소프트웨어 구성 분석(SCA).md index 997f6b25..647c123a 100644 --- a/01_Archive/2026-04-20/소프트웨어 구성 분석(SCA).md +++ b/01_Archive/2026-04-20/소프트웨어 구성 분석(SCA).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-C55C87 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 소프트웨어 구성 분석(SCA)" --- -# [[소프트웨어 구성 분석(SCA)]] +# [[소프트웨어 구성 분석(SCA)|소프트웨어 구성 분석(SCA)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 소프트웨어 구성 분석(SCA, Software Composition Analysis)은 애플리케이션에 포함된 오픈소스 및 서드파티 코드 종속성을 분석하는 보안 테스트 방법론입니다 [1, 2]. 이 기술은 컴포넌트 취약점 데이터베이스(CVE 등)에 이미 보고된 알려진 취약점, 라이선스 규정 준수 위험, 버전 기록 등을 식별하는 데 중점을 둡니다 [1, 2]. 오픈소스 라이브러리를 많이 사용하는 최신 개발 환경에서 소프트웨어 공급망 위험을 관리하고 외부 코드를 안전하게 보호하는 데 필수적인 역할을 수행합니다 [2, 3]. @@ -23,11 +23,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 소프트웨어 구성 분석( - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[SAST(정적 애플리케이션 보안 테스트)]], [[소프트웨어 공급망 보안]], [[오픈소스 의존성]], [[CVE(공통 취약점 및 노출)]] -- **Projects/Contexts:** [[Snyk Open Source]], [[Endor Labs]] +- **Related Topics:** [[SAST (정적 애플리케이션 보안 테스트)|SAST(정적 애플리케이션 보안 테스트)]], 소프트웨어 공급망 보안, 오픈소스 의존성, CVE(공통 취약점 및 노출) +- **Projects/Contexts:** [[Snyk Open Source|Snyk Open Source]], Endor Labs - **Contradictions/Notes:** 소스 간의 모순된 주장은 발견되지 않았으나, 애플리케이션 전체의 보안 강화를 위해서는 SCA 단독 활용보다는 SAST와 결합하여 사용해야 가장 이상적이고 완전한 테스트가 이루어진다는 점이 전반적으로 강조됩니다 [3]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/소프트웨어 구성 분석(SCA).md]] +- Raw Source: 00_Raw/2026-04-20/소프트웨어 구성 분석(SCA).md --- diff --git a/01_Archive/2026-04-20/소프트웨어 시스템 설계 및 아키텍처 구축.md b/01_Archive/2026-04-20/소프트웨어 시스템 설계 및 아키텍처 구축.md index b80f4d52..92a2737a 100644 --- a/01_Archive/2026-04-20/소프트웨어 시스템 설계 및 아키텍처 구축.md +++ b/01_Archive/2026-04-20/소프트웨어 시스템 설계 및 아키텍처 구축.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-6B386C -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 소프트웨어 시스템 설계 및 아키텍처 구축" --- -# [[소프트웨어 시스템 설계 및 아키텍처 구축]] +# [[소프트웨어 시스템 설계 및 아키텍처 구축|소프트웨어 시스템 설계 및 아키텍처 구축]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 소프트웨어 시스템 설계 및 아키텍처 구축은 변화하는 비즈니스 요구에 적응하고 시스템의 복잡성을 제어하기 위해 확장 가능하고 유지보수가 용이한 애플리케이션의 뼈대를 설계하는 과정입니다 [1, 2]. 이 과정은 시스템을 관리 가능한 독립적 모듈로 분할하는 '관심사의 분리(SoC)'를 핵심 원리로 삼으며, 고수준의 비즈니스 규칙과 저수준의 인프라(UI, DB 등)를 격리하는 것을 목표로 합니다 [3, 4]. 이를 통해 개발 조직은 코드의 재사용성을 높이고, 독립적인 테스트와 배포를 가능하게 하여 소프트웨어의 생명주기를 효과적으로 지원할 수 있습니다 [5, 6]. @@ -32,11 +32,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 소프트웨어 시스템 설 - **정책 변화:** Design & Experience 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Separation of Concerns (SoC)]], [[Clean Architecture]], [[Microservices Architecture]], [[SOLID Principles]] -- **Projects/Contexts:** [[Netflix Microservices & Cosmos Platform]], [[Feature-Sliced Design (FSD)]] +- **Related Topics:** [[관심사의 분리 (Separation of Concerns SoC)|Separation of Concerns (SoC)]], [[Clean Architecture|Clean Architecture]], [[마이크로서비스 아키텍처 (Microservices Architecture)|Microservices Architecture]], [[SOLID Principles|SOLID Principles]] +- **Projects/Contexts:** Netflix Microservices & Cosmos Platform, [[Feature-Sliced Design (FSD)|Feature-Sliced Design (FSD)]] - **Contradictions/Notes:** 마이크로서비스 아키텍처는 유연성과 독립적 배포를 제공하지만 분산 시스템 간의 통신, 배포의 복잡성, 메모리 오버헤드를 유발하므로 무조건적인 도입은 지양해야 합니다 [38, 39]. 또한 완벽한 관심사 분리를 위한 과도한 추상화(Over-engineering)나 너무 이른 계층 분리는 오히려 시스템을 복잡하게 만들어 가독성을 해치고 인지적 부하를 유발할 수 있으므로, 응집도와 결합도를 실무적 상황에 맞게 조율해야 합니다 [40-42]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/소프트웨어 시스템 설계 및 아키텍처 구축.md]] +- Raw Source: 00_Raw/2026-04-20/소프트웨어 시스템 설계 및 아키텍처 구축.md --- diff --git a/01_Archive/2026-04-20/소프트웨어 아키텍처 베스트 프랙티스.md b/01_Archive/2026-04-20/소프트웨어 아키텍처 베스트 프랙티스.md index cd744cbd..108978ff 100644 --- a/01_Archive/2026-04-20/소프트웨어 아키텍처 베스트 프랙티스.md +++ b/01_Archive/2026-04-20/소프트웨어 아키텍처 베스트 프랙티스.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-FDDA7F -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 소프트웨어 아키텍처 베스트 프랙티스" --- -# [[소프트웨어 아키텍처 베스트 프랙티스]] +# [[소프트웨어 아키텍처 베스트 프랙티스|소프트웨어 아키텍처 베스트 프랙티스]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 소프트웨어 아키텍처 베스트 프랙티스는 회복성, 확장성, 그리고 유지보수성이 뛰어난 시스템을 구축하기 위한 핵심 원칙과 설계 청사진입니다 [1]. 이는 단순한 이론적 지침을 넘어, 기능의 추가 및 수정을 용이하게 하고 기술 부채를 최소화하여 애플리케이션의 장기적인 비즈니스 가치를 보존하는 근본적인 철학입니다 [1, 2]. 관심사의 분리(SoC), 클린 아키텍처, 도메인 주도 설계(DDD) 등의 원칙을 통해 시스템의 결합도를 낮추고 응집도를 높여 복잡성을 통제하는 것을 궁극적인 목표로 합니다 [3-5]. @@ -33,11 +33,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 소프트웨어 아키텍처 - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[관심사의 분리(SoC)]], [[클린 아키텍처]], [[마이크로서비스 아키텍처]], [[도메인 주도 설계(DDD)]], [[SOLID 원칙]] -- **Projects/Contexts:** [[넷플릭스(Netflix)의 코스모스 플랫폼 및 마이크로서비스 전환]], [[스포티파이(Spotify)의 마이크로 프론트엔드 및 스쿼드 모델]] +- **Related Topics:** [[관심사의 분리(SoC)|관심사의 분리(SoC)]], [[클린 아키텍처|클린 아키텍처]], [[마이크로서비스 아키텍처|마이크로서비스 아키텍처]], [[도메인 주도 설계(DDD)|도메인 주도 설계(DDD)]], [[SOLID 원칙|SOLID 원칙]] +- **Projects/Contexts:** 넷플릭스(Netflix)의 코스모스 플랫폼 및 마이크로서비스 전환, 스포티파이(Spotify)의 마이크로 프론트엔드 및 스쿼드 모델 - **Contradictions/Notes:** 소스에 따르면 완벽한 형태의 아키텍처 경계(예: 완벽한 관심사 분리와 다형성 인터페이스의 전면적 도입)는 유지보수성과 독립성을 극대화하지만, 초기 구현 비용과 성능 오버헤드, 인지적 부하(Over-engineering)를 초래할 수 있습니다. 따라서 아키텍트는 YAGNI(You Aren't Gonna Need It) 철학을 기반으로 "Rule of Three(세 번 이상 중복 시 추상화)" 등을 활용해 부분적 경계만을 도입하는 등 실무적인 타협을 지속적으로 판단해야 한다고 지적합니다 [29-32]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/소프트웨어 아키텍처 베스트 프랙티스.md]] +- Raw Source: 00_Raw/2026-04-20/소프트웨어 아키텍처 베스트 프랙티스.md --- diff --git a/01_Archive/2026-04-20/소프트웨어 아키텍처 설계.md b/01_Archive/2026-04-20/소프트웨어 아키텍처 설계.md index c94563c5..95a62748 100644 --- a/01_Archive/2026-04-20/소프트웨어 아키텍처 설계.md +++ b/01_Archive/2026-04-20/소프트웨어 아키텍처 설계.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-6B7DB7 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 소프트웨어 아키텍처 설계" --- -# [[소프트웨어 아키텍처 설계]] +# [[소프트웨어 아키텍처 설계|소프트웨어 아키텍처 설계]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 소프트웨어 아키텍처 설계는 소프트웨어 시스템이 쉽게 개발, 배포, 운영 및 유지보수될 수 있도록 시스템의 형태와 컴포넌트 간의 관계를 구성하는 작업입니다 [1, 2]. 좋은 아키텍처는 시스템의 복잡성을 관리하여 기술 부채를 최소화하며, 핵심 비즈니스 규칙과 유스케이스를 중심에 두어 외부 프레임워크나 도구에 대한 결정을 지연시킬 수 있도록 돕습니다 [3, 4]. 이를 위해 관심사의 분리(SoC) 및 SOLID 원칙 등 다양한 설계 철학이 적용되어 시스템의 유연성과 확장성을 보장합니다 [5-7]. @@ -31,11 +31,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 소프트웨어 아키텍처 - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[관심사의 분리(SoC)]], [[클린 아키텍처]], [[마이크로서비스 아키텍처]], [[도메인 주도 설계(DDD)]], [[SOLID 원칙]] -- **Projects/Contexts:** [[Netflix 마이크로서비스 전환]], [[스포티파이 자율적 분대 모델]], [[FSD (Feature-Sliced Design)]] +- **Related Topics:** [[관심사의 분리(SoC)|관심사의 분리(SoC)]], [[클린 아키텍처|클린 아키텍처]], [[마이크로서비스 아키텍처|마이크로서비스 아키텍처]], [[도메인 주도 설계(DDD)|도메인 주도 설계(DDD)]], [[SOLID 원칙|SOLID 원칙]] +- **Projects/Contexts:** [[Netflix 마이크로서비스 전환|Netflix 마이크로서비스 전환]], [[스포티파이 자율적 분대 모델|스포티파이 자율적 분대 모델]], [[FSD (Feature-Sliced Design)|FSD (Feature-Sliced Design)]] - **Contradictions/Notes:** 관심사의 분리 원칙은 코드 유지보수성과 확장성을 크게 높이지만, 과도한 분리나 추상화(오버엔지니어링)는 잦은 계층 간 데이터 변환과 네트워크 통신 증가를 유발하여 성능 오버헤드와 디버깅의 어려움을 초래할 수 있으므로 적절한 임계점을 찾는 것이 중요합니다 [31-33]. 또한 최근 도입되는 인공지능(AI) 시스템의 아키텍처에서는 모델의 결과가 확률적이라는 특성상, 전통적인 결정론적 단위 테스트(TDD) 방식 대신 허용 오차 범위 내의 통계적 속성을 검증하는 AI 특화 TDD 접근 방식이 요구됩니다 [34, 35]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/소프트웨어 아키텍처 설계.md]] +- Raw Source: 00_Raw/2026-04-20/소프트웨어 아키텍처 설계.md --- diff --git a/01_Archive/2026-04-20/수동 코드 리뷰 (Manual Code Review).md b/01_Archive/2026-04-20/수동 코드 리뷰 (Manual Code Review).md index 7b77cf60..80ba1069 100644 --- a/01_Archive/2026-04-20/수동 코드 리뷰 (Manual Code Review).md +++ b/01_Archive/2026-04-20/수동 코드 리뷰 (Manual Code Review).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-30780C -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 수동 코드 리뷰 (Manual Code Review)" --- -# [[수동 코드 리뷰 (Manual Code Review)]] +# [[수동 코드 리뷰 (Manual Code Review)|수동 코드 리뷰 (Manual Code Review)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 수동 코드 리뷰(Manual Code Review)는 한 명 이상의 개발자가 코드 변경 사항을 줄 단위로 직접 읽고 논의하여 논리적 오류, 아키텍처 결함, 명명 규칙 위반 등을 식별하는 인간 주도의 검토 프로세스입니다 [1, 2]. 이 방식은 자동화 도구가 파악하기 힘든 비즈니스 로직의 의도, 설계 패턴의 적합성, 프로젝트의 문맥을 깊이 이해하는 데 탁월한 장점을 제공합니다 [3, 4]. 또한, 동료 간의 피드백을 통해 코드 가독성을 높이고 시니어 개발자가 주니어 개발자를 멘토링하는 강력한 지식 공유의 수단으로 활용됩니다 [5-7]. 하지만 검토에 많은 시간과 숙련된 개발자의 인건비가 소모되며, 피로도나 편향으로 인한 인간의 실수 및 일관성 부족에 취약하다는 한계가 있습니다 [8, 9]. @@ -45,11 +45,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 수동 코드 리뷰 (Manual C - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[자동화된 코드 리뷰 (Automated Code Review)]], [[정적 애플리케이션 보안 테스트 (SAST)]], [[하이브리드 코드 리뷰 (Hybrid Code Review)]], [[코드 품질 (Code Quality)]] -- **Projects/Contexts:** [[GitHub/GitLab Pull Request]], [[CI/CD 파이프라인]], [[소프트웨어 개발 수명 주기 (SDLC)]] +- **Related Topics:** 자동화된 코드 리뷰 (Automated Code Review), [[정적 애플리케이션 보안 테스트 (SAST)|정적 애플리케이션 보안 테스트 (SAST)]], [[하이브리드 코드 리뷰 (Hybrid Code Review)|하이브리드 코드 리뷰 (Hybrid Code Review)]], 코드 품질 (Code Quality) +- **Projects/Contexts:** GitHub/GitLab Pull Request, [[CI_CD 파이프라인|CI/CD 파이프라인]], [[소프트웨어 개발 수명 주기 (SDLC)|소프트웨어 개발 수명 주기 (SDLC)]] - **Contradictions/Notes:** 수동 리뷰가 코드의 모든 문제를 잡아낼 수 있다는 것은 잘못된 속설(Myth)입니다. 인간은 시간적 압박과 피로도에 의해 단순한 실수를 놓칠 수 있기 때문에 대규모 코드베이스에서 수동 리뷰에만 의존하는 것은 비실용적입니다 [16]. 마찬가지로 자동화 도구 역시 완벽하지 않아 복잡한 비즈니스 로직 결함이나 새로운 형태의 공격을 놓치는 컨텍스트 사각지대(Context Blindness)를 가지므로, 두 방식을 상호 보완적으로 사용해야 합니다 [16, 27]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/수동 코드 리뷰 (Manual Code Review).md]] +- Raw Source: 00_Raw/2026-04-20/수동 코드 리뷰 (Manual Code Review).md --- diff --git a/01_Archive/2026-04-20/수동 코드 리뷰.md b/01_Archive/2026-04-20/수동 코드 리뷰.md index 758c6b85..e1502f46 100644 --- a/01_Archive/2026-04-20/수동 코드 리뷰.md +++ b/01_Archive/2026-04-20/수동 코드 리뷰.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-AA36FB -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 수동 코드 리뷰" --- -# [[수동 코드 리뷰]] +# [[수동 코드 리뷰|수동 코드 리뷰]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 수동 코드 리뷰는 개발자가 직접 코드 변경 사항을 한 줄씩 검토하여 논리적 오류, 아키텍처 문제, 설계상의 결함 등을 찾아내는 사람 주도의 프로세스입니다 [1, 2]. 자동화 도구가 파악하기 힘든 비즈니스 로직의 의도, 아키텍처의 트레이드오프를 평가하고 팀원 간의 지식을 공유하는 데 탁월한 효과를 발휘합니다 [3-5]. 하지만 많은 시간과 숙련된 개발자의 인건비가 소모되며, 리뷰어의 피로도에 따라 일관성이 떨어질 수 있다는 한계도 지닙니다 [6, 7]. 따라서 최신 개발 환경에서는 단순 검사는 자동화 도구에 맡기고, 수동 리뷰는 복잡한 로직과 보안 컨텍스트 등 고위험 영역에 집중하는 하이브리드 방식이 권장됩니다 [3, 8]. @@ -33,11 +33,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 수동 코드 리뷰" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[자동화된 코드 리뷰]], [[정적 애플리케이션 보안 테스트]] -- **Projects/Contexts:** [[풀 리퀘스트(Pull Request) 워크플로우]], [[하이브리드 코드 리뷰 프로세스]] +- **Related Topics:** [[자동화된 코드 리뷰|자동화된 코드 리뷰]], 정적 애플리케이션 보안 테스트 +- **Projects/Contexts:** 풀 리퀘스트(Pull Request) 워크플로우, 하이브리드 코드 리뷰 프로세스 - **Contradictions/Notes:** 소스 문헌들은 수동 리뷰가 자동화 도구의 맹점(비즈니스 로직 파악 불가, 신규 패턴 탐지 한계 등)을 메우기 위해 필수적이지만 [3, 23], 반대로 자동화 도구 없이는 검토 속도와 일관성의 한계로 인해 대규모 코드베이스를 감당하기 어려우므로 두 가지 방식이 상호 보완적으로 작동해야 한다고 공통적으로 강조합니다 [9, 20, 24]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/수동 코드 리뷰.md]] +- Raw Source: 00_Raw/2026-04-20/수동 코드 리뷰.md --- diff --git a/01_Archive/2026-04-20/수렴-조절 불일치(Vergence-Accommodation Conflict).md b/01_Archive/2026-04-20/수렴-조절 불일치(Vergence-Accommodation Conflict).md index cf105d8d..416ab17c 100644 --- a/01_Archive/2026-04-20/수렴-조절 불일치(Vergence-Accommodation Conflict).md +++ b/01_Archive/2026-04-20/수렴-조절 불일치(Vergence-Accommodation Conflict).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-B697B6 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 수렴-조절 불일치(Vergence-Accommodation Conflict)" --- -# [[수렴-조절 불일치(Vergence-Accommodation Conflict)]] +# [[수렴-조절 불일치(Vergence-Accommodation Conflict)|수렴-조절 불일치(Vergence-Accommodation Conflict)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 수렴-조절 불일치(Vergence-Accommodation Conflict)는 헤드마운트 디스플레이(HMD)와 같은 가상현실(VR) 환경에서 자연스러운 안구 운동인 '수렴'과 '조절' 기능이 서로 분리(decoupled)될 때 발생하는 시각적 불일치 현상입니다 [1]. 자연적인 시각 조건에서는 이 두 기능이 피드백 루프를 통해 함께 작동하지만, HMD 환경에서는 이러한 상호 연동이 깨지게 됩니다 [1]. 이로 인해 깊이 지각에 대한 망막 단서에 불확실성이 발생하며, 가상현실 멀미(VR Sickness)를 비롯해 피로, 두통 등의 다양한 안구 운동 관련 증상을 유발할 수 있습니다 [1, 2]. @@ -23,11 +23,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 수렴-조절 불일치(Vergen - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[가상현실 멀미(VR Sickness)]], [[안구 운동(Oculomotor Functions)]], [[깊이 지각(Depth Perception)]], [[헤드마운트 디스플레이(HMD)]] -- **Projects/Contexts:** [[가상현실(VR) 시뮬레이션 및 엑서게임(Exergaming) 사용 환경]] +- **Related Topics:** [[가상현실 멀미(VR Sickness)|가상현실 멀미(VR Sickness)]], 안구 운동(Oculomotor Functions), [[깊이 지각 (Depth Perception)|깊이 지각(Depth Perception)]], [[헤드 마운트 디스플레이(HMD)|헤드마운트 디스플레이(HMD)]] +- **Projects/Contexts:** 가상현실(VR) 시뮬레이션 및 엑서게임(Exergaming) 사용 환경 - **Contradictions/Notes:** 소스에 따르면 수렴-조절 불일치가 가상현실 멀미를 유발하는 직접적 원인인지, 혹은 멀미 증상을 가중시키는 요인인지에 대한 명확한 인과관계는 아직 불분명한 것으로 나타납니다 [2]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/수렴-조절 불일치(Vergence-Accommodation Conflict).md]] +- Raw Source: 00_Raw/2026-04-20/수렴-조절 불일치(Vergence-Accommodation Conflict).md --- diff --git a/01_Archive/2026-04-20/순차적 게이트 아키텍처.md b/01_Archive/2026-04-20/순차적 게이트 아키텍처.md index 1a842a82..1021cb96 100644 --- a/01_Archive/2026-04-20/순차적 게이트 아키텍처.md +++ b/01_Archive/2026-04-20/순차적 게이트 아키텍처.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-048BB2 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 순차적 게이트 아키텍처" --- -# [[순차적 게이트 아키텍처]] +# [[순차적 게이트 아키텍처|순차적 게이트 아키텍처]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 소스에 관련 정보가 부족합니다. @@ -26,5 +26,5 @@ github_commit: "[P-Reinforce] Continuous Worker - 순차적 게이트 아키텍 --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/순차적 게이트 아키텍처.md]] +- Raw Source: 00_Raw/2026-04-20/순차적 게이트 아키텍처.md --- diff --git a/01_Archive/2026-04-20/스캐빈저(Scavenger) _ 마이너 GC.md b/01_Archive/2026-04-20/스캐빈저(Scavenger) _ 마이너 GC.md index 901bca29..b9da3588 100644 --- a/01_Archive/2026-04-20/스캐빈저(Scavenger) _ 마이너 GC.md +++ b/01_Archive/2026-04-20/스캐빈저(Scavenger) _ 마이너 GC.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-8AD1F6 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 스캐빈저(Scavenger) _ 마이너 GC" --- -# [[스캐빈저(Scavenger) _ 마이너 GC]] +# [[스캐빈저(Scavenger) _ 마이너 GC|스캐빈저(Scavenger) _ 마이너 GC]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 스캐빈저(Scavenger) 또는 마이너 GC(Minor GC)는 V8 엔진 및 IBM JVM 등에서 새롭게 생성된 객체들이 할당되는 '젊은 세대(Young Generation, New-space, Nursery)' 영역을 대상으로 빠르고 빈번하게 수행되는 가비지 컬렉션 주기입니다 [1-3]. 대부분의 객체가 금방 소멸한다는 '세대 가설(Generational Hypothesis)'에 기반하여 작동하며, 살아남은 객체만을 새로운 공간으로 복사하고 나머지는 폐기하여 메모리를 효율적으로 관리하고 단편화를 방지합니다 [1, 4, 5]. @@ -24,11 +24,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 스캐빈저(Scavenger) _ 마 - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[세대 가설(Generational Hypothesis)]], [[메이저 GC(Major GC) / Mark-Compact]], [[쓰기 장벽(Write Barriers)]], [[뉴 스페이스(New Space) / 젊은 세대]], [[올드 스페이스(Old Space)]] -- **Projects/Contexts:** [[V8 엔진(V8 Engine)]], [[Orinoco 프로젝트]], [[IBM OpenJ9 (gencon 정책)]] +- **Related Topics:** [[세대 가설(Generational Hypothesis)|세대 가설(Generational Hypothesis)]], 메이저 GC(Major GC) / Mark-Compact, 쓰기 장벽(Write Barriers), 뉴 스페이스(New Space) / 젊은 세대, 올드 스페이스(Old Space) +- **Projects/Contexts:** [[V8 엔진(V8 Engine)|V8 엔진(V8 Engine)]], [[Orinoco 프로젝트|Orinoco 프로젝트]], IBM OpenJ9 (gencon 정책) - **Contradictions/Notes:** 소스 전반에 걸쳐 V8 엔진과 IBM JVM의 세부 구현 용어(예: New-space와 Nursery)에는 차이가 있으나, 새롭게 할당된 객체 영역을 정기적으로 비우고 살아남은 객체를 다른 영역이나 구세대로 이동시킨다는 스캐빈저의 기본 동작 원리와 목적은 동일합니다 [2, 3, 6]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/스캐빈저(Scavenger) _ 마이너 GC.md]] +- Raw Source: 00_Raw/2026-04-20/스캐빈저(Scavenger) _ 마이너 GC.md --- diff --git a/01_Archive/2026-04-20/스캐빈저(Scavenger).md b/01_Archive/2026-04-20/스캐빈저(Scavenger).md index 528b00bb..17e3f4d6 100644 --- a/01_Archive/2026-04-20/스캐빈저(Scavenger).md +++ b/01_Archive/2026-04-20/스캐빈저(Scavenger).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-07787D -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 스캐빈저(Scavenger)" --- -# [[스캐빈저(Scavenger)]] +# [[스캐빈저(Scavenger)|스캐빈저(Scavenger)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 스캐빈저(Scavenger)는 V8 및 기타 가상 머신에서 새롭게 생성된 수명이 짧은 객체들이 모여 있는 '새로운 공간(New Space 또는 Nursery)'의 메모리를 회수하기 위해 작동하는 마이너 가비지 컬렉션(Minor GC) 메커니즘입니다 [1-3]. 새로운 객체를 위한 공간을 할당하다가 한계에 도달하여 '할당 실패(Allocation failure)'가 발생했을 때 빠르게 실행됩니다 [3, 4]. 살아남은 객체만을 다른 메모리 영역으로 복사하여 단편화를 없애며, 이 과정을 반복하여 오래 살아남은 객체를 기존 세대(Old Generation)로 승격(Promotion)시킵니다 [5, 6]. @@ -20,11 +20,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 스캐빈저(Scavenger)" - **정책 변화:** AI 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[마이너 가비지 컬렉션(Minor GC)]], [[New Space(Young Generation)]], [[할당 실패(Allocation Failure)]], [[Old Space(Old Generation)]], [[메모리 단편화(Fragmentation)]] -- **Projects/Contexts:** [[V8 엔진 힙 아키텍처]], [[Orinoco 가비지 컬렉터]], [[브라우저 및 Node.js 메모리 튜닝]] +- **Related Topics:** [[마이너 가비지 컬렉션(Minor GC)|마이너 가비지 컬렉션(Minor GC)]], [[New Space(Young Generation)|New Space(Young Generation)]], [[할당 실패(Allocation Failure)|할당 실패(Allocation Failure)]], [[Old Space(Old Generation)|Old Space(Old Generation)]], [[메모리 단편화(Fragmentation)|메모리 단편화(Fragmentation)]] +- **Projects/Contexts:** [[V8 엔진 힙 아키텍처|V8 엔진 힙 아키텍처]], [[Orinoco 가비지 컬렉터|Orinoco 가비지 컬렉터]], [[브라우저 및 Node.js 메모리 튜닝|브라우저 및 Node.js 메모리 튜닝]] - **Contradictions/Notes:** 스캐빈저 알고리즘은 빠른 메모리 할당 및 단편화 제거에 매우 효율적이지만, `To-Space`와 `From-Space` 두 영역의 물리적 메모리를 모두 확보해야 하므로 공간 오버헤드가 크다는 단점이 있습니다 [9, 22]. 따라서 몇 메가바이트 이상의 큰 용량을 관리하는 데에는 비실용적이며, 이를 극복하기 위해 크기가 큰 Old Space에서는 Mark-Sweep 및 Mark-Compact 알고리즘을 혼용합니다 [22, 23]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/스캐빈저(Scavenger).md]] +- Raw Source: 00_Raw/2026-04-20/스캐빈저(Scavenger).md --- diff --git a/01_Archive/2026-04-20/스택 트레이스(Stack trace).md b/01_Archive/2026-04-20/스택 트레이스(Stack trace).md index 6bbb844d..6ab5dd07 100644 --- a/01_Archive/2026-04-20/스택 트레이스(Stack trace).md +++ b/01_Archive/2026-04-20/스택 트레이스(Stack trace).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-8FAFC5 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 스택 트레이스(Stack trace)" --- -# [[스택 트레이스(Stack trace)]] +# [[스택 트레이스(Stack trace)|스택 트레이스(Stack trace)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 스택 트레이스(Stack trace) 자체에 대한 기술적이고 포괄적인 정의는 소스에 관련 정보가 부족합니다. 제공된 소스에 따르면, 스택 트레이스는 코드 내에서 특정 객체가 할당되거나 생성된 정확한 위치를 보여주는 기록을 의미합니다 [1, 2]. 주로 브라우저의 개발자 도구나 IDE의 프로파일링 과정에서 메모리 누수(Memory leak) 원인을 찾거나 예외(Exception)를 분석하는 목적으로 활용됩니다 [3, 4]. @@ -23,11 +23,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 스택 트레이스(Stack trac - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Memory Leak]], [[Allocation Timeline]], [[V8 JavaScript Engine]] -- **Projects/Contexts:** [[Chrome DevTools]], [[IntelliJ IDEA V8 CPU Profiling]] +- **Related Topics:** [[Memory Leak|Memory Leak]], [[Allocation Timeline|Allocation Timeline]], [[V8 JavaScript Engine|V8 JavaScript Engine]] +- **Projects/Contexts:** [[Chrome DevTools|Chrome DevTools]], IntelliJ IDEA V8 CPU Profiling - **Contradictions/Notes:** 제공된 소스는 스택 트레이스를 주로 메모리 누수 및 성능 프로파일링을 위한 '도구적 관점'에서만 다루고 있으며, 스택 트레이스의 근본적인 동작 원리에 대해서는 소스에 관련 정보가 부족합니다. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/스택 트레이스(Stack trace).md]] +- Raw Source: 00_Raw/2026-04-20/스택 트레이스(Stack trace).md --- diff --git a/01_Archive/2026-04-20/스토리지 텍스처(Storage Textures).md b/01_Archive/2026-04-20/스토리지 텍스처(Storage Textures).md index a33dcbc6..08a84ceb 100644 --- a/01_Archive/2026-04-20/스토리지 텍스처(Storage Textures).md +++ b/01_Archive/2026-04-20/스토리지 텍스처(Storage Textures).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-F28DA7 -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 스토리지 텍스처(Storage Textures)" --- -# [[스토리지 텍스처(Storage Textures)]] +# [[스토리지 텍스처(Storage Textures)|스토리지 텍스처(Storage Textures)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 스토리지 텍스처(Storage Textures)는 일반적인 텍스처와 달리 컴퓨트 셰이더(Compute Shaders) 내에서 데이터의 읽기와 쓰기 작업이 모두 가능한 특수한 텍스처입니다 [1]. 복잡한 그래픽 처리 및 시뮬레이션을 GPU 상에서 직접 수행하기 위한 핵심적인 역할을 담당합니다 [1, 2]. @@ -21,11 +21,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 스토리지 텍스처(Storage - **정책 변화:** Graphics & Performance 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[컴퓨트 셰이더(Compute Shaders)]], [[웹GPU(WebGPU)]] -- **Projects/Contexts:** [[유체 시뮬레이션(Fluid simulation)]], [[이미지 처리(Image processing)]], [[GPU 기반 렌더링(GPU-driven rendering)]] +- **Related Topics:** [[컴퓨트 셰이더(Compute Shaders)|컴퓨트 셰이더(Compute Shaders)]], 웹GPU(WebGPU) +- **Projects/Contexts:** 유체 시뮬레이션(Fluid simulation), 이미지 처리(Image processing), GPU 기반 렌더링(GPU-driven rendering) - **Contradictions/Notes:** 소스에서는 스토리지 텍스처의 특징을 설명하기 위해 일반 텍스처(regular textures)와 대조하고 있으며, 일반 텍스처는 컴퓨트 셰이더에서 읽고 쓰기를 동시에 할 수 없다는 점을 강조합니다 [1]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/스토리지 텍스처(Storage Textures).md]] +- Raw Source: 00_Raw/2026-04-20/스토리지 텍스처(Storage Textures).md --- diff --git a/01_Archive/2026-04-20/스트랭글러 피그 패턴(Strangler Fig Pattern).md b/01_Archive/2026-04-20/스트랭글러 피그 패턴(Strangler Fig Pattern).md index ec532032..7640362a 100644 --- a/01_Archive/2026-04-20/스트랭글러 피그 패턴(Strangler Fig Pattern).md +++ b/01_Archive/2026-04-20/스트랭글러 피그 패턴(Strangler Fig Pattern).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-739808 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 스트랭글러 피그 패턴(Strangler Fig Pattern)" --- -# [[스트랭글러 피그 패턴(Strangler Fig Pattern)]] +# [[스트랭글러 피그 패턴(Strangler Fig Pattern)|스트랭글러 피그 패턴(Strangler Fig Pattern)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 스트랭글러 피그 패턴(Strangler Fig Pattern)은 크고 복잡한 레거시 시스템을 새로운 시스템으로 마이그레이션할 때 수반되는 위험을 줄이기 위해 도입하는 아키텍처 패턴입니다 [1]. 이 패턴은 새로운 시스템이 기존의 오래된 시스템을 둘러싸며 점진적으로 자라나도록(grow around) 유도하는 방식을 취합니다 [1]. 최종적으로는 새롭게 구축된 시스템이 구형 시스템을 완전히 대체하게 됩니다 [1]. @@ -24,11 +24,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 스트랭글러 피그 패턴( - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[마이크로서비스(Microservices)]], [[레거시 시스템 마이그레이션]] -- **Projects/Contexts:** [[넷플릭스 Cosmos 플랫폼(Netflix Cosmos Platform)]], [[Reloaded 시스템]] +- **Related Topics:** 마이크로서비스(Microservices), 레거시 시스템 마이그레이션 +- **Projects/Contexts:** 넷플릭스 Cosmos 플랫폼(Netflix Cosmos Platform), Reloaded 시스템 - **Contradictions/Notes:** 소스 내에서 스트랭글러 피그 패턴에 대한 상반된 주장이나 모순점은 발견되지 않습니다. 다만 개념의 기본 정의와 넷플릭스의 도입 사례만 간략히 언급되어 있으며, 그 외의 상세한 설계 방법론에 대해서는 소스에 관련 정보가 부족합니다. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/스트랭글러 피그 패턴(Strangler Fig Pattern).md]] +- Raw Source: 00_Raw/2026-04-20/스트랭글러 피그 패턴(Strangler Fig Pattern).md --- diff --git a/01_Archive/2026-04-20/스파게티 코드 (Spaghetti Code).md b/01_Archive/2026-04-20/스파게티 코드 (Spaghetti Code).md index 4ba48ef8..a91e0b87 100644 --- a/01_Archive/2026-04-20/스파게티 코드 (Spaghetti Code).md +++ b/01_Archive/2026-04-20/스파게티 코드 (Spaghetti Code).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-9FBF28 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 스파게티 코드 (Spaghetti Code)" --- -# [[스파게티 코드 (Spaghetti Code)]] +# [[스파게티 코드 (Spaghetti Code)|스파게티 코드 (Spaghetti Code)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 스파게티 코드는 알고리즘의 논리를 작성하거나 파악할 때 여러 기능이나 모듈 사이를 빈번하게 뛰어다녀야 하는 복잡하게 얽힌 상태의 코드를 의미합니다. 이는 시스템 내 코드의 응집도(Cohesion)가 낮다는 것을 보여주는 대표적인 신호입니다. 이러한 코드는 실행 흐름을 추적하기 어렵게 만들어 유지보수성과 가독성을 크게 떨어뜨립니다. @@ -22,11 +22,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 스파게티 코드 (Spaghetti - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[응집도 (Cohesion)]], [[관심사의 분리 (Separation of Concerns)]] +- **Related Topics:** [[응집도 (Cohesion)|응집도 (Cohesion)]], [[관심사의 분리 (Separation of Concerns)|관심사의 분리 (Separation of Concerns)]] - **Projects/Contexts:** 소스에 관련 정보가 부족합니다. - **Contradictions/Notes:** 소스에 관련 정보가 부족합니다. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/스파게티 코드 (Spaghetti Code).md]] +- Raw Source: 00_Raw/2026-04-20/스파게티 코드 (Spaghetti Code).md --- diff --git a/01_Archive/2026-04-20/스포티파이 자율적 분대 모델 (Spotify Squad).md b/01_Archive/2026-04-20/스포티파이 자율적 분대 모델 (Spotify Squad).md index 61edd362..f6caea5a 100644 --- a/01_Archive/2026-04-20/스포티파이 자율적 분대 모델 (Spotify Squad).md +++ b/01_Archive/2026-04-20/스포티파이 자율적 분대 모델 (Spotify Squad).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-376368 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 스포티파이 자율적 분대 모델 (Spotify Squad)" --- -# [[스포티파이 자율적 분대 모델 (Spotify Squad)]] +# [[스포티파이 자율적 분대 모델 (Spotify Squad)|스포티파이 자율적 분대 모델 (Spotify Squad)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 스포티파이(Spotify) 자율적 분대 모델은 조직 구조와 개발 방식에 관심사의 분리(SoC) 원칙을 적용하여 팀 간 의존성을 최소화하고 독립성을 극대화한 조직 운영 모델입니다 [1]. 엔지니어링 조직을 '스쿼드(Squad)'라는 소규모 독립 단위로 나누어 운영하는 것이 핵심입니다 [1]. 이를 통해 조직의 확장성과 유지보수성을 개선하고 병목 현상을 방지합니다 [1]. @@ -23,11 +23,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 스포티파이 자율적 분 - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[관심사의 분리 (Separation of Concerns)]], [[마이크로 프론트엔드 (Micro Frontends)]], [[마이크로서비스 아키텍처 (Microservices Architecture)]] +- **Related Topics:** [[관심사의 분리 (Separation of Concerns)|관심사의 분리 (Separation of Concerns)]], [[마이크로 프론트엔드 (Micro Frontends)|마이크로 프론트엔드 (Micro Frontends)]], [[마이크로서비스 아키텍처 (Microservices Architecture)|마이크로서비스 아키텍처 (Microservices Architecture)]] - **Projects/Contexts:** 대규모 개발 환경에서 팀 간 기술적 간섭을 차단하고, 복잡한 애플리케이션의 확장성과 유지보수성을 획기적으로 개선하기 위한 맥락에서 적용되었습니다 [1]. - **Contradictions/Notes:** 독립적인 스쿼드 운영을 위한 마이크로 프론트엔드 방식을 사용할 경우, 여러 모듈이 동시에 로드되면서 번들 크기가 커지고 초기 로딩 성능에 오버헤드가 발생할 수 있다는 기술적 과제가 공존합니다 [1]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/스포티파이 자율적 분대 모델 (Spotify Squad).md]] +- Raw Source: 00_Raw/2026-04-20/스포티파이 자율적 분대 모델 (Spotify Squad).md --- diff --git a/01_Archive/2026-04-20/스포티파이 자율적 분대 모델 및 마이크로 프론트엔드 (Spotify Squads and Micro Frontends).md b/01_Archive/2026-04-20/스포티파이 자율적 분대 모델 및 마이크로 프론트엔드 (Spotify Squads and Micro Frontends).md index 56cf97a3..19d1e8eb 100644 --- a/01_Archive/2026-04-20/스포티파이 자율적 분대 모델 및 마이크로 프론트엔드 (Spotify Squads and Micro Frontends).md +++ b/01_Archive/2026-04-20/스포티파이 자율적 분대 모델 및 마이크로 프론트엔드 (Spotify Squads and Micro Frontends).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-4B797C -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 스포티파이 자율적 분대 모델 및 마이크로 프론트엔드 (Spotify Squads and Micro Frontends)" --- -# [[스포티파이 자율적 분대 모델 및 마이크로 프론트엔드 (Spotify Squads and Micro Frontends)]] +# [[스포티파이 자율적 분대 모델 및 마이크로 프론트엔드 (Spotify Squads and Micro Frontends)|스포티파이 자율적 분대 모델 및 마이크로 프론트엔드 (Spotify Squads and Micro Frontends)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 스포티파이는 조직 구조와 프론트엔드 개발 방식 모두에 '관심사의 분리(SoC)' 원칙을 적용하여 팀 간의 의존성을 최소화하고 독립성을 극대화한 대표적인 사례입니다 [1]. 조직적으로는 '스쿼드(Squad)'라는 소규모 자율 조직 모델을 도입하여 특정 비즈니스 기능의 디자인부터 배포까지의 모든 과정을 전담하도록 구성했습니다 [1]. 기술적으로는 단일한 거대 웹 애플리케이션을 쪼개어 각 스쿼드가 자신만의 기술 스택으로 웹 플레이어의 특정 부분을 독립적으로 구축하는 마이크로 프론트엔드 아키텍처를 채택했습니다 [1, 2]. 이를 통해 스포티파이는 대규모 시스템 환경에서도 확장성을 확보하고, 한 팀의 작업이 다른 팀의 병목이 되는 현상을 혁신적으로 줄여 더 빠른 릴리스와 유연성을 달성했습니다 [1, 2]. @@ -32,11 +32,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 스포티파이 자율적 분 - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[관심사의 분리 (Separation of Concerns)]], [[마이크로 프론트엔드 (Micro Frontends)]], [[마이크로서비스 아키텍처 (Microservices Architecture)]] -- **Projects/Contexts:** [[대규모 웹 애플리케이션의 조직 및 기술적 확장성 확보]] +- **Related Topics:** [[관심사의 분리 (Separation of Concerns)|관심사의 분리 (Separation of Concerns)]], [[마이크로 프론트엔드 (Micro Frontends)|마이크로 프론트엔드 (Micro Frontends)]], [[마이크로서비스 아키텍처 (Microservices Architecture)|마이크로서비스 아키텍처 (Microservices Architecture)]] +- **Projects/Contexts:** [[대규모 웹 애플리케이션의 조직 및 기술적 확장성 확보|대규모 웹 애플리케이션의 조직 및 기술적 확장성 확보]] - **Contradictions/Notes:** 모놀리식(Monolithic) 구조를 탈피한 스포티파이의 방식은 확장성과 팀의 자율성을 크게 향상시키지만, 여러 마이크로 프론트엔드의 동시 로드로 인한 번들 크기 증가 및 초기 로딩 성능 저하라는 기술적 오버헤드와 트레이드오프(Trade-off) 관계에 있습니다 [1]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/스포티파이 자율적 분대 모델 및 마이크로 프론트엔드 (Spotify Squads and Micro Frontends).md]] +- Raw Source: 00_Raw/2026-04-20/스포티파이 자율적 분대 모델 및 마이크로 프론트엔드 (Spotify Squads and Micro Frontends).md --- diff --git a/01_Archive/2026-04-20/스포티파이 자율적 분대 모델.md b/01_Archive/2026-04-20/스포티파이 자율적 분대 모델.md index 12a29382..a125275d 100644 --- a/01_Archive/2026-04-20/스포티파이 자율적 분대 모델.md +++ b/01_Archive/2026-04-20/스포티파이 자율적 분대 모델.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-14D145 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 스포티파이 자율적 분대 모델" --- -# [[스포티파이 자율적 분대 모델]] +# [[스포티파이 자율적 분대 모델|스포티파이 자율적 분대 모델]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 스포티파이의 자율적 분대(Squad) 모델은 조직 구조와 개발 방식에 '관심사의 분리(SoC)' 철학을 적용하여 팀 간의 의존성을 최소화한 조직 운영 방식입니다 [1]. 엔지니어링 조직을 '스쿼드'라는 소규모 단위로 나누어 각 팀이 독립적으로 움직일 수 있도록 지원합니다 [1]. 이를 통해 한 팀의 작업이 다른 팀의 병목을 초래하는 현상을 혁신적으로 줄이고 확장성을 획기적으로 개선했습니다 [1]. @@ -22,11 +22,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 스포티파이 자율적 분 - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[관심사의 분리 (SoC)]], [[마이크로 프론트엔드 (Micro Frontends)]] -- **Projects/Contexts:** [[스포티파이 (Spotify) 웹 애플리케이션 개발]] +- **Related Topics:** [[관심사의 분리 (SoC)|관심사의 분리 (SoC)]], [[마이크로 프론트엔드 (Micro Frontends)|마이크로 프론트엔드 (Micro Frontends)]] +- **Projects/Contexts:** 스포티파이 (Spotify) 웹 애플리케이션 개발 - **Contradictions/Notes:** 스포티파이의 자율적 분대 모델과 결합된 마이크로 프론트엔드 방식은 대규모 웹 애플리케이션에서 팀 간 독립성과 유지보수성을 크게 높여주지만, 여러 개의 마이크로 프론트엔드가 로드되면서 번들 크기가 커지고 초기 로딩 성능에 오버헤드가 발생할 수 있다는 기술적 과제가 공존합니다 [1]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/스포티파이 자율적 분대 모델.md]] +- Raw Source: 00_Raw/2026-04-20/스포티파이 자율적 분대 모델.md --- diff --git a/01_Archive/2026-04-20/스포티파이(Spotify)의 스쿼드 모델 및 마이크로 프론트엔드 도입.md b/01_Archive/2026-04-20/스포티파이(Spotify)의 스쿼드 모델 및 마이크로 프론트엔드 도입.md index 3623a8e7..5e58b5d5 100644 --- a/01_Archive/2026-04-20/스포티파이(Spotify)의 스쿼드 모델 및 마이크로 프론트엔드 도입.md +++ b/01_Archive/2026-04-20/스포티파이(Spotify)의 스쿼드 모델 및 마이크로 프론트엔드 도입.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-5B6582 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 스포티파이(Spotify)의 스쿼드 모델 및 마이크로 프론트엔드 도입" --- -# [[스포티파이(Spotify)의 스쿼드 모델 및 마이크로 프론트엔드 도입]] +# [[스포티파이(Spotify)의 스쿼드 모델 및 마이크로 프론트엔드 도입|스포티파이(Spotify)의 스쿼드 모델 및 마이크로 프론트엔드 도입]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 스포티파이(Spotify)는 팀 간의 의존성을 최소화하고 독립성을 극대화하기 위해 조직 구조와 프론트엔드 개발 방식 모두에 관심사의 분리(SoC) 원칙을 적용했습니다. 조직을 특정 기능에 대해 완전한 책임을 지는 '스쿼드(Squad)'라는 소규모 단위로 나누고, 거대한 모놀리식 웹 앱을 쪼개어 독립적인 모듈로 결합하는 '마이크로 프론트엔드(Micro Frontends)' 방식을 채택했습니다. 이를 통해 스포티파이는 팀 간의 기술적 간섭을 차단하고 확장성 및 유지보수성을 획기적으로 개선하며 전 세계적인 벤치마킹 대상이 되었습니다. @@ -34,11 +34,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 스포티파이(Spotify)의 - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[관심사의 분리(SoC)]], [[마이크로 프론트엔드(Micro Frontends)]], [[마이크로서비스 아키텍처(MSA)]] -- **Projects/Contexts:** [[스포티파이 웹 플레이어(Spotify Web Player)]] +- **Related Topics:** [[관심사의 분리(SoC)|관심사의 분리(SoC)]], [[마이크로 프론트엔드 (Micro Frontends)|마이크로 프론트엔드(Micro Frontends)]], [[마이크로서비스 아키텍처 (MSA)|마이크로서비스 아키텍처(MSA)]] +- **Projects/Contexts:** 스포티파이 웹 플레이어(Spotify Web Player) - **Contradictions/Notes:** 마이크로 프론트엔드 구조는 확장성과 유지보수성을 비약적으로 개선하지만, 동시에 여러 마이크로 프론트엔드가 로드되면서 번들 크기가 커지고 초기 로딩 성능에 오버헤드가 발생할 수 있다는 단점 및 과제가 공존한다고 소스는 지적합니다 [1]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/스포티파이(Spotify)의 스쿼드 모델 및 마이크로 프론트엔드 도입.md]] +- Raw Source: 00_Raw/2026-04-20/스포티파이(Spotify)의 스쿼드 모델 및 마이크로 프론트엔드 도입.md --- diff --git a/01_Archive/2026-04-20/습관 교정 프로그램.md b/01_Archive/2026-04-20/습관 교정 프로그램.md index db2c2082..e47c2383 100644 --- a/01_Archive/2026-04-20/습관 교정 프로그램.md +++ b/01_Archive/2026-04-20/습관 교정 프로그램.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-240BA8 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 습관 교정 프로그램" --- -# [[습관 교정 프로그램]] +# [[습관 교정 프로그램|습관 교정 프로그램]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - 습관 교정 프로그램" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/습관 교정 프로그램.md]] +- Raw Source: 00_Raw/2026-04-20/습관 교정 프로그램.md --- diff --git a/01_Archive/2026-04-20/시각 및 인지적 후유증 연구.md b/01_Archive/2026-04-20/시각 및 인지적 후유증 연구.md index 307c1660..3db3bea1 100644 --- a/01_Archive/2026-04-20/시각 및 인지적 후유증 연구.md +++ b/01_Archive/2026-04-20/시각 및 인지적 후유증 연구.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-F81826 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 시각 및 인지적 후유증 연구" --- -# [[시각 및 인지적 후유증 연구]] +# [[시각 및 인지적 후유증 연구|시각 및 인지적 후유증 연구]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 가상현실(VR) 환경, 특히 헤드마운트 디스플레이(HMD)를 사용하는 엑서게임(Exergaming) 후 발생하는 시각 및 인지적 후유증(aftereffects)을 정량적으로 측정하고 분석하는 연구입니다 [1, 2]. 이 연구는 짧은 시간(10분)과 긴 시간(50분)의 VR 노출 전, 노출 직후, 그리고 40분 후로 나누어 사용자의 시력 조절(accommodation), 폭주(convergence), 반응 시간, 주관적 멀미 증상을 평가합니다 [2]. 사용자가 겪는 VR 멀미가 심도 지각과 인지에 미치는 영향을 파악하여, VR의 안전한 사용 및 잠재적 부상 위험을 줄이기 위한 권장 사항을 제공하는 데 목적이 있습니다 [1, 3]. @@ -30,11 +30,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 시각 및 인지적 후유증 - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[가상현실 멀미(VR Sickness)]], [[조절-폭주 불일치(Vergence-Accommodation Conflict)]], [[반응 시간(Reaction Time)]] -- **Projects/Contexts:** [[비트 세이버 엑서게임 후유증 평가(Beat Saber Exergaming Aftereffects)]] +- **Related Topics:** [[가상현실 멀미(VR Sickness)|가상현실 멀미(VR Sickness)]], [[조절-폭주 불일치(Vergence-Accommodation Conflict)|조절-폭주 불일치(Vergence-Accommodation Conflict)]], [[반응 시간(Reaction Time)|반응 시간(Reaction Time)]] +- **Projects/Contexts:** [[비트 세이버 엑서게임 후유증 평가(Beat Saber Exergaming Aftereffects)|비트 세이버 엑서게임 후유증 평가(Beat Saber Exergaming Aftereffects)]] - **Contradictions/Notes:** VR 노출이 자극에 빠르게 반응하는 인지 능력(반응 시간)에 미치는 직각적인 영향에 대해서 문헌상으로 반응 속도가 느려진다는 연구와 빨라진다는 연구가 혼재되어 일관성이 다소 부족하다는 점이 지적됩니다 [9]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/시각 및 인지적 후유증 연구.md]] +- Raw Source: 00_Raw/2026-04-20/시각 및 인지적 후유증 연구.md --- diff --git a/01_Archive/2026-04-20/시각-전정 갈등 (Visual-Vestibular Conflict).md b/01_Archive/2026-04-20/시각-전정 갈등 (Visual-Vestibular Conflict).md index 705447ff..5d3ac983 100644 --- a/01_Archive/2026-04-20/시각-전정 갈등 (Visual-Vestibular Conflict).md +++ b/01_Archive/2026-04-20/시각-전정 갈등 (Visual-Vestibular Conflict).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-495C24 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 시각-전정 갈등 (Visual-Vestibular Conflict)" --- -# [[시각-전정 갈등 (Visual-Vestibular Conflict)]] +# [[시각-전정 갈등 (Visual-Vestibular Conflict)|시각-전정 갈등 (Visual-Vestibular Conflict)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 시각-전정 갈등(Visual-Vestibular Conflict)은 가상 현실(VR) 환경 등에서 시각적으로 주어지는 경험과 사용자의 실제 신체적·육체적(전정) 감각이 일치하지 않을 때 발생하는 현상입니다 [1]. 인간이 환경과 상호작용하는 데 필수적인 감각 통합 과정에 교란을 일으키는 것이 특징입니다 [1]. 이 현상은 VR 환경에서 메스꺼움이나 방향 감각 상실과 같은 멀미 증상을 유발하는 주요 이론적 원인으로 설명됩니다 [1]. @@ -21,11 +21,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 시각-전정 갈등 (Visual-V - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[가상 현실 멀미 (VR Sickness)]], [[감각 통합 (Sensory Integration)]], [[양안 시차-조절 갈등 (Vergence-Accommodation Conflict)]] -- **Projects/Contexts:** [[비트 세이버를 활용한 가상 현실 엑서게임 후유증 연구 (VR Exergaming Aftereffects Investigation)]] +- **Related Topics:** [[가상현실 멀미 (VR Sickness)|가상 현실 멀미 (VR Sickness)]], [[감각 통합(Sensory integration)|감각 통합 (Sensory Integration)]], 양안 시차-조절 갈등 (Vergence-Accommodation Conflict) +- **Projects/Contexts:** 비트 세이버를 활용한 가상 현실 엑서게임 후유증 연구 (VR Exergaming Aftereffects Investigation) - **Contradictions/Notes:** 소스에서는 시각-전정 갈등 이론과 더불어, 헤드마운트 디스플레이(HMD) 사용 시 발생하는 '양안 시차-조절 갈등(vergence-accommodation conflict)' 역시 안구 운동 증상 및 시각적 피로를 유발하여 멀미의 심각성을 가중시킬 수 있는 또 다른 주요 요인으로 함께 언급하고 있습니다 [1]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/시각-전정 갈등 (Visual-Vestibular Conflict).md]] +- Raw Source: 00_Raw/2026-04-20/시각-전정 갈등 (Visual-Vestibular Conflict).md --- diff --git a/01_Archive/2026-04-20/시각-전정 감각 충돌(Visual-Vestibular Conflict).md b/01_Archive/2026-04-20/시각-전정 감각 충돌(Visual-Vestibular Conflict).md index 41887b7b..b82a3fc9 100644 --- a/01_Archive/2026-04-20/시각-전정 감각 충돌(Visual-Vestibular Conflict).md +++ b/01_Archive/2026-04-20/시각-전정 감각 충돌(Visual-Vestibular Conflict).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-1CF133 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 시각-전정 감각 충돌(Visual-Vestibular Conflict)" --- -# [[시각-전정 감각 충돌(Visual-Vestibular Conflict)]] +# [[시각-전정 감각 충돌(Visual-Vestibular Conflict)|시각-전정 감각 충돌(Visual-Vestibular Conflict)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 시각-전정 감각 충돌은 가상 현실(VR)과 같은 환경에서 사용자의 시각적 경험이 실제 물리적, 신체적 경험과 일치하지 않을 때 발생하는 감각 불일치 현상입니다 [1]. 인간이 환경과 상호작용하기 위해 필수적인 시각과 전정(신체) 감각의 정보가 뇌로 전달될 때 서로 충돌하게 되면 감각 통합에 교란이 발생하게 됩니다 [1]. 이 현상은 메스꺼움이나 방향 감각 상실 등 멀미(VR 멀미) 증상을 유발하는 주요 원인으로 작용합니다 [1]. @@ -22,11 +22,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 시각-전정 감각 충돌(Vi - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[가상 현실 멀미(VR Sickness)]], [[감각 통합(Sensory Integration)]] -- **Projects/Contexts:** [[VR 엑서게임(VR Exergaming)]] (예: '비트 세이버(Beat Saber)'와 같이 사용자의 적극적인 신체 움직임과 3D 시각 환경이 결합되어 감각 충돌의 위험이 내재된 가상 현실 게임 연구 환경 [2], [1]) +- **Related Topics:** [[가상현실 멀미 (VR Sickness)|가상 현실 멀미(VR Sickness)]], [[감각 통합(Sensory integration)|감각 통합(Sensory Integration)]] +- **Projects/Contexts:** [[VR 엑서게임 (VR Exergaming)|VR 엑서게임(VR Exergaming)]] (예: '비트 세이버(Beat Saber)'와 같이 사용자의 적극적인 신체 움직임과 3D 시각 환경이 결합되어 감각 충돌의 위험이 내재된 가상 현실 게임 연구 환경 [2], [1]) - **Contradictions/Notes:** 소스에 따르면 VR 멀미의 발병 원인에 대해서는 학계의 완전한 합의(consensus)가 아직 없으며, 시각-전정 감각 충돌은 이를 설명하는 여러 유력한 이론(prominent theory) 중 하나로 제시되고 있습니다 [1]. 그 외에 본 주제와 상충하는 이론에 대해서는 소스에 관련 정보가 부족합니다. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/시각-전정 감각 충돌(Visual-Vestibular Conflict).md]] +- Raw Source: 00_Raw/2026-04-20/시각-전정 감각 충돌(Visual-Vestibular Conflict).md --- diff --git a/01_Archive/2026-04-20/시각-전정 충돌(Visual-vestibular conflict).md b/01_Archive/2026-04-20/시각-전정 충돌(Visual-vestibular conflict).md index 9e8e670c..a33d72b2 100644 --- a/01_Archive/2026-04-20/시각-전정 충돌(Visual-vestibular conflict).md +++ b/01_Archive/2026-04-20/시각-전정 충돌(Visual-vestibular conflict).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-F2748B -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 시각-전정 충돌(Visual-vestibular conflict)" --- -# [[시각-전정 충돌(Visual-vestibular conflict)]] +# [[시각-전정 충돌(Visual-vestibular conflict)|시각-전정 충돌(Visual-vestibular conflict)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 시각-전정 충돌(Visual-vestibular conflict)은 가상 세계에서의 시각적 경험이 실제 사용자의 신체적(육체적) 경험과 일치하지 않을 때 발생하는 감각의 불일치 현상입니다 [1]. 이로 인해 뇌로 전달되는 시각 및 전정 감각 간에 충돌이 일어나 감각 통합에 교란이 발생하며, 이는 메스꺼움이나 방향 상실과 같은 멀미(VR sickness) 증상을 유발하는 주요 원인이 됩니다 [1]. @@ -23,11 +23,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 시각-전정 충돌(Visual-ve - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[VR 멀미(VR sickness)]], [[감각 통합(Sensory integration)]], [[폭주-조절 충돌(Vergence-accommodation conflict)]] -- **Projects/Contexts:** [[가상현실 엑서게임 후유증 연구(Virtual reality exergaming aftereffects research)]] +- **Related Topics:** [[VR 멀미(VR sickness)|VR 멀미(VR sickness)]], [[감각 통합(Sensory integration)|감각 통합(Sensory integration)]], [[폭주-조절 충돌(Vergence-accommodation conflict)|폭주-조절 충돌(Vergence-accommodation conflict)]] +- **Projects/Contexts:** [[가상현실 엑서게임 후유증 연구(Virtual reality exergaming aftereffects research)|가상현실 엑서게임 후유증 연구(Virtual reality exergaming aftereffects research)]] - **Contradictions/Notes:** 소스에 따르면 VR 멀미의 정확한 병인에 대해 학계의 완전한 합의(consensus)는 존재하지 않으며, 시각-전정 충돌은 이를 설명하기 위해 널리 받아들여지는 유력한 이론 중 하나로 제시됩니다 [1]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/시각-전정 충돌(Visual-vestibular conflict).md]] +- Raw Source: 00_Raw/2026-04-20/시각-전정 충돌(Visual-vestibular conflict).md --- diff --git a/01_Archive/2026-04-20/시맨틱 웹 (Semantic Web).md b/01_Archive/2026-04-20/시맨틱 웹 (Semantic Web).md index d5b3e5ab..030068ac 100644 --- a/01_Archive/2026-04-20/시맨틱 웹 (Semantic Web).md +++ b/01_Archive/2026-04-20/시맨틱 웹 (Semantic Web).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-A9C2AC -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 시맨틱 웹 (Semantic Web)" --- -# [[시맨틱 웹 (Semantic Web)]] +# [[시맨틱 웹 (Semantic Web)|시맨틱 웹 (Semantic Web)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - 시맨틱 웹 (Semantic Web)" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/시맨틱 웹 (Semantic Web).md]] +- Raw Source: 00_Raw/2026-04-20/시맨틱 웹 (Semantic Web).md --- diff --git a/01_Archive/2026-04-20/시뮬레이터 멀미 설문지(SSQ).md b/01_Archive/2026-04-20/시뮬레이터 멀미 설문지(SSQ).md index 1ca69b6a..6b9bb681 100644 --- a/01_Archive/2026-04-20/시뮬레이터 멀미 설문지(SSQ).md +++ b/01_Archive/2026-04-20/시뮬레이터 멀미 설문지(SSQ).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-30F8D3 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 시뮬레이터 멀미 설문지(SSQ)" --- -# [[시뮬레이터 멀미 설문지(SSQ)]] +# [[시뮬레이터 멀미 설문지(SSQ)|시뮬레이터 멀미 설문지(SSQ)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 시뮬레이터 멀미 설문지(SSQ, Simulator Sickness Questionnaire)는 가상현실(VR) 기기나 시뮬레이터 사용 시 나타나는 멀미 증상과 부작용을 측정하기 위해 널리 사용되는 주관적 자기 보고식 평가 도구입니다 [1]. 16개의 증상 항목에 대해 0점(없음)부터 3점(심각함)까지의 4점 척도로 응답하도록 구성되어 있습니다 [1]. 수집된 점수는 메스꺼움, 안구운동, 방향 감각 상실이라는 세 가지 주요 하위 범주로 분류되어 사용자의 멀미 심각도를 정량화합니다 [1]. @@ -32,11 +32,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 시뮬레이터 멀미 설문 - **정책 변화:** AI 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[가상현실 멀미(VR sickness)]], [[사후 영향(Aftereffects)]] -- **Projects/Contexts:** [[비트 세이버(Beat Saber)를 활용한 가상현실 엑서게이밍 사후 영향 연구]] +- **Related Topics:** [[가상현실 멀미 (VR Sickness)|가상현실 멀미(VR sickness)]], 사후 영향(Aftereffects) +- **Projects/Contexts:** 비트 세이버(Beat Saber)를 활용한 가상현실 엑서게이밍 사후 영향 연구 - **Contradictions/Notes:** 소스에 관련 정보가 부족합니다. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/시뮬레이터 멀미 설문지(SSQ).md]] +- Raw Source: 00_Raw/2026-04-20/시뮬레이터 멀미 설문지(SSQ).md --- diff --git a/01_Archive/2026-04-20/시뮬레이터 멀미 설문지(Simulator Sickness Questionnaire).md b/01_Archive/2026-04-20/시뮬레이터 멀미 설문지(Simulator Sickness Questionnaire).md index 6df792ac..fae41210 100644 --- a/01_Archive/2026-04-20/시뮬레이터 멀미 설문지(Simulator Sickness Questionnaire).md +++ b/01_Archive/2026-04-20/시뮬레이터 멀미 설문지(Simulator Sickness Questionnaire).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-C8E657 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 시뮬레이터 멀미 설문지(Simulator Sickness Questionnaire)" --- -# [[시뮬레이터 멀미 설문지(Simulator Sickness Questionnaire)]] +# [[시뮬레이터 멀미 설문지(Simulator Sickness Questionnaire)|시뮬레이터 멀미 설문지(Simulator Sickness Questionnaire)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 시뮬레이터 멀미 설문지(SSQ)는 시뮬레이터 및 가상현실(VR) 연구에서 멀미 증상을 정량화하기 위해 가장 널리 사용되는 평가 도구입니다 [1]. 이 설문지는 총 16개의 증상 항목을 0점(없음)부터 3점(심각함)까지의 4점 척도로 평가합니다 [1]. 수집된 데이터는 메스꺼움, 안구 운동, 방향 상실이라는 세 가지 주요 하위 범주로 분류되어 사용자의 신체적, 인지적 불편함을 측정합니다 [1]. @@ -26,11 +26,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 시뮬레이터 멀미 설문 - **정책 변화:** AI 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[가상현실 멀미(VR Sickness)]], [[가상현실(Virtual Reality)]] -- **Projects/Contexts:** [[Beat Saber VR 엑서게임 연구]] +- **Related Topics:** [[가상현실 멀미(VR Sickness)|가상현실 멀미(VR Sickness)]], 가상현실(Virtual Reality) +- **Projects/Contexts:** Beat Saber VR 엑서게임 연구 - **Contradictions/Notes:** 소스에 따르면 높은 SSQ 점수(20점 초과)는 시뮬레이터의 문제를 시사하는 것으로 제안되지만, 정작 이 높은 점수가 사용자의 실제 일상생활 및 수행 능력 저하와 어떻게 연결되는지는 명확히 규명되지 않은 채로 남아 있습니다 [2]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/시뮬레이터 멀미 설문지(Simulator Sickness Questionnaire).md]] +- Raw Source: 00_Raw/2026-04-20/시뮬레이터 멀미 설문지(Simulator Sickness Questionnaire).md --- diff --git a/01_Archive/2026-04-20/시스템 다이내믹스 (System Dynamics).md b/01_Archive/2026-04-20/시스템 다이내믹스 (System Dynamics).md index a21dadbd..17260e3b 100644 --- a/01_Archive/2026-04-20/시스템 다이내믹스 (System Dynamics).md +++ b/01_Archive/2026-04-20/시스템 다이내믹스 (System Dynamics).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-6FAAF2 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 시스템 다이내믹스 (System Dynamics)" --- -# [[시스템 다이내믹스 (System Dynamics)]] +# [[시스템 다이내믹스 (System Dynamics)|시스템 다이내믹스 (System Dynamics)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - 시스템 다이내믹스 (Sys ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/시스템 다이내믹스 (System Dynamics).md]] +- Raw Source: 00_Raw/2026-04-20/시스템 다이내믹스 (System Dynamics).md --- diff --git a/01_Archive/2026-04-20/시프트 레프트 (Shift-Left).md b/01_Archive/2026-04-20/시프트 레프트 (Shift-Left).md index 1e6a2e7d..35083a99 100644 --- a/01_Archive/2026-04-20/시프트 레프트 (Shift-Left).md +++ b/01_Archive/2026-04-20/시프트 레프트 (Shift-Left).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-78B318 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 시프트 레프트 (Shift-Left)" --- -# [[시프트 레프트 (Shift-Left)]] +# [[시프트 레프트 (Shift-Left)|시프트 레프트 (Shift-Left)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 시프트 레프트(Shift-Left)는 소프트웨어 개발 수명 주기(SDLC)에서 품질 검사 및 보안 취약점 탐지를 개발 초기 단계로 앞당기는 접근 방식을 의미합니다 [1, 2]. 코드를 실행하기 전인 IDE 작업, 커밋 전(pre-commit) 훅, 풀 리퀘스트(PR) 및 CI 파이프라인 단계에 정적 분석 도구를 통합하여 문제를 선제적으로 해결하는 것을 목표로 합니다 [3, 4]. 이를 통해 취약점이 프로덕션 환경에 도달하기 전에 발견함으로써, 복구에 드는 시간과 비용을 크게 절감할 수 있습니다 [3, 5]. @@ -22,11 +22,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 시프트 레프트 (Shift-Lef - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[DevSecOps]], [[SAST (Static Application Security Testing)]], [[CI/CD]] -- **Projects/Contexts:** [[Snyk Code]], [[Corgea]], [[Axify]] +- **Related Topics:** [[DevSecOps|DevSecOps]], [[SAST (Static Application Security Testing)|SAST (Static Application Security Testing)]], [[CI_CD|CI/CD]] +- **Projects/Contexts:** Snyk Code, [[Corgea|Corgea]], [[Axify|Axify]] - **Contradictions/Notes:** 제공된 소스 전반에 걸쳐 시프트 레프트 접근법에 대한 반대 의견은 존재하지 않으며, 모든 문서가 조기 발견을 통한 수정 비용 절감 및 개발 속도 향상 효과를 긍정적으로 평가하고 있습니다. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/시프트 레프트 (Shift-Left).md]] +- Raw Source: 00_Raw/2026-04-20/시프트 레프트 (Shift-Left).md --- diff --git a/01_Archive/2026-04-20/시프트 레프트(Shift-Left).md b/01_Archive/2026-04-20/시프트 레프트(Shift-Left).md index e160b3aa..0c1e0dc3 100644 --- a/01_Archive/2026-04-20/시프트 레프트(Shift-Left).md +++ b/01_Archive/2026-04-20/시프트 레프트(Shift-Left).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-BC9D48 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 시프트 레프트(Shift-Left)" --- -# [[시프트 레프트(Shift-Left)]] +# [[시프트 레프트(Shift-Left)|시프트 레프트(Shift-Left)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 시프트 레프트(Shift-Left)는 소프트웨어 개발 수명 주기(SDLC)의 초기 단계에서 취약점이나 버그를 탐지하고 수정하는 DevSecOps의 핵심 전략입니다 [1, 2]. 개발자가 코드를 작성하는 IDE나 CI/CD 파이프라인에 보안 검사를 통합하여, 코드가 프로덕션 환경에 도달하기 전에 문제를 미리 파악합니다 [3, 4]. 이를 통해 개발 후반부나 배포 이후에 문제를 수정하는 것보다 훨씬 적은 비용으로 신속하게 결함을 해결할 수 있게 합니다 [5]. @@ -23,11 +23,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 시프트 레프트(Shift-Left - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[DevSecOps]], [[SAST (Static Application Security Testing)]], [[SDLC (소프트웨어 개발 수명 주기)]], [[CI/CD]] +- **Related Topics:** [[DevSecOps|DevSecOps]], [[SAST (Static Application Security Testing)|SAST (Static Application Security Testing)]], [[SDLC (소프트웨어 개발 수명 주기)|SDLC (소프트웨어 개발 수명 주기)]], [[CI_CD|CI/CD]] - **Projects/Contexts:** 코드가 작성되는 IDE, 풀 리퀘스트, CI 파이프라인 단계에 직접 통합하여 소프트웨어가 출시되기 전에 취약점과 버그를 수정하는 컨텍스트에서 주로 사용됩니다 [3, 5]. 구체적인 사례로 BDC 회사는 QA 단계의 시프트 레프트를 통해 소프트웨어 딜리버리를 최적화한 바 있습니다 [8]. - **Contradictions/Notes:** 주어진 소스 내에서 시프트 레프트 개념과 관련하여 상충하는 의견은 확인되지 않습니다. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/시프트 레프트(Shift-Left).md]] +- Raw Source: 00_Raw/2026-04-20/시프트 레프트(Shift-Left).md --- diff --git a/01_Archive/2026-04-20/식별 가능한 유니온 (Discriminated Unions).md b/01_Archive/2026-04-20/식별 가능한 유니온 (Discriminated Unions).md index f50e5a0a..5cffcc56 100644 --- a/01_Archive/2026-04-20/식별 가능한 유니온 (Discriminated Unions).md +++ b/01_Archive/2026-04-20/식별 가능한 유니온 (Discriminated Unions).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-EE02DB -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 식별 가능한 유니온 (Discriminated Unions)" --- -# [[식별 가능한 유니온 (Discriminated Unions)]] +# [[식별 가능한 유니온 (Discriminated Unions)|식별 가능한 유니온 (Discriminated Unions)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -23,11 +23,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 식별 가능한 유니온 (Di - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[유니온 타입 (Union Types)]], [[타입 좁히기 (Type Narrowing)]], [[완전성 검사 (Exhaustiveness Checking)]], [[네버 타입 (never type)]] -- **Projects/Contexts:** [[상태 머신 (State Machine) 모델링 및 Redux 액션/리듀서 설계]], [[API 응답 및 에러 핸들링 아키텍처]] +- **Related Topics:** [[유니온 타입 (Union Types)|유니온 타입 (Union Types)]], [[타입 좁히기 (Type Narrowing)|타입 좁히기 (Type Narrowing)]], [[완전성 검사 (Exhaustiveness Checking)|완전성 검사 (Exhaustiveness Checking)]], [[네버 타입 (never type)|네버 타입 (never type)]] +- **Projects/Contexts:** [[상태 머신 (State Machine) 모델링 및 Redux 액션_리듀서 설계|상태 머신 (State Machine) 모델링 및 Redux 액션/리듀서 설계]], [[API 응답 및 에러 핸들링 아키텍처|API 응답 및 에러 핸들링 아키텍처]] - **Contradictions/Notes:** 소스에 따르면 식별 가능한 유니온은 런타임 오버헤드가 전혀 없는 강력한 컴파일 타임 기능이지만, 너무 깊게 중첩된(Deep nesting) 식별 가능한 유니온을 남용할 경우 에러 메시지를 읽기 어렵게 만들고 거대한 유니온 타입으로 인해 TypeScript 컴파일 속도가 저하될 수 있다는 단점이 있다 [20]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/식별 가능한 유니온 (Discriminated Unions).md]] +- Raw Source: 00_Raw/2026-04-20/식별 가능한 유니온 (Discriminated Unions).md --- diff --git a/01_Archive/2026-04-20/식별 가능한 유니온(Discriminated Unions).md b/01_Archive/2026-04-20/식별 가능한 유니온(Discriminated Unions).md index 95acd38e..edf84e68 100644 --- a/01_Archive/2026-04-20/식별 가능한 유니온(Discriminated Unions).md +++ b/01_Archive/2026-04-20/식별 가능한 유니온(Discriminated Unions).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-0228C6 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 식별 가능한 유니온(Discriminated Unions)" --- -# [[식별 가능한 유니온(Discriminated Unions)]] +# [[식별 가능한 유니온(Discriminated Unions)|식별 가능한 유니온(Discriminated Unions)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 식별 가능한 유니온(Discriminated Unions, 태그된 유니온)은 여러 다른 형태의 데이터를 구별하기 위해 공통된 리터럴 타입 속성(판별자)을 사용하는 TypeScript 패턴이다 [1-3]. 이 패턴은 컴파일러가 각 조건 블록에서 타입을 자동으로 좁혀(Narrowing) 유효하지 않은 상태의 생성을 원천적으로 방지하고 타입 안정성을 보장할 수 있게 한다 [4, 5]. @@ -20,11 +20,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 식별 가능한 유니온(Dis - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[유니온 타입(Union Types)]], [[타입 좁히기(Type Narrowing)]], [[완전성 검사(Exhaustiveness Checking)]], [[never 타입]] -- **Projects/Contexts:** [[상태 머신(State Machine) 설계]], [[React 상태 관리 및 API 응답 처리]] +- **Related Topics:** [[유니온 타입(Union Types)|유니온 타입(Union Types)]], [[타입 좁히기(Type Narrowing)|타입 좁히기(Type Narrowing)]], [[완전성 검사(Exhaustiveness Checking)|완전성 검사(Exhaustiveness Checking)]], [[never 타입|never 타입]] +- **Projects/Contexts:** [[상태 머신(State Machine) 설계|상태 머신(State Machine) 설계]], [[React 상태 관리 및 API 응답 처리|React 상태 관리 및 API 응답 처리]] - **Contradictions/Notes:** 컴파일 시점의 정적 타이핑만 제공하므로 외부에서 유입되는 API 데이터나 설정 파일의 정합성을 보장하려면 런타임 검증 라이브러리(예: Zod)와 함께 사용하는 것이 권장된다 [18, 19]. 또한, 복잡한 분기 처리를 돕기 위해 `ts-pattern`과 같은 외부 라이브러리를 도입할 수 있으나, 이는 기존의 switch나 if/else 문에 기반한 식별 가능한 유니온보다 연산 성능이 떨어질 수 있으므로 성능과 가독성 사이의 트레이드오프를 고려해야 한다 [11, 20, 21]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/식별 가능한 유니온(Discriminated Unions).md]] +- Raw Source: 00_Raw/2026-04-20/식별 가능한 유니온(Discriminated Unions).md --- diff --git a/01_Archive/2026-04-20/식별 가능한 유니온.md b/01_Archive/2026-04-20/식별 가능한 유니온.md index 26a77a64..59e166c5 100644 --- a/01_Archive/2026-04-20/식별 가능한 유니온.md +++ b/01_Archive/2026-04-20/식별 가능한 유니온.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-AB1669 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 식별 가능한 유니온" --- -# [[식별 가능한 유니온]] +# [[식별 가능한 유니온|식별 가능한 유니온]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 식별 가능한 유니온(Discriminated Union 또는 Tagged Union)은 여러 형태의 데이터 구조를 공통 리터럴 속성(판별자)을 통해 구별하는 TypeScript의 강력한 타입 패턴이다 [1, 2]. 이 패턴을 사용하면 TypeScript 컴파일러가 공통 속성의 값을 바탕으로 타입을 자동으로 좁혀(Narrowing) 타입 안전성을 보장한다 [2, 3]. 결과적으로 유효하지 않은 상태 표현을 원천적으로 방지하며, 완전성 검사(Exhaustiveness Checking)를 통해 누락된 코드 케이스를 컴파일 타임에 효과적으로 찾아낼 수 있다 [4-6]. @@ -23,11 +23,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 식별 가능한 유니온" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[타입 좁히기(Type Narrowing)]], [[완전성 검사(Exhaustiveness Checking)]], [[never 타입]] -- **Projects/Contexts:** [[상태 머신(State Machine)]], [[API 응답 처리(API Response Handling)]] +- **Related Topics:** [[타입 좁히기(Type Narrowing)|타입 좁히기(Type Narrowing)]], [[완전성 검사(Exhaustiveness Checking)|완전성 검사(Exhaustiveness Checking)]], [[never 타입|never 타입]] +- **Projects/Contexts:** 상태 머신(State Machine), API 응답 처리(API Response Handling) - **Contradictions/Notes:** 소스 간의 직접적인 모순은 없으나, 주의 사항이 존재한다. 식별 가능한 유니온 분기 처리를 더 선언적이고 안전하게 작성하기 위해 `ts-pattern`과 같은 패턴 매칭 라이브러리를 활용할 수 있지만, 자바스크립트의 기본 제어 구조인 `if/else`나 `switch` 문에 비해 심각한 성능 저하(약 99% 연산 감소)를 일으킬 수 있으므로 무분별한 사용은 지양하고 상황에 맞는 도구를 선택해야 한다 [19, 20]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/식별 가능한 유니온.md]] +- Raw Source: 00_Raw/2026-04-20/식별 가능한 유니온.md --- diff --git a/01_Archive/2026-04-20/신경 가소성 (Neuroplasticity).md b/01_Archive/2026-04-20/신경 가소성 (Neuroplasticity).md index 6db0592c..0a59697f 100644 --- a/01_Archive/2026-04-20/신경 가소성 (Neuroplasticity).md +++ b/01_Archive/2026-04-20/신경 가소성 (Neuroplasticity).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-871BD5 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 신경 가소성 (Neuroplasticity)" --- -# [[신경 가소성 (Neuroplasticity)]] +# [[신경 가소성 (Neuroplasticity)|신경 가소성 (Neuroplasticity)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - 신경 가소성 (Neuroplastic ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/신경 가소성 (Neuroplasticity).md]] +- Raw Source: 00_Raw/2026-04-20/신경 가소성 (Neuroplasticity).md --- diff --git a/01_Archive/2026-04-20/실시간 데이터 대시보드 레이아웃 조절 시스템.md b/01_Archive/2026-04-20/실시간 데이터 대시보드 레이아웃 조절 시스템.md index c4994f39..97a60776 100644 --- a/01_Archive/2026-04-20/실시간 데이터 대시보드 레이아웃 조절 시스템.md +++ b/01_Archive/2026-04-20/실시간 데이터 대시보드 레이아웃 조절 시스템.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-BAC69B -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 실시간 데이터 대시보드 레이아웃 조절 시스템" --- -# [[실시간 데이터 대시보드 레이아웃 조절 시스템]] +# [[실시간 데이터 대시보드 레이아웃 조절 시스템|실시간 데이터 대시보드 레이아웃 조절 시스템]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 실시간으로 쏟아지는 대규모 데이터를 시각화하는 대시보드 환경에서, 사용자의 레이아웃 변경(위젯 크기 조절, 드래그 등)과 잦은 데이터 업데이트가 충돌하여 UI가 멈추거나 버벅거리는 현상을 방지하는 고성능 렌더링 및 상태 제어 시스템입니다. @@ -31,12 +31,12 @@ github_commit: "[P-Reinforce] Continuous Worker - 실시간 데이터 대시보 - **정책 변화:** Design & Experience 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Throttling & Debouncing]], [[React 동시성 훅 (useTransition, useDeferredValue)]], [[상태 관리 최적화 (Zustand, Jotai, Valtio)]], [[Virtualization (리스트 가상화)]], [[Web Worker (웹 워커)]] -- **Projects/Contexts:** [[대용량 데이터 분석 플랫폼 및 모니터링 시스템]], [[고성능 금융/주식 실시간 거래 대시보드]] +- **Related Topics:** [[Throttling & Debouncing|Throttling & Debouncing]], [[React 동시성 훅 (useTransition, useDeferredValue)|React 동시성 훅 (useTransition, useDeferredValue)]], [[상태 관리 최적화 (Zustand, Jotai, Valtio)|상태 관리 최적화 (Zustand, Jotai, Valtio)]], Virtualization (리스트 가상화), [[Web Worker (웹 워커)|Web Worker (웹 워커)]] +- **Projects/Contexts:** 대용량 데이터 분석 플랫폼 및 모니터링 시스템, 고성능 금융/주식 실시간 거래 대시보드 - **Contradictions/Notes:** React에 내장된 Context API는 테마나 로그인 정보처럼 가끔 변하는 데이터에는 훌륭하지만, 고빈도로 상태가 업데이트되는 실시간 대시보드에서는 성능을 조용히 갉아먹는 주범이 되므로 대안 상태 관리 도구가 필수적입니다. --- _Last updated: 2026-04-15_ -- Raw Source: [[00_Raw/2026-04-20/실시간 데이터 대시보드 레이아웃 조절 시스템.md]] +- Raw Source: 00_Raw/2026-04-20/실시간 데이터 대시보드 레이아웃 조절 시스템.md --- diff --git a/01_Archive/2026-04-20/실시간 렌더링 파이프라인.md b/01_Archive/2026-04-20/실시간 렌더링 파이프라인.md index 8ebfe365..45a10614 100644 --- a/01_Archive/2026-04-20/실시간 렌더링 파이프라인.md +++ b/01_Archive/2026-04-20/실시간 렌더링 파이프라인.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-8DF18B -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 실시간 렌더링 파이프라인" --- -# [[실시간 렌더링 파이프라인]] +# [[실시간 렌더링 파이프라인|실시간 렌더링 파이프라인]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 실시간 렌더링 파이프라인은 CPU와 GPU 간의 통신을 통해 3D 객체를 화면에 실시간으로 그려내는 일련의 과정이다 [1]. 이 과정은 CPU가 렌더링 상태를 설정하고 명령을 전달하는 드로우 콜(Draw Call) 단계로 시작하여, GPU가 정점을 변환하고 픽셀을 계산하여 화면에 출력하는 단계로 구성된다 [1, 2]. 파이프라인의 성능은 주로 이 두 장치 간의 통신 오버헤드와 데이터 전송 효율성, 그리고 GPU의 병목 현상을 어떻게 최적화하느냐에 따라 결정된다 [1, 3]. @@ -20,11 +20,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 실시간 렌더링 파이프 - **정책 변화:** Graphics & Performance 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[드로우 콜 (Draw Call)]], [[하드웨어 인스턴싱 (Hardware Instancing)]], [[프래그먼트 셰이딩 (Fragment Shading)]], [[오버드로우 (Overdraw)]] -- **Projects/Contexts:** [[Three.js]], [[WebGPU]], [[Unity]], [[BatchedMesh]] +- **Related Topics:** 드로우 콜 (Draw Call), 하드웨어 인스턴싱 (Hardware Instancing), [[프래그먼트 셰이딩(Fragment Shading)|프래그먼트 셰이딩 (Fragment Shading)]], [[오버드로우(Overdraw)|오버드로우 (Overdraw)]] +- **Projects/Contexts:** [[Three.js|Three.js]], [[WebGPU|WebGPU]], [[Unity|Unity]], [[BatchedMesh|BatchedMesh]] - **Contradictions/Notes:** 실시간 렌더링 파이프라인에서 드로우 콜을 줄이기 위해 도입하는 InstancedMesh 기법은 CPU 오버헤드는 획기적으로 낮추지만, 가시성 판단 로직(시야 절두체 컬링) 부재와 객체 자동 정렬 기능의 한계로 인해 오히려 GPU 측(프래그먼트 처리 등)에 새로운 병목과 막대한 오버드로우 비용을 유발할 수 있다는 기술적 딜레마가 존재한다 [7-9, 15]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/실시간 렌더링 파이프라인.md]] +- Raw Source: 00_Raw/2026-04-20/실시간 렌더링 파이프라인.md --- diff --git a/01_Archive/2026-04-20/실시간 물리 및 유체 시뮬레이션.md b/01_Archive/2026-04-20/실시간 물리 및 유체 시뮬레이션.md index 10c84a97..3884e59c 100644 --- a/01_Archive/2026-04-20/실시간 물리 및 유체 시뮬레이션.md +++ b/01_Archive/2026-04-20/실시간 물리 및 유체 시뮬레이션.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-4173D4 -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 실시간 물리 및 유체 시뮬레이션" --- -# [[실시간 물리 및 유체 시뮬레이션]] +# [[실시간 물리 및 유체 시뮬레이션|실시간 물리 및 유체 시뮬레이션]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 실시간 물리 및 유체 시뮬레이션은 입자의 움직임과 복잡한 물리적 상호작용을 실시간으로 계산하여 시각화하는 기술입니다. 과거에는 CPU에서 관련 계산을 수행하여 처리량에 한계가 있었으나, 최근에는 WebGPU와 컴퓨트 셰이더(Compute Shaders)를 활용해 연산을 GPU로 오프로드(Offload)하는 방식이 도입되었습니다. 이를 통해 수십만에서 수백만 개에 달하는 입자 시스템과 유체 역학을 웹 브라우저 상에서 지연 없이 부드럽게 렌더링할 수 있게 되었습니다. @@ -23,11 +23,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 실시간 물리 및 유체 - **정책 변화:** Graphics & Performance 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[WebGPU]], [[컴퓨트 셰이더(Compute Shaders)]], [[스토리지 텍스처(Storage Textures)]], [[입자 시스템(Particle Systems)]] -- **Projects/Contexts:** [[오사카 엑스포 2025 호쿠사이 인스톨레이션(Hokusai installation)]] (Utsubo 스튜디오가 개발하여 98인치 4K 디스플레이에서 100만 개의 입자로 구성된 유체 시뮬레이션을 다중 인물 신체 추적과 함께 지연 없이 실시간으로 구현한 프로젝트 [11, 12]) +- **Related Topics:** [[WebGPU|WebGPU]], [[컴퓨트 셰이더(Compute Shaders)|컴퓨트 셰이더(Compute Shaders)]], [[스토리지 텍스처(Storage Textures)|스토리지 텍스처(Storage Textures)]], [[입자 시스템(Particle Systems)|입자 시스템(Particle Systems)]] +- **Projects/Contexts:** [[오사카 엑스포 2025 호쿠사이 인스톨레이션(Hokusai installation)|오사카 엑스포 2025 호쿠사이 인스톨레이션(Hokusai installation)]] (Utsubo 스튜디오가 개발하여 98인치 4K 디스플레이에서 100만 개의 입자로 구성된 유체 시뮬레이션을 다중 인물 신체 추적과 함께 지연 없이 실시간으로 구현한 프로젝트 [11, 12]) - **Contradictions/Notes:** 소스에 관련 정보가 부족합니다. (소스 내에서 물리 및 유체 시뮬레이션에 대한 상충되는 주장은 발견되지 않으며, 단순히 CPU 기반 처리와 GPU 컴퓨트 셰이더 기반 처리 간의 극적인 성능 차이와 이점만이 일관되게 강조되고 있습니다 [1, 4].) --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/실시간 물리 및 유체 시뮬레이션.md]] +- Raw Source: 00_Raw/2026-04-20/실시간 물리 및 유체 시뮬레이션.md --- diff --git a/01_Archive/2026-04-20/실시간 물리 시뮬레이션 동기화.md b/01_Archive/2026-04-20/실시간 물리 시뮬레이션 동기화.md index 4deb289a..6fe1b906 100644 --- a/01_Archive/2026-04-20/실시간 물리 시뮬레이션 동기화.md +++ b/01_Archive/2026-04-20/실시간 물리 시뮬레이션 동기화.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-6A6001 -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 실시간 물리 시뮬레이션 동기화" --- -# [[실시간 물리 시뮬레이션 동기화]] +# [[실시간 물리 시뮬레이션 동기화|실시간 물리 시뮬레이션 동기화]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - 실시간 물리 시뮬레이 ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/실시간 물리 시뮬레이션 동기화.md]] +- Raw Source: 00_Raw/2026-04-20/실시간 물리 시뮬레이션 동기화.md --- diff --git a/01_Archive/2026-04-20/실재감(Presence).md b/01_Archive/2026-04-20/실재감(Presence).md index 1103530e..419b6dfe 100644 --- a/01_Archive/2026-04-20/실재감(Presence).md +++ b/01_Archive/2026-04-20/실재감(Presence).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-D49B89 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 실재감(Presence)" --- -# [[실재감(Presence)]] +# [[실재감(Presence)|실재감(Presence)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 실재감(Presence)은 사용자가 가상 공간, 혼합 현실 또는 게임 환경을 현실 세계 대신 일시적으로 수용하여 실제로 그곳에 "존재한다(being there)"고 느끼는 심리적 상태 및 주관적 인식을 의미합니다 [1, 2]. 이는 성공적인 가상 현실 경험을 위한 핵심 기반이며, 몰입(Immersion) 및 참여(Engagement) 개념과 밀접하게 연관되어 사용자의 동기 부여와 성과에 영향을 미칩니다 [1, 3]. @@ -23,11 +23,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 실재감(Presence)" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[몰입(Immersion)]], [[참여(Engagement)]], [[인지 부하(Cognitive Load)]], [[가상 현실(Virtual Reality)]], [[혼합 현실(Mixed Reality)]], [[사회적 실재감(Social Presence)]] -- **Projects/Contexts:** [[게임 기반 학습(Game-based Learning)]], [[가상 현실 엑서게임(VR Exergaming)]] +- **Related Topics:** 몰입(Immersion), 참여(Engagement), 인지 부하(Cognitive Load), 가상 현실(Virtual Reality), 혼합 현실(Mixed Reality), 사회적 실재감(Social Presence) +- **Projects/Contexts:** 게임 기반 학습(Game-based Learning), 가상 현실 엑서게임(VR Exergaming) - **Contradictions/Notes:** 가상 실재감이 높아지면 참여도와 학습 성과가 향상된다는 긍정적인 측면이 있지만, 동시에 사용자의 인지 부하를 증가시킨다는 모순된 성격이 있습니다 [4, 6]. 따라서 가상 환경 설계 시 실재감을 떨어뜨리지 않으면서도 과도한 인지 부하를 줄이는 전략을 찾는 것이 주요한 연구 과제입니다 [8]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/실재감(Presence).md]] +- Raw Source: 00_Raw/2026-04-20/실재감(Presence).md --- diff --git a/01_Archive/2026-04-20/심리적 계약 (Psychological Contract).md b/01_Archive/2026-04-20/심리적 계약 (Psychological Contract).md index 5dc8183a..b3eae50a 100644 --- a/01_Archive/2026-04-20/심리적 계약 (Psychological Contract).md +++ b/01_Archive/2026-04-20/심리적 계약 (Psychological Contract).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-53F659 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 심리적 계약 (Psychological Contract)" --- -# [[심리적 계약 (Psychological Contract)]] +# [[심리적 계약 (Psychological Contract)|심리적 계약 (Psychological Contract)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - 심리적 계약 (Psychologica ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/심리적 계약 (Psychological Contract).md]] +- Raw Source: 00_Raw/2026-04-20/심리적 계약 (Psychological Contract).md --- diff --git a/01_Archive/2026-04-20/심리적 안전감 (Psychological Safety).md b/01_Archive/2026-04-20/심리적 안전감 (Psychological Safety).md index 05b208b6..4ba716b1 100644 --- a/01_Archive/2026-04-20/심리적 안전감 (Psychological Safety).md +++ b/01_Archive/2026-04-20/심리적 안전감 (Psychological Safety).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-6A93C9 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 심리적 안전감 (Psychological Safety)" --- -# [[심리적 안전감 (Psychological Safety)]] +# [[심리적 안전감 (Psychological Safety)|심리적 안전감 (Psychological Safety)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - 심리적 안전감 (Psycholog ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/심리적 안전감 (Psychological Safety).md]] +- Raw Source: 00_Raw/2026-04-20/심리적 안전감 (Psychological Safety).md --- diff --git a/01_Archive/2026-04-20/쓰기 장벽(Write Barrier).md b/01_Archive/2026-04-20/쓰기 장벽(Write Barrier).md index a78536c2..67c86a96 100644 --- a/01_Archive/2026-04-20/쓰기 장벽(Write Barrier).md +++ b/01_Archive/2026-04-20/쓰기 장벽(Write Barrier).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-30E929 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 쓰기 장벽(Write Barrier)" --- -# [[쓰기 장벽(Write Barrier)]] +# [[쓰기 장벽(Write Barrier)|쓰기 장벽(Write Barrier)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 쓰기 장벽(Write Barrier)은 가비지 컬렉션(GC) 환경에서 메모리 저장 작업 직후에 실행되어 특정한 포인터의 변경을 감지하고 기록하는 짧은 코드 조각입니다 [1, 2]. 주로 구세대(Old-space) 객체가 신세대(New-space) 객체를 참조하거나, 이미 스캔을 마친 객체가 스캔되지 않은 객체를 새롭게 참조할 때 이를 추적하는 데 사용됩니다 [1, 3]. 이를 통해 가비지 컬렉터가 힙 전체를 무의미하게 다시 스캔하는 비용을 줄이고, 스캐빈지(Scavenge) 및 점진적/동시성 마킹 과정을 효율적이고 안전하게 수행하도록 돕습니다 [3-5]. @@ -27,11 +27,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 쓰기 장벽(Write Barrier)" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Garbage Collection]], [[Generational Collection]], [[Incremental Marking]], [[Concurrent Marking]], [[Store Buffer]] -- **Projects/Contexts:** [[V8 JavaScript Engine]], [[IBM OpenJ9 GC]] +- **Related Topics:** [[Garbage Collection|Garbage Collection]], Generational Collection, [[Incremental Marking|Incremental Marking]], Concurrent Marking, Store Buffer +- **Projects/Contexts:** [[V8 JavaScript Engine|V8 JavaScript Engine]], IBM OpenJ9 GC - **Contradictions/Notes:** 소스에 따르면 쓰기 장벽은 객체 갱신마다 추가 연산을 수행하여 불가피한 CPU 오버헤드를 유발하지만 [9], 이는 무거운 읽기 장벽(Read Barrier)을 피하고 효율적인 가비지 컬렉션을 유지하기 위한 필수적이고 합리적인 트레이드오프입니다 [1]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/쓰기 장벽(Write Barrier).md]] +- Raw Source: 00_Raw/2026-04-20/쓰기 장벽(Write Barrier).md --- diff --git a/01_Archive/2026-04-20/아보(Bobo) 인형 실험.md b/01_Archive/2026-04-20/아보(Bobo) 인형 실험.md index 991d3c37..bc6d3d5e 100644 --- a/01_Archive/2026-04-20/아보(Bobo) 인형 실험.md +++ b/01_Archive/2026-04-20/아보(Bobo) 인형 실험.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-8F65AF -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 아보(Bobo) 인형 실험" --- -# [[아보(Bobo) 인형 실험]] +# [[아보(Bobo) 인형 실험|아보(Bobo) 인형 실험]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - 아보(Bobo) 인형 실험" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/아보(Bobo) 인형 실험.md]] +- Raw Source: 00_Raw/2026-04-20/아보(Bobo) 인형 실험.md --- diff --git a/01_Archive/2026-04-20/안구 운동 기능 (Oculomotor Functions).md b/01_Archive/2026-04-20/안구 운동 기능 (Oculomotor Functions).md index 80b88623..82e172b5 100644 --- a/01_Archive/2026-04-20/안구 운동 기능 (Oculomotor Functions).md +++ b/01_Archive/2026-04-20/안구 운동 기능 (Oculomotor Functions).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-9C8C53 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 안구 운동 기능 (Oculomotor Functions)" --- -# [[안구 운동 기능 (Oculomotor Functions)]] +# [[안구 운동 기능 (Oculomotor Functions)|안구 운동 기능 (Oculomotor Functions)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 안구 운동 기능(Oculomotor functions)은 수렴(vergence)과 조절(accommodation) 등을 포함하며, 인간이 깊이 단서(depth cues)를 정확하게 사용하고 대상에 명확한 초점을 맞추도록 돕는 필수적인 감각 메커니즘이다 [1, 2]. 가상현실(VR) 환경에서는 이러한 기능들이 자연스러운 피드백 루프에서 벗어나 분리(decoupled)될 수 있다 [2]. 이로 인해 발생하는 수렴-조절 불일치(vergence-accommodation conflicts)는 눈의 피로, 두통, 복시 등 가상현실 멀미와 관련된 안구 운동 증상을 유발하는 주요 원인이 된다 [1, 2]. @@ -23,11 +23,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 안구 운동 기능 (Oculomot - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[수렴과 조절(Vergence and Accommodation)]], [[수렴-조절 불일치(Vergence-Accommodation Conflicts)]], [[VR 멀미(VR Sickness)]], [[시뮬레이터 멀미 설문지(SSQ)]] -- **Projects/Contexts:** [[가상현실(VR) 엑서게임 후유증(Aftereffects) 연구]] +- **Related Topics:** 수렴과 조절(Vergence and Accommodation), 수렴-조절 불일치(Vergence-Accommodation Conflicts), [[VR 멀미 (VR Sickness)|VR 멀미(VR Sickness)]], [[시뮬레이터 멀미 설문지(SSQ)|시뮬레이터 멀미 설문지(SSQ)]] +- **Projects/Contexts:** 가상현실(VR) 엑서게임 후유증(Aftereffects) 연구 - **Contradictions/Notes:** 소스는 가상현실 노출이 즉각적으로 안구 운동 기능에 상당한 부하와 변화를 일으킨다는 점을 지적하지만, 이러한 안구 운동 변화는 노출 시간(10분 또는 50분)의 길이에 의해 통계적으로 유의미한 차이가 발생하지 않았으며 노출 후 40분이 지나면 정상으로 돌아온다고 설명합니다 [2, 4, 5]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/안구 운동 기능 (Oculomotor Functions).md]] +- Raw Source: 00_Raw/2026-04-20/안구 운동 기능 (Oculomotor Functions).md --- diff --git a/01_Archive/2026-04-20/안구 운동 기능(Oculomotor functions).md b/01_Archive/2026-04-20/안구 운동 기능(Oculomotor functions).md index bc5359bc..525cad23 100644 --- a/01_Archive/2026-04-20/안구 운동 기능(Oculomotor functions).md +++ b/01_Archive/2026-04-20/안구 운동 기능(Oculomotor functions).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-91A2A0 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 안구 운동 기능(Oculomotor functions)" --- -# [[안구 운동 기능(Oculomotor functions)]] +# [[안구 운동 기능(Oculomotor functions)|안구 운동 기능(Oculomotor functions)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 안구 운동 기능(Oculomotor functions)은 깊이 단서를 정확하게 사용하도록 돕는 이향운동(vergence) 및 조절(accommodation)과 같은 시각적 핵심 메커니즘을 포함한다 [1]. 또한, 사용자의 인지적 노력을 비침습적으로 평가하기 위해 측정되는 동공 반응, 시선 고정, 사카드(saccade) 등의 다양한 안구 움직임(oculometry)을 포괄하는 개념이다 [2-5]. @@ -31,11 +31,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 안구 운동 기능(Oculomoto - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[가상현실 멀미(VR Sickness)]], [[인지 부하(Cognitive Load)]], [[시뮬레이터 멀미 설문지(SSQ)]] -- **Projects/Contexts:** [[UX 리서치에서의 생체 신호 정량화]], [[e스포츠 선수의 인지 상태 및 피로도 모니터링]] +- **Related Topics:** [[가상현실 멀미(VR Sickness)|가상현실 멀미(VR Sickness)]], 인지 부하(Cognitive Load), [[시뮬레이터 멀미 설문지(SSQ)|시뮬레이터 멀미 설문지(SSQ)]] +- **Projects/Contexts:** UX 리서치에서의 생체 신호 정량화, e스포츠 선수의 인지 상태 및 피로도 모니터링 - **Contradictions/Notes:** 급성 인지 부하나 정신적 노력(Mental workload)이 가해지는 상황에서는 동공이 확장되지만, 작업이 2시간 이상 지속되는 등 인지적 피로(Cognitive fatigue)가 발생하면 반대로 동공이 수축(Pupil constriction)하여 인지 성과 저하와 상관관계를 보인다 [2, 4, 9]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/안구 운동 기능(Oculomotor functions).md]] +- Raw Source: 00_Raw/2026-04-20/안구 운동 기능(Oculomotor functions).md --- diff --git a/01_Archive/2026-04-20/안구 운동 증상(Oculomotor Symptoms).md b/01_Archive/2026-04-20/안구 운동 증상(Oculomotor Symptoms).md index 4cf7f42b..bb191de1 100644 --- a/01_Archive/2026-04-20/안구 운동 증상(Oculomotor Symptoms).md +++ b/01_Archive/2026-04-20/안구 운동 증상(Oculomotor Symptoms).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-064759 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 안구 운동 증상(Oculomotor Symptoms)" --- -# [[안구 운동 증상(Oculomotor Symptoms)]] +# [[안구 운동 증상(Oculomotor Symptoms)|안구 운동 증상(Oculomotor Symptoms)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 안구 운동 증상(Oculomotor Symptoms)은 주로 머리 착용 디스플레이(HMD)를 사용하는 가상현실(VR)에 노출될 때 경험할 수 있는 멀미 부작용 중 하나입니다 [1]. 시뮬레이터 멀미 설문지(SSQ)의 3대 하위 항목 중 하나로, 눈의 긴장, 시각적 피로, 초점의 어려움과 관련된 증상을 포함합니다 [2]. HMD 사용 시 발생하는 폭주-조절 불일치(vergence-accommodation conflict)가 이러한 증상을 유발하는 주된 원인으로 작용합니다 [1]. @@ -23,11 +23,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 안구 운동 증상(Oculomoto - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[가상현실 멀미(VR Sickness)]], [[폭주-조절 불일치(Vergence-Accommodation Conflict)]], [[시뮬레이터 멀미 설문지(Simulator Sickness Questionnaire)]] -- **Projects/Contexts:** [[가상현실 엑서게임 후유증 연구(VR Exergaming Aftereffects Study)]] +- **Related Topics:** [[가상현실 멀미(VR Sickness)|가상현실 멀미(VR Sickness)]], [[폭주-조절 불일치(Vergence-accommodation conflict)|폭주-조절 불일치(Vergence-Accommodation Conflict)]], [[시뮬레이터 멀미 설문지(Simulator Sickness Questionnaire)|시뮬레이터 멀미 설문지(Simulator Sickness Questionnaire)]] +- **Projects/Contexts:** [[가상현실 엑서게임 후유증 연구(VR Exergaming Aftereffects Study)|가상현실 엑서게임 후유증 연구(VR Exergaming Aftereffects Study)]] - **Contradictions/Notes:** 소스에 관련 정보가 부족합니다. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/안구 운동 증상(Oculomotor Symptoms).md]] +- Raw Source: 00_Raw/2026-04-20/안구 운동 증상(Oculomotor Symptoms).md --- diff --git a/01_Archive/2026-04-20/안전한 TypeScript 데이터 모델링 및 설정 관리 구축.md b/01_Archive/2026-04-20/안전한 TypeScript 데이터 모델링 및 설정 관리 구축.md index 211a7b49..85fd4ea2 100644 --- a/01_Archive/2026-04-20/안전한 TypeScript 데이터 모델링 및 설정 관리 구축.md +++ b/01_Archive/2026-04-20/안전한 TypeScript 데이터 모델링 및 설정 관리 구축.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-9DB95B -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 안전한 TypeScript 데이터 모델링 및 설정 관리 구축" --- -# [[안전한 TypeScript 데이터 모델링 및 설정 관리 구축]] +# [[안전한 TypeScript 데이터 모델링 및 설정 관리 구축|안전한 TypeScript 데이터 모델링 및 설정 관리 구축]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 이 주제는 TypeScript의 강력한 정적 타입 시스템을 활용하여 런타임 오류를 예방하고 애플리케이션의 데이터 무결성을 보장하는 데이터 모델링 및 설정(Configuration) 객체 관리 방법론입니다. 브랜디드 타입과 식별 가능한 유니온을 통해 비즈니스 로직에 필요한 명확한 도메인 모델을 구축하고, `readonly` 수식어 및 `satisfies` 연산자를 활용하여 불변하고 구조적으로 정확한 설정 상태를 안전하게 관리하는 설계 패턴을 포함합니다. @@ -28,13 +28,13 @@ github_commit: "[P-Reinforce] Continuous Worker - 안전한 TypeScript 데이터 - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[구조적 타이핑 (Structural Typing)]], [[식별 가능한 유니온 (Discriminated Unions)]], [[브랜디드 타입 (Branded Types)]], [[불변성 (Immutability)]], [[satisfies 연산자]] -- **Projects/Contexts:** [[API 응답 및 상태 머신 모델링]], [[불변 설정 객체(Configuration Object) 관리 및 타입 검증]] +- **Related Topics:** [[구조적 타이핑 (Structural Typing)|구조적 타이핑 (Structural Typing)]], [[식별 가능한 유니온 (Discriminated Unions)|식별 가능한 유니온 (Discriminated Unions)]], [[브랜디드 타입 (Branded Types)|브랜디드 타입 (Branded Types)]], [[불변성 (Immutability)|불변성 (Immutability)]], [[satisfies 연산자|satisfies 연산자]] +- **Projects/Contexts:** API 응답 및 상태 머신 모델링, 불변 설정 객체(Configuration Object) 관리 및 타입 검증 - **Contradictions/Notes:** - `any` 타입을 사용하면 타입 시스템의 이점을 잃고 런타임 에러에 취약해지므로 금지해야 하며, 대신 데이터가 불확실할 때는 `unknown` 타입을 사용하고 타입 가드(Type Guard)를 거쳐 안전하게 사용해야 합니다 [28, 29]. - 객체 확장에 있어서 교집합 타입(Intersection, `&`)보다는 `Interface extends`를 사용하는 것이 TypeScript 컴파일러의 캐싱을 활용해 성능상 유리하고 더 직관적인 오류 메시지를 제공합니다 [30-32]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/안전한 TypeScript 데이터 모델링 및 설정 관리 구축.md]] +- Raw Source: 00_Raw/2026-04-20/안전한 TypeScript 데이터 모델링 및 설정 관리 구축.md --- diff --git a/01_Archive/2026-04-20/안전한 소프트웨어 개발 수명주기(SSDLC).md b/01_Archive/2026-04-20/안전한 소프트웨어 개발 수명주기(SSDLC).md index 7c00ebb9..8231f16b 100644 --- a/01_Archive/2026-04-20/안전한 소프트웨어 개발 수명주기(SSDLC).md +++ b/01_Archive/2026-04-20/안전한 소프트웨어 개발 수명주기(SSDLC).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-8F44F9 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 안전한 소프트웨어 개발 수명주기(SSDLC)" --- -# [[안전한 소프트웨어 개발 수명주기(SSDLC)]] +# [[안전한 소프트웨어 개발 수명주기(SSDLC)|안전한 소프트웨어 개발 수명주기(SSDLC)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 안전한 소프트웨어 개발 수명주기(SSDLC)는 개발 초기 단계부터 보안을 통합하여 취약점을 방지하고 소프트웨어의 전반적인 품질을 향상시키는 프로세스입니다 [1, 2]. 이 접근 방식은 정적 분석(SAST)과 실시간 코드 검사 도구를 개발 워크플로우에 내장하여 결함을 조기에 발견하고 수정하는 '시프트 레프트(Shift-Left)' 전략을 기반으로 합니다 [1, 3]. 결과적으로 조직은 대규모 개발 환경에서도 안전하고 고품질의 코드를 지속적으로 제공하고 거버넌스를 유지할 수 있습니다 [2, 4]. @@ -23,11 +23,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 안전한 소프트웨어 개 - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[SAST(정적 애플리케이션 보안 테스트)]], [[시프트 레프트(Shift-Left)]], [[DevSecOps]], [[코드 리뷰(Code Review)]] -- **Projects/Contexts:** [[CI/CD 파이프라인 통합]], [[NIST SSDF(안전한 소프트웨어 개발 프레임워크)]] +- **Related Topics:** [[SAST (정적 애플리케이션 보안 테스트)|SAST(정적 애플리케이션 보안 테스트)]], [[시프트 레프트(Shift-Left)|시프트 레프트(Shift-Left)]], [[DevSecOps|DevSecOps]], [[코드 리뷰(Code Review)|코드 리뷰(Code Review)]] +- **Projects/Contexts:** CI/CD 파이프라인 통합, NIST SSDF(안전한 소프트웨어 개발 프레임워크) - **Contradictions/Notes:** 소스에 따르면 안전한 개발 수명주기를 위해 SAST 같은 자동화 보안 스캔 도구의 통합이 필수적이지만, 자동화 도구는 비즈니스 로직이나 맥락(Context)을 이해하지 못해 한계가 존재합니다 [8, 9]. 따라서 자동화된 도구로 기본적인 취약점을 빠르게 잡고, 인간의 통찰력이 필요한 아키텍처 및 논리 결함은 수동 코드 리뷰로 해결하는 하이브리드 접근 방식이 필수적이라고 권장합니다 [6, 8, 10]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/안전한 소프트웨어 개발 수명주기(SSDLC).md]] +- Raw Source: 00_Raw/2026-04-20/안전한 소프트웨어 개발 수명주기(SSDLC).md --- diff --git a/01_Archive/2026-04-20/알 수 없는 외부 데이터 검증 (unknown types).md b/01_Archive/2026-04-20/알 수 없는 외부 데이터 검증 (unknown types).md index faf0ed4d..8eddacb0 100644 --- a/01_Archive/2026-04-20/알 수 없는 외부 데이터 검증 (unknown types).md +++ b/01_Archive/2026-04-20/알 수 없는 외부 데이터 검증 (unknown types).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-629DFB -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 알 수 없는 외부 데이터 검증 (unknown types)" --- -# [[알 수 없는 외부 데이터 검증 (unknown types)]] +# [[알 수 없는 외부 데이터 검증 (unknown types)|알 수 없는 외부 데이터 검증 (unknown types)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > TypeScript에서 알 수 없는 외부 데이터는 모든 JavaScript 값을 포함하는 `unknown` 타입으로 다루어집니다 [1, 2]. API 응답이나 JSON 파싱, 에러 핸들링처럼 데이터의 형태가 런타임에 불분명할 때 `any` 타입을 대신해 사용하는 안전한 대안입니다 [2]. 시스템 경계에서 타입 가드(Type Guard)나 파서를 통해 이 데이터를 명확한 타입으로 검증하고 좁혀야만 안전하게 사용할 수 있습니다 [2-4]. @@ -27,11 +27,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 알 수 없는 외부 데이 - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Type Guard]], [[Parse, don't validate]], [[any 타입]], [[Zod]] +- **Related Topics:** Type Guard, [[Parse, don't validate|Parse, don't validate]], any 타입, [[Zod|Zod]] - **Projects/Contexts:** 외부 API 응답 처리, JSON 데이터 파싱, 에러 처리 등 런타임에 데이터 타입이 확정되지 않은 상황 [2], Zod 등의 런타임 검증 라이브러리를 이용한 데이터 스키마 검사 [8, 11]. - **Contradictions/Notes:** `any` 타입은 타입 검사를 회피하게 해 주어 TypeScript의 이점을 상실하게 만드는 반면, `unknown` 타입은 어떤 값이든 받을 수 있으면서도 사용 전 타입 확인을 엄격하게 강제하므로 외부 데이터 처리에 훨씬 더 권장되는 방식입니다 [2, 5, 6]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/알 수 없는 외부 데이터 검증 (unknown types).md]] +- Raw Source: 00_Raw/2026-04-20/알 수 없는 외부 데이터 검증 (unknown types).md --- diff --git a/01_Archive/2026-04-20/애그리거트 (Aggregates).md b/01_Archive/2026-04-20/애그리거트 (Aggregates).md index 53abda71..65206856 100644 --- a/01_Archive/2026-04-20/애그리거트 (Aggregates).md +++ b/01_Archive/2026-04-20/애그리거트 (Aggregates).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-8D448D -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 애그리거트 (Aggregates)" --- -# [[애그리거트 (Aggregates)]] +# [[애그리거트 (Aggregates)|애그리거트 (Aggregates)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 애그리거트(Aggregates)는 도메인 주도 설계(Domain-Driven Design, DDD)에서 단일 단위로 취급될 수 있는 도메인 객체들의 군집을 의미합니다 [1]. 비즈니스 도메인을 모델링할 때 트랜잭션 관리를 단순화하고, 해당 군집 내 객체들의 일관성을 보장하는 핵심적인 역할을 수행합니다 [1]. @@ -22,11 +22,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 애그리거트 (Aggregates)" - **정책 변화:** AI 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Domain-Driven Design (DDD)]], [[Event Storming]], [[Domain Objects]] -- **Projects/Contexts:** [[비즈니스 도메인 모델링 (Business Domain Modeling)]] +- **Related Topics:** [[Domain-Driven Design (DDD)|Domain-Driven Design (DDD)]], [[Event Storming|Event Storming]], [[Domain Objects|Domain Objects]] +- **Projects/Contexts:** [[비즈니스 도메인 모델링 (Business Domain Modeling)|비즈니스 도메인 모델링 (Business Domain Modeling)]] - **Contradictions/Notes:** 소스에 관련 정보가 제한적이며, 애그리거트의 구체적인 구현 방식이나 상반된 주장에 대한 정보는 소스에 부족합니다. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/애그리거트 (Aggregates).md]] +- Raw Source: 00_Raw/2026-04-20/애그리거트 (Aggregates).md --- diff --git a/01_Archive/2026-04-20/애자일 방법론 (Agile Methodology).md b/01_Archive/2026-04-20/애자일 방법론 (Agile Methodology).md index 5012acdd..b2796ed4 100644 --- a/01_Archive/2026-04-20/애자일 방법론 (Agile Methodology).md +++ b/01_Archive/2026-04-20/애자일 방법론 (Agile Methodology).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-3E4349 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 애자일 방법론 (Agile Methodology)" --- -# [[애자일 방법론 (Agile Methodology)]] +# [[애자일 방법론 (Agile Methodology)|애자일 방법론 (Agile Methodology)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - 애자일 방법론 (Agile Met ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/애자일 방법론 (Agile Methodology).md]] +- Raw Source: 00_Raw/2026-04-20/애자일 방법론 (Agile Methodology).md --- diff --git a/01_Archive/2026-04-20/약한 타입 검사(Weak Type Detection).md b/01_Archive/2026-04-20/약한 타입 검사(Weak Type Detection).md index 0a34bfbf..9eaad08f 100644 --- a/01_Archive/2026-04-20/약한 타입 검사(Weak Type Detection).md +++ b/01_Archive/2026-04-20/약한 타입 검사(Weak Type Detection).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-487E76 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 약한 타입 검사(Weak Type Detection)" --- -# [[약한 타입 검사(Weak Type Detection)]] +# [[약한 타입 검사(Weak Type Detection)|약한 타입 검사(Weak Type Detection)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 약한 타입 검사(Weak Type Detection)는 TypeScript에서 모든 속성이 선택적(optional)으로 구성된 '약한 타입(weak type)'에 대해 적용되는 특수한 타입 검사 메커니즘입니다 [1]. 이 검사는 할당하려는 객체가 대상이 되는 약한 타입과 공통된 속성을 단 하나도 가지고 있지 않을 때 타입 오류를 발생시킵니다 [1, 2]. 이는 약한 타입이 가진 구조적인 지나친 유연성을 보완하고, 개발자의 의도치 않은 객체 할당 실수를 방지하는 역할을 합니다 [1, 2]. @@ -22,11 +22,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 약한 타입 검사(Weak Type - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[잉여 속성 검사(Excess Property Checking)]], [[선택적 속성(Optional Properties)]], [[Partial 유틸리티 타입]] -- **Projects/Contexts:** [[TypeScript의 구조적 타이핑(Structural Typing)]] +- **Related Topics:** 잉여 속성 검사(Excess Property Checking), 선택적 속성(Optional Properties), Partial 유틸리티 타입 +- **Projects/Contexts:** TypeScript의 구조적 타이핑(Structural Typing) - **Contradictions/Notes:** 잉여 속성이 존재하더라도 우회 할당 시 대상 타입이 약한 타입이고 공통 속성이 최소 한 개 이상 존재한다면, TypeScript는 이를 유효한 것으로 간주하여 에러를 발생시키지 않는다는 점에 주의해야 합니다 [2, 4]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/약한 타입 검사(Weak Type Detection).md]] +- Raw Source: 00_Raw/2026-04-20/약한 타입 검사(Weak Type Detection).md --- diff --git a/01_Archive/2026-04-20/약한 타입 탐지 (Weak Type Detection).md b/01_Archive/2026-04-20/약한 타입 탐지 (Weak Type Detection).md index 125b4632..a955c447 100644 --- a/01_Archive/2026-04-20/약한 타입 탐지 (Weak Type Detection).md +++ b/01_Archive/2026-04-20/약한 타입 탐지 (Weak Type Detection).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-3F076E -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 약한 타입 탐지 (Weak Type Detection)" --- -# [[약한 타입 탐지 (Weak Type Detection)]] +# [[약한 타입 탐지 (Weak Type Detection)|약한 타입 탐지 (Weak Type Detection)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 약한 타입 탐지(Weak Type Detection)는 TypeScript에서 오직 선택적(optional) 속성만으로 구성된 '약한 타입'에 객체를 할당할 때 발생하는 특별한 타입 검사 과정입니다 [1, 2]. 할당하려는 객체가 대상 약한 타입과 겹치는 공통 속성을 단 하나도 가지고 있지 않을 경우 컴파일 에러를 발생시킵니다 [1, 3]. 이를 통해 지나치게 유연한 타입 구조에서 발생할 수 있는 잠재적인 의도치 않은 할당 오류를 방지합니다 [2]. @@ -22,11 +22,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 약한 타입 탐지 (Weak Typ - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[초과 속성 검사 (Excess Property Checking)]], [[선택적 속성 (Optional Properties)]], [[Partial 유틸리티 타입 (Partial Utility Type)]] -- **Projects/Contexts:** [[TypeScript의 객체 할당 및 타입 검사 (TypeScript Object Assignment and Type Checking)]] +- **Related Topics:** [[초과 속성 검사 (Excess Property Checking)|초과 속성 검사 (Excess Property Checking)]], 선택적 속성 (Optional Properties), Partial 유틸리티 타입 (Partial Utility Type) +- **Projects/Contexts:** TypeScript의 객체 할당 및 타입 검사 (TypeScript Object Assignment and Type Checking) - **Contradictions/Notes:** 객체 리터럴을 직접 할당할 때 동작하는 초과 속성 검사(Excess Property Checking)와 달리, 약한 타입 탐지는 변수를 통해 간접적으로 할당할 때 두 객체 간에 공통 속성이 아예 없을 때 예외적으로 발생하는 방어 기제입니다 [1, 3, 4]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/약한 타입 탐지 (Weak Type Detection).md]] +- Raw Source: 00_Raw/2026-04-20/약한 타입 탐지 (Weak Type Detection).md --- diff --git a/01_Archive/2026-04-20/양가감정(Ambivalence).md b/01_Archive/2026-04-20/양가감정(Ambivalence).md index 7838c22e..a981b13f 100644 --- a/01_Archive/2026-04-20/양가감정(Ambivalence).md +++ b/01_Archive/2026-04-20/양가감정(Ambivalence).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-0A598A -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 양가감정(Ambivalence)" --- -# [[양가감정(Ambivalence)]] +# [[양가감정(Ambivalence)|양가감정(Ambivalence)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - 양가감정(Ambivalence)" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/양가감정(Ambivalence).md]] +- Raw Source: 00_Raw/2026-04-20/양가감정(Ambivalence).md --- diff --git a/01_Archive/2026-04-20/양자화 (Quantization).md b/01_Archive/2026-04-20/양자화 (Quantization).md index f41cfe22..f90fc8d5 100644 --- a/01_Archive/2026-04-20/양자화 (Quantization).md +++ b/01_Archive/2026-04-20/양자화 (Quantization).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-7321F3 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 양자화 (Quantization)" --- -# [[양자화 (Quantization)]] +# [[양자화 (Quantization)|양자화 (Quantization)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - 양자화 (Quantization)" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/양자화 (Quantization).md]] +- Raw Source: 00_Raw/2026-04-20/양자화 (Quantization).md --- diff --git a/01_Archive/2026-04-20/에듀테크 기반 게이미피케이션 전략.md b/01_Archive/2026-04-20/에듀테크 기반 게이미피케이션 전략.md index ecf1f266..cc23c678 100644 --- a/01_Archive/2026-04-20/에듀테크 기반 게이미피케이션 전략.md +++ b/01_Archive/2026-04-20/에듀테크 기반 게이미피케이션 전략.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-4FA22A -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 에듀테크 기반 게이미피케이션 전략" --- -# [[에듀테크 기반 게이미피케이션 전략]] +# [[에듀테크 기반 게이미피케이션 전략|에듀테크 기반 게이미피케이션 전략]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - 에듀테크 기반 게이미 ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/에듀테크 기반 게이미피케이션 전략.md]] +- Raw Source: 00_Raw/2026-04-20/에듀테크 기반 게이미피케이션 전략.md --- diff --git a/01_Archive/2026-04-20/에르고딕 문학(Ergodic Literature).md b/01_Archive/2026-04-20/에르고딕 문학(Ergodic Literature).md index 1243cfb4..8cdcc05e 100644 --- a/01_Archive/2026-04-20/에르고딕 문학(Ergodic Literature).md +++ b/01_Archive/2026-04-20/에르고딕 문학(Ergodic Literature).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-A5FDD2 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 에르고딕 문학(Ergodic Literature)" --- -# [[에르고딕 문학(Ergodic Literature)]] +# [[에르고딕 문학(Ergodic Literature)|에르고딕 문학(Ergodic Literature)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - 에르고딕 문학(Ergodic Li ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/에르고딕 문학(Ergodic Literature).md]] +- Raw Source: 00_Raw/2026-04-20/에르고딕 문학(Ergodic Literature).md --- diff --git a/01_Archive/2026-04-20/에일리어싱 (Aliasing).md b/01_Archive/2026-04-20/에일리어싱 (Aliasing).md index 0719b9ae..7c1e2d4d 100644 --- a/01_Archive/2026-04-20/에일리어싱 (Aliasing).md +++ b/01_Archive/2026-04-20/에일리어싱 (Aliasing).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-E5B908 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 에일리어싱 (Aliasing)" --- -# [[에일리어싱 (Aliasing)]] +# [[에일리어싱 (Aliasing)|에일리어싱 (Aliasing)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 에일리어싱(Aliasing)은 프로그래밍에서 기존 데이터 타입에 새로운 이름을 부여하거나(타입 에일리어싱), 동일한 데이터를 여러 참조 변수가 가리키게 되는 현상(참조 에일리어싱)을 의미합니다 [1, 2]. TypeScript에서 타입 에일리어싱은 기존 타입과 상호 호환되는 서술적인 이름표 역할을 하며, 참조 에일리어싱은 `readonly` 데이터가 가변(mutable) 참조로 전달될 때 의도치 않은 데이터 변형(Mutation)을 일으키는 주요 원인이 되기도 합니다 [1-3]. @@ -27,11 +27,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 에일리어싱 (Aliasing)" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Type Alias (타입 별칭)]], [[Readonly]], [[Opaque Types (불투명 타입)]] -- **Projects/Contexts:** [[TypeScript의 불변성(Immutability) 관리]], [[인터페이스와 타입 별칭 비교(Interface vs Type)]] +- **Related Topics:** Type Alias (타입 별칭), [[Readonly 유틸리티 타입|Readonly]], Opaque Types (불투명 타입) +- **Projects/Contexts:** TypeScript의 불변성(Immutability) 관리, 인터페이스와 타입 별칭 비교(Interface vs Type) - **Contradictions/Notes:** TypeScript의 `readonly`는 컴파일 타임에 불변성을 제공하는 강력한 도구이지만, 에일리어싱을 통해 데이터가 가변 매개변수로 전달될 경우에는 컴파일러가 이를 잡아내지 못하여 데이터가 수정될 수 있다는(얕은 불변성) 근본적인 한계를 지닙니다 [2, 6]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/에일리어싱 (Aliasing).md]] +- Raw Source: 00_Raw/2026-04-20/에일리어싱 (Aliasing).md --- diff --git a/01_Archive/2026-04-20/엑서게임(Exergaming).md b/01_Archive/2026-04-20/엑서게임(Exergaming).md index dd3e2dba..5e15b689 100644 --- a/01_Archive/2026-04-20/엑서게임(Exergaming).md +++ b/01_Archive/2026-04-20/엑서게임(Exergaming).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-F5CD6C -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 엑서게임(Exergaming)" --- -# [[엑서게임(Exergaming)]] +# [[엑서게임(Exergaming)|엑서게임(Exergaming)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 엑서게임(Exergaming)은 **운동(Exercise)과 게임 플레이(Gameplay)를 가상 환경에 결합하여 사용자의 신체 활동을 촉진하는 게임**이다 [1]. 이는 아동, 청소년, 성인 모두의 좌식 생활 습관(sedentary behavior)을 개선하기 위해 활용되며 달리기나 에어로빅과 비견되는 건강상의 이점을 제공한다 [1]. 특히 게임에 대한 몰입감을 통해 **사용자가 육체적 피로를 잊게 만들고 지속적인 운동 동기를 부여**하는 것이 가장 큰 특징이다 [2]. @@ -25,11 +25,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 엑서게임(Exergaming)" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Flow State]], [[Virtual Reality (VR) Sickness]], [[Sedentary Behavior]] -- **Projects/Contexts:** [[비트 세이버(Beat Saber) 시각 및 인지 후유증 연구]] +- **Related Topics:** [[Flow State|Flow State]], Virtual Reality (VR) Sickness, Sedentary Behavior +- **Projects/Contexts:** 비트 세이버(Beat Saber) 시각 및 인지 후유증 연구 - **Contradictions/Notes:** 소스에 따르면, HMD를 사용하는 VR 엑서게임은 대형 스크린 기반의 엑서게임보다 몰입도가 높지만, 동시에 더 높은 수준의 멀미(VR Sickness)를 유발할 위험이 있다는 양면성(trade-off)을 지니고 있습니다 [4]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/엑서게임(Exergaming).md]] +- Raw Source: 00_Raw/2026-04-20/엑서게임(Exergaming).md --- diff --git a/01_Archive/2026-04-20/엔터프라이즈 소프트웨어 개발.md b/01_Archive/2026-04-20/엔터프라이즈 소프트웨어 개발.md index a63b58d0..541f5f86 100644 --- a/01_Archive/2026-04-20/엔터프라이즈 소프트웨어 개발.md +++ b/01_Archive/2026-04-20/엔터프라이즈 소프트웨어 개발.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-117851 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 엔터프라이즈 소프트웨어 개발" --- -# [[엔터프라이즈 소프트웨어 개발]] +# [[엔터프라이즈 소프트웨어 개발|엔터프라이즈 소프트웨어 개발]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 엔터프라이즈 소프트웨어 개발은 기업의 복잡한 비즈니스 요구사항을 충족시키기 위해 확장 가능하고, 유지보수가 쉬우며, 복원력 있는 대규모 시스템을 구축하는 과정입니다 [1, 2]. 이를 위해 관심사의 분리, 계층형 구조, 마이크로서비스 아키텍처와 같은 소프트웨어 아키텍처 모범 사례를 적용하여 기술 부채를 최소화하고 민첩성을 극대화합니다 [1, 3, 4]. 현대의 엔터프라이즈 시스템은 모놀리식 구조의 한계를 극복하고, 독립적인 개발과 배포가 가능한 모듈형 및 클라우드 네이티브 생태계로 진화하고 있습니다 [4, 5]. @@ -33,11 +33,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 엔터프라이즈 소프트 - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[소프트웨어 아키텍처 모범 사례]], [[마이크로서비스 아키텍처]], [[클린 아키텍처]], [[도메인 주도 설계 (DDD)]], [[관심사의 분리 (Separation of Concerns)]] -- **Projects/Contexts:** [[넷플릭스(Netflix)의 마이크로서비스 및 Cosmos 플랫폼 전환 사례]], [[스포티파이(Spotify)의 스쿼드 모델 및 마이크로 프론트엔드 아키텍처 도입]] +- **Related Topics:** 소프트웨어 아키텍처 모범 사례, [[마이크로서비스 아키텍처|마이크로서비스 아키텍처]], [[클린 아키텍처|클린 아키텍처]], [[도메인 주도 설계 (DDD)|도메인 주도 설계 (DDD)]], [[관심사의 분리 (Separation of Concerns)|관심사의 분리 (Separation of Concerns)]] +- **Projects/Contexts:** 넷플릭스(Netflix)의 마이크로서비스 및 Cosmos 플랫폼 전환 사례, 스포티파이(Spotify)의 스쿼드 모델 및 마이크로 프론트엔드 아키텍처 도입 - **Contradictions/Notes:** 복잡성을 완벽하게 제어하기 위한 고도의 아키텍처 경계 구축이나 마이크로서비스로의 분할이 항상 정답은 아닙니다. 초기 팀 규모가 작거나 단순한 요구사항일 경우 모놀리식 구조가 효율적일 수 있으며, 미래를 위해 과도하게 완벽한 경계를 만드는 것은 YAGNI(You Aren't Gonna Need It) 원칙에 어긋나는 오버 엔지니어링이 될 수 있으므로 비용과 이점을 신중하게 따져 부분적 경계를 활용하는 것이 권장됩니다 [28-31]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/엔터프라이즈 소프트웨어 개발.md]] +- Raw Source: 00_Raw/2026-04-20/엔터프라이즈 소프트웨어 개발.md --- diff --git a/01_Archive/2026-04-20/엔터프라이즈 소프트웨어 시스템 설계.md b/01_Archive/2026-04-20/엔터프라이즈 소프트웨어 시스템 설계.md index bc860094..f1b8dd04 100644 --- a/01_Archive/2026-04-20/엔터프라이즈 소프트웨어 시스템 설계.md +++ b/01_Archive/2026-04-20/엔터프라이즈 소프트웨어 시스템 설계.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-CB60AE -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 엔터프라이즈 소프트웨어 시스템 설계" --- -# [[엔터프라이즈 소프트웨어 시스템 설계]] +# [[엔터프라이즈 소프트웨어 시스템 설계|엔터프라이즈 소프트웨어 시스템 설계]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 엔터프라이즈 소프트웨어 시스템 설계는 비즈니스 요구사항을 충족하고 시간이 지남에 따라 시스템이 확장 및 유지보수될 수 있도록 돕는 견고하고 탄력적인 소프트웨어 기반의 청사진입니다 [1, 2]. 이는 관심사의 분리(SoC), 모듈화, 클린 아키텍처 등의 핵심 원칙을 통해 복잡한 시스템을 관리 가능한 단위로 분할하여 기술 부채를 최소화합니다 [1, 3, 4]. 결과적으로 잘 설계된 아키텍처는 개발 속도를 높이고, 독립적인 테스트를 가능하게 하며, 급변하는 비즈니스 환경에 시스템이 유연하게 적응할 수 있도록 지원합니다 [1, 5, 6]. @@ -35,8 +35,8 @@ github_commit: "[P-Reinforce] Continuous Worker - 엔터프라이즈 소프트 - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[관심사의 분리 (Separation of Concerns)]], [[클린 아키텍처 (Clean Architecture)]], [[마이크로서비스 아키텍처]], [[도메인 주도 설계 (DDD)]], [[SOLID 원칙]] -- **Projects/Contexts:** [[넷플릭스 코스모스 플랫폼 (Netflix Cosmos Platform)]], [[넷플릭스 마이크로서비스 마이그레이션]], [[스포티파이 마이크로 프론트엔드 (Spotify Micro Frontends)]] +- **Related Topics:** [[관심사의 분리 (Separation of Concerns)|관심사의 분리 (Separation of Concerns)]], [[클린 아키텍처 (Clean Architecture)|클린 아키텍처 (Clean Architecture)]], [[마이크로서비스 아키텍처|마이크로서비스 아키텍처]], [[도메인 주도 설계 (DDD)|도메인 주도 설계 (DDD)]], [[SOLID 원칙|SOLID 원칙]] +- **Projects/Contexts:** [[넷플릭스 코스모스 플랫폼 (Netflix Cosmos Platform)|넷플릭스 코스모스 플랫폼 (Netflix Cosmos Platform)]], 넷플릭스 마이크로서비스 마이그레이션, 스포티파이 마이크로 프론트엔드 (Spotify Micro Frontends) - **Contradictions/Notes:** - **아키텍처 도입의 트레이드오프:** 마이크로서비스는 독립적인 배포와 혁신을 돕지만, 서비스 간 분산 통신 구현, 여러 서비스에 걸친 요청 처리의 어려움, 메모리 사용량 증가 등 새로운 운영 및 개발 복잡성을 수반합니다 [41-43]. - **관심사 분리의 부작용:** 시스템의 결합도를 낮추고 모듈성을 높이기 위한 관심사의 분리도 지나치게 미세하게 적용할 경우, 성능 오버헤드, 함수 호출 깊이 증가, 조율을 위한 과도한 인디렉션(indirection) 발생 등 오버엔지니어링으로 이어져 오히려 가독성과 디버깅을 어렵게 만들 수 있습니다 [44-46]. @@ -44,5 +44,5 @@ github_commit: "[P-Reinforce] Continuous Worker - 엔터프라이즈 소프트 --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/엔터프라이즈 소프트웨어 시스템 설계.md]] +- Raw Source: 00_Raw/2026-04-20/엔터프라이즈 소프트웨어 시스템 설계.md --- diff --git a/01_Archive/2026-04-20/엔터프라이즈 애플리케이션 및 점진적 리팩토링.md b/01_Archive/2026-04-20/엔터프라이즈 애플리케이션 및 점진적 리팩토링.md index 39dcf413..52b09345 100644 --- a/01_Archive/2026-04-20/엔터프라이즈 애플리케이션 및 점진적 리팩토링.md +++ b/01_Archive/2026-04-20/엔터프라이즈 애플리케이션 및 점진적 리팩토링.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-D8EB32 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 엔터프라이즈 애플리케이션 및 점진적 리팩토링" --- -# [[엔터프라이즈 애플리케이션 및 점진적 리팩토링]] +# [[엔터프라이즈 애플리케이션 및 점진적 리팩토링|엔터프라이즈 애플리케이션 및 점진적 리팩토링]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 엔터프라이즈 애플리케이션은 종종 거대한 레거시 코드로 이루어져 있어 전체를 한 번에 재작성하는 것이 위험하고 비효율적입니다 [1, 2]. 따라서 전체 시스템을 한 번에 리팩토링하는 대신 새로운 기능이나 모듈 개발 시 설계 원칙을 서서히 적용하는 점진적 리팩토링(Incremental Refactoring)이 필수적입니다 [1, 3]. 이를 통해 기업은 기존 시스템의 안정성을 유지하면서 복잡한 기술 부채를 관리하고 시스템을 현대화할 수 있습니다 [2, 4]. @@ -23,11 +23,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 엔터프라이즈 애플리 - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[SOLID Principles]], [[Clean Architecture]], [[Strangler Fig Pattern]], [[Micro Frontends]] -- **Projects/Contexts:** [[넷플릭스의 레거시 시스템(Reloaded) 마이그레이션 프로젝트]], [[넷플릭스 대시보드 레거시 현대화]] +- **Related Topics:** [[SOLID Principles|SOLID Principles]], [[Clean Architecture|Clean Architecture]], [[스트랭글러 피그 패턴(Strangler Fig Pattern)|Strangler Fig Pattern]], [[마이크로 프론트엔드 (Micro Frontends)|Micro Frontends]] +- **Projects/Contexts:** 넷플릭스의 레거시 시스템(Reloaded) 마이그레이션 프로젝트, 넷플릭스 대시보드 레거시 현대화 - **Contradictions/Notes:** 소스에 관련 정보가 부족합니다. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/엔터프라이즈 애플리케이션 및 점진적 리팩토링.md]] +- Raw Source: 00_Raw/2026-04-20/엔터프라이즈 애플리케이션 및 점진적 리팩토링.md --- diff --git a/01_Archive/2026-04-20/엔터프라이즈 애플리케이션 설계.md b/01_Archive/2026-04-20/엔터프라이즈 애플리케이션 설계.md index a2a21616..11834150 100644 --- a/01_Archive/2026-04-20/엔터프라이즈 애플리케이션 설계.md +++ b/01_Archive/2026-04-20/엔터프라이즈 애플리케이션 설계.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-98C87D -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 엔터프라이즈 애플리케이션 설계" --- -# [[엔터프라이즈 애플리케이션 설계]] +# [[엔터프라이즈 애플리케이션 설계|엔터프라이즈 애플리케이션 설계]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 엔터프라이즈 애플리케이션 설계는 기술적 부채와 느린 성능, 엉성한 사용자 경험을 방지하고 복잡한 비즈니스 요구사항을 견딜 수 있는 확장 가능하고 유지보수가 용이한 시스템의 청사진을 구축하는 과정입니다 [1]. 이를 위해 관심사의 분리(SoC), 모듈화, 도메인 주도 설계 등의 철학과 아키텍처 패턴이 적용되며, 대규모 개발 환경에서 각 기능이 상호 간섭 없이 유연하게 확장 및 배포될 수 있도록 하는 것을 핵심 목표로 삼습니다 [1-3]. @@ -35,11 +35,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 엔터프라이즈 애플리 - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[관심사의 분리(SoC)]], [[클린 아키텍처]], [[마이크로서비스 아키텍처]], [[도메인 주도 설계(DDD)]], [[관점 지향 프로그래밍(AOP)]], [[마이크로 프론트엔드]] -- **Projects/Contexts:** [[넷플릭스(Netflix)의 마이크로서비스 및 코스모스 플랫폼 전환]], [[스포티파이(Spotify)의 스쿼드 모델 및 마이크로 프론트엔드 도입]] +- **Related Topics:** [[관심사의 분리(SoC)|관심사의 분리(SoC)]], [[클린 아키텍처|클린 아키텍처]], [[마이크로서비스 아키텍처|마이크로서비스 아키텍처]], [[도메인 주도 설계(DDD)|도메인 주도 설계(DDD)]], [[관점 지향 프로그래밍(AOP)|관점 지향 프로그래밍(AOP)]], [[마이크로 프론트엔드|마이크로 프론트엔드]] +- **Projects/Contexts:** [[넷플릭스(Netflix)의 마이크로서비스 및 코스모스 플랫폼 전환|넷플릭스(Netflix)의 마이크로서비스 및 코스모스 플랫폼 전환]], [[스포티파이(Spotify)의 스쿼드 모델 및 마이크로 프론트엔드 도입|스포티파이(Spotify)의 스쿼드 모델 및 마이크로 프론트엔드 도입]] - **Contradictions/Notes:** 분리와 추상화가 무조건적인 장점만을 갖는 것은 아닙니다. 다수의 소스에서는 완벽한 아키텍처 경계를 만드는 데는 초기 비용이 상당히 크고, 과도한 분리(오버 엔지니어링)는 불필요한 인지적 부하 증대 및 네트워크 통신 성능 저하(오버헤드)를 유발할 수 있다고 경고합니다 [14, 31, 32]. 따라서 "Rule of Three(중복이 세 번 발생하면 추상화하라)"와 같은 실용적 접근을 통해 응집도와 결합도의 적절한 균형을 찾는 것이 엔지니어의 핵심 과제입니다 [14, 33]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/엔터프라이즈 애플리케이션 설계.md]] +- Raw Source: 00_Raw/2026-04-20/엔터프라이즈 애플리케이션 설계.md --- diff --git a/01_Archive/2026-04-20/엔티티 (Entities).md b/01_Archive/2026-04-20/엔티티 (Entities).md index c249126d..a4b6971c 100644 --- a/01_Archive/2026-04-20/엔티티 (Entities).md +++ b/01_Archive/2026-04-20/엔티티 (Entities).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-8E681E -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 엔티티 (Entities)" --- -# [[엔티티 (Entities)]] +# [[엔티티 (Entities)|엔티티 (Entities)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 엔티티(Entities)는 소프트웨어 아키텍처 및 도메인 주도 설계(DDD)에서 핵심 업무 데이터와 이를 기반으로 동작하는 전사적인 핵심 업무 규칙을 캡슐화하는 고수준의 객체입니다 [1-3]. 이들은 아키텍처의 가장 중심 계층에 위치하며, 데이터베이스나 사용자 인터페이스(UI), 프레임워크와 같은 외부 요소에 전혀 의존하지 않고 독립적으로 존재합니다 [1, 4]. 본질적으로 시스템의 입출력 방식이나 외부 기술의 변화에 영향을 받지 않는, 비즈니스의 가장 핵심적이고 순수한 개념을 구체화합니다 [3-5]. @@ -30,11 +30,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 엔티티 (Entities)" - **정책 변화:** Design & Experience 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[도메인 주도 설계 (Domain-Driven Design)]], [[클린 아키텍처 (Clean Architecture)]], [[유스케이스 (Use Cases)]], [[값 객체 (Value Objects)]] -- **Projects/Contexts:** [[엔터프라이즈급 소프트웨어 아키텍처 설계]], [[VIPER 아키텍처 기반 iOS 애플리케이션 개발]] +- **Related Topics:** 도메인 주도 설계 (Domain-Driven Design), [[클린 아키텍처 (Clean Architecture)|클린 아키텍처 (Clean Architecture)]], [[유스케이스 (Use Cases)|유스케이스 (Use Cases)]], 값 객체 (Value Objects) +- **Projects/Contexts:** 엔터프라이즈급 소프트웨어 아키텍처 설계, VIPER 아키텍처 기반 iOS 애플리케이션 개발 - **Contradictions/Notes:** 엔티티와 시스템의 요청 및 응답 모델은 많은 데이터를 공유하기 때문에 서로 참조하거나 결합하려는 유혹에 빠지기 쉽지만, 이는 장기적으로 공통 폐쇄 원칙을 위반하고 코드베이스에 혼란을 초래하므로 엄격히 분리해야 한다고 경고합니다 [14]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/엔티티 (Entities).md]] +- Raw Source: 00_Raw/2026-04-20/엔티티 (Entities).md --- diff --git a/01_Archive/2026-04-20/연합 학습 (Associative Learning).md b/01_Archive/2026-04-20/연합 학습 (Associative Learning).md index 7eb360ed..50e42957 100644 --- a/01_Archive/2026-04-20/연합 학습 (Associative Learning).md +++ b/01_Archive/2026-04-20/연합 학습 (Associative Learning).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-0E1EE5 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 연합 학습 (Associative Learning)" --- -# [[연합 학습 (Associative Learning)]] +# [[연합 학습 (Associative Learning)|연합 학습 (Associative Learning)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - 연합 학습 (Associative Lea ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/연합 학습 (Associative Learning).md]] +- Raw Source: 00_Raw/2026-04-20/연합 학습 (Associative Learning).md --- diff --git a/01_Archive/2026-04-20/오래된 공간(Old Space).md b/01_Archive/2026-04-20/오래된 공간(Old Space).md index e74deddb..4ff614cb 100644 --- a/01_Archive/2026-04-20/오래된 공간(Old Space).md +++ b/01_Archive/2026-04-20/오래된 공간(Old Space).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-0AE506 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 오래된 공간(Old Space)" --- -# [[오래된 공간(Old Space)]] +# [[오래된 공간(Old Space)|오래된 공간(Old Space)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 오래된 공간(Old Space)은 V8 자바스크립트 엔진의 힙(Heap) 메모리에서 새로운 공간(New Space)에 생성된 후 두 번의 마이너 가비지 컬렉션(Minor GC) 주기 동안 살아남은 장기 생존 객체들이 이동(승격)하여 저장되는 메모리 영역입니다 [1-3]. 이 공간은 비교적 크기가 크고 장기 데이터 보존을 위해 설계되었으며, 마크-스윕(Mark-Sweep) 및 마크-컴팩트(Mark-Compact) 알고리즘을 사용하는 메이저 가비지 컬렉션(Major GC)에 의해 관리됩니다 [3-5]. @@ -24,11 +24,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 오래된 공간(Old Space)" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[새로운 공간(New Space)]], [[가비지 컬렉션(Garbage Collection)]], [[세대 가설(Generational Hypothesis)]], [[마크-스윕(Mark-Sweep)]], [[마크-컴팩트(Mark-Compact)]] -- **Projects/Contexts:** [[V8 엔진 힙 아키텍처(V8 Engine Heap Architecture)]], [[할당 타임라인(Allocation Timeline)]], [[Node.js 메모리 튜닝]] +- **Related Topics:** [[새로운 공간(New Space)|새로운 공간(New Space)]], [[가비지 컬렉션(Garbage Collection)|가비지 컬렉션(Garbage Collection)]], [[세대 가설(Generational Hypothesis)|세대 가설(Generational Hypothesis)]], [[마크-스윕(Mark-Sweep)|마크-스윕(Mark-Sweep)]], [[마크-컴팩트(Mark-Compact)|마크-컴팩트(Mark-Compact)]] +- **Projects/Contexts:** [[V8 엔진 힙 아키텍처(V8 Engine Heap Architecture)|V8 엔진 힙 아키텍처(V8 Engine Heap Architecture)]], [[할당 타임라인(Allocation Timeline)|할당 타임라인(Allocation Timeline)]], [[Node.js 메모리 튜닝|Node.js 메모리 튜닝]] - **Contradictions/Notes:** 소스에 내용 상의 모순은 없으며, V8 메모리 관리의 핵심인 세대 가설에 기반하여 새롭게 생성된 단기 생존 객체 공간(New Space)과 명확하게 분리 관리되어 엔진의 전체적인 가비지 컬렉션 효율을 높인다는 점이 일관되게 강조되고 있습니다. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/오래된 공간(Old Space).md]] +- Raw Source: 00_Raw/2026-04-20/오래된 공간(Old Space).md --- diff --git a/01_Archive/2026-04-20/오리노코(Orinoco GC).md b/01_Archive/2026-04-20/오리노코(Orinoco GC).md index 5f2b233f..b0025d4b 100644 --- a/01_Archive/2026-04-20/오리노코(Orinoco GC).md +++ b/01_Archive/2026-04-20/오리노코(Orinoco GC).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-6488F2 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 오리노코(Orinoco GC)" --- -# [[오리노코(Orinoco GC)]] +# [[오리노코(Orinoco GC)|오리노코(Orinoco GC)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 오리노코(Orinoco)는 V8 엔진의 가비지 컬렉터(GC)를 개선하기 위한 프로젝트의 코드명으로, 기존의 순차적인 'Stop-the-world' 방식의 가비지 컬렉터를 병렬(Parallel), 동시(Concurrent), 점진적(Incremental) 처리 기법을 적용하여 새롭게 탈바꿈시켰습니다 [1, 2]. 이 프로젝트의 주요 목적은 메인 스레드의 부하를 줄이고 GC로 인한 일시 정지(Pause) 시간을 최소화하는 것입니다 [2]. 이를 통해 애니메이션, 스크롤, 사용자 상호작용의 지연 시간을 줄이고 전반적인 프로그램 처리량과 성능을 향상시킵니다 [3, 4]. @@ -25,11 +25,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 오리노코(Orinoco GC)" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[가비지 컬렉터(Garbage Collector)]], [[V8 엔진(V8 Engine)]], [[마크-스위프(Mark-Sweep)]], [[스캐빈저(Scavenger)]], [[Stop-the-world]] -- **Projects/Contexts:** [[JavaScript 메모리 관리(JavaScript Memory Management)]] +- **Related Topics:** [[가비지 컬렉터(Garbage Collector)|가비지 컬렉터(Garbage Collector)]], [[V8 엔진(V8 Engine)|V8 엔진(V8 Engine)]], [[마크-스위프(Mark-Sweep)|마크-스위프(Mark-Sweep)]], [[스캐빈저(Scavenger)|스캐빈저(Scavenger)]], [[Stop-the-world|Stop-the-world]] +- **Projects/Contexts:** [[JavaScript 메모리 관리(JavaScript Memory Management)|JavaScript 메모리 관리(JavaScript Memory Management)]] - **Contradictions/Notes:** 점진적(Incremental) GC 기법은 메인 스레드의 응답성을 높이고 지연(Latency) 문제를 해결하는 데에는 효과적이지만, 메인 스레드에서 소비되는 총 시간 자체를 줄여주지는 않으며 오히려 작업 분산으로 인해 약간 증가시킬 수 있다고 소스는 지적합니다 [7]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/오리노코(Orinoco GC).md]] +- Raw Source: 00_Raw/2026-04-20/오리노코(Orinoco GC).md --- diff --git a/01_Archive/2026-04-20/오리노코(Orinoco) 프로젝트.md b/01_Archive/2026-04-20/오리노코(Orinoco) 프로젝트.md index bfa708ff..9544f920 100644 --- a/01_Archive/2026-04-20/오리노코(Orinoco) 프로젝트.md +++ b/01_Archive/2026-04-20/오리노코(Orinoco) 프로젝트.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-C362F7 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 오리노코(Orinoco) 프로젝트" --- -# [[오리노코(Orinoco) 프로젝트]] +# [[오리노코(Orinoco) 프로젝트|오리노코(Orinoco) 프로젝트]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 오리노코(Orinoco) 프로젝트는 구글의 V8 자바스크립트 엔진에 탑재된 최신 가비지 컬렉터(GC)를 개선하기 위한 프로젝트의 코드명입니다 [1, 2]. 기존의 순차적이고 메인 스레드를 완전히 멈추게 하는 "stop-the-world" 방식의 한계를 극복하기 위해 시작되었습니다 [2, 3]. 이를 위해 병렬(parallel), 점진적(incremental), 동시(concurrent) 처리 기법을 도입하여 메인 스레드의 부담을 해방시키고 애플리케이션의 일시 정지 시간(Pause time)을 최소화하는 것을 목표로 합니다 [4, 5]. @@ -25,11 +25,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 오리노코(Orinoco) 프로 - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[가비지 컬렉션(Garbage Collection)]], [[V8 엔진(V8 Engine)]], [[스캐빈저(Scavenger)]], [[메이저 GC(Major GC)]] -- **Projects/Contexts:** [[자바스크립트(JavaScript)]], [[크롬 브라우저(Chrome Browser)]] +- **Related Topics:** [[가비지 컬렉션(Garbage Collection)|가비지 컬렉션(Garbage Collection)]], [[V8 엔진(V8 Engine)|V8 엔진(V8 Engine)]], [[스캐빈저(Scavenger)|스캐빈저(Scavenger)]], 메이저 GC(Major GC) +- **Projects/Contexts:** 자바스크립트(JavaScript), 크롬 브라우저(Chrome Browser) - **Contradictions/Notes:** 점진적(Incremental) GC 기법은 메인 스레드에서 소요되는 전체 총시간을 줄여주지는 않으며 오히려 약간 늘릴 수도 있습니다. 하지만 GC 작업을 여러 시간에 걸쳐 분산시킴으로써 애플리케이션의 애니메이션이나 사용자 입력에 대한 응답성을 유지할 수 있도록 돕습니다 [10]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/오리노코(Orinoco) 프로젝트.md]] +- Raw Source: 00_Raw/2026-04-20/오리노코(Orinoco) 프로젝트.md --- diff --git a/01_Archive/2026-04-20/오버드로우(Overdraw).md b/01_Archive/2026-04-20/오버드로우(Overdraw).md index f358d127..0814b19b 100644 --- a/01_Archive/2026-04-20/오버드로우(Overdraw).md +++ b/01_Archive/2026-04-20/오버드로우(Overdraw).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-8CE1CE -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 오버드로우(Overdraw)" --- -# [[오버드로우(Overdraw)]] +# [[오버드로우(Overdraw)|오버드로우(Overdraw)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 오버드로우(Overdraw)는 렌더링 파이프라인의 프래그먼트 셰이딩(Fragment Shading) 단계에서 동일한 픽셀 위치에 대해 여러 번의 쓰기 작업이 중첩되어 발생하는 현상이다 [1]. 주로 겹쳐진 투명한 기하구조나 비효율적인 깊이 정렬(Depth Sorting)로 인해 보이지 않는 픽셀 연산에 GPU 자원을 낭비하게 만든다 [2]. 이는 결과적으로 불필요한 GPU 픽셀 처리 비용을 유발하여 심각한 프레임 속도 저하 및 성능 병목을 초래한다 [1, 3]. @@ -22,11 +22,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 오버드로우(Overdraw)" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[프래그먼트 셰이딩(Fragment Shading)]], [[깊이 정렬(Depth Sorting)]], [[Early-Z (초기 깊이 테스트)]], [[프래그먼트 바운드(Fragment-bound)]] -- **Projects/Contexts:** [[Three.js InstancedMesh 최적화]], [[투명도(Transparency) 렌더링 관리]] +- **Related Topics:** [[프래그먼트 셰이딩(Fragment Shading)|프래그먼트 셰이딩(Fragment Shading)]], 깊이 정렬(Depth Sorting), Early-Z (초기 깊이 테스트), [[프래그먼트 바운드(Fragment-bound)|프래그먼트 바운드(Fragment-bound)]] +- **Projects/Contexts:** Three.js InstancedMesh 최적화, 투명도(Transparency) 렌더링 관리 - **Contradictions/Notes:** `InstancedMesh`는 드로우 콜(Draw Call)을 획기적으로 줄여 CPU 오버헤드를 감소시키는 최적화 기법으로 알려져 있으나, 자동 정렬 기능이 없어 오히려 막대한 오버드로우를 유발하고 GPU 픽셀 처리 성능을 크게 저하시킬 수 있다는 구조적인 모순(트레이드오프)을 지니고 있다 [1]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/오버드로우(Overdraw).md]] +- Raw Source: 00_Raw/2026-04-20/오버드로우(Overdraw).md --- diff --git a/01_Archive/2026-04-20/오사카 엑스포 2025 호쿠사이 인스톨레이션(Hokusai installation).md b/01_Archive/2026-04-20/오사카 엑스포 2025 호쿠사이 인스톨레이션(Hokusai installation).md index a571018a..ecee2e35 100644 --- a/01_Archive/2026-04-20/오사카 엑스포 2025 호쿠사이 인스톨레이션(Hokusai installation).md +++ b/01_Archive/2026-04-20/오사카 엑스포 2025 호쿠사이 인스톨레이션(Hokusai installation).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-6697EE -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 오사카 엑스포 2025 호쿠사이 인스톨레이션(Hokusai installation)" --- -# [[오사카 엑스포 2025 호쿠사이 인스톨레이션(Hokusai installation)]] +# [[오사카 엑스포 2025 호쿠사이 인스톨레이션(Hokusai installation)|오사카 엑스포 2025 호쿠사이 인스톨레이션(Hokusai installation)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 오사카 엑스포 2025 호쿠사이 인스톨레이션(Hokusai installation)은 인터랙티브 크리에이티브 스튜디오인 Utsubo가 2025년 오사카 엑스포를 위해 제작한 대규모 유체 시뮬레이션 프로젝트입니다 [1]. 이 인스톨레이션은 Three.js의 WebGPU 렌더러를 적극 활용하여 기존의 한계를 뛰어넘는 100만 개 단위의 파티클을 실시간으로 렌더링하는 그래픽 성능을 입증했습니다 [1]. 98인치 4K 디스플레이 상에서 지연 없는 실시간 다인원 신체 추적(multi-person body tracking) 기능과 결합되어, WebGPU 마이그레이션을 통한 성공적인 프로덕션 벤치마크 사례로 평가받고 있습니다 [2, 3]. @@ -22,11 +22,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 오사카 엑스포 2025 호 - **정책 변화:** AI 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[WebGPU]], [[Three.js]], [[Particle Fluid Simulation]] -- **Projects/Contexts:** [[Utsubo]], [[Expo 2025 Osaka]], [[Waves of Connection]] +- **Related Topics:** [[WebGPU|WebGPU]], [[Three.js|Three.js]], Particle Fluid Simulation +- **Projects/Contexts:** [[Utsubo|Utsubo]], [[Expo 2025 Osaka|Expo 2025 Osaka]], [[Waves of Connection|Waves of Connection]] - **Contradictions/Notes:** 소스 문서 내에서 오사카 엑스포 2025의 '호쿠사이 인스톨레이션(Hokusai installation)'과 'Waves of Connection' 인스톨레이션은 모두 100만 개의 파티클을 실시간 렌더링한 Utsubo 스튜디오의 동일하거나 밀접하게 연관된 WebGPU 프로덕션 사례로 교차 언급되고 있습니다 [1, 3]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/오사카 엑스포 2025 호쿠사이 인스톨레이션(Hokusai installation).md]] +- Raw Source: 00_Raw/2026-04-20/오사카 엑스포 2025 호쿠사이 인스톨레이션(Hokusai installation).md --- diff --git a/01_Archive/2026-04-20/오탐 (False Positive).md b/01_Archive/2026-04-20/오탐 (False Positive).md index c056b2ac..26a78003 100644 --- a/01_Archive/2026-04-20/오탐 (False Positive).md +++ b/01_Archive/2026-04-20/오탐 (False Positive).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-86DCBE -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 오탐 (False Positive)" --- -# [[오탐 (False Positive)]] +# [[오탐 (False Positive)|오탐 (False Positive)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -27,11 +27,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 오탐 (False Positive)" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[정적 애플리케이션 보안 테스트 (SAST)]], [[경고 피로 (Alert Fatigue)]], [[하이브리드 코드 리뷰]] -- **Projects/Contexts:** [[Snyk Code]], [[Corgea]], [[Semgrep Assistant]] +- **Related Topics:** [[정적 애플리케이션 보안 테스트 (SAST)|정적 애플리케이션 보안 테스트 (SAST)]], [[경고 피로 (Alert Fatigue)|경고 피로 (Alert Fatigue)]], [[하이브리드 코드 리뷰|하이브리드 코드 리뷰]] +- **Projects/Contexts:** Snyk Code, [[Corgea|Corgea]], [[Semgrep Assistant|Semgrep Assistant]] - **Contradictions/Notes:** 소스에서는 일반적인 자동화 정적 분석 도구가 30~60% 혹은 최대 80%에 이르는 높은 오탐률을 보이며 치명적인 경고 피로를 유발한다고 지적하지만 [3, 5], 동시에 벤더사의 보고에 따르면 특정 최신 AI 네이티브 SAST 도구(예: Veracode, Corgea)는 오탐률을 1.1% 미만 또는 5% 미만 수준으로 극적으로 낮출 수 있다고 주장하여 AI 기술 발전에 따른 상반된 오탐 관리 성능을 보여줍니다 [13]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/오탐 (False Positive).md]] +- Raw Source: 00_Raw/2026-04-20/오탐 (False Positive).md --- diff --git a/01_Archive/2026-04-20/오픈소스 컴포넌트 (Open Source Components).md b/01_Archive/2026-04-20/오픈소스 컴포넌트 (Open Source Components).md index d692e84c..82ca214b 100644 --- a/01_Archive/2026-04-20/오픈소스 컴포넌트 (Open Source Components).md +++ b/01_Archive/2026-04-20/오픈소스 컴포넌트 (Open Source Components).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-AAE756 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 오픈소스 컴포넌트 (Open Source Components)" --- -# [[오픈소스 컴포넌트 (Open Source Components)]] +# [[오픈소스 컴포넌트 (Open Source Components)|오픈소스 컴포넌트 (Open Source Components)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 오픈소스 컴포넌트(또는 오픈소스 종속성)는 현대 애플리케이션의 80~90%를 구성하는 제3자(Third-party) 제공 라이브러리 및 코드 패키지입니다 [1, 2]. 이는 소프트웨어 개발 속도를 높여주지만, 알려진 취약점이나 라이선스 위반 문제를 포함할 수 있어 소프트웨어 공급망 보안의 핵심 관리 대상이 됩니다 [2, 3]. 이를 안전하게 유지하기 위해 기업들은 소프트웨어 구성 분석(SCA) 도구를 통해 오픈소스 컴포넌트를 스캔하고 관리합니다 [1, 4]. @@ -24,11 +24,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 오픈소스 컴포넌트 (Ope - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Software Composition Analysis (SCA)]], [[Supply Chain Security]], [[SAST (Static Application Security Testing)]] -- **Projects/Contexts:** [[Snyk Open Source]], [[Endor Labs]] +- **Related Topics:** [[Software Composition Analysis (SCA)|Software Composition Analysis (SCA)]], [[서플라이 체인 보안 (Supply Chain Security)|Supply Chain Security]], [[SAST (Static Application Security Testing)|SAST (Static Application Security Testing)]] +- **Projects/Contexts:** [[Snyk Open Source|Snyk Open Source]], Endor Labs - **Contradictions/Notes:** 자체적으로 작성한 커스텀 코드의 논리적 결함과 새로운 취약점을 찾는 데는 SAST가 적합하지만, 오픈소스 및 제3자 컴포넌트에 포함된 기존 취약점과 라이선스 문제를 탐지하는 데에는 SCA가 특화되어 있으므로 보안을 위해 이 두 가지를 함께 사용하는 것이 권장됩니다 [2, 3]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/오픈소스 컴포넌트 (Open Source Components).md]] +- Raw Source: 00_Raw/2026-04-20/오픈소스 컴포넌트 (Open Source Components).md --- diff --git a/01_Archive/2026-04-20/온톨로지 (Ontology).md b/01_Archive/2026-04-20/온톨로지 (Ontology).md index 30f18cbc..03ebe3d5 100644 --- a/01_Archive/2026-04-20/온톨로지 (Ontology).md +++ b/01_Archive/2026-04-20/온톨로지 (Ontology).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-25F9C5 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 온톨로지 (Ontology)" --- -# [[온톨로지 (Ontology)]] +# [[온톨로지 (Ontology)|온톨로지 (Ontology)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - 온톨로지 (Ontology)" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/온톨로지 (Ontology).md]] +- Raw Source: 00_Raw/2026-04-20/온톨로지 (Ontology).md --- diff --git a/01_Archive/2026-04-20/온톨로지 지식 베이스.md b/01_Archive/2026-04-20/온톨로지 지식 베이스.md index ffc14201..c58778b3 100644 --- a/01_Archive/2026-04-20/온톨로지 지식 베이스.md +++ b/01_Archive/2026-04-20/온톨로지 지식 베이스.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-A3EA4F -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 온톨로지 지식 베이스" --- -# [[온톨로지 지식 베이스]] +# [[온톨로지 지식 베이스|온톨로지 지식 베이스]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - 온톨로지 지식 베이스" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/온톨로지 지식 베이스.md]] +- Raw Source: 00_Raw/2026-04-20/온톨로지 지식 베이스.md --- diff --git a/01_Archive/2026-04-20/완전성 검사 (Exhaustiveness Checking).md b/01_Archive/2026-04-20/완전성 검사 (Exhaustiveness Checking).md index d5aec6bb..bdbcd3c1 100644 --- a/01_Archive/2026-04-20/완전성 검사 (Exhaustiveness Checking).md +++ b/01_Archive/2026-04-20/완전성 검사 (Exhaustiveness Checking).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-98C2AC -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 완전성 검사 (Exhaustiveness Checking)" --- -# [[완전성 검사 (Exhaustiveness Checking)]] +# [[완전성 검사 (Exhaustiveness Checking)|완전성 검사 (Exhaustiveness Checking)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -23,11 +23,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 완전성 검사 (Exhaustivene - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[식별 가능한 유니온 (Discriminated Unions)]], [[never 타입]], [[ts-pattern]], [[satisfies 연산자]] -- **Projects/Contexts:** [[타입스크립트 상태 관리 및 분기 처리 설계]] +- **Related Topics:** [[식별 가능한 유니온 (Discriminated Unions)|식별 가능한 유니온 (Discriminated Unions)]], [[never 타입|never 타입]], [[ts-pattern|ts-pattern]], [[satisfies 연산자|satisfies 연산자]] +- **Projects/Contexts:** [[타입스크립트 상태 관리 및 분기 처리 설계|타입스크립트 상태 관리 및 분기 처리 설계]] - **Contradictions/Notes:** 소스에서는 완전성 검사의 효과를 긍정적으로 평가하지만, `ts-pattern` 라이브러리의 `.exhaustive()` 등을 활용한 고도의 추상화는 기본 제어 구조(`if/else`, `switch`)보다 성능이 현저히 떨어지고 오버엔지니어링이 될 수 있음을 경계합니다. 따라서 단순한 조건의 경우, 기존 방식과 `satisfies never` 등을 조합하여 가독성을 높이고 안전하게 분기를 처리하는 것이 더 나을 수 있다고 조언합니다 [7-10]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/완전성 검사 (Exhaustiveness Checking).md]] +- Raw Source: 00_Raw/2026-04-20/완전성 검사 (Exhaustiveness Checking).md --- diff --git a/01_Archive/2026-04-20/완전성 검사(Exhaustiveness Checking).md b/01_Archive/2026-04-20/완전성 검사(Exhaustiveness Checking).md index dd75f927..a75ba9ba 100644 --- a/01_Archive/2026-04-20/완전성 검사(Exhaustiveness Checking).md +++ b/01_Archive/2026-04-20/완전성 검사(Exhaustiveness Checking).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-0C762B -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 완전성 검사(Exhaustiveness Checking)" --- -# [[완전성 검사(Exhaustiveness Checking)]] +# [[완전성 검사(Exhaustiveness Checking)|완전성 검사(Exhaustiveness Checking)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 완전성 검사(Exhaustiveness Checking)는 타입 시스템 내에서 특정 유니온 타입의 모든 가능한 케이스(변형)가 코드상에서 빠짐없이 처리되었는지를 컴파일 시점에 검증하는 기법입니다[1-3]. 식별 가능한 유니온(Discriminated Unions)과 함께 결합하여 주로 사용되며, 새로운 상태가 추가되었을 때 이를 처리하지 않은 분기문이 존재하면 즉시 컴파일 에러를 발생시킵니다[2, 3]. 이를 통해 개발자는 런타임 버그를 사전에 예방하고 잘못된 상태가 시스템을 통과하는 것을 원천적으로 차단할 수 있습니다[4, 5]. @@ -23,11 +23,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 완전성 검사(Exhaustivenes - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[식별 가능한 유니온(Discriminated Unions)]], [[never 타입]], [[타입 좁히기(Type Narrowing)]] -- **Projects/Contexts:** [[TypeScript 컴파일러의 정적 타입 시스템]], [[패턴 매칭 라이브러리(ts-pattern 등)]] +- **Related Topics:** [[식별 가능한 유니온(Discriminated Unions)|식별 가능한 유니온(Discriminated Unions)]], [[never 타입|never 타입]], [[타입 좁히기(Type Narrowing)|타입 좁히기(Type Narrowing)]] +- **Projects/Contexts:** TypeScript 컴파일러의 정적 타입 시스템, 패턴 매칭 라이브러리(ts-pattern 등) - **Contradictions/Notes:** TypeScript에서 `strictNullChecks`를 활용한 반환 타입 검사 방식은 구형 코드베이스에서 항상 원활하게 작동하지 않을 수 있으며 다소 미묘한 방식인 반면, `never` 타입을 활용한 검사 방식은 오류 메시지에 누락된 타입 이름이 포함되어 더 명확하게 문제를 파악할 수 있다는 장점이 있습니다[6, 7]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/완전성 검사(Exhaustiveness Checking).md]] +- Raw Source: 00_Raw/2026-04-20/완전성 검사(Exhaustiveness Checking).md --- diff --git a/01_Archive/2026-04-20/외부 API 데이터 및 설정 파일 처리.md b/01_Archive/2026-04-20/외부 API 데이터 및 설정 파일 처리.md index 5568c573..df9b91f9 100644 --- a/01_Archive/2026-04-20/외부 API 데이터 및 설정 파일 처리.md +++ b/01_Archive/2026-04-20/외부 API 데이터 및 설정 파일 처리.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-90144B -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 외부 API 데이터 및 설정 파일 처리" --- -# [[외부 API 데이터 및 설정 파일 처리]] +# [[외부 API 데이터 및 설정 파일 처리|외부 API 데이터 및 설정 파일 처리]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 외부 API 데이터 및 설정 파일 처리는 애플리케이션의 경계에서 유입되는 불확실한 외부 데이터를 안전하게 타입 시스템으로 통합하고, 설정값의 불변성과 정확한 구조를 강제하는 과정입니다 [1-3]. TypeScript에서는 원격 소스의 데이터를 단순히 타입으로 단언하기보다 런타임 스키마를 통해 파싱하는 원칙을 따릅니다 [4]. 또한, API 응답과 설정 객체를 안전하게 다루기 위해 식별 가능한 유니온, readonly 수식어, satisfies 연산자 등의 언어적 도구를 적극적으로 활용합니다 [5-7]. @@ -25,11 +25,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 외부 API 데이터 및 설 - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Parse, Don't Validate]], [[Discriminated Unions]], [[satisfies 연산자]], [[readonly 수식어]], [[Zod 스키마 파싱]] -- **Projects/Contexts:** [[OpenAPI 스펙 기반 SDK 자동 생성]], [[프론트엔드와 백엔드 간 데이터 매핑]] +- **Related Topics:** [[Parse dont validate|Parse, Don't Validate]], [[Discriminated Unions|Discriminated Unions]], [[satisfies 연산자|satisfies 연산자]], [[readonly 수식어|readonly 수식어]], Zod 스키마 파싱 +- **Projects/Contexts:** OpenAPI 스펙 기반 SDK 자동 생성, 프론트엔드와 백엔드 간 데이터 매핑 - **Contradictions/Notes:** 외부에서 유입되는 데이터를 처리할 때 단순히 `as` 연산자를 통한 타입 단언(Type Casting)을 사용하는 것은 초과 속성 검사(Excess Property Checking)를 우회하여 런타임 버그를 초래할 수 있으므로, 검증 로직이나 `satisfies` 연산자를 사용하는 것이 훨씬 안전합니다 [14, 15]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/외부 API 데이터 및 설정 파일 처리.md]] +- Raw Source: 00_Raw/2026-04-20/외부 API 데이터 및 설정 파일 처리.md --- diff --git a/01_Archive/2026-04-20/외부 API 데이터의 런타임 검증 후 처리.md b/01_Archive/2026-04-20/외부 API 데이터의 런타임 검증 후 처리.md index d08e3bde..e94c97d4 100644 --- a/01_Archive/2026-04-20/외부 API 데이터의 런타임 검증 후 처리.md +++ b/01_Archive/2026-04-20/외부 API 데이터의 런타임 검증 후 처리.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-99B08D -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 외부 API 데이터의 런타임 검증 후 처리" --- -# [[외부 API 데이터의 런타임 검증 후 처리]] +# [[외부 API 데이터의 런타임 검증 후 처리|외부 API 데이터의 런타임 검증 후 처리]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 외부 API 데이터의 런타임 검증 후 처리는 시스템 경계에서 알 수 없거나 느슨한 타입의 외부 데이터를 검증 및 변환하여, 시스템 내부로 신뢰할 수 있는 구체적인 타입의 데이터를 전달하는 과정을 의미합니다 [1], [2]. 이는 "검증하지 말고 파싱하라(Parse, don't validate)" 철학에 기반을 두며, Zod와 같은 라이브러리를 활용해 런타임에 데이터를 검증한 뒤 브랜디드 타입(Branded Types)이나 식별 가능한 유니온(Discriminated Unions)으로 안전하게 변환하여 처리하는 것을 핵심으로 합니다 [3], [4], [5], [6]. @@ -23,11 +23,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 외부 API 데이터의 런타 - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Parse, Don't Validate]], [[Branded Types]], [[Discriminated Unions]], [[Zod 런타임 검증]] -- **Projects/Contexts:** [[API Response Handling]], [[시스템 경계 데이터 파싱(System Boundary Data Parsing)]] +- **Related Topics:** [[Parse dont validate|Parse, Don't Validate]], [[Branded Types|Branded Types]], [[Discriminated Unions|Discriminated Unions]], Zod 런타임 검증 +- **Projects/Contexts:** API Response Handling, 시스템 경계 데이터 파싱(System Boundary Data Parsing) - **Contradictions/Notes:** 외부 데이터 무결성을 위해 런타임 검증이 필수적이지만, 런타임 검증에는 성능 비용(Runtime cost)이 수반되므로 성능에 매우 민감한 경로(performance-critical paths)에서는 사용 시 주의가 필요합니다 [15]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/외부 API 데이터의 런타임 검증 후 처리.md]] +- Raw Source: 00_Raw/2026-04-20/외부 API 데이터의 런타임 검증 후 처리.md --- diff --git a/01_Archive/2026-04-20/외부 라이브러리 API 설계.md b/01_Archive/2026-04-20/외부 라이브러리 API 설계.md index 06628316..67cac1ed 100644 --- a/01_Archive/2026-04-20/외부 라이브러리 API 설계.md +++ b/01_Archive/2026-04-20/외부 라이브러리 API 설계.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-44799B -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 외부 라이브러리 API 설계" --- -# [[외부 라이브러리 API 설계]] +# [[외부 라이브러리 API 설계|외부 라이브러리 API 설계]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 외부 라이브러리(SDK) API 설계는 사용자가 내부의 복잡한 구현을 알 필요 없이 명확한 의도에 따라 기능을 쉽게 사용할 수 있도록 인터페이스를 구축하는 과정입니다 [1]. 이를 위해 퍼사드(Facade) 패턴을 활용하여 일반적인 유스케이스를 고수준 API로 제공하고, 특수 케이스를 위해 세밀한 제어가 가능한 저수준 API를 탈출구(Escape Hatch)로 함께 제공하는 것이 핵심입니다 [2, 3]. 잘 설계된 API 인터페이스는 사용자의 휴먼 에러를 구조적으로 방지하며, 장기적인 호환성과 플랫폼의 안정성을 보장합니다 [3-5]. @@ -30,11 +30,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 외부 라이브러리 API 설 - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[퍼사드 패턴(Facade Pattern)]], [[단일 책임 원칙(SRP)]], [[인터페이스 분리 원칙(ISP)]], [[탈출구(Escape Hatch)]] -- **Projects/Contexts:** [[Toss Front 외부 연동 SDK]], [[AWS CDK]] +- **Related Topics:** 퍼사드 패턴(Facade Pattern), [[단일 책임 원칙(SRP)|단일 책임 원칙(SRP)]], 인터페이스 분리 원칙(ISP), 탈출구(Escape Hatch) +- **Projects/Contexts:** Toss Front 외부 연동 SDK, AWS CDK - **Contradictions/Notes:** 퍼사드 패턴을 통해 추상화 수준을 높이면 사용성이 크게 개선되지만, 동시에 사용자의 세밀한 제어를 제한하고 라이브러리 내부의 유지보수 비용과 복잡도를 증가시키는 트레이드오프가 필연적으로 발생합니다. 따라서 저수준 API를 탈출구로 제공하여 설계의 균형을 잡는 것이 매우 중요합니다 [3, 7]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/외부 라이브러리 API 설계.md]] +- Raw Source: 00_Raw/2026-04-20/외부 라이브러리 API 설계.md --- diff --git a/01_Archive/2026-04-20/웹 브라우저 그래픽 API 호환성.md b/01_Archive/2026-04-20/웹 브라우저 그래픽 API 호환성.md index c930a1d3..9ac5f099 100644 --- a/01_Archive/2026-04-20/웹 브라우저 그래픽 API 호환성.md +++ b/01_Archive/2026-04-20/웹 브라우저 그래픽 API 호환성.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-7B4FF5 -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 웹 브라우저 그래픽 API 호환성" --- -# [[웹 브라우저 그래픽 API 호환성]] +# [[웹 브라우저 그래픽 API 호환성|웹 브라우저 그래픽 API 호환성]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 웹 브라우저 그래픽 API 호환성은 WebGL 및 WebGPU와 같은 웹 기반 3D 그래픽 기술이 다양한 웹 브라우저, 운영 체제, 하드웨어 환경에서 일관되게 작동하고 최적화되는 정도를 의미합니다 [1-3]. WebGL은 폭넓게 지원되지만 OS별 그래픽 계층 변환 오버헤드와 브라우저 보안 제약의 영향을 크게 받으며, 차세대 표준인 WebGPU는 최신 하드웨어 기술을 활용하나 브라우저별 파편화가 존재하고 WebGL과 하위 호환되지 않습니다 [4-6]. 따라서 성능 최적화를 위해서는 대상 하드웨어 아키텍처와 브라우저별 API 지원 범위를 고려한 플랫폼 교차적 설계가 필수적입니다 [7, 8]. @@ -23,11 +23,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 웹 브라우저 그래픽 API - **정책 변화:** Graphics & Performance 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[WebGL]], [[WebGPU]], [[ANGLE]], [[Spectre 및 Meltdown]], [[타이머 쿼리 제한(Timer Query Quantization)]] -- **Projects/Contexts:** [[3D Gaussian Splatting(3DGS) 웹 렌더링]], [[크로스 플랫폼 성능 프로파일링]] +- **Related Topics:** [[WebGL|WebGL]], [[WebGPU|WebGPU]], [[ANGLE|ANGLE]], Spectre 및 Meltdown, 타이머 쿼리 제한(Timer Query Quantization) +- **Projects/Contexts:** 3D Gaussian Splatting(3DGS) 웹 렌더링, 크로스 플랫폼 성능 프로파일링 - **Contradictions/Notes:** WebGL의 `EXT_disjoint_timer_query` 확장 기능에 대해 `caniuse.com`의 지원 정보나 일부 문서가 최신 호환성 상태(보안 문제로 인한 브라우저별 비활성화 조치 등)를 정확히 반영하지 못하고 상충되는 정보를 제공했던 혼선이 존재했습니다 [17, 29]. 또한, WebGPU는 그래픽 성능과 리소스 제어권을 크게 향상시키지만 WebGL과 하위 호환되지 않으므로, 보편적 접근성이 필요한 프로젝트의 경우 WebGPU 지원이 대중화되기 전까지 WebGL 기반의 폴백(Fallback) 렌더링 환경을 유지해야만 하는 제약이 있습니다 [6, 25, 30]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/웹 브라우저 그래픽 API 호환성.md]] +- Raw Source: 00_Raw/2026-04-20/웹 브라우저 그래픽 API 호환성.md --- diff --git a/01_Archive/2026-04-20/웹 애플리케이션의 3계층 구조.md b/01_Archive/2026-04-20/웹 애플리케이션의 3계층 구조.md index a8efffcb..c9eb6034 100644 --- a/01_Archive/2026-04-20/웹 애플리케이션의 3계층 구조.md +++ b/01_Archive/2026-04-20/웹 애플리케이션의 3계층 구조.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-073A5E -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 웹 애플리케이션의 3계층 구조" --- -# [[웹 애플리케이션의 3계층 구조]] +# [[웹 애플리케이션의 3계층 구조|웹 애플리케이션의 3계층 구조]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 웹 애플리케이션의 3계층 구조(3-Tier Architecture)는 관심사의 분리(SoC) 원칙에 따라 시스템을 수평적인 층으로 나누어 각각 특정 책임을 부여하는 전통적이고 영향력 있는 소프트웨어 아키텍처 패턴입니다 [1, 2]. 이 구조는 애플리케이션을 사용자 인터페이스를 담당하는 프레젠테이션 계층, 핵심 비즈니스 규칙을 처리하는 비즈니스 로직 계층, 데이터베이스 통신을 관리하는 데이터 액세스 계층으로 엄격히 분리합니다 [2, 3]. 이러한 분리를 통해 개발자는 한 계층의 변경 사항이 다른 계층에 미치는 영향을 최소화하면서 시스템을 보다 모듈화하고 테스트 및 유지보수하기 쉽게 만들 수 있습니다 [1, 4]. @@ -40,11 +40,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 웹 애플리케이션의 3계 - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[관심사의 분리 (Separation of Concerns)]], [[의존성 주입 (Dependency Injection)]], [[MVC (Model-View-Controller)]], [[클린 아키텍처 (Clean Architecture)]] -- **Projects/Contexts:** [[현대 웹 애플리케이션 설계]], [[엔터프라이즈 소프트웨어 개발]] +- **Related Topics:** [[관심사의 분리 (Separation of Concerns)|관심사의 분리 (Separation of Concerns)]], [[의존성 주입 (Dependency Injection)|의존성 주입 (Dependency Injection)]], [[MVC (Model-View-Controller)|MVC (Model-View-Controller)]], [[클린 아키텍처 (Clean Architecture)|클린 아키텍처 (Clean Architecture)]] +- **Projects/Contexts:** [[현대 웹 애플리케이션 설계|현대 웹 애플리케이션 설계]], [[엔터프라이즈 소프트웨어 개발|엔터프라이즈 소프트웨어 개발]] - **Contradictions/Notes:** 3계층 구조와 같은 계층화 아키텍처는 명확한 분리를 통해 유지보수성과 확장성을 높여주지만, 초기 개발 시 계층과 추상화를 정의하고 구현해야 하므로 개발 시간이 증가할 수 있으며, 자칫 과도한 엔지니어링(Over-Engineering)으로 인해 시스템 구조가 불필요하게 비대해질 위험도 존재합니다 [7]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/웹 애플리케이션의 3계층 구조.md]] +- Raw Source: 00_Raw/2026-04-20/웹 애플리케이션의 3계층 구조.md --- diff --git a/01_Archive/2026-04-20/웹 워커 이벤트 포워딩 Event Forwarding.md b/01_Archive/2026-04-20/웹 워커 이벤트 포워딩 Event Forwarding.md index 5ca78e8d..58e9c651 100644 --- a/01_Archive/2026-04-20/웹 워커 이벤트 포워딩 Event Forwarding.md +++ b/01_Archive/2026-04-20/웹 워커 이벤트 포워딩 Event Forwarding.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-7669FA -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 웹 워커 이벤트 포워딩 Event Forwarding" --- -# [[웹 워커 이벤트 포워딩 Event Forwarding]] +# [[웹 워커 이벤트 포워딩 Event Forwarding|웹 워커 이벤트 포워딩 Event Forwarding]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 웹 워커(Web Worker)는 DOM API에 직접 접근할 수 없기 때문에, 메인 스레드의 캔버스에서 발생한 마우스 및 터치 이벤트를 캡처하여 필요한 좌표와 상태 데이터만 추출한 뒤 `postMessage`를 통해 워커 스레드로 전달(Forwarding)하여 상호작용을 대리 처리하는 기법입니다. @@ -58,12 +58,12 @@ self.onmessage = function (evt) { - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[OffscreenCanvas]], [[Web Worker postMessage 동기화]], [[대리 인터랙션 (Proxy Interaction)]], [[Raycasting을 통한 3D 객체 선택]] -- **Projects/Contexts:** [[Konva의 Offscreen Canvas 및 이벤트 포워딩 구현]], [[react-three-offscreen 기반 DOM 이벤트 패치]] +- **Related Topics:** [[OffscreenCanvas|OffscreenCanvas]], Web Worker postMessage 동기화, 대리 인터랙션 (Proxy Interaction), Raycasting을 통한 3D 객체 선택 +- **Projects/Contexts:** Konva의 Offscreen Canvas 및 이벤트 포워딩 구현, react-three-offscreen 기반 DOM 이벤트 패치 - **Contradictions/Notes:** 이벤트 포워딩 방식은 메인 스레드와 워커 간의 통신이므로 직렬화 및 메시지 패싱에 따른 지연(약간의 오버헤드)이 발생합니다. 마우스나 터치 이벤트 발생 빈도 정도는 일반적으로 성능 저하를 일으키지 않으나, 과도하게 많은 이벤트 데이터(예: 수천 번의 `mousemove`)가 발생할 경우 스로틀링(Throttling) 기법을 함께 적용하여 메시지 큐의 병목을 막는 것이 안전합니다. --- _Last updated: 2026-04-14_ -- Raw Source: [[00_Raw/2026-04-20/웹 워커 이벤트 포워딩 Event Forwarding.md]] +- Raw Source: 00_Raw/2026-04-20/웹 워커 이벤트 포워딩 Event Forwarding.md --- diff --git a/01_Archive/2026-04-20/웹 워커 이벤트 포워딩 통신 지연 최소화 방법.md b/01_Archive/2026-04-20/웹 워커 이벤트 포워딩 통신 지연 최소화 방법.md index 3e705596..99c8c530 100644 --- a/01_Archive/2026-04-20/웹 워커 이벤트 포워딩 통신 지연 최소화 방법.md +++ b/01_Archive/2026-04-20/웹 워커 이벤트 포워딩 통신 지연 최소화 방법.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-A787BF -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 웹 워커 이벤트 포워딩 통신 지연 최소화 방법" --- -# [[웹 워커 이벤트 포워딩 통신 지연 최소화 방법]] +# [[웹 워커 이벤트 포워딩 통신 지연 최소화 방법|웹 워커 이벤트 포워딩 통신 지연 최소화 방법]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 웹 워커로 이벤트를 포워딩할 때 발생하는 직렬화 및 메시지 패싱 지연을 줄이려면, 이벤트 발생 빈도를 제어(스로틀링)하고 전송하는 페이로드의 크기를 최소화하며, 극한의 성능이 필요할 경우 `SharedArrayBuffer`를 활용해야 합니다. @@ -26,12 +26,12 @@ github_commit: "[P-Reinforce] Continuous Worker - 웹 워커 이벤트 포워딩 - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Throttling & Debouncing]], [[postMessage 직렬화 최적화]], [[SharedArrayBuffer (Zero-Copy)]], [[Proxy 상태 동기화 (Valtio)]] -- **Projects/Contexts:** [[OffscreenCanvas 기반 대리 인터랙션(Proxy Interaction) 구현]], [[고성능 실시간 상호작용 웹 게임 아키텍처]] +- **Related Topics:** [[Throttling & Debouncing|Throttling & Debouncing]], postMessage 직렬화 최적화, SharedArrayBuffer (Zero-Copy), Proxy 상태 동기화 (Valtio) +- **Projects/Contexts:** OffscreenCanvas 기반 대리 인터랙션(Proxy Interaction) 구현, 고성능 실시간 상호작용 웹 게임 아키텍처 - **Contradictions/Notes:** 스로틀링을 너무 강하게 걸면 메시지 큐의 지연은 줄어들지만, 반대로 워커 스레드에서 렌더링되는 3D 모델이나 화면 조작이 뚝뚝 끊기는(Stuttering) 느낌을 줄 수 있습니다. 따라서 화면 주사율(예: 60FPS 기준 약 16.67ms)에 맞게 적절한 전송 주기를 타협하는 것이 중요합니다. --- _Last updated: 2026-04-14_ -- Raw Source: [[00_Raw/2026-04-20/웹 워커 이벤트 포워딩 통신 지연 최소화 방법.md]] +- Raw Source: 00_Raw/2026-04-20/웹 워커 이벤트 포워딩 통신 지연 최소화 방법.md --- diff --git a/01_Archive/2026-04-20/웹 프론트엔드 성능 최적화.md b/01_Archive/2026-04-20/웹 프론트엔드 성능 최적화.md index 746b8fb7..ad976c0b 100644 --- a/01_Archive/2026-04-20/웹 프론트엔드 성능 최적화.md +++ b/01_Archive/2026-04-20/웹 프론트엔드 성능 최적화.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-921FA9 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 웹 프론트엔드 성능 최적화" --- -# [[웹 프론트엔드 성능 최적화]] +# [[웹 프론트엔드 성능 최적화|웹 프론트엔드 성능 최적화]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 웹 프론트엔드 성능 최적화는 브라우저 내 JavaScript 엔진의 메모리 관리 및 가비지 컬렉션(GC) 효율을 높여 애플리케이션의 지연(Jank)이나 충돌을 방지하는 과정입니다 [1, 2]. 개발자는 메모리 누수 원인을 식별하고 이를 해결하여 렌더링 파이프라인과 메인 스레드 성능을 원활하게 유지해야 합니다 [2, 3]. 이를 위해 Chrome DevTools와 같은 프로파일링 도구를 적극적으로 활용하여 메모리 할당과 객체 보존 상태를 추적할 수 있습니다 [4, 5]. @@ -27,11 +27,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 웹 프론트엔드 성능 최 - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** `[[메모리 누수 (Memory Leaks)]]`, `[[가비지 컬렉션 (Garbage Collection)]]`, `[[V8 엔진 (V8 Engine)]]`, `[[Chrome DevTools]]`, `[[Orinoco]]` -- **Projects/Contexts:** `[[SPA 라우트 전환 (SPA Route Transitions)]]`, `[[Three-snapshot technique]]`, `[[Allocation Timeline]]` +- **Related Topics:** `[[메모리 누수(Memory Leaks)|메모리 누수 (Memory Leaks)]]`, `[[가비지 컬렉션 (Garbage Collection)|가비지 컬렉션 (Garbage Collection)]]`, `[[V8 엔진 (V8 Engine)|V8 엔진 (V8 Engine)]]`, `[[Chrome DevTools|Chrome DevTools]]`, `[[Orinoco|Orinoco]]` +- **Projects/Contexts:** `SPA 라우트 전환 (SPA Route Transitions)`, `Three-snapshot technique`, `[[Allocation Timeline|Allocation Timeline]]` - **Contradictions/Notes:** WeakRef나 FinalizationRegistry와 같은 최신 도구들은 메모리 누수를 줄이는 데 도움을 줄 수 있지만, 가비지 컬렉터의 실행이 자체적인 일정에 따라 비결정적(Non-deterministic)으로 동작하므로 애플리케이션의 적절한 수명 주기 관리(Lifecycle management)를 완전히 대체할 수는 없습니다 [9]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/웹 프론트엔드 성능 최적화.md]] +- Raw Source: 00_Raw/2026-04-20/웹 프론트엔드 성능 최적화.md --- diff --git a/01_Archive/2026-04-20/유기적 통합 이론 (Organismic Integration Theory).md b/01_Archive/2026-04-20/유기적 통합 이론 (Organismic Integration Theory).md index 16373d9b..0a544b48 100644 --- a/01_Archive/2026-04-20/유기적 통합 이론 (Organismic Integration Theory).md +++ b/01_Archive/2026-04-20/유기적 통합 이론 (Organismic Integration Theory).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-ED2A29 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 유기적 통합 이론 (Organismic Integration Theory)" --- -# [[유기적 통합 이론 (Organismic Integration Theory)]] +# [[유기적 통합 이론 (Organismic Integration Theory)|유기적 통합 이론 (Organismic Integration Theory)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - 유기적 통합 이론 (Organ ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/유기적 통합 이론 (Organismic Integration Theory).md]] +- Raw Source: 00_Raw/2026-04-20/유기적 통합 이론 (Organismic Integration Theory).md --- diff --git a/01_Archive/2026-04-20/유능감 및 자율성 욕구.md b/01_Archive/2026-04-20/유능감 및 자율성 욕구.md index c8b2f593..d03f69a2 100644 --- a/01_Archive/2026-04-20/유능감 및 자율성 욕구.md +++ b/01_Archive/2026-04-20/유능감 및 자율성 욕구.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-E8E212 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 유능감 및 자율성 욕구" --- -# [[유능감 및 자율성 욕구]] +# [[유능감 및 자율성 욕구|유능감 및 자율성 욕구]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - 유능감 및 자율성 욕구 ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/유능감 및 자율성 욕구.md]] +- Raw Source: 00_Raw/2026-04-20/유능감 및 자율성 욕구.md --- diff --git a/01_Archive/2026-04-20/유니언 타입 식별 및 상태 분기 처리.md b/01_Archive/2026-04-20/유니언 타입 식별 및 상태 분기 처리.md index 95322eca..15ea4f4b 100644 --- a/01_Archive/2026-04-20/유니언 타입 식별 및 상태 분기 처리.md +++ b/01_Archive/2026-04-20/유니언 타입 식별 및 상태 분기 처리.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-2547B3 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 유니언 타입 식별 및 상태 분기 처리" --- -# [[유니언 타입 식별 및 상태 분기 처리]] +# [[유니언 타입 식별 및 상태 분기 처리|유니언 타입 식별 및 상태 분기 처리]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -30,11 +30,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 유니언 타입 식별 및 - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[유니언 타입 (Union Types)]], [[타입 좁히기 (Type Narrowing)]], [[완전성 검사 (Exhaustiveness Checking)]], [[never 타입]] -- **Projects/Contexts:** [[상태 머신 (State Machine) 모델링]], [[Redux 리듀서 패턴]], [[API 응답 데이터 타입 처리]] +- **Related Topics:** 유니언 타입 (Union Types), [[타입 좁히기 (Type Narrowing)|타입 좁히기 (Type Narrowing)]], [[완전성 검사 (Exhaustiveness Checking)|완전성 검사 (Exhaustiveness Checking)]], [[never 타입|never 타입]] +- **Projects/Contexts:** 상태 머신 (State Machine) 모델링, Redux 리듀서 패턴, API 응답 데이터 타입 처리 - **Contradictions/Notes:** 소스 [16, 17, 19]는 `ts-pattern` 라이브러리가 복잡한 분기와 패턴 매칭을 간결하게 작성하는 데 유용하다고 소개하지만, 동시에 기본 제어 구조인 `if/else`나 `switch`에 비해 연산 속도가 상당히 느리므로 단순한 분기에서는 과도한 최적화(오버엔지니어링)가 될 수 있으며 네이티브 제어문을 사용하는 것이 더 적합하다고 주장합니다. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/유니언 타입 식별 및 상태 분기 처리.md]] +- Raw Source: 00_Raw/2026-04-20/유니언 타입 식별 및 상태 분기 처리.md --- diff --git a/01_Archive/2026-04-20/유니온 타입 (Union Types).md b/01_Archive/2026-04-20/유니온 타입 (Union Types).md index cd5b2351..bceca4c4 100644 --- a/01_Archive/2026-04-20/유니온 타입 (Union Types).md +++ b/01_Archive/2026-04-20/유니온 타입 (Union Types).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-E0FAE7 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 유니온 타입 (Union Types)" --- -# [[유니온 타입 (Union Types)]] +# [[유니온 타입 (Union Types)|유니온 타입 (Union Types)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 유니온 타입(Union Types)은 TypeScript에서 값(Value)이 지정된 여러 타입 중 하나일 수 있음을 나타내는 타입 선언 방식이다 [1, 2]. 수직선 기호(`|`)를 사용하여 구성하며, 타입들을 집합(Set)으로 보았을 때 여러 집합의 합집합(Union)에 해당한다 [2, 3]. 변수나 함수의 매개변수가 하나 이상의 유연한 타입을 허용해야 할 때 주로 사용되며, 런타임에 특정한 타입으로 구별하기 위해서는 '타입 좁히기(Type Narrowing)' 과정이 동반되어야 한다 [4-6]. @@ -20,11 +20,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 유니온 타입 (Union Types) - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[식별 가능한 유니온 (Discriminated Unions)]], [[교집합 타입 (Intersection Types)]], [[타입 좁히기 (Type Narrowing)]], [[리터럴 타입 (Literal Types)]] -- **Projects/Contexts:** [[TypeScript 타입 시스템 (TypeScript Type System)]], [[상태 모델링 (State Modeling)]] +- **Related Topics:** [[식별 가능한 유니온 (Discriminated Unions)|식별 가능한 유니온 (Discriminated Unions)]], [[교집합 타입 (Intersection Types)|교집합 타입 (Intersection Types)]], [[타입 좁히기 (Type Narrowing)|타입 좁히기 (Type Narrowing)]], [[리터럴 타입 (Literal Types)|리터럴 타입 (Literal Types)]] +- **Projects/Contexts:** [[TypeScript 타입 시스템 (TypeScript Type System)|TypeScript 타입 시스템 (TypeScript Type System)]], [[상태 모델링 (State Modeling)|상태 모델링 (State Modeling)]] - **Contradictions/Notes:** TypeScript에서 유니온 타입은 값의 유연성을 제공하지만, 조합된 타입들의 공통 프로퍼티가 아닌 고유 프로퍼티를 타입 좁히기 검증 없이 직접 접근하려고 하면 컴파일 에러가 발생하므로 주의해야 한다 [2, 5]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/유니온 타입 (Union Types).md]] +- Raw Source: 00_Raw/2026-04-20/유니온 타입 (Union Types).md --- diff --git a/01_Archive/2026-04-20/유니온 타입(Union Types).md b/01_Archive/2026-04-20/유니온 타입(Union Types).md index 982b9a39..f681a25f 100644 --- a/01_Archive/2026-04-20/유니온 타입(Union Types).md +++ b/01_Archive/2026-04-20/유니온 타입(Union Types).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-981211 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 유니온 타입(Union Types)" --- -# [[유니온 타입(Union Types)]] +# [[유니온 타입(Union Types)|유니온 타입(Union Types)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 유니온 타입(Union Types)은 값이 여러 가지 지정된 타입 중 하나일 수 있음을 나타내는 TypeScript의 핵심 타입 기능입니다 [1, 2]. 수직선 기호(`|`)를 사용하여 각 타입을 구분하며(예: `number | string`), 함수 매개변수나 변수가 다양한 형태의 데이터를 수용해야 할 때 유용하게 쓰입니다 [1, 3]. 유니온 타입은 여러 데이터 타입의 가능성을 열어두면서도, `any` 타입을 사용하는 것보다 훨씬 더 엄격한 타입 안정성을 제공합니다 [1]. @@ -29,11 +29,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 유니온 타입(Union Types)" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Intersection Types(교집합 타입)]], [[Discriminated Unions(식별 가능한 유니온)]], [[Type Narrowing(타입 좁히기)]], [[never 타입]] -- **Projects/Contexts:** [[React State Management(리액트 상태 관리)]], [[API Response Handling(API 응답 처리)]], [[Redux Reducers(리덕스 리듀서)]] +- **Related Topics:** Intersection Types(교집합 타입), Discriminated Unions(식별 가능한 유니온), Type Narrowing(타입 좁히기), [[never 타입|never 타입]] +- **Projects/Contexts:** React State Management(리액트 상태 관리), API Response Handling(API 응답 처리), Redux Reducers(리덕스 리듀서) - **Contradictions/Notes:** TypeScript에서 값을 다형적으로 수용할 수 있게 해준다는 점에서는 `any` 타입과 비슷해 보일 수 있으나, `any`는 모든 타입 체킹 제약이 풀려버리는 반면, 유니온 타입은 오직 정의된 타입들 사이에서의 가능성만 허용하기 때문에 코드의 타입 안전성을 강력하게 유지합니다 [1, 23]. 또한 값이 명확히 정해진 세트 중 하나임을 알 수 있는 경우, 별도의 클래스 계층구조나 `any`를 사용하는 것보다 유니온 타입을 사용하는 것이 훨씬 적합합니다 [1, 23, 24]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/유니온 타입(Union Types).md]] +- Raw Source: 00_Raw/2026-04-20/유니온 타입(Union Types).md --- diff --git a/01_Archive/2026-04-20/유비쿼터스 언어 (Ubiquitous Language).md b/01_Archive/2026-04-20/유비쿼터스 언어 (Ubiquitous Language).md index 78dee10f..e687d776 100644 --- a/01_Archive/2026-04-20/유비쿼터스 언어 (Ubiquitous Language).md +++ b/01_Archive/2026-04-20/유비쿼터스 언어 (Ubiquitous Language).md @@ -1,19 +1,19 @@ --- id: P-REINFORCE-AUTO-34F79B -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 유비쿼터스 언어 (Ubiquitous Language)" --- -# [[유비쿼터스 언어 (Ubiquitous Language)]] +# [[유비쿼터스 언어 (Ubiquitous Language)|유비쿼터스 언어 (Ubiquitous Language)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 유비쿼터스 언어(Ubiquitous Language)는 소프트웨어 개발 프로젝트의 복잡성을 해결하기 위해 프로젝트에 참여하는 모든 사람이 공통으로 사용하는 공유 언어입니다 [1]. 이는 개발자와 비즈니스 이해관계자(도메인 전문가) 간의 의사소통 격차를 해소하여, 개발된 소프트웨어가 비즈니스의 올바른 문제를 해결할 수 있도록 보장하는 역할을 합니다 [1]. ## 📖 구조화된 지식 (Synthesized Content) -- **도메인 주도 설계(DDD)의 핵심:** 유비쿼터스 언어는 비즈니스 도메인에 대한 깊은 이해를 중심으로 하는 도메인 주도 설계([[Domain-Driven Design (DDD)]]) 접근 방식의 주요 목표 중 하나입니다 [1]. +- **도메인 주도 설계(DDD)의 핵심:** 유비쿼터스 언어는 비즈니스 도메인에 대한 깊은 이해를 중심으로 하는 도메인 주도 설계([[Domain-Driven Design (DDD)|Domain-Driven Design (DDD)]]) 접근 방식의 주요 목표 중 하나입니다 [1]. - **생성 및 적용 범위:** 기술 팀은 도메인 전문가와 긴밀하게 협력하여 용어의 공유집(shared glossary)을 생성하고 유지 관리해야 합니다 [2]. 이렇게 정의된 유비쿼터스 언어는 일상적인 대화, 문서화는 물론 실제 작성되는 코드 자체에도 일관되게 사용되어야 합니다 [2]. - **제한된 컨텍스트(Bounded Contexts) 내의 언어:** 크고 복잡한 도메인은 더 작고 관리하기 쉬운 하위 도메인인 '바운디드 컨텍스트(Bounded Contexts)'로 나뉩니다 [3]. "주문 관리"나 "고객 지원"과 같은 각 컨텍스트는 고유한 모델과 유비쿼터스 언어를 가지며, 이를 통해 시스템 모델을 순수하고 명확하게 집중된 상태로 유지할 수 있습니다 [3]. @@ -22,11 +22,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 유비쿼터스 언어 (Ubiqui - **정책 변화:** AI 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Domain-Driven Design (DDD)]], [[Bounded Contexts]] -- **Projects/Contexts:** [[소프트웨어 아키텍처 설계]] +- **Related Topics:** [[Domain-Driven Design (DDD)|Domain-Driven Design (DDD)]], [[Bounded Contexts|Bounded Contexts]] +- **Projects/Contexts:** [[소프트웨어 아키텍처 설계|소프트웨어 아키텍처 설계]] - **Contradictions/Notes:** 소스 내에 유비쿼터스 언어와 관련하여 대립하거나 상충하는 정보는 없습니다. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/유비쿼터스 언어 (Ubiquitous Language).md]] +- Raw Source: 00_Raw/2026-04-20/유비쿼터스 언어 (Ubiquitous Language).md --- diff --git a/01_Archive/2026-04-20/유스케이스 (Use Cases).md b/01_Archive/2026-04-20/유스케이스 (Use Cases).md index 3b342d42..1707c8f0 100644 --- a/01_Archive/2026-04-20/유스케이스 (Use Cases).md +++ b/01_Archive/2026-04-20/유스케이스 (Use Cases).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-FFC5B7 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 유스케이스 (Use Cases)" --- -# [[유스케이스 (Use Cases)]] +# [[유스케이스 (Use Cases)|유스케이스 (Use Cases)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 유스케이스(Use Cases)는 자동화된 시스템이 사용되는 방법을 설명하고, 애플리케이션에 특화된(application-specific) 업무 규칙을 포함하는 소프트웨어 아키텍처의 핵심 계층입니다 [1, 2]. 이는 사용자의 입력과 출력 및 처리 단계를 기술하며, 엔티티(Entities)와 상호작용하여 특정 비즈니스 목표를 달성하도록 데이터 흐름을 조율(오케스트레이션)합니다 [1-3]. 또한, 사용자 인터페이스나 데이터베이스와 같은 시스템의 외부 세부 구현 사항에 의존하지 않고 철저히 독립적으로 동작하는 특징이 있습니다 [4, 5]. @@ -23,11 +23,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 유스케이스 (Use Cases)" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[엔티티 (Entities)]], [[클린 아키텍처 (Clean Architecture)]], [[업무 규칙 (Business Rules)]] -- **Projects/Contexts:** [[소프트웨어 시스템 설계]], [[계층형 아키텍처 기반 애플리케이션 개발]] +- **Related Topics:** [[엔티티 (Entities)|엔티티 (Entities)]], [[클린 아키텍처 (Clean Architecture)|클린 아키텍처 (Clean Architecture)]], 업무 규칙 (Business Rules) +- **Projects/Contexts:** 소프트웨어 시스템 설계, 계층형 아키텍처 기반 애플리케이션 개발 - **Contradictions/Notes:** 제공된 여러 소스(GeeksforGeeks, 42 Coffee Cups, Catsbi's DLog 등) 간에 모순되는 내용은 없으며, 모두 유스케이스가 애플리케이션에 특화된 비즈니스 로직을 담고 있으며 외부 인프라(DB, UI 등)로부터 반드시 격리되어야 한다는 점을 동일하게 주장하고 있습니다 [1, 3, 4]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/유스케이스 (Use Cases).md]] +- Raw Source: 00_Raw/2026-04-20/유스케이스 (Use Cases).md --- diff --git a/01_Archive/2026-04-20/응용 행동 분석(ABA)] [행동 경제학] [교육 심리학의 행동주의 모델.md b/01_Archive/2026-04-20/응용 행동 분석(ABA)] [행동 경제학] [교육 심리학의 행동주의 모델.md index 7970d89b..a81cf163 100644 --- a/01_Archive/2026-04-20/응용 행동 분석(ABA)] [행동 경제학] [교육 심리학의 행동주의 모델.md +++ b/01_Archive/2026-04-20/응용 행동 분석(ABA)] [행동 경제학] [교육 심리학의 행동주의 모델.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-5A7860 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 응용 행동 분석(ABA)] [행동 경제학] [교육 심리학의 행동주의 모델" --- -# [[응용 행동 분석(ABA)] [행동 경제학] [교육 심리학의 행동주의 모델]] +# [[응용 행동 분석(ABA)] [행동 경제학] [교육 심리학의 행동주의 모델|응용 행동 분석(ABA)] [행동 경제학] [교육 심리학의 행동주의 모델]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - 응용 행동 분석(ABA)] [ ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/응용 행동 분석(ABA)], [행동 경제학], [교육 심리학의 행동주의 모델.md]] +- Raw Source: 00_Raw/2026-04-20/응용 행동 분석(ABA)], [행동 경제학], [교육 심리학의 행동주의 모델.md --- diff --git a/01_Archive/2026-04-20/응용 행동 분석(ABA)], [행동 경제학], [교육 심리학의 행동주의 모델.md b/01_Archive/2026-04-20/응용 행동 분석(ABA)], [행동 경제학], [교육 심리학의 행동주의 모델.md index e302a2da..79e2ac28 100644 --- a/01_Archive/2026-04-20/응용 행동 분석(ABA)], [행동 경제학], [교육 심리학의 행동주의 모델.md +++ b/01_Archive/2026-04-20/응용 행동 분석(ABA)], [행동 경제학], [교육 심리학의 행동주의 모델.md @@ -1,4 +1,4 @@ -[[응용 행동 분석(ABA)], [행동 경제학], [교육 심리학의 행동주의 모델]] +[[응용 행동 분석(ABA)], [행동 경제학], [교육 심리학의 행동주의 모델|응용 행동 분석(ABA)], [행동 경제학], [교육 심리학의 행동주의 모델]] 📌 Brief Summary This topic explores the intersection of behavioral science disciplines that focus on the systematic study, prediction, and modification of observable behaviors. It integrates Applied Behavior Analysis (ABA) for clinical intervention, Behavioral Economics for decision-making processes under cognitive biases, and Behaviorist Models in Educational Psychology for instructional design through reinforcement and conditioning. @@ -24,8 +24,8 @@ This topic explores the intersection of behavioral science disciplines that focu * All three disciplines share a fundamental reliance on the **contingency of reinforcement**: the principle that behavior is shaped by its subsequent consequences within a structured environment. 🔗 Knowledge Connections -* Related Topics: [[Operant Conditioning]], [[Nudge Theory]], [[Cognitive Biases]], [[Reinforcement Schedules]], [[Social Learning Theory]] -* Projects/Contexts: [[Autism Spectrum Disorder (ASD) Intervention]], [[Public Policy Design]], [[Instructional Systems Design (ISD)]], [[Choice Architecture in Digital UX]] +* Related Topics: [[Operant Conditioning|Operant Conditioning]], [[Nudge Theory|Nudge Theory]], [[Cognitive Biases|Cognitive Biases]], [[Reinforcement Schedules|Reinforcement Schedules]], [[Social Learning Theory|Social Learning Theory]] +* Projects/Contexts: [[Autism Spectrum Disorder (ASD) Intervention|Autism Spectrum Disorder (ASD) Intervention]], [[Public Policy Design|Public Policy Design]], [[Instructional Systems Design (ISD)|Instructional Systems Design (ISD)]], [[Choice Architecture in Digital UX|Choice Architecture in Digital UX]] * Contradictions/Notes: A significant tension exists between pure Behaviorism and the "Cognitive Revolution"; while behaviorists focus on observable outputs, modern cognitive psychology emphasizes internal mental processes (mediating variables) that behaviorism traditionally ignores. Last updated: 2026-04-16 \ No newline at end of file diff --git a/01_Archive/2026-04-20/응집도 (Cohesion).md b/01_Archive/2026-04-20/응집도 (Cohesion).md index b7dedead..e80ffba4 100644 --- a/01_Archive/2026-04-20/응집도 (Cohesion).md +++ b/01_Archive/2026-04-20/응집도 (Cohesion).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-2C194C -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 응집도 (Cohesion)" --- -# [[응집도 (Cohesion)]] +# [[응집도 (Cohesion)|응집도 (Cohesion)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 응집도(Cohesion)는 소프트웨어 설계에서 모듈이나 클래스 내의 요소들이 얼마나 밀접하게 관련되어 있고 단일한 목적이나 기능에 집중하고 있는지를 나타내는 척도입니다 [1-3]. 직무의 집합, 세부사항의 수준, 그리고 지역적 유사성의 척도로도 정의됩니다 [4, 5]. 응집도가 높을수록 코드의 가독성과 유지보수성이 향상되며, 반대로 낮을 경우 시스템을 이해하거나 재사용하기 어려워집니다 [3, 6]. 따라서 효과적인 소프트웨어 설계에서는 '**응집도는 높게, 결합도는 낮게**' 유지하는 것이 핵심 원칙입니다 [7, 8]. @@ -33,11 +33,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 응집도 (Cohesion)" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[관심사의 분리 (Separation of Concerns)]], [[결합도 (Coupling)]], [[단일 책임 원칙 (Single Responsibility Principle)]] -- **Projects/Contexts:** [[클린 아키텍처 (Clean Architecture)]], [[마이크로서비스 아키텍처 (MSA)]] +- **Related Topics:** [[관심사의 분리 (Separation of Concerns)|관심사의 분리 (Separation of Concerns)]], [[결합도 (Coupling)|결합도 (Coupling)]], [[단일 책임 원칙 (Single Responsibility Principle)|단일 책임 원칙 (Single Responsibility Principle)]] +- **Projects/Contexts:** [[클린 아키텍처 (Clean Architecture)|클린 아키텍처 (Clean Architecture)]], [[마이크로서비스 아키텍처 (MSA)|마이크로서비스 아키텍처 (MSA)]] - **Contradictions/Notes:** 소스 전반에 걸쳐 응집도에 대한 상반된 의견은 존재하지 않으며, 모든 소프트웨어 공학 문헌에서 "응집도는 높이고 결합도는 낮춰야 한다"는 일관된 설계 방향을 옹호하고 있습니다. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/응집도 (Cohesion).md]] +- Raw Source: 00_Raw/2026-04-20/응집도 (Cohesion).md --- diff --git a/01_Archive/2026-04-20/응집도와 결합도 (Cohesion and Coupling).md b/01_Archive/2026-04-20/응집도와 결합도 (Cohesion and Coupling).md index 54e3e8c7..d3c5f729 100644 --- a/01_Archive/2026-04-20/응집도와 결합도 (Cohesion and Coupling).md +++ b/01_Archive/2026-04-20/응집도와 결합도 (Cohesion and Coupling).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-AECECF -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 응집도와 결합도 (Cohesion and Coupling)" --- -# [[응집도와 결합도 (Cohesion and Coupling)]] +# [[응집도와 결합도 (Cohesion and Coupling)|응집도와 결합도 (Cohesion and Coupling)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > **응집도(Cohesion)**는 모듈 내부의 요소들이 하나의 명확한 목적을 위해 얼마나 밀접하게 관련되어 있는지를 측정하는 척도이며, **결합도(Coupling)**는 모듈 간의 상호 의존성 정도를 나타내는 척도이다 [1], [2], [3]. "관심사의 분리(SoC)" 원칙을 소프트웨어에 적용하는 핵심 과정은 **결합도를 낮추고(Loose Coupling) 응집도를 높이는(High Cohesion)** 것이다 [4], [5]. 이를 달성함으로써 시스템의 복잡성을 줄이고 가독성, 유지보수성, 테스트 가능성을 비약적으로 향상시킬 수 있다 [6], [7], [8]. @@ -36,11 +36,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 응집도와 결합도 (Cohesi - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[단일 책임 원칙 (SRP)]], [[의존성 주입 (Dependency Injection)]], [[스파게티 코드 (Spaghetti Code)]] -- **Projects/Contexts:** [[계층화 아키텍처 (Layered Architecture)]], [[마이크로서비스 아키텍처 (MSA)]] +- **Related Topics:** [[단일 책임 원칙 (SRP)|단일 책임 원칙 (SRP)]], [[의존성 주입 (Dependency Injection)|의존성 주입 (Dependency Injection)]], [[스파게티 코드 (Spaghetti Code)|스파게티 코드 (Spaghetti Code)]] +- **Projects/Contexts:** [[계층화 아키텍처 (Layered Architecture)|계층화 아키텍처 (Layered Architecture)]], [[마이크로서비스 아키텍처 (MSA)|마이크로서비스 아키텍처 (MSA)]] - **Contradictions/Notes:** 세밀한 관심사 분리를 통한 결합도 감소와 응집도 증가가 항상 긍정적인 결과만을 가져오는 것은 아닙니다. 과도하게 세밀한 수준으로 모듈을 쪼개고 분리하면, 복잡한 인디렉션(Indirection)이나 잦은 계층 간 데이터 변환 및 통신 비용 증가 등으로 인해 성능 오버헤드가 발생하거나 오히려 전체 시스템의 추적 가능성을 떨어뜨릴 수 있습니다 [14], [15], [16]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/응집도와 결합도 (Cohesion and Coupling).md]] +- Raw Source: 00_Raw/2026-04-20/응집도와 결합도 (Cohesion and Coupling).md --- diff --git a/01_Archive/2026-04-20/응집도와 결합도.md b/01_Archive/2026-04-20/응집도와 결합도.md index 9e65493e..69e9aee7 100644 --- a/01_Archive/2026-04-20/응집도와 결합도.md +++ b/01_Archive/2026-04-20/응집도와 결합도.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-6D470D -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 응집도와 결합도" --- -# [[응집도와 결합도]] +# [[응집도와 결합도|응집도와 결합도]] ## 📌 한 줄 통찰 (The Karpathy Summary) > **응집도(Cohesion)**와 **결합도(Coupling)**는 소프트웨어 모듈과 컴포넌트가 얼마나 잘 설계되었는지를 평가하는 핵심적인 척도입니다 [1]. 응집도는 모듈 내부의 요소들이 하나의 명확한 목적을 위해 얼마나 밀접하게 관련되어 있는지를 나타내며, 결합도는 모듈 간의 상호 의존성 정도를 의미합니다 [2-4]. 성공적인 소프트웨어 설계와 관심사의 분리(SoC)를 효과적으로 적용하기 위해서는 **'높은 응집도'**와 **'낮은 결합도'**를 지향해야 합니다 [1, 2]. @@ -32,11 +32,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 응집도와 결합도" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[관심사의 분리(Separation of Concerns)]], [[단일 책임 원칙(SRP)]], [[의존성 주입(Dependency Injection)]], [[객체 지향 설계]] -- **Projects/Contexts:** [[모듈화 및 컴포넌트 기반 소프트웨어 개발]], [[마이크로서비스 아키텍처(MSA)]] +- **Related Topics:** [[관심사의 분리(Separation of Concerns)|관심사의 분리(Separation of Concerns)]], [[단일 책임 원칙(SRP)|단일 책임 원칙(SRP)]], [[의존성 주입 (Dependency Injection)|의존성 주입(Dependency Injection)]], 객체 지향 설계 +- **Projects/Contexts:** 모듈화 및 컴포넌트 기반 소프트웨어 개발, [[마이크로서비스 아키텍처 (MSA)|마이크로서비스 아키텍처(MSA)]] - **Contradictions/Notes:** 높은 응집도와 낮은 결합도를 달성하기 위해 관심사를 분리하는 것은 유지보수성을 높이는 훌륭한 접근이지만, 지나치게 세분화된 관심사 분리(미세한 결합도 낮추기 시도)는 종종 불필요한 계층과 함수 호출, 복잡성을 증가시켜 성능 저하나 인지적 오버헤드를 유발할 수 있으므로 상황에 맞는 적절한 균형이 필요합니다 [13-15]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/응집도와 결합도.md]] +- Raw Source: 00_Raw/2026-04-20/응집도와 결합도.md --- diff --git a/01_Archive/2026-04-20/의사결정 속도(Decision Speed).md b/01_Archive/2026-04-20/의사결정 속도(Decision Speed).md index f1805a71..d0ec9f69 100644 --- a/01_Archive/2026-04-20/의사결정 속도(Decision Speed).md +++ b/01_Archive/2026-04-20/의사결정 속도(Decision Speed).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-D12B88 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 의사결정 속도(Decision Speed)" --- -# [[의사결정 속도(Decision Speed)]] +# [[의사결정 속도(Decision Speed)|의사결정 속도(Decision Speed)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -25,11 +25,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 의사결정 속도(Decision S - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[반응 시간(Reaction Time)]], [[인지 부하(Cognitive Load)]] -- **Projects/Contexts:** [[가상현실 엑서게임 사후 영향 연구(VR Exergaming Aftereffects)]], [[e스포츠 인지 상태 평가(eSports Cognitive State Assessment)]] +- **Related Topics:** [[반응 시간(Reaction Time)|반응 시간(Reaction Time)]], 인지 부하(Cognitive Load) +- **Projects/Contexts:** 가상현실 엑서게임 사후 영향 연구(VR Exergaming Aftereffects), e스포츠 인지 상태 평가(eSports Cognitive State Assessment) - **Contradictions/Notes:** 주어진 소스 내에서 의사결정 속도(Decision Speed)는 주로 VR 엑서게임 실험의 하위 측정 지표 및 e스포츠의 요구 역량으로만 다뤄지고 있어, 개념의 이론적 배경이나 심층적인 작동 원리에 대한 소스에 관련 정보가 부족합니다. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/의사결정 속도(Decision Speed).md]] +- Raw Source: 00_Raw/2026-04-20/의사결정 속도(Decision Speed).md --- diff --git a/01_Archive/2026-04-20/의존성 규칙 (Dependency Rule).md b/01_Archive/2026-04-20/의존성 규칙 (Dependency Rule).md index 5f13161d..342f5be6 100644 --- a/01_Archive/2026-04-20/의존성 규칙 (Dependency Rule).md +++ b/01_Archive/2026-04-20/의존성 규칙 (Dependency Rule).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-57A5BA -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 의존성 규칙 (Dependency Rule)" --- -# [[의존성 규칙 (Dependency Rule)]] +# [[의존성 규칙 (Dependency Rule)|의존성 규칙 (Dependency Rule)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 의존성 규칙(Dependency Rule)은 클린 아키텍처(Clean Architecture)의 핵심 원칙으로, 모든 소스 코드 의존성이 반드시 고수준의 핵심 비즈니스 로직을 향해 '안쪽으로만' 향해야 한다는 원칙입니다 [1-3]. 이 규칙은 내부 계층(뇌)이 외부 계층(팔다리)의 존재에 대해 전혀 알지 못하도록 통제하여 시스템의 결합도를 낮추고 독립성을 극대화합니다 [2-4]. 결과적으로 비즈니스의 본질적인 규칙을 UI, 데이터베이스, 프레임워크 등 변동성이 높은 기술적 세부 사항으로부터 완벽하게 격리하고 보호하는 역할을 수행합니다 [1, 4, 5]. @@ -30,11 +30,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 의존성 규칙 (Dependency R - **정책 변화:** Design & Experience 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[클린 아키텍처 (Clean Architecture)]], [[의존성 역전 원칙 (Dependency Inversion Principle, DIP)]], [[엔티티 (Entities)]], [[유스케이스 (Use Cases)]] -- **Projects/Contexts:** [[엔터프라이즈 소프트웨어 시스템 설계]], [[모듈화 및 아키텍처 경계 설정]] +- **Related Topics:** [[클린 아키텍처 (Clean Architecture)|클린 아키텍처 (Clean Architecture)]], [[의존성 역전 원칙 (Dependency Inversion Principle, DIP)|의존성 역전 원칙 (Dependency Inversion Principle, DIP)]], [[엔티티 (Entities)|엔티티 (Entities)]], [[유스케이스 (Use Cases)|유스케이스 (Use Cases)]] +- **Projects/Contexts:** [[엔터프라이즈 소프트웨어 시스템 설계|엔터프라이즈 소프트웨어 시스템 설계]], [[모듈화 및 아키텍처 경계 설정|모듈화 및 아키텍처 경계 설정]] - **Contradictions/Notes:** 의존성 규칙을 엄격하게 준수하기 위해 완벽한 아키텍처 경계(쌍방향 다형적 인터페이스, 분리된 입/출력 데이터 구조 등)를 만드는 것은 초기 설정 및 유지보수 비용이 상당히 큽니다 [11]. 따라서 모든 상황에 이 규칙을 엄격히 적용하기보다는, 프로젝트의 규모에 따라 전략 패턴이나 퍼사드(Facade) 패턴을 활용한 부분적 경계(Partial Boundary)를 두거나 실무적 타협을 하는 경우도 존재합니다 [11-13]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/의존성 규칙 (Dependency Rule).md]] +- Raw Source: 00_Raw/2026-04-20/의존성 규칙 (Dependency Rule).md --- diff --git a/01_Archive/2026-04-20/의존성 역전 (Dependency Inversion).md b/01_Archive/2026-04-20/의존성 역전 (Dependency Inversion).md index 465bdde8..b017ea6d 100644 --- a/01_Archive/2026-04-20/의존성 역전 (Dependency Inversion).md +++ b/01_Archive/2026-04-20/의존성 역전 (Dependency Inversion).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-E2B9C7 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 의존성 역전 (Dependency Inversion)" --- -# [[의존성 역전 (Dependency Inversion)]] +# [[의존성 역전 (Dependency Inversion)|의존성 역전 (Dependency Inversion)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 의존성 역전(Dependency Inversion)은 고수준 모듈이 저수준 모듈에 의존하지 않도록 두 모듈 모두 추상화(인터페이스 등)에 의존하게 만드는 소프트웨어 설계 원칙이다 [1, 2]. 이는 세부 사항이 추상화에 의존하게 만듦으로써 시스템 구성 요소 간의 결합도를 낮추고 모듈성과 유연성을 극대화한다 [2]. @@ -23,11 +23,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 의존성 역전 (Dependency I - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[SOLID 원칙 (SOLID Principles)]], [[관심사의 분리 (Separation of Concerns)]], [[의존성 주입 (Dependency Injection)]], [[인터페이스 (Interfaces)]] -- **Projects/Contexts:** [[클린 아키텍처 (Clean Architecture)]], [[객체 지향 프로그래밍 (OOP)]] +- **Related Topics:** [[SOLID 원칙 (SOLID Principles)|SOLID 원칙 (SOLID Principles)]], [[관심사의 분리 (Separation of Concerns)|관심사의 분리 (Separation of Concerns)]], [[의존성 주입 (Dependency Injection)|의존성 주입 (Dependency Injection)]], 인터페이스 (Interfaces) +- **Projects/Contexts:** [[클린 아키텍처 (Clean Architecture)|클린 아키텍처 (Clean Architecture)]], [[객체 지향 프로그래밍 (OOP)|객체 지향 프로그래밍 (OOP)]] - **Contradictions/Notes:** 의존성 역전은 시스템의 분리와 모듈성을 극대화하지만, 아키텍처 경계를 더 단순하게 구현하기 위해 퍼사드(Facade) 패턴과 같은 부분적 경계를 채택할 경우에는 의존성 역전의 이점이 일부 희생될 수 있다 [8]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/의존성 역전 (Dependency Inversion).md]] +- Raw Source: 00_Raw/2026-04-20/의존성 역전 (Dependency Inversion).md --- diff --git a/01_Archive/2026-04-20/의존성 역전 원칙 (DIP).md b/01_Archive/2026-04-20/의존성 역전 원칙 (DIP).md index 3665659e..ad1695c9 100644 --- a/01_Archive/2026-04-20/의존성 역전 원칙 (DIP).md +++ b/01_Archive/2026-04-20/의존성 역전 원칙 (DIP).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-8D5E45 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 의존성 역전 원칙 (DIP)" --- -# [[의존성 역전 원칙 (DIP)]] +# [[의존성 역전 원칙 (DIP)|의존성 역전 원칙 (DIP)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 의존성 역전 원칙(DIP, Dependency Inversion Principle)은 객체 지향 프로그래밍의 SOLID 설계 원칙 중 하나로, 상위 수준의 모듈이 하위 수준의 모듈에 의존해서는 안 되며 양쪽 모두 추상화(예: 인터페이스)에 의존해야 한다는 원칙이다 [1, 2]. 이 원칙은 추상화가 세부 사항에 의존하는 것이 아니라, 세부 사항이 추상화에 의존해야 함을 강조한다 [2]. 이를 통해 시스템 구성 요소 간의 결합도를 낮추고 모듈성을 증가시켜, 유연성과 테스트 가능성을 크게 향상시킨다 [2, 3]. @@ -27,11 +27,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 의존성 역전 원칙 (DIP)" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[SOLID 원칙]], [[의존성 주입 (DI)]], [[추상화]], [[객체 지향 프로그래밍 (OOP)]] -- **Projects/Contexts:** [[클린 아키텍처]], [[소프트웨어 아키텍처 설계]] +- **Related Topics:** [[SOLID 원칙|SOLID 원칙]], [[의존성 주입 (DI)|의존성 주입 (DI)]], [[추상화|추상화]], [[객체 지향 프로그래밍 (OOP)|객체 지향 프로그래밍 (OOP)]] +- **Projects/Contexts:** [[클린 아키텍처|클린 아키텍처]], [[소프트웨어 아키텍처 설계|소프트웨어 아키텍처 설계]] - **Contradictions/Notes:** 관심사 분리(SoC) 원칙은 기능을 기반으로 코드를 어떻게 구성하고 나눌 것인지에 초점을 맞추는 반면, 의존성 역전 원칙(DIP)은 상위 모듈과 하위 모듈 간의 결합을 분리(decoupling)하여 시스템의 유연성과 테스트 가능성을 향상시키는 데 목적을 둔다는 점에서 두 원칙의 초점이 구분된다 [3]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/의존성 역전 원칙 (DIP).md]] +- Raw Source: 00_Raw/2026-04-20/의존성 역전 원칙 (DIP).md --- diff --git a/01_Archive/2026-04-20/의존성 역전 원칙 (Dependency Inversion Principle DIP).md b/01_Archive/2026-04-20/의존성 역전 원칙 (Dependency Inversion Principle DIP).md index 9c77f96d..3102dbbb 100644 --- a/01_Archive/2026-04-20/의존성 역전 원칙 (Dependency Inversion Principle DIP).md +++ b/01_Archive/2026-04-20/의존성 역전 원칙 (Dependency Inversion Principle DIP).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-9D4394 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 의존성 역전 원칙 (Dependency Inversion Principle DIP)" --- -# [[의존성 역전 원칙 (Dependency Inversion Principle DIP)]] +# [[의존성 역전 원칙 (Dependency Inversion Principle DIP)|의존성 역전 원칙 (Dependency Inversion Principle DIP)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 의존성 역전 원칙(DIP)은 객체 지향 프로그래밍 및 소프트웨어 설계의 핵심인 SOLID 원칙 중 하나입니다 [1, 2]. 이 원칙은 상위 수준의 모듈이 하위 수준의 모듈에 의존해서는 안 되며, 양쪽 모두 추상화(예: 인터페이스)에 의존해야 한다고 규정합니다 [3, 4]. 즉, 세부 사항이 추상화에 의존해야 한다는 원칙으로, 이를 통해 모듈 간의 결합도를 낮추고 시스템의 유연성과 테스트 가능성을 크게 향상시킵니다 [4, 5]. @@ -25,11 +25,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 의존성 역전 원칙 (Depen - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[SOLID 원칙]], [[의존성 주입(Dependency Injection)]], [[인터페이스(Interfaces)]], [[관심사 분리(Separation of Concerns, SoC)]] -- **Projects/Contexts:** [[객체 지향 프로그래밍(OOP)]], [[소프트웨어 아키텍처(Software Architecture)]], [[클린 아키텍처(Clean Architecture)]] +- **Related Topics:** [[SOLID 원칙|SOLID 원칙]], [[의존성 주입 (Dependency Injection)|의존성 주입(Dependency Injection)]], 인터페이스(Interfaces), 관심사 분리(Separation of Concerns, SoC) +- **Projects/Contexts:** [[객체 지향 프로그래밍(OOP)|객체 지향 프로그래밍(OOP)]], 소프트웨어 아키텍처(Software Architecture), [[클린 아키텍처(Clean Architecture)|클린 아키텍처(Clean Architecture)]] - **Contradictions/Notes:** 관심사 분리(SoC)와 의존성 역전 원칙(DIP)은 서로를 보완하는 설계 원칙이나 초점이 다릅니다. SoC는 관심사에 따른 코드의 구성과 격리에 집중하는 반면, DIP는 계층 간(상하위 모듈 간)의 디커플링에 목적을 둡니다 [9]. 또한, 퍼사드 패턴(Facade Pattern)과 같이 단순화된 경계를 구축하는 상황에서는 때에 따라 의존성 역전(DIP)의 이점이 희생될 수도 있습니다 [10]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/의존성 역전 원칙 (Dependency Inversion Principle, DIP).md]] +- Raw Source: 00_Raw/2026-04-20/의존성 역전 원칙 (Dependency Inversion Principle, DIP).md --- diff --git a/01_Archive/2026-04-20/의존성 역전 원칙 (Dependency Inversion Principle).md b/01_Archive/2026-04-20/의존성 역전 원칙 (Dependency Inversion Principle).md index 0e279d2a..fb929afc 100644 --- a/01_Archive/2026-04-20/의존성 역전 원칙 (Dependency Inversion Principle).md +++ b/01_Archive/2026-04-20/의존성 역전 원칙 (Dependency Inversion Principle).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-577066 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 의존성 역전 원칙 (Dependency Inversion Principle)" --- -# [[의존성 역전 원칙 (Dependency Inversion Principle)]] +# [[의존성 역전 원칙 (Dependency Inversion Principle)|의존성 역전 원칙 (Dependency Inversion Principle)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 의존성 역전 원칙(Dependency Inversion Principle, DIP)은 객체 지향 프로그래밍을 위한 SOLID 설계 원칙 중 하나로, 상위 수준의 모듈이 하위 수준의 모듈에 의존해서는 안 되며 둘 다 추상화에 의존해야 한다는 소프트웨어 설계 원칙이다 [1-3]. 또한 추상화는 세부 구현에 의존해서는 안 되며, 반대로 세부 구현이 추상화에 의존해야 함을 명시한다 [3]. 이 원칙은 구체적인 구현 대신 인터페이스와 같은 추상화에 의존함으로써 시스템 컴포넌트 간의 느슨한 결합을 유도하고 유연성 및 테스트 가능성을 향상시킨다 [4, 5]. @@ -29,11 +29,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 의존성 역전 원칙 (Depen - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[SOLID 원칙]], [[의존성 주입 (Dependency Injection)]], [[관심사의 분리 (Separation of Concerns)]] -- **Projects/Contexts:** [[객체 지향 프로그래밍 (Object-Oriented Programming)]], [[클린 아키텍처 (Clean Architecture)]] -- **Contradictions/Notes:** 소스 내에서 의존성 역전 원칙 자체에 대한 직접적인 반대 의견이나 모순은 발견되지 않는다. 다만, 소프트웨어 설계 원칙 중 [[관심사의 분리 (Separation of Concerns)]]와 비교할 때, SoC는 기능에 따라 코드를 구성하는 것에 초점을 맞추는 반면, DIP는 유연성과 테스트 가능성을 높이기 위해 상위-하위 모듈 간의 결합을 분리하는 데 집중한다는 목적의 차이가 명시되어 있다 [4, 5]. +- **Related Topics:** [[SOLID 원칙|SOLID 원칙]], [[의존성 주입 (Dependency Injection)|의존성 주입 (Dependency Injection)]], [[관심사의 분리 (Separation of Concerns)|관심사의 분리 (Separation of Concerns)]] +- **Projects/Contexts:** [[객체 지향 프로그래밍 (Object-Oriented Programming)|객체 지향 프로그래밍 (Object-Oriented Programming)]], [[클린 아키텍처 (Clean Architecture)|클린 아키텍처 (Clean Architecture)]] +- **Contradictions/Notes:** 소스 내에서 의존성 역전 원칙 자체에 대한 직접적인 반대 의견이나 모순은 발견되지 않는다. 다만, 소프트웨어 설계 원칙 중 [[관심사의 분리 (Separation of Concerns)|관심사의 분리 (Separation of Concerns)]]와 비교할 때, SoC는 기능에 따라 코드를 구성하는 것에 초점을 맞추는 반면, DIP는 유연성과 테스트 가능성을 높이기 위해 상위-하위 모듈 간의 결합을 분리하는 데 집중한다는 목적의 차이가 명시되어 있다 [4, 5]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/의존성 역전 원칙 (Dependency Inversion Principle).md]] +- Raw Source: 00_Raw/2026-04-20/의존성 역전 원칙 (Dependency Inversion Principle).md --- diff --git a/01_Archive/2026-04-20/의존성 역전 원칙 (Dependency Inversion Principle, DIP).md b/01_Archive/2026-04-20/의존성 역전 원칙 (Dependency Inversion Principle, DIP).md index 6a15a9cd..afbef2ca 100644 --- a/01_Archive/2026-04-20/의존성 역전 원칙 (Dependency Inversion Principle, DIP).md +++ b/01_Archive/2026-04-20/의존성 역전 원칙 (Dependency Inversion Principle, DIP).md @@ -1,4 +1,4 @@ -# [[의존성 역전 원칙 (Dependency Inversion Principle, DIP)]] +# [[의존성 역전 원칙 (Dependency Inversion Principle, DIP)|의존성 역전 원칙 (Dependency Inversion Principle, DIP)]] ## 📌 Brief Summary 의존성 역전 원칙(DIP)은 객체 지향 프로그래밍 및 소프트웨어 설계의 핵심인 SOLID 원칙 중 하나입니다 [1, 2]. 이 원칙은 상위 수준의 모듈이 하위 수준의 모듈에 의존해서는 안 되며, 양쪽 모두 추상화(예: 인터페이스)에 의존해야 한다고 규정합니다 [3, 4]. 즉, 세부 사항이 추상화에 의존해야 한다는 원칙으로, 이를 통해 모듈 간의 결합도를 낮추고 시스템의 유연성과 테스트 가능성을 크게 향상시킵니다 [4, 5]. @@ -12,8 +12,8 @@ - **관심사 분리(SoC)와의 비교:** 관심사 분리(SoC)가 기능을 기반으로 코드를 구성하는 데 초점을 맞추는 반면, DIP는 유연성과 테스트 가능성을 향상시키기 위해 상위 모듈과 하위 모듈 간의 결합을 끊어내는(decoupling) 데 초점을 맞춘다는 명확한 차이가 있습니다 [5, 9]. ## 🔗 Knowledge Connections -- **Related Topics:** [[SOLID 원칙]], [[의존성 주입(Dependency Injection)]], [[인터페이스(Interfaces)]], [[관심사 분리(Separation of Concerns, SoC)]] -- **Projects/Contexts:** [[객체 지향 프로그래밍(OOP)]], [[소프트웨어 아키텍처(Software Architecture)]], [[클린 아키텍처(Clean Architecture)]] +- **Related Topics:** [[SOLID 원칙|SOLID 원칙]], [[의존성 주입 (Dependency Injection)|의존성 주입(Dependency Injection)]], 인터페이스(Interfaces), 관심사 분리(Separation of Concerns, SoC) +- **Projects/Contexts:** [[객체 지향 프로그래밍(OOP)|객체 지향 프로그래밍(OOP)]], 소프트웨어 아키텍처(Software Architecture), [[클린 아키텍처(Clean Architecture)|클린 아키텍처(Clean Architecture)]] - **Contradictions/Notes:** 관심사 분리(SoC)와 의존성 역전 원칙(DIP)은 서로를 보완하는 설계 원칙이나 초점이 다릅니다. SoC는 관심사에 따른 코드의 구성과 격리에 집중하는 반면, DIP는 계층 간(상하위 모듈 간)의 디커플링에 목적을 둡니다 [9]. 또한, 퍼사드 패턴(Facade Pattern)과 같이 단순화된 경계를 구축하는 상황에서는 때에 따라 의존성 역전(DIP)의 이점이 희생될 수도 있습니다 [10]. --- diff --git a/01_Archive/2026-04-20/의존성 주입 (DI).md b/01_Archive/2026-04-20/의존성 주입 (DI).md index ab91006d..9cdfa5cd 100644 --- a/01_Archive/2026-04-20/의존성 주입 (DI).md +++ b/01_Archive/2026-04-20/의존성 주입 (DI).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-0538AE -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 의존성 주입 (DI)" --- -# [[의존성 주입 (DI)]] +# [[의존성 주입 (DI)|의존성 주입 (DI)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 의존성 주입(DI, Dependency Injection)은 모듈이나 클래스가 필요로 하는 의존성을 내부에서 직접 생성하지 않고 외부에서 제공(주입)받도록 하는 소프트웨어 설계 기법입니다 [1, 2]. 이는 객체 지향 프로그래밍의 주요 원칙인 의존성 역전 원칙(DIP)을 구현하는 대표적인 방법으로 사용됩니다 [3]. 컴포넌트 간의 결합도를 낮추고 모듈성을 높여 시스템의 유지보수성과 테스트 용이성을 크게 향상시키는 것이 주된 목적입니다 [4, 5]. @@ -30,11 +30,11 @@ DI는 주로 의존성 역전 원칙(DIP)을 실현하는 수단으로 활용되 - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[의존성 역전 원칙 (DIP)]], [[관심사의 분리 (SoC)]], [[느슨한 결합 (Loose Coupling)]], [[모듈성 (Modularity)]] -- **Projects/Contexts:** [[Spring Framework]], [[ASP.NET Core]], [[클린 아키텍처 (Clean Architecture)]], [[계층형 아키텍처 (Layered Architecture)]] +- **Related Topics:** [[의존성 역전 원칙 (DIP)|의존성 역전 원칙 (DIP)]], [[관심사의 분리 (SoC)|관심사의 분리 (SoC)]], [[느슨한 결합 (Loose Coupling)|느슨한 결합 (Loose Coupling)]], 모듈성 (Modularity) +- **Projects/Contexts:** [[Spring Framework|Spring Framework]], [[ASP.NET Core|ASP.NET Core]], [[클린 아키텍처 (Clean Architecture)|클린 아키텍처 (Clean Architecture)]], [[계층형 아키텍처 (Layered Architecture)|계층형 아키텍처 (Layered Architecture)]] - **Contradictions/Notes:** 소스에 따르면, 의존성 주입 프레임워크의 편리함에도 불구하고, 시스템이 프레임워크 자체에 강하게 결합되는 것을 피하기 위해 메인(Main) 컴포넌트 내부로 주입 책임을 철저히 제한해야 한다고 지적합니다 [11]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/의존성 주입 (DI).md]] +- Raw Source: 00_Raw/2026-04-20/의존성 주입 (DI).md --- diff --git a/01_Archive/2026-04-20/의존성 주입 (Dependency Injection).md b/01_Archive/2026-04-20/의존성 주입 (Dependency Injection).md index 36e59dd3..bac15d26 100644 --- a/01_Archive/2026-04-20/의존성 주입 (Dependency Injection).md +++ b/01_Archive/2026-04-20/의존성 주입 (Dependency Injection).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-A38513 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 의존성 주입 (Dependency Injection)" --- -# [[의존성 주입 (Dependency Injection)]] +# [[의존성 주입 (Dependency Injection)|의존성 주입 (Dependency Injection)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 의존성 주입(Dependency Injection, DI)은 모듈이 필요로 하는 의존성 객체를 내부에서 직접 생성하지 않고 외부로부터 제공(주입)받도록 설계하는 소프트웨어 패턴입니다 [1, 2]. 이 기법은 시스템 컴포넌트 간의 결합도를 낮추어 코드의 모듈화를 촉진하며 [2, 3], 궁극적으로 애플리케이션의 유지보수성과 테스트 용이성을 크게 향상시키는 데 목적이 있습니다 [3, 4]. @@ -28,11 +28,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 의존성 주입 (Dependency I - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[의존성 역전 원칙 (Dependency Inversion Principle)]], [[느슨한 결합 (Loose Coupling)]], [[관심사의 분리 (Separation of Concerns)]], [[테스트 용이성 (Testability)]] -- **Projects/Contexts:** [[클린 아키텍처 (Clean Architecture)]], [[계층형 아키텍처 (Layered Architecture)]], [[Spring Framework]], [[ASP.NET Core]] +- **Related Topics:** [[의존성 역전 원칙 (Dependency Inversion Principle)|의존성 역전 원칙 (Dependency Inversion Principle)]], [[느슨한 결합 (Loose Coupling)|느슨한 결합 (Loose Coupling)]], [[관심사의 분리 (Separation of Concerns)|관심사의 분리 (Separation of Concerns)]], [[테스트 용이성 (Testability)|테스트 용이성 (Testability)]] +- **Projects/Contexts:** [[클린 아키텍처 (Clean Architecture)|클린 아키텍처 (Clean Architecture)]], [[계층형 아키텍처 (Layered Architecture)|계층형 아키텍처 (Layered Architecture)]], [[Spring Framework|Spring Framework]], [[ASP.NET Core|ASP.NET Core]] - **Contradictions/Notes:** 제공된 모든 소스는 의존성 주입이 모듈 간의 결합도를 낮추고 테스트 용이성을 극대화한다는 점에서 일치된 견해를 보이고 있으며, 코드의 설계 단계부터 하드 코딩을 지양하고 의존성 주입을 염두에 둘 것을 공통적으로 강조하고 있습니다 [2, 9]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/의존성 주입 (Dependency Injection).md]] +- Raw Source: 00_Raw/2026-04-20/의존성 주입 (Dependency Injection).md --- diff --git a/01_Archive/2026-04-20/의존성 주입(DI).md b/01_Archive/2026-04-20/의존성 주입(DI).md index 3491abdc..4a4c8d2f 100644 --- a/01_Archive/2026-04-20/의존성 주입(DI).md +++ b/01_Archive/2026-04-20/의존성 주입(DI).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-BE99B2 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 의존성 주입(DI)" --- -# [[의존성 주입(DI)]] +# [[의존성 주입(DI)|의존성 주입(DI)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 의존성 주입(DI)은 모듈이 필요한 의존 객체를 직접 생성하지 않고 외부로부터 주입(공급)받도록 하는 소프트웨어 설계 기법입니다 [1-3]. 이는 고수준 모듈과 저수준 모듈의 직접적인 결합을 끊어내고 추상화에 의존하게 만드는 '의존성 역전 원칙(DIP)'을 구현하는 데 자주 사용됩니다 [4]. 이를 통해 컴포넌트 간의 결합도를 낮추고 시스템의 테스트 용이성과 유지보수성을 크게 향상시킬 수 있습니다 [3, 5]. @@ -27,11 +27,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 의존성 주입(DI)" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[의존성 역전 원칙(DIP)]], [[결합도(Coupling)]], [[테스트 용이성(Testability)]], [[단일 책임 원칙(SRP)]] -- **Projects/Contexts:** [[Spring Framework]], [[ASP.NET Core]], [[Google ML 시스템]], [[계층형 아키텍처]], [[클린 아키텍처]] +- **Related Topics:** [[의존성 역전 원칙 (DIP)|의존성 역전 원칙(DIP)]], [[결합도 (Coupling)|결합도(Coupling)]], [[테스트 용이성 (Testability)|테스트 용이성(Testability)]], [[단일 책임 원칙(SRP)|단일 책임 원칙(SRP)]] +- **Projects/Contexts:** [[Spring Framework|Spring Framework]], [[ASP.NET Core|ASP.NET Core]], Google ML 시스템, 계층형 아키텍처, [[클린 아키텍처|클린 아키텍처]] - **Contradictions/Notes:** 소스 전반에 걸쳐 의존성 주입은 시스템의 복잡도를 낮추고 모듈성을 높이는 긍정적인 기법으로 일관되게 권장되고 있으며, 상충하는 주장은 존재하지 않습니다. 다만 클린 아키텍처와 같은 구조에서는 의존성이 외부에서 내부로(저수준에서 고수준으로) 향하도록 의존성 규칙을 철저히 관리해야 한다고 강조합니다 [6, 10]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/의존성 주입(DI).md]] +- Raw Source: 00_Raw/2026-04-20/의존성 주입(DI).md --- diff --git a/01_Archive/2026-04-20/이동 속도(Movement Speed).md b/01_Archive/2026-04-20/이동 속도(Movement Speed).md index 25fe6e44..2d2767b9 100644 --- a/01_Archive/2026-04-20/이동 속도(Movement Speed).md +++ b/01_Archive/2026-04-20/이동 속도(Movement Speed).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-482CBE -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 이동 속도(Movement Speed)" --- -# [[이동 속도(Movement Speed)]] +# [[이동 속도(Movement Speed)|이동 속도(Movement Speed)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 이동 속도(Movement Speed)는 사용자의 반응 시간(Reaction time)을 구성하는 두 가지 주요 요소 중 하나로, 의사결정 속도(Decision speed)와 구분되는 개념입니다 [1]. 구체적으로 인지 및 반응 과제에서 시작 버튼에서 손을 뗀 순간부터 목표 자극(Target stimulus)을 터치할 때까지 소요되는 시간의 중간값(Median duration)으로 정의됩니다 [1]. 제공된 소스에서는 가상현실(VR) 엑서게임(Exergame) 플레이 전후에 나타나는 인지적, 운동적 변화를 평가하는 세부 지표로 활용되었습니다 [1, 2]. @@ -24,11 +24,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 이동 속도(Movement Speed)" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Reaction Time]], [[Decision Speed]] -- **Projects/Contexts:** [[VR Exergaming(가상현실 엑서게임) 평가]], [[CANTAB 5-choice RTI(5-선택 반응 시간 과제)]] +- **Related Topics:** [[반응 시간(Reaction Time)|Reaction Time]], [[결정 속도(Decision Speed)|Decision Speed]] +- **Projects/Contexts:** VR Exergaming(가상현실 엑서게임) 평가, CANTAB 5-choice RTI(5-선택 반응 시간 과제) - **Contradictions/Notes:** 소스에 관련 정보가 부족합니다. (짧은 VR 게임(10분) 직후 이동 속도가 일시적으로 향상되는 현상이 관찰되었으나, 통계적으로 측정 시기나 노출 시간에 따른 뚜렷한 주효과는 입증되지 않아 지속적인 효과로 보기는 어렵다는 점이 언급되었습니다 [2, 3].) --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/이동 속도(Movement Speed).md]] +- Raw Source: 00_Raw/2026-04-20/이동 속도(Movement Speed).md --- diff --git a/01_Archive/2026-04-20/이벤트 기반 아키텍처 (Event-Driven Architecture).md b/01_Archive/2026-04-20/이벤트 기반 아키텍처 (Event-Driven Architecture).md index ae7f7f58..4a5ffc16 100644 --- a/01_Archive/2026-04-20/이벤트 기반 아키텍처 (Event-Driven Architecture).md +++ b/01_Archive/2026-04-20/이벤트 기반 아키텍처 (Event-Driven Architecture).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-980240 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 이벤트 기반 아키텍처 (Event-Driven Architecture)" --- -# [[이벤트 기반 아키텍처 (Event-Driven Architecture)]] +# [[이벤트 기반 아키텍처 (Event-Driven Architecture)|이벤트 기반 아키텍처 (Event-Driven Architecture)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 이벤트 기반 아키텍처(EDA)는 사용자의 클릭, 금융 트랜잭션, 센서 판독과 같은 '이벤트'의 생성과 소비를 통해 시스템 구성 요소들이 비동기적으로 통신하는 강력한 소프트웨어 설계 패러다임입니다 [1, 2]. 전통적인 배치 처리나 직접적인 API 호출 방식과 달리, 데이터가 생성되는 즉시 반응하고 처리하여 시스템 간의 느슨한 결합(Loose coupling)을 촉진합니다 [1-3]. 이를 통해 컴포넌트를 독립적으로 개발, 배포 및 확장할 수 있으며, 예측 불가능한 높은 부하와 실시간 데이터 처리가 요구되는 현대의 분산 시스템에 필수적인 아키텍처로 평가받고 있습니다 [2]. @@ -30,11 +30,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 이벤트 기반 아키텍처 - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Microservices Architecture]], [[Real-time Data Streaming]], [[Message Broker]], [[Apache Kafka]] -- **Projects/Contexts:** [[Real-Time Stock Trading]], [[IoT Data Processing]], [[Microservices Orchestration]] +- **Related Topics:** [[마이크로서비스 아키텍처 (Microservices Architecture)|Microservices Architecture]], [[Real-time-Data-Streaming|Real-time Data Streaming]], Message Broker, Apache Kafka +- **Projects/Contexts:** Real-Time Stock Trading, IoT Data Processing, Microservices Orchestration - **Contradictions/Notes:** 소스에 따르면 이벤트 기반 아키텍처는 고도의 반응성과 확장성을 제공하지만, 분산 시스템 및 스트림 의미론과 관련된 비동기적 복잡성과 실행 순서 관리의 난이도가 높으며 브로커 등 인프라를 구축하고 운영하기 위한 높은 전문 지식이 요구된다는 단점(Implementation Complexity: High)이 존재합니다 [4, 5]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/이벤트 기반 아키텍처 (Event-Driven Architecture).md]] +- Raw Source: 00_Raw/2026-04-20/이벤트 기반 아키텍처 (Event-Driven Architecture).md --- diff --git a/01_Archive/2026-04-20/이벤트 포워딩(Event Forwarding).md b/01_Archive/2026-04-20/이벤트 포워딩(Event Forwarding).md index 6ac7a117..16bbbed9 100644 --- a/01_Archive/2026-04-20/이벤트 포워딩(Event Forwarding).md +++ b/01_Archive/2026-04-20/이벤트 포워딩(Event Forwarding).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-797EC7 -category: "[[10_Wiki/💡 Topics/General Knowledge]]" +category: "10_Wiki/💡 Topics/General Knowledge" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 이벤트 포워딩(Event Forwarding)" --- -# [[이벤트 포워딩(Event Forwarding)]] +# [[이벤트 포워딩(Event Forwarding)|이벤트 포워딩(Event Forwarding)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - 이벤트 포워딩(Event Forw ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/이벤트 포워딩(Event Forwarding).md]] +- Raw Source: 00_Raw/2026-04-20/이벤트 포워딩(Event Forwarding).md --- diff --git a/01_Archive/2026-04-20/이전 세대(Old Generation_Space).md b/01_Archive/2026-04-20/이전 세대(Old Generation_Space).md index bc22b2b2..d8edb5c9 100644 --- a/01_Archive/2026-04-20/이전 세대(Old Generation_Space).md +++ b/01_Archive/2026-04-20/이전 세대(Old Generation_Space).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-7BED1F -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 이전 세대(Old Generation_Space)" --- -# [[이전 세대(Old Generation_Space)]] +# [[이전 세대(Old Generation_Space)|이전 세대(Old Generation_Space)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > V8 엔진의 힙(Heap) 메모리 구조에서 '이전 세대(Old Generation 또는 Old Space)'는 신세대(New Space)에서 발생하는 여러 번의 마이너 가비지 컬렉션(스캐빈지)을 거치고 살아남은, 수명이 긴 객체들이 승격(Promote)되어 저장되는 메모리 공간입니다 [1-4]. 이 공간은 데이터의 특성에 따라 포인터가 있는 공간(Old-pointer-space)과 순수 데이터만 있는 공간(Old-data-space)으로 나뉘며, 메이저 가비지 컬렉터(Major GC)에 의해 관리됩니다 [4-6]. @@ -35,11 +35,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 이전 세대(Old Generation_S - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[New Space (Young Generation)]], [[Major GC (Mark-Sweep / Mark-Compact)]], [[Write Barriers]], [[Generational Hypothesis]] -- **Projects/Contexts:** [[V8 JavaScript Engine]], [[Orinoco Garbage Collector]] +- **Related Topics:** [[New Space(Young Generation)|New Space (Young Generation)]], Major GC (Mark-Sweep / Mark-Compact), Write Barriers, [[Generational Hypothesis|Generational Hypothesis]] +- **Projects/Contexts:** [[V8 JavaScript Engine|V8 JavaScript Engine]], Orinoco Garbage Collector - **Contradictions/Notes:** 소스에 관련 정보가 부족합니다. (소스 전반에서 이전 세대 관리에 대한 설명은 일관되며 명시적인 모순점은 존재하지 않습니다.) --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/이전 세대(Old Generation_Space).md]] +- Raw Source: 00_Raw/2026-04-20/이전 세대(Old Generation_Space).md --- diff --git a/01_Archive/2026-04-20/이커머스의 실시간 재고 관리.md b/01_Archive/2026-04-20/이커머스의 실시간 재고 관리.md index 7cd98df8..ffb41815 100644 --- a/01_Archive/2026-04-20/이커머스의 실시간 재고 관리.md +++ b/01_Archive/2026-04-20/이커머스의 실시간 재고 관리.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-E72D2E -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 이커머스의 실시간 재고 관리" --- -# [[이커머스의 실시간 재고 관리]] +# [[이커머스의 실시간 재고 관리|이커머스의 실시간 재고 관리]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 이커머스의 실시간 재고 관리는 기존의 일괄 처리(batch processing) 방식에서 벗어나, 데이터가 생성되는 즉시 처리하는 실시간 데이터 스트리밍을 활용하는 시스템입니다 [1]. 사용자의 클릭이나 주문 접수와 같은 시스템상의 '이벤트'에 즉각적으로 반응하는 이벤트 기반 아키텍처(Event-Driven Architecture)를 통해 작동합니다 [1]. 이를 통해 구식 정보에 의존하지 않고 즉각적인 통찰력을 얻어 신속한 의사결정과 대응을 가능하게 합니다 [1]. @@ -24,11 +24,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 이커머스의 실시간 재 - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[실시간 데이터 스트리밍]], [[이벤트 기반 아키텍처]], [[마이크로서비스 아키텍처]] +- **Related Topics:** 실시간 데이터 스트리밍, 이벤트 기반 아키텍처, [[마이크로서비스 아키텍처|마이크로서비스 아키텍처]] - **Projects/Contexts:** 이커머스 결제 및 체크아웃 파이프라인 (Apache Kafka 및 AWS Kinesis 활용 사례) [1, 2] - **Contradictions/Notes:** 주어진 소스 내에서 이커머스의 실시간 재고 관리는 현대 데이터 아키텍처(이벤트 스트리밍 등)가 어떻게 사용되는지 보여주는 단편적인 예시로만 다뤄지고 있으므로, 재고 관리 시스템의 전반적인 운영 프로세스에 대해서는 소스에 관련 정보가 부족합니다. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/이커머스의 실시간 재고 관리.md]] +- Raw Source: 00_Raw/2026-04-20/이커머스의 실시간 재고 관리.md --- diff --git a/01_Archive/2026-04-20/인간 요인 공학 (Human Factors Engineering).md b/01_Archive/2026-04-20/인간 요인 공학 (Human Factors Engineering).md index b74ad667..be18e3b7 100644 --- a/01_Archive/2026-04-20/인간 요인 공학 (Human Factors Engineering).md +++ b/01_Archive/2026-04-20/인간 요인 공학 (Human Factors Engineering).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-E342BB -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 인간 요인 공학 (Human Factors Engineering)" --- -# [[인간 요인 공학 (Human Factors Engineering)]] +# [[인간 요인 공학 (Human Factors Engineering)|인간 요인 공학 (Human Factors Engineering)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - 인간 요인 공학 (Human Fa ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/인간 요인 공학 (Human Factors Engineering).md]] +- Raw Source: 00_Raw/2026-04-20/인간 요인 공학 (Human Factors Engineering).md --- diff --git a/01_Archive/2026-04-20/인간-컴퓨터 상호작용 (HCI).md b/01_Archive/2026-04-20/인간-컴퓨터 상호작용 (HCI).md index 2b03a807..28004050 100644 --- a/01_Archive/2026-04-20/인간-컴퓨터 상호작용 (HCI).md +++ b/01_Archive/2026-04-20/인간-컴퓨터 상호작용 (HCI).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-5A206B -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 인간-컴퓨터 상호작용 (HCI)" --- -# [[인간-컴퓨터 상호작용 (HCI)]] +# [[인간-컴퓨터 상호작용 (HCI)|인간-컴퓨터 상호작용 (HCI)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - 인간-컴퓨터 상호작용 ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/인간-컴퓨터 상호작용 (HCI).md]] +- Raw Source: 00_Raw/2026-04-20/인간-컴퓨터 상호작용 (HCI).md --- diff --git a/01_Archive/2026-04-20/인공지능 상호작용 (HAI).md b/01_Archive/2026-04-20/인공지능 상호작용 (HAI).md index bc8e714d..d52ac98d 100644 --- a/01_Archive/2026-04-20/인공지능 상호작용 (HAI).md +++ b/01_Archive/2026-04-20/인공지능 상호작용 (HAI).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-BA3F26 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 인공지능 상호작용 (HAI)" --- -# [[인공지능 상호작용 (HAI)]] +# [[인공지능 상호작용 (HAI)|인공지능 상호작용 (HAI)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - 인공지능 상호작용 (HAI ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/인공지능 상호작용 (HAI).md]] +- Raw Source: 00_Raw/2026-04-20/인공지능 상호작용 (HAI).md --- diff --git a/01_Archive/2026-04-20/인문학적 게임 비평 및 서사학.md b/01_Archive/2026-04-20/인문학적 게임 비평 및 서사학.md index 300a3343..4fd92312 100644 --- a/01_Archive/2026-04-20/인문학적 게임 비평 및 서사학.md +++ b/01_Archive/2026-04-20/인문학적 게임 비평 및 서사학.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-AC421C -category: "[[10_Wiki/💡 Topics/Game Design]]" +category: "10_Wiki/💡 Topics/Game Design" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 인문학적 게임 비평 및 서사학" --- -# [[인문학적 게임 비평 및 서사학]] +# [[인문학적 게임 비평 및 서사학|인문학적 게임 비평 및 서사학]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - 인문학적 게임 비평 및 ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/인문학적 게임 비평 및 서사학.md]] +- Raw Source: 00_Raw/2026-04-20/인문학적 게임 비평 및 서사학.md --- diff --git a/01_Archive/2026-04-20/인문학적 게임 비평 및 서사학12.md b/01_Archive/2026-04-20/인문학적 게임 비평 및 서사학12.md index 7fe75c06..7032d302 100644 --- a/01_Archive/2026-04-20/인문학적 게임 비평 및 서사학12.md +++ b/01_Archive/2026-04-20/인문학적 게임 비평 및 서사학12.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-F20E50 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 인문학적 게임 비평 및 서사학12" --- -# [[인문학적 게임 비평 및 서사학12]] +# [[인문학적 게임 비평 및 서사학12|인문학적 게임 비평 및 서사학12]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - 인문학적 게임 비평 및 ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/인문학적 게임 비평 및 서사학12.md]] +- Raw Source: 00_Raw/2026-04-20/인문학적 게임 비평 및 서사학12.md --- diff --git a/01_Archive/2026-04-20/인적 자원 관리(HRM) 전략 수립.md b/01_Archive/2026-04-20/인적 자원 관리(HRM) 전략 수립.md index d22c43d7..1a3d42c7 100644 --- a/01_Archive/2026-04-20/인적 자원 관리(HRM) 전략 수립.md +++ b/01_Archive/2026-04-20/인적 자원 관리(HRM) 전략 수립.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-AD8C86 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 인적 자원 관리(HRM) 전략 수립" --- -# [[인적 자원 관리(HRM) 전략 수립]] +# [[인적 자원 관리(HRM) 전략 수립|인적 자원 관리(HRM) 전략 수립]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - 인적 자원 관리(HRM) 전 ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/인적 자원 관리(HRM) 전략 수립.md]] +- Raw Source: 00_Raw/2026-04-20/인적 자원 관리(HRM) 전략 수립.md --- diff --git a/01_Archive/2026-04-20/인지 부조화 이론.md b/01_Archive/2026-04-20/인지 부조화 이론.md index 14de5b24..5f62c15c 100644 --- a/01_Archive/2026-04-20/인지 부조화 이론.md +++ b/01_Archive/2026-04-20/인지 부조화 이론.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-CE996D -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 인지 부조화 이론" --- -# [[인지 부조화 이론]] +# [[인지 부조화 이론|인지 부조화 이론]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - 인지 부조화 이론" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/인지 부조화 이론.md]] +- Raw Source: 00_Raw/2026-04-20/인지 부조화 이론.md --- diff --git a/01_Archive/2026-04-20/인지 부하 이론(Cognitive Load Theory).md b/01_Archive/2026-04-20/인지 부하 이론(Cognitive Load Theory).md index 6d4193c6..9e0dade9 100644 --- a/01_Archive/2026-04-20/인지 부하 이론(Cognitive Load Theory).md +++ b/01_Archive/2026-04-20/인지 부하 이론(Cognitive Load Theory).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-AA8C86 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 인지 부하 이론(Cognitive Load Theory)" --- -# [[인지 부하 이론(Cognitive Load Theory)]] +# [[인지 부하 이론(Cognitive Load Theory)|인지 부하 이론(Cognitive Load Theory)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - 인지 부하 이론(Cognitive ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/인지 부하 이론(Cognitive Load Theory).md]] +- Raw Source: 00_Raw/2026-04-20/인지 부하 이론(Cognitive Load Theory).md --- diff --git a/01_Archive/2026-04-20/인지 심리학 (Cognitive Psychology).md b/01_Archive/2026-04-20/인지 심리학 (Cognitive Psychology).md index ec1f1ae8..afa277ac 100644 --- a/01_Archive/2026-04-20/인지 심리학 (Cognitive Psychology).md +++ b/01_Archive/2026-04-20/인지 심리학 (Cognitive Psychology).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-30DB87 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 인지 심리학 (Cognitive Psychology)" --- -# [[인지 심리학 (Cognitive Psychology)]] +# [[인지 심리학 (Cognitive Psychology)|인지 심리학 (Cognitive Psychology)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - 인지 심리학 (Cognitive Ps ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/인지 심리학 (Cognitive Psychology).md]] +- Raw Source: 00_Raw/2026-04-20/인지 심리학 (Cognitive Psychology).md --- diff --git a/01_Archive/2026-04-20/인지 평가 이론 (Cognitive Evaluation Theory).md b/01_Archive/2026-04-20/인지 평가 이론 (Cognitive Evaluation Theory).md index a77b6760..75a45ba8 100644 --- a/01_Archive/2026-04-20/인지 평가 이론 (Cognitive Evaluation Theory).md +++ b/01_Archive/2026-04-20/인지 평가 이론 (Cognitive Evaluation Theory).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-C0AA85 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 인지 평가 이론 (Cognitive Evaluation Theory)" --- -# [[인지 평가 이론 (Cognitive Evaluation Theory)]] +# [[인지 평가 이론 (Cognitive Evaluation Theory)|인지 평가 이론 (Cognitive Evaluation Theory)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - 인지 평가 이론 (Cognitiv ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/인지 평가 이론 (Cognitive Evaluation Theory).md]] +- Raw Source: 00_Raw/2026-04-20/인지 평가 이론 (Cognitive Evaluation Theory).md --- diff --git a/01_Archive/2026-04-20/인지 행동 치료 (CBT).md b/01_Archive/2026-04-20/인지 행동 치료 (CBT).md index beb72a87..97b2e62d 100644 --- a/01_Archive/2026-04-20/인지 행동 치료 (CBT).md +++ b/01_Archive/2026-04-20/인지 행동 치료 (CBT).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-A19886 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 인지 행동 치료 (CBT)" --- -# [[인지 행동 치료 (CBT)]] +# [[인지 행동 치료 (CBT)|인지 행동 치료 (CBT)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - 인지 행동 치료 (CBT)" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/인지 행동 치료 (CBT).md]] +- Raw Source: 00_Raw/2026-04-20/인지 행동 치료 (CBT).md --- diff --git a/01_Archive/2026-04-20/인지행동치료(CBT).md b/01_Archive/2026-04-20/인지행동치료(CBT).md index e26dad98..8eaa70a5 100644 --- a/01_Archive/2026-04-20/인지행동치료(CBT).md +++ b/01_Archive/2026-04-20/인지행동치료(CBT).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-624537 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 인지행동치료(CBT)" --- -# [[인지행동치료(CBT)]] +# [[인지행동치료(CBT)|인지행동치료(CBT)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - 인지행동치료(CBT)" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/인지행동치료(CBT).md]] +- Raw Source: 00_Raw/2026-04-20/인지행동치료(CBT).md --- diff --git a/01_Archive/2026-04-20/인터랙티브 스토리텔링 연구.md b/01_Archive/2026-04-20/인터랙티브 스토리텔링 연구.md index 84b317f7..9b132524 100644 --- a/01_Archive/2026-04-20/인터랙티브 스토리텔링 연구.md +++ b/01_Archive/2026-04-20/인터랙티브 스토리텔링 연구.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-5DBDA2 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 인터랙티브 스토리텔링 연구" --- -# [[인터랙티브 스토리텔링 연구]] +# [[인터랙티브 스토리텔링 연구|인터랙티브 스토리텔링 연구]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - 인터랙티브 스토리텔 ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/인터랙티브 스토리텔링 연구.md]] +- Raw Source: 00_Raw/2026-04-20/인터랙티브 스토리텔링 연구.md --- diff --git a/01_Archive/2026-04-20/인터페이스 (Interface).md b/01_Archive/2026-04-20/인터페이스 (Interface).md index 277757f3..159769a5 100644 --- a/01_Archive/2026-04-20/인터페이스 (Interface).md +++ b/01_Archive/2026-04-20/인터페이스 (Interface).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-DEED85 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 인터페이스 (Interface)" --- -# [[인터페이스 (Interface)]] +# [[인터페이스 (Interface)|인터페이스 (Interface)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > TypeScript에서 인터페이스(Interface)는 객체의 형태(Shape)를 정의하고 내부 및 외부 코드 간의 계약(Contract)을 명시하는 구조적 타이핑(Structural Typing) 도구입니다 [1, 2]. 선택적 속성(Optional)과 읽기 전용 속성(Readonly) 등을 통해 유연하면서도 안전한 데이터 구조를 모델링할 수 있습니다 [2-4]. Type Alias와 비교할 때 캐싱 및 평탄화를 통해 컴파일 성능상 이점을 제공하며, 선언 병합(Declaration Merging)이라는 고유한 확장 기능을 갖추고 있습니다 [5-7]. @@ -20,11 +20,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 인터페이스 (Interface)" - **정책 변화:** Design & Experience 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Type Alias]], [[구조적 타이핑 (Structural Typing)]], [[선언 병합 (Declaration Merging)]], [[Interface Segregation Principle (ISP)]], [[객체 타입 (Object Types)]] -- **Projects/Contexts:** [[대규모 TypeScript 애플리케이션 아키텍처 설계]], [[라이브러리 타입 선언 (d.ts) 확장]] +- **Related Topics:** [[Type Alias|Type Alias]], [[구조적 타이핑 (Structural Typing)|구조적 타이핑 (Structural Typing)]], [[선언 병합 (Declaration Merging)|선언 병합 (Declaration Merging)]], [[Interface Segregation Principle (ISP)|Interface Segregation Principle (ISP)]], 객체 타입 (Object Types) +- **Projects/Contexts:** [[대규모 TypeScript 애플리케이션 아키텍처 설계|대규모 TypeScript 애플리케이션 아키텍처 설계]], [[라이브러리 타입 선언 (d.ts) 확장|라이브러리 타입 선언 (d.ts) 확장]] - **Contradictions/Notes:** 인터페이스의 핵심 기능 중 하나인 '선언 병합'에 대하여, 라이브러리 확장을 위해서는 매우 유용하다는 주장이 있지만, 일반적인 애플리케이션 코드베이스에서는 의도치 않게 호환되지 않는 필드가 병합되어 버그를 유발할 수 있으므로 병합 기능이 없는 `type` 사용을 선호하는 개발자들도 다수 존재합니다 [14, 19-22]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/인터페이스 (Interface).md]] +- Raw Source: 00_Raw/2026-04-20/인터페이스 (Interface).md --- diff --git a/01_Archive/2026-04-20/인터페이스 분리 원칙 (Interface Segregation Principle).md b/01_Archive/2026-04-20/인터페이스 분리 원칙 (Interface Segregation Principle).md index b810b720..d4a89e61 100644 --- a/01_Archive/2026-04-20/인터페이스 분리 원칙 (Interface Segregation Principle).md +++ b/01_Archive/2026-04-20/인터페이스 분리 원칙 (Interface Segregation Principle).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-FD8793 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 인터페이스 분리 원칙 (Interface Segregation Principle)" --- -# [[인터페이스 분리 원칙 (Interface Segregation Principle)]] +# [[인터페이스 분리 원칙 (Interface Segregation Principle)|인터페이스 분리 원칙 (Interface Segregation Principle)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 인터페이스 분리 원칙(ISP)은 객체 지향 프로그래밍(OOP)을 위한 5가지 기본 설계 원칙인 SOLID 중 하나로, 로버트 C. 마틴(Robert C. Martin)에 의해 정립되었습니다 [1-3]. 이 원칙은 클라이언트가 자신이 사용하지 않는 인터페이스에 의존하도록 강요받아서는 안 된다는 것을 핵심으로 합니다 [2, 4]. 이를 달성하기 위해 하나의 크고 범용적인 인터페이스 대신, 작고 구체적이며 특화된 인터페이스를 여러 개 설계하는 것을 권장합니다 [2, 4]. @@ -25,11 +25,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 인터페이스 분리 원칙 - **정책 변화:** Design & Experience 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[SOLID Principles]], [[Separation of Concerns (SoC)]], [[Object-Oriented Programming (OOP)]] -- **Projects/Contexts:** [[Clean Architecture]], [[Software System Design]] +- **Related Topics:** [[SOLID Principles|SOLID Principles]], [[관심사의 분리 (Separation of Concerns SoC)|Separation of Concerns (SoC)]], Object-Oriented Programming (OOP) +- **Projects/Contexts:** [[Clean Architecture|Clean Architecture]], Software System Design - **Contradictions/Notes:** 주어진 소스 내에서 인터페이스 분리 원칙에 대한 모순된 주장은 발견되지 않으며, 모든 소스가 이 원칙이 관심사의 분리(SoC) 개념에 뿌리를 두고 있으며 모듈성과 시스템 유연성을 향상시킨다는 점에 동의하고 있습니다. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/인터페이스 분리 원칙 (Interface Segregation Principle).md]] +- Raw Source: 00_Raw/2026-04-20/인터페이스 분리 원칙 (Interface Segregation Principle).md --- diff --git a/01_Archive/2026-04-20/임베딩 (Embedding).md b/01_Archive/2026-04-20/임베딩 (Embedding).md index a015ad28..415506e4 100644 --- a/01_Archive/2026-04-20/임베딩 (Embedding).md +++ b/01_Archive/2026-04-20/임베딩 (Embedding).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-6E92CC -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 임베딩 (Embedding)" --- -# [[임베딩 (Embedding)]] +# [[임베딩 (Embedding)|임베딩 (Embedding)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - 임베딩 (Embedding)" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/임베딩 (Embedding).md]] +- Raw Source: 00_Raw/2026-04-20/임베딩 (Embedding).md --- diff --git a/01_Archive/2026-04-20/임상 심리학의 변화 동기 치료.md b/01_Archive/2026-04-20/임상 심리학의 변화 동기 치료.md index 6bb60c15..92bcc727 100644 --- a/01_Archive/2026-04-20/임상 심리학의 변화 동기 치료.md +++ b/01_Archive/2026-04-20/임상 심리학의 변화 동기 치료.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-EE54A5 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 임상 심리학의 변화 동기 치료" --- -# [[임상 심리학의 변화 동기 치료]] +# [[임상 심리학의 변화 동기 치료|임상 심리학의 변화 동기 치료]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - 임상 심리학의 변화 동 ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/임상 심리학의 변화 동기 치료.md]] +- Raw Source: 00_Raw/2026-04-20/임상 심리학의 변화 동기 치료.md --- diff --git a/01_Archive/2026-04-20/입자 시스템(Particle Systems).md b/01_Archive/2026-04-20/입자 시스템(Particle Systems).md index 2f3c5769..572a9776 100644 --- a/01_Archive/2026-04-20/입자 시스템(Particle Systems).md +++ b/01_Archive/2026-04-20/입자 시스템(Particle Systems).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-1C7197 -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 입자 시스템(Particle Systems)" --- -# [[입자 시스템(Particle Systems)]] +# [[입자 시스템(Particle Systems)|입자 시스템(Particle Systems)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 입자 시스템(Particle Systems)은 게임이나 3D 그래픽 환경에서 유체, 총알, 특수 효과 등 수많은 개체를 효율적으로 렌더링하고 관리하기 위한 기법입니다 [1, 2]. 전통적인 CPU 기반의 입자 업데이트는 연산 한계로 인해 약 5만 개 부근에서 성능 병목에 도달하지만, WebGPU의 컴퓨트 셰이더를 활용하면 처리량을 수백만 개 단위로 끌어올릴 수 있습니다 [1, 3]. 또한 프레임워크에 따라 InstancedMesh나 Solid Particle System(SPS)을 활용하여 드로우 콜(Draw call)을 줄이고 렌더링 성능을 최적화할 수 있습니다 [4-6]. @@ -23,11 +23,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 입자 시스템(Particle Syst - **정책 변화:** Graphics & Performance 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[WebGPU]], [[컴퓨트 셰이더(Compute Shaders)]], [[InstancedMesh]], [[Solid Particle System (SPS)]] -- **Projects/Contexts:** [[Hokusai installation]] - 엑스포 2025 오사카(Expo 2025 Osaka)에서 100만 개의 입자 기반 유체 시뮬레이션을 WebGPU로 구현한 프로젝트입니다 [12]. +- **Related Topics:** [[WebGPU|WebGPU]], [[컴퓨트 셰이더(Compute Shaders)|컴퓨트 셰이더(Compute Shaders)]], [[InstancedMesh|InstancedMesh]], Solid Particle System (SPS) +- **Projects/Contexts:** Hokusai installation - 엑스포 2025 오사카(Expo 2025 Osaka)에서 100만 개의 입자 기반 유체 시뮬레이션을 WebGPU로 구현한 프로젝트입니다 [12]. - **Contradictions/Notes:** Babylon.js 환경의 Solid Particle System(SPS)는 저폴리곤 입자의 CPU 연산 성능 면에서는 우수하지만, 입자별로 기하학적 데이터를 복제해야 하므로 메모리 점유율 측면에서는 인스턴스 메시(InstancedMesh) 방식에 비해 비효율적이라는 트레이드오프(Trade-off)가 존재합니다 [6, 10, 11]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/입자 시스템(Particle Systems).md]] +- Raw Source: 00_Raw/2026-04-20/입자 시스템(Particle Systems).md --- diff --git a/01_Archive/2026-04-20/자기 효능감 (Self-Efficacy).md b/01_Archive/2026-04-20/자기 효능감 (Self-Efficacy).md index b2576745..17313f9f 100644 --- a/01_Archive/2026-04-20/자기 효능감 (Self-Efficacy).md +++ b/01_Archive/2026-04-20/자기 효능감 (Self-Efficacy).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-43FFC2 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 자기 효능감 (Self-Efficacy)" --- -# [[자기 효능감 (Self-Efficacy)]] +# [[자기 효능감 (Self-Efficacy)|자기 효능감 (Self-Efficacy)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - 자기 효능감 (Self-Efficac ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/자기 효능감 (Self-Efficacy).md]] +- Raw Source: 00_Raw/2026-04-20/자기 효능감 (Self-Efficacy).md --- diff --git a/01_Archive/2026-04-20/자기 효능감(Self-Efficacy).md b/01_Archive/2026-04-20/자기 효능감(Self-Efficacy).md index a8a212ae..56fa7a20 100644 --- a/01_Archive/2026-04-20/자기 효능감(Self-Efficacy).md +++ b/01_Archive/2026-04-20/자기 효능감(Self-Efficacy).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-C2A5ED -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 자기 효능감(Self-Efficacy)" --- -# [[자기 효능감(Self-Efficacy)]] +# [[자기 효능감(Self-Efficacy)|자기 효능감(Self-Efficacy)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - 자기 효능감(Self-Efficacy ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/자기 효능감(Self-Efficacy).md]] +- Raw Source: 00_Raw/2026-04-20/자기 효능감(Self-Efficacy).md --- diff --git a/01_Archive/2026-04-20/자기결정성 이론 (SDT).md b/01_Archive/2026-04-20/자기결정성 이론 (SDT).md index c95968cc..999337d8 100644 --- a/01_Archive/2026-04-20/자기결정성 이론 (SDT).md +++ b/01_Archive/2026-04-20/자기결정성 이론 (SDT).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-AB9DD3 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 자기결정성 이론 (SDT)" --- -# [[자기결정성 이론 (SDT)]] +# [[자기결정성 이론 (SDT)|자기결정성 이론 (SDT)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - 자기결정성 이론 (SDT)" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/자기결정성 이론 (SDT).md]] +- Raw Source: 00_Raw/2026-04-20/자기결정성 이론 (SDT).md --- diff --git a/01_Archive/2026-04-20/자기결정성 이론 (Self-Determination Theory).md b/01_Archive/2026-04-20/자기결정성 이론 (Self-Determination Theory).md index e4252458..01e8fc97 100644 --- a/01_Archive/2026-04-20/자기결정성 이론 (Self-Determination Theory).md +++ b/01_Archive/2026-04-20/자기결정성 이론 (Self-Determination Theory).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-5A0AD3 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 자기결정성 이론 (Self-Determination Theory)" --- -# [[자기결정성 이론 (Self-Determination Theory)]] +# [[자기결정성 이론 (Self-Determination Theory)|자기결정성 이론 (Self-Determination Theory)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - 자기결정성 이론 (Self-D ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/자기결정성 이론 (Self-Determination Theory).md]] +- Raw Source: 00_Raw/2026-04-20/자기결정성 이론 (Self-Determination Theory).md --- diff --git a/01_Archive/2026-04-20/자기조절학습(Self-Regulated Learning).md b/01_Archive/2026-04-20/자기조절학습(Self-Regulated Learning).md index 8b90da51..245c4e14 100644 --- a/01_Archive/2026-04-20/자기조절학습(Self-Regulated Learning).md +++ b/01_Archive/2026-04-20/자기조절학습(Self-Regulated Learning).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-282D40 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 자기조절학습(Self-Regulated Learning)" --- -# [[자기조절학습(Self-Regulated Learning)]] +# [[자기조절학습(Self-Regulated Learning)|자기조절학습(Self-Regulated Learning)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - 자기조절학습(Self-Regula ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/자기조절학습(Self-Regulated Learning).md]] +- Raw Source: 00_Raw/2026-04-20/자기조절학습(Self-Regulated Learning).md --- diff --git a/01_Archive/2026-04-20/자동화된 코드 리뷰.md b/01_Archive/2026-04-20/자동화된 코드 리뷰.md index 372760f7..43884724 100644 --- a/01_Archive/2026-04-20/자동화된 코드 리뷰.md +++ b/01_Archive/2026-04-20/자동화된 코드 리뷰.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-AAE0A7 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 자동화된 코드 리뷰" --- -# [[자동화된 코드 리뷰]] +# [[자동화된 코드 리뷰|자동화된 코드 리뷰]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 자동화된 코드 리뷰는 린터(Linter), 포매터(Formatter), 정적 애플리케이션 보안 테스트(SAST) 등의 소프트웨어 도구를 사용하여 프로그램을 실행하지 않고 소스 코드를 자동으로 분석하는 프로세스입니다 [1-3]. 이 방법은 소프트웨어 개발 수명 주기(SDLC) 초기에 구문 오류, 코드 스타일 위반, 알려진 보안 취약점을 일관되고 빠르게 탐지하는 데 중점을 둡니다 [4-6]. 하지만 비즈니스 로직이나 아키텍처 등 문맥을 파악하는 데는 한계가 있으므로 인간이 직접 수행하는 수동 코드 리뷰와 결합된 하이브리드 모델로 활용하는 것이 현대 개발의 모범 사례로 평가받고 있습니다 [7, 8]. @@ -37,11 +37,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 자동화된 코드 리뷰" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[정적 애플리케이션 보안 테스트(SAST)]], [[수동 코드 리뷰]], [[린터(Linter)]] -- **Projects/Contexts:** [[CI/CD 파이프라인]], [[Husky와 lint-staged를 활용한 Git Hooks 연동]] +- **Related Topics:** [[정적 애플리케이션 보안 테스트(SAST)|정적 애플리케이션 보안 테스트(SAST)]], [[수동 코드 리뷰|수동 코드 리뷰]], [[린터 (Linter)|린터(Linter)]] +- **Projects/Contexts:** [[CI_CD 파이프라인|CI/CD 파이프라인]], Husky와 lint-staged를 활용한 Git Hooks 연동 - **Contradictions/Notes:** 소스 [6]는 자동화된 코드 리뷰가 빠른 속도로 방대한 코드베이스의 취약점과 오류를 일관성 있게 잡아낸다는 이점을 강조하지만, 소스 [16, 17]은 자동화 도구가 실제 취약점의 22%를 놓치고 30~60%에 달하는 오탐(False Positives)을 발생시킬 수 있는 한계를 지적하며, 비즈니스 로직과 아키텍처를 이해하기 위해서는 반드시 수동 리뷰가 결합된 하이브리드 접근법을 채택해야 한다고 주장합니다. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/자동화된 코드 리뷰.md]] +- Raw Source: 00_Raw/2026-04-20/자동화된 코드 리뷰.md --- diff --git a/01_Archive/2026-04-20/자바 가상 머신(JVM).md b/01_Archive/2026-04-20/자바 가상 머신(JVM).md index 4e6dd44a..b08c44d5 100644 --- a/01_Archive/2026-04-20/자바 가상 머신(JVM).md +++ b/01_Archive/2026-04-20/자바 가상 머신(JVM).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-2F0FAA -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 자바 가상 머신(JVM)" --- -# [[자바 가상 머신(JVM)]] +# [[자바 가상 머신(JVM)|자바 가상 머신(JVM)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 자바 가상 머신(JVM)은 자바(Java)와 같은 정적 타입 언어의 애플리케이션 실행을 위한 환경으로, 주로 자바 힙(Java heap)의 메모리 할당 및 가비지 컬렉션(GC)을 전담하는 엔진입니다 [1, 2]. 애플리케이션의 메모리 고갈을 방지하기 위해 더 이상 사용되지 않는 객체를 회수하며, 표시(mark), 청소(sweep), 압축(compact) 등의 과정을 거칩니다 [2]. 시중에는 3개의 주요 프로덕션 JVM이 존재하며, 이들은 각기 다른 가비지 컬렉션 알고리즘을 구현하여 사용하고 있습니다 [3]. @@ -23,11 +23,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 자바 가상 머신(JVM)" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[가비지 컬렉션(Garbage Collection)]], [[자바 힙(Java Heap)]], [[컴파일러 힌트(Compiler hints)]] -- **Projects/Contexts:** [[Eclipse OpenJ9]], [[IBM SDK]] +- **Related Topics:** [[가비지 컬렉션(Garbage Collection)|가비지 컬렉션(Garbage Collection)]], 자바 힙(Java Heap), 컴파일러 힌트(Compiler hints) +- **Projects/Contexts:** Eclipse OpenJ9, IBM SDK - **Contradictions/Notes:** JVM의 컴파일러 힌트 방식은 정적 타입 언어의 메모리 관리에 최적화되어 있으나, 자바스크립트처럼 객체의 속성이 포인터인지 데이터인지 미리 알 수 없는 동적 타입 언어에는 적합하지 않아 V8 엔진은 이를 채택하지 않고 태그된 포인터(Tagged pointers) 방식을 사용합니다 [1]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/자바 가상 머신(JVM).md]] +- Raw Source: 00_Raw/2026-04-20/자바 가상 머신(JVM).md --- diff --git a/01_Archive/2026-04-20/자율성 지지 (Autonomy Support).md b/01_Archive/2026-04-20/자율성 지지 (Autonomy Support).md index b1ff6e72..5c829cb5 100644 --- a/01_Archive/2026-04-20/자율성 지지 (Autonomy Support).md +++ b/01_Archive/2026-04-20/자율성 지지 (Autonomy Support).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-EB1B7E -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 자율성 지지 (Autonomy Support)" --- -# [[자율성 지지 (Autonomy Support)]] +# [[자율성 지지 (Autonomy Support)|자율성 지지 (Autonomy Support)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - 자율성 지지 (Autonomy Sup ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/자율성 지지 (Autonomy Support).md]] +- Raw Source: 00_Raw/2026-04-20/자율성 지지 (Autonomy Support).md --- diff --git a/01_Archive/2026-04-20/자폐 스펙트럼 장애(ASD) 중재.md b/01_Archive/2026-04-20/자폐 스펙트럼 장애(ASD) 중재.md index 04f3ae68..c21b5982 100644 --- a/01_Archive/2026-04-20/자폐 스펙트럼 장애(ASD) 중재.md +++ b/01_Archive/2026-04-20/자폐 스펙트럼 장애(ASD) 중재.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-DD3080 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 자폐 스펙트럼 장애(ASD) 중재" --- -# [[자폐 스펙트럼 장애(ASD) 중재]] +# [[자폐 스펙트럼 장애(ASD) 중재|자폐 스펙트럼 장애(ASD) 중재]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - 자폐 스펙트럼 장애(ASD ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/자폐 스펙트럼 장애(ASD) 중재.md]] +- Raw Source: 00_Raw/2026-04-20/자폐 스펙트럼 장애(ASD) 중재.md --- diff --git a/01_Archive/2026-04-20/장기 실행되는 실시간 데이터 대시보드 최적화.md b/01_Archive/2026-04-20/장기 실행되는 실시간 데이터 대시보드 최적화.md index 04a384ee..6fe00d81 100644 --- a/01_Archive/2026-04-20/장기 실행되는 실시간 데이터 대시보드 최적화.md +++ b/01_Archive/2026-04-20/장기 실행되는 실시간 데이터 대시보드 최적화.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-D81993 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 장기 실행되는 실시간 데이터 대시보드 최적화" --- -# [[장기 실행되는 실시간 데이터 대시보드 최적화]] +# [[장기 실행되는 실시간 데이터 대시보드 최적화|장기 실행되는 실시간 데이터 대시보드 최적화]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 장시간 켜져 있으면서 대량의 데이터를 실시간으로 처리해야 하는 대시보드 애플리케이션은 **메모리 누수(Memory Leak) 방지**와 **리렌더링 병목 제어**가 핵심입니다. 이를 위해 상태 관리의 미세 조정, 철저한 클린업, 대규모 리스트 가상화, 그리고 무거운 연산의 웹 워커 오프로딩 기법을 종합적으로 적용해야 합니다. @@ -44,5 +44,5 @@ github_commit: "[P-Reinforce] Continuous Worker - 장기 실행되는 실시간 ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/장기 실행되는 실시간 데이터 대시보드 최적화.md]] +- Raw Source: 00_Raw/2026-04-20/장기 실행되는 실시간 데이터 대시보드 최적화.md --- diff --git a/01_Archive/2026-04-20/재귀적 불변성 (DeepReadonly).md b/01_Archive/2026-04-20/재귀적 불변성 (DeepReadonly).md index 97e45815..38abddfa 100644 --- a/01_Archive/2026-04-20/재귀적 불변성 (DeepReadonly).md +++ b/01_Archive/2026-04-20/재귀적 불변성 (DeepReadonly).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-1F695C -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 재귀적 불변성 (DeepReadonly)" --- -# [[재귀적 불변성 (DeepReadonly)]] +# [[재귀적 불변성 (DeepReadonly)|재귀적 불변성 (DeepReadonly)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 재귀적 불변성(DeepReadonly)은 TypeScript에서 최상위 속성뿐만 아니라 중첩된 내부 객체까지 모두 불변(immutable) 상태로 만드는 커스텀 유틸리티 타입 기법입니다 [1-3]. 내장 `Readonly` 타입이나 `readonly` 수식어가 제공하는 얕은(shallow) 수준의 보호 한계를 극복하기 위해 매핑 타입과 조건부 타입을 결합하여 구현합니다 [1, 3-5]. 전체 데이터 구조의 변경을 방지하여 트리 구조나 복잡한 중첩 데이터를 다루는 상태 관리 및 설정 객체 등에서 데이터 무결성을 보장하는 강력한 방어책 역할을 합니다 [1, 3]. @@ -23,11 +23,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 재귀적 불변성 (DeepReado - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Readonly]], [[매핑 타입 (Mapped Types)]], [[조건부 타입 (Conditional Types)]], [[유틸리티 타입 (Utility Types)]] -- **Projects/Contexts:** [[ts-essentials]], [[프론트엔드 상태 관리 (State Management)]], [[설정 객체 (Configuration objects)]] +- **Related Topics:** [[Readonly 유틸리티 타입|Readonly]], 매핑 타입 (Mapped Types), 조건부 타입 (Conditional Types), 유틸리티 타입 (Utility Types) +- **Projects/Contexts:** ts-essentials, 프론트엔드 상태 관리 (State Management), 설정 객체 (Configuration objects) - **Contradictions/Notes:** `Readonly`는 기본 제공되나 `DeepReadonly`는 TypeScript에 내장되어 있지 않다는 점이 특징입니다 [6]. 또한 런타임에 성능 오버헤드를 일으키는 `Object.freeze()`의 얕은 동결과 달리, 이 방식은 컴파일 타임에 타입 레벨에서만 불변성을 검사하고 강제하므로 훨씬 효율적입니다 [5]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/재귀적 불변성 (DeepReadonly).md]] +- Raw Source: 00_Raw/2026-04-20/재귀적 불변성 (DeepReadonly).md --- diff --git a/01_Archive/2026-04-20/재조정 (Reconciliation).md b/01_Archive/2026-04-20/재조정 (Reconciliation).md index 7248078f..beb1a8a2 100644 --- a/01_Archive/2026-04-20/재조정 (Reconciliation).md +++ b/01_Archive/2026-04-20/재조정 (Reconciliation).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-EDDCE3 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 재조정 (Reconciliation)" --- -# [[재조정 (Reconciliation)]] +# [[재조정 (Reconciliation)|재조정 (Reconciliation)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > React가 렌더링 시 새로운 가상 DOM(Virtual DOM) 트리와 이전 트리를 비교하여, 실제 DOM에 적용해야 할 최소한의 변경 사항만을 찾아내어 업데이트하는 $O(n)$ 복잡도의 핵심 디핑(Diffing) 알고리즘 프로세스입니다. @@ -33,9 +33,9 @@ github_commit: "[P-Reinforce] Continuous Worker - 재조정 (Reconciliation)" - **정책 변화:** Design & Experience 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[가상 DOM (Virtual DOM)]], [[React 동시성 기능 (Concurrent Features)]], [[불필요한 리렌더링 방지]], [[명령형 조작 (Imperative Manipulation)]] +- **Related Topics:** [[가상 DOM (Virtual DOM)|가상 DOM (Virtual DOM)]], [[React 동시성 기능 (Concurrent Features)|React 동시성 기능 (Concurrent Features)]], [[불필요한 리렌더링 방지|불필요한 리렌더링 방지]], 명령형 조작 (Imperative Manipulation) -- **Projects/Contexts:** [[고성능 실시간 상호작용 시스템을 위한 React 기반 게임 엔진 아키텍처]], [[대규모 데이터 렌더링 및 가상화 최적화]] +- **Projects/Contexts:** [[고성능 실시간 상호작용 시스템을 위한 React 기반 게임 엔진 아키텍처|고성능 실시간 상호작용 시스템을 위한 React 기반 게임 엔진 아키텍처]], [[대규모 데이터 렌더링 및 가상화 최적화|대규모 데이터 렌더링 및 가상화 최적화]] - **Contradictions/Notes:** 재조정 알고리즘은 선언적 UI 관리를 가능하게 하는 훌륭한 기능이지만 만능은 아닙니다. Three.js(R3F) 기반의 게임이나 대규모 애니메이션 환경처럼 매 프레임 수만 개의 좌표나 속성이 변하는 경우, React의 재조정 과정을 거치면 성능이 붕괴되므로 `useFrame` 등을 활용해 참조(Ref)의 속성을 직접 조작(Direct/Imperative Mutation)하여 재조정을 우회하는 기법이 반드시 필요합니다. @@ -43,5 +43,5 @@ github_commit: "[P-Reinforce] Continuous Worker - 재조정 (Reconciliation)" --- _Last updated: 2026-04-15_ -- Raw Source: [[00_Raw/2026-04-20/재조정 (Reconciliation).md]] +- Raw Source: 00_Raw/2026-04-20/재조정 (Reconciliation).md --- diff --git a/01_Archive/2026-04-20/전두엽 기능 저하 (Hypofrontality).md b/01_Archive/2026-04-20/전두엽 기능 저하 (Hypofrontality).md index 6583f30f..43457724 100644 --- a/01_Archive/2026-04-20/전두엽 기능 저하 (Hypofrontality).md +++ b/01_Archive/2026-04-20/전두엽 기능 저하 (Hypofrontality).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-B8940A -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 전두엽 기능 저하 (Hypofrontality)" --- -# [[전두엽 기능 저하 (Hypofrontality)]] +# [[전두엽 기능 저하 (Hypofrontality)|전두엽 기능 저하 (Hypofrontality)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - 전두엽 기능 저하 (Hypof ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/전두엽 기능 저하 (Hypofrontality).md]] +- Raw Source: 00_Raw/2026-04-20/전두엽 기능 저하 (Hypofrontality).md --- diff --git a/01_Archive/2026-04-20/절차적 수사학(Procedural Rhetoric).md b/01_Archive/2026-04-20/절차적 수사학(Procedural Rhetoric).md index 86a3c10a..7c2c27f2 100644 --- a/01_Archive/2026-04-20/절차적 수사학(Procedural Rhetoric).md +++ b/01_Archive/2026-04-20/절차적 수사학(Procedural Rhetoric).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-274581 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 절차적 수사학(Procedural Rhetoric)" --- -# [[절차적 수사학(Procedural Rhetoric)]] +# [[절차적 수사학(Procedural Rhetoric)|절차적 수사학(Procedural Rhetoric)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - 절차적 수사학(Procedural ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/절차적 수사학(Procedural Rhetoric).md]] +- Raw Source: 00_Raw/2026-04-20/절차적 수사학(Procedural Rhetoric).md --- diff --git a/01_Archive/2026-04-20/점진적 마킹(Incremental marking).md b/01_Archive/2026-04-20/점진적 마킹(Incremental marking).md index 98e1bcb1..aa7f1a3e 100644 --- a/01_Archive/2026-04-20/점진적 마킹(Incremental marking).md +++ b/01_Archive/2026-04-20/점진적 마킹(Incremental marking).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-EED588 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 점진적 마킹(Incremental marking)" --- -# [[점진적 마킹(Incremental marking)]] +# [[점진적 마킹(Incremental marking)|점진적 마킹(Incremental marking)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 점진적 마킹(Incremental marking)은 가비지 컬렉션(GC) 과정에서 발생하는 긴 중단 시간(Stop-the-world)을 줄이기 위해 전체 마킹 작업을 여러 개의 작은 일시 정지 구간으로 나누어 실행하는 기법입니다 [1-3]. 애플리케이션의 메인 스레드 실행과 마킹 작업이 교차로 진행되므로 힙 탐색 중에도 사용자 입력 처리나 애니메이션 렌더링을 계속할 수 있습니다 [2, 4]. 비록 가비지 컬렉션에 소비되는 총시간을 줄여주지는 못하지만, 작업 시간을 분산시킴으로써 애플리케이션의 지연 시간(Latency)과 반응성을 크게 개선합니다 [2]. @@ -30,11 +30,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 점진적 마킹(Incremental m - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[가비지 컬렉션(Garbage Collection)]], [[쓰기 장벽(Write barriers)]], [[지연 스위핑(Lazy sweeping)]] -- **Projects/Contexts:** [[V8 JavaScript Engine]], [[Orinoco Garbage Collector]], [[IBM OpenJ9 (Balanced GC)]] +- **Related Topics:** [[가비지 컬렉션(Garbage Collection)|가비지 컬렉션(Garbage Collection)]], 쓰기 장벽(Write barriers), 지연 스위핑(Lazy sweeping) +- **Projects/Contexts:** [[V8 JavaScript Engine|V8 JavaScript Engine]], Orinoco Garbage Collector, IBM OpenJ9 (Balanced GC) - **Contradictions/Notes:** 점진적 마킹은 메인 스레드의 긴 일시 정지를 방지하고 응답성을 높이는 데에는 훌륭한 기법이지만, 메인 스레드에서 가비지 컬렉션에 소모되는 전체 시간을 줄여주지는 않으며 오히려 미세하게 증가시키는 경향이 있습니다 [2]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/점진적 마킹(Incremental marking).md]] +- Raw Source: 00_Raw/2026-04-20/점진적 마킹(Incremental marking).md --- diff --git a/01_Archive/2026-04-20/정서적 고전적 조건 형성 (Emotional Classical Conditioning).md b/01_Archive/2026-04-20/정서적 고전적 조건 형성 (Emotional Classical Conditioning).md index 513d9be6..7c01e04b 100644 --- a/01_Archive/2026-04-20/정서적 고전적 조건 형성 (Emotional Classical Conditioning).md +++ b/01_Archive/2026-04-20/정서적 고전적 조건 형성 (Emotional Classical Conditioning).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-BB4E76 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 정서적 고전적 조건 형성 (Emotional Classical Conditioning)" --- -# [[정서적 고전적 조건 형성 (Emotional Classical Conditioning)]] +# [[정서적 고전적 조건 형성 (Emotional Classical Conditioning)|정서적 고전적 조건 형성 (Emotional Classical Conditioning)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - 정서적 고전적 조건 형 ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/정서적 고전적 조건 형성 (Emotional Classical Conditioning).md]] +- Raw Source: 00_Raw/2026-04-20/정서적 고전적 조건 형성 (Emotional Classical Conditioning).md --- diff --git a/01_Archive/2026-04-20/정신 의학적 진단 체계 (DSM-5_ICD-11).md b/01_Archive/2026-04-20/정신 의학적 진단 체계 (DSM-5_ICD-11).md index 7122fece..fabf5a58 100644 --- a/01_Archive/2026-04-20/정신 의학적 진단 체계 (DSM-5_ICD-11).md +++ b/01_Archive/2026-04-20/정신 의학적 진단 체계 (DSM-5_ICD-11).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-4BDF5C -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 정신 의학적 진단 체계 (DSM-5_ICD-11)" --- -# [[정신 의학적 진단 체계 (DSM-5_ICD-11)]] +# [[정신 의학적 진단 체계 (DSM-5_ICD-11)|정신 의학적 진단 체계 (DSM-5_ICD-11)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - 정신 의학적 진단 체계 ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/정신 의학적 진단 체계 (DSM-5_ICD-11).md]] +- Raw Source: 00_Raw/2026-04-20/정신 의학적 진단 체계 (DSM-5_ICD-11).md --- diff --git a/01_Archive/2026-04-20/정적 분석(Static Analysis).md b/01_Archive/2026-04-20/정적 분석(Static Analysis).md index d2fb3c8d..c5290441 100644 --- a/01_Archive/2026-04-20/정적 분석(Static Analysis).md +++ b/01_Archive/2026-04-20/정적 분석(Static Analysis).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-9D9335 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 정적 분석(Static Analysis)" --- -# [[정적 분석(Static Analysis)]] +# [[정적 분석(Static Analysis)|정적 분석(Static Analysis)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 정적 분석(Static Analysis) 또는 정적 애플리케이션 보안 테스트(SAST)는 프로그램을 직접 실행하지 않고 소스 코드나 바이트코드를 분석하여 오류나 취약점을 찾아내는 소프트웨어 검사 기술입니다 [1-3]. 소프트웨어 개발 수명 주기(SDLC)의 초기 단계에 적용되어 보안 취약점, 로직 결함, 코드 스타일 문제 등을 실행 전에 예방할 수 있는 '화이트 박스 테스트'의 일환으로 쓰입니다 [2, 4, 5]. 자동화된 도구를 통해 코딩 규칙을 강제하고 일관성을 확보함으로써 개발 팀의 협업 효율성을 높이고 유지보수성을 향상시키는 데 핵심적인 역할을 합니다 [6-8]. @@ -36,11 +36,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 정적 분석(Static Analysis) - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[수동 코드 리뷰(Manual Code Review)]], [[DAST(Dynamic Application Security Testing)]], [[SCA(Software Composition Analysis)]], [[Linting / Formatter]] -- **Projects/Contexts:** [[Snyk Code]], [[SonarQube]], [[Checkmarx]], [[ESLint / Prettier]] +- **Related Topics:** [[수동 코드 리뷰 (Manual Code Review)|수동 코드 리뷰(Manual Code Review)]], [[DAST (Dynamic Application Security Testing)|DAST(Dynamic Application Security Testing)]], SCA(Software Composition Analysis), Linting / Formatter +- **Projects/Contexts:** Snyk Code, [[SonarQube|SonarQube]], Checkmarx, ESLint / Prettier - **Contradictions/Notes:** 소스 [35], [24], [36] 등은 자동화된 정적 분석 도구가 코드를 빠르고 일관되게 스캔하지만 비즈니스 로직이나 의도를 파악하는 데는 맹점이 있다고 지적합니다. 따라서 자동화 도구에만 의존해서는 안 되며, 보안 맥락과 아키텍처 트레이드오프를 평가하기 위해 반드시 인간의 통찰력이 개입되는 '수동 코드 리뷰(Manual Code Review)'를 결합한 하이브리드 접근법을 취해야 한다고 권장합니다. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/정적 분석(Static Analysis).md]] +- Raw Source: 00_Raw/2026-04-20/정적 분석(Static Analysis).md --- diff --git a/01_Archive/2026-04-20/정적 애플리케이션 보안 테스트 (SAST).md b/01_Archive/2026-04-20/정적 애플리케이션 보안 테스트 (SAST).md index a68df355..aa62a42c 100644 --- a/01_Archive/2026-04-20/정적 애플리케이션 보안 테스트 (SAST).md +++ b/01_Archive/2026-04-20/정적 애플리케이션 보안 테스트 (SAST).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-517F55 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 정적 애플리케이션 보안 테스트 (SAST)" --- -# [[정적 애플리케이션 보안 테스트 (SAST)]] +# [[정적 애플리케이션 보안 테스트 (SAST)|정적 애플리케이션 보안 테스트 (SAST)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > SAST(정적 애플리케이션 보안 테스트)는 애플리케이션의 소스 코드나 바이트코드를 실행하기 전에 정적으로 분석하여 잠재적인 보안 취약점을 식별하는 화이트박스 테스트 기법이다 [1]. 개발 수명 주기(SDLC) 초기에 취약점을 발견하여 수정 비용과 시간을 대폭 절감하게 해주는 '시프트 레프트(Shift-Left)' 보안 전략의 핵심 도구이다 [1, 2]. 최근에는 단순한 규칙 기반 패턴 매칭의 한계를 극복하기 위해 인공지능(AI)과 머신러닝 모델을 통합하여, 코드의 문맥과 의미를 이해하고 수정안까지 자동으로 제안하는 방향으로 진화하고 있다 [3, 4]. @@ -24,11 +24,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 정적 애플리케이션 보 - **정책 변화:** AI 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[정적 코드 분석]], [[시프트 레프트 (Shift-Left)]], [[오염 분석 (Taint Analysis)]], [[동적 애플리케이션 보안 테스트 (DAST)]], [[소프트웨어 구성 분석 (SCA)]], [[자동화된 코드 거버넌스]] -- **Projects/Contexts:** [[Snyk Code]], [[Corgea]], [[GitHub Advanced Security]], [[DevSecOps 파이프라인]] +- **Related Topics:** 정적 코드 분석, [[시프트 레프트 (Shift-Left)|시프트 레프트 (Shift-Left)]], 오염 분석 (Taint Analysis), [[동적 애플리케이션 보안 테스트(DAST)|동적 애플리케이션 보안 테스트 (DAST)]], [[소프트웨어 구성 분석(SCA)|소프트웨어 구성 분석 (SCA)]], 자동화된 코드 거버넌스 +- **Projects/Contexts:** Snyk Code, [[Corgea|Corgea]], GitHub Advanced Security, DevSecOps 파이프라인 - **Contradictions/Notes:** 자동화된 SAST 도구들은 처리 속도와 규모 확장성이 뛰어나지만, 정해진 규칙에 벗어나거나 복잡한 비즈니스 로직 및 새로운 아키텍처 맥락에 따른 취약점은 놓칠 수 있다. 연구에 따르면 SAST 툴들은 실제 취약점의 약 22% 정도를 탐지하지 못하거나 30~60%의 높은 오탐률로 경고 피로도(Alert fatigue)를 일으킨다 [12, 28, 29]. 따라서 AI로 개선된 SAST 도구를 사용하여 일차적인 검열을 수행하더라도, 고위험 코드나 복잡한 시스템 로직의 최종 보안 검증을 위해서는 반드시 인간 중심의 '수동 코드 리뷰(Manual Code Review)'를 결합하는 하이브리드 리뷰가 필수적으로 요구된다 [30-32]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/정적 애플리케이션 보안 테스트 (SAST).md]] +- Raw Source: 00_Raw/2026-04-20/정적 애플리케이션 보안 테스트 (SAST).md --- diff --git a/01_Archive/2026-04-20/정적 애플리케이션 보안 테스트(SAST).md b/01_Archive/2026-04-20/정적 애플리케이션 보안 테스트(SAST).md index 5fffa116..ab7c25ee 100644 --- a/01_Archive/2026-04-20/정적 애플리케이션 보안 테스트(SAST).md +++ b/01_Archive/2026-04-20/정적 애플리케이션 보안 테스트(SAST).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-E9615F -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 정적 애플리케이션 보안 테스트(SAST)" --- -# [[정적 애플리케이션 보안 테스트(SAST)]] +# [[정적 애플리케이션 보안 테스트(SAST)|정적 애플리케이션 보안 테스트(SAST)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 정적 애플리케이션 보안 테스트(SAST)는 애플리케이션을 실행하지 않고 소스 코드, 바이트코드 등의 구조와 구문을 정적으로 분석하여 보안 취약점과 논리적 오류를 식별하는 화이트박스 테스트 기법입니다 [1, 2]. 소프트웨어 개발 생명주기(SDLC)의 가장 초기 단계(코드 작성 및 CI/CD 파이프라인)에 적용되어 문제를 발견하므로, 수정에 드는 비용과 시간을 크게 절감할 수 있습니다 [1, 3, 4]. 최근의 SAST 도구들은 단순한 패턴 매칭을 넘어 머신러닝 및 대형 언어 모델(LLM)을 결합하여 코드의 문맥을 이해하고, 자동으로 수정 코드를 제안하는 AI 기반으로 진화하고 있습니다 [5, 6]. @@ -36,13 +36,13 @@ github_commit: "[P-Reinforce] Continuous Worker - 정적 애플리케이션 보 - **정책 변화:** AI 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[동적 애플리케이션 보안 테스트(DAST)]], [[소프트웨어 구성 분석(SCA)]], [[시프트 레프트(Shift-Left)]], [[추상 구문 트리(AST)]] -- **Projects/Contexts:** [[CI/CD 파이프라인]], [[OWASP Top 10]], [[하이브리드 코드 리뷰]] +- **Related Topics:** [[동적 애플리케이션 보안 테스트(DAST)|동적 애플리케이션 보안 테스트(DAST)]], [[소프트웨어 구성 분석(SCA)|소프트웨어 구성 분석(SCA)]], [[시프트 레프트(Shift-Left)|시프트 레프트(Shift-Left)]], [[추상 구문 트리(AST)|추상 구문 트리(AST)]] +- **Projects/Contexts:** [[CI_CD 파이프라인|CI/CD 파이프라인]], [[OWASP Top 10|OWASP Top 10]], [[하이브리드 코드 리뷰|하이브리드 코드 리뷰]] - **Contradictions/Notes:** * "전통적인 규칙 기반의 SAST 도구는 50~80%에 이르는 높은 오탐률(False Positive)을 보여 개발자의 피로도를 높일 수 있지만, 최근의 AI 및 기계 학습 기반 SAST(예: Veracode, Corgea 등)는 컨텍스트를 이해함으로써 오탐률을 5% 이하(일부 1.1% 미만)로 현저히 줄일 수 있다고 보고됩니다." [19, 32]. * "자동화된 정적 분석 도구만으로 모든 보안 오류를 막을 수 있다고 기대하는 것은 위험합니다. 실증 연구에 따르면 SAST 도구는 실제 존재하는 취약점의 약 22%를 완전히 놓칠 수 있으며, 따라서 자동화 도구를 맹신하지 말고 고위험 코드 변경에 대해서는 반드시 수동 코드 리뷰를 병행해야 합니다." [18, 33-35]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/정적 애플리케이션 보안 테스트(SAST).md]] +- Raw Source: 00_Raw/2026-04-20/정적 애플리케이션 보안 테스트(SAST).md --- diff --git a/01_Archive/2026-04-20/제어 흐름 분석 (Control Flow Analysis).md b/01_Archive/2026-04-20/제어 흐름 분석 (Control Flow Analysis).md index e9529183..c6e1016c 100644 --- a/01_Archive/2026-04-20/제어 흐름 분석 (Control Flow Analysis).md +++ b/01_Archive/2026-04-20/제어 흐름 분석 (Control Flow Analysis).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-9FF9A4 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 제어 흐름 분석 (Control Flow Analysis)" --- -# [[제어 흐름 분석 (Control Flow Analysis)]] +# [[제어 흐름 분석 (Control Flow Analysis)|제어 흐름 분석 (Control Flow Analysis)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 제어 흐름 분석(Control Flow Analysis)은 TypeScript가 코드의 실행 흐름을 파악하여 변수의 타입을 더 구체적으로 좁혀나가는(Narrowing) 메커니즘입니다 [1]. 주로 `if`나 `switch` 문과 같은 조건 블록 내에서 타입 가드(Type Guard)를 이해하고 적용하는 데 핵심적인 역할을 합니다 [1]. 이 분석을 통해 컴파일러는 여러 가능성이 있는 객체 집합을 단일한 특정 객체 타입으로 좁혀서(Code flow analysis) 안전하게 취급할 수 있도록 만듭니다 [2]. @@ -22,11 +22,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 제어 흐름 분석 (Control - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[타입 좁히기 (Type Narrowing)]], [[타입 가드 (Type Guards)]], [[식별 가능한 유니온 (Discriminated Unions)]] -- **Projects/Contexts:** [[TypeScript 상태 모델링 및 에러 처리 맥락]] (로딩, 성공, 에러와 같은 상태나 유사한 객체들의 집합을 `switch`문 등을 통해 구체적인 타입으로 좁혀서 런타임 오류 없이 안전하게 다뤄야 하는 프로젝트 환경 [2, 3]) +- **Related Topics:** [[타입 좁히기 (Type Narrowing)|타입 좁히기 (Type Narrowing)]], [[타입 가드 (Type Guards)|타입 가드 (Type Guards)]], [[식별 가능한 유니온 (Discriminated Unions)|식별 가능한 유니온 (Discriminated Unions)]] +- **Projects/Contexts:** TypeScript 상태 모델링 및 에러 처리 맥락 (로딩, 성공, 에러와 같은 상태나 유사한 객체들의 집합을 `switch`문 등을 통해 구체적인 타입으로 좁혀서 런타임 오류 없이 안전하게 다뤄야 하는 프로젝트 환경 [2, 3]) - **Contradictions/Notes:** 주어진 소스 내에서 제어 흐름 분석에 대한 개념들 간의 모순점은 발견되지 않았으나, 해당 주제를 더 깊게 이해하기 위한 구체적인 동작 구조 정보는 부족합니다. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/제어 흐름 분석 (Control Flow Analysis).md]] +- Raw Source: 00_Raw/2026-04-20/제어 흐름 분석 (Control Flow Analysis).md --- diff --git a/01_Archive/2026-04-20/조작적 조건 형성 (Operant Conditioning).md b/01_Archive/2026-04-20/조작적 조건 형성 (Operant Conditioning).md index 374937e9..79b6f432 100644 --- a/01_Archive/2026-04-20/조작적 조건 형성 (Operant Conditioning).md +++ b/01_Archive/2026-04-20/조작적 조건 형성 (Operant Conditioning).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-901DFC -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 조작적 조건 형성 (Operant Conditioning)" --- -# [[조작적 조건 형성 (Operant Conditioning)]] +# [[조작적 조건 형성 (Operant Conditioning)|조작적 조건 형성 (Operant Conditioning)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - 조작적 조건 형성 (Opera ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/조작적 조건 형성 (Operant Conditioning).md]] +- Raw Source: 00_Raw/2026-04-20/조작적 조건 형성 (Operant Conditioning).md --- diff --git a/01_Archive/2026-04-20/조작적 조건 형성.md b/01_Archive/2026-04-20/조작적 조건 형성.md index 4a5a7c52..0a198ca1 100644 --- a/01_Archive/2026-04-20/조작적 조건 형성.md +++ b/01_Archive/2026-04-20/조작적 조건 형성.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-05C66E -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 조작적 조건 형성" --- -# [[조작적 조건 형성]] +# [[조작적 조건 형성|조작적 조건 형성]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - 조작적 조건 형성" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/조작적 조건 형성.md]] +- Raw Source: 00_Raw/2026-04-20/조작적 조건 형성.md --- diff --git a/01_Archive/2026-04-20/조작적 조건형성.md b/01_Archive/2026-04-20/조작적 조건형성.md index a10f877d..6f5e9925 100644 --- a/01_Archive/2026-04-20/조작적 조건형성.md +++ b/01_Archive/2026-04-20/조작적 조건형성.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-C7CA1A -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 조작적 조건형성" --- -# [[조작적 조건형성]] +# [[조작적 조건형성|조작적 조건형성]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - 조작적 조건형성" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/조작적 조건형성.md]] +- Raw Source: 00_Raw/2026-04-20/조작적 조건형성.md --- diff --git a/01_Archive/2026-04-20/조절-폭주 불일치 (Vergence-Accommodation Conflict).md b/01_Archive/2026-04-20/조절-폭주 불일치 (Vergence-Accommodation Conflict).md index 71ef0d81..692ff263 100644 --- a/01_Archive/2026-04-20/조절-폭주 불일치 (Vergence-Accommodation Conflict).md +++ b/01_Archive/2026-04-20/조절-폭주 불일치 (Vergence-Accommodation Conflict).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-747672 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 조절-폭주 불일치 (Vergence-Accommodation Conflict)" --- -# [[조절-폭주 불일치 (Vergence-Accommodation Conflict)]] +# [[조절-폭주 불일치 (Vergence-Accommodation Conflict)|조절-폭주 불일치 (Vergence-Accommodation Conflict)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 조절-폭주 불일치(Vergence-Accommodation Conflict)는 가상현실(VR) 헤드마운트 디스플레이(HMD) 환경에서 주로 관찰되는 시각적 문제로, 자연스러운 상태에서 함께 작용하는 폭주와 조절이라는 안구 운동 기능이 상호 분리되면서 발생하는 현상입니다 [1, 2]. 자연적인 시각 조건에서는 이 두 기능이 피드백 루프를 통해 동반 변화하여 가까운 대상에 선명한 초점을 맺도록 돕지만, HMD 기기 내에서는 이 연결이 끊어지게 됩니다 [2]. 이러한 시각적 불일치는 깊이 지각을 위한 망막 단서의 불확실성을 초래하며, 눈의 피로, 두통, VR 멀미 등의 원인으로 지목되고 있습니다 [1, 2]. @@ -22,11 +22,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 조절-폭주 불일치 (Verge - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[가상현실 멀미 (VR Sickness)]], [[헤드마운트 디스플레이 (HMD)]], [[깊이 지각 (Depth Perception)]], [[안구 운동 기능 (Oculomotor Functions)]] -- **Projects/Contexts:** [[가상현실 후유증 (Virtual Reality Aftereffects)]] +- **Related Topics:** [[가상현실 멀미 (VR Sickness)|가상현실 멀미 (VR Sickness)]], [[헤드마운트 디스플레이 (HMD)|헤드마운트 디스플레이 (HMD)]], [[깊이 지각 (Depth Perception)|깊이 지각 (Depth Perception)]], [[안구 운동 기능 (Oculomotor Functions)|안구 운동 기능 (Oculomotor Functions)]] +- **Projects/Contexts:** [[가상현실 후유증 (Virtual Reality Aftereffects)|가상현실 후유증 (Virtual Reality Aftereffects)]] - **Contradictions/Notes:** 소스에 따르면 조절-폭주 불일치가 특정 개인의 가상현실 멀미(VR sickness)를 유발하는 직접적 원인인지, 아니면 멀미 증상의 심각성을 가중시키는 요인인지에 대해서는 아직 명확히 밝혀지지 않았습니다 [1]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/조절-폭주 불일치 (Vergence-Accommodation Conflict).md]] +- Raw Source: 00_Raw/2026-04-20/조절-폭주 불일치 (Vergence-Accommodation Conflict).md --- diff --git a/01_Archive/2026-04-20/조절-폭주 불일치(Vergence-Accommodation Conflict).md b/01_Archive/2026-04-20/조절-폭주 불일치(Vergence-Accommodation Conflict).md index ac746fc9..01fbbc54 100644 --- a/01_Archive/2026-04-20/조절-폭주 불일치(Vergence-Accommodation Conflict).md +++ b/01_Archive/2026-04-20/조절-폭주 불일치(Vergence-Accommodation Conflict).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-4FA83F -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 조절-폭주 불일치(Vergence-Accommodation Conflict)" --- -# [[조절-폭주 불일치(Vergence-Accommodation Conflict)]] +# [[조절-폭주 불일치(Vergence-Accommodation Conflict)|조절-폭주 불일치(Vergence-Accommodation Conflict)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 조절-폭주 불일치(Vergence-Accommodation Conflict)는 가상현실의 머리 착용 디스플레이(HMD)를 사용할 때 발생하는 시각적 깊이 단서의 충돌 현상이다 [1, 2]. 자연스러운 시각 환경에서 함께 작동하는 안구의 조절(accommodation)과 폭주(vergence) 기능이 HMD 환경에서는 분리(decoupled)되면서 발생한다 [2]. 이로 인해 깊이 지각에 대한 불확실성이 커지며, 두통, 안구 통증, 시각적 피로, 복시 및 가상현실 멀미와 같은 다양한 시각적·인지적 후유증이 유발될 수 있다 [1, 2]. @@ -23,11 +23,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 조절-폭주 불일치(Vergen - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[가상현실 멀미(VR Sickness)]], [[안구 운동 증상(Oculomotor Symptoms)]], [[깊이 지각(Depth Perception)]] -- **Projects/Contexts:** [[머리 착용 디스플레이(HMD) 시각 연구]], [[가상현실 엑서게임(Exergaming) 후유증 연구]] +- **Related Topics:** [[가상현실 멀미(VR Sickness)|가상현실 멀미(VR Sickness)]], [[안구 운동 증상(Oculomotor Symptoms)|안구 운동 증상(Oculomotor Symptoms)]], [[깊이 지각 (Depth Perception)|깊이 지각(Depth Perception)]] +- **Projects/Contexts:** [[머리 착용 디스플레이(HMD) 시각 연구|머리 착용 디스플레이(HMD) 시각 연구]], [[가상현실 엑서게임(Exergaming) 후유증 연구|가상현실 엑서게임(Exergaming) 후유증 연구]] - **Contradictions/Notes:** 소스에 따르면 조절-폭주 불일치가 사람들에게 VR 멀미를 유발하는 직접적인 원인인지, 아니면 기존의 멀미 증상을 심화시키는 역할을 하는지에 대해서는 아직 분명하지 않다(unclear)고 지적하고 있다 [1]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/조절-폭주 불일치(Vergence-Accommodation Conflict).md]] +- Raw Source: 00_Raw/2026-04-20/조절-폭주 불일치(Vergence-Accommodation Conflict).md --- diff --git a/01_Archive/2026-04-20/조직 개발(OD) 프로그램 설계.md b/01_Archive/2026-04-20/조직 개발(OD) 프로그램 설계.md index d6eb7cff..dacb0f19 100644 --- a/01_Archive/2026-04-20/조직 개발(OD) 프로그램 설계.md +++ b/01_Archive/2026-04-20/조직 개발(OD) 프로그램 설계.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-E12DC4 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 조직 개발(OD) 프로그램 설계" --- -# [[조직 개발(OD) 프로그램 설계]] +# [[조직 개발(OD) 프로그램 설계|조직 개발(OD) 프로그램 설계]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - 조직 개발(OD) 프로그램 ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/조직 개발(OD) 프로그램 설계.md]] +- Raw Source: 00_Raw/2026-04-20/조직 개발(OD) 프로그램 설계.md --- diff --git a/01_Archive/2026-04-20/조직 시민 행동 (OCB).md b/01_Archive/2026-04-20/조직 시민 행동 (OCB).md index 8414062e..ab110b51 100644 --- a/01_Archive/2026-04-20/조직 시민 행동 (OCB).md +++ b/01_Archive/2026-04-20/조직 시민 행동 (OCB).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-03634D -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 조직 시민 행동 (OCB)" --- -# [[조직 시민 행동 (OCB)]] +# [[조직 시민 행동 (OCB)|조직 시민 행동 (OCB)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - 조직 시민 행동 (OCB)" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/조직 시민 행동 (OCB).md]] +- Raw Source: 00_Raw/2026-04-20/조직 시민 행동 (OCB).md --- diff --git a/01_Archive/2026-04-20/조직 행동 관리(OBM).md b/01_Archive/2026-04-20/조직 행동 관리(OBM).md index 633d2d27..d6c24491 100644 --- a/01_Archive/2026-04-20/조직 행동 관리(OBM).md +++ b/01_Archive/2026-04-20/조직 행동 관리(OBM).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-532605 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 조직 행동 관리(OBM)" --- -# [[조직 행동 관리(OBM)]] +# [[조직 행동 관리(OBM)|조직 행동 관리(OBM)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - 조직 행동 관리(OBM)" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/조직 행동 관리(OBM).md]] +- Raw Source: 00_Raw/2026-04-20/조직 행동 관리(OBM).md --- diff --git a/01_Archive/2026-04-20/조직 행동론 및 직무 만족도 연구.md b/01_Archive/2026-04-20/조직 행동론 및 직무 만족도 연구.md index 8462dc3e..e958a838 100644 --- a/01_Archive/2026-04-20/조직 행동론 및 직무 만족도 연구.md +++ b/01_Archive/2026-04-20/조직 행동론 및 직무 만족도 연구.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-2FE438 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 조직 행동론 및 직무 만족도 연구" --- -# [[조직 행동론 및 직무 만족도 연구]] +# [[조직 행동론 및 직무 만족도 연구|조직 행동론 및 직무 만족도 연구]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - 조직 행동론 및 직무 ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/조직 행동론 및 직무 만족도 연구.md]] +- Raw Source: 00_Raw/2026-04-20/조직 행동론 및 직무 만족도 연구.md --- diff --git a/01_Archive/2026-04-20/조직 행동론의 성과급 체계 분석.md b/01_Archive/2026-04-20/조직 행동론의 성과급 체계 분석.md index a0750139..813a58ca 100644 --- a/01_Archive/2026-04-20/조직 행동론의 성과급 체계 분석.md +++ b/01_Archive/2026-04-20/조직 행동론의 성과급 체계 분석.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-6AFB3F -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 조직 행동론의 성과급 체계 분석" --- -# [[조직 행동론의 성과급 체계 분석]] +# [[조직 행동론의 성과급 체계 분석|조직 행동론의 성과급 체계 분석]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - 조직 행동론의 성과급 ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/조직 행동론의 성과급 체계 분석.md]] +- Raw Source: 00_Raw/2026-04-20/조직 행동론의 성과급 체계 분석.md --- diff --git a/01_Archive/2026-04-20/조직 행동론의 직무 몰입 연구.md b/01_Archive/2026-04-20/조직 행동론의 직무 몰입 연구.md index 5a2112d2..4d913fa7 100644 --- a/01_Archive/2026-04-20/조직 행동론의 직무 몰입 연구.md +++ b/01_Archive/2026-04-20/조직 행동론의 직무 몰입 연구.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-6B36D0 -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 조직 행동론의 직무 몰입 연구" --- -# [[조직 행동론의 직무 몰입 연구]] +# [[조직 행동론의 직무 몰입 연구|조직 행동론의 직무 몰입 연구]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - 조직 행동론의 직무 몰 ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/조직 행동론의 직무 몰입 연구.md]] +- Raw Source: 00_Raw/2026-04-20/조직 행동론의 직무 몰입 연구.md --- diff --git a/01_Archive/2026-04-20/중뇌-변연계 경로 (Mesolimbic Pathway).md b/01_Archive/2026-04-20/중뇌-변연계 경로 (Mesolimbic Pathway).md index 5802f770..bcb6d53e 100644 --- a/01_Archive/2026-04-20/중뇌-변연계 경로 (Mesolimbic Pathway).md +++ b/01_Archive/2026-04-20/중뇌-변연계 경로 (Mesolimbic Pathway).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-D5E4BD -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 중뇌-변연계 경로 (Mesolimbic Pathway)" --- -# [[중뇌-변연계 경로 (Mesolimbic Pathway)]] +# [[중뇌-변연계 경로 (Mesolimbic Pathway)|중뇌-변연계 경로 (Mesolimbic Pathway)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - 중뇌-변연계 경로 (Mesol ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/중뇌-변연계 경로 (Mesolimbic Pathway).md]] +- Raw Source: 00_Raw/2026-04-20/중뇌-변연계 경로 (Mesolimbic Pathway).md --- diff --git a/01_Archive/2026-04-20/중독 의학 및 정신 병리학.md b/01_Archive/2026-04-20/중독 의학 및 정신 병리학.md index d4e26051..1162488f 100644 --- a/01_Archive/2026-04-20/중독 의학 및 정신 병리학.md +++ b/01_Archive/2026-04-20/중독 의학 및 정신 병리학.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-E50291 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 중독 의학 및 정신 병리학" --- -# [[중독 의학 및 정신 병리학]] +# [[중독 의학 및 정신 병리학|중독 의학 및 정신 병리학]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - 중독 의학 및 정신 병 ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/중독 의학 및 정신 병리학.md]] +- Raw Source: 00_Raw/2026-04-20/중독 의학 및 정신 병리학.md --- diff --git a/01_Archive/2026-04-20/중독 재활 프로그램.md b/01_Archive/2026-04-20/중독 재활 프로그램.md index 591be115..0c32a092 100644 --- a/01_Archive/2026-04-20/중독 재활 프로그램.md +++ b/01_Archive/2026-04-20/중독 재활 프로그램.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-383266 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 중독 재활 프로그램" --- -# [[중독 재활 프로그램]] +# [[중독 재활 프로그램|중독 재활 프로그램]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - 중독 재활 프로그램" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/중독 재활 프로그램.md]] +- Raw Source: 00_Raw/2026-04-20/중독 재활 프로그램.md --- diff --git a/01_Archive/2026-04-20/지식 그래프 (Knowledge Graph).md b/01_Archive/2026-04-20/지식 그래프 (Knowledge Graph).md index 520a1117..1b2967f3 100644 --- a/01_Archive/2026-04-20/지식 그래프 (Knowledge Graph).md +++ b/01_Archive/2026-04-20/지식 그래프 (Knowledge Graph).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-276A1A -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 지식 그래프 (Knowledge Graph)" --- -# [[지식 그래프 (Knowledge Graph)]] +# [[지식 그래프 (Knowledge Graph)|지식 그래프 (Knowledge Graph)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - 지식 그래프 (Knowledge Gr ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/지식 그래프 (Knowledge Graph).md]] +- Raw Source: 00_Raw/2026-04-20/지식 그래프 (Knowledge Graph).md --- diff --git a/01_Archive/2026-04-20/지식 베이스 (Knowledge Base).md b/01_Archive/2026-04-20/지식 베이스 (Knowledge Base).md index a63a6229..bc3d240a 100644 --- a/01_Archive/2026-04-20/지식 베이스 (Knowledge Base).md +++ b/01_Archive/2026-04-20/지식 베이스 (Knowledge Base).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-295580 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 지식 베이스 (Knowledge Base)" --- -# [[지식 베이스 (Knowledge Base)]] +# [[지식 베이스 (Knowledge Base)|지식 베이스 (Knowledge Base)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - 지식 베이스 (Knowledge Ba ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/지식 베이스 (Knowledge Base).md]] +- Raw Source: 00_Raw/2026-04-20/지식 베이스 (Knowledge Base).md --- diff --git a/01_Archive/2026-04-20/직렬화(Serialization) 및 병목 현상.md b/01_Archive/2026-04-20/직렬화(Serialization) 및 병목 현상.md index 3d327fae..9b56b582 100644 --- a/01_Archive/2026-04-20/직렬화(Serialization) 및 병목 현상.md +++ b/01_Archive/2026-04-20/직렬화(Serialization) 및 병목 현상.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-9AD769 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 직렬화(Serialization) 및 병목 현상" --- -# [[직렬화(Serialization) 및 병목 현상]] +# [[직렬화(Serialization) 및 병목 현상|직렬화(Serialization) 및 병목 현상]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - 직렬화(Serialization) 및 ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/직렬화(Serialization) 및 병목 현상.md]] +- Raw Source: 00_Raw/2026-04-20/직렬화(Serialization) 및 병목 현상.md --- diff --git a/01_Archive/2026-04-20/직무 특성 모델 (Job Characteristics Model).md b/01_Archive/2026-04-20/직무 특성 모델 (Job Characteristics Model).md index 50acb412..8eb6b3e4 100644 --- a/01_Archive/2026-04-20/직무 특성 모델 (Job Characteristics Model).md +++ b/01_Archive/2026-04-20/직무 특성 모델 (Job Characteristics Model).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-599CE0 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 직무 특성 모델 (Job Characteristics Model)" --- -# [[직무 특성 모델 (Job Characteristics Model)]] +# [[직무 특성 모델 (Job Characteristics Model)|직무 특성 모델 (Job Characteristics Model)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - 직무 특성 모델 (Job Char ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/직무 특성 모델 (Job Characteristics Model).md]] +- Raw Source: 00_Raw/2026-04-20/직무 특성 모델 (Job Characteristics Model).md --- diff --git a/01_Archive/2026-04-20/집합론 (Set Theory).md b/01_Archive/2026-04-20/집합론 (Set Theory).md index bf4e5911..6f31fc69 100644 --- a/01_Archive/2026-04-20/집합론 (Set Theory).md +++ b/01_Archive/2026-04-20/집합론 (Set Theory).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-20C803 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 집합론 (Set Theory)" --- -# [[집합론 (Set Theory)]] +# [[집합론 (Set Theory)|집합론 (Set Theory)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 집합론(Set Theory)은 객체들의 순서 없는 모임(unordered collections of objects)을 다루는 수학적 이론입니다 [1]. TypeScript의 맥락에서 집합론은 '타입(Type)'을 JavaScript 값들의 집합으로 이해하고 해석하는 모델로 사용됩니다 [2, 3]. 이를 통해 서브타입(subtype), 유니언(union), 인터섹션(intersection) 등의 복잡한 타입 시스템 동작 원리를 부분집합, 합집합, 교집합과 같은 수학적 집합 개념으로 명확하게 설명할 수 있습니다 [2, 4, 5]. @@ -35,11 +35,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 집합론 (Set Theory)" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[TypeScript Type System]], [[Structural Typing]], [[Union and Intersection Types]] -- **Projects/Contexts:** [[TypeScript의 타입 연산과 조건부 타입(Conditional Types)의 동작 원리 이해 및 인터페이스 설계]] +- **Related Topics:** [[TypeScript-Type-System|TypeScript Type System]], [[Structural Typing|Structural Typing]], Union and Intersection Types +- **Projects/Contexts:** TypeScript의 타입 연산과 조건부 타입(Conditional Types)의 동작 원리 이해 및 인터페이스 설계 - **Contradictions/Notes:** 객체(Object) 타입에 대한 `&`(인터섹션) 연산이나 `|`(유니언) 연산은 객체의 형태(Shape)를 단순히 결합하는 것이 아니라, 해당 객체 형태를 만족하는 '값들의 집합'에 대한 교집합 및 합집합 연산으로 작동합니다. 따라서 `{ name: string } & { age: number }`는 두 속성을 모두 가진 객체들의 교집합을 의미하게 됩니다 [9, 10]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/집합론 (Set Theory).md]] +- Raw Source: 00_Raw/2026-04-20/집합론 (Set Theory).md --- diff --git a/01_Archive/2026-04-20/집합론(Set Theory).md b/01_Archive/2026-04-20/집합론(Set Theory).md index 677e5a40..12a8f786 100644 --- a/01_Archive/2026-04-20/집합론(Set Theory).md +++ b/01_Archive/2026-04-20/집합론(Set Theory).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-1B9760 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 집합론(Set Theory)" --- -# [[집합론(Set Theory)]] +# [[집합론(Set Theory)|집합론(Set Theory)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 집합론(Set Theory)은 TypeScript의 타입 시스템을 이해하는 핵심적인 철학이자 접근 방식으로, 타입을 가능한 자바스크립트 값들의 '집합'으로 간주하는 개념입니다 [1, 2]. 이 관점을 통해 타입 간의 호환성, 합집합과 교집합 연산, 그리고 타입의 서브타입(Subtype) 및 슈퍼타입(Supertype) 관계를 수학적 집합의 원리로 명확하게 설명할 수 있습니다 [2-5]. @@ -25,11 +25,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 집합론(Set Theory)" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[TypeScript Type System]], [[Structural Typing]], [[Union and Intersection Types]] -- **Projects/Contexts:** [[TypeScript Interface Design]], [[Type Narrowing and Widening]] +- **Related Topics:** [[TypeScript-Type-System|TypeScript Type System]], [[Structural Typing|Structural Typing]], Union and Intersection Types +- **Projects/Contexts:** [[TypeScript Interface Design|TypeScript Interface Design]], Type Narrowing and Widening - **Contradictions/Notes:** TypeScript의 `any` 타입은 집합론으로 완벽히 설명되지 않는 예외적인 존재입니다. 모든 세트를 부분집합으로 허용하면서도 동시에 스스로가 비어있을 수(`never`) 있는 '역설적인(paradoxical)' 집합으로 동작하기 때문에 일반적인 집합론의 논리를 따르지 않습니다 [7, 9]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/집합론(Set Theory).md]] +- Raw Source: 00_Raw/2026-04-20/집합론(Set Theory).md --- diff --git a/01_Archive/2026-04-20/창발 능력 (Emergent Abilities).md b/01_Archive/2026-04-20/창발 능력 (Emergent Abilities).md index 7d8ef2d1..7022dc6c 100644 --- a/01_Archive/2026-04-20/창발 능력 (Emergent Abilities).md +++ b/01_Archive/2026-04-20/창발 능력 (Emergent Abilities).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-9DBA7B -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 창발 능력 (Emergent Abilities)" --- -# [[창발 능력 (Emergent Abilities)]] +# [[창발 능력 (Emergent Abilities)|창발 능력 (Emergent Abilities)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - 창발 능력 (Emergent Abilit ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/창발 능력 (Emergent Abilities).md]] +- Raw Source: 00_Raw/2026-04-20/창발 능력 (Emergent Abilities).md --- diff --git a/01_Archive/2026-04-20/철벽 수비대 인터페이스 설계 전략.md b/01_Archive/2026-04-20/철벽 수비대 인터페이스 설계 전략.md index ea52c8e1..6171069d 100644 --- a/01_Archive/2026-04-20/철벽 수비대 인터페이스 설계 전략.md +++ b/01_Archive/2026-04-20/철벽 수비대 인터페이스 설계 전략.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-CE3C8E -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 철벽 수비대 인터페이스 설계 전략" --- -# [[철벽 수비대 인터페이스 설계 전략]] +# [[철벽 수비대 인터페이스 설계 전략|철벽 수비대 인터페이스 설계 전략]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 철벽 수비대 인터페이스 설계 전략은 대규모 애플리케이션 개발 시 발생하는 런타임 에러와 무분별한 상태 변경의 불확실성을 방어하기 위한 TypeScript 아키텍처 방법론입니다 [1]. 이 전략은 구조적 타이핑의 유연함을 살리면서도 과잉 속성 체크, 불변성, 식별 가능한 유니온 등의 강력한 수비 기제를 통해 의도치 않은 데이터 유입과 예기치 않은 상태 변경을 차단합니다 [1-4]. 또한, 인터페이스와 타입 별칭의 전략적 분리, 브랜디드 타입을 적극적으로 활용하여 비즈니스 로직을 엄격하게 보호합니다 [5, 6]. 궁극적으로 이 설계 전략은 개발자에게 심리적 안전감을 제공하고, 확장에 열려 있으면서도 변화에 따른 부작용을 최소화하는 견고한 시스템 구축을 목표로 합니다 [7, 8]. @@ -25,11 +25,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 철벽 수비대 인터페이 - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[구조적 타이핑]], [[과잉 속성 체크(EPC)]], [[식별 가능한 유니온]], [[브랜디드 타입]], [[불변성(Immutability)]], [[satisfies 연산자]], [[SOLID 원칙]] -- **Projects/Contexts:** [[대규모 애플리케이션 개발]], [[도메인 기반 설계(DDD)]], [[토스(Toss) SDK 설계]] +- **Related Topics:** [[구조적 타이핑|구조적 타이핑]], [[과잉 속성 체크(EPC)|과잉 속성 체크(EPC)]], [[식별 가능한 유니온|식별 가능한 유니온]], [[브랜디드 타입|브랜디드 타입]], [[불변성(Immutability)|불변성(Immutability)]], [[satisfies 연산자|satisfies 연산자]], [[SOLID 원칙|SOLID 원칙]] +- **Projects/Contexts:** [[대규모 애플리케이션 개발|대규모 애플리케이션 개발]], [[도메인 기반 설계(DDD)|도메인 기반 설계(DDD)]], [[토스(Toss) SDK 설계|토스(Toss) SDK 설계]] - **Contradictions/Notes:** 과잉 속성 체크(EPC)는 객체 리터럴을 직접 할당할 때만 작동하고 변수 간접 할당 시 우회되는 약점이 존재하나, 이는 `satisfies` 연산자를 도입하여 우아하게 해결할 수 있습니다 [11, 12]. 또한 TypeScript는 인터페이스의 선언 병합을 허용하여 확장에 용이하지만 이로 인한 의도치 않은 병합의 위험이 존재하므로, 핵심 로직에서는 재선언이 불가한 타입 별칭(Type Alias)을 혼용하는 전략이 필수적입니다 [5, 9]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/철벽 수비대 인터페이스 설계 전략.md]] +- Raw Source: 00_Raw/2026-04-20/철벽 수비대 인터페이스 설계 전략.md --- diff --git a/01_Archive/2026-04-20/철벽 수비대_ - TypeScript 타입 시스템 (인터페이스 설계).md b/01_Archive/2026-04-20/철벽 수비대_ - TypeScript 타입 시스템 (인터페이스 설계).md index 0a236630..89f5d5db 100644 --- a/01_Archive/2026-04-20/철벽 수비대_ - TypeScript 타입 시스템 (인터페이스 설계).md +++ b/01_Archive/2026-04-20/철벽 수비대_ - TypeScript 타입 시스템 (인터페이스 설계).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-A8177A -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 철벽 수비대_ - TypeScript 타입 시스템 (인터페이스 설계)" --- -# [[철벽 수비대_ - TypeScript 타입 시스템 (인터페이스 설계)]] +# [[철벽 수비대_ - TypeScript 타입 시스템 (인터페이스 설계)|철벽 수비대_ - TypeScript 타입 시스템 (인터페이스 설계)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > TypeScript의 타입 시스템은 구조적 타이핑(Structural Typing)을 기반으로 유연성을 제공하면서도, 런타임 에러와 예기치 않은 상태 변경으로부터 애플리케이션을 보호하는 아키텍처적 도구입니다. 견고한 수비 체계를 구축하기 위해서는 성능과 확장성을 고려하여 인터페이스(Interface)와 타입 별칭(Type Alias)을 전략적으로 선택해야 합니다. 또한, 불변성 보장, 식별 가능한 유니온, 브랜디드 타입 등 고급 설계 기법을 활용하여 외부의 불안정한 데이터와 내부의 예기치 않은 상태 변경으로부터 시스템을 안전하게 지켜낼 수 있습니다. @@ -33,11 +33,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 철벽 수비대_ - TypeScript - **정책 변화:** Design & Experience 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[구조적 타이핑 (Structural Typing)]], [[선언 병합 (Declaration Merging)]], [[식별 가능한 유니온 (Discriminated Unions)]], [[브랜디드 타입 (Branded Types)]], [[satisfies 연산자]] -- **Projects/Contexts:** [[대규모 애플리케이션 개발]], [[도메인 기반 설계 (DDD)]] +- **Related Topics:** [[구조적 타이핑 (Structural Typing)|구조적 타이핑 (Structural Typing)]], [[선언 병합 (Declaration Merging)|선언 병합 (Declaration Merging)]], [[식별 가능한 유니온 (Discriminated Unions)|식별 가능한 유니온 (Discriminated Unions)]], [[브랜디드 타입 (Branded Types)|브랜디드 타입 (Branded Types)]], [[satisfies 연산자|satisfies 연산자]] +- **Projects/Contexts:** [[대규모 애플리케이션 개발|대규모 애플리케이션 개발]], [[도메인 기반 설계 (DDD)|도메인 기반 설계 (DDD)]] - **Contradictions/Notes:** 과잉 속성 체크(EPC)는 객체 리터럴을 직접 다룰 때만 활성화되어 간접 할당 시 우회될 수 있다는 취약점이 있으나, TypeScript 4.9부터 도입된 satisfies 연산자를 통해 이 문제를 해결하고 엄격한 속성 검사를 수행할 수 있습니다 [9, 10]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/철벽 수비대_ - TypeScript 타입 시스템 (인터페이스 설계).md]] +- Raw Source: 00_Raw/2026-04-20/철벽 수비대_ - TypeScript 타입 시스템 (인터페이스 설계).md --- diff --git a/01_Archive/2026-04-20/철벽 수비대_ TypeScript 타입 시스템과 견고한 인터페이스 설계의 정수.md b/01_Archive/2026-04-20/철벽 수비대_ TypeScript 타입 시스템과 견고한 인터페이스 설계의 정수.md index 29b37799..9ec0e0dc 100644 --- a/01_Archive/2026-04-20/철벽 수비대_ TypeScript 타입 시스템과 견고한 인터페이스 설계의 정수.md +++ b/01_Archive/2026-04-20/철벽 수비대_ TypeScript 타입 시스템과 견고한 인터페이스 설계의 정수.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-31F1D8 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 철벽 수비대_ TypeScript 타입 시스템과 견고한 인터페이스 설계의 정수" --- -# [[철벽 수비대_ TypeScript 타입 시스템과 견고한 인터페이스 설계의 정수]] +# [[철벽 수비대_ TypeScript 타입 시스템과 견고한 인터페이스 설계의 정수|철벽 수비대_ TypeScript 타입 시스템과 견고한 인터페이스 설계의 정수]] ## 📌 한 줄 통찰 (The Karpathy Summary) > TypeScript는 자바스크립트의 유연함이 초래하는 런타임 에러의 불확실성을 극복하기 위해 도입된 정적 타입 시스템으로, 복잡한 비즈니스 로직을 보호하는 철벽 수비대와 같은 역할을 수행한다 [1]. 이 시스템은 구조적 타이핑(Structural Typing)을 기반으로 객체의 형태에 따라 타입을 결정하며, 개발자의 의도를 명확히 규정하는 아키텍처 도구로 작용한다 [1, 2]. 효과적인 방어 체계 구축을 위해 개발자는 인터페이스와 타입 별칭의 전략적 분리, 불변성(readonly)의 확립, 식별 가능한 유니온 및 브랜디드 타입과 같은 고급 기법을 활용하여 외부의 오염된 데이터와 예기치 않은 상태 변경으로부터 시스템을 안전하게 지켜낼 수 있다 [1, 3-5]. @@ -33,11 +33,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 철벽 수비대_ TypeScript - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[구조적 타이핑 (Structural Typing)]], [[과잉 속성 체크 (Excess Property Checking) 및 satisfies 연산자]], [[식별 가능한 유니온 (Discriminated Unions)]], [[브랜디드 타입 (Branded Types)]], [[불변성 (Immutability) 및 DeepReadonly]], [[SOLID 원칙 및 Facade 패턴]] -- **Projects/Contexts:** [[대규모 프론트엔드 및 백엔드 애플리케이션 개발]], [[도메인 기반 설계 (DDD)]], [[안전한 API 응답 데이터 파싱 및 매핑]], [[토스(Toss) Front 외부 연동 SDK 인터페이스 설계 사례]] +- **Related Topics:** [[구조적 타이핑 (Structural Typing)|구조적 타이핑 (Structural Typing)]], 과잉 속성 체크 (Excess Property Checking) 및 satisfies 연산자, [[식별 가능한 유니온 (Discriminated Unions)|식별 가능한 유니온 (Discriminated Unions)]], [[브랜디드 타입 (Branded Types)|브랜디드 타입 (Branded Types)]], 불변성 (Immutability) 및 DeepReadonly, SOLID 원칙 및 Facade 패턴 +- **Projects/Contexts:** 대규모 프론트엔드 및 백엔드 애플리케이션 개발, [[도메인 기반 설계 (DDD)|도메인 기반 설계 (DDD)]], 안전한 API 응답 데이터 파싱 및 매핑, 토스(Toss) Front 외부 연동 SDK 인터페이스 설계 사례 - **Contradictions/Notes:** `Interface`와 `Type Alias`의 사용에 관해 일부 개발자 팀(예: Reddit 커뮤니티의 여러 팀)은 선언 병합의 부작용을 피하고 문법의 일관성을 위해 전역적으로 `Type`만을 강제하여 사용하기도 한다. 그러나 TypeScript 공식 문서 및 컴파일러 성능 가이드에서는 객체 구조 확장이 필요하고 캐싱 성능이 중요한 경우 `Interface`를 우선하여 사용할 것을 권장하는 등 실무적인 논쟁과 트레이드오프가 존재한다 [15, 19-21, 53-55]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/철벽 수비대_ TypeScript 타입 시스템과 견고한 인터페이스 설계의 정수.md]] +- Raw Source: 00_Raw/2026-04-20/철벽 수비대_ TypeScript 타입 시스템과 견고한 인터페이스 설계의 정수.md --- diff --git a/01_Archive/2026-04-20/초과 속성 검사 (Excess Property Checking).md b/01_Archive/2026-04-20/초과 속성 검사 (Excess Property Checking).md index d156dd37..bb94fdcc 100644 --- a/01_Archive/2026-04-20/초과 속성 검사 (Excess Property Checking).md +++ b/01_Archive/2026-04-20/초과 속성 검사 (Excess Property Checking).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-BD62E2 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 초과 속성 검사 (Excess Property Checking)" --- -# [[초과 속성 검사 (Excess Property Checking)]] +# [[초과 속성 검사 (Excess Property Checking)|초과 속성 검사 (Excess Property Checking)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 초과 속성 검사(Excess Property Checking)는 TypeScript에서 객체 리터럴을 다른 변수에 직접 할당하거나 함수의 인수로 전달할 때, 예상치 못한(정의되지 않은) 속성이 객체에 포함되어 있는지 감지하여 에러를 발생시키는 기능입니다 [1-5]. 이는 개발자가 속성 이름에 오타를 내거나 잘못된 속성을 전달하는 실수를 방지하여 의도치 않은 런타임 동작을 막기 위해 존재합니다 [6-8]. 하지만 객체를 중간 변수에 먼저 할당한 후 전달하면 구조적 타이핑의 원칙에 따라 이 검사를 우회하게 되는 특징이 있습니다 [6, 9, 10]. @@ -31,11 +31,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 초과 속성 검사 (Excess P - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[구조적 타이핑 (Structural Typing)]], [[satisfies 연산자]] -- **Projects/Contexts:** [[typescript-eslint]] +- **Related Topics:** [[구조적 타이핑 (Structural Typing)|구조적 타이핑 (Structural Typing)]], [[satisfies 연산자|satisfies 연산자]] +- **Projects/Contexts:** typescript-eslint - **Contradictions/Notes:** TypeScript는 근본적으로 속성 집합의 포함 관계만 확인하는 '구조적 타이핑' 원칙을 따르지만, 객체 리터럴을 직접 다루는 맥락에서는 이러한 유연성을 예외적으로 차단하고 '초과 속성 검사'라는 더 엄격한 잣대를 적용한다는 점에서 뚜렷한 동작의 대비를 보입니다 [1, 6, 11]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/초과 속성 검사 (Excess Property Checking).md]] +- Raw Source: 00_Raw/2026-04-20/초과 속성 검사 (Excess Property Checking).md --- diff --git a/01_Archive/2026-04-20/초과 속성 검사 (Excess Property Checks).md b/01_Archive/2026-04-20/초과 속성 검사 (Excess Property Checks).md index 3fc18e9d..6c5eea0f 100644 --- a/01_Archive/2026-04-20/초과 속성 검사 (Excess Property Checks).md +++ b/01_Archive/2026-04-20/초과 속성 검사 (Excess Property Checks).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-920865 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 초과 속성 검사 (Excess Property Checks)" --- -# [[초과 속성 검사 (Excess Property Checks)]] +# [[초과 속성 검사 (Excess Property Checks)|초과 속성 검사 (Excess Property Checks)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 초과 속성 검사(Excess Property Checks)는 TypeScript에서 객체 리터럴을 다른 변수에 직접 할당하거나 함수의 인자로 전달할 때, 대상 타입에 정의되지 않은 예상치 못한 속성이 포함되어 있는지 확인하여 에러를 발생시키는 엄격한 타입 검사 기능입니다 [1-3]. 이는 속성 이름의 오타나 잘못된 데이터가 유입되는 실수를 컴파일 시점에 포착하여, 의도하지 않은 런타임 동작을 방어하는 핵심적인 수비 기제 역할을 합니다 [4-6]. @@ -29,11 +29,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 초과 속성 검사 (Excess P - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[구조적 타이핑 (Structural Typing)]], [[객체 리터럴 (Object Literals)]], [[satisfies 연산자]] -- **Projects/Contexts:** [[typescript-eslint]] (초과 속성 검사가 변수 할당 시 우회되는 문제를 해결하기 위해 `no-excess-properties`라는 새로운 린트 규칙이 제안되었으나, 유연성 및 복잡도 문제로 반영되지 않음 [12, 17, 18]), [[React 컴포넌트 프로퍼티 검증]] (우회된 초과 속성이 예기치 못한 리렌더링을 일으키는 대표적 맥락 [11]) +- **Related Topics:** [[구조적 타이핑 (Structural Typing)|구조적 타이핑 (Structural Typing)]], 객체 리터럴 (Object Literals), [[satisfies 연산자|satisfies 연산자]] +- **Projects/Contexts:** typescript-eslint (초과 속성 검사가 변수 할당 시 우회되는 문제를 해결하기 위해 `no-excess-properties`라는 새로운 린트 규칙이 제안되었으나, 유연성 및 복잡도 문제로 반영되지 않음 [12, 17, 18]), React 컴포넌트 프로퍼티 검증 (우회된 초과 속성이 예기치 못한 리렌더링을 일으키는 대표적 맥락 [11]) - **Contradictions/Notes:** TypeScript의 기본 철학인 '구조적 타이핑'은 최소 요건만 맞으면 추가 속성을 허용한다는 입장이지만, '초과 속성 검사'는 추가 속성을 에러로 처리한다는 점에서 타입 시스템 내에서 서로 상반되는 규칙처럼 보일 수 있습니다. 이는 TypeScript가 개발자의 '실수 방지'를 위해 객체 리터럴에만 부여한 의도적 예외 동작입니다 [1, 7]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/초과 속성 검사 (Excess Property Checks).md]] +- Raw Source: 00_Raw/2026-04-20/초과 속성 검사 (Excess Property Checks).md --- diff --git a/01_Archive/2026-04-20/추론 엔진 (Semantic Reasoner).md b/01_Archive/2026-04-20/추론 엔진 (Semantic Reasoner).md index 7a94df9b..1beb287b 100644 --- a/01_Archive/2026-04-20/추론 엔진 (Semantic Reasoner).md +++ b/01_Archive/2026-04-20/추론 엔진 (Semantic Reasoner).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-A3E15F -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 추론 엔진 (Semantic Reasoner)" --- -# [[추론 엔진 (Semantic Reasoner)]] +# [[추론 엔진 (Semantic Reasoner)|추론 엔진 (Semantic Reasoner)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - 추론 엔진 (Semantic Reason ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/추론 엔진 (Semantic Reasoner).md]] +- Raw Source: 00_Raw/2026-04-20/추론 엔진 (Semantic Reasoner).md --- diff --git a/01_Archive/2026-04-20/추상 구문 트리(AST).md b/01_Archive/2026-04-20/추상 구문 트리(AST).md index a6319039..78d1ff9f 100644 --- a/01_Archive/2026-04-20/추상 구문 트리(AST).md +++ b/01_Archive/2026-04-20/추상 구문 트리(AST).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-0C0765 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 추상 구문 트리(AST)" --- -# [[추상 구문 트리(AST)]] +# [[추상 구문 트리(AST)|추상 구문 트리(AST)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 추상 구문 트리(AST, Abstract Syntax Tree)는 소스 코드를 파싱하여 언어의 문법적 구조와 형태를 표현한 트리 형태의 데이터 구조입니다 [1, 2]. 콘크리트 구문 트리(CST)와 달리 코드의 레이아웃이나 주석, 매크로 등은 기본적으로 포함하지 않고 핵심적인 구문(Syntax) 및 어휘(Lexical) 기능만을 보존하는 것이 특징입니다 [1, 3]. 정적 애플리케이션 보안 테스트(SAST), 린터(Linter) 도구, 그리고 개발자의 코딩 스타일을 분석하는 코드 스타일로메트리(Code Stylometry) 등에서 소스 코드를 구조적으로 분석하고 특징을 추출하는 핵심 기반 기술로 사용됩니다 [2, 4, 5]. @@ -22,11 +22,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 추상 구문 트리(AST)" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[콘크리트 구문 트리(CST)]], [[코드 스타일로메트리(Code Stylometry)]], [[정적 애플리케이션 보안 테스트(SAST)]] -- **Projects/Contexts:** [[ESLint]], [[code2vec]], [[Google Code Jam 데이터셋]] +- **Related Topics:** 콘크리트 구문 트리(CST), [[코드 스타일로메트리 (Code Stylometry)|코드 스타일로메트리(Code Stylometry)]], [[정적 애플리케이션 보안 테스트(SAST)|정적 애플리케이션 보안 테스트(SAST)]] +- **Projects/Contexts:** [[ESLint|ESLint]], code2vec, Google Code Jam 데이터셋 - **Contradictions/Notes:** 소스 코드의 저자 식별 시 AST를 활용하면 저자 고유의 구문적 특성을 성공적으로 추출할 수 있지만, 레이아웃 정보가 누락되기 때문에 CST를 활용한 분석에 비해 정확도가 떨어진다는 점이 연구 결과로 입증되었습니다(AST 기반 51%에서 CST 기반 68%로 정확도 상승) [8]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/추상 구문 트리(AST).md]] +- Raw Source: 00_Raw/2026-04-20/추상 구문 트리(AST).md --- diff --git a/01_Archive/2026-04-20/추상화(Abstraction).md b/01_Archive/2026-04-20/추상화(Abstraction).md index 39a28a05..bc6982e9 100644 --- a/01_Archive/2026-04-20/추상화(Abstraction).md +++ b/01_Archive/2026-04-20/추상화(Abstraction).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-766E2E -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 추상화(Abstraction)" --- -# [[추상화(Abstraction)]] +# [[추상화(Abstraction)|추상화(Abstraction)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 추상화(Abstraction)는 복잡한 내부 구현을 숨기고 사용자의 '의도(Intent)'나 이상적인 형태(인터페이스)를 기준으로 코드를 단순하게 재구성하는 소프트웨어 설계 기법입니다 [1, 2]. 의존성 역전 원칙(DIP)의 핵심 개념으로, 상위 모듈과 하위 모듈이 구체적인 세부 사항이 아닌 추상화에 의존하도록 만들어 시스템의 결합도를 낮추고 인지 부하를 줄입니다 [2, 3]. 그러나 도메인을 충분히 이해하지 못한 상태에서의 과도한 추상화는 오히려 시스템의 복잡성을 폭발시키고 개발 속도를 늦출 수 있으므로 주의가 필요합니다 [4, 5]. @@ -29,11 +29,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 추상화(Abstraction)" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[의존성 역전 원칙(Dependency Inversion Principle)]], [[퍼사드 패턴(Facade Pattern)]], [[이른 추상화(Premature Abstraction)]], [[오버엔지니어링(Over-Engineering)]] -- **Projects/Contexts:** [[Toss Front SDK 설계]], [[SOLID Design Principles]], [[TypeScript 아키텍처 설계]] +- **Related Topics:** [[의존성 역전 원칙 (Dependency Inversion Principle)|의존성 역전 원칙(Dependency Inversion Principle)]], 퍼사드 패턴(Facade Pattern), 이른 추상화(Premature Abstraction), 오버엔지니어링(Over-Engineering) +- **Projects/Contexts:** Toss Front SDK 설계, SOLID Design Principles, TypeScript 아키텍처 설계 - **Contradictions/Notes:** 소스에서는 추상화가 시스템을 모듈화하고 결합도를 낮추는 강력한 도구임을 강조하지만, 동시에 "모든 컴퓨터 과학의 문제는 또 다른 추상화 계층으로 해결할 수 있지만, 그 추상화 계층 자체가 문제가 된다"는 모순적 특성을 지적하며 무분별한 추상화의 위험성을 경고합니다 [4, 6, 7]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/추상화(Abstraction).md]] +- Raw Source: 00_Raw/2026-04-20/추상화(Abstraction).md --- diff --git a/01_Archive/2026-04-20/추상화.md b/01_Archive/2026-04-20/추상화.md index 122ade5c..97b6a128 100644 --- a/01_Archive/2026-04-20/추상화.md +++ b/01_Archive/2026-04-20/추상화.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-0EA2E7 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 추상화" --- -# [[추상화]] +# [[추상화|추상화]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 추상화는 소프트웨어 설계에서 공통된 기능이나 비즈니스 로직을 추출하여 재사용 가능한 컴포넌트, 인터페이스 또는 기반 클래스로 분리하는 기법입니다 [1, 2]. 이를 통해 시스템의 결합도를 낮추고 유연성을 높이며 코드의 중복을 방지할 수 있습니다 [2, 3]. 하지만 지나치고 성급한 추상화는 오히려 시스템의 복잡성을 증가시키고 인지적 부하를 높일 수 있으므로, 실제 중복이 발생했을 때 실용적으로 적용하는 절제력이 필요합니다 [4-6]. @@ -27,11 +27,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 추상화" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[DRY 원칙]], [[의존성 역전 원칙(DIP)]], [[개방-폐쇄 원칙(OCP)]], [[관심사의 분리(SoC)]], [[Rule of Three]], [[YAGNI]] -- **Projects/Contexts:** [[소프트웨어 아키텍처 설계]], [[객체 지향 프로그래밍(OOP)]] +- **Related Topics:** DRY 원칙, [[의존성 역전 원칙 (DIP)|의존성 역전 원칙(DIP)]], 개방-폐쇄 원칙(OCP), [[관심사의 분리(SoC)|관심사의 분리(SoC)]], [[Rule of Three|Rule of Three]], YAGNI +- **Projects/Contexts:** [[소프트웨어 아키텍처 설계|소프트웨어 아키텍처 설계]], [[객체 지향 프로그래밍(OOP)|객체 지향 프로그래밍(OOP)]] - **Contradictions/Notes:** 소스 문헌들은 추상화가 시스템을 유연하게 하고 결합도를 낮추는 핵심 도구라고 강조하면서도 동시에, 지나치거나 성급한 추상화는 오히려 개발자의 인지적 부하를 높이고 코드를 복잡하게 만드는 부작용(오버엔지니어링)을 낳을 수 있다고 양면성을 경고합니다 [2, 5, 7]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/추상화.md]] +- Raw Source: 00_Raw/2026-04-20/추상화.md --- diff --git a/01_Archive/2026-04-20/치타 사람 이미지 프롬프트.md b/01_Archive/2026-04-20/치타 사람 이미지 프롬프트.md index 5a528a9b..941729ef 100644 --- a/01_Archive/2026-04-20/치타 사람 이미지 프롬프트.md +++ b/01_Archive/2026-04-20/치타 사람 이미지 프롬프트.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-8EC391 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 치타 사람 이미지 프롬프트" --- -# [[치타 사람 이미지 프롬프트]] +# [[치타 사람 이미지 프롬프트|치타 사람 이미지 프롬프트]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 거대한 모래 치타의 추격을 받으며 사막을 질주하는 육상 선수를 통해 속도감과 자연의 힘을 초현실적으로 담아낸 시네마틱 컨셉 아트 프롬프트입니다. @@ -20,9 +20,9 @@ github_commit: "[P-Reinforce] Continuous Worker - 치타 사람 이미지 프롬 - **정책 변화:** Design & Experience 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[VFX Particle Simulation]], [[Cinematic Sports Advertising]], [[Surrealism Concept Art]] +- **Related Topics:** VFX Particle Simulation, Cinematic Sports Advertising, Surrealism Concept Art -- **Projects/Contexts:** [[Sportswear Brand Campaign Visuals]] +- **Projects/Contexts:** Sportswear Brand Campaign Visuals - **Contradictions/Notes:** 치타는 고체 형태의 동물이 아니라 수백만 개의 모래와 먼지로 이루어진 볼륨 시뮬레이션(Volumetric Simulation)이므로 경계면이 모래폭풍 속으로 자연스럽게 흩어지도록 연출 요망 @@ -30,5 +30,5 @@ github_commit: "[P-Reinforce] Continuous Worker - 치타 사람 이미지 프롬 --- _Last updated: 2026년 4월 14일_ -- Raw Source: [[00_Raw/2026-04-20/치타 사람 이미지 프롬프트.md]] +- Raw Source: 00_Raw/2026-04-20/치타 사람 이미지 프롬프트.md --- diff --git a/01_Archive/2026-04-20/카산드라(Cassandra).md b/01_Archive/2026-04-20/카산드라(Cassandra).md index 5cafeb73..5a977612 100644 --- a/01_Archive/2026-04-20/카산드라(Cassandra).md +++ b/01_Archive/2026-04-20/카산드라(Cassandra).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-A802F0 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 카산드라(Cassandra)" --- -# [[카산드라(Cassandra)]] +# [[카산드라(Cassandra)|카산드라(Cassandra)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 카산드라(Cassandra)는 기존의 RDBMS를 대체하여 대규모 데이터 환경(NoSQL at scale)을 지원하기 위해 사용되는 오픈 소스 기반의 데이터베이스입니다 [1]. 다중 리전(Multi-Regional) 및 다방향(Multi-directional) 아키텍처를 지원하며, 가용성(Available)과 파티션 허용성(Partition Tolerance)을 제공하는 것이 특징입니다 [1]. 넷플릭스(Netflix)의 마이크로서비스 아키텍처에서 인프라의 핵심 데이터 저장소로 활용되었습니다 [1, 2]. @@ -28,11 +28,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 카산드라(Cassandra)" - **정책 변화:** AI 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[NoSQL]], [[RDBMS]], [[Microservices Architecture]], [[Tunable Consistency]] -- **Projects/Contexts:** [[넷플릭스 마이크로서비스 아키텍처 전환(Adopting Microservices at Netflix)]] +- **Related Topics:** NoSQL, RDBMS, [[마이크로서비스 아키텍처 (Microservices Architecture)|Microservices Architecture]], Tunable Consistency +- **Projects/Contexts:** 넷플릭스 마이크로서비스 아키텍처 전환(Adopting Microservices at Netflix) - **Contradictions/Notes:** 카산드라 자체에 대한 깊이 있는 기술적 원리보다는 넷플릭스의 마이크로서비스 도입 과정에서 RDBMS를 대체한 대규모 NoSQL 솔루션의 사례로서만 간략하게 언급되어 있어 추가적인 기술적 세부 정보는 소스에 관련 정보가 부족합니다 [1]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/카산드라(Cassandra).md]] +- Raw Source: 00_Raw/2026-04-20/카산드라(Cassandra).md --- diff --git a/01_Archive/2026-04-20/카오스 몽키(Chaos Monkey).md b/01_Archive/2026-04-20/카오스 몽키(Chaos Monkey).md index decdc493..682683a7 100644 --- a/01_Archive/2026-04-20/카오스 몽키(Chaos Monkey).md +++ b/01_Archive/2026-04-20/카오스 몽키(Chaos Monkey).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-E9B14A -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 카오스 몽키(Chaos Monkey)" --- -# [[카오스 몽키(Chaos Monkey)]] +# [[카오스 몽키(Chaos Monkey)|카오스 몽키(Chaos Monkey)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 카오스 몽키(Chaos Monkey)는 넷플릭스(Netflix)가 마이크로서비스 아키텍처(MSA)를 도입하는 과정에서 시스템의 회복 탄력성(Resiliency)을 검증하기 위해 사용한 자동화된 파괴 테스트(Automate destructive testing) 도구입니다 [1, 2]. 이 도구의 도입은 넷플릭스의 '시미안 아미(Simian Army)' 프로젝트가 시작되는 계기가 되었습니다 [2]. (소스에 관련 정보가 부족하여 더 이상의 자세한 정의는 제공하기 어렵습니다.) @@ -23,11 +23,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 카오스 몽키(Chaos Monkey) - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[자동화된 파괴 테스트(Automate destructive testing)]], [[시미안 아미(Simian Army)]], [[마이크로서비스 아키텍처(Microservice Architecture)]] -- **Projects/Contexts:** [[넷플릭스의 마이크로서비스 도입(Netflix journey to microservices)]] +- **Related Topics:** 자동화된 파괴 테스트(Automate destructive testing), 시미안 아미(Simian Army), 마이크로서비스 아키텍처(Microservice Architecture) +- **Projects/Contexts:** 넷플릭스의 마이크로서비스 도입(Netflix journey to microservices) - **Contradictions/Notes:** 주어진 소스 문서(Netflix's Microservices Adoption Case Study)에는 카오스 몽키에 대한 발표 슬라이드 수준의 단편적인 언급만 존재하며, 그 이상의 구체적인 정보는 포함되어 있지 않습니다 [2]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/카오스 몽키(Chaos Monkey).md]] +- Raw Source: 00_Raw/2026-04-20/카오스 몽키(Chaos Monkey).md --- diff --git a/01_Archive/2026-04-20/커뮤니티 탐지 (Community Detection).md b/01_Archive/2026-04-20/커뮤니티 탐지 (Community Detection).md index 7e2b9380..544fd0d8 100644 --- a/01_Archive/2026-04-20/커뮤니티 탐지 (Community Detection).md +++ b/01_Archive/2026-04-20/커뮤니티 탐지 (Community Detection).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-D5C627 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 커뮤니티 탐지 (Community Detection)" --- -# [[커뮤니티 탐지 (Community Detection)]] +# [[커뮤니티 탐지 (Community Detection)|커뮤니티 탐지 (Community Detection)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - 커뮤니티 탐지 (Community ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/커뮤니티 탐지 (Community Detection).md]] +- Raw Source: 00_Raw/2026-04-20/커뮤니티 탐지 (Community Detection).md --- diff --git a/01_Archive/2026-04-20/컴포넌트 기반 웹 프레임워크 아키텍처 설계.md b/01_Archive/2026-04-20/컴포넌트 기반 웹 프레임워크 아키텍처 설계.md index 0140dbb5..76ea7e1c 100644 --- a/01_Archive/2026-04-20/컴포넌트 기반 웹 프레임워크 아키텍처 설계.md +++ b/01_Archive/2026-04-20/컴포넌트 기반 웹 프레임워크 아키텍처 설계.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-F36267 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 컴포넌트 기반 웹 프레임워크 아키텍처 설계" --- -# [[컴포넌트 기반 웹 프레임워크 아키텍처 설계]] +# [[컴포넌트 기반 웹 프레임워크 아키텍처 설계|컴포넌트 기반 웹 프레임워크 아키텍처 설계]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 컴포넌트 기반 웹 프레임워크 아키텍처는 특정 기능이나 UI 요소를 구현하기 위해 HTML 구조, CSS 스타일, JavaScript 동작을 하나의 단위(컴포넌트)로 묶어 다루는 설계 방식입니다 [1]. 과거 기술적 역할 중심의 분리에서 벗어나 기능 중심의 수직적 모듈화를 통해 코드의 재사용성을 높이고 독립적인 개발과 테스트를 가능하게 합니다 [1, 2]. 프로젝트 규모가 커짐에 따라 발생하는 결합도 증가와 컴포넌트 비대화 문제를 해결하기 위해, 현대에는 마이크로 프론트엔드 및 FSD(Feature-Sliced Design)와 같은 발전된 아키텍처 방법론과 결합되어 사용됩니다 [3-5]. @@ -28,11 +28,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 컴포넌트 기반 웹 프레 - **정책 변화:** Design & Experience 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[관심사의 분리(Separation of Concerns)]], [[마이크로 프론트엔드(Micro Frontends)]], [[Feature-Sliced Design(FSD)]], [[단일 책임 원칙(SRP)]] -- **Projects/Contexts:** [[Spotify, Netflix, Amazon의 마이크로 프론트엔드 도입]], [[대규모 웹 애플리케이션의 폴더 구조 진화]] +- **Related Topics:** [[관심사의 분리(Separation of Concerns)|관심사의 분리(Separation of Concerns)]], [[마이크로 프론트엔드 (Micro Frontends)|마이크로 프론트엔드(Micro Frontends)]], [[Feature-Sliced Design (FSD)|Feature-Sliced Design(FSD)]], [[단일 책임 원칙(SRP)|단일 책임 원칙(SRP)]] +- **Projects/Contexts:** Spotify, Netflix, Amazon의 마이크로 프론트엔드 도입, 대규모 웹 애플리케이션의 폴더 구조 진화 - **Contradictions/Notes:** 컴포넌트 기반 아키텍처는 초기에 관심사 분리의 혁신으로 여겨졌으나, 점차 하나의 컴포넌트에 너무 많은 로직이 집중되며 독립성이 훼손되는 모순이 발생했습니다. 이를 해결하기 위해 기능 단위로 묶인 컴포넌트 내부에서 다시 데이터 로직과 뷰 로직의 역할을 나누는 계층적(Layer) 분리 방식이 재도입되었습니다 [4, 9, 12]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/컴포넌트 기반 웹 프레임워크 아키텍처 설계.md]] +- Raw Source: 00_Raw/2026-04-20/컴포넌트 기반 웹 프레임워크 아키텍처 설계.md --- diff --git a/01_Archive/2026-04-20/컴퓨트 셰이더(Compute Shaders).md b/01_Archive/2026-04-20/컴퓨트 셰이더(Compute Shaders).md index b4b1e303..c9a1ec47 100644 --- a/01_Archive/2026-04-20/컴퓨트 셰이더(Compute Shaders).md +++ b/01_Archive/2026-04-20/컴퓨트 셰이더(Compute Shaders).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-C4EB25 -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 컴퓨트 셰이더(Compute Shaders)" --- -# [[컴퓨트 셰이더(Compute Shaders)]] +# [[컴퓨트 셰이더(Compute Shaders)|컴퓨트 셰이더(Compute Shaders)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 컴퓨트 셰이더(Compute Shaders)는 JavaScript 메인 스레드에서 수행되던 무거운 작업을 수천 개의 GPU 코어에서 병렬로 처리하도록 오프로드하는 범용 GPU 연산(general-purpose GPU computation) 기술입니다 [1]. 주로 WebGPU 환경에서 사용되며, 파티클 시스템, 물리 시뮬레이션, 대규모 데이터 필터링 등의 CPU 병목 현상을 획기적으로 해결하여 렌더링 성능을 극대화하는 데 필수적인 역할을 합니다 [2-4]. @@ -32,11 +32,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 컴퓨트 셰이더(Compute Sh - **정책 변화:** Graphics & Performance 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[WebGPU]], [[GPU-driven Rendering]], [[TSL (Three Shader Language)]], [[Storage Textures]] -- **Projects/Contexts:** [[Three.js WebGPURenderer]], [[Native WebGPU]], [[대규모 건설/BIM 플랫폼 (Large-Scale Construction Viewers)]] +- **Related Topics:** [[WebGPU|WebGPU]], [[GPU-driven Rendering|GPU-driven Rendering]], [[TSL (Three Shader Language)|TSL (Three Shader Language)]], [[스토리지 텍스처(Storage Textures)|Storage Textures]] +- **Projects/Contexts:** [[Three.js WebGPURenderer|Three.js WebGPURenderer]], Native WebGPU, 대규모 건설/BIM 플랫폼 (Large-Scale Construction Viewers) - **Contradictions/Notes:** 컴퓨트 셰이더를 통한 GPU 병렬 연산은 압도적인 성능 향상을 가져오지만, 작업 디스패치 사이에 `await mapAsync()`를 무분별하게 사용하면 GPU 파이프라인이 멈추고 최대 60%의 시간 동안 GPU가 유휴 상태에 빠지는 성능 저하 역효과가 발생할 수 있으므로 주의해야 합니다 [11]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/컴퓨트 셰이더(Compute Shaders).md]] +- Raw Source: 00_Raw/2026-04-20/컴퓨트 셰이더(Compute Shaders).md --- diff --git a/01_Archive/2026-04-20/코드 리뷰 (Code Review).md b/01_Archive/2026-04-20/코드 리뷰 (Code Review).md index f3b70753..dd560b4b 100644 --- a/01_Archive/2026-04-20/코드 리뷰 (Code Review).md +++ b/01_Archive/2026-04-20/코드 리뷰 (Code Review).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-A3AFCE -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 코드 리뷰 (Code Review)" --- -# [[코드 리뷰 (Code Review)]] +# [[코드 리뷰 (Code Review)|코드 리뷰 (Code Review)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 코드 리뷰(Code Review)는 소스 코드의 품질, 보안 및 유지보수성을 보장하기 위해 코드를 검사하고 논의하는 프로세스입니다 [1-3]. 완벽함보다는 시간이 지남에 따라 코드베이스의 전반적인 건강 상태(Code health)를 지속적으로 개선하는 것을 목표로 하며, 개발 속도와 품질 간의 균형을 맞추는 것이 핵심입니다 [2, 4, 5]. 현대의 소프트웨어 개발에서는 아키텍처와 비즈니스 로직을 파악하는 인간의 '수동 코드 리뷰'와 문법 및 취약점을 빠르게 찾아내는 '자동화된 코드 리뷰'를 결합한 하이브리드 접근 방식이 최적의 표준으로 평가받고 있습니다 [1, 6, 7]. @@ -24,11 +24,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 코드 리뷰 (Code Review)" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[수동 코드 리뷰 (Manual Code Review)]], [[정적 애플리케이션 보안 테스트 (SAST)]], [[하이브리드 코드 리뷰 (Hybrid Code Review)]], [[린터 (Linter)]] -- **Projects/Contexts:** [[CI/CD 파이프라인 (CI/CD Pipelines)]], [[Pull Request (PR) 워크플로우]] +- **Related Topics:** [[수동 코드 리뷰 (Manual Code Review)|수동 코드 리뷰 (Manual Code Review)]], [[정적 애플리케이션 보안 테스트 (SAST)|정적 애플리케이션 보안 테스트 (SAST)]], [[하이브리드 코드 리뷰 (Hybrid Code Review)|하이브리드 코드 리뷰 (Hybrid Code Review)]], [[린터 (Linter)|린터 (Linter)]] +- **Projects/Contexts:** [[CI_CD 파이프라인 (CI_CD Pipelines)|CI/CD 파이프라인 (CI/CD Pipelines)]], [[Pull Request (PR) 워크플로우|Pull Request (PR) 워크플로우]] - **Contradictions/Notes:** 자동화된 코드 리뷰 도구는 매우 빠르고 일관성 있게 코드를 검사하지만, 비즈니스 로직과 아키텍처의 의도를 이해하지 못하므로 인간 리뷰어를 완전히 대체할 수 없습니다. 따라서 양쪽의 단점을 상쇄하고 장점을 취하기 위해, 자동화가 일차적인 방어선을 구축하고 인간이 고차원적인 검토를 수행하는 상호 보완적(Hybrid) 접근이 필수적입니다 [7, 20, 37-39]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/코드 리뷰 (Code Review).md]] +- Raw Source: 00_Raw/2026-04-20/코드 리뷰 (Code Review).md --- diff --git a/01_Archive/2026-04-20/코드 리뷰(Code Review).md b/01_Archive/2026-04-20/코드 리뷰(Code Review).md index 837ff3a0..89518a76 100644 --- a/01_Archive/2026-04-20/코드 리뷰(Code Review).md +++ b/01_Archive/2026-04-20/코드 리뷰(Code Review).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-119026 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 코드 리뷰(Code Review)" --- -# [[코드 리뷰(Code Review)]] +# [[코드 리뷰(Code Review)|코드 리뷰(Code Review)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 코드 리뷰는 소프트웨어의 품질, 보안 및 전반적인 코드 건강 상태를 개선하고 유지하기 위해 개발자들이 작성한 코드 변경 사항을 검사하는 프로세스입니다[1, 2]. 이 과정은 사람이 직접 코드를 읽고 분석하는 수동 리뷰와 정적 분석 도구 및 AI를 활용하는 자동화된 리뷰로 구성됩니다[3, 4]. 성공적인 코드 리뷰는 완벽한 코드만을 추구하기보다는 지속적인 개선과 개발 진행 속도 간의 적절한 균형을 맞추는 것을 목표로 합니다[5, 6]. @@ -30,11 +30,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 코드 리뷰(Code Review)" - **정책 변화:** AI 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[수동 코드 리뷰(Manual Code Review)]], [[자동화된 코드 리뷰(Automated Code Review)]], [[정적 애플리케이션 보안 테스트(SAST)]] -- **Projects/Contexts:** [[하이브리드 코드 리뷰 워크플로우]], [[Google의 코드 리뷰 표준]], [[DevSecOps 및 CI/CD 파이프라인]] +- **Related Topics:** [[수동 코드 리뷰 (Manual Code Review)|수동 코드 리뷰(Manual Code Review)]], 자동화된 코드 리뷰(Automated Code Review), [[정적 애플리케이션 보안 테스트(SAST)|정적 애플리케이션 보안 테스트(SAST)]] +- **Projects/Contexts:** 하이브리드 코드 리뷰 워크플로우, Google의 코드 리뷰 표준, DevSecOps 및 CI/CD 파이프라인 - **Contradictions/Notes:** 자동화된 코드 리뷰 도구는 스캔 속도가 빠르고 규칙을 일관되게 적용하지만 비즈니스 로직의 의도를 이해하지 못해 다수의 오탐(False Positive)을 발생시킬 수 있습니다[22]. 반면 수동 코드 리뷰는 문맥을 이해하고 복잡한 아키텍처를 검토하는 데 필수적이지만 시간이 오래 걸리고 인적 오류의 위험이 병존합니다[13]. 따라서 이 두 가지 리뷰 방식은 상호 배타적인 것이 아니라, 장단점을 상호 보완하는 하이브리드 방식(기계적 검증 후 인간의 논리적 판단)으로 결합하여 사용하는 것이 권장됩니다[4, 26]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/코드 리뷰(Code Review).md]] +- Raw Source: 00_Raw/2026-04-20/코드 리뷰(Code Review).md --- diff --git a/01_Archive/2026-04-20/코드 서식 지정과 축소가 코드 스타일로메트리(작성자 인식)에 미치는 영향을 평가하는 기계 학습 모델 분류 연구.md b/01_Archive/2026-04-20/코드 서식 지정과 축소가 코드 스타일로메트리(작성자 인식)에 미치는 영향을 평가하는 기계 학습 모델 분류 연구.md index 7fc0aa53..86e651c7 100644 --- a/01_Archive/2026-04-20/코드 서식 지정과 축소가 코드 스타일로메트리(작성자 인식)에 미치는 영향을 평가하는 기계 학습 모델 분류 연구.md +++ b/01_Archive/2026-04-20/코드 서식 지정과 축소가 코드 스타일로메트리(작성자 인식)에 미치는 영향을 평가하는 기계 학습 모델 분류 연구.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-952EE7 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 코드 서식 지정과 축소가 코드 스타일로메트리(작성자 인식)에 미치는 영향을 평가하는 기계 학습 모델 분류 연구" --- -# [[코드 서식 지정과 축소가 코드 스타일로메트리(작성자 인식)에 미치는 영향을 평가하는 기계 학습 모델 분류 연구]] +# [[코드 서식 지정과 축소가 코드 스타일로메트리(작성자 인식)에 미치는 영향을 평가하는 기계 학습 모델 분류 연구|코드 서식 지정과 축소가 코드 스타일로메트리(작성자 인식)에 미치는 영향을 평가하는 기계 학습 모델 분류 연구]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 이 연구는 소프트웨어 개발에서 흔히 쓰이는 코드 서식 지정(formatting)과 코드 축소(minification)가 코드 스타일로메트리(작성자 자동 인식) 시스템의 정확도에 어떠한 영향을 미치는지 정량적으로 평가한 논문입니다 [1], [2]. 연구진은 Python 코드를 구체적 구문 트리(CST)로 표현하고 code2vec 기반의 기계 학습 분류 모델을 사용하여 작성자 식별 실험을 수행했습니다 [1]. 실험 결과, 서식 지정과 축소 과정은 작성자 인식 정확도를 유의미하게 감소시켰으나, 여전히 작성자를 식별할 수 있는 수준의 정보는 남아있는 것으로 나타났습니다 [1], [3]. @@ -33,11 +33,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 코드 서식 지정과 축소 - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[코드 스타일로메트리]], [[작성자 인식(Authorship Attribution)]], [[구체적 구문 트리(CST)]], [[추상 구문 트리(AST)]], [[code2vec]], [[기계 학습 분류기(Machine Learning Classifier)]] -- **Projects/Contexts:** [[Google Code Jam 데이터셋]], [[Black (Python 코드 포매터)]], [[Python Minifier]] +- **Related Topics:** 코드 스타일로메트리, 작성자 인식(Authorship Attribution), 구체적 구문 트리(CST), [[추상 구문 트리(AST)|추상 구문 트리(AST)]], code2vec, 기계 학습 분류기(Machine Learning Classifier) +- **Projects/Contexts:** Google Code Jam 데이터셋, Black (Python 코드 포매터), Python Minifier - **Contradictions/Notes:** 소스에 따르면 서식 지정된 코드(52.68%)와 축소된 코드(50.00%)의 작성자 인식 정확도는 원본 AST 기반 모델의 정확도(51.00%)와 매우 유사한 수치를 보입니다. 이는 서식 지정과 축소라는 과정이 CST가 제공하는 구체적 구문 특징의 이점을 대부분 상쇄시키지만, AST로도 포착 가능한 더 깊은 수준의 추상적 구문 내재 스타일까지는 파괴하지 못한다는 점을 의미합니다 [15]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/코드 서식 지정과 축소가 코드 스타일로메트리(작성자 인식)에 미치는 영향을 평가하는 기계 학습 모델 분류 연구.md]] +- Raw Source: 00_Raw/2026-04-20/코드 서식 지정과 축소가 코드 스타일로메트리(작성자 인식)에 미치는 영향을 평가하는 기계 학습 모델 분류 연구.md --- diff --git a/01_Archive/2026-04-20/코드 스타일로메트리 (Code Stylometry).md b/01_Archive/2026-04-20/코드 스타일로메트리 (Code Stylometry).md index 354231e2..185970c1 100644 --- a/01_Archive/2026-04-20/코드 스타일로메트리 (Code Stylometry).md +++ b/01_Archive/2026-04-20/코드 스타일로메트리 (Code Stylometry).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-325355 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 코드 스타일로메트리 (Code Stylometry)" --- -# [[코드 스타일로메트리 (Code Stylometry)]] +# [[코드 스타일로메트리 (Code Stylometry)|코드 스타일로메트리 (Code Stylometry)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -24,11 +24,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 코드 스타일로메트리 ( - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[기계 학습 (Machine Learning)]], [[추상 구문 트리 (AST)]], [[구체적 구문 트리 (CST)]], [[코드 포맷팅 (Code Formatting)]], [[적대적 스타일로메트리 (Adversarial Stylometry)]] -- **Projects/Contexts:** [[Google Code Jam 데이터셋]], [[StyleCounsel 도구]], [[모리스 웜 (Morris Worm) 사건]] +- **Related Topics:** 기계 학습 (Machine Learning), [[추상 구문 트리(AST)|추상 구문 트리 (AST)]], 구체적 구문 트리 (CST), 코드 포맷팅 (Code Formatting), 적대적 스타일로메트리 (Adversarial Stylometry) +- **Projects/Contexts:** Google Code Jam 데이터셋, StyleCounsel 도구, 모리스 웜 (Morris Worm) 사건 - **Contradictions/Notes:** 소스 코드를 자동 포맷팅하거나 축소(Minification)하면 분석기의 저자 식별 정확도가 감소하여 프라이버시 보호 효과가 발생하지만, 그것만으로는 스타일적 특징을 완전히 지울 수 없어 저자를 익명으로 유지하는 데에는 불충분합니다 [23], [18]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/코드 스타일로메트리 (Code Stylometry).md]] +- Raw Source: 00_Raw/2026-04-20/코드 스타일로메트리 (Code Stylometry).md --- diff --git a/01_Archive/2026-04-20/코드 축소 (Code minification).md b/01_Archive/2026-04-20/코드 축소 (Code minification).md index 05c7cf72..2b9aa64a 100644 --- a/01_Archive/2026-04-20/코드 축소 (Code minification).md +++ b/01_Archive/2026-04-20/코드 축소 (Code minification).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-AE4852 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 코드 축소 (Code minification)" --- -# [[코드 축소 (Code minification)]] +# [[코드 축소 (Code minification)|코드 축소 (Code minification)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 코드 축소(Code minification)는 공백, 줄 바꿈, 주석 등 소스 코드에서 의미적으로 불필요한 요소를 제거하고 식별자 이름을 짧게 변경하여 파일의 크기를 최소화하는 최적화 기법입니다 [1, 2]. 이 과정은 코드의 실행 의미(semantics)를 훼손하지 않으면서도, 웹 브라우저의 다운로드 및 페이지 렌더링 속도를 크게 향상시키기 위해 소프트웨어 배포 시점에 자동화되어 수행됩니다 [2, 3]. 코드를 사람이 읽기 어렵게 만들고 프로그래머의 코딩 스타일 특징을 모호하게 만들지만, 작성자의 익명성을 완벽하게 보장하는 수단이 될 수는 없습니다 [3, 4]. @@ -23,11 +23,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 코드 축소 (Code minificati - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[코드 문체 분석 (Code stylometry)]], [[코드 포맷팅 (Code formatting)]], [[구체적 구문 트리 (CST)]], [[추상 구문 트리 (AST)]] -- **Projects/Contexts:** [[웹 개발 최적화]], [[Python Minifier]] +- **Related Topics:** 코드 문체 분석 (Code stylometry), 코드 포맷팅 (Code formatting), 구체적 구문 트리 (CST), [[추상 구문 트리(AST)|추상 구문 트리 (AST)]] +- **Projects/Contexts:** 웹 개발 최적화, Python Minifier - **Contradictions/Notes:** 일반적으로 코드 축소는 코드를 사람이 읽기 훨씬 더 어렵게 만들기 때문에 작성자 식별도 매우 어려울 것으로 예상되지만, 연구 결과 자동화된 코드 포맷팅을 적용한 상태와 비교했을 때 시스템의 작성자 식별 방해 효과(인식률 저하)는 매우 미미한 차이(2.68%)밖에 나지 않았습니다 [7]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/코드 축소 (Code minification).md]] +- Raw Source: 00_Raw/2026-04-20/코드 축소 (Code minification).md --- diff --git a/01_Archive/2026-04-20/코드 포매팅 (Code formatting).md b/01_Archive/2026-04-20/코드 포매팅 (Code formatting).md index 4effb11f..fdc4de1e 100644 --- a/01_Archive/2026-04-20/코드 포매팅 (Code formatting).md +++ b/01_Archive/2026-04-20/코드 포매팅 (Code formatting).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-C0F871 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 코드 포매팅 (Code formatting)" --- -# [[코드 포매팅 (Code formatting)]] +# [[코드 포매팅 (Code formatting)|코드 포매팅 (Code formatting)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 코드 포매팅(Code formatting)은 소스 코드를 정해진 코딩 스타일 가이드나 컨벤션에 맞게 일관된 형태로 변환하는 과정입니다 [1, 2]. 들여쓰기, 공백, 줄 바꿈, 괄호 위치 등의 시각적 요소를 조정하며 코드의 실행 의미(Semantics)나 기능은 변경하지 않습니다 [1, 3, 4]. 전용 도구를 통해 자동화되어 개발자의 생산성을 높이고, 코드의 가독성 향상 및 유지보수를 용이하게 만들어 협업 시 발생하는 혼란을 최소화하는 역할을 합니다 [5, 6]. @@ -29,11 +29,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 코드 포매팅 (Code formatt - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Prettier]], [[Linter (린터)]], [[정적 분석 (Static Analysis)]], [[코드 스타일로메트리 (Code Stylometry)]] -- **Projects/Contexts:** 팀 단위 개발 환경에서 [[Git Hook (Husky)]]과 [[lint-staged]]를 CI/CD 파이프라인에 연동하여 커밋 시점에 자동으로 포매팅이 적용되도록 강제하는 업무 맥락 [11-13]. +- **Related Topics:** [[Prettier|Prettier]], Linter (린터), [[정적 분석(Static Analysis)|정적 분석 (Static Analysis)]], [[코드 스타일로메트리 (Code Stylometry)|코드 스타일로메트리 (Code Stylometry)]] +- **Projects/Contexts:** 팀 단위 개발 환경에서 Git Hook (Husky)과 [[lint-staged|lint-staged]]를 CI/CD 파이프라인에 연동하여 커밋 시점에 자동으로 포매팅이 적용되도록 강제하는 업무 맥락 [11-13]. - **Contradictions/Notes:** Linter와 Formatter를 동시에 사용할 때 두 도구 모두 코드 스타일을 검사할 수 있어 규칙 충돌 현상이 발생할 수 있으므로, 코드 포매팅은 전적으로 Prettier 등의 포매터에 맡기고 Linter의 포매팅 기능은 끄도록 설정하는 것이 바람직합니다 [6, 14, 19]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/코드 포매팅 (Code formatting).md]] +- Raw Source: 00_Raw/2026-04-20/코드 포매팅 (Code formatting).md --- diff --git a/01_Archive/2026-04-20/코드 품질 관리 및 자동화 (Code Quality Management and Automation).md b/01_Archive/2026-04-20/코드 품질 관리 및 자동화 (Code Quality Management and Automation).md index a1920d4b..1207ce0e 100644 --- a/01_Archive/2026-04-20/코드 품질 관리 및 자동화 (Code Quality Management and Automation).md +++ b/01_Archive/2026-04-20/코드 품질 관리 및 자동화 (Code Quality Management and Automation).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-A84338 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 코드 품질 관리 및 자동화 (Code Quality Management and Automation)" --- -# [[코드 품질 관리 및 자동화 (Code Quality Management and Automation)]] +# [[코드 품질 관리 및 자동화 (Code Quality Management and Automation)|코드 품질 관리 및 자동화 (Code Quality Management and Automation)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 코드 품질 관리 및 자동화는 린터(Linter), 포매터(Formatter), SAST(정적 애플리케이션 보안 테스트) 등의 도구를 활용하여 소스 코드의 문법적 오류, 스타일 일관성, 보안 취약점을 식별하고 수정하는 프로세스이다 [1-3]. 이를 Husky, lint-staged와 같은 도구와 결합하여 CI/CD 파이프라인 또는 Git 훅에 통합함으로써 개발 초기 단계에서 결함을 예방하는 '시프트 레프트(Shift-Left)' 보안 및 품질 검증을 수행한다 [4-6]. 최근에는 이러한 자동화 검사와 인간의 문맥적 이해가 필요한 수동 리뷰를 결합한 하이브리드 접근법이 표준적인 개발 문화로 자리 잡고 있다 [7, 8]. @@ -23,11 +23,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 코드 품질 관리 및 자 - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[정적 애플리케이션 보안 테스트 (SAST)]], [[수동 코드 리뷰 (Manual Code Review)]], [[지속적 통합 및 지속적 배포 (CI/CD)]], [[린터와 포매터 (Linters and Formatters)]] +- **Related Topics:** [[정적 애플리케이션 보안 테스트 (SAST)|정적 애플리케이션 보안 테스트 (SAST)]], [[수동 코드 리뷰 (Manual Code Review)|수동 코드 리뷰 (Manual Code Review)]], 지속적 통합 및 지속적 배포 (CI/CD), 린터와 포매터 (Linters and Formatters) - **Projects/Contexts:** Git pre-commit 훅 환경에서 Husky와 lint-staged를 활용한 검증 파이프라인 자동화 구성, Turborepo 등 모노레포에서의 중앙 집중식 린트 환경 구축, Snyk 및 SonarQube를 통한 DevSecOps 도입 사례. - **Contradictions/Notes:** 자동화 도구는 빠르고 일관된 스캔을 보장하지만, 코드의 비즈니스 의도나 아키텍처적 맥락(Context Blindness)을 파악하지 못해 최대 30~60%의 높은 오탐률(False Positives)을 낼 수 있으며 실제 취약점의 약 22%가량을 놓칠 수 있으므로 아키텍처 및 고위험 영역에 대한 인간의 검토가 반드시 병행되어야 한다 [27, 41]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/코드 품질 관리 및 자동화 (Code Quality Management and Automation).md]] +- Raw Source: 00_Raw/2026-04-20/코드 품질 관리 및 자동화 (Code Quality Management and Automation).md --- diff --git a/01_Archive/2026-04-20/코스모스(Cosmos).md b/01_Archive/2026-04-20/코스모스(Cosmos).md index bb5fef99..4e16dbec 100644 --- a/01_Archive/2026-04-20/코스모스(Cosmos).md +++ b/01_Archive/2026-04-20/코스모스(Cosmos).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-2F7488 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 코스모스(Cosmos)" --- -# [[코스모스(Cosmos)]] +# [[코스모스(Cosmos)|코스모스(Cosmos)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -34,11 +34,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 코스모스(Cosmos)" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Microservices]], [[Serverless Computing]], [[Separation of Concerns]], [[Workflow]] -- **Projects/Contexts:** [[Netflix Media Cloud Engineering]], [[Reloaded (Netflix Legacy System)]], [[Tapas (Netflix Service)]] +- **Related Topics:** Microservices, [[서버리스 컴퓨팅(Serverless Computing)|Serverless Computing]], [[_뇌와 팔다리의 분리_ - 관심사의 분리 (Separation of Concerns)|Separation of Concerns]], Workflow +- **Projects/Contexts:** Netflix Media Cloud Engineering, Reloaded (Netflix Legacy System), Tapas (Netflix Service) - **Contradictions/Notes:** 넷플릭스는 기존의 거대하고 복잡한 레거시 시스템(Reloaded)에서 코스모스로 전환하는 데 따른 위험을 줄이기 위해, 새로운 시스템이 기존 시스템을 둘러싸면서 점진적으로 완전히 대체하는 스트랭글러 피그(strangler fig) 패턴을 채택했습니다 [13]. 한편 "마이크로서비스가 워크플로우를 트리거하고 서버리스 함수를 오케스트레이션한다"는 코스모스의 프로그래밍 모델은 대부분의 사용 사례에 효과적이지만, 너무 단순한 애플리케이션의 경우에는 오히려 추가되는 복잡성이 이점보다 클 수 있다고 지적됩니다 [14]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/코스모스(Cosmos).md]] +- Raw Source: 00_Raw/2026-04-20/코스모스(Cosmos).md --- diff --git a/01_Archive/2026-04-20/클로저(Closures).md b/01_Archive/2026-04-20/클로저(Closures).md index d930e2ba..8247f52d 100644 --- a/01_Archive/2026-04-20/클로저(Closures).md +++ b/01_Archive/2026-04-20/클로저(Closures).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-7F81A9 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 클로저(Closures)" --- -# [[클로저(Closures)]] +# [[클로저(Closures)|클로저(Closures)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 클로저(Closures)는 중첩된 함수가 접근할 수 있는 로컬 변수를 포함하는 자바스크립트 스코프를 의미합니다 [1]. 클로저는 가비지 컬렉션(GC)의 루트(Root) 역할을 수행하므로, 활성화된 클로저가 참조하는 객체나 변수는 메모리에서 해제되지 않고 유지됩니다 [2, 3]. 다수의 클로저가 스코프를 공유하거나 비동기 처리 과정에서 불필요하게 큰 객체를 캡처할 경우 심각한 메모리 누수를 발생시키는 주요 원인이 됩니다 [4, 5]. @@ -23,11 +23,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 클로저(Closures)" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Garbage Collection]], [[Memory Leaks]], [[GC Roots]], [[system / Context]] -- **Projects/Contexts:** [[Heap Snapshots]]를 활용한 메모리 프로파일링 및 브라우저/Node.js 환경의 누수 디버깅 +- **Related Topics:** [[Garbage Collection|Garbage Collection]], [[Memory Leaks|Memory Leaks]], GC Roots, system / Context +- **Projects/Contexts:** [[힙 스냅샷 (Heap Snapshots)|Heap Snapshots]]를 활용한 메모리 프로파일링 및 브라우저/Node.js 환경의 누수 디버깅 - **Contradictions/Notes:** 소스에 관련 정보가 부족합니다. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/클로저(Closures).md]] +- Raw Source: 00_Raw/2026-04-20/클로저(Closures).md --- diff --git a/01_Archive/2026-04-20/클린 아키텍처 (Clean Architecture).md b/01_Archive/2026-04-20/클린 아키텍처 (Clean Architecture).md index e95b966e..5121678a 100644 --- a/01_Archive/2026-04-20/클린 아키텍처 (Clean Architecture).md +++ b/01_Archive/2026-04-20/클린 아키텍처 (Clean Architecture).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-0A3765 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 클린 아키텍처 (Clean Architecture)" --- -# [[클린 아키텍처 (Clean Architecture)]] +# [[클린 아키텍처 (Clean Architecture)|클린 아키텍처 (Clean Architecture)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 클린 아키텍처는 로버트 C. 마틴(Uncle Bob)이 창안한 소프트웨어 설계 철학으로, 시스템을 '관심사의 분리(Separation of Concerns)' 원칙에 따라 명확한 계층으로 나누는 아키텍처 구조입니다 [1-3]. 이 아키텍처는 시스템의 핵심인 비즈니스 로직을 프레임워크, UI, 데이터베이스와 같은 외부 기술 요소로부터 완벽히 분리시켜 유지보수성, 확장성, 그리고 테스트 용이성을 극대화하는 것을 목표로 합니다 [1, 4, 5]. 핵심 원리는 소스 코드의 의존성이 오직 내부의 고수준 정책(비즈니스 로직)을 향하도록 통제하는 '의존성 규칙(Dependency Rule)'을 엄격히 준수하는 것입니다 [1, 6, 7]. @@ -37,11 +37,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 클린 아키텍처 (Clean Arc - **정책 변화:** Design & Experience 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[관심사의 분리 (Separation of Concerns)]], [[의존성 역전 원칙 (Dependency Inversion Principle)]], [[단일 책임 원칙 (Single Responsibility Principle)]] -- **Projects/Contexts:** [[웹 애플리케이션의 3계층 구조]], [[도메인 주도 설계 (DDD)]], [[넷플릭스의 코스모스 플랫폼 및 마이크로서비스 전환]] +- **Related Topics:** [[관심사의 분리 (Separation of Concerns)|관심사의 분리 (Separation of Concerns)]], [[의존성 역전 원칙 (Dependency Inversion Principle)|의존성 역전 원칙 (Dependency Inversion Principle)]], [[단일 책임 원칙 (Single Responsibility Principle)|단일 책임 원칙 (Single Responsibility Principle)]] +- **Projects/Contexts:** [[웹 애플리케이션의 3계층 구조|웹 애플리케이션의 3계층 구조]], [[도메인 주도 설계 (DDD)|도메인 주도 설계 (DDD)]], [[넷플릭스의 코스모스 플랫폼 및 마이크로서비스 전환|넷플릭스의 코스모스 플랫폼 및 마이크로서비스 전환]] - **Contradictions/Notes:** 소스에 따르면 클린 아키텍처는 유지보수성과 확장성을 비약적으로 높여주지만, 초기 개발 시간이 증가하고 계층과 추상화가 너무 많아질 경우 시스템 구조가 지나치게 복잡해지는 오버엔지니어링(Over-Engineering) 및 간접 참조에 의한 가독성 저하를 유발할 수 있습니다 [16, 17]. 따라서 과도한 추상화를 경계하고, 실용적 필요에 맞게 응집도와 결합도를 고려하여 아키텍처의 균형을 맞추는 것이 중요합니다 [16, 18]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/클린 아키텍처 (Clean Architecture).md]] +- Raw Source: 00_Raw/2026-04-20/클린 아키텍처 (Clean Architecture).md --- diff --git a/01_Archive/2026-04-20/클린 아키텍처(Clean Architecture).md b/01_Archive/2026-04-20/클린 아키텍처(Clean Architecture).md index 8cee9904..f89c82c2 100644 --- a/01_Archive/2026-04-20/클린 아키텍처(Clean Architecture).md +++ b/01_Archive/2026-04-20/클린 아키텍처(Clean Architecture).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-2298F3 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 클린 아키텍처(Clean Architecture)" --- -# [[클린 아키텍처(Clean Architecture)]] +# [[클린 아키텍처(Clean Architecture)|클린 아키텍처(Clean Architecture)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > **클린 아키텍처(Clean Architecture)**는 로버트 C. 마틴(Robert C. Martin, "Uncle Bob")이 대중화한 소프트웨어 설계 철학으로, 비즈니스 로직과 애플리케이션 규칙을 시스템의 중심에 두어 코드의 품질을 높이는 것을 목표로 합니다 [1], [2]. 이 접근 방식은 시스템을 각기 다른 책임을 지는 여러 동심원 계층으로 분리하여 **관심사의 분리(Separation of Concerns)**를 촉진합니다 [1], [3]. 핵심 원칙인 **'의존성 규칙(Dependency Rule)'**을 강제하여 소스 코드 의존성이 오직 내부로만 향하게 함으로써 프레임워크, UI, 데이터베이스 등의 외부 요소로부터 독립적이고, 유지보수성, 확장성 및 테스트 용이성이 뛰어난 시스템을 구축할 수 있습니다 [1], [4], [5], [6]. @@ -38,11 +38,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 클린 아키텍처(Clean Arch - **정책 변화:** Design & Experience 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[관심사의 분리(Separation of Concerns)]], [[의존성 역전 원칙(Dependency Inversion Principle)]], [[SOLID 원칙(SOLID Principles)]] -- **Projects/Contexts:** [[안드로이드 애플리케이션(Android Applications)]], [[iOS 애플리케이션의 VIPER 패턴(VIPER Architecture)]], [[ASP.NET Core 애플리케이션]], [[넷플릭스 마이크로서비스(Netflix Microservices)]] +- **Related Topics:** [[관심사의 분리(Separation of Concerns)|관심사의 분리(Separation of Concerns)]], [[의존성 역전 원칙 (Dependency Inversion Principle)|의존성 역전 원칙(Dependency Inversion Principle)]], [[SOLID 원칙 (SOLID Principles)|SOLID 원칙(SOLID Principles)]] +- **Projects/Contexts:** 안드로이드 애플리케이션(Android Applications), iOS 애플리케이션의 VIPER 패턴(VIPER Architecture), ASP.NET Core 애플리케이션, 넷플릭스 마이크로서비스(Netflix Microservices) - **Contradictions/Notes:** 소스 출처 "Complete Guide to Clean Architecture - GeeksforGeeks"는 클린 아키텍처가 시스템의 장기적인 유지보수성, 테스트 가능성, 유연성을 제공한다고 강조하지만, 동시에 도입 초기에는 여러 추상화 계층을 구축해야 하므로 초기 개발 시간이 증가하고 오버엔지니어링(Over-Engineering)에 빠질 위험이 있다고 지적합니다. 따라서 실용적인 관점과의 균형 유지가 필수적입니다 [21], [19]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/클린 아키텍처(Clean Architecture).md]] +- Raw Source: 00_Raw/2026-04-20/클린 아키텍처(Clean Architecture).md --- diff --git a/01_Archive/2026-04-20/클린 아키텍처.md b/01_Archive/2026-04-20/클린 아키텍처.md index 9d4a9fab..96b37b8e 100644 --- a/01_Archive/2026-04-20/클린 아키텍처.md +++ b/01_Archive/2026-04-20/클린 아키텍처.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-417677 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 클린 아키텍처" --- -# [[클린 아키텍처]] +# [[클린 아키텍처|클린 아키텍처]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 클린 아키텍처(Clean Architecture)는 로버트 C. 마틴(Robert C. Martin)이 제안한 소프트웨어 설계 철학으로, 비즈니스 로직과 애플리케이션 규칙을 시스템의 중심에 배치하는 구조를 갖습니다 [1, 2]. 소프트웨어를 여러 동심원 계층으로 분리하여 관심사를 철저히 분리하며, 프레임워크, 사용자 인터페이스(UI), 데이터베이스 등 외부 요소로부터 시스템을 완전히 독립시키는 것을 목표로 합니다 [1, 3-5]. 이 아키텍처의 핵심은 소스 코드의 의존성이 오직 내부의 고수준 정책만을 향해야 한다는 '의존성 규칙(Dependency Rule)'입니다 [1, 5, 6]. 이를 통해 시스템은 프레임워크나 외부 에이전시의 변경에 영향을 받지 않으며, 유지보수성, 확장성, 그리고 테스트 용이성을 극대화할 수 있습니다 [5, 7, 8]. @@ -37,11 +37,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 클린 아키텍처" - **정책 변화:** Design & Experience 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[관심사의 분리]], [[의존성 규칙]], [[의존성 역전 원칙]], [[SOLID 원칙]] -- **Projects/Contexts:** [[Netflix 마이크로서비스]], [[Android 애플리케이션 아키텍처]], [[VIPER 아키텍처]] +- **Related Topics:** 관심사의 분리, 의존성 규칙, 의존성 역전 원칙, [[SOLID 원칙|SOLID 원칙]] +- **Projects/Contexts:** Netflix 마이크로서비스, Android 애플리케이션 아키텍처, VIPER 아키텍처 - **Contradictions/Notes:** 클린 아키텍처는 시스템의 유지보수성과 유연성을 극대화하지만, 동시에 여러 계층과 추상화의 추가로 인해 초기 개발 시간이 늘어나고 구조가 복잡해지는 '오버 엔지니어링'의 위험을 동반하므로 실용성과의 적절한 균형이 필요하다는 점을 주의해야 합니다 [18]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/클린 아키텍처.md]] +- Raw Source: 00_Raw/2026-04-20/클린 아키텍처.md --- diff --git a/01_Archive/2026-04-20/타임라인 할당 계측(Allocation instrumentation on timeline).md b/01_Archive/2026-04-20/타임라인 할당 계측(Allocation instrumentation on timeline).md index 02c74036..d12ccc45 100644 --- a/01_Archive/2026-04-20/타임라인 할당 계측(Allocation instrumentation on timeline).md +++ b/01_Archive/2026-04-20/타임라인 할당 계측(Allocation instrumentation on timeline).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-733CA6 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 타임라인 할당 계측(Allocation instrumentation on timeline)" --- -# [[타임라인 할당 계측(Allocation instrumentation on timeline)]] +# [[타임라인 할당 계측(Allocation instrumentation on timeline)|타임라인 할당 계측(Allocation instrumentation on timeline)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 타임라인 할당 계측(Allocation instrumentation on timeline)은 Chrome 및 Microsoft Edge DevTools의 메모리(Memory) 패널에서 제공하는 성능 프로파일링 도구로, 특정 기간 동안 발생하는 모든 메모리 할당을 스택 트레이스와 함께 기록합니다 [1-3]. 힙 프로파일러의 상세한 스냅샷 정보와 타임라인 패널의 점진적 업데이트 및 추적 기능을 결합한 것이 특징입니다 [2, 3]. 이 도구는 정상적으로 가비지 컬렉션(GC)되지 않고 메모리에 남아 메모리 누수를 일으키는 객체와 해당 객체의 생성 위치를 시각적으로 추적하고 식별하는 데 주로 사용됩니다 [1, 2, 4, 5]. @@ -25,11 +25,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 타임라인 할당 계측(All - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[메모리 누수(Memory leak)]], [[가비지 컬렉션(Garbage Collection)]], [[힙 스냅샷(Heap snapshot)]], [[스택 트레이스(Stack trace)]] -- **Projects/Contexts:** [[Chrome DevTools]], [[Microsoft Edge DevTools]], [[Node.js 성능 디버깅]] +- **Related Topics:** [[메모리 누수(Memory Leak)|메모리 누수(Memory leak)]], [[가비지 컬렉션(Garbage Collection)|가비지 컬렉션(Garbage Collection)]], [[힙 스냅샷(Heap Snapshot)|힙 스냅샷(Heap snapshot)]], [[스택 트레이스(Stack trace)|스택 트레이스(Stack trace)]] +- **Projects/Contexts:** [[Chrome DevTools|Chrome DevTools]], [[Microsoft Edge DevTools|Microsoft Edge DevTools]], [[Node.js 성능 디버깅|Node.js 성능 디버깅]] - **Contradictions/Notes:** 소스에 관련 정보가 부족합니다. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/타임라인 할당 계측(Allocation instrumentation on timeline).md]] +- Raw Source: 00_Raw/2026-04-20/타임라인 할당 계측(Allocation instrumentation on timeline).md --- diff --git a/01_Archive/2026-04-20/타입 가드 (Type Guards).md b/01_Archive/2026-04-20/타입 가드 (Type Guards).md index bde41260..2a2085e1 100644 --- a/01_Archive/2026-04-20/타입 가드 (Type Guards).md +++ b/01_Archive/2026-04-20/타입 가드 (Type Guards).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-5D0418 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 타입 가드 (Type Guards)" --- -# [[타입 가드 (Type Guards)]] +# [[타입 가드 (Type Guards)|타입 가드 (Type Guards)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 타입 가드(Type Guards)는 TypeScript에서 `unknown` 변수나 유니온(Union) 타입 변수의 실제 타입을 안전하게 판별하고 확신할 수 있게 해주는 기법입니다 [1, 2]. 이를 통해 TypeScript의 제어 흐름 분석(Control Flow Analysis)이 실행되어, 특정 조건문 블록 내에서 변수의 가능한 타입을 좁혀(Narrowing) 안전하게 속성에 접근할 수 있도록 돕습니다 [2, 3]. @@ -31,11 +31,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 타입 가드 (Type Guards)" - **정책 변화:** Design & Experience 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Type Narrowing]], [[Union Types]], [[Type Predicates]], [[unknown type]] -- **Projects/Contexts:** [[외부 API의 불확실한(unknown) 데이터 검증 로직]], [[복잡한 유니온 타입 분기 처리]] +- **Related Topics:** [[Type Narrowing|Type Narrowing]], [[Union Types|Union Types]], [[Type Predicates|Type Predicates]], unknown type +- **Projects/Contexts:** 외부 API의 불확실한(unknown) 데이터 검증 로직, 복잡한 유니온 타입 분기 처리 - **Contradictions/Notes:** 사용자 정의 타입 가드는 타입 좁히기에 매우 유용하지만, TypeScript가 내부 판별 로직의 논리적 오류를 잡아주지 못하기 때문에 개발자의 부주의로 인해 타입 안정성이 훼손될 위험이 존재합니다 [5]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/타입 가드 (Type Guards).md]] +- Raw Source: 00_Raw/2026-04-20/타입 가드 (Type Guards).md --- diff --git a/01_Archive/2026-04-20/타입 가드 (Type Predicates).md b/01_Archive/2026-04-20/타입 가드 (Type Predicates).md index 56fa09ff..aec6b951 100644 --- a/01_Archive/2026-04-20/타입 가드 (Type Predicates).md +++ b/01_Archive/2026-04-20/타입 가드 (Type Predicates).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-328E4F -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 타입 가드 (Type Predicates)" --- -# [[타입 가드 (Type Predicates)]] +# [[타입 가드 (Type Predicates)|타입 가드 (Type Predicates)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 타입 가드(Type Predicates)는 런타임에 반환되는 불리언(boolean) 값을 기반으로 TypeScript의 타입 시스템이 매개변수의 타입을 더 구체적으로 좁힐 수(Narrowing) 있도록 돕는 함수입니다 [1]. 주로 유니언 타입이나 알 수 없는 데이터를 다룰 때 변수가 특정 타입 구조를 만족하는지 검증하기 위해 사용됩니다 [2, 3]. 다만 TypeScript 컴파일러는 타입 가드 내부의 검증 로직이 정확한지까지는 확인하지 않으므로, 개발자 스스로 로직의 정확성을 보장해야 합니다 [1]. @@ -23,11 +23,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 타입 가드 (Type Predicates - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Type Narrowing]], [[Branded Types]], [[Union Types]] -- **Projects/Contexts:** [[알 수 없는 외부 데이터 검증 (unknown types)]], [[유니언 타입 식별 및 상태 분기 처리]] +- **Related Topics:** [[Type Narrowing|Type Narrowing]], [[Branded Types|Branded Types]], [[Union Types|Union Types]] +- **Projects/Contexts:** [[알 수 없는 외부 데이터 검증 (unknown types)|알 수 없는 외부 데이터 검증 (unknown types)]], [[유니언 타입 식별 및 상태 분기 처리|유니언 타입 식별 및 상태 분기 처리]] - **Contradictions/Notes:** 브랜디드 타입 등의 값을 강제할 때 타입 가드가 `as` 단언에 비해 "종종 더 안전한 방법"으로 소개되기도 하나 [5], 정작 컴파일러가 타입 가드의 내부 구현 로직을 검증해 주지 않기 때문에 본질적으로는 `as` 단언보다 훨씬 더 타입에 안전하다고 볼 수는 없다는 주의 사항이 함께 언급됩니다 [1]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/타입 가드 (Type Predicates).md]] +- Raw Source: 00_Raw/2026-04-20/타입 가드 (Type Predicates).md --- diff --git a/01_Archive/2026-04-20/타입 가드(Type Guards).md b/01_Archive/2026-04-20/타입 가드(Type Guards).md index 66561613..cad3cb64 100644 --- a/01_Archive/2026-04-20/타입 가드(Type Guards).md +++ b/01_Archive/2026-04-20/타입 가드(Type Guards).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-05AFCC -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 타입 가드(Type Guards)" --- -# [[타입 가드(Type Guards)]] +# [[타입 가드(Type Guards)|타입 가드(Type Guards)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 타입 가드(Type Guards)는 TypeScript에서 유니언(Union) 타입이나 `unknown` 타입의 변수를 다룰 때 특정 타입을 구별해 내기 위해 사용되는 메커니즘입니다 [1, 2]. 런타임에 실행되는 검사를 바탕으로 TypeScript의 타입 시스템이 자동으로 타입을 좁히도록(Narrowing) 유도합니다 [1, 3]. 이를 통해 개발자는 알 수 없는 변수를 분석할 때 해당 변수의 타입을 확신을 가지고 안전하게 식별할 수 있습니다 [4]. @@ -23,11 +23,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 타입 가드(Type Guards)" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Type Narrowing]], [[Type Predicates]], [[Unknown Type]], [[Discriminated Unions]] -- **Projects/Contexts:** [[API 응답 등 외부의 불확실한 데이터 구조 검증 및 처리]] +- **Related Topics:** [[Type Narrowing|Type Narrowing]], [[Type Predicates|Type Predicates]], Unknown Type, [[Discriminated Unions|Discriminated Unions]] +- **Projects/Contexts:** API 응답 등 외부의 불확실한 데이터 구조 검증 및 처리 - **Contradictions/Notes:** 타입 서술어(Type predicates) 형태의 커스텀 타입 가드는 타입 단언(as assertions)보다 훨씬 타입에 안전한 편은 아니며, TypeScript는 타입 가드 내부의 논리가 해당 브랜드 타입의 의도와 완벽히 일치하는지까지 검증하지 않으므로 전적으로 코드 작성자에게 책임이 위임됩니다 [3]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/타입 가드(Type Guards).md]] +- Raw Source: 00_Raw/2026-04-20/타입 가드(Type Guards).md --- diff --git a/01_Archive/2026-04-20/타입 단언 (Type Assertions).md b/01_Archive/2026-04-20/타입 단언 (Type Assertions).md index af126cbf..03d19182 100644 --- a/01_Archive/2026-04-20/타입 단언 (Type Assertions).md +++ b/01_Archive/2026-04-20/타입 단언 (Type Assertions).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-FE3FC7 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 타입 단언 (Type Assertions)" --- -# [[타입 단언 (Type Assertions)]] +# [[타입 단언 (Type Assertions)|타입 단언 (Type Assertions)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 타입 단언(Type Assertions)은 개발자가 TypeScript 컴파일러보다 특정 값의 타입 정보를 더 잘 알고 있을 때, 컴파일러에게 해당 값을 특정 타입으로 간주하도록 지시하는 기능이다 [1, 2]. 런타임에는 데이터에 어떠한 영향도 주지 않고 오직 컴파일 과정에서만 작용하며 주로 `as` 키워드가 사용된다 [2]. 그러나 컴파일러의 타입 검증을 우회하므로 잘못 사용될 경우 런타임 오류의 원인이 될 수 있어 주의가 필요하다 [3, 4]. @@ -30,11 +30,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 타입 단언 (Type Assertions - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[satisfies 연산자]], [[브랜디드 타입 (Branded Types)]], [[타입 캐스팅 (Type Casting)]], [[초과 속성 검사 (Excess Property Checks)]] -- **Projects/Contexts:** [[DOM 요소 조작]], [[서드파티 라이브러리 및 API 연동]] +- **Related Topics:** [[satisfies 연산자|satisfies 연산자]], [[브랜디드 타입 (Branded Types)|브랜디드 타입 (Branded Types)]], [[타입 캐스팅 (Type Casting)|타입 캐스팅 (Type Casting)]], [[초과 속성 검사 (Excess Property Checks)|초과 속성 검사 (Excess Property Checks)]] +- **Projects/Contexts:** [[DOM 요소 조작|DOM 요소 조작]], [[서드파티 라이브러리 및 API 연동|서드파티 라이브러리 및 API 연동]] - **Contradictions/Notes:** 타입 단언(`as`)은 코딩 시 편리함을 제공하지만, 컴파일러의 엄격한 타입 유효성 및 초과 속성 검사를 우회해버리는 치명적인 단점이 있다. 따라서 최근 TypeScript 생태계에서는 이 단점을 극복하고 구체적인 추론과 검사를 동시에 수행하는 `satisfies` 연산자가 더 나은 대안으로 평가된다 [9, 13]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/타입 단언 (Type Assertions).md]] +- Raw Source: 00_Raw/2026-04-20/타입 단언 (Type Assertions).md --- diff --git a/01_Archive/2026-04-20/타입 단언(Type Assertion).md b/01_Archive/2026-04-20/타입 단언(Type Assertion).md index c233d253..1df0d3f9 100644 --- a/01_Archive/2026-04-20/타입 단언(Type Assertion).md +++ b/01_Archive/2026-04-20/타입 단언(Type Assertion).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-742CFD -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 타입 단언(Type Assertion)" --- -# [[타입 단언(Type Assertion)]] +# [[타입 단언(Type Assertion)|타입 단언(Type Assertion)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 타입 단언(Type Assertion)은 개발자가 TypeScript 컴파일러보다 값의 타입에 대해 더 잘 알고 있을 때, 컴파일러에게 특정 값의 타입을 명시적으로 지정하여 이를 신뢰하도록 지시하는 기능입니다 [1, 2]. 런타임 동작이나 데이터 구조를 실제로 변경하지 않으며, 오직 컴파일 타임의 타입 검사에만 사용됩니다 [2]. 그러나 컴파일러의 안전성 검사를 우회하게 만들어 런타임 에러를 유발할 수 있으므로, 사용에 각별한 주의가 요구됩니다 [1, 3]. @@ -27,11 +27,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 타입 단언(Type Assertion)" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Branded Types]], [[satisfies 연산자]], [[타입 선언(Type Declaration)]], [[잉여 속성 검사(Excess Property Checking)]], [[타입 가드(Type Predicates)]] -- **Projects/Contexts:** [[외부 데이터 처리 및 DOM 조작]], [[타입 안전성이 요구되는 대규모 애플리케이션]] +- **Related Topics:** [[Branded Types|Branded Types]], [[satisfies 연산자|satisfies 연산자]], 타입 선언(Type Declaration), 잉여 속성 검사(Excess Property Checking), [[타입 가드 (Type Predicates)|타입 가드(Type Predicates)]] +- **Projects/Contexts:** 외부 데이터 처리 및 DOM 조작, 타입 안전성이 요구되는 대규모 애플리케이션 - **Contradictions/Notes:** 소스에서는 `as`를 이용한 타입 단언이 코드를 빠르게 작성하고 컴파일 에러를 넘길 수 있는 편리한 기능임을 인정하면서도, 타입스크립트의 강력한 타입 검증 혜택을 무력화하여 버그를 숨길 수 있으므로(타입 캐스팅에만 의존하지 말 것) 사용을 최소한으로 제한해야 한다고 강력히 경고하고 있습니다 [1, 3, 6, 8]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/타입 단언(Type Assertion).md]] +- Raw Source: 00_Raw/2026-04-20/타입 단언(Type Assertion).md --- diff --git a/01_Archive/2026-04-20/타입 단언(Type Assertions).md b/01_Archive/2026-04-20/타입 단언(Type Assertions).md index 6a8440c6..59457c4d 100644 --- a/01_Archive/2026-04-20/타입 단언(Type Assertions).md +++ b/01_Archive/2026-04-20/타입 단언(Type Assertions).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-113099 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 타입 단언(Type Assertions)" --- -# [[타입 단언(Type Assertions)]] +# [[타입 단언(Type Assertions)|타입 단언(Type Assertions)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 타입 단언(Type Assertions)은 개발자가 TypeScript 컴파일러에게 특정 값의 타입을 자신이 더 확실히 파악하고 있음을 명시적으로 알려주는 기능입니다. 런타임 단계에서 데이터를 검사하거나 재구성하지 않고 순수하게 컴파일러 수준의 타입 검사에만 영향을 미칩니다. 주로 `as` 키워드를 사용하여 유용하게 쓰일 수 있으나, 컴파일러의 안전성 검사를 우회하게 되므로 잘못 사용하면 조용한 런타임 에러를 유발할 수 있어 주의가 필요합니다. @@ -23,11 +23,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 타입 단언(Type Assertions) - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Type Casting]], [[Satisfies Operator]], [[Branded Types]], [[Non-null Assertion Operator]], [[Type Declaration]] -- **Projects/Contexts:** [[DOM 요소 조작 및 타입 좁히기]], [[외부 API 데이터의 런타임 검증 후 처리]], [[타입 정의가 부족한 서드파티 라이브러리 연동]] +- **Related Topics:** [[Type Casting|Type Casting]], [[Satisfies Operator|Satisfies Operator]], [[Branded Types|Branded Types]], [[Non-null Assertion Operator|Non-null Assertion Operator]], [[Type Declaration|Type Declaration]] +- **Projects/Contexts:** [[DOM 요소 조작 및 타입 좁히기|DOM 요소 조작 및 타입 좁히기]], [[외부 API 데이터의 런타임 검증 후 처리|외부 API 데이터의 런타임 검증 후 처리]], [[타입 정의가 부족한 서드파티 라이브러리 연동|타입 정의가 부족한 서드파티 라이브러리 연동]] - **Contradictions/Notes:** 개발자는 타입 단언을 통해 손쉽게 컴파일 에러를 통과할 수 있지만, 이는 잉여 속성 검사 등을 무력화하여 시스템의 타입 안전성을 크게 훼손할 수 있습니다. 따라서 대부분의 상황에서는 타입 단언을 지양하고 '타입 선언'이나 `satisfies`를 통해 안전한 구조적 타이핑을 유지하는 것이 강하게 권장됩니다 [1, 5-7, 14]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/타입 단언(Type Assertions).md]] +- Raw Source: 00_Raw/2026-04-20/타입 단언(Type Assertions).md --- diff --git a/01_Archive/2026-04-20/타입 별칭 (Type Alias).md b/01_Archive/2026-04-20/타입 별칭 (Type Alias).md index d7fdcd1f..295742f0 100644 --- a/01_Archive/2026-04-20/타입 별칭 (Type Alias).md +++ b/01_Archive/2026-04-20/타입 별칭 (Type Alias).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-37A8A8 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 타입 별칭 (Type Alias)" --- -# [[타입 별칭 (Type Alias)]] +# [[타입 별칭 (Type Alias)|타입 별칭 (Type Alias)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 타입 별칭(Type Alias)은 TypeScript에서 기존 타입에 새로운 이름을 부여하여 재사용성을 높이는 기능입니다 [1]. 인터페이스(Interface)와 유사하게 객체의 형태를 정의하는 데 사용할 수 있으며, 그 외에도 원시 타입(Primitives), 유니온(Union), 튜플(Tuple) 및 기타 복잡한 타입 조합을 명명할 수 있는 폭넓은 표현력을 갖습니다 [1]. 인터페이스와 달리 선언 병합(Declaration Merging)을 허용하지 않아, 동일한 이름으로 재선언 시 에러를 발생시킴으로써 더 엄격한 타입 관리를 가능하게 합니다 [2, 3]. @@ -32,11 +32,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 타입 별칭 (Type Alias)" - **정책 변화:** Design & Experience 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[인터페이스 (Interface)]], [[유니온 타입 (Union Types)]], [[구조적 타이핑 (Structural Typing)]], [[선언 병합 (Declaration Merging)]] -- **Projects/Contexts:** [[대규모 TypeScript 프로젝트의 컴파일 성능 최적화]], [[견고한 도메인 모델 및 API 계약 설계]] +- **Related Topics:** [[인터페이스 (Interface)|인터페이스 (Interface)]], [[유니온 타입 (Union Types)|유니온 타입 (Union Types)]], [[구조적 타이핑 (Structural Typing)|구조적 타이핑 (Structural Typing)]], [[선언 병합 (Declaration Merging)|선언 병합 (Declaration Merging)]] +- **Projects/Contexts:** [[대규모 TypeScript 프로젝트의 컴파일 성능 최적화|대규모 TypeScript 프로젝트의 컴파일 성능 최적화]], [[견고한 도메인 모델 및 API 계약 설계|견고한 도메인 모델 및 API 계약 설계]] - **Contradictions/Notes:** TypeScript 핸드북 및 성능 가이드라인은 컴파일러의 캐싱 이점과 성능 최적화를 이유로 객체 확장 시 교집합을 사용하는 타입 별칭보다 인터페이스 상속(extends)을 사용할 것을 권장합니다 [8-10]. 하지만 실무 현장에서는 의도치 않은 선언 병합을 방지하고 유연성을 얻고자 린팅(Linting) 규칙을 통해 인터페이스 사용을 아예 금지하고 타입 별칭(Type Alias)만을 전면적으로 사용하는 개발 팀들도 많아 명확한 대립이 존재합니다 [4, 6, 15]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/타입 별칭 (Type Alias).md]] +- Raw Source: 00_Raw/2026-04-20/타입 별칭 (Type Alias).md --- diff --git a/01_Archive/2026-04-20/타입 서술어 (Type Predicates).md b/01_Archive/2026-04-20/타입 서술어 (Type Predicates).md index 7e891ffd..63a00411 100644 --- a/01_Archive/2026-04-20/타입 서술어 (Type Predicates).md +++ b/01_Archive/2026-04-20/타입 서술어 (Type Predicates).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-E4DAF5 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 타입 서술어 (Type Predicates)" --- -# [[타입 서술어 (Type Predicates)]] +# [[타입 서술어 (Type Predicates)|타입 서술어 (Type Predicates)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 타입 서술어(Type Predicates)는 매개변수가 특정 타입에 해당하는지 여부를 반환 타입을 통해 명시하는 커스텀 타입 가드 함수입니다 [1]. 런타임에는 불리언(boolean) 값을 반환하지만, 타입스크립트 컴파일러는 이 반환 값을 바탕으로 타입 좁히기(Type Narrowing)를 적용합니다 [1]. 주로 반환 타입에 `is` 키워드를 사용하여 정의되며, 런타임 검증 로직과 타입 시스템을 연결하여 변수의 타입을 안전하게 특정하는 데 유용합니다 [1-3]. @@ -30,11 +30,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 타입 서술어 (Type Predica - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Type Guards (타입 가드)]], [[Type Narrowing (타입 좁히기)]], [[Branded Types (브랜디드 타입)]], [[Type Assertion Functions (타입 단언 함수)]] +- **Related Topics:** Type Guards (타입 가드), Type Narrowing (타입 좁히기), Branded Types (브랜디드 타입), Type Assertion Functions (타입 단언 함수) - **Projects/Contexts:** 복잡한 유니온 타입 사이에서 특정 타입을 구별해 내거나, 숫자 및 문자열 같은 원시 타입에 제약을 부여한 브랜디드 타입의 런타임 값 유효성을 검증하고 타입스크립트 시스템에 이를 인지시킬 때 활용됩니다 [1-3]. - **Contradictions/Notes:** 타입 서술어는 컴파일러가 알아서 타입을 안전하게 보장해 줄 것이라는 착각을 일으키기 쉽지만, 실제로는 함수 내부의 구현 로직을 타입스크립트가 검증하지 않으므로 개발자의 실수(잘못된 논리 작성)에 취약하다는 점을 주의해야 합니다 [1]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/타입 서술어 (Type Predicates).md]] +- Raw Source: 00_Raw/2026-04-20/타입 서술어 (Type Predicates).md --- diff --git a/01_Archive/2026-04-20/타입 서술어(Type Predicates).md b/01_Archive/2026-04-20/타입 서술어(Type Predicates).md index d6686fe0..7c972cee 100644 --- a/01_Archive/2026-04-20/타입 서술어(Type Predicates).md +++ b/01_Archive/2026-04-20/타입 서술어(Type Predicates).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-4A5E0E -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 타입 서술어(Type Predicates)" --- -# [[타입 서술어(Type Predicates)]] +# [[타입 서술어(Type Predicates)|타입 서술어(Type Predicates)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 타입 서술어(Type Predicates)는 함수의 반환 타입을 통해 특정 매개변수가 특정 타입에 해당하는지 여부를 타입스크립트 컴파일러에 알려주는 함수입니다 [1]. 런타임에는 불리언(boolean) 값을 반환하지만, 타입 시스템은 이 반환 값을 바탕으로 타입 좁히기(Type Narrowing)를 적용합니다 [1]. 개발자는 `is` 키워드를 활용해 커스텀 타입 가드(Type Guard)를 정의할 때 이 기능을 핵심적으로 사용합니다 [2]. @@ -27,11 +27,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 타입 서술어(Type Predicat - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[타입 좁히기(Type Narrowing)]], [[타입 가드(Type Guards)]], [[브랜디드 타입(Branded Types)]], [[타입 단언(Type Assertions)]] -- **Projects/Contexts:** [[타입스크립트 애플리케이션의 런타임 값 검증 및 커스텀 타입 보장 구조 설계]] +- **Related Topics:** [[타입 좁히기(Type Narrowing)|타입 좁히기(Type Narrowing)]], [[타입 가드(Type Guards)|타입 가드(Type Guards)]], [[브랜디드 타입(Branded Types)|브랜디드 타입(Branded Types)]], [[타입 단언(Type Assertions)|타입 단언(Type Assertions)]] +- **Projects/Contexts:** 타입스크립트 애플리케이션의 런타임 값 검증 및 커스텀 타입 보장 구조 설계 - **Contradictions/Notes:** 타입 서술어는 타입을 좁혀주는 훌륭한 도구이지만, 그 자체로 내부 로직의 무결성을 타입스크립트가 검증해 주지 않기 때문에 개발자가 검증 로직을 잘못 작성하면 `as` 단언처럼 타입 시스템에 치명적인 거짓 정보(타입 오류)를 제공할 위험이 있습니다 [1]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/타입 서술어(Type Predicates).md]] +- Raw Source: 00_Raw/2026-04-20/타입 서술어(Type Predicates).md --- diff --git a/01_Archive/2026-04-20/타입 안전성 (Type Safety).md b/01_Archive/2026-04-20/타입 안전성 (Type Safety).md index d1806c72..bbc9370e 100644 --- a/01_Archive/2026-04-20/타입 안전성 (Type Safety).md +++ b/01_Archive/2026-04-20/타입 안전성 (Type Safety).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-4B2CBD -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 타입 안전성 (Type Safety)" --- -# [[타입 안전성 (Type Safety)]] +# [[타입 안전성 (Type Safety)|타입 안전성 (Type Safety)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 타입 안전성은 소프트웨어 개발에서 예기치 않은 런타임 오류를 방지하고 컴파일 시점에 타입을 엄격하게 검사하여 코드의 예측 가능성을 높이는 원칙이다 [1-3]. TypeScript와 같은 정적 타입 시스템에서는 구조적 타이핑, 과잉 속성 검사, 식별 가능한 유니온 등의 메커니즘을 통해 유효하지 않은 데이터나 잘못된 상태가 코드상에 표현되는 것을 원천적으로 차단한다 [4-6]. 이를 통해 개발자는 런타임 디버깅에 의존하는 대신 정적 분석을 활용하여 버그를 조기에 발견하고 견고한 아키텍처를 구축할 수 있다 [3, 7, 8]. @@ -23,11 +23,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 타입 안전성 (Type Safety) - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[구조적 타이핑 (Structural Typing)]], [[식별 가능한 유니온 (Discriminated Unions)]], [[과잉 속성 검사 (Excess Property Checking)]], [[브랜디드 타입 (Branded Types)]], [[불변성 (Immutability)]] -- **Projects/Contexts:** [[TypeScript의 컴파일 타임 에러 검증]], [[API 응답 및 데이터 변환 처리]], [[React 컴포넌트 상태 관리]] +- **Related Topics:** [[구조적 타이핑 (Structural Typing)|구조적 타이핑 (Structural Typing)]], [[식별 가능한 유니온 (Discriminated Unions)|식별 가능한 유니온 (Discriminated Unions)]], 과잉 속성 검사 (Excess Property Checking), [[브랜디드 타입 (Branded Types)|브랜디드 타입 (Branded Types)]], [[불변성 (Immutability)|불변성 (Immutability)]] +- **Projects/Contexts:** TypeScript의 컴파일 타임 에러 검증, API 응답 및 데이터 변환 처리, React 컴포넌트 상태 관리 - **Contradictions/Notes:** 소스에 따르면, 구조적 타이핑은 속성 구조가 일치하면 호환을 허용하는 유연성을 제공하지만, 의도치 않은 추가 속성을 허용할 수 있는 맹점이 존재한다 [19, 26, 27]. 이를 보완하기 위해 TypeScript는 객체 리터럴이 직접 할당될 때 '과잉 속성 검사(Excess Property Checking)'를 수행하지만, 중간 변수를 거칠 경우 이 검사가 무력화되는 한계가 있으며, 이 경우 `satisfies` 연산자가 효과적인 대안이 된다 [4, 24, 28, 29]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/타입 안전성 (Type Safety).md]] +- Raw Source: 00_Raw/2026-04-20/타입 안전성 (Type Safety).md --- diff --git a/01_Archive/2026-04-20/타입 정의가 부족한 서드파티 라이브러리 연동.md b/01_Archive/2026-04-20/타입 정의가 부족한 서드파티 라이브러리 연동.md index 994057b0..cbad979e 100644 --- a/01_Archive/2026-04-20/타입 정의가 부족한 서드파티 라이브러리 연동.md +++ b/01_Archive/2026-04-20/타입 정의가 부족한 서드파티 라이브러리 연동.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-471F26 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 타입 정의가 부족한 서드파티 라이브러리 연동" --- -# [[타입 정의가 부족한 서드파티 라이브러리 연동]] +# [[타입 정의가 부족한 서드파티 라이브러리 연동|타입 정의가 부족한 서드파티 라이브러리 연동]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 타입 정의가 부족한 서드파티 라이브러리 연동은 정적 타입 시스템(예: 타입스크립트, 파이썬 등)을 사용하는 프로젝트에서 타입 정보가 없거나 부정확한 외부 패키지를 통합하는 과정을 의미합니다 [1, 2]. 신중하게 작성된 코드일지라도 타입이 불완전한 외부 라이브러리를 거치면 타입 정보가 손실되거나 훼손될 위험이 있습니다 [1]. 이를 해결하기 위해 개발자는 선언 파일(`.d.ts`)을 추가하거나, 모듈 선언, 타입 단언(`as`), `any` 타입 등을 활용하여 에러를 억제하고 타입 안정성을 보완해야 합니다 [2-4]. @@ -30,11 +30,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 타입 정의가 부족한 서 - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[선언 파일(.d.ts)]], [[타입 단언(Type Assertions)]], [[any 타입]] -- **Projects/Contexts:** [[타입스크립트 프로젝트의 외부 자바스크립트 라이브러리 마이그레이션 및 연동]] +- **Related Topics:** [[선언 파일(.d.ts)|선언 파일(.d.ts)]], [[타입 단언(Type Assertions)|타입 단언(Type Assertions)]], any 타입 +- **Projects/Contexts:** 타입스크립트 프로젝트의 외부 자바스크립트 라이브러리 마이그레이션 및 연동 - **Contradictions/Notes:** 소스에 관련 정보가 부족합니다. (타입 정의가 부족한 서드파티 라이브러리 연동에 관하여 소스들 간의 명시적인 상충 의견은 제공된 자료에 포함되어 있지 않습니다.) --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/타입 정의가 부족한 서드파티 라이브러리 연동.md]] +- Raw Source: 00_Raw/2026-04-20/타입 정의가 부족한 서드파티 라이브러리 연동.md --- diff --git a/01_Archive/2026-04-20/타입 조건자(Type Predicates).md b/01_Archive/2026-04-20/타입 조건자(Type Predicates).md index 5b31f344..4083420d 100644 --- a/01_Archive/2026-04-20/타입 조건자(Type Predicates).md +++ b/01_Archive/2026-04-20/타입 조건자(Type Predicates).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-F5B64F -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 타입 조건자(Type Predicates)" --- -# [[타입 조건자(Type Predicates)]] +# [[타입 조건자(Type Predicates)|타입 조건자(Type Predicates)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 타입 조건자(Type Predicates)는 특정 매개변수가 지정된 타입인지 여부를 나타내는 함수입니다 [1]. 런타임 시점에는 불리언(boolean) 값을 반환하지만, TypeScript의 타입 시스템은 이 반환 값을 인식하여 자동으로 타입 좁히기(Type Narrowing)를 적용합니다 [1]. 일반적으로 커스텀 타입 가드 함수 내에서 `is` 키워드를 사용하여 정의됩니다 [2]. @@ -23,11 +23,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 타입 조건자(Type Predicat - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[타입 좁히기(Type Narrowing)]], [[브랜디드 타입(Branded Types)]], [[타입 단언(Type Assertions)]], [[타입 가드(Type Guards)]] -- **Projects/Contexts:** [[TypeScript의 안전한 타입 검증 및 커스텀 타입 가드 설계]] +- **Related Topics:** [[타입 좁히기(Type Narrowing)|타입 좁히기(Type Narrowing)]], [[브랜디드 타입(Branded Types)|브랜디드 타입(Branded Types)]], [[타입 단언(Type Assertions)|타입 단언(Type Assertions)]], [[타입 가드(Type Guards)|타입 가드(Type Guards)]] +- **Projects/Contexts:** TypeScript의 안전한 타입 검증 및 커스텀 타입 가드 설계 - **Contradictions/Notes:** 타입 조건자는 타입을 안전하게 좁히기 위한 유용한 도구로 사용되지만, 실제로는 TypeScript 컴파일러가 내부 로직의 정확성을 검증해주지 않으므로 `as` 단언문(Type Assertion)보다 본질적으로 더 타입-안전(type-safe)하다고 볼 수는 없습니다 [1]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/타입 조건자(Type Predicates).md]] +- Raw Source: 00_Raw/2026-04-20/타입 조건자(Type Predicates).md --- diff --git a/01_Archive/2026-04-20/타입 좁히기 (Type Narrowing).md b/01_Archive/2026-04-20/타입 좁히기 (Type Narrowing).md index c8a6daeb..a8f0bebe 100644 --- a/01_Archive/2026-04-20/타입 좁히기 (Type Narrowing).md +++ b/01_Archive/2026-04-20/타입 좁히기 (Type Narrowing).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-4245C8 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 타입 좁히기 (Type Narrowing)" --- -# [[타입 좁히기 (Type Narrowing)]] +# [[타입 좁히기 (Type Narrowing)|타입 좁히기 (Type Narrowing)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 타입 좁히기(Type Narrowing)는 TypeScript에서 유니온 타입과 같이 여러 타입의 가능성을 내포하는 변수를 다룰 때, 코드 흐름 분석(Code Flow Analysis)을 통해 더 구체적이고 한정된 타입으로 줄여나가는 과정입니다 [1, 2]. 이를 통해 컴파일러는 특정 코드 블록 내에서 값의 형태를 확신할 수 있게 되며, 개발자는 특정 타입에만 존재하는 속성에 안전하게 접근할 수 있습니다 [2-4]. 주로 `typeof`, `instanceof`, `in` 연산자 또는 사용자 정의 타입 가드 및 판별자(Discriminant)를 활용하여 수행됩니다 [5, 6]. @@ -32,11 +32,11 @@ TypeScript의 `satisfies` 연산자를 식별 가능한 유니온과 함께 사 - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[유니온 타입 (Union Types)]], [[식별 가능한 유니온 (Discriminated Unions)]], [[타입 가드 (Type Guards)]], [[타입 서술어 (Type Predicates)]] -- **Projects/Contexts:** [[제어 흐름 분석 (Control Flow Analysis)]], [[API 응답 및 상태 모델링 (State Modeling and API Responses)]] +- **Related Topics:** [[유니온 타입 (Union Types)|유니온 타입 (Union Types)]], [[식별 가능한 유니온 (Discriminated Unions)|식별 가능한 유니온 (Discriminated Unions)]], [[타입 가드 (Type Guards)|타입 가드 (Type Guards)]], [[타입 서술어 (Type Predicates)|타입 서술어 (Type Predicates)]] +- **Projects/Contexts:** [[제어 흐름 분석 (Control Flow Analysis)|제어 흐름 분석 (Control Flow Analysis)]], [[API 응답 및 상태 모델링 (State Modeling and API Responses)|API 응답 및 상태 모델링 (State Modeling and API Responses)]] - **Contradictions/Notes:** 타입 서술어(Type Predicates)를 사용하여 타입을 좁힐 때, TypeScript 컴파일러는 함수 내부의 로직이 개발자가 의도한 브랜드 타입이나 좁히기 조건과 실제로 일치하는지까지는 검사하지 않고 전적으로 코드 작성자의 논리에 의존하므로 주의가 필요합니다 [9]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/타입 좁히기 (Type Narrowing).md]] +- Raw Source: 00_Raw/2026-04-20/타입 좁히기 (Type Narrowing).md --- diff --git a/01_Archive/2026-04-20/타입 좁히기(Type Narrowing).md b/01_Archive/2026-04-20/타입 좁히기(Type Narrowing).md index f3defd7a..19186239 100644 --- a/01_Archive/2026-04-20/타입 좁히기(Type Narrowing).md +++ b/01_Archive/2026-04-20/타입 좁히기(Type Narrowing).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-C17DEE -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 타입 좁히기(Type Narrowing)" --- -# [[타입 좁히기(Type Narrowing)]] +# [[타입 좁히기(Type Narrowing)|타입 좁히기(Type Narrowing)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 타입 좁히기(Type Narrowing)는 TypeScript에서 변수가 가질 수 있는 여러 넓은 타입(예: 유니온 타입)을 특정 코드 블록 내에서 더 구체적인 타입으로 범위를 좁혀나가는 과정입니다 [1, 2]. 조건문과 같은 런타임 동작을 기반으로 제어 흐름 분석(Control flow analysis)을 수행하여 컴파일러가 타입을 안전하게 추론하게 만듭니다 [2]. 이를 통해 개발자는 런타임 에러를 방지하고, IDE의 자동 완성과 타입 안전성을 극대화할 수 있습니다 [3]. @@ -27,11 +27,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 타입 좁히기(Type Narrowin - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[식별 가능한 유니온(Discriminated Unions)]], [[타입 가드(Type Guards)]], [[유니온 타입(Union Types)]] -- **Projects/Contexts:** [[상태 관리 및 API 응답 모델링(State Management and API Response Modeling)]] +- **Related Topics:** [[식별 가능한 유니온(Discriminated Unions)|식별 가능한 유니온(Discriminated Unions)]], [[타입 가드(Type Guards)|타입 가드(Type Guards)]], [[유니온 타입(Union Types)|유니온 타입(Union Types)]] +- **Projects/Contexts:** [[상태 관리 및 API 응답 모델링(State Management and API Response Modeling)|상태 관리 및 API 응답 모델링(State Management and API Response Modeling)]] - **Contradictions/Notes:** 소스 상에서 타입 좁히기 자체에 대한 모순된 주장은 존재하지 않습니다. 다만, 타입 좁히기를 통한 검증 과정을 생략하고 타입 단언(`as`)을 사용하여 강제로 타입을 캐스팅하는 방식은 런타임 타입 안전성을 보장하지 못하며 초과 속성 검사(Excess Property Checking)를 무력화할 수 있어 지양해야 한다는 점이 강조됩니다 [2, 12, 13]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/타입 좁히기(Type Narrowing).md]] +- Raw Source: 00_Raw/2026-04-20/타입 좁히기(Type Narrowing).md --- diff --git a/01_Archive/2026-04-20/타입 캐스팅 (Type Casting).md b/01_Archive/2026-04-20/타입 캐스팅 (Type Casting).md index 9fe6ff0c..c1d886a0 100644 --- a/01_Archive/2026-04-20/타입 캐스팅 (Type Casting).md +++ b/01_Archive/2026-04-20/타입 캐스팅 (Type Casting).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-A91EB7 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 타입 캐스팅 (Type Casting)" --- -# [[타입 캐스팅 (Type Casting)]] +# [[타입 캐스팅 (Type Casting)|타입 캐스팅 (Type Casting)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 타입 캐스팅(Type Casting) 또는 타입 단언(Type Assertion)은 개발자가 TypeScript 컴파일러에게 특정 값의 타입 정보를 강제로 지정하여 "내가 이 타입을 더 잘 알고 있다"고 알려주는 기능입니다 [1, 2]. 다른 프로그래밍 언어의 타입 캐스팅과 유사해 보이지만, 런타임에 데이터 구조를 바꾸거나 특별한 검사를 수행하지 않으며 순전히 컴파일 타임에만 작용합니다 [2]. 그러나 잘못 사용하면 컴파일러의 안전장치를 우회하게 되어 런타임 에러를 유발할 수 있으므로 극히 주의해서 사용해야 합니다 [1, 3]. @@ -30,11 +30,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 타입 캐스팅 (Type Casting - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[타입 단언 (Type Assertions)]], [[satisfies 연산자 (Satisfies Operator)]], [[브랜디드 타입 (Branded Types)]], [[타입 가드 (Type Guards)]] +- **Related Topics:** [[타입 단언 (Type Assertions)|타입 단언 (Type Assertions)]], satisfies 연산자 (Satisfies Operator), [[브랜디드 타입 (Branded Types)|브랜디드 타입 (Branded Types)]], [[타입 가드 (Type Guards)|타입 가드 (Type Guards)]] - **Projects/Contexts:** TypeScript가 타입을 정밀하게 추론하지 못하는 DOM 요소 조작이나 런타임 검증이 완료된 외부 API 응답 처리 맥락 [1, 7], 구조적 타이핑 우회 및 Opaque Type 강제 할당 시스템 설계 시 [4, 5, 8] - **Contradictions/Notes:** 타입 캐스팅(`as`)은 강력한 강제성을 지니지만 데이터 유효성을 담보하지는 않습니다. 따라서 잉여 속성을 체크하거나 타입 안정성을 잃지 않으려면 캐스팅을 남용하지 말고 `satisfies` 키워드를 활용해 구조와 값을 동시에 엄격하게 검증하는 편이 낫다는 것이 소스의 주요한 조언입니다 [1, 5, 9]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/타입 캐스팅 (Type Casting).md]] +- Raw Source: 00_Raw/2026-04-20/타입 캐스팅 (Type Casting).md --- diff --git a/01_Archive/2026-04-20/타입스크립트 상태 관리 및 분기 처리 설계.md b/01_Archive/2026-04-20/타입스크립트 상태 관리 및 분기 처리 설계.md index 16f9d31f..72e27c5a 100644 --- a/01_Archive/2026-04-20/타입스크립트 상태 관리 및 분기 처리 설계.md +++ b/01_Archive/2026-04-20/타입스크립트 상태 관리 및 분기 처리 설계.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-8F7FE7 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 타입스크립트 상태 관리 및 분기 처리 설계" --- -# [[타입스크립트 상태 관리 및 분기 처리 설계]] +# [[타입스크립트 상태 관리 및 분기 처리 설계|타입스크립트 상태 관리 및 분기 처리 설계]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 타입스크립트의 상태 관리 및 분기 처리 설계는 강력한 타입 시스템을 활용하여 유효하지 않은 상태를 원천적으로 차단하고 조건 분기의 안전성을 보장하는 아키텍처 기법입니다. 핵심적으로 '식별 가능한 유니온(Discriminated Unions)' 패턴을 통해 다양한 상태를 구조화하고, `switch`나 `if` 문에서 공통 속성을 판별자로 사용하여 타입을 안전하게 좁힙니다. 여기에 `never` 타입을 활용한 완전성 검사(Exhaustiveness Checking)와 `readonly`를 통한 상태의 불변성을 결합하여, 런타임 에러를 컴파일 타임에 방지하는 견고한 애플리케이션 논리를 구축합니다. @@ -33,11 +33,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 타입스크립트 상태 관 - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[식별 가능한 유니온(Discriminated Unions)]], [[타입 좁히기(Type Narrowing)]], [[완전성 검사(Exhaustiveness Checking)]], [[불변성과 Readonly]], [[구조적 타이핑(Structural Typing)]] -- **Projects/Contexts:** [[React 상태 관리 및 리듀서 패턴 구현]], [[ts-pattern 라이브러리를 활용한 패턴 매칭]] +- **Related Topics:** [[식별 가능한 유니온(Discriminated Unions)|식별 가능한 유니온(Discriminated Unions)]], [[타입 좁히기(Type Narrowing)|타입 좁히기(Type Narrowing)]], [[완전성 검사(Exhaustiveness Checking)|완전성 검사(Exhaustiveness Checking)]], 불변성과 Readonly, [[구조적 타이핑(Structural Typing)|구조적 타이핑(Structural Typing)]] +- **Projects/Contexts:** React 상태 관리 및 리듀서 패턴 구현, ts-pattern 라이브러리를 활용한 패턴 매칭 - **Contradictions/Notes:** 분기 처리를 간결하게 만들기 위해 고안된 `ts-pattern` 라이브러리는 유용하지만, 내부적으로 복잡한 타입 추론과 객체 생성을 수반하므로 기본 `if/else` 구문에 비해 성능이 99%가량 느리다는 벤치마크 결과가 있습니다 [19, 23]. 따라서 무조건적인 라이브러리 의존보다는 기존 분기문과 IIFE를 적절히 활용하는 유연한 접근이 필요하다는 주장이 존재합니다 [20, 22]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/타입스크립트 상태 관리 및 분기 처리 설계.md]] +- Raw Source: 00_Raw/2026-04-20/타입스크립트 상태 관리 및 분기 처리 설계.md --- diff --git a/01_Archive/2026-04-20/타파스(Tapas).md b/01_Archive/2026-04-20/타파스(Tapas).md index cef6430f..50fc9833 100644 --- a/01_Archive/2026-04-20/타파스(Tapas).md +++ b/01_Archive/2026-04-20/타파스(Tapas).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-610FD5 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 타파스(Tapas)" --- -# [[타파스(Tapas)]] +# [[타파스(Tapas)|타파스(Tapas)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 타파스(Tapas)는 넷플릭스(Netflix)의 코스모스(Cosmos) 플랫폼 내에서 작동하는 가장 크고 복잡한 상위 계층의 서비스입니다 [1]. 이 서비스의 주된 목적은 제작 스튜디오로부터 원본 미디어를 수신하여 넷플릭스 서비스에서 재생할 수 있는 최종 형태로 처리하는 것입니다 [1]. 짧은 대기 시간보다는 하루 단위의 대규모 작업 완료와 비용 효율성에 중점을 두는 처리량 민감형(throughput-sensitive) 애플리케이션입니다 [2]. @@ -22,11 +22,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 타파스(Tapas)" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[넷플릭스 코스모스 플랫폼(Netflix Cosmos Platform)]], [[스트라툼(Stratum)]] -- **Projects/Contexts:** [[넷플릭스의 미디어 처리 및 인코딩 파이프라인]] +- **Related Topics:** [[넷플릭스 코스모스 플랫폼 (Netflix Cosmos Platform)|넷플릭스 코스모스 플랫폼(Netflix Cosmos Platform)]], 스트라툼(Stratum) +- **Projects/Contexts:** 넷플릭스의 미디어 처리 및 인코딩 파이프라인 - **Contradictions/Notes:** 소스에 타파스와 상반되는 주장이나 모순되는 정보는 포함되어 있지 않습니다. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/타파스(Tapas).md]] +- Raw Source: 00_Raw/2026-04-20/타파스(Tapas).md --- diff --git a/01_Archive/2026-04-20/테스트 용이성 (Testability).md b/01_Archive/2026-04-20/테스트 용이성 (Testability).md index 3790faee..a331b38b 100644 --- a/01_Archive/2026-04-20/테스트 용이성 (Testability).md +++ b/01_Archive/2026-04-20/테스트 용이성 (Testability).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-BF1A40 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 테스트 용이성 (Testability)" --- -# [[테스트 용이성 (Testability)]] +# [[테스트 용이성 (Testability)|테스트 용이성 (Testability)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 테스트 용이성이란 소프트웨어 시스템의 다양한 부분에 대해 자동화된 테스트를 직관적이고 쉽게 생성할 수 있도록 설계된 정도를 의미합니다 [1]. 이는 비즈니스 로직을 데이터베이스나 UI 같은 외부 환경으로부터 완전히 격리하여, 복잡한 설정이나 거대한 통합 테스트 없이 핵심 로직만을 검증할 수 있게 하는 아키텍처 및 코드의 특성입니다 [2, 3]. 테스트가 용이한 코드는 각 모듈이 독립적이고 결합도가 낮아 전체 시스템을 설정할 필요 없이 개별 관심사에 초점을 맞춘 단위 테스트를 용이하게 만듭니다 [4, 5]. @@ -24,11 +24,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 테스트 용이성 (Testabili - **정책 변화:** Design & Experience 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[관심사의 분리 (Separation of Concerns)]], [[의존성 주입 (Dependency Injection)]], [[클린 아키텍처 (Clean Architecture)]], [[테스트 더블 (Test Double)]] -- **Projects/Contexts:** [[소프트웨어 아키텍처 설계]], [[AI 시스템 아키텍처 개발]], [[마이크로서비스 아키텍처 구축]] +- **Related Topics:** [[관심사의 분리 (Separation of Concerns)|관심사의 분리 (Separation of Concerns)]], [[의존성 주입 (Dependency Injection)|의존성 주입 (Dependency Injection)]], [[클린 아키텍처 (Clean Architecture)|클린 아키텍처 (Clean Architecture)]], 테스트 더블 (Test Double) +- **Projects/Contexts:** [[소프트웨어 아키텍처 설계|소프트웨어 아키텍처 설계]], AI 시스템 아키텍처 개발, 마이크로서비스 아키텍처 구축 - **Contradictions/Notes:** 모의 객체(Mock)와 스텁(Stub) 사용에 있어, 테스트를 단순하게 하고 외부 시스템으로부터 코드를 보호해 준다는 강력한 장점이 있지만, 너무 남용할 경우 코드가 실제와 다르게 동작할 수 있고 구현 세부 사항과 강하게 결합되어 테스트의 신뢰성을 떨어뜨릴 수 있다는 classicist 관점의 경고가 존재합니다 [19, 20]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/테스트 용이성 (Testability).md]] +- Raw Source: 00_Raw/2026-04-20/테스트 용이성 (Testability).md --- diff --git a/01_Archive/2026-04-20/토스(Toss) Front SDK 퍼사드 패턴 적용.md b/01_Archive/2026-04-20/토스(Toss) Front SDK 퍼사드 패턴 적용.md index e34d819d..4ff9ecf4 100644 --- a/01_Archive/2026-04-20/토스(Toss) Front SDK 퍼사드 패턴 적용.md +++ b/01_Archive/2026-04-20/토스(Toss) Front SDK 퍼사드 패턴 적용.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-1CFB9E -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 토스(Toss) Front SDK 퍼사드 패턴 적용" --- -# [[토스(Toss) Front SDK 퍼사드 패턴 적용]] +# [[토스(Toss) Front SDK 퍼사드 패턴 적용|토스(Toss) Front SDK 퍼사드 패턴 적용]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 토스플레이스는 자체 개발한 결제 단말기인 Toss Front의 외부 연동 SDK를 개발하며, 사용성을 높이기 위해 퍼사드(Facade) 패턴을 적용했습니다 [1, 2]. 이 패턴은 단순히 복잡한 내부 로직을 숨기는 데 그치지 않고, 복잡한 내부 구현을 '사용자의 의도(Intent)'를 기준으로 재구성하는 데 본질적인 목적이 있습니다 [3]. 이를 통해 연동사 측의 휴먼 에러를 구조적으로 방지함과 동시에 SDK의 장기적인 호환성과 개발자 경험(DX)을 크게 향상시킬 수 있습니다 [4-6]. @@ -30,11 +30,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 토스(Toss) Front SDK 퍼사 - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[단일 책임 원칙(SRP)]], [[추상화(Abstraction)]], [[개발자 경험(DX)]] -- **Projects/Contexts:** [[토스플레이스 결제 단말기 외부 연동 SDK 개발]] +- **Related Topics:** [[단일 책임 원칙(SRP)|단일 책임 원칙(SRP)]], [[추상화(Abstraction)|추상화(Abstraction)]], [[개발자 경험(DX)|개발자 경험(DX)]] +- **Projects/Contexts:** [[토스플레이스 결제 단말기 외부 연동 SDK 개발|토스플레이스 결제 단말기 외부 연동 SDK 개발]] - **Contradictions/Notes:** 퍼사드 패턴을 통한 높은 추상화는 사용자에게 큰 편의성을 제공하지만, 필연적으로 세밀한 제어를 불가능하게 만들고 SDK 내부 구현의 복잡성을 가중시키는 단점이 존재하므로, 탈출구(Escape Hatch) 역할을 할 수 있는 저수준(Low-level) 인터페이스의 병행 제공이 필수적입니다 [8, 9]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/토스(Toss) Front SDK 퍼사드 패턴 적용.md]] +- Raw Source: 00_Raw/2026-04-20/토스(Toss) Front SDK 퍼사드 패턴 적용.md --- diff --git a/01_Archive/2026-04-20/토스(Toss) SDK 설계.md b/01_Archive/2026-04-20/토스(Toss) SDK 설계.md index 96c8fed1..e2cb5d6d 100644 --- a/01_Archive/2026-04-20/토스(Toss) SDK 설계.md +++ b/01_Archive/2026-04-20/토스(Toss) SDK 설계.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-D59267 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 토스(Toss) SDK 설계" --- -# [[토스(Toss) SDK 설계]] +# [[토스(Toss) SDK 설계|토스(Toss) SDK 설계]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 토스플레이스의 자체 결제 단말기인 Toss Front를 위한 외부 연동 SDK 설계 방식입니다 [1]. 이 SDK는 퍼사드(Facade) 패턴을 활용하여 복잡한 내부 로직을 사용자의 의도(Intent) 중심으로 추상화하여 사용 편의성과 안정성을 극대화했습니다 [2]. 결과적으로 개발자 경험(DX)을 향상시키면서도 휴먼 에러를 구조적으로 방지하고, 고수준과 저수준 인터페이스를 함께 제공하여 유연성까지 확보한 것이 특징입니다 [3, 4]. @@ -26,11 +26,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 토스(Toss) SDK 설계" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[퍼사드(Facade) 패턴]], [[단일 책임 원칙(SRP)]], [[개발자 경험(DX)]] -- **Projects/Contexts:** [[Toss Front]], [[토스플레이스]] +- **Related Topics:** 퍼사드(Facade) 패턴, [[단일 책임 원칙(SRP)|단일 책임 원칙(SRP)]], [[개발자 경험(DX)|개발자 경험(DX)]] +- **Projects/Contexts:** Toss Front, 토스플레이스 - **Contradictions/Notes:** 퍼사드 패턴을 통해 추상화 수준이 높아질수록 사용자에게 편의성을 제공하지만, 세밀한 제어가 제한되고 SDK 내부의 유지 비용 및 복잡도가 증가하는 트레이드오프(Trade-off)가 발생합니다. 소스에서는 이를 해결하기 위해 저수준 인터페이스를 '탈출구(Escape Hatch)'로 함께 제공해야 한다고 설명합니다 [8, 9]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/토스(Toss) SDK 설계.md]] +- Raw Source: 00_Raw/2026-04-20/토스(Toss) SDK 설계.md --- diff --git a/01_Archive/2026-04-20/토스플레이스 결제 단말기 외부 연동 SDK 개발.md b/01_Archive/2026-04-20/토스플레이스 결제 단말기 외부 연동 SDK 개발.md index b22f1dae..11dc1b7f 100644 --- a/01_Archive/2026-04-20/토스플레이스 결제 단말기 외부 연동 SDK 개발.md +++ b/01_Archive/2026-04-20/토스플레이스 결제 단말기 외부 연동 SDK 개발.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-53C817 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 토스플레이스 결제 단말기 외부 연동 SDK 개발" --- -# [[토스플레이스 결제 단말기 외부 연동 SDK 개발]] +# [[토스플레이스 결제 단말기 외부 연동 SDK 개발|토스플레이스 결제 단말기 외부 연동 SDK 개발]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 토스플레이스 결제 단말기 외부 연동 SDK는 자체 개발한 결제 단말기인 'Toss Front'에서 외부 연동사가 원하는 플러그인 앱을 개발하고 동작시킬 수 있도록 지원하는 도구입니다 [1]. 이 SDK는 단순한 기능 노출을 넘어, 사용자의 의도(Intent)에 맞춰 복잡한 내부 구현을 재구성하는 퍼사드(Facade) 패턴을 적용하여 설계되었습니다 [2, 3]. 이를 통해 연동 과정에서 발생할 수 있는 휴먼 에러를 구조적으로 방지하고, 단말기 생태계의 안정적인 확장을 도모하는 것을 핵심 목표로 합니다 [2, 4]. @@ -25,11 +25,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 토스플레이스 결제 단 - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Facade 패턴]], [[단일 책임 원칙(SRP)]], [[Escape Hatch]] -- **Projects/Contexts:** [[Toss Front]] +- **Related Topics:** Facade 패턴, [[단일 책임 원칙(SRP)|단일 책임 원칙(SRP)]], [[Escape Hatch (탈출구)|Escape Hatch]] +- **Projects/Contexts:** Toss Front - **Contradictions/Notes:** 소스에서는 Facade 패턴이 모든 문제의 정답은 아니며, 추상화가 높아질수록 세밀한 제어가 어려워지고 유지 비용이 증가하는 단점이 있다고 지적합니다 [6]. 따라서 Facade의 편리함에만 안주하지 않고, 언제든 저수준 인터페이스로 내려갈 수 있는 탈출구(Escape Hatch)를 제공하여 설계의 균형을 잡는 것이 중요하다고 주장합니다 [6, 7]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/토스플레이스 결제 단말기 외부 연동 SDK 개발.md]] +- Raw Source: 00_Raw/2026-04-20/토스플레이스 결제 단말기 외부 연동 SDK 개발.md --- diff --git a/01_Archive/2026-04-20/팀 단위 코드 품질 및 컨벤션 유지.md b/01_Archive/2026-04-20/팀 단위 코드 품질 및 컨벤션 유지.md index f4ed0b71..e34ce17f 100644 --- a/01_Archive/2026-04-20/팀 단위 코드 품질 및 컨벤션 유지.md +++ b/01_Archive/2026-04-20/팀 단위 코드 품질 및 컨벤션 유지.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-9B19C8 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 팀 단위 코드 품질 및 컨벤션 유지" --- -# [[팀 단위 코드 품질 및 컨벤션 유지]] +# [[팀 단위 코드 품질 및 컨벤션 유지|팀 단위 코드 품질 및 컨벤션 유지]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 팀 단위 코드 품질 및 컨벤션 유지는 다수의 개발자가 협업하는 환경에서 일관된 코드 스타일을 적용하고 결함을 사전에 방지하여 소프트웨어의 전반적인 품질을 향상시키는 과정입니다. 이를 위해 ESLint와 Prettier 같은 정적 분석 및 포매팅 도구를 활용하며, Husky와 lint-staged를 통해 Git 훅(Hook) 단계에서 규칙 준수를 강제합니다. 더불어 기계적인 검사와 사람의 아키텍처 판단이 결합된 하이브리드 코드 리뷰와 명확한 거버넌스 정책을 통해 코드베이스의 건전성을 지속적으로 개선합니다. @@ -33,11 +33,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 팀 단위 코드 품질 및 - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[ESLint]], [[Prettier]], [[Husky]], [[lint-staged]], [[코드 리뷰(Code Review)]], [[정적 애플리케이션 보안 테스트(SAST)]] -- **Projects/Contexts:** [[모노레포(Monorepo) 설정 중앙화]], [[CI/CD 파이프라인 자동화]], [[AI 거버넌스 정책(AI Usage Policy)]] +- **Related Topics:** [[ESLint|ESLint]], [[Prettier|Prettier]], [[Husky|Husky]], [[lint-staged|lint-staged]], [[코드 리뷰(Code Review)|코드 리뷰(Code Review)]], [[정적 애플리케이션 보안 테스트(SAST)|정적 애플리케이션 보안 테스트(SAST)]] +- **Projects/Contexts:** [[모노레포(Monorepo) 설정 중앙화|모노레포(Monorepo) 설정 중앙화]], [[CI_CD 파이프라인 자동화|CI/CD 파이프라인 자동화]], [[AI 거버넌스 정책(AI Usage Policy)|AI 거버넌스 정책(AI Usage Policy)]] - **Contradictions/Notes:** 소스에 따르면 ESLint와 Prettier는 함께 사용할 때 포매팅 규칙에서 충돌이 발생할 수 있으며, 이를 해결하기 위해 `eslint-config-prettier`를 사용하여 ESLint의 관련 기능을 끄는 것이 공식 권장 사항입니다 [5, 9]. 또한, 자동화된 코드 리뷰 도구가 매우 빠르고 일관적이지만 비즈니스 로직의 의도나 아키텍처의 문맥을 이해할 수는 없으므로(Context Blindness), 자동화가 수동 리뷰를 완전히 대체해서는 안 되며 상호 보완적으로 사용해야 한다고 강조합니다 [47, 48]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/팀 단위 코드 품질 및 컨벤션 유지.md]] +- Raw Source: 00_Raw/2026-04-20/팀 단위 코드 품질 및 컨벤션 유지.md --- diff --git a/01_Archive/2026-04-20/포인터 압축(Pointer Compression).md b/01_Archive/2026-04-20/포인터 압축(Pointer Compression).md index a5490a34..8d966f42 100644 --- a/01_Archive/2026-04-20/포인터 압축(Pointer Compression).md +++ b/01_Archive/2026-04-20/포인터 압축(Pointer Compression).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-E763EA -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 포인터 압축(Pointer Compression)" --- -# [[포인터 압축(Pointer Compression)]] +# [[포인터 압축(Pointer Compression)|포인터 압축(Pointer Compression)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 포인터 압축(Pointer Compression)은 64비트 플랫폼에서 V8 엔진이 객체 참조에 따른 메모리 오버헤드를 줄이기 위해 포인터를 전체 주소 대신 기본 주소로부터의 32비트 오프셋(offset)으로 저장하는 기술입니다 [1]. 이 기술을 활성화하면 메모리 사용량이 감소하고 전반적인 성능이 향상되지만, 모든 힙 객체가 4GB 크기의 연속된 메모리 영역 내에 상주해야 한다는 제약이 생깁니다 [1-3]. @@ -23,11 +23,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 포인터 압축(Pointer Compr - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[V8 Memory Cage]], [[V8 Heap]], [[Garbage Collection (GC)]] -- **Projects/Contexts:** [[Electron]], [[V8 Engine]], [[Node.js]] +- **Related Topics:** [[V8 Memory Cage|V8 Memory Cage]], [[V8 힙(Heap)|V8 Heap]], [[Garbage Collection (GC)|Garbage Collection (GC)]] +- **Projects/Contexts:** [[Electron|Electron]], [[V8 Engine|V8 Engine]], [[Node.js|Node.js]] - **Contradictions/Notes:** 포인터 압축은 애플리케이션의 성능 향상 및 메모리 최적화를 제공하지만, 그 대가로 단일 V8 프로세스의 힙 크기를 4GB로 엄격히 제한하는 명확한 트레이드오프(Trade-off)를 갖습니다 [2, 3]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/포인터 압축(Pointer Compression).md]] +- Raw Source: 00_Raw/2026-04-20/포인터 압축(Pointer Compression).md --- diff --git a/01_Archive/2026-04-20/폭주-조절 갈등 (Vergence-Accommodation Conflict).md b/01_Archive/2026-04-20/폭주-조절 갈등 (Vergence-Accommodation Conflict).md index f075271c..c167523f 100644 --- a/01_Archive/2026-04-20/폭주-조절 갈등 (Vergence-Accommodation Conflict).md +++ b/01_Archive/2026-04-20/폭주-조절 갈등 (Vergence-Accommodation Conflict).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-6F67B5 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 폭주-조절 갈등 (Vergence-Accommodation Conflict)" --- -# [[폭주-조절 갈등 (Vergence-Accommodation Conflict)]] +# [[폭주-조절 갈등 (Vergence-Accommodation Conflict)|폭주-조절 갈등 (Vergence-Accommodation Conflict)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 폭주-조절 갈등(Vergence-Accommodation Conflict)은 자연스러운 시야 환경에서 함께 피드백 루프를 형성하여 정확한 깊이 단서를 제공하는 필수 안구 운동 기능인 폭주(Vergence)와 조절(Accommodation)이 서로 분리되거나 불일치하는 현상입니다 [1, 2]. 가상현실용 헤드마운트 디스플레이(HMD)와 같은 환경에서 시각적 깊이 단서가 상충할 때 발생하며, 깊이 지각의 불확실성과 여러 시각적 부작용을 초래합니다 [1, 2]. @@ -22,11 +22,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 폭주-조절 갈등 (Vergence - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[안구 운동 기능 (Oculomotor Functions)]], [[헤드마운트 디스플레이 (HMD)]], [[깊이 지각 (Depth Perception)]] -- **Projects/Contexts:** [[가상현실 엑서게임 (VR Exergaming)]] +- **Related Topics:** [[안구 운동 기능 (Oculomotor Functions)|안구 운동 기능 (Oculomotor Functions)]], [[헤드마운트 디스플레이 (HMD)|헤드마운트 디스플레이 (HMD)]], [[깊이 지각 (Depth Perception)|깊이 지각 (Depth Perception)]] +- **Projects/Contexts:** 가상현실 엑서게임 (VR Exergaming) - **Contradictions/Notes:** 소스에 폭주-조절 갈등과 관련된 상반된 정보나 모순점은 나타나지 않습니다. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/폭주-조절 갈등 (Vergence-Accommodation Conflict).md]] +- Raw Source: 00_Raw/2026-04-20/폭주-조절 갈등 (Vergence-Accommodation Conflict).md --- diff --git a/01_Archive/2026-04-20/폭주-조절 불일치(Vergence-Accommodation Conflicts).md b/01_Archive/2026-04-20/폭주-조절 불일치(Vergence-Accommodation Conflicts).md index 3391f9cf..11c544e8 100644 --- a/01_Archive/2026-04-20/폭주-조절 불일치(Vergence-Accommodation Conflicts).md +++ b/01_Archive/2026-04-20/폭주-조절 불일치(Vergence-Accommodation Conflicts).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-254684 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 폭주-조절 불일치(Vergence-Accommodation Conflicts)" --- -# [[폭주-조절 불일치(Vergence-Accommodation Conflicts)]] +# [[폭주-조절 불일치(Vergence-Accommodation Conflicts)|폭주-조절 불일치(Vergence-Accommodation Conflicts)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 폭주-조절 불일치(Vergence-Accommodation Conflicts)는 머리 착용 디스플레이(HMD)와 같은 가상현실 환경에서 정상적인 안구 운동 기능인 폭주와 조절이 서로 분리(decoupled)되는 현상을 뜻합니다 [1, 2]. 자연스러운 환경에서는 두 기능이 피드백 루프를 통해 함께 작동하여 정확한 깊이 지각을 돕지만, HMD에서는 이 과정이 어긋나게 됩니다 [2]. 이로 인해 깊이 지각의 불확실성이 발생하며, 두통, 눈의 피로, 복시 및 VR 멀미와 같은 다양한 시각적, 신체적 부작용이 유발될 수 있습니다 [1, 2]. @@ -22,11 +22,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 폭주-조절 불일치(Vergen - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[안구 운동 기능(Oculomotor functions)]], [[가상현실 멀미(VR Sickness)]], [[깊이 지각(Depth perception)]], [[헤드 마운트 디스플레이(HMD)]] -- **Projects/Contexts:** [[가상현실(VR) 시뮬레이션 및 HMD 사용 환경]] +- **Related Topics:** [[안구 운동 기능(Oculomotor functions)|안구 운동 기능(Oculomotor functions)]], [[가상현실 멀미(VR Sickness)|가상현실 멀미(VR Sickness)]], [[깊이 지각(Depth perception)|깊이 지각(Depth perception)]], [[헤드 마운트 디스플레이(HMD)|헤드 마운트 디스플레이(HMD)]] +- **Projects/Contexts:** 가상현실(VR) 시뮬레이션 및 HMD 사용 환경 - **Contradictions/Notes:** 소스에 따르면 폭주-조절 불일치가 특정 개인에게 VR 멀미를 일으키는 직접적인 원인인지, 아니면 단순히 멀미 증상의 심각성을 가중시키는 역할만 하는 것인지에 대해서는 아직 명확하게 밝혀지지 않았습니다 [1]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/폭주-조절 불일치(Vergence-Accommodation Conflicts).md]] +- Raw Source: 00_Raw/2026-04-20/폭주-조절 불일치(Vergence-Accommodation Conflicts).md --- diff --git a/01_Archive/2026-04-20/폭주-조절 불일치(Vergence-accommodation conflict).md b/01_Archive/2026-04-20/폭주-조절 불일치(Vergence-accommodation conflict).md index 0f196556..736fbdc7 100644 --- a/01_Archive/2026-04-20/폭주-조절 불일치(Vergence-accommodation conflict).md +++ b/01_Archive/2026-04-20/폭주-조절 불일치(Vergence-accommodation conflict).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-FC54F0 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 폭주-조절 불일치(Vergence-accommodation conflict)" --- -# [[폭주-조절 불일치(Vergence-accommodation conflict)]] +# [[폭주-조절 불일치(Vergence-accommodation conflict)|폭주-조절 불일치(Vergence-accommodation conflict)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 폭주-조절 불일치(Vergence-accommodation conflict)는 헤드 마운트 디스플레이(HMD)와 같은 가상현실(VR) 기기를 사용할 때 자연스러운 시각의 폭주(vergence)와 초점 조절(accommodation) 기능이 서로 분리되면서 발생하는 현상입니다 [1, 2]. 이는 상충되는 깊이 단서로 인해 망막의 깊이 지각에 불확실성을 초래하며, 결과적으로 눈의 피로, 두통, 복시 및 VR 멀미와 같은 시각적·인지적 후유증을 유발합니다 [1, 2]. @@ -23,11 +23,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 폭주-조절 불일치(Vergen - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[가상현실 멀미(VR sickness)]], [[헤드 마운트 디스플레이(HMD)]], [[깊이 지각(Depth perception)]], [[안구 운동 기능(Oculomotor functions)]] -- **Projects/Contexts:** [[비트 세이버를 활용한 가상현실 엑서게임 후유증 연구(Exergaming With Beat Saber: An Investigation of Virtual Reality Aftereffects)]] +- **Related Topics:** [[가상현실 멀미 (VR Sickness)|가상현실 멀미(VR sickness)]], [[헤드 마운트 디스플레이(HMD)|헤드 마운트 디스플레이(HMD)]], [[깊이 지각(Depth perception)|깊이 지각(Depth perception)]], [[안구 운동 기능(Oculomotor functions)|안구 운동 기능(Oculomotor functions)]] +- **Projects/Contexts:** [[비트 세이버를 활용한 가상현실 엑서게임 후유증 연구(Exergaming With Beat Saber_ An Investigation of Virtual Reality Aftereffects)|비트 세이버를 활용한 가상현실 엑서게임 후유증 연구(Exergaming With Beat Saber: An Investigation of Virtual Reality Aftereffects)]] - **Contradictions/Notes:** 소스에 따르면 폭주-조절 불일치가 개인의 VR 멀미를 유발하는 근본 원인인지, 혹은 단순히 멀미 증상을 더 악화시키는 복합적 요인인지는 불분명한 상태입니다 [1]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/폭주-조절 불일치(Vergence-accommodation conflict).md]] +- Raw Source: 00_Raw/2026-04-20/폭주-조절 불일치(Vergence-accommodation conflict).md --- diff --git a/01_Archive/2026-04-20/폭주-조절 충돌(Vergence-accommodation conflict).md b/01_Archive/2026-04-20/폭주-조절 충돌(Vergence-accommodation conflict).md index 5d4528da..34561ccf 100644 --- a/01_Archive/2026-04-20/폭주-조절 충돌(Vergence-accommodation conflict).md +++ b/01_Archive/2026-04-20/폭주-조절 충돌(Vergence-accommodation conflict).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-12CE66 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 폭주-조절 충돌(Vergence-accommodation conflict)" --- -# [[폭주-조절 충돌(Vergence-accommodation conflict)]] +# [[폭주-조절 충돌(Vergence-accommodation conflict)|폭주-조절 충돌(Vergence-accommodation conflict)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 폭주-조절 충돌(Vergence-accommodation conflict)은 가상현실(VR)의 헤드 마운트 디스플레이(HMD) 사용 시 발생하는 상충되는 깊이 단서로 인해 나타나는 시각적 현상입니다 [1]. 자연스러운 시각 환경에서는 가까운 물체에 초점을 맞추기 위해 폭주(Vergence)와 조절(Accommodation) 기능이 상호 피드백 루프를 통해 함께 작용하지만, HMD에서는 이 두 메커니즘이 분리(decoupled)되면서 충돌을 일으킵니다 [1]. 이 현상은 깊이 지각에 대한 불확실성을 초래하며, 가상현실 멀미나 눈의 피로와 같은 다양한 안구 운동 증상을 유발하는 요인으로 지목되고 있습니다 [1, 2]. @@ -20,11 +20,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 폭주-조절 충돌(Vergence- - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[가상현실 멀미(VR sickness)]], [[안구 운동 기능(Oculomotor functions)]], [[깊이 지각(Depth perception)]], [[헤드 마운트 디스플레이(HMD)]] -- **Projects/Contexts:** [[가상현실(VR) 경험 및 엑서게이밍(Exergaming)]] +- **Related Topics:** [[가상현실 멀미 (VR Sickness)|가상현실 멀미(VR sickness)]], [[안구 운동 기능(Oculomotor functions)|안구 운동 기능(Oculomotor functions)]], [[깊이 지각(Depth perception)|깊이 지각(Depth perception)]], [[헤드 마운트 디스플레이(HMD)|헤드 마운트 디스플레이(HMD)]] +- **Projects/Contexts:** 가상현실(VR) 경험 및 엑서게이밍(Exergaming) - **Contradictions/Notes:** 소스에 따르면 폭주-조절 충돌이 VR 멀미의 근본적인 원인인지, 혹은 기존의 멀미 증상을 심화시키는 역할만 하는 것인지에 대해서는 인과관계가 아직 불분명합니다 [2]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/폭주-조절 충돌(Vergence-accommodation conflict).md]] +- Raw Source: 00_Raw/2026-04-20/폭주-조절 충돌(Vergence-accommodation conflict).md --- diff --git a/01_Archive/2026-04-20/풀 리퀘스트 워크플로우.md b/01_Archive/2026-04-20/풀 리퀘스트 워크플로우.md index 7e257cb5..a66d458e 100644 --- a/01_Archive/2026-04-20/풀 리퀘스트 워크플로우.md +++ b/01_Archive/2026-04-20/풀 리퀘스트 워크플로우.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-9C30BC -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 풀 리퀘스트 워크플로우" --- -# [[풀 리퀘스트 워크플로우]] +# [[풀 리퀘스트 워크플로우|풀 리퀘스트 워크플로우]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 풀 리퀘스트 워크플로우(Pull Request Workflow)는 개발자가 작성한 소스 코드 변경 사항을 메인 브랜치에 병합(Merge)하기 전에 검토하고 검증하는 소프트웨어 개발 수명 주기(SDLC)의 핵심 단계입니다 [1, 2]. 현대의 풀 리퀘스트 워크플로우는 정적 애플리케이션 보안 테스트(SAST) 및 AI 기반 코드 리뷰 도구들과 긴밀하게 통합되어 작동합니다 [2, 3]. 이를 통해 코드의 품질과 보안을 자동으로 평가하고 수동 검토와 결합함으로써 리뷰 지연을 줄이고 결함이 프로덕션으로 넘어가는 것을 방지합니다 [4, 5]. @@ -23,11 +23,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 풀 리퀘스트 워크플로 - **정책 변화:** AI 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[자동화된 코드 리뷰]], [[수동 코드 리뷰]], [[SAST (정적 애플리케이션 보안 테스트)]], [[Git 훅 (Git Hooks)]] -- **Projects/Contexts:** [[DevSecOps]], [[CI/CD 파이프라인]] +- **Related Topics:** [[자동화된 코드 리뷰|자동화된 코드 리뷰]], [[수동 코드 리뷰|수동 코드 리뷰]], [[SAST (정적 애플리케이션 보안 테스트)|SAST (정적 애플리케이션 보안 테스트)]], Git 훅 (Git Hooks) +- **Projects/Contexts:** [[DevSecOps|DevSecOps]], [[CI_CD 파이프라인|CI/CD 파이프라인]] - **Contradictions/Notes:** 소스들은 AI 및 자동화 도구가 풀 리퀘스트 리뷰 주기를 단축시킨다고 주장하지만, 올바른 워크플로우 체계 없이 단순히 도구만 도입할 경우 오히려 무의미한 경고(False Positives)가 쏟아져 리뷰어의 경고 피로도(Alert Fatigue)를 높이고 리뷰 지연을 초래할 수 있다고 경고합니다 [11, 20, 21]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/풀 리퀘스트 워크플로우.md]] +- Raw Source: 00_Raw/2026-04-20/풀 리퀘스트 워크플로우.md --- diff --git a/01_Archive/2026-04-20/풀 리퀘스트(PR) 기반 보안 검토.md b/01_Archive/2026-04-20/풀 리퀘스트(PR) 기반 보안 검토.md index a738a738..9a0a0916 100644 --- a/01_Archive/2026-04-20/풀 리퀘스트(PR) 기반 보안 검토.md +++ b/01_Archive/2026-04-20/풀 리퀘스트(PR) 기반 보안 검토.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-8FBB2B -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 풀 리퀘스트(PR) 기반 보안 검토" --- -# [[풀 리퀘스트(PR) 기반 보안 검토]] +# [[풀 리퀘스트(PR) 기반 보안 검토|풀 리퀘스트(PR) 기반 보안 검토]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 풀 리퀘스트(PR) 기반 보안 검토는 소프트웨어 개발 수명 주기(SDLC)에서 코드 변경 사항이 메인 브랜치에 병합되기 전에 보안 취약점과 품질 문제를 검사하는 핵심 과정입니다 [1, 2]. 이 과정은 자동화된 정적 분석(SAST) 및 AI 도구를 통한 사전 필터링과 개발자의 수동 피어 리뷰(Peer Review)를 결합하여, 개발 속도를 저하시키지 않으면서 코드의 보안성과 유지보수성을 확보하는 것을 목표로 합니다 [3, 4]. @@ -23,11 +23,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 풀 리퀘스트(PR) 기반 - **정책 변화:** AI 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[정적 애플리케이션 보안 테스트(SAST)]], [[AI 기반 코드 리뷰]], [[시프트 레프트(Shift-Left)]], [[품질 게이트(Quality Gates)]], [[하이브리드 코드 리뷰(Hybrid Code Review)]] -- **Projects/Contexts:** [[GitHub Code Security 및 Copilot Autofix]], [[SonarQube PR 분석]], [[Snyk Code PR 통합]] +- **Related Topics:** [[정적 애플리케이션 보안 테스트(SAST)|정적 애플리케이션 보안 테스트(SAST)]], AI 기반 코드 리뷰, [[시프트 레프트(Shift-Left)|시프트 레프트(Shift-Left)]], 품질 게이트(Quality Gates), [[하이브리드 코드 리뷰 (Hybrid Code Review)|하이브리드 코드 리뷰(Hybrid Code Review)]] +- **Projects/Contexts:** GitHub Code Security 및 Copilot Autofix, SonarQube PR 분석, Snyk Code PR 통합 - **Contradictions/Notes:** 자동화된 PR 코드 검토는 속도와 확장성 측면에서 매우 우수하지만 코드의 의도나 아키텍처 맥락을 이해하지 못해 오탐(False Positive)을 유발할 수 있습니다. 따라서 도구의 결과에만 의존하기보다는 복잡한 비즈니스 로직과 보안 컨텍스트 평가는 반드시 인간의 수동 검토가 동반되어야 상호 보완적인 보안 품질을 달성할 수 있습니다 [18, 25, 26]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/풀 리퀘스트(PR) 기반 보안 검토.md]] +- Raw Source: 00_Raw/2026-04-20/풀 리퀘스트(PR) 기반 보안 검토.md --- diff --git a/01_Archive/2026-04-20/프래그먼트 바운드(Fragment-bound).md b/01_Archive/2026-04-20/프래그먼트 바운드(Fragment-bound).md index a74dedb3..de77218e 100644 --- a/01_Archive/2026-04-20/프래그먼트 바운드(Fragment-bound).md +++ b/01_Archive/2026-04-20/프래그먼트 바운드(Fragment-bound).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-8CAEFF -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 프래그먼트 바운드(Fragment-bound)" --- -# [[프래그먼트 바운드(Fragment-bound)]] +# [[프래그먼트 바운드(Fragment-bound)|프래그먼트 바운드(Fragment-bound)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 프래그먼트 바운드(Fragment-bound)는 3D 렌더링 파이프라인에서 GPU의 프래그먼트(픽셀) 연산 부하가 극심해져 전체 렌더링 성능과 프레임 레이트(FPS)를 제한하는 병목 상태를 의미합니다. 주로 화면에 그려지는 객체들이 렌더링 순서대로 정렬되지 않아 동일한 픽셀 위치에 렌더링 계산이 여러 번 중첩되는 오버드로우(Overdraw) 현상으로 인해 발생합니다. 무거운 조명 연산이 포함된 재질을 사용할 때 이 상태에 더욱 쉽게 빠지게 됩니다 [1, 2]. @@ -23,11 +23,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 프래그먼트 바운드(Frag - **정책 변화:** Graphics & Performance 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[오버드로우(Overdraw)]], [[InstancedMesh]], [[BatchedMesh]], [[프래그먼트 셰이딩(Fragment Shading)]] -- **Projects/Contexts:** [[Three.js 렌더링 성능 최적화]], [[MeshStandardMaterial 조명 연산]] +- **Related Topics:** [[오버드로우(Overdraw)|오버드로우(Overdraw)]], [[InstancedMesh|InstancedMesh]], [[BatchedMesh|BatchedMesh]], [[프래그먼트 셰이딩(Fragment Shading)|프래그먼트 셰이딩(Fragment Shading)]] +- **Projects/Contexts:** [[Three.js 렌더링 성능 최적화|Three.js 렌더링 성능 최적화]], [[MeshStandardMaterial 조명 연산|MeshStandardMaterial 조명 연산]] - **Contradictions/Notes:** 소스에 따르면 `InstancedMesh`는 CPU의 드로우 콜 병목을 해소하기 위해 도입되지만, 내부 정렬(Sorting)의 부재로 인해 오히려 GPU 측에서 프래그먼트 바운드라는 새로운 형태의 성능 병목을 유발할 수 있는 구조적 트레이드오프를 지니고 있습니다 [1, 2]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/프래그먼트 바운드(Fragment-bound).md]] +- Raw Source: 00_Raw/2026-04-20/프래그먼트 바운드(Fragment-bound).md --- diff --git a/01_Archive/2026-04-20/프래그먼트 셰이딩(Fragment Shading).md b/01_Archive/2026-04-20/프래그먼트 셰이딩(Fragment Shading).md index 7c53d55c..62bd39e7 100644 --- a/01_Archive/2026-04-20/프래그먼트 셰이딩(Fragment Shading).md +++ b/01_Archive/2026-04-20/프래그먼트 셰이딩(Fragment Shading).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-CE737D -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 프래그먼트 셰이딩(Fragment Shading)" --- -# [[프래그먼트 셰이딩(Fragment Shading)]] +# [[프래그먼트 셰이딩(Fragment Shading)|프래그먼트 셰이딩(Fragment Shading)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 프래그먼트 셰이딩(Fragment Shading)은 그래픽 렌더링 파이프라인의 후반부 단계로, 최종 색상 값을 결정하기 위해 픽셀 단위의 연산을 실행하는 과정이다 [1, 2]. 주로 텍스처 데이터 샘플링, 픽셀 단위 조명(per-pixel lighting), 알파(투명도) 값을 계산하여 표면의 디테일을 구현하는 역할을 수행한다 [1, 3, 4]. 화면에 보이는 픽셀에 대해 계산을 수행하므로, 픽셀이 중첩되어 여러 번 렌더링되는 오버드로우(Overdraw)가 발생하거나 복잡한 셰이더를 사용할 경우 GPU 성능 저하 및 프레임 지연의 주요 원인이 된다 [1, 2]. @@ -29,11 +29,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 프래그먼트 셰이딩(Frag - **정책 변화:** Graphics & Performance 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Overdraw]], [[Vertex Shader]], [[Level of Detail (LOD)]], [[Physically Based Rendering (PBR)]] -- **Projects/Contexts:** [[Three.js]], [[WebGL]] +- **Related Topics:** [[Overdraw|Overdraw]], [[Vertex Shader|Vertex Shader]], [[Level of Detail (LOD)|Level of Detail (LOD)]], Physically Based Rendering (PBR) +- **Projects/Contexts:** [[Three.js|Three.js]], [[WebGL|WebGL]] - **Contradictions/Notes:** 시각적인 현실감을 제공하는 PBR 모델의 재질은 사실적인 빛 반사를 구현하지만 프래그먼트 셰이더에서 수많은 연산과 텍스처 샘플링을 요구한다. 따라서 내장 GPU(iGPU)와 같은 저사양 하드웨어 환경에서는 성능을 크게 저하시키며, 오히려 연산량이 적은 Phong 모델이나 플랫 셰이딩 재질을 사용하는 것이 높은 프레임 레이트 유지를 위해 필수적이라고 소스는 설명한다 [1, 10, 11]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/프래그먼트 셰이딩(Fragment Shading).md]] +- Raw Source: 00_Raw/2026-04-20/프래그먼트 셰이딩(Fragment Shading).md --- diff --git a/01_Archive/2026-04-20/프론트엔드 및 Node.js 개발 워크플로우.md b/01_Archive/2026-04-20/프론트엔드 및 Node.js 개발 워크플로우.md index d4120377..ea34adf4 100644 --- a/01_Archive/2026-04-20/프론트엔드 및 Node.js 개발 워크플로우.md +++ b/01_Archive/2026-04-20/프론트엔드 및 Node.js 개발 워크플로우.md @@ -1,4 +1,4 @@ -# [[프론트엔드 및 Node.js 개발 워크플로우]] +# [[프론트엔드 및 Node.js 개발 워크플로우|프론트엔드 및 Node.js 개발 워크플로우]] ## 📌 Brief Summary 프론트엔드 및 Node.js 개발 워크플로우는 소스 코드의 품질, 일관성, 그리고 보안을 자동화된 방식으로 유지하기 위해 일련의 도구들을 파이프라인에 결합하는 과정입니다. 주축이 되는 도구로는 코드 에러를 정적으로 분석하는 ESLint와 코드 스타일을 자동으로 정렬해주는 Prettier가 있으며, 이를 Git 훅(Git Hooks) 관리 도구인 Husky와 변경된 파일만 검사하는 lint-staged를 통해 커밋 전에 강제합니다. 최근에는 이러한 파이프라인과 IDE에 AI 기반의 정적 애플리케이션 보안 테스트(SAST)를 결합하여 취약점을 조기에 탐지하고 자동 수정하는 체계가 필수적으로 자리 잡고 있습니다. @@ -20,8 +20,8 @@ 개발 워크플로우를 구성하는 도구 자체의 보안 검증 또한 중요합니다. 실제로 워크플로우 구축 시 가장 흔하게 사용되는 `eslint-config-prettier` 패키지가 2025년에 공급망 공격(CVE-2025-54313)의 타겟이 된 사례가 있습니다 [30-32]. 관리자의 토큰 탈취를 통해 배포된 악성 버전은 `npm install` 실행 시 윈도우(Windows) 개발자 머신에 원격 코드 실행(RCE)을 가능하게 하는 악성 DLL을 드롭하도록 조작되어 있어, 코드 검증 도구와 서드파티 패키지 사용에 대한 지속적인 보안 및 의존성 관리가 필수적임을 시사합니다 [31-33]. ## 🔗 Knowledge Connections -- **Related Topics:** [[ESLint]], [[Prettier]], [[Husky]], [[lint-staged]], [[정적 애플리케이션 보안 테스트 (SAST)]], [[공급망 공격 (Supply Chain Attack)]] -- **Projects/Contexts:** [[React 및 Next.js 개발 환경]], [[Turborepo 기반 모노레포 워크플로우]] +- **Related Topics:** [[ESLint|ESLint]], [[Prettier|Prettier]], [[Husky|Husky]], [[lint-staged|lint-staged]], [[정적 애플리케이션 보안 테스트 (SAST)|정적 애플리케이션 보안 테스트 (SAST)]], [[공급망 공격 (Supply Chain Attack)|공급망 공격 (Supply Chain Attack)]] +- **Projects/Contexts:** [[React 및 Next.js 개발 환경|React 및 Next.js 개발 환경]], [[Turborepo 기반 모노레포 워크플로우|Turborepo 기반 모노레포 워크플로우]] - **Contradictions/Notes:** ESLint와 Prettier를 결합할 때, `eslint-plugin-prettier`를 사용하여 Prettier를 ESLint 규칙의 일부로 실행하는 방식이 존재하지만, Prettier 공식 문서 및 실무 환경에서는 성능 저하 문제와 에디터 내 과도한 경고(빨간 밑줄) 발생 등의 피로도 문제로 인해 `eslint-config-prettier`를 활용해 역할(규칙 검사는 ESLint, 포맷팅은 Prettier)을 명확히 분리하는 것을 가장 권장합니다 [5, 34, 35]. --- diff --git a/01_Archive/2026-04-20/프론트엔드 및 Nodejs 개발 워크플로우.md b/01_Archive/2026-04-20/프론트엔드 및 Nodejs 개발 워크플로우.md index 22741ec7..5f5cdb20 100644 --- a/01_Archive/2026-04-20/프론트엔드 및 Nodejs 개발 워크플로우.md +++ b/01_Archive/2026-04-20/프론트엔드 및 Nodejs 개발 워크플로우.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-D024EA -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 프론트엔드 및 Nodejs 개발 워크플로우" --- -# [[프론트엔드 및 Nodejs 개발 워크플로우]] +# [[프론트엔드 및 Nodejs 개발 워크플로우|프론트엔드 및 Nodejs 개발 워크플로우]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 프론트엔드 및 Node.js 개발 워크플로우는 소스 코드의 품질, 일관성, 그리고 보안을 자동화된 방식으로 유지하기 위해 일련의 도구들을 파이프라인에 결합하는 과정입니다. 주축이 되는 도구로는 코드 에러를 정적으로 분석하는 ESLint와 코드 스타일을 자동으로 정렬해주는 Prettier가 있으며, 이를 Git 훅(Git Hooks) 관리 도구인 Husky와 변경된 파일만 검사하는 lint-staged를 통해 커밋 전에 강제합니다. 최근에는 이러한 파이프라인과 IDE에 AI 기반의 정적 애플리케이션 보안 테스트(SAST)를 결합하여 취약점을 조기에 탐지하고 자동 수정하는 체계가 필수적으로 자리 잡고 있습니다. @@ -33,11 +33,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 프론트엔드 및 Nodejs 개 - **정책 변화:** AI 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[ESLint]], [[Prettier]], [[Husky]], [[lint-staged]], [[정적 애플리케이션 보안 테스트 (SAST)]], [[공급망 공격 (Supply Chain Attack)]] -- **Projects/Contexts:** [[React 및 Next.js 개발 환경]], [[Turborepo 기반 모노레포 워크플로우]] +- **Related Topics:** [[ESLint|ESLint]], [[Prettier|Prettier]], [[Husky|Husky]], [[lint-staged|lint-staged]], [[정적 애플리케이션 보안 테스트 (SAST)|정적 애플리케이션 보안 테스트 (SAST)]], [[공급망 공격 (Supply Chain Attack)|공급망 공격 (Supply Chain Attack)]] +- **Projects/Contexts:** [[React 및 Next.js 개발 환경|React 및 Next.js 개발 환경]], [[Turborepo 기반 모노레포 워크플로우|Turborepo 기반 모노레포 워크플로우]] - **Contradictions/Notes:** ESLint와 Prettier를 결합할 때, `eslint-plugin-prettier`를 사용하여 Prettier를 ESLint 규칙의 일부로 실행하는 방식이 존재하지만, Prettier 공식 문서 및 실무 환경에서는 성능 저하 문제와 에디터 내 과도한 경고(빨간 밑줄) 발생 등의 피로도 문제로 인해 `eslint-config-prettier`를 활용해 역할(규칙 검사는 ESLint, 포맷팅은 Prettier)을 명확히 분리하는 것을 가장 권장합니다 [5, 34, 35]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/프론트엔드 및 Node.js 개발 워크플로우.md]] +- Raw Source: 00_Raw/2026-04-20/프론트엔드 및 Node.js 개발 워크플로우.md --- diff --git a/01_Archive/2026-04-20/프론트엔드 및 모노레포(Monorepo) 개발 환경 설정.md b/01_Archive/2026-04-20/프론트엔드 및 모노레포(Monorepo) 개발 환경 설정.md index 935c1934..89e9df36 100644 --- a/01_Archive/2026-04-20/프론트엔드 및 모노레포(Monorepo) 개발 환경 설정.md +++ b/01_Archive/2026-04-20/프론트엔드 및 모노레포(Monorepo) 개발 환경 설정.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-F3FA69 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 프론트엔드 및 모노레포(Monorepo) 개발 환경 설정" --- -# [[프론트엔드 및 모노레포(Monorepo) 개발 환경 설정]] +# [[프론트엔드 및 모노레포(Monorepo) 개발 환경 설정|프론트엔드 및 모노레포(Monorepo) 개발 환경 설정]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 프론트엔드 및 모노레포(Monorepo) 개발 환경 설정은 대규모 프로젝트에서 코드 품질과 스타일의 일관성을 유지하고 중복된 설정을 줄이기 위한 핵심 과정입니다. Turborepo와 같은 모노레포 환경에서는 여러 애플리케이션과 패키지가 혼재하므로 중앙 집중식 ESLint 및 Prettier 설정 패키지를 구축하는 것이 권장됩니다 [1, 2]. 여기에 Husky와 lint-staged를 결합하여 변경된 파일에 대해서만 린팅(linting)과 포맷팅(formatting)을 수행하도록 오케스트레이션(orchestration)함으로써 개발자의 생산성과 커밋 속도를 크게 향상시킬 수 있습니다 [3, 4]. @@ -38,11 +38,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 프론트엔드 및 모노레 - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[Turborepo]], [[ESLint]], [[Prettier]], [[Husky]], [[lint-staged]] -- **Projects/Contexts:** [[Next.js 애플리케이션 및 내부 라이브러리 패키지 관리]] +- **Related Topics:** [[Turborepo|Turborepo]], [[ESLint|ESLint]], [[Prettier|Prettier]], [[Husky|Husky]], [[lint-staged|lint-staged]] +- **Projects/Contexts:** Next.js 애플리케이션 및 내부 라이브러리 패키지 관리 - **Contradictions/Notes:** 모노레포에서 `lint-staged`의 공식 권장 사항은 각 패키지별로 별도의 설정 파일을 두고 가장 가까운 구성 파일이 적용되도록 하는 것이지만 [12, 13], Turborepo를 활용하는 현대적인 접근 방식에서는 루트 오케스트레이션 구성 파일(`eslint.config.mjs`)을 통해 파일 패턴을 각 프리셋에 중앙에서 매핑하는 방식이 더 효율적인 해결책으로 제시됩니다 [9, 10]. 또한, ESLint와 Prettier를 함께 사용할 경우 포맷팅 충돌을 방지하기 위해 반드시 `eslint-config-prettier`를 설정 배열의 마지막에 위치시켜야 합니다 [14]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/프론트엔드 및 모노레포(Monorepo) 개발 환경 설정.md]] +- Raw Source: 00_Raw/2026-04-20/프론트엔드 및 모노레포(Monorepo) 개발 환경 설정.md --- diff --git a/01_Archive/2026-04-20/프론트엔드 컴포넌트 구조화.md b/01_Archive/2026-04-20/프론트엔드 컴포넌트 구조화.md index 00543dca..3ae0e0cd 100644 --- a/01_Archive/2026-04-20/프론트엔드 컴포넌트 구조화.md +++ b/01_Archive/2026-04-20/프론트엔드 컴포넌트 구조화.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-353103 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 프론트엔드 컴포넌트 구조화" --- -# [[프론트엔드 컴포넌트 구조화]] +# [[프론트엔드 컴포넌트 구조화|프론트엔드 컴포넌트 구조화]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 프론트엔드 컴포넌트 구조화는 웹 개발에서 복잡성을 줄이고 유지보수성을 높이기 위해 기능과 역할 단위로 코드를 분리하고 조직하는 방법론입니다 [1, 2]. 초기에는 HTML, CSS, JavaScript라는 언어적 역할에 따라 분리되었으나, 특정 기능과 UI 요소를 하나의 단위로 묶는 컴포넌트 기반 아키텍처로 진화했습니다 [3]. 프로젝트의 규모가 커짐에 따라 발생하는 컴포넌트 간의 높은 결합도를 해결하기 위해, 관심사의 분리(SoC) 원칙을 다시 적용하여 Feature-Sliced Design(FSD)과 같이 기능 중심으로 구조를 세분화하는 방향으로 발전하고 있습니다 [2, 4]. @@ -23,11 +23,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 프론트엔드 컴포넌트 - **정책 변화:** Design & Experience 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[관심사의 분리]], [[Feature-Sliced Design]], [[단일 책임 원칙 (SRP)]], [[Atomic Design Pattern]] -- **Projects/Contexts:** [[대규모 프론트엔드 웹 프로젝트 폴더 구조화]], [[컴포넌트 기반 웹 프레임워크 아키텍처 설계]] +- **Related Topics:** 관심사의 분리, [[Feature-Sliced Design|Feature-Sliced Design]], [[단일 책임 원칙 (SRP)|단일 책임 원칙 (SRP)]], [[Atomic Design Pattern|Atomic Design Pattern]] +- **Projects/Contexts:** [[대규모 프론트엔드 웹 프로젝트 폴더 구조화|대규모 프론트엔드 웹 프로젝트 폴더 구조화]], [[컴포넌트 기반 웹 프레임워크 아키텍처 설계|컴포넌트 기반 웹 프레임워크 아키텍처 설계]] - **Contradictions/Notes:** 초기 웹 개발은 HTML, CSS, JS라는 역할 중심의 계층 구조로 이루어졌으나, 컴포넌트 패러다임의 등장으로 기능 중심의 융합 구조로 변하였습니다 [1, 3]. 하지만 컴포넌트 비대화와 결합도 증가라는 복잡성 문제가 다시 발생함에 따라, 현대에는 컴포넌트 내외부를 다시 세분화된 역할과 기능(Feature) 단위로 분리하는 FSD 아키텍처 구조로 나아가는 진화 흐름을 보입니다 [2, 4, 7]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/프론트엔드 컴포넌트 구조화.md]] +- Raw Source: 00_Raw/2026-04-20/프론트엔드 컴포넌트 구조화.md --- diff --git a/01_Archive/2026-04-20/프론트엔드 컴포넌트 설계.md b/01_Archive/2026-04-20/프론트엔드 컴포넌트 설계.md index b97ee8da..4270e77c 100644 --- a/01_Archive/2026-04-20/프론트엔드 컴포넌트 설계.md +++ b/01_Archive/2026-04-20/프론트엔드 컴포넌트 설계.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-F2362F -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 프론트엔드 컴포넌트 설계" --- -# [[프론트엔드 컴포넌트 설계]] +# [[프론트엔드 컴포넌트 설계|프론트엔드 컴포넌트 설계]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 프론트엔드 컴포넌트 설계는 웹 개발에서 특정 기능이나 UI 요소를 구현하기 위해 HTML 구조, CSS 스타일, JavaScript 동작을 하나의 기능적 단위로 묶어 다루는 개발 방식입니다 [1]. 기존의 역할 중심 분리에서 기능 중심의 모듈화로 패러다임이 전환되면서 코드의 재사용성을 높이고 독립적인 테스트를 가능하게 했습니다 [1, 2]. 하지만 프로젝트 규모가 커짐에 따라 발생하는 컴포넌트의 비대화와 강한 결합도를 해결하기 위해, 다시 계층을 나누고 관심사를 분리하는 고도화된 설계 원칙이 요구됩니다 [3, 4]. @@ -34,11 +34,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 프론트엔드 컴포넌트 - **정책 변화:** Design & Experience 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[관심사의 분리 (SoC)]], [[단일 책임 원칙 (SRP)]], [[아토믹 디자인 패턴 (Atomic Design Pattern)]], [[단방향 데이터 흐름]], [[FSD (Feature-Sliced Design)]] -- **Projects/Contexts:** [[대규모 프론트엔드 애플리케이션 아키텍처 구축 및 리팩토링]] +- **Related Topics:** [[관심사의 분리 (SoC)|관심사의 분리 (SoC)]], [[단일 책임 원칙 (SRP)|단일 책임 원칙 (SRP)]], 아토믹 디자인 패턴 (Atomic Design Pattern), 단방향 데이터 흐름, [[FSD (Feature-Sliced Design)|FSD (Feature-Sliced Design)]] +- **Projects/Contexts:** 대규모 프론트엔드 애플리케이션 아키텍처 구축 및 리팩토링 - **Contradictions/Notes:** 소스에서는 시각적 형태가 비슷하다고 무작정 동일한 컴포넌트로 묶는 것을 프론트엔드 개발자들이 흔히 하는 실수로 지적합니다. 데이터(도메인)가 다를 경우 결합도가 급증하여 오히려 유지보수성이 저해되므로, UI 컴포넌트와 도메인 컴포넌트를 명확히 분리해야 한다고 강조합니다. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/프론트엔드 컴포넌트 설계.md]] +- Raw Source: 00_Raw/2026-04-20/프론트엔드 컴포넌트 설계.md --- diff --git a/01_Archive/2026-04-20/플레이어 경험 디자인 (Player Experience Design).md b/01_Archive/2026-04-20/플레이어 경험 디자인 (Player Experience Design).md index 42764780..7407ab8b 100644 --- a/01_Archive/2026-04-20/플레이어 경험 디자인 (Player Experience Design).md +++ b/01_Archive/2026-04-20/플레이어 경험 디자인 (Player Experience Design).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-216B69 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 플레이어 경험 디자인 (Player Experience Design)" --- -# [[플레이어 경험 디자인 (Player Experience Design)]] +# [[플레이어 경험 디자인 (Player Experience Design)|플레이어 경험 디자인 (Player Experience Design)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - 플레이어 경험 디자인 ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/플레이어 경험 디자인 (Player Experience Design).md]] +- Raw Source: 00_Raw/2026-04-20/플레이어 경험 디자인 (Player Experience Design).md --- diff --git a/01_Archive/2026-04-20/핀테크의 실시간 사기 탐지.md b/01_Archive/2026-04-20/핀테크의 실시간 사기 탐지.md index ab8da5c7..c0790287 100644 --- a/01_Archive/2026-04-20/핀테크의 실시간 사기 탐지.md +++ b/01_Archive/2026-04-20/핀테크의 실시간 사기 탐지.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-7428BF -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 핀테크의 실시간 사기 탐지" --- -# [[핀테크의 실시간 사기 탐지]] +# [[핀테크의 실시간 사기 탐지|핀테크의 실시간 사기 탐지]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 핀테크의 실시간 사기 탐지는 금융 거래와 같은 데이터가 발생한 즉시 이를 처리하여 실각적인 통찰력과 조치를 취할 수 있게 하는 필수적인 기능입니다 [1]. 이 시스템은 전통적인 일괄 처리(batch processing)가 아닌 실시간 데이터 스트리밍과 이벤트 중심 아키텍처(Event-driven Architecture)를 기반으로 작동합니다 [1, 2]. 이를 통해 핀테크 기업은 오래된 정보에 의존하여 발생하는 경쟁력 손실을 방지하고 즉각적으로 사기 행위에 대응할 수 있습니다 [1]. @@ -22,11 +22,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 핀테크의 실시간 사기 - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[실시간 데이터 스트리밍(Real-time Data Streaming)]], [[이벤트 중심 아키텍처(Event-Driven Architecture)]], [[Apache Kafka]], [[AWS Kinesis]] -- **Projects/Contexts:** [[현대적 데이터 엔지니어링 파이프라인 구축 맥락(Modern Data Engineering)]] +- **Related Topics:** 실시간 데이터 스트리밍(Real-time Data Streaming), 이벤트 중심 아키텍처(Event-Driven Architecture), Apache Kafka, AWS Kinesis +- **Projects/Contexts:** 현대적 데이터 엔지니어링 파이프라인 구축 맥락(Modern Data Engineering) - **Contradictions/Notes:** 특정 사기 탐지 알고리즘이나 모델의 구체적인 구현 방법에 대해서는 소스에 관련 정보가 부족합니다. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/핀테크의 실시간 사기 탐지.md]] +- Raw Source: 00_Raw/2026-04-20/핀테크의 실시간 사기 탐지.md --- diff --git a/01_Archive/2026-04-20/하이브리드 검색 (Hybrid Search).md b/01_Archive/2026-04-20/하이브리드 검색 (Hybrid Search).md index 65cb2b30..56329540 100644 --- a/01_Archive/2026-04-20/하이브리드 검색 (Hybrid Search).md +++ b/01_Archive/2026-04-20/하이브리드 검색 (Hybrid Search).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-F7F96B -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 하이브리드 검색 (Hybrid Search)" --- -# [[하이브리드 검색 (Hybrid Search)]] +# [[하이브리드 검색 (Hybrid Search)|하이브리드 검색 (Hybrid Search)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - 하이브리드 검색 (Hybrid ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/하이브리드 검색 (Hybrid Search).md]] +- Raw Source: 00_Raw/2026-04-20/하이브리드 검색 (Hybrid Search).md --- diff --git a/01_Archive/2026-04-20/하이브리드 코드 리뷰 (Hybrid Code Review).md b/01_Archive/2026-04-20/하이브리드 코드 리뷰 (Hybrid Code Review).md index 2c60cc78..5ecdf7a7 100644 --- a/01_Archive/2026-04-20/하이브리드 코드 리뷰 (Hybrid Code Review).md +++ b/01_Archive/2026-04-20/하이브리드 코드 리뷰 (Hybrid Code Review).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-4CD9A4 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 하이브리드 코드 리뷰 (Hybrid Code Review)" --- -# [[하이브리드 코드 리뷰 (Hybrid Code Review)]] +# [[하이브리드 코드 리뷰 (Hybrid Code Review)|하이브리드 코드 리뷰 (Hybrid Code Review)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 하이브리드 코드 리뷰는 자동화된 정적 분석 및 AI 도구 스캔과 사람(개발자)에 의한 수동 코드 리뷰를 결합한 접근 방식입니다 [1]. 자동화 도구를 통해 구문 오류나 알려진 보안 취약점을 빠르고 일관되게 찾아내는 동시에, 복잡한 비즈니스 로직, 아키텍처 설계 및 맥락 판단은 인간의 전문성에 맡깁니다 [1, 2]. 두 방식의 장점을 상호 보완적으로 활용하여 릴리스 속도를 높이면서도 코드의 품질과 보안을 극대화하는 현대적인 소프트웨어 개발 워크플로우입니다 [1, 3, 4]. @@ -34,11 +34,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 하이브리드 코드 리뷰 - **정책 변화:** AI 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[수동 코드 리뷰 (Manual Code Review)]], [[자동화된 코드 리뷰 (Automated Code Review)]], [[정적 애플리케이션 보안 테스트 (SAST)]], [[소프트웨어 구성 분석 (SCA)]] -- **Projects/Contexts:** [[지속적 통합/지속적 배포 (CI/CD) 파이프라인]], [[Pull Request (PR) 승인 워크플로우]] +- **Related Topics:** [[수동 코드 리뷰 (Manual Code Review)|수동 코드 리뷰 (Manual Code Review)]], 자동화된 코드 리뷰 (Automated Code Review), [[정적 애플리케이션 보안 테스트 (SAST)|정적 애플리케이션 보안 테스트 (SAST)]], [[소프트웨어 구성 분석(SCA)|소프트웨어 구성 분석 (SCA)]] +- **Projects/Contexts:** 지속적 통합/지속적 배포 (CI/CD) 파이프라인, Pull Request (PR) 승인 워크플로우 - **Contradictions/Notes:** 소스는 수동 리뷰와 자동화 리뷰 중 어느 하나가 다른 하나를 완벽히 대체할 수 없음을 강조합니다. 자동화 도구(AI 포함)는 속도와 확장성이 뛰어나나 비즈니스 로직과 설계의 맥락을 파악하지 못해 한계(Context Blindness)를 보이며, 반대로 사람은 피로도와 비용 문제로 모든 코드를 완벽히 리뷰할 수 없습니다. 따라서 양쪽을 결합하는 하이브리드 접근이 보안과 품질 유지의 핵심 타협점으로 꼽힙니다 [1, 8, 16, 17]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/하이브리드 코드 리뷰 (Hybrid Code Review).md]] +- Raw Source: 00_Raw/2026-04-20/하이브리드 코드 리뷰 (Hybrid Code Review).md --- diff --git a/01_Archive/2026-04-20/하이브리드 코드 리뷰.md b/01_Archive/2026-04-20/하이브리드 코드 리뷰.md index 2096d982..2345fead 100644 --- a/01_Archive/2026-04-20/하이브리드 코드 리뷰.md +++ b/01_Archive/2026-04-20/하이브리드 코드 리뷰.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-F958B3 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 하이브리드 코드 리뷰" --- -# [[하이브리드 코드 리뷰]] +# [[하이브리드 코드 리뷰|하이브리드 코드 리뷰]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 하이브리드 코드 리뷰는 인공지능(AI) 및 자동화 도구의 처리 속도와 인간 개발자의 깊은 통찰력을 결합한 최적의 코드 리뷰 모델입니다 [1]. 자동화 도구가 반복적인 구문 검사와 알려진 취약점을 신속하고 일관되게 찾아내는 동안, 인간 리뷰어는 도구가 파악할 수 없는 아키텍처의 트레이드오프, 복잡한 비즈니스 로직 및 보안 컨텍스트에 집중합니다 [1-3]. 두 방식의 단점을 상호 보완함으로써 개발 속도를 늦추지 않으면서도 소프트웨어의 보안과 코드 품질을 극대화하는 것이 이 접근법의 핵심입니다 [1, 4]. @@ -40,11 +40,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 하이브리드 코드 리뷰" - **정책 변화:** AI 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[수동 코드 리뷰]], [[자동화된 코드 리뷰]], [[SAST (Static Application Security Testing)]] -- **Projects/Contexts:** [[CI/CD 파이프라인]], [[순차적 게이트 아키텍처]] +- **Related Topics:** [[수동 코드 리뷰|수동 코드 리뷰]], [[자동화된 코드 리뷰|자동화된 코드 리뷰]], [[SAST (Static Application Security Testing)|SAST (Static Application Security Testing)]] +- **Projects/Contexts:** [[CI_CD 파이프라인|CI/CD 파이프라인]], [[순차적 게이트 아키텍처|순차적 게이트 아키텍처]] - **Contradictions/Notes:** 자동화 도구는 속도와 확장성 측면에서 훌륭하지만 비즈니스 로직과 의도를 파악하는 "문맥맹(Context Blindness)"의 한계가 있어 30~60%의 높은 오탐지율을 발생시키거나 특정 취약점(예: 신종 논리 공격)을 완전히 놓칠 수 있습니다. 따라서 오직 자동화에만 의존하는 것은 위험하며, 인간의 문맥 이해를 결합한 하이브리드 접근이 필수적이라고 소스들은 공통적으로 지적합니다 [2, 14]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/하이브리드 코드 리뷰.md]] +- Raw Source: 00_Raw/2026-04-20/하이브리드 코드 리뷰.md --- diff --git a/01_Archive/2026-04-20/할당 실패(Allocation Failure).md b/01_Archive/2026-04-20/할당 실패(Allocation Failure).md index fe25cd28..9af6568b 100644 --- a/01_Archive/2026-04-20/할당 실패(Allocation Failure).md +++ b/01_Archive/2026-04-20/할당 실패(Allocation Failure).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-32A771 -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 할당 실패(Allocation Failure)" --- -# [[할당 실패(Allocation Failure)]] +# [[할당 실패(Allocation Failure)|할당 실패(Allocation Failure)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 할당 실패(Allocation Failure)는 애플리케이션이 새로운 객체를 생성하기 위해 메모리를 요청했으나, 현재의 메모리 공간(주로 New Space나 Java 객체 힙)에 연속된 여유 메모리가 충분하지 않을 때 발생하는 이벤트이다 [1, 2]. 이 실패 현상은 시스템이 메모리 요청을 충족시키기 위해 가비지 컬렉션(GC)을 강제로 실행하도록 만드는 가장 주요한 트리거(trigger) 역할을 한다 [1, 3]. V8 엔진이나 Java 가상 머신(JVM) 등에서 공통적으로 발생하며, 할당 실패가 감지되면 엔진은 즉시 Scavenge(마이너 GC) 또는 전역 GC 사이클을 시작하여 메모리를 확보한다 [4, 5]. @@ -27,11 +27,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 할당 실패(Allocation Failu - **정책 변화:** AI 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** `[[가비지 컬렉션(Garbage Collection)]]`, `[[Scavenge(마이너 GC)]]`, `[[New Space(Young Generation)]]` -- **Projects/Contexts:** `[[V8 자바스크립트 엔진의 메모리 관리 메커니즘]]`, `[[IBM Java 가상 머신(JVM)의 가비지 컬렉션 로깅 분석]]` +- **Related Topics:** `[[가비지 컬렉션(Garbage Collection)|가비지 컬렉션(Garbage Collection)]]`, `Scavenge(마이너 GC)`, `[[New Space(Young Generation)|New Space(Young Generation)]]` +- **Projects/Contexts:** `V8 자바스크립트 엔진의 메모리 관리 메커니즘`, `IBM Java 가상 머신(JVM)의 가비지 컬렉션 로깅 분석` - **Contradictions/Notes:** 소스 간의 모순점은 발견되지 않았으며, 할당 실패는 V8 엔진과 Java JVM 환경 모두에서 연속된 여유 메모리가 부족할 때 가비지 컬렉션을 즉각적으로 유발하는 동일한 트리거 원리로 일관되게 설명되고 있다. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/할당 실패(Allocation Failure).md]] +- Raw Source: 00_Raw/2026-04-20/할당 실패(Allocation Failure).md --- diff --git a/01_Archive/2026-04-20/할당 타임라인(Allocation Timeline).md b/01_Archive/2026-04-20/할당 타임라인(Allocation Timeline).md index 14b4c278..57960cf3 100644 --- a/01_Archive/2026-04-20/할당 타임라인(Allocation Timeline).md +++ b/01_Archive/2026-04-20/할당 타임라인(Allocation Timeline).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-1A08DE -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 할당 타임라인(Allocation Timeline)" --- -# [[할당 타임라인(Allocation Timeline)]] +# [[할당 타임라인(Allocation Timeline)|할당 타임라인(Allocation Timeline)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 할당 타임라인(Allocation Timeline)은 힙 프로파일러의 상세한 스냅샷 정보와 타임라인 패널의 추적 기능을 결합한 메모리 프로파일링 도구입니다 [1, 2]. 이 도구는 녹화 기간 동안 주기적으로 힙 스냅샷을 캡처하여 객체 할당과 가비지 컬렉션(GC) 이후의 생존 여부를 시각적으로 보여줍니다 [3, 4]. 주로 메모리에 계속 남아 누수를 일으키는 객체를 찾고, 해당 객체가 할당된 정확한 스택 트레이스를 식별하는 데 사용됩니다 [1, 2, 5]. @@ -33,11 +33,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 할당 타임라인(Allocation - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[힙 스냅샷(Heap Snapshot)]], [[가비지 컬렉션(Garbage Collection)]], [[메모리 누수(Memory Leak)]] -- **Projects/Contexts:** [[Chrome DevTools]], [[Microsoft Edge DevTools]] +- **Related Topics:** [[힙 스냅샷(Heap Snapshot)|힙 스냅샷(Heap Snapshot)]], [[가비지 컬렉션(Garbage Collection)|가비지 컬렉션(Garbage Collection)]], [[메모리 누수(Memory Leak)|메모리 누수(Memory Leak)]] +- **Projects/Contexts:** [[Chrome DevTools|Chrome DevTools]], [[Microsoft Edge DevTools|Microsoft Edge DevTools]] - **Contradictions/Notes:** 소스 간의 모순된 내용은 없으며, Chrome DevTools와 Microsoft Edge DevTools 등 Chromium 기반 브라우저 문서들에서 파란색/회색 막대의 의미와 도구의 작동 방식(50ms 주기의 스냅샷 등)을 모두 동일하게 설명하고 있습니다 [3, 4, 7, 8]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/할당 타임라인(Allocation Timeline).md]] +- Raw Source: 00_Raw/2026-04-20/할당 타임라인(Allocation Timeline).md --- diff --git a/01_Archive/2026-04-20/함수 호출 (Function Calling).md b/01_Archive/2026-04-20/함수 호출 (Function Calling).md index 38b59906..f36e88ac 100644 --- a/01_Archive/2026-04-20/함수 호출 (Function Calling).md +++ b/01_Archive/2026-04-20/함수 호출 (Function Calling).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-34CE7C -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 함수 호출 (Function Calling)" --- -# [[함수 호출 (Function Calling)]] +# [[함수 호출 (Function Calling)|함수 호출 (Function Calling)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - 함수 호출 (Function Callin ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/함수 호출 (Function Calling).md]] +- Raw Source: 00_Raw/2026-04-20/함수 호출 (Function Calling).md --- diff --git a/01_Archive/2026-04-20/행동 경제학의 인센티브 구조 설계.md b/01_Archive/2026-04-20/행동 경제학의 인센티브 구조 설계.md index a56cd724..a00acac3 100644 --- a/01_Archive/2026-04-20/행동 경제학의 인센티브 구조 설계.md +++ b/01_Archive/2026-04-20/행동 경제학의 인센티브 구조 설계.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-8FE0F9 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 행동 경제학의 인센티브 구조 설계" --- -# [[행동 경제학의 인센티브 구조 설계]] +# [[행동 경제학의 인센티브 구조 설계|행동 경제학의 인센티브 구조 설계]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - 행동 경제학의 인센티 ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/행동 경제학의 인센티브 구조 설계.md]] +- Raw Source: 00_Raw/2026-04-20/행동 경제학의 인센티브 구조 설계.md --- diff --git a/01_Archive/2026-04-20/행동 경제학의 학습 이론.md b/01_Archive/2026-04-20/행동 경제학의 학습 이론.md index 9491fd8e..31d1503a 100644 --- a/01_Archive/2026-04-20/행동 경제학의 학습 이론.md +++ b/01_Archive/2026-04-20/행동 경제학의 학습 이론.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-151F07 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 행동 경제학의 학습 이론" --- -# [[행동 경제학의 학습 이론]] +# [[행동 경제학의 학습 이론|행동 경제학의 학습 이론]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - 행동 경제학의 학습 이 ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/행동 경제학의 학습 이론.md]] +- Raw Source: 00_Raw/2026-04-20/행동 경제학의 학습 이론.md --- diff --git a/01_Archive/2026-04-20/행동 수정 기법.md b/01_Archive/2026-04-20/행동 수정 기법.md index f53e7354..774858dd 100644 --- a/01_Archive/2026-04-20/행동 수정 기법.md +++ b/01_Archive/2026-04-20/행동 수정 기법.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-C66F3C -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 행동 수정 기법" --- -# [[행동 수정 기법]] +# [[행동 수정 기법|행동 수정 기법]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - 행동 수정 기법" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/행동 수정 기법.md]] +- Raw Source: 00_Raw/2026-04-20/행동 수정 기법.md --- diff --git a/01_Archive/2026-04-20/행동 치료 및 인지 행동 치료 (CBT).md b/01_Archive/2026-04-20/행동 치료 및 인지 행동 치료 (CBT).md index 8e0417ea..8bd3edca 100644 --- a/01_Archive/2026-04-20/행동 치료 및 인지 행동 치료 (CBT).md +++ b/01_Archive/2026-04-20/행동 치료 및 인지 행동 치료 (CBT).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-121D57 -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 행동 치료 및 인지 행동 치료 (CBT)" --- -# [[행동 치료 및 인지 행동 치료 (CBT)]] +# [[행동 치료 및 인지 행동 치료 (CBT)|행동 치료 및 인지 행동 치료 (CBT)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - 행동 치료 및 인지 행 ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/행동 치료 및 인지 행동 치료 (CBT).md]] +- Raw Source: 00_Raw/2026-04-20/행동 치료 및 인지 행동 치료 (CBT).md --- diff --git a/01_Archive/2026-04-20/행동주의 심리학 (Behaviorism).md b/01_Archive/2026-04-20/행동주의 심리학 (Behaviorism).md index 6fb7ac13..51272e61 100644 --- a/01_Archive/2026-04-20/행동주의 심리학 (Behaviorism).md +++ b/01_Archive/2026-04-20/행동주의 심리학 (Behaviorism).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-EA760E -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 행동주의 심리학 (Behaviorism)" --- -# [[행동주의 심리학 (Behaviorism)]] +# [[행동주의 심리학 (Behaviorism)|행동주의 심리학 (Behaviorism)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - 행동주의 심리학 (Behavi ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/행동주의 심리학 (Behaviorism).md]] +- Raw Source: 00_Raw/2026-04-20/행동주의 심리학 (Behaviorism).md --- diff --git a/01_Archive/2026-04-20/행동주의 심리학.md b/01_Archive/2026-04-20/행동주의 심리학.md index dd67f4f1..ff927111 100644 --- a/01_Archive/2026-04-20/행동주의 심리학.md +++ b/01_Archive/2026-04-20/행동주의 심리학.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-CC1A7B -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 행동주의 심리학" --- -# [[행동주의 심리학]] +# [[행동주의 심리학|행동주의 심리학]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - 행동주의 심리학" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/행동주의 심리학.md]] +- Raw Source: 00_Raw/2026-04-20/행동주의 심리학.md --- diff --git a/01_Archive/2026-04-20/헤드 마운트 디스플레이(HMD).md b/01_Archive/2026-04-20/헤드 마운트 디스플레이(HMD).md index 8a067ac4..932ee162 100644 --- a/01_Archive/2026-04-20/헤드 마운트 디스플레이(HMD).md +++ b/01_Archive/2026-04-20/헤드 마운트 디스플레이(HMD).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-F31E1F -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 헤드 마운트 디스플레이(HMD)" --- -# [[헤드 마운트 디스플레이(HMD)]] +# [[헤드 마운트 디스플레이(HMD)|헤드 마운트 디스플레이(HMD)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 헤드 마운트 디스플레이(HMD)는 사용자가 컴퓨터로 생성된 3D 가상 현실(VR) 또는 혼합 현실(MR) 환경과 상호작용할 수 있도록 머리에 착용하는 디스플레이 기기입니다 [1]. 이 기기들은 시각, 청각, 햅틱 등 다양한 감각 정보를 제공하여 높은 몰입감을 선사하지만, 높은 인지 부하(Cognitive Load)와 VR 멀미(VR Sickness)를 유발할 수 있는 부작용도 존재합니다 [2-4]. 최근의 HMD는 무선 사용, 풀 컬러 패스스루, 향상된 해상도 및 시야각을 갖추어 교육, 시뮬레이션 훈련, 엔터테인먼트 등 다양한 분야에서 널리 활용되고 있습니다 [5-7]. @@ -22,11 +22,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 헤드 마운트 디스플레 - **정책 변화:** Graphics & Performance 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[가상 현실(Virtual Reality)]], [[혼합 현실(Mixed Reality)]], [[인지 부하(Cognitive Load)]], [[VR 멀미(VR Sickness)]] -- **Projects/Contexts:** [[비트 세이버(Beat Saber) 엑서게임 연구]], [[Meta Quest 시리즈 및 HTC Vive Pro 활용 사례]] +- **Related Topics:** 가상 현실(Virtual Reality), 혼합 현실(Mixed Reality), 인지 부하(Cognitive Load), [[VR 멀미 (VR Sickness)|VR 멀미(VR Sickness)]] +- **Projects/Contexts:** [[비트 세이버(Beat Saber) 엑서게임 연구|비트 세이버(Beat Saber) 엑서게임 연구]], Meta Quest 시리즈 및 HTC Vive Pro 활용 사례 - **Contradictions/Notes:** 소스에 관련 정보가 부족합니다. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/헤드 마운트 디스플레이(HMD).md]] +- Raw Source: 00_Raw/2026-04-20/헤드 마운트 디스플레이(HMD).md --- diff --git a/01_Archive/2026-04-20/헤드마운트 디스플레이 (HMD).md b/01_Archive/2026-04-20/헤드마운트 디스플레이 (HMD).md index 9fbccd28..7af433ba 100644 --- a/01_Archive/2026-04-20/헤드마운트 디스플레이 (HMD).md +++ b/01_Archive/2026-04-20/헤드마운트 디스플레이 (HMD).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-3585FE -category: "[[10_Wiki/💡 Topics/Graphics & Performance]]" +category: "10_Wiki/💡 Topics/Graphics & Performance" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 헤드마운트 디스플레이 (HMD)" --- -# [[헤드마운트 디스플레이 (HMD)]] +# [[헤드마운트 디스플레이 (HMD)|헤드마운트 디스플레이 (HMD)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 헤드마운트 디스플레이(HMD)는 사용자가 컴퓨터로 생성된 3D 환경과 상호작용할 수 있도록 머리에 착용하는 하드웨어 장치(헤드셋)로, 주로 가상현실(VR) 및 혼합현실(MR) 경험을 제공하는 데 사용됩니다 [1, 2]. 최근의 HMD는 시야각, 디스플레이 지연 시간, 해상도가 크게 개선되었으며, 풀 컬러 패스스루 및 독립형(standalone) 무선 사용과 같은 기술적 발전을 이루었습니다 [3-6]. 그러나 향상된 몰입감을 제공하는 반면, 과도한 인지 부하, 폭주-조절 불일치(vergence-accommodation conflict)로 인한 시각적 결함, 그리고 높은 VR 멀미(VR sickness) 발생률과 같은 사용자 경험의 과제도 함께 수반합니다 [7-9]. @@ -23,11 +23,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 헤드마운트 디스플레 - **정책 변화:** Graphics & Performance 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[가상현실 (VR)]], [[혼합현실 (MR)]], [[VR 멀미 (VR Sickness)]], [[폭주-조절 불일치 (Vergence-Accommodation Conflict)]], [[인지 부하 (Cognitive Load)]] -- **Projects/Contexts:** [[비트 세이버 (Beat Saber) 등 엑서게임]], [[교육 및 훈련용 VR 시뮬레이션]] +- **Related Topics:** [[가상현실(VR)|가상현실 (VR)]], 혼합현실 (MR), [[VR 멀미 (VR Sickness)|VR 멀미 (VR Sickness)]], [[폭주-조절 불일치(Vergence-accommodation conflict)|폭주-조절 불일치 (Vergence-Accommodation Conflict)]], 인지 부하 (Cognitive Load) +- **Projects/Contexts:** 비트 세이버 (Beat Saber) 등 엑서게임, 교육 및 훈련용 VR 시뮬레이션 - **Contradictions/Notes:** HMD는 대형 화면을 사용하는 것보다 사용자에게 훨씬 더 깊은 몰입감을 제공할 수 있는 수단이지만, 역설적으로 화면 기반 환경보다 시뮬레이터 멀미 설문지(SSQ) 점수가 실질적으로 더 높게 나타나 VR 멀미를 더 많이 유발한다는 취약점이 존재합니다 [9]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/헤드마운트 디스플레이 (HMD).md]] +- Raw Source: 00_Raw/2026-04-20/헤드마운트 디스플레이 (HMD).md --- diff --git a/01_Archive/2026-04-20/헬스케어의 민감 데이터(PII_PCI) 보안 규제 준수.md b/01_Archive/2026-04-20/헬스케어의 민감 데이터(PII_PCI) 보안 규제 준수.md index 826f1a12..4b1a479a 100644 --- a/01_Archive/2026-04-20/헬스케어의 민감 데이터(PII_PCI) 보안 규제 준수.md +++ b/01_Archive/2026-04-20/헬스케어의 민감 데이터(PII_PCI) 보안 규제 준수.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-C45097 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 헬스케어의 민감 데이터(PII_PCI) 보안 규제 준수" --- -# [[헬스케어의 민감 데이터(PII_PCI) 보안 규제 준수]] +# [[헬스케어의 민감 데이터(PII_PCI) 보안 규제 준수|헬스케어의 민감 데이터(PII_PCI) 보안 규제 준수]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 헬스케어 분야와 같이 개인식별정보(PII) 및 지불카드산업(PCI) 데이터를 다루는 시스템에서는 민감한 정보를 보호하고 GDPR, CCPA와 같은 엄격한 규제 요구사항을 충족하기 위해 강력한 보안 조치가 필수적입니다 [1, 2]. 이는 단순한 사후 조치가 아니라, 암호화, 세분화된 접근 제어 및 데이터 익명화를 포함하는 다층적 방어 전략(Multi-layered defense strategy)을 데이터 파이프라인의 모든 단계에 통합하는 것을 의미합니다 [1]. @@ -20,11 +20,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 헬스케어의 민감 데이 - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[데이터 보안 및 암호화(Data Security, Privacy, and Encryption)]], [[역할 기반 접근 제어(RBAC)]], [[데이터 거버넌스(Data Governance)]] -- **Projects/Contexts:** [[확장 가능한 시스템을 위한 데이터 엔지니어링 모범 사례(Data Engineering Best Practices)]], [[다층적 방어 전략(Multi-layered Defense Strategy)]] +- **Related Topics:** 데이터 보안 및 암호화(Data Security, Privacy, and Encryption), 역할 기반 접근 제어(RBAC), [[데이터 거버넌스 (Data Governance)|데이터 거버넌스(Data Governance)]] +- **Projects/Contexts:** 확장 가능한 시스템을 위한 데이터 엔지니어링 모범 사례(Data Engineering Best Practices), 다층적 방어 전략(Multi-layered Defense Strategy) - **Contradictions/Notes:** 소스에서는 헬스케어 시스템 및 PII/PCI 처리 시스템이 GDPR 및 CCPA 등의 규제를 준수하기 위해 다층적 보안 및 암호화를 도입해야 한다고 설명하고 있으나, 헬스케어 산업에만 특화된 고유 규제(예: HIPAA 등)에 대한 구체적인 세부 지침에 대해서는 소스에 관련 정보가 부족합니다. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/헬스케어의 민감 데이터(PII_PCI) 보안 규제 준수.md]] +- Raw Source: 00_Raw/2026-04-20/헬스케어의 민감 데이터(PII_PCI) 보안 규제 준수.md --- diff --git a/01_Archive/2026-04-20/현대 웹 애플리케이션 설계.md b/01_Archive/2026-04-20/현대 웹 애플리케이션 설계.md index 4e57c443..ed2f64b4 100644 --- a/01_Archive/2026-04-20/현대 웹 애플리케이션 설계.md +++ b/01_Archive/2026-04-20/현대 웹 애플리케이션 설계.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-21E1FE -category: "[[10_Wiki/💡 Topics/Design & Experience]]" +category: "10_Wiki/💡 Topics/Design & Experience" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 현대 웹 애플리케이션 설계" --- -# [[현대 웹 애플리케이션 설계]] +# [[현대 웹 애플리케이션 설계|현대 웹 애플리케이션 설계]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 현대 웹 애플리케이션 설계는 시스템의 확장성, 유지보수성, 그리고 개발 속도를 향상시키기 위해 복잡성을 효과적으로 분리하고 관리하는 구조적 접근 방식을 의미한다 [1-3]. 전통적인 모놀리식 구조의 한계를 극복하기 위해 관심사의 분리(SoC) 원칙을 기반으로 시스템을 독립적인 모듈과 계층으로 철저히 분할한다 [4-6]. 백엔드의 마이크로서비스 아키텍처부터 프론트엔드의 마이크로 프론트엔드, API 우선 설계, 클린 아키텍처에 이르기까지 다양한 패러다임이 결합되어 대규모 팀의 자율적이고 병렬적인 개발과 안정적인 서비스 배포를 지원한다 [7-10]. @@ -24,11 +24,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 현대 웹 애플리케이션 - **정책 변화:** Design & Experience 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[관심사의 분리(SoC)]], [[마이크로서비스 아키텍처]], [[마이크로 프론트엔드]], [[클린 아키텍처]], [[Feature-Sliced Design (FSD)]], [[API 우선 아키텍처]] -- **Projects/Contexts:** [[넷플릭스(Netflix) 마이크로서비스 도입]], [[스포티파이(Spotify) 스쿼드 모델 및 마이크로 프론트엔드]] +- **Related Topics:** [[관심사의 분리(SoC)|관심사의 분리(SoC)]], [[마이크로서비스 아키텍처|마이크로서비스 아키텍처]], [[마이크로 프론트엔드|마이크로 프론트엔드]], [[클린 아키텍처|클린 아키텍처]], [[Feature-Sliced Design (FSD)|Feature-Sliced Design (FSD)]], API 우선 아키텍처 +- **Projects/Contexts:** 넷플릭스(Netflix) 마이크로서비스 도입, 스포티파이(Spotify) 스쿼드 모델 및 마이크로 프론트엔드 - **Contradictions/Notes:** 마이크로서비스나 모듈화를 통한 관심사의 분리는 개발 및 배포의 완벽한 독립성을 제공하는 것처럼 보이지만, 횡단 관심사(Cross-cutting concerns)나 공유 데이터 구조 변경 시에는 여러 서비스가 간접적으로 결합되어 파급 효과가 발생할 수 있다는 맹점이 존재한다 [34-36]. 또한, 과도한 계층 분리와 추상화는 네트워크 지연 시간 증가, 데이터 변환 오버헤드, 가독성 저하 등의 '오버엔지니어링'을 초래할 수 있으므로 프로젝트의 규모와 실용성에 맞춘 적절한 트레이드오프와 조율이 필요하다 [37-39]. --- *Last updated: 2026-04-18* -- Raw Source: [[00_Raw/2026-04-20/현대 웹 애플리케이션 설계.md]] +- Raw Source: 00_Raw/2026-04-20/현대 웹 애플리케이션 설계.md --- diff --git a/01_Archive/2026-04-20/환영합니다!.md b/01_Archive/2026-04-20/환영합니다!.md deleted file mode 100644 index d80d118d..00000000 --- a/01_Archive/2026-04-20/환영합니다!.md +++ /dev/null @@ -1,5 +0,0 @@ -새로운 *보관함*입니다. - -내용을 한번 적어보세요, [[create a link]], 혹은 [임포터](https://help.obsidian.md/Plugins/Importer)를 사용해봐도 좋습니다! - -준비가 됐다면 이 노트를 삭제하고 맞춤형 보관함을 만들어보세요. \ No newline at end of file diff --git a/01_Archive/2026-04-20/환영합니다.md b/01_Archive/2026-04-20/환영합니다.md index f6002d14..98793435 100644 --- a/01_Archive/2026-04-20/환영합니다.md +++ b/01_Archive/2026-04-20/환영합니다.md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-BD84CA -category: "[[10_Wiki/💡 Topics/General Knowledge]]" +category: "10_Wiki/💡 Topics/General Knowledge" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 환영합니다" --- -# [[환영합니다]] +# [[환영합니다|환영합니다]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - 환영합니다" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/환영합니다!.md]] +- Raw Source: 00_Raw/2026-04-20/환영합니다!.md --- diff --git a/01_Archive/2026-04-20/회복탄력성 (Resilience).md b/01_Archive/2026-04-20/회복탄력성 (Resilience).md index 71218b14..8b539c8c 100644 --- a/01_Archive/2026-04-20/회복탄력성 (Resilience).md +++ b/01_Archive/2026-04-20/회복탄력성 (Resilience).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-848690 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 회복탄력성 (Resilience)" --- -# [[회복탄력성 (Resilience)]] +# [[회복탄력성 (Resilience)|회복탄력성 (Resilience)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -21,5 +21,5 @@ github_commit: "[P-Reinforce] Continuous Worker - 회복탄력성 (Resilience)" ## 🔗 지식 연결 (Graph) -- Raw Source: [[00_Raw/2026-04-20/회복탄력성 (Resilience).md]] +- Raw Source: 00_Raw/2026-04-20/회복탄력성 (Resilience).md --- diff --git a/01_Archive/2026-04-20/힙 메모리(Heap Memory).md b/01_Archive/2026-04-20/힙 메모리(Heap Memory).md index 764fda02..e599fb93 100644 --- a/01_Archive/2026-04-20/힙 메모리(Heap Memory).md +++ b/01_Archive/2026-04-20/힙 메모리(Heap Memory).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-109DBE -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 힙 메모리(Heap Memory)" --- -# [[힙 메모리(Heap Memory)]] +# [[힙 메모리(Heap Memory)|힙 메모리(Heap Memory)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 힙 메모리(Heap Memory)는 프로그램이 실행되는 동안 크기나 수량을 컴파일 타임에 결정할 수 없는 동적 데이터와 객체를 저장하는 데 사용되는 메모리 영역입니다 [1-3]. 운영 체제가 자동으로 구조를 관리하는 스택(Stack)과 달리, 힙 메모리는 가비지 컬렉터(Garbage Collector)를 통해 더 이상 참조되지 않는 객체의 메모리를 식별하고 주기적으로 회수하는 방식으로 관리됩니다 [4-6]. 특히 V8 엔진은 메모리 할당 및 가비지 컬렉션의 효율성을 극대화하기 위해 객체의 예상 수명(Generational hypothesis)에 따라 힙을 여러 세대별 공간으로 나누어 구조화합니다 [7-9]. @@ -34,11 +34,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 힙 메모리(Heap Memory)" - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[가비지 컬렉션(Garbage Collection)]], [[스택 메모리(Stack Memory)]], [[메모리 누수(Memory Leak)]], [[V8 엔진(V8 Engine)]] -- **Projects/Contexts:** [[Node.js 메모리 관리(Node.js Memory Management)]], [[크롬 개발자 도구 힙 프로파일링(Chrome DevTools Heap Profiling)]] +- **Related Topics:** [[가비지 컬렉션(Garbage Collection)|가비지 컬렉션(Garbage Collection)]], 스택 메모리(Stack Memory), [[메모리 누수(Memory Leak)|메모리 누수(Memory Leak)]], [[V8 엔진(V8 Engine)|V8 엔진(V8 Engine)]] +- **Projects/Contexts:** Node.js 메모리 관리(Node.js Memory Management), 크롬 개발자 도구 힙 프로파일링(Chrome DevTools Heap Profiling) - **Contradictions/Notes:** 소스에 따르면 V8 메모리 케이지(V8 Memory Cage)와 포인터 압축(Pointer Compression) 기술이 활성화된 환경(예: Chrome 103 및 Electron 21 이상)에서는 시스템에 RAM이 풍부한 64비트 플랫폼에서 실행되더라도 V8 힙의 최대 크기가 4GB로 엄격하게 제한된다는 특이점이 있습니다 [24-27]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/힙 메모리(Heap Memory).md]] +- Raw Source: 00_Raw/2026-04-20/힙 메모리(Heap Memory).md --- diff --git a/01_Archive/2026-04-20/힙 스냅샷 (Heap Snapshots).md b/01_Archive/2026-04-20/힙 스냅샷 (Heap Snapshots).md index 3c0f9293..2fe62297 100644 --- a/01_Archive/2026-04-20/힙 스냅샷 (Heap Snapshots).md +++ b/01_Archive/2026-04-20/힙 스냅샷 (Heap Snapshots).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-1E11F0 -category: "[[10_Wiki/💡 Topics/Programming & Language]]" +category: "10_Wiki/💡 Topics/Programming & Language" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 힙 스냅샷 (Heap Snapshots)" --- -# [[힙 스냅샷 (Heap Snapshots)]] +# [[힙 스냅샷 (Heap Snapshots)|힙 스냅샷 (Heap Snapshots)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 힙 스냅샷(Heap Snapshots)은 특정 시점에 애플리케이션의 자바스크립트 객체와 관련된 DOM 노드가 차지하는 메모리 분포 및 전체 객체 그래프를 캡처하여 보여주는 분석 도구입니다 [1, 2]. 이 도구는 메모리 그래프를 분석하거나 여러 스냅샷을 비교하여 메모리 누수를 찾아내고 객체 참조 트리를 확인하는 데 주로 사용됩니다 [2]. 힙 스냅샷을 생성하는 작업은 항상 가비지 컬렉션(Garbage Collection)과 함께 시작되며, 전역 객체(global object)에서 도달 가능한 객체들만을 화면에 표시합니다 [3]. @@ -33,11 +33,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 힙 스냅샷 (Heap Snapshots) - **정책 변화:** Programming & Language 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[가비지 컬렉션 (Garbage Collection)]], [[메모리 누수 (Memory Leaks)]], [[Shallow Size]], [[Retained Size]], [[할당 타임라인 (Allocation Timeline)]] -- **Projects/Contexts:** [[Chrome DevTools 메모리 패널]], [[V8 자바스크립트 엔진]] +- **Related Topics:** [[가비지 컬렉션 (Garbage Collection)|가비지 컬렉션 (Garbage Collection)]], [[메모리 누수(Memory Leaks)|메모리 누수 (Memory Leaks)]], Shallow Size, Retained Size, [[할당 타임라인(Allocation Timeline)|할당 타임라인 (Allocation Timeline)]] +- **Projects/Contexts:** Chrome DevTools 메모리 패널, [[V8 자바스크립트 엔진|V8 자바스크립트 엔진]] - **Contradictions/Notes:** 원시 힙 스냅샷에는 사용자의 애플리케이션 객체뿐만 아니라 `(compiled code)`, `(concatenated string)`, `InternalNode` 등 수천 개의 V8 내부 항목들이 포함되어 있으므로, 생성자 필터를 통해 애플리케이션 객체에 초점을 맞춰야 합니다 [15-19]. 또한 메모리 그래프가 커진다고 해서 모두 누수인 것은 아니며(캐시 보존 등 의도적 보존일 수 있음), 네이티브 코드로 실행되는 getter가 구현된 프로퍼티나 숫자 같은 비문자열 값은 자바스크립트 힙에 저장되지 않아 스냅샷에 캡처되지 않는다는 점을 유의해야 합니다 [15, 20]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/힙 스냅샷 (Heap Snapshots).md]] +- Raw Source: 00_Raw/2026-04-20/힙 스냅샷 (Heap Snapshots).md --- diff --git a/01_Archive/2026-04-20/힙 스냅샷(Heap Snapshot).md b/01_Archive/2026-04-20/힙 스냅샷(Heap Snapshot).md index 318b57c8..77e37931 100644 --- a/01_Archive/2026-04-20/힙 스냅샷(Heap Snapshot).md +++ b/01_Archive/2026-04-20/힙 스냅샷(Heap Snapshot).md @@ -1,13 +1,13 @@ --- id: P-REINFORCE-AUTO-BE247C -category: "[[10_Wiki/💡 Topics/AI]]" +category: "10_Wiki/💡 Topics/AI" confidence_score: 0.90 tags: [auto-reinforced] last_reinforced: 2026-04-20 github_commit: "[P-Reinforce] Continuous Worker - 힙 스냅샷(Heap Snapshot)" --- -# [[힙 스냅샷(Heap Snapshot)]] +# [[힙 스냅샷(Heap Snapshot)|힙 스냅샷(Heap Snapshot)]] ## 📌 한 줄 통찰 (The Karpathy Summary) > 지식 요약 정보 추출 중... @@ -37,11 +37,11 @@ github_commit: "[P-Reinforce] Continuous Worker - 힙 스냅샷(Heap Snapshot)" - **정책 변화:** AI 분야의 자동 자산화 수행. ## 🔗 지식 연결 (Graph) -- **Related Topics:** [[메모리 누수(Memory Leak)]], [[가비지 컬렉션(Garbage Collection)]], [[Allocation Timeline]] -- **Projects/Contexts:** [[Chrome DevTools Memory Panel]], [[V8 Engine Heap Management]] +- **Related Topics:** [[메모리 누수(Memory Leak)|메모리 누수(Memory Leak)]], [[가비지 컬렉션(Garbage Collection)|가비지 컬렉션(Garbage Collection)]], [[Allocation Timeline|Allocation Timeline]] +- **Projects/Contexts:** [[Chrome DevTools Memory Panel|Chrome DevTools Memory Panel]], [[V8 Engine Heap Management|V8 Engine Heap Management]] - **Contradictions/Notes:** 메모리 그래프가 증가한다고 해서 무조건 메모리 누수인 것은 아닙니다. 캐시(Caches), 실행 취소 내역, 가상화된 목록 버퍼 등은 의도적으로 데이터를 보존하므로 의도적인 메모리 보존과 사고에 의한 메모리 누수를 명확히 구별해야 합니다 [17]. --- *Last updated: 2026-04-19* -- Raw Source: [[00_Raw/2026-04-20/힙 스냅샷(Heap Snapshot).md]] +- Raw Source: 00_Raw/2026-04-20/힙 스냅샷(Heap Snapshot).md --- diff --git a/01_Archive/Old_2nd_Structure/2026-04-20.md b/01_Archive/Old_2nd_Structure/2026-04-20.md deleted file mode 100644 index e69de29b..00000000 diff --git a/01_Archive/Old_2nd_Structure/환영합니다!.md b/01_Archive/Old_2nd_Structure/환영합니다!.md deleted file mode 100644 index d80d118d..00000000 --- a/01_Archive/Old_2nd_Structure/환영합니다!.md +++ /dev/null @@ -1,5 +0,0 @@ -새로운 *보관함*입니다. - -내용을 한번 적어보세요, [[create a link]], 혹은 [임포터](https://help.obsidian.md/Plugins/Importer)를 사용해봐도 좋습니다! - -준비가 됐다면 이 노트를 삭제하고 맞춤형 보관함을 만들어보세요. \ No newline at end of file diff --git a/10_Wiki/Decisions/Index.md b/10_Wiki/Decisions/Index.md index 5eae2899..aafb18a1 100644 --- a/10_Wiki/Decisions/Index.md +++ b/10_Wiki/Decisions/Index.md @@ -1,5 +1,5 @@ # Index: Decisions ## 📁 Subcategories -- [[Skybound/Index|Skybound]] +- Skybound diff --git a/10_Wiki/Decisions/Skybound/Combat_Balance_Buff.md b/10_Wiki/Decisions/Skybound/Combat_Balance_Buff.md index d2beddb5..9651a89e 100644 --- a/10_Wiki/Decisions/Skybound/Combat_Balance_Buff.md +++ b/10_Wiki/Decisions/Skybound/Combat_Balance_Buff.md @@ -1,12 +1,12 @@ --- id: 550e8400-e29b-41d4-a716-446655440006 -category: "[[10_Wiki/Decisions/Skybound]]" +category: "10_Wiki/Decisions/Skybound" confidence_score: 0.96 tags: [skybound, game-balance, combat, buff] last_reinforced: 2026-04-21 --- -# [[플레이어 전투 밸런스 상향]] +# 플레이어 전투 밸런스 상향 ## 📌 한 줄 통찰 (The Karpathy Summary) > 스테이지 1의 몰입도 향상을 위해 플레이어 기체의 기본 연사력을 20% 상향 조정하여 전투 리듬을 개선함. @@ -23,6 +23,6 @@ last_reinforced: 2026-04-21 - **정책 변화:** 전투 밸런스 수정 시 반드시 프레임 단위의 수치를 기록하고 비교할 것. ## 🔗 지식 연결 (Graph) -- **Parent:** [[10_Wiki/Decisions/Skybound]] -- **Related:** [[10_Wiki/Projects/Skybound/HUD_UI_Refinement]] -- **Raw Source:** [[00_Raw/2026-04-21-Skybound_Player_Combat_Buff]] +- **Parent:** 10_Wiki/Decisions/Skybound +- **Related:** 10_Wiki/Projects/Skybound/HUD_UI_Refinement +- **Raw Source:** 00_Raw/2026-04-21-Skybound_Player_Combat_Buff diff --git a/10_Wiki/Decisions/Skybound/Frame_Type_Restoration.md b/10_Wiki/Decisions/Skybound/Frame_Type_Restoration.md index 22f786a9..ebf1d134 100644 --- a/10_Wiki/Decisions/Skybound/Frame_Type_Restoration.md +++ b/10_Wiki/Decisions/Skybound/Frame_Type_Restoration.md @@ -1,12 +1,12 @@ --- id: 550e8400-e29b-41d4-a716-446655440002 -category: "[[10_Wiki/Decisions/Skybound]]" +category: "10_Wiki/Decisions/Skybound" confidence_score: 1.0 tags: [skybound, typesystem, maintenance] last_reinforced: 2026-04-21 --- -# [[Skybound 프레임 타입 복구]] +# Skybound 프레임 타입 복구 ## 📌 한 줄 통찰 (The Karpathy Summary) > 엔진 루프의 시간축 참조를 위한 `frame` 속성을 인터페이스에 명시하여 정적 타입 무결성을 복구함. @@ -23,6 +23,6 @@ last_reinforced: 2026-04-21 - **정책 변화:** 핵심 엔진 상태 속성은 누락 시 즉시 반려(Veto) 대상임. ## 🔗 지식 연결 (Graph) -- **Parent:** [[10_Wiki/Decisions/Skybound]] -- **Related:** [[10_Wiki/Projects/Skybound/Architecture_Refactor]] -- **Raw Source:** [[00_Raw/2026-04-21-Skybound_Frame_Type_Restoration]] +- **Parent:** 10_Wiki/Decisions/Skybound +- **Related:** 10_Wiki/Projects/Skybound/Architecture_Refactor +- **Raw Source:** 00_Raw/2026-04-21-Skybound_Frame_Type_Restoration diff --git a/10_Wiki/Decisions/Skybound/IDE_Stability_Fix.md b/10_Wiki/Decisions/Skybound/IDE_Stability_Fix.md index 4be51085..cd4e6b57 100644 --- a/10_Wiki/Decisions/Skybound/IDE_Stability_Fix.md +++ b/10_Wiki/Decisions/Skybound/IDE_Stability_Fix.md @@ -1,12 +1,12 @@ --- id: 550e8400-e29b-41d4-a716-446655440004 -category: "[[10_Wiki/Decisions/Skybound]]" +category: "10_Wiki/Decisions/Skybound" confidence_score: 0.99 tags: [skybound, typescript, stability, code-quality] last_reinforced: 2026-04-21 --- -# [[Skybound IDE 안정성 및 타입 보정]] +# Skybound IDE 안정성 및 타입 보정 ## 📌 한 줄 통찰 (The Karpathy Summary) > 엄격한 타입 매칭과 필수 속성 초기화를 통해 런타임 잠재 에러를 사전에 차단하고 개발자 생산성을 향상함. @@ -23,6 +23,6 @@ last_reinforced: 2026-04-21 - **정책 변화:** 모든 유틸리티 함수 반환값은 Partial을 지양하고 Full-spec을 따를 것. ## 🔗 지식 연결 (Graph) -- **Parent:** [[10_Wiki/Decisions/Skybound]] -- **Related:** [[10_Wiki/Projects/Skybound/Architecture_Refactor]] -- **Raw Source:** [[00_Raw/2026-04-21-Skybound_IDE_Problems_Fix]] +- **Parent:** 10_Wiki/Decisions/Skybound +- **Related:** 10_Wiki/Projects/Skybound/Architecture_Refactor +- **Raw Source:** 00_Raw/2026-04-21-Skybound_IDE_Problems_Fix diff --git a/10_Wiki/Decisions/Skybound/Index.md b/10_Wiki/Decisions/Skybound/Index.md index 9eee0c12..5a3b1def 100644 --- a/10_Wiki/Decisions/Skybound/Index.md +++ b/10_Wiki/Decisions/Skybound/Index.md @@ -1,6 +1,6 @@ # Index: Decisions > Skybound ## 📝 Documents -- [[Combat_Balance_Buff]] -- [[Frame_Type_Restoration]] -- [[IDE_Stability_Fix]] +- [[Combat_Balance_Buff|Combat_Balance_Buff]] +- [[Frame_Type_Restoration|Frame_Type_Restoration]] +- [[IDE_Stability_Fix|IDE_Stability_Fix]] diff --git a/10_Wiki/Development/Code Splitting.md b/10_Wiki/Development/Code Splitting.md index 96aa31b1..f4eb39d4 100644 --- a/10_Wiki/Development/Code Splitting.md +++ b/10_Wiki/Development/Code Splitting.md @@ -1,4 +1,4 @@ -# [[Code Splitting]] +# [[Code Splitting|Code Splitting]] ## 📌 Brief Summary 큰 자바스크립트 번들을 더 작은 청크(chunk) 단위로 나누어 사용자가 필요로 할 때(on demand) 로드하는 프로세스입니다 [1, 2]. 모든 애플리케이션 코드를 초기에 한 번에 다운로드하는 대신, 필요한 파일만 먼저 불러오게 하여 초기 번들 크기를 극적으로 줄일 수 있습니다 [2, 3]. 결과적으로 초기 페이지 로드 속도를 향상시키고, 애플리케이션의 체감 성능을 개선하는 핵심적인 프론트엔드 최적화 기법입니다 [1, 4]. @@ -19,18 +19,18 @@ ### Related Concepts #### [아키텍처/기반 기술] -- [[Lazy Loading]] +- [[Lazy Loading|Lazy Loading]] - 연결 이유: 코드 분할이 번들을 쪼개는 행위라면, 지연 로딩(Lazy Loading)은 그 쪼개진 코드를 필요 시점에 로드하는 기술적 방법론입니다 [2, 3]. - 이 개념을 통해 더 깊게 이해할 수 있는 부분: 분할된 코드가 언제 브라우저로 전송되고 애플리케이션에 병합되는지 이해할 수 있습니다 [8]. -- [[Core Web Vitals]] +- [[Core Web Vitals|Core Web Vitals]] - 연결 이유: 코드 분할을 적용하는 주된 성능적 목적은 초기 자바스크립트 실행을 최소화하여 LCP(Largest Contentful Paint)와 INP(Interaction to Next Paint) 같은 핵심 웹 지표를 향상시키는 데 있습니다 [1, 8, 14]. - 이 개념을 통해 더 깊게 이해할 수 있는 부분: 최적화 결과가 실제 사용자의 체감 성능 및 페이지 측정 지표에 어떻게 긍정적 영향을 주는지 평가할 수 있습니다 [15]. #### [구현/활용 도구] -- [[React.lazy() and Suspense]] +- React.lazy() and Suspense - 연결 이유: React 애플리케이션에서 컴포넌트 레벨 및 라우트 레벨의 동적 코드 분할을 구현하기 위해 사용하는 공식 API입니다 [6, 8]. - 이 개념을 통해 더 깊게 이해할 수 있는 부분: 동적 임포트 처리 과정에서의 비동기 UI 렌더링 흐름과 예외(지연) 처리 방식을 배울 수 있습니다 [5]. -- [[Vite (Rollup)]] +- Vite (Rollup) - 연결 이유: 개발 및 프로덕션 환경에서 자바스크립트 애플리케이션을 번들링하고 실제 물리적인 청크 파일들로 분리해 내는 도구입니다 [9, 11]. - 이 개념을 통해 더 깊게 이해할 수 있는 부분: 번들러의 `manualChunks` 설정을 통해 어떻게 벤더 라이브러리와 애플리케이션 코드를 효율적으로 나누어 브라우저 캐싱을 활용할 수 있는지 이해할 수 있습니다 [5]. @@ -49,9 +49,9 @@ - **My Project Relevance:** 프로젝트 규모가 커짐에 따라 메인 자바스크립트 번들이 수 메가바이트 단위로 무거워져 모바일 기기 등에서 로딩 속도 저하 현상이 보일 경우, 즉각적으로 라우트 기반 코드 분할과 차트/에디터 등 무거운 UI의 지연 로딩을 도입하여 LCP 문제를 해결할 수 있습니다 [3, 14, 16]. ### Adjacent Topics -- [[Tree Shaking]] +- [[Tree Shaking (번들 크기 최적화)|Tree Shaking]] - 확장 방향: 코드 분할이 필요한 코드를 '쪼개어' 가져오는 방식이라면, 트리 쉐이킹은 사용되지 않는 죽은 코드(Dead Code) 자체를 번들에서 '제거'하여 초기 번들 크기를 줄이는 상호 보완적인 최적화 기법입니다 [17, 18]. -- [[Server Components (Next.js)]] +- Server Components (Next.js) - 확장 방향: 클라이언트 사이드의 코드 분할에서 더 나아가, 아예 정적인 UI 렌더링을 서버에서 처리하여 클라이언트로 보내는 자바스크립트 번들의 양 자체를 획기적으로 줄이거나 제거하는 최신 아키텍처 접근법입니다 [19-21]. --- diff --git a/10_Wiki/Development/Concurrent Features.md b/10_Wiki/Development/Concurrent Features.md index 2c5c54ed..c38e53a8 100644 --- a/10_Wiki/Development/Concurrent Features.md +++ b/10_Wiki/Development/Concurrent Features.md @@ -1,4 +1,4 @@ -# [[Concurrent Features]] +# [[Concurrent Features|Concurrent Features]] ## 📌 Brief Summary Concurrent Features는 React 18부터 도입된 기능으로, 렌더링 작업을 일시 중지(pause), 중단(interrupt), 재개(resume)할 수 있게 해주는 기능입니다 [1]. 이를 통해 중요한 사용자 상호작용(클릭, 타이핑 등)의 우선순위를 높이고, 상대적으로 느린 업데이트(대용량 필터링 등)를 지연시킬 수 있습니다 [1]. 결과적으로 앱의 실제 연산 속도 자체를 마법처럼 빠르게 만드는 것은 아니지만, 인지되는 속도(perceived speed)를 최적화하여 사용자 인터페이스를 반응성 있게 유지합니다 [2]. @@ -19,16 +19,16 @@ Concurrent Features는 React 18부터 도입된 기능으로, 렌더링 작업 ### Related Concepts #### [관계 유형 A: 아키텍처/기반 기술] -- [[useTransition]] +- [[useTransition|useTransition]] - 연결 이유: 상태 업데이트를 긴급하지 않은 것으로 표시하여 지연시킬 수 있는 Concurrent Feature의 핵심 요소입니다 [3]. - 이 개념을 통해 더 깊게 이해할 수 있는 부분: React가 렌더링 우선순위를 조정하여 사용자 입력 반응성을 잃지 않게 유지하는 구체적인 메커니즘. -- [[useDeferredValue]] +- [[useDeferredValue|useDeferredValue]] - 연결 이유: 비용이 큰 파생 데이터의 렌더링 반영 시점을 지연시켜 UI 끊김을 막는 또 다른 주요 요소입니다 [4]. - 이 개념을 통해 더 깊게 이해할 수 있는 부분: 상태의 업데이트 시점이 아닌, 계산된 값을 읽어 들이는 시점을 분리하는 최적화 전략. #### [관계 유형 B: 구현/활용 도구] -- [[Suspense]] +- Suspense - 연결 이유: Concurrent Feature(특히 `useTransition`)와 결합하여 무거운 렌더링이나 데이터가 로드되는 동안 Fallback UI를 유연하게 표시하는 데 사용됩니다 [4]. - 이 개념을 통해 더 깊게 이해할 수 있는 부분: 비동기 로딩 상태에서 사용자 경험(UX)을 부드럽게 설계하는 선언적 UI 패턴. @@ -47,9 +47,9 @@ Concurrent Features는 React 18부터 도입된 기능으로, 렌더링 작업 - **My Project Relevance:** 검색 필터가 많은 대시보드나 실시간 데이터 시각화 차트를 구축할 때 UI 스레드가 멈추는 것을 방지하여 사용자 경험을 크게 개선하는 데 직접적으로 적용될 수 있습니다. ### Adjacent Topics -- [[Server Components]] +- [[Server Components|Server Components]] - 확장 방향: 클라이언트에서 렌더링을 지연시키거나 최적화하는 것을 넘어, 무거운 렌더링 작업 자체를 서버로 완전히 옮겨 클라이언트의 자바스크립트 번들 크기와 실행 부담을 근본적으로 줄이는 방법론 탐구 [6, 7]. -- [[Code Splitting & Lazy Loading]] +- Code Splitting & Lazy Loading - 확장 방향: 화면의 렌더링 과정을 매끄럽게 하는 것을 넘어, 초기 애플리케이션 로딩 시 네트워크를 통해 다운로드하는 코드의 양 자체를 분할하여 초기 응답성(Time to Interactive)을 향상시키는 전략 탐구 [8, 9]. --- diff --git a/10_Wiki/Development/Concurrent Rendering in React 18+.md b/10_Wiki/Development/Concurrent Rendering in React 18+.md index b20eeb11..d8b116cb 100644 --- a/10_Wiki/Development/Concurrent Rendering in React 18+.md +++ b/10_Wiki/Development/Concurrent Rendering in React 18+.md @@ -1,4 +1,4 @@ -# [[Concurrent Rendering in React 18+]] +# [[Concurrent Rendering in React 18+|Concurrent Rendering in React 18+]] ## 📌 Brief Summary React 18+의 동시성 렌더링(Concurrent Rendering)은 React가 렌더링 작업을 일시 중지, 중단 및 재개할 수 있도록 하는 강력한 기능입니다 [1]. 이를 통해 개발자는 업데이트 발생 시기와 방식을 세밀하게 제어할 수 있으며, 사용자의 상호작용성을 저하시키지 않으면서도 화면이 멈추지 않는 더 부드럽고 반응성 높은 애플리케이션을 구축할 수 있습니다 [1, 2]. @@ -22,15 +22,15 @@ React 18+의 동시성 렌더링(Concurrent Rendering)은 React가 렌더링 작 ### Related Concepts -- [[useTransition]] +- [[useTransition|useTransition]] - 연결 이유: 동시성 렌더링 환경에서 특정 상태 업데이트를 '긴급하지 않은 작업'으로 명시적으로 분류하기 위해 사용되는 핵심 훅입니다 [3]. - 이 개념을 통해 더 깊게 이해할 수 있는 부분: 상태 업데이트의 우선순위를 낮추어 사용자 입력에 대한 메인 스레드 차단을 방지하는 구체적인 제어 방법. -- [[useDeferredValue]] +- [[useDeferredValue|useDeferredValue]] - 연결 이유: 연산 비용이 높은 값의 화면 적용 시점을 늦추어 UI의 즉각적인 체감 반응성을 향상시키는 동시성 기능이기 때문입니다 [4]. - 이 개념을 통해 더 깊게 이해할 수 있는 부분: 사용자 입력(타이핑 등)의 즉각적인 반영과 무거운 파생 데이터 렌더링 간의 처리 시점을 분리하는 메커니즘. -- [[Suspense]] +- Suspense - 연결 이유: 동시성 훅(`useTransition` 등)과 결합하여 비동기 처리나 지연된 렌더링이 완료되기 전까지 자연스러운 대체 UI(Fallback UI)를 표시하는 역할을 합니다 [4]. - 이 개념을 통해 더 깊게 이해할 수 있는 부분: 비동기 데이터 로딩 과정에서 동시성 렌더링을 활용한 부드러운 사용자 경험(UX) 설계 방식. @@ -52,10 +52,10 @@ React 18+의 동시성 렌더링(Concurrent Rendering)은 React가 렌더링 작 ### Adjacent Topics -- [[React Server Components]] +- [[React Server Components|React Server Components]] - 확장 방향: 동시성 렌더링과 함께 Next.js App Router 환경의 핵심 성능 최적화 축을 이루며, 클라이언트 측 자바스크립트 번들을 획기적으로 줄여주는 서버 컴포넌트의 렌더링 원리 탐구 [5, 6]. -- [[Core Web Vitals (INP/TBT)]] +- Core Web Vitals (INP/TBT) - 확장 방향: 동시성 렌더링 기능 적용이 웹의 핵심 반응성 지표인 INP 및 TBT를 어떻게 개선하는지 실제 성능 측정 툴(Chrome DevTools, Lighthouse) 데이터와 연계하여 조사 [7-9]. --- diff --git a/10_Wiki/Development/Context API.md b/10_Wiki/Development/Context API.md index b0dfba57..315c5a47 100644 --- a/10_Wiki/Development/Context API.md +++ b/10_Wiki/Development/Context API.md @@ -1,4 +1,4 @@ -# [[Context API]] +# [[Context API|Context API]] ## 📌 Brief Summary Context API는 React에 내장된 상태 공유 솔루션으로, 컴포넌트 트리의 모든 레벨을 통해 명시적으로 props를 전달하지 않고도 데이터를 전송할 수 있게 해주는 기능입니다 [1, 2]. 이는 독립적인 상태 관리 도구라기보다는 데이터를 전달하는 브로드캐스트 전송 메커니즘에 가깝습니다 [3, 4]. 주로 테마, 다국어 설정 등 변경이 거의 없는 정적인 데이터를 전역적으로 공유할 때 적합하게 사용됩니다 [5, 6]. @@ -12,13 +12,13 @@ Context API는 React에 내장된 상태 공유 솔루션으로, 컴포넌트 ## 🔗 Knowledge Connections ### Related Concepts -- [[Prop Drilling]] +- [[Prop Drilling|Prop Drilling]] - 연결 이유: 부모 컴포넌트에서 깊게 중첩된 자식 컴포넌트로 데이터를 전달하기 위해 불필요한 중간 컴포넌트들을 거쳐야 하는 패턴입니다 [2]. - 이 개념을 통해 더 깊게 이해할 수 있는 부분: Context API가 탄생하게 된 근본적인 배경과, 데이터를 어떻게 트리 아래로 "건너뛰어" 전달하는지 그 목적을 이해할 수 있습니다 [2, 19]. -- [[useContext]] +- useContext - 연결 이유: Context API의 Provider가 제공하는 브로드캐스트 값을 읽기 위해 개별 컴포넌트 내부에서 호출하는 React의 내장 훅입니다 [4]. - 이 개념을 통해 더 깊게 이해할 수 있는 부분: 구독(Subscription)이 발생하는 정확한 지점과, 값이 변경될 때 어떤 컴포넌트에서 리렌더링이 트리거되는지 렌더링 동작 원리를 파악할 수 있습니다 [8]. -- [[Zustand]] +- Zustand - 연결 이유: Context API의 리렌더링 한계와 보일러플레이트를 극복하기 위해 자주 비교되고 채택되는 경량 상태 관리 라이브러리입니다 [20, 21]. - 이 개념을 통해 더 깊게 이해할 수 있는 부분: Zustand의 'Selector 패턴'이 어떻게 특정 상태 슬라이스만 구독하게 하여 Context API의 "전체 리렌더링" 문제를 해결하는지 성능 최적화의 차이를 비교할 수 있습니다 [8, 10]. @@ -37,9 +37,9 @@ Context API는 React에 내장된 상태 공유 솔루션으로, 컴포넌트 - **My Project Relevance:** 기존 코드베이스에 'Global Context' 안티 패턴(모든 상태를 한 곳에 몰아넣은 형태)이 존재하지 않는지 점검하고 [11], 렌더링 병목이 있는 경우 `useMemo`, `useCallback`과 함께 Context를 책임별로 분할하는 리팩토링 목표와 직접적으로 연관됩니다 [1, 12]. ### Adjacent Topics -- [[React.memo]] +- React.memo - 확장 방향: Context API에 의해 발생하는 불필요한 하위 컴포넌트 렌더링을 방지하기 위한 얕은 비교(Shallow Compare) 최적화 도구로, 렌더링 성능 최적화(Performance Optimization) 기법 전반으로의 이해를 확장합니다 [28, 29]. -- [[Concurrent Rendering]] +- [[Concurrent Rendering|Concurrent Rendering]] - 확장 방향: React 18의 동시성 렌더링 기능(`useTransition`, `useDeferredValue`)을 통해 무거운 컴포넌트 렌더링을 어떻게 지연시키고 애플리케이션의 반응성을 개선할 수 있는지 상태 업데이트 흐름으로 탐구를 확장합니다 [6, 30]. --- diff --git a/10_Wiki/Development/Debugging Frontend Applications.md b/10_Wiki/Development/Debugging Frontend Applications.md index 51a64a0b..d2a1177c 100644 --- a/10_Wiki/Development/Debugging Frontend Applications.md +++ b/10_Wiki/Development/Debugging Frontend Applications.md @@ -1,4 +1,4 @@ -# [[Debugging Frontend Applications]] +# [[Debugging Frontend Applications|Debugging Frontend Applications]] ## 📌 Brief Summary 프론트엔드 디버깅은 웹 애플리케이션에서 발생하는 자바스크립트 런타임 에러, 메모리 누수, 그리고 불필요한 리렌더링과 같은 성능 저하 요인을 식별하고 해결하는 과정입니다 [1-3]. Chrome DevTools와 같은 브라우저 내장 도구부터 React DevTools, 그리고 Sentry나 LogRocket과 같은 프로덕션 클라우드 로깅 도구를 활용하여 문제의 근본 원인을 추적합니다 [4-7]. 효과적인 디버깅 전략과 에러 핸들링 아키텍처는 애플리케이션의 안정성을 보장하고 사용자 경험을 최적화하는 데 필수적입니다 [8-10]. @@ -30,20 +30,20 @@ ### Related Concepts #### [관계 유형 A (브라우저 및 성능 분석 기반 도구)] -- [[Chrome DevTools]] +- [[Chrome DevTools|Chrome DevTools]] - 연결 이유: 자바스크립트 힙 메모리와 DOM의 상태를 프로파일링하여 메모리 누수를 진단하는 가장 근본적인 프론트엔드 디버깅 도구이기 때문입니다 [6, 34]. - 이 개념을 통해 더 깊게 이해할 수 있는 부분: 브라우저의 가비지 컬렉션(GC) 동작 원리, 분리된 DOM 노드(Detached DOM nodes)와 클로저(Closure)가 메모리를 점유하여 성능을 저하시키는 원리를 시각적으로 이해할 수 있습니다 [2, 14, 17, 35]. #### [관계 유형 B (React 컴포넌트 및 에러 핸들링 도구)] -- [[React Error Boundaries]] +- React Error Boundaries - 연결 이유: 렌더링 및 생명주기 도중 발생하는 컴포넌트 런타임 에러를 디버깅/핸들링하여 "하얀 화면(White screen of death)"을 막아주는 React만의 고유한 방어적 디버깅 패턴입니다 [1, 36]. - 이 개념을 통해 더 깊게 이해할 수 있는 부분: 선언적(Declarative) UI 트리의 에러 전파 방식과, 명령형(Imperative) 이벤트 핸들러에서 `try-catch`를 사용해야 하는 아키텍처적 차이를 명확히 구분할 수 있습니다 [32]. -- [[React DevTools Profiler]] +- [[React DevTools Profiler|React DevTools Profiler]] - 연결 이유: 어떤 컴포넌트가 언제, 왜 리렌더링되었는지를 측정(Profiling)하여 렌더링 병목 현상을 디버깅하는 필수 도구입니다 [7, 37]. - 이 개념을 통해 더 깊게 이해할 수 있는 부분: React의 렌더링 라이프사이클, 불필요한 상태 및 props 변경 추적, 그리고 React Compiler 도입 전후의 렌더링 패스(Render pass) 차이를 검증하는 방법을 배울 수 있습니다 [7, 38]. #### [관계 유형 C (프로덕션 환경 관측성 도구)] -- [[Session Replay & Distributed Tracing]] +- Session Replay & Distributed Tracing - 연결 이유: 로컬에서 재현이 불가능한 프로덕션 에러를 추적하기 위해 사용자의 브라우저 상호작용(Sentry, LogRocket)과 백엔드 데이터 흐름(Datadog)을 연결하여 디버깅 단서를 찾는 핵심 개념입니다 [5, 24, 39]. - 이 개념을 통해 더 깊게 이해할 수 있는 부분: 풀스택 환경에서의 엔드투엔드(End-to-End) 성능 모니터링 한계와 프론트엔드 에러가 백엔드 서비스에 미치는 연관 관계를 깊게 이해할 수 있습니다 [24, 25]. @@ -65,9 +65,9 @@ ### Adjacent Topics -- [[State Management Architecture]] +- State Management Architecture - 확장 방향: 상태 관리 라이브러리(Redux, Zustand, Context API 등)의 아키텍처적 선택이 상태 변화 추적성과 DevTools 디버깅 퀄리티에 어떤 영향을 미치는지 분석 [21, 22, 49]. -- [[Frontend Performance Optimization]] +- [[프론트엔드 성능 최적화(Frontend Performance Optimization)|Frontend Performance Optimization]] - 확장 방향: 디버깅을 통해 발견한 메모리 누수와 불필요한 컴포넌트 렌더링(Re-renders) 문제를 실질적인 성능 최적화 기법(가상화, 코드 스플리팅)으로 해결하여 Core Web Vitals를 개선하는 방향 [20, 50]. --- diff --git a/10_Wiki/Development/Engineering Scalable Frontend Systems.md b/10_Wiki/Development/Engineering Scalable Frontend Systems.md index 387ef5fb..a6090569 100644 --- a/10_Wiki/Development/Engineering Scalable Frontend Systems.md +++ b/10_Wiki/Development/Engineering Scalable Frontend Systems.md @@ -1,4 +1,4 @@ -# [[Engineering Scalable Frontend Systems]] +# [[Engineering Scalable Frontend Systems|Engineering Scalable Frontend Systems]] ## 📌 Brief Summary 확장 가능한 프론트엔드 시스템(Engineering Scalable Frontend Systems)은 단순한 스크립트 실행을 넘어 유지보수성, 고성능, 견고성을 갖춘 분산 소프트웨어 아키텍처를 구축하는 것을 의미합니다 [1]. 이는 기술적 파일 기반 폴더 구조에서 기능 중심(Feature-Based) 및 도메인 기반 설계로의 전환을 요구하며, 엄격한 코드 컨벤션과 거버넌스를 동반합니다 [2, 3]. 또한 프론트엔드 개발에 SOLID와 같은 소프트웨어 공학 원칙을 결합하고, 서버/클라이언트 상태의 분리, 그리고 빌드 타임 및 런타임 성능 최적화를 통해 예측 가능한 성장을 가능하게 합니다 [1, 4, 5]. @@ -34,26 +34,26 @@ ### Related Concepts #### [관계 유형 A: 아키텍처 및 시스템 구조 (Architecture & Structural Design)] -* `[[Feature-Sliced Design (FSD)]]` +* `[[Feature-Sliced Design (FSD)|Feature-Sliced Design (FSD)]]` * 연결 이유: 현대 프론트엔드의 모듈화 및 확장성을 해결하기 위해 널리 채택되는 아키텍처 방법론의 핵심이기 때문입니다 [9, 10]. * 이 개념을 통해 더 깊게 이해할 수 있는 부분: 비즈니스 도메인 기반의 코드 분할, 엄격한 단방향 의존성 규칙 적용 방법, 그리고 퍼블릭 API를 통한 모듈 캡슐화 원리 [4, 8, 50]. -* `[[Error Boundaries]]` +* `[[Error Boundaries|Error Boundaries]]` * 연결 이유: 부분적인 UI 런타임 에러가 시스템 전체의 장애(White screen of death)로 확산되는 것을 방지하는 구조적 안전 장치이기 때문입니다 [33, 34]. * 이 개념을 통해 더 깊게 이해할 수 있는 부분: 렌더링 트리에서 컴포넌트 결함을 격리하는 원리와 시스템 복원력을 높이는 에러 처리 전략 [33, 35]. #### [관계 유형 B: 상태 관리 패러다임 (State Management Paradigms)] -* `[[Zustand vs Context API]]` +* `Zustand vs Context API` * 연결 이유: 전역 상태 관리에서 성능과 확장성을 결정짓는 가장 빈번한 아키텍처 결정 지점이기 때문입니다 [5, 19]. * 이 개념을 통해 더 깊게 이해할 수 있는 부분: Context API의 브로드캐스트 렌더링 문제점과 이를 해결하기 위한 Zustand의 구독/선택자(Selector) 기반 렌더링 최적화 기법 [19, 20, 51]. -* `[[TanStack Query (React Query)]]` +* `TanStack Query (React Query)` * 연결 이유: 클라이언트 상태와 서버 상태(Server State)를 구조적으로 분리하여 API 데이터 처리의 병목을 없애주기 때문입니다 [18, 22]. * 이 개념을 통해 더 깊게 이해할 수 있는 부분: 데이터 캐싱, 백그라운드 동기화 및 API 계층의 관심사 분리(Separation of Concerns) [18, 22]. #### [관계 유형 C: 성능 및 빌드 최적화 (Performance & Build Optimization)] -* `[[React Compiler]]` +* `[[React Compiler|React Compiler]]` * 연결 이유: 수동 메모이제이션의 복잡성을 줄이고 빌드 타임에 컴포넌트 렌더링 성능을 자동으로 최적화하는 최신 핵심 도구이기 때문입니다 [25, 28, 29]. * 이 개념을 통해 더 깊게 이해할 수 있는 부분: 선언적 UI 프레임워크에서의 빌드 타임 최적화 한계 및 React의 규칙(Rules of React)이 강제하는 불변성의 중요성 [52, 53]. -* `[[Code Splitting & Lazy Loading]]` +* `Code Splitting & Lazy Loading` * 연결 이유: 초기 로드(First Paint) 속도 향상과 JavaScript 번들 크기를 제어하는 확장 가능한 시스템의 필수 성능 전략이기 때문입니다 [30, 31, 54]. * 이 개념을 통해 더 깊게 이해할 수 있는 부분: Vite나 Webpack 같은 번들러 환경에서 동적 임포트를 통한 라우트 단위 분할 및 무거운 벤더 청크(`manualChunks`)의 캐싱 분리 전략 [26, 27, 31]. @@ -75,9 +75,9 @@ ### Adjacent Topics -* `[[Core Web Vitals]]` +* `[[Core Web Vitals|Core Web Vitals]]` * 확장 방향: LCP(Largest Contentful Paint), INP(Interaction to Next Paint), CLS(Cumulative Layout Shift) 등 구글이 정의한 사용자 경험 중심의 성능 측정 지표를 이해하고, 앞서 다룬 코드 스플리팅, 레이지 로딩, 렌더링 최적화 기법이 실제 사용자 체감 속도 향상에 어떻게 직결되는지 심층 분석하는 방향으로 연구할 수 있습니다 [23, 60, 61]. -* `[[Git Branching Strategies & CI/CD Governance]]` +* `Git Branching Strategies & CI/CD Governance` * 확장 방향: 복잡한 프론트엔드 시스템을 다수의 개발자가 협업하여 구축할 때 충돌을 최소화하고 릴리스 안정성을 높이기 위한 GitHub Flow, Trunk-Based Development 등의 브랜칭 전략과, ESLint/Prettier 자동화, Conventional Commits를 활용한 배포 파이프라인(CI/CD) 통제 방법을 확장해서 조사할 수 있습니다 [62-64]. --- diff --git a/10_Wiki/Development/Folder Structure Best Practices.md b/10_Wiki/Development/Folder Structure Best Practices.md index c340d218..f1aeedd8 100644 --- a/10_Wiki/Development/Folder Structure Best Practices.md +++ b/10_Wiki/Development/Folder Structure Best Practices.md @@ -1,4 +1,4 @@ -# [[Folder Structure Best Practices]] +# [[Folder Structure Best Practices|Folder Structure Best Practices]] ## 📌 Brief Summary React 등 프론트엔드 프로젝트에서 코드의 유지보수성, 확장성, 그리고 협업 효율성을 높이기 위해 파일과 디렉터리를 체계적으로 구성하는 방법론입니다 [1]. 현대적인 애플리케이션에서는 과거의 파일 유형 기반(유형별 분류) 구조에서 벗어나, 기능(Feature)이나 도메인 중심으로 관련된 로직을 묶는 하이브리드 또는 기능 기반 방식이 모범 사례로 권장됩니다 [2, 3]. 이를 통해 UI, 비즈니스 로직, 상태 관리 등의 관심사를 명확히 분리하고 프로젝트가 커짐에 따라 발생하는 기술 부채를 최소화할 수 있습니다 [4]. @@ -33,15 +33,15 @@ React 등 프론트엔드 프로젝트에서 코드의 유지보수성, 확장 ## 🔗 Knowledge Connections ### Related Concepts -- [[Feature-Sliced Design]] +- [[Feature-Sliced Design|Feature-Sliced Design]] - 연결 이유: 대규모 React 애플리케이션의 폴더 구조를 구축하기 위해 고안된 전문적인 프론트엔드 아키텍처 방법론이기 때문입니다 [21]. - 이 개념을 통해 더 깊게 이해할 수 있는 부분: 폴더 간의 단방향 의존성 규칙과 각 폴더(Layer, Slice, Segment)가 담당해야 하는 역할의 엄격한 분리 방식 [22, 28]. -- [[Separation of Concerns]] (관심사의 분리) +- [[_뇌와 팔다리의 분리_ - 관심사의 분리 (Separation of Concerns)|Separation of Concerns]] (관심사의 분리) - 연결 이유: 폴더 구조를 설계하는 근본적인 목적이 UI 렌더링, 전역 상태 관리, 데이터 통신(API) 등의 책임을 각기 다른 위치로 분리하는 데 있기 때문입니다 [4, 29]. - 이 개념을 통해 더 깊게 이해할 수 있는 부분: `services/`, `store/`, `components/` 등의 폴더를 분리하여 단일 책임 원칙(SRP)을 프론트엔드 아키텍처 전반에 적용하는 방법 [4, 30]. -- [[Naming Conventions]] (명명 규칙) +- [[Naming Conventions|Naming Conventions]] (명명 규칙) - 연결 이유: 일관된 폴더 및 파일 명명 규칙(예: 폴더명은 kebab-case, 컴포넌트는 PascalCase)은 폴더 구조 내에서 파일을 예측 가능하게 찾고 충돌을 방지하는 핵심 규칙이기 때문입니다 [31-33]. - 이 개념을 통해 더 깊게 이해할 수 있는 부분: 다양한 운영체제와 CI/CD 파이프라인에서 빌드 에러를 방지하고 팀 내 코드 가독성을 유지하는 방법 [34, 35]. @@ -60,9 +60,9 @@ React 등 프론트엔드 프로젝트에서 코드의 유지보수성, 확장 - **My Project Relevance:** 현재 진행 중이거나 리팩토링해야 할 React 코드베이스에서, 거대해진 `components/` 폴더를 도메인 단위의 `features/` 폴더로 나누고 재사용 불가 로직들을 분리하는 데 직접적으로 적용됩니다. ### Adjacent Topics -- [[State Management]] +- [[상태 관리(State Management)|State Management]] - 확장 방향: 전역 상태(Global State)와 로컬 상태(Local State)를 어디에 보관해야 하는지, Zustand와 같은 도구가 `store/` 폴더의 구조를 어떻게 단순화하는지 확장하여 조사할 수 있습니다. -- [[Code Splitting]] (코드 스플리팅) +- [[Code Splitting|Code Splitting]] (코드 스플리팅) - 확장 방향: 라우트 혹은 폴더(Feature) 단위로 코드 스플리팅과 지연 로딩(Lazy Loading)을 적용하여 초기 번들 크기를 줄이고 성능을 최적화하는 전략과 연결됩니다. --- diff --git a/10_Wiki/Development/Frontend Performance Debugging.md b/10_Wiki/Development/Frontend Performance Debugging.md index e8479bfa..c0a62bf3 100644 --- a/10_Wiki/Development/Frontend Performance Debugging.md +++ b/10_Wiki/Development/Frontend Performance Debugging.md @@ -1,4 +1,4 @@ -# [[Frontend Performance Debugging]] +# [[Frontend Performance Debugging|Frontend Performance Debugging]] ## 📌 Brief Summary 프론트엔드 성능 디버깅(Frontend Performance Debugging)은 웹 애플리케이션의 메모리 누수, 불필요한 리렌더링, 잦은 가비지 컬렉션 등으로 인해 발생하는 성능 저하와 응답 지연을 식별하고 해결하는 과정입니다 [1-3]. 개발자는 브라우저의 내장 개발자 도구(Chrome DevTools)를 활용해 메모리 상태와 컴포넌트 렌더링 비용을 로컬에서 분석합니다 [4, 5]. 더 나아가 프로덕션 환경에서는 클라우드 기반 로깅 및 모니터링 도구를 사용하여 실제 사용자의 세션과 에러를 추적함으로써 복잡한 성능 병목의 근본 원인을 파악합니다 [6-8]. @@ -25,23 +25,23 @@ React 애플리케이션에서는 상태(State), 프로퍼티(Props), 컨텍스 ### Related Concepts #### [관계 유형 A (로컬 디버깅 및 분석 도구)] -- [[Chrome DevTools Memory Profiler]] +- Chrome DevTools Memory Profiler - 연결 이유: 자바스크립트 애플리케이션의 메모리 누수와 객체 보존 상태를 프로파일링하는 브라우저 내장 도구. - 이 개념을 통해 더 깊게 이해할 수 있는 부분: Heap Snapshots 비교, Allocation Timeline을 통한 메모리 할당 추적, Detached DOM tree 파악 기법 [9, 12, 33]. -- [[React DevTools Profiler]] +- [[React DevTools Profiler|React DevTools Profiler]] - 연결 이유: React 특유의 렌더링 사이클과 성능 병목을 시각화하는 핵심 도구. - 이 개념을 통해 더 깊게 이해할 수 있는 부분: 컴포넌트 렌더링 소요 시간, 렌더링 발생 원인(Props/State 변경 여부 판별) [5, 14]. #### [관계 유형 B (프로덕션 관측성 및 모니터링)] -- [[Frontend Cloud Logging Tools]] +- Frontend Cloud Logging Tools - 연결 이유: Sentry, LogRocket, Datadog RUM, SigNoz 등 배포 이후 발생하는 성능 저하와 버그를 추적하는 플랫폼. - 이 개념을 통해 더 깊게 이해할 수 있는 부분: 프로덕션 레벨에서의 세션 리플레이, 자동 에러 그룹화, 엔드투엔드 분산 트레이싱, Core Web Vitals 추적 [7, 8, 20, 21, 34]. #### [관계 유형 C (아키텍처 및 안티패턴)] -- [[JavaScript Memory Leaks]] +- JavaScript Memory Leaks - 연결 이유: 애플리케이션 성능을 점진적으로 파괴하는 현상으로 메모리 팽창, 가비지 컬렉션 등과 연관. - 이 개념을 통해 더 깊게 이해할 수 있는 부분: 클로저 잔류 참조(Closure-Retained References), 해제되지 않은 이벤트 리스너의 동작 메커니즘 [2, 10, 35]. -- [[React Re-render Optimization]] +- React Re-render Optimization - 연결 이유: React의 렌더링 특성상 발생하는 메인 스레드 블로킹 문제를 해결하기 위한 코드 레벨 기법. - 이 개념을 통해 더 깊게 이해할 수 있는 부분: 참조 안정성(Reference stability), 익명 함수의 부작용, `useMemo` 및 `useCallback`의 올바른 활용법 [36-38]. @@ -63,9 +63,9 @@ React 애플리케이션에서는 상태(State), 프로퍼티(Props), 컨텍스 ### Adjacent Topics -- [[Core Web Vitals]] +- [[Core Web Vitals|Core Web Vitals]] - 확장 방향: 프론트엔드 성능 최적화와 디버깅의 궁극적인 성과 지표이자 기준점이 되는 실제 사용자 체감 속도 지표(LCP, FID, INP, CLS 등) 심층 탐구 [8]. -- [[React Server Components (RSC)]] +- [[React Server Components (RSC)|React Server Components (RSC)]] - 확장 방향: Next.js 환경에서 클라이언트 측 자바스크립트 번들 사이즈 자체를 줄이고 상호작용 없는 UI를 서버에서 렌더링함으로써 근본적인 클라이언트 디버깅 요소 및 리렌더링 비용을 제거하는 아키텍처 [42, 43]. --- diff --git a/10_Wiki/Development/Index.md b/10_Wiki/Development/Index.md index b8a55e54..b03aa5f6 100644 --- a/10_Wiki/Development/Index.md +++ b/10_Wiki/Development/Index.md @@ -1,7 +1,7 @@ # Index: Development ## 📁 Subcategories -- [[UI_Components/Index|UI_Components]] +- UI_Components ## 📝 Documents -- [[Homepage_React_Best_Practices]] +- [[Homepage_React_Best_Practices|Homepage_React_Best_Practices]] diff --git a/10_Wiki/Development/Large-scale Application Refactoring.md b/10_Wiki/Development/Large-scale Application Refactoring.md index 57dc756e..3206b88e 100644 --- a/10_Wiki/Development/Large-scale Application Refactoring.md +++ b/10_Wiki/Development/Large-scale Application Refactoring.md @@ -1,4 +1,4 @@ -# [[Large-scale Application Refactoring]] +# [[Large-scale Application Refactoring|Large-scale Application Refactoring]] ## 📌 Brief Summary 대규모 애플리케이션 리팩토링은 코드의 동작 방식을 보존하면서 내부 구조를 개선하여 오래된 코드베이스의 유지보수성과 확장성을 회복하는 과정이다 [1]. 이는 단순히 코드를 '수정'하는 것이 아니라, 복잡한 비즈니스 로직을 분리하고 구조적 결합도를 낮추는 것을 목표로 한다 [2]. 성공적인 리팩토링을 위해서는 점진적인 접근 방식, 엄격한 아키텍처 적용, 그리고 코드 변경을 뒷받침할 수 있는 테스트 구축이 필수적이다 [1, 3]. @@ -22,20 +22,20 @@ ### Related Concepts #### [아키텍처 및 기반 원칙] -- [[Feature-Sliced Design]] +- [[Feature-Sliced Design|Feature-Sliced Design]] - 연결 이유: 대규모 코드베이스의 스파게티화를 해결하고, 도메인/기능 중심의 단방향 의존성 규칙을 부여하여 확장 가능한 구조를 만드는 리팩토링의 궁극적 목표 모델이기 때문이다 [7, 22]. - 이 개념을 통해 더 깊게 이해할 수 있는 부분: 기능(Feature)과 계층(Layer)을 어떻게 나누고 캡슐화하여 서로 간의 의존성 결합을 끊어내는지에 대한 실무적 아키텍처 구조 [6, 23]. -- [[SOLID Principles]] +- [[SOLID Principles|SOLID Principles]] - 연결 이유: 단일 책임 원칙(SRP) 등을 통해 거대한 컴포넌트가 가지는 여러 책임을 분리하고, 함수나 컴포넌트를 테스트 가능하게 잘게 쪼개는 리팩토링의 핵심 이론적 배경이기 때문이다 [24, 25]. - 이 개념을 통해 더 깊게 이해할 수 있는 부분: 기능적 컴포넌트 내에서 인터페이스(Props)를 어떻게 분리하고, 확장에 열려있으면서 수정에는 닫힌 코드 작성을 구현하는 방법 [25, 26]. #### [구현 및 활용 도구] -- [[Unit Testing]] +- Unit Testing - 연결 이유: 레거시 코드 구조를 변경할 때 기능이 망가지지 않았음을 보장하는 첫 번째 단계이자 가장 중요한 안전망 역할을 수행하기 때문이다 [3, 12]. - 이 개념을 통해 더 깊게 이해할 수 있는 부분: 코드를 어떻게 더 작고 논리적인 블록 단위로 나누어(Triangulation) 의존성 없이 독립적으로 검증할 수 있는지에 대한 방법론 [9, 12]. -- [[Custom Hooks]] +- Custom Hooks - 연결 이유: 리액트 컴포넌트 내부에 복잡하게 얽힌 상태와 사이드 이펙트 로직을 외부로 추출하는 리팩토링의 주된 단위이자 도구이기 때문이다 [9]. - 이 개념을 통해 더 깊게 이해할 수 있는 부분: UI 렌더링 책임과 비즈니스 데이터 처리 책임을 어떻게 물리적으로 격리하여 코드 재사용성을 높일 수 있는지의 원리 [9, 10]. @@ -57,9 +57,9 @@ ### Adjacent Topics -- [[Web Performance Optimization]] +- [[Web Performance Optimization|Web Performance Optimization]] - 확장 방향: 리팩토링 작업과 병행하여 번들 사이즈 감소(코드 스플리팅), 리렌더링 최적화, 불필요한 렌더 블로킹 제거 등을 통해 애플리케이션의 런타임 및 로딩 속도를 향상하는 전략적 기법을 탐구한다. -- [[State Management Fragmentation]] +- State Management Fragmentation - 확장 방향: 레거시 앱의 거대한 단일 전역 상태를 분석하여 로컬 컴포넌트 상태, 전역 UI 상태, 서버 캐시 상태, URL 상태 등으로 파편화 및 전문화하여 각각에 맞는 도구(Zustand, React Query 등)로 이관하는 설계 방법론을 조사한다. --- diff --git a/10_Wiki/Development/Lazy Loading.md b/10_Wiki/Development/Lazy Loading.md index 8756a85b..806ef27c 100644 --- a/10_Wiki/Development/Lazy Loading.md +++ b/10_Wiki/Development/Lazy Loading.md @@ -1,4 +1,4 @@ -# [[Lazy Loading]] +# [[Lazy Loading|Lazy Loading]] ## 📌 Brief Summary Lazy Loading은 리소스나 코드 청크를 애플리케이션 초기 구동 시 한 번에 로드하지 않고, 사용자가 실제로 필요로 하는 시점에 비동기적으로 불러오는 성능 최적화 기법입니다 [1, 2]. 프론트엔드 환경에서는 초기 JavaScript 번들 크기를 최대 20~70%까지 줄여 초기 페이지 로드 시간을 획기적으로 향상시킵니다 [3]. 주로 경로(Route) 기반 컴포넌트, 무거운 UI 위젯(차트 등), 뷰포트 하단의 이미지 등에 적용되어 앱의 전반적인 반응성과 Core Web Vitals 지표를 개선합니다 [4, 5]. @@ -19,20 +19,20 @@ Lazy Loading은 리소스나 코드 청크를 애플리케이션 초기 구동 ### Related Concepts #### [아키텍처/기반 기술] -- [[Code Splitting]] +- [[Code Splitting|Code Splitting]] - 연결 이유: Lazy Loading이 가능하도록 애플리케이션의 단일 JavaScript 번들을 여러 개의 작은 청크 단위로 나누는 근본적인 기반 기술이기 때문입니다 [2, 13]. - 이 개념을 통해 더 깊게 이해할 수 있는 부분: 모던 프론트엔드 환경에서 빌드 툴(Vite, Webpack)이 런타임 최적화를 위해 코드를 어떻게 분할하고 관리하는지 이해할 수 있습니다 [6, 7]. -- [[Dynamic Imports]] +- Dynamic Imports - 연결 이유: 자바스크립트 모듈을 파일의 최상단에서 정적으로 불러오지 않고, 실행 중에 비동기적으로 불러오기 위해 `import()` 문법을 사용하는 방식입니다 [1, 7]. - 이 개념을 통해 더 깊게 이해할 수 있는 부분: 라우트 전환이나 특정 이벤트 발생 시점에 필요한 코드만 네트워크로 호출하는 런타임 메커니즘을 파악할 수 있습니다 [7]. #### [구현/활용 도구] -- [[React Suspense]] +- React Suspense - 연결 이유: `React.lazy()`를 이용해 지연 로딩을 수행할 때, 청크가 로드되기 전까지 렌더링을 일시 중지하고 Fallback UI를 화면에 그려주는 핵심 컴포넌트입니다 [7, 8]. - 이 개념을 통해 더 깊게 이해할 수 있는 부분: 비동기 UI 로딩 시 사용자 경험(UX)을 부드럽게 유지하기 위한 렌더링 제어 및 로딩 상태 설계 패턴을 배울 수 있습니다 [8, 11]. -- [[Vite manualChunks]] +- Vite manualChunks - 연결 이유: Vite를 통해 빌드할 때, 변경이 잦지 않은 무거운 벤더 라이브러리(React 코어 등)를 Lazy Loading의 청크 분할 전략과 결합해 별도 파일로 독립시키는 환경 설정입니다 [7, 14]. - 이 개념을 통해 더 깊게 이해할 수 있는 부분: 브라우저 캐싱 전략을 극대화하고, 초기 번들 용량 경고("Large Chunks") 문제를 해결하는 구체적인 번들러 최적화 방법을 학습할 수 있습니다 [7, 15]. @@ -54,9 +54,9 @@ Lazy Loading은 리소스나 코드 청크를 애플리케이션 초기 구동 ### Adjacent Topics -- [[Core Web Vitals]] +- [[Core Web Vitals|Core Web Vitals]] - 확장 방향: 지연 로딩이 검색 엔진 최적화(SEO) 및 사용자 경험 지표인 FCP, LCP(Largest Contentful Paint), INP(Interaction to Next Paint) 수치를 실제로 얼마나 개선하는지 측정 및 분석하는 관점으로 확장할 수 있습니다 [3, 23, 24]. -- [[Server Components (RSC)]] +- Server Components (RSC) - 확장 방향: 클라이언트 사이드의 자바스크립트 크기를 줄이기 위한 또 다른 현대적 패러다임으로, 클라이언트에서 실행될 코드를 아예 서버에서 렌더링하고 HTML로만 보내는 방식과 Lazy Loading과의 역할을 비교/대조합니다 [20, 21]. --- diff --git a/10_Wiki/Development/Next.js App Router.md b/10_Wiki/Development/Next.js App Router.md index 43ddac1f..ae9bcbe5 100644 --- a/10_Wiki/Development/Next.js App Router.md +++ b/10_Wiki/Development/Next.js App Router.md @@ -1,4 +1,4 @@ -# [[Next.js App Router]] +# [[Next.js App Router|Next.js App Router]] ## 📌 Brief Summary Next.js App Router는 Next.js(버전 13 이후)에서 도입된 최신 라우팅 및 아키텍처 시스템으로, React Server Components(RSC)를 기본적으로 지원하여 클라이언트 측 자바스크립트 전송량을 줄이고 초기 로딩 속도를 향상시킵니다 [1, 2]. 이 시스템은 `app` 디렉토리를 기반으로 동작하며, `page.js`, `layout.js`와 같은 특수 파일들을 통해 직관적이고 구조화된 라우팅을 제공합니다 [3, 4]. @@ -15,15 +15,15 @@ Next.js App Router는 Next.js(버전 13 이후)에서 도입된 최신 라우팅 ### Related Concepts -- [[React Server Components]] +- [[React Server Components|React Server Components]] - 연결 이유: Next.js App Router 아키텍처의 핵심 기반으로, 번들 크기를 줄이고 데이터 페칭 성능을 향상시키는 역할을 합니다 [1, 2]. - 이 개념을 통해 더 깊게 이해할 수 있는 부분: 클라이언트 측 렌더링 코드와 서버 측 렌더링 코드 간의 명확한 경계 구분 및 Hydration 최소화 전략 [6, 7, 9]. -- [[Route Groups]] +- Route Groups - 연결 이유: App Router 내에서 URL 경로를 변경하지 않고도 폴더 구조를 논리적으로 조직할 수 있게 해주는 핵심 폴더 라우팅 패턴입니다 [5, 11]. - 이 개념을 통해 더 깊게 이해할 수 있는 부분: 복잡한 애플리케이션에서 별도의 레이아웃을 가진 섹션(예: 마케팅 페이지와 상점 페이지)을 충돌 없이 독립적으로 분리하는 방법 [5, 11]. -- [[Concurrent Rendering]] +- [[Concurrent Rendering|Concurrent Rendering]] - 연결 이유: Next.js App Router가 기본적으로 완벽하게 지원하는 React의 렌더링 메커니즘으로, 렌더링 작업을 일시 중지, 중단 및 재개할 수 있게 해줍니다 [10, 12]. - 이 개념을 통해 더 깊게 이해할 수 있는 부분: `useTransition` 및 `useDeferredValue` 훅을 통해 무거운 렌더링 시에도 사용자 입력 반응성(UX)을 높게 유지하는 원리 [13, 14]. @@ -45,9 +45,9 @@ Next.js App Router는 Next.js(버전 13 이후)에서 도입된 최신 라우팅 ### Adjacent Topics -- [[Code Splitting & Lazy Loading]] +- Code Splitting & Lazy Loading - 확장 방향: App Router의 Server Components뿐만 아니라, `React.lazy`와 `Suspense`를 결합하여 라우트 및 무거운 컴포넌트(차트, 에디터 등)를 필요한 순간에만 로드하도록 최적화하는 기법으로의 이해 확장 [20, 21]. -- [[React Context API Optimization]] +- React Context API Optimization - 확장 방향: App Router 환경 하의 클라이언트 컴포넌트 내에서 불가피하게 전역 상태를 쓸 때, Context의 광범위한 리렌더링 이슈를 회피하기 위해 컨텍스트를 분리하거나 Zustand, Jotai 등의 외부 라이브러리를 도입하는 방향으로 학습 확장 [22-24]. --- diff --git a/10_Wiki/Development/Prop Drilling.md b/10_Wiki/Development/Prop Drilling.md index aea73383..bf6e5f38 100644 --- a/10_Wiki/Development/Prop Drilling.md +++ b/10_Wiki/Development/Prop Drilling.md @@ -1,4 +1,4 @@ -# [[Prop Drilling]] +# [[Prop Drilling|Prop Drilling]] ## 📌 Brief Summary Prop Drilling은 실제로 해당 데이터가 필요하지 않은 여러 중간 컴포넌트들을 거쳐 계층적으로 데이터를 전달하는 안티 패턴을 의미합니다 [1]. 주로 깊게 중첩된 하위 컴포넌트에 상태나 데이터를 전달해야 할 때 발생합니다 [1]. React 생태계에서는 이 문제를 해결하기 위해 내장된 Context API나 외부 상태 관리 라이브러리를 활용합니다 [1, 2]. @@ -19,15 +19,15 @@ Prop Drilling을 피하기 위해 가장 먼저 고려되는 Context API는 빈 ### Related Concepts #### [기반 기술/해결책] -- [[Context API]] +- [[Context API|Context API]] - 연결 이유: Prop Drilling 문제를 해결하기 위해 React에서 자체적으로 도입한 내장 데이터 전달 메커니즘이기 때문입니다 [1]. - 이 개념을 통해 더 깊게 이해할 수 있는 부분: props를 일일이 넘기지 않고 컴포넌트 트리에 데이터를 브로드캐스트하는 원리와 그에 따른 리렌더링 한계를 이해할 수 있습니다 [6, 12]. #### [상태 관리 도구/대안] -- [[Zustand]] +- Zustand - 연결 이유: Prop Drilling의 대안인 Context API가 갖는 리렌더링 성능 문제를 극복할 수 있는 경량 상태 관리 라이브러리이기 때문입니다 [2, 7]. - 이 개념을 통해 더 깊게 이해할 수 있는 부분: 선택자(Selector) 패턴을 활용해 필요한 상태의 변경에만 컴포넌트를 리렌더링하도록 스마트하게 구독(subscribe)하는 구조를 이해할 수 있습니다 [7, 13]. -- [[Redux]] +- [[Redux|Redux]] - 연결 이유: 대규모 애플리케이션에서 Prop Drilling을 방지하고 상태를 일관성 있게 관리하기 위한 산업 표준 상태 컨테이너 도구이기 때문입니다 [5, 14]. - 이 개념을 통해 더 깊게 이해할 수 있는 부분: 파생 선택자(derived selectors)가 존재함으로써 Prop Drilling 없이 복잡한 상태와 비동기 로직을 어떻게 효율적으로 다루는지 파악할 수 있습니다 [5, 15]. @@ -49,7 +49,7 @@ Prop Drilling을 피하기 위해 가장 먼저 고려되는 Context API는 빈 ### Adjacent Topics -- [[Re-renders]] +- Re-renders - 확장 방향: Prop Drilling을 피하기 위한 수단(Context API)이 초래하는 부작용인 불필요한 렌더링을 방지하기 위한 메모이제이션(`React.memo`, `useMemo`, `useCallback`) 등 React 런타임 성능 최적화 기법으로의 이해 확장이 필요합니다 [3, 6, 23]. --- diff --git a/10_Wiki/Development/Re-renders Optimization.md b/10_Wiki/Development/Re-renders Optimization.md index be2c3213..ea2a1643 100644 --- a/10_Wiki/Development/Re-renders Optimization.md +++ b/10_Wiki/Development/Re-renders Optimization.md @@ -1,4 +1,4 @@ -# [[Re-renders Optimization]] +# [[Re-renders Optimization|Re-renders Optimization]] ## 📌 Brief Summary Re-renders Optimization은 React 애플리케이션에서 불필요한 컴포넌트 업데이트를 최소화하여 성능, 반응성 및 사용자 경험을 향상시키는 과정입니다 [1, 2]. 주로 상태(state), 속성(props), 컨텍스트(context)의 변경으로 인해 발생하는 과도한 렌더링을 타겟으로 합니다 [3]. 이를 위해 수동 메모이제이션, 상태 관리 최적화, 가상화 기법, 그리고 React Compiler와 같은 최신 자동화 도구를 활용하여 병목 현상을 방지합니다 [4-6]. @@ -18,15 +18,15 @@ Re-renders Optimization은 React 애플리케이션에서 불필요한 컴포넌 ## 🔗 Knowledge Connections ### Related Concepts -- [[React Compiler]] +- [[React Compiler|React Compiler]] - 연결 이유: 개발자가 수동으로 리렌더링을 최적화하던 기존 방식을 대체하여, 빌드 타임에 자동으로 메모이제이션을 적용하는 2025년 기준 핵심 기술이기 때문입니다 [4]. - 이 개념을 통해 더 깊게 이해할 수 있는 부분: 컴포넌트 전체가 아닌 개별 JSX 요소와 연산이 어떻게 독립적으로 캐싱되는지의 원리와 서드파티 라이브러리 호환성 한계 [19, 26]. -- [[State Management (Zustand vs Context)]] +- State Management (Zustand vs Context) - 연결 이유: 불필요한 전체 리렌더링을 유발하는 Context API의 구조적 한계를 Zustand의 선택자(Selector) 패턴이 어떻게 극복하여 렌더링을 최적화하는지 설명하기 때문입니다 [13, 17]. - 이 개념을 통해 더 깊게 이해할 수 있는 부분: 자주 변경되는 전역 상태 관리에서 React 렌더링 사이클 외부의 스토어가 어떻게 컴포넌트 렌더링을 정밀하게 제어하는지 [17, 27]. -- [[Memoization (useMemo, useCallback)]] +- Memoization (useMemo, useCallback) - 연결 이유: React의 얕은 비교(Shallow comparison) 특성을 극복하고 참조 동등성을 유지하여 `React.memo`와 결합한 리렌더링 최적화의 기반이 되기 때문입니다 [10]. - 이 개념을 통해 더 깊게 이해할 수 있는 부분: 무분별한 메모이제이션이 오히려 렌더링 비용보다 큰 성능 오버헤드를 유발하는 이유와 올바른 적용 조건 [11, 12]. @@ -45,9 +45,9 @@ Re-renders Optimization은 React 애플리케이션에서 불필요한 컴포넌 - **My Project Relevance:** 현재 유지보수하거나 새로 구축하는 React 프로젝트에서 성능 저하를 겪고 있다면, 익명 함수 인라인 작성 패턴을 수정하고, 불필요한 거대 Context를 분리하며, 식별 가능한 병목 지점에 프로파일링 기반의 메모이제이션을 적용해 즉각적인 성능 개선을 이룰 수 있습니다 [5, 15, 22]. ### Adjacent Topics -- [[Core Web Vitals (INP, FCP, TTI)]] +- Core Web Vitals (INP, FCP, TTI) - 확장 방향: 프론트엔드 코드의 리렌더링 최적화가 실제 사용자의 체감 성능을 측정하는 지표(특히 Interaction to Next Paint)에 브라우저 레벨에서 어떤 영향을 미치는지 확장하여 조사합니다 [2, 33]. -- [[Code Splitting & Lazy Loading]] +- Code Splitting & Lazy Loading - 확장 방향: 컴포넌트 업데이트 시점(리렌더링)의 최적화뿐만 아니라, 컴포넌트 최초 로드 시점의 번들 크기를 줄여 초기 렌더링 성능을 극대화하는 `React.lazy`와 동적 임포트 기법을 함께 학습합니다 [34]. --- diff --git a/10_Wiki/Development/React 18 Concurrent Features.md b/10_Wiki/Development/React 18 Concurrent Features.md index a5c653e9..5d3d3d09 100644 --- a/10_Wiki/Development/React 18 Concurrent Features.md +++ b/10_Wiki/Development/React 18 Concurrent Features.md @@ -1,4 +1,4 @@ -# [[React 18 Concurrent Features]] +# [[React 18 Concurrent Features|React 18 Concurrent Features]] ## 📌 Brief Summary React 18 Concurrent Features(동시성 기능)는 업데이트가 발생하는 시점과 방식을 제어하여 응답성을 희생하지 않으면서도 더 매끄러운 앱을 구축할 수 있게 해주는 기능이다 [1]. 이 렌더링 모델은 React가 렌더링 작업을 일시 중지(pause), 중단(interrupt), 재개(resume)할 수 있도록 허용하여 중요도에 따른 업데이트 우선순위 지정을 가능하게 한다 [2]. 대표적인 훅(Hook)인 `useTransition`과 `useDeferredValue`를 통해 느린 렌더링이 중요한 사용자 상호작용을 차단하지 못하게 방지할 수 있다 [3, 4]. @@ -16,13 +16,13 @@ React 18 Concurrent Features(동시성 기능)는 업데이트가 발생하는 ## 🔗 Knowledge Connections ### Related Concepts -- [[useTransition]] +- [[useTransition|useTransition]] - 연결 이유: React 18 동시성 기능의 핵심 훅으로, 비긴급 업데이트를 지연시키는 구체적인 구현체이다 [3]. - 이 개념을 통해 더 깊게 이해할 수 있는 부분: 라이브 검색이나 필터링 시 렌더링 병목 현상을 방지하고, 어떻게 비긴급 작업과 긴급 상호작용(타이핑 등)을 분리하는지 이해할 수 있다 [3]. -- [[useDeferredValue]] +- [[useDeferredValue|useDeferredValue]] - 연결 이유: 값의 읽기를 지연시켜 UI 업데이트와 연산 부하를 분리하는 동시성 기능의 또 다른 핵심 훅이다 [4]. - 이 개념을 통해 더 깊게 이해할 수 있는 부분: 즉각적인 UI 반영이 필요한 부분과 지연시켜도 무방한 무거운 계산(derived data)을 어떻게 나누어 처리하는지 알 수 있다 [4]. -- [[Suspense]] +- Suspense - 연결 이유: 동시성 훅(`useTransition` 등)과 결합하여 백그라운드 렌더링이 진행되거나 데이터가 로드될 때 스켈레톤(fallback UI)을 보여줄 수 있도록 설계된 기능이다 [4]. - 이 개념을 통해 더 깊게 이해할 수 있는 부분: 지연 중인 렌더링 상태에서 사용자의 경험(UX)을 어떻게 부드럽게 이어갈 수 있는지 이해할 수 있다 [4]. @@ -41,9 +41,9 @@ React 18 Concurrent Features(동시성 기능)는 업데이트가 발생하는 - **My Project Relevance:** 현재 진행 중인 프로젝트에서 데이터가 많은 차트나 테이블 필터링 시 UI가 끊기는(Jank) 현상이 있다면, 이 동시성 기능 훅을 도입하여 즉각적인 클릭/입력 응답성을 확보할 수 있다 [3, 4]. ### Adjacent Topics -- [[React Performance Optimization]] +- [[React Performance Optimization|React Performance Optimization]] - 확장 방향: 동시성 렌더링 외에도 불필요한 리렌더링 자체를 막는 `React.memo`, `useCallback`, `useMemo` 활용법과 같은 다양한 React 성능 최적화 기법 전반으로 지식을 확장할 수 있다 [9-11]. -- [[Server Components]] +- [[Server Components|Server Components]] - 확장 방향: Next.js에서 동시성 기능과 함께 성능 향상의 양대 축을 이루는 기능으로, 클라이언트 측 JavaScript를 전송하지 않고 서버에서 렌더링을 완료하여 번들 크기를 줄이는 전략을 학습할 수 있다 [12, 13]. --- diff --git a/10_Wiki/Development/React Application Scaling.md b/10_Wiki/Development/React Application Scaling.md index 3baf9301..2acb2bf3 100644 --- a/10_Wiki/Development/React Application Scaling.md +++ b/10_Wiki/Development/React Application Scaling.md @@ -1,4 +1,4 @@ -# [[React Application Scaling]] +# [[React Application Scaling|React Application Scaling]] ## 📌 Brief Summary 리액트 애플리케이션 스케일링(React Application Scaling)은 애플리케이션의 크기와 복잡성이 증가함에 따라 발생하는 아키텍처, 성능, 상태 관리, 그리고 협업 문제를 체계적으로 해결하는 과정입니다 [1-3]. 이는 단순히 렌더링 속도를 높이는 것을 넘어, 비즈니스 로직과 UI의 결합을 막고, 예측 가능한 폴더 구조를 도입하며, 불필요한 리렌더링과 번들 크기를 최적화하는 것을 포함합니다 [2-5]. 결과적으로 대규모 팀이 안정적이고 유지보수하기 쉬운 프론트엔드 시스템을 구축할 수 있도록 돕는 핵심 엔지니어링 패러다임입니다 [3, 6]. @@ -24,6 +24,6 @@ ### Related Concepts #### [아키텍처 및 폴더 구조 (Architecture & Structure)] -- [[Feature-Sliced Design (FSD)]] +- [[Feature-Sliced Design (FSD)|Feature-Sliced Design (FSD)]] - 연결 이유: 확장 가능한 리액트 앱을 구축하기 위한 핵심 도메인 주도 아키텍처 방법론입니다. - 이 개념을 통해 더 깊게 이해할 수 있는 부분: 기능, 위젯, 엔티티를 분리하고 단방향 의존성 규칙을 강제하여 결 \ No newline at end of file diff --git a/10_Wiki/Development/React Codebase Refactoring.md b/10_Wiki/Development/React Codebase Refactoring.md index 53140358..3b473bad 100644 --- a/10_Wiki/Development/React Codebase Refactoring.md +++ b/10_Wiki/Development/React Codebase Refactoring.md @@ -1,4 +1,4 @@ -# [[React Codebase Refactoring]] +# [[React Codebase Refactoring|React Codebase Refactoring]] ## 📌 Brief Summary React 코드베이스 리팩토링은 기존 앱의 외부 동작을 변경하지 않으면서 유지보수성, 성능, 가독성을 향상시키기 위해 코드를 재설계하고 정리하는 과정입니다. 대규모 React 앱에서 자주 발생하는 논리 결합, 불필요한 재렌더링, 전역 상태의 남용 등의 아키텍처 문제를 해결하는 데 중점을 둡니다. 성공적인 리팩토링을 위해서는 단위 테스트로 안전망을 확보한 후, 컴포넌트 책임 분리, TypeScript 도입, 상태 관리 도구의 현대화를 점진적으로 수행하는 것이 권장됩니다 [1-3]. @@ -22,21 +22,21 @@ React 코드베이스 리팩토링은 기존 앱의 외부 동작을 변경하 ### Related Concepts #### [관계 유형 A (아키텍처/기반 기술)] -- [[Feature-Sliced Design]] +- [[Feature-Sliced Design|Feature-Sliced Design]] - 연결 이유: 리팩토링 과정에서 기술 단위(Component, Hooks 등)로 흩어진 기존 폴더 구조를 기능(Feature) 중심으로 모듈화하고 재편할 때 기준이 되는 현대적인 프론트엔드 아키텍처론입니다 [22, 23]. - 이 개념을 통해 더 깊게 이해할 수 있는 부분: 확장성을 위한 단방향 의존성 규칙과 도메인 중심의 코드 캡슐화 설계 방법. -- [[SOLID Principles]] +- [[SOLID Principles|SOLID Principles]] - 연결 이유: 거대한 React 컴포넌트를 작게 분리하고 인터페이스를 구성할 때, 단일 책임 원칙(SRP)과 같은 클린 코드의 기반 지침을 제공합니다 [6, 24]. - 이 개념을 통해 더 깊게 이해할 수 있는 부분: 리액트 컴포넌트의 책임을 올바르게 분리하고 유지보수하기 쉬운 추상화를 설계하는 기준. #### [관계 유형 B (구현/활용 도구)] -- [[TanStack Query]] +- TanStack Query - 연결 이유: 기존의 비효율적인 Context API나 거대한 Redux 스토어를 리팩토링할 때, 서버 상태(캐싱, 동기화 등)를 깔끔하게 분리해 주는 핵심 도구입니다 [10, 11]. - 이 개념을 통해 더 깊게 이해할 수 있는 부분: 서버 데이터 페칭 로직의 분리와 컴포넌트 내 복잡한 상태 관리 감소 방법. -- [[Zustand]] +- Zustand - 연결 이유: 불필요한 재렌더링을 유발하는 기존의 Context API 기반 상태 관리를 리팩토링할 때 주로 도입되는 경량 클라이언트 상태 관리 라이브러리입니다 [1, 25]. - 이 개념을 통해 더 깊게 이해할 수 있는 부분: 상태 선택자(Selector)를 통한 렌더링 최적화 구조 및 보일러플레이트 없는 상태 관리 로직 작성법. -- [[Unit Testing]] +- Unit Testing - 연결 이유: 리팩토링 시 코드를 변경하더라도 기존의 비즈니스 로직이 파괴되지 않음을 보장하기 위해 리팩토링 작업에 선행되어야 하는 기술입니다 [2, 5]. - 이 개념을 통해 더 깊게 이해할 수 있는 부분: 기존 코드를 검증 가능한 형태로 쪼개고 안전성을 확보하는 실질적인 엔지니어링 절차. @@ -55,9 +55,9 @@ React 코드베이스 리팩토링은 기존 앱의 외부 동작을 변경하 - **My Project Relevance:** 현재 유지보수하고 있는 복잡한 레거시 React 프로젝트의 성능 및 유지보수성 저하 원인을 분석하고, 컴포넌트 분리와 상태 관리 라이브러리(Zustand, React Query) 교체 작업을 체계적으로 기획할 때 직접 적용할 수 있습니다. ### Adjacent Topics -- [[Web Performance Optimization]] +- [[Web Performance Optimization|Web Performance Optimization]] - 확장 방향: 리팩토링의 궁극적 결과물 중 하나인 초기 로딩 속도 향상, 렌더링 최적화, 그리고 불필요한 번들 사이즈를 줄이는 코드 스플리팅(Code Splitting) 기법 등으로 개념을 확장하여 학습할 수 있습니다. -- [[Git Workflow & CI/CD]] +- Git Workflow & CI/CD - 확장 방향: 대규모 리팩토링 시 발생할 수 있는 브랜치 충돌 방지와 코드 리뷰 자동화, 그리고 Pull Request 과정에서 Visual Regression Testing을 연동하는 등 협업 전략으로 확장할 수 있습니다. --- diff --git a/10_Wiki/Development/React DevTools Profiler.md b/10_Wiki/Development/React DevTools Profiler.md index 0ed6a720..5f3faf59 100644 --- a/10_Wiki/Development/React DevTools Profiler.md +++ b/10_Wiki/Development/React DevTools Profiler.md @@ -1,4 +1,4 @@ -# [[React DevTools Profiler]] +# [[React DevTools Profiler|React DevTools Profiler]] ## 📌 Brief Summary React DevTools Profiler는 React 애플리케이션의 렌더링 성능을 측정하고 최적화 대상을 식별하기 위해 React DevTools에 내장된 프로파일링 및 디버깅 도구이다 [1]. 이 도구는 어떤 컴포넌트가 언제, 얼마나 오래 렌더링되었는지, 그리고 어떤 요인(props, state 변경 등)이 렌더링을 유발했는지 파악하는 데 사용된다 [1, 2]. 주로 로컬 개발 환경에서 성능 병목 현상을 식별하고 불필요한 리렌더링을 찾아내는 데 핵심적으로 활용된다 [3]. @@ -17,15 +17,15 @@ React DevTools Profiler는 React 애플리케이션의 렌더링 성능을 측 ### Related Concepts #### [관계 유형 A: 아키텍처/기반 기술] -- [[React Compiler]] +- [[React Compiler|React Compiler]] - 연결 이유: React Compiler가 빌드 타임에 주입한 자동 메모이제이션 로직의 성공 여부와 렌더링 스킵 결과를 Profiler를 통해 시각적으로 확인할 수 있다 [7-9]. - 이 개념을 통해 더 깊게 이해할 수 있는 부분: 명시적인 메모이제이션 코드 없이도 렌더링 성능이 최적화되는 원리와, 블랙박스화된 렌더링 메커니즘을 디버깅하는 방법 [9, 11]. #### [관계 유형 B: 구현/활용 도구] -- [[React.memo]] +- React.memo - 연결 이유: Profiler를 통해 특정 컴포넌트의 렌더링 빈도와 비용을 측정한 뒤, 그 결과에 따라 `React.memo` 적용이 성능 향상에 실질적인 도움이 될지 판단할 수 있다 [4]. - 이 개념을 통해 더 깊게 이해할 수 있는 부분: 얕은 비교(Shallow comparison)의 원리와 프로파일링 데이터에 기반한 전략적 메모이제이션 방법 [4, 12, 13]. -- [[useCallback & useMemo]] +- useCallback & useMemo - 연결 이유: Profiler에서 자식 컴포넌트가 참조(Reference) 변경 때문에 계속 리렌더링되는 것을 발견했다면, 이 훅들을 사용하여 참조 안정성(Reference stability)을 확보할 수 있다 [5, 14]. - 이 개념을 통해 더 깊게 이해할 수 있는 부분: 함수나 객체의 참조 동일성이 컴포넌트 렌더링 트리에 미치는 직접적인 영향 [14]. @@ -43,9 +43,9 @@ React DevTools Profiler는 React 애플리케이션의 렌더링 성능을 측 - **My Project Relevance:** 화면 내 대용량 리스트나 복잡한 필터를 조작할 때 발생하는 지연 현상(Jank)의 원인이 렌더링 시간 자체인지, 아니면 불필요한 연쇄 리렌더링 때문인지 진단하고 해결책을 마련한다 [21, 22]. ### Adjacent Topics -- [[why-did-you-render]] +- why-did-you-render - 확장 방향: Profiler와 결합하여 사용할 수 있는 라이브러리로, 실제 데이터 변경이 없음에도 불구하고 컴포넌트가 리렌더링된 '정확한 이유'를 콘솔에 경고 형태로 남겨주어 디버깅을 더욱 쉽게 만들어주는 도구에 대해 조사한다 [3, 23]. -- [[Chrome DevTools Performance Tab]] +- Chrome DevTools Performance Tab - 확장 방향: Profiler가 알려주는 React 내부의 렌더링 속도 이외에, 프레임 드롭이나 메인 스레드를 막는 무거운 자바스크립트 실행, 레이아웃 이동 등 브라우저 레벨의 전체적인 성능 분석으로 시야를 확장한다 [3, 23]. --- diff --git a/10_Wiki/Development/React Frontend Architecture.md b/10_Wiki/Development/React Frontend Architecture.md index 76200a99..9335c178 100644 --- a/10_Wiki/Development/React Frontend Architecture.md +++ b/10_Wiki/Development/React Frontend Architecture.md @@ -1,4 +1,4 @@ -# [[React Frontend Architecture]] +# [[React Frontend Architecture|React Frontend Architecture]] ## 📌 Brief Summary React 프론트엔드 아키텍처는 확장 가능하고 유지보수하기 쉬운 애플리케이션을 구축하기 위한 구조적 뼈대이자 조직화 방법론이다 [1, 2]. 기존의 기술적 파일 단위 분리에서 벗어나, 비즈니스 도메인과 기능(Feature-Based)을 중심으로 코드를 구성하여 결합도를 낮추고 응집도를 높이는 것을 목표로 한다 [3-5]. 이를 통해 무분별한 비즈니스 로직의 UI 누수를 막고 명확한 상태 소유권을 확립하며, 팀과 코드베이스가 성장함에 따라 시스템이 예측 가능하게 확장할 수 있도록 돕는다 [6-8]. @@ -23,18 +23,18 @@ React 프론트엔드 아키텍처는 확장 가능하고 유지보수하기 쉬 ### Related Concepts #### [아키텍처 및 디자인 패턴] -- [[Feature-Sliced Design]] +- [[Feature-Sliced Design|Feature-Sliced Design]] - 연결 이유: 현대 React 애플리케이션의 모듈화 및 계층화를 위해 고안된 가장 대표적이고 구체적인 프론트엔드 아키텍처 방법론이기 때문 [3, 13]. - 이 개념을 통해 더 깊게 이해할 수 있는 부분: 도메인 기반 분할, 단방향 의존성 규칙 적용 방법, 그리고 Public API를 통한 컴포넌트의 캡슐화 원리 [14, 16, 17]. -- [[SOLID Principles]] +- [[SOLID Principles|SOLID Principles]] - 연결 이유: 확장 가능한 프론트엔드 구조를 짜기 위해 클래스 기반 OOP를 넘어 React의 함수형 컴포넌트에도 적용해야 하는 근본적인 소프트웨어 설계 원칙이기 때문 [17, 48]. - 이 개념을 통해 더 깊게 이해할 수 있는 부분: 단일 책임 원칙(SRP)을 이용한 비대해진 컴포넌트의 리팩토링 방식 및 개방-폐쇄 원칙(OCP)을 활용한 UI 컴포넌트 합성(Composition) 전략 [25, 49]. #### [상태 관리 및 최적화 전략] -- [[State Management]] +- [[상태 관리(State Management)|State Management]] - 연결 이유: 아키텍처 내에서 데이터(서버 데이터, 로컬 상태, 전역 UI 상태)의 성격에 따라 책임과 저장소를 어떻게 나눌지 결정하는 핵심 분야이기 때문 [20, 50]. - 이 개념을 통해 더 깊게 이해할 수 있는 부분: Context API의 렌더링 한계를 돌파하기 위한 Zustand/Jotai의 Selector 패턴 작동 원리 및 TanStack Query를 활용한 서버 상태 격리 기법 [21, 43, 51]. -- [[Performance Optimization]] +- [[Performance Optimization|Performance Optimization]] - 연결 이유: 대규모 아키텍처가 실제로 사용자 브라우저에서 효율적으로 동작하기 위해 필수적으로 수반되어야 하는 성능 지표(Web Vitals) 관리 방법이기 때문 [52, 53]. - 이 개념을 통해 더 깊게 이해할 수 있는 부분: 지연 로딩(Lazy Loading) 및 코드 스플리팅을 통한 초기 번들 사이즈 최적화, 그리고 동시성 렌더링(Concurrent Rendering) 훅의 활용법 [54-56]. @@ -55,9 +55,9 @@ React 프론트엔드 아키텍처는 확장 가능하고 유지보수하기 쉬 ### Adjacent Topics -- [[Micro-Frontends]] +- [[마이크로 프론트엔드 (Micro Frontends)|Micro-Frontends]] - 확장 방향: 단일 React SPA 아키텍처의 한계를 넘어, 독립적으로 배포 및 관리 가능한 여러 프론트엔드 팀과 서비스를 하나로 조율하는 엔터프라이즈급 인프라 확장 관점으로 연결 [3, 63]. -- [[Observability and Monitoring]] +- Observability and Monitoring - 확장 방향: 설계한 아키텍처가 실제 프로덕션 환경에서 어떻게 동작하고 어디서 병목을 일으키는지 측정하기 위한 구조적 로깅, 성능 프로파일링(Web Vitals), 그리고 Sentry를 활용한 세션 모니터링 기법으로 확장 [64-66]. --- diff --git a/10_Wiki/Development/React Scalability.md b/10_Wiki/Development/React Scalability.md index 6bd3e18d..c7a89ec4 100644 --- a/10_Wiki/Development/React Scalability.md +++ b/10_Wiki/Development/React Scalability.md @@ -1,4 +1,4 @@ -# [[React Scalability]] +# [[React Scalability|React Scalability]] ## 📌 Brief Summary React Scalability(React 확장성)는 기능, 팀 규모, 비즈니스 로직의 복잡성이 증가함에 따라 애플리케이션의 성능, 유지보수성, 예측 가능한 성장을 유지하는 능력을 의미합니다. 단순히 컴포넌트를 렌더링하는 것을 넘어, 결합도를 낮추고 응집도를 높이는 아키텍처 설계, 상태 관리의 최적화, 그리고 코드 스플리팅과 렌더링 성능 최적화를 포괄합니다. 확장 가능한 React 시스템은 명확한 폴더 구조(예: Feature-Sliced Design)와 엄격한 관심사 분리를 통해 코드베이스가 자체적인 무게로 인해 붕괴되는 것을 방지합니다. [1-4] @@ -20,21 +20,21 @@ React Scalability(React 확장성)는 기능, 팀 규모, 비즈니스 로직의 ### Related Concepts #### [아키텍처/기반 기술] -- [[Feature-Sliced Design]] +- [[Feature-Sliced Design|Feature-Sliced Design]] - 연결 이유: React의 한계인 구체적인 아키텍처 부재를 해결하기 위해 설계된 대규모 프론트엔드 방법론입니다. - 이 개념을 통해 더 깊게 이해할 수 있는 부분: 레이어(Layer) 간의 단방향 의존성 원칙과 Public API를 활용한 모듈의 캡슐화 및 결합도 최소화 방법. -- [[SOLID Principles]] +- [[SOLID Principles|SOLID Principles]] - 연결 이유: 확장 가능하고 유지보수가 쉬운 React 코드를 작성하기 위한 핵심 소프트웨어 엔지니어링 원칙입니다. - 이 개념을 통해 더 깊게 이해할 수 있는 부분: 거대한 컴포넌트를 단일 책임 원칙(SRP)에 따라 작은 기능으로 분리하고, 커스텀 훅을 활용하여 로직을 재사용하는 구조적 사고. #### [구현/활용 도구] -- [[State Management Libraries (Redux, Zustand, Context API)]] +- State Management Libraries (Redux, Zustand, Context API) - 연결 이유: 애플리케이션의 크기와 상태 업데이트 빈도에 따라 적절한 도구를 선택하는 것은 확장성에 지대한 영향을 미칩니다. - 이 개념을 통해 더 깊게 이해할 수 있는 부분: 불필요한 리렌더링 방지를 위한 Selector 패턴의 동작 원리와, 대규모 프로젝트에서 강제되는 상태 관리 아키텍처의 중요성. -- [[Code Splitting & Lazy Loading]] +- Code Splitting & Lazy Loading - 연결 이유: 코드가 비대해짐에 따라 발생하는 성능 저하(번들 크기 증가)를 해결하기 위한 핵심 런타임 최적화 기법입니다. - 이 개념을 통해 더 깊게 이해할 수 있는 부분: `React.lazy`와 Vite의 `manualChunks`를 이용한 번들 크기 축소 및 브라우저 캐싱 전략. -- [[React Error Boundaries]] +- React Error Boundaries - 연결 이유: 대규모 앱에서 하나의 결함 있는 컴포넌트로 인해 전체 애플리케이션이 붕괴되는 것을 막아주는 안전 장치입니다. - 이 개념을 통해 더 깊게 이해할 수 있는 부분: 런타임 렌더링 에러를 격리(Isolate)하고 폴백(Fallback) UI를 제공하여 시스템 복원력을 높이는 방법. @@ -56,11 +56,11 @@ React Scalability(React 확장성)는 기능, 팀 규모, 비즈니스 로직의 ### Adjacent Topics -- [[Server Components (Next.js)]] +- Server Components (Next.js) - 확장 방향: 클라이언트 측으로 전송되는 JavaScript 번들 자체를 제거하여 하이드레이션(Hydration) 오버헤드를 줄이고 확장성과 성능을 동시에 잡는 최신 렌더링 패러다임. -- [[Memory Leak Detection in JavaScript]] +- Memory Leak Detection in JavaScript - 확장 방향: 확장 가능한 애플리케이션에서 장시간 사용 시 성능을 저하시키는 Detached DOM Nodes나 이벤트 리스너 누수 등을 Chrome DevTools Heap Snapshot을 통해 디버깅하는 방법. -- [[Git Branching Workflows for Small & Large Teams]] +- Git Branching Workflows for Small & Large Teams - 확장 방향: 규모가 확장되는 프론트엔드 팀이 충돌 없이 코드를 통합하기 위해 사용하는 GitHub Flow, Trunk-Based Development 및 PR(Pull Request) 리뷰 에티켓. --- diff --git a/10_Wiki/Development/React.lazy().md b/10_Wiki/Development/React.lazy().md index afb49c8c..be9abef2 100644 --- a/10_Wiki/Development/React.lazy().md +++ b/10_Wiki/Development/React.lazy().md @@ -1,4 +1,4 @@ -# [[React.lazy()]] +# [[React.lazy()|React.lazy()]] ## 📌 Brief Summary `React.lazy()`는 리액트(React)에서 컴포넌트를 필요한 시점에 동적으로 불러올 수 있게 해주는 내장 함수입니다 [1]. 이 기능을 동적 임포트(Dynamic Imports)와 결합하면 거대한 자바스크립트 번들을 더 작은 청크(Chunk)로 나눌 수 있습니다 [2, 3]. 결과적으로 사용자가 앱에 처음 접근할 때 다운로드해야 하는 초기 자바스크립트 페이로드 크기를 대폭 줄여 앱의 초기 로드 속도와 전반적인 성능을 크게 향상시킵니다 [2-4]. @@ -24,23 +24,23 @@ ### Related Concepts #### [아키텍처/기반 기술] -- [[Code Splitting]] +- [[Code Splitting|Code Splitting]] - 연결 이유: `React.lazy()`의 존재 목적이자 근본적인 성능 최적화 기법입니다 [6]. - 이 개념을 통해 더 깊게 이해할 수 있는 부분: 초기 렌더링 시 불필요한 자바스크립트 번들 크기를 줄여 로딩 성능을 최적화하는 애플리케이션 구조 원리. -- [[Dynamic Imports]] +- Dynamic Imports - 연결 이유: `React.lazy()` 함수 내부에서 비동기적으로 모듈을 로드하기 위해 사용하는 표준 자바스크립트 문법(`import()`)입니다 [2, 3, 8]. - 이 개념을 통해 더 깊게 이해할 수 있는 부분: 브라우저가 특정 코드가 실행되어야 할 시점에 네트워크 요청을 생성하여 모듈을 가져오는 메커니즘. #### [구현/활용 도구] -- [[Suspense]] +- Suspense - 연결 이유: `React.lazy()`로 분리된 코드가 백그라운드에서 다운로드되는 동안 앱이 멈추지 않도록 로딩 UI를 처리하기 위해 필수적으로 결합되는 리액트 기능입니다 [1, 3]. - 이 개념을 통해 더 깊게 이해할 수 있는 부분: 비동기 렌더링 흐름에서 로딩 상태(Loading State)를 컴포넌트 트리 상단에서 선언적으로 처리하는 방법. -- [[Vite/Rollup]] +- Vite/Rollup - 연결 이유: 소스 코드에 작성된 `React.lazy()` 구문을 분석하여 빌드 타임에 물리적으로 개별 자바스크립트 파일(청크)로 분할해 내는 도구들입니다 [2, 8]. - 이 개념을 통해 더 깊게 이해할 수 있는 부분: 모듈 번들러가 코드 스플리팅을 인식하고 프로덕션 환경의 정적 에셋으로 변환하여 캐싱 효율을 높이는 과정. ### Deeper Research Questions -- `React.lazy()`를 활용한 클라이언트 사이드 코드 스플리팅과 서버 사이드에서 이루어지는 [[React Server Components]]의 성능 최적화 방식은 어떻게 다르며 서로 어떻게 보완될 수 있는가? +- `React.lazy()`를 활용한 클라이언트 사이드 코드 스플리팅과 서버 사이드에서 이루어지는 [[React Server Components|React Server Components]]의 성능 최적화 방식은 어떻게 다르며 서로 어떻게 보완될 수 있는가? - ``로 감싸진 지연 로딩 컴포넌트가 로드될 때 발생하는 Cumulative Layout Shift (CLS)를 최소화하기 위한 구체적인 UI 패턴과 전략은 무엇인가? - 모바일 환경 등 네트워크 속도가 느린 곳에서 `React.lazy()`로 분리된 청크를 불러올 때, 에러가 발생한 경우(예: 배포 후 이전 해시 청크 삭제됨) 이를 Error Boundary로 어떻게 우아하게 복구할 수 있는가? - 사용자가 컴포넌트를 요청하기 전(예: 링크에 마우스를 올리는 시점)에 `React.lazy()`로 분리된 청크를 미리 가져오는 프리패치(Prefetching/Preloading) 전략은 어떻게 구현하는가? @@ -54,11 +54,11 @@ - **My Project Relevance:** 현재 유지보수 중인 프로젝트에 모달, 어드민 설정 패널 등 즉시 보이지 않는 컴포넌트들이 메인 번들에 포함되어 있다면, 이를 `React.lazy()`로 리팩토링하여 Time To Interactive (TTI) 지표를 당장 개선하는 데 적용할 수 있습니다. ### Adjacent Topics -- [[Core Web Vitals]] +- [[Core Web Vitals|Core Web Vitals]] - 확장 방향: `React.lazy()`를 적용했을 때 First Contentful Paint (FCP)와 Interaction to Next Paint (INP) 같은 구글의 웹 성능 지표가 어떻게 개선되는지 확인하는 방향으로 연구 확장 [1, 5]. -- [[manualChunks]] +- manualChunks - 확장 방향: `React.lazy()`에 의한 스플리팅 외에, React 코어나 서드파티 라이브러리들(vendor)을 별도 분리해 브라우저 캐싱을 고도화하는 빌드 도구 수준의 수동 제어 기법 파악 [8, 14]. -- [[React Server Components (RSC)]] +- [[React Server Components (RSC)|React Server Components (RSC)]] - 확장 방향: 자바스크립트를 클라이언트로 아예 보내지 않고 서버에서 렌더링하여 성능을 극대화하는 최신 Next.js 패러다임과 클라이언트 단의 `React.lazy`를 비교 [9, 15]. --- diff --git a/10_Wiki/Development/Real User Monitoring (RUM).md b/10_Wiki/Development/Real User Monitoring (RUM).md index fafa3074..e1debd89 100644 --- a/10_Wiki/Development/Real User Monitoring (RUM).md +++ b/10_Wiki/Development/Real User Monitoring (RUM).md @@ -1,4 +1,4 @@ -# [[Real User Monitoring (RUM)]] +# [[Real User Monitoring (RUM)|Real User Monitoring (RUM)]] ## 📌 Brief 시 Summary Real User Monitoring (RUM)은 다양한 기기와 네트워크 조건에서 사용자가 경험하는 실제 성능과 상호작용을 추적하는 모니터링 방식입니다 [1]. 합성 테스트(Synthetic testing)가 놓칠 수 있는 실제 성능 문제를 파악하는 데 필수적이며 [1], 프론트엔드의 사용자 액션과 백엔드의 인프라 트레이스를 연결하여 전체 시스템에 대한 가시성을 제공합니다 [2]. @@ -20,21 +20,21 @@ Real User Monitoring (RUM)은 다양한 기기와 네트워크 조건에서 사 ### Related Concepts #### [관계 유형 A (아키텍처/기반 기술)] -- [[Synthetic Testing]] +- [[Synthetic Testing|Synthetic Testing]] - 연결 이유: RUM과 대비되는 모니터링 개념으로, 가상 환경에서 애플리케이션의 성능을 시뮬레이션하여 측정합니다 [1]. - 이 개념을 통해 더 깊게 이해할 수 있는 부분: 시뮬레이션 데이터와 실제 사용자 경험(RUM) 데이터가 어떻게 상호보완적으로 작용하여 성능 병목 현상을 찾아내는지 이해할 수 있습니다. -- [[Distributed Tracing]] +- Distributed Tracing - 연결 이유: RUM 도구가 프론트엔드의 사용자 동작을 백엔드의 서비스 요청과 연관 짓기 위해 사용하는 핵심 메커니즘입니다 [2, 4, 12]. - 이 개념을 통해 더 깊게 이해할 수 있는 부분: 마이크로서비스 아키텍처 환경에서 클라이언트 에러의 근본 원인을 백엔드 데이터베이스나 외부 API까지 어떻게 추적하는지 원리를 파악할 수 있습니다. -- [[Core Web Vitals]] +- [[Core Web Vitals|Core Web Vitals]] - 연결 이유: RUM을 통해 주로 측정하고 최적화하려는 대상인 실제 사용자 중심의 로딩 속도, 상호작용, 시각적 안정성 지표입니다 [13, 14]. - 이 개념을 통해 더 깊게 이해할 수 있는 부분: RUM 데이터가 웹 성능 최적화의 기준(LCP, FID, CLS, INP)과 어떻게 매핑되어 사용자 경험(UX)을 수치화하는지 이해할 수 있습니다. #### [관계 유형 B (구현/활용 도구)] -- [[Datadog RUM]] +- Datadog RUM - 연결 이유: 소스에서 엔드투엔드 프론트엔드-백엔드 모니터링을 연결해 주는 대표적인 RUM 플랫폼으로 소개되었습니다 [2]. - 이 개념을 통해 더 깊게 이해할 수 있는 부분: 대규모 분산 시스템에서 RUM을 활용하는 구체적인 사례와, 인덱싱 비용 최적화(Trade-off) 전략의 중요성을 학습할 수 있습니다. -- [[Session Replay]] +- Session Replay - 연결 이유: 사용자의 상태 변경, 콘솔 로그, 네트워크 요청 등을 마치 화면 녹화처럼 재현하는 RUM의 고급 디버깅 기능입니다 [7, 12, 15]. - 이 개념을 통해 더 깊게 이해할 수 있는 부분: 스택 트레이스만으로 찾기 힘든 복잡한 사용자 상호작용 오류의 디버깅 방법론과 이에 따른 프라이버시 설정의 중요성을 알 수 있습니다. @@ -53,9 +53,9 @@ Real User Monitoring (RUM)은 다양한 기기와 네트워크 조건에서 사 - **My Project Relevance:** 현재 진행 중인 프론트엔드 프로젝트에서 사용자 이탈률이 높은 특정 화면의 병목 지점을 찾기 위해, RUM을 적용하여 실제 모바일 기기와 3G/LTE 환경에서의 INP(Interaction to Next Paint)와 렌더링 지연을 측정 및 개선할 때 활용합니다. ### Adjacent Topics -- [[OpenTelemetry]] +- OpenTelemetry - 확장 방향: 특정 벤더에 종속되지 않고(No vendor lock-in) 오픈 스탠다드 프로토콜을 이용해 RUM, 메트릭, 로그 데이터를 수집하고 백엔드와 연결하는 아키텍처로 지식을 확장할 수 있습니다 [16, 17]. -- [[Error Boundaries]] +- [[Error Boundaries|Error Boundaries]] - 확장 방향: React 애플리케이션 내에서 UI 렌더링 중 발생하는 런타임 에러를 캡처하여 전체 앱의 크래시를 방지하는 개념으로, 여기서 포착된 에러를 RUM 시스템에 보고하는 방식으로 연계할 수 있습니다 [18-20]. --- diff --git a/10_Wiki/Development/Redux.md b/10_Wiki/Development/Redux.md index 332910b5..107b5d80 100644 --- a/10_Wiki/Development/Redux.md +++ b/10_Wiki/Development/Redux.md @@ -1,4 +1,4 @@ -# [[Redux]] +# [[Redux|Redux]] ## 📌 Brief Summary Redux는 예측 가능한 상태 컨테이너로, 불변성을 유지하는 업데이트, 액션 디스패치(action dispatch), 그리고 리듀서(reducer)를 통해 전역 상태를 관리하는 산업 표준 라이브러리이다 [1]. 주로 복잡한 파생 및 계산된 상태가 존재하거나 500개 이상의 컴포넌트를 다루는 대규모 애플리케이션에서 일관된 개발 패턴을 강제하기 위해 채택된다 [2]. RTK Query와 Redux DevTools 같은 성숙한 생태계를 통해 비동기 상태 관리의 복잡성을 줄이고 강력한 디버깅 기능을 제공한다 [2-4]. @@ -13,19 +13,19 @@ Redux는 예측 가능한 상태 컨테이너로, 불변성을 유지하는 업 ## 🔗 Knowledge Connections ### Related Concepts -- [[Context API]] +- [[Context API|Context API]] - 연결 이유: Redux와 자주 비교되는 React의 내장 상태 공유 기능으로, 소규모 애플리케이션의 테마나 언어 설정 등을 관리하기 적합하지만, 상태 변경 시 발생하는 대규모 리렌더링 폭풍(Re-render Storm)을 유발하여 대규모 앱에서 Redux가 필요한 당위성을 제공한다 [8, 9, 16]. - 이 개념을 통해 더 깊게 이해할 수 있는 부분: 상태 구독 아키텍처의 차이가 React 컴포넌트의 리렌더링 성능에 미치는 치명적인 영향성 [8, 10]. -- [[Zustand]] +- Zustand - 연결 이유: Redux의 무거운 보일러플레이트와 Context API의 성능 문제 사이에서 적절한 타협점을 제공하는 경량 상태 관리 라이브러리이다 [17-19]. - 이 개념을 통해 더 깊게 이해할 수 있는 부분: 상태 관리 라이브러리의 과도한 유연성(Zustand)이 팀 단위 협업에서 어떻게 비동기 패턴의 파편화와 혼란을 야기할 수 있는지, 대조적으로 Redux의 엄격한 구조가 갖는 방어적 이점 [1, 11, 18, 20]. -- [[RTK Query]] +- RTK Query - 연결 이유: Redux Toolkit(RTK) 생태계에 포함된 데이터 패칭 및 캐싱 도구이다 [4]. - 이 개념을 통해 더 깊게 이해할 수 있는 부분: Redux가 어떻게 단순한 클라이언트 상태 관리를 넘어 서버 API 응답(캐싱, 무효화, 재요청)이라는 현대적인 요구사항을 보일러플레이트 없이 소화하는지 파악 [4, 21]. -- [[Time-Travel Debugging]] +- Time-Travel Debugging - 연결 이유: Redux DevTools가 제공하는 고유의 강력한 기능으로, 언제 어떤 액션이 디스패치되어 상태가 어떻게 변경되었는지 기록하고 되감는 기술이다 [2, 3]. - 이 개념을 통해 더 깊게 이해할 수 있는 부분: 5년 이상 지속되는 엔터프라이즈 애플리케이션에서 아키텍처의 디버깅 역량이 개발자의 생산성 및 장애 대응에 미치는 영향 [11, 12]. @@ -44,9 +44,9 @@ Redux는 예측 가능한 상태 컨테이너로, 불변성을 유지하는 업 - **My Project Relevance:** 글로벌 상태가 다수의 컴포넌트에 복잡하게 얽혀 있거나, 팀원 간 동일한 비동기/상태 관리 구조를 강제하여 파편화를 막아야 하는 애플리케이션을 구축할 때 핵심적인 기술 스택으로 검토될 수 있다 [1, 12]. ### Adjacent Topics -- [[Server State Management (TanStack Query 등)]] +- Server State Management (TanStack Query 등) - 확장 방향: 클라이언트 전역 상태와 구별되는 "서버 데이터(API 캐싱, 동기화, 로딩/에러 사이클)"만을 전문적으로 처리하는 모던 라이브러리와 Redux의 역할 비교 및 연동 방안 탐색 [24, 25]. -- [[React Rendering Optimization]] +- React Rendering Optimization - 확장 방향: 상태 관리 라이브러리의 선택과 별개로, React 컴포넌트 생명주기 및 메모이제이션(`useMemo`, `useCallback`, `React.memo`)이 애플리케이션 퍼포먼스에 미치는 원리와 프로파일링 방법 탐색 [26-28]. --- diff --git a/10_Wiki/Development/Rollup.md b/10_Wiki/Development/Rollup.md index 5a38f732..da4dcc44 100644 --- a/10_Wiki/Development/Rollup.md +++ b/10_Wiki/Development/Rollup.md @@ -1,4 +1,4 @@ -# [[Rollup]] +# [[Rollup|Rollup]] ## 📌 Brief Summary Rollup은 2025년 기준 최신 프론트엔드 빌드 도구인 Vite의 프로덕션 빌드를 백그라운드에서 담당하는 모듈 번들러입니다 [1]. 개발 단계에서는 네이티브 ES 모듈(ESM)을 사용하는 Vite가 실제 배포 시점에는 Rollup으로 전환하여 애플리케이션 코드를 병합하고 최적화합니다 [1, 2]. 자동 코드 분할(Code Splitting)과 사용하지 않는 코드를 제거하는 트리 쉐이킹(Tree-shaking) 기능을 통해 매우 최적화된 최종 에셋을 생성하는 것이 핵심 역할입니다 [1]. @@ -18,18 +18,18 @@ Rollup은 2025년 기준 최신 프론트엔드 빌드 도구인 Vite의 프로 ### Related Concepts #### [아키텍처/기반 기술] -- [[Vite]] +- Vite - 연결 이유: Rollup은 Vite의 아키텍처 내에서 프로덕션 배포 시 최적화된 빌드를 수행하는 내부 엔진으로 작동합니다 [1]. - 이 개념을 통해 더 깊게 이해할 수 있는 부분: 개발 모드(ESM)와 배포 모드(Rollup)를 다르게 가져가는 Vite의 하이브리드 번들링 아키텍처 전략을 이해할 수 있습니다 [1, 2]. -- [[Tree-shaking]] +- [[Tree Shaking (번들 크기 최적화)|Tree-shaking]] - 연결 이유: Rollup이 배포용 코드를 최적화할 때 사용하지 않는 코드를 덜어내는 핵심 메커니즘입니다 [1]. - 이 개념을 통해 더 깊게 이해할 수 있는 부분: ES 모듈 기반 라이브러리 사용이 왜 최종 번들 사이즈 최적화에 필수적인지 파악할 수 있습니다 [10]. #### [구현/활용 도구] -- [[manualChunks]] +- manualChunks - 연결 이유: Rollup을 사용하여 거대한 메인 번들을 세분화된 벤더 청크(Vendor chunk)로 쪼갤 때 사용되는 핵심 설정입니다 [4-6]. - 이 개념을 통해 더 깊게 이해할 수 있는 부분: 브라우저 캐싱을 극대화하기 위해 코드를 성격(변경 빈도)에 따라 분리하는 최적화 전략을 배울 수 있습니다 [6, 7]. -- [[Code Splitting]] +- [[Code Splitting|Code Splitting]] - 연결 이유: Rollup의 기능과 React의 지연 로딩(`React.lazy`)을 결합하여 구현되는 성능 최적화 기법입니다 [3, 11]. - 이 개념을 통해 더 깊게 이해할 수 있는 부분: 초기 페이로드(Payload)를 줄이고 Core Web Vitals를 개선하는 런타임 최적화 방법을 학습할 수 있습니다 [9, 12]. @@ -48,9 +48,9 @@ Rollup은 2025년 기준 최신 프론트엔드 빌드 도구인 Vite의 프로 - **My Project Relevance:** Vite 기반 React 애플리케이션을 Vercel이나 AWS 서버에 배포하기 전에 빌드 속도 및 초기 다운로드 속도를 개선하기 위한 필수 점검 단계로 활용합니다 [2, 11]. ### Adjacent Topics -- [[ES Modules (ESM)]] +- ES Modules (ESM) - 확장 방향: Rollup의 프로덕션 빌드 이전, Vite가 개발 환경에서 코드 변경 사항을 즉각적으로 브라우저에 반영하는 원리 파악 [1, 15]. -- [[Core Web Vitals]] +- [[Core Web Vitals|Core Web Vitals]] - 확장 방향: Rollup의 번들 분할 및 경량화 작업이 LCP(Largest Contentful Paint)나 INP(Interaction to Next Paint)와 같은 브라우저 성능 측정 지표를 어떻게 개선하는지 조사 [9, 14]. --- diff --git a/10_Wiki/Development/Scalable Frontend Systems.md b/10_Wiki/Development/Scalable Frontend Systems.md index 57f7da94..b55d5ca9 100644 --- a/10_Wiki/Development/Scalable Frontend Systems.md +++ b/10_Wiki/Development/Scalable Frontend Systems.md @@ -1,4 +1,4 @@ -# [[Scalable Frontend Systems]] +# [[Scalable Frontend Systems|Scalable Frontend Systems]] ## 📌 Brief Summary 대규모 프론트엔드 시스템(Scalable Frontend Systems)은 높은 유지보수성, 고성능, 확장성을 보장하기 위해 기존의 단순한 스크립트 실행을 넘어 정교하게 분산된 소프트웨어 아키텍처를 도입한 시스템입니다 [1]. 기능별 또는 도메인 중심의 모듈형 폴더 구조를 사용하며, SOLID와 같은 클린 코드 원칙을 준수하고 애플리케이션 상태와 서버 상태를 분리하여 관리합니다 [2-4]. 더불어 자동화된 빌드 최적화, 예측 가능한 렌더링 최적화, 정교한 에러 처리 및 협업 워크플로우를 결합하여 애플리케이션이 안정적으로 성장할 수 있도록 지원합니다 [1, 5]. @@ -16,23 +16,23 @@ ### Related Concepts -- [[Feature-Sliced Design (FSD)]] +- [[Feature-Sliced Design (FSD)|Feature-Sliced Design (FSD)]] - 연결 이유: 확장 가능한 프론트엔드 아키텍처에서 빈번하게 발생하는 '비즈니스 로직 얽힘' 문제를 해결하기 위해 도입된 핵심적인 컴포넌트/디렉토리 분할 방법론입니다 [33, 34]. - 이 개념을 통해 더 깊게 이해할 수 있는 부분: 단방향 의존성 흐름, 계층별(Layered) 분할, 캡슐화를 통한 Public API 인터페이스 설계 원리 [7, 9]. -- [[State Management Fragmentation (상태 관리 파편화)]] +- State Management Fragmentation (상태 관리 파편화) - 연결 이유: 대규모 애플리케이션에서 단일 스토어나 Context API만으로는 리렌더링 성능 최적화가 불가능해짐에 따라, 전역 상태(Zustand), 서버 상태(React Query), 로컬 상태로 역할을 분리하여 관리하는 트렌드입니다 [4, 13, 35]. - 이 개념을 통해 더 깊게 이해할 수 있는 부분: 불필요한 렌더링 방지 원리(Zustand의 선택자 패턴)와 서버/클라이언트 데이터 간의 캐싱 및 동기화 전략 [4, 14]. -- [[React Compiler]] +- [[React Compiler|React Compiler]] - 연결 이유: 개발자가 수동으로 수행하던 `useMemo`, `useCallback`, `React.memo` 등의 메모이제이션을 빌드 타임에 자동으로 처리해 주어, 깔끔한 코드를 유지하면서 성능 확장을 가능케 하는 최신 도구입니다 [19, 36]. - 이 개념을 통해 더 깊게 이해할 수 있는 부분: React의 렌더링 최적화 한계 및 Rules of React 준수 중요성, 써드파티 라이브러리와의 호환성 문제 [37, 38]. -- [[Error Boundaries]] +- [[Error Boundaries|Error Boundaries]] - 연결 이유: 시스템의 크기가 커질 때 단일 컴포넌트의 오류가 전체 앱의 '화이트 스크린' 크래시로 이어지지 않게 UI의 일부분만 대체(Fallback)하여 시스템 복원력(Resilience)을 보장하는 장치입니다 [23, 24, 39]. - 이 개념을 통해 더 깊게 이해할 수 있는 부분: 클래스형 컴포넌트 생명주기를 활용한 런타임 에러 포착 원리 및 대규모 UI 보호 전략 [40, 41]. -- [[Code Splitting & Lazy Loading (코드 분할과 지연 로딩)]] +- Code Splitting & Lazy Loading (코드 분할과 지연 로딩) - 연결 이유: 프론트엔드 코드가 비대해지면서 초기 로딩 속도(TTI, LCP)를 최적화하기 위해 필수적으로 요구되는 기술로, Vite나 React.lazy를 통해 필요한 시점에만 모듈을 다운로드하게 합니다 [15, 17, 42]. - 이 개념을 통해 더 깊게 이해할 수 있는 부분: 모듈 번들러의 청크(Chunk) 분리 원리 및 브라우저 성능 최적화(Core Web Vitals)와 번들 사이즈의 상관관계 [43, 44]. @@ -54,11 +54,11 @@ ### Adjacent Topics -- [[Frontend Cloud Logging Tools (프론트엔드 클라우드 로깅 도구)]] +- Frontend Cloud Logging Tools (프론트엔드 클라우드 로깅 도구) - 확장 방향: 확장 가능한 시스템이 프로덕션 단계에 들어갔을 때, Sentry나 Datadog, SigNoz 같은 모니터링 툴을 활용해 사용자 세션과 에러 로그를 연동하여 가시성(Observability)을 확보하는 방향으로 확장할 수 있습니다 [58-60]. -- [[Storybook Visual Regression Testing (Storybook 시각적 회귀 테스트)]] +- Storybook Visual Regression Testing (Storybook 시각적 회귀 테스트) - 확장 방향: 대규모 팀에서 UI 컴포넌트를 변경할 때, 기존 화면(baseline)의 레이아웃이나 픽셀이 의도치 않게 깨지는 것을 방지하기 위한 자동화된 시각적 회귀 검증(Happo, Chromatic) 및 CI 파이프라인 연동 방향으로 확장할 수 있습니다 [61-63]. -- [[Git Branching Strategies & Workflows (Git 브랜치 전략 및 워크플로우)]] +- Git Branching Strategies & Workflows (Git 브랜치 전략 및 워크플로우) - 확장 방향: 어플리케이션 확장뿐만 아니라 참여하는 개발자 수가 많아질 때, Trunk-based 개발이나 GitHub Flow 등을 도입하여 충돌을 줄이고 티켓 기반 추적성을 확보하는 형상관리 방향으로 확장할 수 있습니다 [31, 64]. --- diff --git a/10_Wiki/Development/Storybook.md b/10_Wiki/Development/Storybook.md index 6d872c98..9e5c7bcd 100644 --- a/10_Wiki/Development/Storybook.md +++ b/10_Wiki/Development/Storybook.md @@ -1,4 +1,4 @@ -# [[Storybook]] +# [[Storybook|Storybook]] ## 📌 Brief 주Summary Storybook은 프론트엔드 개발 시 UI 컴포넌트를 주 애플리케이션과 격리하여 개발하고 문서화할 수 있도록 돕는 도구입니다 [1-3]. 특히 개발된 컴포넌트의 다양한 상태(스토리)를 기반으로 자동화된 시각적 회귀 테스트(Visual Regression Testing) 및 상호작용 테스트(Interaction Testing)를 수행하여 의도치 않은 UI 변경이나 접근성 위반을 방지합니다 [4-6]. Pull Request 과정에 결합되어 안전한 UI 업데이트와 리뷰를 지원하는 필수적인 플랫폼으로 활용됩니다 [1, 7]. @@ -25,20 +25,20 @@ Storybook은 프론트엔드 개발 시 UI 컴포넌트를 주 애플리케이 ### Related Concepts #### [테스트 및 검증 기법 (Testing Methods)] -- [[Visual Regression Testing]] +- [[Visual Regression Testing|Visual Regression Testing]] - 연결 이유: Storybook이 컴포넌트의 변경 사항을 픽셀 단위로 확인하기 위해 사용하는 핵심 테스트 방법론입니다 [4, 8]. - 이 개념을 통해 더 깊게 이해할 수 있는 부분: HTML 마크업을 비교하는 Snapshot Test의 한계점과 오탐(False Positive)의 원리, 그리고 픽셀 렌더링 기반 비교의 장점을 명확히 이해할 수 있습니다 [9]. -- [[Interaction Testing]] +- Interaction Testing - 연결 이유: 컴포넌트의 단순한 렌더링뿐만 아니라 유저의 행동(이벤트, 상태 등)을 시뮬레이션하여 다양한 UI 상태(로딩, 호버 등)를 검증하는 Storybook의 기능입니다 [5, 6]. - 이 개념을 통해 더 깊게 이해할 수 있는 부분: 상태 전이에 따라 동적으로 변하는 UI를 어떻게 시각적 테스트와 결합하여 검증할 수 있는지 원리를 파악할 수 있습니다 [5]. #### [통합 및 자동화 도구 (Integration Tools)] -- [[Chromatic]] +- Chromatic - 연결 이유: Storybook 유지보수 팀이 만든 공식 클라우드 서비스로, 크로스 브라우저 시각적 테스트와 CI 통합을 네이티브로 지원합니다 [8, 15]. - 이 개념을 통해 더 깊게 이해할 수 있는 부분: 클라우드 환경에서 베이스라인(Baseline) 이미지가 어떻게 저장, 비교, 동기화되는지 CI/CD 파이프라인 통합 과정을 이해할 수 있습니다 [7, 13]. -- [[Happo]] +- Happo - 연결 이유: Storybook과 통합되어 다중 브라우저 스크린샷 테스트 및 접근성 회귀 테스트를 병렬로 수행하는 시각적 테스트 도구입니다 [4]. - 이 개념을 통해 더 깊게 이해할 수 있는 부분: Flakiness 방지를 위해 애니메이션을 정지하거나 색상 오차 범위(color-delta tolerance)를 설정하여 시각적 노이즈를 줄이는 구체적 최적화 기법을 알 수 있습니다 [11, 14]. @@ -57,9 +57,9 @@ Storybook은 프론트엔드 개발 시 UI 컴포넌트를 주 애플리케이 - **My Project Relevance:** 현재 유지보수 중인 애플리케이션의 리팩토링이나 새로운 디자인 시스템(UI 라이브러리) 구축 작업 시, 실수로 발생하는 CSS/레이아웃 깨짐을 사전에 방지하기 위한 안전장치로 도입할 수 있습니다. ### Adjacent Topics -- [[Pull Request Workflow]] +- Pull Request Workflow - 확장 방향: Storybook 시각적 테스트의 결과를 GitHub, GitLab 등의 리뷰 프로세스와 결합하여, 버그 없는 UI 코드를 배포하기 위한 협업 및 검증 파이프라인 구축 전략으로 확장합니다. -- [[Feature-Sliced Design]] +- [[Feature-Sliced Design|Feature-Sliced Design]] - 확장 방향: 프론트엔드 코드를 기능(Feature) 단위로 분리할 때, Storybook을 이용해 각 기능의 UI 컴포넌트들을 메인 앱에 의존하지 않고 독립적으로 작동하게 만드는 설계 원칙으로 확장합니다. --- diff --git a/10_Wiki/Development/UI_Components/Index.md b/10_Wiki/Development/UI_Components/Index.md index 8bd67033..93fe9891 100644 --- a/10_Wiki/Development/UI_Components/Index.md +++ b/10_Wiki/Development/UI_Components/Index.md @@ -1,4 +1,4 @@ # Index: Development > UI_Components ## 📝 Documents -- [[Accordion]] +- [[Accordion|Accordion]] diff --git a/10_Wiki/Development/Visual Regression Testing.md b/10_Wiki/Development/Visual Regression Testing.md index 7711b648..da6e2184 100644 --- a/10_Wiki/Development/Visual Regression Testing.md +++ b/10_Wiki/Development/Visual Regression Testing.md @@ -1,4 +1,4 @@ -# [[Visual Regression Testing]] +# [[Visual Regression Testing|Visual Regression Testing]] ## 📌 Brief Summary 시각적 회귀 테스트(Visual Regression Testing)는 스토리북(Storybook) 등의 도구로 렌더링된 컴포넌트의 픽셀 단위 스크린샷을 캡처하여 이전에 알려진 "정상(baseline)" 상태의 스크린샷과 자동으로 비교하는 테스트 방식이다 [1, 2]. 이를 통해 개발자는 풀 리퀘스트(PR) 과정에서 의도치 않은 UI 레이아웃, 색상, 타이포그래피 등의 시각적 변경이나 결함을 찾아낼 수 있다 [3-5]. HTML 마크업만 비교하는 기존의 스냅샷 테스트와 달리, 실제 사용자가 경험하는 화면 픽셀을 직접 검증하므로 추가적인 테스트 코드 작성이나 유지보수 부담을 줄이면서도 오탐(false positive)을 최소화할 수 있는 것이 특징이다 [1, 2]. @@ -18,18 +18,18 @@ ### Related Concepts #### [테스트 및 검증 기술] -- [[Snapshot Testing]] +- Snapshot Testing - 연결 이유: 시각적 회귀 테스트와 대조되는 테스트 방식으로, 픽셀이 아닌 렌더링된 HTML 마크업 코드 덩어리를 비교한다 [2]. - 이 개념을 통해 더 깊게 이해할 수 있는 부분: HTML 구조 비교 방식이 왜 빈번하게 오탐(False Positive)을 발생시키는지, 그리고 픽셀 기반 비교가 유지보수에 왜 더 유리한지 명확하게 이해할 수 있다 [2]. -- [[Interaction Testing]] +- Interaction Testing - 연결 이유: 사용자의 상호작용이나 이벤트를 시뮬레이션하여 컴포넌트의 특정 UI 상태를 유도하는 테스트 방식이다 [5, 10]. - 이 개념을 통해 더 깊게 이해할 수 있는 부분: 정적 UI 화면뿐만 아니라 로딩, 에러, 클릭 시 드롭다운 오픈 등 동적으로 변화하는 UI 상태를 시각적 회귀 테스트가 어떻게 캡처하고 검증하는지 파악할 수 있다 [9, 10]. #### [구현 및 활용 도구] -- [[Storybook]] +- [[Storybook|Storybook]] - 연결 이유: UI 컴포넌트를 애플리케이션의 복잡한 로직과 분리하여 격리된 환경에서 시각적으로 개발하고 문서화할 수 있게 해주는 도구이다 [3, 6]. - 이 개념을 통해 더 깊게 이해할 수 있는 부분: 시각적 회귀 테스트가 전체 페이지 단위가 아닌 개별 컴포넌트의 상태(Story) 단위로 렌더링되고 기준선과 비교되는 아키텍처적 기반을 이해할 수 있다 [1]. -- [[Chromatic]] / [[Happo]] +- Chromatic / Happo - 연결 이유: Storybook과 연결되어 실제 브라우저 기반의 스크린샷 캡처, 베이스라인 픽셀 비교, CI/CD 연동 등을 수행하는 시각적 회귀 테스트 클라우드 서비스(도구)이다 [1, 3, 4]. - 이 개념을 통해 더 깊게 이해할 수 있는 부분: 자동화된 시각적 회귀 테스트가 브라우저 간의 렌더링 차이를 어떻게 병렬로 처리하고 풀 리퀘스트(PR) 프로세스와 어떻게 상호작용하는지 확인할 수 있다 [4, 12]. @@ -48,9 +48,9 @@ - **My Project Relevance:** 프론트엔드 레거시 코드를 리팩토링하거나 수백 개의 화면에서 공유되는 코어 UI 라이브러리 버전을 업그레이드할 때, 다른 팀의 컴포넌트에서 발생하는 의도치 않은 파급 효과(Side Effect) 및 시각적 깨짐을 안전하게 감지하고 확신을 갖고 배포하는 데 핵심적인 역할을 한다 [3, 16]. ### Adjacent Topics -- [[Accessibility Regression Testing]] +- Accessibility Regression Testing - 확장 방향: 시각적 테스트 워크플로우와 결합하여, 새로운 테스트 코드를 별도로 작성할 필요 없이 스크린샷 실행 단계에서 UI의 접근성 위반(명도 대비 부족, 키보드 포커스 누락 등)까지 동시에 자동 검증하는 영역으로 확장할 수 있다 [9, 10]. -- [[Continuous Integration (CI) Pipelines]] +- Continuous Integration (CI) Pipelines - 확장 방향: GitHub Actions, CircleCI 등의 CI 도구에서 시각적 테스트 인프라가 어떻게 연동되며, 코드가 병합되기 전에 PR의 상태 체크(Status Check)를 필수로 제어하는 자동화 파이프라인 및 DevOps 프로세스로 학습을 넓힐 수 있다 [12]. --- diff --git a/10_Wiki/Development/Vite + React 성능 최적화.md b/10_Wiki/Development/Vite + React 성능 최적화.md index 5fbe3306..e7b896cf 100644 --- a/10_Wiki/Development/Vite + React 성능 최적화.md +++ b/10_Wiki/Development/Vite + React 성능 최적화.md @@ -1,4 +1,4 @@ -# [[Vite + React 성능 최적화]] +# [[Vite + React 성능 최적화|Vite + React 성능 최적화]] ## 📌 Brief Summary Vite와 React 환경에서 애플리케이션의 성능을 최적화하는 것은 초기 로딩 속도를 높이고 런타임 성능을 향상시켜 전반적인 사용자 경험을 개선하는 과정입니다. 개발 환경에서는 기본 ES 모듈(ESM)을, 운영 환경에서는 Rollup을 통한 번들링을 활용하는 Vite의 구조적 이점을 극대화하는 것이 핵심입니다. 주요 최적화 기법으로는 빠른 컴파일을 위한 SWC 도입, 동적 임포트를 통한 코드 분할, `manualChunks`를 활용한 무거운 벤더 라이브러리 분리, 그리고 번들 시각화 도구를 통한 불필요한 의존성 제거 등이 포함됩니다. @@ -26,24 +26,24 @@ Vite와 React 환경에서 애플리케이션의 성능을 최적화하는 것 ### Related Concepts #### [관계 유형 A (아키텍처/기반 기술)] -- [[네이티브 ES 모듈(ESM)]] +- 네이티브 ES 모듈(ESM) - 연결 이유: Vite가 개발 환경에서 코드 모듈을 서빙하는 방식의 핵심 기반 원리입니다. - 이 개념을 통해 더 깊게 이해할 수 있는 부분: 번들러가 전체 앱을 매번 빌드하지 않고 변경된 모듈만 요청/로드함으로써 프로젝트 크기에 상관없이 빠른 HMR과 응답성을 유지하는 메커니즘을 파악할 수 있습니다 [1, 29, 30]. -- [[Rollup]] +- [[Rollup|Rollup]] - 연결 이유: Vite 환경에서 프로덕션 배포 시 코드를 하나로 모으고 최적화하는 데 사용되는 번들러입니다. - 이 개념을 통해 더 깊게 이해할 수 있는 부분: Vite의 설정 파일(`vite.config.js`)에서 `manualChunks` 등 Rollup 전용 빌드 옵션을 통해 어떻게 효율적인 정적 애셋(Asset)을 생성하고, 코드 분할과 트리 쉐이킹을 수행하는지 이해할 수 있습니다 [14, 18, 31, 32]. #### [관계 유형 B (구현/활용 도구)] -- [[SWC 컴파일러]] +- SWC 컴파일러 - 연결 이유: Vite의 기본 구성을 확장해 속도를 향상시키기 위한 강력한 도구입니다. - 이 개념을 통해 더 깊게 이해할 수 있는 부분: 과거 Babel이 처리하던 JSX/TypeScript 변환 작업을 Rust 기반의 빠른 도구(`@vitejs/plugin-react-swc`)로 교체하여 대형 React 애플리케이션의 재빌드 시간을 즉각적으로 단축시키는 방식을 파악할 수 있습니다 [1, 3, 5]. -- [[React.lazy & Suspense]] +- React.lazy & Suspense - 연결 이유: React 내부에서 동적 임포트를 통한 컴포넌트 레벨 지연 로딩을 구현하기 위한 API입니다. - 이 개념을 통해 더 깊게 이해할 수 있는 부분: 라우트나 무거운 모듈을 분리하고, 번들이 로드되는 동안 ``를 통해 폴백(Fallback) UI를 처리함으로써 초기 자바스크립트 페이로드 용량을 대폭 줄이는 실무 기법을 배울 수 있습니다 [6, 9, 11, 12, 33]. -- [[rollup-plugin-visualizer]] +- rollup-plugin-visualizer - 연결 이유: 최적화 작업 전후로 번들 크기를 시각화하고 문제를 진단하는 필수 분석 플러그인입니다. - 이 개념을 통해 더 깊게 이해할 수 있는 부분: 큰 청크가 왜 발생하는지, 어떤 외부 라이브러리(벤더)가 의도치 않게 용량을 과도하게 점유하는지 분석하여 `manualChunks`나 코드 교체를 결단하는 측정/디버깅 기반을 확립할 수 있습니다 [6, 13, 21]. @@ -65,10 +65,10 @@ Vite와 React 환경에서 애플리케이션의 성능을 최적화하는 것 ### Adjacent Topics -- [[Core Web Vitals]] +- [[Core Web Vitals|Core Web Vitals]] - 확장 방향: Vite와 React 최적화를 통해 얻어낸 메인 번들 크기 감소 및 렌더링 속도 향상이 실제 사용자 체감 성능 지표(LCP, FID/INP 등)에 어떤 수치적 개선으로 나타나는지를 구체적으로 연구합니다 [11, 34, 35]. -- [[Concurrent Rendering (동시성 렌더링)]] +- Concurrent Rendering (동시성 렌더링) - 확장 방향: 로딩과 번들링 최적화뿐만 아니라, `useTransition` 및 `useDeferredValue` 훅을 이용하여 복잡한 데이터 변화 시에도 사용자 입력 등의 UI 반응성을 유지하는 런타임 차원의 성능 향상 전략으로 지식을 확장합니다 [36-38]. --- diff --git a/10_Wiki/Development/Vite Build System.md b/10_Wiki/Development/Vite Build System.md index 9ee03e7c..04a693b8 100644 --- a/10_Wiki/Development/Vite Build System.md +++ b/10_Wiki/Development/Vite Build System.md @@ -1,4 +1,4 @@ -# [[Vite Build System]] +# [[Vite Build System|Vite Build System]] ## 📌 Brief Summary Vite는 현대 프론트엔드 애플리케이션(특히 React) 개발을 위한 새로운 산업 표준 빌드 도구로, 거의 즉각적인 서버 시작과 초고속 HMR(Hot Module Replacement)을 제공합니다 [1, 2]. 기존 번들러와 달리 개발 환경에서는 브라우저에 네이티브 ES 모듈 형태로 코드를 제공하고, 프로덕션 환경에서는 Rollup을 사용하여 고도로 최적화된 번들을 생성하는 하이브리드 아키텍처를 사용합니다 [3, 4]. 또한 SWC나 esbuild와 같은 Rust 기반 컴파일러를 활용하여 대규모 프로젝트에서도 빠르고 원활한 개발자 경험을 보장합니다 [3, 5, 6]. @@ -12,19 +12,19 @@ Vite는 현대 프론트엔드 애플리케이션(특히 React) 개발을 위한 ## 🔗 Knowledge Connections ### Related Concepts -- [[Native ES Modules (ESM)]] +- Native ES Modules (ESM) - 연결 이유: Vite가 개발 환경에서 파일 전체를 사전 번들링하지 않고, 필요할 때 브라우저에 코드를 제공하는 핵심 메커니즘이기 때문입니다 [3, 7]. - 이 개념을 통해 더 깊게 이해할 수 있는 부분: Vite가 기존 도구(Webpack 등)에 비해 어떻게 초기 구동 속도와 HMR 응답성을 극적으로 단축할 수 있는지 그 원리를 파악할 수 있습니다 [2, 3]. -- [[Rollup]] +- [[Rollup|Rollup]] - 연결 이유: Vite가 프로덕션용 빌드를 생성할 때 내부적으로 채택하고 있는 번들러 도구이기 때문입니다 [4]. - 이 개념을 통해 더 깊게 이해할 수 있는 부분: 프로덕션 환경에서 청크가 어떻게 나뉘며(`manualChunks`), 코드 스플리팅과 트리 쉐이킹을 통해 최적화된 정적 자산이 만들어지는 과정을 이해할 수 있습니다 [4, 8, 11]. -- [[SWC (Speedy Web Compiler)]] +- SWC (Speedy Web Compiler) - 연결 이유: Vite 환경에서 기존의 Babel을 대체하여 JSX와 TypeScript를 실시간에 가깝게 변환하는 Rust 기반 컴파일러 기술이기 때문입니다 [3, 5, 6]. - 이 개념을 통해 더 깊게 이해할 수 있는 부분: 대규모 React 애플리케이션 개발 시 컴파일 속도와 핫 리로드 속도를 향상하는 기술적 배경을 깊이 이해할 수 있습니다 [3, 6]. -- [[Code Splitting & manualChunks]] +- Code Splitting & manualChunks - 연결 이유: 대용량 메인 번들 문제를 해결하고, 초기 페이지 로드 속도를 높이기 위한 Vite 성능 최적화의 핵심 기법이기 때문입니다 [12, 14]. - 이 개념을 통해 더 깊게 이해할 수 있는 부분: 동적 임포트와 결합하여 벤더 라이브러리(안정적인 코드)를 별도 파일로 캐싱하고 기능 단위로 청크를 나누는 전략을 학습할 수 있습니다 [8, 16]. @@ -43,9 +43,9 @@ Vite는 현대 프론트엔드 애플리케이션(특히 React) 개발을 위한 - **My Project Relevance:** 소스에 관련 정보가 부족합니다. (개인의 현재 진행 중인 특정 프로젝트에 대한 정보가 소스 텍스트에 포함되어 있지 않습니다.) ### Adjacent Topics -- [[React Server Components (RSC) & Next.js App Router]] +- React Server Components (RSC) & Next.js App Router - 확장 방향: Vite를 이용한 빌드 툴 체인 최적화(CSR/SPA 성능 최적화)를 넘어, 클라이언트 측 자바스크립트 번들 자체를 전송하지 않고 서버에서 미리 렌더링하는 아키텍처 수준의 성능 최적화 패러다임으로 이해를 넓힙니다 [21-23]. -- [[Performance Metrics (Core Web Vitals)]] +- Performance Metrics (Core Web Vitals) - 확장 방향: Vite의 청크 최적화와 레이지 로딩 기법이 실제 사용자 체감 성능 지표인 FCP(First Contentful Paint), LCP(Largest Contentful Paint), INP(Interaction to Next Paint)에 어떤 직접적인 영향을 미치는지 연결하여 학습합니다 [13, 24, 25]. --- diff --git a/10_Wiki/Development/Vite Build Tool.md b/10_Wiki/Development/Vite Build Tool.md index de593fe3..ea50b38c 100644 --- a/10_Wiki/Development/Vite Build Tool.md +++ b/10_Wiki/Development/Vite Build Tool.md @@ -1,4 +1,4 @@ -# [[Vite Build Tool]] +# [[Vite Build Tool|Vite Build Tool]] ## 📌 Brief 임무 Vite는 현대 프론트엔드 애플리케이션(주로 React)을 위한 표준 빌드 도구로, 기존 Webpack 및 Create React App(CRA)을 대체하며 빠르게 자리 잡았습니다 [1, 2]. 이 도구는 개발 환경에서는 브라우저의 네이티브 ES 모듈(ESM)을 활용해 즉각적인 서버 시작과 초고속 HMR(Hot Module Replacement)을 제공합니다 [2-4]. 프로덕션 배포 시에는 내부적으로 Rollup을 사용하여 코드 스플리팅과 트리 쉐이킹이 적용된 고도로 최적화된 번들을 생성하는 하이브리드 아키텍처를 특징으로 합니다 [5, 6]. @@ -28,20 +28,20 @@ Vite는 현대 프론트엔드 애플리케이션(주로 React)을 위한 표준 ### Related Concepts #### [아키텍처/기반 기술] -- [[Native ES Modules (ESM)]] +- Native ES Modules (ESM) - 연결 이유: Vite가 개발 단계에서 빠른 구동 속도를 달성하기 위해 활용하는 브라우저의 기본 모듈 시스템입니다 [2, 4]. - 이 개념을 통해 더 깊게 이해할 수 있는 부분: 과거 도구(Webpack)의 무거운 사전 번들링 방식과 대비되는 Vite의 '요청 시 제공(On-demand serving)' 메커니즘의 원리. -- [[Rollup]] +- [[Rollup|Rollup]] - 연결 이유: Vite의 프로덕션 빌드를 담당하는 내부 번들러입니다 [5, 6]. - 이 개념을 통해 더 깊게 이해할 수 있는 부분: 배포 환경에서 어떻게 `manualChunks`를 활용하여 번들을 분할하고, 트리 쉐이킹을 통해 최적화된 결과물을 도출하는지 그 과정 [10, 16]. -- [[SWC]] +- SWC - 연결 이유: 기존의 Babel을 대체하여 JSX와 TypeScript 컴파일을 엄청나게 빠른 속도로 처리하는 Rust 기반 트랜스포머입니다 [4, 7, 8]. - 이 개념을 통해 더 깊게 이해할 수 있는 부분: Vite 환경에서 React 애플리케이션의 핫 리로드와 빌드 퍼포먼스를 한 차원 끌어올리는 컴파일러의 역할. #### [최적화 기법] -- [[Code Splitting & manualChunks]] +- Code Splitting & manualChunks - 연결 이유: 500kB 이상의 거대한 메인 번들 경고 문제를 해결하기 위해 Vite/Rollup 환경에서 벤더 코드와 앱 코드를 나누는 핵심 기법입니다 [6, 14, 15]. - 이 개념을 통해 더 깊게 이해할 수 있는 부분: 브라우저 병렬 다운로드와 효율적인 캐시 무효화 전략, 초기 페이로드 최소화 방법 [17, 19]. @@ -63,9 +63,9 @@ Vite는 현대 프론트엔드 애플리케이션(주로 React)을 위한 표준 ### Adjacent Topics -- [[Webpack]] +- Webpack - 확장 방향: Vite가 등장하기 전 업계 표준이었으나 시작 전 전체 번들링 과정으로 인해 무거운 구조를 가진 Webpack의 한계와 Vite와의 아키텍처 비교 [1, 2]. -- [[Core Web Vitals]] +- [[Core Web Vitals|Core Web Vitals]] - 확장 방향: Vite의 청크 분할 및 지연 로딩 기법이 실제 사용자 경험 지표인 FCP(First Contentful Paint), LCP(Largest Contentful Paint), INP(Interaction to Next Paint)에 어떻게 직결되는지 탐구 [17, 20]. --- diff --git a/10_Wiki/Development/대규모 프론트엔드 애플리케이션.md b/10_Wiki/Development/대규모 프론트엔드 애플리케이션.md index b3e02b9e..9b5c4546 100644 --- a/10_Wiki/Development/대규모 프론트엔드 애플리케이션.md +++ b/10_Wiki/Development/대규모 프론트엔드 애플리케이션.md @@ -1,4 +1,4 @@ -# [[대규모 프론트엔드 애플리케이션]] +# [[대규모 프론트엔드 애플리케이션|대규모 프론트엔드 애플리케이션]] ## 📌 Brief Summary 대규모 프론트엔드 애플리케이션은 단순한 스크립트 실행을 넘어 확장성, 유지보수성, 고성능을 요구하는 고도로 정교한 분산 소프트웨어 시스템입니다. 비즈니스 로직과 UI의 분리, 명확한 상태 소유권, 엄격한 폴더 구조(Feature-Sliced Design 등)를 통해 아키텍처의 붕괴를 방지합니다. 또한, 코드 스플리팅, 자동 메모이제이션, 세분화된 상태 관리 도구를 활용하여 최적의 렌더링 성능과 사용자 경험을 유지하는 것이 핵심입니다. @@ -24,19 +24,19 @@ ## 🔗 Knowledge Connections ### Related Concepts -- [[Feature-Sliced Design (FSD)]] +- [[Feature-Sliced Design (FSD)|Feature-Sliced Design (FSD)]] - 연결 이유: 대규모 프론트엔드 프로젝트의 폴더 구조와 모듈 의존성을 통제하는 핵심 아키텍처 방법론입니다. - 이 개념을 통해 더 깊게 이해할 수 있는 부분: 비즈니스 도메인과 UI를 어떻게 계층적으로 분리하고, 순환 참조 및 강한 결합을 어떻게 방지할 수 있는지 이해할 수 있습니다. -- [[상태 관리 (State Management)]] +- [[상태 관리(State Management)|상태 관리 (State Management)]] - 연결 이유: 대규모 앱에서는 전역 상태, 서버 상태, 로컬 상태를 명확히 분리해야 확장 및 성능 유지가 가능합니다. - 이 개념을 통해 더 깊게 이해할 수 있는 부분: Context API의 성능적 한계(리렌더링 폭풍)와 Zustand의 Selector 패턴, TanStack Query를 통한 서버 상태 캐싱 원리를 이해할 수 있습니다. -- [[성능 최적화 (Performance Optimization)]] +- [[성능 최적화(Performance Optimization)|성능 최적화 (Performance Optimization)]] - 연결 이유: 대규모 코드베이스는 필연적으로 번들 크기 증가와 렌더링 병목을 초래하므로 이를 제어하는 기술이 필수적입니다. - 이 개념을 통해 더 깊게 이해할 수 있는 부분: React Compiler의 자동화된 메모이제이션 원리, Vite의 manualChunks를 통한 번들 분할, React.lazy 기반의 코드 스플리팅 적용 방식을 파악할 수 있습니다. -- [[에러 바운더리 (Error Boundaries)]] +- 에러 바운더리 (Error Boundaries) - 연결 이유: 컴포넌트 하나의 오류가 전체 앱의 크래시로 이어지지 않게 막아주는 대규모 시스템의 필수 안전망입니다. - 이 개념을 통해 더 깊게 이해할 수 있는 부분: 컴포넌트 트리 내에서 에러를 격리하는 원리와 런타임 에러를 우아하게 처리(Graceful degradation)하는 방법을 배울 수 있습니다. -- [[메모리 누수 (Memory Leaks)]] +- [[메모리 누수(Memory Leaks)|메모리 누수 (Memory Leaks)]] - 연결 이유: 앱 사용 시간이 길어질수록 성능을 심각하게 저하시키는 숨은 원인입니다. - 이 개념을 통해 더 깊게 이해할 수 있는 부분: 클로저(Closure)나 Detached DOM에 의해 가비지 컬렉터가 메모리를 회수하지 못하는 구조적 원인과 DevTools를 활용한 디버깅 기법을 이해할 수 있습니다. @@ -55,9 +55,9 @@ - **My Project Relevance:** 팀 단위의 협업 시 ESLint, Prettier, Husky를 도입해 아키텍처 규칙(다른 Feature에 직접 접근 금지 등)을 자동 강제하고, 코드 리뷰 시 일관된 아키텍처 원칙을 기준으로 삼을 수 있습니다. ### Adjacent Topics -- [[마이크로 프론트엔드 (Micro-Frontends)]] +- [[마이크로 프론트엔드 (Micro Frontends)|마이크로 프론트엔드 (Micro-Frontends)]] - 확장 방향: 단일 저장소(Monorepo) 및 모듈화의 한계를 넘어, 초대형 엔터프라이즈 환경에서 여러 팀이 프론트엔드를 독립적으로 배포하고 운영하기 위한 런타임 통합 아키텍처로 지식을 확장합니다. -- [[시각적 회귀 테스트 (Visual Regression Testing)]] +- 시각적 회귀 테스트 (Visual Regression Testing) - 확장 방향: Storybook을 활용한 컴포넌트 고립 개발을 넘어서, Happo, Chromatic 등의 도구를 통해 코드 변경이 UI나 접근성(Accessibility)에 의도치 않은 파괴적 영향을 미쳤는지 자동 검증하는 QA 고도화 영역으로 확장합니다. --- diff --git a/10_Wiki/Development/비동기 데이터 관리.md b/10_Wiki/Development/비동기 데이터 관리.md index a26dcf51..6c178d1f 100644 --- a/10_Wiki/Development/비동기 데이터 관리.md +++ b/10_Wiki/Development/비동기 데이터 관리.md @@ -1,4 +1,4 @@ -# [[비동기 데이터 관리]] +# [[비동기 데이터 관리|비동기 데이터 관리]] ## 📌 Brief Summary 비동기 데이터 관리(서버 상태 관리)는 API에서 가져온 데이터를 클라이언트 측 애플리케이션 상태와 명확히 분리하여 처리하는 것을 의미합니다 [1]. 이는 네트워크 요청에 따른 데이터 캐싱, 동기화, 로딩 및 에러 사이클 관리를 포함하며, 현대 프론트엔드 시스템 아키텍처의 핵심 요소입니다 [1, 2]. 대규모 앱에서는 RTK Query나 TanStack Query(React Query)와 같은 특화된 도구를 사용하여 비동기 보일러플레이트를 줄이고 효율적인 캐시 관리를 수행합니다 [1, 3, 4]. @@ -23,19 +23,19 @@ ## 🔗 Knowledge Connections ### Related Concepts -- [[TanStack Query 및 RTK Query]] +- TanStack Query 및 RTK Query - 연결 이유: 서버 상태(API 데이터) 관리에 있어 캐싱, 중복 요청 제거, 자동 재요청 등을 처리하기 위한 현대적인 필수 표준 도구로 소스에서 강조되고 있기 때문입니다 [1, 2, 4]. - 이 개념을 통해 더 깊게 이해할 수 있는 부분: 비동기 데이터 관리에서 발생하는 보일러플레이트 감소 원리와 데이터 동기화 메커니즘. -- [[서버 상태 (Server State)]] +- 서버 상태 (Server State) - 연결 이유: API로부터 패치(fetch)되는 데이터는 클라이언트 상태와 성격이 완전히 달라 별도의 관리가 필요하다는 비동기 관리의 핵심 전제이기 때문입니다 [1]. - 이 개념을 통해 더 깊게 이해할 수 있는 부분: 캐싱 로딩, 에러 사이클, 서버 데이터 최신화 기법. -- [[디바운싱(Debouncing) 및 쓰로틀링(Throttling)]] +- 디바운싱(Debouncing) 및 쓰로틀링(Throttling) - 연결 이유: 잦은 사용자 이벤트로 인해 발생하는 무분별한 비동기 API 호출을 제어하여 성능을 최적화하는 구체적인 전략이기 때문입니다 [6, 7]. - 이 개념을 통해 더 깊게 이해할 수 있는 부분: 프론트엔드에서의 네트워크 최적화 및 런타임 병목 현상 방지. -- [[클린업 (Cleanup) 함수와 메모리 누수]] +- 클린업 (Cleanup) 함수와 메모리 누수 - 연결 이유: 비동기 작업 완료 전 컴포넌트가 언마운트되었을 때 발생할 수 있는 자원 낭비와 메모리 누수를 막는 필수 규칙이기 때문입니다 [8, 9]. - 이 개념을 통해 더 깊게 이해할 수 있는 부분: React 생명주기(Lifecycle)와 결합된 안전한 비동기 처리 방법. @@ -54,9 +54,9 @@ - **My Project Relevance:** 실시간 알림, 방대한 데이터의 무한 스크롤, 사용자 검색 시의 자동완성(디바운스 적용) 기능 등 복잡한 API 기반 기능이 있는 프로젝트의 성능 및 아키텍처 개선에 직접 적용됩니다 [2, 6, 7]. ### Adjacent Topics -- [[상태 관리 아키텍처 (State Management Architecture)]] +- 상태 관리 아키텍처 (State Management Architecture) - 확장 방향: 비동기 데이터 관리(서버 상태)와 로컬 상태, 전역 애플리케이션 상태가 애플리케이션 내에서 어떻게 상호작용하고 조화롭게 구성되는지 확장해서 알아봅니다 [1, 14]. -- [[성능 프로파일링 및 렌더링 최적화 (Performance Profiling & Rendering Optimization)]] +- 성능 프로파일링 및 렌더링 최적화 (Performance Profiling & Rendering Optimization) - 확장 방향: 잘못된 비동기 데이터 처리가 어떻게 불필요한 리렌더링 폭풍(re-render storm)이나 병목을 일으키는지 파악하고, React Profiler를 통해 이를 어떻게 탐지하는지 알아봅니다 [15-17]. --- diff --git a/10_Wiki/Development/프론트엔드 애플리케이션 렌더링 병목 개선.md b/10_Wiki/Development/프론트엔드 애플리케이션 렌더링 병목 개선.md index 600727cc..3148de10 100644 --- a/10_Wiki/Development/프론트엔드 애플리케이션 렌더링 병목 개선.md +++ b/10_Wiki/Development/프론트엔드 애플리케이션 렌더링 병목 개선.md @@ -1,4 +1,4 @@ -# [[프론트엔드 애플리케이션 렌더링 병목 개선]] +# [[프론트엔드 애플리케이션 렌더링 병목 개선|프론트엔드 애플리케이션 렌더링 병목 개선]] ## 📌 Brief Summary 프론트엔드 애플리케이션 렌더링 병목은 불필요하거나 과도한 컴포넌트 리렌더링으로 인해 UI 반응성이 떨어지고 상호작용 속도가 지연되는 현상을 의미합니다 [1, 2]. 이를 개선하기 위해서는 렌더링 트리거(상태, Props, Context 등)를 식별하고 메모이제이션, 리스트 가상화, 상태 분리, 동시성 렌더링(Concurrent Rendering) 기능 등을 활용해야 합니다 [3, 4]. 지속적인 프로파일링을 통해 렌더링 비용이 높은 부분을 측정하고 전략적으로 최적화를 적용하는 것이 핵심입니다 [5, 6]. @@ -28,21 +28,21 @@ ### Related Concepts #### [아키텍처/기반 기술] -- [[Context API]] +- [[Context API|Context API]] - 연결 이유: 컴포넌트 트리 깊은 곳까지 상태를 전달할 수 있으나 구독 중인 모든 컴포넌트를 리렌더링시키는 특성상 렌더링 병목의 주요 원인이 됩니다 [17]. - 이 개념을 통해 더 깊게 이해할 수 있는 부분: 브로드캐스트 기반 상태 관리의 한계와 리렌더링 발생 범위를 이해할 수 있습니다. -- [[Concurrent Rendering]] +- [[Concurrent Rendering|Concurrent Rendering]] - 연결 이유: 렌더링 작업의 우선순위를 부여하고 중단/재개할 수 있는 기술로, `useTransition` 등을 통해 무거운 렌더링이 메인 스레드를 막는 병목 현상을 방지합니다 [21]. - 이 개념을 통해 더 깊게 이해할 수 있는 부분: 반응성 지표(INP 등)를 개선하기 위한 렌더링 스케줄링 메커니즘을 이해할 수 있습니다. -- [[React Compiler]] +- [[React Compiler|React Compiler]] - 연결 이유: 수동 메모이제이션의 한계를 극복하고 빌드 타임에 자동으로 JSX 요소 단위의 메모이제이션을 적용하여 렌더링 최적화를 달성합니다 [13, 14]. - 이 개념을 통해 더 깊게 이해할 수 있는 부분: 최신 React의 렌더링 최적화가 런타임 제어에서 컴파일러 기반 정적 분석으로 넘어가는 기술적 진화를 이해할 수 있습니다. #### [구현/활용 도구] -- [[Zustand]] +- Zustand - 연결 이유: 셀렉터(Selector) 기능을 활용해 컴포넌트가 자신이 필요한 상태 조각(Slice)이 변경될 때만 리렌더링되도록 보장하여 병목을 줄이는 상태 관리 도구입니다 [18]. - 이 개념을 통해 더 깊게 이해할 수 있는 부분: 전역 상태의 파편화 관리와 불필요한 리렌더링을 차단하는 구독 최적화 패턴을 학습할 수 있습니다. -- [[List Virtualization (Windowing)]] +- List Virtualization (Windowing) - 연결 이유: 대규모 리스트에서 사용자의 화면 뷰포트에 존재하는 DOM 노드만 제한적으로 렌더링하여 DOM 트리 비대화를 막습니다 [25, 26]. - 이 개념을 통해 더 깊게 이해할 수 있는 부분: 다수의 데이터를 렌더링할 때 발생하는 메모리 및 레이아웃 페인팅 병목을 제어하는 원리를 이해할 수 있습니다. @@ -61,9 +61,9 @@ - **My Project Relevance:** 현재 유지 보수하거나 신규 구축하는 React 웹 앱에서 스크롤 끊김이나 클릭 시 반응 지연이 발생할 때, 해당 개념을 기반으로 병목이 되는 컴포넌트의 렌더링 횟수를 측정하고 적절한 최적화 도구를 즉각 적용할 수 있습니다. ### Adjacent Topics -- [[Server Components (Next.js)]] +- Server Components (Next.js) - 확장 방향: 브라우저에서의 렌더링 부하를 줄이기 위해 클라이언트 자바스크립트 번들을 최소화하고 서버에서 정적 UI를 렌더링하여 넘겨주는 아키텍처적 최적화에 대해 심도 있게 조사할 수 있습니다 [39-41]. -- [[JavaScript Memory Leaks]] +- JavaScript Memory Leaks - 확장 방향: 과도한 렌더링 외에도 클로저나 분리된 DOM 노드에 의해 자바스크립트 메모리가 해제되지 않고 누적되어 성능 저하를 일으키는 메모리 누수 식별 및 해결 방법으로 이해를 확장합니다 [42-44]. --- diff --git a/10_Wiki/Index.md b/10_Wiki/Index.md index ad44a3a7..f995736d 100644 --- a/10_Wiki/Index.md +++ b/10_Wiki/Index.md @@ -1,18 +1,18 @@ # Index: . ## 📁 Subcategories -- [[.git/Index|.git]] -- [[Decisions/Index|Decisions]] -- [[Development/Index|Development]] -- [[Management/Index|Management]] -- [[Projects/Index|Projects]] -- [[Skills/Index|Skills]] -- [[Technical_Reports/Index|Technical_Reports]] -- [[Topics/Index|Topics]] -- [[Topics_Art/Index|Topics_Art]] -- [[Topics_Biz/Index|Topics_Biz]] -- [[Topics_Blog/Index|Topics_Blog]] -- [[Topics_GD/Index|Topics_GD]] +- .git +- Decisions +- Development +- Management +- Projects +- Skills +- Technical_Reports +- Topics +- Topics_Art +- Topics_Biz +- Topics_Blog +- Topics_GD ## 📝 Documents -- [[Placeholder_Tracking_List]] +- [[Placeholder_Tracking_List|Placeholder_Tracking_List]] diff --git a/10_Wiki/Management/Agile Environments.md b/10_Wiki/Management/Agile Environments.md index dbf3a829..46a29ba3 100644 --- a/10_Wiki/Management/Agile Environments.md +++ b/10_Wiki/Management/Agile Environments.md @@ -1,4 +1,4 @@ -# [[Agile Environments]] +# [[Agile Environments|Agile Environments]] ## 📌 Brief Summary Agile Environments(애자일 환경)는 요구사항이 지속적으로 변화하는 프로젝트나 스타트업 환경을 의미합니다 [1]. 이러한 환경에서는 미래에 필요할지도 모르는 복잡한 기능을 미리 개발하기보다는 오직 현재의 요구사항에 집중하는 것이 핵심입니다 [2]. 따라서 각 기능을 독립적으로 생성하고 구현할 수 있는 유연하고 모듈화된 접근 방식이 매우 적합합니다 [3]. @@ -13,13 +13,13 @@ Agile Environments(애자일 환경)는 요구사항이 지속적으로 변화 ## 🔗 Knowledge Connections ### Related Concepts -- [[YAGNI]] +- YAGNI - 연결 이유: 애자일 환경에서 미래의 불확실한 기능을 미리 만들지 않고 현재의 요구사항에 집중하도록 이끄는 가장 핵심적인 개발 원칙입니다 [1, 2]. - 이 개념을 통해 더 깊게 이해할 수 있는 부분: 애자일 환경에서 불필요한 코드(Dead Code)의 생성을 방지하고 유지보수 비용을 최소화하는 구체적인 판단 기준을 이해할 수 있습니다 [2]. -- [[Feature-Based Structure]] +- Feature-Based Structure - 연결 이유: 애자일 방법론과 가장 잘 어울리는 아키텍처 패턴으로, 코드 베이스를 기능 단위로 분리하여 독립적인 개발을 가능하게 합니다 [3]. - 이 개념을 통해 더 깊게 이해할 수 있는 부분: 애자일 팀이 요구사항 변경에 맞춰 여러 기능을 독립적으로 확장하고 개발할 때 파일과 폴더를 어떻게 구성해야 하는지 이해할 수 있습니다 [3]. -- [[Startup Projects]] +- [[Startup Projects|Startup Projects]] - 연결 이유: 애자일 환경과 마찬가지로 요구사항이 지속적으로 변화하는 특성을 공유하며, YAGNI 원칙이 강하게 적용되는 대표적인 비즈니스 환경입니다 [1]. - 이 개념을 통해 더 깊게 이해할 수 있는 부분: 애자일 원칙이 실무에서 어떠한 형태의 프로젝트 규모나 상황(빠른 변화와 유연성 요구)에서 주로 채택되는지 파악할 수 있습니다 [1]. @@ -38,9 +38,9 @@ Agile Environments(애자일 환경)는 요구사항이 지속적으로 변화 - **My Project Relevance:** 잦은 기획 변경이 예상되는 초기 단계의 스타트업 프로젝트나 애자일 조직을 세팅할 때, 초기 개발 속도를 높이면서도 변경에 유연하게 대응하기 위한 가이드라인으로 직결됩니다 [1, 3]. ### Adjacent Topics -- [[SOLID Principles]] +- [[SOLID Principles|SOLID Principles]] - 확장 방향: 애자일 환경에서 당장의 기능을 단순하게 개발(YAGNI)하면서도, 장기적으로 애플리케이션의 규모가 커졌을 때 코드를 어떻게 유지보수 가능하게 설계할지 객체 지향적/구조적 관점에서 이해를 확장할 수 있습니다 [1, 4]. -- [[Clean Code]] +- Clean Code - 확장 방향: 빠른 변화와 반복 개발(Iteration)이 일어나는 애자일 환경 속에서, 여러 명의 개발자가 코드를 쉽게 읽고 협업할 수 있도록 하는 기본적인 코드 품질 유지 기법으로 확장이 가능합니다 [4, 5]. --- diff --git a/10_Wiki/Management/Branching Strategies.md b/10_Wiki/Management/Branching Strategies.md index 0c39642f..779ebe5c 100644 --- a/10_Wiki/Management/Branching Strategies.md +++ b/10_Wiki/Management/Branching Strategies.md @@ -1,4 +1,4 @@ -# [[Branching Strategies]] +# [[Branching Strategies|Branching Strategies]] ## 📌 Brief 소Summary Branching Strategies(브랜칭 전략)는 소프트웨어 개발 과정에서 코드 변경 사항을 관리하고 팀원 간의 협업을 조율하기 위해 버전 관리 시스템(Git 등)에서 브랜치를 생성, 병합, 유지보수하는 규칙과 워크플로우를 의미합니다. 팀의 규모와 프로젝트 요구사항에 따라 Git Flow, GitHub Flow, Trunk-Based Development, Feature Branch Workflow 등 다양한 전략이 사용됩니다. 명확한 브랜칭 전략의 도입은 메인 코드베이스의 안정성을 보장하고 병합 충돌을 방지하며 코드 리뷰와 추적성을 강화하는 핵심 역할을 합니다 [1-3]. @@ -29,21 +29,21 @@ Branching Strategies(브랜칭 전략)는 소프트웨어 개발 과정에서 ### Related Concepts #### [관계 유형 A: 아키텍처/기반 방법론] -- [[Feature Branch Workflow]] +- Feature Branch Workflow - 연결 이유: 소규모 3~5인 개발 팀에 가장 추천되는 단순하고 직관적인 브랜칭 전략의 기반 개념입니다. - 이 개념을 통해 더 깊게 이해할 수 있는 부분: 메인 브랜치를 오염시키지 않고 새로운 기능을 격리된 환경에서 개발하고 병합하는 방법론을 이해할 수 있습니다. -- [[Trunk-Based Development]] +- Trunk-Based Development - 연결 이유: 무거운 워크플로우를 탈피하여 브랜치 생명주기를 극한으로 줄이고 빠른 통합을 중시하는 최신 트렌드 모델입니다. - 이 개념을 통해 더 깊게 이해할 수 있는 부분: CI/CD 환경에서의 잦은 소규모 배포 방식과 충돌 최소화 전략을 학습할 수 있습니다. -- [[Git Flow]] +- Git Flow - 연결 이유: 브랜칭 전략의 고전적이고 체계적인 형태로서, 대형 프로젝트의 정기적 버저닝 관리를 위해 설계되었습니다. - 이 개념을 통해 더 깊게 이해할 수 있는 부분: `develop`, `release`, `hotfix` 등 개발 파이프라인에 따른 브랜치의 역할 분리 기법을 이해할 수 있습니다. #### [관계 유형 B: 구현/활용 도구 및 규칙] -- [[Pull Request & Code Review]] +- Pull Request & Code Review - 연결 이유: 브랜칭 전략이 안전하게 동작하기 위해 모든 병합 전에 필수적으로 거쳐야 하는 품질 검증 관문입니다. - 이 개념을 통해 더 깊게 이해할 수 있는 부분: 팀원 간의 비동기적 피드백 수렴, 시각적 검증, 그리고 CI 통과를 전제로 한 안전한 병합 과정을 배울 수 있습니다. -- [[Conventional Commits]] +- Conventional Commits - 연결 이유: 브랜치 병합 내역을 추적하고 가독성을 높이기 위해 전 세계적으로 통용되는 커밋 메시지 작성 표준입니다. - 이 개념을 통해 더 깊게 이해할 수 있는 부분: `feat(scope): message` 와 같은 형식의 구문을 통해 코드 히스토리 파악 및 문서 자동화를 어떻게 이룰 수 있는지 이해할 수 있습니다. @@ -62,9 +62,9 @@ Branching Strategies(브랜칭 전략)는 소프트웨어 개발 과정에서 - **My Project Relevance:** 3~5인 규모의 프로젝트에서 무거운 Git Flow의 도입을 지양하고, '단기 기능 브랜치 → PR 및 1인 이상 피어 리뷰 승인 → Squash Merge 및 브랜치 즉시 삭제'라는 단순화된 룰을 적용하여 개발 속도와 코드 품질을 동시에 챙깁니다. ### Adjacent Topics -- [[Continuous Integration / Continuous Deployment (CI/CD)]] +- Continuous Integration / Continuous Deployment (CI/CD) - 확장 방향: 브랜칭 전략에 의해 트리거(Trigger)되어 실행되는 빌드, 테스트, 배포 파이프라인의 자동화 프로세스를 깊이 알아봅니다. -- [[Feature-Sliced Design (FSD)]] +- [[Feature-Sliced Design (FSD)|Feature-Sliced Design (FSD)]] - 확장 방향: 도메인과 기능 단위로 코드를 분리하는 프론트엔드 아키텍처 방법론으로, 브랜치를 기능별로 나눌 때 충돌을 물리적으로 최소화하는 코드 구조 설계법을 탐구합니다. --- diff --git a/10_Wiki/Management/Code Review.md b/10_Wiki/Management/Code Review.md index 5436d57b..e8ba29f5 100644 --- a/10_Wiki/Management/Code Review.md +++ b/10_Wiki/Management/Code Review.md @@ -1,4 +1,4 @@ -# [[Code Review]] +# [[Code Review|Code Review]] ## 📌 Brief Summary 코드 리뷰(Code Review)는 개발자가 작성한 코드를 메인 브랜치에 병합하기 전에 팀원(동료)이 검토하여 승인하는 품질 관리 및 협업 프로세스입니다 [1, 2]. 주로 Pull Request(PR) 단계를 통해 이루어지며, 단독으로 잘못된 코드가 병합되는 것을 방지하고 팀 내 빠른 피드백 루프를 형성합니다 [1]. 최근 프론트엔드 환경에서는 단순한 코드 검토를 넘어 Storybook과 같은 도구를 CI 파이프라인과 결합한 '시각적 리뷰(Visual Review)'로 확장되어 의도치 않은 UI 변경을 방지하는 역할도 수행합니다 [3]. @@ -18,16 +18,16 @@ ### Related Concepts #### [협업 및 형상 관리 워크플로우] -- [[Pull Request (PR)]] +- [[Pull Request (PR)|Pull Request (PR)]] - 연결 이유: 코드 리뷰가 실질적으로 요청되고, 검토 피드백이 오가는 핵심 플랫폼이자 단위입니다 [1, 2]. - 이 개념을 통해 더 깊게 이해할 수 있는 부분: 브랜치 병합 전 품질 관리 게이트로서의 기능과 짧고 명확한 작업 단위 분할의 중요성을 파악할 수 있습니다. -- [[Feature Branch Workflow]] +- Feature Branch Workflow - 연결 이유: 코드 리뷰 시스템을 쉽게 도입하기 위한 가장 기본적이고 충돌이 적은 브랜치 전략입니다 [14, 15]. - 이 개념을 통해 더 깊게 이해할 수 있는 부분: 메인 브랜치를 항상 안정적으로 유지하면서, 각각의 태스크를 독립된 브랜치에서 작업하고 리뷰를 통해 검증하는 전체 흐름을 이해할 수 있습니다. #### [자동화 및 품질 검증 도구] -- [[Visual Regression Testing]] +- [[Visual Regression Testing|Visual Regression Testing]] - 연결 이유: 프론트엔드 코드 리뷰 시 육안으로 확인하기 힘든 의도치 않은 레이아웃/색상 변경을 자동화 도구가 시각적으로 찾아내어 리뷰어에게 제시합니다 [3, 9]. - 이 개념을 통해 더 깊게 이해할 수 있는 부분: Chromatic이나 Happo를 CI 파이프라인과 결합하여 PR 리뷰의 정확도를 높이고 안정적인 UI를 배포하는 프로세스를 배울 수 있습니다. @@ -49,7 +49,7 @@ ### Adjacent Topics -- [[Continuous Integration (CI)]] +- [[Continuous Integration (CI)|Continuous Integration (CI)]] - 확장 방향: PR이 올라왔을 때 코드 리뷰를 돕기 위해 사전에 테스트 통과 여부, 빌드 성공 여부 등을 자동으로 검사해주는 자동화 파이프라인의 구축에 대해 학습할 수 있습니다 [7, 19]. --- diff --git a/10_Wiki/Management/Git Workflow.md b/10_Wiki/Management/Git Workflow.md index 5dc64fac..83d81bbb 100644 --- a/10_Wiki/Management/Git Workflow.md +++ b/10_Wiki/Management/Git Workflow.md @@ -1,4 +1,4 @@ -# [[Git Workflow]] +# [[Git Workflow|Git Workflow]] ## 📌 Brief Summary Git Workflow(깃 워크플로우)는 팀 환경에서 코드 변경 사항을 관리하고 협업하기 위한 체계적이고 구조화된 접근 방식입니다 [1, 2]. 이는 기능 브랜치(Feature-branch), 트렁크 기반(Trunk-based), Git Flow 등 다양한 전략을 포괄하며, 충돌을 방지하고 `main` 브랜치의 배포 가능 상태를 보장하는 것을 목표로 합니다 [2-4]. 일관된 브랜치 명명 규칙, 커밋 메시지 규약, 풀 리퀘스트(PR)와 리뷰 절차를 도입함으로써 잠재적인 혼돈을 예측 가능한 릴리스 흐름으로 전환할 수 있습니다 [1, 5, 6]. @@ -30,24 +30,24 @@ Git Workflow(깃 워크플로우)는 팀 환경에서 코드 변경 사항을 ### Related Concepts #### [관계 유형 A (아키텍처/기반 기술)] -- `[[Trunk-Based Development]]` +- `Trunk-Based Development` - 연결 이유: Git Workflow를 구성하는 핵심 전략 중 하나로, 빠른 통합을 목적으로 하는 방법론입니다 [2]. - 이 개념을 통해 더 깊게 이해할 수 있는 부분: 짧은 수명의 브랜치, 빈번한 병합, 기능 플래그(Feature Flags) 활용이 프로젝트 배포 속도에 어떻게 기여하는지 이해할 수 있습니다 [9, 12]. -- `[[Git Flow]]` +- `Git Flow` - 연결 이유: 구조가 복잡한 대규모 프로젝트의 릴리스를 관리하기 위해 만들어진 전통적 브랜칭 모델입니다 [2, 10]. - 이 개념을 통해 더 깊게 이해할 수 있는 부분: `develop`, `release`, `hotfix` 등 다중 브랜치 전략이 왜 오버헤드를 유발하면서도 엔터프라이즈 환경에서 사용되는지 파악할 수 있습니다 [8, 10]. #### [관계 유형 B (구현/활용 도구)] -- `[[Conventional Commits]]` +- `Conventional Commits` - 연결 이유: 팀의 일관된 코드베이스 히스토리 관리를 위해 Git 커밋 메시지 작성에 적용되는 업계 표준 규칙입니다 [6, 16]. - 이 개념을 통해 더 깊게 이해할 수 있는 부분: `feat:`, `fix:`, `chore:`와 같은 접두사가 리뷰어의 코드 이해도를 어떻게 높이고 자동화된 릴리스에 기여하는지 배울 수 있습니다 [6, 16]. -- `[[Pull Requests (PR)]]` +- `Pull Requests (PR)` - 연결 이유: 브랜치의 코드를 `main`으로 병합하기 전, 협업 팀원들이 코드를 검토하는 핵심 관문입니다 [13, 16]. - 이 개념을 통해 더 깊게 이해할 수 있는 부분: 브랜치 보호 설정, 동료 리뷰 요구(1 review required), 지속적 통합(CI) 체크가 시스템 안정성 유지에 어떻게 필수적으로 작용하는지 이해할 수 있습니다 [16, 17]. -- `[[Ticket IDs (Traceability)]]` +- `Ticket IDs (Traceability)` - 연결 이유: 코드의 변경 사항이 어떤 비즈니스 요구사항(예: Jira 티켓)에 의해 발생했는지를 연결하는 도구적 장치입니다 [5, 22]. - 이 개념을 통해 더 깊게 이해할 수 있는 부분: `PROJ-123` 형태의 티켓 번호를 브랜치와 커밋에 삽입함으로써 리뷰어에게 맥락을 제공하고, 문서화 및 작업 추적(Traceability)을 어떻게 달성하는지 알 수 있습니다 [5, 22]. @@ -66,9 +66,9 @@ Git Workflow(깃 워크플로우)는 팀 환경에서 코드 변경 사항을 - **My Project Relevance:** 현재 진행하는 3인 규모의 프로젝트 등에서는 Git Flow의 무거운 절차를 피하고, 항상 배포 가능한 안정적인 `main` 브랜치를 기준으로 짧은 기능 브랜치를 생성하여 빠른 리뷰와 피드백을 주고받는 방식을 즉각 도입할 수 있습니다 [4, 8]. ### Adjacent Topics -- `[[CI/CD (Continuous Integration/Continuous Deployment)]]` +- `CI/CD (Continuous Integration/Continuous Deployment)` - 확장 방향: PR을 생성하거나 병합할 때 코드를 자동으로 테스트하고 빌드, 배포하는 인프라 파이프라인 구성 방법론으로 확장하여 조사. -- `[[Semantic Versioning (SemVer)]]` +- `Semantic Versioning (SemVer)` - 확장 방향: Git 태그(Tag)와 Conventional Commits를 활용하여 소프트웨어의 버전을 체계적이고 일관성 있게 부여하는 방법으로 확장. --- diff --git a/10_Wiki/Management/GitHub Flow.md b/10_Wiki/Management/GitHub Flow.md index 2214b4bc..4d9f663a 100644 --- a/10_Wiki/Management/GitHub Flow.md +++ b/10_Wiki/Management/GitHub Flow.md @@ -1,4 +1,4 @@ -# [[GitHub Flow]] +# [[GitHub Flow|GitHub Flow]] ## 📌 Brief Summary GitHub Flow는 복잡한 Git Flow의 대안으로 사용되는 가볍고 단순한 브랜치 기반 워크플로우입니다 [1, 2]. 이 방식은 항상 배포 가능한 상태(deployable)를 유지하는 `main` 브랜치를 중심으로 작동하며, 개발자는 새로운 작업을 위해 짧은 주기의 기능 브랜치(feature branch)를 생성합니다 [3-5]. 변경된 코드는 동료의 코드 리뷰와 CI/CD 테스트를 모두 통과한 후 오직 Pull Request(PR)를 통해서만 `main`에 병합됩니다 [1, 6]. @@ -25,18 +25,18 @@ GitHub Flow는 복잡한 Git Flow의 대안으로 사용되는 가볍고 단순 ### Related Concepts #### [관계 유형 A: 아키텍처/기반 기술 (개발 워크플로우)] -- [[Git Flow]] +- Git Flow - 연결 이유: GitHub Flow와 자주 비교되는 분기 전략으로, 프로젝트의 복잡성에 따라 두 전략 사이를 마이그레이션하는 경우가 많습니다 [2, 12]. - 이 개념을 통해 더 깊게 이해할 수 있는 부분: `develop`, `release`, `hotfix` 브랜치를 사용하는 Git Flow를 이해함으로써, 상대적으로 GitHub Flow가 생략한 구조적 복잡성과 그에 따른 속도/단순성의 이점을 명확히 비교할 수 있습니다. -- [[Trunk-Based Development]] +- Trunk-Based Development - 연결 이유: 소규모 팀에서 빠르고 충돌 없는 병합을 위해 도입할 수 있는 또 다른 경량 워크플로우입니다 [3, 16]. - 이 개념을 통해 더 깊게 이해할 수 있는 부분: 극단적으로 짧은 생명주기의 브랜치를 사용하거나 메인에 빈번히 직접 병합하는 철학을 통해 CI(지속적 통합)의 본질을 더 깊게 이해할 수 있습니다. #### [관계 유형 B: 구현/활용 도구] -- [[Pull Request]] +- [[풀 리퀘스트 (Pull Request)|Pull Request]] - 연결 이유: GitHub Flow에서 코드 병합을 수행하고 팀원 간의 협업 및 리뷰를 진행하는 가장 핵심적인 메커니즘입니다 [8, 10]. - 이 개념을 통해 더 깊게 이해할 수 있는 부분: 코드 품질 통제, 피어 리뷰(Peer Review)의 역할 및 CI/CD 훅(Hook)이 작동하는 방식을 구체적으로 이해할 수 있습니다. -- [[CI/CD]] +- [[CI_CD|CI/CD]] - 연결 이유: `main` 브랜치를 항상 배포 가능한 상태로 유지하기 위해 배후에서 코드를 검증하는 필수 자동화 파이프라인입니다 [1, 6]. - 이 개념을 통해 더 깊게 이해할 수 있는 부분: 왜 수동 병합이 위험한지, PR 리뷰가 끝난 코드가 어떻게 안전하게 프로덕션 레벨까지 배포되는지의 전 과정을 파악할 수 있습니다. @@ -55,9 +55,9 @@ GitHub Flow는 복잡한 Git Flow의 대안으로 사용되는 가볍고 단순 - **My Project Relevance:** 3~5명의 소규모 팀에서 충돌을 최소화하면서도 빠른 피드백과 릴리스가 필요한 현재 프로젝트 상황에, 불필요한 절차를 없애고 안정성을 보장하는 가장 이상적인 협업 모델로 적용할 수 있습니다. ### Adjacent Topics -- [[Conventional Commits]] +- Conventional Commits - 확장 방향: 커밋 메시지를 `feat:`, `fix:`, `chore:` 등의 규격으로 통일함으로써, PR 내용의 가독성을 높이고 향후 릴리스 노트를 자동화하는 방향으로 지식을 확장할 수 있습니다. -- [[Issue Tracking System]] +- Issue Tracking System - 확장 방향: 코드 구현(GitHub)과 요구사항 정의(JIRA, Linear 등)를 연결하여 프로젝트 관리 수준을 높이고 변경 사항의 비즈니스 맥락(Traceability)을 추적하는 방법론으로 확장됩니다. --- diff --git a/10_Wiki/Management/Index.md b/10_Wiki/Management/Index.md index c9c07795..f06399ff 100644 --- a/10_Wiki/Management/Index.md +++ b/10_Wiki/Management/Index.md @@ -1,5 +1,5 @@ # Index: Management ## 📁 Subcategories -- [[System/Index|System]] +- System diff --git a/10_Wiki/Management/System/Antigravity_Agent_System_v1.md b/10_Wiki/Management/System/Antigravity_Agent_System_v1.md index 59b44abb..6ad20e88 100644 --- a/10_Wiki/Management/System/Antigravity_Agent_System_v1.md +++ b/10_Wiki/Management/System/Antigravity_Agent_System_v1.md @@ -1,12 +1,12 @@ --- id: 550e8400-e29b-41d4-a716-446655440007 -category: "[[10_Wiki/Management/System]]" +category: "10_Wiki/Management/System" confidence_score: 0.99 tags: [antigravity, agent, collaboration, governance] last_reinforced: 2026-04-21 --- -# [[Antigravity 에이전트 협업 시스템 v1.0]] +# Antigravity 에이전트 협업 시스템 v1.0 ## 📌 한 줄 통찰 (The Karpathy Summary) > 에이전트 간의 엄격한 핸드오버 계약과 반려권(Veto) 행사를 통해 '가혹한 무결성'과 '자율적 진화'를 동시에 달성함. @@ -25,6 +25,6 @@ last_reinforced: 2026-04-21 - **정책 변화:** "Insanely Great" 하지 않은 모든 결과물은 반려(Veto) 대상임. ## 🔗 지식 연결 (Graph) -- **Parent:** [[10_Wiki/Management/System]] -- **Related:** [[10_Wiki/Global/Universal_Knowledge_Bridge]], [[10_Wiki/Projects/Skybound/HUD_UI_Refinement]] -- **Raw Source:** [[00_Raw/2026-04-21-Antigravity_Agent_System_Overhaul]] +- **Parent:** 10_Wiki/Management/System +- **Related:** 10_Wiki/Global/Universal_Knowledge_Bridge, 10_Wiki/Projects/Skybound/HUD_UI_Refinement +- **Raw Source:** 00_Raw/2026-04-21-Antigravity_Agent_System_Overhaul diff --git a/10_Wiki/Management/System/Index.md b/10_Wiki/Management/System/Index.md index d1a154d3..f25d45e4 100644 --- a/10_Wiki/Management/System/Index.md +++ b/10_Wiki/Management/System/Index.md @@ -1,4 +1,4 @@ # Index: Management > System ## 📝 Documents -- [[Antigravity_Agent_System_v1]] +- [[Antigravity_Agent_System_v1|Antigravity_Agent_System_v1]] diff --git a/10_Wiki/Management/Team Collaboration.md b/10_Wiki/Management/Team Collaboration.md index cd5d477d..9019ce29 100644 --- a/10_Wiki/Management/Team Collaboration.md +++ b/10_Wiki/Management/Team Collaboration.md @@ -1,4 +1,4 @@ -# [[Team Collaboration]] +# [[Team Collaboration|Team Collaboration]] ## 📌 Brief Summary 프론트엔드 개발에서 'Team Collaboration(팀 협업)'이란 다수의 개발자가 동일한 코드베이스에서 효율적으로 함께 작업할 수 있도록 지원하는 실천 방식, 아키텍처, 그리고 워크플로우를 의미한다 [1, 2]. 이는 일관된 폴더 구조, 명명 규칙, 상태 관리 패턴 및 Git 브랜칭 전략을 확립하여 개발자 간의 충돌과 소통 비용을 최소화하는 것을 목표로 한다 [2-4]. 성공적인 협업은 린팅이나 포매팅과 같은 자동화된 도구를 통한 엄격한 코드 거버넌스와 명확한 코드 리뷰 문화를 바탕으로 애플리케이션과 팀이 확장될 때 안정성을 유지하도록 돕는다 [5-7]. @@ -23,21 +23,21 @@ ### Related Concepts #### [관계 유형 A (협업/코드 관리 프로세스)] -- [[Git Branching Strategies]] +- Git Branching Strategies - 연결 이유: 다수의 개발자가 동시에 코드를 작성할 때 충돌을 방지하고 통합 과정을 관리하기 위한 핵심 규약이기 때문이다 [3, 34]. - 이 개념을 통해 더 깊게 이해할 수 있는 부분: Pull Request, 코드 리뷰, 브랜치 명명 규칙, Trunk-based 워크플로우 등 실제 팀 운영 방식 [7, 35]. -- [[Commit Message Conventions]] +- Commit Message Conventions - 연결 이유: 변경 사항의 의도와 작업 내역(버그 픽스, 기능 추가 등)을 다른 팀원들에게 명확히 전달하는 소통의 도구이기 때문이다 [36]. - 이 개념을 통해 더 깊게 이해할 수 있는 부분: 티켓 ID 통합, `feat:`, `fix:`와 같은 접두사를 통한 변경 이력의 자동화 및 스캐닝 [14, 36, 37]. #### [관계 유형 B (아키텍처 및 거버넌스 도구)] -- [[Feature-Sliced Design]] +- [[Feature-Sliced Design|Feature-Sliced Design]] - 연결 이유: 코드를 기술적 계층이 아닌 비즈니스 기능(Feature) 중심으로 분리하여, 여러 팀이 서로 간섭 없이 독립적으로 작업할 수 있는 환경을 제공한다 [16, 38]. - 이 개념을 통해 더 깊게 이해할 수 있는 부분: 도메인 주도 설계의 프론트엔드 적용, 명시적 퍼블릭 API를 통한 모듈 캡슐화와 결합도 낮추기 [38-40]. -- [[Automated Governance]] +- Automated Governance - 연결 이유: 사람의 수동 확인에 의존하지 않고 ESLint, Prettier, Husky 등으로 코드 컨벤션과 아키텍처 룰(의존성 방향 등)을 시스템적으로 강제한다 [6, 20]. - 이 개념을 통해 더 깊게 이해할 수 있는 부분: CI/CD 파이프라인에서의 코드 품질 보증 및 팀원 간의 스타일 분쟁 방지 [20]. -- [[Redux vs Zustand in Teams]] +- Redux vs Zustand in Teams - 연결 이유: 팀의 규모(소규모 vs 엔터프라이즈)에 따라 상태 관리 도구의 선택이 협업의 일관성에 결정적인 영향을 미치기 때문이다 [5, 24, 27]. - 이 개념을 통해 더 깊게 이해할 수 있는 부분: 개발자의 자율성 부여와 일관성 강제(Boilerplate) 사이의 아키텍처적 트레이드오프 [22, 41]. @@ -59,11 +59,11 @@ ### Adjacent Topics -- [[Code Review Practices]] +- Code Review Practices - 확장 방향: 작은 단위의 Pull Request 유지, 시각적 리뷰 도구의 도입, 효율적인 동료 피드백 제공 등 코드 리뷰 자체의 품질과 속도를 높이는 방법론 [37, 45]. -- [[CI/CD Pipelines]] +- CI/CD Pipelines - 확장 방향: 팀원의 코드가 `main`에 병합되기 전, 자동으로 테스트와 린팅을 수행하고 배포까지 이어지는 인프라 및 데브옵스 환경 [7]. -- [[Visual Regression Testing]] +- [[Visual Regression Testing|Visual Regression Testing]] - 확장 방향: Storybook 및 Chromatic을 활용해 UI 변경 사항을 리뷰어가 시각적으로 직접 확인하고, 예기치 않은 레이아웃 깨짐을 방지하는 협업 기술 [45, 46]. --- diff --git a/10_Wiki/Management/Version Control.md b/10_Wiki/Management/Version Control.md index 2da5260d..379be486 100644 --- a/10_Wiki/Management/Version Control.md +++ b/10_Wiki/Management/Version Control.md @@ -1,4 +1,4 @@ -# [[Version Control]] +# [[Version Control|Version Control]] ## 📌 Brief Summary 버전 관리(Version Control)는 소규모부터 대규모 팀에 이르기까지 코드의 변경 사항을 추적하고, 병합 충돌을 방지하며 안정적인 배포를 가능하게 하는 필수적인 협업 도구 및 거버넌스 프로세스입니다 [1, 2]. 개발팀은 프로젝트 규모와 팀의 숙련도에 따라 Feature-Branch 워크플로우, Trunk-based 개발, Git Flow 등 다양한 브랜칭 전략을 선택하여 사용합니다 [3, 4]. 효과적인 버전 관리는 브랜치와 커밋에 티켓 ID 연동, 의미 있는 커밋 메시지 작성, 작고 빈번한 커밋, 그리고 엄격한 풀 리퀘스트(PR) 리뷰 등의 모범 사례를 준수하여 코드베이스의 품질과 추적성을 유지하는 것을 목표로 합니다 [2, 5]. @@ -27,21 +27,21 @@ ### Related Concepts #### [워크플로우 및 방법론 (Workflow Strategies)] -- [[Feature Branch Workflow]] +- Feature Branch Workflow - 연결 이유: 버그 수정이나 새 기능 개발 시 `main`과 분리된 독립적이고 짧은 수명의 브랜치를 사용하는 전략이기 때문입니다. [6, 7] - 이 개념을 통해 더 깊게 이해할 수 있는 부분: 어떻게 `main` 브랜치의 안정성을 훼손하지 않으면서도 다수의 개발자가 코드를 작성하고 충돌을 방지할 수 있는지 이해할 수 있습니다. -- [[Trunk-Based Development]] +- Trunk-Based Development - 연결 이유: 모든 개발자가 빈번하게 짧은 주기로 메인 브랜치(Trunk)에 코드를 병합하는 방법론이기 때문입니다. [8, 9] - 이 개념을 통해 더 깊게 이해할 수 있는 부분: 지속적 통합(CI)을 어떻게 보장하며, 장기 브랜치로 인해 발생하는 문제를 어떻게 회피하는지 파악할 수 있습니다. -- [[Git Flow]] +- Git Flow - 연결 이유: 릴리스용 브랜치와 개발용 브랜치를 명확히 나누어 복잡한 프로젝트 릴리스를 관리하는 아키텍처이기 때문입니다. [9, 19] - 이 개념을 통해 더 깊게 이해할 수 있는 부분: 팀의 규모와 배포 스케줄에 따라 워크플로우에 어떤 구조적 레이어를 추가해야 하는지 이해할 수 있습니다. #### [협업 및 품질 관리 (Quality Assurance & Collaboration)] -- [[Pull Request (PR)]] +- [[Pull Request (PR)|Pull Request (PR)]] - 연결 이유: 코드를 주 브랜치에 병합하기 전, 변경 사항을 동료에게 검토받는 핵심 품질 통제 절차이기 때문입니다. [13, 16] - 이 개념을 통해 더 깊게 이해할 수 있는 부분: 코드 리뷰와 CI 테스트 자동화가 어떻게 실제 코드 품질을 유지하고 팀 내 지식 공유를 돕는지 이해할 수 있습니다. -- [[Conventional Commits]] +- Conventional Commits - 연결 이유: `feat:`, `fix:`와 같이 표준화된 접두사를 사용하여 커밋 메시지의 의도를 명확하게 만드는 구문 규칙이기 때문입니다. [5, 13] - 이 개념을 통해 더 깊게 이해할 수 있는 부분: 커밋 히스토리를 통한 변경 사항 추적성 확보와 릴리스 노트 자동화에 어떻게 기여하는지 이해할 수 있습니다. @@ -60,9 +60,9 @@ - **My Project Relevance:** 프론트엔드/React 개발 프로젝트 등의 팀 단위 협업 시, 불필요한 절차 없이 코드 충돌을 최소화하고 추적 가능한 변경 내역을 보장하는 협업 기준을 마련하는 데 즉각적으로 활용할 수 있습니다 [1, 22]. ### Adjacent Topics -- [[Continuous Integration / Continuous Deployment (CI/CD)]] +- Continuous Integration / Continuous Deployment (CI/CD) - 확장 방향: PR 단계에서 자동화된 테스트 및 린팅을 실행하고, 메인 브랜치 병합 시 배포를 자동화하여 버전 관리 도구와 어떻게 시너지를 내는지 조사. [1, 19] -- [[Issue Tracking Systems]] +- Issue Tracking Systems - 확장 방향: JIRA나 GitHub Issues 등의 도구가 Git의 티켓 ID 거버넌스와 결합되어 요구사항부터 코드 변경까지 어떻게 완벽한 추적성(Traceability)을 보장하는지 조사. [2, 23] --- diff --git a/10_Wiki/Projects/ConnectAI/Core_Optimization_Plan.md b/10_Wiki/Projects/ConnectAI/Core_Optimization_Plan.md index 07f1ff22..e2ce5c41 100644 --- a/10_Wiki/Projects/ConnectAI/Core_Optimization_Plan.md +++ b/10_Wiki/Projects/ConnectAI/Core_Optimization_Plan.md @@ -1,13 +1,13 @@ --- id: a7f8e1c2-d3b4-4e5f-9a0b-1c2d3e4f5a6b -category: "[[10_Wiki/Projects/ConnectAI]]" +category: "10_Wiki/Projects/ConnectAI" confidence_score: 0.90 tags: [connectai, optimization, python, architecture, performance] last_reinforced: 2026-05-01 github_commit: "initial-wikification" --- -# [[ConnectAI Core Optimization Plan (Python Core)]] +# ConnectAI Core Optimization Plan (Python Core) ## 📌 한 줄 통찰 (The Karpathy Summary) > ConnectAI의 성능 병목을 해결하기 위해 $O(N^2)$ 알고리즘을 $O(N \log N)$으로 고도화하고, 동기식 I/O를 비동기 파이프라인으로 전환하며, 옵저버 패턴을 통해 모듈 간 결합도를 제거하는 전면적인 코어 아키텍처 개편 계획이다. @@ -36,9 +36,9 @@ github_commit: "initial-wikification" - **비동기 오버헤드**: 단순 연산 위주 작업에서는 `asyncio` 전환이 오히려 컨텍스트 스위칭 비용만 늘릴 수 있으므로 프로파일링 필수. ## 🔗 지식 연결 (Graph) -- **Parent**: [[10_Wiki/Projects/ConnectAI]] -- **Related**: [[Observer Pattern]], [[KD-Tree]], [[Asynchronous I/O]] -- **Raw Source**: [[00_Raw/system_analysis_and_improvement_plan]] +- **Parent**: 10_Wiki/Projects/ConnectAI +- **Related**: Observer Pattern, KD-Tree, Asynchronous I/O +- **Raw Source**: 00_Raw/system_analysis_and_improvement_plan ## 💻 GitHub 동기화 자동화 워크플로우 1. Stage: git add . diff --git a/10_Wiki/Projects/Index.md b/10_Wiki/Projects/Index.md index ab8766f1..152a0fa0 100644 --- a/10_Wiki/Projects/Index.md +++ b/10_Wiki/Projects/Index.md @@ -1,5 +1,5 @@ # Index: Projects ## 📁 Subcategories -- [[Skybound/Index|Skybound]] +- Skybound diff --git a/10_Wiki/Projects/Skybound/Architecture_Refactor.md b/10_Wiki/Projects/Skybound/Architecture_Refactor.md index eef264c6..bd01828f 100644 --- a/10_Wiki/Projects/Skybound/Architecture_Refactor.md +++ b/10_Wiki/Projects/Skybound/Architecture_Refactor.md @@ -1,12 +1,12 @@ --- id: 550e8400-e29b-41d4-a716-446655440001 -category: "[[10_Wiki/Projects/Skybound]]" +category: "10_Wiki/Projects/Skybound" confidence_score: 0.95 tags: [skybound, architecture, performance, zero-leak] last_reinforced: 2026-04-21 --- -# [[Skybound 아키텍처 리팩토링]] +# Skybound 아키텍처 리팩토링 ## 📌 한 줄 통찰 (The Karpathy Summary) > 엔진-모듈 간의 '의도(Intent)' 기반 통신과 선언적 파이프라인 도입을 통해 시스템 신뢰도와 성능을 동시에 확보하는 'Zero-Leak' 아키텍처로 진화함. @@ -24,6 +24,6 @@ last_reinforced: 2026-04-21 - **정책 변화:** 성능보다는 '예측 가능성(Predictability)'을 우선하는 설계 원칙 수립. ## 🔗 지식 연결 (Graph) -- **Parent:** [[10_Wiki/Projects/Skybound]] -- **Related:** [[10_Wiki/Decisions/Skybound/IDE_Stability_Fix]], [[10_Wiki/Decisions/Skybound/Frame_Type_Restoration]] -- **Raw Source:** [[00_Raw/2026-04-21-Skybound_Architecture_Refactor_Plan]] +- **Parent:** 10_Wiki/Projects/Skybound +- **Related:** 10_Wiki/Decisions/Skybound/IDE_Stability_Fix, 10_Wiki/Decisions/Skybound/Frame_Type_Restoration +- **Raw Source:** 00_Raw/2026-04-21-Skybound_Architecture_Refactor_Plan diff --git a/10_Wiki/Projects/Skybound/HUD_UI_Refinement.md b/10_Wiki/Projects/Skybound/HUD_UI_Refinement.md index 14c0ab43..93b172c4 100644 --- a/10_Wiki/Projects/Skybound/HUD_UI_Refinement.md +++ b/10_Wiki/Projects/Skybound/HUD_UI_Refinement.md @@ -1,12 +1,12 @@ --- id: 550e8400-e29b-41d4-a716-446655440003 -category: "[[10_Wiki/Projects/Skybound]]" +category: "10_Wiki/Projects/Skybound" confidence_score: 0.98 tags: [skybound, ui, ux, minimalism] last_reinforced: 2026-04-21 --- -# [[Skybound HUD UI 최적화]] +# Skybound HUD UI 최적화 ## 📌 한 줄 통찰 (The Karpathy Summary) > 중복된 점수 노출을 제거하고 "High Score Sync" 맥락으로 정보를 통합하여 "Digital Cockpit" 미학을 실현함. @@ -23,6 +23,6 @@ last_reinforced: 2026-04-21 - **정책 변화:** UI 요소 추가 시 '중복 여부'를 반드시 검수하는 체크리스트 도입. ## 🔗 지식 연결 (Graph) -- **Parent:** [[10_Wiki/Projects/Skybound]] -- **Related:** [[10_Wiki/Management/System/Antigravity_Agent_System_v1]] -- **Raw Source:** [[00_Raw/2026-04-21-Skybound_HUD_UI_Refinement]] +- **Parent:** 10_Wiki/Projects/Skybound +- **Related:** 10_Wiki/Management/System/Antigravity_Agent_System_v1 +- **Raw Source:** 00_Raw/2026-04-21-Skybound_HUD_UI_Refinement diff --git a/10_Wiki/Projects/Skybound/Index.md b/10_Wiki/Projects/Skybound/Index.md index 950a4c97..bc42e401 100644 --- a/10_Wiki/Projects/Skybound/Index.md +++ b/10_Wiki/Projects/Skybound/Index.md @@ -1,5 +1,5 @@ # Index: Projects > Skybound ## 📝 Documents -- [[Architecture_Refactor]] -- [[HUD_UI_Refinement]] +- [[Architecture_Refactor|Architecture_Refactor]] +- [[HUD_UI_Refinement|HUD_UI_Refinement]] diff --git a/10_Wiki/Skills/BuildSystem/Incremental_Build.md b/10_Wiki/Skills/BuildSystem/Incremental_Build.md index ee9bc719..1092b7a2 100644 --- a/10_Wiki/Skills/BuildSystem/Incremental_Build.md +++ b/10_Wiki/Skills/BuildSystem/Incremental_Build.md @@ -1,12 +1,12 @@ --- id: 550e8400-e29b-41d4-a716-446655440005 -category: "[[10_Wiki/Skills/BuildSystem]]" +category: "10_Wiki/Skills/BuildSystem" confidence_score: 0.97 tags: [build, devops, automation, versioning] last_reinforced: 2026-04-21 --- -# [[증분형 빌드 관리 시스템]] +# 증분형 빌드 관리 시스템 ## 📌 한 줄 통찰 (The Karpathy Summary) > 빌드 결과물을 버전별로 격리된 폴더에 저장하여 배포 이력을 보존하고 롤백 안정성을 확보함. @@ -23,6 +23,6 @@ last_reinforced: 2026-04-21 - **정책 변화:** 모든 빌드 요청은 반드시 고유한 버전 번호를 가져야 함. ## 🔗 지식 연결 (Graph) -- **Parent:** [[10_Wiki/Skills/BuildSystem]] -- **Related:** [[10_Wiki/Projects/Skybound/Architecture_Refactor]] -- **Raw Source:** [[00_Raw/2026-04-21-Skybound_Incremental_Build_System]] +- **Parent:** 10_Wiki/Skills/BuildSystem +- **Related:** 10_Wiki/Projects/Skybound/Architecture_Refactor +- **Raw Source:** 00_Raw/2026-04-21-Skybound_Incremental_Build_System diff --git a/10_Wiki/Skills/BuildSystem/Index.md b/10_Wiki/Skills/BuildSystem/Index.md index 64d3a7a7..4b19bf60 100644 --- a/10_Wiki/Skills/BuildSystem/Index.md +++ b/10_Wiki/Skills/BuildSystem/Index.md @@ -1,4 +1,4 @@ # Index: Skills > BuildSystem ## 📝 Documents -- [[Incremental_Build]] +- [[Incremental_Build|Incremental_Build]] diff --git a/10_Wiki/Skills/Connect-AI-Architecture.md b/10_Wiki/Skills/Connect-AI-Architecture.md index 20de2c7b..c7d6f710 100644 --- a/10_Wiki/Skills/Connect-AI-Architecture.md +++ b/10_Wiki/Skills/Connect-AI-Architecture.md @@ -1,6 +1,6 @@ --- id: {{UUID}} -category: "[[10_Wiki/Skills]]" +category: "10_Wiki/Skills" confidence_score: 1.0 tags: [ai, architecture, git-sync, automation, connect-ai] last_reinforced: 2026-04-29 @@ -29,5 +29,5 @@ last_reinforced: 2026-04-29 - **보안 정책**: Zero Cloud API 원칙에 따라 모든 연산은 로컬에서 수행되지만, GitHub 동기화 시 개인 인증(Credential) 관리가 보안의 핵심 변수로 작용함. ## 🔗 지식 연결 (Graph) -- [[WIKIFICATION_PROTOCOL]], [[P-Reinforce_Skill]], [[System_Manual]] +- [[WIKIFICATION_PROTOCOL|WIKIFICATION_PROTOCOL]], [[P-Reinforce_Skill|P-Reinforce_Skill]], [[System_Manual|System_Manual]] - **Raw Source:** E:/Wiki/Wonseok_AI_original/ARCHITECTURE.md diff --git a/10_Wiki/Skills/Index.md b/10_Wiki/Skills/Index.md index 6d985e62..4f6254a3 100644 --- a/10_Wiki/Skills/Index.md +++ b/10_Wiki/Skills/Index.md @@ -1,7 +1,7 @@ # Index: Skills ## 📁 Subcategories -- [[BuildSystem/Index|BuildSystem]] +- BuildSystem ## 📝 Documents -- [[P-Reinforce_Skill]] +- [[P-Reinforce_Skill|P-Reinforce_Skill]] diff --git a/10_Wiki/Skills/P-Reinforce_Skill.md b/10_Wiki/Skills/P-Reinforce_Skill.md index be62c3c3..29b583a0 100644 --- a/10_Wiki/Skills/P-Reinforce_Skill.md +++ b/10_Wiki/Skills/P-Reinforce_Skill.md @@ -6,7 +6,7 @@ 1. **Knowledge Ingestion**: `knowledge/` 폴더에 존재하는 모든 마크다운 파일을 정기적으로 `00_Raw/`의 날짜별 폴더로 자동 복사(Ingestion)하여 시스템의 먹이로 제공한다. 2. **Real-time Monitoring**: `00_Raw/` 폴더의 모든 입력을 실시간 모니터링하고 지식화하라. 3. **Autonomous Structure**: 폴더 구조를 고정하지 말고, 지식의 맥락에 따라 스스로 '폴더 트리'를 설계하고 확장하라. -4. **Knowledge Synthesis**: 지식의 파편들을 [[쌍방향 링크]]로 엮어 하나의 거대한 '외부 뇌'를 구축하라. +4. **Knowledge Synthesis**: 지식의 파편들을 쌍방향 링크로 엮어 하나의 거대한 '외부 뇌'를 구축하라. 5. **Version Preservation**: 모든 변화를 GitHub에 커밋하여 지식의 타임라인을 보존하라. 6. **Meeting Archiving**: 문서 제목에 **'회의'**라는 키워드가 포함될 경우, `10_Wiki/Topics_meeting/` 폴더에 자동으로 복사본을 생성하여 보관하라. @@ -41,14 +41,14 @@ root/ ## 📝 지식 문서 변환 규격 --- id: {{UUID}} -category: "[[10_Wiki/Path/To/Folder]]" +category: "10_Wiki/Path/To/Folder" confidence_score: 0.0 ~ 1.0 (RL 기반 확신도) tags: [tag1, tag2] last_reinforced: {{DATE}} github_commit: "{{commit_hash}}" --- -# [[문서 제목]] +# 문서 제목 ## 📌 한 줄 통찰 (The Karpathy Summary) > 이 지식의 핵심을 꿰뚫는 단 한 문장. @@ -58,13 +58,13 @@ github_commit: "{{commit_hash}}" - **세부 내용:** (불렛포인트 위주의 간결한 정리) ## ⚠️ 모순 및 업데이트 (Contradictions & RL Update) -- **과거 데이터와의 충돌:** [[이전_문서]]와 달라진 점 기록. +- **과거 데이터와의 충돌:** 이전_문서와 달라진 점 기록. - **정책 변화:** 이 문서를 통해 강화된 분류 기준 설명. ## 🔗 지식 연결 (Graph) -- **Parent:** [[상위_카테고리]] -- **Related:** [[연관_개념_A]], [[연관_개념_B]] -- **Raw Source:** [[00_Raw/YYYY-MM-DD/Original_Note]] +- **Parent:** 상위_카테고리 +- **Related:** 연관_개념_A, 연관_개념_B +- **Raw Source:** 00_Raw/YYYY-MM-DD/Original_Note ## 💻 GitHub 동기화 자동화 워크플로우 1. Stage: git add . diff --git a/10_Wiki/Skills/knowledge_inventory_1535.json b/10_Wiki/Skills/knowledge_inventory_1535.json deleted file mode 100644 index e69de29b..00000000 diff --git a/10_Wiki/Technical_Reports/Index.md b/10_Wiki/Technical_Reports/Index.md index 16850901..91ea53a4 100644 --- a/10_Wiki/Technical_Reports/Index.md +++ b/10_Wiki/Technical_Reports/Index.md @@ -1,5 +1,5 @@ # Index: Technical_Reports ## 📝 Documents -- [[2026-04-22_Boss_Battle_System_Implementation]] -- [[2026-04-22_Boss_Spawn_Logic_Fix]] +- [[2026-04-22_Boss_Battle_System_Implementation|2026-04-22_Boss_Battle_System_Implementation]] +- [[2026-04-22_Boss_Spawn_Logic_Fix|2026-04-22_Boss_Spawn_Logic_Fix]] diff --git a/10_Wiki/Topics/.obsidian/graph.json b/10_Wiki/Topics/.obsidian/graph.json index 9dec217f..e2964ad0 100644 --- a/10_Wiki/Topics/.obsidian/graph.json +++ b/10_Wiki/Topics/.obsidian/graph.json @@ -17,6 +17,6 @@ "repelStrength": 10, "linkStrength": 1, "linkDistance": 250, - "scale": 0.05432900836085962, + "scale": 0.02727225354101746, "close": true } \ No newline at end of file diff --git a/10_Wiki/Topics/.obsidian/workspace.json b/10_Wiki/Topics/.obsidian/workspace.json index d87d3a25..c5dae64a 100644 --- a/10_Wiki/Topics/.obsidian/workspace.json +++ b/10_Wiki/Topics/.obsidian/workspace.json @@ -181,6 +181,10 @@ }, "active": "e84fb23982481828", "lastOpenFiles": [ + "Economics & Algorithms/페이 투 윈 (Pay to Win).md", + "무제 1.canvas", + "E-Travelive.md", + "페이 투 윈(Pay to Win.md", "04_Governance_Reliability/Code Review Operational Excellence (코드 리뷰 운영 우수성).md", "04_Governance_Reliability/Security Core Practices (보안 핵심 프랙티스).md", "02_Software_Engineering/Modern Engineering Practices (현대적 엔지니어링 프랙티스).md", @@ -206,9 +210,6 @@ "프롬프트 확장(Prompt Expansion).md", "프롬프트 파라미터 제어 (Prompt Parameter Control).md", "프롬프트 정밀도 (Prompt Precision).md", - "프롬프트 엔지니어링의 진화.md", - "프롬프트 엔지니어링.md", - "프롬프트 구조 및 문법.md", "sessions/2026-04-30T07-07", "sessions", "company_state.json", diff --git a/10_Wiki/Topics/00_Raw/conversations/2026-04-30.md b/10_Wiki/Topics/00_Raw/conversations/2026-04-30.md index b9e09cfb..4d07537d 100644 --- a/10_Wiki/Topics/00_Raw/conversations/2026-04-30.md +++ b/10_Wiki/Topics/00_Raw/conversations/2026-04-30.md @@ -4,24 +4,24 @@ _모든 명령·분배·산출물·대화가 시간순으로 누적됩니다. ## [16:07:45] 👤 **사용자** -[모닝 브리핑] 오늘 날짜는 2026-04-30입니다. 회사 목표([[goals]].md)와 지금까지의 의사결정 로그를 바탕으로 오늘 우리 회사가 우선순위로 처리해야 할 작업 3가지를 결정하고, 각 작업을 적절한 에이전트에게 분배하세요. +[모닝 브리핑] 오늘 날짜는 2026-04-30입니다. 회사 목표(goals.md)와 지금까지의 의사결정 로그를 바탕으로 오늘 우리 회사가 우선순위로 처리해야 할 작업 3가지를 결정하고, 각 작업을 적절한 에이전트에게 분배하세요. ## [16:28:10] 🧭 **CEO** · _작업 분배_ 회사 목표와 로그가 초기화 상태이므로, 시장 분석을 통한 닉슈 선정 → 수익화 전략 및 KPI 도출 → 일일/주간 실행 계획 수립 순으로 3가지 우선 작업을 정의합니다. **할당:** -- 🔍 **[[Research]]er**: AI/기술/콘텐츠 관련 상위 3개 시장 트렌드와 주요 경쟁 채널의 성장 패턴을 분석한 후, 우리 회사가 1개월 내 진입 가능한 최적의 1개 닉슈와 핵심 타깃 키워드 5개를 정리해 보고하세요. -- 💰 **[[business]]**: re[[Search]]er의 분석 결과를 기반으로 초기 수익화 모델(광고/스폰서/디지털 제품 중 1개 선택)을 제안하고, 월별 조회수·구독자·변환율 목표를 포함한 KPI 프레임워크와 가격/수익 구조를 1페이지 분량으로 작성하세요. -- 📱 **[[secretary]]**: 리서치와 비즈니스 전략 결과를 종합해 오늘 하루의 핵심 작업 3가지를 최종 확정하고, 마감 시간·담당 에이전트·진행 상태를 명시한 데일리 브리핑과 1주일 액션 플랜을 텔레그램 보고 형식으로 출력하세요. +- 🔍 **[[Research|Research]]er**: AI/기술/콘텐츠 관련 상위 3개 시장 트렌드와 주요 경쟁 채널의 성장 패턴을 분석한 후, 우리 회사가 1개월 내 진입 가능한 최적의 1개 닉슈와 핵심 타깃 키워드 5개를 정리해 보고하세요. +- 💰 **[[business|business]]**: re[[Search|Search]]er의 분석 결과를 기반으로 초기 수익화 모델(광고/스폰서/디지털 제품 중 1개 선택)을 제안하고, 월별 조회수·구독자·변환율 목표를 포함한 KPI 프레임워크와 가격/수익 구조를 1페이지 분량으로 작성하세요. +- 📱 **secretary**: 리서치와 비즈니스 전략 결과를 종합해 오늘 하루의 핵심 작업 3가지를 최종 확정하고, 마감 시간·담당 에이전트·진행 상태를 명시한 데일리 브리핑과 1주일 액션 플랜을 텔레그램 보고 형식으로 출력하세요. -## [16:33:10] 🔍 **[[researcher]]** · _AI/기술/콘텐츠 관련 상위 3개 시장 트렌드와 주요 경쟁 채널의 성장 패턴을 분석한 후, 우리 회사가 1개_ +## [16:33:10] 🔍 **[[researcher|researcher]]** · _AI/기술/콘텐츠 관련 상위 3개 시장 트렌드와 주요 경쟁 채널의 성장 패턴을 분석한 후, 우리 회사가 1개_ ⚠️ Researcher 에이전트 호출 실패: aborted ## [16:37:31] 👤 **사용자** -[자율 사이클 — 2026-04-30] 사용자가 자리를 비웠습니다. 회사 목표·각 에이전트의 개인 목표(_agents/{id}/[[goal]].md)·최근 의사결정·메모리를 검토해서 지금 가장 가치 있는 단일 작업 1개를 결정하고, 적절한 1~2명 에이전트에게 분배해서 실행하세요. 같은 산출물을 반복하지 마세요 — 메모리에 비슷한 항목이 24시간 내에 있으면 다른 각도로 진전시키세요. +[자율 사이클 — 2026-04-30] 사용자가 자리를 비웠습니다. 회사 목표·각 에이전트의 개인 목표(_agents/{id}/[[goal|goal]].md)·최근 의사결정·메모리를 검토해서 지금 가장 가치 있는 단일 작업 1개를 결정하고, 적절한 1~2명 에이전트에게 분배해서 실행하세요. 같은 산출물을 반복하지 마세요 — 메모리에 비슷한 항목이 24시간 내에 있으면 다른 각도로 진전시키세요. ## [16:38:10] 💰 **Business** · _researcher의 분석 결과를 기반으로 초기 수익화 모델(광고/스폰서/디지털 제품 중 1개 선택)을 제안_ diff --git a/10_Wiki/Topics/01_Frontend_Mastery/Index.md b/10_Wiki/Topics/01_Frontend_Mastery/Index.md index 48899ef1..afc0758c 100644 --- a/10_Wiki/Topics/01_Frontend_Mastery/Index.md +++ b/10_Wiki/Topics/01_Frontend_Mastery/Index.md @@ -1,11 +1,11 @@ # Index: Topics > 01_Frontend_Mastery ## 📝 Documents -- [[React_Clean_Code_Best_Practices]] -- [[React_Hooks_Deep_Dive]] -- [[React_Mental_Model]] -- [[React_Performance_Optimization]] -- [[React_State_Management_Strategy]] -- [[React_Testing_Strategy]] -- [[TypeScript_Type_Safety]] -- [[WebWorker_Performance]] +- [[React_Clean_Code_Best_Practices|React_Clean_Code_Best_Practices]] +- [[React_Hooks_Deep_Dive|React_Hooks_Deep_Dive]] +- [[React_Mental_Model|React_Mental_Model]] +- [[React_Performance_Optimization|React_Performance_Optimization]] +- [[React_State_Management_Strategy|React_State_Management_Strategy]] +- [[React_Testing_Strategy|React_Testing_Strategy]] +- [[TypeScript_Type_Safety|TypeScript_Type_Safety]] +- [[WebWorker_Performance|WebWorker_Performance]] diff --git a/10_Wiki/Topics/01_Frontend_Mastery/React_Clean_Code_Best_Practices.md b/10_Wiki/Topics/01_Frontend_Mastery/React_Clean_Code_Best_Practices.md index 2cd8886b..c26ad0e3 100644 --- a/10_Wiki/Topics/01_Frontend_Mastery/React_Clean_Code_Best_Practices.md +++ b/10_Wiki/Topics/01_Frontend_Mastery/React_Clean_Code_Best_Practices.md @@ -1,11 +1,11 @@ --- title: 리액트 클린 코드 및 개발 에티켓 -category: Software [[Architecture]] +category: Software [[Architecture|Architecture]] tags: [Clean Code, Etiquette, Best Practice, Readable Code] created: 2026-04-20 --- -# [[React_Clean_Code_Best_Practices]] (리액트 클린 코드) +# [[React_Clean_Code_Best_Practices|React_Clean_Code_Best_Practices]] (리액트 클린 코드) ## 📌 한 줄 통찰 (The Karpathy Summary) > 가독성 좋은 코드는 '컴퓨터'가 이해하는 코드가 아니라, '나중에 이 코드를 고칠 동료(혹은 미래의 나)'가 숨 쉬듯 읽어내려갈 수 있는 코드다. @@ -16,7 +16,7 @@ created: 2026-04-20 - **Props Destructuring (구조 분해 할당)**: - `props.user.name` 처럼 경로를 길게 쓰는 대신, 함수의 인자 단계에서 `{ user: { name } }` 처럼 분해하라. 코드가 숨을 쉬기 시작한다. - **Explicit Naming (명시적 네이밍)**: - - 핸들러 함수는 `handle[Action]` (예: `handle[[Search]]`), 비즈니스 함수는 `on[Action]` (예: `onSearchSubmit`)으로 구분하여 책임 소재를 명확히 한다. + - 핸들러 함수는 `handle[Action]` (예: `handle[[Search|Search]]`), 비즈니스 함수는 `on[Action]` (예: `onSearchSubmit`)으로 구분하여 책임 소재를 명확히 한다. - **조건부 렌더링 에티켓**: - `&&` 연산자 대신 삼항 연산자(`? :`)를 권장한다. 특히 `0 && ` 시 화면에 숫자 0이 출력되는 대참사를 방지하기 위함이다. @@ -24,5 +24,5 @@ created: 2026-04-20 - 과도한 추상화는 오히려 독이다. 코드가 3줄인데 함수 5개로 쪼개는 것은 가독성을 해친다. '직관성'이 '분리'보다 우선할 때가 있음을 명심하라. ## 🔗 지식 연결 (Graph) -- Related: [[Collaboration_Governance]] , [[System_Debugging_Protocol]] -- Foundation: [[React_Mental_Model]] +- Related: [[Collaboration_Governance|Collaboration_Governance]] , [[System_Debugging_Protocol|System_Debugging_Protocol]] +- Foundation: [[React_Mental_Model|React_Mental_Model]] diff --git a/10_Wiki/Topics/01_Frontend_Mastery/React_Hooks_Deep_Dive.md b/10_Wiki/Topics/01_Frontend_Mastery/React_Hooks_Deep_Dive.md index 866092d5..75d92ce0 100644 --- a/10_Wiki/Topics/01_Frontend_Mastery/React_Hooks_Deep_Dive.md +++ b/10_Wiki/Topics/01_Frontend_Mastery/React_Hooks_Deep_Dive.md @@ -1,11 +1,11 @@ --- title: 리액트 훅(Hooks) 심층 분석 및 활용 -category: Software [[Architecture]] +category: Software [[Architecture|Architecture]] tags: [React, Hooks, useEffect, Custom Hooks] created: 2026-04-20 --- -# [[React_Hooks_Deep_Dive]] (리액트 훅 심화) +# [[React_Hooks_Deep_Dive|React_Hooks_Deep_Dive]] (리액트 훅 심화) ## 📌 한 줄 통찰 (The Karpathy Summary) > 훅은 단순히 함수를 재사용하는 것이 아니라, 컴포넌트의 생애 주기와 논리를 '선언적'으로 결합하는 고도의 동기화 기제다. @@ -14,7 +14,7 @@ created: 2026-04-20 - **useEffect의 올바른 관점**: - "마운트될 때 실행"이라는 라이프사이클 사고방식에서 벗어나라. `useEffect`는 **의존성 배열의 값과 컴포넌트 외부 시스템(API, DOM 등)을 동기화**하는 작업이다. - **Custom Hooks (추상화의 꽃)**: - - 복잡한 비즈니스 로직(예: 데이터 페칭, 타이머 관리)을 `useMy[[Logic]]` 처럼 따로 빼내어 컴포넌트는 오직 UI 선언에만 집중하게 만든다. 이것이 컴포넌트의 가독성을 폭발시키는 비결이다. + - 복잡한 비즈니스 로직(예: 데이터 페칭, 타이머 관리)을 `useMy[[Logic|Logic]]` 처럼 따로 빼내어 컴포넌트는 오직 UI 선언에만 집중하게 만든다. 이것이 컴포넌트의 가독성을 폭발시키는 비결이다. - **Rules of Hooks**: - 반드시 함수의 최상위에서만 호출되어야 한다. 그래야 리액트가 훅의 상태를 유한 상태 머신처럼 정확한 순서로 관리할 수 있다. @@ -22,5 +22,5 @@ created: 2026-04-20 - `useEffect` 내에서 무분별하게 상태를 업데이트하면 무한 루프나 성능 저하가 발생한다. 가능하면 `useMemo`나 `useCallback`으로 계산 결과를 캐싱하거나, 상태 업데이트 로직을 `useReducer`로 위임하라. ## 🔗 지식 연결 (Graph) -- Related: [[React_Performance_Optimization]] , [[React_[[State]]_[[Management]]_Strategy]] -- Context: [[WebWorker_Performance]] +- Related: [[React_Performance_Optimization|React_Performance_Optimization]] , React_State_Management_Strategy +- Context: [[WebWorker_Performance|WebWorker_Performance]] diff --git a/10_Wiki/Topics/01_Frontend_Mastery/React_Mental_Model.md b/10_Wiki/Topics/01_Frontend_Mastery/React_Mental_Model.md index 255c6679..250093cf 100644 --- a/10_Wiki/Topics/01_Frontend_Mastery/React_Mental_Model.md +++ b/10_Wiki/Topics/01_Frontend_Mastery/React_Mental_Model.md @@ -1,11 +1,11 @@ --- -title: 리액트 핵심 멘탈 모델 (UI as a Function of [[State]]) -category: Software [[Architecture]] +title: 리액트 핵심 멘탈 모델 (UI as a Function of [[State|State]]) +category: Software [[Architecture|Architecture]] tags: [React, State, Mental Model, Immutability] created: 2026-04-20 --- -# [[React_Mental_Model]] (리액트 멘탈 모델) +# [[React_Mental_Model|React_Mental_Model]] (리액트 멘탈 모델) ## 📌 한 줄 통찰 (The Karpathy Summary) > 리액트 개발은 DOM을 '조작(Manipulate)'하는 것이 아니라, 데이터의 흐름인 '상태(State)'를 정의하고 그 결과물을 화면에 '선언(Declare)'하는 과정이다. @@ -14,13 +14,13 @@ created: 2026-04-20 - **UI = f(State)**: - 화면은 상태의 결과값이어야 한다. 명령형(Imperative)으로 "이 버튼의 글자를 바꿔라"라고 하는 순간 리액트의 질서는 무너진다. 오직 상태를 바꾸고 리액트가 알아서 그리게 하라. - **Immutability (불변성)**: - - 리액트는 객체의 주소값이 변할 때만 렌더링을 시도한다. `arr.push(1)`이 아니라 `setArr([...arr, 1])`처럼 **새로운 원본**을 복제하여 가상 DOM([[Virtual DOM]])이 효율적으로 동작하게 돕는다. + - 리액트는 객체의 주소값이 변할 때만 렌더링을 시도한다. `arr.push(1)`이 아니라 `setArr([...arr, 1])`처럼 **새로운 원본**을 복제하여 가상 DOM([[Virtual DOM|Virtual DOM]])이 효율적으로 동작하게 돕는다. - **Virtual DOM Diffing**: - 리액트는 실제 DOM을 직접 건드리기 전에 메모리상의 가상 DOM에서 이전 상태와 비교(Diffing)하여, 꼭 필요한 부분만 실제 화면에 반영(Commit)한다. 이것이 고성능 웹의 비결이다. ## ⚠️ 모순 및 업데이트 (RL Update) -- 불변성 유지를 위해 매번 거대한 객체를 복사하는 것은 때로 손해다. `Immer` 같은 라이브러리를 쓰거나, 상태의 크기를 작게 쪼개어([[Normalization]]) 업데이트 비용을 최소화하는 전략이 중급 개발자의 역량이다. +- 불변성 유지를 위해 매번 거대한 객체를 복사하는 것은 때로 손해다. `Immer` 같은 라이브러리를 쓰거나, 상태의 크기를 작게 쪼개어([[Normalization|Normalization]]) 업데이트 비용을 최소화하는 전략이 중급 개발자의 역량이다. ## 🔗 지식 연결 (Graph) -- Related: [[React_Hooks_Deep_Dive]] , [[Component_Design_Patterns]] -- Foundation: [[System_Protocol_Standard]] +- Related: [[React_Hooks_Deep_Dive|React_Hooks_Deep_Dive]] , [[Component_Design_Patterns|Component_Design_Patterns]] +- Foundation: [[System_Protocol_Standard|System_Protocol_Standard]] diff --git a/10_Wiki/Topics/01_Frontend_Mastery/React_Performance_Optimization.md b/10_Wiki/Topics/01_Frontend_Mastery/React_Performance_Optimization.md index 7205735f..79372506 100644 --- a/10_Wiki/Topics/01_Frontend_Mastery/React_Performance_Optimization.md +++ b/10_Wiki/Topics/01_Frontend_Mastery/React_Performance_Optimization.md @@ -1,11 +1,11 @@ --- title: 리액트 렌더링 최적화 전략 -category: Software [[Architecture]] -tags: [Performance, Memoization, React.memo, [[Optimization]]] +category: Software [[Architecture|Architecture]] +tags: [Performance, Memoization, React.memo, [[Optimization|Optimization]]] created: 2026-04-20 --- -# [[React_Performance_Optimization]] (리액트 성능 최적화) +# [[React_Performance_Optimization|React_Performance_Optimization]] (리액트 성능 최적화) ## 📌 한 줄 통찰 (The Karpathy Summary) > 가장 빠른 렌더링은 '하지 않는 렌더링'이다. 필요 없는 업데이트를 차단하고 데이터가 흐를 때만 화면이 출렁이게 하라. @@ -17,12 +17,12 @@ created: 2026-04-20 - **useCallback**: 함수 객체의 변동을 막아 자식 컴포넌트의 불필요한 리렌더링을 방지한다. - **Windowing (가상 리스트)**: - 수천 개의 리스트 아이템이 있어도 사용자의 눈에 보이는 수십 개만 실제 DOM에 렌더링한다. (예: `react-window`, `react-virtualized`). -- **상태의 위치 선정 ([[State]] Colocation)**: +- **상태의 위치 선정 ([[State|State]] Colocation)**: - 전역 상태가 바뀔 때마다 앱 전체가 들썩이지 않게 하라. 상태는 그것을 사용하는 가장 하위 컴포넌트 근처로 내려라. ## ⚠️ 모순 및 업데이트 (RL Update) - 모든 곳에 `memo`를 쓰는 것은 메모리 낭비다. 리액트의 기본 렌더링 성능은 이미 매우 뛰어나다. 병목 현상이 '실제로 관측'될 때만 최적화를 적용하는 것이 원칙이다. ## 🔗 지식 연결 (Graph) -- Related: [[WebWorker_Performance]] , [[System_Debugging_Protocol]] -- Foundation: [[React_Mental_Model]] +- Related: [[WebWorker_Performance|WebWorker_Performance]] , [[System_Debugging_Protocol|System_Debugging_Protocol]] +- Foundation: [[React_Mental_Model|React_Mental_Model]] diff --git a/10_Wiki/Topics/01_Frontend_Mastery/React_State_Management_Strategy.md b/10_Wiki/Topics/01_Frontend_Mastery/React_State_Management_Strategy.md index 5e2eb949..31b687f9 100644 --- a/10_Wiki/Topics/01_Frontend_Mastery/React_State_Management_Strategy.md +++ b/10_Wiki/Topics/01_Frontend_Mastery/React_State_Management_Strategy.md @@ -1,11 +1,11 @@ --- -title: 전략적 상태 관리 가이드 (Global & Server [[State]]) -category: Software [[Architecture]] -tags: [State [[Management]], React Query, SSOT, Architecture] +title: 전략적 상태 관리 가이드 (Global & Server [[State|State]]) +category: Software [[Architecture|Architecture]] +tags: [State [[Management|Management]], React Query, SSOT, Architecture] created: 2026-04-20 --- -# [[React_State_Management_Strategy]] (상태 관리 전략) +# [[React_State_Management_Strategy|React_State_Management_Strategy]] (상태 관리 전략) ## 📌 한 줄 통찰 (The Karpathy Summary) > 상태는 '어디든' 있을 수 있지만, '아무데나' 있어서는 안 된다. 상태의 생명주기와 전파 범위에 따라 명확한 거주지를 결정하라. @@ -21,8 +21,8 @@ created: 2026-04-20 - 다른 상태로부터 계산될 수 있는 값(예: `firstName`+`lastName` = `fullName`)은 절대 '상태'로 만들지 마라. 렌더링 시점에 계산하는 것이 정합성 유지의 핵심이다. ## ⚠️ 모순 및 업데이트 (RL Update) -- 무조건적인 전역 상태 지상주의는 '[[Prop Drilling]]'보다 위험할 수 있다. 컴포넌트 간의 의존성이 암시적으로 얽히기 때문이다. 상태는 되도록 사용하는 곳에서 가장 가깝게 위치시켜라. +- 무조건적인 전역 상태 지상주의는 '[[Prop Drilling|Prop Drilling]]'보다 위험할 수 있다. 컴포넌트 간의 의존성이 암시적으로 얽히기 때문이다. 상태는 되도록 사용하는 곳에서 가장 가깝게 위치시켜라. ## 🔗 지식 연결 (Graph) -- Related: [[Single_Source_of_Truth]] , [[API_Communication_Patterns]] -- Foundation: [[React_Hooks_Deep_Dive]] +- Related: [[Single_Source_of_Truth|Single_Source_of_Truth]] , [[API_Communication_Patterns|API_Communication_Patterns]] +- Foundation: [[React_Hooks_Deep_Dive|React_Hooks_Deep_Dive]] diff --git a/10_Wiki/Topics/01_Frontend_Mastery/React_Testing_Strategy.md b/10_Wiki/Topics/01_Frontend_Mastery/React_Testing_Strategy.md index 82183622..cf1950eb 100644 --- a/10_Wiki/Topics/01_Frontend_Mastery/React_Testing_Strategy.md +++ b/10_Wiki/Topics/01_Frontend_Mastery/React_Testing_Strategy.md @@ -1,11 +1,11 @@ --- title: 리액트 애플리케이션 테스트 전략 -category: Software [[Architecture]] -tags: [[[Testing]], Vitest, RTL, Unit Test, QA] +category: Software [[Architecture|Architecture]] +tags: [[Testing|[Testing]], Vitest, RTL, Unit Test, QA] created: 2026-04-20 --- -# [[React_Testing_Strategy]] (리액트 테스트 전략) +# [[React_Testing_Strategy|React_Testing_Strategy]] (리액트 테스트 전략) ## 📌 한 줄 통찰 (The Karpathy Summary) > 테스트는 '내가 짠 코드'를 검사하는 것이 아니라, '사용자가 경험할 가치'가 유지되고 있는지 수학적으로 증명하는 보험이다. @@ -22,5 +22,5 @@ created: 2026-04-20 - 테스트 커버리지 100% 집착은 생산성을 갉아먹는다. 비즈니스 핵심 로직과 사용자가 가장 많이 쓰는 '메인 시나리오'부터 견고하게 보호하는 지혜가 필요하다. ## 🔗 지식 연결 (Graph) -- Related: [[System_Debugging_Protocol]] , [[Reliability_Safety_First]] -- Tool: [[Modern_Environment_Ecosystem]] +- Related: [[System_Debugging_Protocol|System_Debugging_Protocol]] , [[Reliability_Safety_First|Reliability_Safety_First]] +- Tool: [[Modern_Environment_Ecosystem|Modern_Environment_Ecosystem]] diff --git a/10_Wiki/Topics/01_Frontend_Mastery/TypeScript_Type_Safety.md b/10_Wiki/Topics/01_Frontend_Mastery/TypeScript_Type_Safety.md index fd67b450..7ff64b3e 100644 --- a/10_Wiki/Topics/01_Frontend_Mastery/TypeScript_Type_Safety.md +++ b/10_Wiki/Topics/01_Frontend_Mastery/TypeScript_Type_Safety.md @@ -1,11 +1,11 @@ --- title: 타입스크립트 기반의 안정적 개발 (Type Safety) -category: Software [[Architecture]] +category: Software [[Architecture|Architecture]] tags: [TypeScript, Interface, Type Safety, Generic] created: 2026-04-20 --- -# [[TypeScript_Type_Safety]] (타입스크립트 정석) +# [[TypeScript_Type_Safety|TypeScript_Type_Safety]] (타입스크립트 정석) ## 📌 한 줄 통찰 (The Karpathy Summary) > 타입스크립트는 당신을 귀찮게 하는 '잔소리꾼'이 아니라, 런타임 에러라는 '낭떠러지' 앞에서 당신을 붙잡아주는 '생명줄'이다. @@ -22,5 +22,5 @@ created: 2026-04-20 - `any`를 남발하는 순간 타입스크립트의 모든 이점은 사라진다. 차라리 `unknown`을 쓰고 타입을 좁히는(Narrowing) 방식을 택하라. 타입 정의에 너무 많은 시간을 뺏기는 '타입 헬(Type Hell)'을 경계하고 적절한 타협점을 찾아라. ## 🔗 지식 연결 (Graph) -- Related: [[React_Clean_Code_Best_Practices]] , [[React_Hooks_Deep_Dive]] -- Foundation: [[System_Protocol_Standard]] +- Related: [[React_Clean_Code_Best_Practices|React_Clean_Code_Best_Practices]] , [[React_Hooks_Deep_Dive|React_Hooks_Deep_Dive]] +- Foundation: [[System_Protocol_Standard|System_Protocol_Standard]] diff --git a/10_Wiki/Topics/01_Frontend_Mastery/WebWorker_Performance.md b/10_Wiki/Topics/01_Frontend_Mastery/WebWorker_Performance.md index a697efc9..dcc9e995 100644 --- a/10_Wiki/Topics/01_Frontend_Mastery/WebWorker_Performance.md +++ b/10_Wiki/Topics/01_Frontend_Mastery/WebWorker_Performance.md @@ -10,9 +10,9 @@ created: 2026-04-20 ## 🎯 개요 (Overview) 실시간 상태 변화가 매우 빈번한 애플리케이션(예: 게임, 시뮬레이션)에서 UI 스레드와 복잡한 연산 로직을 분리하여 **프레임 드롭(Jank)**을 방지하는 아키텍처 설계 기법입니다. -## 🚀 주요 원칙 (Key [[Principles]]) +## 🚀 주요 원칙 (Key [[Principles|Principles]]) - **스레드 분리 (Thread Isolation)**: 무거운 계산은 백그라운드 스레드(Web Worker)에서 수행하고, 메인 스레드는 렌더링에만 집중합니다. -- **메시징 기반 통신 (Messaging [[Architecture]])**: `postMessage`와 `onmessage`를 통해 비동기적으로 데이터를 주고받아 결합도를 낮춥니다. +- **메시징 기반 통신 (Messaging [[Architecture|Architecture]])**: `postMessage`와 `onmessage`를 통해 비동기적으로 데이터를 주고받아 결합도를 낮춥니다. ## 💡 레슨 런 (Lesson Learned) > [!IMPORTANT] @@ -20,5 +20,5 @@ created: 2026-04-20 > 복잡한 물리 계산이나 루프가 UI 응답성을 해치지 않도록, 연산 엔진을 완전히 별도의 스레드로 격리하는 것이 부드러운 UX의 핵심입니다. ## 🔗 연결된 지식 -- [[Separation_of_Concerns]] -- [[Systemic_Simulation_Principles]] +- [[Separation_of_Concerns|Separation_of_Concerns]] +- [[Systemic_Simulation_Principles|Systemic_Simulation_Principles]] diff --git a/10_Wiki/Topics/01_Process_Methodology/SDLC & SSDLC (소프트웨어 개발 생명주기).md b/10_Wiki/Topics/01_Process_Methodology/SDLC & SSDLC (소프트웨어 개발 생명주기).md index 6f5fa27e..35e0d7da 100644 --- a/10_Wiki/Topics/01_Process_Methodology/SDLC & SSDLC (소프트웨어 개발 생명주기).md +++ b/10_Wiki/Topics/01_Process_Methodology/SDLC & SSDLC (소프트웨어 개발 생명주기).md @@ -1,4 +1,4 @@ -# [[SDLC & SSDLC (소프트웨어 개발 생명주기)]] +# [[SDLC & SSDLC (소프트웨어 개발 생명주기)|SDLC & SSDLC (소프트웨어 개발 생명주기]] ## 📌 Brief Summary 소프트웨어 개발 생명주기(SDLC)는 시스템의 기획, 설계, 구현, 테스트, 배포 및 운영에 이르는 전 과정을 체계화한 모델입니다. **Secure SDLC (SSDLC)**는 이 전통적인 과정의 각 단계에 보안 활동을 내재화하여 안전한 소프트웨어를 구축하는 방법론입니다 [1]. 현대적인 SDLC 환경에서 코드 리뷰는 개발과 배포 사이의 핵심적인 품질 및 보안 게이트(Quality Gate)로 작용하며, 특히 보안 점검을 초기 단계로 앞당기는 **'시프트 레프트(Shift-Left)'** 전략을 통해 결함 수정 비용을 절감하고 시스템 무결성을 확보합니다 [4, 5]. @@ -23,10 +23,10 @@ ## 🔗 Knowledge Connections ### Related Concepts -* **[[Shift-Left Security]]**: 보안 테스트를 SDLC의 가장 좌측(초기 단계)으로 옮겨 수정 비용을 절감하는 핵심 전략입니다. -* **[[CI/CD Pipeline]]**: 빌드, 테스트, 보안 스캔을 자동화하여 SDLC의 안정성과 속도를 보장하는 물리적 인프라입니다. -* **[[DORA Metrics]]**: 팀의 소프트웨어 전달 성능을 측정하여 SDLC의 효율성을 평가하는 지표 체계입니다. -* **[[SAST (Static Application Security Testing)]]**: SDLC 구현 및 검증 단계에서 소스 코드 보안을 자동 스캔하는 기술입니다. +* **Shift-Left Security**: 보안 테스트를 SDLC의 가장 좌측(초기 단계)으로 옮겨 수정 비용을 절감하는 핵심 전략입니다. +* **[[CI-CD Pipeline|CI/CD Pipeline]]**: 빌드, 테스트, 보안 스캔을 자동화하여 SDLC의 안정성과 속도를 보장하는 물리적 인프라입니다. +* **[[DORA-Metrics|DORA Metrics]]**: 팀의 소프트웨어 전달 성능을 측정하여 SDLC의 효율성을 평가하는 지표 체계입니다. +* **[[SAST (Static Application Security Testing)|SAST (Static Application Security Testing]]**: SDLC 구현 및 검증 단계에서 소스 코드 보안을 자동 스캔하는 기술입니다. ### Deeper Research Questions * '시프트 레프트' 보안 모델에서 개발자와 보안 전문가 간의 코드 리뷰 책임 소재와 최종 승인 권한(Merge Authority)은 어떻게 정의하는 것이 최적인가? @@ -43,8 +43,8 @@ * **My Project Relevance:** 조직의 리뷰 프로세스를 체계화하고 자동화 검사를 파이프라인에 통합하여 품질 향상과 배포 속도 증가를 동시에 달성합니다. ### Adjacent Topics -* **[[Agile Development]]**: 스크럼, 칸반 등 반복적 개발 방법론 내에서 SDLC가 어떻게 유연하게 운영되는지 확장하여 탐구합니다. -* **[[Software Supply Chain Security]]**: 소스 코드를 넘어 패키지 매니저, 빌드 도구 등 SDLC 인프라 전체의 보안을 강화하는 전략입니다. +* **[[Agile Development|Agile Development]]**: 스크럼, 칸반 등 반복적 개발 방법론 내에서 SDLC가 어떻게 유연하게 운영되는지 확장하여 탐구합니다. +* **Software Supply Chain Security**: 소스 코드를 넘어 패키지 매니저, 빌드 도구 등 SDLC 인프라 전체의 보안을 강화하는 전략입니다. --- *Last updated: 2026-05-02* diff --git a/10_Wiki/Topics/01_Process_Methodology/Team Culture & Onboarding (팀 문화 및 온보딩).md b/10_Wiki/Topics/01_Process_Methodology/Team Culture & Onboarding (팀 문화 및 온보딩).md index 0a40a15e..a185ed6a 100644 --- a/10_Wiki/Topics/01_Process_Methodology/Team Culture & Onboarding (팀 문화 및 온보딩).md +++ b/10_Wiki/Topics/01_Process_Methodology/Team Culture & Onboarding (팀 문화 및 온보딩).md @@ -1,4 +1,4 @@ -# [[Team Culture & Onboarding (팀 문화 및 온보딩)]] +# [[Team Culture & Onboarding (팀 문화 및 온보딩)|Team Culture & Onboarding (팀 문화 및 온보딩]] ## 📌 Brief Summary 팀 문화 및 온보딩은 새로운 구성원이 조직에 신속히 적응하고, 기존 팀원들이 비난 없이 소통하며 지속적으로 성장할 수 있는 환경을 구축하는 활동입니다 [1]. 심리적 안전감(Psychological Safety)을 기반으로 코드 리뷰를 학습의 장으로 활용하며, 온보딩 프로세스를 통해 팀의 기술 표준과 협업 방식을 전수합니다 [4]. 특히 장애 발생 시 블레임리스 포스트모템(Blameless Post-mortem)을 수행하여 비난 대신 시스템적 개선을 도모하는 성숙한 문화를 지향합니다. @@ -22,10 +22,10 @@ ## 🔗 Knowledge Connections ### Related Concepts -* **[[Egoless Programming]]**: 자신의 코드와 자신을 동일시하지 않는 태도("You are not your code")로 리뷰 수용성을 높이는 철학입니다. -* **[[Constructive Feedback]]**: 방어적 반응을 유발하지 않으면서 코드 품질을 높이는 구체적인 소통 기술입니다. -* **[[Conventional Comments]]**: 피드백의 의도를 라벨링하여 오해를 줄이고 안전감을 높이는 시스템적 도구입니다. -* **[[I-Messages (나-전달법)]]**: "너"가 아닌 "나"를 주어로 사용하여 부드럽게 의견을 전달하는 기법입니다. +* **Egoless Programming**: 자신의 코드와 자신을 동일시하지 않는 태도("You are not your code")로 리뷰 수용성을 높이는 철학입니다. +* **Constructive Feedback**: 방어적 반응을 유발하지 않으면서 코드 품질을 높이는 구체적인 소통 기술입니다. +* **Conventional Comments**: 피드백의 의도를 라벨링하여 오해를 줄이고 안전감을 높이는 시스템적 도구입니다. +* **I-Messages (나-전달법**: "너"가 아닌 "나"를 주어로 사용하여 부드럽게 의견을 전달하는 기법입니다. ### Deeper Research Questions * 팀 내 심리적 안전감이 결여되었을 때 코드 리뷰 프로세스에서 발생하는 구체적인 기술적 부채와 이직률 사이의 상관관계는 무엇인가? @@ -42,8 +42,8 @@ * **My Project Relevance:** Conventional Comments와 멘토링 제도를 도입하여 상호 존중과 신뢰 기반의 건강한 엔지니어링 문화를 구축합니다 [49]. ### Adjacent Topics -* **[[DORA Metrics (Cultural Dimension)]]**: 팀 문화가 소프트웨어 배포 성과에 미치는 정량적 영향을 탐구합니다. -* **[[Cognitive Load Theory]]**: 온보딩 과정에서 신규 입사자에게 전달되는 정보량을 조절하여 학습 효율을 높이는 이론적 배경입니다. +* **DORA Metrics (Cultural Dimension**: 팀 문화가 소프트웨어 배포 성과에 미치는 정량적 영향을 탐구합니다. +* **[[Cognitive Load Theory|Cognitive Load Theory]]**: 온보딩 과정에서 신규 입사자에게 전달되는 정보량을 조절하여 학습 효율을 높이는 이론적 배경입니다. --- *Last updated: 2026-05-02* diff --git a/10_Wiki/Topics/02_Architecture_Principles/API_Communication_Patterns.md b/10_Wiki/Topics/02_Architecture_Principles/API_Communication_Patterns.md index 96b98154..55668e02 100644 --- a/10_Wiki/Topics/02_Architecture_Principles/API_Communication_Patterns.md +++ b/10_Wiki/Topics/02_Architecture_Principles/API_Communication_Patterns.md @@ -1,11 +1,11 @@ --- title: 효율적인 API 통신 패턴 (Axios & Interceptors) -category: Software [[Architecture]] +category: Software [[Architecture|Architecture]] tags: [API, Axios, Interceptor, Error Handling, Network] created: 2026-04-20 --- -# [[API_Communication_Patterns]] (API 통신 패턴) +# [[API_Communication_Patterns|API_Communication_Patterns]] (API 통신 패턴) ## 📌 한 줄 통찰 (The Karpathy Summary) > 서버와의 대화는 항상 '정중하되 의심하며' 처리하라. 모든 요청은 중앙 통제소(Interceptor)를 거치고 모든 에러는 시나리오가 준비되어 있어야 한다. @@ -22,5 +22,5 @@ created: 2026-04-20 - 모든 통신에 Axios가 정답은 아니다. 브라우저 네이티브인 `fetch`로도 충분한 경우가 많으며, 라이브러리 의존성을 낮추는 것이 가벼운 앱을 만드는 첫걸음일 수 있다. ## 🔗 지식 연결 (Graph) -- Related: [[System_Protocol_Standard]] , [[React_[[State]]_[[Management]]_Strategy]] -- Foundation: [[Reliability_Safety_First]] +- Related: [[System_Protocol_Standard|System_Protocol_Standard]] , React_State_Management_Strategy +- Foundation: [[Reliability_Safety_First|Reliability_Safety_First]] diff --git a/10_Wiki/Topics/02_Architecture_Principles/Clean Architecture & Patterns.md b/10_Wiki/Topics/02_Architecture_Principles/Clean Architecture & Patterns.md index 6ef2bfa7..7a07a353 100644 --- a/10_Wiki/Topics/02_Architecture_Principles/Clean Architecture & Patterns.md +++ b/10_Wiki/Topics/02_Architecture_Principles/Clean Architecture & Patterns.md @@ -6,7 +6,7 @@ tags: [architecture, clean-architecture, design-patterns, mvc, separation-of-con last_reinforced: 2026-05-01 --- -# [[Clean Architecture & Patterns]] +# [[Clean Architecture & Patterns|Clean Architecture & Patterns]] ## 📌 한 줄 통찰 (The Karpathy Summary) > "기술적 세부 사항(DB, Framework)으로부터 비즈니스 로직을 격리하여, 시스템의 수명을 연장하고 변화에 유연하게 대응하게 만드는 관심사 분리(Separation of Concerns)의 정점." @@ -27,9 +27,9 @@ last_reinforced: 2026-05-01 - **아키텍처 부패 (Architectural Decay)**: 시간이 흐름에 따라 편의를 위해 계층을 우회하는 코드가 쌓일 수 있습니다. 매 PR마다 아키텍처 무결성을 점검하여 부패를 조기에 차단해야 합니다. ## 🔗 지식 연결 (Graph) -- [[SOLID Principles]]: 아키텍처를 지탱하는 세부 설계 원칙. -- [[Architecture Review]]: 아키텍처 일관성을 검증하는 프로세스. -- [[Dependency Management (DI & DIP)]]: 계층 간 결합도를 낮추는 기술적 수단. -- [[Single Responsibility Principle (SRP)]]: 컴포넌트 분리의 근거. -- [[Abstraction & Over-engineering]]: 아키텍처 도입 시 경계해야 할 함정. +- [[SOLID Principles|SOLID Principles]]: 아키텍처를 지탱하는 세부 설계 원칙. +- [[Architecture Review (아키텍처 및 설계 리뷰)|Architecture Review]]: 아키텍처 일관성을 검증하는 프로세스. +- [[Dependency Management (DI & DIP)|Dependency Management (DI & DIP]]: 계층 간 결합도를 낮추는 기술적 수단. +- [[Single Responsibility Principle (SRP)|Single Responsibility Principle (SRP]]: 컴포넌트 분리의 근거. +- Abstraction & Over-engineering: 아키텍처 도입 시 경계해야 할 함정. --- diff --git a/10_Wiki/Topics/02_Architecture_Principles/Clean Architecture.md b/10_Wiki/Topics/02_Architecture_Principles/Clean Architecture.md index bcd8de3d..ad831689 100644 --- a/10_Wiki/Topics/02_Architecture_Principles/Clean Architecture.md +++ b/10_Wiki/Topics/02_Architecture_Principles/Clean Architecture.md @@ -6,7 +6,7 @@ tags: [architecture, clean-architecture, layering, decoupling, domain-driven-des last_reinforced: 2026-05-01 --- -# [[Clean Architecture]] +# [[Clean Architecture|Clean Architecture]] ## 📌 한 줄 통찰 (The Karpathy Summary) > "비즈니스 로직(Domain)을 중심에 두고 UI, DB, 프레임워크와 같은 외부 세부 사항을 주변부로 밀어내어, 외부 기술의 변화가 시스템의 핵심 논리에 영향을 주지 않도록 격리하는 계층화 아키텍처의 정수." @@ -31,9 +31,9 @@ last_reinforced: 2026-05-01 - **학습 곡선**: 계층 간 경계를 엄격히 지키는 설계 철학을 팀 전체가 공유하고 준수하는 데 높은 수준의 컨센서스와 코드 리뷰 역량이 요구됩니다. ## 🔗 지식 연결 (Graph) -- [[SOLID Principles]]: 각 계층 내부 설계를 지탱하는 원칙들. -- [[Domain-Driven Design (DDD)]]: 도메인 중심 설계 사상과의 시너지. -- [[Dependency Inversion Principle (DIP)]]: 계층 간 통신을 가능하게 하는 핵심 기술. -- [[Software Architecture Patterns]]: MVC, Hexagonal 아키텍처 등과의 비교. -- [[Over-engineering]]: 패턴의 맹목적 적용 시 경계해야 할 부작용. +- [[SOLID Principles|SOLID Principles]]: 각 계층 내부 설계를 지탱하는 원칙들. +- [[Domain-Driven-Design-DDD|Domain-Driven Design (DDD]]: 도메인 중심 설계 사상과의 시너지. +- [[의존성 역전 원칙 (Dependency Inversion Principle DIP)|Dependency Inversion Principle (DIP]]: 계층 간 통신을 가능하게 하는 핵심 기술. +- [[Software-Architecture-Patterns|Software Architecture Patterns]]: MVC, Hexagonal 아키텍처 등과의 비교. +- Over-engineering: 패턴의 맹목적 적용 시 경계해야 할 부작용. --- diff --git a/10_Wiki/Topics/02_Architecture_Principles/Component_Design_Patterns.md b/10_Wiki/Topics/02_Architecture_Principles/Component_Design_Patterns.md index ad02b46e..cf1244a7 100644 --- a/10_Wiki/Topics/02_Architecture_Principles/Component_Design_Patterns.md +++ b/10_Wiki/Topics/02_Architecture_Principles/Component_Design_Patterns.md @@ -1,20 +1,20 @@ --- title: 컴포넌트 설계 패턴 (Atomic & Composition) -category: Software [[Architecture]] -tags: [Design Pattern, [[Atomic Design]], Composition, Architecture] +category: Software [[Architecture|Architecture]] +tags: [Design Pattern, [[Atomic Design|Atomic Design]], Composition, Architecture] created: 2026-04-20 --- -# [[Component_Design_Patterns]] (컴포넌트 설계 패턴) +# [[Component_Design_Patterns|Component_Design_Patterns]] (컴포넌트 설계 패턴) ## 📌 한 줄 통찰 (The Karpathy Summary) > 컴포넌트는 작을수록 강하고, 단순할수록 재사용성이 극대화된다. 복잡한 컴포넌트는 여러 개의 작고 순수한(Pure) 컴포넌트로 해체하라. ## 📖 구조화된 지식 (Synthesized Content) - **Container-Presenter 패턴**: - - **Container**: 데이터([[State]], API)를 가져오고 관리하는 '머리'. + - **Container**: 데이터([[State|State]], API)를 가져오고 관리하는 '머리'. - **Presenter**: 오직 Props만 받아 화면을 그리는 '몸통'. 스타일과 UI 구조에만 집중하여 테스트 가능성을 높인다. -- **[[Compound Components]] (복합 컴포넌트)**: +- **[[Compound Components|Compound Components]] (복합 컴포넌트)**: - `` 처럼 부모와 자식이 상태를 공유하며 하나의 긴밀한 기능을 수행하는 패턴. 사용자가 UI 구조를 자유롭게 배치할 수 있게 유연성을 제공한다. - **Atomic Design (원자 중심 설계)**: - Atom(버튼, 입력창) $\rightarrow$ Molecule(검색바) $\rightarrow$ Organism(헤더) $\rightarrow$ Template $\rightarrow$ Page. @@ -24,5 +24,5 @@ created: 2026-04-20 - 너무 과도한 컴포넌트 분할은 프로토타이핑 속도를 늦춘다. 처음에는 크게 짜고, 중복이 발생하거나 복잡도가 높아질 때 '사후적 리팩토링'을 통해 분리하는 것이 실무적으로 현명하다. ## 🔗 지식 연결 (Graph) -- Related: Project_Architecture_Guidelines , [[Styling_Governance]] -- Design: [[Accessibility_Inclusivity]] +- Related: Project_Architecture_Guidelines , [[Styling_Governance|Styling_Governance]] +- Design: [[Accessibility_Inclusivity|Accessibility_Inclusivity]] diff --git a/10_Wiki/Topics/02_Architecture_Principles/Dependency Injection (DI).md b/10_Wiki/Topics/02_Architecture_Principles/Dependency Injection (DI).md index d66cb733..365f1d11 100644 --- a/10_Wiki/Topics/02_Architecture_Principles/Dependency Injection (DI).md +++ b/10_Wiki/Topics/02_Architecture_Principles/Dependency Injection (DI).md @@ -6,7 +6,7 @@ tags: [architecture, di, dependency-injection, decoupling, inversion-of-control, last_reinforced: 2026-05-01 --- -# [[Dependency Injection (DI)]] +# [[Dependency Injection (DI)|Dependency Injection (DI]] ## 📌 한 줄 통찰 (The Karpathy Summary) > "클래스 내부에서 직접 의존 객체를 생성하지 않고 외부에서 주입받음으로써, 객체 간의 결합을 끊어내고 테스트와 확장이 용이한 '유연한 부품'으로 만드는 제어 역전(IoC)의 실천적 기법." @@ -28,9 +28,9 @@ DI는 현대 소프트웨어 아키텍처에서 컴포넌트 간의 결합도를 - **코드 추적성 저하**: 정적 코드만으로는 어떤 구현체가 주입될지 즉각 확인하기 어려울 수 있습니다. 이를 해결하기 위해 명확한 네이밍 컨벤션과 DI 바인딩 로그의 가시성 확보가 중요합니다. ## 🔗 지식 연결 (Graph) -- [[SOLID Principles]]: 의존성 역전 원칙(DIP)의 실현 방법. -- [[Single Responsibility Principle (SRP)]]: 클래스의 책임을 생성과 실행으로 분리하는 관점. -- [[Testability]]: Mock 객체 주입을 통한 단위 테스트 용이성 확보. -- [[Constructor Injection]]: 가장 권장되는 DI 패턴. -- [[Dependency Lifetimes]]: Transient, Scoped, Singleton의 이해. +- [[SOLID Principles|SOLID Principles]]: 의존성 역전 원칙(DIP)의 실현 방법. +- [[Single Responsibility Principle (SRP)|Single Responsibility Principle (SRP]]: 클래스의 책임을 생성과 실행으로 분리하는 관점. +- [[테스트 용이성 (Testability)|Testability]]: Mock 객체 주입을 통한 단위 테스트 용이성 확보. +- Constructor Injection: 가장 권장되는 DI 패턴. +- Dependency Lifetimes: Transient, Scoped, Singleton의 이해. --- diff --git a/10_Wiki/Topics/02_Architecture_Principles/Dependency Management (DI & DIP).md b/10_Wiki/Topics/02_Architecture_Principles/Dependency Management (DI & DIP).md index e5ce75db..eec726f9 100644 --- a/10_Wiki/Topics/02_Architecture_Principles/Dependency Management (DI & DIP).md +++ b/10_Wiki/Topics/02_Architecture_Principles/Dependency Management (DI & DIP).md @@ -6,7 +6,7 @@ tags: [architecture, dependency-management, dependency-injection, di, dependency last_reinforced: 2026-05-01 --- -# [[Dependency Management (DI & DIP)]] +# [[Dependency Management (DI & DIP)|Dependency Management (DI & DIP]] ## 📌 한 줄 통찰 (The Karpathy Summary) > "구체적인 구현이 아닌 추상화에 의존하게 하여 컴포넌트 간의 결합도를 낮추고, 코드 수정 없이 기능을 확장하거나 교체할 수 있는 유연한 시스템 구조의 핵심 기법." @@ -14,10 +14,10 @@ last_reinforced: 2026-05-01 ## 📖 구조화된 지식 (Synthesized Content) 의존성 관리는 소프트웨어의 모듈성과 테스트 가능성을 결정짓는 가장 중요한 설계 요소입니다. -1. **[[Dependency Inversion Principle (DIP)]]**: +1. **[[의존성 역전 원칙 (Dependency Inversion Principle DIP)|Dependency Inversion Principle (DIP]]**: * **고수준 모듈의 보호**: 고수준 모듈(비즈니스 로직)은 저수준 모듈(데이터베이스, 외부 API)의 구체적인 구현에 의존해서는 안 됩니다. 둘 다 추상화(인터페이스)에 의존해야 합니다. * **의존성 방향의 역전**: 전통적인 계층 구조에서의 의존성 방향을 뒤집어, 구현체가 인터페이스를 따르게 함으로써 핵심 로직을 외부 변화로부터 보호합니다. -2. **[[Dependency Injection (DI)]]**: +2. **[[Dependency Injection (DI)|Dependency Injection (DI]]**: * **객체 생성이 아닌 주입**: 클래스 내부에서 의존 객체를 직접 생성(New)하지 않고, 외부(생성자, 메서드 등)에서 주입받습니다. * **유연한 교체**: 인터페이스를 통해 종속성을 주입받으므로, 실제 구현체를 환경(Staging, Production)이나 테스트 목적(Mocking)에 따라 쉽게 교체할 수 있습니다. 3. **코드 리뷰에서의 역할**: @@ -28,9 +28,9 @@ last_reinforced: 2026-05-01 - **의존성 그래프의 복잡성**: 주입되는 객체가 많아지면 객체 생성 로직이나 DI 컨테이너 설정이 복잡해집니다. 생성자 주입(Constructor Injection)을 권장하고 클래스의 책임을 작게 유지하여 주입되는 의존성 수를 제한해야 합니다. ## 🔗 지식 연결 (Graph) -- [[SOLID Principles]]: DIP가 포함된 설계 원칙 그룹. -- [[Clean Architecture & Patterns]]: DIP를 통해 도메인 로직을 보호하는 상위 아키텍처. -- [[Testing Strategy]]: DI가 가능하게 하는 테스트 용이성. -- [[Single Responsibility Principle (SRP)]]: 의존성이 많아지는 것을 방지하는 근거. -- [[Over-engineering]]: 무분별한 추상화의 위험. +- [[SOLID Principles|SOLID Principles]]: DIP가 포함된 설계 원칙 그룹. +- [[Clean Architecture & Patterns|Clean Architecture & Patterns]]: DIP를 통해 도메인 로직을 보호하는 상위 아키텍처. +- [[Testing Strategy|Testing Strategy]]: DI가 가능하게 하는 테스트 용이성. +- [[Single Responsibility Principle (SRP)|Single Responsibility Principle (SRP]]: 의존성이 많아지는 것을 방지하는 근거. +- Over-engineering: 무분별한 추상화의 위험. --- diff --git a/10_Wiki/Topics/02_Architecture_Principles/Index.md b/10_Wiki/Topics/02_Architecture_Principles/Index.md index c70a47f2..cfe82790 100644 --- a/10_Wiki/Topics/02_Architecture_Principles/Index.md +++ b/10_Wiki/Topics/02_Architecture_Principles/Index.md @@ -1,8 +1,8 @@ # Index: Topics > 02_Architecture_Principles ## 📝 Documents -- [[API_Communication_Patterns]] -- [[Component_Design_Patterns]] -- [[Separation_of_Concerns]] -- [[Single_Source_of_Truth]] -- [[Systemic_Simulation_Principles]] +- [[API_Communication_Patterns|API_Communication_Patterns]] +- [[Component_Design_Patterns|Component_Design_Patterns]] +- [[Separation_of_Concerns|Separation_of_Concerns]] +- [[Single_Source_of_Truth|Single_Source_of_Truth]] +- [[Systemic_Simulation_Principles|Systemic_Simulation_Principles]] diff --git a/10_Wiki/Topics/02_Architecture_Principles/MVC (Model-View-Controller).md b/10_Wiki/Topics/02_Architecture_Principles/MVC (Model-View-Controller).md index bcd69c3a..33bbd1f7 100644 --- a/10_Wiki/Topics/02_Architecture_Principles/MVC (Model-View-Controller).md +++ b/10_Wiki/Topics/02_Architecture_Principles/MVC (Model-View-Controller).md @@ -6,7 +6,7 @@ tags: [architecture, design-pattern, mvc, decoupling, ui-architecture, p-reinfor last_reinforced: 2026-05-01 --- -# [[MVC (Model-View-Controller)]] +# [[MVC (Model-View-Controller)|MVC (Model-View-Controller]] ## 📌 한 줄 통찰 (The Karpathy Summary) > "데이터(Model), 사용자 인터페이스(View), 로직 제어(Controller)를 분리하여 시스템의 관심사를 격리함으로써, UI의 변화가 데이터 구조에 영향을 주지 않도록 설계하는 고전적이고 강력한 관심사 분리(SoC) 패턴." @@ -29,9 +29,9 @@ MVC는 애플리케이션의 구조적 무결성을 유지하기 위한 가장 - **현대적 변형**: 웹 프레임워크의 발전에 따라 MVP, MVVM 등 다양한 변형 패턴이 등장하였으나, 관심사 분리라는 핵심 철학은 MVC에서 계승되었습니다. ## 🔗 지식 연결 (Graph) -- [[Design Patterns]]: 아키텍처 패턴의 범주. -- [[Clean Architecture]]: MVC를 보다 고도화한 계층화 구조. -- [[SOLID Principles]]: 각 계층의 단일 책임을 정의하는 원칙. -- [[Separation of Concerns (SoC)]]: 패턴의 근본적인 설계 철학. -- [[Code Health]]: 일관된 패턴 준수가 가져오는 시스템의 건강성. +- Design Patterns: 아키텍처 패턴의 범주. +- [[Clean Architecture|Clean Architecture]]: MVC를 보다 고도화한 계층화 구조. +- [[SOLID Principles|SOLID Principles]]: 각 계층의 단일 책임을 정의하는 원칙. +- [[관심사의 분리 (Separation of Concerns SoC)|Separation of Concerns (SoC]]: 패턴의 근본적인 설계 철학. +- Code Health: 일관된 패턴 준수가 가져오는 시스템의 건강성. --- diff --git a/10_Wiki/Topics/02_Architecture_Principles/SOLID Principles.md b/10_Wiki/Topics/02_Architecture_Principles/SOLID Principles.md index c1a5068a..1f2eb480 100644 --- a/10_Wiki/Topics/02_Architecture_Principles/SOLID Principles.md +++ b/10_Wiki/Topics/02_Architecture_Principles/SOLID Principles.md @@ -6,7 +6,7 @@ tags: [architecture, ooad, solid-principles, maintainability, code-review, p-rei last_reinforced: 2026-05-01 --- -# [[SOLID Principles]] +# [[SOLID Principles|SOLID Principles]] ## 📌 한 줄 통찰 (The Karpathy Summary) > "소프트웨어의 유지보수성과 확장성을 보장하기 위한 5가지 핵심 설계 기둥: 인지적 부하를 낮추고, 변화에 유연하며, 결합도가 낮은 강건한 시스템을 구축하기 위한 객체지향 설계의 표준 지침." @@ -14,20 +14,20 @@ last_reinforced: 2026-05-01 ## 📖 구조화된 지식 (Synthesized Content) SOLID 원칙은 코드 리뷰와 시스템 설계의 무결성을 평가하는 핵심 기준입니다. -1. **[[Single Responsibility Principle (SRP)]]**: 클래스나 함수는 단 하나의 변경 이유만을 가져야 합니다. 모듈화를 통해 가독성과 테스트 용이성을 극대화합니다. +1. **[[Single Responsibility Principle (SRP)|Single Responsibility Principle (SRP]]**: 클래스나 함수는 단 하나의 변경 이유만을 가져야 합니다. 모듈화를 통해 가독성과 테스트 용이성을 극대화합니다. 2. **Open-Closed Principle (OCP)**: 확장에는 열려 있고 수정에는 닫혀 있어야 합니다. 기존 코드를 건드리지 않고 새로운 기능을 추가할 수 있는 구조를 지향합니다. 3. **Liskov Substitution Principle (LSP)**: 하위 타입은 언제나 상위 타입으로 교체 가능해야 합니다. 상속 구조에서의 행동 일관성을 보장합니다. 4. **Interface Segregation Principle (ISP)**: 클라이언트가 사용하지 않는 메서드에 의존하도록 강요해서는 안 됩니다. 거대한 인터페이스보다 구체적이고 작은 인터페이스 여러 개가 낫습니다. -5. **[[Dependency Inversion Principle (DIP)]]**: 고수준 모듈은 저수준 모듈에 의존해서는 안 되며, 둘 다 추상화에 의존해야 합니다. 구체적인 구현이 아닌 추상화에 의존하여 결합도를 낮춥니다. +5. **[[의존성 역전 원칙 (Dependency Inversion Principle DIP)|Dependency Inversion Principle (DIP]]**: 고수준 모듈은 저수준 모듈에 의존해서는 안 되며, 둘 다 추상화에 의존해야 합니다. 구체적인 구현이 아닌 추상화에 의존하여 결합도를 낮춥니다. ## ⚠️ 모순 및 업데이트 (Contradictions & RL Update) - **추상화의 비용**: 확장성을 위해 인터페이스와 추상화를 과도하게 도입할 경우, 코드의 직관성이 떨어지고 오버엔지니어링(Over-engineering)으로 이어질 수 있습니다. 현재의 요구사항과 미래의 유연성 사이의 실용적 타협(Trade-off)이 필수적입니다. - **실행 흐름 파악의 어려움**: DI(의존성 주입)를 극한으로 활용할 경우 런타임에 의존성이 결정되므로, 코드 정적 분석만으로는 전체 실행 흐름을 파악하기 어려워질 수 있습니다. 이를 보완하기 위한 명확한 문서화와 추적 로직이 필요합니다. ## 🔗 지식 연결 (Graph) -- [[Single Responsibility Principle (SRP)]]: 첫 번째 원칙의 심화. -- [[Dependency Injection (DI)]]: DIP를 실현하는 구체적 기법. -- [[Clean Architecture]]: SOLID를 애플리케이션 전체로 확장한 구조. -- [[Abstraction & Over-engineering]]: 설계 시 경계해야 할 트레이드오프. -- [[Test-Driven Development (TDD)]]: 테스트하기 좋은 코드를 만드는 원칙으로서의 연결. +- [[Single Responsibility Principle (SRP)|Single Responsibility Principle (SRP]]: 첫 번째 원칙의 심화. +- [[Dependency Injection (DI)|Dependency Injection (DI]]: DIP를 실현하는 구체적 기법. +- [[Clean Architecture|Clean Architecture]]: SOLID를 애플리케이션 전체로 확장한 구조. +- Abstraction & Over-engineering: 설계 시 경계해야 할 트레이드오프. +- Test-Driven Development (TDD: 테스트하기 좋은 코드를 만드는 원칙으로서의 연결. --- diff --git a/10_Wiki/Topics/02_Architecture_Principles/Separation_of_Concerns.md b/10_Wiki/Topics/02_Architecture_Principles/Separation_of_Concerns.md index de2734ef..671f641e 100644 --- a/10_Wiki/Topics/02_Architecture_Principles/Separation_of_Concerns.md +++ b/10_Wiki/Topics/02_Architecture_Principles/Separation_of_Concerns.md @@ -1,6 +1,6 @@ --- -title: 시스템 아키텍처와 관심사 분리 ([[Separation of Concerns]]) -category: Software [[Architecture]] +title: 시스템 아키텍처와 관심사 분리 ([[_뇌와 팔다리의 분리_ - 관심사의 분리 (Separation of Concerns)|Separation of Concerns]]) +category: Software [[Architecture|Architecture]] tags: [Architecture, SoC, Modular Design, Design Pattern] created: 2026-04-20 --- @@ -11,8 +11,8 @@ created: 2026-04-20 복잡한 소프트웨어 시스템을 역할별로 구분된 독립적인 모듈로 나누어, 유지보수성과 확장성을 극대화하는 설계 철학입니다. ## 🚀 계층구조 예시 (Layering Example) -1. **[[Logic]] Engine**: 순수 비즈니스 로직 및 규칙 수행 (예: `gameWorker.js`) -2. **[[State]] Manager**: 데이터의 중앙 집중 처리 (예: `TetrisGame.jsx`) +1. **[[Logic|Logic]] Engine**: 순수 비즈니스 로직 및 규칙 수행 (예: `gameWorker.js`) +2. **[[State|State]] Manager**: 데이터의 중앙 집중 처리 (예: `TetrisGame.jsx`) 3. **View Layer**: 사용자 인터페이스 표현 및 렌더링 (예: React Components) ## 💡 레슨 런 (Lesson Learned) @@ -21,5 +21,5 @@ created: 2026-04-20 > 기능을 추가할 때 기존 코드를 수정하기보다 새로운 모듈을 덧붙일 수 있는 구조를 고민해야 합니다. ## 🔗 연결된 지식 -- [[WebWorker_Performance]] -- [[Single_Source_of_Truth]] +- [[WebWorker_Performance|WebWorker_Performance]] +- [[Single_Source_of_Truth|Single_Source_of_Truth]] diff --git a/10_Wiki/Topics/02_Architecture_Principles/Single Responsibility Principle (SRP).md b/10_Wiki/Topics/02_Architecture_Principles/Single Responsibility Principle (SRP).md index 5a768a8e..e28fcba3 100644 --- a/10_Wiki/Topics/02_Architecture_Principles/Single Responsibility Principle (SRP).md +++ b/10_Wiki/Topics/02_Architecture_Principles/Single Responsibility Principle (SRP).md @@ -6,7 +6,7 @@ tags: [architecture, srp, cohesion, refactoring, code-review, p-reinforce] last_reinforced: 2026-05-01 --- -# [[Single Responsibility Principle (SRP)]] +# [[Single Responsibility Principle (SRP)|Single Responsibility Principle (SRP]] ## 📌 한 줄 통찰 (The Karpathy Summary) > "하나의 모듈은 오직 하나의 변경 이유(Reason to change)만을 가져야 한다: 코드의 응집도를 높이고 복잡성을 분산하여, 버그 수정과 기능 확장이 다른 영역에 미치는 부작용을 최소화하는 설계의 기초." @@ -28,9 +28,9 @@ SRP는 객체 지향 설계의 첫 번째 단추이자 가장 보편적인 리 - **아키텍처적 부채**: 초기 설계 시 SRP를 무시하면 시간이 흐를수록 '신(God) 객체'가 탄생하며, 이는 리팩토링 비용을 기하급수적으로 증가시키는 주요 원인이 됩니다. ## 🔗 지식 연결 (Graph) -- [[SOLID Principles]]: 5대 원칙의 시작점. -- [[Testability]]: 테스트하기 좋은 코드를 만드는 직접적 원인. -- [[Refactoring]]: SRP 위반 시 리뷰어가 내리는 핵심 처방. -- [[Clean Architecture]]: 책임을 계층별로 격리하는 거시적 구조. -- [[Code Readability]]: 단순해진 코드가 가져오는 가독성 향상. +- [[SOLID Principles|SOLID Principles]]: 5대 원칙의 시작점. +- [[테스트 용이성 (Testability)|Testability]]: 테스트하기 좋은 코드를 만드는 직접적 원인. +- [[Refactoring|Refactoring]]: SRP 위반 시 리뷰어가 내리는 핵심 처방. +- [[Clean Architecture|Clean Architecture]]: 책임을 계층별로 격리하는 거시적 구조. +- Code Readability: 단순해진 코드가 가져오는 가독성 향상. --- diff --git a/10_Wiki/Topics/02_Architecture_Principles/Single_Source_of_Truth.md b/10_Wiki/Topics/02_Architecture_Principles/Single_Source_of_Truth.md index 1cfcef47..f89b9727 100644 --- a/10_Wiki/Topics/02_Architecture_Principles/Single_Source_of_Truth.md +++ b/10_Wiki/Topics/02_Architecture_Principles/Single_Source_of_Truth.md @@ -1,7 +1,7 @@ --- -title: 상태 관리의 단일 진실 공급원 ([[Single Source of Truth]]) -category: Software [[Architecture]] -tags: [[[State]] [[Management]], Data Consistency, Redux, Architecture] +title: 상태 관리의 단일 진실 공급원 ([[Single_Source_of_Truth|Single Source of Truth]]) +category: Software [[Architecture|Architecture]] +tags: [[State|[State]] [[Management|Management]], Data Consistency, Redux, Architecture] created: 2026-04-20 --- @@ -10,7 +10,7 @@ created: 2026-04-20 ## 🎯 개요 (Overview) 시스템의 핵심 데이터를 중앙 집중식으로 관리하여, 데이터 불일치(Inconsistency) 현상을 원천 차단하고 예측 가능한 데이터 흐름을 확보하는 설계 원칙입니다. -## 🚀 주요 원칙 (Key [[Principles]]) +## 🚀 주요 원칙 (Key [[Principles|Principles]]) - **단일 지점 정의 (Defined at Single Point)**: 상태는 오직 한 곳에서만 정의되고 관리되어야 합니다. - **예측 가능성 (Predictability)**: 상태 변경은 정해진 규칙(Action/Setter)을 통해서만 발생하여 디버깅을 용이하게 합니다. @@ -20,5 +20,5 @@ created: 2026-04-20 > 코드의 파편화를 막기 위해 데이터의 책임 범위(Responsibility)를 명확히 하는 것이 대규모 프로젝트 성공의 열쇠입니다. ## 🔗 연결된 지식 -- [[Separation_of_Concerns]] -- [[Domain-Driven Design (DDD)]] +- [[Separation_of_Concerns|Separation_of_Concerns]] +- [[Domain-Driven-Design-DDD|Domain-Driven Design (DDD]] diff --git a/10_Wiki/Topics/02_Architecture_Principles/Systemic_Simulation_Principles.md b/10_Wiki/Topics/02_Architecture_Principles/Systemic_Simulation_Principles.md index 894916cb..de1bc8ad 100644 --- a/10_Wiki/Topics/02_Architecture_Principles/Systemic_Simulation_Principles.md +++ b/10_Wiki/Topics/02_Architecture_Principles/Systemic_Simulation_Principles.md @@ -1,7 +1,7 @@ --- title: 시스템 시뮬레이션 설계 원리 -category:[[ system]]ic Modeling & Fun -tags: [Simulation, [[Physics]] Engine, Systemic Modeling, Ruleset] +category:Systemic Modeling & Fun +tags: [Simulation, [[Physics|Physics]] Engine, Systemic Modeling, Ruleset] created: 2026-04-20 --- @@ -20,5 +20,5 @@ created: 2026-04-20 > 이를 통해 단순한 게임을 넘어 자율주행, 물리 엔진 등 고도의 결정론적 시스템 모델링이 가능해집니다. ## 🔗 연결된 지식 -- [[WebWorker_Performance]] -- [[Separation_of_Concerns]] +- [[WebWorker_Performance|WebWorker_Performance]] +- [[Separation_of_Concerns|Separation_of_Concerns]] diff --git a/10_Wiki/Topics/02_Software_Engineering/Modern Engineering Practices (현대적 엔지니어링 프랙티스).md b/10_Wiki/Topics/02_Software_Engineering/Modern Engineering Practices (현대적 엔지니어링 프랙티스).md index 99c4c4dd..e663830f 100644 --- a/10_Wiki/Topics/02_Software_Engineering/Modern Engineering Practices (현대적 엔지니어링 프랙티스).md +++ b/10_Wiki/Topics/02_Software_Engineering/Modern Engineering Practices (현대적 엔지니어링 프랙티스).md @@ -1,4 +1,4 @@ -# [[Modern Engineering Practices (현대적 엔지니어링 프랙티스)]] +# [[Modern Engineering Practices (현대적 엔지니어링 프랙티스)|Modern Engineering Practices (현대적 엔지니어링 프랙티스]] ## 📌 Brief Summary 현대적 엔지니어링 프랙티스는 애자일(Agile) 철학을 바탕으로 개발 속도, 품질, 그리고 인프라 관리의 효율성을 극대화하기 위한 구체적인 방법론들의 모음입니다. Extreme Programming(XP)에서 파생된 짝 프로그래밍(Pair Programming)을 통해 실시간 피드백 루프를 형성하고, 기능 플래그(Feature Flags)를 활용해 코드 배포와 기능 노출을 분리하며, 코드 기반 인프라(IaC)를 통해 서버 및 환경 구성을 자동화합니다 [1, 3]. 이러한 프랙티스들은 코드 리뷰를 단순한 '사후 검사'에서 '지속적이고 선제적인 품질 보증' 프로세스로 전환합니다. @@ -24,10 +24,10 @@ ## 🔗 Knowledge Connections ### Related Concepts -* **[[Agile Methodologies]]**: XP, 스크럼 등 유연성과 반복적 피드백을 중시하는 상위 방법론입니다. -* **[[Continuous Integration (CI)]]**: 작은 단위의 빈번한 병합을 가능하게 하는 IaC와 기능 플래그의 기술적 토대입니다. -* **[[Constructive Feedback]]**: XP 철학에서 강조하는 교육적이고 협력적인 리뷰 커뮤니케이션 방식입니다. -* **[[Shift-Left Security]]**: IaC 리뷰를 통해 보안 설정을 개발 초기 단계에서 검증하는 전략적 연계입니다. +* **Agile Methodologies**: XP, 스크럼 등 유연성과 반복적 피드백을 중시하는 상위 방법론입니다. +* **[[Continuous Integration (CI)|Continuous Integration (CI]]**: 작은 단위의 빈번한 병합을 가능하게 하는 IaC와 기능 플래그의 기술적 토대입니다. +* **Constructive Feedback**: XP 철학에서 강조하는 교육적이고 협력적인 리뷰 커뮤니케이션 방식입니다. +* **Shift-Left Security**: IaC 리뷰를 통해 보안 설정을 개발 초기 단계에서 검증하는 전략적 연계입니다. ### Deeper Research Questions * 짝 프로그래밍을 통한 실시간 리뷰가 비동기 PR 리뷰에 비해 '결함 밀도(Defect Density)'와 '지식 전파 속도' 측면에서 가지는 정량적인 비교 우위는 어느 정도인가? @@ -44,8 +44,8 @@ * **My Project Relevance:** 중요도와 위험도에 따라 리뷰 방식을 차별화(Tier 1: 자동화, Tier 2: 비동기, Tier 3: 짝 프로그래밍)하여 효율적인 품질 관리 체계를 구축합니다 [56]. ### Adjacent Topics -* **[[Trunk-Based Development]]**: 기능 플래그를 활용해 브랜치 수명을 극도로 단축시키는 고도화된 개발 워크플로우입니다. -* **[[Site Reliability Engineering (SRE)]]**: IaC와 자동화를 통해 시스템의 가용성과 복원력을 관리하는 운영 철학입니다. +* **Trunk-Based Development**: 기능 플래그를 활용해 브랜치 수명을 극도로 단축시키는 고도화된 개발 워크플로우입니다. +* **Site Reliability Engineering (SRE**: IaC와 자동화를 통해 시스템의 가용성과 복원력을 관리하는 운영 철학입니다. --- *Last updated: 2026-05-02* diff --git a/10_Wiki/Topics/02_Software_Engineering/Software Engineering Core Principles (소프트웨어 엔지니어링 핵심 원칙).md b/10_Wiki/Topics/02_Software_Engineering/Software Engineering Core Principles (소프트웨어 엔지니어링 핵심 원칙).md index 11262594..ca3c16b9 100644 --- a/10_Wiki/Topics/02_Software_Engineering/Software Engineering Core Principles (소프트웨어 엔지니어링 핵심 원칙).md +++ b/10_Wiki/Topics/02_Software_Engineering/Software Engineering Core Principles (소프트웨어 엔지니어링 핵심 원칙).md @@ -1,4 +1,4 @@ -# [[Software Engineering Core Principles (소프트웨어 엔지니어링 핵심 원칙)]] +# [[Software Engineering Core Principles (소프트웨어 엔지니어링 핵심 원칙)|Software Engineering Core Principles (소프트웨어 엔지니어링 핵심 원칙]] ## 📌 Brief Summary 소프트웨어 엔지니어링 핵심 원칙은 유지보수성이 뛰어나고 확장이 용이한 고품질 시스템을 구축하기 위한 설계 지침입니다 [1]. SOLID 원칙을 기반으로 객체 간의 결합도를 낮추고 응집도를 높이며, 검증된 디자인 패턴을 적용하여 반복되는 설계 문제에 최적의 해결책을 제시합니다 [4]. 코드 리뷰 과정에서 리뷰어는 단순히 코드가 동작하는지를 넘어, 해당 코드가 조직의 아키텍처 가이드라인과 설계 원칙에 부합하는 구조적인 무결성을 갖췄는지 평가해야 합니다 [1, 3]. @@ -24,10 +24,10 @@ ## 🔗 Knowledge Connections ### Related Concepts -* **[[Clean Architecture]]**: SOLID 원칙이 실제 계층형 아키텍처로 구현된 고수준 디자인 패턴입니다. -* **[[Unit Testing / Testability]]**: SRP와 DIP를 준수할 때 모의 객체(Mock)를 활용한 단위 테스트가 용이해집니다. -* **[[Technical Debt (기술 부채)]]**: 설계 원칙을 무시했을 때 누적되는 눈에 보이지 않는 유지보수 비용입니다. -* **[[Code Refactoring]]**: 거대해진 클래스를 SRP에 맞춰 분리하고 시스템을 안전하게 재구조화하는 활동입니다. +* **[[Clean Architecture|Clean Architecture]]**: SOLID 원칙이 실제 계층형 아키텍처로 구현된 고수준 디자인 패턴입니다. +* **Unit Testing / Testability**: SRP와 DIP를 준수할 때 모의 객체(Mock)를 활용한 단위 테스트가 용이해집니다. +* **Technical Debt (기술 부채**: 설계 원칙을 무시했을 때 누적되는 눈에 보이지 않는 유지보수 비용입니다. +* **[[Code Refactoring|Code Refactoring]]**: 거대해진 클래스를 SRP에 맞춰 분리하고 시스템을 안전하게 재구조화하는 활동입니다. ### Deeper Research Questions * 복잡한 도메인 비즈니스 로직을 구현할 때, 단일 책임 원칙(SRP)을 위반하지 않기 위한 '책임의 경계'를 식별하는 구체적인 프레임워크는 무엇인가? @@ -44,8 +44,8 @@ * **My Project Relevance:** 체크리스트에 '아키텍처 및 코드 구조 검토' 항목을 포함하여, PR이 기술 부채를 유발하지 않는지 객관적으로 검증합니다 [51]. ### Adjacent Topics -* **[[Domain-Driven Design (DDD)]]**: 비즈니스 도메인의 복잡성을 관리하기 위한 상위 수준의 설계 전략입니다. -* **[[Egoless Programming]]**: 개인의 취항보다 팀의 설계 원칙을 우선시하는 협업 철학입니다. +* **[[Domain-Driven-Design-DDD|Domain-Driven Design (DDD]]**: 비즈니스 도메인의 복잡성을 관리하기 위한 상위 수준의 설계 전략입니다. +* **Egoless Programming**: 개인의 취항보다 팀의 설계 원칙을 우선시하는 협업 철학입니다. --- *Last updated: 2026-05-02* diff --git a/10_Wiki/Topics/02_Software_Engineering/Testing Methodologies (테스트 방법론).md b/10_Wiki/Topics/02_Software_Engineering/Testing Methodologies (테스트 방법론).md index f6cd23df..ca96f2d0 100644 --- a/10_Wiki/Topics/02_Software_Engineering/Testing Methodologies (테스트 방법론).md +++ b/10_Wiki/Topics/02_Software_Engineering/Testing Methodologies (테스트 방법론).md @@ -1,4 +1,4 @@ -# [[Testing Methodologies (테스트 방법론)]] +# [[Testing Methodologies (테스트 방법론)|Testing Methodologies (테스트 방법론]] ## 📌 Brief Summary 테스트 방법론(Testing Methodologies)은 소프트웨어 개발 및 코드 리뷰 과정에서 프로그램의 기능적 정확성, 안정성, 보안성을 검증하기 위한 체계적인 접근 방식입니다 [1]. 자동화된 테스트(Automated Testing)를 통해 사람이 직접 리뷰하기 전 코드의 기초 결함을 걸러내고, TDD 및 BDD와 같은 방법론을 적용하여 설계 품질을 높입니다. 이는 인간 리뷰어가 사소한 스타일 오류에서 벗어나 아키텍처와 비즈니스 로직 등 고차원적인 피드백에 집중할 수 있도록 돕는 강력한 품질 게이트(Quality Gate) 역할을 수행합니다. @@ -26,10 +26,10 @@ ## 🔗 Knowledge Connections ### Related Concepts -* **[[CI/CD Pipeline]]**: 자동화된 테스트가 지속적으로 실행되고 품질 게이트 역할을 수행하는 핵심 인프라입니다. -* **[[Static Code Analysis]]**: 코드를 실행하지 않고 잠재적 버그와 스타일 위반을 찾아내는 보완적 검증 수단입니다. -* **[[Mocking & Stubbing]]**: 단위 테스트 시 외부 의존성을 격리하여 독립적인 테스트 환경을 구축하는 기술입니다. -* **[[Shift-Left Security]]**: 보안 테스트를 개발 초기 단계로 앞당겨 수정 비용을 절감하는 전략입니다. +* **[[CI-CD Pipeline|CI/CD Pipeline]]**: 자동화된 테스트가 지속적으로 실행되고 품질 게이트 역할을 수행하는 핵심 인프라입니다. +* **Static Code Analysis**: 코드를 실행하지 않고 잠재적 버그와 스타일 위반을 찾아내는 보완적 검증 수단입니다. +* **Mocking & Stubbing**: 단위 테스트 시 외부 의존성을 격리하여 독립적인 테스트 환경을 구축하는 기술입니다. +* **Shift-Left Security**: 보안 테스트를 개발 초기 단계로 앞당겨 수정 비용을 절감하는 전략입니다. ### Deeper Research Questions * 각 프로젝트의 비즈니스 중요도와 변경 빈도에 따라 최적의 '투자 대비 효율(ROI)'을 내는 테스트 커버리지 임계값은 어떻게 산출하는가? @@ -46,8 +46,8 @@ * **My Project Relevance:** 스타일 및 기초 로직 검증을 자동화에 위임하여, 리뷰어가 시스템 아키텍처와 핵심 비즈니스 로직 논의에 집중할 수 있는 문화를 정착시킵니다. ### Adjacent Topics -* **[[Technical Debt (기술 부채)]]**: 테스트가 결여되거나 잘못 작성된 코드가 장기적으로 초래하는 유지보수 비용과 개발 속도 저하에 대해 탐구합니다. -* **[[Mutation Testing]]**: 테스트 코드 자체의 품질(결함 발견 능력)을 측정하고 개선하는 고급 테스트 기법입니다. +* **Technical Debt (기술 부채**: 테스트가 결여되거나 잘못 작성된 코드가 장기적으로 초래하는 유지보수 비용과 개발 속도 저하에 대해 탐구합니다. +* **Mutation Testing**: 테스트 코드 자체의 품질(결함 발견 능력)을 측정하고 개선하는 고급 테스트 기법입니다. --- *Last updated: 2026-05-02* diff --git a/10_Wiki/Topics/03_DevOps_Environment/CI-CD Pipeline (지속적 통합 및 배포).md b/10_Wiki/Topics/03_DevOps_Environment/CI-CD Pipeline (지속적 통합 및 배포).md index f8b46188..4209c520 100644 --- a/10_Wiki/Topics/03_DevOps_Environment/CI-CD Pipeline (지속적 통합 및 배포).md +++ b/10_Wiki/Topics/03_DevOps_Environment/CI-CD Pipeline (지속적 통합 및 배포).md @@ -1,4 +1,4 @@ -# [[CI/CD Pipeline (지속적 통합 및 배포)]] +# [[CI-CD Pipeline (지속적 통합 및 배포)|CI/CD Pipeline (지속적 통합 및 배포]] ## 📌 Brief Summary CI/CD(Continuous Integration and Continuous Deployment) 파이프라인은 소프트웨어의 빌드, 테스트 및 배포 과정을 자동화하여 코드 변경 사항을 신속하고 신뢰할 수 있게 통합하고 배포하는 시스템입니다 [1]. 코드 리뷰 과정에서 CI/CD 파이프라인은 인간 리뷰어가 검토하기 전에 린팅(Linting), 스타일 검사, 단위 테스트, 정적 코드 분석 등을 기계적으로 먼저 수행하는 자동화된 1차 방어선 역할을 합니다 [2, 3]. 이를 통해 자동화된 품질 및 보안 게이트를 구축함으로써 전체 개발 프로세스의 속도와 안정성을 비약적으로 향상시킵니다 [5, 6]. @@ -20,10 +20,10 @@ CI/CD(Continuous Integration and Continuous Deployment) 파이프라인은 소 ## 🔗 Knowledge Connections ### Related Concepts -* **[[Automated Testing]]**: CI/CD 파이프라인 내에서 코드의 기능적 정확성을 기계적으로 확인하는 핵심 단계입니다. -* **[[Linters and Formatters]]**: 스타일 논쟁(Nitpicking)을 제거하고 코드 일관성을 유지하기 위해 파이프라인 초기 단계에 통합되는 도구들입니다. -* **[[SAST (Static Application Security Testing)]]**: 배포 전 소스 코드 수준에서 보안 취약점을 자동으로 스캔하는 기술입니다. -* **[[Pull Request (PR) Workflow]]**: 코드 병합 전 리뷰를 요청하는 프로세스로, CI/CD 파이프라인을 동작시키는 주요 트리거입니다. +* **Automated Testing**: CI/CD 파이프라인 내에서 코드의 기능적 정확성을 기계적으로 확인하는 핵심 단계입니다. +* **Linters and Formatters**: 스타일 논쟁(Nitpicking)을 제거하고 코드 일관성을 유지하기 위해 파이프라인 초기 단계에 통합되는 도구들입니다. +* **[[SAST (Static Application Security Testing)|SAST (Static Application Security Testing]]**: 배포 전 소스 코드 수준에서 보안 취약점을 자동으로 스캔하는 기술입니다. +* **Pull Request (PR) Workflow**: 코드 병합 전 리뷰를 요청하는 프로세스로, CI/CD 파이프라인을 동작시키는 주요 트리거입니다. ### Deeper Research Questions * 대규모 모노레포(Monorepo) 환경에서 변경된 영역에 대해서만 선택적으로 자동화 검증을 수행(Impact Analysis)하도록 파이프라인을 최적화하는 기술적 방법은 무엇인가? @@ -39,8 +39,8 @@ CI/CD(Continuous Integration and Continuous Deployment) 파이프라인은 소 * **My Project Relevance:** 리뷰 대기 시간이 길거나 반복적인 스타일 지적이 많을 때, 가장 먼저 도입하여 리뷰 프로세스의 병목을 해소해야 할 최우선 인프라입니다. ### Adjacent Topics -* **[[Feature Flags]]**: CI/CD를 통해 코드를 자주 병합하면서도 실제 기능 노출은 런타임에 제어하는 고급 배포 기법으로 확장됩니다. -* **[[DORA Metrics]]**: 배포 빈도, 변경 실패율 등 CI/CD 파이프라인의 성능을 측정하고 개선하는 지표로 연결됩니다. +* **[[Feature-Flags|Feature Flags]]**: CI/CD를 통해 코드를 자주 병합하면서도 실제 기능 노출은 런타임에 제어하는 고급 배포 기법으로 확장됩니다. +* **[[DORA-Metrics|DORA Metrics]]**: 배포 빈도, 변경 실패율 등 CI/CD 파이프라인의 성능을 측정하고 개선하는 지표로 연결됩니다. --- *Last updated: 2026-05-02* diff --git a/10_Wiki/Topics/03_DevOps_Environment/CI-CD Pipeline.md b/10_Wiki/Topics/03_DevOps_Environment/CI-CD Pipeline.md index ae08aa9e..4a444ae2 100644 --- a/10_Wiki/Topics/03_DevOps_Environment/CI-CD Pipeline.md +++ b/10_Wiki/Topics/03_DevOps_Environment/CI-CD Pipeline.md @@ -6,7 +6,7 @@ tags: [development, ci-cd, automation, quality-gate, devops, p-reinforce] last_reinforced: 2026-05-01 --- -# [[CI-CD Pipeline]] +# [[CI-CD Pipeline|CI-CD Pipeline]] ## 📌 한 줄 통찰 (The Karpathy Summary) > "소프트웨어의 빌드, 테스트, 배포 전 과정을 자동화하여, 인간 리뷰어보다 먼저 결함을 찾아내는 '기계적 파수꾼'이자 배포의 신뢰성을 보장하는 핵심 인프라." @@ -27,9 +27,9 @@ CI-CD는 현대적 개발 워크플로우에서 품질과 속도를 동시에 - **자동화의 한계**: CI-CD는 정해진 패턴은 잘 찾지만 비즈니스적 맥락이나 설계상의 논리적 오류는 잡지 못합니다. 기계적 검증과 인간의 정성적 리뷰가 결합된 상호 보완 구조를 유지해야 합니다. ## 🔗 지식 연결 (Graph) -- [[Shift-Left Security]]: 보안 점검을 CI 단계로 앞당기는 전략. -- [[Automated Testing]]: 파이프라인의 핵심 관문. -- [[Pull Request Workflow]]: CI-CD가 트리거되는 지점. -- [[DevSecOps]]: 보안이 내재화된 자동화 철학. -- [[Infrastructure as Code (IaC)]]: 인프라 배포의 자동화 확장. +- Shift-Left Security: 보안 점검을 CI 단계로 앞당기는 전략. +- Automated Testing: 파이프라인의 핵심 관문. +- Pull Request Workflow: CI-CD가 트리거되는 지점. +- [[DevSecOps|DevSecOps]]: 보안이 내재화된 자동화 철학. +- [[Infrastructure-as-Code-IaC|Infrastructure as Code (IaC]]: 인프라 배포의 자동화 확장. --- diff --git a/10_Wiki/Topics/03_DevOps_Environment/Deployment_Final_Gate.md b/10_Wiki/Topics/03_DevOps_Environment/Deployment_Final_Gate.md index f00857f0..307f3b06 100644 --- a/10_Wiki/Topics/03_DevOps_Environment/Deployment_Final_Gate.md +++ b/10_Wiki/Topics/03_DevOps_Environment/Deployment_Final_Gate.md @@ -1,11 +1,11 @@ --- title: 배포 프로토콜 및 CI/CD 자동화 -category: Software [[Architecture]] -tags: [Deployment, CI/CD, [[GitHub Actions]], Vercel, DevOps] +category: Software [[Architecture|Architecture]] +tags: [Deployment, CI/CD, [[GitHub Actions|GitHub Actions]], Vercel, DevOps] created: 2026-04-20 --- -# [[Deployment_Final_Gate]] (배포 및 자동화) +# [[Deployment_Final_Gate|Deployment_Final_Gate]] (배포 및 자동화) ## 📌 한 줄 통찰 (The Karpathy Summary) > 수동 배포는 '실버 불렛'이 아니라 '시한폭탄'이다. 인간의 손을 거치지 않는 자동화된 보급로만이 시스템의 영속성을 보장한다. @@ -22,5 +22,5 @@ created: 2026-04-20 - 무조건적인 '자동 배포'가 늘 정답은 아니다. 운영 단계에서는 '블루-그린 배포'나 '카나리 배포'처럼 트래픽을 조금씩 흘려보내며 안정성을 확인하는 고급 전략이 필요하다. ## 🔗 지식 연결 (Graph) -- Related: [[Modern_Environment_Ecosystem]] , [[Collaboration_Governance]] -- Pre-requisite: [[React_[[Testing]]_Strategy]] +- Related: [[Modern_Environment_Ecosystem|Modern_Environment_Ecosystem]] , [[Collaboration_Governance|Collaboration_Governance]] +- Pre-requisite: [[React_Testing_Strategy|React_Testing_Strategy]] diff --git a/10_Wiki/Topics/03_DevOps_Environment/DevOps_Environment_Setup.md b/10_Wiki/Topics/03_DevOps_Environment/DevOps_Environment_Setup.md index 425f2fcf..84e926dd 100644 --- a/10_Wiki/Topics/03_DevOps_Environment/DevOps_Environment_Setup.md +++ b/10_Wiki/Topics/03_DevOps_Environment/DevOps_Environment_Setup.md @@ -1,7 +1,7 @@ --- title: 개발 환경 및 실행 프로세스 관리 (DevOps & Setup) category: DevOps -tags: [DevOps, Environment, CI/CD, Process [[Management]]] +tags: [DevOps, Environment, CI/CD, Process [[Management|Management]]] created: 2026-04-20 --- @@ -21,4 +21,4 @@ created: 2026-04-20 > 논리적 로직의 완성뿐만 아니라, 그것이 실제로 구동되는 물리적 인프라 설정을 문서화하고 자동화하는 능력이 필수적입니다. ## 🔗 연결된 지식 -- [[Systemic_Simulation_Principles]] +- [[Systemic_Simulation_Principles|Systemic_Simulation_Principles]] diff --git a/10_Wiki/Topics/03_DevOps_Environment/Engineering Metrics (DORA).md b/10_Wiki/Topics/03_DevOps_Environment/Engineering Metrics (DORA).md index 9b623c51..85a7e948 100644 --- a/10_Wiki/Topics/03_DevOps_Environment/Engineering Metrics (DORA).md +++ b/10_Wiki/Topics/03_DevOps_Environment/Engineering Metrics (DORA).md @@ -6,7 +6,7 @@ tags: [governance, dora-metrics, engineering-metrics, performance, devops, cycle last_reinforced: 2026-05-01 --- -# [[Engineering Metrics (DORA)]] +# [[Engineering Metrics (DORA)|Engineering Metrics (DORA]] ## 📌 한 줄 통찰 (The Karpathy Summary) > "데이터에 기반하여 소프트웨어 인도 성과(Delivery Performance)를 정량화하고, 엘리트 팀의 벤치마크를 통해 개발 프로세스의 병목과 개선 방향을 제시하는 엔지니어링 표준 지표." @@ -31,9 +31,9 @@ DORA 지표는 데브옵스(DevOps) 연구를 통해 입증된 고성과 팀의 - **데이터의 맥락**: 단순 수치만으로 팀을 평가하기보다, 지표의 변화 추이를 통해 팀의 프로세스 건전성을 진단하고 병목을 해결하는 도구로 활용해야 합니다. ## 🔗 지식 연결 (Graph) -- [[Review Performance & Flow]]: DORA 지표를 달성하기 위한 구체적 운영 전략. -- [[Small Pull Requests (작은 PR)]]: Lead Time을 단축하는 가장 강력한 수단. -- [[Automated Quality & Review]]: 인간의 시간을 절약하여 성과를 극대화하는 기반. -- [[CI-CD Pipeline]]: 지표 수집과 자동화가 이루어지는 인프라. -- [[DORA Metrics]]: 원본 개념 정의. +- [[Review Performance & Flow|Review Performance & Flow]]: DORA 지표를 달성하기 위한 구체적 운영 전략. +- Small Pull Requests (작은 PR: Lead Time을 단축하는 가장 강력한 수단. +- [[Automated Quality & Review|Automated Quality & Review]]: 인간의 시간을 절약하여 성과를 극대화하는 기반. +- [[CI-CD Pipeline|CI-CD Pipeline]]: 지표 수집과 자동화가 이루어지는 인프라. +- [[DORA-Metrics|DORA Metrics]]: 원본 개념 정의. --- diff --git a/10_Wiki/Topics/03_DevOps_Environment/Git_Operation_Protocol.md b/10_Wiki/Topics/03_DevOps_Environment/Git_Operation_Protocol.md index cc502623..5fc8ed33 100644 --- a/10_Wiki/Topics/03_DevOps_Environment/Git_Operation_Protocol.md +++ b/10_Wiki/Topics/03_DevOps_Environment/Git_Operation_Protocol.md @@ -1,4 +1,4 @@ -# 🛠️ Git [[Opera]]tion & Work Log Protocol (Git 작업 및 기록 지침) +# 🛠️ Git [[Opera|Opera]]tion & Work Log Protocol (Git 작업 및 기록 지침) > **카테고리**: 03_DevOps_Environment, Automation > **상태**: 🟢 활성화 (Active) @@ -9,7 +9,7 @@ ## 📌 개요 (Overview) 본 문서는 Skybound 프로젝트를 포함한 4개 주요 개발 거점의 원격 저장소 동기화 정합성을 유지하고, 모든 AI 작업 과정을 체계적으로 문서화하기 위한 Git 운영 규정 및 작업 로그(Work Log) 시스템을 정의한다. -## 🔗 프로젝트별 Git 맵핑 ([[Repository]] Mapping) +## 🔗 프로젝트별 Git 맵핑 ([[Repository|Repository]] Mapping) 대표님의 명령 한마디로 정확한 경로에서 작업을 수행하기 위해 각 폴더별로 독립적인 Git 설정을 유지한다. | 프로젝트 | 로컬 경로 | 원격 저장소 (Remote URL) | 리모트 명칭 | @@ -17,7 +17,7 @@ | **Wiki (2nd)** | `E:\Wiki\2nd` | `https://github.com/wonseokjung/solopreneur-ai-agents.git` | `lm_sync` | | **Skybound** | `E:\Wiki\skybound` | `https://github.com/wonseokjung/skybound-protocol.git` | `origin` | | **Legal** | `E:\Wiki\legal-bridge` | `https://github.com/wonseokjung/legal-bridge.git` | `origin` | -| **Agent** | `E:\Wiki\auto-[[Research]]-agent`| `https://github.com/wonseokjung/auto-re[[Search]]-agent.git` | `origin` | +| **Agent** | `E:\Wiki\auto-[[Research|Research]]-agent`| `https://github.com/wonseokjung/auto-re[[Search|Search]]-agent.git` | `origin` | ## 🛠️ 운영 지침 (Operational Guidelines) @@ -37,7 +37,7 @@ - **Result**: 최종 결과 및 관련 연결 지식. ### 3. 위키화 (Wikification) -- `00_Raw`에 축적된 로그는 주기적으로 `10_Wiki\Topics` 하위 카테고리로 고도화([[Refinement]])되어 이동된다. +- `00_Raw`에 축적된 로그는 주기적으로 `10_Wiki\Topics` 하위 카테고리로 고도화([[Refinement|Refinement]])되어 이동된다. - 위키화가 완료된 원본 로그는 삭제하여 지식 베이스의 정결성을 유지한다. ## 🚀 기대 효과 diff --git a/10_Wiki/Topics/03_DevOps_Environment/Index.md b/10_Wiki/Topics/03_DevOps_Environment/Index.md index b88603c0..2ea162f6 100644 --- a/10_Wiki/Topics/03_DevOps_Environment/Index.md +++ b/10_Wiki/Topics/03_DevOps_Environment/Index.md @@ -1,8 +1,8 @@ # Index: Topics > 03_DevOps_Environment ## 📝 Documents -- [[Deployment_Final_Gate]] -- [[DevOps_Environment_Setup]] -- [[Git_Operation_Protocol]] -- [[Modern_Environment_Ecosystem]] -- [[Tetris_Project_Retrospective]] +- [[Deployment_Final_Gate|Deployment_Final_Gate]] +- [[DevOps_Environment_Setup|DevOps_Environment_Setup]] +- [[Git_Operation_Protocol|Git_Operation_Protocol]] +- [[Modern_Environment_Ecosystem|Modern_Environment_Ecosystem]] +- [[Tetris_Project_Retrospective|Tetris_Project_Retrospective]] diff --git a/10_Wiki/Topics/03_DevOps_Environment/Modern_Environment_Ecosystem.md b/10_Wiki/Topics/03_DevOps_Environment/Modern_Environment_Ecosystem.md index 9097a48b..40949316 100644 --- a/10_Wiki/Topics/03_DevOps_Environment/Modern_Environment_Ecosystem.md +++ b/10_Wiki/Topics/03_DevOps_Environment/Modern_Environment_Ecosystem.md @@ -1,11 +1,11 @@ --- title: 모던 개발 환경 및 프레임워크 생태계 -category: Software [[Architecture]] -tags: [Vite, [[Next.js]], Ecosystem, Modern Stack] +category: Software [[Architecture|Architecture]] +tags: [Vite, [[Next.js|Next.js]], Ecosystem, Modern Stack] created: 2026-04-20 --- -# [[Modern_Environment_Ecosystem]] (모던 개발 생태계) +# [[Modern_Environment_Ecosystem|Modern_Environment_Ecosystem]] (모던 개발 생태계) ## 📌 한 줄 통찰 (The Karpathy Summary) > 도구는 목적이 아니라 '생산성'을 위한 수단이다. 하지만 최신 생태계의 변화를 놓치는 것은 스스로 생산성을 깎아내는 것과 같다. @@ -16,11 +16,11 @@ created: 2026-04-20 - **Framework: Next.js (The Fullstack Edge)**: - 단순히 SEO를 위한 SSR 도구가 아니다. API Routes를 통한 서버리스 함수 구현, 데이터 캐싱 전략(ISR/SSG) 등 현대 웹이 요구하는 거의 모든 기능을 탑재한 '거버넌스' 그 자체다. - **패키지 매니저의 선택**: - - `pnpm` 또는 `npm v7+`의 워크스페이스 기능을 통해 모노레포([[Monorepo]]) 구조를 효율적으로 관리하고, 패키지 중복 설치를 최소화하여 빌드 성능을 최적화한다. + - `pnpm` 또는 `npm v7+`의 워크스페이스 기능을 통해 모노레포([[Monorepo|Monorepo]]) 구조를 효율적으로 관리하고, 패키지 중복 설치를 최소화하여 빌드 성능을 최적화한다. ## ⚠️ 모순 및 업데이트 (RL Update) - 최신 기술이 항상 정답은 아니다. 안정성이 최우선인 기업 환경에서는 검증된 `CRA` 혹은 `Webpack` 기반의 설정을 유지하는 것이 보수적인 면에서 유리할 수 있다. 기술 부채(Tech Debt)와 도입 비용을 항상 저울질하라. ## 🔗 지식 연결 (Graph) -- Related: [[Deployment_Final_Gate]] , Project_Architecture_Guidelines -- Foundation: [[TypeScript_Type_Safety]] +- Related: [[Deployment_Final_Gate|Deployment_Final_Gate]] , Project_Architecture_Guidelines +- Foundation: [[TypeScript_Type_Safety|TypeScript_Type_Safety]] diff --git a/10_Wiki/Topics/03_DevOps_Environment/Tetris_Project_Retrospective.md b/10_Wiki/Topics/03_DevOps_Environment/Tetris_Project_Retrospective.md index 9c5b3312..fc46e7c0 100644 --- a/10_Wiki/Topics/03_DevOps_Environment/Tetris_Project_Retrospective.md +++ b/10_Wiki/Topics/03_DevOps_Environment/Tetris_Project_Retrospective.md @@ -1,21 +1,21 @@ --- title: 프로젝트 회고: 고성능 테트리스 아키텍처 category: Projects -tags: [Retrospective, Tetris, [[Architecture]], Performance] +tags: [Retrospective, Tetris, [[Architecture|Architecture]], Performance] created: 2026-04-20 --- -# 프로젝트 회고: 고성능 테트리스 아키텍처 ([[P-Reinforce]]) +# 프로젝트 회고: 고성능 테트리스 아키텍처 ([[P-Reinforce|P-Reinforce]]) ## 🌊 프로젝트 아키텍처 요약 본 프로젝트는 **Web Worker**를 활용한 완전한 연산-렌더링 분리를 실현하여, 실시간 게임 환경에서 극강의 부드러움을 확보하는 데 성공했습니다. ### 🧩 컴포넌트별 기술적 역할 - **Game Engine**: 물리 계산 및 상태 전이 (`public/gameWorker.js`). -- **[[State]] Manager**: UI의 유일한 진실 공급원 (`src/App.js`). +- **[[State|State]] Manager**: UI의 유일한 진실 공급원 (`src/App.js`). - **Renderer**: Props 기반의 순수 매핑 렌더러 (`src/components/GameBoard.jsx`). -## ⚠️ 핵심 교훈 ([[Lessons Learned]]) +## ⚠️ 핵심 교훈 ([[Lessons Learned|Lessons Learned]]) > [!IMPORTANT] > **"논리가 완벽해도 실행 환경이 무너지면 아무 의미가 없다."** > 아키텍처 설계만큼이나 '파일 무결성 검증'과 '환경 재설정 루틴'이 개발 생산성에 지대한 영향을 미친다는 것을 확인했습니다. @@ -26,5 +26,5 @@ created: 2026-04-20 - [x] 체계적인 디버깅 프로토콜 수립. ## 🔗 연결된 지식 -- [[System_Debugging_Protocol]] +- [[System_Debugging_Protocol|System_Debugging_Protocol]] - Project_Architecture_Guidelines diff --git a/10_Wiki/Topics/04_Governance_Reliability/AI-Generated Code Assurance (AI 생성 코드 검증).md b/10_Wiki/Topics/04_Governance_Reliability/AI-Generated Code Assurance (AI 생성 코드 검증).md index 1319e5f5..de9e2a09 100644 --- a/10_Wiki/Topics/04_Governance_Reliability/AI-Generated Code Assurance (AI 생성 코드 검증).md +++ b/10_Wiki/Topics/04_Governance_Reliability/AI-Generated Code Assurance (AI 생성 코드 검증).md @@ -1,45 +1,41 @@ -# [[AI-Generated Code Assurance (AI 생성 코드 검토 및 보안)]] +# AI-Generated Code Assurance (AI 생성 코드 검토 및 보안 ## 📌 Brief Summary -AI 생성 코드는 개발 생산성을 극적으로 향상시키지만, 인간 작성 코드보다 보안 취약점(XSS, 인젝션 등) 발생률이 높고 '환각(Hallucination)'으로 인한 가짜 API 호출 위험을 내포합니다. 연구에 따르면 AI가 작성한 풀 리퀘스트(PR)는 인간보다 1.7배 더 많은 문제와 높은 보안 취약점을 포함하는 경향이 있습니다. 따라서 AI 생성 코드는 완성본이 아닌 '초안'으로 취급되어야 하며, 정적 분석(SAST), 소프트웨어 구성 분석(SCA) 등 자동화 도구와 인간 리뷰어의 비판적 검토가 결합된 엄격한 품질 게이트(Quality Gate) 적용이 필수적입니다. +AI 생성 코드는 개발 생산성을 극적으로 향상시키지만, 인간 작성 코드보다 보안 취약점(XSS, 인젝션 등) 발생률이 높고 '환각(Hallucination)'으로 인한 가짜 API 호출 위험을 내포합니다 [1]. 연구에 따르면 AI가 작성한 풀 리퀘스트(PR)는 인간보다 1.7배 더 많은 보안 취약점을 포함하는 경향이 있습니다 [7, 8]. 따라서 AI 생성 코드는 완성본이 아닌 '초안'으로 취급되어야 하며, 정적 분석(SAST), 소프트웨어 구성 분석(SCA) 등 자동화 도구와 인간 리뷰어의 비판적 검토가 결합된 엄격한 품질 게이트(Quality Gate) 적용이 필수적입니다. ## 📖 Core Content -* **증가하는 보안 위협과 취약점 발생률:** AI 생성 코드는 XSS(교차 사이트 스크립팅) 취약점 도입 확률이 2.74배, 불안전한 객체 참조 포함 확률이 1.91배 높습니다 [1, 7]. 입력값 검증 누락, 데이터베이스 자격 증명 및 API 키 하드코딩이 빈번하게 발생하며, 이는 실제 데이터 유출 및 커맨드 인젝션 사고로 이어지기도 합니다 [8, 10]. -* **AI 특화 위험 (환각 및 슬롭스쿼팅):** AI 모델은 존재하지 않는 API, 라이브러리, 패키지를 실제인 것처럼 지어내는 '환각(Hallucination)' 현상을 보입니다 [2, 11]. 공격자들은 AI가 자주 지어내는 패키지 이름을 노려 악성 코드를 배포하는 '슬롭스쿼팅(Slopsquatting)' 또는 '타이포스쿼팅' 공격을 시도할 수 있습니다 [1, 9]. -* **비즈니스 맥락 및 엣지 케이스 무시:** AI는 주로 정상 작동 시나리오인 '해피 패스(Happy path)'에 집중하여, Null 값, 빈 배열, 유효하지 않은 입력 등 중요한 엣지 케이스 처리를 누락하는 경향이 있습니다 [3, 12]. 또한, 비즈니스 맥락이나 시스템 아키텍처 의도를 파악하지 못해 루프 내 순차적 I/O 수행 등 성능 병목을 유발하기도 합니다 [13, 14]. -* **품질 저하 및 라이선스 위반:** AI 코드는 불필요하게 장황하거나 DRY(Don't Repeat Yourself) 원칙을 위반하는 경우가 많습니다 [15, 16]. 특히 오픈소스 코드를 그대로 복제하여 AGPL-3.0 코드를 MIT 프로젝트에 삽입하는 등의 지적 재산권 및 라이선스 호환성 문제를 일으킬 위험이 큽니다 [17]. -* **검증 프로세스 및 도구 통합:** AI 생성 코드를 감지하고 태깅하여 관리해야 하며, SonarQube, Semgrep, CodeQL, Dependabot 등 SAST/SCA 도구를 CI/CD 파이프라인에 통합하여 최소 80% 이상의 테스트 커버리지 조건을 강제해야 합니다 [4, 15, 18]. +* **증가하는 보안 위협과 취약점 발생률:** AI 생성 코드는 XSS(교차 사이트 스크립팅) 취약점 도입 확률이 2.74배 높으며, 하드코딩된 자격 증명이나 입력값 검증 누락이 빈번합니다 [1, 7]. +* **AI 특화 위험 (환각 및 슬롭스쿼팅):** AI 모델은 존재하지 않는 패키지를 제안하는 '환각(Hallucination)' 현상을 보이며, 공격자들은 이를 악용해 악성 코드를 배포하는 '슬롭스쿼팅(Slopsquatting)' 공격을 시도합니다 [2, 9]. +* **비즈니스 맥락 및 엣지 케이스 무시:** AI는 주로 '해피 패스(Happy path)' 시나리오에 집중하여, Null 값 처리나 예외 상황 등 중요한 엣지 케이스를 누락하는 경향이 있습니다 [3, 12]. +* **품질 저하 및 라이선스 위반:** 불필요하게 장황한 코드(Slop)를 양산하거나, AGPL-3.0 등 라이선스가 엄격한 오픈소스 코드를 무단 복제하여 지적 재산권 문제를 일으킬 수 있습니다 [17]. +* **검증 프로세스 통합:** SonarQube, Semgrep, CodeQL 등 SAST/SCA 도구를 CI/CD 파이프라인에 통합하여 최소 80% 이상의 테스트 커버리지를 강제하고, 모든 AI 생성 코드에 태깅을 수행합니다 [15, 18]. ## ⚖️ Trade-offs & Caveats -* **개발 속도(생산성) vs. 기술 부채 및 보안 위험:** AI 코딩 어시스턴트를 통해 마이그레이션 기간을 수개월에서 수주로 단축하는 압도적인 생산성 향상을 얻을 수 있으나, 동시에 예측 가능한 보안 약점을 시스템에 도입합니다 [19, 20]. 이를 상쇄하기 위해 자동화된 리뷰 파이프라인 및 보안 검증 리소스 투자가 트레이드오프로 요구됩니다. -* **AI 자동화 리뷰 vs. 인간의 비즈니스 맥락 이해:** AI 리뷰 도구는 빠른 피드백을 제공하지만 아키텍처적 트레이드오프를 완벽히 이해하지 못합니다 [13, 22]. AI 피드백을 무비판적으로 수용할 경우 오히려 잘못된 수정이 적용될 수 있으므로, 최종 검증은 항상 비즈니스 의도를 파악하고 있는 인간(시니어 리뷰어)이 수행해야 합니다. +* **속도 vs 안전성:** AI 코딩 어시스턴트는 마이그레이션 기간을 획기적으로 단축하지만, 예측 가능한 보안 약점을 시스템에 도입합니다. 이를 위해 자동화된 보안 검증 리소스 투자가 트레이드오프로 요구됩니다 [19]. +* **자동화의 사각지대:** AI 기반 리뷰 도구는 30~60%의 오탐률을 보이며 실제 취약점의 약 22%를 놓치는 근본적인 한계가 있습니다 [Augment Code 벤치마크]. 아키텍처 설계와 비즈니스 로직의 무결성 판단에는 여전히 인간의 수동 검토가 필수 불가결합니다. +* **리뷰 피로도(Review Fatigue):** AI가 양산하는 대량의 코드(Slop)는 리뷰어의 인지 부하를 높여 형식적인 승인(Rubber-stamping)을 유도할 위험이 있습니다. ## 🔗 Knowledge Connections ### Related Concepts -* **[[SAST (정적 애플리케이션 보안 테스트)]]**: AI 코드에서 하드코딩된 시크릿, 인젝션 결함 등을 코드가 실행되기 전 소스 수준에서 자동 식별하는 핵심 기술입니다. -* **[[SCA (소프트웨어 구성 분석)]]**: AI가 제안하는 의존성 패키지의 실존 여부, 취약점, 라이선스 호환성을 검증하여 환각 및 슬롭스쿼팅 공격을 방어합니다. -* **[[Slopsquatting (Typosquatting)]]**: AI 환각을 이용한 구체적인 공급망 공격 기법으로, AI 코드를 수동으로 검증해야 하는 강력한 이유를 제공합니다. -* **[[Shift-Left Security]]**: AI가 양산하는 대량의 결함을 배포 전(PR 단계 이전) 조기에 차단하여 수정 비용을 낮추는 전략적 접근입니다. +* **[[Static Analysis & Linting (정적 분석 및 린팅)|Static Analysis & Linting]]**: AI 코드의 구문적 오류와 보안 결함을 자동 식별하는 1차 방어선입니다. +* **[[Software Security Standards & Vulnerabilities (소프트웨어 보안 표준 및 취약점)|Software Security Standards & Vulnerabilities]]**: AI가 자주 위반하는 OWASP Top 10 등 보안 표준에 대한 이해가 필요합니다. +* **Shift-Left Security**: AI 대량 생산 코드를 배포 전 PR 단계에서 조기에 차단하는 전략입니다. +* **Software Supply Chain Security**: AI 환각으로 인한 악성 패키지 도입을 방어하는 전체적인 공급망 보안 전략입니다. ### Deeper Research Questions -* AI의 '의존성 환각'을 CI/CD 단계에서 100% 차단하기 위한 실시간 패키지 레지스트리 교차 검증 아키텍처는 어떻게 설계해야 하는가? -* 외부 AI 코드 리뷰 도구 도입 시 소스 코드 노출에 따른 데이터 주권(Data Sovereignty) 문제를 해결하기 위한 Self-hosted LLM 활용 방안은 무엇인가? -* '바이브 코딩' 환경에서 인간 리뷰어의 인지적 과부하(Review Fatigue)를 방지하면서도 시스템의 아키텍처 무결성을 유지하는 '계층화된 리뷰(Tiered Review)' 모델은 무엇인가? -* AI가 생성한 단위 테스트 자체가 내포할 수 있는 논리적 결함(False Positive)을 교차 검증하기 위한 자동화된 Mutation Testing 도입의 실익은 무엇인가? -* AI 생성 코드의 라이선스 위반 여부를 소스 코드 지문 분석(Code Fingerprinting)을 통해 실시간 감지하는 효율적인 프로세스는 무엇인가? +* AI의 '의존성 환각'을 CI/CD 단계에서 실시간으로 차단하기 위한 패키지 레지스트리 교차 검증 아키텍처는 무엇인가? +* Self-hosted LLM을 활용하여 소스 코드 노출 없이 AI 리뷰를 수행할 때의 성능과 비용 효율성은 어떠한가? +* AI 생성 코드의 라이선스 위반 여부를 실시간으로 감지하는 소스 코드 지문 분석(Fingerprinting) 기술의 정확도는? ### Practical Application Contexts -* **Implementation:** AI가 생성한 코드를 복사-붙여넣기 전, OWASP Top 10 기준에 맞춰 입력값을 검증하고 파라미터화된 쿼리 사용 여부를 직접 수정해야 합니다. -* **System Design:** AI 제안 로직이 기존 아키텍처 결정 사항(ADR)과 충돌하지 않는지 확인하고, 루프 내 I/O 발생 등 성능 안티 패턴을 집중 리뷰합니다. -* **Operation / Maintenance:** CI/CD에 보안 스캐너를 통합하여 정책 위반 코드를 자동 차단하고, 커밋 메시지에 AI 사용 여부를 태깅하여 향후 감사를 대비합니다. -* **Learning Path:** 주니어 개발자가 AI 코드를 그대로 수용하지 않도록 "이 코드가 놓친 엣지 케이스는 무엇인가?"를 묻는 비판적 사고 훈련 멘토링에 활용합니다. -* **My Project Relevance:** PR 템플릿에 "AI-Generated Code Verification" 체크리스트(의존성 확인, 시크릿 검사, 라이선스 체크 등)를 추가하고 품질 게이트를 설정합니다. +* **Implementation:** AI 코드를 복사하기 전 파라미터화된 쿼리 사용 여부를 직접 검증합니다. +* **System Design:** AI 제안 로직이 기존 아키텍처 결정(ADR)과 충돌하지 않는지 확인합니다. +* **My Project Relevance:** PR 템플릿에 "AI 생성 코드 체크리스트"를 추가하고 보안 스캔 통과를 강제합니다. ### Adjacent Topics -* **[[Vibe Coding]]**: 인간이 논리 작성보다 의도와 맥락에 집중하는 코딩 방식으로, 리뷰어가 결과물의 '의도 일치성'을 판단하는 역량이 중요해집니다. -* **[[Technical Debt Management]]**: AI가 양산하는 '작동은 하지만 유지보수성이 낮은 코드'가 쌓이는 현상을 측정하고 관리하는 전략으로 확장됩니다. -* **[[Software Supply Chain Security]]**: AI가 도입하는 외부 컴포넌트의 무결성을 점검하고 SBOM을 통해 관리하는 전체적인 방어 전략입니다. +* **Technical Debt Management**: AI가 양산하는 '작동하지만 유지보수성 낮은 코드' 관리 전략입니다. +* **Vibe Coding**: 인간이 논리보다 의도에 집중하는 환경에서의 리뷰어 역량 변화를 탐구합니다. --- *Last updated: 2026-05-02* diff --git a/10_Wiki/Topics/04_Governance_Reliability/Accessibility_Inclusivity.md b/10_Wiki/Topics/04_Governance_Reliability/Accessibility_Inclusivity.md index f251ec77..7aaaa770 100644 --- a/10_Wiki/Topics/04_Governance_Reliability/Accessibility_Inclusivity.md +++ b/10_Wiki/Topics/04_Governance_Reliability/Accessibility_Inclusivity.md @@ -1,11 +1,11 @@ --- title: 웹 접근성 및 포용적 설계 (a11y) -category: Software [[Architecture]] -tags: [[[Accessibility]], a11y, Semantic HTML, Inclusivity] +category: Software [[Architecture|Architecture]] +tags: [[Accessibility|[Accessibility]], a11y, Semantic HTML, Inclusivity] created: 2026-04-20 --- -# [[Accessibility_Inclusivity]] (포용적 설계와 접근성) +# [[Accessibility_Inclusivity|Accessibility_Inclusivity]] (포용적 설계와 접근성) ## 📌 한 줄 통찰 (The Karpathy Summary) > 웹은 '모두'를 위한 공간이어야 한다. 신체적 제약이 시스템 이용의 제약이 되지 않게 하는 것은 '매너'가 아니라 전문 개발자의 '책임'이다. @@ -13,7 +13,7 @@ created: 2026-04-20 ## 📖 구조화된 지식 (Synthesized Content) - **Semantic HTML (의미론적 태그)**: - `
`로만 도배하지 마라. `
`, `
`, `
`, `