Anyone can learn coding, but developing good programming habits is a completely different problem. Programming is one of the easiest professions to learn without formal education. However, if you are completely self-taught, you may eventually develop a bad habit that is difficult to get rid of. Until someone points it out to you, you may not even know whether you have chosen the common evil virtue. The result is a dreadful \
1. if you are a young developer who has made plans, everyone will have done it. When you come up with a new idea, your first instinct is to jump in and start coding. But if the heating runs out and there is no plan to do anything, the project will end up dead. If the project is interrupted more times than can be counted, the solution is to start planning in advance. This can not only help you achieve the clear goals you need to pursue, but also improve code quality and save valuable time. Before starting a new project, you need the following information: Project summary – for what, for whom, and for what. List of technologies to use – including languages, frameworks, etc. General functional overview – consider the architecture of the project and how the elements interact. Display the required functions, main functions and minor functions. Deadline – plan when different phases of the project will be completed. Even such a simple overview is much better than blindly. Conversely, excessive planning can be harmful. Don’t wait for the perfect idea or everything to be perfectly understood. Create a profile and reach it. The
Remember: plan before programming. It will relieve a lot of headaches in the future. 2. don’t repeat the hundreds of small organizational skills that your (dry) developers need to follow, but the most popular is dry:don’t repeat yourself. This common principle is: \
It is best to set the module builder def build (n) n+1 endclass John include builder def destroy (n) n-1 endclass Peter include builder end method once, reuse it if necessary, and then set it every time you need to use it in the class. What should I do if I need to change this function in the future? Editing one is easier than editing 20. Wet code (as opposed to dry, \
3. let people read androg let people read. Properly specifying the code format is more important than optimizing and minimizing the code. Not just for the people you work with. It helps you, too. If the variable name is random, the code has no comments, and the format is bad, problems will occur in the future. To keep your code clean and readable, follow these tips: Specifying the appropriate name for the variable is a small hint, but it is very important. Variables, methods, files, etc. must be named immediately so that the function is clear
whole Technically, it may be more efficient to specify names as 1, 2, and 3, but remember that what you actually do is a nightmare for you and your colleagues. The
Please name these objects with phrases that describe their purpose. Do not use headers or abbreviations unless they are very common. Example: forminput is a good variable name. Do not use names such as frminp, form 7, or form because they use confusing abbreviations or are not their own descriptions. After annotating the code for a few weeks or months, go back to the project and imagine that you need to look at the code painstakingly and wonder what each bit is doing. Annotated code can avoid all this. Also, if you work with others, make sure you don’t go through the same process. The
You do not need to describe all lines of code. If the appropriate variable name is used, the code usually executes itself. However, to specify code that does not need explanation, you must use comments. It also helps to explain why a better looking solution is not used. One more thing: don’t put a lot of comment headers at the beginning of your code to specify change logs, licenses, and other daily information. But please create a reading. No one likes to indent huge blocks of code correctly. Proper indentation and line wrapping are tricky, but rather than not doing it at all, try and make mistakes. White space helps others read the code and makes navigation easier. The
The indented code shows the structure and how each line interacts with the next. The \
Another point: for many web development languages, it is best to use spaces instead of labels. Two spaces are a common standard for HTML, CSS, and JavaScript. In addition, developers who use spaces instead of tabs can make more money. To maintain consistency, all developers have their own opinions on indentation, annotation handling, and file naming methods. But whatever you do, the most important thing is consistency. You can use the desired naming convention, but it is the same every time. If you use the functionname shell to specify the function name in JavaScript and the classname shell to specify the class name, do not switch. It also applies to indentation criteria. Format the code the same way each time. The
While you will develop your own shortcomings, it is recommended that you find general rules for the language you are using. Code imprinting can help you find inconsistent or malformed formats in your code. 4. in the middle of a code refactoring project, have you ever felt the urge to clean up your code? It’s time to abandon this habit. Code refactoring refers to the process of deleting and optimizing all bar graph bits to reduce the occupied space and follow the principles of dry. The function remains unchanged. ready-made
Get into the habit of checking or browsing language documents. Continue to track what you are interested in and experiment when you have time. That will make a big difference in your experience. Developing better programming habits can take a lot of time. Especially when working alone on a large project, you may want to do anything that works. However, although it can end up as a working prototype, the fundamental problems of the code will eventually cause problems again. If you want to be a better web developer, especially to gain experience in team work, you must know the correct programming method. The code must be readable by others, so before you start, make an effort to plan and maintain the system. Please consider using version management software and learning new languages in your free time. With a few changes to your habits, you will find that your code becomes cleaner and you will become a more skilled and versatile developer. What bad programming habits have you picked in the past? How long did you stop? Share experiences with fellow developers in comments.
