On Tue, 17 Jan 2012, richo wrote:
I'm very aware that the code I produce for $WORK is very different to
code I write in my own time. Code for $WORK is wrapped in test cases,
clean, neat and well documented.
code I write in my own time tends to be hackish, incomplete totally
undocumented and ludicrously easy to break because I'm intrigued by
implementing a single interesting figure that has my attention, or to
see whether or not a concept is technically feasible.
====================
code i write for work is (typically) under pressure of time and money.
sometimes good documentation is more important than good code, sometimes
documentation is irrelevant. at work i've been complimented for getting
things done on time and under budget, but NEVER for getting it done right.
code i write in my own time is art. i wouldn't write a sloppy song in my
spare time, and i don't write sloppy code in my spare time.
--
...atom
________________________
http://atom.smasher.org/
762A 3B98 A3C3 96C9 C6B7 582A B88D 52E4 D9F5 7808
-------------------------------------------------
A student asked his old Sufi Master if he should tie up
his camel for the night, so that it wouldn't wander
away while they were sleeping or if doing so was an
insult to God. Should he leave the camel untied to
show his trust in God that the camel wouldn't run away?
The Master replied "Trust God AND tie up your camel."
_______________________________________________
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
