comment on

I relate a lot to fever's recurring thought. I have inherited tons of hacked-up, dangerously insecure, bloated Perl scripts, and I do not ever want to do that to anyone else.

Like fever, I want to make future developers' jobs easier. But I want to make their jobs so much easier, they won't even realize it was easy. By designing systems, programs and scripts that anticipate future changes, future coders will be able to extend and modify without putting too much thought into the existing code and focus solely on what they're trying to do.

Current mantra: What would I think of this code if I needed to make a change and I wasn't a Perl expert?

Once my current mantra is absorbed into my subconscious sufficiently, I'd like my next mantra to be: Can I think abstractly enough about this task that I could write a CPAN-worthy module for it?

--Dave

In reply to Re: Re: Programming Mantras by redsquirrel
in thread Programming Mantras by dws

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


We don't bite newbies here... much
	PerlMonks