Loading LAYOUT.md +5 −43 Original line number Diff line number Diff line Loading @@ -63,8 +63,7 @@ plots, and diagrams used in the lessons must go in a `fig/` directory. Files used to display the lesson, such as artwork, CSS, and Javascript, are stored in `img/`, `css/`, and `js/` directories of their own, while the `deck.js/` directory contains files used to make HTML slideshows. We keep website artwork in the `img/` directory their own. We keep website artwork in the `img/` directory separate from figures used in the lesson (which are stored in `fig/`) to make it simple to update the former automatically. Most authors should not need to modify any of the support files themselves. Loading Loading @@ -98,22 +97,18 @@ The root directory holds the content of the lesson, and must contain: this lesson, and is about the filesystem. (Note that we use hyphens rather than underscores in filenames.) See "Topics" below. 4. `motivation.md`: slides for a short introductory presentation (three minutes or less) explaining what the lesson is about and why people would want to learn it. See "Introductory Slides" below. 5. `reference.md`: a cheat sheet summarizing key terms and commands, 4. `reference.md`: a cheat sheet summarizing key terms and commands, syntax, etc., that can be printed and given to learners. See "Reference Guide" below. 6. `discussion.md`: notes about more advanced ideas that would 5. `discussion.md`: notes about more advanced ideas that would distract from the main lesson, and pointers to where to go next. See "Discussion Page" below. 7. `instructors.md`: the instructor's guide for the lesson. See 6. `instructors.md`: the instructor's guide for the lesson. See "Instructor's Guide" below. 8. `CONTRIBUTING.md`: instructions for people who want to contribute. 7. `CONTRIBUTING.md`: instructions for people who want to contribute. This file should be edited to replace references to `lesson-template` with references to your lesson's repository. Loading Loading @@ -337,39 +332,6 @@ random number generation is outside the scope of the lesson, summary(ex_dat) ``` ## Motivational Slides Every lesson must include a short slide deck in `motivation.md` suitable for a short presentation (3 minutes or less) that the instructor can use to explain to learners how knowing the subject will help them. The slides must use level-2 headings as slide titles, but may use anything within the slide: --- layout: slides title: Lesson Title subtitle: Motivation --- ## Our Mission We make scientists and engineering more productive by teaching them basic computing skills. ## The Problem - Surveyed 1972 scientists in 2008. - "How do you use computers?" - "How did you learn what you know?" **Notes:** 1. We use [deck.js](http://imakewebthings.com/deck.js/) for our slides as it is simpler and prettier than alternatives like [reveal.js](http://lab.hakim.se/reveal-js/). 2. For examples of slideshows, please see the [slideshow repository](https://github.com/swcarpentry/slideshows). ## Reference Guide The reference guide in `reference.md` is a cheat sheet for learners to print, doodle on, Loading README.md +0 −3 Original line number Diff line number Diff line Loading @@ -200,9 +200,6 @@ cover, and that coverage to include: Along with the lesson materials themselves, each lesson must contain: * *Introductory slides* to give learners a sense of where the next two or three hours are going to take them. * A *reference guide* that learners can use during the lesson and take away afterward. This must include a glossary of terms, not only to help learners, but also to help lesson authors summarize what the Loading motivation.htmldeleted 100644 → 0 +0 −133 Original line number Diff line number Diff line <!DOCTYPE html> <html> <head> <meta charset="utf-8"> <meta http-equiv="X-UA-Compatible" content="IE=edge,chrome=1"> <meta name="viewport" content="width=device-width, user-scalable=no, initial-scale=1.0, minimum-scale=1.0, maximum-scale=1.0"> <title>Lesson Title</title> <script src="js/deckjs-custom.js"></script> <script> // TODO: finer filter on what is needed (vs profile-5) includedeck("css/swc-slides.css", { BEFOREINIT: function() { $(".slide.auto li:not(li li):not(.notslide)").addClass("slide"); } }); </script> </head> <body> <div class="deck-container"> <div class="slide title-slide" data-container-class="no-status"> <h1 class="var-title"></h1> <img class="logo" src="img/software-carpentry-banner.png" alt="Software Carpentry"/> </div> <!-- Begin slides. Just make elements with a class of slide. --> <section id="our-mission" class="slide level2"> <h1>Our Mission</h1> <p>We make scientists and engineering more productive by teaching them basic computing skills.</p> </section> <section id="the-problem" class="slide level2"> <h1>The Problem</h1> <ul> <li>Surveyed 1972 scientists in 2008.</li> <li>“How do you use computers?”</li> <li>“How did you learn what you know?”</li> </ul> </section> <section id="the-problem-1" class="slide level2"> <h1>The Problem</h1> <ul> <li>Scientists spend 40% of their time building or using software.</li> <li>55% say this figure is rising.</li> <li><em>96% are mostly self-taught</em>.</li> </ul> </section> <section id="the-problem-2" class="slide level2"> <h1>The Problem</h1> <ul> <li>No hard data on how <em>well</em> they do things.</li> <li>But anecdotal evidence suggests “not very”.</li> </ul> </section> <section id="our-solution" class="slide level2"> <h1>Our Solution</h1> <ul> <li>Intensive hands-on training.</li> <li>Two full days of instruction.</li> <li>Unix shell (automate repetitive tasks)</li> <li>Git and GitHub (track and share work)</li> <li>Python or R (build modular code)</li> <li>SQL (manage data)</li> </ul> </section> <section id="outcomes" class="slide level2"> <h1>Outcomes</h1> <ul> <li>20% improvement in productivity is common.</li> <li>10X isn’t rare.</li> </ul> </section> <section id="outcomes-1" class="slide level2"> <h1>Outcomes</h1> <ul> <li>Empowers people.</li> <li>HPC, the cloud, web services, big data, …</li> <li>Reproducible research, open science, …</li> </ul> </section> <section id="the-details" class="slide level2"> <h1>The Details</h1> <ul> <li>Materials are all open access.</li> <li>Instructors are volunteers.</li> <li>Only cost is travel and accommodation</li> <li>(but contributions to central costs are welcome).</li> </ul> </section> <section id="how-to-help" class="slide level2"> <h1>How To Help</h1> <ul> <li>Come and learn.</li> <li>Join the discussion.</li> <li>Host a workshop.</li> <li>Become an instructor.</li> <li>Create new teaching materials.</li> </ul> </section> <section id="learn-more" class="slide level2"> <h1>Learn More</h1> <ul> <li><a href="http://software-carpentry.org" class="uri">http://software-carpentry.org</a></li> <li><script type="text/javascript"> <!-- h='software-carpentry.org';a='@';n='admin';e=n+a+h; document.write('<a h'+'ref'+'="ma'+'ilto'+':'+e+'" clas'+'s="em' + 'ail">'+e+'<\/'+'a'+'>'); // --> </script><noscript>admin at software-carpentry dot org</noscript></li> </ul> </section> <!-- End slides. --> <!-- Begin extension snippets. Add or remove as needed. --> <!-- deck.navigation snippet --> <div aria-role="navigation"> <a href="#" class="deck-prev-link" title="Previous">←</a> <a href="#" class="deck-next-link" title="Next">→</a> </div> <!-- footer --> <p class="deck-status deck-progress-10"> <span class="deck-status-current"></span> / <span class="deck-status-total"></span> − <span class="var-title">will be replaced by the title</span></p> <!-- progress bar --> <div class="progress-bar" data-progress-size=":spe.bottom(0, 1) ; left: slide.left+'px' ; height: designRatio+'px'" data-progress="width: detail.p * slide.width" style="position: absolute;"> </div> <!-- End extension snippets. --> </div> </body> </html> motivation.mddeleted 100644 → 0 +0 −73 Original line number Diff line number Diff line --- layout: slides title: Lesson Title subtitle: Motivation --- ## Our Mission We make scientists and engineering more productive by teaching them basic computing skills. ## The Problem - Surveyed 1972 scientists in 2008. - "How do you use computers?" - "How did you learn what you know?" ## The Problem - Scientists spend 40% of their time building or using software. - 55% say this figure is rising. - *96% are mostly self-taught*. ## The Problem - No hard data on how *well* they do things. - But anecdotal evidence suggests "not very". ## Our Solution - Intensive hands-on training. - Two full days of instruction. - Unix shell (automate repetitive tasks) - Git and GitHub (track and share work) - Python or R (build modular code) - SQL (manage data) ## Outcomes - 20% improvement in productivity is common. - 10X isn't rare. ## Outcomes - Empowers people. - HPC, the cloud, web services, big data, ... - Reproducible research, open science, ... ## The Details - Materials are all open access. - Instructors are volunteers. - Only cost is travel and accommodation - (but contributions to central costs are welcome). ## How To Help - Come and learn. - Join the discussion. - Host a workshop. - Become an instructor. - Create new teaching materials. ## Learn More - <http://software-carpentry.org> - [admin@software-carpentry.org](mailto:admin@software-carpentry.org) Loading
LAYOUT.md +5 −43 Original line number Diff line number Diff line Loading @@ -63,8 +63,7 @@ plots, and diagrams used in the lessons must go in a `fig/` directory. Files used to display the lesson, such as artwork, CSS, and Javascript, are stored in `img/`, `css/`, and `js/` directories of their own, while the `deck.js/` directory contains files used to make HTML slideshows. We keep website artwork in the `img/` directory their own. We keep website artwork in the `img/` directory separate from figures used in the lesson (which are stored in `fig/`) to make it simple to update the former automatically. Most authors should not need to modify any of the support files themselves. Loading Loading @@ -98,22 +97,18 @@ The root directory holds the content of the lesson, and must contain: this lesson, and is about the filesystem. (Note that we use hyphens rather than underscores in filenames.) See "Topics" below. 4. `motivation.md`: slides for a short introductory presentation (three minutes or less) explaining what the lesson is about and why people would want to learn it. See "Introductory Slides" below. 5. `reference.md`: a cheat sheet summarizing key terms and commands, 4. `reference.md`: a cheat sheet summarizing key terms and commands, syntax, etc., that can be printed and given to learners. See "Reference Guide" below. 6. `discussion.md`: notes about more advanced ideas that would 5. `discussion.md`: notes about more advanced ideas that would distract from the main lesson, and pointers to where to go next. See "Discussion Page" below. 7. `instructors.md`: the instructor's guide for the lesson. See 6. `instructors.md`: the instructor's guide for the lesson. See "Instructor's Guide" below. 8. `CONTRIBUTING.md`: instructions for people who want to contribute. 7. `CONTRIBUTING.md`: instructions for people who want to contribute. This file should be edited to replace references to `lesson-template` with references to your lesson's repository. Loading Loading @@ -337,39 +332,6 @@ random number generation is outside the scope of the lesson, summary(ex_dat) ``` ## Motivational Slides Every lesson must include a short slide deck in `motivation.md` suitable for a short presentation (3 minutes or less) that the instructor can use to explain to learners how knowing the subject will help them. The slides must use level-2 headings as slide titles, but may use anything within the slide: --- layout: slides title: Lesson Title subtitle: Motivation --- ## Our Mission We make scientists and engineering more productive by teaching them basic computing skills. ## The Problem - Surveyed 1972 scientists in 2008. - "How do you use computers?" - "How did you learn what you know?" **Notes:** 1. We use [deck.js](http://imakewebthings.com/deck.js/) for our slides as it is simpler and prettier than alternatives like [reveal.js](http://lab.hakim.se/reveal-js/). 2. For examples of slideshows, please see the [slideshow repository](https://github.com/swcarpentry/slideshows). ## Reference Guide The reference guide in `reference.md` is a cheat sheet for learners to print, doodle on, Loading
README.md +0 −3 Original line number Diff line number Diff line Loading @@ -200,9 +200,6 @@ cover, and that coverage to include: Along with the lesson materials themselves, each lesson must contain: * *Introductory slides* to give learners a sense of where the next two or three hours are going to take them. * A *reference guide* that learners can use during the lesson and take away afterward. This must include a glossary of terms, not only to help learners, but also to help lesson authors summarize what the Loading
motivation.htmldeleted 100644 → 0 +0 −133 Original line number Diff line number Diff line <!DOCTYPE html> <html> <head> <meta charset="utf-8"> <meta http-equiv="X-UA-Compatible" content="IE=edge,chrome=1"> <meta name="viewport" content="width=device-width, user-scalable=no, initial-scale=1.0, minimum-scale=1.0, maximum-scale=1.0"> <title>Lesson Title</title> <script src="js/deckjs-custom.js"></script> <script> // TODO: finer filter on what is needed (vs profile-5) includedeck("css/swc-slides.css", { BEFOREINIT: function() { $(".slide.auto li:not(li li):not(.notslide)").addClass("slide"); } }); </script> </head> <body> <div class="deck-container"> <div class="slide title-slide" data-container-class="no-status"> <h1 class="var-title"></h1> <img class="logo" src="img/software-carpentry-banner.png" alt="Software Carpentry"/> </div> <!-- Begin slides. Just make elements with a class of slide. --> <section id="our-mission" class="slide level2"> <h1>Our Mission</h1> <p>We make scientists and engineering more productive by teaching them basic computing skills.</p> </section> <section id="the-problem" class="slide level2"> <h1>The Problem</h1> <ul> <li>Surveyed 1972 scientists in 2008.</li> <li>“How do you use computers?”</li> <li>“How did you learn what you know?”</li> </ul> </section> <section id="the-problem-1" class="slide level2"> <h1>The Problem</h1> <ul> <li>Scientists spend 40% of their time building or using software.</li> <li>55% say this figure is rising.</li> <li><em>96% are mostly self-taught</em>.</li> </ul> </section> <section id="the-problem-2" class="slide level2"> <h1>The Problem</h1> <ul> <li>No hard data on how <em>well</em> they do things.</li> <li>But anecdotal evidence suggests “not very”.</li> </ul> </section> <section id="our-solution" class="slide level2"> <h1>Our Solution</h1> <ul> <li>Intensive hands-on training.</li> <li>Two full days of instruction.</li> <li>Unix shell (automate repetitive tasks)</li> <li>Git and GitHub (track and share work)</li> <li>Python or R (build modular code)</li> <li>SQL (manage data)</li> </ul> </section> <section id="outcomes" class="slide level2"> <h1>Outcomes</h1> <ul> <li>20% improvement in productivity is common.</li> <li>10X isn’t rare.</li> </ul> </section> <section id="outcomes-1" class="slide level2"> <h1>Outcomes</h1> <ul> <li>Empowers people.</li> <li>HPC, the cloud, web services, big data, …</li> <li>Reproducible research, open science, …</li> </ul> </section> <section id="the-details" class="slide level2"> <h1>The Details</h1> <ul> <li>Materials are all open access.</li> <li>Instructors are volunteers.</li> <li>Only cost is travel and accommodation</li> <li>(but contributions to central costs are welcome).</li> </ul> </section> <section id="how-to-help" class="slide level2"> <h1>How To Help</h1> <ul> <li>Come and learn.</li> <li>Join the discussion.</li> <li>Host a workshop.</li> <li>Become an instructor.</li> <li>Create new teaching materials.</li> </ul> </section> <section id="learn-more" class="slide level2"> <h1>Learn More</h1> <ul> <li><a href="http://software-carpentry.org" class="uri">http://software-carpentry.org</a></li> <li><script type="text/javascript"> <!-- h='software-carpentry.org';a='@';n='admin';e=n+a+h; document.write('<a h'+'ref'+'="ma'+'ilto'+':'+e+'" clas'+'s="em' + 'ail">'+e+'<\/'+'a'+'>'); // --> </script><noscript>admin at software-carpentry dot org</noscript></li> </ul> </section> <!-- End slides. --> <!-- Begin extension snippets. Add or remove as needed. --> <!-- deck.navigation snippet --> <div aria-role="navigation"> <a href="#" class="deck-prev-link" title="Previous">←</a> <a href="#" class="deck-next-link" title="Next">→</a> </div> <!-- footer --> <p class="deck-status deck-progress-10"> <span class="deck-status-current"></span> / <span class="deck-status-total"></span> − <span class="var-title">will be replaced by the title</span></p> <!-- progress bar --> <div class="progress-bar" data-progress-size=":spe.bottom(0, 1) ; left: slide.left+'px' ; height: designRatio+'px'" data-progress="width: detail.p * slide.width" style="position: absolute;"> </div> <!-- End extension snippets. --> </div> </body> </html>
motivation.mddeleted 100644 → 0 +0 −73 Original line number Diff line number Diff line --- layout: slides title: Lesson Title subtitle: Motivation --- ## Our Mission We make scientists and engineering more productive by teaching them basic computing skills. ## The Problem - Surveyed 1972 scientists in 2008. - "How do you use computers?" - "How did you learn what you know?" ## The Problem - Scientists spend 40% of their time building or using software. - 55% say this figure is rising. - *96% are mostly self-taught*. ## The Problem - No hard data on how *well* they do things. - But anecdotal evidence suggests "not very". ## Our Solution - Intensive hands-on training. - Two full days of instruction. - Unix shell (automate repetitive tasks) - Git and GitHub (track and share work) - Python or R (build modular code) - SQL (manage data) ## Outcomes - 20% improvement in productivity is common. - 10X isn't rare. ## Outcomes - Empowers people. - HPC, the cloud, web services, big data, ... - Reproducible research, open science, ... ## The Details - Materials are all open access. - Instructors are volunteers. - Only cost is travel and accommodation - (but contributions to central costs are welcome). ## How To Help - Come and learn. - Join the discussion. - Host a workshop. - Become an instructor. - Create new teaching materials. ## Learn More - <http://software-carpentry.org> - [admin@software-carpentry.org](mailto:admin@software-carpentry.org)