The speed of Application Express

Application Express is like a racing. The speed of development is amazing, not only to me but also to my customers. I experienced that again some days ago. A collegue came up to me and asked whether i had time to create an application for an line-up he was performing for all the IT standards and guideline documents within my organization. He had a rough data model with 6 simple entities. Two and a half hours later I had a working application to maintain the data. He was amazed, because he had expected it to take two days.
I like to start with a rough outline and refine the model while creating the application. That way I can exploit my creativity in shaping the application. For the users it is a lot easier to talk about a real application that about abstract schemes. So the development process is a lot faster. After the first version of the application I made I have spent an odd 4 hours refining the application, amongst other things adding a search page with report.
In the process of developing an application I use email a lot. With Apex it is possible to react within minutes after the reception of an email with a few changes, lest you keep your application simple. Once you start using complex Javascript, Ajax and PL/SQL construction, it will be much harder to maintain the application. So think well, and think again, before you incorporate those flashy features into your application.
Disadvantage of the speed of development will usually be that the technical documentation is not up to date. The least you need is an accurate data model, describing the meaning of the tables and columns. I mean the real meaning, like 'we intended to use this column to store xxx but now it is not used anymore', or 'contrary to the name of column it contains yyy'. The design patterns and conventions used should also be written down. This technical documentation makes it a lot easier for the next person to understand and maintain the application. In all the Apex projects I have done so far it has been neccesary to take some time at the end of the project to wrap up the technical documentation.

History of an Oracle professional

I have been in the IT business for many years now, and still I think it's an exciting and ever changing environment. I like that, because I like challenges and new technologies.
I have been working with Oracle products now from 1988 on.
Before that time I was into 3-D modelling and I tought databases and administrative programs were boring. I created programs, that generated 3-D pictures of houses with various light sources, that was exciting, though the effort to get that result was a couple months conversation with the computer terminal.
Still I tought it was boring to produce data-entry forms and reports of several feet long covered with numbers. How wrong I was, because from the moment I started to create database applications I was hooked, and I still am.
Luckily the technology has changed during the years. I started off with a terminal on a DEC VAX system. My first PC was not connected to a network. I used Oracle V5 on a DOS PC with extended memory (a total of 1 Mb, it cost a fortune). A year or so later I started to connect my PC to the Oracle database on the server using the terminal connection. I had to enter strange connection strings with lot's of single quotes, i believe up to 4 or 5 even, but it worked and it was magic. Moments of victory like this are the reason I am putting in all the effort.
In 1988 I had my first SQL*Forms 2.0 course. I liked the tool, because I was able to create programs to enter and retrieve data with ease and flexibility. It has been my love for a long time, until it was finally replaced by webdevelopment. But that's for a next post.