Simple Design Introduction - On Code Quality

The standards for good code - must they inevitably be 'subjective'?

Are there standards for good code? Clean code? Readable code? Beautiful code? Are the only standards for good code these subjective ones? Do my team leader and I have different code standards? What can I say when reviewing my colleagues' code?

This course presents standards that can more objectively judge code quality.

However, rather than simply presenting those standards, we want to share what questions were asked to derive those standards,
what thought processes were involved, and provide opportunities for each person to think and judge for themselves.
So, we hope to experience together that even if each person goes through different thought processes, they can reach universal standards.

You can view the complete roadmap for the Simple Design series at the following link: https://inf.run/VvwxD

This lecture examines various perspectives on code quality standards, discusses why readable code cannot be a good code quality standard, and presents Kent Beck's Simple Design as an alternative. It also aims to show that while Simple Design can be summarized into two simple principles, adhering to these two principles is more difficult than one might think, but despite the difficulty, it can be conquered step by step.

You might wonder why code quality is necessary in the AI era, but the importance of code quality is actually growing even more in the AI era. Software that relies solely on AI without considering code quality often fails to produce the desired results accurately or creates maintenance problems that are difficult to resolve. Additionally, token costs can be enormous, and the performance is often disappointing compared to those costs. To use AI efficiently and effectively, we need to demand high code quality from AI as well, and for that, we need clearer standards rather than subjective and vague criteria like "readability."

In this course, I hope we can think together about standards that allow us to judge code quality objectively rather than subjectively, and find good criteria.

Let's think together about how to write good code 🤔

>> Fill in the blanks through the lectures!