.comment-link {margin-left:.6em;}

Oracle Sponge -- Now Moved To Wordpress

Please use http://oraclesponge.wordpress.com

Monday, August 01, 2005


I don't know about you, but sometimes I feel that getting motivated to learn a new task or topic can be one of the hardest stages to tackle. It often goes something like this:
  1. Thinks: I really like the idea of knowing more about X
  2. A little online research to get the general feel for the topic
  3. Software downloads
  4. Possible investment is (tax-deductable) book
  5. Realisation that neither my client nor I have any problems to be solved by this
  6. Collapse into reclining chair, exhausted by ordeal
What is needed is some actual problem that can be solved, and that's how I ended up learning shell scripting, SQL, Perl, PL/SQL ... wel just about everything really.

To take an example a third-party tool was generating EDIFACT files for transmission to a client's major customers. Sad to relate, the customers' superior acceptance software would often reject the files due to some error in a totals line. Hence I researched, bought a book on Perl, and learned enough that in a couple of days we could scan the files for internal consistency before transmission. I bet that now I would not even recognise the code that I wrote back then, some nine or ten years ago, for I have had no use for Perl ever since.

I like to think of it as a beneficial character trait -- it keeps me focussed on what I need to know right now in order to make Bad Things go away and not come back, yet allows me the flexibility of getting familiar enough with topics to hopefully be able to recognise situations where they can help. On the other hand, it is really irritating that I can't follow through with these potentially educational experiences, and am condemned to live the life of a practical person. Yuk.

So speaking of which, what would be the worst possible job for me? It would be this: working on manned space flight at NASA.

Those with long and detailed memories may recall that the the space shuttle was needed to support the International Space Station, which was needed to support manned missions to Mars, which were needed because ... erm ... well let us not inquire too closely of that. The ISS has been occupied since November 2002, with a net contribution to science of precisely zero -- if we can exclude the science of how to stay alive in Earth orbit, or the urine-based sciences, that is. Can anyone explain why it it helps to study astronaut urine in order to understand the formation of kidney stones? Or why you need to have an astronaut to take photos of the Earth in order to "... provide researchers on Earth with vital, continuous images needed to better understand the planet"?

And the purpose of the space shuttle now seems to be to research how to mend space shuttles so as to better avoid killing people with them.

Sending robots to Mars, or better yet to Europa, now there's some interesting work. But not this manned-mission nonsense. How depressing it would all be.


At 6:54 AM, Anonymous adewri said...

I usually try fitting in what I want to learn. Sometime back I planned to replace our existing "database change request process" which developers used to send in excel sheets. Initially I thought I would use forms and reports as every one was comfortable with it. But then I wanted to learn HTMLDB, so I ended up creating the application in HTMLDB.

Similarly I relaced existing shell scripts with Perl scripts to have a general backup scripts for both Unix and Windows databases.

At 7:05 AM, Blogger David Aldridge said...

That's a great example -- I need something like that to get me into HTMLDB.

At 9:03 AM, Anonymous adewri said...

You better hurry... cause you are missing something good.

After making an application in HTMLDB you feel like moving everthing to HTMLDB. It's simply great.

At 9:08 AM, Blogger David Aldridge said...

Did you face any hurdles ingetting people to agree on adopting a new technology? Managers ...developers etc?

At 9:55 AM, Blogger John Baughman said...

Maybe you could use HTMLDB to analyze co-workers urine for kidney stones and generate reports in Perl, and beat those NASA guys to the punch... Real science at work... (I'm surprised no one else thought of that one!!!)

That's pretty much how I've learnt all I know. Look at something and say, "Hmmmm... How can I make this better... VB sounds cool, that'll make this work better." And in reality, that's about the only way to stay on top of new technologies, look at something and say, "How can I make that work for me." Then put into practical use.

At 9:59 AM, Blogger John Baughman said...

Usually when I would bring something to a manager, they would look at it and go "Hmmm... can I get that in mauve?" Usually it's a 50/50 thing getting some idea across to a manager. Either they like it or they don't. Never had a streak of "John created tools" at any one particular place. Just a sprinkling here and there. Most of the things I created I have kept and put in my personal archive so that I can always come back to it later and use it to my advantage elsewhere. Someday, somewhere, someone will use it.

At 11:02 AM, Anonymous adewri said...

Did you face any hurdles ingetting people to agree on adopting a new technology? Managers ...developers etc?

In fact the developers were happy to have an online system for "Database Change Management". Best part,this was the only application that was bug free and working :D.

May be in the next project I'll try to see if things can be done using HTMLDB instead of J2EE which we are using right now. I think I need to develop a prototype of existing J2EE application and test before putting the case.

At 4:03 PM, Blogger Robert Vollman said...

I couldn't have said it better myself.

It helps me just to have a pet project at home. Something you would like to have.


Post a Comment

Links to this post:

Create a Link

<< Home