> The other talk is a shorter talk (~20 minutes, incuding Q&A) about > the > differences teaching Python via straight command line compared to > teaching > from the Jupyter notebook. When I've taught for the Carpentries, > I've > always used Jupyter. In other contexts, I've taught strictly from > the > CLI. I'm curious to know if others have taught in both ways (either > for > the Carpentries or in other circumstances) and what you've thought of > it. > Advantages/disadvantages? What you like and don't like about Jupyter > and > CLI environments?
Some instructors already answered Maneesha's question but I want to add my two cents. Before I add my two cents, when I wrote CLI you show read Jupyter command line instead of the standard Python command line because as you know the standard Python command line "sucks", e.g. it doesn't support auto-complete and don't let you access the previous command. In all the workshops that I taught, I always had at least one student who was taking notes with paper and pen. Is completely out of scope of this email discuss "analog" vs digital taking note tools but I would say that we should expect that some learners will try to keep their own personal notes despite our use of Etherpad/Google Docs/... and I think that among "IDE specific select and run", Jupyter Notebook and nano+CLI the best experience to take personal digital notes and run the commands is "IDE specific select and run". By "IDE specific select and run" I mean that learners can type freely at a text file what they want, they don't need to worry about comment notation, but they can select the command they type and by pressing some keys they will run that command. Unfortunately, the price that you need to pay is explaining the IDE that you pick to the students. Cheers, Raniere _______________________________________________ Discuss mailing list [email protected] http://lists.software-carpentry.org/listinfo/discuss
