You are here

New Research Direction

    My committee meeting was very interesting. I learned how much I was on the wrong track, and how unimaginative I was. It was a good experience though. I learned that many of the things I’ve been doing have been done, but there are still some that aren’t done. The best piece of advice I got was to follow the lines of agriculture and veterinarian medicine. At the company I work for, they do several web projects for professors that have a good amount of money to spend on websites that they need for teaching and whatnot, but there isn’t many veterinarian related computer science projects that can be used in everyday situations. So my research has taken a new and exciting direction.

    I will still be doing grid research and context aware stuff, but now I’ll be adding pattern recognition to the mix. It’s a good thing I still have my image processing book, or I wouldn’t know where to start. The more I think about it, the more I get some better idea of where my research has to go and where I have to look for information on what’s going on.

    The one thing I really want to get into is UML. I remember learning it, but since I started working at GiantGoat, I never realized how important modelling a system before beginning was important. I brought it up and they ignored me, so I’m not going to wait for them to pick it up. If I want to learn it, I’m going to have to master it myself. The best part of mastering UML is that I can do it for free because I have the resources (ebooks and regular books), but I just don’t know if I could find the time. I really should have paid attention to UML back when I was studying it in Software Engineering. I’ve always stayed away from UML because I always heard it was for object oriented software development and I also develop in procedural languages. Then I realized that the only language I code in that procedural is C. So I think I can drop all that fear and start focusing on OOAD (object oriented analysis and design). But now my time is spread so thin that I’m worried I won’t finish my masters in a decent amount of time.

    So what will I do with all my SOA knowledge? Keep it! Modern grid applications are built on top of web services (WSRF). Grid just adds more resource management to web services. So if I were going to do more research in web services, I would probably be making it more like grid. But then again, there’s grid. So I’m just going to use grid and the web services knowledge would help.

    Platform computing specializes in grid stuff, so maybe they’ll notice me when I’m done.

Comments

Hi Jay,

 

If I've learned one thing over the past 8 months it's that planning is the most important part of a great software company. I'm not talking large corps or anything close. I'm talking about small little guys that end up being bought by the big guys.

 

I don't think you have a problem in the area of finding work in your specific subject matter. I can truthfully say that there is constant evolution and expansion in the area of SOA, Grid, and Web Services--combined!

 

The main reason the company I work under was bought, is not because of fantastic programming; it's because of fantastic planning. When I teach a course, people aren't asking about specific functions or algorithms (that can be outsourced), they're talking about the idea behind the whole application. What was the ideology behind the concept? What makes it different from the other guy?

 

If I could offer a two liner answer to these guys, it could be quickly programmed. An idea that can persevere for generations is priceless. SOA offers companies the opportunity to set standards. If you can develop an SOA architecture that is so intuitive, and organizations understand its value, you can become a market leader in extremely little time. Suddenly, everyone realizes what Bill Gates is about.

 

There is a huge realization that our previous path was wrong. All that the past has offered us is the ability to create programs that are cripplingly limited to communicating to applications written in the same language and for the same platform. There is significant value in creating applications that interface at EVERY level.

 

SOA, Web Services, and Grid computing make excellent candidates for an infrastructure that can't become outdated. It must be a solution that is adaptable where ever technology takes us.

 

This is where UML also comes into the mix. I can't explain how important this can be. I do not have access to the UML diagrams of the program I teach. They let me determine the layout on my own, in my own way. The UML is the key. If a competitor had our UML, we would be in serious trouble.

 

 

Cheers, Tony

 

P.S. Something is messed up with your paragraphs or something... they all bunch together when I make a comment or you make a post.