엔지니어링 문화
Protecting Attention in a Busy Team
A calm note on treating attention as a shared team resource, not an infinite personal budget that people can recover alone.
글
엔지니어링 문화
소프트웨어 구축의 인간적 측면 — 리뷰, 피드백, 멘토십, 그리고 사람을 성장시키는 팀.
엔지니어링 문화에 관한 실용적이고 사람 중심의 글: 코드와 사람을 모두 더 낫게 만드는 코드 리뷰 진행 방법, 피드백을 잘 주고 받는 방법, 리뷰어들이 좋아하는 pull request 작성법, 엔지니어를 시니어로 멘토링하는 방법, 그리고 친절하고 높은 신뢰의 팀을 구축하는 방법. 두 명의 스타트업부터 천 명 규모의 조직까지 적용할 수 있는 실제 스크립트, 예제, 교훈.
엔지니어링 문화
Noticing Friction Before It Becomes Blame
A calm note on treating repeated team friction as useful signal before it hardens into personal blame.
엔지니어링 문화
Making Space for the Quiet Reviewer
A calm note on helping quieter teammates contribute thoughtful review feedback without forcing every useful signal into the loudest channel.
엔지니어링 문화
What Calm Ownership Looks Like in Practice
A grounded note on ownership as clear follow-through, explicit handoffs, and steady accountability without drama.
엔지니어링 문화
The Quiet Skill of Asking for Help Early
A calm note on why asking for help early is not weakness, but one of the small habits that keeps work honest and teams healthy.
엔지니어링 문화
Why Good Teams Make Risk Visible Early
A calm note on why healthy teams surface risk early: not to create fear, but to give the work more room to adjust.
엔지니어링 문화
The Culture Hidden in Small Reviews
A calm note on how engineering culture shows up in small reviews: the phrasing, patience, and care teams bring to ordinary feedback.
엔지니어링 문화
How Trust Grows in Ordinary Follow-Through
A calm note on how engineering trust grows through ordinary follow-through: small promises kept, visible updates, and repairs when reality changes.
엔지니어링 문화
The Quiet Discipline of Saying Not Yet
A calm note on why healthy engineering teams sometimes say not yet: to protect quality, trust, and the people who will operate the release later.
엔지니어링 문화
The Reviewer as a Future Reader
A reflective note on code review culture: how treating the reviewer as a future reader can make pull requests clearer, kinder, and more useful for the people who will maintain the change later.
엔지니어링 문화
When Silence in a Team Becomes a Signal
A calm look at team silence: how quiet rooms, missing replies, and low participation can reveal unclear ownership, unsafe disagreement, fatigue, or hidden context.
엔지니어링 문화
The Quiet Skill of Asking for Help
A calm look at asking for help in engineering teams: how to make context visible, protect dignity, and turn stuck moments into shared learning instead of silent pressure.
엔지니어링 문화
A Calm Script for Difficult Feedback
A practical guide to difficult feedback in engineering teams: how to prepare the facts, keep dignity in the room, name behavior clearly, and turn a tense conversation into a fair next step.
엔지니어링 문화
Fostering Innovation in Teams
A grounded reflection on fostering innovation in engineering teams: how psychological safety, slack, user context, small experiments, technical quality, and honest prioritization help ideas become useful change.
엔지니어링 문화
Navigating Office Politics
A calm look at office politics in engineering teams: how to understand incentives, build trust, communicate context, disagree cleanly, and stay principled without becoming naive.
엔지니어링 문화
The Difference Between Mentorship and Sponsorship
A calm explanation of mentorship and sponsorship in engineering careers: how advice, feedback, advocacy, visibility, trust, and opportunity work together without turning growth into politics.
엔지니어링 문화
Onboarding That Actually Helps New Teammates
A calm look at engineering onboarding that helps people become useful without feeling lost: context, small early wins, clear ownership, buddy support, documentation, feedback loops, and patient team habits.
엔지니어링 문화
Async Communication for Remote Teams
A calm guide to async communication for remote teams: writing enough context, recording decisions, setting response expectations, improving handoffs, building trust, and protecting people from always-on pressure.
엔지니어링 문화
Handling Toxic Rockstars
A calm look at high-output behavior that damages trust: why teams reward it, how feedback loops break, and how leaders can set boundaries while still offering a real repair path.
엔지니어링 문화
Hiring for Potential vs. Experience
A calm reflection on balancing experience and potential in engineering hiring. The article focuses on evidence, learning pace, team needs, and the quiet conditions that help a person grow after they join.
엔지니어링 문화
From Software Engineer to Technical Manager: The Counterintuitive Things You Learn
Moving from Software Engineer to Technical Manager isn’t a bigger version of the same job — it’s a quiet rewrite of the very habits that made you good at the last one. Step back from the IDE to see architecture, people, and process, and three surprising truths come into focus: code is an asset and a liability at once, your value shifts from addition to multiplication, and delegation is simple to say but genuinely hard to let go of. A practical, honest reflection for senior engineers eyeing the lead role — and for new managers still reaching for the keyboard.
엔지니어링 문화
코드 리뷰의 기술: 사람을 무너뜨리지 않고 코드를 비평하는 방법
코드 리뷰는 팀 문화가 만들어지거나 무너지는 곳입니다. 코드가 더 잘 배포되고 작성자도 더 강해져서 돌아오도록 리뷰하는 실용적인 가이드 — 구체적인 표현, 리뷰어 체크리스트, 그리고 리뷰를 조용히 독성으로 만드는 습관들.
엔지니어링 문화
Kind Engineering: 친절함이 더 나은 엔지니어를 만드는 이유
친절함은 상냥함이 아니고, 약함도 아닙니다. 친절함은 힘을 배가시키는 것입니다 — 더 명확한 피드백, 더 안전한 장애 대응, 더 빠르게 성장하는 팀원들. '엔지니어링에서의 친절함'이 실제로 무엇을 의미하는지, 그리고 코드 리뷰, 장애 대응, 일상 업무에서 어떻게 실천하는지.
엔지니어링 문화
사람들이 실제로 즐겁게 리뷰하는 Pull Request 작성하는 방법
훌륭한 pull request는 리뷰어에게 주는 선물입니다: 작고, 잘 설명되어 있으며, 쉽게 승인할 수 있습니다. 리뷰 가능한 PR의 해부학 — 크기, 제목, 설명, 커밋 위생, 그리고 셀프 리뷰 — 구체적인 before/after 예제와 함께.
엔지니어링 문화
The Pull Request That Reviewers Can Trust
A trusted pull request does more than look tidy. It names the behavior being changed, shows the safer pattern, and gives reviewers enough evidence to approve with real confidence instead of guesswork.
엔지니어링 문화
잘 전달되는 피드백: 엔지니어로서 비평을 주고받는 방법
대부분의 엔지니어들은 피드백을 주는 방법을 배운 적이 없습니다 — 받는 방법도 마찬가지입니다. 구체적이고, 친절하며, 실행 가능한 피드백에 대한 실전 가이드, 그리고 받는 입장에서 열린 자세를 유지하는 방법 — 바로 쓸 수 있는 스크립트와 함께.
엔지니어링 문화
엔지니어 멘토링: 주니어를 시니어로 성장시키는 방법
훌륭한 팀은 채용만으로는 만들어지지 않습니다. 엔지니어링 팀을 이끌어 본 경험에서: 사람들이 빠르게 레벨업하도록 멘토링하는 방법 — 페어링, 가르침으로서의 코드 리뷰, 적절한 크기의 스트레치 과제, 그리고 주니어를 무엇이든 믿고 맡길 수 있는 사람으로 만드는 마인드셋의 전환.
엔지니어링 문화
Over-Managed and Under-Led: Why a Busy Team Can Still Lose Its Way
A team can be carefully managed and still drift. Using John Kotter's distinction between coping with complexity and coping with change, here is how to spot when a team is over-managed and under-led — and small, repeatable ways to bring the direction back.
엔지니어링 문화
Vision Without Craft: Why Leaders Can't Float Above the Work
Warren Bennis said leaders do the right thing while managers do things right. Robert Sutton added the part that matters: to do the right thing, you must understand what it takes to do things right. On the trap of vision detached from craft — and the bounce between big picture and detail.
엔지니어링 문화
Signals or Messages: The Quiet Cost of Vague Communication
Abraham Zaleznik noticed that people uncomfortable with direct engagement communicate in signals rather than messages. On why vague communication feels safe to send and lands as anxiety, how it quietly breeds office politics, and why a clear message is a kindness — especially when it is hard.
엔지니어링 문화
The Discipline of Sitting With a Problem You Can't Yet Solve
Some people restore order the instant disorder appears; others can hold a problem open long enough to understand it. On tolerance for ambiguity as a learnable discipline, the cost of solving before understanding, the Einstellung trap, and why the maturity is in how long you can stay with a hard problem.
엔지니어링 문화
Pull, Don't Push: Why People Follow Meaning, Not Instructions
Bennis and Goldsmith described two ways to move people: push (deadlines, KPIs, position power) and pull (meaning and trust). On the unforgettable sign-language image of reins versus a cradle, why pull is slower but deeper, the honesty it requires, and when to reach for each. The closing piece of the series.
엔지니어링 문화
Why "Culture Fit" is Often a Trap
Culture fit sounds responsible, but it can reward sameness and hide vague concerns. This piece separates real values signals from comfort signals and argues for culture contribution.
엔지니어링 문화
건강한 1-on-1 의 구조
건강한 1-on-1 은 부드러운 status meeting 이 아닙니다. context, 신뢰, feedback, 커리어 방향을 위한 작고 규칙적인 공간입니다.
엔지니어링 문화
Celebrating Failure
A grounded look at what teams should really mean by celebrating failure: not applauding damage, but making honest learning, early signal reporting, repair, and changed systems safer to practice.
엔지니어링 문화
Building Diverse Engineering Teams
A grounded reflection on building diverse engineering teams: moving beyond slogans into hiring, onboarding, meeting design, decision-making, feedback, and the daily habits that let different people contribute fully.
엔지니어링 문화
Managing Up: Communicating with Non-Technical Leadership
A calm guide to managing up with non-technical leadership: translating technical work into risk, options, impact, timing, and decisions without hiding complexity or talking down to people.
엔지니어링 문화
Performance Reviews That Matter
A calm reflection on performance reviews that actually help people grow: using evidence, expectations, calibration, feedback, and follow-through without turning the review into a surprise or a ritual.
엔지니어링 문화
Handling Burnout Before It Happens
A calm look at preventing burnout in engineering teams: early signals, workload visibility, recovery time, sustainable expectations, management responsibility, and the small habits that keep people from disappearing quietly.
엔지니어링 문화
Creating a Blameless Culture
A calm look at blameless engineering culture: how teams can study incidents without blame, separate accountability from punishment, improve systems, and make it safer for people to tell the truth early.
엔지니어링 문화
Giving Constructive Feedback
A calm reflection on constructive feedback: how specific observations, timing, care, accountability, and follow-up help people improve without turning feedback into blame or performance theater.