Broncos make an expensive mistake on C.J. Anderson alvin March 15, 2016 - 9:46pm

Note: I write all of the following as a fan of the Denver Broncos and C.J. Anderson.

Don’t believe what you read from the Denver Broncos front office today (3/15/16). They made another mistake this offseason — a very expensive mistake this time — by not making C.J. Anderson a mid-tier free agent at $2.356M. That offer was only $800K more than the first-tier offer they made, and because other teams would have had to compensate Denver if they signed Anderson, it’s unlikely anyone would have offered him a contract. Because of this mistake, Denver will have to pay Anderson almost $6M this year, and another $4-5M next year, with something like $1.7M of that guaranteed. (I don’t remember the exact number.)

I have no earthly idea why the Denver management team did this. So far in this offseason they really seem to be off in trying to judge “market value.” I don’t care that they lost Osweiler, but with this move they’ve cost themselves a lot of salary cap money, which would be really nice to have because they need to sign a new starting QB.

As Mark Schlereth just said on the radio, the move was “reactionary” and a “panic move.” His radio partner said that Anderson is now the fourth-highest paid RB in the NFL.

(Image from this page.)

Follow your interests

Following up on the “keep learning” theme I wrote about a little while ago, I also encourage you to explore any personal interests you have, in technology or otherwise. In my case, over the last few weeks I’ve been working on my Android football game, and while it currently pisses me off more than it makes me happy, I can see its potential. And beyond that, I’ve learned a lot more about Android than I would have learned any other way. I don’t know where this will ever lead, but I do enjoy the game, and it has laid a foundation for the future changes I know I want to make to it.

P.S. A strong running game and third-down efficiency are also important. ;)

A Java method to calculate the NFL Passer Rating alvin January 16, 2016 - 3:58pm

Note: The code below is based on the Wikipedia formula, which is not correct. The correct algorithm seems to be at this page. I’ll update the code below once I verify this for sure.

In working on my “XO Play” Android football game, I just created this Java method to calculate the NFL Passer Rating for my quarterbacks:

Third UI version of my football game

These screenshots show the UI for the third version of my XO Play Android football game. The UI for when I’m playing offense is shown on the left, and the UI for when I’m playing defense is shown on the right.

The defense is pretty limited — you can only choose from three current defensive plays — but that actually inspired me to show the history of previous plays called by the computer on the lower-right of that screen, which can be useful to see the computer’s tendencies.

I’m still not blown away by the UI, but it is getting better. I like the idea of having the “Hike” button close to the playing field, as that’s where your eyes will want to be when the button is pressed, but I’m not blown away by my implementation.

XO Play lesson: Game perspective is important

One thing I learned last night about my XO Play football game is that even in a “thinking man’s game” like this, visual perspective is important. I thought I would like the game as I showed it yesteday, as if you were looking at it from a coordinator’s box or sideline seat, but even though this image is a poor mockup and the perspective isn’t great, I like it better. (And of course now this makes me want to show real players (with depth) instead of Xs and Os.)

UL vs Texas A&M (Music City Bowl, 2015)

For me, seeing the University of Louisville (UL) and Texas A&M play this afternoon must be how it feels to see two of your kids fighting. When I went to UL I lived in the basement of the house on the left, and when I went to A&M I lived in that brick and cinder block place on the right.

As George Costanza would say, “An Al divided cannot stand.”