My official position(s)

Ok, here is Laurence E. Drake's official position(s).

On Machine Platforms:

• Now that I wave worked on IBM Main Frames, Multiple IBM Midranges, and Several IBM/IBM Compatible Personal Computers (Micro Computers) Stand Alone and Networked, I have come to the conclusion that each has strong points. The decision as to which platform is right for you is dependent on the primary purpose and task to be performed. If your processing involves a lot of computations and non-interactive processing you are looking into the Main Frame and high End Mid Range Computers. From my experience Main Frames seem to shine in that arena. If you need centralized multiple concurrent applications, multiple multi-user interactive applications, then you are looking to the Mid Range platform. Now if you are looking for client server then a combination of Mid Range and PCs is in order. I know that what I have just stated is simplistic (perhaps too simplistic) but when you boil it down to the essence this is what I see.

On Languages:

• I would like to confine my comments to COBOL, RPG III & IV, C, MS BASIC. I do not believe that any one language is totally superior to another. Again, the choice of language should be suited to the task. For example: I would rather code a low level communications module or a sort routine in C, rather than COBOL, RPG or even BASIC. For writing reports on a Mid-Range Computer RPG is a good way to go. I admit there are times when the choice of language is difficult, especially when functionally equivalent libraries and or features are available for the task to be performed.
  
  Concerning BASIC I left MS BASIC long ago for C. At the time I thought it was a good move. Two or three years ago VB 3 made it's way on to my computer. Now VB 5 on my box and it 's here to stay! I want you VBers to know VB is a real and viable language, don't let the ignorant prejudices from programmers of other languages dissuade you.

Coming of age:

• Languages set aside, I have developed a real concern for the quality of Software Engineers coming into the field today. I remember a time when we concerned ourselves with structure, design and maintenance issues. The concepts of design, maintenance and structure appear to have lost meaning to many of our newest siblings. I know, I am not one of the Old Timers nor am I one of the New Breeds, but guys/gals there is much to be shared between all of us. I listen to the young talk extensively about 'language', and the old, critical of change and lack of discipline of the younger programming groups. In our business change is inevitable, but there are some practices and principles that have proven useful. So to my younger programming siblings take some time to find out about methods, methodology and how it may help you become a better programmer if not to become a better Software Engineer. To the old Vanguard things in this industry change daily, so fighting change in many cases is a waste of energy and time. Won't you take some time and teach the young your technique. If we can do this we will advance our profession greatly.
  
  - Laurence

$Revision: 1.2 $

This page hosted by Get your own Free Home Page