By Avonelle Lovhaug
Publication Date: 12/4/2007 4:00:00 PM
Occasionally software developers fall into the trap of thinking that the little things aren't important.
Sometimes the little things are small cosmetic problems with our applications. A misspelled word, some misaligned controls, or some CSS that looks funny in the wrong browser - all of these things can seem like "little things". Unworthy of concern or time.
The problem is that these little things can detract and distress. Users can't focus on the software they are using when their eyes are drawn to a flaw. If the flaw isn't corrected quickly, it becomes a blight in the software. It demonstrates a lack of ...
Read More
Comments (0)
Publication Date: 11/26/2007 4:00:00 PM
A business requirement I often hear when designing software is that the application must be flexible and easy to change without additional programming. This seems like a sensible idea - we all know that nothing stays the same, and flexibility can make the software continue its usefulness despite changing business conditions, regulations, and standards.
There are two challenges with this requirement. One challenge is that flexibility is a very vague term. For some users, flexibility means that they can customize the colors or menu text. For others, flexibility means the ability to create custom business rules or reports. And for some people, ...
Publication Date: 11/6/2007 4:00:00 PM
Business people often describe their software application idea as "simple" or "easy" to build. Have you? Here are some things you may not have considered which can make building your application less "simple":
Comments (1)
Publication Date: 11/2/2007 5:00:00 PM
Every year at Halloween I buy too much trick-or-treat candy. Why? I don't want to disappoint any costumed children that may come to my door. Buying an extra bag or two of candy is an easy and fairly inexpensive way to handle the risky business of stiffing a local cherub.
Throwing money at a problem isn't usually the best way to mitigate risk. Still, contingency planning is something technologists must embrace. While server experts must plan for issues like hardware failure, software developers must think about how their applications will respond to unanticipated problems. Error handling is one area that needs to be considered in ...
Publication Date: 11/1/2007 5:00:00 PM
I'm often amazed at the number of developers who don't use source code control software. The arguments I've heard against it are lame and half hearted:
Too expensive
Other than some time to set it up and the disk space to set aside for it, there is no reason for it to cost anything at all. There are several source code control options that are open source or free. (Some examples include Subversion and CVS.) Personally, I use Sourcegear's Vault, which is free for a single user.
Only large teams need source code control
Even teams of one person can benefit ...
Top 5 Programmers to Avoid
What everyone should know about bugs
How to tell if an estimate sucks
The Secret to Building a Crappy User Interface
The Problem with Selecting the Lowest Bidder
5 Ways to Control Software Development Costs
As someone with over 20 years of software development experience and currently a small business owner, it has been a pleasure working with Avonelle. In addition to being a talented developer, Avonelle also has database expertise and system design skills. Avonelle is open minded and willing to discuss various methodologies for achieving a project goal. She is also not afraid to ask questions which is vital in a software development project. Her up-front project cost (not estimate) is very helpful in budgeting for a project.
--Dwayne Wolterstorff, Owner @ Fair
Sitefinity ASP.NET CMS