A shortened form of the manifesto principles are as follows:
Open over closed: Scientific code should be open when published, so it can be reviewed and re-used.
Incorrect code results in incorrect science: Reviewers should review code as well as the the subject matter.
Code for the future: Good coding practices make for better science!
Availability over perfection: It’s easy to be tempted to hide code until it’s “perfect” – share early.
Code deserves credit: software authors should gain credit for writing code and not just papers.
@codeisscience manifesto “open over closed”; “code for the future”; “incorrect code==incorrect science”; “availability over perfection”; “code deserves credit” @yoyehudi presenting amazing things #GCCBOSC
Overall, my talk seemed to go well, if Twitter is any judge. I only had a seven-minute lightning talk slot, so I didn’t have quite enough time to give it as full a background as I’d have liked, nor cover future plans. Still, I was incredibly pleased to get the chance to share it at GCCBOSC, and I hope others feel similarly about scientific code.