Observe that for the programmer, as for the chef, the urgency of the patron （顧客）may govern  the scheduled completion of the task, but it cannot govern the actual completion. An omelette（煎雞蛋）, promised in two minutes, may appear to be progressing nicely. But when it has not set in  two minutes, the customer has two choices—waits or eats it raw. Software customers have had（1）choices.  
Now I do not think software（2）have less inherent courage and firmness than chefs, nor than other engineering managers. But false（3）to match the patron’s desired date is much more common in our discipline than elsewhere in engineering. It is very（4）to make a vigorous, plausible, and job risking defense of an estimate that is derived by no quantitative method, supported by little data, and certified chiefly by the hunches of the managers.  
Clearly two solutions are needed.We need to develop and publicize productivity figures, bug-incidence figures, estimating rules, and so on. The whole profession can only profit from（5）such data.Until estimating is on a sounder basis,  individual managers will need to stiffen their backbones and defend their estimates with the assurance that their poor hunches are better than wish derived estimates. 
（1）
A.no 
B.the same 
C.other 
D.lots of 
（2）
A.testers 
B.constructors 
C.managers 
D.architects 
（3）
A.tasks 
B.jobs 
C.works 
D.scheduling 
（4）
A.easy 
B.difficult 
C.simple 
D.painless 
（5）
A.sharing 
B.excluding 
C.omitting 
D.ignoring