I have database-a-phobia. Surely, there's an officially recognized phobia for that.
So instead of doing the "proper" thing for my ruby rumble last night, which would've been building a proper CRUD interface, instead I'm predominantly storing my data in a google spreadsheet, then pulling it into the database that way. Which means, I can freely blow away the database on a whim and run one script to get all the data back.
Doing things the wrong way solves many problems for me, at least temporarily:
So what's the project?
I'm keeping track of my rock band drumming scores. The actual thing I want is what I keep calling an inverse search, which is, I want to be able to put in "expert level, 50% playing speed" or similar parameters and have the app tell me either 1) what songs I've never practiced or 2) what songs I've practiced least recently.
I want to make sure I'm practicing all of the songs on a regular basis, so the app is so supposed to make it easy to figure that out.
Second to that is actually tracking progress. To show that yes, I am getting better.
At this point, the data side is (I think) done. Now I just have to build all of the custom database queries I need and the frontend part of the site.