Tagged: research in action

Research in action at University of Toronto on March 24

And it is happening again. Research in action presented by the department of Computer Science at the University of Toronto is taking place on March 24, 2009 from 1 PM to 6 PM. And of course as all previous years, the website describing what is usually an awesome get together and demonstrations by awesome group researchers and projects is pathetic.

I have been saying for 3 years now that if you want industry relations and collaborations you are gonna have to do a little bit better than this:

The department hopes “Research in Action” will provide a catalyst for new partnerships- and play a role in building the City of Toronto as a leader in high technology.

Bla bla bla. Please give me the following:

  • A description and links for each project that is in the showcase. I want to read the project description not google it from the description provided in your advertising postcard
  • A link to the teams working on the various project. I mean how can I develop relationships with folks I don’t know? Can I please get to know you? Links, profiles, videos, anything?
  • Linkable descriptions for the projects: If you want to spread the word, than I need links to forward to colleagues who may be interested in some of the projects you will be showing. I know my colleagues, I also know what they are interested in. I can get them to you but only if I have what I need. Links = getting the word out = participation = building a community. It is  not complicated.
  • Stop sending out postcards. And no, I don’t need a description of last year’s projects on this year’s website. I need this year’s descriptions.

Ok, folks, please get to it. Pronto. Please help me help you. Oui?

Now that my rant is out of the way, here are the details for attending (and yes, you will meet some great folks!): Tuesday March 24, 2009; 1 PM to 6 PM at the Bahen Centre for Information Technology; 40 St George Street, Room 3200. Registration and further *limited* details here.