Re: Development Standards

[Nathan Andelin <nandelin@xxxxxxxxx>]

I think consistency has a lot of value. Just make the process of coming up
with standards a joint effort between those who end up having to adhere to
them. Each shop may have different ideas. I personally prefer fully free
form. But the younger generation around here still prefer "D" and "P" specs
;-).



On Fri, Dec 9, 2016 at 1:30 PM, Michael Ryan <michaelrtr@xxxxxxxxx> wrote:

> Well, I hope I'm not thinking about consistency for its own sake. I don't
> know of a specific example. It's just my sense that if one developer starts
> work variable names with one prefix, and another with a different prefix,
> one could make assumptions when they look at code. Maybe I'm not making
> sense. Maybe consistency is overrated. I was really looking for a 'this is
> how we do it.' I'll sharpen my Google skills.
>
> Sent from my iPhone
>
> > On Dec 9, 2016, at 3:12 PM, Buck Calabro <kc2hiz@xxxxxxxxx> wrote:
> >
> > > On 12/9/2016 2:14 PM, Michael Ryan wrote:
> > > At least stars are in your eyes Buck. :)
> > >
> > > Consistency is the main goal here. Rather than multiple developers all
> > > using different conventions and techniques, the goal would be to have
> > > everyone using the same methods. A goal would be to have a developer be
> > > able to look at another developer's product without having to 'learn'
> their
> > > technique. It's not much of a goal, but it's (I think) a critical first
> > > step for more advancement.
> >
> > Again, I don't want to inject my... bias into the thread (yet).  What
> > about the current setup makes it necessary for programmer A to learn
> > programmer B's technique before working on her code?
> >
> > Can you post an example where this occurs?
> >
> > I'm thinking about the difference between
> > I think X is happening
> > A told me that X is happening
> > I see X happening
> >
> > --
> >  --buck
> >
> > Visit wiki.midrange.com and register for an account. Edit a page that
> > helps you, and because it's public, you'll help someone else, too!
> >
> > --
> > 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.
> >
> > Please contact support@xxxxxxxxxxxx for any subscription related
> questions.
> > Help support midrange.com by shopping at amazon.com with our affiliate
> link: http://amzn.to/2dEadiD
> --
> 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.
>
> Please contact support@xxxxxxxxxxxx for any subscription related
> questions.
>
> Help support midrange.com by shopping at amazon.com with our affiliate
> link: http://amzn.to/2dEadiD