Re: Development Standards -- MIDRANGE-L

Subject: Re: Development Standards
From: Buck Calabro <kc2hiz@xxxxxxxxx>
Date: Mon, 12 Dec 2016 14:40:53 -0500
List-archive: <http://archive.midrange.com/midrange-l/>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

On 12/12/2016 2:28 PM, Michael Ryan wrote:

implement, and 3. Decide on enforcement. I don't know the odds of pulling
this off - it's going to depend on management buy-in. But, they asked for
ideas, so here we go.

Take the broadest viewpoint your situation allows. For example, I think
that there is immense utility in TDD, and if at all possible, that's
where I'd stick my pry bar.

Follow-Ups:

Re: Development Standards , Michael Ryan

This mailing list archive is Copyright 1997-2026 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.