글

블로그

소프트웨어 아키텍처와 소스 코드 구조에 대한 깊이 있는 글입니다. 입문자도 이해할 수 있으면서, 대규모로 개발하는 팀에도 유용하도록 썼습니다. 다이어그램과 실제 사례를 곁들였고, 두루뭉술한 설명은 없습니다.

주제별로 보기

소스 코드 & 아키텍처

성장과 팀 규모, 변화를 견딜 수 있도록 소스 코드를 구조화하는 방법.

11 개의 글

엔지니어링 문화

소프트웨어 구축의 인간적 측면 — 리뷰, 피드백, 멘토십, 그리고 사람을 성장시키는 팀.

6 개의 글

AI & 미래

AI 이해하기 — 컨텍스트 엔지니어링부터 신뢰할 수 있는 AI 제품 구축까지.

9 개의 글

Perspectives & Field Notes

Personal reflections from work, learning, people, and the quiet moments that shape a career.

1 개의 글

Ways of Working

How software teams actually operate and work together — from Agile and Scrum to how delivery really happens in big corps, startups, and outsourcing.

20 개의 글

최신 글

Cognitive Debt in AI-Assisted Development: When Code Grows Faster Than Understanding

AI coding tools can make a team produce code faster than it can understand, review, debug, and safely operate that code. This article explains cognitive debt, how it differs from technical debt and intent debt, why agentic coding makes it more visible, and the practical controls teams can use: smaller batches, better PR rationale, human-owned invariants, disposable prototypes, and AI used to repay understanding instead of only generating more work.

2026년 6월 17일15분 읽기

Ways of Working

Lean Business Analysis: Start from Value, Not Requirements

A practical introduction to Lean Business Analysis: why BA starts with value, how needs assessment protects teams from solving the wrong problem, and how a business case keeps decisions grounded without turning analysis into ceremony.

2026년 6월 17일13분 읽기

Ways of Working

Lean BA Planning: Stakeholders, Elicitation, and the Questions Behind Requirements

A practical guide to Lean BA planning: stakeholder analysis, predictive versus adaptive BA rhythms, elicitation planning, and the difference between collecting stated requests and uncovering the need behind them.

2026년 6월 17일14분 읽기

Ways of Working

Requirements Modeling: How BA Turns Messy Conversations into Shared Pictures

A calm, practical guide to requirements modeling: scope, process, rule, data, and interface models, with examples of how diagrams and structured descriptions help teams reason together before building.

2026년 6월 17일15분 읽기

Ways of Working

Requirements Quality, Traceability, and Solution Evaluation: Keep the Promise After Sign-off

A practical reflection on the later half of Business Analysis: requirement quality, prioritization, traceability, change control, UAT, rollout choices, transition, and evaluating whether the delivered solution actually worked.

2026년 6월 17일15분 읽기

Ways of Working

Software Measurement and Estimation: Fewer Gut Feelings, Better Engineering Decisions

A practical reflection on Software Measurement and Estimation: A Practical Approach by Linda M. Laird and M. Carol Brennan. The article focuses on the ideas engineers can use at work: measure from decisions, estimate as uncertainty instead of promise, track quality before release, and keep dashboards useful instead of decorative.

2026년 6월 17일16분 읽기

Ways of Working

Agile Estimating and Planning: Estimates Are Conversations, Not Promises

A practical reflection from Mike Cohn’s Agile Estimating and Planning on story points, velocity, planning poker, ideal days, and why estimates should expose uncertainty instead of pretending to remove it.

2026년 6월 17일13분 읽기

Ways of Working

Agile Release Planning: Plan with Value, Risk, and Real Feedback

A second reflection from Agile Estimating and Planning, focused on release planning: prioritizing by value and risk, splitting stories into useful slices, using buffers for uncertainty, and communicating plans without pretending the future is fixed.

2026년 6월 17일18분 읽기

Ways of Working

The Design of Everyday Things: Make the Interface Explain Itself

A practical reflection from Don Norman’s The Design of Everyday Things for software and product teams: discoverability, signifiers, mapping, feedback, conceptual models, and why a clear interface should not make users guess what it wants.

2026년 6월 17일12분 읽기