Book recommend. Rapid Development
by Steve McConnell
Actually I can heartily recommend everything that I have
ever read that he wrote, but that book addresses the topic
at hand. Including why a spec is nice, what a good spec
should be, why you are unlikely to get one, what can
(sometimes) be done about that, etc. A lot of this may
sound like management theory. But it is really addressed
as management theory for a technical lead (a role you can
find yourself being thrown in unexpectedly - or be in by
default by virtue of being the only developer) who would
rather be a programmer but needs to know what works out of
Another approach to the issue of the fact you will never
get a spec is to try some of the ideas from
out. If you search you will also find some previous
discussions of that.
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.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||