The Engineer sees science as a problem to solve. How can I build systems and processes that see through the noise of biology and deliver an answer to my question? Your experiments aren't 'one-offs', they are robust – they are tested with different samples and different conditions. When you get the data, you don't jump to a verdict, each data point is rigorously analysed before you think about drawing any conclusions.

That's not to say that the Engineer is an over-optimiser. You are guided, not by process, but by a clear objective. "Put man on the moon by the end of the decade". "Clone 100 genes by Friday". That sort of thing. Once you reach that objective, you look for the next problem to solve. Your solutions don't need to be perfect, but they do need to get the job done properly.

While you're building your next great system, remember that many of the greatest discoveries in science came through serendipity. Don't be afraid to turn over a few stones while you're running your finely tuned workflows. You never know what you might find.

Perhaps discuss your results with The Visionary every now and then? They might spot something unexpected that you missed.