Good conversation!
The way I've always taught it as part of an R-shell-git-R sequence is to
do a full half-day with git from the command line, then in the second R
segment (end of second day), move over to using git in RStudio.
That way it reinforces the concepts learned on the command line in a new
context, and shows learners an IDE-based workflow that they are (if they
stick with R) likely to use in the future. It lowers the re-activation
energy needed to apply the use of version control once the workshop is
over, but without risking the misconception that you can only use git
from within RStudio.
Best,
Naupaka
On 14 Mar 2018, at 10:24, JACKSON Michael wrote:
Hi,
I second this. It can be challenging enough getting over the message
that Git is not GitHub or that Jupyter is not Python, for example. I
want attendees to leave with an awareness of underlying concepts and
to use them in the tools that they will be required to use on their
future projects. Especially as the choice of tools, or languages, to
use will frequently be made by others. Once they've learned the
underlying concepts, the specific tools will be more straightforward
for them to learn.
cheers,
mike
________________________________________
From: Discuss <[email protected]> on behalf
of Jan T Kim <[email protected]>
Sent: 14 March 2018 15:32
To: [email protected]
Subject: Re: [Discuss] Git lesson through RStudio?
Hi All,
while I understand the attraction of minimising the number of systems
and UIs used in a workshop, I think it should also be considered that
the majority of learners will eventually move to other systems.
The focus of workshops should therefore be on enabling learners to do
what they need, independently of specific tools, UIs etc. From this
perspective, some exposition to different UIs is a key value provided
by workshops, rather than a distracting effect to be engineered away
to any extent possible.
Best regards, Jan
On Wed, Mar 14, 2018 at 02:39:35PM +0000, Abhijit Dasgupta wrote:
Thanks for the feedback!
One of the reasons RStudio is attractive is that the workshop becomes
immersive and unified in one IDE.
The git interface is pretty good, and merge conflicts are dealt with
much
as a standard text editor would, so standard but nothing as nice as
Atom.
For beginners, and intermediates, it appears sufficient. There hasnt
been
major drift across RStudio versions in a while, so even with a 6
month old
version, it is fine (key being having RStudio > version 1.0).
The RStudio interface also comes with a terminal built in. I'll check
what
it is for Windows, but that, I think, simplifies a lot of the issues
with
installing and using shell on Windows boxes, again simplifying the
workflow.
Still thinking aloud, but the more I think about this, the happier
I'm
getting :)
On Wed, Mar 14, 2018, 10:31 AM Raniere Silva <[email protected]>
wrote:
Hi Abhijit,
The Software Carpentry "bylaws" only mentioned that you must teach a
version control system. It could be Git, Mercurial, SVN or another
one.
In terms of learners experience during the lesson, I was helping on
a web
development workshop and I noticed that different users had
different
graphical user interfaces of GitHub Desktop client which made very
hard to
help learners. I don't use R Studio's Git interface so I don't know
how
often it change that will impact the workshop, for example, if one
of the
learners installed R Studio 6 months ago and didn't updated it for
the
workshop how much the graphical user interface will be different?
Another
point, is how the conflict resolution works in R Studio?
Cheers,
Raniere
_______________________________________________
Discuss mailing list
[email protected]
http://lists.software-carpentry.org/listinfo/discuss
_______________________________________________
Discuss mailing list
[email protected]
http://lists.software-carpentry.org/listinfo/discuss
--
The University of Edinburgh is a charitable body, registered in
Scotland, with registration number SC005336.
_______________________________________________
Discuss mailing list
[email protected]
http://lists.software-carpentry.org/listinfo/discuss
_______________________________________________
Discuss mailing list
[email protected]
http://lists.software-carpentry.org/listinfo/discuss
