RE: A cautionary tale: Portfolio Assessment

[KMcLauchlan -at- chrysalis-its -dot- com]

Whirlistas,

Is it a common practice to include in your documents 
(somewhere in frontmatter, I assume) what tools were 
used?

Just about the only place I really expect to see such 
info is in books about typesetting and layout, and 
manuals for layout and publishing tools.

Is there any reason to include such info in a hardware 
or software install guide?

/kevin

John Posada [mailto:jposada01 -at- yahoo -dot- com] was heard to intone:

> A portfolio is not eveluated in a
> vacuum, but with the conditions under which it was created. I want to
> be able to answer the following question:
> 
> "Gee...this piece  doesn't seem as polished as some of the others. I
> notice it was done in Frame...it must mean that you have limited
> experience in Frame?." 
> 
> With the answer, "No...what you see is is a 30 page user guide that
> was created in 24 hours 
[snip]

 

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Collect Royalties, Not Rejection Letters! Tell us your rejection story when you 
submit your manuscript to iUniverse Nov. 6 -Dec. 15 and get five free copies of 
your book. What are you waiting for? http://www.iuniverse.com/media/techwr

Have you looked at the new content on TECHWR-L lately?
See http://www.raycomm.com/techwhirl/ and check it out.

---
You are currently subscribed to techwr-l as: archive -at- raycomm -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- raycomm -dot- com
Send administrative questions to ejray -at- raycomm -dot- com -dot-  Visit 
http://www.raycomm.com/techwhirl/ for more resources and info.