직장에서 지속적인 학습 작업을 수행합니다

• The most impactful learning happens in the flow of work—during code reviews, retros, and problem-solving—not in classrooms or LMS platforms.
• Leaders should embed learning into daily routines using the Learn → Question → Answer → Apply cycle.
• To make continuous learning stick, focus on three practices: be intentional, lead by example, and offer multimodal solutions.

If you feel like tech skills have a shorter shelf life than ever, you’re not alone. New frameworks, programming languages, tools, and workflows are constantly reshaping the way developers and technologists work—the way entire organizations work. The skills your teams mastered last year may already feel outdated, especially in the AI arena, where models and applications are evolving with dizzying speed. The need for continuous learning is a given.

But the way organizations approach professional development often doesn’t align with how learning actually happens. Traditional classrooms, online learning modules, and lengthy certification programs have plenty of value to offer, but on their own, they’re not enough. That’s because knowledge decays quickly when it’s not applied: a phenomenon called the forgetting curve. Unless employees use what they’ve learned right away, much of it vanishes.

The most effective learning doesn’t happen in a classroom. It happens during work. A developer encounters a tricky bug. An engineer spots a better pattern in a code review. A team reflects during a sprint retrospective. The question is: How do leaders harness these moments of real-world learning so they become lasting, collective knowledge?

Embedding education directly into daily tasks and workflows makes it part of the natural rhythm of work rather than something separate and siloed. Because learning and application are nearly simultaneous, the forgetting curve flattens out. Teams retain knowledge because they’re putting it into practice straightaway.

For developers, learning in the flow of work might happen:

• During a code review: A junior developer learns a best practice for structuring APIs.
• While troubleshooting a bug: An engineer discovers a new debugging technique and shares it with their peers.
• In a sprint retrospective: The team identifies a recurring pain point and develops a better workflow.

These are valuable learning moments. If they aren’t captured, reinforced, and made accessible to others, their value fades quickly. Over time, organizations lose an enormous amount of institutional knowledge that costs them precious time and energy.

In our most recent episode of Leaders of Code

일의 흐름에서 학습에 대해 생각하는 한 가지 방법은 학습 → 질문 → 답변 → 적용 뼈대:

1. 배우다: 프로그래밍 패턴, 도구 또는 워크 플로와 같은 새로운 정보에 대한 노출.
2. 질문: 호기심이나 문제 중심이 필요한 자연스러운 다음 단계.
3. 답변: 기술 문서, 동료 지식 또는 내부 자원을 통한 솔루션 찾기.
4. 적용하다: 그 지식을 즉시 실천하여 그 지식을 강화합니다.

이주기는 개발자가 자연스럽게 운영하는 방식을 반영합니다. 예를 들어, AI 지원 프로그래밍을 실험하는 개발자는 새로운 라이브러리에 대해 배우고, 기존 시스템과 어떻게 통합되는지에 대한 질문을하고, 문서 또는 동료를 문의 한 다음 답변에 적용 할 수 있습니다. 각 단계는 유지를 심화시키고 교육을보다 내구성있게 만듭니다.

오버플로 스택[–>2025 Developer SurveyLeaders of Code