Like economics, the discipline of software development suffers from a weakness that prevents the resolution of competing theories, in that it is generally impossible to perform controlled experiments. It would take an extremely brave manager to ever try out two competing development theories by having two teams build the same product simultaneously. However, it is possible to borrow a technique from theoretical physics and perform thought experiments. Such an experiment would involve having more than one team develop the same product simultaneously, but using different techniques. That type of experiment is the premise of this novel.
The main character is a recent victim of downsizing who is kidnapped and taken to a formerly communist country where the educational level is high and the costs are low. Once there, he succumbs to his fantasies and agrees to perform the experiment of his dreams. With six products to build and a large staff of developers, he splits them into eighteen groups where each product is being built by three teams simultaneously. Each group of the three then uses a different development method. Throw in impossible deadlines and you have a microcosm of software development.
It would appear that such a premise would guarantee a boring book, but nothing could be further from the truth. The book is entertaining and enduring, as developers will recognize most of their development problems, albeit couched in somewhat unique circumstances. Many of the leading figures in the theory of software development management make cameo appearances, including a certain very rich man. The end result is a true stroke of genius that has somewhat of a surprise ending, but actually quite natural, given the current climate in the computer business.
It is rare when a book about the management of software development is not as dull as baked dirt, and this book is indeed the exception. Not only is it entertaining, but you can even learn some management skills in the process.
很多年前读过的这本书,只能说是一本有趣的读物,对初学者了解一些软件工程的概念有帮助,但不具有实践参考意义。可以当小说看(其实就是一部小说),消磨时间之余还能了解一点软件工程的只是。
评分关于项目管理,其实,我真的没有多大的感觉,本书说的是软件设计的项目管理,是靠我最近的一个项目。 不过,所有项目的互通感,让我了解到 一、项目的组建,包括项目成员人数,项目产品经理的任命,职能 1、人刚刚好,就好,如果所有的项目功能都设计好了以后,那就是任务...
评分 评分很多年前读过的这本书,只能说是一本有趣的读物,对初学者了解一些软件工程的概念有帮助,但不具有实践参考意义。可以当小说看(其实就是一部小说),消磨时间之余还能了解一点软件工程的只是。
前段和中间部分可以,ending不清不楚,可能由于篇幅所限吧。
评分前段和中间部分可以,ending不清不楚,可能由于篇幅所限吧。
评分台湾旧书店随手买的,豆瓣竟然有~
评分台湾旧书店随手买的,豆瓣竟然有~
评分软件工程课推荐的枕边读物
本站所有内容均为互联网搜索引擎提供的公开搜索信息,本站不存储任何数据与内容,任何内容与数据均与本站无关,如有需要请联系相关搜索引擎包括但不限于百度,google,bing,sogou 等
© 2025 book.wenda123.org All Rights Reserved. 图书目录大全 版权所有