>> When I used version
>> control for my solo research project, I used mercurial. Mercurial is not
>> just for small projects. Python uses mercurial for their open source
>> project. Facebook recently started using Mercurial instead of Git [1].
>
> Note, Python is moving to github --
>
> http://
Not *really* on topic here, but maybe we should be teaching learners `git
reflog show` [1]. Everyone messes git up sometimes; Checking the reflog is
often the best fix when that happens.
On the other hand, the output of `reflog show` is *confusing*. It would
certainly be a distraction and no one
> Dealing with git is a huge pain. When I screw something up in git, I have
> to take a deep breath, look things up on StackOverflow, and double check
> all my commands, so that I don't break something. The only reason I
> learned it was because I had to learn it to contribute to open source
> pr
On Mon, Feb 29, 2016 at 04:00:21PM -0500, Terri Yu wrote:
> Dealing with git is a huge pain. When I screw something up in git, I have
> to take a deep breath, look things up on StackOverflow, and double check
> all my commands, so that I don't break something. The only reason I
> learned it was b
Dealing with git is a huge pain. When I screw something up in git, I have
to take a deep breath, look things up on StackOverflow, and double check
all my commands, so that I don't break something. The only reason I
learned it was because I had to learn it to contribute to open source
projects. A
We spend about 50 contact hours teaching our undergraduates the basics of R.
Even that is not enough. It has been said that you need 100 hours to reach
competency, and 1000 hours to master a subject. And the next stage is 10,000
hours to be an expert..
How much time has he invested in actually
Hi all and thanks for the many responses.
My feeling reading this post was about tools (partly echoing Greg): 'we' know
'all of us' should use the appropriate tool, e.g. version control (is that what
you call the moral high-ground?). But for the novice, these tools/methods have
steep learning
> if you’re like me, you will screw up at some point, leading to some problem,
> potentially catastrophic, that you will spend hours trying to figure out.
> I’m clearly not alone... “Abort: remote heads forked” anyone? :) At that
> point, we all just call over the one person in lab who knows how to
On Mon, Feb 29, 2016 at 5:38 PM, Bennet Fauber wrote:
> Should we not mistake the tool for the task? A hammer and a
> screwdriver are different tools for different tasks, but if a
> screwdriver with a 2" shaft and one with a 4" shaft will both tighten
> and loosen the same screw, who's to say tha
On Mon, Feb 29, 2016 at 04:24:42PM +0100, Lex Nederbragt wrote:
> Hi,
>
> This blog post:
> http://rajlaboratory.blogspot.no/2016/02/from-reproducibility-to-over.html
> seems like a perfect example of how many people will think. And I can???t
> really come up with some compelling evidence to co
Should we not mistake the tool for the task? A hammer and a
screwdriver are different tools for different tasks, but if a
screwdriver with a 2" shaft and one with a 4" shaft will both tighten
and loosen the same screw, who's to say that one is the 'right' one to
use? As Greg's pointed out, we tea
One reason why I like to use graphical clients such as SourceTree for Git. It
hides much of the pain. Part of it is training and experience. It takes some
time to be familiar with appropriate record keeping in a lab book. The same is
true of using any software. I don't know why there is such an
The biggest thing I'm taking away from this blog post is that lousy
interfaces and obscure failure modes really are inhibiting adoption of
better computing practices. From the post:
if you’re like me, you will screw up at some point, leading to some
problem, potentially catastrophic, that you
>
> And I can’t really come up with some compelling evidence to convince this
> person he is (completely) wrong.
I think it's less important to read a piece like this as about specifics,
and more important to read it as being about where the messaging and
practice of 'open science' goes wrong. I
I practically disagree with every word of that blog post. Wow.
If you use version control properly it can also serve as a lab notebook. If
there are more people developing a project, it can also tell who to ask for a
reason for some specific change.
I use latex, because shuffling figures, table
On 29.02.2016 16:24, Lex Nederbragt wrote:
Hi,
This blog post:
http://rajlaboratory.blogspot.no/2016/02/from-reproducibility-to-over.html
seems like a perfect example of how many people will think. And I
can’t really come up with some compelling evidence to convince this
person he is (completely
Hi,
This blog post:
http://rajlaboratory.blogspot.no/2016/02/from-reproducibility-to-over.html
seems like a perfect example of how many people will think. And I can’t really
come up with some compelling evidence to convince this person he is
(completely) wrong.
On the plus side, they are ver
As one of the people who have gone through Insight Data Science, I can
share my experiences to this interesting discussion.
For someone looking to learn development skills, Insight really isn't the
best option. You are expected to be able to code fairly well before the
program. In addition, the wo
Hi All,
I’ve been lurking this conversation for a bit and it’s been really interesting
to hear different perspectives. I’m a geophysics PhD who is also employable /
sometimes employed as a programmer (including some closed source work right
now). This all resonates a lot with me.
I guess that
Erik,
I think you bring up a good point explicitly.
> At the same time I also agree with others in this thread who are
> skeptical about pushing this as THE way.
It isn't the only way, and not all of what one puts into GitHub should
be used. Isn't this a bit like an artist's portfolio? If one
On Sun, Feb 28, 2016 at 7:46 PM, Terri Yu wrote:
> The panelists at Versatile PhD did say that contributing to open source
> projects was a good way to develop an online portfolio. But it sounded more
> like they were just repeating conventional industry advice. It didn't sound
> like any of the
21 matches
Mail list logo
