How to write the work log?

The work log need not be complicated. Clear text files are the best. You can add it to your version control system and track its changes.

Every day, write the date. Talk about your ideas and solutions to problems. Write down your choices, opinions, observations, test methods, results and decisions. If you make a mistake, write down why it happened and describe your choice. If you encounter a bug or problem, describe it and how you solved it.

Like people who have the habit of keeping a diary, the work log is only used by individuals to record their own work, so it will not replace the comments in the official project documents or source code. Write hundreds of lines a day.

Finally, don't modify it. Describe what you did and the detailed results. Write it down honestly, whether it's good, bad or annoying.

-

Personal work log management (record the history of work log)

In fact, it is not difficult to manage the work log. The easiest way is to use it as a work diary and write down what happened that day, but don't forget to sum up today's lessons, experiences and gains at the end.

Keeping a diary for a long time, I summed up the following "rules":

-The daily diary is actually composed of seemingly independent things that happened at different points in time;

-some of these things were originally arranged by themselves, and some happened temporarily;

-Some things are related to one or more tasks and projects you are working on;

-Some things will definitely involve other people, perhaps their colleagues, friends, customers, suppliers, competitors and so on.

Later, I usually organize the contents according to the following work log format:

Xxxx year xxx month xxx day

Work log 1 (something): occurrence time, main contents and summary, related projects/tasks, and related contacts.

Work log 2 (something): occurrence time, main contents and summary, related projects/tasks, and related contacts.

……

After a period of time, I found that with the increase of work logs, it was still inconvenient to find some content by myself. So I joined several like-minded software developers to try to develop my own work log software to manage my own related affairs, and at the same time make it a platform for personal information management.

We classify personal information into four objects: work log, project/task, contact person and work unit.

The work log includes date, time, main content records and some value-added information. You can complete your work log by recording the "schedule". These work logs can also appear in cycles. You can also set whether you need a reminder, record the expenses related to something, and so on.

We manage projects (tasks), contacts and work units in separate tables, so that when you record the work log, you can add projects (tasks), contacts and work units related to this work log. If the related record you want to add already exists, you don't need to re-enter, just select it.

Another advantage of this is that when you query a project (task), contact person and work unit, you can see what work logs these objects have, and our personal information management will be more organized.

The work log system formed by this arrangement has become a very extensive work log format. When people in different industries and positions use it, it can "transform" into different work log software, such as class teacher's work log, student's work log, sales work log (customer manager's work log, customer work log), procurement work log, administrative work log, customer service work log and so on.