Homepage
How to make a good developer
I want to say here is some of the qualities I think that developers need to have, of course, these are just my own opinion, I hope everyone can add. I hope everyone will join the online forum to talk about their own opinions and feelings:
* Amaze of knowledge, and you can add your own knowledge and improve your knowledge structure.
* Patience, especially in debugging and learning, there is no smart person in the world. Doing development, in fact, learning and improving the two things, the development process in the middle of these two things is actually relatively simple
* Always remember: The code is given to people instead of running the machine, the computer is not afraid of being tired when executing the program, and people are very tired when they look at the code.
* Good coding habits, at least guarantees yourself to read the code you wrote before you can read more time
* Try to make your code can be easily understood by others, think about it when you write the code, you will not be embarrassed by others after two months.
* Do not tolerate your own repetitive errors and write duplicate code
* Know how to do more important than getting code
* Try not to do something that has already been done
* Learn to respect the achievements of others, unless you have to decide to fully replace the previous system
* Cherish your time and work results, try to make others share your development results
* Avoid assumptions, think more about the possibility of extreme conditions and cause errors, and strive to reduce low-level errors
* Don't believe that at least don't believe in the test results you do for yourself.
* Know your own development ideas and know how to understand and absorb others' thoughts
* Learn to be consistent with others, but you can't give up your development characteristics
* Know the people around you, whether it is developing skills or development experience
* Understand the importance of software structure, analyze the structure of code before analyzing the code
* Summary, regularly summarize the knowledge you have learned, see the time for the past due to various reasons
* Society plan, try not to think of the task by extending their work hours
* Learn to properly estimate your ability and working hours
Here, this is what I think some is suitable for my own, not necessarily for everyone:
* Take more magazines, you can see the reference book you have seen before, you are likely to have some details you haven't noticed before.
* Don't be too early to do something unrelated to the development, because the golden period of learning is very short
* Learn to analyze the system of others, see the advanced side of the system developed by others. Here, this includes the development of others, the structure used in realization
* I often feel that I will be eliminated, I often complain myself.
* Know what you lack
* Forced things you don't like to do, such as writing documents
* Can have courage to rewrite the system you develop, but when you react, you should take and learn the next way and method, otherwise it will not be necessary.
* Simplify the problem rather than complication
* Some issues that will be generated during maintenance is transferred to development or when designing
* Sometimes you may wish to ask yourself: What do I do when I don't do it?
* Adhere to your weekly development plan, don't easily transfer your attention before things
* As much as possible to teach you to others, because you may no longer be responsible for this system one day.
* Doing things must have end, unless there is no reason to leave, do not leave before work
* Don't take your own things to the company, you should take away the development experience and the understanding of development rather than code and products.
* Take a break at all, give yourself a false, after all, people are not machine
I hope everyone will join the online forum to talk about their own opinions and feelings.
