comment on

A former employer preferred the acronym "LAW" (Least Amount of Work) over "KISS." ¹

On its face, it seems like pure semantics. However, there is something to the mental shift. First, few people enjoy being called stupid. Second, if you reduce the amount of work needed to create, maintain, or use something, then you've done a good job. This is the heart of Laziness as a Perl virtue. You don't take shortcuts in your work, you work to provide shortcuts. After all, if software doesn't make something easier, cheaper, or better, then why are we writing it?

Personally, I'd go with keeping the fgrep/fmap/fdo functions and providing an example for your "fgrep_flat" function in your Usage/Examples POD.

--f

¹ - He also preferred to say "Well, if I win the lottery..." instead of "Well, if I get hit by a bus..." He had this thing for putting things positively. At the time, I tended to get annoyed at what I called "optimistic sugar-coating;" however, I've since begun to realize that while it's good to plan for the worst, you don't necessarily have to be a sourpuss about it. YMMV.

In reply to Re: KISS vs Feature set by footpad
in thread KISS vs Feature set by Masem

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.


Come for the quick hacks, stay for the epiphanies.
	PerlMonks