Software Engineer role guide-[3] daily work

This seriesArticleDirectory:Http://www.cnblogs.com/lzhdim/archive/2010/06/10/1755376.html

Directory of this series of articles:Http://www.cnblogs.com/lzhdim/archive/2010/06/10/1755418.html

 

The1Chapter Software Engineer Guide

 

1.3Daily Work

Our work involves two types of work: work and study. Daily Work is the work that is basically done every day.

Based on the daily progress, we summarize the daily work of software engineers as follows:

L
compile Code (including new code and modifications bug MSO-Hansi-font-family: "Times New Roman" ">)

L
unit test

L
participate in system testing

L
related design documents

L
participate in Writing user manual documents

L
find the solution and content (search for the book or Google MSO-Hansi-font-family: "Times New Roman" ">, Baidu "Times New Roman">)

L
learn new technologies and ideas (reading books or online materials)

L
Group discussion or training

In fact, we have divided daily work into work and study. However, it is estimated that many people will complain that their daily work is too busy to learn. What I want to say here is that learning is your own business. You must be good at squeezing and drilling, and read the knowledge you are interested in while you are in the middle of the market. This can help ease your work tension, and learn or pay attention to your favorite content.

In addition, the project manager has the responsibility to arrange the time for employees to learn and organize the content. This is what I need to arrange for project management.