A colleague asks what he should tell his students when they say:<\/p>\n
What’s the point of formalizing all of this into such a long dense 10-page paper? why can’t we just put up our code and demos on github, maybe write a blog post on it, make some youtube demos and give talks, etc.?<\/p><\/blockquote>\n
Tell them they don’t want to end up like me!<\/p>\n
Blog posts and demo videos don’t stick. I’ve been doing them for years and almost no one pays any attention. They don’t get cited by related work. It’s like they never happened. Writing\u00a0a paper sucks, and you have to do a ton of bullshit to get it accepted, but it has two crucial benefits:<\/p>\n
\n
- \n
\n
- You need a really deep dive to explain something new or complicated. Someone can closely study a paper and get 10x more information than any slide deck or video.<\/li>\n
- Other researchers doing related work are obliged<\/strong> to read your paper if it is peer reviewed. Let’s face it, that is usually the only reason a paper gets read. Researchers are not obliged to cite non-peer-reviewed content, so it gets ignored.<\/li>\n<\/ol>\n<\/li>\n<\/ol>\n
Let’s see if I can take my own advice!<\/p>\n","protected":false},"excerpt":{"rendered":"
A colleague asks what he should tell his students when they say: What’s the point of formalizing all of this into such a long dense 10-page paper? why can’t we just put up our code and demos on github, maybe write a blog post on it, make some youtube demos and give talks, etc.? Tell … <\/p>\n