For the convenience of CodeGym students, we decided to collect lectures and articles on the most important topics in programming. The eighth collection is about how to work with code: the rules for writing high-quality code and the rules for refactoring, writing comments on the code. In the mini-guide, we briefly outline the essence of the articles, and if you follow the link, you can learn more about the topic of interest. Add a collection to your bookmarks and return to it when you need to.
This is a small guide for writing higher level code. The article lists the basic rules and concepts that relate to creating a system, working with interfaces, classes and objects. The structure of the article is formed “from top to bottom”, that is, from the general structure of the appendix to more narrowly focused details.
This article will discuss the correct naming of certain elements. Correct names make the code much easier to read. Also in the article there are examples of comments in the code.
Development tips are never redundant, especially if you are just starting to write code. The article contains recommendations for code analysis that are specific to the Java language.
When monitoring the quality of code, it is important to keep in mind the quality of the comments that accompany that code. This article will introduce you to the topic of commenting and explain why it is worth taking the time to comment on.
Working with code that someone else wrote can lead to some problems. The code may refer to technology that is unfamiliar to you. Perhaps this code needs to be improved. Or you may need to urgently fix a bug found in an old codebase. In this text, the author gives some tips that can make it easier to work with legacy code.
An overview article about static code analysis tools. They can help you find and fix problematic code before it goes into production. The text presents some popular static analysis tools that can be used to test code in various situations. For example, DeepSource or SonarQube.
It's one thing to refactor your own code, it's another to refactor legacy code. It's much more difficult. The text contains tips for working with legacy code.
One way to improve the quality of code in a company is refactoring. It is often overlooked because it is almost invisible to users. The code still works, so everything is in order, right? However, problematic and messy code affects the speed of the product and its overall performance. The author of the article talks about the main benefits that can be obtained from code refactoring.
Anyone can learn to write code. But can you write it cleanly? In this article, the author shows his methods of writing clean code. The tips are simple, so even a beginner can handle them.
Modern tools make it possible to simplify the development process. Including, it is easier to follow the style of your code, trying to minimize its "unauthorized" formatting. This overview talks about what tools the IntelliJ Idea IDE provides to the developer so that the code is pleasant to read and easy to understand.
Another article on how to make your code better. Big one this time. It has a lot of simple tips. For example, one of them is writing unit tests. For the rest, read the text.
Writing clean code is not easy. This is hard hard work. Through trial and error, you will improve, repeating the same steps over and over until you find the solution you want. This article lists some tips to help you learn how to write clean code.
In software, an anti-pattern (anti-pattern) is a term for techniques that should NOT be applied when solving problems. The author talks about the six most common anti-patterns: Spaghetti Code, Golden Hammer, Boat Anchor, Dead Code, Code Growth, and God Object.
This text discusses the topic of lack of control over code quality in IT companies and why this is important. You will learn what technical debt is, why automation is the key to success, and how to build a code quality control process.
You have probably heard the term "static analysis". Most often, it means any one well-known tool or method. But in fact there are several varieties of static analysis, each of which has a certain meaning when used. About what types of analysis are and will be discussed in this article.
SOLID are five design principles in object-oriented programming. In addition to the theory that you will be asked about at the interview, you also need to learn how to write code according to the principles of SOLID. How to achieve this will be discussed in the report of the lead developer from the St. Petersburg office of EPAM Alexander Barmin. The author's presentation is accompanied by examples of "pure" Java code written according to SOLID conditions. The author also answers questions from viewers.
The article is devoted to the review of the book "Clean Code" by Robert Martin. The author considers ways to improve and optimize the code, and at the end he gives a small but interesting problem.
GO TO FULL VERSION