“The first paper I ever wrote was "Gestalt Programming" and that was in 1955. The whole idea there was to replace the laborious writing out of detailed programs and all those steps by having analyzed a problem area well enough so that you had what I later came to call a "systematized solution." Then you could compose different problems of this class by just plugging together pieces of program, and they would in turn be controlled by a pushbutton language. The user would make a number of discreet selections. It's just like nowadays it's done with menus, and when you had indicated all the pieces that you wanted to put together--by these mnemonic names and words for things associated with buttons, switches, with one meaning "period," essentially, for that sentence, you see--all these things would be brought together and that would be the man/machine, manual-intervention mode of problem-solving. I took over the term from studying Gestalt psychology, meaning that everything was brought together at once, as a unit, instead of this laborious step-by-step build-up.”

— Douglas T. Ross

Source: An Interview with Douglas T. Ross (1989), p. 4.

Adopted from Wikiquote. Last update Sept. 14, 2021. History

Help us to complete the source, original and additional information

Do you have more details about the quote "The first paper I ever wrote was "Gestalt Programming" and that was in 1955. The whole idea there was to replace the la…" by Douglas T. Ross?

Douglas T. Ross 27

American computer scientist 1929–2007

Related quotes

“I don't know how to stop it, there was never any intent to write a programming language […] I have absolutely no idea how to write a programming language, I just kept adding the next logical step on the way.”

Rasmus Lerdorf (1968) Danish programmer and creator of PHP

Itconversations.com http://itc.conversationsnetwork.org/shows/detail58.html quoted in www.dasgenie.com http://www.dasgenie.com/scrap/archives/000060.html

“If the users don't control the program, the program controls the users. With proprietary software, there is always some entity, the "owner" of the program, that controls the program—and through it, exercises power over its users. A nonfree program is a yoke, an instrument of unjust power.”

Richard Stallman (1953) American software freedom activist, short story writer and computer programmer, founder of the GNU project

Free Software Is Even More Important Now (September 2013) https://www.gnu.org/philosophy/free-software-even-more-important.html
2010s

“The vision we have of conversational programming takes in much more than rapid turn around time and convenient debugging aids: our most interesting programs are never wrong and never final. […] What is new is the requirement to make variable in our languages what we had previously taken as fixed. I do not refer to new data classes now, but to variables whose values are programs or parts of programs, syntax or parts of syntax, and regimes of control.”

Alan Perlis (1922–1990) American computer scientist

The Synthesis of Algorithmic Systems, 1966

“Programming in the abstract sense is what I really enjoy. I enjoy lots of different areas of it… I'm taking a great deal of enjoyment writing device drivers for Linux. I could also be having a good time writing a database manager or something because there are always interesting problems.”

John D. Carmack (1970) American computer programmer, engineer, and businessman

Quoted in Bob Colayco, "John Carmack Interview" http://www.firingsquad.com/features/carmack/page3.asp Firing Squad(2000-02-09)

“Programming languages on the whole are very much more complicated than they used to be: object orientation, inheritance, and other features are still not really being thought through from the point of view of a coherent and scientifically well-based discipline or a theory of correctness. My original postulate, which I have been pursuing as a scientist all my life, is that one uses the criteria of correctness as a means of converging on a decent programming language design—one which doesn’t set traps for its users, and ones in which the different components of the program correspond clearly to different components of its specification, so you can reason compositionally about it. […] The tools, including the compiler, have to be based on some theory of what it means to write a correct program.”

C. A. R. Hoare (1934) British computer scientist

Oral history interview http://hdl.handle.net/11299/107362 by Philip L. Frana, 17 July 2002, Cambridge, England; Charles Babbage Institute, University of Minnesota.

“Organizations make two responses to deal with the behavior control problem. The first change involves the substitution of craft or professional training of the work force for the detailed centralized programming of the work processes.”

Jay R. Galbraith (1939–2014) American business theorist

Source: Designing complex organizations, 1973, p. 12

“If there's a particular problem that Perl is trying to solve, it's the basic fact that all programming languages suck. Sort of the concept of original sin, applied to programming languages.”

Larry Wall (1954) American computer programmer and author, creator of Perl

Public Talks, The State of the Onion 10

“Well, take it from an old hand: the only reason it would be easier to program in C is that you can't easily express complex problems in C, so you don't.”

Erik Naggum (1965–2009) Norwegian computer programmer

Re: new to lisp (3rd time lucky) http://groups.google.com/group/comp.lang.lisp/msg/ef9b57ecc5555931 (Usenet article).
Usenet articles

“Program designers have a tendency to think of the users as idiots who need to be controlled. They should rather think of their program as a servant, whose master, the user, should be able to control it. If designers and programmers think about the apparent mental qualities that their programs will have, they'll create programs that are easier and pleasanter — more humane — to deal with.”

John McCarthy (1927–2011) American computer scientist and cognitive scientist

" The Little Thoughts of Thinking Machines http://www-formal.stanford.edu/jmc/little.html", Psychology Today, December 1983, pp. 46–49. Reprinted in Formalizing Common Sense: Papers By John McCarthy, 1990, ISBN 0893915351
1980s

“When we had no computers, we had no programming problem either. When we had a few computers, we had a mild programming problem. Confronted with machines a million times as powerful, we are faced with a gigantic programming problem.”

Edsger W. Dijkstra (1930–2002) Dutch computer scientist

Dijkstra (1986) Visuals for BP's Venture Research Conference http://www.cs.utexas.edu/users/EWD/transcriptions/EWD09xx/EWD963.html (EWD 963).
1980s

Help us to complete the source, original and additional information

Douglas T. Ross 27

Related quotes

Related topics