It's not always interesting listing to somebody else explain the same thing to you that you have heard before. There are some prerequisites for it to stay interesting:
1. You were interested in the first place
2. It's not a carbon copy of what you heard before, ie: it must be of a different format and convey information in a different format, it would also help if there was extra information that you didn't hear before.
3. The delivery and information must be good. If the information and delivery is worse than the first time you are sure to think that it is a waste of time.
Critically for me the lecture this week ticked those three boxes. I had heard a lot of the stuff before but there was stuff spliced in to make it interesting and to keep me entertained. The material was a little bit different to what was the content in IT for Management Decision Making IT4MD).
I think it's funny how Arnott didn't go over POD's paper in IT4MD. Must be cos it's not published and properly peer reviewed, but fudge that. It's still evidence if it's not peer reviewed if the procedures were good.
The idea that I brought away from the lecture was that BI was hard but doable, just like a good woman... SNAP! Stupid immature jokes aside, i think there is a lot of evidence that BI systems can be fantastic when done correctly.
One thing that i would like to criticise is that BI ppl always seem to quote how important BI is in industry surveys of things that they might be considering in the next few years. I think that BI systems are something that most managers don't get around to implementing. I think quoting stats about how likely they are to implement things is a bit of a useless stat. I am planning on clearning my car, i should do it in the next two week and if a survey asked me if i was planning on it I would say yes but I haven't cleaned my car in a while and it's needed a clean for ages and I still haven't cleaned it. It's just not high on my priorities. It's much more important for me to write this blog, do other assignments and
watch my football team lose after the siren and then write about it (it's a weird reflective experience; a kin to writing this post).
Secretly... psst... creating that app in visual studio was easy. I think it's cos it's so similar to the music player for mulo things that we created in SDI that it was easy for me. I'd done the ODBC thing before sometime too, I all seemed familiar. Great instructions too, maybe some more screenshots would have been good, there was one part where i was confused and there wasn't one, can't remember. I found that i didn't need to read the instructions, most of it was easy if i skimmed and then guessed.
Infoholic was late, which i communicated to the class brilliantly after he called me once he had acquired my number from the wonderful Alex. Small world. He then proceeded to go through the history of reporting apps in 35mins, which was quite interesting, i was aching to get started on the app a bit, but oh well. I did have time to complete the app though in class, but i don't think my fellow students were as fast as me. I am a bit of a bullet at these kinds of things when i have a bit of experience.
That's probably enough talk for the week, I better steer away from the TV right now. Australia are taking wickets and I have work tomorrow, don't wanna be up all night.