> code and audio samples are never available, and verbal descriptions always skip crucial details. I have no doubt that academics have a ton of expertise, but

> code and audio samples are never available, and verbal descriptions always skip crucial details. I have no doubt that academics have a ton of expertise, but their output in paper form is basically unusable, It doesn't have to be this way. Here's the process I use in my lab: 1. Every paper that makes a claim of any kind based on code contains a link to a public Git repo. 2. The paper contains the Git hash identifying the exact commit used to justify the claim. Copy-paste it from the paper into your checkout. 3. The repo may have moved on with fixes and improvements, you can have those too. If you are using version control already, it's not much work to do this. Of course, you have to be committed to making your code public.