I wonder if this is a static vs dynamic or compiled vs interpreted reference.
Anyway I love it. Made me giggle that we are still discussing this today, and just to be clear I love both sides, for different things.
> Since size is such a large part of the user cost of a programming system product, the builder must set size targets, control size, and devise size-reduction techniques, just as the hardware builder sets component-count targets, controls component count, and devises count-reduction techniques. Like any cost, size itself is not bad, but unnecessary size is.
And the why of Agile, DDD and TDD:
> Plan the System for Change [...] Plan the Organization for Change