《快速软件开发》封面

快速软件开发

Rapid development

Steve McConnell · 初版 1996 年

27人推荐
37位读者提及
82次提及

为什么值得读

  • 提倡为复杂脑力任务保持适度工时与充足休息
  • 总结经过验证的软件开发实践供团队选取落地
  • 帮助理清软件工程规范以减少研发中的巨大浪费

Hacker News 上怎么说

  • ……生产力与处理复杂认知任务所需的状态是不同的。认知任务要求越高,睡眠和放松就越重要。这就是为什么 Steve McConnell 在经典著作《Rapid Development》(快速软件开发)中提倡每周工作 35 小时。而且对很多人来说,实际的极限可能还要更低。比如读读 http://www.kalzumeus.com/2012/05/18/kalzumeus-podcast-ep-2-w... 就会发现 patio11 认为……

    …productivity is different than what is needed for complex cognitive tasks. The more demanding the cognitive task, the more important sleep and relaxation are. That is why in Steve McConnell's classic Rapid Development he advocates a 35 hour week. And the real limit for a lot of people may be less. For instance read http://www.kalzumeus.com/2012/05/18/kalzumeus-podcast-ep-2-w... to find out that patio11 thinks that…

  • ……岗位的人听说过它们,更别说读过了。举个例子,90 年代 Microsoft Press 出的书就很棒:《Debugging the Development Process》《Software Project Survival Guide》《Writing Solid Code》《Rapid Development》,还有像《人月神话》(The Mythical Man-Month)和《人件》(Peopleware)这种书。我只要求他们稍微了解一点点就行。但现实并非如此。得宠的人和“被公交车撞了公司就转不下去”(can't be hit by a bus)的核心骨干干啥都没事,而优秀的人却……

    …positions have heard of them, let alone read them. For example, the Microsoft Press books form the 90s are great. Debugging the Development Process, Software Project Survival Guide, Writing Solid Code, Rapid Development, and then books like The Mythical Man-Month, and Peopleware. Just a passing familiarity is all I ask. But no. Favored people and 'can't be hit by a bus' people get away with anything, great people with…

  • ……低吞吐量,最后一个方案虽然接受了这些问题,但能让你搞定小团队解决不了的难题。顺便再随口提个建议。如果你对生产力感兴趣,去搞一本《Peopleware》和《Rapid Development》,读一读,挑一套最佳实践去试水。

    …low throughput, the last accepts the issues but lets you tackle problems that the small team couldn't. Another random suggestion. If you're interested in productivity, pick up a copy of Peopleware and Rapid Development, read them, and pick a set of best practices to try.

  • 我不同意这篇文章的一些观点,对其前提也存疑。我认为软件工程虽然定义得还不够完善,但已经在变好了。Steve McConnell 写的《Rapid Development》在这方面做出了很大贡献。文章声称花了大笔钱最后却一无所获肯定是在为软件开发买单。但如果你遵循这些原则……

    I disagree with points of this article, and I'm not sure about the premise. I think Software Engineering is not as well defined as it could be but I think it is getting better. The book Rapid Development by Steve McConnel goes a long way in that regard. The article states that to spend vast sums of money and end up with nothing, you must be paying for software development. But if you follow the principles…

  • 你有没有考虑过也读一些软件工程的经典著作?《代码大全》(Code Complete)、《快速软件开发》(Rapid Development)、《人月神话》(The Mythical Man-Month)、《程序员修炼之道》(The Pragmatic Programmer)、《人件》(Peopleware)还有《软件工程规范》(A Discipline for Software Engineering)?(最后一本挺有争议的)。

    Have you considered reading some software engineering classics as well? Code Complete, Rapid Development, The Mythical Man-Month, The Pragmatic Programmer, Peopleware and A Discipline for Software Engineering? (The last one is controversial).

  • ……& Teams http://www.amazon.com/Peopleware-Productive-Projects-Teams-S... Delivering Happiness: A Path to Profits, Passion, and Purpose http://www.amazon.com/Delivering-Happiness-Profits-Passion-P... Rapid Development: Taming Wild Software Schedules http://www.amazon.com/dp/1556159005/?tag=stackoverfl08-20 The Five Dysfunctions of a Team: A Leadership Fable http://www.amazon.com/Five-Dysfunctions-Team-Leadership-Fabl...……

    …& Teams http://www.amazon.com/Peopleware-Productive-Projects-Teams-S... Delivering Happiness: A Path to Profits, Passion, and Purpose http://www.amazon.com/Delivering-Happiness-Profits-Passion-P... Rapid Development: Taming Wild Software Schedules http://www.amazon.com/dp/1556159005/?tag=stackoverfl08-20 The Five Dysfunctions of a Team: A Leadership Fable http://www.amazon.com/Five-Dysfunctions-Team-Leadership-Fabl...…

正在加载完整评论……

键盘快捷键

/
聚焦搜索框
j / k
下一本 / 上一本
Enter
打开选中的书
Esc
关闭 / 返回
g h
回到首页
g b
值得读精选
g t
历史总榜
g r
上升最快
g l
我的书架
?
显示本帮助