This guide to writing rock solid, fast-running SQL/C Code was written for the consultants and employees at one of our client's locations. Though the original platform was AS/400 and DB2, techniques discussed in this guide are relevant to all database programming projects.
Choosing the Right Language for the Job
Contrary to what you may have been told, there is no best computer language. However, for any given job, some are better than others. Picking the right language can cut development costs of the project.
There are a number of techniques that can be used to keep a project out of trouble. However, there are a lot of programmers who are unaware of them. Here is a short list of ways to keep a project out of trouble in the first place.
I make most of my living by fixing projects that have gone wrong, rather than controlling and performing on projects that are going well. I'd rather be doing the latter, because my customers are a lot calmer and happier when they're not in trouble. To that end, I present the case for doing a project by the book, rather than by cutting corners.
Everything You Know is Wrong
Over the years, many advances have been made in computer science. For every advance, we have gained a rule-of thumb to guide us to this advance. We have also had a number of untested, wild-assed theories foisted upon us, also with their rules of thumb. These rules-of-thumb are just that -- not hard-and-fast rules, but general guidelines. Some of these rules are always valid. Some are valid under some circumstances. Others are never valid. Below, I list some rules, and explain my categorization of them.
Everything You Know is Wrong - A Guide to Real-Time Programming
by Sheldon Linker
Over the years, many advances have been made in computer science. For every advance, we have gained a rule-of thumb to guide us to this advance. We have also had a number of untested, wild-assed theories foisted upon us, also with their rules of thumb. These rules-of-thumb are just that -- not hard-and-fast rules, but general guidelines. Some of these rules are always valid. Some are valid under some circumstances. Others are never valid. Below, I list some rules, and explain my categorization of them.
“David Harrison and the Linker Systems team rescued our project at a critical time. They did it all. Requirements collection, analysis, design and coding. The work turned in was top notch, of highest quality and well documented. The price was reasonable. Linker Systems and David Harrison took our project from the failing point and brought it to a working, maintainable state. Bring David H. and Linker Systems into your team and watch as these wizards roll out great ideas and code under budget and on time.”