@12:19: <a href="https://youtu.be/UGhfB-NICzg?t=739" rel="nofollow">https://youtu.be/UGhfB-NICzg?t=739</a><p>> At this point, we threw the programmers an unexpected but not unrealistic curve.<p>> Like a typical user, we asked them to add a feature not in the original spec. In this case, a button would recall all the trouble logs for a particular customer.<p>> Using NeXT Step, the NeXT programmer completed the task in about 20 minutes.<p>> [NeXT progammer discussing some details]<p>> The sun programmer also estimated a time of 20 minutes, but it took about 45 before he was ready to test his version.<p>This was about 20 hours in, which means that since they started on Wed, 30 October 1991 and assuming maximum 8-hour days, they have missed Halloween and would be at least halfway into Friday. The video states that the programmers finished on Sat, 2 November.<p>The video goes on to state that the NeXT system enabled the NeXT programmer to add a number of features such as system fonts and button icons "for free", which goes to show that the video's intended audience are managers and executives of software development teams who would of course want faster development, ad hoc requests, and cost-free features.<p>I personally would have been tempted to (╯°□°)╯︵ ┻━┻ once they announced a planned "unexpected" feature request because rather than train users and customers to frontload requirements in order to benefit from the design decisions that would be made as a result, the video encourages customers to believe their out-of-spec requests will be more quickly accommodated if only their programmers were using object-oriented NeXT Step.<p>25 years later, we know the truth about how easy it is to shoehorn in 11th-hour feature requests when using object-oriented code.<p>EDIT: link to specified timecode; formatting; additional detail about date code was written.