>>One rule of thumb is, "If I'm thinking about features I don't need yet, I'm probably going to design and implement them wrong and will have to rework them when I really do need them."
Really? It seems to me that the advice most often given here is to "always plan ahead". Why do you reccomend something different?
I've had some personal experience with not planning ahead and having to rewrite large portions of a project and I'd like to try to avoid that this go-round.
As to the higher idea of modules in general, I hadn't planned on implementing this modules myself, but rather providing an easy to use framework that people could easily develop their own or share their developed modules. Basically what I'm looking for is a way to provide a 'patching service' to change how one or more features work, but without resorting to some projects that have patches like "go to line 23 in foo.php and replace all the lines until the next semicolon and then go to line 56 and replace two variables" and so on and so forth.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||