My advice is always to make it easy for next guy. Chances are, over time, the 
'next guy' will be the future you. 

.
.
J.O.Skip Robinson
Southern California Edison Company
Electric Dragon Team Paddler 
SHARE MVS Program Co-Manager
323-715-0595 Mobile
626-543-6132 Office ⇐=== NEW
robin...@sce.com

-----Original Message-----
From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On Behalf Of 
John McKown
Sent: Tuesday, August 13, 2019 9:19 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: (External):Re: Instruction speeds

On Tue, Aug 13, 2019 at 11:10 AM Brian Chapman <bchapma...@gmail.com> wrote:

> Thanks Charles and Steve.
>
> Now that I am becoming a more experience assembler programmer, I have 
> wondered if I should be greatly concerned about instruction timings or 
> pipeline order, or just simply focus on readability and maintenance.
> Especially since assembler programming is becoming a dying art. I 
> think I am only 1 of a handful of assembler programmers at my shop 
> with hundreds of mainframe programmers! I think you both answered my 
> question. Thanks!
>

KISS - make it easy to maintain. I have written code which even I didn't 
understand a few years later.


>
>
> Thank you,
>
> Brian Chapman


----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Reply via email to