From the course: Agile Software Development: Remote Teams
Join today to access over 22,500 courses taught by industry experts or purchase this course individually.
Branching and forking
From the course: Agile Software Development: Remote Teams
Branching and forking
- [Instructor] Before I came into the software industry, I worked as a writer, specializing in business communication. My team and I would write articles, blog posts, website content, all sorts of stuff. The basic process went like this. Draft, review, publish. We had a rule that nothing would go out unless it had at least two pairs of eyes. This drastically reduced the number of errors that made it into publication, and helped improve the quality of our work. This same basic process applies to software development too. Let's look at how this process works using branches, forks, and poll requests. If a developer wants to change some code, it's probably not a good idea for them to log into the server where the live code is running and just start making changes. This is a huge risk, especially on a team with more than one contributor, and drastically increases the chances that the application will crash, frustrating pretty much everyone. Instead, you want to set up your process so that…
Practice while you learn with exercise files
Download the files the instructor uses to teach the course. Follow along and learn by watching, listening and practicing.
Download courses and learn on the go
Watch courses on your mobile device without an internet connection. Download courses using your iOS or Android LinkedIn Learning app.