Reflections 2016-11-2

Standard

Computer Science:

The struggle between collaboration and focus is real. We started out ok with just a little talking but it was not enough to mess up someone who was flowing with the activity. Ā But after about 15 minutes I noticed that the noise level had increased to the point where it was impossible to ignore. How did I notice this? Because it was impossible to ignore! šŸ˜‰ Maybe the lesson is that 10-15 minutes is a magic number and we need to stay within that time frame for activities in here. Or we might try 10 minutes silence, 2 minutes talking or some other time strategy like that.

We are trying to do our daily reflection in silence in our notebooks today (as opposed to the spreadsheet on the computer) so we packed up the computers and wrote for about 5 minutes. I think this class knew the drill for the most part because they are mostly Engineering students. I think that maybe I should start writing my own reflections in my Engineering notebook as well; that was the point, to model the process right?

Ā 

 

Advertisements

Reflections 2016-11-1

Standard

Computer Science:Ā 

We started learning python today. As expected, it would have been totally impossible to lead the class through the first activity. Everyone was at a different pace and there were a lot of technical difficulties. So it was a good thing that the activity is well written so that they could follow at their own pace.

Mini lessons included:

  • using the up arrow to retrieve the previous command
  • variable types (python assigns them for you)
  • .py files are text files

Intro to Engineering:

I realized today that there is a big skills gap between students who took the Gateway classes and those that didn’t. I don’t think I need to modify the activities in the automaton project, but they will need more time to learn the skills. We continued with the manufacturing a box activity, but no one finished it because they were learning skills and then trying to apply them right away (as opposed to the “Gateway” Ss who have the skills and are just applying them).

Reflections 2016-10-31

Standard

Introduction to Engineering:

This class is really high energy and we discussed this again today. Strategies we discussed included taking a break when you need one. I think this may be an opportunity to work with breathing techniques with a few students. Because I think that they need a redirect more than once or twice per class, so taking a break by leaving the room might take too long.

I also think the Automaton project is going really well. We are using the “manufacturing a box” activity to learn assembly constraints in Inventor. They are making box joints like the one below, so they’re making the sides as part files and then assembling them.

box_joint

Mindfulness. Not just a buzzword.

Standard

So I startedĀ tblreading this book. I had been thinking about getting a book on mindfulness specifically aimed at classroom teachers, but this one came to me! My wife went to a conference (Momentous I think it was called) and came back with three or four great books. So I stole this one ;).

I feel like I have a head start on some of the things that she talks about in the first few chapters because of my yoga practice. When she talks about breath, I canĀ feelĀ what she means. Like the way it feels when you breathe in through your nose and the air swirls around in your mouth and heats up a little bit. It slows me down when I notice that.

I have already gotten a lot of great advice from the first section of the book. The other day, I was so close to snapping at a student when he didn’t take his seat after I had asked the class several times. But I took notice of this emotion right away because I was being mindful. I stopped, took a deep breath in, felt the air swirl around in my mouth and heat up a little. This noticing centered me and it only took a few seconds so I was still in a position to handle the situation appropriately. I asked the student if there was a reason he needed to be standing up. This question was intended to get him to think about it for himself. We have previously talked about strategies that will allow him more movement throughout class, like we have a stand up station set up for him when he needs it. Ā This time, he just wasn’t paying attention and so he just took his seat, but my hope is that he will begin to realize for himself when heĀ needs to stand or move around and when he just needs to try and focus. Maybe we’ll work on mindful breathing soon.

But what I’ve found most helpful so far is Ms Srinivasan’s description of helpful and unhelpful seeds. In that situation from the other day, if I had snapped I would have most definitely been watering an unhelpful seed. This student does not respond well to a stern “teacher voice” sort of discipline (and I know this!). So by giving him that feedback, I would be reinforcing in his mind that I am not there to help him, but just another hassle in his day to get through. By not reacting, breathing mindfully, I was able to water a helpful seed. And writing about it here is helping me to water this same seed in myself! šŸ™‚

I am super excited about sharing mindfulness techniques with my students, but I know I need to practice more myself first. One thing at a time.

 

Reflections 2016-10-27

Standard

Computer Science:

Getting everyone to stop what they are doing and write a reflection on the day is kind of hard. A bunch of students will typically continue what they are working on, and then it’s weird for me to be like “stop working on your awesome app that you are making”. But I think the reflections are going to be really important. So maybe I need some sort of incentive in order to get them Ā to write good ones? I am modeling the process now by projecting this on the board as I type it, not sure anyone is reading it though. Students: if you are reading this, let me know!

 

…they did šŸ™‚

 

Reflections 2016-10-26

Standard

Intro to Engineering:

We got most of our motors working with Arduino today. It was difficult at times to figure out who needed my help the most. I think I need better structures for them to help each other out on a project like this. Or maybe we just need more training in figuring out who can help. Like for this one, it was “whose motor is working already? how did they get it there? what was their troubleshooting process like?”. If I am more explicit about these Qs beforehand next time, maybe it will be easier for them to figure out.

Computer Science:

Another work day for creating apps in App Inventor. It is interesting working on problems along with students and it comes up a lot because I haven’t created many apps myself. The problem of using the “otherScreenClosed” function needs more time to figure out. We tried using the tutorial here but didn’t get it to work overall.

 

Reflections Every Day!

Standard

At some point last year, I started writing reflections on the board at the end of each day. It was a really good practice that somehow I lost track of over the summer and haven’t done at all this year. But as part of my new no-grades assessment scheme, I am having students do a reflection at the end of each class. How I didn’t put it together that I was supposed to be doing these reflections also (in order to model the practice) is beyond me!

So here I go. I am going to start reflecting at the end of each class (visibly! this is being projected on the board right now as I type).

Computer Science Principles:

Today was a work day on the Project: App Inventor. It was nice to have a full day just to work on the apps, as opposed to trying to fit in a mini lesson or something else. Almost everyone in the class seems to have paired up in some way even though everyone is engaged in the work, so there’s no “well I have nothing to do because so and so is doing everything”. I think this is the right grouping mechanism moving forward:

  • everyone starts creating on their own
  • groups are formed based on interestsĀ after they have explored/tested for at least half a class
  • everyone submits their own version of the code

Intro to Engineering:

We started the Automaton Project today by looking at lots of examples like this:Ā pig

 

 

Then we discussed the main components of the project, which are the box, the cams, and whatever is on top. I think the pairs that I made for them are going to work. Now that I know the kids a little better, I am able to make pairs based on who is going to work well together.

We also did a basic Arduino project, which I am stupid excited about! They just used a transistor and diode to hook up a motor and a button. Only one group had it working by the end, but that’s what I expected. Next class: troubleshooting!