|
Years of experience in programming has given me a library of code fragments to draw from. I've used nearly every User Interface widget somewhere, sometime, and I have that code available to customize to your application. I don't have to re-invent the wheel. Nor is my library of code limited to User Interface elements - I also have substantial code for handling databases, reports, charts and graphics, device communications, program installation/setup, and much more.
Using C++ and the Jet Engine (which comes with Windows), I can create database applications that are MS Access compatible but do not require Microsoft Access (MS Office) to be installed. If you have a different ODBC database, I can use it instead of MS Access. This also frees you from the forced upgrade path - your application continues to work.
I do most of the development off-site. You do not have to dedicate computer equipment or office facilities. I cause less disruption to your staff and your daily activities. Our development system is substantially larger and faster than is usually found in a standard office environment (dual-monitor). I also have dedicated test systems. For Palm development, I have multiple units and can often test on the actual hardware. I also have virtually all the Palm Emulators and Simulators. I am a member of several different Developer Programs.
Whether I work for you on an hourly basis or on a fixed-price contract, you don't pay for coffee breaks, office chit-chat, equipment maintenance, or other non-productive time.
I don't do training - because no classes are required. I tailor the software to your business and take special effort to make the software user-friendly. This means that any training you require will be for your business practices and not in how to use the software. You get software that makes sense in your business. You get the source code too (unless otherwise specified), so that when your business changes your software can be easily changed to match.
I have developed a detailed set of guidelines for developing your Software Specification. This is not a rigid set of rules and forms, but a process to make sure that we solve the correct problem. The final specifications may be as little as a single page, or as detailed as required. Typically, the process results in five documents:
The Specification is complete enough that, if you wish, you can take it elsewhere for the actual coding. Your risk is reduced as you can see the implementation and quality before you have too much invested in it. If necessary, you can change direction at minimal cost.
No Specification or Project Plan can ever foresee every eventuality. I have the experience to identify many potential problems before they become an issue. I can handle many issues without requiring detailed oversight. For larger problems, I can often present alternatives that substantially shorten the Change Order/Review process.
I have over 15 years experience
dealing with handheld computers and their limitations in speed, UI,
etc. I design using pick lists and buttons wherever possible to make
data entry quicker and easier. I use all the tricks to optimize speed,
reduce program size, conserve memory, and to save battery life.
The first step is to think about (and detail) the requirements in "black box" terms (we can help):
Ready to start? Contact me:
© Copyright 2012, Baxter Codeworks