[aab0]

All valid advice, but god is some of it depressing. Papers can be evaluated by flipping through and looking for pretty graphs and equations. Incremental, replication, or comparison work is discouraged. Never include the dead ends or what didn't work. Get into only the elite colleges and betwork at conferences as much as possible - it's not what you know but who you know. Hype up and make your paper as sexy and short as possible. Tell a story. Good teaching, blogging, and sharing software probably hurts you.

[wodenokoto]

> Good teaching, blogging, and sharing software probably hurts you.

Karpathy is pretty famous for his blogging and open software. His code and blog post about recurrent neural networks practically got him a language model named after him.

He also recommend you to release code in this article, so I'm not really sure what you are getting at.

[aab0]

> Karpathy is pretty famous for his blogging and open software.

Yes, he's famous for that, but that didn't earn him his PhD nor would it have gotten him tenure. As he remarks about his teaching of his course, him doing a good job actively worked against him because... it's not writing a sexy new paper or networking.

> He also recommend you to release code in this article, so I'm not really sure what you are getting at.

Releasing code isn't the same thing as creating polished end-user applicable stuff on the level of char-rnn. In ML, you're increasingly expected to at least chuck over the wall a barebones implementation to demonstrate it works at all, but there is no expectation that it will be generalized, well-written, or polished, or maintained, and typically they are not. (Most ML releases I've looked at are kind of horrifying from a software engineering perspective. Just thinking about improved-gan makes me shudder.)

[wodenokoto]

Most of the "Release your code" section is about how you should put your code in public because in makes you do the extra effort to write a better implementation.

> but that didn't earn him his PhD nor would it have gotten him tenure.

He doesn't have tenure. He works at a private organisation. We don't know how he landed it, but I think his internet famous helped.

In the "Don't play the game" section, which is where I think you got the "don't teach"-thing, he writes:

> but I did them anyway, I would do it the same way again, and here I am encouraging others to as well.

How you read this as anything but an encouragement to teach, write software and blogging is a mystery to me.

[baby]

> Incremental, replication, or comparison work is discouraged

I haven't read that. The author says that poorly incremental work is discouraged.

> Get into only the elite colleges and betwork at conferences as much as possible

It's about being part of the community, having brilliant people around you to push you and exchange ideas with, meeting people to collaborate with...