Though I am totally dying to show and tell, the mystery must continue...
Actually, there is a lot of stuff about this process that has surprised me. For example, after we finished the "bazillion page" document that details how the program will work, I thought the next step would be programming.
I was wrong. The next step was building a program prototype - all in HTML code!
When someone creates a prototype that includes pretty much everything in a "bazillion page" document, it can take awhile to work through all the details. Once 'all the details' have been included, it is time to start that new career.
What does a "program sleuth" do? A lot of clicking!
As I clicked, I made lists of all the stuff that was missing. I sent the list to the coders and they'd go back into the code and add the missing stuff. While they were busy with that, I'd continue to go through the prototype and find MORE stuff that was missing! I'd send another list. This cycle continues over and over again.
I wondered if I'd ever stop finding stuff that was missing or needed to be altered in some way.
a few weeks later...
We, the coders and I, hope we finally have it all. They are ready to "freeze" the prototype and move on. The pressure is on. I need to put on my super sleuth hat and go through the prototype one last time before I approve the "freeze."
I sit down with project team members. I begin explaining the prototype to them and guess what?
Yes, that's right. I discover there is more missing stuff.
At this point there is only one thing I am sure of... My sleuthing career is not over and, being a newbie, something is probably going to be forgotten or overlooked.
I wouldn't want anyone to think I am complaining - this has been mind boggling, frustrating, and very educational - but, mostly it has been fun!
(confession: I exaggerated when I said, "a bazillion pages.")