You will learn how to write clean code, which is essential for collaboration.
Refactoring Tip
Tips for writing clean code for collaboration
Other development-related tips that job seekers, prospective/new developers should know
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.
“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.
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.
If the code is a mess, which is already difficult, then your fellow developers will be very confused.
I believe that writing clean code is as important as problem solving skills and basic computer science knowledge.
Good for collaboration You will learn how to write clean code and anti-patterns to avoid when writing code.
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 .
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.)
“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.
Who is this course right for?
Developer Job Seeker
Pre/New Developer
Those who are afraid of code review
If you are curious about how to write good code for collaboration
Developers who haven't read [Clean Code] or [Refactoring] yet
I have read [Clean Code] and [Refactoring], but I am curious about more diverse and detailed tips for prospective/new developers.
Need to know before starting?
Someone who has learned object-oriented languages such as Java, Python, Go, and Kotlin
Some experience with object-oriented and design pattern learning
757
Learners
68
Reviews
19
Answers
4.4
Rating
1
Course
안녕하세요.
저는 카카오에서 백엔드 개발자로 일하고 있는 클린 코더입니다.
평소 객체지향, 소프트웨어 공학, 클린코드, 리팩토링 같은 주제에 많은 관심을 갖고 고민해왔습니다. 이런 저의 고민과 실무에서 개발하며 경험한 지식을 제가 걸어왔던 길을 걷고 계시는 취업 준비생, 예비/신입 개발자 여러분과 공유하려고 합니다.
저의 지식이 여러분에게 작게나마 도움이 되길 바랍니다. :D
All
23 lectures
All
68 reviews
4.4
68 reviews
Reviews 7
∙
Average Rating 5.0
5
I really want to implement this theory into my project and make it my own.
I support you, Gungkwon :) Write code based on the lecture content while being conscious of it. It may be slow and you may feel impatient at first, but if you keep applying it, you will complete a clean and easy-to-understand code that anyone can see. If you are not familiar with it yet, don't try to write it perfectly from the beginning, but it is also good to write and modify the code step by step. (There is no perfect code anyway. When you look at it next time, you will wonder why I wrote it like this.) If you are going to modify the source code of an existing project, First, change the variable names to meaningful ones (This is especially recommended when the code is so messy that you can't even tell where to start and how to change it.) If you changed the variable names, remove meaningless value assignments or (useless) temporary variables. If you take these small modification steps that seem meaningless at the moment, you will find yourself adding more parts to modify one by one. If you are not satisfied with the project code even after modifying it step by step and it is different from what is explained in the lecture, and you no longer have a sense of what to do, it may be due to the limitations of the design. In this case, since there are limitations to modifying the code level, you need to modify it in larger units at the component level. Here is a tip: Do not start without thinking, (The more complex the source code is), divide the entire source code into several large steps (don't worry about the details) and start. You can also draw a picture. Thank you for the good review :):)
Reviews 9
∙
Average Rating 5.0
5
I am a student majoring in computer engineering. It was great to learn the basic framework of clean code for the first time. If I apply it little by little and practice it and study it as I go, I think I can become a better developer! It is difficult to refer to the table of contents when I look at it again, so I think it would be good if you made the table of contents a little more detailed and easy to refer to again!
Thank you for the review. I'm so glad it helped you :) I'll think about how to change the table of contents. I'll try to change it in October. Have a nice Chuseok holiday ;)
Reviews 1
∙
Average Rating 5.0
5
I am currently working as a front-end engineer :) When I first joined the company, there were many parts where it was difficult to ask questions or get advice because there was no mentor. However, after listening to this lecture, I was able to write good-looking code and clearly understand why it should be done that way. As mentioned in the introduction, it is not a lecture that cannot be understood even if you do not know the Java language, and it was easy to read and understand because it easily explained the core contents covered in the Clean Code book. I highly recommend it to those who are about to join the company or want to write good-looking code!
Thank you so much for your help. :) Have a Merry Christmas and a Merry Holiday And thank you for the great review
Reviews 10
∙
Average Rating 4.9
5
There was a lot of good content than I thought, so it was very helpful.
Thank you so much for the great review Hyunho I'm honored that it was helpful Hyunho's review seems to be a great help Have a nice holiday and have a great day and a great tomorrow :)
Reviews 7
∙
Average Rating 4.6
5
As a junior developer, I was wondering what clean code is, and after watching this lecture, I got a little bit of an outline. And there were some things that were completely opposite to what I thought, so I think I made a good decision to take the course. Thank you for the great lecture :)
Minjeong, thank you so much for your kind words. (You're the one who reported the typo earlier, right?) You must already be an excellent developer, so I'm honored that I could be of some help. I'm rooting for you as a fellow junior developer :) Be careful of Corona, have a good holiday, and I hope you have a rewarding and wonderful day every day. Thank you so much for your kind review.
Limited time deal ends in 7 days
$10,780.00
30%
$12.10
Explore other courses in the same field!
