4/9/07 • I'm not entirely sure why, but I searched ACM and IEEE for all papers
with "Considered Harmful" in the title. The length of this list
should substantiate my claim that that phrase should be banned from the
literature.
I was pleased to find that someone has already formed the same opinion as me
but actually bothered to justify it: see
"Considered
Harmful" Essays Considered Harmful.
Guy Steele is the winner with two entries. I moved the more
interesting ones to the top and linked them to the full text... everything through
"Garbage In/Garbage Out."
Knowledge considered harmful
Scott, P.D.; Markovitch, S.
Hello, world considered harmful
Ralph Westfall
Software engineering considered harmful
Dennis de Champeaux
The arrogant programmer: Dijkstra and Wegner considered harmful
Robert J. DuWorks, Steven W. Smoliar
Junk considered harmful
Philip S. Abrams
Polymorphism considered harmful
Carl Ponder, Bill Bush
"=" considered harmful
Dean W. Gonzalez
Comments considered harmful
Anders Beckman
Ignorance of ALGOL 68 considered harmful
Richard Hamlet
IF-THEN-ELSE considered harmful
Gerald M. Weinberg, Dennis P. Geller, Thomas W. S. Plum
Pseudo object-oriented programming considered harmful
Conrad Weisert
Web services considered harmful?
Rohit Khare, Jeff Barr, Mark Baker, Adam Bosworth, Tim Bray, Jeffery McManus
In defense of program testing or correctness proofs considered harmful
Andrew S. Tanenbaum
Use cases considered harmful
Simons, A.J.H.
Primitive types in Java considered harmful
Nick Ourusoff
Operators Considered Harmful
Martin Gfeller
C++ templates considered harmful
H. Paul Haiduk
Arrays and pointers considered harmful
D. C. Ince
Frameless rendering: double buffering considered harmful
Gary Bishop, Henry Fuchs, Leonard McMillan, Ellen J. Scher Zagier
I/O considered harmful (at least for the first few weeks)
John Rosenberg, Michael K??lling
Toy projects considered harmful
Fred Martin
Multiple choice questions not considered harmful
Karyn Woodford, Peter Bancroft
Analogy considered harmful
Frank Halasz, Thomas P. Moran
Fragmentation considered harmful
C. A. Kent, J. C. Mogul
Benchmark health considered harmful
Craig B. Zilles
C in the first course considered harmful
L. F. Johnson
Compiler textbook bibliographies considered harmful
V. Schneider
Debunking the "expensive procedure call" myth or, procedure call
implementations considered harmful or, LAMBDA: The Ultimate GOTO
Guy Lewis Steele
Address/memory management for a gigantic LISP environment or, GC
considered harmful
Jon L. White
Operators considered harmful
Martin Gfeller
Garbage In/Garbage Out: You could learn a lot from a quadratic:
overloading considered harmful
Henry G. Baker
Programming early considered harmful
Lewis E. Hitchner, Judith Gersting, Peter B. Henderson, Philip
Machanick, Yale N. Patt
The education and licensing of software professionals: the myth of "a
perfected science" considered harmful
Don Gotterbarn
Design early considered harmful: graduated exposure to complexity and
structure based on levels of cognitive development
Duane Buck, David J. Stucki
Goal-oriented programming, or composition using events, or threads
considered harmful
Robbert van Renesse
Bandwagons considered harmful, or the past as prologue in curriculum change
David G. Kay
Considered harmful--still
Robert Bernecky
L-one-two-three (L1:..L2:..L3:) considered harmful
F. H. D. van Batenburg
Partially overlapped channels not considered harmful
Arunesh Mishra, Vivek Shrivastava, Suman Banerjee, William Arbaugh
Fresh: Human-centered design considered harmful
Donald A. Norman
Dataless objects considered harmful
Chenglie Hu
Lack of priority queuing considered harmful
Vijay Gill
Life cycle concept considered harmful
Daniel D. McCracken, Michael A. Jackson
"Cloning Considered Harmful" Considered Harmful
Kapser, C.; Godfrey, M.W.
Rainbow Color Map (Still) Considered Harmful
David Borland; Russell M. Taylor II
W* effect considered harmful
Khare, R.
Monopoly considered harmful
Geer, D.E., Jr.
Visuo-Haptic Systems: Half-Mirrors Considered Harmful
Christian Sandor; Shinji Uchiyama; Hiroyuki Yamamoto
IPv6 Stateless Address Autoconfiguration Considered Harmful
Lindqvist, J.
Random waypoint considered harmful
Yoon, J.; Liu, M.; Noble, B.
Communication primitives for ubiquitous systems or RPC considered harmful
Saif, U.; Greaves, D.J.
Policy division and fusion: examples and a method-or, multiple
classifiers considered harmful
Kanada, Y.
Current parsing techniques in software renovation considered harmful
van den Brand, M.; Sellink, A.; Verhoef, C.
Strictly class-based modelling considered harmful
Krogh, B.; Levy, S.; Dutoit, A.; Subrahmanian, E.
Symbol security condition considered harmful
Schaefer, M.
Virtual Processors Considered Harmful
Christy, P.
Global consistency constraints considered harmful for heterogeneous
database systems
Garcia-Molina, H.
Independence assumptions considered harmful
Alexander Franz
Emergent behaviours considered harmful
Dana Moore, William Wright
English for decision tables considered harmful
Michael Lesk
Structured programming considered harmful
William Slater, Howard Modell
"Structured programming" considered harmful
Paul Abrahams
Send-receive considered harmful: Myths and realities of message passing
Sergei Gorlatch
Arithmetic shifting considered harmful
Guy L. Steele
Global variable considered harmful
W. Wulf, Mary Shaw
Go to statement considered harmful
Edsger W. Dijkstra
