RE: Saving the System i: Fight Rather Than Switch

["albartell" <albartell@xxxxxxxxx>]

I didn't bring the rest up because they can all be "caught" by a
code/programmer review.  I agree that those things should be in place though
I don't want to dig into any of them today as I am sure we could discuss at
length :-)  For instance, I have my own ideas about modernization that have
been fleshed out on the RPG-L list.  I very much dislike purist
modernization.

Anyways, back to work for me:-)

Aaron Bartell

 

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Trevor Perry
Sent: Friday, December 15, 2006 3:57 PM
To: Midrange Systems Technical Discussion
Subject: Re: Saving the System i: Fight Rather Than Switch

Aaron,

What about the other 6 things?

My point is that we, in the System i world, do NOT follow disciplined
standards. Which sets us apart from the IT industry as being out-of-date.

When I DO find a System i shop who performs regular code reviews, I
generally find that they spend less time on maintenance. And less time in
the code/fix/compile cycle.

Trevor


----- Original Message -----
From: "albartell" <albartell@xxxxxxxxx>
To: "'Midrange Systems Technical Discussion'" <midrange-l@xxxxxxxxxxxx>
Sent: Friday, December 15, 2006 3:48 PM
Subject: RE: Saving the System i: Fight Rather Than Switch


> How many of the IT managers on this list do programmer reviews of code on 
> a
> regular basis?  I don't disagree that this can really make a shops code
> clean, organized, efficient, etc, but I am thinking it is incredibly rare
> today.  I only check other peoples code if I am training them on something
> new or am suspicious of their commitment to code well.
>
> Awhile back there were rumors that developers were going to be held 
> legally
> liable for errors in code because of the disrupting currents in economics
> software bugs can create.
>
> In summary: I think shops do code reviews were it is imperative the code 
> be
> right (pricing routines come to mind).
>
> Aaron Bartell
>
> -----Original Message-----
> From: midrange-l-bounces@xxxxxxxxxxxx
> [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Trevor Perry
> Sent: Friday, December 15, 2006 3:37 PM
> To: Midrange Systems Technical Discussion
> Subject: Re: Saving the System i: Fight Rather Than Switch
>
> Aaron,
>
> I have already mentioned some of them. Here is a longer list off the top 
> of
> my head:
>
> 1. Coding standards - documented. And followed.
> 2. Change management - enforced.
> 3. Coding documentation - enforced.
> 4. Program design (before coding, after application design) 5. Right tool
> for the right job - starting with a correctly sized developer PC 6. 
> Program
> review/s.
> 7. Modularization.
>
> Trevor