Build time
Build time is the elapsed duration required to transform source code and related inputs into a compiled, packaged, or otherwise built software artifact.
Shipping Go: Develop, deliver, discuss, design, and go again
Build time is the elapsed duration required to transform source code and inputs into a build artifact.
- How it is used
- Use build time as a delivery-process metric for finding opportunities to improve software development.
- How deep it goes
- Treats build time as a metric to monitor, but gives no measurement procedure or optimization steps.
- Examples
- Names long builds, flaky tests, build failures, dependency timeouts, slow build servers, and development environments as improvement signals.
- What you can do after
- Diagnose workflow bottlenecks by gathering metrics and discussing long builds and their possible causes.
Read how Shipping Go: Develop, deliver, discuss, design, and go again explains build time →
Go in Action, Second Edition
Compilation speed is the time or rate required to transform source code into executable or intermediate output.
- How it is used
- Uses compilation speed to support rapid development cycles and keep engineers in flow.
- How deep it goes
- Explains import-graph and type-system constraints that accelerate builds, but stops short of compiler implementation details.
- Examples
- Uses enormous codebases, file-save builds, and near-instant compiler feedback as concrete examples.
- What you can do after
- Evaluate/understand how Go's compiler constraints turn builds into a continuous development feedback loop.
Related concepts
- integration testproduced by · An integration test evaluates whether multiple software components, or a component and an external dependency, interact and behave correctly together.
- developer productivityproduces · Developer productivity is the value or amount of useful software work produced relative to the time, effort, and resources required.
- continuous improvementused by · Continuous improvement is an ongoing process of evaluating outcomes and making successive changes to improve a system, process, or result.
These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.