강의

멘토링

커뮤니티

Programming

/

etc. (Programming)

Developing together without getting hurt or hurting others

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.

(5.0) 6 reviews

33 learners

Level Beginner

Course period 12 months

  • codercollie
Communication
Communication
Software Engineering
Software Engineering
Communication
Communication
Software Engineering
Software Engineering

Reviews from Early Learners

Reviews from Early Learners

5.0

5.0

코더콜리

100% enrolled

- I listened to all the videos to check if the lecture was well-made. For people who create something, what they create always seems to have shortcomings, but for some reason, listening to the lecture I made myself, I think the feeling of satisfaction came first rather than a lack or regret. - If you say, "Aren't you praising yourself too much??", I honestly don't have much to say, but at least my lecture seems to please me. It's actually a paid lecture, and I also think, "Isn't it more embarrassing to charge money for a lecture that doesn't even please the creator?" - After listening to the entire lecture, I, as the creator, was also given the opportunity to leave a review. I briefly wondered if it wouldn't be too ridiculous for the creator to give themselves a rating, decide how many stars to give, and write the review themselves, but I boldly gave it ⭐️⭐️⭐️⭐️⭐️. I believe my lecture deserves five stars. - Lecture reviews are only revealed when three or more are written. Excluding myself, there were two other grateful individuals who had already left reviews, and with my review, a total of three were written, so all lecture reviews were switched to public. If the other reviews that were already written hadn't been good, I might have been hesitant to make them public, but thankfully the content of the other reviews was good, which is also why I decided to 'make the lecture reviews public'. - Regardless of whether the quality of the lecture satisfies me as the creator, there may naturally be aspects that others who are taking the lecture find disappointing. Although you may be busy, if you send your feedback on disappointing points to coder.collie.dev@gmail.com, I will incorporate them. - Finally, I sincerely thank you for taking the time to listen to my lecture.

5.0

잘하자

100% enrolled

잘 들었습니다. 주니어에게는 회사와 대화할 수 있는 자기언어를, 조직/프로젝트 관리자에게는 자기반성의 기회를 주는 강의였습니다. 종종 인프런에 들어가 담당 부서에 필요한 강의를 찾는데 이 강의는 제목이 특이해 들었습니다. 그런데 선생님은 제 생각보다 더 특이하신 분이더군요. 성선설을 믿는 공학 박사이면서 구글 오퍼를 거절하고 반도체 회사에 갔고, 그 안에서 관리자의 여러 안티 패턴을 경험했지만 물들지 않기 위해(unlearn하기 위해) 강의를 만든 사람. 보통 안티 패턴을 경험하면 성선설 안 믿습니다. 아무튼 이 모순 덕분에 재미난 강의가 만들어진 것 같습니다. 대학원을 다녀봤거나 타인의 성의없는 말에 하루를 망쳐본 사람이라면 공감할 이야기로 시작해 처음에는 라디오 듣듯 재미나게 들었습니다. 뒤로 갈수록 실무에 적용할 수 있는 이야기가 많이 나와 받아적어야 하더군요. 아무래도 톡식한 개발 문화를 재생산하기 쉬운 스타트업, SI의 CTO, 개발팀장이 모두 들어야 하지 않나 싶었습니다. 특히 코드리뷰의 필요성과 의미가 인상 깊습니다. 한국에서 이렇게 해석하고 이용하는 사람이 있는 걸 처음 봤어요. 제가 있던 곳들을 포함해 많은 곳이 코드리뷰를 하나의 형식, 부차적인 회의, 상급자의 호의 정도로 생각합니다. 그런데 매번 일이 왜 이렇게 답답하게 돌아가지 싶었던 건 서로의 코드를 유기적으로 보지 못했기 때문이었나 싶습니다. 강의에서 언급한 대로 코드리뷰를 했을 때 당장 내일 동료의 업무성과가 달라질 수 있겠다는 생각이 듭니다. 그리고 이 강의를 들을 주니어 친구들이 부럽습니다. 주니어는 본인에게 필요한 것을 파악하는 데도 오래 걸리지만, 필요한 걸 알았다고 해도 어떤 언어로 회사에 요구해야 하는지를 알지 못합니다. 강사 선생님의 언어를 빌려 팀에 원하는 것을 제안해 봐도 좋겠네요. 본인이 상대하는 관리자가 안티 패턴을 보이는지 아닌지 빠르게 판단하세요. 레드 플래그가 떴는지를 인지하는 것도 사회에서 오래 버티기 위해 필요한 기술입니다. 이 강의를 볼 주니어들이 톡식한 개발문화에 덜 다치고 오래 코딩하길 바랍니다. 여러 모로 유익한 강의였습니다. 고맙습니다.

5.0

초보자

100% enrolled

It was a good lecture.

What you will gain after the course

  • Why a blog is absolutely necessary for developers for sustainable development and growth!

  • How to grow without burning out, escaping the 'self-validation' trap!

  • Self-protection methods naturally acquired while running a blog!

  • Why a Healthy Code Review Culture is Needed for the Team and Practical Guides to Establish It!

  • Manager Anti-Patterns You Must Avoid Meeting And Never Become!

As I develop, my heart keeps getting hurt. How can I develop together without getting hurt? 🤔

  • In the past, I thought, "Development is something you do alone, and I just have to do my job well, right?" (hahahahahahaha). However, in modern development, you can't do anything alone (of course, you can do anything with ChatGPT!).


  • Not alone, but with others, "This Very Fun Development" is more enjoyable and sustainable, and we introduce strong ways to protect yourself and others at the same time!

💡 In this knowledge sharing, we talk about:

  • The fact that a blog can be more than just a portfolio; it can also be a haven for developers!
    (At least I survived thanks to blogging…)

  • The strange mechanism of trying to prove to your company that you are working hard but instead end up burning out!
    (And the story that things got better after stopping is a shocking true story)

  • If you just do a good job of code reviewing, your team will fight a lot less. It's true.
    (It also grows quickly. Killing two birds with one stone!)

  • A practical guide to code review that will help you stop saying, “I’m not good at commenting…”!
    (How to make everyone grow while no one gets hurt)

  • The realization that test code isn't a pain, it's actually the best onboarding document ever!
    (“Why is this code written like this?” disappears)

  • Let's take a look at the characteristics of bad managers that we unknowingly become like and swear at, and avoid them.
    (If you don't know, you'll be punished)

I recommend this to these people

Blogging, Developers Who Don't Know How or Why to Start

A developer who runs a blog and wants to grow sustainably and steadily

Team members or leaders who want to create a healthy code review culture

Developers who hope that code review becomes a tool for communication and growth rather than a simple 'inspection'

Senior developers or new managers who are overwhelmed by their first management job

Developers who want to know common mistakes and bad habits (anti-patterns) and grow into good leaders.

After taking the class, this is what happens 🎉 !

  • Through blogging, you can systematically record your narrative as a developer and objectively look at your own value from your own perspective rather than from the perspective of others. (It becomes the most solid evidence for yourself.)

  • Instead of wasting energy on 'self-proving', you learn how to grow with yourself and your team (you learn that you don't have to struggle alone anymore).

  • Understand a healthy code review culture and learn to give and receive positive and productive feedback with your team members (reducing unnecessary conflicts and naturally improving team atmosphere).

  • By learning effective code review guidelines, you will gain confidence and expertise in the review process (and be able to communicate clearly without unnecessary emotional drain).

  • By understanding the importance and role of test code, you can write code that is of great help in onboarding and maintaining new developers within your team. (You will become a developer who naturally writes test code.)

  • Avoid common manager mistakes and errors that you may not even realize you are making, and become a leader your team can trust (the first step to creating a healthy organizational culture).

How did you come to create this lecture 💭 ?

  • 2018 ~: While I was studying for my degree, both the professor and I ignored me, so I was worried that I was really useless. 🤔 Then I created a personal technology blog, and it went better than I thought (over 1 million cumulative views), so I recovered my self-esteem and even graduated 🎓 . Blogging saved me 🙏 .

  • 2020~: I am currently working hard as a developer at a semiconductor company. It is also quite interesting to work as a software developer in a place where the company's main product is not software. 🔍

  • 2023 ~: During the project, I was having a hard time because of the Manager, so I started thinking about the Manager's Anti-Pattern, and I'm thinking about how to become a good Manager quite fiercely 🔥 . The villains in my life enrich my life, but I don't welcome the villains. Please stop coming. Please 🙏 .


Things to note before taking the class

Practice environment

  • You don't need anything. I'll explain everything verbally, so just turn it on like a radio and listen. A real ASMR lecture, whispering!


Learning Materials

  • Provided via Google Slides link! The material will be updated regularly!

Player Knowledge and Notes

  • This is a Soft Skill course, not a Hard Skill course, so no prior knowledge is required.


Recommended for
these people

Who is this course right for?

  • A junior developer who learned collaboration is important, but whose heart sinks even at a single Slack reply.

  • Senior Developer: Wanted good manager, strangely only gets flak

  • A developer who learned code reviews should be done, but ends up just saying ‘LGTM…’ every time.

  • Developer getting tired from the constant thought 'What more do I have to prove?' despite working hard.

  • A developer who thought about writing a blog dozens of times but gave up after only leaving "Didn't do anything today either" on the first line of their TIL.

  • Developer who, while writing a tech blog, thought 'Who's gonna read this?' and has 17 drafts left.

  • Developer who feels the team atmosphere is good but everyone suddenly gets cold during code reviews

Need to know before starting?

  • It might resonate more if you have experience trying to document yourself, for example, through a tech blog.

  • If you are someone familiar with the mindset and pressure of "having to prove yourself," it might resonate a little more.

  • If you've experienced what code review is and how it's done, it might make more sense.

  • If you've ever experienced communication issues during collaboration (""It's the right thing to say, but why do I feel bad?""), it might resonate a bit more.

Hello
This is

33

Learners

6

Reviews

5.0

Rating

1

Course

Hello! I'm CoderCollie🐶!

Coder Collie, why are you called Coder Collie?🐾

  • I am a developer who endures a four-hour daily round-trip commute with the determination that "I will raise a Border Collie in the future."

    Until I can create courses and finally bring a Border Collie home! I will work even harder🚀 Coder Collie, what has your life been like?🤔 1) Mid-2000s ~ 2010

  • I will work even harder until I can create enough courses to finally bring a Border Collie home!🚀

CoderCollie, what is your story?🤔

1) Mid-2000s – Early 2010s: Programming💻 is fun, but I don't think I can do it

  • I entered a certain engineering college and learned programming (C language) for the first time. At first, I struggled because it was unfamiliar, but the process of creating something by typing away on the keyboard was fun. It suited my aptitude, and my grades were pretty good too.

  • However, the atmosphere at the time was not like today, where developers are treated well. Computer science was always at the bottom of the list of preferred majors. Also, I once interned at a consulting firm during my undergraduate years, and it didn't feel like developers were the ones proactively leading the projects (to put it politely, haha).

  • I enjoyed programming, but I compromised with myself and decided to go to graduate school, thinking it wasn't the right choice.

2) Early 2010s – Late 2010s: It's late, but I need to go back now🔄

  • Immediately after entering graduate school, the academic paradigm began to shift gradually toward Data and AI, and after AlphaGo, it underwent a complete transformation.

  • During the research process, I had constant arguments with my advisor, who failed to adapt to the new paradigm (of course, the professor was wrong and I was right). My research remained stagnant for a long time, and feeling physically and mentally exhausted, I decided to put my degree on hold and spend some time at home.

  • During my time resting at home, I started creating and running a Python-related development blog. About a year after launching it, I began receiving around 2,000 daily visitors. Influenced positively by the blog (it truly saved me), I was fortunate enough to graduate.

    From that point on, I even had about 2,000 visitors a day. Influenced positively by the blog (it truly saved me), I luckily managed to graduate.

3) Early 2020s ~: What decisions should be made in the ChatGPT paradigm?🤖

  • I joined a major domestic semiconductor company and am continuing my career there. I'm physically comfortable and well-fed, but I don't feel mentally fulfilled. Is it because my ego is unnecessarily bloated?

  • Working as a software developer in a place where the final product is not software, I am experiencing various interesting situations. Just as flowers bloom even in the mud, I am experiencing many things that can only be encountered here.

  • I am living in a state of constant inner turmoil amidst a new paradigm—perhaps even greater than those of the past—epitomized by ChatGPT. With predictions of mass layoffs for developers due to ChatGPT, I am stuck in a dilemma: should I commit even harder to my corporate life, or should I pursue life as a solopreneur, given that I can now more rapidly bring the ideas in my head to life thanks to ChatGPT?

  • Anyway, I will do my best.

    Consistency is the one thing I'm truly confident in🔥

email:

coder.collie.dev@gmail.com

Curriculum

All

31 lectures ∙ (2hr 16min)

Published: 
Last updated: 

Reviews

All

6 reviews

5.0

6 reviews

  • codercollie님의 프로필 이미지
    codercollie

    Reviews 1

    Average Rating 5.0

    Edited

    5

    100% enrolled

    - I listened to all the videos to check if the lecture was well-made. For people who create something, what they create always seems to have shortcomings, but for some reason, listening to the lecture I made myself, I think the feeling of satisfaction came first rather than a lack or regret. - If you say, "Aren't you praising yourself too much??", I honestly don't have much to say, but at least my lecture seems to please me. It's actually a paid lecture, and I also think, "Isn't it more embarrassing to charge money for a lecture that doesn't even please the creator?" - After listening to the entire lecture, I, as the creator, was also given the opportunity to leave a review. I briefly wondered if it wouldn't be too ridiculous for the creator to give themselves a rating, decide how many stars to give, and write the review themselves, but I boldly gave it ⭐️⭐️⭐️⭐️⭐️. I believe my lecture deserves five stars. - Lecture reviews are only revealed when three or more are written. Excluding myself, there were two other grateful individuals who had already left reviews, and with my review, a total of three were written, so all lecture reviews were switched to public. If the other reviews that were already written hadn't been good, I might have been hesitant to make them public, but thankfully the content of the other reviews was good, which is also why I decided to 'make the lecture reviews public'. - Regardless of whether the quality of the lecture satisfies me as the creator, there may naturally be aspects that others who are taking the lecture find disappointing. Although you may be busy, if you send your feedback on disappointing points to coder.collie.dev@gmail.com, I will incorporate them. - Finally, I sincerely thank you for taking the time to listen to my lecture.

    • goodworker님의 프로필 이미지
      goodworker

      Reviews 2

      Average Rating 3.5

      Edited

      5

      100% enrolled

      잘 들었습니다. 주니어에게는 회사와 대화할 수 있는 자기언어를, 조직/프로젝트 관리자에게는 자기반성의 기회를 주는 강의였습니다. 종종 인프런에 들어가 담당 부서에 필요한 강의를 찾는데 이 강의는 제목이 특이해 들었습니다. 그런데 선생님은 제 생각보다 더 특이하신 분이더군요. 성선설을 믿는 공학 박사이면서 구글 오퍼를 거절하고 반도체 회사에 갔고, 그 안에서 관리자의 여러 안티 패턴을 경험했지만 물들지 않기 위해(unlearn하기 위해) 강의를 만든 사람. 보통 안티 패턴을 경험하면 성선설 안 믿습니다. 아무튼 이 모순 덕분에 재미난 강의가 만들어진 것 같습니다. 대학원을 다녀봤거나 타인의 성의없는 말에 하루를 망쳐본 사람이라면 공감할 이야기로 시작해 처음에는 라디오 듣듯 재미나게 들었습니다. 뒤로 갈수록 실무에 적용할 수 있는 이야기가 많이 나와 받아적어야 하더군요. 아무래도 톡식한 개발 문화를 재생산하기 쉬운 스타트업, SI의 CTO, 개발팀장이 모두 들어야 하지 않나 싶었습니다. 특히 코드리뷰의 필요성과 의미가 인상 깊습니다. 한국에서 이렇게 해석하고 이용하는 사람이 있는 걸 처음 봤어요. 제가 있던 곳들을 포함해 많은 곳이 코드리뷰를 하나의 형식, 부차적인 회의, 상급자의 호의 정도로 생각합니다. 그런데 매번 일이 왜 이렇게 답답하게 돌아가지 싶었던 건 서로의 코드를 유기적으로 보지 못했기 때문이었나 싶습니다. 강의에서 언급한 대로 코드리뷰를 했을 때 당장 내일 동료의 업무성과가 달라질 수 있겠다는 생각이 듭니다. 그리고 이 강의를 들을 주니어 친구들이 부럽습니다. 주니어는 본인에게 필요한 것을 파악하는 데도 오래 걸리지만, 필요한 걸 알았다고 해도 어떤 언어로 회사에 요구해야 하는지를 알지 못합니다. 강사 선생님의 언어를 빌려 팀에 원하는 것을 제안해 봐도 좋겠네요. 본인이 상대하는 관리자가 안티 패턴을 보이는지 아닌지 빠르게 판단하세요. 레드 플래그가 떴는지를 인지하는 것도 사회에서 오래 버티기 위해 필요한 기술입니다. 이 강의를 볼 주니어들이 톡식한 개발문화에 덜 다치고 오래 코딩하길 바랍니다. 여러 모로 유익한 강의였습니다. 고맙습니다.

      • codercollie
        Instructor

        Hello 잘하자 님, this is 코더콜리! Thank you for writing such a thoughtful lecture review. It might be a cliché expression, but it's very rewarding and heartwarming. Honestly, while preparing the lecture, I was a bit worried because the lecture I prepared wasn't a technical one, but rather closer to a developer's mindset or soft skills, so I'm relieved that it was helpful and also grateful for you leaving a good review. Thanks to you, I feel I can prepare well for the next knowledge sharing session. Sincerely, thank you. P.S. Your ID is also in Korean, and it seems you wrote the comment in Korean too, but it looks like the comment is being automatically translated into English! It was a great comment, so I read it both in English and Korean!

    • miri0502님의 프로필 이미지
      miri0502

      Reviews 14

      Average Rating 5.0

      5

      61% enrolled

      • codercollie
        Instructor

        Hello Hyeseong! Thank you for taking the course and leaving a course rating.

    • idiotist님의 프로필 이미지
      idiotist

      Reviews 44

      Average Rating 5.0

      Edited

      5

      100% enrolled

      It was a good lecture.

      • codercollie
        Instructor

        Hello beginner. Thank you for taking your precious time to listen to the lecture and for leaving a review. I hope it will be of some help, even if small, in your future life. Thank you!

    • qhdrn67님의 프로필 이미지
      qhdrn67

      Reviews 6

      Average Rating 5.0

      5

      32% enrolled

      • codercollie
        Instructor

        Hello Jay! This is CoderColly. - Thank you for your valuable time with the lecture, and for the rating!

    $17.60

    Similar courses

    Explore other courses in the same field!