Saturday, November 24, 2012

on hashtags: who needs 'em

ever use twitter?  no?  then please move along... nothing to see here.

but if yes...  do you know what a hashtag is?  hmm... are you sure?

c’mon, everyone knows this right?  you tweet about something, just find the keywords in there and drop a # in front of those, like this:

right?  not really.  the fact is, sometimes hashing helps, sometimes it doesn't, sometimes it makes no difference, and sometimes it actually works against you.

it’s simple...

step 1:  use a hashtag when it helps someone find your tweet.
step 2:  don’t use a hashtag when it doesn’t help, or even makes it harder to find your tweet.

sounds kinda "duh", but it’s not. the key is in figuring out the difference.  in the end, it's more important to know when to not use a hashtag as it is to use one.

why?:  because the only reason why you spend time tweeting is so that most people who might have an interest in what you’re saying, get to hear you say it, and so that you can all then participate in the conversation.

first, what are other twitter advice blogs saying?:

they say "keep it short":  well, sure.  also true about your twitter name, and everything else about your tweet.  some might say 140 char isn’t a lot, but you’ve seen those tweets that are 100-140 char long.  who reads them?  our time is short, move along.

they say "keep them unique":  well, sure.  also true for anything else you search for using any social media tool or even any google search.  but in the end, it isn't like hashtags are registered or regulated.  anyone can use them.

some simple tips for quitting hashtags

tip #1:  omg...  first... do a twitter search on your tag to see if anyone else is using it.  and... for the same purpose you want to use it.  if no one is, then don’t hash it because no need using it to make your tweet findable if no one's looking.  for example, i was going to tweet about the new york giants, so i started with #giants just to find that there are conversations about football and baseball in there.  so then i searched #nyg and #bigblue to find not so much traffic.  finally i found most of the conversation is tagged with #nygiants, so i used that one because that's where the chatter is.

tip #2:  if you want to be a part of a conversation, and the words you think will get you in are unique enough, don’t hash it.  words like shakespeare, nascar, nfl, facebook, knicks, thanksgiving, and astronaut

tip #3:  stay away from underscores, hyphens or other special characters that cause smartphone users to have to toggle their keyboards or shift to upper-case.  just squish it together, we won’t get confused, we promise.  everyone is using #stanleycup not #Stanley_Cup (or they would, if the nhl wasn't on lockout).

tip #4:  tweets made available for searches don’t last more than a few days, so really no need to be more specific than that.  example:  for our developer summit conference in california in march, we used #devsummit.  for the summits in november in europe we used... yep... #devsummit.  not #devsummiteurope or #devsummit2012.  tweets are too fleeting for that.

some examples of when hashtags are not needed:

if a word is unique enough, putting a # in front of it is simply not necessary.  The name obama is fairly unique as the topic in a tweet.  we get it, you’re talking about the president.  why use #obama?  those who are searching for tweets about the prez will be better off searching for obama, because it’ll find tweets containing obama and #obama.  Search #obama and you miss obama.

the company i work for sells a software product called “arcgis”.  reasonably unique.  too often i see people dropping a hash in front of it.  why?  it burns a character.  but even more important... if i search on #arcgis, i only get #arcgis.  but if i search on arcgis, i get both arcgis and #arcgis.  better.

in the example at the top of this article, the terms Socialist, Marxist, and POTUS are also unique. why hash them?

but there are still times when a hashtag helps:

conversations about last month's hurricane that struck the east coast did benefit from being an actual hashtag:  #sandy, since otherwise your search for info would also catch tweets about other people (sandy koufax, sandy alomar) or places named sandy (sandy hook, new jersey [also hit by hurricane sandy]) or things that are sandy.

during washington capitals hockey games the hashtag people tend to use is #caps.  good thing, because that word could mean a lot of things and when it does appear in a tweet, it's usually not the keyword unless it's about the hockey team.

in short:  just tweet about what you want to say.  if the keywords are ambiguous, hash them.  if the keywords are unique then don't, else you could make it harder for other tweeters to find what you're saying.


Saturday, October 6, 2012

hey hey, ho ho, infield fly rule's gotta go

yet another disclaimer: i'm kind of a mets fan, atlanta losing is normally a good thing, but...

sports get better when judgement calls go away.  until yesterday the MLB's own twitter site  contained this snarky quote in the bio section:

"yeah, we don't understand the infield fly rule either"

oops, probably best to get rid of that.  so they did.

why does the infield fly rule exist?  well, i found this on the internet so i know it's true:

"is a fair fly ball which can be caught by an infielder with ordinary effort, blah, blah, other stuff about existing runners and outs"

oh geez, i love this part of MLB's own rules:

"[this is a judgement call] not by some arbitrary limitation such as the grass, or the base lines"

well sure, because lines are arbitrary [eye roll]. we wouldn't want baseball muddled with other lines like foul lines, the batter's box, the pitcher's mound, the outfield fence.  let's just make it all judgement.

baseball is so adorable in the way it's steeped in clumsy traditions, nutso superstitions, and unwritten codes.

i can hear it now... but jimbarry, it's so that the fielder isn't able to choose whether he wants to catch it (and double up runners who stray too far) or drop it (and double up runners who didn't stray far enough).

i know.  i get that.  my answer is, "so?"  why can't that be part of a fielder's strategy?  the ball is in play, let it be in play and let the players on the field all decide what they want to do.  just like any other ball in play.

in fact, while we're at it...

let's make balls and strikes a judgement call

i mean, we all know that the edges of the plate are lines, also knees, armpits.  even 30 year old technology can locate a 100mph fastball well within one millimeter well within one millisecond.

let's toss that out and ask the home plate ump to just call it...

so that he can toss in personal bias, his own body position, game situation, and how cool he's going to look to the home crowd and espn rambo-punching out that third strike a foot outside to end that playoff game.

oh wait, we already do that.


Thursday, September 27, 2012

the case for golden tate

woot!  the old refs go back to the field, the new refs go back to foot locker, and next week we can complain about the higher paid refs making higher paid mistakes.

you can say it's been fun watching goodell and the owners stew, you can say it's not been right that we've been talking about the contract drama more than the game, but you can't say it's been boring.

common sense test?  sure...

md jennings:
two hands on the ball in the air, two hands on the ground, ball to his chest the whole way

golden tate:
one hand on the ball in the air, then two, then one then two, never on his chest til the pile ended.

if your wallet contains one of these things here, you probably think tate caught a touchdown pass.

...the rest of us with eyes know different.

but y'know what?

i actually think the running shoe salesmen were right: tate scored a touchdown

let's do this...

one rule says
"if a pass is caught simultaneously by two opponents and both retain it...[tie goes to the passing team]"

which brings us to what "caught" means, which is when the
"...ball is secured by one or both hands and both feet or any other part body other than hands touch the ground".

the video shows that by the time tate's feet were on the ground, he had two hands on and control of the ball.  better put, because it was called a touchdown on the field, there's nothing in the video that shows that he didn't.  in fact, when this happens in the end zone, that's an immediate touchdown and the play ends.

and it's more important to add that at this moment, both of jenning's feet were still in the air.

another rule says that "it's not a simultaneous catch if a player gains control first and an opponent then gains joint control".  and you can gain control before your feet come down.

but here's the problem with that.  first, the video shows that at the same time jennings gained control with two hands, tate gained control with his left hand.  how can we be reasonably sure both had control?  because the ref could've reasoned that if one didn't have control he would've lost the ball to the other.

the fact that jennings controlled the ball more does pass the smell test, but two-versus-one is not part of the rules.  it is possible, according to the rules, to catch a ball one-handed.  plaxico did that one-handed shit all the time.  c'mon... he even shot himself one-handed.
(and if he'd done that in new jersey instead of new york city, he probably would've never went to jail either)

the fact that tate took a while to get his second hand on the ball doesn't mean he gained control after jennings did.  at least according to the rules.

when it comes to judging what control is, that's a call on the field and reviewable under the hood.  and remember that the hood isn't for making calls, it's for seeing if there is any opposite evidence than what was called on the field.  there's nothing in the video that suggests that tate didn't have control of the ball also (no evidence that he lost it, or that the ball slid or wobbled around)

you can say that tate pushed off (foul) before the ball got there, and he did, but that wasn't the call on the field.  and besides, have you ever seen interference called on a hail mary?  never.

but... i'm glad that happened on monday night football, because it seems that's what it took to get the deal done.


Friday, August 10, 2012

on same sex marriage

(i expect this to be the first, only, and last "political" post on my blog, but we're 3 months from the 2012 election and this is a topic that defies logic and i have to vent and say something.)

disclaimer: i'm a conservative. 

sounds like i'm supposed to ignore some key things i've learned and lived about core conservatism and join the fight to defend society against same-sex marriage.

i'm also straight.  no dog in this hunt.  but why aren't more conservatives on the "pro" side of this?  or at least "hey man, that's your business not mine".  we're all about individual rights, especially when those rights don't inflict on anyone else's?  aren't we all about freedom to follow our chosen life path and not imposing our views on others?  

anywho...  here are 10 things the "new right" say about it.  i went and knocked some logic against all 10 and ended up with a perfect losing record of 0-10.  can you do any better? (or worse?)

1.  because The Bible says so

well...  all this tells me is that some parts of Leviticus are important and some not so much.  but no one ever says how they know which is which.  or what this means to americans who don't follow The Bible.  

2.  marriage is for breeding, so... opposite-sex couples only

true.  the biology isn't there.  then what about these?:

a.  ...a post-menopausal woman can't get married
b.  ...a man without testicles can't get married
c.  ...if a couple chooses not to breed, we take away their marriage license

these 3 points above follow the same logic and aren't opposed.

3.  gay marriage destroys the sanctity of marriage

divorce does.  infidelity does.  even if same-sex marriage did, why isn't divorce illegal?  yet again the logic is very selective.

4. if gays can marry, then the gov't will force my church to marry gays

no it won't, can't, shouldn't, never has.  nothing shows it ever would.

besides... your church already has the right to choose who it marries, doesn't marry.  no level of gov't is stopping you.  that's religious freedom.  to bring it up as resistance to same-sex marriage is a red herring.

5. if gays can marry, then our schools will have to teach homosexuality

public schools teach human sexuality as part of their health curriculum.  they're not teaching sexual preference as right or wrong.  if they were, then fight that.  until then, schools teach biology and hygiene. you as parents teach them the rest.

6.  legitimizing homosexuality will only encourage it to grow

us "straights" are born this way, and you can't convert me to be gay. same goes for gays. all i can tell you for sure is that if i were a woman, i'd be a lesbian.  it's the way i'm wired.

in fairness, if some are confused, not sure, figuring themselves out, seeking out counseling.  ok sure.  then in those cases let each individual deal with their own issues as they see fit.  but you don't solve that problem by enjoying a right and denying it to someone else. 

i mean, it almost sounds like you're trying to fix one problem by breaking something else.  careful... that's what liberals do.

7. marriage is a religious term.  same-sex couples should have a civil union with the same rights, obligations, protections, just don't call it "marriage".

you mean "separate but equal"?  we know how that turns out, right?

but ok, if you believe our secular legal system should lose the word "marriage", and replace it with "civil union" for all, then say that.  that's logical and provides equal freedom.

let's play this out.  let's separate the sacrament of marriage in the eyes of our church away from the legal contract of civil union in the eyes of our society.  if you're an opposite-sex couple of faith, get a civil union at the courthouse, and a marriage from your clergy.  atheists, you only get the civil union because you don't want the second one.

problem is, i don't hear those opposed to same-sex marriage fighting for that. instead i see folks using a personal bias to deny a legitimate right to others.  

8.  if it's legal for gays to marry, it'll teach my kids that being gay is ok

it won't teach your kids anything.  that's your job.  if you believe that homosexuality is wrong for you and your family, then let it be wrong for you and your family.  teach your kids what you think is right and wrong.  maybe at the same time teach them to not impose their beliefs on others.  especially when others exercise rights that don't impose on your rights.  

i mean... telling others what to do with their lives is un-american and un-conservative.

but ok, let's go in the other direction.  there are a lot of things that are legal that aren't ok for kids, or even ok for anyone, so even then there's no connection.  still falls flat.

9.  if gays marry, what's next?  marrying a child?  an animal?  a sandwich?

nope.  opposite-sex marriage is two consenting adults.  same-sex marriage is two consenting adults.  no slippery slope either way.  

10.  it's just not right and damages our society and our way of life

right.  how?  [crickets chirping]

so there you go.  10 of the most common objections and once you follow them two or three steps in, there's no traction.  all you're left with is inconsistency or selective logic.

how about this?  if you're against gay marriage, then don't get gay married.

and... notice that nothing in any of the 10 points above says that those of faith shouldn't believe what they want.  because they should.  and they should support their families and raise their children in the spirit of their faith.  

and if they raise their kids to believe that same-sex marriage is wrong, or homosexuality in general for that matter, that's their right too.  parental responsibility is really important to us conservatives.  personal responsibility too.  but at the same time we need to remember that deciding right-and-wrong for ourselves and pushing it onto others are two different things.

what am i missing?  i'm a conservative and because logic is stronger than creed i'm "pro" same-sex marriage!  where did i go wrong?

- jimbarry

Wednesday, July 18, 2012

hello prezi

bad powerpoint presentations make me bored.  but bad prezi's make me dizzy.  here is my first lame attempt of creating a prezi.  mostly because i'm testing the sharing, embedding, and export options.

in this case here on my blog, the embedding part.

so i humbly thank you, my legions of guinea pigs.

Friday, June 22, 2012

if this then that

so i found this site a few months ago:  it stands for "if this then that".  it's a web-based utility you can use, and it's pretty darn cool.  and really useful.  

it works for you like this.  think of your alarm clock as having a trigger and an action. when the clock reaches your wakeup time (trigger) it makes some kind of annoying noise (action).  i mean, the whole purpose of an alarm clock is that you're not paying attention to the time, so it will. 

now think of a web service that provides hundreds of triggers to choose from and hundreds more possible actions that can happen from it.  all you have to do is choose one trigger and attach to it one action.  IFTTT does the rest.

here's one i setup...

about three years ago i bought some stock in cisco systems at $19.72 and at the moment it's at $17.13.  if it ever gets up to about $20, i'll probably want to sell it.  so i made a recipe that's going to let me know.

here's what the trigger looks like:

and here's what the action looks like:

like a good alarm clock, i don't have to keep track of cisco's price myself.  when the trigger happens, it does the action.  (you might be thinking, just place a "limit" order.  the order won't sell until the price hits $20.  yeah... but i might not really want to sell.  i just want to know, then i can research what's going on, then decide.  just like, if i set my alarm clock for 6am, i can still snooze in til 9:30 if i want.)

here's another one:

dilbert's cool but i don't often think to go to the website and read it, or *gulp* buy a newspaper.  but, the dilbert site has an rss feed.  i tap into that.  when my recipe senses today's dilbert is ready (trigger), then grab it and send it to my gmail account (action).

or here's another one.  any picture i take and upload to my instagram account (trigger), the recipe senses and also then posts it (action) as a tweet using my twitter account:

of if anyone in the world posts to twitter with "#devmeetup" in the sentence (trigger), it grabs the tweet and adds it to a text file (action) i have in my dropbox folder:

i can go on and on but i won't.  but there are a few dozen channels (check em out), any of which you can use as a trigger or as an action.  there are also a thousand or so creative recipes that other users have created that you can borrow, use as-is, or modify then save and use as your own.

oh, right... last recipe i want to show you. check it out, it's an alarm clock. :-)

- jimbarry

Friday, April 20, 2012

is there a doctor on the beach?

less than one week til chris barry heads to st kitts for his first two years of veterinary school.  gonna miss my dude, but i'm totally looking forward to the chance to head down to the caribbean (never been) to visit soon.  until then, a good chance to check out this apple facetime thing.  i'm sure he'll have a great time and do very well.  he always does.  as i like to say, as his dad, c-dude turned out really well in spite of anything i ever did. ;-)

if you want, you can keep up with his latest happenings on his:
 "journey thru vet school" blog.

chris, what's your skype name again?

Friday, February 3, 2012

5 *more* NFL rules that need to go away

two weeks back i wrote up my top 10 ridiculous NFL rules that need to go away.  while writing those i came up with a few more.  it was pretty easy.  let’s start with a good one...

1.  here’s what’s wrong with the new overtime rule

first... let’s just say i had no problem with the old rule, but i am ok with trying to improve it.

but let's start here, because it’s a great example of the nfl fixing a problem in the most complicated half-assed way.  it's complicated cuz it takes a few minutes and a few pages of text to explain. it's half-assed, because if the first team scores a TD, the second team still doesn’t get a possession.   

so let's fix it.  here are three new rules that are simpler and more fair:

a.  possession-swapping: this is the way it works in hockey (sort of), tennis, baseball and oh right, college football.  first team does what they can with a possession, if the second team betters that, they win, comes up short, they lose, or ties, you get one more pair of possessions.

b.  a full 15 minute quarter:  this is the way it works in hockey (sort of) and basketball. it’s a mini-game.  play the entire 15 and whoever’s in the lead after that wins.  this is easy to do because it simply extends the game to a 5th quarter.  no other rules need to change.  tied after that, go to a 6th, 7th.

c.  or maybe just the old rules:  it was a straight coin-flip and a straight sudden death. sounds unfair if you lose the toss, the ball and get 3 points kicked against you, but historically and statistically the receiving team would only win overtime about half the time.  some would say this isn’t fair because the second team doesn’t get a possession.  fine, but at least it’s simpler.

but if you’re gonna keep the new complicated rules, at least explain it clearly:

overtime is sudden death, except if the team receiving the ball first scores a field goal on their first possession”  (period)

you don’t need to get into what happens with fumbles, safeties, etc.  it’s all covered in that one simple sentence.

2.  here’s what’s wrong with video replay

probably *not* what you might think.   

sure, no one likes how replays slow the game down.  it tries to analyze a train wreck with surgical precision, but we all love it when our team benefits from something being confirmed or overturned, so I’m not gonna get all purist about it.  that’s not the problem.  

rather, the fastest and most correct way to figure out what happened is off the field.  put an official up in the booth and have him to make the decision, then call it down to the field..  much quicker that way.  college football already does it this way and it definitely speeds things up.  (or maybe coors *wants* more silver bullet commercials) 

shoot, in the NHL the official review is sometimes not even in the same country as the game being played.  plus the booth can see many angles at once timecoded together.  under the hood there’s only one camera view at a time.  so go on coach!  let that little red bean bag fly!  

which brings us to...

3.  here’s what’s wrong with coaches challenge

look, if you keep getting challenges right, you should get more than three.  

why should a team be rewarded for a few bad calls but punished for a lot of bad calls.  but of course get one wrong and you’re done.  that way you still can’t “game” the system and you still don’t slow down the game any more than it is already.

yeah, yeah, your probably saying that this is less of a problem now that all scores are reviewed and refs call challenges after 2:00 warnings.  i have two words to say about that: true, and moot.  reviewing all scores is ham-handed and misdirected.  most scores are so obvious and don't need it, and this change to force a video review all of them slows the game down when we should be finding ways to keep things moving.   

simple:  if it's worth the risk, the coach will challenge... so review it.  if it's not, they won't... so don't review it.  either way it's in the coach's hands.

4.  here is what’s wrong with eligible receivers

as it is, an offense can only have 6 eligible receivers.  why??  let’s make this simpler.

let’s start with the assertion that every man on the field is a football player.  if a lineman can recover a fumble and run with it, why can't he can’t he catch it and run with it?  if everyone on the defense is eligible, then everyone on the offense shud be eligible.  is this suddenly going to change offensive schemes and make more linemen actual receivers by design?  No, they’re too big and slow, but it will create more receptions as QBs have 5 more check-down opportunities to get an extra yard or two.

and c'mon let's admit it, every once in a while it *is* a lot of fun to watch a 6'5" 325# guard rumble and bumble his way down the field, isn't it?  big!  boy!  with!  foot!  ball!

or are we saying that a QB fleeing the pocket then hurling the ball into the stands is a part of the game that’s just too valuable to give up? 

5.  here is what’s wrong with the tuck rule

omg... it’s obvious.  the tuck rule is exactly the opposite of what it should be.  

in short, if a QB is clearly not throwing the ball, and he drops it, it should be a fumble.  just like any other player who does the same thing.  let’s face it, this rule is still in place because it helped out that ugg’s spokesmodel who's bangin giselle bundchen.  if it’d happened to any mortal QB, it *would* be the opposite of what it is.  all players are supposed to be equal, but of course some are "more equal" than others (...and some "less equal", right mike vick?)

thanks NFL.  just change those 5.  oh, and the 10 from before.  you rock!


Saturday, January 14, 2012

top 10 ridiculous NFL rules that need to go away

let me ask you this.  how often do you watch a game when something happens and you say to yourself “huh? what’s that rule?  i never heard of that one before”  yeah, me too.  at least once every couple of weeks.

ever seen the NFL rule book?  thousands of rules, hundreds of pages, dozens of changes every year.  many are so easy to make fun of... i think i'm gonna.

why so many?  

well, as with most complex things, a problem comes along which begs for a rule to solve it.  the rule probably fixed it in some half-assed way, which then begged for a few more rules.  fix all of those halfway, mix in a bunch more unintended consequences needing a few more rules, and voila, you end up with the NFL where complexity itself is now part of the culture of the sport.

so let's have a little fun.  here's some low-hanging fruit.  what do you think?

let's go...

1.  here’s what’s wrong with false starts

losing 5 yards because some lineman flinched his bicep or moved his helmet a half inch (I am *not* exaggerating) is sort of ridiculous and totally blows the intent of what this rule was supposed to be for.  not to mention the defense can move around pretty much all they want.  

how about this?  no one on either side can cross the line until the ball is lifted.  period.  allow as much pre-snap lateral movement, but keep vertical movement to a foot or so.  i mean, we don’t want receivers sprinting toward the line like in arena ball.  

now, if the offense starts jumping around like sean avery in front of marty brodeur then flag them, sure, but then just call that unsportsmanlike conduct like you would for excessive celebration. 

which brings us to...

2.  here’s what’s wrong with excessive celebration

every other pro sport can celebrate scores with their team and with their fans.  funny how players of the most violent sport can't seem to grow a thicker skin.  time to put on your big boy pants fellas.  

if a team scores, a team should celebrate.  one player, two players, or 11.  if you want to limit it to keep the game moving along, then limit it by time, not by number of players nor limit what they do or how they act.  much simpler to judge that way, removes the personal preference of various officials.  you get 30 seconds on the field, then you gotta move the party over to the bench.  do anything beyond that and it’s delay of game.  that way you use a rule that’s already in place rather than inventing something new.    if the defense doesn’t like it, then they should try harder to prevent the score.

speaking of thicker skin...

3.  here’s what’s wrong with taunting

look, if it’s a physical act like a finger to the chest or tossing the ball at an opposing coach, fine, (yeah im lookin at you desean jackson) but if it’s just words, let it be words.  psychology is part of the game.  as long as no one touches anyone else, what’s the problem? and if you're a player being taunted, remember that what taunters hate most is being ignored.  (it's a nice life lesson for kids too.)

and don't sell me on the league's interest in "sportsmanship", because the NFL's own network will replay unsportsmanlike fouls on highlight shows and promos for days and weeks afterward, all the while adding "oh that's so wrong" voice overs from hall-of-fame studio analysts.

4.  here is what’s wrong with 12 men in the huddle

as long as there are 11 on the field at the snap, who cares if the whole team is in there beforehand talking about it?  the play clock is still only 40 seconds long.  which brings us to...

5.  here's what's wrong with the play clock

it's way too long... most of the time.  so, shorten it to 25 seconds for anything less than a 10 yard gain. and yes, that includes kneel-outs after the 2:00 warning.  

but make a big gain? sure, keep it at 40.  gotta give the big boys some time to stumble on down there.

6.  here's what's wrong with "the ball started to come out"

simplify!  how about this?: 

the player with the ball -- has the ball -- until -- he no longer has the ball 

but of course in the NFL that's not true because it wouldn't be the NFL if we couldn't make it more complicated.  

so until the league goes with something that passes the common sense test (and they won't) we're going to watch, week after week, the zebra with the switch on his belt hear his stadium echo explain... 

"after further review-view... there was detectable movement of the ball-all... which in the previous frame of video was securely wedged under brandon jacobs' meaty bicep-cep... before his knee touched the ground, therefore, because the ball came fully out a second or two later-gator, the ruling on the field of a fumble is confirmed-irmed.  the giants will be charged two timeouts: one for the failed challenge and another to give #27 a chance to find his helmet that he threw into the stands, the big baby-aby-aby."

yeah, officials like to hear themselves talk-alk...

7.  here is what’s wrong with crack back

probably nothing.  i just like saying "crack back"  

(disclaimer: i don’t actually know what crack back is)

8.  here is what’s wrong with late hits

the NFL only takes the best college players, and even they always talk about how much faster the pro game is.  when 200# players are sprinting at 15mph, that momentum can't be neutralized within 1/10th of a second after the dude with the ball touches the white line.  

and yes, the hit looks 5 seconds late in super slomo, but not at the speed it happened in real life.  sure, there is a point in time when the hit is clearly too late, but officials have cinched up their sphincters far too tight given our current laws of physics.  

not to mention this can be (and every once in a while is) easily “gamed” by mobile QBs faking like they're going out just to cut in for a few extra.  (yeah i’m lookin at you michael vick)  at this speed, the defenseman is defenseless, cuz the next time he'll lay the runner out a fraction of a second too late and get nailed for 15 yards, and maybe even a fine from the league front office tuesday morning.  who’s gaming the system now?

9.  here is what’s wrong with sideline receptions

it’s simple and logical.  if i have possession of the ball and one foot is down, how can you say i’m not “in”.

more logic... if two feet equal one knee, why can't one foot equal one knee?  more consistent.  just like college football.  

refs spend far too long under the hood watching 4 or 5 different angles to check possession, control, then one foot then the other.  those last three simultaneously, and the last two often being the most difficult to see, even one frame at a time.  

this way the player can finish standing up or at least roll easier.  with two feet down, often the player has to sprawl out there, crashing down hard or opening him up to (sometimes late) hits.  safety, right?

10.  here is what's wrong with block-in-the-back

ok, i've never played football, but this has got to be the most-called and most-preventable fouls in the game.  how is blocking someone from behind not the easiest thing to not do?  get rid of the rule.  three reasons: 

  • dozens of coaches and hundreds of players on special teams all over the NFL simply cannot find a way to keep this foul from happening at least two or three times a game, and
  • when it's called it often nullifies a really nice run back or worse yet, a stadium-shaking touchdown, and 
  • is blocking someone in the back really that bad?  as much as it happens, have you ever seen anyone injured from it?  carted off the field from it? yeah, me neither.

ok, that’s 10.

hey guess what?  as I'm writing this up I came up with 10 more. it was pretty easy.  good ones too.  

my "here's what's wrong with" preview: tuck rule, video replay, helmets, and of course holding, and more...

i'll push that list out on super bowl sunday 2012, which I predict will be the giants beating the new england patriots 17-13... again. ;-)

go big blue!