Working efficiency of work reflection

Programming has been so many years, but found that their work efficiency is low, often spend more time than others, engaged in a very tired but the effect is relatively poor, in this way to reflect on their own working style, feel that they have the following work problems:
1. Work is too edgy, often do not think well on the dry, in addition to the problem and repeated debugging, and try to do before you do more before doing, do not move the code does not check the run debugging, the results found some with obvious errors did not change well, very time-consuming
2. Estimate the workload is too optimistic, did not consider some of the key points to the boss of the chest shop, the final physical and mental exhaustion, to the boss left a bad impression
3. Encounter problems like their own slowly to study, in fact, sometimes as long as asked to the more familiar colleagues will soon be able to take care of. Do things later to give yourself a deadline, if not done with colleagues to discuss
4. For the boss of the design and needs of no in-depth scrutiny, often his demand design is not reasonable, repeated changes, resulting in a waste of time, to play their own initiative to control the progress of the project, to avoid walking along others, encounter the risk of others
5. It is also a waste of time to start with a colleague when it comes to discussing issues. Be sure to fully understand what the collaborators mean to do again.

Working efficiency of work reflection