140 ;;Quote: a design goal for Multics was continuous operation like electric power or the telephone network

140 ;;Quote: a design goal was a highly reliable file system which did not need independent backups

143 ;;Quote: in Multics an elaborate macroassembler failed; replaced by a simple, primitive assembler

144 ;;Quote: Multics developed incrementally; no one person could understand the effect of a module on the system

145 ;;Quote: incremental design is expected for hardware, e.g., breadboards and test machine; not so for software

146 ;;Quote: the copy machine was important for designing Multics; increased speed of design interactions

149 ;;Quote: insufficient computer time for building Multics; should have reduced programming staff and bought hardware

149 ;;Quote: consensus design encouraged too many requirements and generalized designs

149 ;;Quote: Multics should have used minimal implementations for each set of ideas

150 ;;Quote: need a rigorous review after programming and before debugging; often caused major improvements or revised design strategies

151 ;;Quote: Multics development dramatically improved once development moved to Multics (after four years)

151 ;;Quote: with development on Multics, system changes within ten minutes and sometimes seconds

151 ;;Quote: main obstacle to changing Multics was updating system documentation

151 ;;Quote: Multics development by new system release once or twice a week; one person responsible

156 ;;Quote: large software projects often fail by orders-of-magnitude miscalculations; modeling and estimation could detect these