├── LICENSE └── readme.md /LICENSE: -------------------------------------------------------------------------------- 1 | CC0 1.0 Universal 2 | 3 | Statement of Purpose 4 | 5 | The laws of most jurisdictions throughout the world automatically confer 6 | exclusive Copyright and Related Rights (defined below) upon the creator and 7 | subsequent owner(s) (each and all, an "owner") of an original work of 8 | authorship and/or a database (each, a "Work"). 9 | 10 | Certain owners wish to permanently relinquish those rights to a Work for the 11 | purpose of contributing to a commons of creative, cultural and scientific 12 | works ("Commons") that the public can reliably and without fear of later 13 | claims of infringement build upon, modify, incorporate in other works, reuse 14 | and redistribute as freely as possible in any form whatsoever and for any 15 | purposes, including without limitation commercial purposes. These owners may 16 | contribute to the Commons to promote the ideal of a free culture and the 17 | further production of creative, cultural and scientific works, or to gain 18 | reputation or greater distribution for their Work in part through the use and 19 | efforts of others. 20 | 21 | For these and/or other purposes and motivations, and without any expectation 22 | of additional consideration or compensation, the person associating CC0 with a 23 | Work (the "Affirmer"), to the extent that he or she is an owner of Copyright 24 | and Related Rights in the Work, voluntarily elects to apply CC0 to the Work 25 | and publicly distribute the Work under its terms, with knowledge of his or her 26 | Copyright and Related Rights in the Work and the meaning and intended legal 27 | effect of CC0 on those rights. 28 | 29 | 1. Copyright and Related Rights. A Work made available under CC0 may be 30 | protected by copyright and related or neighboring rights ("Copyright and 31 | Related Rights"). Copyright and Related Rights include, but are not limited 32 | to, the following: 33 | 34 | i. the right to reproduce, adapt, distribute, perform, display, communicate, 35 | and translate a Work; 36 | 37 | ii. moral rights retained by the original author(s) and/or performer(s); 38 | 39 | iii. publicity and privacy rights pertaining to a person's image or likeness 40 | depicted in a Work; 41 | 42 | iv. rights protecting against unfair competition in regards to a Work, 43 | subject to the limitations in paragraph 4(a), below; 44 | 45 | v. rights protecting the extraction, dissemination, use and reuse of data in 46 | a Work; 47 | 48 | vi. database rights (such as those arising under Directive 96/9/EC of the 49 | European Parliament and of the Council of 11 March 1996 on the legal 50 | protection of databases, and under any national implementation thereof, 51 | including any amended or successor version of such directive); and 52 | 53 | vii. other similar, equivalent or corresponding rights throughout the world 54 | based on applicable law or treaty, and any national implementations thereof. 55 | 56 | 2. Waiver. To the greatest extent permitted by, but not in contravention of, 57 | applicable law, Affirmer hereby overtly, fully, permanently, irrevocably and 58 | unconditionally waives, abandons, and surrenders all of Affirmer's Copyright 59 | and Related Rights and associated claims and causes of action, whether now 60 | known or unknown (including existing as well as future claims and causes of 61 | action), in the Work (i) in all territories worldwide, (ii) for the maximum 62 | duration provided by applicable law or treaty (including future time 63 | extensions), (iii) in any current or future medium and for any number of 64 | copies, and (iv) for any purpose whatsoever, including without limitation 65 | commercial, advertising or promotional purposes (the "Waiver"). Affirmer makes 66 | the Waiver for the benefit of each member of the public at large and to the 67 | detriment of Affirmer's heirs and successors, fully intending that such Waiver 68 | shall not be subject to revocation, rescission, cancellation, termination, or 69 | any other legal or equitable action to disrupt the quiet enjoyment of the Work 70 | by the public as contemplated by Affirmer's express Statement of Purpose. 71 | 72 | 3. Public License Fallback. Should any part of the Waiver for any reason be 73 | judged legally invalid or ineffective under applicable law, then the Waiver 74 | shall be preserved to the maximum extent permitted taking into account 75 | Affirmer's express Statement of Purpose. In addition, to the extent the Waiver 76 | is so judged Affirmer hereby grants to each affected person a royalty-free, 77 | non transferable, non sublicensable, non exclusive, irrevocable and 78 | unconditional license to exercise Affirmer's Copyright and Related Rights in 79 | the Work (i) in all territories worldwide, (ii) for the maximum duration 80 | provided by applicable law or treaty (including future time extensions), (iii) 81 | in any current or future medium and for any number of copies, and (iv) for any 82 | purpose whatsoever, including without limitation commercial, advertising or 83 | promotional purposes (the "License"). The License shall be deemed effective as 84 | of the date CC0 was applied by Affirmer to the Work. Should any part of the 85 | License for any reason be judged legally invalid or ineffective under 86 | applicable law, such partial invalidity or ineffectiveness shall not 87 | invalidate the remainder of the License, and in such case Affirmer hereby 88 | affirms that he or she will not (i) exercise any of his or her remaining 89 | Copyright and Related Rights in the Work or (ii) assert any associated claims 90 | and causes of action with respect to the Work, in either case contrary to 91 | Affirmer's express Statement of Purpose. 92 | 93 | 4. Limitations and Disclaimers. 94 | 95 | a. No trademark or patent rights held by Affirmer are waived, abandoned, 96 | surrendered, licensed or otherwise affected by this document. 97 | 98 | b. Affirmer offers the Work as-is and makes no representations or warranties 99 | of any kind concerning the Work, express, implied, statutory or otherwise, 100 | including without limitation warranties of title, merchantability, fitness 101 | for a particular purpose, non infringement, or the absence of latent or 102 | other defects, accuracy, or the present or absence of errors, whether or not 103 | discoverable, all to the greatest extent permissible under applicable law. 104 | 105 | c. Affirmer disclaims responsibility for clearing rights of other persons 106 | that may apply to the Work or any use thereof, including without limitation 107 | any person's Copyright and Related Rights in the Work. Further, Affirmer 108 | disclaims responsibility for obtaining any necessary consents, permissions 109 | or other rights required for any use of the Work. 110 | 111 | d. Affirmer understands and acknowledges that Creative Commons is not a 112 | party to this document and has no duty or obligation with respect to this 113 | CC0 or use of the Work. 114 | 115 | For more information, please see 116 | -------------------------------------------------------------------------------- /readme.md: -------------------------------------------------------------------------------- 1 | # Pseudocode 2 | 3 | ## Learning Objectives 4 | - Describe the role of pseudocode in development 5 | - List the steps for problem solving 6 | - Create pseudocode to describe a basic problem 7 | 8 | ## What Is Pseudocode? (5 minutes / 0:05) 9 | 10 | Pseudocode is a way to describe the solution to a problem without writing code in full. 11 | * Writing pseudocode forces you to think critically about the problem and break it down into smaller steps. 12 | * It is usually written using a combination of English and logic. As a result, it is easy to read. 13 | * It might display some features of the final product, such as indentation and code blocks. 14 | 15 | Pseudocode should describe the entire logic of a problem so that programming becomes a task of translating pseudocode line by line into actual code. 16 | 17 | ## How to Make a PB&J Sandwich (10 minutes / 0:15) 18 | 19 | > Source: [Get Creative Today](http://getcreativetoday.com/lessons/pseudo-code-flowcharts/) 20 | 21 | We're going to make a PB&J sandwich — for real. 22 | 23 | In today's demo, the supporting instructor will act like a computer. You'll be tasked with guiding the instructor through the process of making the sandwich. Keep in mind that your instructions will need to be explicit otherwise things could get messy! 24 | 25 |
26 | **Here's one approach to solving our problem** 27 | 28 | ``` 29 | PROGRAM MakePB&JSandwich: 30 | Grab a paper plate; 31 | Open bread container; 32 | Grab bread package; 33 | Untwist bread package; 34 | Open bread bag and remove two slices; 35 | Place slices on paper plate; 36 | Grab a plastic knife; 37 | Open peanut butter jar; 38 | Use knife to scoop out peanut butter; 39 | Apply peanut butter to one slice of bread; 40 | Spread peanut butter on slice; 41 | Place knife on plate; 42 | Close peanut butter jar; 43 | Open jelly bottle; 44 | Squeeze jelly onto second bread slice; 45 | Close jelly bottle; 46 | Place down jelly; 47 | Pick up knife; 48 | Spread jelly on slice; 49 | Bring two slices of bread together; 50 | Cut slices in half down the middle; 51 | Throw knife in the trash; 52 | Pick up one half of sandwich; 53 | Enjoy; 54 | END. 55 | ``` 56 | 57 | > A. This example's sequence is very thorough! However, we are still assuming certain conditions that our utensils or ingredients already exist. What if we are out of plates? Will we grab a napkin instead to place our sandwich on? What if we are out of jelly? Will you throw the sandwich away or eat it with just peanut butter? 58 |
59 | 60 | ## Approaching a Coding Problem (15 minutes / 0:35) 61 | 62 | 63 | Computers are not smart. We need to give them step by step instructions to account for conditions. They can not adapt to make changes without being explicitly told. Programing is a series of tasks, which can be completed only if a certain number of conditions are met. 64 | 65 | Computers can not adapt, but we can. Your first pass at pseudocode will probably not cover everything. Once you know more, you may come back to update and refactor your pseudocode. 66 | 67 | Pseudocode isn't just about writing down the steps that you already know. It's a tool to help you work through the problem. Before we can write pseudocode to solve the problem, we need to know the problem. 68 | 69 | #### Identify the Problem 70 | 71 | - What exactly are we trying to solve? 72 | - What are we delivering? 73 | 74 | #### Conceptualize 75 | 76 | - Look at the big picture 77 | - Avoid details 78 | - Whiteboards and pen-and-paper can be useful tools here 79 | 80 | #### Break It Down 81 | 82 | - Break the conceptual models down into concrete steps / actionable items 83 | - Identify risks (e.g., gaps in knowledge and technology) 84 | 85 | #### Start Small, Stay Small 86 | 87 | Write code using those concrete steps 88 | - Verify that each step achieves what we want before continuing on 89 | - If we do too much at once and things break, which they always do, we won't know what is causing the problem 90 | - Humans thrive on easy wins and forward progress. Use this to your advantage. 91 | 92 | 93 | ### Where Does Pseudocode Fit In? 94 | 95 | #### "Break It Down" 96 | 97 | This process is iterative. We keep circling around and repeating the earlier steps, just at a different level. 98 | 99 | When we first approach a problem, we see the big picture. "Break it down" first into big steps. Then we take one of those steps and "Break it down" again into smaller steps. We write pseudocode to help illustrate the problem. 100 | 101 | Pseudocoding proves that we have *identified* the problem, understand it *conceptually*, and have *broken it down* into *small steps* that we can follow. 102 | 103 | #### Example 1.1 104 | 105 | ``` 106 | PROGRAM IsEvenOrOdd: 107 | var num = number; 108 | IF (num % 2 === 0) 109 | THEN Print "even"; 110 | ELSE Print "odd"; 111 | ENDIF; 112 | END. 113 | ``` 114 | 115 |
116 | What do we think? 117 | 118 | > This is not a great example. Here we are using "var" in our pseudocode when it should read plain english! Also, we should not be using the javascript syntax "===" in our conditional. Would a non-programmer know that `num % 2 === 0` indicates an even number? 119 | 120 |
121 | 122 | #### Example 1.2 123 | 124 | ``` 125 | PROGRAM IsEvenOrOdd: 126 | Read number; 127 | IF (number divided by two has no remainder) 128 | THEN Print the number is even; 129 | ELSE Print the number is odd; 130 | ENDIF; 131 | END. 132 | ``` 133 | 134 |
135 | What do we think? 136 | 137 | > This is better. It's closer to English. It clearly states what we are trying to achieve and how, without getting bogged down in the minutia of code. Even someone that doesn't code can help us check our logic. Is any number that can be divided by two, cleanly -- without leaving a remainder -- even? Is anything else odd? 138 | 139 |
140 | 141 | 142 | ## You Do: Pseudocode Concentration (15 minutes / 0:50) 143 | 144 | Take 10 minutes to pseudocode the game Concentration with a partner. 145 | 146 | The user should see a grid of cards. Clicking a card reveals it and allows them 147 | to click another card. If they match, the cards stay up and if not they flip 148 | back over. Users get a point for every pair they flip. The game ends after 1 149 | minute or all cards have been matched. 150 | 151 | Afterwards, we'll spend 5 minutes sharing approaches as a class. 152 | 153 | 154 | 155 | ## Conclusion 156 | 157 | 1. What are some helpful steps for solving problems? 158 | 2. What does pseudocode help us do? 159 | 3. Do we only pseudocode at the start of a project? 160 | 161 | ## Resources 162 | 163 | - [Introduction to Pseudocode](http://www.slideshare.net/DamianGordon1/pseudocode-10373156) 164 | - [Get Creative Today](http://getcreativetoday.com/lessons/pseudo-code-flowcharts/) 165 | 166 | ## Screencasts 167 | 168 | - [Pseudocoding](https://www.youtube.com/playlist?list=PL-6bwUTtCRVTMUUSjqIYVXYyfZBzs8saD) 169 | --------------------------------------------------------------------------------