Software Craftsmanship 在線電子書 圖書標籤: 軟件開發 計算機 工藝 項目管理 軟件工藝 計算 英文版 編程
發表於2024-12-23
Software Craftsmanship 在線電子書 pdf 下載 txt下載 epub 下載 mobi 下載 2024
剛開始讀覺得很喜歡很贊同,經過最近的學術reflection發覺書中意見有所“偏激”和絕對。但是也可以看一下,對衝擊傳統的software engineering概念有幫助。
評分當年路過某書攤看見就買瞭=.= 看來沒買錯⋯⋯
評分當年路過某書攤看見就買瞭=.= 看來沒買錯⋯⋯
評分剛開始讀覺得很喜歡很贊同,經過最近的學術reflection發覺書中意見有所“偏激”和絕對。但是也可以看一下,對衝擊傳統的software engineering概念有幫助。
評分剛開始讀覺得很喜歡很贊同,經過最近的學術reflection發覺書中意見有所“偏激”和絕對。但是也可以看一下,對衝擊傳統的software engineering概念有幫助。
Craftsmanship is a return to the roots of software development: Good software developers have always understood that programming is a craft skill. Regardless of the amount of arcane and detailed technical knowledge that a person has, in the end, application development comes down to feel and experience. Someone can know all of the esoteric technical details of the Java programming language, but that person will never be able to master application development unless he or she develops a feel for the aesthetics of software. Conversely, once a person gets the feel for software development, the specific technical details become almost irrelevant. Great developers are always picking up and using new technology and techniques; learning a new technology is just a normal part of the life of a software developer. The term software engineering was coined in 1967 by a NATO study group that recommended a conference to discuss the problems of software. The report from this 1968 conference, which was sponsored by the NATO Science Committee and took place in Garmish, Germany, was titled Software Engineering .1 In the report, Peter Naur and Brian Randell stated, The phrase 'software engineering' was deliberately chosen to be provocative, in implying the need for software manufacture to be based on the types of theoretical foundations and practical disciplines that are traditional in the established branches of engineering. In the same spirit, it is the intention of this book to be deliberately provocative in implying the need for practitioners to start paying attention to the craft of software development. Software craftsmanship is important because it takes us away from the manufacturing metaphor that software engineering invokes and makes us pay attention to the people who do software development. Craftsmanship brings with it the metaphor of skilled practitioners intent on mastering their craft, of pride in and responsibility for, the fruits of their labor. Software craftsmanship is not the opposite of software engineering or computer science. Rather, craftsmanship is a different tradition that happily coexists with and benefits from science and engineering. Just as the modern blacksmith benefits from better tools, materials, and understanding, so software craftsmanship benefits from better computers, reusable components, and programming languages. Just as blacksmiths transcend science and engineering with their skill and artistry, software craftsmanship can transcend computer science and software engineering to produce great programs, applications, and systems. UNIX and the modern-day GNU Linux are probably the best-known examples of this-;systems that are thriving due to the craft, skill, and dedication of their creators. Software craftsmanship is a response to the problems of trying to force-fit software engineering into commercial application development. Software engineering was developed to meet the needs of NATO in developing very large defense systems. Commercial application development differs from the development of defense and government systems in that applications are a whole lot smaller and normally have to be up and running in less than 18 months. It is rare for a commercial application to be developed by a team of more than 20 people, and most application developers work in teams with fewer than 10 members. Software engineering is good at handling the problems of really large teams of 200 or more people, but it has little to say about how the individuals in a team should practice their craft. Software engineering encourages the human wave 2 approach to software development. Rather than solving the problem of how to develop highly skilled developers, software engineering attempts to deskill software development by suggesting that every problem can be solved by throwing more people at it. Although this approach sometimes succeeds, the resulting software is junk. Slow and bloated, it just never feels right. Users are dazzled by the graphics and animation but never really manage to come to grips with the software. They are thwarted by their inability to learn the software and use only a small fraction of the available features. Software does not have to be like that. All too often I see application development teams shipping valuable applications that provide real, measurable business benefit, but apologizing for not following software engineering best practices. For me, the real test of a team is whether it manages to ship and then enhance and extend the application for years afterward. Timely shipping of the first release is important, but it is more important that subsequent releases occur in a timely fashion and that each new release improves the application. Whenever I'm asked about hiring developers, I tell people to look for developers who have shipped a few applications successfully and then stuck around long enough to handle the next enhancement or maintenance release. Shipping proves that the developer can make something work; staying around for the next release allows the developer to experience the effects of the way that he or she built the application in the first place. If a developer has done this three times, my guess is that he or she is skilled and experienced enough in the craft of software development to be successful again. Software craftsmanship is the new imperative because many members of the software development community are starting to chase technology for its own sake, forgetting what is important. The purpose of software development is to create high-quality, robust software applications that deliver value to their users. What matters is growing a new generation of developers who can do that. Software craftsmanship stands for putting the joy and excitement back into creating applications for our users. 1 Naur, Peter, and Brian Randell, (eds.), Software Engineering: A Report on a Conference Spnsored by the NATO Science Committee, NATO, 1969. 2 Levy, Steven, Hackers, Penguin Books, 1994, p. 88. 0201733862P08202001
很久前看过,凭映象回忆一下。这本书更注重个人素质培养,呵呵,尤其是学徒式传授,想想还是有点道理的,明师出高徒嘛。不过在实际中大师来亲自指点你是太难得啦,所以只能说做做梦咯;)
評分很久前看过,凭映象回忆一下。这本书更注重个人素质培养,呵呵,尤其是学徒式传授,想想还是有点道理的,明师出高徒嘛。不过在实际中大师来亲自指点你是太难得啦,所以只能说做做梦咯;)
評分看来我们在使用软件工程的时候,真的忽略的一个问题,软件工程到底使用什么样的团队?作为一个小型的开发团队不超过10个人,软件工程里面所推崇的过程意义是否有效?书中给了详细的讲解.个人感觉软件开发更像是艺术不是工程,我们需要资深的开发者,我们需要团结的团队,我们需...
評分软件工艺是我比较钟爱的一本书,虽与传统的软件工程思路有出入,但里面有很多思想&思路可以借鉴。其实软件工艺和软件工程并不矛盾和敌对。项目的特点不同,周期不同,我们在做项目的时候确实应该采用不同的策略和方法论。其目的只有一个就是保证项目成功和按期的交付。 1...
評分[软件工艺] 作者以一个程序员兼社会学家的视角重新审视“软件”的本质。 什么是软件? 软件是相对于硬件而言的,他是计算机重要的组成部分,通过软件,人们可以让通用的、标准的计算机完成特定的任务。 从经济学的角度来说,软件就是被具现化的智力资产。 从认知学的角度,软件...
Software Craftsmanship 在線電子書 pdf 下載 txt下載 epub 下載 mobi 下載 2024