NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.
All the Perl that's Practical to Extract and Report
use Perl Log In
chromatic (983)
chromatic
(email not shown publicly)
http://wgz.org/chromatic/
(email not shown publicly)
http://wgz.org/chromatic/
Blog Information [technorati.com]
Profile for chr0matic [technorati.com]
Monday February 23, 2004
11:01 PM
On Technical Writing: Gerunding It Up
Some days, I'm tempted to propose a book on effective technical writing. Then I realize that my editors could produce examples of my bad prose. Also, the writers I work with are overwhelmingly quite nice, intelligent, and fully capable of fixing most minor issues with better feedback.
Still, it's nice to believe that the world is a better place for me having changed a heading from "Using $application To $verb $task" to "$verb-ing $task".
What's important? Is it the tool? In this case, no. It's getting something done. How is less important than what.
You have limited space in headings. Use it wisely.
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
Full
Abbreviated
Hidden
Loading... please wait.
--Larry Wall in stab.c from the perl source code
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
This presumes.... (Score:2, Funny)
Re:This presumes.... (Score:2)
not always (Score:2)
"Writing games with SDL"
vs
"Using Perl to write games with SDL"
- ask
-- ask bjoern hansen [askbjoernhansen.com], !try; do();
Re:not always (Score:1)
True, though I might write the second as "Writing Games with Perl and SDL". "Using" can be pretty weak.