Engineering · Systems

The Case for Engineering as a Knowledge Discipline

Engineering is often reduced to building things. At its surface, that is what it looks like: circuits, systems, structures, software. But at its foundation, engineering is a systematic way of generating, applying and preserving knowledge about how the world works.

An engineer who designs a system without understanding the underlying physics is not really engineering — they are assembling. Engineering, properly understood, is the application of rigorous knowledge to the practical transformation of reality. And that makes it a knowledge discipline as much as any research field.

Engineering as investigation

Before any system is built, it must be investigated. What are the requirements? What are the constraints? What is the state of existing knowledge? What needs to be tested? What is not yet understood? Engineering begins as a form of structured inquiry — and the quality of the engineering depends heavily on the quality of that inquiry.

This is why, at Novae Ratio, engineering and research are not separate capabilities operating in parallel. They are connected. An engineering project begins with research. It generates new knowledge as it proceeds. And it ends — or should end — with documentation that makes that knowledge available for future use.

The documentation obligation

An engineering project that produces a working system but no documentation has produced something that cannot be maintained, replicated, improved or understood by anyone other than its creators. It is engineering that does not compound. The knowledge it generated is locked inside the system and inside the people who built it, where it will decay.

This is an institutional failure, even when the system works perfectly.

← All Articles