A Quote by Martin Fowler

Never in the annals of software engineering was so much owed by so many to so few lines of code — © Martin Fowler
Never in the annals of software engineering was so much owed by so many to so few lines of code
We flew down weekly to meet with IBM, but they thought the way to measure software was the amount of code we wrote, when really the better the software, the fewer lines of code.
Never in the field of human conflict was so much owed by so many to so few.
Code reuse is the Holy Grail of Software Engineering.
Software engineering is the establishment and use of sound engineering principles to obtain economically software that is reliable and works on real machines efficiently.
Trying to read our DNA is like trying to understand software code - with only 90% of the code riddled with errors. It's very difficult in that case to understand and predict what that software code is going to do.
Simply put, when you have very large pieces of software, most of the tools look at the individual lines of code as text. It is often extremely powerful to look not at individual pieces of code but at a system as a whole.
A short, glorious life in service of a greater good - say, the life of the Spartans at Thermopylae, or the pilots in the Battle of Britain, of whom Winston Churchill said 'Never have so many owed so much to so few,' - that is worth praising. But for glory alone? I think not.
Type a few lines of code, you create an organism.
No man is greater than his prayer life. The pastor who is not praying is playing; the people who are not praying are straying. We have many organizers, but few agonizers; many players and payers, few pray-ers; many singers, few clingers; lots of pastors, few wrestlers; many fears, few tears; much fashion, little passion; many interferers, few intercessors; many writers, but few fighters. Failing here, we fail everywhere.
Perhaps the worst software technology of all time was the use of physical lines of code [for metrics]. Continued use of this approach, in the author's opinion, should be considered professional malpractice.
If we wish to count lines of code, we should not regard them as "lines produced" but as "lines spent."
There is no one "root of all evil" in software development. Design is hard in many ways. People tend to underestimate the intellectual and practical difficulties involved in building a significant system involving software. It is not and will not be reduced to a simple mechanical "assembly line" process. Creativity, engineering principles, and evolutionary change are needed to create a satisfactory large system.
Never before in human history have so few owed so much to so many, Mr. Jiabao. A handful of men in this country have trained the remaining 99.9 percent—as strong, as talented, as inteligent in every way—to exist in perpetual servitude; a servitude so strong that you can put the key of his emancipation in a man's hands and he will throw it back at you with a curse.
It seemed really amazing that you could write a few lines of code and have it learn to do interesting things.
The gratitude of every home in our Island, in our Empire, and indeed throughout the world, except in the abodes of the guilty, goes out to the British airmen who, undaunted by odds, unwearied in their constant challenge and mortal danger, are turning the tide of the World War by their prowess and by their devotion. Never in the field of human conflict was so much owed by so many to so few.
There's a strong distinction to be made between dry code smart contacts and wet code's physical law. So law is based on our minds, our wetware - it's based on analogy. The law is more flexible; software is more rigid. Various laws tend to be batched in jurisdictional silos. Software tends to be independent.
This site uses cookies to ensure you get the best experience. More info...
Got it!