Creating Coding Lessons – Grade 6-8: Part 2

Any time I try something new I get some unexpected results. Often I learn something new. Usually I tweak something. Sometimes I find a connection to something else. My students find the lesson easier or harder than I expected. I’ve even discovered that some of my basic assumptions were faulty before. This time is no different. This coding lessons reflection will be of dubious use to you without having read this post. Don’t let me dissuade you though, read away. What follows is an outline, and reflection on what I have done for the coding lesson I am working on so far.

I tend towards jumping right in, and being flexible as I go with new lesson ideas. I know that others prefer to have every moment planned out in advance (and there’s nothing wrong with that), but I am more comfortable winging it a bit. That isn’t to say I don’t have a plan, it’s more to say that my plans are fluid. I trust my research and experience to guide me as I go. This post is a bit different than usual as well. There are a lot of moving pieces to this lesson, and I’m writing to focus my own thinking in addition to documenting what I’m doing for others.

Refined Overview

I am working towards several goals in this lesson. First, I want to provide a solid foundation in computer science to my grade 8 students. Second, I want to introduce my students to some basic web design. Third, I want to give them an outlet for their desire to create. Fourth, I want my students to be less dependent on me for the knowledge they require, and finally I am exploring how to differentiate a performance based lesson across students of varying needs.

Students learn different subjects in different ways. Some students require more scaffolding than others in order to benefit from a lesson, other students learn best with more independence, and still others require something in between. I have always been of the opinion that it is not a given student’s responsibility to learn how I teach. Rather, it is my responsibility to teach how they learn. In the immortal words of Mr. Miyagi: “Teacher say, student do”. My hope here is that I can create a lesson for all students.

Assignments Thus Far

As mentioned here, I started of with a simple tutorial for the Talk to Me App in App Inventor 2. Additionally, I assigned the students to create a google site, populate it with an About Me page, a Links page, a Classwork page, and a Portfolio page. We did the tutorial, and the web site assignments together during class. They were also given a question to answer about computers in general.

Students are required to create a project page for each app, and to fill it with documentation and reflections on each project. After the first assignment they have been given several more in rapid succession. They were assigned the second part of the Talk to me App, the Ball Bounce App, and were tasked with making unique improvements for each app as well. All of the apps up to this point are part of App Inventor’s Hour of Code. As part of these apps we have discussed the concept of abstraction in computer science. Additional App assignments will be designed to cover other topics mentioned in my last post. As an assessment for this first, basic section I asked students to work through the set of tutorials under the Paint Pot App. This assignment is different as I am not giving students class time to complete it.

Coding Lessons Reflection

All assignments are given in the google classroom, and students are encouraged to ask any questions in the google classroom as well. They are also encouraged to answer each others questions.  The first App assignment, and the first web assignments are the only ones we do together in class. The rest will simply be assignments. Students are given class time to work on their assignments. I also expect them to answer many of their own questions through internet research.

There was some push back on these ideas at first, but students are really beginning to embrace this style. This manner of having video tutorials, and performance tasks is allowing me the time to help those students that need it while allowing other students to work at a more accelerated pace. I don’t know yet how the assessment will pan out. My goal is to have students doing work outside of class which will foster greater levels of collaboration on their sites, and in the classroom. My main concern with this is that some students may be unable to work from home because they lack a computer with internet. We’ll see.

I’ve mapped out the app assignments for the rest of the quarter already. I am however, still trying to fit in the concepts & practices I discussed in the first article. That portion is a moving target that I will revisit periodically. Certainly, the app assignments will have most of these ideas built in. My challenge will be to pull out these specific concepts & practices to shine a light on them. A lot of this will come into greater focus as student move away from tutorials, and into building their own unique ideas, but I need to keep them at the top of my mind.

Differentiation in Coding Lessons Reflection

One of the pleasant surprises I’ve come up with is that assigning work in this manner is exceptionally easy to differentiate. In my current class I have several students who are incredibly comfortable with the subject matter, several who are moderately comfortable, and several who need significant scaffolding in order to be successful. By taking myself out of the initial distribution of knowledge to my students, I allow myself to be available to scaffold where needed.

Additionally, by forcing my students to add unique features to their apps I have allowed my students the opportunity to dictate their own level of challenge. Improvements to an app can run the gamut from changing the color of the screen, to translating typed text into another language before “speaking” it. What I’m left with is a room full of engaged students who are given the exact amount of support they require. This has allowed me to view all of my lessons differently, and will change how I teach moving forward.

Next Steps

This Coding Lessons Reflection would be of reduced value without a discussion of where I plan to go next. The rest of the course will continue to be focused on App Tutorials, and web design. In order, the apps I will assign are:

• Magic 8 Ball
• Persisting Photos
• Android Mash
• Logo (App Template Here)
• Student Designed App Number 1
• Presidents Quiz
• No Text While Busy
• Socially Aware App
• Student Designed App Number 2 (Final)

 

As time goes on the tutorials begin to focus on specific features without repeating information. Many deal with some pretty advanced programming concepts so, I’ll have to pay close attention to how my students are doing. There’s a good deal of work left to do on this unit, and I expect to make revisions as I go. I will continue posting about what is going on with the apps individually, as well as what’s happening in my classroom. The really interesting items will be what the kids come up with for individual apps.

Conclusion

Though I am essentially 20% through this first iteration of my coding lessons curriculum there are still a huge number of questions that need answering. I feel like it is going well, and I am excited to see how everything pans out in the end.

Thanks for reading, and if you’d like to keep updated on what’s happening on the blog please sign up for email updates. I promise I will never send you anything other than updates on my posts. Additionally, the more you share this around the more people will get use out of it. Please use the buttons at the top of the post to let everyone know whats happening here.

 

Creating Coding Lessons – Grades 6-8: Part 1

As a STEM teacher I am continually taking workshops and courses to get better at my job. As a public school teacher I am always on the lookout for those who are willing to donate equipment to my program. While on a follow-up call for a coding PD I took last summer, I was asked what I would need in order to implement coding fully into my curriculum.  My answer was simple: “I need 9 new Android tablets”. I was half joking, but you miss 100% of the shots you don’t take. When the response was: “Okay we should be able to get those to you in January”. I realized I needed to begin Creating Coding Lessons for my grade 8 students, and the idea for this post was born.

If you don’t have access to an Android device for each student (or each pair if you are using pair programming), check out this post for your coding lesson needs.

Creating Coding Lessons Overview

I am Creating Coding Lessons for a 10 week course for 14 grade 8 students. We use tablets and cellular phones running the Android operating system to run our programs. We use Chromebooks, and the App Inventor 2 IDE to create them. This course focuses on teaching Computer Science fundamentals, and specific event based programming skills. Class time is spent on performance tasks, and all assessments are performance based. Any lecture is video based. For the final assessment, students will create an app that solves a real world problem. Successful completion of this task will show mastery of the content at Depth Of Knowledge (DOK) 4. The process for Creating Coding Lessons for this unit will be outlined over several posts.

Standards framework for Computer Science Education in primary grades is evolving. No clear system with fully developed standards, and practices seems to be available. There is a generally accepted framework I will be working from which can be found here, but this will be my interpretation of the general concepts they recommend.

Unlike most of my curriculum posts, I will not initially be focused on a full STEM implementation here. Eventually, Math and Science will be integrated, but to start I will be focusing on Technology and Engineering. Designing a full fledged STEM unit is a daunting task, but designing a focused unit to be altered later is significantly less problematic. In this case I am under a time crunch to start teaching this unit so, Creating Coding Lessons for it needs to happen quickly. Remember that much like the design tasks we use to teach engineering, we can iterate on our lessons. In fact, none of my lessons are exactly as I originally envisioned them.

Creating Coding Lessons Practices

K12cs.org outlines 7 core practices of Computer Science that students in all grade bands should work towards mastering. Within the greater context of the coding unit each performance task should be working towards fostering the following.

1. Fostering an Inclusive Computing Culture: This practice refers to the idea that computing is for everyone, and that perspectives from various genders, ethnicities, and abilities have positive effects on computing.
2. Collaborating around Computing: This practice encourages individual students to become used to working collaboratively on teams, and in pairs.
3. Recognizing and Defining Computational Problems: This practice fosters the ability to recognize, and define problems that can be solved with computing.
4. Developing and Using Abstractions: The concept of abstraction revolves around helping students develop the ability to generalize portions of a solution for reuse in other computational problems.
5. Creating Computational Artifacts: This practice involves having students actually create things as opposed to just learn about them conceptually. Students should create programs, videos, robotics systems, and apps as part of their study.
6. Testing and Refining Computational Artifacts: This practice refers to having students iterate on their creations.
7. Communicating About Computing: At its core this practice asks students to not only create computational artifacts and iterate on them, but also to be able to describe what their creation does as well as how it does it.

 

Creating Coding Lesson Concepts

In addition to the core practices as outlined by k12cs.org there are 8 Computer Science core concepts. These concepts are broken out by grade band level. This set of lessons is focused on the 6-8 grade band. Additionally, this set lessons is designed to teach students these concepts to a level they should know by the time they graduate grade 8. The descriptions for these concepts, and what students need to know by the end of grade 8 are found here.

• Algorithms
• Variables
• Control
• Modularity
• Program Development
• Culture
• Social Interactions
• Safety, Law, and Ethics

 

First Lesson

As evidenced  by the Concepts & Practices above I am teaching far more than simply app development.  I will use the App Inventor 2 IDE & Google sites for the lesson, but I am teaching a core of Computer Science. As it turns out, I just had my first class in this lesson today. After the normal opening day items such as how to get permission to use the rest room, and safety concerns we really only had enough time to get set up with the various systems that will be in play for this class.

Google Classroom

For this course I will use Google Classroom primarily to assign homework, and give students direction for independent research. I use Google Classroom, because I am at a Google school, I’m certain that there are other tools available, but I find it very easy to use, and it’s available to me. Since I am working towards teaching Computer Science through App Development the first thing I did was assign the students a set research questions, and a video.

The questions are: What is a Computer? What are it’s features? What is Computer Science?

My students are asked to research the above questions, and provide answers on their individual Google site. I made the questions broad based intentionally to see what the kids come up with. This question set serves the primary purpose of getting students used to research. The discussions that will follow will work to refine their understanding of computer science. By the end of this course they should have a better understanding of the above concepts.

The video I assigned is here and just covers the basics of the App Inventor 2 IDE, as well as walking learners through creating their first app. We will actually create the app in class, but I wanted them familiar with the video before we work through it. I gave my students the option of attempting the project by themselves as well. Allowing students this opportunity will take advantage of their excitement, and allow them additional autonomy if they would like it.

Google Sites

In addition to software development, web site design is another foundational Computer Science skill. Teaching some simple design, with a simple tool will make later exploration more efficient. I also want to have a way for my students to effectively collaborate with one another in their work, and to archive their work. With all of this in mind, having them create a digital portfolio is the right call. Again, I work at a Google School so I have access to this tool, but others are certainly out there. Additionally, for younger students I really like Google Sites. It is easy to use, and incredibly easy to control who sees the content. One of the things I am trying to teach my students is the concept of safe computing, and one of the foundations of safe computing is limiting access.

Some things to keep in mind here are that students will need to “share” their site with you in for for you to view/edit it. You should also have them set their privacy settings to “anyone with the link”. This allows them to share it more easily while keeping the  circle of viewers small. I ask my students to set up an about me page, a links page, and an assignments page to start. When they complete an assigned question they put the link to their answer in the comments to the question in google classroom. Later I will have them collaborate using their sites by posting links to them in the google classroom.

 

Talk to me App

The first App we will develop is a simple piece of software that is designed to use the text to talk feature of the Android Operating System. This feature allows a user to input a string of text, and the computer will “read” that string out loud through the device’s speakers. In this first iteration of the App, students will program in a graphical button on the device’s screen which when tapped will “speak” a pre-determined statement. The tutorial for this app can be found here.

This particular App isn’t overly complex. It requires changes to the code itself in order to change the message spoken, and only has one component. However, if we look a bit deeper it teaches a good deal more than we think. First, this tutorial, and the app created with it gives students a solid overview of how App Inventor 2 works, which will serve them well later on. Second, it shows all of the computing practices outlined above. Thirdly, it opens up conversations about algorithms, program development, and modularity. You can also add important general coding good practices such as annotation. Finally, this program allows you to ease students in to how you will be assessing, and grading them.

Grading & Assessment

If you’ve already had a look at my Ev3 Robotics Lesson 2 post you are familiar with my method for assessing a computer program. Assuming you haven’t gotten to that post yet, I assess computer programs by breaking them down into three measurable components. They are Accuracy, Efficiency, and Annotation. Accuracy refers to whether the program functions predictably. Efficiency deals with how many commands are used, and Annotation refers to what manner of commentary a program contains. In the case of this first lesson, as we will be creating the program in class by following a tutorial so using this method gets a bit tricky.

For most of my classes I use a class participation rubric, which would apply here. When students have advanced sufficiently for assessment I create a separate rubric for the assessment. For an example of what that may look like, click the link in the first sentence of this section.

Part 1 Conclusion

This first article is about getting set up to teach using  variety of tools. Though the first lesson is discussed here, it is not done in detail.  I will do a series of reflection posts about how the lesson is going, and discuss further lessons in greater detail. If you found this article helpful, please share it wherever you think it will do the most good. Stay tuned for more in this series.