Oracle Mix + Suggest-a-Session
A little over a month ago, I saw this tweet from Neil Kodner (
@neilkod).

That links to this
set of data on github (using gist?).
The data gets interesting the further down you go.
Annoying, yes, but no big deal.
I was then off to KScope for a week of fun.
This weekend, I decided to open up Google Reader for the first time in, well, a long time. Scanning through my Oracle folder, I found the little gem.
Data Science Fun with the OOW Mix Session Voting DataThat was written by Greg Rahn (
@gregrahn) on June 23rd, 6 days after Neil's post.
On July 1st, the winners were
announced on the Oracle Mix blog.
A little tidbit from Greg's post that Bex (see below) quoted as well:
-- number of users who voted for exactly one author
+---------------------------+
| users_voting_for_1_author |
+---------------------------+
| 828 |
+---------------------------+
-- number of voters who voted for every session by a given author
-- and total # of votes per voter is the same # as sessions by an author
+-------------------------------------------------+
| users_who_voted_for_every_session_of_an_author |
+-------------------------------------------------+
| 826 |
+-------------------------------------------------+
Yikes.
I think it's safe to say that Greg's analysis predicted the outcome.
It's also...unfortunate.
Which brings me to this post by Brian 'Bex' Huff today,
Has Oracle MIX "Suggest-A-Session" Jumped the Shark???I'm thankful that Bex wrote this up because, quite honestly, I was scared...to rock the boat I guess.
This conversation needs to take place. I don't believe anything was done illegally, but I think it broke the "spirit" of the rules that were set up.
I'm all for using Twitter, your blog,
whatever ("whatever" gets us into trouble) to get people to vote for your stuff; but this seemed to go to far.
Bex has some suggestions for changing the rules over there, check out his piece and chime in.
Labels: oradb, rant