Feh, comments are for wimps! /s Srsly, though -- at a previous job (Linuxcare), VP of Engineering made an offhand comment about not commenting code, making it clear that he saw this as A Good Thing. I asked one of the other guys about it and was told that he was dead serious: that some people see commenting code as bad because "The comments might be wrong", or at least might become wrong as the code evolves. See, you're supposed to figure out what the code is doing by reading it.
Still SMH at that one. I tried but could not get any understanding that the point of comments isn't what the code is *doing*, but rather what it's *trying to do*. -----Original Message----- From: IBM Mainframe Assembler List <ASSEMBLER-LIST@LISTSERV.UGA.EDU> On Behalf Of Seymour J Metz Sent: Saturday, August 23, 2025 7:24 PM To: ASSEMBLER-LIST@LISTSERV.UGA.EDU Subject: Re: Execute-Type Instructions Shortening the code often makes it easier to read. Of course, suitable comments are still a must.
