While my life experiences were flashing before me in the few seconds before my ABS brakes gripped the frozen payment in front of a stop sign, I thought how similar this braking system was to U2 databases.
ABS was first introduced in late 1920's by Gabriel Voisin for stop his aircraft without blowing tires. It took until 1970's when Ford and General Motors first put them on mass production cars. Around the early 1990's you could get ABS brakes as option on most cars. ABS brakes took some where around 60 years to refine the technology for the masses.
The Pick database the precursor of U2 databases Universe and Unidata was started in 1973 with the release of Microdata version. In around the middle 1980's Universe and Unidata we started. We are 40 years in to this technology. Hopefully, before the next 20 years main stream users, programmers, C-suite people, and the media will find out revolutionary these databases can be.
I believe we won't have to wait another 20 years to harvest this technology. I, with my team of programmers, have created our suite of tools using Eclipse IDE. Our XLr8Editor allows editing of programs, dictionaries, procedures, paragraphs, and data with built-in version control. With our XLr8Resizer you can resize your account with a few click of the mouse. Our XLr8Installer allows you to build a XML install script you can run to build you software accounts for your internal use or for your customers. Our XLr8Developer and XLr8Object Editor the help you create these wonderful web pages using our middle-ware call U2WebLink.
U2logic offers free trials on all of our tools. With U2logic there is no capital investment you just pay maintenance every year to get access to all bug fixes, releases, and email support.
Wednesday, April 11, 2012
Friday, March 23, 2012
Is there a Dinosaur sitting next to you?
Sometime in the near future you will look at your coding partner, or your fellow programmers, or even your boss and wonder if you are ever going to start coding like you live in this century. It is something we must do every now and then when people find out you are coding in BASIC. Really UniBasic is not Dartmouth BASIC which was created in 1964. No we are using a language related to Data/Basic from its big commercialization in 1973. It has some similar conventions as Dartmouth BASIC and the same thing can be said of JavaScript and Java.
If you write programs that, for example have variable names like "A" or "B", then the dinosaur is not sitting next to you, it is you.
If you cannot spell out the word count and use CNT or CT, then extinction might be right around the corner.
If we cannot name programs to match the functionality calling them Wh200 which should be something like Warehouse_EDI_Subroutine, then you are becoming a DoDo bird.
If you continually use archaic tools like AE (Alternative Editor), ED (Editor), or plethora of the other names strategically not mentioned, then you may find our self's looking for a job in a shrinking environment.
If you have seen the word "Version Control" but think you should save the old version of the program in a file called BP.OLD, the world is getting a lot colder than you realize.
If think that your editor should not be auto correcting as you type, then you cannot see the forest through the trees and maybe the T-Rex will not get you.
If we think that your manager does not know anything of how you do what you do, then you are in for a long winter this summer.
At U2logic, we are enjoying ourselves with state of the art tools and processes, so we are neither too cold or too hot. Check us out at our web page at www.u2logic.com/tools.html.
If you write programs that, for example have variable names like "A" or "B", then the dinosaur is not sitting next to you, it is you.
If you cannot spell out the word count and use CNT or CT, then extinction might be right around the corner.
If we cannot name programs to match the functionality calling them Wh200 which should be something like Warehouse_EDI_Subroutine, then you are becoming a DoDo bird.
If you continually use archaic tools like AE (Alternative Editor), ED (Editor), or plethora of the other names strategically not mentioned, then you may find our self's looking for a job in a shrinking environment.
If you have seen the word "Version Control" but think you should save the old version of the program in a file called BP.OLD, the world is getting a lot colder than you realize.
If think that your editor should not be auto correcting as you type, then you cannot see the forest through the trees and maybe the T-Rex will not get you.
If we think that your manager does not know anything of how you do what you do, then you are in for a long winter this summer.
At U2logic, we are enjoying ourselves with state of the art tools and processes, so we are neither too cold or too hot. Check us out at our web page at www.u2logic.com/tools.html.
Wednesday, February 8, 2012
The Big Lie
So what is the big lie you should be asking yourself? It is the fact that taking applications from the green screen to the web is easy and/or fast. All of the software vendors sell this. Here are some gleaned from their current web pages.
"...provides a wealth of end-user capabilities allowing the developer to rapidly create feature-rich, high performance applications.."
'Rapid application development for multivalue"
Web development can be fast and easy if you are converting or creating a simple screen. Simple screens it turns out are a significant number of the forms that are done, however, they compromise only 5 to 15 percent of the time of development.
Lets talk about normal forms and where the time is spent. Depending on which tool you use, some of your time is divided in setting up the objects to allow the translation of variables from Universe and Unidata to the web, and designing the form or re-designing the form to fit the web. The rest of you time is either writing the JavaScript to run the custom features you want and modify or writing from scratch the UniBasic subroutine that handles the business logic. For example, business logic might be where we are allowed to buy this dollar amount from this vendor or only these particular products.
The last part of Web development that no brochure or web page talks about is debugging the four headed monster you just created. It is the UniBasic code, JavaScript, HTML, or objects that are causing my form to function unexpectedly. A good rule of thumb is them more complex the form, the more complex the debugging.
Here is the figure you should use on most Web form development. For example, if this form took about 20 hours to develop count on 40 to 60 hours to debug, pass quality assurance, and client approval.
BTW: U2logic's XLr8Developer hardly ever uses the word rapid to describe the web development process. If we do we are speaking of those code file Web entry forms.
"...provides a wealth of end-user capabilities allowing the developer to rapidly create feature-rich, high performance applications.."
'Rapid application development for multivalue"
Web development can be fast and easy if you are converting or creating a simple screen. Simple screens it turns out are a significant number of the forms that are done, however, they compromise only 5 to 15 percent of the time of development.
Lets talk about normal forms and where the time is spent. Depending on which tool you use, some of your time is divided in setting up the objects to allow the translation of variables from Universe and Unidata to the web, and designing the form or re-designing the form to fit the web. The rest of you time is either writing the JavaScript to run the custom features you want and modify or writing from scratch the UniBasic subroutine that handles the business logic. For example, business logic might be where we are allowed to buy this dollar amount from this vendor or only these particular products.
The last part of Web development that no brochure or web page talks about is debugging the four headed monster you just created. It is the UniBasic code, JavaScript, HTML, or objects that are causing my form to function unexpectedly. A good rule of thumb is them more complex the form, the more complex the debugging.
Here is the figure you should use on most Web form development. For example, if this form took about 20 hours to develop count on 40 to 60 hours to debug, pass quality assurance, and client approval.
BTW: U2logic's XLr8Developer hardly ever uses the word rapid to describe the web development process. If we do we are speaking of those code file Web entry forms.
Subscribe to:
Posts (Atom)