The scientist builds in order to study; the engineer studies in order to build.

Study to build, or build to study?

There's a useful tension hiding in this distinction. Scientists are driven by curiosity—they want to understand how things work, and building something is just their way of testing ideas. Engineers flip that priority: they have a problem to solve or something to create, so they learn whatever's necessary to make it happen. Both approaches need each other, but they can clash when they work together.

In real life, this shows up everywhere. A researcher might spend months perfecting a model that captures every variable, while a team launching a product needs a working solution by next month. Neither is wrong—they're just operating from different engines. The scientist wants truth; the engineer wants function. The surprise is how often the best innovations come from people who can do both: study enough to avoid obvious mistakes, but stay focused on actually shipping something real.

If you're stuck between learning something perfectly and just getting started, Brooks suggests asking yourself which role you're actually playing right now. Are you building to discover, or discovering to build? That clarity alone can cut through a lot of unnecessary wheel-spinning.