A Code-Driven Site

Now you have a good looking site that is driven by a database and changes consistently. Developers can accomplish almost all of their tasks through code in the back-end (server) part of the system. However, there is a penalty for doing this. Just like most other things in life, there is a balance that needs to be struck in order to provide the user the best possible experience. This is where SitesDynamic pulls out the punches. One of our major goals as a company is to provide sites which users walk away from not only satisfied, but actually enjoying their experience. Since it is a well-known fact that people remember the negative side of things much more often than the positive, we position ourselves so that those negative impressions are kept to an absolute minimum. How? Through a complete and thorough design / development / testing phase that is implemented through a balance of back-end (server) and front-end (client) code. First, however, a proper design is vital to the success of a usable system. We want you to know up front that we will take the time necessary to do it right the first time. This may add overall time to the project, but the benefits of that far outweigh the consequences in both future maintenance and updatability of the site.

Back to the code. We mentioned server-side code in the previous section when it related to the database driven site. This is very important to a dynamic website. Just as important, though, is the combination of back-end code with front-end code. Have you ever been to a site, logged in with your username and password, pressed "Submit" and then waited for what seemed like a life-time to only have the system come back and say, "You must enter a minimum of 7 characters for your password. UGGGHHHH!!! What's the answer? Client-side code. Every system has a set of business rules that are provided so the developer knows what should be done in every case of data entry on the site. Unfortunately, too many attempt to implement them all in server-side code when there are very appropriate times to do otherwise. This, for example, is one of those cases. Whereas it would be very important to go to the server to validate the password, checking to be sure it had the appropriate number of characters is a small and very fast solution to the problem.