Liu Tianbei
It is said that there is once, a lady complained that the portrait of Picasso was too "unlike" she. The answer to the three-dimensional master is: "It doesn't matter, lady, it will be like". Picasso's answer reflects the typical relationship between artists and the public in modern times. As a prophet and genius, artists can re-create the public's feelings and aesthetics in advanced works. According to this logic, portraits "unlike", it can only be a problem with the complaints of the ruins - she should work hard to adapt to the new perspective of her art to bring her new perspective until she feels "like", there is no It. According to my observation, the programmer and the public in today's society faithfully copies the above "opposite and leading" weird relationships. It is necessary to draw a quick-sold for the programmer in the eyes of the average person. The necessary elements must include the ten fingers of the mad attack on the keyboard, the red eyes, the screen on the screen, the screen, which is difficult to identify, etc., the color is added to add Hold a proud of the secrets and the gods of the door. The coats here are strengthened when people use the software products completed by the programmer. Complex interface, blunt tips, difficult to understand the operation sequence, and finally frequent errors and crashs - how are these are "necessary evils" with high technology? It is also a product that is like accepting Picasso, and strives to adapt to these technological mad people and their mad products, no matter whether it is Alan Cooper made a negative answer in its famous "innovative thinking": must resist this trend, how to have the right to decide on the problem, not full The programmer of the brain code - otherwise, Cooper has a very wonderful metaphor. On this matter, the programmer has said, and let the mental patient operate the madhouse dangerous and absurd. If you are currently fortunate (or unfortunate) is developing software or websites, in a broad programmer camp, then I expect, you will feel strong when you start reading this book (like I am in my own). To a large extent, this is a programmer evil record, and the programmer is often crossed in designing software products, and analyzes the unconscious roots behind these errors - a programmer culture, we This high-tech era is unique. These ruthless, uncomfortable analyzes can successfully agitate their emotions, because they are true and are neutralization. The programmers did not have to be proud, they were inexplicably design ideas, they all got the explanation of whip. Most importantly, the author Cooper is from the programmer camp. He successfully developed a programming language Ruby and sold it to Microsoft. Basic it was based on this, and it has brought a revolutionary impact on software development methods and software industries. The authority of the design area, Cooper has also received a variety of important awards in the industry. Recently, the US Software History Museum has passed the software industrial name, organized a series of speeches, and COOPER entitled "Future of Software Development" is scheduled to be in the third place in all speakers, seeing its influence and status. The anti-fang attack from the authority of the industry, even if the voice is harsh, it is definitely what is good, it needs to be listened carefully: After all, try - Discovery error - the corrected cycle is one of the important modes of human progress. Cooper further comes to the sorrow level of software product design, and consequences are not easy to use. This will not only reduce the customer's loyalty and customer reputation of software companies, but also make software development departure from the original intention of popularization of computer applications. From this, it has been, and it will also be remembered in the field of culture, social structure, and the programs that have just been talked - the opposition between the public is a large extent is the product of the decay design, and more Result in a further vicious circle. So how do software companies get rid of this dilemma as soon as possible? Cooper has a valid answer in the second half of this book.
