I'm currently in the middle of a large and poorly specified project, so I feel your pain on this. However, it seems like there has to be a way to properly communicate what's needed in a small project without requiring a formal document that may take a significant amount of time for the customer to write. It also seems like these documents never include what I need on the first try, and I end up having to go back and ask for lots of clarification anyway. Sadly, most of the people who are asked to write the specs for this stuff know absolutely nothing about issues of web UI like confirmation pages and error handling, and even less about tech issues like which templating tool will be used.
Maybe the answer to this problem lies in one of the lightweight methodologies like Extreme Programming. I don't have any hands-on experience with XP (yet!), so it's hard to tell.
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.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||