Programmers are more like artists. What kind of psychology is more creative?

[CsdnCompile]Unlike traditional ideas,ProgramMembers are more like artists than scientists. If you want to discover the greatest creativity of your team, you should begin to think about the programmer's psychology and integrate it into your management methods..

It is often said that programmers are introverted, and I find that this is not the case in most cases. However, programmers are more focused and more focused than others. These two points will generate an introverted feeling.

WriteCodeIt is a creative job, not science or engineering, although if possible, programmers are willing to apply scientific and engineering stuff to writing code. Therefore, to be a programmer, you must be highly creative, which is precisely why the programmer is willing to engage in new projects rather than maintaining the old ones, because the maintenance work cannot lead them to create opportunities.

When creative programmers are engaged in new projects, they will enter a mental state named "flow", which is very good for organizations and individuals.

Professor Mihaly Csikszentmihalyi from the University of Chicago (former chairman of the Psychological Department) investigated hundreds of individuals, from IT entrepreneurs to Nobel Prize winners, to research creativity. He has written many books and papers on Flow and creativity.

He said, "we should put them in such a state, instead of letting them follow our requirements or directions, so that they can find their methods, this kind of freedom gives them the power we don't know. Instead of directly forcing them ."

Flow is a mental state dependent on context. In this state, programmers can skillfully solve tasks as long as they are in this context. Once it is not in the context, it takes a long time to fix it.

Flow takes time and is vulnerable. If a programmer's status is interrupted, it will take a long time for them to obtain it again, sometimes up to an hour. That means your team has lost one hour of creation. If a programmer is interrupted for multiple times, he may never reach this state in a day. Without this state, there will be no creativity.

Flow is very fragile, but not as fragile as it looks. It only breaks down when you ask the programmer to change the mental context. In details, you can touch the shoulders of a programmer to ask what they are doing or ask your questions. It doesn't matter. But if you ask them where timesheet is, you break the flow.

So how can we create a flow state to maximize the creativity of your team? The method is simple: provide enough space, including time, and psychological independence; give them enough time to rest; When a programmer is assigned a creative task, do not interrupt them from context; do not hold unnecessary meetings. Do not disturb others. [Compilation: Yu Lei]

From: http://news.csdn.net/n/20070808/107216.html