Archive: February 2008

People Who Need People

It is sometimes difficult to remember that every organization, whether a newspaper, a state government, or a a school, exists only because of people: people who work for the organization and people who are served by the organization.

This principle is true for Omnitech as well. We are who we are today because of people: our employees and our clients.

When Omnitech was incorporated back in November of 1998, the world of online technology was approaching an apex. People with good (and sometimes not so good) ideas were being chased by venture capitalists with briefcases full of cash. New technology companies seemed to sprout from cracks in the concrete at business parks everywhere.

We began without whiz-bang ideas, venture capital or even a cool sock puppet to help out. Instead, Omnitech began with a handful of people who were good at what we did and who had determined that combining efforts as members of a single team would allow for every one of us to be more effective, efficient and, ultimately, more successful. We started with people who knew how to meet our clients’ business needs.

In the beginning, our employees (most of whom had been independent software developers) brought their clients with them. Once again, we didn’t have many clients, but those we had trusted us to take care of them – and we did.

Since those days, we have grown to about 40 employees. Our client base has expanded several times over the last 9 years. Though much of our business is based in the regional market, we now have clients around the nation and in several countries overseas. Regardless of where on the map our clients may be, we continue to bring them the best technology solutions for their needs.

When you have a medical need, you visit the doctor. When you have a business need which would benefit from a custom software solution, we’d like you to visit us. We are in the technology business: the business of using technology to meet the needs of people like you.

AJAX Was Here

So what is AJAX and why do you want it? The word AJAX is nothing more than an acronym for Asynchronous Javascript and XML. If you are from Brazil, AJAX could stand for the Associação de Jogadores Amadores de Xadrez. However, we are not speaking of the Brazilian Chess Fans Players Association. When we talk about AJAX, we are discussing a technique used for creating highly interactive web applications. No one owns it and neither is it a technology, as such. Rather it is a new and growing approach for architecting web sites and web applications using several classic technologies:

  • Standard Presentation (X)HTML and CSS
  • The Document Object Model (DOM)
  • Server Data Exchange via the XMLHttpRequest Object
  • Javascript (which binds it all together)

AJAX is rapidly changing the way the web is being used; it is becoming the standard for enhancing the user interaction with forms. It curbs the traditional stop-go-stop-go that you normally encounter with web pages. AJAX allows the user’s interaction to happen asynchronously with the application, forgoing the common alternative of continual page reloads and the browser hour-glass.

Great examples of AJAX in use which most people are familiar with are Microsoft’s Web Outlook Access and Google’s online applications. Even this Omnitech site you’re browsing is driven by AJAX. Data is constantly being fed into this blog engine behind the scenes.

While AJAX sets the stage for a lot of razzle-dazzle, the main reason businesses are turning to AJAX is for usability. If your application involves e-commerce, then usability for you translates into sales. If your application is internal, then usability equates to employee productivity. It has been said that spending 10% of a web development project budget specifically on usability returns more than double the benefit of spending the same percentage on quality.

The trend in web application development is towards open standards and vendor neutrality. Internet connections are getting faster and AJAX is here to close the user richness/responsiveness gap which has traditionally existed between desktop applications and web applications.