[an error occurred while processing this directive]

<p>
<font size=+1><b>Notes: Wednesday 23 August 2006</b></font><br>

<table cellspacing=2 cellpadding=2 width=100%>
<tr><td colspan=2 align=center>
<b><font size=+1>Assignments Due</font></b>
</td></tr>
</table>

<ul>
<li> 24 August, 11:59pm: <a href="/cs205/survey.html">Registration Survey</a>
<li> 25 August: <a href="/cs205/pledge.html">Course Pledge</a>
<li> 28 August: Read Liskov, Ch 1-2
<li> 28 August: <a href="/cs205/ps/ps1/">Problem Set 1</a>
</ul>

<p>

<center>
<font size=+1>
<b>Notes and Questions</b><br>
</font>
</center>
<p>

What are the differences between small, fun programs and large, important programs?

<p><br><p><br><p><br><p><br><p><br>

What is engineering?

<p><br><p><br><p><br><p><br><p><br>

How is constructing software similar to constructing bridges?<br>

<p><br><p><br><p><br><p><br><p><br>

<p>
How is constructing software different from constructing bridges?<br>


<p><br><p><br><p><br><p><br><p><br>

What tools can we use to manage complexity?
<p>
<p><br><p><br><p><br><p><br><p><br>


<font size=-1>
<em>
There are two ways of constructing a software design. One way is to make
it so simple that there are obviously no deficiencies. And the other way
is to make it so complicated that there are no obvious deficiencies. </em>
<p align=right>
Tony Hoare 
</font>
<p>


[an error occurred while processing this directive]