<div dir="ltr"><br><br><div class="gmail_quote">On Wed, Aug 13, 2008 at 1:03 PM, Marco Morazan <span dir="ltr"><<a href="mailto:morazanm@gmail.com">morazanm@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="Ih2E3d">On Wed, Aug 13, 2008 at 12:38 PM, David Einstein <<a href="mailto:deinst@gmail.com">deinst@gmail.com</a>> wrote:<br>
> I do not think that programming per se is or needs to be a particularly<br>
> difficult endeavor. With a scant few exceptions, we are not engineers or<br>
> scientists,<br>
<br>
</div>But programming IS a difficult endeavor. It requires careful study and<br>
a disciplined approach to development. Furthermore, livelihoods and,<br>
sometimes, lives depend on the correct functioning of software. </blockquote><div><br>The same is true of the guy that does my brakes. <br><br>One of the things that I see is that the probability that a programming effort fails is inversely proportional to its complexity. Piecing together genomes from millions of DNA fragments succeeds, while an accounting system for LA schools fails miserably. Yes there are exciting and interesting things in CS that are complicated and interesting that rise to the level of engineering or science, but most of what we do only takes an understanding of the problem, and an understanding of the tools at hand. <br>
<br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">I<br>
would say that we are most certainly engineers AND scientists. Just<br>
like engineers and scientists, we must be reasonably sure that the<br>
fruits of our labor are sound, efficient, and get the job done. After<br>
all, no one wants a bridge that collapses, is made of gold, needs<br>
maintenance every week, or does not reach the other side of the river<br>
it is suppossed to cross. Likewise, no one wants software that<br>
crashes, that unnecessarily consumes too much memory or time, that<br>
needs to constantly be updated, or does not fully solve the problem it<br>
is intended to solve.<br></blockquote><div> </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>
<br>
Does not a textbook, like HtDP, clearly bring home the point that<br>
there is a disciplined and methodical approach to programming? To me<br>
that says science and engineering.<br>
<font color="#888888"><br>
Marco<br>
</font></blockquote></div><br></div>