source commit: 42a5e2d

Author: actions-user

2023-11-20_tolkien_counts.xlsx

@@ -0,0 +1 @@
+- [Belinda Weaver](https://github.com/weaverbel), Griffith University Library

2024-05-20_comp-think-open-version.pptx

@@ -0,0 +1,13 @@
+---
+title: "Contributor Code of Conduct"
+---
+
+As contributors and maintainers of this project,
+we pledge to follow the [The Carpentries Code of Conduct][coc].
+
+Instances of abusive, harassing, or otherwise unacceptable behavior
+may be reported by following our [reporting guidelines][coc-reporting].
+
+
+[coc-reporting]: https://docs.carpentries.org/topic_folders/policies/incident-reporting.html
+[coc]: https://docs.carpentries.org/topic_folders/policies/code-of-conduct.html

2024-05-31_script-for-teaching-comp-thinking.pdf

@@ -0,0 +1,79 @@
+---
+title: "Licenses"
+---
+
+## Instructional Material
+
+All Carpentries (Software Carpentry, Data Carpentry, and Library Carpentry)
+instructional material is made available under the [Creative Commons
+Attribution license][cc-by-human]. The following is a human-readable summary of
+(and not a substitute for) the [full legal text of the CC BY 4.0
+license][cc-by-legal].
+
+You are free:
+
+- to **Share**---copy and redistribute the material in any medium or format
+- to **Adapt**---remix, transform, and build upon the material
+
+for any purpose, even commercially.
+
+The licensor cannot revoke these freedoms as long as you follow the license
+terms.
+
+Under the following terms:
+
+- **Attribution**---You must give appropriate credit (mentioning that your work
+  is derived from work that is Copyright (c) The Carpentries and, where
+  practical, linking to <https://carpentries.org/>), provide a [link to the
+  license][cc-by-human], and indicate if changes were made. You may do so in
+  any reasonable manner, but not in any way that suggests the licensor endorses
+  you or your use.
+
+- **No additional restrictions**---You may not apply legal terms or
+  technological measures that legally restrict others from doing anything the
+  license permits.  With the understanding that:
+
+Notices:
+
+* You do not have to comply with the license for elements of the material in
+  the public domain or where your use is permitted by an applicable exception
+  or limitation.
+* No warranties are given. The license may not give you all of the permissions
+  necessary for your intended use. For example, other rights such as publicity,
+  privacy, or moral rights may limit how you use the material.
+
+## Software
+
+Except where otherwise noted, the example programs and other software provided
+by The Carpentries are made available under the [OSI][osi]-approved [MIT
+license][mit-license].
+
+Permission is hereby granted, free of charge, to any person obtaining a copy of
+this software and associated documentation files (the "Software"), to deal in
+the Software without restriction, including without limitation the rights to
+use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies
+of the Software, and to permit persons to whom the Software is furnished to do
+so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.
+
+## Trademark
+
+"The Carpentries", "Software Carpentry", "Data Carpentry", and "Library
+Carpentry" and their respective logos are registered trademarks of [Community
+Initiatives][ci].
+
+[cc-by-human]: https://creativecommons.org/licenses/by/4.0/
+[cc-by-legal]: https://creativecommons.org/licenses/by/4.0/legalcode
+[mit-license]: https://opensource.org/licenses/mit-license.html
+[ci]: https://communityin.org/
+[osi]: https://opensource.org

AUTHORS.md

@@ -0,0 +1,85 @@
+---
+title: Computational thinking in practice
+teaching: 20
+exercises: 10
+---
+
+::::::::::::::::::::::::::::::::::::::: objectives
+
+- Understand the difference between programming and computational thinking
+- Recognize how computational thinking is applied in everyday life
+- Learn the steps of computational thinking such as problem breakdown, pattern recognition, and developing algorithms
+
+::::::::::::::::::::::::::::::::::::::::::::::::::
+
+:::::::::::::::::::::::::::::::::::::::: questions
+
+- What is the difference between programming and computational thinking?
+- How is computational thinking used in daily life?
+- What are the steps involved in computational thinking?
+- How can structure diagrams help in breaking down problems?
+
+::::::::::::::::::::::::::::::::::::::::::::::::::
+
+
+While thinking computationally is a prerequisite for programming, programming and computational thinking are not the same thing.
+
+| **Programming** |   |  **Computational thinking** |
+| :---: | :---: | :---: | 
+| instructs a computer to carry out a sequence of steps in a particular order. |   | is the process that helps decide what those steps will be, i.e.  what the computer will be told to do. |      
+
+------
+
+Computers are precise, and computing instructions must be clear and unambiguous, as the computer cannot think - it can only follow orders. Unlike humans, computers do not get bored or distracted, they process data very quickly, and will carry out the same tedious, repetitive tasks over and over again without making mistakes.
+
+![The computational thinking process in action](fig/proc-diagram.png){alt="Computational thinking at work" width="100%"}
+
+#### Computational thinking in our daily lives
+
+Subconsciously, we practise computational thinking every day of our lives. 
+
+::::::::::::::::::::::::::::::::::::::::::: testimonial
+
+“Computational thinking describes the mental activity in formulating a problem to admit a computational solution. The solution can be carried out by a human or machine.”
+
+— Jeannette Wing
+
+:::::::::::::::::::::::::::::::::::::::::::::::::::::::
+
+Every time we need to plan to do something, we use some of the steps of computational thinking such as problem breakdown, pattern recognition and developing algorithms. 
+
+- Project managers use computational thinking to plan complex activities such as building a tunnel or revamping a playground. 
+
+- Epidemiologists use it to identify patterns that help predict how a disease outbreak will spread. 
+
+- Parents use it to juggle work, parenting, community responsibilities and housework.
+
+- Lost hikers can use it to try to find their way out of the forest.
+
+#### Breaking problems down with structure diagrams
+
+When trying to solve problems, it is essential to break them down into their constituent parts. Pasting sticky notes on a wall is one way to visualise the necessary steps. 
+
+Structure diagrams also allow you to plan problem breakdown visually. At the top should be the objective, and the steps underneath should start with high level considerations. These high level considerations can then be broken down into smaller and smaller steps.
+
+In the hiking scenario, the group of four people have to try to solve the problem of being lost. This diagram is the very start of their thinking about their immediate needs. 
+
+![Basic Structure Diagram](fig/structure.png){alt="Structure diagram" width="100%"}
+
+---------
+
+:::challenge
+## Practice
+
+Imagine that night is now falling fast, and our friends are still stuck in the forest. Add some more detail to the structure diagram to help them survive the night.
+:::
+
+:::::::::::::::::::::::::::::::::::::::: keypoints
+
+- Computational thinking involves breaking down problems, recognizing patterns, and developing algorithms.
+- While programming is instructing a computer to carry out tasks, computational thinking helps decide what those tasks will be.
+- Computational thinking is used in various fields, from project management to epidemiology, and even in daily tasks.
+- Structure diagrams are useful tools for visually breaking down and planning problem-solving steps.
+
+::::::::::::::::::::::::::::::::::::::::::::::::::
+

CODE_OF_CONDUCT.md

@@ -0,0 +1,82 @@
+---
+title: Computational thinking in programming
+teaching: 30
+exercises: 10
+---
+
+::::::::::::::::::::::::::::::::::::::: objectives
+
+- Understand the importance of decomposition in programming
+- Learn how to break down a problem into discrete parts for programming
+- Recognize the difference between linear and branching code
+- Apply pattern recognition to adapt existing code for new problems
+
+::::::::::::::::::::::::::::::::::::::::::::::::::
+
+:::::::::::::::::::::::::::::::::::::::: questions
+
+- Why is decomposition crucial in programming?
+- How can we break down a problem like counting words in a text?
+- What is the difference between linear and branching code?
+- How can pattern recognition help in programming?
+
+::::::::::::::::::::::::::::::::::::::::::::::::::
+
+*Decomposition* is crucial in any kind of problem breakdown, but especially so in programming. The computer must be told **precisely** what to do, and in what order, so problems must be broken down into discrete parts and each section coded appropriately.
+
+#### Defining Inputs and Outputs
+
+Before we can tell the computer *what* to do (the algorithm), we must clarify *what data* we are working with. Every computational problem involves a transformation:
+
+1.  **Input:** What is the starting state? What data do we have? What format is it in?
+2.  **Output:** What is the desired goal? What should the result look like?
+
+If we don't define these clearly, we cannot design effective steps to bridge the gap.
+
+Suppose we want to find the ten words most commonly used in a text.
+
+**Input:** A digital text file (e.g., a book chapter).
+**Output:** A list of the top 10 most frequent words.
+
+The *process* (or algorithm) is the series of steps that turns that specific Input into that specific Output.
+
+How might we go about that?
+
+#### Linear code
+
+While there are many different ways to do this task, this is one way, where all the commands are run in a linear sequence, e.g.,
+
+![Counting words in a text](fig/count-words.png){alt="counting words in a text" width="60%"}
+
+First we save the file in `.txt` format to eliminate all the "smart" formatting created by programs like Word (as they would otherwise introduce a messy bunch of extraneous characters). Then we progressively eliminate everything from the text that is not a word, i.e. punctuation. 
+
+Converting all the words to lower case means we end up with a single version of each word - not two. This is important because, to a computer, `Word` (starting with an upper case letter) does not equal `word` (starting with a lower case letter) - it treats them as two separate entities. 
+
+By replacing spaces with `new line` characters, each word will end up on its own line, which makes them easy to sort alphabetically and then count.
+
+Each part of the sequence would need to be individually programmed. Fortunately, programmers can adapt code that others have already used to do similar tasks, such as code to identify letter, number or word frequency. Once you are coding, this is where the computational thinking skill of *pattern recognition* comes in - identifying similar code that can be used for or adapted to the specific problem you want to solve. 
+
+--------
+
+#### Branching code
+
+Programming rarely works in such a linear fashion. Code generally includes branching so that different pathways can be taken, depending on whether or not certain conditions are met, e.g., different responses to a `Yes/No` or `True/False` decision, as in the example here.
+
+![Branching code](fig/workflow.png){alt="Branching code" width="90%"}
+
+----------------
+
+:::challenge
+## Hiking Preparation Strategy
+
+Our friends have finally made it out of the forest and back to civilisation. Their experience, while unpleasant, has not put them off hiking. Draw a structure diagram of the planning they need to do for next time to avert another disaster.
+:::
+
+:::::::::::::::::::::::::::::::::::::::: keypoints
+
+- Decomposition is essential for breaking down problems into discrete parts in programming.
+- Computers require precise instructions, and problems must be broken down accordingly.
+- Linear code runs commands in a sequence, while branching code allows for different pathways based on conditions.
+- Pattern recognition helps programmers adapt existing code for new problems.
+
+::::::::::::::::::::::::::::::::::::::::::::::::::

LICENSE.md

@@ -0,0 +1,88 @@
+#------------------------------------------------------------
+# Values for this lesson.
+#------------------------------------------------------------
+
+# Which carpentry is this (swc, dc, lc, or cp)?
+# swc: Software Carpentry
+# dc: Data Carpentry
+# lc: Library Carpentry
+# cp: Carpentries (to use for instructor training for instance)
+# incubator: The Carpentries Incubator
+carpentry: 'lc'
+
+# Overall title for pages.
+title: 'Introducing Computational Thinking'
+
+# Date the lesson was created (YYYY-MM-DD, this is empty by default)
+created: "2022-08-12"
+
+# Comma-separated list of keywords for the lesson
+keywords: 'software, data, lesson, The Carpentries'
+
+# Life cycle stage of the lesson
+# possible values: pre-alpha, alpha, beta, stable
+life_cycle: 'alpha'
+
+# License of the lesson materials (recommended CC-BY 4.0)
+license: 'CC-BY 4.0'
+
+# Link to the source repository for this lesson
+source: 'https://github.com/LibraryCarpentry/lc-computational-thinking/'
+
+# Default branch of your lesson
+branch: 'main'
+
+# Who to contact if there are any issues
+contact: 'team@carpentries.org'
+
+# Navigation ------------------------------------------------
+#
+# Use the following menu items to specify the order of
+# individual pages in each dropdown section. Leave blank to
+# include all pages in the folder.
+#
+# Example -------------
+#
+# episodes:
+# - introduction.md
+# - first-steps.md
+#
+# learners:
+# - setup.md
+#
+# instructors:
+# - instructor-notes.md
+#
+# profiles:
+# - one-learner.md
+# - another-learner.md
+
+# Order of episodes in your lesson
+episodes: 
+- intro.md
+- exercise.md
+- computation_practice.md
+- computation_programming.md
+- pseudocode.md
+
+
+# Information for Learners
+learners: 
+
+# Information for Instructors
+instructors: 
+
+# Learner Profiles
+profiles: 
+
+# Customisation ---------------------------------------------
+#
+# This space below is where custom yaml items (e.g. pinning
+# sandpaper and varnish versions) should live
+
+url: 'https://library-carpentry.org/lc-computational-thinking'
+analytics: carpentries
+lang: en
+
+
+