top of page

Top 12 Engineering Quotes

11 minutes ago
4 min read

A good engineering quote can give you a useful thought to carry into the day.


It won't finish the calculation or review the drawing for you. But it can remind you to ask a better question, check the evidence or finally start the work you've been circling around.


These are twelve quotes I think are worth considering from an engineering perspective. They come from engineers, inventors, scientists, mathematicians and computing pioneers, so this isn't a claim that every person on the list held the same profession.


Each has a source link. The practical interpretation underneath is mine.


1. Theodore von Kármán: create something useful


“The scientist describes what is; the engineer creates what never was.”



This captures the creative responsibility of engineering. Understanding the world is part of the work; deciding what to make within its constraints is another. What useful result are you trying to bring into existence?


2. Wilbur Wright: build your capability


“It is possible to fly without motors, but not without knowledge and skill.”



The equipment matters, but so does the capability of the person using it. Before adding another tool to the process, ask whether you understand the problem and can judge the result the tool produces.


3. Thomas Edison: give the idea some work


“Genius is one percent inspiration and ninety-nine percent perspiration.”



Ideas need development. Sketching, comparing options, building and testing all take effort. My takeaway isn't to work endlessly; it's to give a promising idea a concrete next action instead of waiting for the complete solution to appear.


4. Michael Faraday: stay open, then test


“Nothing is too wonderful to be true, if it be consistent with the laws of nature”


This is a short excerpt from Faraday's laboratory-notebook entry, reproduced by Physics Today.


An unfamiliar idea deserves consideration. It also needs evidence. Curiosity and disciplined checking can work together; you don't have to choose one attitude for the whole project.


5. Ada Lovelace: connect different ways of thinking


“The Analytical Engine weaves algebraic patterns just as the Jacquard loom weaves flowers and leaves.”



The connection between a loom and computation makes an abstract capability easier to picture. Useful analogies can help you explain an idea, and sometimes they help you see a different way to approach it.


6. Charles Babbage: check what the question assumes


“I am not able rightly to apprehend the kind of confusion of ideas that could provoke such a question.”



Babbage was responding to a question about whether incorrect inputs could produce correct answers. Beneath the sharp wording is a practical reminder: inspect the assumptions behind a request before promising what the system can do.


7. Benjamin Franklin: produce the result


“Well done is better than well said.”



A persuasive explanation is useful. So is the evidence that the work meets its requirement. Finish the test, capture the result and make sure the promised output actually exists.


8. Alan Turing: take the next useful step


“We can only see a short distance ahead, but we can see plenty there that needs to be done.”



You won't remove every uncertainty before beginning a difficult project. Decide what you can establish next. A small piece of sound evidence can be more valuable than a detailed plan built on untested guesses.


9. Katherine Johnson: notice the ordinary details


“I counted everything.”



Johnson was describing her childhood curiosity. For me, the reminder is to pay attention to ordinary things. Counts, units, timing and patterns can reveal something important before you reach for a more elaborate explanation.


10. Margaret Hamilton: ask the question


“no question is a dumb question.”


This excerpt comes from Hamilton's advice in an interview highlighted by MIT News.


Admitting that you don't understand gives you a chance to learn. Carrying an unexamined assumption into the design can create more work later. Ask clearly, listen carefully and record the answer you need.


11. Grace Hopper: examine inherited habits


“we've always done it this way.”


This is the phrase Hopper challenged, rather than advice she endorsed; the context is described by the US Naval History and Heritage Command.


An established practice may have a very good reason. Find it. Then consider whether the reason and the current conditions still match.


12. Richard Feynman: keep the evidence in charge


“For a successful technology, reality must take precedence over public relations, for nature cannot be fooled.”



Confidence is not a test result. Engineering decisions need to stay connected to what the evidence supports, including uncertainty and inconvenient findings. This is a serious reminder to make the technical reality visible.


Pick one and put it to work


Which quote connects with something you're doing today?


Choose one and turn it into an action: check an assumption, ask a question, run an appropriate test or finish a small deliverable.


If writing helps you organise that thinking, see how taking notes can spark engineering inspiration.


A quote can provide the nudge. The useful part is what you do next.


 
 
 

Comments


HUBS[48131].png
OT Ultimate Guide Cover.png
bottom of page