How to Write Clean Code That Will Make You a Developer People Want to Work With

📝 Lecture Introduction

Just look at one page on GitHub
It depends on whether I want to work with you or not.

Do you think that's an exaggeration? No, it's not. Just one page on GitHub can tell you a lot about the author's good and bad coding style . Especially when it's written by someone who has no idea what clean and collaborative code is.


First impressions are the strongest impressions.
You should definitely learn how to write clean code in advance, as you can tell good and bad things just by looking at one GitHub page.

Why we need clean code writing techniques

“Any idiot can write code that a computer understands.
“Good programmers write code that people can understand.”

This is what Martin Fowler, author of [Refactoring], said. Good code should be easy for others to read and understand .

As job seekers and prospective/new developers, you probably have little experience maintaining code written by others . Most of your experience is probably in team projects for coding test preparation, contests, or job portfolios. These projects usually have the main purpose of implementing service functions, so the program just needs to work.

“But the reality is different.”

In practice, there are countless cases where you have to understand and modify code written by others. There are also many cases where you have to communicate based on the code of your colleagues. Even your own code is difficult to understand after a few months, so is it easy to collaborate while understanding code written by others? Absolutely not.

✏️ What you will learn in this course

Good for collaboration You will learn how to write clean code and anti-patterns to avoid when writing code.

We have prepared the lectures so that you can easily watch them without the burden of learning, so please read them comfortably as a reference whenever you think of them.

👨‍💻 Instructor Introduction

Hello. I am a junior developer currently working at a large corporation.
I have always been interested in and thought a lot about topics such as object-oriented, software engineering, clean code, and refactoring.
My concerns so far and the knowledge I have gained through development in the field
I would like to share with prospective/new developers who are following the path I have walked .

📖 Course Features

It contains a selection of clean code writing practices that will make you a developer people want to work with.

This course is a lecture in the form of a board lecture, providing reading materials.
You can read the lecture materials directly from the Inflearn lecture screen.
( No separate videos are provided other than the lecture text. Please make sure to check this before registering for the course.)

🙋🏻‍♂️ Expected Questions Q&A

“Are there any development languages I should know in advance to take the course?”
• Although there are some parts in the lecture that use Java as an example, you can take this lecture regardless of the language you use. Of course, the more object-oriented the language, such as Java, Python, Go, or Kotlin, the better.

“I don’t know anything about [object-oriented paradigm] or [design patterns]. Can I still take this course? ”
• Yes, you can. This course does not cover any difficult content at all. This course was created assuming that the target audience is someone who knows a little bit about object-oriented theory or design patterns, but you can still take the course without any difficulty.

“ I’ve already taken [Clean Code] and [Refactoring]. Do I need to take this course? ”
• The students I recommend the most are those who are planning to read [Clean Code] and [Refactoring]. If you take this course before reading [Clean Code] and [Refactoring], it will be a great help in understanding the contents of the above books. On the other hand, since this course covers a lot of the contents covered in the above books, those who have already read them may get less. However, the course also includes other detailed and various tips that are not covered in the above books, so those who want to take the course are always welcome.

“ Are there any special features unique to this course? ”
• There is a saying called 'The curse of knowledge' . It refers to the problem that occurs when you mistakenly believe that others have enough background knowledge to fully understand what you are trying to say when conveying information to others. As a junior developer who knows the minds of job seekers and prospective/new developers better than anyone else, I have included in the lectures content that may make you think, "Do I really need to include this in the lecture?"

“ Can I write good code right away after taking this course? ”
• I think there will definitely be a difference before and after taking this course. However, in order to embody the theory, it is good to practice in parallel. I strongly recommend that you refactor the code you have already written based on the various tips provided in this course.

📣 Additional Information
• We will respond to any questions regarding the lectures as quickly as possible after every weekday evening.
• This lecture is in the form of a lecture (text reading material) , and no separate video is provided. Please make sure to check this before registering for the course, as it is difficult to get a refund for the lecture if the refund policy is exceeded.