Just Enough Governance for Notes Blog

Bookmark :              

On Ben Poole's recent post (Starting a New Project?) I commented that many people we speak to consider some of the things on Ben's list to be anti-RAD. They see RAD as being quick and flexible, yet too often this translates to sloppy and cutting corners in practice. This of course implies the things on Ben's list are a bad thing for Notes development, or at the very least, not suited to the way these devs work.

On first read of Ben's, it brought The Joel Test to mind even though Ben's is primarily looking at Domino. Both are sensible, sound lists of simple steps that can be undertaken by pretty much any team. Tips and suggestions like the contents on the list make you look better, make your life easier and help Domino utilise principles that apply to the majority of development platforms in use today. How can they be sacrificed to appease deadlines when they should be worshipped on the altar of the development gods?"

Which is the better guide list? Tough call. Domino development is not such a special case when it comes to the simple requirements of using source code control or simple, regular builds. If Notes pros & managers accepted this, I believe they would be able to increase the quality and robustness of their apps, delivering a more cost effective service to their organisation at the same time. After all, we all have a vested interest in making sure the Redmond monster doesn't creep in at Notes' expense.

Finally, if you are going to UKLUG this week, come over and say hello at the Teamstudio area.