We want to know what you think!

Thursday, October 23, 2008: 4:00-5:00 p.m.
Paul G. Allen Center

Academic and Industrial Partnerships in HCI & Design (CSE 403)

dub (see dub.washington.edu) is a cross-campus coalition of over 30 faculty and 50 graduate students exploring the future of research in human-computer interaction and design. One of the important attributes of the Puget Sound area is the large number of companies producing research and products that are dependent on high quality and innovative product, interface, and interaction designs. The purpose of this feedback session is to hear how our affiliates can take a stronger role in this new campus activity:

Relevant topics include:

  • Does your company need to hire talented engineers and designers that have a strong combination of computing, interaction design, and usability skills?
  • How are our existing educational programs meeting or not meeting these personnel needs?
  • Would your company be interested in hiring engineers and designers with a new MS interdisciplinary degree in HCI & Design?
  • What should these engineers & designers know how to do?
  • How might your company collaborate with a new MS program in HCI & Design?
  • Would they be interested in helping support 6-month long team design/prototyping projects? Would members of your company be interested in mentoring students and teams?
  • How might your company impact our research agenda in HCI & Design?

Mainstream Parallel Computing (CSE 691)

The computer industry has moved toward a future of desktop computing that relies on parallelism (multicore/manycore) for increased performance. While UW is actively researching hardware and software innovations to help this fundamental transition, the purpose of this feedback session to hear how our affiliates are (or are not) attacking this changed and changing landscape.

Relevant topics include:

  • Does your company have a coordinated strategy toward desktop parallelism?
  • How do you think desktop parallelism will change software development over the next n years?
  • What are the successful techniques you use for exploiting parallelism and avoiding its pitfalls?
  • Is programming a quad-core fundamentally different than programming a 64-core, or will things "just scale up"?
  • If you could change something about the platforms for multicore computing you have seen, what would it be?