| |
|
|
Zum leidigen Thema
Dokumentation |
|
|
Aber |
“If your program isn´t worth
documenting, it probably isn´t worth running.” [Nagler
95] |
“When you feel the need to write a
comment, first try to refactor the code so that any
comment becomes superfluous.” [Fowler
99]
|
und
Code-Verständlichkeit |
|
Da kenn ich so ein paar C++-Spezialisten, für
die gilt: |
"Any fool can write code that a
computer can understand. Good programmers write code that
humans can understand." [Fowler
99] pg.15
|
Zum leidigen Thema
Testen |
|
"It is better to write and run
incomplete tests that not to run complete tests" [Fowler
99] pg.98 |
"Don't let the fear that testing
can't catch all bugs stop you from writing the tests that will
catch most bugs." [Fowler
99]pg.101
|
"When you get a bug report, start by
writing a unit test that exposes the bug." [Fowler
99] pg.97 |
"Before you start refactoring, check
that you have a solid suite of tests. These tests must be
self-checking." [Fowler
99] pg.8 | |
“Would you buy a house or a car that had a typical
`shring-wrapped software´ disclaimer?” fragt Dennis Frailey in einem
Artikel über Professional Software-Engineering in IEEE Software Dec99 Natürlich
nicht, oder?
|
|
"Die Komplexität heutiger
Software wird nur noch von einem übertroffen: von der Komplexität,
Verschlungenheit und Widersprüchlichkeit der gruppendynamischen Prozesse,
die diese Software umranken."
|
"Is Design Dead? Extreme
Programming (XP)challenges many of the common assumptions about software
development. Of these one of the most controversial is its rejection of
significant effort in up-front design, in favor of a more evolutionary
approach. To its detractors this is a return to "code and fix" development
- usually derided as hacking. To its fans it is often seen as a rejection
of design techniques (such as the UML), principles and patterns. Don't
worry about design, if you listen to your code a good design will appear."
Martin
Fowler
|
James Gosling über AOP, deren Theorie er mag, aber "It's like giving
them (the people) a chainsaw without any safety instructions."
Mich erinnert AOP ziemlich an multiple inheritance (z.B. in C++), das ähnlich
intransparent und fehleranfällig war. |
|
|
Letzte Änderung: 1.9.2001 |
| |