different program designers, the speed differences in writing programs may fundraiser. Some programs write very quickly, others are turtle speed. Jeffrey Ventrella is a representative of the turtle, he recently in an article on the speed of the design of the difference, and from the point of view of the turtle, to explain why in this fast-growing era, he thought the program should be slow to write better
The following is the readme of Jeffrey Ventrella
my dad used to say to me that a little bit slower to write the program, you can quickly finish writing the program.
I have worked in a lot of internet companies in San Francisco, and now I'm 52 years old, and I'm a big age for programmers . I write the program at a speed near turtle speed, in fact, I am more like an artist who can write programs.
once, I worked with some of the younger programmers, who believed in the program designed to be "fast and with little change." We work together in the same codebase as if we were cooking a big pot of soup together. If each of us continue to contribute to the code, the future of this project should be very beautiful and spectacular presentation.
but not yet.
The problem is, these young programmers in the mind actually have such a thought, they think: 1, everyone is replaceable, 2, no one should be responsible for a certain part of the specific code, 3, everyone should be able to arbitrarily modify the entire project code.
they feel that there is now a tool for GitHub to manage the program code contribution during asynchronous time, so long as everyone is consistently contributing code, engineering and products will come out of the process.
That 's not the case. Programming never should be a tool to reduce the time of software development.
The program design should be a rhythmic and rhythmic movement. I tend to divide the project into different stages in terms of scale and time, and each phase starts with small things such as exploration, experimentation, error, and temporary variables. Sometimes when this building is finished, I'm going to do it again because I think I have a better way of building it. This new approach is sometimes right, or wrong, and in fact you never know which one is better unless you really do it again.
in the software development ecosystem, it is important to think about the hybrid thinking that drives and supports the entire design process, without this part of the work, the faster the programmer, the more good the design can make?
Many neuroscientists believe that the flow of neuron information can have a transient blockage and reverberation in the course of the brain's conduction, which plays an important role in thinking and perception. The design of the program should be the same, it takes time.
A good programmer is not to type fast