“All OO languages show some tendency to suck programmers into the trap of excessive layering. Object frameworks and object browsers are not a substitute for good design or documentation, but they often get treated as one. Too many layers destroy transparency: It becomes too difficult to see down through them and mentally model what the code is actually doing. The Rules of Simplicity, Clarity, and Transparency get violated wholesale, and the result is code full of obscure bugs and continuing maintenance problems.”

—  Eric S. Raymond, book The Art of Unix Programming

The Art of Unix Programming: Unix and Object-Oriented Languages, Eric S. Raymond, 2003, 2014-08-06 http://www.catb.org/esr/writings/taoup/html/unix_and_oo.html,

Adopted from Wikiquote. Last update June 3, 2021. History

Help us to complete the source, original and additional information

Do you have more details about the quote "All OO languages show some tendency to suck programmers into the trap of excessive layering. Object frameworks and obje…" by Eric S. Raymond?
Eric S. Raymond photo
Eric S. Raymond22
American computer programmer, author, and advocate for the … 1957

Related quotes

Martin Fowler photo

“Transparency is valuable, but while many things can be made transparent in distributed objects, performance isn't usually one of them.”

Martin Fowler (1963) British programmer

Fowler (2003) in: Software development. Vol. 11. p. 99

Linus Torvalds photo

“…git actually has a simple design, with stable and reasonably well-documented data structures. In fact, I'm a huge proponent of designing your code around the data, rather than the other way around, and I think it's one of the reasons git has been fairly successful […] I will, in fact, claim that the difference between a bad programmer and a good one is whether he considers his code or his data structures more important. Bad programmers worry about the code. Good programmers worry about data structures and their relationships.”

Linus Torvalds (1969) Finnish-American software engineer and hacker

Message to Git mailing list, Torvalds, Linus, 2006-06-27, 2006-08-28 http://lwn.net/Articles/193245/, <br class="br">2000s, 2006

Karen Joy Fowler photo

“Antagonism in my family comes wrapped in layers of code, sideways feints, full deniability. I believe the same can be said of many families.”

Karen Joy Fowler book We Are All Completely Beside Ourselves

Source: We Are All Completely Beside Ourselves

Rob Pike photo

“On a related topic, let me say that I'm not much of a fan of object-oriented design. I've seen some beautiful stuff done with OO, and I've even done some OO stuff myself, but it's just one way to approach a problem. For some problems, it's an ideal way; for others, it's not such a good fit. […] OO is great for problems where an interface applies naturally to a wide range of types, not so good for managing polymorphism (the machinations to get collections into OO languages are astounding to watch and can be hellish to work with), and remarkably ill-suited for network computing. That's why I reserve the right to match the language to the problem, and even - often - to coordinate software written in several languages towards solving a single problem. It's that last point - different languages for different subproblems - that sometimes seems lost to the OO crowd.”

Rob Pike (1956) software engineer

Rob Pike (2004) in interview http://interviews.slashdot.org/article.pl?sid=04/10/18/1153211&amp;tid=189 at slashdot.com, Oct 18 2004

“Frameworks are white boxes to those that make use of them. Application developers must be able to quickly understand the structure of a framework, and how to write code that will fit into the framework. Frameworks are reusable designs as well as reusable code.”

Rebecca Wirfs-Brock (1953) American software engineer

Source: Object-oriented design: a responsibility-driven approach (1989), p. 13

“One of the distinct features of XP is the lack of any documentation whatsoever, except for the code itself. This is a contraposition to the modeling techniques like the Unified Modeling Language (UML), which strongly focus on documentation. XP takes an extreme position there, not even documenting the architecture of the system. Often, it is very difficult to extract the overall structure, behavior or interactions with the environment from the code. The code is a rather detailed and fragile representation of the system’s tasks. Even though the code contains all necessary information about the system, this information is often burdened with details and it is tedious to extract the aspects one is interested in. Therefore, it would be useful to have a more compact system representation. The UML does provide a number of notations that are suited for this purpose. However, the tools so far are not capable of supporting UML in such a manner that it can be well-integrated with the approach of Extreme Programming.”

Bernhard Rumpe (1967) German computer scientist

Source: Executable Modeling with UML. A vision or a Nightmare (2002), p. 698

Barry Boehm photo

“The Code-and-Fix Model. The basic model used in the earliest days of software development contained two steps:
:1. Write some code.
:2. Fix the problems in the code.
Thus, the order of the steps was to do some coding first and to think about the requirements, design, test, and maintenance later. This model has three primary difficulties: (a) After a number of fixes, the code became so poorly structured that subsequent fixes were very expensive. This underscored the need for a design phase prior to coding. (b) Frequently, even well designed software was such a poor match to users' needs that it was either rejected outright or expensively redevelopment…”

Barry Boehm (1935) American software engineer

Source: A spiral model of software development and enhancement. (1988), p. 61-62

Théophile Gautier photo

“Eyes so transparent that through them one sees the lucent soul.”

Théophile Gautier Paris

Ils sont si transparents qu'ils laissent voir votre âme.
"À Deux Beaux Yeux", line 12, in Poésies Complètes (Paris: Charpentier, 1845) p. 278; Maturin Murray Ballou (ed.) Notable Thoughts about Women (Boston: Houghton, Mifflin, 1882) p. 398.

C. A. R. Hoare photo

“The real value of tests is not that they detect bugs in the code, but that they detect inadequacies in the methods, concentration, and skills of those who design and produce the code.”

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

How Did Software Get So Reliable Without Proof? Lecture Notes in Computer Science vol 1051 1996 pp. 1-17 : FME '96: Industrial Benefit and Advances in Formal Methods, Third International Symposium of Formal Methods Europe, Co-Sponsored by IFIP WG 14.3, Oxford, UK, March 18-22, 1996, Proceedings.

“Thus it is with all pictures, there are many layers, and with good reason an analysis nearly always deals with the last [layer]. The last layer in a superficial sense. But how then can one talk of what one cannot see, the overpainted or wiped-off layers, how to go about for example, photographs that are like slates with layers which no longer exist. The answer is that they exists nevertheless, taken up into the visible layer by a rubbing-off, but the problem, on the whole, is how one deals with the visible layer. The angle-sure, viewpoint seeking and in the worse sense 'analytic' intercourse with the picture.”

Per Kirkeby (1938–2018) Danish artist

1965 - 1995, Bravura', Per Kirkeby, (1982)

Related topics