I like the sound of it. :) I think it would be great to see something similar in the SWC frameworks. It makes a lot of sense for writing research notes and even paper drafts. The main problem with markdown is the diversity of implementations and extensions. You basically need to tie markdown to pandoc.
All kinds of lessons
We still have an issue with intro to data @drjwbaker - in this quiz, we expect people to know that {2,4} denotes a range but we haven't taught that yet. https://data-lessons.github.io/library-data-intro/06-quiz-answers/
So when people have to choose between {2-4} and {2,4} for a range they think it should be the hyphenated one.
Should be in the list.
I am going to add some extra bits to regex - we need to include that, and also \i for case insensitivity.
But not today - teaching two full days tomorrow - SWC instructor training to 23 people !
@weaverbel http://data-lessons.github.io/library-data-intro/04-regular-expressions/
{VALUE} matches the preceding character the number of times defined by VALUE; ranges can be specified with the syntax {VALUE,VALUE}
OK, thanks @drjwbaker but that is actually a bit ambiguous and I didn't read it that way at all when I saw it. Wiser now, of course, but the way I (erroneously) read that, I thought it meant the actual value was the first VALUE and the number of times it should repeat was the second VALUE Not explaining it well but I guess I thought it would work out as {\d,4} which is obviously nonsense but I had no idea you were conveying a range of NUMBERS OF TIMES. Maybe I am an idiot but if I can get confused, so can other people. As with all these things, I think an example is worth gold and we need to put an example for most of these as they are pretty challenging. And clearing up any ambiguity is worth doing.
Anyway I get it now which is good if I am teaching it and I will make a point of pointing it out.
I've got an idea for a lesson plan that cropped up because of a variety of conversations in several contexts about the same problem: namely, the difficulty of installing new programs/software etc. on Windows machines. This has been a bugbear in the Bash LC lessons, and even occasionally for OpenRefine.
What if we developed a lesson on Windows installation? To make clear the fact that it is a trial and error process at the best of times, and to bring home the fact that it isn't because you are stupid - even intermediate/advanced Windows users have to devote time and research and troubleshooting to get something installed and working correctly.
I'd like to develop a lesson that covers basic Windows file structure, where you should put the programs you are installing and why, the research process for finding answers to error messages, and the troubleshooting process. Have learners install the programs they would be using in future LC lessons, and maybe go through a VM installation, just to show them how a multi-program install works, and how the order in which you install things can be critical to making the end result work properly?
Yes? No?
Oooh, we could get them to install Jeckyll....er, never mind. OK, I'ma put down the coffee now.
Hi @JulianeS_twitter You are very brave with that idea! Or what politicians call 'courageous' - and we all know what that means - certifiable, looney, batsh*t crazy. I don't know that we need a Windows thing so much as just a digital tune up of how to download a file and know how to find it, how to install a program, how to get Chrome installed on your system if you haven't already, how to open multiple tabs in a browser (yes, I know, lame, but I have HAD THAT PROBLEM on the roadshow).
Also lots of enthusiasm at the roadshow for my cyber security stuff - this is just an off the cuff five minutes where I tell them to get wise and help their customers wise up too. I email my 21 point plan to them later.
@JulianeS_twitter @weaverbel I second the idea of a tuneup lesson, with a focus on getting things installed on Win could be good. Interesting that you mention where things should be installed etc. This could have linux/mac stuff too, and you could (perhaps) mention things like Homebrew for mac. Dare I say even talk about $PATH :)
Hi @jt14den can you help me out please? How would you incorporate previewing in Jekyll (http://swcarpentry.github.io/lesson-example/05-checking/) into this workflow? http://www.tim-dennis.com/swc/2016/07/25/contributing-carpentries.html
i updated that blog entry to include the jykll stuff http://www.tim-dennis.com/swc/2016/07/25/contributing-carpentries.html
though i seemed to creamed my template :)
ironic
I don't know if this would be useful for anyone else. First time I had to fork someone's repository I was somewhat terrified of breaking something. I found a handy tutorial and sample repo to fork - the Spoon and Fork repository at https://guides.github.com/activities/forking/. It walks you through the process of contributing to a project.
For the SA workshop, I look @weaverbel's open refine lesson exercises handout and put up in hacked.io, my fav new markdown tool https://hackmd.io/KwUwTADAjAZgJjAtDALPRKCGUBGiCcc+AHIgMYQDsMZYAbCmfnQMxA==
*I took
Many thanks @weaverbel
Gave them the link