Relfections on Class

CSMN 601 has been a good experience. I actually started this same class 8 years ago, but withdrew half way through the class. Getting cancer (said in a Monty Python way "...but I got better") and having a newborn didn't leave much time for school work. This go-round things were much more manageable.

I learned a number of things and solidified some more familiar technologies. I now find myself looking at the tech sites each morning for "what's new." Now on to "computer security."

Thanks!

Reflections on Week 14

My mini project dealt with robots. Here is my favorite robot. I would have said Ultra Man, but he technically wasn't a robot.

The discussion question on teleworking was relevant for me. This issue comes up often at UMBC. In the end, for professional level staff, it comes down to a case-by-case basis. Blanket policies don't seem to work out well for people with diverse jobs and responsibilities.

I did enjoy watching the Steve Jobs speech - even though I'm a much bigger Steve Wozniak fan :)

Reflections on Week 13

The countdown has started. The end of the semester is approaching and assignment due dates are coming fast and furious.

I've found that the readings have become more and more interesting to me, in that they touch on a lot of the situations that I have been in. Offshore outsourcing being one. I see the practical application of this practice, yet my personal experience left a little to be desired. Perhaps that was because I was in a development role rather than customer service.

I have to go now and punch in the numbers which will allow me a little more time to work on my projects. Let's see... where did I put those numbers? Ah, yes...
4...8...15...16....23....42

Reflections on Week 12

Software development.. A subject that is near and dear to my heart. Pictured is my first computer. A TI99-4A. I taught myself to program on it. I had a giant 16k worth of memory. My how times have changed. The subject discussed this week was object oriented vs. procedural. Both methods are great ways to develop. It all boils down to "the right tool for the right job." Thats very similar to the question regarding SDLCs and web developers. All things in moderation...

Now leave me alone so I can work on my research paper - my prof is cracking the whip!

Reflections on Session 11

In this session we discussed the topic of successful and not so successful e-businesses. We also discussed how we could use IT to make our own businesses more competitive. Thinking about this from the perspective of a public institution was interesting. I often made fun of some of the "hip" banner ads that I've seen for UMBC. I would joke and say that I've found one that had a picture of a skateboarder that said "UMBC: Come Get Your Learn On!" But the more I think about it, the more I see that this type of advertising might just attract the technically savvy young people that UMBC would like to have apply.

The article that I posted was about the speed of wireless / mobile networks. I found the idea that a Japanese company is testing out a 300Mbps network to be a little depressing. Depressing in the fact that my iPhone maxes out in the 1.5Mbps range.

Reflections on Week 10

Week 10 was quite eclectic. We discussed data warehousing as well as GPS technologies. While I very much enjoy using a GPS for both turn-by-turn directions as well as Geocaching, I really dislike data warehousing. Coming from a DBA, that might sound odd. My experience has been that the data warehouse community is a whole separate subculture from the rest of the IT world. They feel that IT is a necessary evil that really stands in their way of obtaining their rolled up facts and figures. I happen to disagree. I feel the bread and butter of an organization is the day to day transactions and transactional data. This IS the business, and not just a means to obtain summary information. I suppose thats why I won't be invited back to another Data Warehousing Institute conference. Whew!

Reflections on Session 9

Week 9 discussed teamwork and collaboration. One collaborative tool that I really make use of is the wiki. While I'm not sure it's for everyone, I can't help believe that an organization wouldn't benefit from one or more. Gone "should" be the day of the magic operations or policy binder. Gone "should" be the day of documents stored locally that contain important information / scripts / how-to, etc. I've found the easiest way to manage these types of information is through a wiki. Our text book mentioned "Organizational Memory." The wiki is the perfect tool to be part of the overall organizational memory strategy.

Wikis: They're not just for geeks anymore!