|Subject:||[Info-gne] shout spades|
|Date:||Mon, 16 Oct 2006 13:16:23 +0100|
|User-agent:||Thunderbird 188.8.131.52 (Windows/20060909)|
It looks great as documentation, but is more cumbersome to write.
That time investment is repaid later. One object can perfectly well be an Edit and several other things as well.
Are there any regularities to what teams of good people actually do, in the ways they transform inputs into outputs ?
We can say everything we have a need to say about that role in one and only one place.
Haben wir schon Krieg? So systems of this sort tend to have provisions for garbage collection and removal.
Only the rigidity remains.
This ups the ante for someone who would review the code without being intimately familiar with it.
And ran into a few enlightening problems. No big deal, just a missed encounter - and I now know more about Fit and Fitnesse. Kind of spooky - the conference that reads your mind. This mechanism is fundamental to, for instance, vaccination.
At a lower level of abstraction, we may well have different kinds of edits: major, minor, spellcheck, file upload, page deletion.
Are there any regularities to what teams of good people actually do, in the ways they transform inputs into outputs ? The type Edit can be an interface in Java terms, or a protocol in Smalltalk terms. This ups the ante for someone who would review the code without being intimately familiar with it.
We invest time in refactoring duplication out of the code. Big Robots, small robots, fun robots, scientific robots.
Another protein may fit into the first only if it has the proper shape for that slot, called a binding site.
That time investment is repaid later.
|[Prev in Thread]||Current Thread||[Next in Thread]|