<story><title>Implementing VisiCalc (2003)</title><url>https://www.landley.net/history/mirror/apple2/implementingvisicalc.html</url></story><parent_chain></parent_chain><comment><author>not_that_noob</author><text>This design-first approach is the hallmark of many successful products. It is the rare engineer who can say &amp;quot;I had to change code that I had labored over&amp;quot; with such equanimity. Excellent read!&lt;p&gt;&amp;quot;The ability for Dan and I to work as a team was crucial. While he could&amp;#x27;ve written the program, the fact that he wasn&amp;#x27;t gave him the freedom to focus on what the program should do rather than how to do it. I could appreciate his reasons and would eventually accept that I had to change code that I had labored over. We were able to find ways to take advantage of the limited space available for the program in deciding what features to include or not include.&amp;quot;</text></comment>
<story><title>Implementing VisiCalc (2003)</title><url>https://www.landley.net/history/mirror/apple2/implementingvisicalc.html</url></story><parent_chain></parent_chain><comment><author>js2</author><text>&lt;i&gt;If the user typed a character before the keyboard input buffer was emptied it would be lost.&lt;/i&gt;&lt;p&gt;Huh. I never noticed this. Then I recalled that my Apple ][ had a Videx Keyboard Enhancer. Turns out it provided an input buffer (besides providing upper&amp;#x2F;lower case which is the primary reason we added it). Now I&amp;#x27;m wondering how much latency the buffer added and whether it reduced my high score on Lode Runner.</text></comment>