In f255efe0ecf08c4a9c1db6aff423541709366...@ch2wpmail1.na.ds.ussco.com,
on 01/05/2009
at 07:32 AM, Chase, John jch...@ussco.com said:
LAR1,13 Thirteen,
When I last taught a programming class I explained that such comments
would reduce their grades.
SLR R0,R0
On 6 Jan 2009 08:01:46 -0800, shmuel+ibm-m...@patriot.net (Shmuel Metz
, Seymour J.) wrote:
LAR1,13 Thirteen,
When I last taught a programming class I explained that such comments
would reduce their grades.
SLR R0,R0 Multiply by one,
An incorrect comment
On 5 Jan 2009 05:35:23 -0800, jch...@ussco.com (Chase, John) wrote:
[label] DS0H
LAR1,13 Thirteen,
SLR R0,R0 Multiply by one,
LTR R1,R1 Still got thirteen,
BZOOPSIE But wasn't that fun?
LAR1,13 Now take
IMO, the best exploration of literate programming and the like is
the anti-pattern - How to write unmaintainable code :
http://mindprod.com/jgloss/unmain.html
Kirk Wolf
Dovetailed Technologies
--
For IBM-MAIN subscribe /
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of P S
[ snip ]
I worked for a development company where, at an engineering meeting,
the VP of Engineering said that folks shouldn't comment their code,
because the comments might not be correct. I waited for him
Argh, key typo: ...they're NOW out of business...!
On Sun, Jan 4, 2009 at 12:10 AM, P S zosw...@gmail.com wrote:
On Fri, Jan 2, 2009 at 3:04 PM, Eric Bielefeld eric-ibmm...@wi.rr.com wrote:
I hope that when people say Real Programmers don't comment code that they
are being humorous, or just
In epusl49s89hp80n0v2teq5k7utai1p6...@4ax.com, on 01/02/2009
at 01:45 PM, Howard Brazee howard.bra...@cusys.edu said:
Today's code should not be obtuse enough that other programmers have to
study to find out what we did. But sometimes they should know why we
did it a particular way.
On Fri, Jan 2, 2009 at 3:04 PM, Eric Bielefeld eric-ibmm...@wi.rr.com wrote:
I hope that when people say Real Programmers don't comment code that they
are being humorous, or just kidding around. Assemble code for someone like
myself who has done a lot of coding, but done it a long time ago, is
On 1 Jan 2009 17:25:30 -0800, eamacn...@yahoo.ca (Ted MacNEIL) wrote:
A TRUE programmer does not comment their code!
It was hard to write; it should be hard to read!
(We don't want others to know that it really wasn't hard to write).
But if we had to analyze what the users wanted - they should
Interesting link
http://www.cfug-md.org/articles/progcreed.cfm
On Fri, Jan 2, 2009 at 10:33 AM, Howard Brazee howard.bra...@cusys.eduwrote:
On 1 Jan 2009 17:25:30 -0800, eamacn...@yahoo.ca (Ted MacNEIL) wrote:
A TRUE programmer does not comment their code!
It was hard to write; it should be
-Ursprungligt meddelande-
Från: IBM Mainframe Discussion List
[mailto:ibm-m...@bama.ua.edu] För Howard Brazee
Skickat: den 2 januari 2009 15:33
Till: IBM-MAIN@bama.ua.edu
Ämne: Re: A Smile for the Week
On 1 Jan 2009 17:25:30 -0800, eamacn...@yahoo.ca (Ted MacNEIL) wrote:
A TRUE
- Original Message -
From: Thomas Berg thomas.b...@swedbank.se
Newsgroups: bit.listserv.ibm-main
To: IBM-MAIN@bama.ua.edu
Sent: Friday, January 02, 2009 9:00 AM
Subject: SV: A Smile for the Week
If You comment Your code You disclose how
smart - or dumb - the thoughts behind the
coding
On 2 Jan 2009 12:10:57 -0800, eric-ibmm...@wi.rr.com (Eric Bielefeld)
wrote:
I hope that when people say Real Programmers don't comment code that they
are being humorous, or just kidding around. Assemble code for someone like
myself who has done a lot of coding, but done it a long time ago, is
Instead of comments and flow charts and the like, let's just go with
literate programming ala Dr. Knuth.
http://www-cs-faculty.stanford.edu/~knuth/lp.html
quote
Literate programming is a methodology that combines a programming language
with a documentation language, thereby making programs more
Howard Brazee wrote:
I remember running a flow-chart program around 1980 that made
absolutely no sense to me. Why have a program read a CoBOL program
and create a flow chart? It's much easier to read the CoBOL program
itself.Documentation is useful in telling us what the program is
4) A TRUE Klingon Warrior does not comment his code!
A TRUE programmer does not comment their code!
It was hard to write; it should be hard to read!
-
Too busy driving to stop for gas!
--
For IBM-MAIN subscribe / signoff /
4) A TRUE Klingon Warrior does not comment his code!
No programmer should comment code!
It was hard to write -- it should be hard to read!
-
Too busy driving to stop for gas!
--
For IBM-MAIN subscribe / signoff / archive access
Received this and thought it worth sharing - may it bring a smile to you
this holiday season and may no one see themselves in this (if so I
apologize in advance)
Top 12 things likely to be overheard if you had a Klingon Programmer
12) Specifications are for the weak and timid!
11) This
18 matches
Mail list logo