The voice, pace, and content are good.. But I can't find the slide link..
And it would be good to have the blog link mentioned in the lecture.

It was good to have the opportunity to reflect on past days while looking at the anti-patterns. It would be better if there was a way to know things beforehand that you only realize after they've passed.. In my case, not enjoying work felt like an opportunity to check for such anti-patterns. Usually in this situation, it was time to change companies.. but I couldn't do that..

Time is the most precious thing.. that's something I regret..

sc7258

In the past, I thought, "Isn't it enough to just be good at developing on my own?" but the truth is, you can't do anything alone (of course, some people are good on their own, but that wasn't my story haha). In this knowledge sharing session, we will talk about how all of us can break free from the frame of being a solo battle and grow steadily by building healthy communication and culture with the team, without hurting each other.

We will discuss together why blogging is necessary for a developer's continuous growth and for protecting oneself amidst anxiety, whether the desire to prove oneself at the company works to deplete oneself rather than aid growth, how essential Code Review is for maintaining a team's healthy culture, what detailed guides are needed to establish a healthy Code Review culture, and what are the Anti-Patterns of managers you should absolutely avoid or never emulate when you encounter them.

codercollie

Developing together without getting hurt or hurting others

Hello Shin Sung-chul! This is CoderColly.
- First of all, thank you for leaving feedback that the voice, speed, and content were all good. It was my first lecture, so I was a bit nervous, but your good review gives me great strength to create the next lecture. Thank you very much.
- I have added the slide links for each chapter. It was something I missed, so thank you for letting me know!
- As you mentioned, I've been considering making my technical blog public. However, while preparing the Inflearn lecture, I wanted to keep my work life separate from my appearance on Inflearn, so I'm less inclined to make the blog public for now. But I will continue to think about this going forward. Thank you very much for offering the good suggestion!

커뮤니케이션

커리어고민

과거의 저는, “혼자서 개발만 잘하면 되는 것 아니야?”라고 생각했지만, 사실 혼자서는 아무것도 할 수 없습니다(물론 혼자 잘하는 사람도 있지만 제 이야기는 아니었어요 하핳). 이 지식 공유에서는 우리 모두가 혼자만의 싸움이라는 프레임에서 벗어나, 팀과 함께 서로 상처 주지 않고 건강한 소통과 문화를 만들어 나가며 꾸준히 성장하는 법을 이야기합니다.

개발자가 지속적으로 성장하기 위해서, 그리고 불안함 속에서 자기 자신을 지켜내기 위해 블로그가 왜 필요한지, 회사에서 자기 자신을 증명해내려는 마음은 성장에 도움을 주기 보다 스스로를 고갈시키기 위해 작동하는 것은 아닌지, Code Review가 팀의 건강한 문화를 유지하기 위해 얼마나 필요한지, 그리고 건강한 Code Review 문화를 정착시키기 위해 필요한 세부적인 Guide에는 어떤 것들이 있는지, 만나면 반드시 피해야 하는 혹은 내가 절대로 닮아서는 안되는 Manager들의 Anti-Pattern에는 무엇이 있는지 등에 대해서 함께 이야기해봅니다.

코더콜리

입문

초급

중급이상

Communication

Software Engineering

소프트웨어 공학

상처받지 않고, 상처주지 않으며, 함께 개발하기

Chapter 0: 귀한 Inflearn에 누추한 제가 왔습니다.

Chapter 1: May The Blog Save You: 어쩌면, 블로그가 당신을 구원할지도 모릅니다.

Chapter 2: 회사에서 자기자신을 증명하려는 소중한 마음

Chapter 3: CodeReview를 통해 우리 모두 빠르게 성장하기

Chapter 4: 발전적인(?) CodeReview문화를 정착시키기 위해서 필요한 것

Chapter 5: Test Code는 개발자의 학습을 촉진시킵니다

Chapter 6: Manager의 Anti-Pattern

Chapter -1: Outro

수업자료