Volume 2: Inside Software: How Real Systems Are Built4/10
Chapter 04 of 10
Developer Workflow 131-140
10 lessons66 min readingParts 131-140
- 01Version ControlHow do developers track and coordinate changes to source code?7 min read7 min read
- 02Git CommitsWhat makes a useful unit of source-code history?7 min read7 min read
- 03Branches and MergingHow can several lines of work progress without constantly interfering?6 min read6 min read
- 04Code ReviewWhy should another person inspect a change before it ships?7 min read7 min read
- 05Package Managers and DependenciesHow does a project install and track reusable software components?7 min read7 min read
- 06Semantic VersioningWhat are major, minor, and patch version numbers trying to communicate?6 min read6 min read
- 07Build ToolsWhy does source code often need a build step before it can run?6 min read6 min read
- 08Development, Test, and Production EnvironmentsWhy do teams run the same software in several environments?6 min read6 min read
- 09Feature FlagsHow can code be deployed without immediately exposing a feature to everyone?6 min read6 min read
- 10Documentation That Stays UsefulWhat technical information is worth writing down?8 min read8 min read