Submitting a Bibliography Entry

Why

• Because it's there.
• It's easier for other people to find stuff here, so it helps other people do their work.
• People doing related work will write you and tell you what they are doing --- so it helps you do your work!
• It helps make you famous.
• It helps make the UW CS&E department famous.

What You Need

• A one-line summary, such as the title or anything else descriptive.
• The abstract, if you have one.
• A bibliographic citation, refer or BibTeX preferred.
• A URL pointer to PostScript(tm) or another online form, if you have one.
• A URL pointer to you and your coauthors, if you (they) have one.

You don't need to have all of this info to submit something -- just the name and a citation will do, but more is better.

Sending It In

Example

Studying how users learn from examples

Many tasks are easier when the user copies an example and
modifies it for their particular situation.  This paper
studies users who where given manual pages, users given
examples, users given both, and users given none at all.
Both time-to-completion and user feedback results show
that even when the examples do not closely match the
intended tasks, they still dramatically improve both
productivity and perception of the tool's utility.

@techreport{NOP:99,
    author = {Should Be and Hasn't Been},
    title = {Examples: Learning by Manipulation},
    number = {53-14-ZZ},
    institution = {University of Washington, Department of CS&E},
    month = {Nobruary},
    year = {2953}
}

ftp://ftp.cs.washington.edu/tr/2953/14/UW-CSE-53-14-ZZ.PS.Z

http://www.cs.washington.edu/homes/shoobe
http://www.cs.okiboji.edu/homes/habbie

Samples

• Limitations of Cache Prefetching on a Bus-Based Multiprocessor
• Reducing False Sharing on Shared Memory Multiprocessors through Compile Time Data Transformations
• Shade: A Fast Instruction-Set Simulator for Execution Profiling

Questions?