×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
We have an IS Menu with a "Standard Modules" page
This works ok, as long as we remember to add a demo pgm
to the page (and re-fresh old demos when enhancing existing)
Funny how eliminating some of these problems seems
like chasing a carrot on a stick....
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Sam_L
Sent: Thursday, January 05, 2012 7:19 PM
To: midrange-l@xxxxxxxxxxxx
Subject: In-house Reusable Code: Publishing and Documenting
Reusable code is a great concept, but unless you know a routine exists and what it does you can't use it.
We're a small shop and we have some reusable service programs and commands. The few heavily used commands are easy to remember, but folk forget about the rest. (I just bumped into one today that *I* created a year ago and had completely forgotten about.)
Have any of you found good answers to either of these questions for a shop with 5 or more developers?
1) How do y'all make people aware what reusable routines exist?
2) How do folk find what a reusable routine does, short of reading the code?
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at
http://archive.midrange.com/midrange-l.
midrange.com
