How deeply does Think Like a CTO cover parallel development?

Defines the operational rationale and illustrates a production-fix scenario, but does not detail integration procedures.

Parallel development

As explained in Think Like a CTO

A software-development approach in which multiple lines of work proceed concurrently and are later integrated.

Parallel development lets one or more developers work on multiple lines of work concurrently, then integrate changes without manually reshaping environments to maintain versions. Version control provides the library and time vault that makes this practical. section 9.3

A defensible setup should let teams:

Preserve the production code separately while developing a future version. section 9.3
Fix an urgent production bug without accidentally releasing unfinished features. section 9.3
Replace informal directories and zip-file backups with tracked versions and shared history. section 9.3

Production fix during new development

A team developing a new release can retrieve the code currently running in production, correct a bug there, and release the fix without allowing new work to leak into production. section 9.3

How Think Like a CTO covers it

liveBook manning.com

Read Think Like a CTO on liveBook Get the book at manning.com

Related concepts

mockingaddressed by · Mocking is a testing technique that replaces a real dependency with a controlled substitute to simulate behavior or inspect interactions.
stubused by · A stub is a stand-in for a component or operation that exposes an interface while substituting simplified, generated, or controlled behavior for its full implementation.
versioningproduced by · The practice of identifying and managing successive revisions of files, data, models, interfaces, or other artifacts so changes can be tracked and earlier states recovered.

This explainer was generated by Manning's knowledge graph from the text of Think Like a CTO. The section links point to the parts of the book it draws on.