1 / 4

Ten Commandments for Poor Technology Transfer

Ten Commandments for Poor Technology Transfer. Mark D. Hill Computer Sciences Department University of Wisconsin—Madison February 2004 http://www.cs.wisc.edu/~markhill/tech-transfer.html Acknowledgements: Multifacet Sponsors, David Patterson, & David Wood.

maille
Download Presentation

Ten Commandments for Poor Technology Transfer

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Ten Commandments forPoor Technology Transfer Mark D. Hill Computer Sciences Department University of Wisconsin—Madison February 2004 http://www.cs.wisc.edu/~markhill/tech-transfer.html Acknowledgements: Multifacet Sponsors, David Patterson, & David Wood

  2. Ten Commandments for Poor Technology Transfer • I. Always work 30 years in the future. • That way no one can prove you wrong before retirement. • II. Always start with a clean slate. • Why be encumbered by past successes? • III. Remember that publishing papers is the end of research and technology transfer. • If people don't have time to read your papers, their loss. • IV. Always remember that you are smarter than people in industry. • You balance research with teaching a few classes, while they only make systems with multi-million-transistor chips. • V. Never give talks in industry. • They might make you wear a badge.

  3. Ten Commandments for Poor Technology Transfer • VI. Never hold industrial affiliates meetings or get feedback from industry on your research agenda. • Industrial people know little about real computer architecture. • VII. Never allow your students to do internships in industry (or, even worse, take a sabbatical there). • Industrial people might get to know your students and corrupt them (or corrupt you!). • VIII. Never consult for industry. • One might spend time on problems people care about. • IX. Protect your intellectual property by not telling industry (or anyone else) what you are doing until patents are filed. • Lawyers are more fun than your computer architecture colleagues. • X. When meeting industrial people, just ask for money and don't waste time building long-term relationships. • Relationships are for people in the humanities

  4. Ten Commandments for Poor Technology Transfer • I. Always work 30 years in the future. • II. Always start with a clean slate. • III. Remember that publishing papers is the end of research and technology transfer. • IV. Always remember that you are smarter than people in industry. • V. Never give talks in industry. • VI. Never hold industrial affiliates meetings or get feedback from industry on your research agenda. • VII. Never allow your students to do internships in industry (or, even worse, take a sabbatical there). • VIII. Never consult for industry. • IX. Protect your intellectual property by not telling industry (or anyone else) what you are doing until patents are filed. • X. When meeting industrial people, just ask for money and don't waste time building long-term relationships.

More Related