Zero-cost build step

Zero-cost abstraction is a key concept in programming, particularly associated with languages like C++ (where the “zero-overhead principle” originates) and Rust.

The core idea is that you can use high-level, expressive programming tools (abstractions) without incurring any runtime performance overhead compared to writing the equivalent, highly-optimized, low-level code by hand.

BigConfig approach

Zero-cost build step wants to convey the same idea for authoring configuration files. Writing code instead of configurations files doesn’t slow down the inner loop during development.

The inner loop in development refers to the rapid, iterative cycle a developer goes through to write code, test it locally, get immediate feedback, and refine it. It’s the tight feedback cycle for making small, frequent changes.

This loop typically involves the following steps:

1. Code/Edit: Writing or modifying source code in an editor or IDE.
2. Build/Compile: Transforming the source code into an executable format (if applicable).
3. Run/Execute: Starting the application or running the newly changed part of the code locally.
4. Test/Debug: Observing the results, testing functionality, and identifying and fixing bugs.

Key Characteristics

• Speed: The primary goal is to make this cycle as fast as possible (ideally seconds or a few minutes) to maintain the developer’s focus and productivity.
• Local Scope: It primarily uses tools and environments on the developer’s local machine (or a local development container).
• Immediate Feedback: The developer gets instantaneous feedback on the success or failure of their small change.

Frontend development

The build step has long been a fundamental and beneficial part of frontend development. Technologies like TypeScript, JSX, and MDX are prime examples, demonstrating that the build process enhances developer productivity and does not disrupt the inner development loop (the cycle of coding and seeing results).