Pull Up, Abstract, Override
“The core of object oriented design: pull up, abstract, override.” (Elisa Baniassad et al.)
“The core of object oriented design: pull up, abstract, override.” (Elisa Baniassad et al.)
“There’s a school of thought that says you «start with the types,» my view is «you start with reflection»” (Gilad Bracha)
”A program is decisions made. Humans make those decisions and write them into programs.” (Ward Cunningham)
“Data/facts are not in any way dynamic (they are accreting, that’s all)” (Rich Hickey)
“Design — the interaction between understanding and creation” (T. Winograd, F. Flores)
“In fact, you shouldn’t write any serious application in Forth; as a language it’s simply not powerful enough. What you should do is write your own language in Forth to model your understanding of the problem, in which you can elegantly describe its solution.” (Leo Brodie) After Lisp, here comes another lousy language.
“It appears to me that if one wants to make progress in mathematics one should study the masters and not the pupils.” (N.H. Abel)
“Analysis is the study and modeling of a given problem domain, within the context of stated goals and objectives.” (Ken Rubin, Adele Goldberg)
“Good programmers don’t just write programs. They build a working vocabulary.” (Guy L. Steele Jr)
In short, it demands the reviewer’s full participation in finishing the solution that the original developer started. That is, asynchronous pair programming. Rest of the article