Hi All,
when deciding to use the notebook or the editor / CLI approach, I
think it's worthwhile to consider which tool workshop participants
are anticipated to use in their "real work" after the workshop.
There's no doubt that taking care to eliminate any unnecessary
stumbling blocks from the
by the takers themselves and
open in that sense.
Best regards, Jan
> - Jory
> ___
> Discuss mailing list
> Discuss@lists.software-carpentry.org
> http://lists.software-carpentry.org/listinfo/discuss
--
+- Jan T. Kim -
software-craftsmanship/list_prefs/?pref=2
Don't send me mailing list messages
https://www.meetup.com/london-software-craftsmanship/list_prefs/?pref=0
Meetup, POB 4668 #37895 NY NY USA 10163 | supp...@meetup.com
- End forwarded message ---
Hi Titus and All,
On Mon, Nov 14, 2016 at 04:57:52AM -0800, C. Titus Brown wrote:
> On Mon, Nov 14, 2016 at 09:34:09AM +0000, Jan T Kim wrote:
> > When using the "top down" approach of starting with a prepared piece of
> > working code, I'd suggest that learners shoul
scores in a LaTeX
> document and have it clickable in the resulting PDF.
>
>
> --
> The University of Edinburgh is a charitable body, registered in
> Scotland, with registration number SC005336.
>
>
>
> __________
Dear All,
On Fri, Nov 28, 2014 at 07:13:24PM -0500, Greg Wilson wrote:
Hi Kai,
Our experience is that trying to get learners who have little
previous training in programming all the way to defining classes in
half a day (which is all the time we usually have for Python in our
workshops)
