On Tue, Jan 01, 2013 at 09:01:18PM -0800, Chuck Guzis wrote:
On 01/01/2013 08:33 PM, Richard wrote:
In article <50E342F8.5020607 at sydex.com>,
Chuck Guzis <cclist at sydex.com> writes:
Moral: If you write throw-away code [...]
Moral: it is not throw-away code, if you don't actually throw it away.
To be honest, even my throwaway code is well-commented and clean.
That's the sign of a good coder. There is no disposable code.
What surprised me was that about half of the
instructions that I
made use of were no longer part of the current architecture. The
editor served the purpose to demonstrate some oddball instructions
(microprogramming gone mad) rather than offer a full-featured editor
for production use.
I don't have that problem. All the instructions I have used are still in the
current version. We do things differently now but the old stuff still works.
What horrified me was that someone had worked very
hard with my
original code to emulate those long-gone instructions, instead of
writing a better editor from the ground up.
People will go to almost any length to cut and paste or hack something
together so they can proudly say to management they haven't reinvented the
wheel. Usually, it's much smarter, cheaper, and even faster to engineer and
deploy a new wheel. I've thrown out a lot of other people's code against
managements' wishes, threats, etc. I have never regretted it and sometimes
the brass even thanks me for doing it afterwards. But never beforehand!
--
_ _
._ _ _ <_> ___ _ _ ___ ___ ___ _| | ___
| ' ' || |/ | '| '_>/ . \/ | '/ . \/ . |/ ._>
|_|_|_||_|\_|_.|_| \___/\_|_.\___/\___|\___.