This is that lesson for getting started with OpenRefine. http://datacarpentry.org/OpenRefine-ecology-lesson/
129 karma · joined March 19, 2009
This is that lesson for getting started with OpenRefine. http://datacarpentry.org/OpenRefine-ecology-lesson/
There’s also an Avida-ED version designed for classroom use.
http://jupyter.readthedocs.io/en/latest/install.html
It does work better for people to install Jupyter with Anaconda, rather than use virtual environments, because there's not the overhead of also having to learn about virtual environments. People tend to think of them as just associated with the class and don't use them as much for their own work outside of the workshop or course.
I've seen this comment before. It emphasizes the need for more founders with diverse backgrounds. More types of problems solved and more opportunities to reach new markets.
There are a few elements they emphasize.
One is what the blog format enables that traditional publishing doesn't support. Those are things like having real-time feedback and comments, being able to version and making the blog post interactive, rather than a static document. Another element to the format is a lack of gatekeepers, so it can be quickly disseminated and disseminated by anyone, so there aren't barriers to participation in the scientific discourse.
Another is norms and expectations. In blogging, it is more the norm that data and code are open. Open is still possible in traditional publishing; it just isn't yet the norm. A new format however, enables new norms and it's easier to set them from the start, than try to revise existing ones.
Finally, there's the element of 'correctness'. Going through peer review and being in a traditional journal certainly doesn't ensure that the paper is correct. You can just look at retractions to see that http://retractionwatch.com/2011/08/11/is-it-time-for-a-retra.... However it would be interesting to see more evidence around whether the blog format does ultimately lead to more 'correct' conclusions, on the whole, and not just for the posts that lead to a lot of discussion.
Most scientific software probably doesn't already have all these components in place. It would be a great problem to have, to have a flood of submissions!
Criticism passes judgement — Critique poses questions; Criticism finds fault — Critique uncovers opportunity; Criticism is personal — Critique is objective; Criticism is vague — Critique is concrete; Criticism tears down — Critique builds up; Criticism is ego-centric — Critique is altruistic; Criticism is adversarial — Critique is cooperative; Criticism belittles the designer — Critique improves the design
The author also highlights the importance of a good Board. Often not enough thought goes in to selecting a Board. A Board that believes in the idea and the people, has a diversity of perspectives and backgrounds, and has a relationship with the founder/CEO where there's room for disagreement and discussion can make all the difference.
I didn't know about the Amazon trade-in program. That sounds great for books and games.