25 Jun
2019
25 Jun
'19
6:11 p.m.
There's nothing like sitting in a room listening to your elders argue
over minutiae. Or huge issues such as code cleanliness ;)
I didn't even graduate high school, but one of the first things my
mentor/boss did before I started working for him as a consultant was to
comment, and write clean code. And that was on TOPS-10, using MACRO-10.
I've recently been exposed to a grad student's C++ code, and between no
error checking and outright lack of formatting or any other care in the
world for "clean" code, his stuff is atrocious. His casts from one type
to another to another to another through nested function calls makes my
skin crawl.
ak
On 6/25/2019 4:00 AM, Kevin Bowling wrote:
Why not? The utility of history isn't just
recording or paying
reverence for the past, we can also draw conclusions in the current or
insights into the future -- "the old new thing"
That's certainly why I'm here and invest in computer history. Of
course it can be lossy, and victors get more air time. But there's
nothing inherently wrong with strong opinions or criticism of the
past.
Regards,
Kevin
On Mon, Jun 24, 2019 at 6:01 PM Richard Salz <rich.salz(a)gmail.com> wrote:
> Is this really the kind of commentary appropriate for this list? I mean I'm new
here, but...