To actually do something, I usually require a reason. I am a lazy person and I abhor work for the sake of work itself. I’ve known I really should learn Python at some point, but never had a good purpose. The thing that really struck me at in my one MIT book is the use of state machines to break down a problem into really small bits of code.
Entirely for fun I guess who the winners each weak are in the NFL. My record sucks. I usually do better than 0.500 but compared to other people, I show my obvious lack of knowledge. I’m cool with that. It’s fun. I was thinking though. As the impetus for better coding, why not look at my picks.
I’m figuring start by making a spreadsheet of every season game. Have all my data, or at least the ability to add it in later. Ooh 80, I could totally make it better. I don’t do any real work. I could have my script make its own tweaking after giving the data and rough handlers. It needs to know that one game affects two different teams. These teams both played in one stadium, giving only one team home field advantage, both both are affected by the weather in separate and distinct ways, not only for the teams, but the field itself.
So I have my raw data that it can mangle to its hearts content, and then complex data like the weather.
Right. Let’s do this.
Peter's stuff.