Anticipation was extremely high for this day. Finally a chance to see how much of this information had actually stuck. Miracle had an Oracle expert flown in to present a problem for us to fix. The problem ended up being to create a datamodel for an inventory and booking system with a quotation system. Hmmm datamodeling, when did I read about that? Not so much really? Tom Kyte discusses how important it is, but not really how to do it. Lex de Haan describes it, tells about the importance of "normalization", says a little about how to do it. Well, apparently there was also a bit confusion on how long this assignment was to last. We, the meepers, was of the expectation that it was a one day thing. A view that was apparently shared by one of the mentors as well, since we got pushed to start developing the application eventhough we weren't done with the datamodel. On the other hand the presenter expected us to finish this in the time coming. So after some dilly dalling, we are now going to meet in Aarhus to finish the datamodel on this upcoming thursday.
In retrospect, my expectations were not met for this event. I had hoped that we would get some database stuff that we would have to get a hands-on experience from the real life. It was said to be a oneday midterm, but it wasn't, and now we are going to work on this project alongside finsishing MEEP.
Don't get me wrong the project is quite exciting and interesting. It just wasn't what i had expected, and sometimes that's what happen with expectations.
Abonner på:
Kommentarer til indlægget (Atom)
1 kommentar:
start developing the application eventhough we weren't done with the datamodel
That's the biggest mistake you can make in any project. I remember either James Morle shared interesting story about the same mistake in one of projects he was mentoring. (or was it Anjo Kolk?)
No single line of code without completed data model - otherwise, you can find yourself in tweaking data model to suite you current code. Humans are lazy. :)
Send en kommentar