|
Hurry Up & Wait There are no industry standards for Web response times. How long a user is willing to wait for a Web page to load depends on any number of variables and conditions. Find out how to determine and quantify performance criteria and use those criteria to create happy customers.
|
|
|
Piles of Sand When was the last time you thought about floating-point arithmetic? Chuck Allison says in order to attain maximum accuracy we need to brush up on our floating-point number knowledge and get back to our roots.
|
|
|
The Exceptional Exception So much more than a bucket for your errors, exceptions can be a valuable tool that lets you communicate to your clients not only that there is a problem but why and where the code failed.
|
|
|
The Power of Persuasion Twenty years ago, Brian Marick defined a small startup's company process and coding standard in his position as head of quality assurance--and didn't win any popularity points. Looking back, Brian thinks that he and others in charge of process would be more successful using persuasion than using commands.
|
|
|
Browsers with a Bean to Grind Listen in on a coffehouse conversation between Internet Explorer and Mozilla, that have been pushed to the brink by technologies that test their limits and a standards body that nixes their ability to innovate. Find out what they think of their previous successes and what the future holds.
|
|
|
Developers Who Test Every software professional knows that testing is hard, and the situation is even bleaker for software developers. The good news is that effective techniques exist that won't break the schedule or overwhelm developers with test cases. Let loose your inner tester with patterns designed with developers in mind.
|
|
|
Refactoring: Small Steps to Help You Clean Up Your Code Poor software design will slow down even the most well-meaning code. Code smells are one element of poor design to watch out for in your projects. C. Keith Ray explains how you can start washing away your code smells with a dose of code refactoring.
|
|
|
Logging a Path to Code Clarity A good log file may be the best tool to track down those "cannot reproduce" bugs, but creating the best log takes a certain amount of careful nurturing. In this article, Tod Golding explains why log files can be worth every extra line of code.
|
|
|
Patterns Without Purpose Architectural patterns are a convenient way to design and build your code, but be careful not to bite off more than you can chew. Tod Golding offers advice on avoiding useless layers and letting each pattern earn its way into your architecture.
|
|
|
Code With Character Use .NET generics to get to know your data types and form more meaningful, trusting, typesafe relationships with them.
|
|