I can’t disagree with your observations if the independent user is regularly working in a similar field but for different clients (for example). Of perhaps is working with a particlar application set on a regular basis. In those situations there will be shared needs that would work well based on a core and generic ‘object’.

For very random work, however, the opportunties to develop uniquely useful custom functions seem to be fewer. It’s not that they don’t exist but more that the number of opportunities is small and the benefits in terms of saving of effort or sharing methods are much less. Partly, of course, this is because such widely usable good ideas tend to be adopted quite rapidly into general Monarch releases!

However your final paragraph above hit the centre of the target. It all comes down to the personal level of how you get on with the facility available and trying it out is always going to be the best approach for one’s own personal assessment.

Your points concerning modeling in a larger environment are well taken, but I believe that there’s value in the re-use tools for even those working independently.

Creating a library of custom functions can aid both initial development and subsequent readability and it becomes a great resource over time.

While I’ll be among the first to say that there might be a limited need for reusing objects such as specific and unique templates, or simple sort orders, reusing other objects like filters, predefined address blocks and complex calculations can be immensely useful.

Having said that, everyone’s situation and needs are different and what’s useful for me might be useless to you.

There’s only one reliable way to know what you do or do not need to employ when modeling: try it out and get accustomed to the process. You may well be pleasantly surprised by the result and find it well worth the additional effort of learning something new.

I have often wondered how many people manage to take advantage of the Linked Objects facility.

Anyone working on random and varied projects might find the challenge of keeping track of what they have developed and how it might (mostly) be re-used would be more effort than they wish to carry.

But working within a corporate environment with fairly consistent systems and processes should provide many opportunities for re-use and collaboration, consistency and ease of traceability from an audit perspective.

It just has to be worth investing a little time to identify where the gains are to be found.

Grant