ok... here's just a quick one that hopefully will make sense...

I think the subject line says it all - where possible, use Functions instead of Subroutines (in LotusScript).

Over the last few years I've seen a lot of code and it seems that most people are writing their code in subroutines and not taking advantage of the return code available with a function. At the very least, one of the greatest benefits of using a function is so you can return a True/False value based on whether the function succeeds or fails.

...more »

Here's one that seems to slip through the nets here and there and people tend to forget about it - using the alias on the design element so you can name the same design element in a number of different ways.

an example - I might have a view which shows all the user profile documents in my app. If that same view is used to show the documents in the application outline, used in a lookup function, and used to display a picklist to the user so they can select a user document, I would give it four different names - well.. probably only 3 but for argument's sake, let's go with the following 4...

...more »

ok... obviously for every "don't" list there's a "do" list

Again, it's just an opinion, but I feel that there are a number of things that Lotus let you do that are underutilised by a lot of people - I'm not sure why, perhaps it's because once you're on a strategy that works for you then most people don't change, but it's worth lifting yourself up from the swampy landscape that surrounds your cubicle to see how you can change your ways in case it makes things a little funkier than normal.

same thing applies as the don't list... feel free to agree/disagree, but it's just my opinion

...more »