At 08:36 +0100 8/9/05, Paul Martin wrote:
Well, I'm not sure about that one. I'm on an Electronics & Software MEng
course and it's far from hard! Each year I get more and more free time, and
talking to CS students the only reason why they end up working for longer is
because the university hasn't taught them the correct ways to program, or
more importantly to plan to program. I had the same in my first year.
A small piece of analysis first is worthwhile. Others have suggested
a "rapid prototype" approach. Projects often benefit from a small
"back of the envelope" calculation to see if the code would run in
reasonable time (order n squared or better??).
If you plan a little and programme a little and plan some more, then
that is an approach (is that the waterfall model?)...
"Extreme programming" is my favoured approach at the moment :-)
http://en.wikipedia.org/wiki/Extreme_programming
I have heard of "third normal form", but as a mathematics graduate, I
have never actually touched one.
Gordo
--
"Think Feynman"/////////
http://pobox.com/~gordo/
[EMAIL PROTECTED]///
-
Sent via the backstage.bbc.co.uk discussion group. To unsubscribe, please
visit http://backstage.bbc.co.uk/archives/2005/01/mailing_list.html.
Unofficial list archive: http://www.mail-archive.com/[email protected]/
