Re: simpletest vs phpunit vs ... [message #180508 is a reply to message #180505] |
Fri, 22 February 2013 20:41 |
Anders Wegge Keller
Messages: 30 Registered: May 2012
Karma:
|
Member |
|
|
legalize+jeeves(at)mail(dot)xmission(dot)com (Richard) writes:
> In my decades of experience looking at other people's code, code that
> is aggressively refactored and has well chosen identifiers -- in other
> words the kind of code that I and others are saying doesn't need
> explanatory comments -- is much, much more maintainable years or
> decades later than code festooned with explanatory comments.
You are right. And you're wrong.
I guess that your primary work is on a _product_ that is debugged,
refined, relased over and over again, but never exist in more than one
incarnation. If that is so, you are probably right.
If on the other hand, you had been working in a project organization,
like I do, you would have known that there isn't enough time to
refactor all 600.000 lines of code[1], for each of the 600 projects
that has 92-96% of the code in common. What you'd do, had you worked
at my job, would be commenting the changes to the routing code
algorithm. And depending on the particulars, it could be so simple as
to explain that characters 4 to 17 of the barcode scanned is looked up
in a table that tells the destination, or refering to a 17 page
flowchart[2], that explains the neccesity of all the backtracking
that's done.
My claim is that what works for you, doesn't neccesarily work for
everyone else.
1. C in this case. But that's probably not changing the merits of my
observations.
2.I'm not making this up. There's one postal order company in Germany,
that sorts parcel according to the individual rules of 13 different
european countries, an with barcode labels having a rather limited
amount of expression, wrt. length and typology, this leads to
insanity.
--
/Wegge
Leder efter redundant peering af dk.*,linux.debian.*
|
|
|