11–20 of 52 posts
We don't need faster scientific writing We need slower scientific writing. Edit: While I understand policy involved, apologies, I'd contend 'shallow'. Not lengthy? Sure. But the point was made enough @kbk et al. got it
> We are scientists. We don’t blog. We don’t twitter. We take our time.
We don't need faster scientific writing We need slower scientific writing. Edit: While I understand policy involved, apologies, I'd contend 'shallow'. Not lengthy? Sure. But the point was made enough @kbk et al. got it
We don't need faster scientific writing We need slower scientific writing. Edit: While I understand policy involved, apologies, I'd contend 'shallow'. Not lengthy? Sure. But the point was made enough @kbk et al. got it
There are however many other contexts where I would argue speed and a simple UX makes a big difference.
* Notes that need to be taken on the fly: class notes, lab notes, field observations, general notes
* Prototyping, brainstorming, ideation sessions, especially collaborative ones
* Drafting outlines
* Creating presentations on work you've already completed
* Doing schoolwork, such as assignments or lab reports
* Creating teaching material on content material you're a subject matter expert in
That's a few examples but there are plenty more. The goal isn't to rush the scientific process. The goal is to have a tool that doesn't get in your way and enables speed-of-thought writing for science. This can be helpful in many ways, especially for students, but also for scientists.
if you want this to go main stream, you have to at least make some parts of it open source
Is it possible to embed the stempad editor in something like a react app?
We don't need faster scientific writing We need slower scientific writing. Edit: While I understand policy involved, apologies, I'd contend 'shallow'. Not lengthy? Sure. But the point was made enough @kbk et al. got it
I totally get where you're coming from, maybe I could have worded the title differently. In contexts such as publishing scientific papers and journals, patience and attention to detail are really important. There are however many other contexts where I would argue speed and a simple UX makes a big difference. * Notes that need to be taken on the fly: class notes, lab notes, field observations, general notes * Prototy…
During my Master's or PhD I would have agreed with the "slow science" sentiments here. These days I want to get things done and work with collaborators.
My biggest frustration as an academic was reproducibility of papers I was reading. The pdf is such a useless medium for information transfer and the academic publishing industry is a complete racket where all the value is generated by the authors and reviewers who work for free and have to pay (in most cases) to have their work accessible freely to the public. I would love to see this turn into a default way to publi…
If you can consistently locate and run academic publication code without direct help from the authors, you are The Chosen One.
[edit]
In seriousness, reproducibility is also my biggest concern. Scientific/academic publishing could do a lot better than rendering pretty static documents - we can provide the data, code, version control, and build processes which produced the paper so anyone can reproduce what they see in the paper. AND we could host them together so they're bidirectionally linked, to facilitate other scientists building on top of our work.
That could be our future, with the right incentive structures in place.