16 Aug
2007
16 Aug
'07
1:25 p.m.
"... It is also easier to debug because it does
not use the
structures of nested if-then-else statements known as spaghetti code
popular in conventional programming languages."
...
When did the meaning change?
It hasn't. Let's just say that the quoted speaker has
his own take on things.
http://www.vsmerlot.com/
Click the "Wasn't the GOTO" link to see what he's
talking about.
Then take a look at the QuickSort example, to see how he's
brought new clarity to the ghastly confusion of the
usual coded implementation.
16 Aug
16 Aug
1:30 p.m.
Brian Knittel wrote:
?!
Yuck! Maybe a hard-core mathematician would want to write code like
that, but not me!
Peace... Sridhar
"... It
is also easier to debug because it does not use the
structures of nested if-then-else statements known as spaghetti code
popular in conventional programming languages."
...
When did the meaning change?
It hasn't. Let's just say that the quoted speaker has
his own take on things.
http://www.vsmerlot.com/
Click the "Wasn't the GOTO" link to see what he's
talking about.
Then take a look at the QuickSort example, to see how he's
brought new clarity to the ghastly confusion of the
usual coded implementation.
9:58 a.m.
Chuck Guzis wrote:
Indeed. I think I'd have an easier time writing machine code directly
in hex.
That guy doesn't seem to grasp that many real world problems have
solutions that "evolve". A lot of the time, a programmer isn't
*completely* sure exactly how the program logic will work until it's
well on its way to being written, no? I mean, I'll have a general idea
on how everything will fit together, but I'll get the details done as I
come across them.
Peace... Sridhar
Then take a
look at the QuickSort example, to see how he's
brought new clarity to the ghastly confusion of the
usual coded implementation.
Why...it's so CLEAR and SIMPLE! NOT! :) 
2:24 p.m.
Sridhar Ayengar wrote:
That guy doesn't seem to grasp that many real
world problems have
solutions that "evolve". A lot of the time, a programmer isn't
*completely* sure exactly how the program logic will work until it's
well on its way to being written, no? I mean, I'll have a general idea
on how everything will fit together, but I'll get the details done as I
come across them.
More like when managent decides they need a new feature but only when the customer
pays for it and then it is needed *yesterday*.
Peace... Sridhar
10:50 a.m.
woodelf wrote:
Indeed. Coping with that particular eventuality with one of these giant
state tables must be a nightmare.
Peace... Sridhar
That guy
doesn't seem to grasp that many real world problems have
solutions that "evolve". A lot of the time, a programmer isn't
*completely* sure exactly how the program logic will work until it's
well on its way to being written, no? I mean, I'll have a general
idea on how everything will fit together, but I'll get the details
done as I come across them.
More like when managent decides they need a new feature but only when
the customer
pays for it and then it is needed *yesterday*. 
11:17 a.m.
Zane H. Healy wrote:
I love it when that happens. 8-)
Peace... Sridhar
More like when
managent decides they need a new feature but only when the
customer pays for it and then it is needed *yesterday*.
You've got that right. Though recently I had the fun of telling them the
new feature they wanted was already in place. :^) 
4:01 p.m.
On 16 Aug 2007 at 9:58, Sridhar Ayengar wrote:
That guy doesn't seem to grasp that many real
world problems have
solutions that "evolve". A lot of the time, a programmer isn't
*completely* sure exactly how the program logic will work until it's
well on its way to being written, no? I mean, I'll have a general idea
on how everything will fit together, but I'll get the details done as I
come across them.
This reminds me of hardware sequencers that use a ROM and a few
latches. The glue around it is simplicity itself, but the toasted
gray matter that goes into actually working out the sequencer table
to keep the hardware simple is another story.
Of course, this guy probably thinks that yacc is fluff and writes his
own LALR parser tables from scratch.
Cheers,
Chuck
2:26 p.m.
Brian Knittel wrote:
Well, that was all quite hilarious.
The site also presents a good example of how some people need some
appreciation for history (or should we assume malice instead of ignorance?):
"Using COSA technology the company is capable of demonstrating how to
eliminate the need for software developers."
Thousands have made that claim starting in the 50s with "Automatic
Programming".
"... It is also easier to debug because it
does not use the
structures of nested if-then-else statements known as spaghetti code
popular in conventional programming languages."
...
When did the meaning change?
It hasn't. Let's just say that the quoted speaker has
his own take on things.
http://www.vsmerlot.com/
Click the "Wasn't the GOTO" link to see what he's
talking about.
Then take a look at the QuickSort example, to see how he's
brought new clarity to the ghastly confusion of the
usual coded implementation.
10:36 a.m.
Brent Hilpert wrote:
Well, that was all quite hilarious.
The site also presents a good example of how some people need some
appreciation for history (or should we assume malice instead of ignorance?):
"Using COSA technology the company is capable of demonstrating how to
eliminate the need for software developers."
Thousands have made that claim starting in the 50s with "Automatic
Programming".
And let's not forget DigiTalk PARTS Workbench.
Peace... Sridhar
5:58 p.m.
On Thu, 16 Aug 2007, Brent Hilpert wrote:
"Using COSA technology the company is capable
of demonstrating how to
eliminate the need for software developers."
Thousands have made that claim starting in the 50s with "Automatic
Programming".
false advertising: I had so hoped that "The Last One" would keep their
promise!
2:46 p.m.
On Thu, 2007-08-16 at 10:25 -0700, Brian Knittel wrote:
I would, but the site has broken CSS, so when I hover my mouse over the
link the whole thing jitters up and down.
Gordon
"... It
is also easier to debug because it does not use the
structures of nested if-then-else statements known as spaghetti code
popular in conventional programming languages."
...
When did the meaning change?
It hasn't. Let's just say that the quoted speaker has
his own take on things.
http://www.vsmerlot.com/
Click the "Wasn't the GOTO" link to see what he's
talking about.
6186
days inactive
6186
days old
12 comments
8 participants
participants (8)
-
bfranchuk＠jetnet.ab.ca -
brian＠quarterbyte.com -
cclist＠sydex.com -
cisin＠xenosoft.com -
gordon＠gjcp.net -
healyzh＠aracnet.com -
hilpert＠cs.ubc.ca -
ploopster＠gmail.com