Starting from the details to create a glorious workplace Image

A real thing occurs many times in different places every day.

Yesterday, I discussed a design with an employee who was still in the internship and asked him to document the process.
In the afternoon, I received a1234. rarThe compressed file contains four pictures (flowcharts): 1.jpg-4.jpg ).

A programmer is not only impressed by your ability to write programs,
Each of your emails, speeches at each meeting, and documents from your hands,
It will make profits and losses to your overall image.

Therefore, I think it is wrong to hold the idea that "everything is fine if you do a good job of technology,
Imagine how much discount will be given if Apple products are put in poor packaging and the specification is printed like a small advertisement, coupled with headphones on the roadside stalls?

Naming a file is a small problem, but I can also list two major crimes:
1. Ignore others' feelings and reduce others' work efficiency.
How do people who receive files classify them?
If the recipient changes the name of the file, will the file be located based on memory?

2. Shortsighted.
Question: as the next 4234, and files emerge in an endless stream,
How can I tell which one is the author?

I will list the "details of non-checkpoint" that I have learned in a random order as follows (please add them ):
1. Meaningless file name
2. garbled junk files on the desktop
3. There is no chapter-based file management, and documents provided by others will not be found in a twinkling of an eye
4. Blank emails with attachments only
5. Empty emails.
6. Top-standing Word documents (the first is the content, no cover, directory, and so on)
7. You do not need the title of a chapter in word. The title is unknown.
8. execl table not trimmed in any format
9. unreasonable use of segments, clauses, and punctuation marks (greatly increasing the difficulty of understanding ).

If you see this, you still think the details are not important,
I will explain the final reasons (also described at my internal team meeting ):

As a programmer, how many opportunities can your code be seen by the leaders of your superiors?
In addition, unless in special circumstances, will a leader really pay attention to the code you write?

On the other hand, the email you sent or replied to, a Word file, PPT, and Excel file you wrote,
However, it may fall into the hands of leaders, or even serve as the discussion material at the meeting.

Do not miss any chance to impress others !!