As inanimate as it was gigantic A Fragment by John Ruskin blog.ayjay.org And among such false means largeness of scale in the dwelling-house was of course one of the easiest and most direct. All persons, however senseless or dull, could appreciate size: it required some exertion of intelligence to enter into the spirit of the quaint carving of the Gothic times, but none to perceive that one heap of stones was higher than another. And therefore, while in the execution and manner of work the Renaissance builders zealously vindicated for themselves the attribute of cold and superior learning, they appealed for such approbation as they needed from the multitude, to the lowest possible standard of taste; and while the older workman lavished his labor on the minute niche and narrow casement, on the doorways no higher than the head, and the contracted angles of the turreted chamber, the Renaissance builder spared such cost and toil in his detail, that he might spend it in bringing larger stones from a distance; and restricted himself to rustication and five orders, that he might load the ground with colossal piers, and raise an ambitious barrenness of architecture, as inanimate as it was gigantic, above the feasts and follies of the powerful or the rich. architecturesizescale
The heart of systems engineering While the client has some knowledge of his symptoms, he may not understand the real causes of them, and it is foolish to try to cure the symptoms only. Thus while the systems engineers must listen to the client, they should also try to extract from the client a deeper understanding of the phenomena. Therefore, part of the job of a systems engineer is to define, in a deeper sense, what the problem is and to pass from the symptoms to the causes. Just as there is no definite system within which the solution is to be found, and the boundaries of the problem are elastic and tend to expand with each round of solution, so too there is often no final solution, yet each cycle of input and solution is worth the effort. A solution which does not prepare for the next round with some increased insight is hardly a solution at all. I suppose the heart of systems engineering is the acceptance that there is neither a definite fixed problem nor a final solution, rather evolution is the natural state of affairs. This is, of course, not what you learn in school, where you are given definite problems which have definite solutions. Richard Hamming, The Art of Doing Science and Engineering: Learning to Learn What the problem isComplete and consistent requirements