While I agree with all that's in your manifesto, it's way too pompous. Spend more time thinking of small, concrete steps that will show obvious benefit.
dragonchild and
brian_d_foy both had some excellent comments. I suspect most of your programmer peers have not worked
together on projects. Besides testing, spending the time to define APIs is critical. In my view, the more top level review a project gets, the better and quicker its success. And no, I don't consider management "top level", although they can often be included in another buzzphrase that's important, "Customer-centered solution".
Even if you just improve your team-based development practices, you'll be better off. Add to that a clear and complete specification, and you'll be worldbeaters!
Don Wilde
"There's more than one level to any answer."
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.