Tea and Engineering

My old theory about scientists and engineers was simple: the scientist drinks tea while the engineer works. There was another version too. The scientist discovers something, and the engineer turns it into money. These were not serious definitions; they were professional jokes produced by someone who was already tired enough to believe that engineering had received the harder part of the bargain.

Engineering felt full of unfinished things. Design it, build it, test it, fix it, make it cheaper, make it faster, make sure someone else can maintain it, then explain why it still cannot be ready by Friday. From inside that rhythm, science could look wonderfully peaceful: think, research, drink tea, discover something.

Of course, this was nonsense. Scientists also spend nights with failed experiments, bad data, broken equipment, rejected papers, and questions that refuse to become answers. Every profession sees the polished output of the other one and misses most of the failed attempts behind it. The engineer sees the paper; the scientist sees the finished product.

Over time, I also stopped believing that the boundary was very sharp. An engineer facing a strange bug becomes a scientist for an hour: observe, form a hypothesis, change one thing, test again. A scientist building an instrument becomes an engineer: design, choose materials, make it reliable. The roles move according to the problem.

Maybe that was the better answer all along. The scientist drinks tea. The engineer drinks tea too. Then both go back to work.