Bob La Quey wrote:
BTW, I hear this "programming in anger" phrase from time to
time. The phrase strikes me as juvenile.
I'm one of the primary promulgators of that phrase.
It does not mean you do something while you are angry.
It means that you do a significant project in which you will have to
confront both the benefits *and* the problems of whatever tool you are
using.
Generally, when you have "programmed in language X in anger" you can now
talk intelligently about the ways in which "language X sucks".
In spite of their inexperience, my CS530 class from last year had to
write about 4000 lines of code to build an assembler. Afterward, they
had *very* clear ideas about what parts of Java suck.
100+ lines of code for yourself is not programming in anger.
1000+ lines of code that you have to support and/or extend for 6 months
is probably right around the boundary.
For me, nowadays, it takes about 3000-4000 lines of debugged code for me
to feel that I have started "programming in anger".
-a
--
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
