Definitions: Architect vs Engineer vs Contractor

An Architect is said to be a man who knows a great deal about very little and who goes along knowing more and more about less and less until finally he knows practically everything about nothing.

An Engineer, on the other hand, is a man who knows a very little about a great deal and keeps knowing less and less about more and more until he knows practically nothing about everything.

A Contractor starts out knowing practically everything about everything, but ends by knowing nothing about anything, due to his association with Architects and Engineers.

Click on the hyperlink for more engineering humour.

1 Response to “Definitions: Architect vs Engineer vs Contractor”


  • This reminds me of the joke about experts knowing more and more about less and less until they know everything about nothing.

    It is an issue we have to deal with because we provide research and development services for hire and our clients all do different things. A quick survey of our current projects shows were are working on:
    - 3 phase power controller
    - tracking solar panels
    - microinverter
    - 2.4KW motor control
    - low power timing gates operating over wireless links
    - battery operated portable timer
    - active RFID based proximity warnign systems
    - plumbers electrical safety warning device
    - proximity card reader
    - corrosion protection monitoring data logger
    - inertial navigation add on for a GPS system
    - water metering and telemetry

    So for Electronics Design for the above we cover a fair few areas of technology. We must be engineers who have managed to stay away from architects and work with contractors who still know everything about everything.

    Ray Keefe
    Successful Endeavours Pty Ltd
    Casey Business of the Year 2010
    Industrial Electronics Future Award Winner 2011
    Award Winning Electronics Design and Embedded Software Development

Leave a Reply