On Sun, Apr 17, 2016 at 10:45 AM, Koeng <koeng101@gmail.com> wrote:
I think that equating "It just pastes sequences together" to "I just extracted teh DNA" to be flawed logic. Saying "the cloning was simulated with snapgene 3.1.2" is just about as good as saying "the DNA was extracted with the Qiagen miniprep kit", in which the latter is sufficient for a user to go and find out how the protocol was done (and vice versa).
Blackboxing is fine if there is no alternative, but I would say there should be effort to actively try and 'unbox' these items/processes. The mini-prep might have been discovered by academics, published on, then improved by commercial industry... only to later be dissected by academics again when they were trying to improve/reverse-engineer things. (the reverse-engineering effort is supposed to be saved by patent disclosure... but... well... we all know those have their issues in practice and in society)
Science is definitely about being open and well documented, so things can be reproduced. Good, well quality-controlled black boxes can still fit in to this pipeline and accelerate the time-to-success of an experiment.
When a miniprep is done with 2 different kits, the outcome can be very different.
Which can be a MAJOR problem if the company that produced a closed-source/blackbox kit goes bankrupt or gets bought by another company that then discontinues that kit with no alternative. For all we know, the magic "spells" in children's cartoons that call for "frog extract" could have actually worked, at some historical time with some historical and specific frog and a specific extract technique. For the present-day though, this is just a junk recipe that we all "know" is fake/fictitious. (will the biochemists who did their PhD dissertations on magic frog-guts extract please stand up!)
I think the big difference, as a scientist/engineer is whether the solutions available meet my needs. As a decent programmer (and so called software engineer, by day, these days) I can tweak software to add new features sometimes within minutes of getting the source code. This is not happening with any decent commercial software tool through feature requests unless you've got thousands of dollars on the line and are willing to make it well worth their time. Pretty much the same thing about new features that are specific to your workflow, or maybe are experimental ideas. Another issue which I can attest to is, what if you have some technique which doesn't integrate with existing closed-source tools, and which you cannot even PAY the closed-source company to help you with, because you don't want to risk leaking ANY details about your own Intellectual Property.
I was just tweaking some open-source scientific simulator GUI code last night, it felt really good.
-- You received this message because you are subscribed to the Google Groups DIYbio group. To post to this group, send email to diybio@googlegroups.com. To unsubscribe from this group, send email to diybio+unsubscribe@googlegroups.com. For more options, visit this group at https://groups.google.com/d/forum/diybio?hl=en
Learn more at www.diybio.org
---
You received this message because you are subscribed to the Google Groups "DIYbio" group.
To unsubscribe from this group and stop receiving emails from it, send an email to diybio+unsubscribe@googlegroups.com.
To post to this group, send email to diybio@googlegroups.com.
Visit this group at https://groups.google.com/group/diybio.
To view this discussion on the web visit https://groups.google.com/d/msgid/diybio/CA%2B82U9J2G%2BZR_W6gPxUvgnamZjfS9AFaNaZ6PXNpYQNWWKPnkg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.






0 comments:
Post a Comment