For me, that point is when I've grown tired of investing my time in band-aid code. Hopefully this comes early in the design process, if not it might be more fruitful to slowly, gracefully, "steer" the project in the new direction.
In the case of
Hatchet, I learned soon enough that the advanced sorting/search/statistics features that users were begging for would be damn near impossible using the existing design. Fortunately, the project was immature enough that it wasn't too harsh an effort to ask folks to move from the old design to the new SQLite-based engine. Yes, it required that they basically un/re-install the whole shmere, but it also gave them a better upgrade path with exciting new features (that I could incorporate without fear of burnout).
In short, there is no easy answer, but you'll probably know when the time is right. Just don't be afraid to jump because you might piss off users. Tomorrow might be a day too late. ;-)
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:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, 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, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.