## Rethinking my linear function approach in Algebra 2

My treatment of linear functions in the past has been pretty traditional. Solve for y, y = mx + b, graphing using slope intercept, then move on to linear inequalities in two variables...it is just dull this way. Most students have seen it before in one form or another, and it wasn't exciting (or that novel) to them the first time they learned it. It doesn't have to be this way, and I committed myself this year to doing things differently.

My approach has been centered on two big ideas:

1. Linear functions have a constant rate of change. All of the other qualities they have are related to this important fact.
2. There is an amazing connection between graphs, tables of values, and the equations that generate linear functions. These are not three separate skills, they are three views of the same fundamental mathematical object. Corollary: Teaching them on three separate days or sticking to one view at a time creates an unnecessary pigeon-holing effect that sticks with students for as long as conditions in your class permit.

On day one, we did my Robot Tracking activity posted here at GeogebraTube. The video introduction was reviewed in class and students worked on it for much of the period. This emphasized a fundamental concept around linear functions of distance and time that was pretty intuitive to nearly all of the students that did this activity.

Predicting where something is located, assuming it continues moving at a constant rate is one of the most common applications of linearity. We do it all the time. Can we cross the street in front of the bus? Mental calculation. Where should I kick the soccer ball to get it right in front of the forward moving toward the goal? Mental calculation. I don't mean actually sitting down and calculating where it will be, but that the human brain is pretty good at noticing the velocity of objects, and making a pretty good guess of where it will be. They had a number of methods of coming to an answer that ranged from geometric (simply drawing a line) to counting grid squares, using the trace function, and proportional reasoning.

We ended the period looking at the Python script I posted here and trying to calculate speed from the information generated by the program. Part of the homework assignment for the next class was to try to answer the question posed by another Python program posted here. The table of values is randomly determined each time, and students could (and often did) try it multiple times to get it right.

The next lesson had a single instance of this program as a warm up for the whole class - everyone had to agree on what value of position I needed to enter for the given time value.. They were pretty good at checking each other and having good conversations about how to go about it. They answered correctly, but we had a good conversation about the different ways to get there. They all centered on using the fact that there was equal spacing between all of the points. Most students used some variation of finding the distance moved per second and whether it was positive or negative, and then counted off intervals. In most cases, it was a bit complicated and required a lot of accounting to get to their answer.

We went over the reason we could do this - the constant rate of change - and verified it using a few different pairs of points. I then threw in the idea of using the point (x,y) and using the constant rate of change with that point. We got to $frac{y - b}{x - a}=m$ and I asked them to write this using the slope we calculated and any point they liked from the table of data. Students seated next to each other I encouraged to use different points. I then asked them to answer the original question from the Python program using their equation. (Un)surprisingly enough, they all ended up with the correct (and same) answer as before.

Some of them started distributing and writing in slope intercept form. THe thing I was kind of excited about was that they didn't feel the equation had to be written that way, they just felt like seeing what happened. Many discovered the fact that their answers were the same after doing so, even though they started with different points. We did a couple examples of solving more basic 'Write an equation for a line that..." questions, but did so without making a huge deal out of slope-intercept form or point-slope form and why one might be better than the other in different situations.

Today was the third day going through this concept - the warm up activity had three levels to it:

The goal here was to constantly push the students to go back and forth between the equation and numerical representations of these functions. There were lots of good things students figured out from these. We then made the jump to looking at how the graph is connected to the table and equation - just one more way of looking at the same mathematical function, and it shares the meaning that comes with the other two representations: a constant rate of change. The new idea introduced as part of this was that of an intercept. What does it mean on the graph? What does it mean for the table? We didn't talk explicitly about the intercept's meaning of the equation (again, trying to avoid the "that's just y = mx + b, I know this already...TUNED OUT") , but it came out in the process of identifying it algebraically, from tables, and then graphing.

By the end of the period, we were graphing linear functions. Students were asking excellent questions about when the intercepts alone can be used to graph the line, when they can't ($2x+3y=6$ versus $2x+3y=7$) but they again stuck to the idea of finding a point they know is on the graph, and then using the constant rate of change to find others. Instead of spending a boring lesson explicitly telling them what my expectations are for graphing lines (labeled and scaled axes, line going all the way across the extent of the axes, arrows on axes and lines) I was able to gently nudge students to do this while they worked.

We'll see how things go as we continue to move forward. The big thing I like about this progression so far is that modeling real phenomena will be a natural extension of what we've already done - not a lesson at the end of contrived examples with clean numbers. My goal originally was to get this group comfortable with messy data and being comfortable with using different tools to make sense of it.

I've kept my students hermetically sealed from this messiness in the past - integer coefficients, integer values, and explicit step-by-step ways of graphing, generating tables, and writing equations. As I mentioned before, it was, well, boring and predictable, and perpetuated the idea that these skills are all separated from each other. It also continued the pattern that there would be a day in each unit where the numbers are messy, the real world word problems day, but that the pain associated with it would last a day and would be over soon enough.

I'm hoping to reduce this effect by changing my approach. That by seeing the different aspects of linear functions, it will seem natural to use a graph to figure out something that might not make sense algebraically, or use numerical values to solve an algebraic problem. I especially like this because exploring the three views of functions really is, in my opinion, the primary learning goal of the Algebra 2 course. If I can establish this as an expectation early on, I think the latter parts of the course will work much more smoothly.

## "What can you do with this?" (WCYDWT) - Flood Gates Open

I've been making an effort to look for as much WCYDWT material as possible on a regular basis. This is not so much because I've had students asking 'when are we going to use this' though that is always brewing under the surface. Instead, I've been making an effort this year to spend less time in class plodding through curriculum, and more time getting students to get their hands dirty with real data, real numbers, and using their brains to actually figure things out. By recording screencasts, doing demos, and using Geogebrs, I've made some progress in getting the students to see the benefit of learning the routine skills-based stuff on their own for HW so we can use class time to do more interesting things. I've quizzed and am feeling pretty good about this thus far, but we'll see.

During my trip with the ninth graders to Shandong and my week off due to the national holiday when my parents visited, I've kept my eyes open on reasonable, non-contrived problems that might serve as applications of linear functions. I've wanted some problems with non-trivial answers along with some low-hanging fruit that might give all of the students in the class a way in.

I'm pretty happy with how things have ended up with the top three contenders. There are some other things in the works, but I'm hoping to keep those under wraps for the moment. Click on the links to read the details.

This one I already started talking about in a previous post, but I spiced it up just a bit by putting images together and throwing the head image I've now used in a few places to be cute.

Ms. Josie and the 180 Days

I like this one especially since it has a good story behind it. My students know my wife, and I defer to her awesomeness quite a bit in class. Students certainly love it when their teacher is willing to knock him/herself down a few pegs, especially when it's for their entertainment and for comedic effect in class. I think this challenge is a good combination of mathematical reasoning and drama - I don't think I can lose!

Moving on up at the Intercontinental Hotel

I was looking for a third one that really jumped out as kinda cool and visually stunning since the others, though cool, weren't particularly impressive visually. On the last day my parents were in town, we went to the Intercontinental hotel in Hangzhou and the problem smacked me in the face.

The videos aren't all up yet - in addition to the two outside videos, the more enlightening videos (which I will post tomorrow before class) have a view of the elevator doors and the digital floor display as the elevator moves up and down. In addition, there is a nice reflection of the view out the glass wall of the elevator, beautiful in its own right, but perhaps a wee bit distracting from the really useful stuff in this problem. If I wanted to go the full-eye-candy route, I suppose I could have gotten a reflection of the elevator doors and floor display in the glass wall of the elevator. Maybe next time.

My plan is to let students choose which of the three projects they want to work on, and then give them tomorrow's class (and finishing up for HW) to put something together. I plan to grade according to this rubric:

I think it gives them enough detail on what I want them to do, without being overly difficult to grade. I am even thinking of giving them a chance to grade each other since they will all be posting their work (from groups) on the wiki page.

I've had these things in my mind for a little while - I admit, after how this particular class made an impressive effort I am really excited to see what happens next.