＋设为首页 ＋添加到收藏夹
jack walked into the office one monday morning. underneath his arm, he carried a rolled-up piece of poster paper. he walked to the back of the building, where a group of couches and tables made up the "engineering conference room," and used masking tape to stick his homemade poster to the wall. on it, jack had carefully written in block letters, "keep changes small." satisfied, he went to the cube the company let him use and waited for the developers to get there.
figure 1. actual quality curve 【程序编程相关:使用内部和匿名类优化Java代码】
while he waited, jack worked on a document for the development manager. like most of jacks documents, it was one page and covered a single idea. jack described the current quality curve of the product. in the main branch of the code, where development on the next release was taking place, the curve looked like this: 【推荐阅读:设计合适的接口】
jack wanted to move towards a curve like this: 【扩展信息:让XDoclet为你写存根类】
there had been an initial batch of bug fixes left over from the current release that had been fixed, followed by new feature development -- and new bugs. only now, near the release date, were those new bugs being addressed, and the curve starting to turn up again. the nextgen branch, where development on the "next plus one" release was happening, was even more chaotic.
figure 2. ideal quality curve
... 下一页