Skip to main content
    Country/region select      Terms of use
     Home      Products      Services & solutions      Support & downloads      My account     

developerWorks  >  Lotus  >  Forums & community  >  Best Practice Makes Perfect

Best Practice Makes Perfect

A collaboration with Domino developers about how to do it and how to get it right in Domino

A while back I blogged about the collected set of Notes/Domino best practices -- we were promised more of these, and now they have arrived. The Notes from Lotus Support blog contains a table of links.
Of course, there's more to say about best practices in any particular sub-area than you can fit into a document that can be read on-screen, so these are primarily compilations of links to articles and whitepapers on the subject. I guess I should put that on my list.

We seem to be missing a best practice document for maintainability of applications. As I've been saying, performance is all very well, but people time is more expensive than computer time, and the difference is only going to increase since Moore's Law doesn't apply to people (yet). An application you write today will get faster as time goes by, and it probably also will get somewhat easier to maintain as the tools improve, but at nowhere near the same rate of improvement. Good design is the only answer that really works.

Andre Guirard | 7 May 2007 08:56:00 PM ET | Caribou Coffee, Plymouth, MN, USA | Comments (1)


1) Uh no
Nathan T. Freeman | 5/8/2007 6:49:10 AM

"An application you write today will get faster as time goes by..."

Andre, I have to outright disagree with you there. An application you write today will get faster, IF THERE IS NO USAGE OF IT. But even with Moore's Law, the usage patterns of a successful application will tend to slow it down at a rate faster than Moore's Law will accelerate it.

There is no better example of this than a person's Notes Inbox. As time goes by, the steady addition of new mail drags performance. In the vast majority of real world situations, the performance degradation outpaces hardware updates, whether at the client, the server, or the network.

The history of the Notes platform in many implementations is one of non-scalable departmental applications thrown on bigger and bigger hardware, in an effort to find scalability out of something that was designed on the cheap and in a hurry in the first place.

There's something far more valuable than developer time. It's user time. A developer who spends an extra week or an extra month making sure an app is scalable and easy to use is investing wisely. Banking on Moore's law to lower interface click-count is just a fool's errand.

Sorry if I seem adamant about this -- since you probably mean something different than I'm reading, but based on what you chose to boldface in this posting, I believe you should re-think that statement.

 Add a Comment
Comment:  (No HTML - Links will be converted if prefixed http://)
Remember Me?     Cancel

Search this blog 


    About IBM Privacy Contact