J/K but I'm really am in the RL opposite situation. I'm in charge of setting the rules and writing the specs (as well as writing about 95% of the code, welcome to the world of startups) and I'm just not sure where to go with it all.
Taint is a must, CPAN is a must, writing modules vs. hacking code is a must. The problem is the spec changes every day as we think of new things and the priorities are all over the map. One day I write documents for a big presentation, the next day billing code, the day after that I tinker with modules that I want to rebuild the hack jobs I kicked out last week on... Some days I'd rather have unreasonable, blind bosses and a clear direction of failure to head in. Not many tho and whenever it seems bleakest Ovid seems to cheer me back up. =)
--
$you = new YOU;
honk() if $you->love(perl)
In reply to Re: What quality is your company's code?
by extremely
in thread What quality is your company's code?
by Ovid
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |