From: Pjotr Prins <pjotr.public12@thebird.nl>
To: Marco van Hulten <marco@hulten.org>
Cc: Guix Devel <guix-devel@gnu.org>
Subject: Re: good practices in science
Date: Fri, 3 Apr 2020 08:00:39 -0500 [thread overview]
Message-ID: <20200403130039.lgdr5wdmm6as3wpr@thebird.nl> (raw)
In-Reply-To: <20200403135421.5f800ffa@hulten.org>
Dear Marco,
I don't think this is the place to discuss the ins and outs of
science. The scientific community and arena can be frustrating and I
would say (i.e., as an opinion) that you should only work in science
if the subject itself grabs you. I left the software industry for
biology 15 years ago and have not looked back. I love my work.
We are organizing a COVID-19 biohackathon coming week for free
software and free data. Feel free to watch and join. We are
using some proprietary tools - usually they come with lab protocols -
such as sequencers - though for me I try to avoid them as much as
possible, and we can create free alternatives. But overall I am pretty
happy with what I can do in science with free software and I only
write free software! Let free software rule.
I am excited about free hardware developments and Linux phones.
Hopefully we'll get GNU Guix on those soon.
Pj.
next prev parent reply other threads:[~2020-04-03 13:07 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-03 11:54 good practices in science Marco van Hulten
2020-04-03 13:00 ` Pjotr Prins [this message]
2020-04-03 13:56 ` Pierre Neidhardt
2020-04-03 14:28 ` Konrad Hinsen
2020-04-03 16:11 ` Cook, Malcolm
2020-04-03 16:20 ` Pierre Neidhardt
2020-04-05 9:55 ` Marco van Hulten
2020-04-05 13:50 ` Bijan
2020-04-06 8:18 ` Pierre Neidhardt
2020-04-06 10:01 ` Bijan
2020-04-06 15:09 ` Konrad Hinsen
2020-04-06 18:51 ` Bengt Richter
2020-04-07 8:37 ` Konrad Hinsen
2020-04-07 17:51 ` Bengt Richter
2020-04-07 22:00 ` bijan ghavami-kia
2020-04-08 7:30 ` Konrad Hinsen
2020-04-12 17:02 ` Pierre Neidhardt
2020-04-06 16:34 ` Bengt Richter
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200403130039.lgdr5wdmm6as3wpr@thebird.nl \
--to=pjotr.public12@thebird.nl \
--cc=guix-devel@gnu.org \
--cc=marco@hulten.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.