Work for 10 years, summed up some programming skills, personal views, do not like spray. Useful points are absorbed. The useless points are ignored
-
Break up chunks of code into functions.
-
Please turn off the computer and look at it tomorrow.
-
The YAGNI Rule (you won’t need it) : Only write features that are asked of you. Don’t predict the future, just get the development done as quickly as possible. Code only what is most necessary to solve the problem at hand.
-
You don’t need to know everything, and you don’t need to know every framework. The best thing to do is to lay a solid foundation. Dive into the language before you start using a framework, learn the basics (like SOLID principles), or how to write clean code.
-
The KISS principle: The KISS (Keep It Simple and Stupid) principle states that most systems will work well if kept simple rather than complicated. While this is logical, it can sometimes be difficult to do.
-
Don’t overthink it.
-
If you struggle with a problem or bug for too long, leave for a while and come back later. Often, the solution comes to mind on the way out of the office to the bathroom. When you’re angry with a client or colleague, it’s also advisable to take time off if you want to keep your job…
-
Learn to write useful tests and learn to use TDD (Test Driven Development). TDD is a software development process that repeats the following short development cycles: write tests; Run all tests to see if new tests are running; Write the code; Run tests; Refactoring code; Repeat.
-
Solve the problem before you write the code. Don’t start programming when you have nothing to do.
-
Don’t memorize the code, understand the logic.
-
If you copy and paste the solution from Stack Overflow, make sure you understand it first. Learn how to use Stack Overflow appropriately.
-
If you want to learn, practice. Create examples and get them running, because learning by reading is not enough.
-
Study other people’s code, and occasionally let others study yours. It’s a good idea to pair program and review code.
-
Don’t duplicate the wheel.
-
Code is the best documentation.
-
Know how to search. You need to be experienced, read a lot, and know what to look for.
-
The code you write will be maintained by yourself or someone else later, so keep the reader in mind and don’t assume you’re the smartest person in the room. Write code like a story.
-
The best way to fix a bug with Google is to copy and paste.
-
Don’t give up. Problems will always be solved. The bad times will pass.
-
Have a good rest. The best way to solve a problem is to rest your brain first.
-
Learn to use software design patterns. Design patterns are solutions to common problems in software design. Each pattern is like a blueprint that you can customize to solve common design problems in your own code (remember, don’t reinvent the wheel).
-
Use integrated tools and automation whenever possible.
-
Code Kata: A code kata is a programming exercise that helps programmers improve their skills through repeated practice. For example, see codingdojo.org/kata/
-
Program at the interface level, not the implementation level. Dependency injection is necessary, see SOLID principles.
-
Refactor – test – refactor. Refactoring is the reconstruction and modification of existing code to improve its internal structure without changing its internal behavior.
-
Ask for help when you need it. Don’t waste time.
-
Practice makes perfect.
-
Although comments can sometimes help, don’t pay too much attention to them. Comments may be outdated.
-
Know your development environment and build one strong enough, such as IntelliJ.
-
Reuse components.
-
When developing web applications, think about mobile devices and their associated power and bandwidth limitations.
-
Don’t optimize or refactor your code too early. It is important to have a minimum viable product as soon as possible.
-
Don’t take inefficient shortcuts just to save a few minutes. Every time you write code, try your best.
-
Follow documentation standards.
-
Users are not technical people. Keep this in mind as you develop your UI.
-
Use source control systems like GitHub or Bitbucket frequently and commit small updates frequently.
-
Log is better than code debug. Write down all the key parts.
-
Be consistent when writing code. If you use a style, stick to it. If you’re working with multiple people, use the same style as the entire team.
-
Don’t stop learning, not just new languages or frameworks, but also the basics of software development.
-
Finally, be patient and love.