Lists Home |
Date Index |
Miles Sabin <firstname.lastname@example.org> wrote:
| Arjun Ray wrote,
| Well, I've heard a lot of complaints about printf's in my time, but I
| don't think I've ever heard anyone complain about them being so simple
| that even chimps could use 'em ;-)
Oh, I wasn't complaining! Rather, it was an issue why the Printf Style
continues to have so much traction, and I think the answer is to a great
extent "managerial" - in terms of their (at least implicit) requirements
Albeit in a different context, Sean Mc Grath once described the phenomenon
as "Problem Containment":
: Utilmately, no one can buck the market and the market only buys what
: it can understand. Just ask Bill. The market understands percieved
: simplicity, short term gain, immediate results, problem containment.
:  Problem Containment
: There are two ways to get work done with a computer:-
: a) Manually: It will take hours but you will get there eventually.
: Progress will be slow but measurable. The total time required can
: be accurately estimated and budgeted for. Required expertise level
: can be diminished to the point where cheap/casual labor can do the job.
: Hell, if necessary, you can call in the kids to help out.
: b) Automatically: This involves an unmeasurable period of seemingly
: zero progress (software development/application configuration) followed
: by an instantaneous result - all going well. The expertise level is
: high, easily annoyed, expensive and drinks a lot of coffee.
: People who sign purchase orders will go for (a) far more often than (b).
|> parent.add( new Eusability( ).aFactor( 2 ).add( s ) ) ;
Oops, should have been:
parent.add( new Eusability( ).aFactor( i ).add( s ) ) ;
| You missed out the first step: "first write your vocabulary specific
Actually, that would be *generate* your vocabulary specific library. :-)
| That'd make sense in some cases, but clearly not in anything like all.
Where "all" includes spur-of-the-moment as-the-spirit-moves-you tag soup,